Hi guys,
As talked with Marshall I did a small test for how the versioning numbering affects the update mechanism.
If I make a update site with the following features:
id="nestea.feature" version="1.0.0"
id="nestea.feature" version="1.0.1.N20050516123460"
id="nestea.feature" version="1.0.1.N20060516123460"
Then everything seems to work fine, BUT when I
add
id="nestea.feature" version="1.0.1
then it is not calculated as the latest version -
id="nestea.feature" version="1.0.1.N20060516123460" is.
This is not bad if its the first time you install from the site
because you can then choose the proper latest version, but when
you want to update you wont be able to select the versions eclipse
thinks is "behind" a version.
so if you have 1.0.1.NSOMETHING installed and 1.0.1 is released then you wont be able to install it.
seems like we have to have the nightly builds stay at the last released version number (1.0.0.NXXX) and then only upgrade the actual version 1.0.1 when we want to release)
...any comments/ideas/info on how other plugins does this stuff (besides not providing updatesite for nighlty builds :)
/max
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3877803#3877803
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3877803
|
