You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by fa...@mpsa.com on 2005/05/26 17:13:54 UTC
Réf. : RE: [OT]Re: Réf. : Re: [m2] Multiproject with flat layout
Jeff,
here is part of my "project.properties" file that works for Dashboard :
# --------- MULTIPROJECT ---------
maven.multiproject.basedir=${basedir}/..
maven.multiproject.includes=myProject1/project.xml,myProject2/project.xml
maven.multiproject.site.goals=site,dashboard:report-single
# --------- DASHBOARD ---------
maven.dashboard.runreactor = false
maven.dashboard.basedir=${basedir}/..
maven.dashboard.includes=*/project.xml
maven.dashboard.excludes=**/target/**/project.xml
maven.dashboard.aggregators =csfiles,cswarnings,cserrors,\
junittests,junitpassrate,junitfailures,juniterrors,\
jcoverageloc,jcoveragelipc,\
scmchangedfiles,scmchangedcommit
HTH,
Regards,
Fabrice
Jeff Jensen
<jeffjensen@nosp
am.visi.com> Pour
'Maven Users List'
26/05/2005 15:10 <us...@maven.apache.org>
cc
Veuillez Objet
répondre à RE: [OT]Re: Réf. : Re: [m2]
Maven Users List Multiproject with flat layout
<users@maven.apa
che.org>
Same environment here.
I setup a Maven project for each WSAD project. It was the best way I could
determine to generate all the reports. Perhaps there is a better way??
But
this works well and I do not know how to improve on it at this point! :-)
Any suggestions/comments welcome!
So running maven site:deploy for each is easy and works well.
I originally tried one Maven project on the main WSAD project that included
all dependent projects, but that became cumbersome and painful. Too much
hacking in the maven.xml file to get additional source paths on each goal.
A lot of slow iterative change/test! (allowing the POM to have multiple
source dirs is the solution here!)
So when I considered it like managing each WSAD project in source control,
it was a natural fit to have each project have its own Maven project.
Perhaps this will help you too.
My next step is to setup multiproject to have the dashboard report.
I tried simple attempts twice and failed both times, and now need to make
time to look into it. Multiproject would run successfully, but only
generated the Project Info, not the Project Reports. It never ran those
parts of the subprojects, and I am currently clueless...
-----Original Message-----
From: bryan ( admin@revoltingdigits.com) [mailto:revoltingdigits@gmail.com]
Sent: Thursday, May 26, 2005 3:57 AM
To: Maven Users List
Subject: [OT]Re: Réf. : Re: [m2] Multiproject with flat layout
Hi Fabrice,
I'm using maven 1.0.2 with WSAD as well. How do you go about generating
reports for all the dependant projects ?
I would like to generate javadoc/junit reports etc for all the modules not
just the main maven project.
--b
On 5/26/05, fabrice.belingard@mpsa.com <fa...@mpsa.com> wrote:
>
>
>
>
>
> 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
> <brett.porter@gm
> ail.com <http://ail.com>> Pour
> Maven Users List
> 26/05/2005 02:07 <us...@maven.apache.org>, admin@revoltingdigits.com
> cc Veuillez répondre à Objet Maven Users List Re: [m2] Multiproject
> with flat <users@maven.apa layout che.org <http://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 ( admin@revoltingdigits.com)
> <re...@gmail.com> 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, fabrice.belingard@mpsa.com <fa...@mpsa.com>
> 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: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org