From: Rajarshi G. <raj...@gm...> - 2010-06-20 13:23:39
|
Patch uploaded (with a simple solution that doesn't require a new class or packaging build.props) On Sat, Jun 19, 2010 at 4:17 PM, Egon Willighagen <ego...@gm...> wrote: > On Sat, Jun 19, 2010 at 10:14 PM, Rajarshi Guha <raj...@gm...> wrote: >> Hi, it would be useful to have a static function or field somewhere >> that would return the version of the library. Maybe a constant in >> CDKConstants? For external code that depends on the CDK, it'd be a >> handy way to indicate the a new version of the CDK is required etc > > Yes, that would indeed be useful. > > I suggest a class org.openscience.cdk.CDK > > with a method that takes the version from the build.props which we > would put in the jar file. > > That way we do not have to update the constant and/or class all the > time, which will be forgotten at some point :) > > Egon > > -- > Post-doc @ Uppsala University > Proteochemometrics / Bioclipse Group of Prof. Jarl Wikberg > Homepage: http://egonw.github.com/ > Blog: http://chem-bla-ics.blogspot.com/ > PubList: http://www.citeulike.org/user/egonw/tag/papers > > ------------------------------------------------------------------------------ > ThinkGeek and WIRED's GeekDad team up for the Ultimate > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > lucky parental unit. See the prize list and enter to win: > http://p.sf.net/sfu/thinkgeek-promo > _______________________________________________ > Cdk-devel mailing list > Cdk...@li... > https://lists.sourceforge.net/lists/listinfo/cdk-devel > -- Rajarshi Guha NIH Chemical Genomics Center |