You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by hb...@apache.org on 2010/05/05 23:42:51 UTC
svn commit: r941507 -
/maven/shared/branches/maven-reporting-impl-2.0.4.x/pom.xml
Author: hboutemy
Date: Wed May 5 21:42:51 2010
New Revision: 941507
URL: http://svn.apache.org/viewvc?rev=941507&view=rev
Log:
o next version will be 2.0.5
o updated parent pom
Modified:
maven/shared/branches/maven-reporting-impl-2.0.4.x/pom.xml
Modified: maven/shared/branches/maven-reporting-impl-2.0.4.x/pom.xml
URL: http://svn.apache.org/viewvc/maven/shared/branches/maven-reporting-impl-2.0.4.x/pom.xml?rev=941507&r1=941506&r2=941507&view=diff
==============================================================================
--- maven/shared/branches/maven-reporting-impl-2.0.4.x/pom.xml (original)
+++ maven/shared/branches/maven-reporting-impl-2.0.4.x/pom.xml Wed May 5 21:42:51 2010
@@ -23,12 +23,12 @@
<parent>
<groupId>org.apache.maven.shared</groupId>
<artifactId>maven-shared-components</artifactId>
- <version>14</version>
+ <version>15</version>
</parent>
<groupId>org.apache.maven.reporting</groupId>
<artifactId>maven-reporting-impl</artifactId>
- <version>2.0.4.4-SNAPSHOT</version>
+ <version>2.0.5-SNAPSHOT</version>
<name>Maven Reporting Implementation</name>
<description>Abstract classes to manage report generation.</description>
Re: Pending plugin releases
Posted by Kristian Rosenvold <kr...@gmail.com>.
I meant the Y in x.y.z, not the x;)
Den 10. mai 2010 kl. 10.32 skrev Stephane Nicoll <stephane.nicoll@gmail.com
>:
> Hi,
>
> What does full point upgrade means exactly?
>
> S.
>
> ---
> [image: Linkedin] <http://www.linkedin.com/in/snicoll>[image:
> Twitter]<http://twitter.com/snicoll>
>
>
> On Mon, May 10, 2010 at 9:01 AM, Kristian Rosenvold <
> kristian.rosenvold@gmail.com> wrote:
>
>> I'm going to be releasing .1 upgrades to add @threadSafe to the
>> following
>> mojos this week/next week:
>>
>> maven-compiler-plugin
>> maven-install-plugin
>> maven-source-plugin
>> maven-resources-plugin
>> maven-surefire-plugin
>> maven-jar-plugin
>> maven-war-plugin
>> maven-ear-plugin (will be full point upgrade)
>> maven-antrun-plugin
>> maven-enforcer-plugin
>> (org.codehaus.plexus:plexus-component-metadata)
>>
>> If anyone else wants to fix bugs or similar, now's the time to do
>> it ;) I
>> will normally just go for bugfix release possible, and I will be
>> committing the acutal fix to the plugins over the next few days.
>> Let me
>> know if you want to do a different kind of release.
>>
>> The changes I'm doing to these are:
>> * maven-plugins to version 18
>> * @threadSafe annotation to the mojo(s), including code review of
>> "auxilarry" mojos in the plugin
>> Library upgrades:
>> * plexus-utils to 2.0.5 (and maven dependency to >=2.0.6 for the
>> sake of
>> clarity)
>> * plexus-io to 1.0
>> * plexus-archiver to 1.0
>> * maven-archiver to 2.4.1 (pending release, blocking release of the
>> xAR
>> plugins ATM)
>>
>> This week it's going to be compiler/install. Most of the others have
>> archiver dependencies and will be done next week.
>>
>> Kristian
>>
>>
>> ---------------------------------------------------------------------
>> 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: Pending plugin releases
Posted by Stephane Nicoll <st...@gmail.com>.
Hi,
What does full point upgrade means exactly?
S.
---
[image: Linkedin] <http://www.linkedin.com/in/snicoll>[image:
Twitter]<http://twitter.com/snicoll>
On Mon, May 10, 2010 at 9:01 AM, Kristian Rosenvold <
kristian.rosenvold@gmail.com> wrote:
> I'm going to be releasing .1 upgrades to add @threadSafe to the following
> mojos this week/next week:
>
> maven-compiler-plugin
> maven-install-plugin
> maven-source-plugin
> maven-resources-plugin
> maven-surefire-plugin
> maven-jar-plugin
> maven-war-plugin
> maven-ear-plugin (will be full point upgrade)
> maven-antrun-plugin
> maven-enforcer-plugin
> (org.codehaus.plexus:plexus-component-metadata)
>
> If anyone else wants to fix bugs or similar, now's the time to do it ;) I
> will normally just go for bugfix release possible, and I will be
> committing the acutal fix to the plugins over the next few days. Let me
> know if you want to do a different kind of release.
>
> The changes I'm doing to these are:
> * maven-plugins to version 18
> * @threadSafe annotation to the mojo(s), including code review of
> "auxilarry" mojos in the plugin
> Library upgrades:
> * plexus-utils to 2.0.5 (and maven dependency to >=2.0.6 for the sake of
> clarity)
> * plexus-io to 1.0
> * plexus-archiver to 1.0
> * maven-archiver to 2.4.1 (pending release, blocking release of the xAR
> plugins ATM)
>
> This week it's going to be compiler/install. Most of the others have
> archiver dependencies and will be done next week.
>
> Kristian
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Pending plugin releases
Posted by Kristian Rosenvold <kr...@gmail.com>.
I'm going to be releasing .1 upgrades to add @threadSafe to the
following mojos this week/next week:
maven-compiler-plugin
maven-install-plugin
maven-source-plugin
maven-resources-plugin
maven-surefire-plugin
maven-jar-plugin
maven-war-plugin
maven-ear-plugin (will be full point upgrade)
maven-antrun-plugin
maven-enforcer-plugin
(org.codehaus.plexus:plexus-component-metadata)
If anyone else wants to fix bugs or similar, now's the time to do it ;)
I will normally just go for bugfix release possible, and I will be
committing the acutal fix to the plugins over the next few days. Let me
know if you want to do a different kind of release.
The changes I'm doing to these are:
* maven-plugins to version 18
* @threadSafe annotation to the mojo(s), including code review of
"auxilarry" mojos in the plugin
Library upgrades:
* plexus-utils to 2.0.5 (and maven dependency to >=2.0.6 for the sake of
clarity)
* plexus-io to 1.0
* plexus-archiver to 1.0
* maven-archiver to 2.4.1 (pending release, blocking release of the xAR
plugins ATM)
This week it's going to be compiler/install. Most of the others have
archiver dependencies and will be done next week.
Kristian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: svn commit: r941507 - /maven/shared/branches/maven-reporting-impl-2.0.4.x/pom.xml
Posted by Hervé BOUTEMY <he...@free.fr>.
Le dimanche 09 mai 2010, Dennis Lundberg a écrit :
> > I documented doxia-sink-api and maven-reporting-impl coupling issues and
> > changes.
>
> Thanks! That's great and certainly make things easier to understand.
It was hard to understand: now it's time to explain and have everybody
understand too :)
>
> > There is no confusion any more. The summary is as simple as:
> > - Maven 2.0.x, Doxia 1.0.x, maven-reporting-impl 2.0.x, maven-site-plugin
> > 2.0.x
> > - Maven 2.1.x, Doxia 1.1.x, maven-reporting-impl 2.1.x, maven-site-plugin
> > 2.1.x
> > - Maven 3.x, maven-site-plugin 3.x
>
> So far I'm with you, but what about maven-reporting-api?
>
> If the api (version 3.0) was decoupled from the core in version 3.0 (of
> the core), can Maven 2.x use version 3.0 of the api?
>
> Isn't version 2.0.4 of the api included in the core for the entire
> current Maven 2.x line? If so doesn't that prevent it from using another
> version of the api?
In fact, the API had very few changes: the API consists in interfaces that
didn't change over time (only javadoc addition). The only change is one
interface addition (MavenMultiPageReport), which has been copied in maven-
reporting-impl and maven-site-plugin 2.0-beta-6 to have it available even in
Maven versions that don't provide directly the class.
So no problem: version 3.0 of the API can be used everywhere without any
problem.
Regards,
Hervé
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: svn commit: r941507 - /maven/shared/branches/maven-reporting-impl-2.0.4.x/pom.xml
Posted by Dennis Lundberg <de...@apache.org>.
On 2010-05-09 18:54, Hervé BOUTEMY wrote:
> Le dimanche 09 mai 2010, Dennis Lundberg a écrit :
>> On 2010-05-05 23:42, hboutemy@apache.org wrote:
>>> Author: hboutemy
>>> Date: Wed May 5 21:42:51 2010
>>> New Revision: 941507
>>>
>>> URL: http://svn.apache.org/viewvc?rev=941507&view=rev
>>> Log:
>>> o next version will be 2.0.5
>>
>> Why do you want to change the version?
>> This is after all the 2.0.4.x branch.
>> As strange as the numbering scheme if for this component, I suggest that
>> we stick by it so we don't add more confusion.
>
> I finally understood the whole reasoning behind this numbering scheme. And now
> that everything is clear, we don't need to stick with it, just by fear.
>
> It's all tied to reporting decoupling from Maven core, which was done in
> steps:
> - maven-reporting-impl was moved to shared components from Maven Core after
> maven 2.0.4
> - maven-reporting-api was only moved with 3.0
>
> I documented doxia-sink-api and maven-reporting-impl coupling issues and
> changes.
Thanks! That's great and certainly make things easier to understand.
> There is no confusion any more. The summary is as simple as:
> - Maven 2.0.x, Doxia 1.0.x, maven-reporting-impl 2.0.x, maven-site-plugin
> 2.0.x
> - Maven 2.1.x, Doxia 1.1.x, maven-reporting-impl 2.1.x, maven-site-plugin
> 2.1.x
> - Maven 3.x, maven-site-plugin 3.x
So far I'm with you, but what about maven-reporting-api?
If the api (version 3.0) was decoupled from the core in version 3.0 (of
the core), can Maven 2.x use version 3.0 of the api?
Isn't version 2.0.4 of the api included in the core for the entire
current Maven 2.x line? If so doesn't that prevent it from using another
version of the api?
> Yes, there has been confusion. But There should not be any more by now.
>
> Regards,
>
> Hervé
>
> ---------------------------------------------------------------------
> 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: r941507 - /maven/shared/branches/maven-reporting-impl-2.0.4.x/pom.xml
Posted by Hervé BOUTEMY <he...@free.fr>.
Le dimanche 09 mai 2010, Dennis Lundberg a écrit :
> On 2010-05-05 23:42, hboutemy@apache.org wrote:
> > Author: hboutemy
> > Date: Wed May 5 21:42:51 2010
> > New Revision: 941507
> >
> > URL: http://svn.apache.org/viewvc?rev=941507&view=rev
> > Log:
> > o next version will be 2.0.5
>
> Why do you want to change the version?
> This is after all the 2.0.4.x branch.
> As strange as the numbering scheme if for this component, I suggest that
> we stick by it so we don't add more confusion.
I finally understood the whole reasoning behind this numbering scheme. And now
that everything is clear, we don't need to stick with it, just by fear.
It's all tied to reporting decoupling from Maven core, which was done in
steps:
- maven-reporting-impl was moved to shared components from Maven Core after
maven 2.0.4
- maven-reporting-api was only moved with 3.0
I documented doxia-sink-api and maven-reporting-impl coupling issues and
changes.
There is no confusion any more. The summary is as simple as:
- Maven 2.0.x, Doxia 1.0.x, maven-reporting-impl 2.0.x, maven-site-plugin
2.0.x
- Maven 2.1.x, Doxia 1.1.x, maven-reporting-impl 2.1.x, maven-site-plugin
2.1.x
- Maven 3.x, maven-site-plugin 3.x
Yes, there has been confusion. But There should not be any more by now.
Regards,
Hervé
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: svn commit: r941507 - /maven/shared/branches/maven-reporting-impl-2.0.4.x/pom.xml
Posted by Dennis Lundberg <de...@apache.org>.
On 2010-05-05 23:42, hboutemy@apache.org wrote:
> Author: hboutemy
> Date: Wed May 5 21:42:51 2010
> New Revision: 941507
>
> URL: http://svn.apache.org/viewvc?rev=941507&view=rev
> Log:
> o next version will be 2.0.5
Why do you want to change the version?
This is after all the 2.0.4.x branch.
As strange as the numbering scheme if for this component, I suggest that
we stick by it so we don't add more confusion.
> o updated parent pom
>
> Modified:
> maven/shared/branches/maven-reporting-impl-2.0.4.x/pom.xml
>
> Modified: maven/shared/branches/maven-reporting-impl-2.0.4.x/pom.xml
> URL: http://svn.apache.org/viewvc/maven/shared/branches/maven-reporting-impl-2.0.4.x/pom.xml?rev=941507&r1=941506&r2=941507&view=diff
> ==============================================================================
> --- maven/shared/branches/maven-reporting-impl-2.0.4.x/pom.xml (original)
> +++ maven/shared/branches/maven-reporting-impl-2.0.4.x/pom.xml Wed May 5 21:42:51 2010
> @@ -23,12 +23,12 @@
> <parent>
> <groupId>org.apache.maven.shared</groupId>
> <artifactId>maven-shared-components</artifactId>
> - <version>14</version>
> + <version>15</version>
> </parent>
>
> <groupId>org.apache.maven.reporting</groupId>
> <artifactId>maven-reporting-impl</artifactId>
> - <version>2.0.4.4-SNAPSHOT</version>
> + <version>2.0.5-SNAPSHOT</version>
>
> <name>Maven Reporting Implementation</name>
> <description>Abstract classes to manage report generation.</description>
>
>
>
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org