Hi,
Okay... so what's decided now. Shall we,
1. extend the plugin executor in the maven core to not invoke the plugin at
all (as implemented by my patches)
or...
2. extend the maven-plugin-plugin to automatically generate skip properties
Moreover, if we make maven-plugin-plugin to emit the 'skip
On 2011-02-08 21:41, Dennis Lundberg wrote:
> I think it would be a useful service to our users to list which plugins
> and components are @threadSafe, and also in which version it was first
> marked as @threadSafe.
A list of released plugins is now in place, as well as some that are in
the pipeli
The Maven team is pleased to announce the release of the Maven Plugin
Plugin, version 2.7
The Maven Plugin Plugin is used to create a Maven plugin descriptor for
any Mojo's found in the source tree, to include in the JAR. It is also
used to generate report files for the Mojos as well as for updati
Here's a workaround in the meantime:
http://svn.apache.org/viewvc/maven/pom/trunk/asf/pom.xml?p2=%2Fmaven%2Fpom%2Ftrunk%2Fasf%2Fpom.xml&p1=%2Fmaven%2Fpom%2Ftrunk%2Fasf%2Fpom.xml&r1=1065778&r2=1065777&view=diff&pathrev=1065778
On Wed, Feb 9, 2011 at 9:12 AM, John Patrick wrote:
> Hi,
>
> I believe
Vote for this jira ticket:
http://jira.codehaus.org/browse/MNG-4760
/Anders
On Wed, Feb 9, 2011 at 15:12, John Patrick wrote:
> Hi,
>
> I believe this is the right mailing list, but please send me else where if
> not.
>
> I would like to request that a new profile activation type be added,
> wh
Hi,
I believe this is the right mailing list, but please send me else where if not.
I would like to request that a new profile activation type be added,
which is based upon the maven version that is executing. What are
people version upon this change?
Base Ground
I've just done an upgrade f
I think this was my suggestion originally, as being one way to
document how to find information on the ASF POM from the POM.
I suggested using the and which provide the
relevant information.
However, a block comment would do just as well if those are needed to
be set differently.
[And clearly t
If folks are willing to maintain a list of configured plugins in CMS,
I (not that it matters a lot) don't object to shovelling all this into
the CMS.
On Tue, Feb 8, 2011 at 9:51 PM, Brian Fox wrote:
> On Tue, Feb 8, 2011 at 9:45 PM, Benson Margulies
> wrote:
>> I was somewhat squeamish about al
In which case please add some comments:
- to say why URL must be www.a.o
- to note the URL for the POM itself so people can find its documentation.
On 9 February 2011 02:27, Brian Fox wrote:
> You realize that this may cause everyone to inherit the wrong url now?
> We should have the default url
http://jira.codehaus.org/browse/MINDEXER-11
Please comment.
Thanks,
~t~
2011/2/9 Tamás Cservenák :
> Just to chime in:
>
> Maven Indexer already cranks up and parses plugin.xml to gather the
> plugin prefix and existing goals
>
>
> Thanks,
> ~t~
>
> On Tue, Feb 8, 2011 at 11:00 PM, Jason va
Just to chime in:
Maven Indexer already cranks up and parses plugin.xml to gather the
plugin prefix and existing goals
Thanks,
~t~
On Tue, Feb 8, 2011 at 11:00 PM, Jason van Zyl wrote:
>
> On Feb 8, 2011, at 4:54 PM, Dennis Lundberg wrote:
>
>> My current focus is on the Apache Maven proje
Hello,
I agree.
But note I have missed something in the ASF pom
org.apache.maven.plugins
maven-release-plugin
2.1
false
deploy
apache-release
And I have added in two places a kind of warning f
Benson, the signing itself doesn't take that long, even for projects like
OpenJPA which needs about 1 hour for the whole build. So I'm with Brian that
it's better to spend 1 minute for the code signing in the prepare phase than
having to revert tags, branches, rebuild all from scratch again, etc
13 matches
Mail list logo
