On Sun, Oct 30, 2011 at 4:50 AM, Ron Wheeler <[email protected]> wrote: > If you want to continue the conversation, you should maybe tell everyone a > bit about what you are trying to build and why your application structure > has to be so different from everyone else building the same type of > application. > That will get you much better advice since there are probably dozens of > people in the forum who have built applications to run in exactly the same > environment. > If you can tell them where you are deviating from the standard structure, > they may be able to give you some good advice. > If you are building a normal web application that runs in one of the normal > environments, Maven will work very simply as is.
And I will add to Ron's advice - have a read of the free books available at http://maven.apache.org/articles.html > According to my knowledge, there is no proper way to override the scope of A3 > without specifying its version nor losing granularity. Also as Ron says you want to have the correct scope defined the first time so that you only need to override it once for you "library" artifact. It is definitely possible to only specify group and artifact with the new scope to change what was defined in dependencyManagement. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
