Eclipse Community Forums: ServerTools (WTP) » <import feature="org.eclipse.wst" version="1.5" match="equivalent"/

Home » Language IDEs » ServerTools (WTP) » <import feature="org.eclipse.wst" version="1.5" match="equivalent"/

<import feature="org.eclipse.wst" version="1.5" match="equivalent"/ [message #176220]

Thu, 03 August 2006 08:16

Eclipse User

<import feature="org.eclipse.wst" version="1.5" match="equivalent"/>

Should this match:

1.5
1.5.0
1.5.0.vANYTHING
1.5.1
1.5.1.vANYTHING
1.5.2
1.5.2.vANYTHING
1.5.9999999
1.5.9999999.vANYTHING

But not:

1
1.4
1.6
2
2.0

At this moment this doesn't work like this. The ATF plugins correctly
(IMHO) set <import feature="org.eclipse.wst" version="1.5"
match="equivalent"/> but it does not match for
org.eclipse.wst_1.5.0.v200606092300-boSnpRZVq78N2Sm from this weeks WTP
I-build in update manager.

Question two, with the addition of the ".0" in "1.5.0" :

<import feature="org.eclipse.wst" version="1.5.0" match="equivalent"/>

Should this match:

1.5.0
1.5.0.vANYTHING

But not:

1
1.4
1.5
1.5.1
1.5.1.vANYTHING
1.5.2
1.5.2.vANYTHING
1.5.9999999
1.5.9999999.vANYTHING
1.6
2.0

Re: <import feature="org.eclipse.wst" version="1.5" match="equivalent&qu [message #176244 is a reply to message #176220]

Thu, 03 August 2006 14:45

Eclipse User

Hi Darryl,

Thanks for reporting this issue. Have you opened a bug? If not, care to
open one against Web Tools->releng.

Lawrence

Re: <import feature="org.eclipse.wst" version="1.5" match="equivalent&qu [message #176279 is a reply to message #176244]

Thu, 03 August 2006 15:52

Eclipse User

lmandel@ca.ibm.com wrote:
> Thanks for reporting this issue. Have you opened a bug? If not, care to
> open one against Web Tools->releng.

https://bugs.eclipse.org/bugs/show_bug.cgi?id=152782

Another related question, why do you bump the version of the I-build
drivers into the next minor release. For example you are already using
1.5.1.v200601010000 but 1.5.1 has not been released yet.

Using 1.5.0.v200601010000 with a higher date is more natural to
understand, that being "a successive build based on 1.5.0 but not yet
1.5.1".

From a which is older/newer standpoint the current method obviously
works fine with the date in it. Maybe this is just a caveat of your
release method chosen but goes a little against the norm.

It would also be really dandy to have pretty names for releases, so when
you spin the build one last time after tagging a release the generated
files gets pretty names when the CVS tag conforms to a release version:

plugins/org.eclipse.wst_1.5.0.v200606092300-RELEASE

Darryl

Previous Topic:	Version number problems with last weeks Integration build
Next Topic:	getFinalPerspectiveID

Goto Forum:

-=] Back to Top [=-

Current Time: Fri Jul 25 13:28:54 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter