wiki:net.sf.basedb.mev

Version 17 (modified by nicklas, 6 years ago) (diff)

Releasing MeV Launcher 1.8

MEV Launcher extension for BASE

This package is an extension package to BASE that installs an action that opens TIGR MultiExperiment Viewer (MEV) as a Java webstart application and automatically imports data from the currently selected bioassay set. For more information:

Documentation

README contains information about this package, how to install it and how to compile it.

License

GNU General Public License version 3.

Download

Version Revision Date Binary (tar.gz) BASE Version* MeV Version* *
1.8 1444 November 2, 2011 mev-launcher-1.8.tar.gz (16MB) 3.0 4.7.3 changelog
1.7 1263 November 3, 2010 mev-launcher-1.7.tar.gz (16MB) 2.16 4.6.01 changelog
1.6 1192 February 22, 2010 mev-launcher-1.6.tar.gz (19MB) 2.14 4.5.01 changelog
1.5 1183 October 22, 2009 mev-launcher-1.5.tar.gz (20MB) 2.13 4.4.01 changelog
1.4 1154 August 31, 2009 mev-launcher-1.4.tar.gz (20MB) 2.12 4.4.01 changelog
1.3 1100 May 28, 2009 mev-launcher-1.3.tar.gz (19MB) 2.12 4.3.02 changelog
1.2 1017 March 31, 2009 mev-launcher-1.2.tar.gz (19MB) 2.11 4.3.02 changelog
1.1 1012 March 30, 2009 removed due to critical bugs 2.11 4.3.02 changelog
1.0 696 May 13, 2008 mev-launcher-1.0.tar.gz (12MB) 2.7 4.0.01 (modified for BASE) changelog

* In general, each release works with the specified and later BASE versions, except that releases for BASE 2 do not work with BASE 3.

* * All MeV components that are needed are include in the mev-launcher-*.tar.gz downloads. You do not have to download MeV separately.

Source code can be downloaded from the subversion repository. Use the following command to get source code for the 1.8 version:

svn co http://baseplugins.thep.lu.se/svn/extensions/net.sf.basedb.mev/tags/1.8 mev-1.8

The latest development (maybe unstable; do not use on a production server) revision can be checked out from the repository using the following command:

svn co http://baseplugins.thep.lu.se/svn/extensions/net.sf.basedb.mev/trunk mev-devel

Contribute

After making modifications to the source code, compose a clear and concise log message to describe those changes and the reasons for them. Then, send an email to the developers list containing your log message and the output of svn diff (from the top of your subversion working copy). If the community members consider your changes acceptable, someone who has commit privileges will add your changes to the public source code tree. Recall that permission to directly commit changes to the repository is granted on merit - if you demonstrate comprehension of subversion, programming competency, and a team spirit, you will likely be awarded that permission.

TODO

No results

Attachments (11)