Hi Oscar and Randy
I would suggest that
+) you move your external libraries to a Maven repository
+) you might tweak the dependency section to use libraries with non-conforming naming convention (check out the docs). But consider to rename your external dependencies to have a version number otherwise you shoot yourself in the long run
+) it is always possible to reference multiple remote repository using "maven.repo.remote" in your global build.properties (check out the docs). So you can set up a company wide remote repo. If the library is generally useful you can request an upload to IBIBLIO and its mirrors
Cheers,
Siegfried Goeschl
Oscar Picasso wrote:
I have a related question.
Is it possible to upload a resource to ibiblio even if we are not related to its development?
For example I use 'some-userful.jar' in an open source project.
The resource 'some-userful.jar' itself is open source but I am not its author.
I would find more convenient to have this jar in a central repository, like ibiblio.
Oscar
--- Randolph Kahle <[EMAIL PROTECTED]> wrote:
I am converting a project to Maven. This project has dependencies on many external libraries (JAR files).
Which is the preferred way to handle these:
* Create a /src/lib area for run-time dependencies
* Move the JAR files into the local repository
Examples of dependencies include Spring, aspectjrt.jar, imap.jar, etc.
I do not that some (most?) of these JAR files does not follow the naming convention that allows for automatic version management.
Regards,
Randy
-- Randolph S. Kahle, 6161 N Canon del Pajaro, Tucson, AZ 85750 Phone: +1 520 577 7680 [EMAIL PROTECTED] http://www.variantia.net Variantia
ATTACHMENT part 2 application/pkcs7-signature name=smime.p7s
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
