Not too surprised really the thing that really sold me on maven was the testing (JUnit and checkstyle...) and site generation.
-----Original Message----- From: swebb [mailto:[EMAIL PROTECTED] Sent: May 25, 2007 9:22 AM To: [email protected] Subject: [m2eclipse-user] RE: RE: Multiproject auto selection of local source or repository project Hi Phil, Yes we were looking to change to Maven2 however we have some issues with our build producing multiple jars from a single project and things like that. In the last few days I've written an Ant script to do what we want (build all projects and there deps, javadoc and so on). It seems to work fairly well and adding a new project just required 3 line changes in a property file so I think we will stick with it as it seems less hassle that carrying on with Maven. It also makes IDE support for our project a bit easier. Cheers Steve Phill Moran wrote: > > The Maven 2 POM can do this and Eclipse can be updated (to some > degree) to reflect Maven POM changes (mvn eclipse:eclipse in the project directory). > I have > a similar situation where I kick the whole thing off with shell script > but this is not strictly necessary since you can do this through the > eclipse-subversion plug-in. The main advantage is that for those that > do not want all source local they can just grab the JAR files (or > source jar for that matter). > I noticed in your next response you use maven 1 take a look at some of > the changes in Maven 2 and think about making this the central project > descriptor/builder. In case you have not figured this out yet you can > also run Maven commands from the eclipse external tools > > -----Original Message----- > From: swebb [mailto:[EMAIL PROTECTED] > Sent: May 23, 2007 10:45 AM > To: [email protected] > Subject: [m2eclipse-user] RE: Multiproject auto selection of local > source or repository project > > > Yes but the problem is that some engineers might like to checkout all > projects and source onto their local drive from svn and some might > just want the one they are working on or a combination of the two > methods. At the moment it strikes me that I can't have a standard > eclipse setup or maven one for that matter that will automatically > determine whats available and work with it. So everyone ends up having > to change the eclipse classpaths when they check things out and then > remember not to commit those changes sometime later. > > Also there is the little matter of adding to add to both the eclipse > class path and the maven pom when a new dependency is introduced. > Ideally I'd like to add it to the POM and eclipse would pic it up > automatically and build using it (local if available as already > mentioned). > > Personally I have everything checked out local because I like to be > able to debug the full system and also search on the full source. > > > > Phill Moran wrote: >> >> Is this not standard Maven? Where you setup a corporate repository >> and put the Jars from Project A, B and C in it. That way those that >> checkout only one of the projects will only download the Jars for the >> others and link them? >> >> Phill >> >> -----Original Message----- >> From: swebb [mailto:[EMAIL PROTECTED] >> Sent: May 23, 2007 8:54 AM >> To: [email protected] >> Subject: [m2eclipse-user] Multiproject auto selection of local source >> or repository project >> >> >> Hi, >> >> If I say have project A that depends on B & C is there anyway using >> the combination of Eclipse/Maven2 to set up Eclipse so that if say >> project A & B is local it will automatically build A against B's >> source rather than fetch its jar from the Repro. What I mean by >> automattically is that we don't have to touch anything once the POM >> and eclipse settings are set. >> >> I ask about this because some people like to check all projects out >> and other just the project they are working on and each has to mess >> around with the eclipse settings each time. It would be good if they >> could just check what they want out of svn and eclipse would >> automatically build against local project sources if they were there >> otherwise use the maven repro ! >> >> Any thoughts, ideas ? >> >> Thanks >> >> Steve >> -- >> View this message in context: >> http://www.nabble.com/Multiproject-auto-selection-of-local-source-or- >> r >> epository- >> project-tf3803864.html#a10763329 >> Sent from the Maven Eclipse - User mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> To unsubscribe from this list please visit: >> >> http://xircles.codehaus.org/manage_email >> >> >> --------------------------------------------------------------------- >> To unsubscribe from this list please visit: >> >> http://xircles.codehaus.org/manage_email >> >> >> > > -- > View this message in context: > http://www.nabble.com/Multiproject-auto-selection-of-local-source-or-r > epository- > project-tf3803864.html#a10765420 > Sent from the Maven Eclipse - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email > > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email > > > -- View this message in context: http://www.nabble.com/Multiproject-auto-selection-of-local-source-or-repository- project-tf3803864.html#a10802905 Sent from the Maven Eclipse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
