On Wed, Aug 12, 2009 at 2:59 AM, Jason van Zyl wrote:
> For Maven 2.x you'll be interested in this:
>
> http://svn.codehaus.org/plexus/plexus-containers/branches/PLX-343-plexus-container-default-1.0-alpha-9-stable-1/src/main/java/org/codehaus/plexus/component/configurator/
Thanks, I'll take a loo
On 11-Aug-09, at 7:37 AM, Jochen Wiedmann wrote:
On Tue, Aug 11, 2009 at 12:13 PM, Jason van
Zyl wrote:
Brian semi-abused the configuration mechanism to achieve what he
wanted. But
he did get it to work :-) We'll devise something that uses the
components
for 3.x but what's happening is t
The release notes are messed up. I am running Firefox 3.5 and all the issues
are within one paragraph.
On Tue, Aug 11, 2009 at 4:46 PM, John Casey wrote:
> The Maven team is pleased to announce the release of Apache Maven, version
> 2.2.1
>
> Maven is a project comprehension and build tool, desi
The Maven team is pleased to announce the release of Apache Maven,
version 2.2.1
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 are
You may want to take a look at the enforcer plugin and the rules, many
of the release criteria checks are already implemented as enforcer
rules. If you build something that could consume the enforcer rule
api, that would be pretty handy at least for the validation parts of
the release process.
On
Fine with me.
On Tue, Aug 11, 2009 at 11:09 AM, John Casey wrote:
> Re-posting to get this out of the original message thread, so it doesn't
> hide on some email clients:
>
> ---
>
> This is something I wanted to bring up on the dev list, actually. I simply
> went through all of the source-release
Hi,
This vote has passed with the following:
+1 (binding): John, Arnaud, Benjamin, Ralph, Stephane, Vincent S.
+1 (non-binding): Paul Merlin, Paul Gier
I'll promote the artifacts and make the appropriate announcements.
Thanks,
-john
John Casey wrote:
Hi,
It looks like we've got a stable r
Hi *,
We've been trying to build our internal release tools based on maven-release
infrastructure.
We failed when we tried to add new properties to configuration.
Now we are building maven plugin that will feature a bit extended concept of
ReleasePhase
(added dependencies between phases) and pluga
Re-posting to get this out of the original message thread, so it doesn't
hide on some email clients:
---
This is something I wanted to bring up on the dev list, actually. I
simply went through all of the source-release assembly descriptors used
to release various plugins, and compiled all of
Re-sending, I used the wrong from address...
---
The Maven team is pleased to announce the release of the Maven
Repository Plugin, version 2.2
This plugin simplifies the task of creating upload bundles for adding
artifacts to Maven's central repository.
http://maven.apache.org/plugins/maven-re
This is something I wanted to bring up on the dev list, actually. I
simply went through all of the source-release assembly descriptors used
to release various plugins, and compiled all of the exclusion patterns.
I'm not sure it's a good idea to leave these or any of them out, but I
can definit
The Maven team is pleased to announce the release of the Maven
Repository Plugin, version 2.2
This plugin simplifies the task of creating upload bundles for adding
artifacts to Maven's central repository.
http://maven.apache.org/plugins/maven-repository-plugin/
You should specify the version
I actually already released it, it just looks like my email didn't come
through yesterday morning...we can push another release, if we get
things filed in JIRA.
-john
Brian Fox wrote:
Before we push this, I'd like to add a requirement to include the scm
url and project url in the pom that is
I'm not sure this went through yesterday morning when I sent it, so I'm
re-sending now:
---
This vote has passed with the following:
+1: John, Benjamin, Arnaud
I'll release the artifacts and deploy the site.
Thanks,
-john
John Casey wrote:
Hi,
We solved 2 issues, and none remain in JIRA:
On Tue, Aug 11, 2009 at 12:13 PM, Jason van Zyl wrote:
> Brian semi-abused the configuration mechanism to achieve what he wanted. But
> he did get it to work :-) We'll devise something that uses the components
> for 3.x but what's happening is that configuration elements translate into
> classes i
On 11-Aug-09, at 1:27 AM, Jochen Wiedmann wrote:
On Tue, Aug 11, 2009 at 6:01 AM, Jason van Zyl
wrote:
Look at the enforcer plugin. As each rule is a component that gets
configured.
Thanks once more. I have checked the sources of the enforcer and it
sounds *exactly* like what I am looking f
2009/8/10 John Casey :
> If I do that, we'll have to redo this vote. I'm hoping to get 2.2.1 out to
> fix some problems in 2.2.0 that make it nearly unusable for deployment.
>
> Is this issue important enough to push the release off by another week? If
> not, can we just push it out as part of 2.2.
On Tue, Aug 11, 2009 at 6:01 AM, Jason van Zyl wrote:
> Look at the enforcer plugin. As each rule is a component that gets
> configured.
Thanks once more. I have checked the sources of the enforcer and it
sounds *exactly* like what I am looking for. However, I haven't got
the slightest idea how it
18 matches
Mail list logo
