Are you thinking of maven-enforcer-plugin? I was referring to
maven-plugin-enforcer! :-p *crosses eyes*
https://svn.apache.org/repos/asf/maven/enforcer/trunk/maven-enforcer-plugin/
https://svn.apache.org/repos/asf/maven/shared/trunk/maven-plugin-enforcer/
maven-enforcer-plugin is, indeed, a
Enforcer is a plugin with a set if plexus component rules...not an
extension. I would add this to shared, it doesn't seem to justify a
new tree and parent structure.
On Friday, November 5, 2010, Dan Fabulich wrote:
>
> The maven-reactor-plugin for M2 served its purpose, which was to make it
> ea
Really, this is a question of how apache maven wants to approach the apache
version standard. I'm begin to believe it would be bad form to rely on a
mojo plugin to do this. It would also be inappropriate to build the
functionality into maven proper as well (as part of the
DefaultArtifactVersion)
The maven-reactor-plugin for M2 served its purpose, which was to make it
easier to build partial subsets of Maven projects in Maven 2.0. In Maven
2.1, we added much of the functionality of maven-reactor-plugin as
command-line arguments to maven: --resume-from, --also-make,
--also-make-depend
I thought you were going to rework the patch...
If you have reworked the patch, then ping the d...@mojo list again...
given that the feeling is that m-enforcer-p is not a good fit (because
of phases)
and given that v-m-p is not a good fit (because I'm going to insist
that v-m-p does not have any
Actually since it's merged with the Enforcer Plugin, I'll wait until
tomorrow and promote them together.
On Fri, Nov 5, 2010 at 2:50 PM, Brian Fox wrote:
> Vote passed, I'll release it now.
>
> +1: Brian, Jason, Stephen, Arnaud, Olivier
>
> On Mon, Nov 1, 2010 at 7:03 PM, Olivier Lamy wrote:
>>
Hmm... good point about the phase i'll have to think on that. We can
always have two executions for the plugin, or perhaps the plugin should
allow a rule to specify what phase it wants to be run in, thought that would
be harder to pull off. Though probably more correct.
I have already writte
Vote passed, I'll release it now.
+1: Brian, Jason, Stephen, Arnaud, Olivier
On Mon, Nov 1, 2010 at 7:03 PM, Olivier Lamy wrote:
> +1
> - Olivier
>
> Le 1 nov. 2010 22:52, "Brian Fox" a écrit :
>
> I'm preparing the enforcer release and it needs the latest parent
> changes, so I've cut a releas
Hi,
Can you please tell me which class is responsible for parsing pom.xml in maven
jar. Also is there a javadoc available for maven jar.
Regards
Raghvendra
On 4 November 2010 18:28, Rex Hoffman wrote:
> Seems reasonable, build a helper library to run clirr and analyze it's
> results, allow the clirr plugin to use it in it's existing manner, or by an
> enforcer rule.
>
> That fact that it's clirr under the hood of that enforcer rule will be
> complete
Hi All,
We have small problem with Apache Camel archetypes. Archetypes from version
2.2 are not visible in archetype-catalog.xml. There was no changes in
release procedure. Similar archetypes (with a bit different versions) are
available on FUSE maven 2 repo:
http://repo.fusesource.com/maven2/arch
maven-parent 17 is being voted for and is in a staged repo.
http://maven.40175.n5.nabble.com/vote-release-maven-parent-17-td3245817.html#a3245817
/Anders
On Fri, Nov 5, 2010 at 09:01, Matthias Wessendorf wrote:
> Hi,
>
> I noticed that our (MyFaces) hudson fails to build some of our
> subprojec
Hi,
I noticed that our (MyFaces) hudson fails to build some of our
subprojects, like:
https://hudson.apache.org/hudson/job/MyFaces-Trinidad-2.0.x/31/consoleText
While tracing down the issue, I think there is a problem with the
maven-parent used inside
of the 1.1-SNAPSHOT (trunk) of the enforcer m
13 matches
Mail list logo