On Tue, 2005-05-17 at 07:19 +1000, Brett Porter wrote:
> Can you explain your use case, and would adding the 1 - 3 lines in each
> pom be prohibitive?
It would not be prohibitive, but imagine I have dozens of projects whose
default goal is the same (defined in a custom plugin, for instance). It
wo
Me too...
On Mon, 2005-05-16 at 09:15 -0700, dan tran wrote:
> In M1, I heavily use default goal inheritant.This way I dont have to add an
> extra maven.xml to all sub probject.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For a
Can you explain your use case, and would adding the 1 - 3 lines in each
pom be prohibitive?
- Brett
dan tran wrote:
>In M1, I heavily use default goal inheritant.This way I dont have to add an
>extra maven.xml to all sub probject.
>
>-D
>
>On 5/16/05, Felipe Leme <[EMAIL PROTECTED]> wrote:
>
>
On Mon, 2005-05-16 at 20:17 +1000, Brett Porter wrote:
> Hi,
>
> I'd like to propose the following POM additions, rounding out what's
> left from the M1 JIRA, for inclusion in both m1 and m2.
>
> inside . Not inherited. Specifies the goal to use
> if none is speci
In M1, I heavily use default goal inheritant.This way I dont have to add an
extra maven.xml to all sub probject.
-D
On 5/16/05, Felipe Leme <[EMAIL PROTECTED]> wrote:
> On Mon, 2005-05-16 at 20:17 +1000, Brett Porter wrote:
>
> > inside . Not inherited. Specifies the goal to use
> > if none is
On Mon, 2005-05-16 at 20:17 +1000, Brett Porter wrote:
> inside . Not inherited. Specifies the goal to use
> if none is specified.
Why not inherited?
-- Felipe
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional comma
Hi,
I'd like to propose the following POM additions, rounding out what's
left from the M1 JIRA, for inclusion in both m1 and m2.
inside . Not inherited. Specifies the goal to use
if none is specified.
in alongside .
Also, which allows arbitrary settings, like
, etc. We can standa
