Download the latest version of JPhyloIO
This is the latest version of JPhyloIO (1.0.0-1681 beta) which was released on 2019-06-12 15:30:00.0.
License
JPhyloIO is distributed under GNU Lesser General Public License. Copyright (C) 2015 - 2018 by Ben Stöver and Sarah Wiechers. This program is distributed in the hope that it will be useful, but without any warranty; without even the implied warranty of merchantability or fitness for a particular purpose. See the GNU Lesser General Public License for more details.
By downloading JPhyloIO you agree with the License. Please read it carefully.
Note that the releases 0.0.0 and 0.1.0 were distributed under GNU General Public License instead.
Downloads
Complete download
The complete download contains the classes of all components associated with this release.
| Complete binary, sources, docs |
|
|---|---|
| Complete binary only |
|
[Browse source codes] [Browse JavaDoc]
Single component downloads
The following components are associated with version 1.0.0. Components that were updated in this version are shown in bold.
| Component | Module binary JAR | Module sources |
|---|---|---|
| Core |
|
|
Subversion
Developers can also check out the source codes directly from the subversion repository under https://secure.bioinfweb.info/Code/svn/JPhyloIO/trunk/main/.
Maven
Developers can use the following code to add dependencies for the modules of JPhyloIO to their Maven project.
Dependencies
<dependency>
<groupId>info.bioinfweb.jphyloio</groupId>
<artifactId>jphyloio-core</artifactId>
<version>1.0.0</version>
</dependency>
Repository
<repository>
<id>bioinfweb-maven-repo</id>
<name>bioinfweb repository</name>
<url>http://bioinfweb.info/MavenRepository/</url>
</repository>
Changes in this version
- New version of core.
- JPhyloIO left alpha state and now has uses major version number 1. API will remain stable under this major version number.
Core
- The parameter ReadWriteParameterNames.KEY_TRANSLATE_INTERNAL_NODE_NAMES now allows to determine whether internal node names in [i]NEXUS[/i] documents should be translated using the taxon list from the [i]TAXA[/i] block of a translation table. Not translating them can be useful if support values are provided as internal node names.
