[ANN] Maven Release Plugin 2.1 Released

2010-10-08 Thread Brett Porter
The Maven team is pleased to announce the release of the Maven Release Plugin, 
version 2.1

This plugin is used to release a project with Maven, saving a lot of 
repetitive, manual work. Releasing a project is made in two steps: prepare and 
perform.

http://maven.apache.org/plugins/maven-release-plugin/

You should specify the version in your project's plugin configuration:


 org.apache.maven.plugins
 maven-release-plugin
 2.1


Release Notes - Maven Release Plugin - Version 2.1

** Bug
* [MRELEASE-128] - SCM properties being replaced during release:perform
* [MRELEASE-317] - release:prepare should fail if any pom depends on 
SNAPSHOT parent
* [MRELEASE-318] - Release plugin throws NullPointerException when using 
version range for dependency
* [MRELEASE-350] - Option '0' for "specify the selection number ( 0:All 
1:Project Dependencies 2:Plugins 3:Reports 4:Extensions ):" is broken
* [MRELEASE-370] - release:prepare is not updating inter-modules 
dependencies to the next version snapshot identifier correctly (-DdryRun=true).
* [MRELEASE-458] - Branch Does Not Honor updateWorkingCopyVersions Setting
* [MRELEASE-524] -  command line versions don't seem to work on 
release:branch for specific format 
* [MRELEASE-536] - CommonBasedir Calculation fails on windows
* [MRELEASE-546] - regression introduced in MRELEASE-261
* [MRELEASE-551] - Unable to release with maven 3 when having no 
$HOME/.m2/settings.xml
* [MRELEASE-563] - help strings need help, they are not helpful out of 
context
* [MRELEASE-586] - release:perform - The temporary file "pom.xml.branch" 
should be ignored as "pom.xml.next" and "pom.xml.tag" are ignored
* [MRELEASE-589] - Resolved dependencies overwritten when multiple 
subprojects with SNAPSHOT dependencies are released

** Improvement
* [MRELEASE-497] - Don't overwrite SVN auth cache
* [MRELEASE-530] - Git provider does 'git push' during 'mvn 
release:prepare' which causes unwanted problems (scm 1.4 upgrade)
* [MRELEASE-554] - Allow custom files to be modified before doing a prepare 
or branch...
* [MRELEASE-583] - Better Snapshot Dependency Handling

Enjoy,
-The Maven team

--
Brett Porter
br...@apache.org
http://brettporter.wordpress.com/





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



Re: [ANN] Apache Maven 3.0 Released

2010-10-08 Thread Baptiste MATHUS
+1, or PHP :-).

Thanks for all the work.

2010/10/8 Jochen Wiedmann 

> Thanks god, this didn't become a new Perl 6 ... :-)
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>


-- 
Baptiste  MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !


[RESULT] Release Maven Release plugin version 2.1

2010-10-08 Thread Brett Porter
Binding +1 votes: Brett, Emmanuel, Olivier
Non-binding +1 votes: Mark

I'm proceeding with the release.

Cheers,
Brett

On 04/10/2010, at 11:01 PM, Brett Porter wrote:

> Hi,
> 
> We solved 17 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11144&styleName=Html&version=12571
> 
> Staging repo:
> https://repository.apache.org/content/repositories/maven-002/
> 
> Source distribution:
> https://repository.apache.org/content/repositories/maven-002/org/apache/maven/release/maven-release/2.1/maven-release-2.1-source-release.zip
> 
> SCM tag:
> http://svn.apache.org/repos/asf/maven/release/tags/maven-release-2.1
> 
> Staging site:
> http://maven.apache.org/plugins/maven-release-plugin-2.1/
> http://maven.apache.org/maven-release/staging/
> 
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
> 
> Vote open for 72 hours.
> 
> [ ] +1
> [ ] +0
> [ ] -1
> 
> Cheers,
> Brett
> 
> 
> --
> Brett Porter
> br...@apache.org
> http://brettporter.wordpress.com/
> 
> 
> 
> 

--
Brett Porter
br...@apache.org
http://brettporter.wordpress.com/





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



Re: [ANN] Apache Maven 3.0 Released

2010-10-08 Thread Mark Hobson
Congrats!  Thanks to everyone who put the substantial effort into
making this milestone release.

Mark

On 8 October 2010 14:10, Benjamin Bentmann  wrote:
> The Maven team is pleased to announce the release of Apache Maven 3.0.
>
> Maven is a project comprehension and build tool, designed to simplify the
> process of maintaining a healthy development lifecycle for your project. You
> can read more here:
>
>  http://maven.apache.org/
>
> Downloads of source and binary distributions are listed in our download
> section:
>
>  http://maven.apache.org/download.html
>
> A major goal of Maven 3.0 is to be compatible, to the extent possible, with
> existing plugins and projects designed for Maven 2.x. Users interested in
> upgrading to this new major release should have a glance at the
> compatibility notes for known differences between Maven 3.0 and Maven 2.x:
>
>  http://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html
>
> If you encounter unexpected problems while using Maven 3.0, please feel free
> to contact us via the Maven developer list:
>
>  http://maven.apache.org/mail-lists.html
>
> Last but not least, the Maven team would like to thank all the users that
> tested the various alphas/betas/RCs and provided valuable feedback that
> helped us to eventually release a solid Maven 3.0!
>
> Release Notes - Maven 2 & 3 - Version 3.0 (since 3.0-beta-3 only)
>
> ** Bug
>    * [MNG-4592] - Snapshot artifacts that could not be downloaded due to
> communication problems are "blacklisted" for a day by default.
>    * [MNG-4751] - Snapshot version not resolved for version range
>    * [MNG-4785] - NPE in dependency resolution code for TC plugin
>    * [MNG-4786] - [regression] Ant-based mojo using maven-script-ant:2.1.0+
> cause NPE
>    * [MNG-4788] - [regression] Appassembler Maven Plugin doesn't work like
> as it should
>    * [MNG-4789] - [regression] Difference in compile scope dependency
> resolution
>    * [MNG-4791] - [regression] POM artifacts passed into
> MavenProjectBuilder.buildFromRepository() are no longer resolved
>    * [MNG-4793] - Unable to obtain archiver for extension 'zip'
>    * [MNG-4794] - 'org.apache.maven.plugins:maven-install-plugin:2.3.1'. A
> required class is missing: org.codehaus.plexus.digest.Digester
>    * [MNG-4795] - [regression] Dependencies in forked reactor projects are
> not resolved when aggregator bound to lifecycle forks
>    * [MNG-4800] - Conflict resolution does not pick sub tree of nearest
> dependency if farther conflicting dependency has wider scope
>    * [MNG-4810] - Maven cannot build if loaded in a classloader that is not
> backed by a real JAR file / classpath
>    * [MNG-4811] - Custom Maven Plugin regression in Maven 3.x, custom
> ComponentConfigurator causes infinite loop
>    * [MNG-4814] - Eary dependency resolution attempts for reactor projects
> prevent their later resolution from the reactor
>    * [MNG-4818] - NPE in legacy.DefaultWagonManager.getArtifact
>    * [MNG-4829] - [regression] Checksum failures aren't logged
>    * [MNG-4832] - Maven 3 Regression: Missing constructor of
> org.codehaus.plexus.component.configurator.converters.special.ClassRealmConverter
>    * [MNG-4834] - [regression] MavenProject.getParent() ignores configured
> repositories
>    * [MNG-4836] - Incorrect recursive expression cycle errors (update
> plexus-interpolation)
>    * [MNG-4837] - Interpolation error due to cyclic expression for one of
> the POM coordinates gets needlessly repeated
>    * [MNG-4842] - [regression] Repositories discovered in dependency POMs
> override repositories configured for original resolution request of POM
>    * [MNG-4845] - [regression] MavenProject.getDependencyArtifact() returns
> artifacts without version for dependency with version range
>
> ** Improvement
>    * [MNG-4452] - Metadata for snapshots should include classifier
>    * [MNG-4787] - Allow class realm manager delegates to alter public part
> of Maven core realm
>    * [MNG-4815] - (3.0-RC1) Maven Java API does not give nice error messages
> when improperly configured
>    * [MNG-4824] - multiple failures need additional whitespace
>    * [MNG-4825] - Relative path errors could be more explicit
>
> ** New Feature
>    * [MNG-4484] - Create a Maven API for component configuration
>
> ** Task
>    * [MNG-4805] - Update default plugin versions used for built-in lifecycle
> mappings
>    * [MNG-4807] - Extend core artifact filter to exclude relocated
> Guice-based Plexus shim
>
> ** Wish
>    * [MNG-4796] - add a warning when profiles.xml is used (Maven 2) or
> detected (Maven 3)
>
> Enjoy,
>
>
> -The Maven team
>

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



Re: [ANN] Apache Maven 3.0 Released

2010-10-08 Thread Paul Benedict
Or Duke Nukem Forever :-) -- legendary vaporware.

On Fri, Oct 8, 2010 at 9:05 AM, nicolas de loof
 wrote:
> aren't "software" and "late" some sort of synonyms ?
>
> 2010/10/8 Jason van Zyl 
>
>> A week late, but better then most of my predictions :-)
>>
>> On Oct 8, 2010, at 9:59 AM, Jochen Wiedmann wrote:
>>
>> > Thanks god, this didn't become a new Perl 6 ... :-)
>> >
>> > -
>> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> > For additional commands, e-mail: dev-h...@maven.apache.org
>> >
>>
>> Thanks,
>>
>> Jason
>>
>> --
>> Jason van Zyl
>> Founder,  Apache Maven
>> http://twitter.com/jvanzyl
>> -
>>
>> A language that doesn’t affect the way you think about programming is not
>> worth knowing.
>>
>>  -— Alan Perlis
>>
>>
>>
>>
>

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



Re: [ANN] Apache Maven 3.0 Released

2010-10-08 Thread nicolas de loof
aren't "software" and "late" some sort of synonyms ?

2010/10/8 Jason van Zyl 

> A week late, but better then most of my predictions :-)
>
> On Oct 8, 2010, at 9:59 AM, Jochen Wiedmann wrote:
>
> > Thanks god, this didn't become a new Perl 6 ... :-)
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
>
> Thanks,
>
> Jason
>
> --
> Jason van Zyl
> Founder,  Apache Maven
> http://twitter.com/jvanzyl
> -
>
> A language that doesn’t affect the way you think about programming is not
> worth knowing.
>
>  -— Alan Perlis
>
>
>
>


Re: [ANN] Apache Maven 3.0 Released

2010-10-08 Thread Jason van Zyl
A week late, but better then most of my predictions :-)

On Oct 8, 2010, at 9:59 AM, Jochen Wiedmann wrote:

> Thanks god, this didn't become a new Perl 6 ... :-)
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
> 

Thanks,

Jason

--
Jason van Zyl
Founder,  Apache Maven
http://twitter.com/jvanzyl
-

A language that doesn’t affect the way you think about programming is not worth 
knowing. 
 
 -— Alan Perlis





Re: [ANN] Apache Maven 3.0 Released

2010-10-08 Thread Jochen Wiedmann
Thanks god, this didn't become a new Perl 6 ... :-)

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



Re: [ANN] Apache Maven 3.0 Released

2010-10-08 Thread Paul Merlin

Big up ! :)

Thanks a lot for all the work and ... can't wait for the pom mixins ;)

/Paul



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



Re: Explanation for bundle&shade of org.sonatype.sisu ?

2010-10-08 Thread Stuart McCulloch
On 8 October 2010 14:10, Stanislav Ochotnicky wrote:

> Hi,
>
> I am currently in the process of packaging Maven 3 and all its
> dependencies for Fedora. I encountered few things in org.sonatype.sisu
> pom.xml that I don't entirely understand.
>
> This is the main directory structure:
> .
> ├── guice-bean
> │   ├── guice-bean-binders
> │   ├── guice-bean-containers
> │   ├── guice-bean-converters
> │   ├── guice-bean-inject
> │   ├── guice-bean-locators
> │   ├── guice-bean-reflect
> │   ├── guice-bean-scanners
> │   └── sisu-inject-bean
> └── guice-plexus
>├── guice-plexus-binders
>├── guice-plexus-converters
>├── guice-plexus-locators
>├── guice-plexus-metadata
>├── guice-plexus-scanners
>├── guice-plexus-shim
>└── sisu-inject-plexus
>
>
> sisu-inject-bean and sisu-inject plexus seem to be bundling and shading
> rest of their group respectively (plus few other libraries such as
> objectweb-asm, javax.inject and some plexus parts).
>

if you want the individual component jars then use guice-plexus-shim
and it will have the appropriate dependencies

however, you will end up with a lot of small jars so for convenience
the sisu-inject-* projects assemble the modules into a single bundle
along with OSGi metadata - the dependencies for this are adjusted
so you won't get duplicates of all the contained modules

this makes it easier to deploy and update the jars on platforms such
as OSGi where the modules form a logical group that should always
be updated at the same time


> What I don't understand is why was this approach used instead of
> standard dependency resolution of maven (addding libraries into
>  section or similar).


think of this as the equivalent of having small sub-projects which
are then assembled into a larger WAR file - it's exactly the same
except here we use the bundle-plugin to do the assembly instead
of the assembly-plugin


> For the reference I am adding part of
> sisu-inject-plexus pom.xml containing settings for bundle and shade
> plugin. I am guessing it might have something to do with the way bundle
> plugin is used, but I'd rather know for sure.
>
> -
> 
>
>  
>org.apache.felix
>maven-bundle-plugin
>true
>
>  
>
>sisu-inject-bean,*;groupId=org.codehaus.plexus
>  
>  
>
>  org.sonatype.inject.plexus
>
>
>  org.sonatype.inject
>
>
>
> org.codehaus.plexus.*;-noimport:=true;-split-package:=merge-first
>
>
>  META-INF.plexus,org.sonatype.guice.*,org.objectweb.asm
>
>  
>
>  
>  
>maven-shade-plugin
>
>  
>package
>
>  shade
>
>
>  
>
>
> ${project.groupId}:${project.artifactId}
>
>  
>  
>
>  org.objectweb
>  org.sonatype.guice
>
>  
>  
>
>  *:*
>  
>META-INF/**
>org/codehaus/plexus/**
>org/sonatype/guice/plexus/**
>org/objectweb/asm/*Writer*
>  
>
>  
>
>  
>
>  
>
>  
> 
>
> --
> Stanislav Ochotnicky 
> Associate Software Engineer - Base Operating Systems Brno
>
> PGP: 71A1677C
> Red Hat Inc.   http://cz.redhat.com
>
>


-- 
Cheers, Stuart


Explanation for bundle&shade of org.sonatype.sisu ?

2010-10-08 Thread Stanislav Ochotnicky
Hi,

I am currently in the process of packaging Maven 3 and all its
dependencies for Fedora. I encountered few things in org.sonatype.sisu
pom.xml that I don't entirely understand.

This is the main directory structure:
.
├── guice-bean
│   ├── guice-bean-binders
│   ├── guice-bean-containers
│   ├── guice-bean-converters
│   ├── guice-bean-inject
│   ├── guice-bean-locators
│   ├── guice-bean-reflect
│   ├── guice-bean-scanners
│   └── sisu-inject-bean
└── guice-plexus
├── guice-plexus-binders
├── guice-plexus-converters
├── guice-plexus-locators
├── guice-plexus-metadata
├── guice-plexus-scanners
├── guice-plexus-shim
└── sisu-inject-plexus


sisu-inject-bean and sisu-inject plexus seem to be bundling and shading
rest of their group respectively (plus few other libraries such as
objectweb-asm, javax.inject and some plexus parts).

What I don't understand is why was this approach used instead of
standard dependency resolution of maven (addding libraries into
 section or similar). For the reference I am adding part of
sisu-inject-plexus pom.xml containing settings for bundle and shade
plugin. I am guessing it might have something to do with the way bundle
plugin is used, but I'd rather know for sure.

-


  
org.apache.felix
maven-bundle-plugin
true

  

sisu-inject-bean,*;groupId=org.codehaus.plexus
  
  

  org.sonatype.inject.plexus


  org.sonatype.inject



org.codehaus.plexus.*;-noimport:=true;-split-package:=merge-first


  META-INF.plexus,org.sonatype.guice.*,org.objectweb.asm

  

  
  
maven-shade-plugin

  
package

  shade


  


${project.groupId}:${project.artifactId}

  
  

  org.objectweb
  org.sonatype.guice

  
  

  *:*
  
META-INF/**
org/codehaus/plexus/**
org/sonatype/guice/plexus/**
org/objectweb/asm/*Writer*
  

  

  

  

  


-- 
Stanislav Ochotnicky 
Associate Software Engineer - Base Operating Systems Brno

PGP: 71A1677C
Red Hat Inc.   http://cz.redhat.com



signature.asc
Description: OpenPGP digital signature


[ANN] Apache Maven 3.0 Released

2010-10-08 Thread Benjamin Bentmann

The Maven team is pleased to announce the release of Apache Maven 3.0.

Maven is a project comprehension and build tool, designed to simplify 
the process of maintaining a healthy development lifecycle for your 
project. You can read more here:


  http://maven.apache.org/

Downloads of source and binary distributions are listed in our download 
section:


  http://maven.apache.org/download.html

A major goal of Maven 3.0 is to be compatible, to the extent possible, 
with existing plugins and projects designed for Maven 2.x. Users 
interested in upgrading to this new major release should have a glance 
at the compatibility notes for known differences between Maven 3.0 and 
Maven 2.x:


  http://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html

If you encounter unexpected problems while using Maven 3.0, please feel 
free to contact us via the Maven developer list:


  http://maven.apache.org/mail-lists.html

Last but not least, the Maven team would like to thank all the users 
that tested the various alphas/betas/RCs and provided valuable feedback 
that helped us to eventually release a solid Maven 3.0!


Release Notes - Maven 2 & 3 - Version 3.0 (since 3.0-beta-3 only)

** Bug
* [MNG-4592] - Snapshot artifacts that could not be downloaded due 
to communication problems are "blacklisted" for a day by default.

* [MNG-4751] - Snapshot version not resolved for version range
* [MNG-4785] - NPE in dependency resolution code for TC plugin
* [MNG-4786] - [regression] Ant-based mojo using 
maven-script-ant:2.1.0+ cause NPE
* [MNG-4788] - [regression] Appassembler Maven Plugin doesn't work 
like as it should
* [MNG-4789] - [regression] Difference in compile scope dependency 
resolution
* [MNG-4791] - [regression] POM artifacts passed into 
MavenProjectBuilder.buildFromRepository() are no longer resolved

* [MNG-4793] - Unable to obtain archiver for extension 'zip'
* [MNG-4794] - 
'org.apache.maven.plugins:maven-install-plugin:2.3.1'. A required class 
is missing: org.codehaus.plexus.digest.Digester
* [MNG-4795] - [regression] Dependencies in forked reactor projects 
are not resolved when aggregator bound to lifecycle forks
* [MNG-4800] - Conflict resolution does not pick sub tree of 
nearest dependency if farther conflicting dependency has wider scope
* [MNG-4810] - Maven cannot build if loaded in a classloader that 
is not backed by a real JAR file / classpath
* [MNG-4811] - Custom Maven Plugin regression in Maven 3.x, custom 
ComponentConfigurator causes infinite loop
* [MNG-4814] - Eary dependency resolution attempts for reactor 
projects prevent their later resolution from the reactor

* [MNG-4818] - NPE in legacy.DefaultWagonManager.getArtifact
* [MNG-4829] - [regression] Checksum failures aren't logged
* [MNG-4832] - Maven 3 Regression: Missing constructor of 
org.codehaus.plexus.component.configurator.converters.special.ClassRealmConverter
* [MNG-4834] - [regression] MavenProject.getParent() ignores 
configured repositories
* [MNG-4836] - Incorrect recursive expression cycle errors (update 
plexus-interpolation)
* [MNG-4837] - Interpolation error due to cyclic expression for one 
of the POM coordinates gets needlessly repeated
* [MNG-4842] - [regression] Repositories discovered in dependency 
POMs override repositories configured for original resolution request of POM
* [MNG-4845] - [regression] MavenProject.getDependencyArtifact() 
returns artifacts without version for dependency with version range


** Improvement
* [MNG-4452] - Metadata for snapshots should include classifier
* [MNG-4787] - Allow class realm manager delegates to alter public 
part of Maven core realm
* [MNG-4815] - (3.0-RC1) Maven Java API does not give nice error 
messages when improperly configured

* [MNG-4824] - multiple failures need additional whitespace
* [MNG-4825] - Relative path errors could be more explicit

** New Feature
* [MNG-4484] - Create a Maven API for component configuration

** Task
* [MNG-4805] - Update default plugin versions used for built-in 
lifecycle mappings
* [MNG-4807] - Extend core artifact filter to exclude relocated 
Guice-based Plexus shim


** Wish
* [MNG-4796] - add a warning when profiles.xml is used (Maven 2) or 
detected (Maven 3)


Enjoy,


-The Maven team

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



Re: [RESULT] [VOTE] Release Apache Maven 3.0

2010-10-08 Thread Mark Derricutt
w00t - congrats to all developers and testers alike.

Time to go add an enforcer rule to all of $works projects for a 3.0 minimum
:)

-- 
Pull me down under...



On Fri, Oct 8, 2010 at 9:52 PM, Benjamin Bentmann  wrote:

> I will promote the artifacts to the central repository and continue with
> the release.


[RESULT] [VOTE] Release Apache Maven 3.0

2010-10-08 Thread Benjamin Bentmann

Hi,

The vote has passed with the following result:

+1 (binding): Benjamin Bentmann, Jason van Zyl, Emmanuel Venisse, 
Stephen Connolly, John Casey, Vincent Siveton, Daniel Kulp, Stéphane 
Nicoll, Hervé Boutemy, Arnaud Héritier, Olivier Lamy, Dennis Lundberg, 
Brett Porter, Lukas Theussl, Carlos Sanchez, Kristian Rosenvold, Brian Fox


+1 (non-binding): Greg Akins, Nicolas De Loof, Stuart McCulloch, Tony 
Chemit, Julien Henry, Jesse McConnell, Paul Merlin, Baptiste Mathus, 
Robert Scholte, Igor Fedorenko, Jesse Glick, Toni Menzel, Evgeny 
Mandrikov, Paul Benedict, Mark Derricutt, Niall Pemberton, Mark 
Struberg, Luke Patterson, Tamás Cservenák, Mark Donszelmann, Oleg 
Gusakov, Jörg Schaible


+/-0: Ralph Goers, Mark Hobson

I will promote the artifacts to the central repository and continue with 
the release.



Benjamin


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



Re: [VOTE] Release Apache Maven 3.0

2010-10-08 Thread Fabrice Bellingard
+1

Used to build Sonar, no problem.


- Fabrice
  belling...@apache.org


On Mon, Oct 4, 2010 at 2:16 PM, Benjamin Bentmann  wrote:

> Hi,
>
> feedback on the RCs seems to be decreasing and I am currently not aware of
> any major regression so let's try and cross the finishing line of this
> marathon.
>
> We solved 31 issues since 3.0-beta-3:
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=13142
>
> There are still a couple of issues left in JIRA:
>
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10500&status=1
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-004/
>
> Staged source and binary distros:
>
> https://repository.apache.org/content/repositories/maven-004/org/apache/maven/apache-maven/3.0/
>
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> +1 from me
>
>
> Benjamin
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>


Re: [VOTE] Release Apache Maven 3.0

2010-10-08 Thread chemit
Le Mon, 04 Oct 2010 14:16:07 +0200,
Benjamin Bentmann  a écrit :

Hi Benjamin, 

72 hours passed, we are so excited to have the final decision ? Would
it be today ?

Thanks ;)

Tony.
> Hi,
> 
> feedback on the RCs seems to be decreasing and I am currently not
> aware of any major regression so let's try and cross the finishing
> line of this marathon.
> 
> We solved 31 issues since 3.0-beta-3:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=13142
> 
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10500&status=1
> 
> Staging repo:
> https://repository.apache.org/content/repositories/maven-004/
> 
> Staged source and binary distros:
> https://repository.apache.org/content/repositories/maven-004/org/apache/maven/apache-maven/3.0/
> 
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
> 
> Vote open for 72 hours.
> 
> [ ] +1
> [ ] +0
> [ ] -1
> 
> +1 from me
> 
> 
> Benjamin
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
> 



-- 
Tony Chemit

tél: +33 (0) 2 40 50 29 28
email: che...@codelutin.com  
http://www.codelutin.com 

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



Re: [VOTE] Release Apache Maven 3.0

2010-10-08 Thread Jörg Schaible
Benjamin Bentmann wrote:

> Hi,
> 
> feedback on the RCs seems to be decreasing and I am currently not aware
> of any major regression so let's try and cross the finishing line of
> this marathon.
> 
> We solved 31 issues since 3.0-beta-3:
> 
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=13142
> 
> There are still a couple of issues left in JIRA:
> 
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10500&status=1
> 
> Staging repo:
> https://repository.apache.org/content/repositories/maven-004/
> 
> Staged source and binary distros:
> 
https://repository.apache.org/content/repositories/maven-004/org/apache/maven/apache-
maven/3.0/
> 
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
> 
> Vote open for 72 hours.
> 
> [ ] +1
> [ ] +0
> [ ] -1


No problems so far.
+1 from me (non-binding)

- Jörg



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