[vote] release maven-eclipse-plugin

[Graham Leggett <mi...@sharp.fm>]

Hi all,

I would like to propose the release of the maven-eclipse-plugin. This 
will bring the eclipse:make-artifacts goal into a non snapshot release.

Regards,
Graham
--

Re: [vote] release maven-eclipse-plugin

[Carlos Sanchez <ca...@apache.org>]

some time ago I made all poms created by install-files extend a common
"eclipse" parent pom, with all the common info, Fabrizio reverted it.

On 12/11/06, Barrie Treloar <ba...@gmail.com> wrote:
> > > > did you finally remove the usage of a parent pom for install-files?
> > > > that made it easier to add information to all the artifacts than
> > > > regenerate all poms
> [disussion del]
>
> err, this appears to be out of context and I am struggling to work out
> what is being discussed.
> Are there links to the background and what is being solved, or a brief
> summary that could be provided?  Maybe on another thread?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>


-- 
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
                             -- The Princess Bride

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: [vote] release maven-eclipse-plugin

[Barrie Treloar <ba...@gmail.com>]

> > > did you finally remove the usage of a parent pom for install-files?
> > > that made it easier to add information to all the artifacts than
> > > regenerate all poms
[disussion del]

err, this appears to be out of context and I am struggling to work out
what is being discussed.
Are there links to the background and what is being solved, or a brief
summary that could be provided?  Maybe on another thread?

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: [vote] release maven-eclipse-plugin

[Carlos Sanchez <ca...@apache.org>]

On 12/11/06, Fabrizio Giustina <fg...@apache.org> wrote:
> On 12/11/06, Carlos Sanchez <ca...@apache.org> wrote:
> > did you finally remove the usage of a parent pom for install-files?
> > that made it easier to add information to all the artifacts than
> > regenerate all poms
>
> yes, at the moment no parent is used. It's a minor change, I could
> turn it on before the release if needed.
>
> Sincerely I still think it's better to have such info into each pom,
> given that a change in the parent pom should mean a new release for it
> and an update of each child (ok, you say you can "fix" it in a single
> place in the repo, but everybody who previously downloaded also a
> single eclipse artifact before will never see that change, since the
> parent pom will never be downloaded again).

but you'd only need to delete the parent to get a new one, instead of
deleting all children poms

> If you put those informations into each pom and change them only for
> different releases (I don't think we should even plan to "enrich"
> already deployed poms) that will be transparent to users.

sometimes is done making sure it doesn't change previous build
behaviour (relocations, license info, urls, scm info, ...)

>
> Another reason is that the make:artifacts goal was also intended to
> help users in generating/installing artifacts from a local eclipse
> installation to a local maven repository: breaking this by requiring a
> remotely downloaded parent pom doesn't worth this change IMHO.

the parent pom can be in central so they'll get it as soon as they need it

>
> Anyway: at the moment only you and me discussed about this, I would
> like to hear some other thoughts from maven/eclipse users and from
> other devs involved in repository management (jason, brett?). Let's
> keep the release vote anyway, please, and I will turn the writing of
> the <parent> tag on or off based on the result of this discussion...
>
> fabrizio
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>


-- 
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
                             -- The Princess Bride

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: [vote] release maven-eclipse-plugin

[Fabrizio Giustina <fg...@apache.org>]

On 12/11/06, Carlos Sanchez <ca...@apache.org> wrote:
> did you finally remove the usage of a parent pom for install-files?
> that made it easier to add information to all the artifacts than
> regenerate all poms

yes, at the moment no parent is used. It's a minor change, I could
turn it on before the release if needed.

Sincerely I still think it's better to have such info into each pom,
given that a change in the parent pom should mean a new release for it
and an update of each child (ok, you say you can "fix" it in a single
place in the repo, but everybody who previously downloaded also a
single eclipse artifact before will never see that change, since the
parent pom will never be downloaded again).
If you put those informations into each pom and change them only for
different releases (I don't think we should even plan to "enrich"
already deployed poms) that will be transparent to users.

Another reason is that the make:artifacts goal was also intended to
help users in generating/installing artifacts from a local eclipse
installation to a local maven repository: breaking this by requiring a
remotely downloaded parent pom doesn't worth this change IMHO.

Anyway: at the moment only you and me discussed about this, I would
like to hear some other thoughts from maven/eclipse users and from
other devs involved in repository management (jason, brett?). Let's
keep the release vote anyway, please, and I will turn the writing of
the <parent> tag on or off based on the result of this discussion...

fabrizio

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: [vote] release maven-eclipse-plugin

[Carlos Sanchez <ca...@apache.org>]

did you finally remove the usage of a parent pom for install-files?
that made it easier to add information to all the artifacts than
regenerate all poms

On 12/11/06, Fabrizio Giustina <fg...@apache.org> 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
>
>
> On 12/11/06, Graham Leggett <mi...@sharp.fm> wrote:
> > Hi all,
> >
> > I would like to propose the release of the maven-eclipse-plugin. This
> > will bring the eclipse:make-artifacts goal into a non snapshot release.
> >
> > Regards,
> > Graham
> > --
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>


-- 
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
                             -- The Princess Bride

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: [vote] release maven-eclipse-plugin

[Andrew Williams <an...@handyande.co.uk>]

your wish is etc...
plexus-utils 1.4-alpha-1 released :)

Andy

Fabrizio Giustina wrote:
> Thanks Jason,
> could I ask you to take care of the plexus-utils stuff? Should be the
> only non-maven dependency needed for this release, I could take care
> of the rest... the plexus release should be solved independently from
> this vote.
>
> fabrizio
>
>
>
> On 12/11/06, Jason van Zyl <ja...@maven.org> wrote:
>> +1
>>
>> Go for it, I will help you release and move stuff. I question is far
>> from settled as to integration testing but the eclipse plugin release
>> needs to be made. I'll be doing nothing but releases from now until
>> the new year it seems so I can help you with anything related to m2.
>>
>> Jason.
>>
>> On 11 Dec 06, at 5:02 AM 11 Dec 06, Fabrizio Giustina 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
>> >
>> >
>> > On 12/11/06, Graham Leggett <mi...@sharp.fm> wrote:
>> >> Hi all,
>> >>
>> >> I would like to propose the release of the maven-eclipse-plugin. This
>> >> will bring the eclipse:make-artifacts goal into a non snapshot
>> >> release.
>> >>
>> >> Regards,
>> >> Graham
>> >> --
>> >>
>> >>
>> >>
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> > For additional commands, e-mail: dev-help@maven.apache.org
>> >
>> >
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: [vote] release maven-eclipse-plugin

[Fabrizio Giustina <fg...@apache.org>]

Thanks Jason,
could I ask you to take care of the plexus-utils stuff? Should be the
only non-maven dependency needed for this release, I could take care
of the rest... the plexus release should be solved independently from
this vote.

fabrizio



On 12/11/06, Jason van Zyl <ja...@maven.org> wrote:
> +1
>
> Go for it, I will help you release and move stuff. I question is far
> from settled as to integration testing but the eclipse plugin release
> needs to be made. I'll be doing nothing but releases from now until
> the new year it seems so I can help you with anything related to m2.
>
> Jason.
>
> On 11 Dec 06, at 5:02 AM 11 Dec 06, Fabrizio Giustina 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
> >
> >
> > On 12/11/06, Graham Leggett <mi...@sharp.fm> wrote:
> >> Hi all,
> >>
> >> I would like to propose the release of the maven-eclipse-plugin. This
> >> will bring the eclipse:make-artifacts goal into a non snapshot
> >> release.
> >>
> >> Regards,
> >> Graham
> >> --
> >>
> >>
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: [vote] release maven-eclipse-plugin

[Jason van Zyl <ja...@maven.org>]

+1

Go for it, I will help you release and move stuff. I question is far  
from settled as to integration testing but the eclipse plugin release  
needs to be made. I'll be doing nothing but releases from now until  
the new year it seems so I can help you with anything related to m2.

Jason.

On 11 Dec 06, at 5:02 AM 11 Dec 06, Fabrizio Giustina 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
>
>
> On 12/11/06, Graham Leggett <mi...@sharp.fm> wrote:
>> Hi all,
>>
>> I would like to propose the release of the maven-eclipse-plugin. This
>> will bring the eclipse:make-artifacts goal into a non snapshot  
>> release.
>>
>> Regards,
>> Graham
>> --
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: [vote] release maven-eclipse-plugin

[Stephane Nicoll <st...@gmail.com>]

+1

Stéphane

On 12/11/06, Fabrizio Giustina <fg...@apache.org> 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
>
>
> On 12/11/06, Graham Leggett <mi...@sharp.fm> wrote:
> > Hi all,
> >
> > I would like to propose the release of the maven-eclipse-plugin. This
> > will bring the eclipse:make-artifacts goal into a non snapshot release.
> >
> > Regards,
> > Graham
> > --
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: [vote] release maven-eclipse-plugin

[Barrie Treloar <ba...@gmail.com>]

On 12/11/06, Fabrizio Giustina <fg...@apache.org> wrote:
[del]
sandbox and shared stuff...

+1 to get a release with all the other stuff that needs doing too.

I've just spent the last 2 days deploying all these snapshots
internally so I can get a reproducible build...

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: [vote] release maven-eclipse-plugin

[Fabrizio Giustina <fg...@apache.org>]

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


On 12/11/06, Graham Leggett <mi...@sharp.fm> wrote:
> Hi all,
>
> I would like to propose the release of the maven-eclipse-plugin. This
> will bring the eclipse:make-artifacts goal into a non snapshot release.
>
> Regards,
> Graham
> --
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org