Brett,
IMHO, the "../" path in <modules> would really be helpful. I imagine that
it does not add a big implementation problem, and it would solve the issue
of the flat layout of Eclipse.
My problem is that the company I'm working for only uses WSAD. I'm
currently working on spreading Maven all over hundreds of Java projects,
and I want it to be as simple as possible. And having the root POM outside
of the workspace is not an acceptable solution: people will want to edit it
in WSAD, they will need to have it in CVS and handled like any other source
file, ...etc.
I agree that the issue for Eclipse project organization is interesting. But
before anything gets changed in WSAD, it will take a lot of time. For the
time being, Eclipse forces us to have 1 project = 1 CVS module, and
therefore, the root POM must be in a separate project.
If m2 can't handle flat layout for multiprojects, I won't be able to spread
it over the hundreds of teams, and that'd be sad because it looks great...
:o|
We see that Eclipse is not flexible enough. Maven should prove more
flexiblility than Eclipse and not force a special layout for multiprojects
(m1 used to be that flexible!).
I do hope something can be done this way... or I will need to find another
company to use m2 ;o)
Thanks & best regards,
Fabrice
Brett Porter
<[EMAIL PROTECTED]
ail.com> Pour
Maven Users List
26/05/2005 02:07 <users@maven.apache.org>,
[EMAIL PROTECTED]
cc
Veuillez
répondre à Objet
Maven Users List Re: [m2] Multiproject with flat
<[EMAIL PROTECTED] layout
che.org>
I don't believe we are doing anything special to support this in the
first release. It is entirely possible to use this structure as is.
To be honest, reading that bug again, I don't know what is being asked
for. The only thing in Maven that could be affected is <modules> for
which we haven't allowed "../" as a directory.
The only downside of this I can see is that you don't get to have the
root pom.xml file in your workspace.
Maybe one of the MevenIDE folks comment on this?
Incidentally, there is an open issue at Eclipse I am tracking that
they support a different type of project layout. I'd encourage
everyone here that has this problem to go and vote for it.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=35973
- Brett
On 5/26/05, bryan ( [EMAIL PROTECTED])
<[EMAIL PROTECTED]> wrote:
> hmmm ... now i understand why my project isn't working. This is
particularly
> a pain if you are working with IBM WAS /
> WSAD ... it forces you to adopt this stucture when working on a EAR
> deployment ... and just about anything else.
>
> Eclipse is ( despite what some may say ) probably the most popular java
IDE
> out there, especially for open source
> projects. Good interoperability with maven ( allready a good mavenide
plugin
> ) would be a dream situation.
>
> --
>
> On 5/25/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]>
wrote:
> >
> >
> >
> >
> >
> > Hi guys,
> >
> > the issue of multiproject handling with a flat layout was tackled some
> > weeks ago on this mailing list, and there's an issue on JIRA
> > (http://jira.codehaus.org/browse/MNG-359) concerning this point, but it
> > has
> > not been resolved nor assigned.
> >
> > I just wanted to know: is this issue left apart intentionally, or will
it
> > be done for m2 august release?
> >
> > Best regards,
> > Fabrice.
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]