Rajesh Kartha wrote: > J�rg von Frantzius (JIRA) wrote: > >> Bad Eclipse plugin version specification >> ---------------------------------------- >> >> Key: DERBY-153 >> URL: http://issues.apache.org/jira/browse/DERBY-153 >> Project: Derby >> Type: Bug >> Versions: 10.1.0.0 Environment: Eclipse 3.1 M5 (probably >> problematic also with earlier versions) >> Reporter: J�rg von Frantzius >> >> >> In the plugin.xml of the Derby Eclipse plugin, the version >> specification reads "10.1.0.0 (124830)", which Eclipse complains >> about as being illegal. In consequence, the plugin is not loaded. >> >> The Eclipse docs have the following to say about the version >> specification: "Plug-in version format is >> major.minor.service.qualifier". >> >> Stripping the "(1234830)", whatever that is anyway, solves the problem. >> >> >> > Hello, > I will look into that. The big number (1234830) is the Derby build > number. The Derby plugin version worked fine on Eclipse 3.0 and hence > we decided to add that in there, but looks like things have changed > again in Eclipse 3.1 M5. > > I will post my changes to the dev-list soon after testing the newer one. > > Regards, > Rajesh > > > > Perhaps a sideline, but I wonder, since we have so few fixes going into the release branch if it might not be more practical to just bump that fourth number in the version each time a fix goes into the release branch instead of relying on the build number to differentiate. Does that sound like a good idea? Could it be automated?
