on is
all that is needed. Done.
> support project inheritence with flat project layout
>
>
> Key: MNG-359
> URL: http://jira.codehaus.org/browse/MNG-359
> Project: Maven 2
> Type:
accesible from eclipse;
so I normally create an eclipse project per maven project. This works really
well for maven1.
How would I be able to edit all my maven2 project in Eclipse with the 'no flat
layout' restriction?
> support project inheritence with flat p
cture their
maven projects for easy sharing with their team members and quick
eclipse setup for new developers.
> support project inheritence with flat project layout
>
>
> Key: MNG-359
> URL: http://jira.cod
modules as follows:
../m2-test-app
../m2-test-web
../m2-test-plugin
What is the reasoning behind disallowing "../"? I'm sure that you had good
reasons for adding this limitation.
> support project inherite
ually wanted can be given.
See: http://www.mail-archive.com/users%40maven.apache.org/msg19133.html
> support project inheritence with flat project layout
>
>
> Key: MNG-359
> URL: http://jira.codehaus.org/browse/MN
structure is the
element which requires that the modules be in subdirectories.
> support project inheritence with flat project layout
>
>
> Key: MNG-359
> URL: http://jira.codehaus.org/browse/MNG-359
>
support project inheritence with flat project layout
Key: MNG-359
URL: http://jira.codehaus.org/browse/MNG-359
Project: m2
Type: Bug
Components: maven-core
Versions: 2.0-alpha-1
Reporter: Ryan
What do you think? This is actually one of the areas
that I have a keen interest in, but it looks like several other people do as
well.
-- Steve
-Original Message-
From: Nathan Coast
To: Maven Dev
Sent: 9/28/2003 7:42 PM
Subject: project inheritence
Hi,
I'd just like to clarify
On Mon, 2003-09-29 at 00:01, Nathan Coast wrote:
> > maven.xml already gets run as well. My latest work not only clears up
> > inheritence for project.xml but also loads parent project.properties I
> > think. I haven't tested that far yet as I am clearing up other issues with
> > it. This needs mor
-Original Message-
> From: Nathan Coast [mailto:[EMAIL PROTECTED]
> Sent: Monday, 29 September 2003 2:02 PM
> To: Maven Developers List
> Subject: Re: project inheritence
>
>
> > maven.xml already gets run as well. My latest work not only
> clears up
> > inh
maven.xml already gets run as well. My latest work not only clears up
inheritence for project.xml but also loads parent project.properties I
think. I haven't tested that far yet as I am clearing up other issues with
it. This needs more discussion as dIon and I disagree on what exactly should
be inh
o: Maven Dev
> Subject: project inheritence
>
>
> Hi,
>
> I'd just like to clarify what the current state of play is
> with project
> inheritence and where the eventual goal is.
>
> I think there are 3 artifacts which could sensibly be inherited.
>
Hi,
I'd just like to clarify what the current state of play is with project
inheritence and where the eventual goal is.
I think there are 3 artifacts which could sensibly be inherited.
project.xml / POM
project.properties
maven.xml
I remember reading in a post from Jason that eventuall
13 matches
Mail list logo
