On Fri, Mar 2, 2007 at 12:38 AM, Guillaume Duchesneau
<[EMAIL PROTECTED]> wrote:
> I am currently developing some mojos to improve our build and I am a
> little bit confused between two parameters that can be set in a mojo:
> - ${executedProject}
> - ${project}
> What is the diffe
I don't like the idea that I can use one version of the plugin as a
plugin (is there a better term for the use in a build?) and then
specify another version of the plugin for reporting. I find that it's
very difficult to keep them in sync since there are many plugins that
end up in both sections.
as said IIRC, I'm working on Modello stabilization and having a consistent set
of features across every plugins.
I need some more weeks to include features tests on every plugin, then fix
inconsistencies like MODELLO-127: I still don't have the full list of
inconsistencies to fix before 1.0 (or
Given that this has been copied into trunk and is not used from Maven
2.x, I'd like to suggest the following:
- move all OPEN issues to either MERCURY or MNG, and make the JIRA
project inactive (basically just a record of the 3.0-alpha-1 release)
- remove the trunk and the svn:externals defin
Jason van Zyl wrote:
Oleg,
Shane and I were chatting and I think the maven-mercury module in
trunk can actually go into Mercury itself, there is nothing trunk
specific in there and almost makes you trunk free.
This kind of beats the purpose of externalizing dependency processing.
Mercury de
2008/12/1 <[EMAIL PROTECTED]>
> Author: jvanzyl
> Date: Sun Nov 30 11:38:09 2008
> New Revision: 721877
>
> URL: http://svn.apache.org/viewvc?rev=721877&view=rev
> Log:
> o transfer notes about compatibility to a confluence document, we'll
> eventually use idiom to generate the new site. no more
>
Dear devs,
I would like confirmation that what I am doing is wrong, stupid and foolish
and potentially should be detected and prevented by mvn.
I have a corp pom that binds checkstyle and pmd to validate phase. Both
these plugins have an extra config jar artifact added as a plugin dependency
tha
Hervé,
Is there much left more your working on in Modello? If not do you
think we could cut the 1.0 for modello as that's what I would like to
start using for trunk. Then create a branch for bug fixes so that
during the alpha releases of Maven 3.x the underlying sub-systems can
remain as
Oleg,
Shane and I were chatting and I think the maven-mercury module in
trunk can actually go into Mercury itself, there is nothing trunk
specific in there and almost makes you trunk free.
We're trying to figure out what to do with the project builder which
only relies on maven-shared-mod
Brett Porter wrote:
Maybe I'm missing something but that issue seems to indicate a bug
regardless since the configuration is completely lost instead of
duplicated (assuming your latter example is complete).
Clarifying whether the behavior I observed with the plugin configuration
is a bug or
of course since the tld naming rules have been relaxed so that
anything goes, is this really an issue (other than nobody, yet,
registering as the registrar for the log4j tld)
;-)
Sent from my iPod
On 30 Nov 2008, at 02:24, "Paul Benedict" <[EMAIL PROTECTED]> wrote:
But with a configuratio
11 matches
Mail list logo
