You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by ol...@apache.org on 2008/02/22 23:25:08 UTC

svn commit: r630338 - in /maven/plugins/trunk/maven-deploy-plugin: pom.xml src/main/java/org/codehaus/

Author: olamy
Date: Fri Feb 22 14:25:07 2008
New Revision: 630338

URL: http://svn.apache.org/viewvc?rev=630338&view=rev
Log:
upgrade to p-u 1.5
remove duplicated classes from p-u


Removed:
    maven/plugins/trunk/maven-deploy-plugin/src/main/java/org/codehaus/
Modified:
    maven/plugins/trunk/maven-deploy-plugin/pom.xml

Modified: maven/plugins/trunk/maven-deploy-plugin/pom.xml
URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-deploy-plugin/pom.xml?rev=630338&r1=630337&r2=630338&view=diff
==============================================================================
--- maven/plugins/trunk/maven-deploy-plugin/pom.xml (original)
+++ maven/plugins/trunk/maven-deploy-plugin/pom.xml Fri Feb 22 14:25:07 2008
@@ -30,7 +30,7 @@
   <version>2.4-SNAPSHOT</version>
   <inceptionYear>2004</inceptionYear>
   <prerequisites>
-    <maven>2.0</maven>
+    <maven>2.0.6</maven>
   </prerequisites>
   <issueManagement>
     <system>JIRA</system>
@@ -68,6 +68,11 @@
       <groupId>org.apache.maven</groupId>
       <artifactId>maven-artifact</artifactId>
       <version>2.0.6</version>
+    </dependency>
+    <dependency>
+      <groupId>org.codehaus.plexus</groupId>
+      <artifactId>plexus-utils</artifactId>
+      <version>1.5</version>
     </dependency>
     <dependency>
       <groupId>org.apache.maven</groupId>



Re: svn commit: r630338 - in /maven/plugins/trunk/maven-deploy-plugin: pom.xml src/main/java/org/codehaus/

Posted by Dennis Lundberg <de...@apache.org>.
I agree with Jason's comments below. We need to be careful when 
upgrading the Maven prerequisite for plugins.

As far as I have seen, the number one reason for bumping the 
prerequisite to Maven 2.0.6 is so that a version of plexus-utils > 1.1 
can be used. There can be two reasons for this. Either to get around 
bugs in plexus-utils 1.1 or to take advantage of new classes. One of 
these new classes that seems to be used in many places is 
org.codehaus.plexus.xml.XmlStreamReader.

Would it be at all possible to get a special plexus-utils-extra jar, 
which is the latest plexus release minus all the classes that came in 
plexus-utils 1.1? This jar could then be used as a dependency, together 
with plexus-utils-1.1, for plugins or other components that are only 
interested in the added classes - not the bug fixes. That way we can 
stay compatible with older Maven releases.


Jason van Zyl wrote:
> That's probably not a good idea as it's a plugin in the default 
> lifecycle which means now that anyone using anything before 2.0.6 is 
> going to get cut off from any improvements.
> 
> It's really a policy decision but I think it would be a good idea to try 
> and keep the default lifecycle plugins working as far back to 2.0 as we 
> can. We just have to live with the cruft in this case.
> 
> On 22-Feb-08, at 2:25 PM, olamy@apache.org wrote:
> 
>> Author: olamy
>> Date: Fri Feb 22 14:25:07 2008
>> New Revision: 630338
>>
>> URL: http://svn.apache.org/viewvc?rev=630338&view=rev
>> Log:
>> upgrade to p-u 1.5
>> remove duplicated classes from p-u
>>
>>
>> Removed:
>>    maven/plugins/trunk/maven-deploy-plugin/src/main/java/org/codehaus/
>> Modified:
>>    maven/plugins/trunk/maven-deploy-plugin/pom.xml
>>
>> Modified: maven/plugins/trunk/maven-deploy-plugin/pom.xml
>> URL: 
>> http://svn.apache.org/viewvc/maven/plugins/trunk/maven-deploy-plugin/pom.xml?rev=630338&r1=630337&r2=630338&view=diff 
>>
>> ============================================================================== 
>>
>> --- maven/plugins/trunk/maven-deploy-plugin/pom.xml (original)
>> +++ maven/plugins/trunk/maven-deploy-plugin/pom.xml Fri Feb 22 
>> 14:25:07 2008
>> @@ -30,7 +30,7 @@
>>   <version>2.4-SNAPSHOT</version>
>>   <inceptionYear>2004</inceptionYear>
>>   <prerequisites>
>> -    <maven>2.0</maven>
>> +    <maven>2.0.6</maven>
>>   </prerequisites>
>>   <issueManagement>
>>     <system>JIRA</system>
>> @@ -68,6 +68,11 @@
>>       <groupId>org.apache.maven</groupId>
>>       <artifactId>maven-artifact</artifactId>
>>       <version>2.0.6</version>
>> +    </dependency>
>> +    <dependency>
>> +      <groupId>org.codehaus.plexus</groupId>
>> +      <artifactId>plexus-utils</artifactId>
>> +      <version>1.5</version>
>>     </dependency>
>>     <dependency>
>>       <groupId>org.apache.maven</groupId>
>>
>>
> 
> Thanks,
> 
> Jason
> 
> ----------------------------------------------------------
> Jason van Zyl
> Founder,  Apache Maven
> jason at sonatype dot com
> ----------------------------------------------------------
> 
> We know what we are, but know not what we may be.
> 
> -- Shakespeare
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
> 
> 


-- 
Dennis Lundberg

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


RE: svn commit: r630338 - in /maven/plugins/trunk/maven-deploy-plugin: pom.xml src/main/java/org/codehaus/

Posted by Jörg Schaible <Jo...@Elsag-Solutions.com>.
Dennis Lundberg wrote:
> Jörg Schaible wrote:

[snip]

>> Additionally I would really appreciate if the plugin
> documentation would also document the minimal Maven version.
> Normally you simply notice when the plugin breaks your build
> claiming it needs a newer version. This is especially nasty
> if the plugin is normally only used during the release ...
> 
> Yes, that's a nice feature. It's coming in the next release of the
> plugin plugin (the one that auto generates documentation for
> a plugin):
> 
>    http://jira.codehaus.org/browse/MPLUGIN-67

Great news!

- Jörg

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


Re: svn commit: r630338 - in /maven/plugins/trunk/maven-deploy-plugin: pom.xml src/main/java/org/codehaus/

Posted by Dennis Lundberg <de...@apache.org>.
Jörg Schaible wrote:
> Joakim Erdfelt wrote:
>> I still use 2.0.5 daily at the office.
>> I do have 2.0.7 and 2.0.8 installed too, but there's some bad
>> juju (re:
>> bugs) starting in 2.0.6+ WRT corporate repositories, wagon lightweight
>> http, non-projects (archetype, install-file, deploy-file, eclipse,
>> etc...) and also plugin resolution.  So we are stuck on 2.0.5 for the
>> time being. 
>>
>> John Casey has recently closed many of the bugs that we are
>> having with
>> 2.0.6+, but there hasn't been a release of 2.0.x yet with
>> those fixes in it.
>> I've been using a build from the maven-2.0.x branch for a week or so
>> that seems to address many of the issues, but haven't fully
>> fleshed out
>> the use cases yet.
> 
> Same here, but it is getting promising (http://jira.codehaus.org/browse/MNG-3259#action_124708). Although we use fixed plugin versions, we start to miss added functionality. Nothing really critical yet, but it gets annoying. And there are already quite some plugin's that latest versions cannot be used in M205 anymore:
> 
> - maven-changes-plugin
> - maven-dependency-plugin
> - maven-jar-plugin
> - maven-javadoc-plugin
> - maven-war-plugin
> 
> Additionally I would really appreciate if the plugin documentation would also document the minimal Maven version. Normally you simply notice when the plugin breaks your build claiming it needs a newer version. This is especially nasty if the plugin is normally only used during the release ...

Yes, that's a nice feature. It's coming in the next release of the 
plugin plugin (the one that auto generates documentation for a plugin):

   http://jira.codehaus.org/browse/MPLUGIN-67

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


-- 
Dennis Lundberg

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


RE: svn commit: r630338 - in /maven/plugins/trunk/maven-deploy-plugin: pom.xml src/main/java/org/codehaus/

Posted by Jörg Schaible <Jo...@Elsag-Solutions.com>.
Joakim Erdfelt wrote:
> I still use 2.0.5 daily at the office.
> I do have 2.0.7 and 2.0.8 installed too, but there's some bad
> juju (re:
> bugs) starting in 2.0.6+ WRT corporate repositories, wagon lightweight
> http, non-projects (archetype, install-file, deploy-file, eclipse,
> etc...) and also plugin resolution.  So we are stuck on 2.0.5 for the
> time being. 
> 
> John Casey has recently closed many of the bugs that we are
> having with
> 2.0.6+, but there hasn't been a release of 2.0.x yet with
> those fixes in it.
> I've been using a build from the maven-2.0.x branch for a week or so
> that seems to address many of the issues, but haven't fully
> fleshed out
> the use cases yet.

Same here, but it is getting promising (http://jira.codehaus.org/browse/MNG-3259#action_124708). Although we use fixed plugin versions, we start to miss added functionality. Nothing really critical yet, but it gets annoying. And there are already quite some plugin's that latest versions cannot be used in M205 anymore:

- maven-changes-plugin
- maven-dependency-plugin
- maven-jar-plugin
- maven-javadoc-plugin
- maven-war-plugin

Additionally I would really appreciate if the plugin documentation would also document the minimal Maven version. Normally you simply notice when the plugin breaks your build claiming it needs a newer version. This is especially nasty if the plugin is normally only used during the release ...

- Jörg

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


Re: svn commit: r630338 - in /maven/plugins/trunk/maven-deploy-plugin: pom.xml src/main/java/org/codehaus/

Posted by Joakim Erdfelt <jo...@erdfelt.com>.
I still use 2.0.5 daily at the office.
I do have 2.0.7 and 2.0.8 installed too, but there's some bad juju (re: 
bugs) starting in 2.0.6+ WRT corporate repositories, wagon lightweight 
http, non-projects (archetype, install-file, deploy-file, eclipse, 
etc...) and also plugin resolution.  So we are stuck on 2.0.5 for the 
time being.

John Casey has recently closed many of the bugs that we are having with 
2.0.6+, but there hasn't been a release of 2.0.x yet with those fixes in it.
I've been using a build from the maven-2.0.x branch for a week or so 
that seems to address many of the issues, but haven't fully fleshed out 
the use cases yet.

- Joakim

Olivier Lamy wrote:
> Hi,
> Ok I understand the point (I have reverted the commit).
> But 2.0.6 has been released ~ 1 year ago.
> What could be the time to wait to add a core prerequisite ? (Note :
> the jar plugin have this prerequisite and I haven't yet seen user
> complaining).
>
> I don't know how many people use mvn before 2.0.6 currently (except
> the guys who wants to deploy plexus-utils ;-) but they could easily
> lock the plugin version).
> It's difficult to have such statistic.
>
> --
> Olivier
>
> 2008/2/23, Jason van Zyl <ja...@maven.org>:
>   
>> That's probably not a good idea as it's a plugin in the default
>>  lifecycle which means now that anyone using anything before 2.0.6 is
>>  going to get cut off from any improvements.
>>
>>  It's really a policy decision but I think it would be a good idea to
>>  try and keep the default lifecycle plugins working as far back to 2.0
>>  as we can. We just have to live with the cruft in this case.
>>
>>  On 22-Feb-08, at 2:25 PM, olamy@apache.org wrote:
>>
>>  > Author: olamy
>>  > Date: Fri Feb 22 14:25:07 2008
>>  > New Revision: 630338
>>  >
>>  > URL: http://svn.apache.org/viewvc?rev=630338&view=rev
>>  > Log:
>>  > upgrade to p-u 1.5
>>  > remove duplicated classes from p-u
>>  >
>>  >
>>  > Removed:
>>  >    maven/plugins/trunk/maven-deploy-plugin/src/main/java/org/codehaus/
>>  > Modified:
>>  >    maven/plugins/trunk/maven-deploy-plugin/pom.xml
>>  >
>>  > Modified: maven/plugins/trunk/maven-deploy-plugin/pom.xml
>>  > URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-deploy-plugin/pom.xml?rev=630338&r1=630337&r2=630338&view=diff
>>  > =
>>  > =
>>  > =
>>  > =
>>  > =
>>  > =
>>  > =
>>  > =
>>  > ======================================================================
>>  > --- maven/plugins/trunk/maven-deploy-plugin/pom.xml (original)
>>  > +++ maven/plugins/trunk/maven-deploy-plugin/pom.xml Fri Feb 22
>>  > 14:25:07 2008
>>  > @@ -30,7 +30,7 @@
>>  >   <version>2.4-SNAPSHOT</version>
>>  >   <inceptionYear>2004</inceptionYear>
>>  >   <prerequisites>
>>  > -    <maven>2.0</maven>
>>  > +    <maven>2.0.6</maven>
>>  >   </prerequisites>
>>  >   <issueManagement>
>>  >     <system>JIRA</system>
>>  > @@ -68,6 +68,11 @@
>>  >       <groupId>org.apache.maven</groupId>
>>  >       <artifactId>maven-artifact</artifactId>
>>  >       <version>2.0.6</version>
>>  > +    </dependency>
>>  > +    <dependency>
>>  > +      <groupId>org.codehaus.plexus</groupId>
>>  > +      <artifactId>plexus-utils</artifactId>
>>  > +      <version>1.5</version>
>>  >     </dependency>
>>  >     <dependency>
>>  >       <groupId>org.apache.maven</groupId>
>>  >
>>  >
>>
>>  Thanks,
>>
>>  Jason
>>
>>  ----------------------------------------------------------
>>  Jason van Zyl
>>  Founder,  Apache Maven
>>  jason at sonatype dot com
>>  ----------------------------------------------------------
>>
>>  We know what we are, but know not what we may be.
>>
>>  -- Shakespeare
>>
>>
>>
>>
>>  ---------------------------------------------------------------------
>>  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
>
>   


-- 
- Joakim Erdfelt
  joakim@erdfelt.com
  Open Source Software (OSS) Developer


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


Re: svn commit: r630338 - in /maven/plugins/trunk/maven-deploy-plugin: pom.xml src/main/java/org/codehaus/

Posted by Jason van Zyl <ja...@maven.org>.
On 23-Feb-08, at 5:26 AM, Olivier Lamy wrote:

> Hi,
> Ok I understand the point (I have reverted the commit).
> But 2.0.6 has been released ~ 1 year ago.

There are still lots of people using 2.0.5 due to some core+surefire  
problems. But really if people have products building with version of  
Maven like 2.0.4 then there is little reason to change if those  
projects are in maintenance, but they may very well want some fixes in  
the plugins. If we started blocking them out of core plugin fixes I  
think they would get upset. I think we should make an attempt with all  
the plugins but with the default lifecycle plugins it's particularly  
nasty if we made people upgrade to get critical fixes in plugins.

>
> What could be the time to wait to add a core prerequisite ? (Note :
> the jar plugin have this prerequisite and I haven't yet seen user
> complaining).
>

I don't know who did that, but again it's really a policy decision. If  
it's just some code lying around we think makes the code more "tidy"  
then I don't think that's really a good enough reason. I think if  
users understood the implications they would probably complain. If  
there are people who are not locking down the versions of plugins that  
they use and are using an older version of Maven then the plugin  
version selector just ignores that plugin update if there is a  
prerequisite for a newer version.

> I don't know how many people use mvn before 2.0.6 currently (except
> the guys who wants to deploy plexus-utils ;-) but they could easily
> lock the plugin version).
> It's difficult to have such statistic.
>
> --
> Olivier
>
> 2008/2/23, Jason van Zyl <ja...@maven.org>:
>> That's probably not a good idea as it's a plugin in the default
>> lifecycle which means now that anyone using anything before 2.0.6 is
>> going to get cut off from any improvements.
>>
>> It's really a policy decision but I think it would be a good idea to
>> try and keep the default lifecycle plugins working as far back to 2.0
>> as we can. We just have to live with the cruft in this case.
>>
>> On 22-Feb-08, at 2:25 PM, olamy@apache.org wrote:
>>
>>> Author: olamy
>>> Date: Fri Feb 22 14:25:07 2008
>>> New Revision: 630338
>>>
>>> URL: http://svn.apache.org/viewvc?rev=630338&view=rev
>>> Log:
>>> upgrade to p-u 1.5
>>> remove duplicated classes from p-u
>>>
>>>
>>> Removed:
>>>   maven/plugins/trunk/maven-deploy-plugin/src/main/java/org/ 
>>> codehaus/
>>> Modified:
>>>   maven/plugins/trunk/maven-deploy-plugin/pom.xml
>>>
>>> Modified: maven/plugins/trunk/maven-deploy-plugin/pom.xml
>>> URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-deploy-plugin/pom.xml?rev=630338&r1=630337&r2=630338&view=diff
>>> =
>>> =
>>> =
>>> =
>>> =
>>> =
>>> =
>>> =
>>> = 
>>> = 
>>> ====================================================================
>>> --- maven/plugins/trunk/maven-deploy-plugin/pom.xml (original)
>>> +++ maven/plugins/trunk/maven-deploy-plugin/pom.xml Fri Feb 22
>>> 14:25:07 2008
>>> @@ -30,7 +30,7 @@
>>>  <version>2.4-SNAPSHOT</version>
>>>  <inceptionYear>2004</inceptionYear>
>>>  <prerequisites>
>>> -    <maven>2.0</maven>
>>> +    <maven>2.0.6</maven>
>>>  </prerequisites>
>>>  <issueManagement>
>>>    <system>JIRA</system>
>>> @@ -68,6 +68,11 @@
>>>      <groupId>org.apache.maven</groupId>
>>>      <artifactId>maven-artifact</artifactId>
>>>      <version>2.0.6</version>
>>> +    </dependency>
>>> +    <dependency>
>>> +      <groupId>org.codehaus.plexus</groupId>
>>> +      <artifactId>plexus-utils</artifactId>
>>> +      <version>1.5</version>
>>>    </dependency>
>>>    <dependency>
>>>      <groupId>org.apache.maven</groupId>
>>>
>>>
>>
>> Thanks,
>>
>> Jason
>>
>> ----------------------------------------------------------
>> Jason van Zyl
>> Founder,  Apache Maven
>> jason at sonatype dot com
>> ----------------------------------------------------------
>>
>> We know what we are, but know not what we may be.
>>
>> -- Shakespeare
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> 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
>

Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder,  Apache Maven
jason at sonatype dot com
----------------------------------------------------------

You are never dedicated to something you have complete confidence in.
No one is fanatically shouting that the sun is going to rise tomorrow.
They know it is going to rise tomorrow. When people are fanatically
dedicated to political or religious faiths or any other kind of
dogmas or goals, it's always because these dogmas or
goals are in doubt.

-- Robert Pirzig, Zen and the Art of Motorcycle Maintenance 




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


Re: svn commit: r630338 - in /maven/plugins/trunk/maven-deploy-plugin: pom.xml src/main/java/org/codehaus/

Posted by Olivier Lamy <ol...@apache.org>.
Hi,
Ok I understand the point (I have reverted the commit).
But 2.0.6 has been released ~ 1 year ago.
What could be the time to wait to add a core prerequisite ? (Note :
the jar plugin have this prerequisite and I haven't yet seen user
complaining).

I don't know how many people use mvn before 2.0.6 currently (except
the guys who wants to deploy plexus-utils ;-) but they could easily
lock the plugin version).
It's difficult to have such statistic.

--
Olivier

2008/2/23, Jason van Zyl <ja...@maven.org>:
> That's probably not a good idea as it's a plugin in the default
>  lifecycle which means now that anyone using anything before 2.0.6 is
>  going to get cut off from any improvements.
>
>  It's really a policy decision but I think it would be a good idea to
>  try and keep the default lifecycle plugins working as far back to 2.0
>  as we can. We just have to live with the cruft in this case.
>
>  On 22-Feb-08, at 2:25 PM, olamy@apache.org wrote:
>
>  > Author: olamy
>  > Date: Fri Feb 22 14:25:07 2008
>  > New Revision: 630338
>  >
>  > URL: http://svn.apache.org/viewvc?rev=630338&view=rev
>  > Log:
>  > upgrade to p-u 1.5
>  > remove duplicated classes from p-u
>  >
>  >
>  > Removed:
>  >    maven/plugins/trunk/maven-deploy-plugin/src/main/java/org/codehaus/
>  > Modified:
>  >    maven/plugins/trunk/maven-deploy-plugin/pom.xml
>  >
>  > Modified: maven/plugins/trunk/maven-deploy-plugin/pom.xml
>  > URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-deploy-plugin/pom.xml?rev=630338&r1=630337&r2=630338&view=diff
>  > =
>  > =
>  > =
>  > =
>  > =
>  > =
>  > =
>  > =
>  > ======================================================================
>  > --- maven/plugins/trunk/maven-deploy-plugin/pom.xml (original)
>  > +++ maven/plugins/trunk/maven-deploy-plugin/pom.xml Fri Feb 22
>  > 14:25:07 2008
>  > @@ -30,7 +30,7 @@
>  >   <version>2.4-SNAPSHOT</version>
>  >   <inceptionYear>2004</inceptionYear>
>  >   <prerequisites>
>  > -    <maven>2.0</maven>
>  > +    <maven>2.0.6</maven>
>  >   </prerequisites>
>  >   <issueManagement>
>  >     <system>JIRA</system>
>  > @@ -68,6 +68,11 @@
>  >       <groupId>org.apache.maven</groupId>
>  >       <artifactId>maven-artifact</artifactId>
>  >       <version>2.0.6</version>
>  > +    </dependency>
>  > +    <dependency>
>  > +      <groupId>org.codehaus.plexus</groupId>
>  > +      <artifactId>plexus-utils</artifactId>
>  > +      <version>1.5</version>
>  >     </dependency>
>  >     <dependency>
>  >       <groupId>org.apache.maven</groupId>
>  >
>  >
>
>  Thanks,
>
>  Jason
>
>  ----------------------------------------------------------
>  Jason van Zyl
>  Founder,  Apache Maven
>  jason at sonatype dot com
>  ----------------------------------------------------------
>
>  We know what we are, but know not what we may be.
>
>  -- Shakespeare
>
>
>
>
>  ---------------------------------------------------------------------
>  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: svn commit: r630338 - in /maven/plugins/trunk/maven-deploy-plugin: pom.xml src/main/java/org/codehaus/

Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
I agree. We still have lots of users stuck on 2.0.5 due to various
issues in the newer versions. Once we've closed the gap, then supporting
all the way back to 2.0 is not as critical as it is now.

-----Original Message-----
From: Jason van Zyl [mailto:jason@maven.org] 
Sent: Friday, February 22, 2008 8:13 PM
To: dev@maven.apache.org
Subject: Re: svn commit: r630338 - in
/maven/plugins/trunk/maven-deploy-plugin: pom.xml
src/main/java/org/codehaus/

That's probably not a good idea as it's a plugin in the default  
lifecycle which means now that anyone using anything before 2.0.6 is  
going to get cut off from any improvements.

It's really a policy decision but I think it would be a good idea to  
try and keep the default lifecycle plugins working as far back to 2.0  
as we can. We just have to live with the cruft in this case.

On 22-Feb-08, at 2:25 PM, olamy@apache.org wrote:

> Author: olamy
> Date: Fri Feb 22 14:25:07 2008
> New Revision: 630338
>
> URL: http://svn.apache.org/viewvc?rev=630338&view=rev
> Log:
> upgrade to p-u 1.5
> remove duplicated classes from p-u
>
>
> Removed:
>    maven/plugins/trunk/maven-deploy-plugin/src/main/java/org/codehaus/
> Modified:
>    maven/plugins/trunk/maven-deploy-plugin/pom.xml
>
> Modified: maven/plugins/trunk/maven-deploy-plugin/pom.xml
> URL:
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-deploy-plugin/pom
.xml?rev=630338&r1=630337&r2=630338&view=diff
> = 
> = 
> = 
> = 
> = 
> = 
> = 
> = 
> ======================================================================
> --- maven/plugins/trunk/maven-deploy-plugin/pom.xml (original)
> +++ maven/plugins/trunk/maven-deploy-plugin/pom.xml Fri Feb 22  
> 14:25:07 2008
> @@ -30,7 +30,7 @@
>   <version>2.4-SNAPSHOT</version>
>   <inceptionYear>2004</inceptionYear>
>   <prerequisites>
> -    <maven>2.0</maven>
> +    <maven>2.0.6</maven>
>   </prerequisites>
>   <issueManagement>
>     <system>JIRA</system>
> @@ -68,6 +68,11 @@
>       <groupId>org.apache.maven</groupId>
>       <artifactId>maven-artifact</artifactId>
>       <version>2.0.6</version>
> +    </dependency>
> +    <dependency>
> +      <groupId>org.codehaus.plexus</groupId>
> +      <artifactId>plexus-utils</artifactId>
> +      <version>1.5</version>
>     </dependency>
>     <dependency>
>       <groupId>org.apache.maven</groupId>
>
>

Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder,  Apache Maven
jason at sonatype dot com
----------------------------------------------------------

We know what we are, but know not what we may be.

-- Shakespeare 




---------------------------------------------------------------------
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: svn commit: r630338 - in /maven/plugins/trunk/maven-deploy-plugin: pom.xml src/main/java/org/codehaus/

Posted by Jason van Zyl <ja...@maven.org>.
That's probably not a good idea as it's a plugin in the default  
lifecycle which means now that anyone using anything before 2.0.6 is  
going to get cut off from any improvements.

It's really a policy decision but I think it would be a good idea to  
try and keep the default lifecycle plugins working as far back to 2.0  
as we can. We just have to live with the cruft in this case.

On 22-Feb-08, at 2:25 PM, olamy@apache.org wrote:

> Author: olamy
> Date: Fri Feb 22 14:25:07 2008
> New Revision: 630338
>
> URL: http://svn.apache.org/viewvc?rev=630338&view=rev
> Log:
> upgrade to p-u 1.5
> remove duplicated classes from p-u
>
>
> Removed:
>    maven/plugins/trunk/maven-deploy-plugin/src/main/java/org/codehaus/
> Modified:
>    maven/plugins/trunk/maven-deploy-plugin/pom.xml
>
> Modified: maven/plugins/trunk/maven-deploy-plugin/pom.xml
> URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-deploy-plugin/pom.xml?rev=630338&r1=630337&r2=630338&view=diff
> = 
> = 
> = 
> = 
> = 
> = 
> = 
> = 
> ======================================================================
> --- maven/plugins/trunk/maven-deploy-plugin/pom.xml (original)
> +++ maven/plugins/trunk/maven-deploy-plugin/pom.xml Fri Feb 22  
> 14:25:07 2008
> @@ -30,7 +30,7 @@
>   <version>2.4-SNAPSHOT</version>
>   <inceptionYear>2004</inceptionYear>
>   <prerequisites>
> -    <maven>2.0</maven>
> +    <maven>2.0.6</maven>
>   </prerequisites>
>   <issueManagement>
>     <system>JIRA</system>
> @@ -68,6 +68,11 @@
>       <groupId>org.apache.maven</groupId>
>       <artifactId>maven-artifact</artifactId>
>       <version>2.0.6</version>
> +    </dependency>
> +    <dependency>
> +      <groupId>org.codehaus.plexus</groupId>
> +      <artifactId>plexus-utils</artifactId>
> +      <version>1.5</version>
>     </dependency>
>     <dependency>
>       <groupId>org.apache.maven</groupId>
>
>

Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder,  Apache Maven
jason at sonatype dot com
----------------------------------------------------------

We know what we are, but know not what we may be.

-- Shakespeare 




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


Re: svn commit: r630338 - in /maven/plugins/trunk/maven-deploy-plugin: pom.xml src/main/java/org/codehaus/

Posted by Vincent Siveton <vi...@gmail.com>.
Hi,

Why not using the shade plugin instead of removal?

Cheers,

Vincent

2008/2/22, olamy@apache.org <ol...@apache.org>:
> Author: olamy
>  Date: Fri Feb 22 14:25:07 2008
>  New Revision: 630338
>
>  URL: http://svn.apache.org/viewvc?rev=630338&view=rev
>  Log:
>  upgrade to p-u 1.5
>  remove duplicated classes from p-u
>
>
>  Removed:
>     maven/plugins/trunk/maven-deploy-plugin/src/main/java/org/codehaus/
>  Modified:
>     maven/plugins/trunk/maven-deploy-plugin/pom.xml
>
>  Modified: maven/plugins/trunk/maven-deploy-plugin/pom.xml
>  URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-deploy-plugin/pom.xml?rev=630338&r1=630337&r2=630338&view=diff
>  ==============================================================================
>  --- maven/plugins/trunk/maven-deploy-plugin/pom.xml (original)
>  +++ maven/plugins/trunk/maven-deploy-plugin/pom.xml Fri Feb 22 14:25:07 2008
>  @@ -30,7 +30,7 @@
>    <version>2.4-SNAPSHOT</version>
>    <inceptionYear>2004</inceptionYear>
>    <prerequisites>
>  -    <maven>2.0</maven>
>  +    <maven>2.0.6</maven>
>    </prerequisites>
>    <issueManagement>
>      <system>JIRA</system>
>  @@ -68,6 +68,11 @@
>        <groupId>org.apache.maven</groupId>
>        <artifactId>maven-artifact</artifactId>
>        <version>2.0.6</version>
>  +    </dependency>
>  +    <dependency>
>  +      <groupId>org.codehaus.plexus</groupId>
>  +      <artifactId>plexus-utils</artifactId>
>  +      <version>1.5</version>
>      </dependency>
>      <dependency>
>        <groupId>org.apache.maven</groupId>
>
>
>

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