Hello, Thanks for your feedback.
I really don't think I'm trying to make a simple problem into a difficult one, so perhaps I can outline my thoughts again? Consider two separate projects: common and plugin. In Eclipse, you'd create two projects and add common to the build path of plugin. If I recall correctly, we can build these projects as a pair and run plugin - any changes to the common project are reflected in plugin as it's run. If I have to maven projects, common and plugin, where plugin declares the dependency on common, the compilation process becomes a little more tedious. If a change is made to common, make install (compile a jar and place into the repository) must be run before a make install/jar/etc. can be run in the plugin project. I guess this isn't an awful price to pay if most of the work is being performed in Eclipse and running maven is the last thing to do. It would be nice if maven had a mode where by it checked (perhaps marked) dependencies for changes before possibly recompiling a new jar and insertinog into the repository. Obviously, if a build directory exists and no source files have been changed (so no new classes are generated), it need do nothing. However if changes were detected then it could rebuild a new jar and place into the repository. John > -----Original Message----- > From: Graham Leggett [mailto:[EMAIL PROTECTED] > Sent: 07 November 2008 10:20 > To: Maven Users List > Subject: Re: Multiple project dependencies > > [EMAIL PROTECTED] wrote: > > > My question surrounds dependencies, and while I understand how to > > declare a dependency, what I want to know is how I make maven > > recompile dependencies. > > > > So if A depends on B, and I run 'mvn jar' in project B, how > can I make > > it recompile (and I guess, run 'mvn install') in A? My scenerio is > > that I will be making changes to both A and B, but both are > separate > > projects and I don't want to have to run 'mvn install' in A before > > doing anything with project B. Obviously, if A depends on > B, A will > > not compile if B has been modified in some way given A > fetches A.jar from the repository. > > > > Neither A or B share a common parent. In fact, they could > easily have > > different parents. > > Having read and reread this, my gut feeling is that you're > potentially trying to make a simple problem into a complicated one. > > If A depends on B, and you want to B to trigger stuff > happening in A, that sounds like a classic circular > dependency problem, which is broken regardless of what build > strategy you use. > > Can you describe in more detail what problem you are trying solve? > > Regards, > Graham > -- > _______________________________________________ This e-mail may contain information that is confidential, privileged or otherwise protected from disclosure. If you are not an intended recipient of this e-mail, do not duplicate or redistribute it by any means. Please delete it and any attachments and notify the sender that you have received it in error. Unless specifically indicated, this e-mail is not an offer to buy or sell or a solicitation to buy or sell any securities, investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Barclays. Any views or opinions presented are solely those of the author and do not necessarily represent those of Barclays. This e-mail is subject to terms available at the following link: www.barcap.com/emaildisclaimer. By messaging with Barclays you consent to the foregoing. Barclays Capital is the investment banking division of Barclays Bank PLC, a company registered in England (number 1026167) with its registered office at 1 Churchill Place, London, E14 5HP. This email may relate to or be sent from other members of the Barclays Group. _______________________________________________ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
