Is exactly what I'm doing. I only build the project I'm working on. The dependencies are pulled from my local repository. Run mvn clean package install from your jars. Only if you change any of them, you execute mvn package install. I'm not sure if you understand me.
2010/1/24 Josh Stone <[email protected]> > Thanks for the response. Allow me to try and explain again: > > Since our stack is so large and consists of many projects, developers don't > build the entire stack from source, they only build the specific projects > that they work on. Dependencies on other projects in our stack should be > resolved from jars that are built by our continuous integration box and > deployed to the maven repository. So if I'm actively developing only two > projects I'd only want to build those two projects from source. All the > other project dependencies I'd want to be pulled in from the maven > repository as jars. I'm not sure how to manage this... > > Josh > > On Sun, Jan 24, 2010 at 2:03 PM, Wendy Smoak <[email protected]> wrote: > > > On Sun, Jan 24, 2010 at 2:55 PM, Josh Stone <[email protected]> > wrote: > > > > > Since any given project could be built locally from source or from > jars, > > do > > > I need two poms for each project, one to serve as a "build" pom and one > > to > > > reference jars? > > > > No, you don't need two poms. What do you mean by building from source > > or from jars? The source jars in the Maven repo are generally for > > IDEs to use when debugging. The pom that builds the project will > > usually have <dependencies> on other jars. > > > > > Should I store the pom(s) in SCM along with having them in the maven > > > repository? > > > > Yes, the pom belongs in scm along with the project source code. This > > is the same pom that gets deployed to the Maven repo when you do a > > release. > > > > Ideally the conversion will go bottom up, so that you convert your > > lower level utility jars, release them, then move up to the projects > > that depend on them. To bootstrap you may want to deploy some > > existing jars to the your internal Maven repo for projects to use. > > For those you'll need to construct a pom or let Maven generate a > > minimal one. > > > > I'm not sure I understood the question, so ask again if that's not > > what you were looking for. > > > > -- > > Wendy > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > -- "Everything should be made as simple as possible, but not simpler" Albert Einstein
