In case I want to make changes to the dependency. This won't be the general workflow, but if I'm working on artifact A, which depends on artifact B, and I notice a change needs to be made to B, rather than have to manually checkout B and make changes there, I want to make it more seamless by providing an automatic way of getting the source that was used to build B.
Then of course I can make changes, commit them, and install/deploy a new version of B. Phillip On Fri, Oct 1, 2010 at 1:36 AM, Antonio Petrelli <[email protected] > wrote: > 2010/9/30 Phillip Hellewell <[email protected]>: > > The biggest question for me is in how these all fit together, e.g., is it > a > > normal mechanism to want to fetch an artifact into the local repository, > > copying and extracting it to a subfolder, and then (if it includes > source) > > compile it when compiling the "parent" artifact? > > Why do you want to recompile an already compiled dependency? > > Antonio > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
