You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Brian E. Fox" <br...@reply.infinity.nu> on 2008/09/08 21:19:16 UTC

[vote] release maven-parent 9

I need to release the maven-parent v9 before I can do the enforcer
release. Since there isn't a project to track changes in jira, here are
the diffs since v8. It's mostly housekeeping and plugin lockdown:

 

http://svn.apache.org/viewvc/maven/pom/trunk/maven/pom.xml?r1=632423&r2=
693201&diff_format=h

 

The pom is staged at:
http://people.apache.org/~brianf/stage/org/apache/maven/maven-parent/

 

Vote is open for 72hrs.

 

+1

 

 

I will go forward and stage the enforcer release in the same repository.


Re: [vote] release maven-parent 9

Posted by Dennis Lundberg <de...@apache.org>.
OK, thanks for explaining Brian.

I'll take snippets of your descriptions and put into a JIRA for the
Clirr plugin. A skip parameter is on top of the wish list right?

Brian E. Fox wrote:
>> No, it's available in the quality-checks profile as well.
> 
> I saw that but it didn't work. It tried to find alpha-3-snapshot because
> it was running against alpha-4-snapshot.
> 
>> It is supposed to do this:
>>  "compares the current code against the latest released version"
>> This is also what it does, to my experience. Can you give us an example
>> that isn't working for you?
> 
> Nope. See above as I was testing to exclude certain things I found this
> problem.
> 
>>> and worse, I can't even disable this from running in my
>>> project.
> 
>> Although a plain and simple "skip" parameter would be preferable, you
>> should be able to exclude all classes from Clirr using something like
> this:
> 
> No because the plugin first tries to resolve an artifact that doesn't
> exist. It doesn't matter if I have excluded everything, it blows up
> before that.
> 
> 
>> I disagree. If necessary you can use the comparisonVersion parameter to
>> specify exactly which version Clirr should compare against, although as
>> I said above you shouldn't need to.
> 
> Again, see above. What should I set it to if there is no previous
> version? It wants to resolve something and blows up when it can't find
> it...doesn't matter if I exclude everything.
> 
>> What is it in the enforcer that blows up because of this?
> The rules and api where not separate projects in alpha-3 so there is
> nothing to compare against.
> 
>> -----Original Message-----
>> From: Vincent Siveton [mailto:vincent.siveton@gmail.com] 
>> Sent: Monday, September 08, 2008 3:48 PM
>> To: Maven Developers List
>> Subject: Re: [vote] release maven-parent 9
>>
>> 2008/9/8 Brian E. Fox <br...@reply.infinity.nu>
>>> I need to release the maven-parent v9 before I can do the enforcer
>>> release. Since there isn't a project to track changes in jira, here
>> are
>>> the diffs since v8. It's mostly housekeeping and plugin lockdown:
>>>
>>>
>>>
>>>
> http://svn.apache.org/viewvc/maven/pom/trunk/maven/pom.xml?r1=632423&r2=
>>> 693201&diff_format=h
>>>
>> -1 since maven-enforcer-plugin has snapshot version.
>>
>> Vincent
>>
>>> The pom is staged at:
>>> http://people.apache.org/~brianf/stage/org/apache/maven/maven-parent/
>>>
>>>
>>>
>>> Vote is open for 72hrs.
>>>
>>>
>>>
>>> +1
>>>
>>>
>>>
>>>
>>>
>>> I will go forward and stage the enforcer release in the same
>> repository.
>>
>> ---------------------------------------------------------------------
>> 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
>>
>>
> 
> 


-- 
Dennis Lundberg

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


Re: [vote] release maven-parent 9

Posted by Brian Fox <br...@reply.infinity.nu>.
Ok, I'll take another look and if it works correctly put it back for v10

Sent from my iPhone

On Sep 13, 2008, at 6:12 PM, Dennis Lundberg <de...@apache.org> wrote:

> Brian E. Fox wrote:
>>> No, it's available in the quality-checks profile as well.
>>
>> I saw that but it didn't work. It tried to find alpha-3-snapshot  
>> because
>> it was running against alpha-4-snapshot.
>
> I had a look at this and the Clirr Plugin works as expected for the
> enforcer for me. Here are the (trimmed down) results I get when I run
> 'mvn clirr:clirr' on r694550. That's just prior to your last Release
> Plugin run.
>
>
> G:\apache\maven\tags\enforcer-r694550>mvn clirr:clirr
> [INFO] Scanning for projects...
> [INFO] Reactor build order:
> [INFO]   Enforcer
> [INFO]   Enforcer API
> [INFO]   Enforcer Rules
> [INFO]   Maven Enforcer Plugin
> ...
> [INFO]
> --- 
> ---------------------------------------------------------------------
> [INFO] Building Enforcer
> [INFO]    task-segment: [clirr:clirr]
> [INFO]
> --- 
> ---------------------------------------------------------------------
> ...
> [INFO] [clirr:clirr]
> [INFO] Not generating Clirr report as there are no classes generated  
> by
> the project
> [INFO]
> --- 
> ---------------------------------------------------------------------
> [INFO] Building Enforcer API
> [INFO]    task-segment: [clirr:clirr]
> [INFO]
> --- 
> ---------------------------------------------------------------------
> ...
> [INFO] [clirr:clirr]
> [INFO] artifact org.apache.maven.enforcer:enforcer-api: checking for
> updates from central
> [INFO] Unable to find a previous version of the project in the  
> repository
> [INFO] Not generating Clirr report as there is no previous version of
> the library to compare against
> [INFO]
> --- 
> ---------------------------------------------------------------------
> [INFO] Building Enforcer Rules
> [INFO]    task-segment: [clirr:clirr]
> [INFO]
> --- 
> ---------------------------------------------------------------------
> ...
> [INFO] [clirr:clirr]
> [INFO] artifact org.apache.maven.enforcer:enforcer-rules: checking for
> updates from central
> [INFO] Unable to find a previous version of the project in the  
> repository
> [INFO] Not generating Clirr report as there is no previous version of
> the library to compare against
> [INFO]
> --- 
> ---------------------------------------------------------------------
> [INFO] Building Maven Enforcer Plugin
> [INFO]    task-segment: [clirr:clirr]
> [INFO]
> --- 
> ---------------------------------------------------------------------
> ...
> [INFO] [clirr:clirr]
> [INFO] artifact org.apache.maven.plugins:maven-enforcer-plugin:  
> checking
> for updates from central
> [INFO] Comparing to version: 1.0-alpha-3
>
>
>
> Summary:
> - It skips the parent because there are no classes
> - It skips the API because there is no previous version in the repo
> - It skips the rules because there is no previous version in the repo
> - It compares the plugin against 1.0-alpha-3
>
> This all seems to be in order to me.
>
> The only possible reason I could find in JIRA was
> http://jira.codehaus.org/browse/MCLIRR-15 which was because of bad  
> local
> meta data.
>
>>
>>> It is supposed to do this:
>>> "compares the current code against the latest released version"
>>> This is also what it does, to my experience. Can you give us an  
>>> example
>>> that isn't working for you?
>>
>> Nope. See above as I was testing to exclude certain things I found  
>> this
>> problem.
>>
>>>> and worse, I can't even disable this from running in my
>>>> project.
>>
>>> Although a plain and simple "skip" parameter would be preferable,  
>>> you
>>> should be able to exclude all classes from Clirr using something  
>>> like
>> this:
>>
>> No because the plugin first tries to resolve an artifact that doesn't
>> exist. It doesn't matter if I have excluded everything, it blows up
>> before that.
>>
>>
>>> I disagree. If necessary you can use the comparisonVersion  
>>> parameter to
>>> specify exactly which version Clirr should compare against,  
>>> although as
>>> I said above you shouldn't need to.
>>
>> Again, see above. What should I set it to if there is no previous
>> version? It wants to resolve something and blows up when it can't  
>> find
>> it...doesn't matter if I exclude everything.
>>
>>> What is it in the enforcer that blows up because of this?
>> The rules and api where not separate projects in alpha-3 so there is
>> nothing to compare against.
>>
>>> -----Original Message-----
>>> From: Vincent Siveton [mailto:vincent.siveton@gmail.com]
>>> Sent: Monday, September 08, 2008 3:48 PM
>>> To: Maven Developers List
>>> Subject: Re: [vote] release maven-parent 9
>>>
>>> 2008/9/8 Brian E. Fox <br...@reply.infinity.nu>
>>>> I need to release the maven-parent v9 before I can do the enforcer
>>>> release. Since there isn't a project to track changes in jira, here
>>> are
>>>> the diffs since v8. It's mostly housekeeping and plugin lockdown:
>>>>
>>>>
>>>>
>>>>
>> http://svn.apache.org/viewvc/maven/pom/trunk/maven/pom.xml?r1=632423&r2=
>>>> 693201&diff_format=h
>>>>
>>> -1 since maven-enforcer-plugin has snapshot version.
>>>
>>> Vincent
>>>
>>>> The pom is staged at:
>>>> http://people.apache.org/~brianf/stage/org/apache/maven/maven-parent/
>>>>
>>>>
>>>>
>>>> Vote is open for 72hrs.
>>>>
>>>>
>>>>
>>>> +1
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> I will go forward and stage the enforcer release in the same
>>> repository.
>>>
>>> --- 
>>> ------------------------------------------------------------------
>>> 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
>>>
>>>
>>
>>
>
>
> -- 
> Dennis Lundberg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>

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


Re: [vote] release maven-parent 9

Posted by Dennis Lundberg <de...@apache.org>.
Brian E. Fox wrote:
>> No, it's available in the quality-checks profile as well.
> 
> I saw that but it didn't work. It tried to find alpha-3-snapshot because
> it was running against alpha-4-snapshot.

I had a look at this and the Clirr Plugin works as expected for the
enforcer for me. Here are the (trimmed down) results I get when I run
'mvn clirr:clirr' on r694550. That's just prior to your last Release
Plugin run.


G:\apache\maven\tags\enforcer-r694550>mvn clirr:clirr
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO]   Enforcer
[INFO]   Enforcer API
[INFO]   Enforcer Rules
[INFO]   Maven Enforcer Plugin
...
[INFO]
------------------------------------------------------------------------
[INFO] Building Enforcer
[INFO]    task-segment: [clirr:clirr]
[INFO]
------------------------------------------------------------------------
...
[INFO] [clirr:clirr]
[INFO] Not generating Clirr report as there are no classes generated by
the project
[INFO]
------------------------------------------------------------------------
[INFO] Building Enforcer API
[INFO]    task-segment: [clirr:clirr]
[INFO]
------------------------------------------------------------------------
...
[INFO] [clirr:clirr]
[INFO] artifact org.apache.maven.enforcer:enforcer-api: checking for
updates from central
[INFO] Unable to find a previous version of the project in the repository
[INFO] Not generating Clirr report as there is no previous version of
the library to compare against
[INFO]
------------------------------------------------------------------------
[INFO] Building Enforcer Rules
[INFO]    task-segment: [clirr:clirr]
[INFO]
------------------------------------------------------------------------
...
[INFO] [clirr:clirr]
[INFO] artifact org.apache.maven.enforcer:enforcer-rules: checking for
updates from central
[INFO] Unable to find a previous version of the project in the repository
[INFO] Not generating Clirr report as there is no previous version of
the library to compare against
[INFO]
------------------------------------------------------------------------
[INFO] Building Maven Enforcer Plugin
[INFO]    task-segment: [clirr:clirr]
[INFO]
------------------------------------------------------------------------
...
[INFO] [clirr:clirr]
[INFO] artifact org.apache.maven.plugins:maven-enforcer-plugin: checking
for updates from central
[INFO] Comparing to version: 1.0-alpha-3



Summary:
- It skips the parent because there are no classes
- It skips the API because there is no previous version in the repo
- It skips the rules because there is no previous version in the repo
- It compares the plugin against 1.0-alpha-3

This all seems to be in order to me.

The only possible reason I could find in JIRA was
http://jira.codehaus.org/browse/MCLIRR-15 which was because of bad local
meta data.

> 
>> It is supposed to do this:
>>  "compares the current code against the latest released version"
>> This is also what it does, to my experience. Can you give us an example
>> that isn't working for you?
> 
> Nope. See above as I was testing to exclude certain things I found this
> problem.
> 
>>> and worse, I can't even disable this from running in my
>>> project.
> 
>> Although a plain and simple "skip" parameter would be preferable, you
>> should be able to exclude all classes from Clirr using something like
> this:
> 
> No because the plugin first tries to resolve an artifact that doesn't
> exist. It doesn't matter if I have excluded everything, it blows up
> before that.
> 
> 
>> I disagree. If necessary you can use the comparisonVersion parameter to
>> specify exactly which version Clirr should compare against, although as
>> I said above you shouldn't need to.
> 
> Again, see above. What should I set it to if there is no previous
> version? It wants to resolve something and blows up when it can't find
> it...doesn't matter if I exclude everything.
> 
>> What is it in the enforcer that blows up because of this?
> The rules and api where not separate projects in alpha-3 so there is
> nothing to compare against.
> 
>> -----Original Message-----
>> From: Vincent Siveton [mailto:vincent.siveton@gmail.com] 
>> Sent: Monday, September 08, 2008 3:48 PM
>> To: Maven Developers List
>> Subject: Re: [vote] release maven-parent 9
>>
>> 2008/9/8 Brian E. Fox <br...@reply.infinity.nu>
>>> I need to release the maven-parent v9 before I can do the enforcer
>>> release. Since there isn't a project to track changes in jira, here
>> are
>>> the diffs since v8. It's mostly housekeeping and plugin lockdown:
>>>
>>>
>>>
>>>
> http://svn.apache.org/viewvc/maven/pom/trunk/maven/pom.xml?r1=632423&r2=
>>> 693201&diff_format=h
>>>
>> -1 since maven-enforcer-plugin has snapshot version.
>>
>> Vincent
>>
>>> The pom is staged at:
>>> http://people.apache.org/~brianf/stage/org/apache/maven/maven-parent/
>>>
>>>
>>>
>>> Vote is open for 72hrs.
>>>
>>>
>>>
>>> +1
>>>
>>>
>>>
>>>
>>>
>>> I will go forward and stage the enforcer release in the same
>> repository.
>>
>> ---------------------------------------------------------------------
>> 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
>>
>>
> 
> 


-- 
Dennis Lundberg

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


RE: [vote] release maven-parent 9

Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
>No, it's available in the quality-checks profile as well.

I saw that but it didn't work. It tried to find alpha-3-snapshot because
it was running against alpha-4-snapshot.

>It is supposed to do this:
>  "compares the current code against the latest released version"
>This is also what it does, to my experience. Can you give us an example
>that isn't working for you?

Nope. See above as I was testing to exclude certain things I found this
problem.

>> and worse, I can't even disable this from running in my
>> project.

>Although a plain and simple "skip" parameter would be preferable, you
>should be able to exclude all classes from Clirr using something like
this:

No because the plugin first tries to resolve an artifact that doesn't
exist. It doesn't matter if I have excluded everything, it blows up
before that.


>I disagree. If necessary you can use the comparisonVersion parameter to
>specify exactly which version Clirr should compare against, although as
>I said above you shouldn't need to.

Again, see above. What should I set it to if there is no previous
version? It wants to resolve something and blows up when it can't find
it...doesn't matter if I exclude everything.

>What is it in the enforcer that blows up because of this?
The rules and api where not separate projects in alpha-3 so there is
nothing to compare against.

> -----Original Message-----
> From: Vincent Siveton [mailto:vincent.siveton@gmail.com] 
> Sent: Monday, September 08, 2008 3:48 PM
> To: Maven Developers List
> Subject: Re: [vote] release maven-parent 9
> 
> 2008/9/8 Brian E. Fox <br...@reply.infinity.nu>
>> I need to release the maven-parent v9 before I can do the enforcer
>> release. Since there isn't a project to track changes in jira, here
> are
>> the diffs since v8. It's mostly housekeeping and plugin lockdown:
>>
>>
>>
>>
>
http://svn.apache.org/viewvc/maven/pom/trunk/maven/pom.xml?r1=632423&r2=
>> 693201&diff_format=h
>>
> 
> -1 since maven-enforcer-plugin has snapshot version.
> 
> Vincent
> 
>> The pom is staged at:
>> http://people.apache.org/~brianf/stage/org/apache/maven/maven-parent/
>>
>>
>>
>> Vote is open for 72hrs.
>>
>>
>>
>> +1
>>
>>
>>
>>
>>
>> I will go forward and stage the enforcer release in the same
> repository.
> 
> ---------------------------------------------------------------------
> 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
> 
> 


-- 
Dennis Lundberg

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


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


Re: [vote] release maven-parent 9

Posted by Dennis Lundberg <de...@apache.org>.
Brian E. Fox wrote:
> -1 also because Clirr is a PITA. First of all, it is only setup to run
> when you do a release so you don't notice a problem until you are in the
> throws of releasing.

No, it's available in the quality-checks profile as well.

> Second, Clirr can't run against a snapshot because
> it tries to find the previous version snapshot (not the last release
> version)

It is supposed to do this:
  "compares the current code against the latest released version"
This is also what it does, to my experience. Can you give us an example
that isn't working for you?

> and worse, I can't even disable this from running in my
> project.

Although a plain and simple "skip" parameter would be preferable, you
should be able to exclude all classes from Clirr using something like this:

<configuration>
  <excludes>
    <exclude>org/apache/**</exclude>
  </excludes>
</configuration>

> Having clirr in the parent is forcing it on enforcer...well for
> some jars there is nothing old to compare it against and so it will
> always fail for me. We simply have to take it out of the parent until
> Clirr has better control over the versions and a skip flag.

I disagree. If necessary you can use the comparisonVersion parameter to
specify exactly which version Clirr should compare against, although as
I said above you shouldn't need to.

What is it in the enforcer that blows up because of this?

> -----Original Message-----
> From: Vincent Siveton [mailto:vincent.siveton@gmail.com] 
> Sent: Monday, September 08, 2008 3:48 PM
> To: Maven Developers List
> Subject: Re: [vote] release maven-parent 9
> 
> 2008/9/8 Brian E. Fox <br...@reply.infinity.nu>
>> I need to release the maven-parent v9 before I can do the enforcer
>> release. Since there isn't a project to track changes in jira, here
> are
>> the diffs since v8. It's mostly housekeeping and plugin lockdown:
>>
>>
>>
>>
> http://svn.apache.org/viewvc/maven/pom/trunk/maven/pom.xml?r1=632423&r2=
>> 693201&diff_format=h
>>
> 
> -1 since maven-enforcer-plugin has snapshot version.
> 
> Vincent
> 
>> The pom is staged at:
>> http://people.apache.org/~brianf/stage/org/apache/maven/maven-parent/
>>
>>
>>
>> Vote is open for 72hrs.
>>
>>
>>
>> +1
>>
>>
>>
>>
>>
>> I will go forward and stage the enforcer release in the same
> repository.
> 
> ---------------------------------------------------------------------
> 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
> 
> 


-- 
Dennis Lundberg

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


RE: [vote] release maven-parent 9

Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
-1 also because Clirr is a PITA. First of all, it is only setup to run
when you do a release so you don't notice a problem until you are in the
throws of releasing. Second, Clirr can't run against a snapshot because
it tries to find the previous version snapshot (not the last release
version) and worse, I can't even disable this from running in my
project. Having clirr in the parent is forcing it on enforcer...well for
some jars there is nothing old to compare it against and so it will
always fail for me. We simply have to take it out of the parent until
Clirr has better control over the versions and a skip flag.


-----Original Message-----
From: Vincent Siveton [mailto:vincent.siveton@gmail.com] 
Sent: Monday, September 08, 2008 3:48 PM
To: Maven Developers List
Subject: Re: [vote] release maven-parent 9

2008/9/8 Brian E. Fox <br...@reply.infinity.nu>
>
> I need to release the maven-parent v9 before I can do the enforcer
> release. Since there isn't a project to track changes in jira, here
are
> the diffs since v8. It's mostly housekeeping and plugin lockdown:
>
>
>
>
http://svn.apache.org/viewvc/maven/pom/trunk/maven/pom.xml?r1=632423&r2=
> 693201&diff_format=h
>

-1 since maven-enforcer-plugin has snapshot version.

Vincent

>
> The pom is staged at:
> http://people.apache.org/~brianf/stage/org/apache/maven/maven-parent/
>
>
>
> Vote is open for 72hrs.
>
>
>
> +1
>
>
>
>
>
> I will go forward and stage the enforcer release in the same
repository.
>

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


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


Re: [vote] release maven-parent 9

Posted by Vincent Siveton <vi...@gmail.com>.
2008/9/8 Brian E. Fox <br...@reply.infinity.nu>
>
> I need to release the maven-parent v9 before I can do the enforcer
> release. Since there isn't a project to track changes in jira, here are
> the diffs since v8. It's mostly housekeeping and plugin lockdown:
>
>
>
> http://svn.apache.org/viewvc/maven/pom/trunk/maven/pom.xml?r1=632423&r2=
> 693201&diff_format=h
>

-1 since maven-enforcer-plugin has snapshot version.

Vincent

>
> The pom is staged at:
> http://people.apache.org/~brianf/stage/org/apache/maven/maven-parent/
>
>
>
> Vote is open for 72hrs.
>
>
>
> +1
>
>
>
>
>
> I will go forward and stage the enforcer release in the same repository.
>

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


Re: [vote] release maven-parent 9

Posted by Arnaud HERITIER <ah...@gmail.com>.
+1

Arnaud

On Mon, Sep 8, 2008 at 9:19 PM, Brian E. Fox <br...@reply.infinity.nu>wrote:

> I need to release the maven-parent v9 before I can do the enforcer
> release. Since there isn't a project to track changes in jira, here are
> the diffs since v8. It's mostly housekeeping and plugin lockdown:
>
>
>
> http://svn.apache.org/viewvc/maven/pom/trunk/maven/pom.xml?r1=632423&r2=
> 693201&diff_format=h<http://svn.apache.org/viewvc/maven/pom/trunk/maven/pom.xml?r1=632423&r2=693201&diff_format=h>
>
>
>
> The pom is staged at:
> http://people.apache.org/~brianf/stage/org/apache/maven/maven-parent/<http://people.apache.org/%7Ebrianf/stage/org/apache/maven/maven-parent/>
>
>
>
> Vote is open for 72hrs.
>
>
>
> +1
>
>
>
>
>
> I will go forward and stage the enforcer release in the same repository.
>
>


-- 
..........................................................
Arnaud HERITIER
..........................................................
OCTO Technology - aheritier AT octo DOT com
www.octo.com | blog.octo.com
..........................................................
ASF - aheritier AT apache DOT org
www.apache.org | maven.apache.org
...........................................................