Lachlan, You also need to quite simply understand that Maven is not Ant (!). While there are some similarities in the two (they both build Java code), there are far more dissimilarities.
Maven has certain beliefs based on best practices about how builds should be organized and performed. One of those best practices is "jars shouldn't go into SCM". So, you won't find a lot of support for this "feature" in Maven. In general, Maven is less flexible than Ant. For example, Maven expects a certain project structure for your code. While you can adjust (through configuration) the location of source code etc, it makes things a little more complex and increases the size of your pom, plus you may run into issues with certain plugins etc. If you are used to and require a large amount of flexibility in your builds, then please stick with Ant. Those of us who have migrated to Maven generally believe we are better off as a result, but there is a transition period and the mindset is a bit different. I'm also curious -- why are you moving to Maven for this particular project? Was a mandate handed down from someone above you, or did a customer ask for it, or was it simply personal interest? You mention that you have no ability to create a shared repo etc, so I wonder where all this is coming from... Wayne --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
