Hmm, this is nice as it doesn't need to touch source files. But I suppose it only works when you're working with a jar'd version of the classes
On Thu, Jul 22, 2010 at 2:35 PM, Nina Jeliazkova <[email protected]> wrote: > Hi All, > > Another approach to versioning is to use package versions, provided they are > written in the package manifest files. > > http://download.oracle.com/docs/cd/E17476_01/javase/1.4.2/docs/api/java/lang/Package.html > > "Package objects contain version information about the implementation and > specification of a Java package. This versioning information is retrieved > and made available by the ClassLoader instance that loaded the class(es). > Typically, it is stored in the manifest that is distributed with the > classes. > > The set of classes that make up the package may implement a particular > specification and if so the specification title, version number, and vendor > strings identify that specification. An application can ask if the package > is compatible with a particular version, see the isCompatibleWith method for > details." > > Best regards, > > Nina > > > > On Thu, Jul 22, 2010 at 9:21 PM, gilleain torrance > <[email protected]> wrote: >> >> Hmmm. On the one hand I do agree with Rajarshi that a whole class for >> this is a bit heavyweight, but it does open the door for other >> properties for the library to be made programatically available. >> >> The problem is : what? The only thing that occurs to me is what >> modules are available - but the code wouldn't compile if the module >> wasn't there. In any case, you could probably use the classloader for >> that. >> >> The CDKConstants class is a bit of a god class - if that's the right >> anti-pattern - but I'm not sure it's the largest building in CDK >> city... >> >> http://gilleain.blogspot.com/2008/11/cdk-city.html >> >> gilleain >> >> On Thu, Jul 22, 2010 at 2:18 PM, Egon Willighagen >> <[email protected]> wrote: >> > Hi all CDK-users, >> > >> > it is time for a short popularity poll: please do reply, whatevery >> > your opinion is. >> > >> > Rajarshi and I want to introduce a method to get the version number of >> > a particular CDK release. We both came up with two difference patches: >> > >> > Patch 1: >> > add a static string field to CDKConstants that gets updated by the >> > build script, but leads to one extra change and commit for each >> > version >> > >> > Patch 2: >> > use the version in the already existing build.props, and have a new >> > class with the CDK.getVersion() method. This has the obvious downside >> > that we have another extra class, but does not require code changes >> > with each new version. >> > >> > Both for pros and cons... please discuss your favorite approach, >> > further ideas, etc. >> > >> > One particular question would be: is there other information about the >> > library you like to have available via the API? >> > >> > Your input would be very much appreciated! >> > >> > Egon >> > >> > >> > ---------- Forwarded message ---------- >> > From: Rajarshi Guha <[email protected]> >> > Date: Thu, Jul 22, 2010 at 3:03 PM >> > Subject: Re: [Cdk-devel] mol2 reader not working >> > To: Egon Willighagen <[email protected]> >> > Cc: "Developers forum for discussion about the Chemistry Development >> > Kit (CDK)" <[email protected]> >> > >> > On Thu, Jul 22, 2010 at 2:45 AM, Rajarshi wrote: >> >>> The following we should take to the mailing list, I guess... >> >>> >> >>> 3018684 Add a constant to indicate library version >> >>> >> >>> Please check my comments, and see how I can make my patch acceptable >> >>> for you... would it help if I added more functionality to the CDK >> >> >> >> Your approach makes sense, but I still think a whole class extra class >> >> for a version string is a bit overkill. Lets see what the mailling >> >> ist has to say? >> > >> > -- >> > Rajarshi Guha >> > NIH Chemical Genomics Center >> > >> > >> > >> > -- >> > 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 >> > >> > >> > ------------------------------------------------------------------------------ >> > This SF.net email is sponsored by Sprint >> > What will you do first with EVO, the first 4G phone? >> > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first >> > _______________________________________________ >> > Cdk-user mailing list >> > [email protected] >> > https://lists.sourceforge.net/lists/listinfo/cdk-user >> > >> >> >> ------------------------------------------------------------------------------ >> This SF.net email is sponsored by Sprint >> What will you do first with EVO, the first 4G phone? >> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first >> _______________________________________________ >> Cdk-user mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/cdk-user > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Sprint > What will you do first with EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > _______________________________________________ > Cdk-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/cdk-user > > -- Rajarshi Guha NIH Chemical Genomics Center ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Cdk-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/cdk-user
