The vote for the release of the eclipse plugin (and related shared
libraries) closed with 3 positive PMC binding votes (me, jason,
stephane) + two positive user votes.
However, due to recent discussions on how votes should be called (on a
stable svn revision, deploying a preview binary and site), plus the
well know issues related to the updated apache guidelines I think it
would be better to repeat the vote, breaking this release into two:
- I will now take care of releasing all the shared dependencies listed
in the previous mails as prerequisite of the eclipse plugin release
(details below)
- after that I will update the maven-eclipse-plugin pom in order to
depend on stable versions, and call again a vote based on a stable svn
revision and a deployed binary/site.
the only non-maven snapshot dependency was plexus-utils, now released.
Thanks to Andrew Williams. This is the remaining tree of our
dependencies
maven-eclipse-plugin -> will wait for another vote on a stable revision
maven-test-tools -> will be moved out of sandbox and released as 1.0-alpha-1
maven-plugin-testing-harness -> will be released as 1.0-beta-2 (I
will see if 1.0-beta-1 could work)
maven-plugin-testing-tools -> will be moved out of sandbox and
released as 1.0-alpha-1
maven-test-tools (already listed above)
maven-invoker --> actually 1.0-SNAPSHOT, dependency will be moved
to already released 2.0.5
maven-repository-builder -> will be moved out of sandbox and
released as 1.0-alpha-1
maven-common-artifact-filters -> will be moved out of sandbox
and released as 1.0-alpha-1
fabrizio
On 12/11/06, Fabrizio Giustina <[EMAIL PROTECTED]> wrote:
I was already planning to start a vote, so a +1 from me since we
already waited too long and added so many changes and enhancements
lately.
Anyway, as usual there are a couple of things that need to be done before:
- license headers needs to be updated and added where missing
- we will have to wait till the remote-resources-plugin is released
(but this should happen soon)
And a bigger issue (the reason why I was delaying this vote):
- there are a few (!) shared components used for testing that need to
be release as well:
org.apache.maven.shared:maven-test-tools:1.0-SNAPSHOT
org.apache.maven.shared:maven-plugin-testing-tools:1.0-SNAPSHOT
org.apache.maven.shared:maven-plugin-testing-harness:1.0-beta-2-SNAPSHOT
plus:
- org.apache.maven.shared:maven-test-tools is still in the sandbox and
it requires a release version of:
org.codehaus.plexus:plexus-utils:1.4-SNAPSHOT
- org.apache.maven.shared:maven-plugin-testing-tools is in the sandbox
too and depends on the following snapshots:
org.apache.maven.shared:maven-repository-builder
org.apache.maven.shared:maven-invoker
and more:
- maven-repository-builder is still in the sandbox too and depends on
a snapshot version of
org.apache.maven.shared:maven-common-artifact-filters
... so, this vote should also mean moving 3 artifacts out of the
sandbox and release other 6 artifacts (not counting the plexus one)?
I think we really need to do this bunch of release (even marking some
components as beta or even alpha), so for me this is an unconditional
+1 for everything: we need a way out from this mess...
fabrizio
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
