Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [wtp-dev] Proposal to move to "3.2 Style Builds" using ".qualifier" even for 1.0.1


>I think the compiler change is low risk.
>I would think the qualifier change is bigger. How does it affect adopters?

Thanks Arthur. Adopters do not need to make any changes to their plugins or features, they should continue to use
"1.0" in their "requires" statements (or, maybe 1.0.1, in some cases, depending on their needs),
but never that 4th field.

So, I would have said "no effect" but ... wouldn't you know ... there did just happen to be guy down the hall that
had a custom build/copy utility that proved me wrong. Since these types of problems would have
to be fixed anyway, I do not think this will be prohibitive and adopters can fix their scripts now instead of later .. if by chance
they were mistakenly assuming there always had to be 3 fields.

The experience did, however, emphasize we should broadly disseminate the information,
so I posted following to our WTP newsgroup.

and created a bugzilla entry for comment/problems.
Bug 125257 Should move to ".qualifier" version of plugins, even for WTP 1.0.1
https://bugs.eclipse.org/bugs/show_bug.cgi?id=125257

I will, however, make the change in our WTP M-builds tonight, so we will have time to
react (or "back out") if any issues found.

David


= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Display all headersFrom: "David Williams" <david_williams@xxxxxxxxxx>
Newsgroups: eclipse.webtools
Subject: NOTICE to adopters: WTP 1.0.1 will move to use 4th field "service" qualifier in plugin versions
Date: Wed, 25 Jan 2006 17:29:07 -0500
Organization: IBM

 
 
I wanted to be sure this notice got wide attention, so am posting here, even though
this won't effect "end users" -- only those who adopt WTP in their products or
add ons, and even then, only those that might "rebuild" it or otherwise have custom
ant scripts, or similar.
 
You can see or respond to following bugzilla entry,
Bug 125257 Should move to ".qualifier" version of plugins, even for WTP 1.0.1
https://bugs.eclipse.org/bugs/show_bug.cgi?id=125257
 
but in brief, there's good reason to use 4 qualifiers
in a plugin or features version
identifier, such as, 1.0.1.v20060214
where that last one is the CVS tag of the version
that was used in that build. This is the plan for eclipse
3.2 based components anyway, and in our case, makes
sense to move to this scheme now, even though WTP 1.0.1
will still be based on eclipse 3.1
 
Typically this would be completely transparent to everyone
(except for long ugly file names in some cases
 
but we have heard of at least one case of one large
international business machine company that
had some copy/build script somewhere
that didn't like the four fields very well.
 
Since any adopters that have similar scripts would
have to fix them for 3.2 based scripts or builds anyway,
we are hoping to beg your indulgence and get things fixed now.
Please post concerns or problems to bug 125257.
 
Any adoptees of WTP would continue to "require/import" simply
version "1.0" in the runtime version of their plugins, so no
changes are required there (there might be some cases where you'd
want to use 3 fields in a "requires", but ... I don't ever think
you'd need or want to ever use all 4 fields).
 
For anyone who hasn't kept up with the 3.2 planned versioning scheme, the
best reference for it is
http://www.eclipse.org/equinox/documents/plugin-versioning.html
 
Thanks,
 

Back to the top