I'm brand new to Maven. How can it help me manage the mess of JARs and the corresponding source and Javadocs that generally aren't packaged within those JARs?
Right now my projects are a mess of inconsistency in terms of storing source and Javadocs for external libraries. Some JARs have this within them, other include it separately. I understand that Maven has a standard directory structure, but I'm confused as to how to take advantage of this with external libraries (I know how I can use it to make my own code easier to manage). Is the only way for external library mgmt to be easy with Maven if those libraries "use" Maven in their development and already store it in a standard format (then you simply connect with mvn to their repository and grab everything in a nice, clean format). Or is there a way even if they've not used Maven? I realize I could download their source code and treat it as a project in my own repository, but is that the right way of doing it...or does Maven or your personal best practices suggest anything else I could consider? Thanks. -- View this message in context: http://www.nabble.com/Managing-external-libraries-tf3122915s177.html#a8653161 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
