You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Andrey Razumovsky <ra...@gmail.com> on 2009/10/11 21:18:02 UTC
Surefire 2.5 release
Hello,
While enchancing our Hudson builds here at Apache Cayenne, we got bitten by
SUREFIRE-551. It is now fixed, but doesn't exist in any released version.
We've found the snapshot in http://repository.apache.org/snapshots/. So our
questions are:
1. Is 2.5-SNAPSHOT stable enough?
2. Can we rely on http://repository.apache.org/snapshots/ repository in our
builds (i.e. aren't there any plans to delete snapshot from that repo)?
3. When official 2.5 will be released?
Thanks,
Andrey
Re: Surefire 2.5 release
Posted by Frederic Camblor <fc...@gmail.com>.
Agreed with Jason ...
Migration to maven 2.0.10 was really impacting for us, since super POM
artefacts was upgraded (especially surefire plugin to 2.4.3 which implied
failures in our tests because system properties are no longer
passed<http://jira.codehaus.org/browse/SUREFIRE-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=193293#action_193293>to
our test cases)
Since surefire is a "key" plugin (plugin which is called in the standard
build lifecycle with version declared in the super pom) any release of these
plugins should be strongly detailed (so, to my mind, release early & often
is not a good practice *for these "key plugins"* : when maven will align its
super pom, it will be a pain to measure quickly enhancements)
Frédéric
On Tue, Oct 13, 2009 at 1:06 AM, Jason van Zyl <ja...@sonatype.com> wrote:
> In this case it is not the mechanics of running the releases. With Surefire
> it's really a matter really taking a look at what's being tested. I know we
> try but incompatibilities have been known to slip in, or configuration
> changes. With unlocked plugin versions this potentially bites people in the
> ass. Yes we should be able to do releases, yes people should lock down
> plugin versions but we know in practice otherwise.
>
> I would check with Dan Fabulich on the dev list what he thinks the state of
> the plugin is before attempting a release.
>
>
> On 2009-10-12, at 3:55 PM, Stephen Connolly wrote:
>
> I'll run a release if I can figure out how ;-)
>>
>> (I'm not sure if it is ready for a release, but I am a release early &
>> often kind of guy... the only other thing I'd consider is merging the
>> failsafe mojos into surefire)
>>
>> Sent from my [rhymes with tryPod] ;-)
>>
>> On 12 Oct 2009, at 23:52, Jason van Zyl <ja...@sonatype.com> wrote:
>>
>> That or just change the version and keep it in a repository not exposed
>>> to everyone else. We can easily make a repository for them in Nexus.
>>>
>>> On 2009-10-11, at 11:24 PM, Dan Tran wrote:
>>>
>>> Jason, I am not sure how Cayenne can cut its release with a private
>>>> copy of surefire plugin. Checkin the private copy surefire plugin
>>>> and change it to cayenne group id?
>>>>
>>>> -D
>>>>
>>>>
>>>>
>>>> On Sun, Oct 11, 2009 at 11:15 PM, Jason van Zyl <ja...@sonatype.com>
>>>> wrote:
>>>>
>>>>>
>>>>> On 2009-10-11, at 10:54 PM, Dan Tran wrote:
>>>>>
>>>>> yes, I did cut a sureplugin release my self at work, however since you
>>>>>> are an apache project, dont think you can release Cayenne with a
>>>>>> private copy of surefire.
>>>>>>
>>>>>>
>>>>> This isn't a problem. I'm not sure when anyone here will get around to
>>>>> releasing Surefire so making an internal release is perfectly fine.
>>>>> Their
>>>>> world can't stop just because ours is moving a little slower.
>>>>>
>>>>> Perhaps you can file a JIRA to release 2.5, i am sure lots of folks
>>>>>> will vote for it, that will get attention.
>>>>>>
>>>>>> -Dan
>>>>>>
>>>>>> On Sun, Oct 11, 2009 at 10:01 PM, Andrey Razumovsky
>>>>>> <ra...@gmail.com> wrote:
>>>>>>
>>>>>>>
>>>>>>> Well, we can if we want to - we have a repository which can be used
>>>>>>> for
>>>>>>> such
>>>>>>> artifacts. So you advice to make a *local* copy of 2.5-SNAPSHOT and
>>>>>>> use
>>>>>>> it
>>>>>>> until official 2.5 is released?
>>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>> 2009/10/12 Dan Tran <da...@gmail.com>
>>>>>>>
>>>>>>> since Apache Cayenne cant just fork its own copy of surefire plugin,
>>>>>>>> i
>>>>>>>> think releasing 2.5 is badly needed.
>>>>>>>>
>>>>>>>> -D
>>>>>>>>
>>>>>>>> On Sun, Oct 11, 2009 at 4:26 PM, Barrie Treloar <baerrach@gmail.com
>>>>>>>> >
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Mon, Oct 12, 2009 at 5:48 AM, Andrey Razumovsky
>>>>>>>>> <ra...@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Hello,
>>>>>>>>>>
>>>>>>>>>> While enchancing our Hudson builds here at Apache Cayenne, we got
>>>>>>>>>> bitten
>>>>>>>>>>
>>>>>>>>>
>>>>>>>> by
>>>>>>>>
>>>>>>>>>
>>>>>>>>>> SUREFIRE-551. It is now fixed, but doesn't exist in any released
>>>>>>>>>>
>>>>>>>>>
>>>>>>>> version.
>>>>>>>>
>>>>>>>>>
>>>>>>>>>> We've found the snapshot in
>>>>>>>>>> http://repository.apache.org/snapshots/.
>>>>>>>>>> So
>>>>>>>>>>
>>>>>>>>>
>>>>>>>> our
>>>>>>>>
>>>>>>>>>
>>>>>>>>>> questions are:
>>>>>>>>>> 1. Is 2.5-SNAPSHOT stable enough?
>>>>>>>>>> 2. Can we rely on http://repository.apache.org/snapshots/repository
>>>>>>>>>> in
>>>>>>>>>>
>>>>>>>>>
>>>>>>>> our
>>>>>>>>
>>>>>>>>>
>>>>>>>>>> builds (i.e. aren't there any plans to delete snapshot from that
>>>>>>>>>> repo)?
>>>>>>>>>> 3. When official 2.5 will be released?
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>> Andrey
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>> For 1) & 2) NEVER rely on snapshots for your builds.
>>>>>>>>>
>>>>>>>>> There are a number of problems with using the snapshot repository.
>>>>>>>>> 1) You can't select which snapshots to use, it is all or nothing.
>>>>>>>>> So
>>>>>>>>> if you aren't following best practice and locking down plugin
>>>>>>>>> versions
>>>>>>>>> then you will automatically start using snapshot versions when you
>>>>>>>>> didnt want to.
>>>>>>>>> 2) Snapshots get rebuilt so it may work one day and fail the next.
>>>>>>>>>
>>>>>>>>> I wrote up the steps I use for this scenario
>>>>>>>>> http://docs.codehaus.org/display/MAVENUSER/Patching+Maven+Plugins
>>>>>>>>>
>>>>>>>>> Essentially you take a copy of the source and build a local version
>>>>>>>>> of
>>>>>>>>> the plugin.
>>>>>>>>> If you use a suitable numbering scheme when the official release
>>>>>>>>> arrives it will replace your patched version.
>>>>>>>>>
>>>>>>>>> I can't answer 3) for you.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>>>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> ---------------------------------------------------------------------
>>>>>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Andrey
>>>>>>>
>>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>>
>>>>>>
>>>>> Thanks,
>>>>>
>>>>> Jason
>>>>>
>>>>> ----------------------------------------------------------
>>>>> Jason van Zyl
>>>>> Founder, Apache Maven
>>>>> http://twitter.com/jvanzyl
>>>>> ----------------------------------------------------------
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>
>>>>>
>>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>
>>>>
>>> Thanks,
>>>
>>> Jason
>>>
>>> ----------------------------------------------------------
>>> Jason van Zyl
>>> Founder, Apache Maven
>>> http://twitter.com/jvanzyl
>>> ----------------------------------------------------------
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder, Apache Maven
> http://twitter.com/jvanzyl
> ----------------------------------------------------------
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: Surefire 2.5 release
Posted by Jason van Zyl <ja...@sonatype.com>.
In this case it is not the mechanics of running the releases. With
Surefire it's really a matter really taking a look at what's being
tested. I know we try but incompatibilities have been known to slip
in, or configuration changes. With unlocked plugin versions this
potentially bites people in the ass. Yes we should be able to do
releases, yes people should lock down plugin versions but we know in
practice otherwise.
I would check with Dan Fabulich on the dev list what he thinks the
state of the plugin is before attempting a release.
On 2009-10-12, at 3:55 PM, Stephen Connolly wrote:
> I'll run a release if I can figure out how ;-)
>
> (I'm not sure if it is ready for a release, but I am a release early
> & often kind of guy... the only other thing I'd consider is merging
> the failsafe mojos into surefire)
>
> Sent from my [rhymes with tryPod] ;-)
>
> On 12 Oct 2009, at 23:52, Jason van Zyl <ja...@sonatype.com> wrote:
>
>> That or just change the version and keep it in a repository not
>> exposed to everyone else. We can easily make a repository for them
>> in Nexus.
>>
>> On 2009-10-11, at 11:24 PM, Dan Tran wrote:
>>
>>> Jason, I am not sure how Cayenne can cut its release with a private
>>> copy of surefire plugin. Checkin the private copy surefire plugin
>>> and change it to cayenne group id?
>>>
>>> -D
>>>
>>>
>>>
>>> On Sun, Oct 11, 2009 at 11:15 PM, Jason van Zyl
>>> <ja...@sonatype.com> wrote:
>>>>
>>>> On 2009-10-11, at 10:54 PM, Dan Tran wrote:
>>>>
>>>>> yes, I did cut a sureplugin release my self at work, however
>>>>> since you
>>>>> are an apache project, dont think you can release Cayenne with a
>>>>> private copy of surefire.
>>>>>
>>>>
>>>> This isn't a problem. I'm not sure when anyone here will get
>>>> around to
>>>> releasing Surefire so making an internal release is perfectly
>>>> fine. Their
>>>> world can't stop just because ours is moving a little slower.
>>>>
>>>>> Perhaps you can file a JIRA to release 2.5, i am sure lots of
>>>>> folks
>>>>> will vote for it, that will get attention.
>>>>>
>>>>> -Dan
>>>>>
>>>>> On Sun, Oct 11, 2009 at 10:01 PM, Andrey Razumovsky
>>>>> <ra...@gmail.com> wrote:
>>>>>>
>>>>>> Well, we can if we want to - we have a repository which can be
>>>>>> used for
>>>>>> such
>>>>>> artifacts. So you advice to make a *local* copy of 2.5-SNAPSHOT
>>>>>> and use
>>>>>> it
>>>>>> until official 2.5 is released?
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> 2009/10/12 Dan Tran <da...@gmail.com>
>>>>>>
>>>>>>> since Apache Cayenne cant just fork its own copy of surefire
>>>>>>> plugin, i
>>>>>>> think releasing 2.5 is badly needed.
>>>>>>>
>>>>>>> -D
>>>>>>>
>>>>>>> On Sun, Oct 11, 2009 at 4:26 PM, Barrie Treloar <baerrach@gmail.com
>>>>>>> >
>>>>>>> wrote:
>>>>>>>>
>>>>>>>> On Mon, Oct 12, 2009 at 5:48 AM, Andrey Razumovsky
>>>>>>>> <ra...@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>> Hello,
>>>>>>>>>
>>>>>>>>> While enchancing our Hudson builds here at Apache Cayenne,
>>>>>>>>> we got
>>>>>>>>> bitten
>>>>>>>
>>>>>>> by
>>>>>>>>>
>>>>>>>>> SUREFIRE-551. It is now fixed, but doesn't exist in any
>>>>>>>>> released
>>>>>>>
>>>>>>> version.
>>>>>>>>>
>>>>>>>>> We've found the snapshot in http://repository.apache.org/snapshots/
>>>>>>>>> .
>>>>>>>>> So
>>>>>>>
>>>>>>> our
>>>>>>>>>
>>>>>>>>> questions are:
>>>>>>>>> 1. Is 2.5-SNAPSHOT stable enough?
>>>>>>>>> 2. Can we rely on http://repository.apache.org/snapshots/
>>>>>>>>> repository
>>>>>>>>> in
>>>>>>>
>>>>>>> our
>>>>>>>>>
>>>>>>>>> builds (i.e. aren't there any plans to delete snapshot from
>>>>>>>>> that
>>>>>>>>> repo)?
>>>>>>>>> 3. When official 2.5 will be released?
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> Andrey
>>>>>>>>>
>>>>>>>>
>>>>>>>> For 1) & 2) NEVER rely on snapshots for your builds.
>>>>>>>>
>>>>>>>> There are a number of problems with using the snapshot
>>>>>>>> repository.
>>>>>>>> 1) You can't select which snapshots to use, it is all or
>>>>>>>> nothing. So
>>>>>>>> if you aren't following best practice and locking down plugin
>>>>>>>> versions
>>>>>>>> then you will automatically start using snapshot versions
>>>>>>>> when you
>>>>>>>> didnt want to.
>>>>>>>> 2) Snapshots get rebuilt so it may work one day and fail the
>>>>>>>> next.
>>>>>>>>
>>>>>>>> I wrote up the steps I use for this scenario
>>>>>>>> http://docs.codehaus.org/display/MAVENUSER/Patching+Maven+Plugins
>>>>>>>>
>>>>>>>> Essentially you take a copy of the source and build a local
>>>>>>>> version of
>>>>>>>> the plugin.
>>>>>>>> If you use a suitable numbering scheme when the official
>>>>>>>> release
>>>>>>>> arrives it will replace your patched version.
>>>>>>>>
>>>>>>>> I can't answer 3) for you.
>>>>>>>>
>>>>>>>> ---------------------------------------------------------------------
>>>>>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Andrey
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>
>>>>
>>>> Thanks,
>>>>
>>>> Jason
>>>>
>>>> ----------------------------------------------------------
>>>> Jason van Zyl
>>>> Founder, Apache Maven
>>>> http://twitter.com/jvanzyl
>>>> ----------------------------------------------------------
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>
>> Thanks,
>>
>> Jason
>>
>> ----------------------------------------------------------
>> Jason van Zyl
>> Founder, Apache Maven
>> http://twitter.com/jvanzyl
>> ----------------------------------------------------------
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Surefire 2.5 release
Posted by Stephen Connolly <st...@gmail.com>.
I'll run a release if I can figure out how ;-)
(I'm not sure if it is ready for a release, but I am a release early &
often kind of guy... the only other thing I'd consider is merging the
failsafe mojos into surefire)
Sent from my [rhymes with tryPod] ;-)
On 12 Oct 2009, at 23:52, Jason van Zyl <ja...@sonatype.com> wrote:
> That or just change the version and keep it in a repository not
> exposed to everyone else. We can easily make a repository for them
> in Nexus.
>
> On 2009-10-11, at 11:24 PM, Dan Tran wrote:
>
>> Jason, I am not sure how Cayenne can cut its release with a private
>> copy of surefire plugin. Checkin the private copy surefire plugin
>> and change it to cayenne group id?
>>
>> -D
>>
>>
>>
>> On Sun, Oct 11, 2009 at 11:15 PM, Jason van Zyl
>> <ja...@sonatype.com> wrote:
>>>
>>> On 2009-10-11, at 10:54 PM, Dan Tran wrote:
>>>
>>>> yes, I did cut a sureplugin release my self at work, however
>>>> since you
>>>> are an apache project, dont think you can release Cayenne with a
>>>> private copy of surefire.
>>>>
>>>
>>> This isn't a problem. I'm not sure when anyone here will get
>>> around to
>>> releasing Surefire so making an internal release is perfectly
>>> fine. Their
>>> world can't stop just because ours is moving a little slower.
>>>
>>>> Perhaps you can file a JIRA to release 2.5, i am sure lots of folks
>>>> will vote for it, that will get attention.
>>>>
>>>> -Dan
>>>>
>>>> On Sun, Oct 11, 2009 at 10:01 PM, Andrey Razumovsky
>>>> <ra...@gmail.com> wrote:
>>>>>
>>>>> Well, we can if we want to - we have a repository which can be
>>>>> used for
>>>>> such
>>>>> artifacts. So you advice to make a *local* copy of 2.5-SNAPSHOT
>>>>> and use
>>>>> it
>>>>> until official 2.5 is released?
>>>>>
>>>>> Thanks,
>>>>>
>>>>> 2009/10/12 Dan Tran <da...@gmail.com>
>>>>>
>>>>>> since Apache Cayenne cant just fork its own copy of surefire
>>>>>> plugin, i
>>>>>> think releasing 2.5 is badly needed.
>>>>>>
>>>>>> -D
>>>>>>
>>>>>> On Sun, Oct 11, 2009 at 4:26 PM, Barrie Treloar <baerrach@gmail.com
>>>>>> >
>>>>>> wrote:
>>>>>>>
>>>>>>> On Mon, Oct 12, 2009 at 5:48 AM, Andrey Razumovsky
>>>>>>> <ra...@gmail.com> wrote:
>>>>>>>>
>>>>>>>> Hello,
>>>>>>>>
>>>>>>>> While enchancing our Hudson builds here at Apache Cayenne, we
>>>>>>>> got
>>>>>>>> bitten
>>>>>>
>>>>>> by
>>>>>>>>
>>>>>>>> SUREFIRE-551. It is now fixed, but doesn't exist in any
>>>>>>>> released
>>>>>>
>>>>>> version.
>>>>>>>>
>>>>>>>> We've found the snapshot in http://repository.apache.org/snapshots/
>>>>>>>> .
>>>>>>>> So
>>>>>>
>>>>>> our
>>>>>>>>
>>>>>>>> questions are:
>>>>>>>> 1. Is 2.5-SNAPSHOT stable enough?
>>>>>>>> 2. Can we rely on http://repository.apache.org/snapshots/
>>>>>>>> repository
>>>>>>>> in
>>>>>>
>>>>>> our
>>>>>>>>
>>>>>>>> builds (i.e. aren't there any plans to delete snapshot from
>>>>>>>> that
>>>>>>>> repo)?
>>>>>>>> 3. When official 2.5 will be released?
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Andrey
>>>>>>>>
>>>>>>>
>>>>>>> For 1) & 2) NEVER rely on snapshots for your builds.
>>>>>>>
>>>>>>> There are a number of problems with using the snapshot
>>>>>>> repository.
>>>>>>> 1) You can't select which snapshots to use, it is all or
>>>>>>> nothing. So
>>>>>>> if you aren't following best practice and locking down plugin
>>>>>>> versions
>>>>>>> then you will automatically start using snapshot versions when
>>>>>>> you
>>>>>>> didnt want to.
>>>>>>> 2) Snapshots get rebuilt so it may work one day and fail the
>>>>>>> next.
>>>>>>>
>>>>>>> I wrote up the steps I use for this scenario
>>>>>>> http://docs.codehaus.org/display/MAVENUSER/Patching+Maven
>>>>>>> +Plugins
>>>>>>>
>>>>>>> Essentially you take a copy of the source and build a local
>>>>>>> version of
>>>>>>> the plugin.
>>>>>>> If you use a suitable numbering scheme when the official release
>>>>>>> arrives it will replace your patched version.
>>>>>>>
>>>>>>> I can't answer 3) for you.
>>>>>>>
>>>>>>> ---
>>>>>>> ---
>>>>>>> ---------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> ---
>>>>>> ---
>>>>>> ---------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Andrey
>>>>>
>>>>
>>>> ---
>>>> ------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>
>>>
>>> Thanks,
>>>
>>> Jason
>>>
>>> ----------------------------------------------------------
>>> Jason van Zyl
>>> Founder, Apache Maven
>>> http://twitter.com/jvanzyl
>>> ----------------------------------------------------------
>>>
>>>
>>> ---
>>> ------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder, Apache Maven
> http://twitter.com/jvanzyl
> ----------------------------------------------------------
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Surefire 2.5 release
Posted by Jason van Zyl <ja...@sonatype.com>.
That or just change the version and keep it in a repository not
exposed to everyone else. We can easily make a repository for them in
Nexus.
On 2009-10-11, at 11:24 PM, Dan Tran wrote:
> Jason, I am not sure how Cayenne can cut its release with a private
> copy of surefire plugin. Checkin the private copy surefire plugin
> and change it to cayenne group id?
>
> -D
>
>
>
> On Sun, Oct 11, 2009 at 11:15 PM, Jason van Zyl <ja...@sonatype.com>
> wrote:
>>
>> On 2009-10-11, at 10:54 PM, Dan Tran wrote:
>>
>>> yes, I did cut a sureplugin release my self at work, however since
>>> you
>>> are an apache project, dont think you can release Cayenne with a
>>> private copy of surefire.
>>>
>>
>> This isn't a problem. I'm not sure when anyone here will get around
>> to
>> releasing Surefire so making an internal release is perfectly fine.
>> Their
>> world can't stop just because ours is moving a little slower.
>>
>>> Perhaps you can file a JIRA to release 2.5, i am sure lots of folks
>>> will vote for it, that will get attention.
>>>
>>> -Dan
>>>
>>> On Sun, Oct 11, 2009 at 10:01 PM, Andrey Razumovsky
>>> <ra...@gmail.com> wrote:
>>>>
>>>> Well, we can if we want to - we have a repository which can be
>>>> used for
>>>> such
>>>> artifacts. So you advice to make a *local* copy of 2.5-SNAPSHOT
>>>> and use
>>>> it
>>>> until official 2.5 is released?
>>>>
>>>> Thanks,
>>>>
>>>> 2009/10/12 Dan Tran <da...@gmail.com>
>>>>
>>>>> since Apache Cayenne cant just fork its own copy of surefire
>>>>> plugin, i
>>>>> think releasing 2.5 is badly needed.
>>>>>
>>>>> -D
>>>>>
>>>>> On Sun, Oct 11, 2009 at 4:26 PM, Barrie Treloar <baerrach@gmail.com
>>>>> >
>>>>> wrote:
>>>>>>
>>>>>> On Mon, Oct 12, 2009 at 5:48 AM, Andrey Razumovsky
>>>>>> <ra...@gmail.com> wrote:
>>>>>>>
>>>>>>> Hello,
>>>>>>>
>>>>>>> While enchancing our Hudson builds here at Apache Cayenne, we
>>>>>>> got
>>>>>>> bitten
>>>>>
>>>>> by
>>>>>>>
>>>>>>> SUREFIRE-551. It is now fixed, but doesn't exist in any released
>>>>>
>>>>> version.
>>>>>>>
>>>>>>> We've found the snapshot in http://repository.apache.org/snapshots/
>>>>>>> .
>>>>>>> So
>>>>>
>>>>> our
>>>>>>>
>>>>>>> questions are:
>>>>>>> 1. Is 2.5-SNAPSHOT stable enough?
>>>>>>> 2. Can we rely on http://repository.apache.org/snapshots/
>>>>>>> repository
>>>>>>> in
>>>>>
>>>>> our
>>>>>>>
>>>>>>> builds (i.e. aren't there any plans to delete snapshot from that
>>>>>>> repo)?
>>>>>>> 3. When official 2.5 will be released?
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Andrey
>>>>>>>
>>>>>>
>>>>>> For 1) & 2) NEVER rely on snapshots for your builds.
>>>>>>
>>>>>> There are a number of problems with using the snapshot
>>>>>> repository.
>>>>>> 1) You can't select which snapshots to use, it is all or
>>>>>> nothing. So
>>>>>> if you aren't following best practice and locking down plugin
>>>>>> versions
>>>>>> then you will automatically start using snapshot versions when
>>>>>> you
>>>>>> didnt want to.
>>>>>> 2) Snapshots get rebuilt so it may work one day and fail the
>>>>>> next.
>>>>>>
>>>>>> I wrote up the steps I use for this scenario
>>>>>> http://docs.codehaus.org/display/MAVENUSER/Patching+Maven+Plugins
>>>>>>
>>>>>> Essentially you take a copy of the source and build a local
>>>>>> version of
>>>>>> the plugin.
>>>>>> If you use a suitable numbering scheme when the official release
>>>>>> arrives it will replace your patched version.
>>>>>>
>>>>>> I can't answer 3) for you.
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>>
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Andrey
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>
>> Thanks,
>>
>> Jason
>>
>> ----------------------------------------------------------
>> Jason van Zyl
>> Founder, Apache Maven
>> http://twitter.com/jvanzyl
>> ----------------------------------------------------------
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Surefire 2.5 release
Posted by Dan Tran <da...@gmail.com>.
Jason, I am not sure how Cayenne can cut its release with a private
copy of surefire plugin. Checkin the private copy surefire plugin
and change it to cayenne group id?
-D
On Sun, Oct 11, 2009 at 11:15 PM, Jason van Zyl <ja...@sonatype.com> wrote:
>
> On 2009-10-11, at 10:54 PM, Dan Tran wrote:
>
>> yes, I did cut a sureplugin release my self at work, however since you
>> are an apache project, dont think you can release Cayenne with a
>> private copy of surefire.
>>
>
> This isn't a problem. I'm not sure when anyone here will get around to
> releasing Surefire so making an internal release is perfectly fine. Their
> world can't stop just because ours is moving a little slower.
>
>> Perhaps you can file a JIRA to release 2.5, i am sure lots of folks
>> will vote for it, that will get attention.
>>
>> -Dan
>>
>> On Sun, Oct 11, 2009 at 10:01 PM, Andrey Razumovsky
>> <ra...@gmail.com> wrote:
>>>
>>> Well, we can if we want to - we have a repository which can be used for
>>> such
>>> artifacts. So you advice to make a *local* copy of 2.5-SNAPSHOT and use
>>> it
>>> until official 2.5 is released?
>>>
>>> Thanks,
>>>
>>> 2009/10/12 Dan Tran <da...@gmail.com>
>>>
>>>> since Apache Cayenne cant just fork its own copy of surefire plugin, i
>>>> think releasing 2.5 is badly needed.
>>>>
>>>> -D
>>>>
>>>> On Sun, Oct 11, 2009 at 4:26 PM, Barrie Treloar <ba...@gmail.com>
>>>> wrote:
>>>>>
>>>>> On Mon, Oct 12, 2009 at 5:48 AM, Andrey Razumovsky
>>>>> <ra...@gmail.com> wrote:
>>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> While enchancing our Hudson builds here at Apache Cayenne, we got
>>>>>> bitten
>>>>
>>>> by
>>>>>>
>>>>>> SUREFIRE-551. It is now fixed, but doesn't exist in any released
>>>>
>>>> version.
>>>>>>
>>>>>> We've found the snapshot in http://repository.apache.org/snapshots/.
>>>>>> So
>>>>
>>>> our
>>>>>>
>>>>>> questions are:
>>>>>> 1. Is 2.5-SNAPSHOT stable enough?
>>>>>> 2. Can we rely on http://repository.apache.org/snapshots/ repository
>>>>>> in
>>>>
>>>> our
>>>>>>
>>>>>> builds (i.e. aren't there any plans to delete snapshot from that
>>>>>> repo)?
>>>>>> 3. When official 2.5 will be released?
>>>>>>
>>>>>> Thanks,
>>>>>> Andrey
>>>>>>
>>>>>
>>>>> For 1) & 2) NEVER rely on snapshots for your builds.
>>>>>
>>>>> There are a number of problems with using the snapshot repository.
>>>>> 1) You can't select which snapshots to use, it is all or nothing. So
>>>>> if you aren't following best practice and locking down plugin versions
>>>>> then you will automatically start using snapshot versions when you
>>>>> didnt want to.
>>>>> 2) Snapshots get rebuilt so it may work one day and fail the next.
>>>>>
>>>>> I wrote up the steps I use for this scenario
>>>>> http://docs.codehaus.org/display/MAVENUSER/Patching+Maven+Plugins
>>>>>
>>>>> Essentially you take a copy of the source and build a local version of
>>>>> the plugin.
>>>>> If you use a suitable numbering scheme when the official release
>>>>> arrives it will replace your patched version.
>>>>>
>>>>> I can't answer 3) for you.
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>
>>>>
>>>
>>>
>>> --
>>> Andrey
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder, Apache Maven
> http://twitter.com/jvanzyl
> ----------------------------------------------------------
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Surefire 2.5 release
Posted by Jason van Zyl <ja...@sonatype.com>.
On 2009-10-11, at 10:54 PM, Dan Tran wrote:
> yes, I did cut a sureplugin release my self at work, however since you
> are an apache project, dont think you can release Cayenne with a
> private copy of surefire.
>
This isn't a problem. I'm not sure when anyone here will get around to
releasing Surefire so making an internal release is perfectly fine.
Their world can't stop just because ours is moving a little slower.
> Perhaps you can file a JIRA to release 2.5, i am sure lots of folks
> will vote for it, that will get attention.
>
> -Dan
>
> On Sun, Oct 11, 2009 at 10:01 PM, Andrey Razumovsky
> <ra...@gmail.com> wrote:
>> Well, we can if we want to - we have a repository which can be used
>> for such
>> artifacts. So you advice to make a *local* copy of 2.5-SNAPSHOT and
>> use it
>> until official 2.5 is released?
>>
>> Thanks,
>>
>> 2009/10/12 Dan Tran <da...@gmail.com>
>>
>>> since Apache Cayenne cant just fork its own copy of surefire
>>> plugin, i
>>> think releasing 2.5 is badly needed.
>>>
>>> -D
>>>
>>> On Sun, Oct 11, 2009 at 4:26 PM, Barrie Treloar <ba...@gmail.com>
>>> wrote:
>>>> On Mon, Oct 12, 2009 at 5:48 AM, Andrey Razumovsky
>>>> <ra...@gmail.com> wrote:
>>>>> Hello,
>>>>>
>>>>> While enchancing our Hudson builds here at Apache Cayenne, we
>>>>> got bitten
>>> by
>>>>> SUREFIRE-551. It is now fixed, but doesn't exist in any released
>>> version.
>>>>> We've found the snapshot in http://repository.apache.org/snapshots/
>>>>> . So
>>> our
>>>>> questions are:
>>>>> 1. Is 2.5-SNAPSHOT stable enough?
>>>>> 2. Can we rely on http://repository.apache.org/snapshots/
>>>>> repository in
>>> our
>>>>> builds (i.e. aren't there any plans to delete snapshot from that
>>>>> repo)?
>>>>> 3. When official 2.5 will be released?
>>>>>
>>>>> Thanks,
>>>>> Andrey
>>>>>
>>>>
>>>> For 1) & 2) NEVER rely on snapshots for your builds.
>>>>
>>>> There are a number of problems with using the snapshot repository.
>>>> 1) You can't select which snapshots to use, it is all or
>>>> nothing. So
>>>> if you aren't following best practice and locking down plugin
>>>> versions
>>>> then you will automatically start using snapshot versions when you
>>>> didnt want to.
>>>> 2) Snapshots get rebuilt so it may work one day and fail the next.
>>>>
>>>> I wrote up the steps I use for this scenario
>>>> http://docs.codehaus.org/display/MAVENUSER/Patching+Maven+Plugins
>>>>
>>>> Essentially you take a copy of the source and build a local
>>>> version of
>>>> the plugin.
>>>> If you use a suitable numbering scheme when the official release
>>>> arrives it will replace your patched version.
>>>>
>>>> I can't answer 3) for you.
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>
>>
>> --
>> Andrey
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Surefire 2.5 release
Posted by Andrey Razumovsky <ra...@gmail.com>.
Oh, and the link. You can vote here:
http://jira.codehaus.org/browse/SUREFIRE-578
2009/10/12 Andrey Razumovsky <ra...@gmail.com>
> Created a JIRA.
> Actually, since Surefire has only "test" dependency, so it will not be
> anyhow included in a release, so no problems should occur
>
>
> 2009/10/12 Dan Tran <da...@gmail.com>
>
>> yes, I did cut a sureplugin release my self at work, however since you
>> are an apache project, dont think you can release Cayenne with a
>> private copy of surefire.
>>
>> Perhaps you can file a JIRA to release 2.5, i am sure lots of folks
>> will vote for it, that will get attention.
>>
>> -Dan
>>
>> On Sun, Oct 11, 2009 at 10:01 PM, Andrey Razumovsky
>> <ra...@gmail.com> wrote:
>> > Well, we can if we want to - we have a repository which can be used for
>> such
>> > artifacts. So you advice to make a *local* copy of 2.5-SNAPSHOT and use
>> it
>> > until official 2.5 is released?
>> >
>> > Thanks,
>> >
>> > 2009/10/12 Dan Tran <da...@gmail.com>
>> >
>> >> since Apache Cayenne cant just fork its own copy of surefire plugin, i
>> >> think releasing 2.5 is badly needed.
>> >>
>> >> -D
>> >>
>> >> On Sun, Oct 11, 2009 at 4:26 PM, Barrie Treloar <ba...@gmail.com>
>> >> wrote:
>> >> > On Mon, Oct 12, 2009 at 5:48 AM, Andrey Razumovsky
>> >> > <ra...@gmail.com> wrote:
>> >> >> Hello,
>> >> >>
>> >> >> While enchancing our Hudson builds here at Apache Cayenne, we got
>> bitten
>> >> by
>> >> >> SUREFIRE-551. It is now fixed, but doesn't exist in any released
>> >> version.
>> >> >> We've found the snapshot in http://repository.apache.org/snapshots/.
>> So
>> >> our
>> >> >> questions are:
>> >> >> 1. Is 2.5-SNAPSHOT stable enough?
>> >> >> 2. Can we rely on http://repository.apache.org/snapshots/repository in
>> >> our
>> >> >> builds (i.e. aren't there any plans to delete snapshot from that
>> repo)?
>> >> >> 3. When official 2.5 will be released?
>> >> >>
>> >> >> Thanks,
>> >> >> Andrey
>> >> >>
>> >> >
>> >> > For 1) & 2) NEVER rely on snapshots for your builds.
>> >> >
>> >> > There are a number of problems with using the snapshot repository.
>> >> > 1) You can't select which snapshots to use, it is all or nothing. So
>> >> > if you aren't following best practice and locking down plugin
>> versions
>> >> > then you will automatically start using snapshot versions when you
>> >> > didnt want to.
>> >> > 2) Snapshots get rebuilt so it may work one day and fail the next.
>> >> >
>> >> > I wrote up the steps I use for this scenario
>> >> > http://docs.codehaus.org/display/MAVENUSER/Patching+Maven+Plugins
>> >> >
>> >> > Essentially you take a copy of the source and build a local version
>> of
>> >> > the plugin.
>> >> > If you use a suitable numbering scheme when the official release
>> >> > arrives it will replace your patched version.
>> >> >
>> >> > I can't answer 3) for you.
>> >> >
>> >> > ---------------------------------------------------------------------
>> >> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> >> > For additional commands, e-mail: users-help@maven.apache.org
>> >> >
>> >> >
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> >> For additional commands, e-mail: users-help@maven.apache.org
>> >>
>> >>
>> >
>> >
>> > --
>> > Andrey
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
>
> --
> Andrey
>
--
Andrey
Re: Surefire 2.5 release
Posted by Andrey Razumovsky <ra...@gmail.com>.
Created a JIRA.
Actually, since Surefire has only "test" dependency, so it will not be
anyhow included in a release, so no problems should occur
2009/10/12 Dan Tran <da...@gmail.com>
> yes, I did cut a sureplugin release my self at work, however since you
> are an apache project, dont think you can release Cayenne with a
> private copy of surefire.
>
> Perhaps you can file a JIRA to release 2.5, i am sure lots of folks
> will vote for it, that will get attention.
>
> -Dan
>
> On Sun, Oct 11, 2009 at 10:01 PM, Andrey Razumovsky
> <ra...@gmail.com> wrote:
> > Well, we can if we want to - we have a repository which can be used for
> such
> > artifacts. So you advice to make a *local* copy of 2.5-SNAPSHOT and use
> it
> > until official 2.5 is released?
> >
> > Thanks,
> >
> > 2009/10/12 Dan Tran <da...@gmail.com>
> >
> >> since Apache Cayenne cant just fork its own copy of surefire plugin, i
> >> think releasing 2.5 is badly needed.
> >>
> >> -D
> >>
> >> On Sun, Oct 11, 2009 at 4:26 PM, Barrie Treloar <ba...@gmail.com>
> >> wrote:
> >> > On Mon, Oct 12, 2009 at 5:48 AM, Andrey Razumovsky
> >> > <ra...@gmail.com> wrote:
> >> >> Hello,
> >> >>
> >> >> While enchancing our Hudson builds here at Apache Cayenne, we got
> bitten
> >> by
> >> >> SUREFIRE-551. It is now fixed, but doesn't exist in any released
> >> version.
> >> >> We've found the snapshot in http://repository.apache.org/snapshots/.
> So
> >> our
> >> >> questions are:
> >> >> 1. Is 2.5-SNAPSHOT stable enough?
> >> >> 2. Can we rely on http://repository.apache.org/snapshots/ repository
> in
> >> our
> >> >> builds (i.e. aren't there any plans to delete snapshot from that
> repo)?
> >> >> 3. When official 2.5 will be released?
> >> >>
> >> >> Thanks,
> >> >> Andrey
> >> >>
> >> >
> >> > For 1) & 2) NEVER rely on snapshots for your builds.
> >> >
> >> > There are a number of problems with using the snapshot repository.
> >> > 1) You can't select which snapshots to use, it is all or nothing. So
> >> > if you aren't following best practice and locking down plugin versions
> >> > then you will automatically start using snapshot versions when you
> >> > didnt want to.
> >> > 2) Snapshots get rebuilt so it may work one day and fail the next.
> >> >
> >> > I wrote up the steps I use for this scenario
> >> > http://docs.codehaus.org/display/MAVENUSER/Patching+Maven+Plugins
> >> >
> >> > Essentially you take a copy of the source and build a local version of
> >> > the plugin.
> >> > If you use a suitable numbering scheme when the official release
> >> > arrives it will replace your patched version.
> >> >
> >> > I can't answer 3) for you.
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >> > For additional commands, e-mail: users-help@maven.apache.org
> >> >
> >> >
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: users-help@maven.apache.org
> >>
> >>
> >
> >
> > --
> > Andrey
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
Andrey
Re: Surefire 2.5 release
Posted by Dan Tran <da...@gmail.com>.
yes, I did cut a sureplugin release my self at work, however since you
are an apache project, dont think you can release Cayenne with a
private copy of surefire.
Perhaps you can file a JIRA to release 2.5, i am sure lots of folks
will vote for it, that will get attention.
-Dan
On Sun, Oct 11, 2009 at 10:01 PM, Andrey Razumovsky
<ra...@gmail.com> wrote:
> Well, we can if we want to - we have a repository which can be used for such
> artifacts. So you advice to make a *local* copy of 2.5-SNAPSHOT and use it
> until official 2.5 is released?
>
> Thanks,
>
> 2009/10/12 Dan Tran <da...@gmail.com>
>
>> since Apache Cayenne cant just fork its own copy of surefire plugin, i
>> think releasing 2.5 is badly needed.
>>
>> -D
>>
>> On Sun, Oct 11, 2009 at 4:26 PM, Barrie Treloar <ba...@gmail.com>
>> wrote:
>> > On Mon, Oct 12, 2009 at 5:48 AM, Andrey Razumovsky
>> > <ra...@gmail.com> wrote:
>> >> Hello,
>> >>
>> >> While enchancing our Hudson builds here at Apache Cayenne, we got bitten
>> by
>> >> SUREFIRE-551. It is now fixed, but doesn't exist in any released
>> version.
>> >> We've found the snapshot in http://repository.apache.org/snapshots/. So
>> our
>> >> questions are:
>> >> 1. Is 2.5-SNAPSHOT stable enough?
>> >> 2. Can we rely on http://repository.apache.org/snapshots/ repository in
>> our
>> >> builds (i.e. aren't there any plans to delete snapshot from that repo)?
>> >> 3. When official 2.5 will be released?
>> >>
>> >> Thanks,
>> >> Andrey
>> >>
>> >
>> > For 1) & 2) NEVER rely on snapshots for your builds.
>> >
>> > There are a number of problems with using the snapshot repository.
>> > 1) You can't select which snapshots to use, it is all or nothing. So
>> > if you aren't following best practice and locking down plugin versions
>> > then you will automatically start using snapshot versions when you
>> > didnt want to.
>> > 2) Snapshots get rebuilt so it may work one day and fail the next.
>> >
>> > I wrote up the steps I use for this scenario
>> > http://docs.codehaus.org/display/MAVENUSER/Patching+Maven+Plugins
>> >
>> > Essentially you take a copy of the source and build a local version of
>> > the plugin.
>> > If you use a suitable numbering scheme when the official release
>> > arrives it will replace your patched version.
>> >
>> > I can't answer 3) for you.
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> > For additional commands, e-mail: users-help@maven.apache.org
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
>
> --
> Andrey
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Surefire 2.5 release
Posted by Andrey Razumovsky <ra...@gmail.com>.
Well, we can if we want to - we have a repository which can be used for such
artifacts. So you advice to make a *local* copy of 2.5-SNAPSHOT and use it
until official 2.5 is released?
Thanks,
2009/10/12 Dan Tran <da...@gmail.com>
> since Apache Cayenne cant just fork its own copy of surefire plugin, i
> think releasing 2.5 is badly needed.
>
> -D
>
> On Sun, Oct 11, 2009 at 4:26 PM, Barrie Treloar <ba...@gmail.com>
> wrote:
> > On Mon, Oct 12, 2009 at 5:48 AM, Andrey Razumovsky
> > <ra...@gmail.com> wrote:
> >> Hello,
> >>
> >> While enchancing our Hudson builds here at Apache Cayenne, we got bitten
> by
> >> SUREFIRE-551. It is now fixed, but doesn't exist in any released
> version.
> >> We've found the snapshot in http://repository.apache.org/snapshots/. So
> our
> >> questions are:
> >> 1. Is 2.5-SNAPSHOT stable enough?
> >> 2. Can we rely on http://repository.apache.org/snapshots/ repository in
> our
> >> builds (i.e. aren't there any plans to delete snapshot from that repo)?
> >> 3. When official 2.5 will be released?
> >>
> >> Thanks,
> >> Andrey
> >>
> >
> > For 1) & 2) NEVER rely on snapshots for your builds.
> >
> > There are a number of problems with using the snapshot repository.
> > 1) You can't select which snapshots to use, it is all or nothing. So
> > if you aren't following best practice and locking down plugin versions
> > then you will automatically start using snapshot versions when you
> > didnt want to.
> > 2) Snapshots get rebuilt so it may work one day and fail the next.
> >
> > I wrote up the steps I use for this scenario
> > http://docs.codehaus.org/display/MAVENUSER/Patching+Maven+Plugins
> >
> > Essentially you take a copy of the source and build a local version of
> > the plugin.
> > If you use a suitable numbering scheme when the official release
> > arrives it will replace your patched version.
> >
> > I can't answer 3) for you.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
Andrey
Re: Surefire 2.5 release
Posted by Dan Tran <da...@gmail.com>.
since Apache Cayenne cant just fork its own copy of surefire plugin, i
think releasing 2.5 is badly needed.
-D
On Sun, Oct 11, 2009 at 4:26 PM, Barrie Treloar <ba...@gmail.com> wrote:
> On Mon, Oct 12, 2009 at 5:48 AM, Andrey Razumovsky
> <ra...@gmail.com> wrote:
>> Hello,
>>
>> While enchancing our Hudson builds here at Apache Cayenne, we got bitten by
>> SUREFIRE-551. It is now fixed, but doesn't exist in any released version.
>> We've found the snapshot in http://repository.apache.org/snapshots/. So our
>> questions are:
>> 1. Is 2.5-SNAPSHOT stable enough?
>> 2. Can we rely on http://repository.apache.org/snapshots/ repository in our
>> builds (i.e. aren't there any plans to delete snapshot from that repo)?
>> 3. When official 2.5 will be released?
>>
>> Thanks,
>> Andrey
>>
>
> For 1) & 2) NEVER rely on snapshots for your builds.
>
> There are a number of problems with using the snapshot repository.
> 1) You can't select which snapshots to use, it is all or nothing. So
> if you aren't following best practice and locking down plugin versions
> then you will automatically start using snapshot versions when you
> didnt want to.
> 2) Snapshots get rebuilt so it may work one day and fail the next.
>
> I wrote up the steps I use for this scenario
> http://docs.codehaus.org/display/MAVENUSER/Patching+Maven+Plugins
>
> Essentially you take a copy of the source and build a local version of
> the plugin.
> If you use a suitable numbering scheme when the official release
> arrives it will replace your patched version.
>
> I can't answer 3) for you.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Surefire 2.5 release
Posted by Barrie Treloar <ba...@gmail.com>.
On Mon, Oct 12, 2009 at 5:48 AM, Andrey Razumovsky
<ra...@gmail.com> wrote:
> Hello,
>
> While enchancing our Hudson builds here at Apache Cayenne, we got bitten by
> SUREFIRE-551. It is now fixed, but doesn't exist in any released version.
> We've found the snapshot in http://repository.apache.org/snapshots/. So our
> questions are:
> 1. Is 2.5-SNAPSHOT stable enough?
> 2. Can we rely on http://repository.apache.org/snapshots/ repository in our
> builds (i.e. aren't there any plans to delete snapshot from that repo)?
> 3. When official 2.5 will be released?
>
> Thanks,
> Andrey
>
For 1) & 2) NEVER rely on snapshots for your builds.
There are a number of problems with using the snapshot repository.
1) You can't select which snapshots to use, it is all or nothing. So
if you aren't following best practice and locking down plugin versions
then you will automatically start using snapshot versions when you
didnt want to.
2) Snapshots get rebuilt so it may work one day and fail the next.
I wrote up the steps I use for this scenario
http://docs.codehaus.org/display/MAVENUSER/Patching+Maven+Plugins
Essentially you take a copy of the source and build a local version of
the plugin.
If you use a suitable numbering scheme when the official release
arrives it will replace your patched version.
I can't answer 3) for you.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org