> -----Original Message----- > From: Jeff Wang [mailto:[EMAIL PROTECTED] > Sent: Friday, March 14, 2008 9:37 PM > To: [email protected] > Subject: Dependency generation > > I'm part of this messy project that's been around for about 10 years. > We've got Ant, and have checked in all of our libraries in > our SVN. I just want to start with dependency generation > first, but it seems like I need to setup a Maven 2 > repository? Or am I just reading the tutorials wrong?
The missing link is that you need a repository. It can be dirt simple like a shared network directory, as long as it observes a consistent layout scheme. You don't have to use the Maven 2 scheme. But it's simple, most of the examples follow that scheme, and a number of useful tools anticipate it in their defaults, like Archiva. It's nothing but organisation/module/revision/artifact.jar. For your internal repository I suggest reserving the right to be very creative with organisation to uniquely identify modules, don't just use com/mycompany and stick everything under that. You can look at http://repo1.maven.org/maven2/ and see how different projects have approached it. Good luck. ----------------------------------------- ==================================================== This message contains PRIVILEGED and CONFIDENTIAL information that is intended only for use by the named recipient. If you are not the named recipient, any disclosure, dissemination, or action based on the contents of this message is prohibited. In such case please notify us and destroy and delete all copies of this transmission. Thank you. ====================================================
