Hello,
I downloaded Jalview 2.7 source today and have started integrating it with the Phytozome system. So far everything looks great!
The only hitch I’ve run into is that the build.xml still sets the version of Jalview to “DEVELOPMENT”. I’ve changed it for my local build to “2.7”, but ideally we would like to work with a version of the Jalview that is completely unmodified. Would it be possible for you to make this change?
Thanks,
Joni
···
–
Plant and Computational Genomics Group
Joint Genome Institute - U.S. Dept. of Energy
http://www.phytozome.net
Hi Joni.
I downloaded Jalview 2.7 source today and have started integrating it with the Phytozome system. So far everything looks great!
glad to hear it, and I'd be interested in checking out the latest phytozome when its available!
The only hitch I've run into is that the build.xml still sets the version of Jalview to "DEVELOPMENT". I've changed it for my local build to "2.7", but ideally we would like to work with a version of the Jalview that is completely unmodified. Would it be possible for you to make this change?
The version not coded in the source, but is intentionally a build time configurable property - both the build date and version are recorded in the jalview.jar when the ant task creates it. You've basically got 3 options here:
1. If you simply want to take an existing, unmodified version of jalview, then I suggest you download the jars at http://www.jalview.org/webstart/, since these have been produced using the standard production build pipeline. That's almost certainly the simplest approach, and one that has been used by other sites.
2. If you don't want to add any new Java code to Jalview then you could even get away with a custom JNLP which launches jalview from www.jalview.org but passes in your own groovy script arguments.
3.Alternately, 'ant -propertyfile RELEASE makedist' in the jalview source directory will build a jalview.jar with the correct version. Note, however, that if you do this, the build time will be different, but this might be useful to you.
Take your pick!
Jim.
···
On 04/10/2011 22:52, Joni Fazo wrote:
Thanks Jim! I used a combo of options 1 and 2.
I downloaded all the required jars from http://www.jalview.org/webstart/ , and then packaged them up into a WAR file with our servlet that creates a JNLP to fire up Jalview with our groovy startup script and custom jalview.properties.
As always, thanks for your great support!
Joni
···
–
Plant and Computational Genomics Group
Joint Genome Institute - U.S. Dept. of Energy
http://www.phytozome.net
On Wed, Oct 5, 2011 at 12:45 AM, Jim Procter <jprocter@compbio.dundee.ac.uk> wrote:
Hi Joni.
On 04/10/2011 22:52, Joni Fazo wrote:
I downloaded Jalview 2.7 source today and have started integrating it with the Phytozome system. So far everything looks great!
glad to hear it, and I’d be interested in checking out the latest phytozome when its available!
The only hitch I’ve run into is that the build.xml still sets the version of Jalview to “DEVELOPMENT”. I’ve changed it for my local build to “2.7”, but ideally we would like to work with a version of the Jalview that is completely unmodified. Would it be possible for you to make this change?
The version not coded in the source, but is intentionally a build time configurable property - both the build date and version are recorded in the jalview.jar when the ant task creates it. You’ve basically got 3 options here:
- If you simply want to take an existing, unmodified version of jalview, then I suggest you download the jars at http://www.jalview.org/webstart/, since these have been produced using the standard production build pipeline. That’s almost certainly the simplest approach, and one that has been used by other sites.
- If you don’t want to add any new Java code to Jalview then you could even get away with a custom JNLP which launches jalview from www.jalview.org but passes in your own groovy script arguments.
3.Alternately, ‘ant -propertyfile RELEASE makedist’ in the jalview source directory will build a jalview.jar with the correct version. Note, however, that if you do this, the build time will be different, but this might be useful to you.
Take your pick!
Jim.