[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [eclipse-dev] 2.0.1 builds
|
Darn, it's for me ;-)
we can do
1) change all the version of all
the features to 2.0.1, when your plugin changes, change the plugin.xml to 2.0.1,
change the version of you rplugin in your feature.xml to 2.0.1.
All the
features will be installed, only 2.0.1 plugin will be installed.
2)
follow Peter's recommendation. If your plugin change, change the version in
plugin.xml, change the version of your plugin in your feature.xml, change the
version of feature.xml, [change the version of this feature in feature.xml that
requires this feature, change the version of the feature.xml that requires this
feature (recursively to the top)]
only new features and new plugins will be
installed
Are you using PDE feature builder ? Should be easy to do that no
?
Chris
Thursday, July 18, 2002 4:23 PM
To:
eclipse-dev@xxxxxxxxxxx
cc: eclipse-dev@xxxxxxxxxxx
Subject: Re:
[eclipse-dev] 2.0.1 builds
Hi
Peter, Good point. I don't
think this would result in a complete refresh since I believe the underlying
plugin versions change. I thought
that the 2.0.1 release should contain all 2.0.1 features, but after reading your
post I am not so sure. I would
welcome input from the update team or anybody else for that matter on how to
proceed. My intent is that all
features become 2.0.1 but plugin versions are only revised as required.
...Dean...
| manahan@xxxxxxxxxx
Sent by:
eclipse-dev-admin@xxxxxxxxxxx
07/18/2002 03:59 PM Please respond to eclipse-dev
| To:
eclipse-dev@xxxxxxxxxxx cc:
Subject:
Re: [eclipse-dev] 2.0.1
builds |
Hi,
What is the rational for changing the
feature.xml's in advance. When
the plugin owners change the feature.xml
for the first time shouldn't that
be the time the features get upgraded
to 2.0.1? Otherwise 2.0.1 will be a
complete refresh of the features when
perhaps some of the underlying
plugins haven't changed?
The reason I
ask is I am wondering if there was something I missed about
how updates work?
Since we tend to follow eclipses lead in this
area.
Thanks,
-----------------------------------
Peter
Manahan
WebSphere Tools
Build/Install and
Product
Architecture
------------------------------------
manahan@xxxxxxxxxx
"Dean
Roberts"
<Dean_Roberts@oti.
To: eclipse-dev@xxxxxxxxxxx
com>
cc:
Sent by:
Subject:
[eclipse-dev] 2.0.1 builds
eclipse-dev-admin@
eclipse.org
07/18/2002 01:43
PM
Please respond to
eclipse-dev
Hello folks,
I have edited all the
*-feature and primary plugin projects in the R2_0_1
branch in preparation for
starting 2.0.1 builds. In the feature.xml files
I have only changed the
feature versions from 2.0.0 to 2.0.1. I have not
changed any of the
plugin versions. These are all primarily 2.0.0
Your plugin versions
(in the plugin.xml files) should only change to 2.0.1
IF you actually have
plugin changes to contribute to 2.0.1. If you do
change a plugin
version for the 2.0.1 builds you must remember to make the
corresponding
change to the appropriate feature.xml files in the
appropriate
features.
If you do not feel comfortable making these changes, or do not
have commit
rights to make them please send mail to the
platform-releng-dev@xxxxxxxxxxx
and we will make the change for you.
Please let us know of impending
changes well before (24 hours) schedule
2.0.1 builds.
Please do not change your plugin versions in the HEAD (2.1)
stream at this
time.
2.0.1 builds should start next week. I will
send out email when
it
happens.
Thanks
...Dean...
_______________________________________________
eclipse-dev
mailing
list
eclipse-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/eclipse-dev