here is my +1
Le mercredi 31 août 2011, Hervé BOUTEMY a écrit :
Hi,
We solved 24 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11095styleName=
Htmlversion=16795
There are still a good number of issues left in JIRA:
Hi,
The vote has passed with the following result :
+1 (binding): Kristian Rosenvold, Vincent Siveton, John Casey, Olivier Lamy,
Emmanuel Venisse, Hervé Boutemy
+1 (non binding): Tamás Cservenák, Jesse Glick
I will promote the artifacts to the central repo.
Hi Benson,
about MPLUGIN-181: The right to solve this is a java-escape of the forward
slash, so: default-value=**\/*.xml
Might be worth an entry for the FAQ's.
-Robert
Date: Fri, 2 Sep 2011 09:38:24 -0400
Subject: I'd like to release maven-plugin-plugin
From: bimargul...@gmail.com
The Maven team is pleased to announce the release of the Maven Archetype
Plugin, version 2.1
Archetype is a Maven project templating toolkit.
http://maven.apache.org/archetype/maven-archetype-plugin/
Release Notes - Maven Archetype - Version 2.1
** Bug
* [ARCHETYPE-220] - Unable to
I'm trying to be slightly helpful to the Tycho project. They have a
problem: they need to define a lifecycle that adds a plugin to a phase
*not at the end* of the plugins in the standard lifecycle.
Has anyone else thought about this?
This is an awesome set of features
Congrats!!!
On Sep 4, 2011 8:05 AM, Hervé Boutemy hbout...@apache.org wrote:
The Maven team is pleased to announce the release of the Maven Archetype
Plugin, version 2.1
Archetype is a Maven project templating toolkit.
On 05/09/2011, at 3:49 AM, Benson Margulies wrote:
I'm trying to be slightly helpful to the Tycho project. They have a
problem: they need to define a lifecycle that adds a plugin to a phase
*not at the end* of the plugins in the standard lifecycle.
Has anyone else thought about this?
On Sun, Sep 4, 2011 at 7:10 PM, Brett Porter br...@apache.org wrote:
On 05/09/2011, at 3:49 AM, Benson Margulies wrote:
I'm trying to be slightly helpful to the Tycho project. They have a
problem: they need to define a lifecycle that adds a plugin to a phase
*not at the end* of the plugins
On 05/09/2011, at 10:37 AM, Benson Margulies wrote:
On Sun, Sep 4, 2011 at 7:10 PM, Brett Porter br...@apache.org wrote:
On 05/09/2011, at 3:49 AM, Benson Margulies wrote:
I'm trying to be slightly helpful to the Tycho project. They have a
problem: they need to define a lifecycle that
Looked around; cannot find out where to report bugs in the apache jar
resource bundle.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
I agree that adding new phase (or phases) does not look like a scalable
solution. For example, in addition to signing, Eclipse projects are
encouraged to pack200 their artifacts, but neither signing nor pack200
are mandatory. So we need to be able add both sign and pack200 steps to
the lifecycle
I don't believe there is one. Probably the easiest thing to do would be to
create some new components in https://issues.apache.org/jira/browse/MPOM (I
know they aren't POMs, but it's basically the same scope).
On 05/09/2011, at 12:41 PM, sebb wrote:
Looked around; cannot find out where to
12 matches
Mail list logo
