[
http://jira.codehaus.org/browse/MNG-3989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated MNG-3989:
------------------------------
Attachment: MNG-3989.zip
hey Greg - this structure seems closest to what you are looking for without
making modifications. IS it on the right track for what you were looking for?
You can do a bit more by using the dependency plugin or install:install-file
(eg, generate POMs), but you still tend to end up with a separate module and
declarations can be quite lengthy.
Beyond that it is getting towards writing a custom plugin to copy files
directly into the local repository.
In any of these cases, it'll result in a transitive closure that won't be
resolvable if the project is deployed into the repository without copying the
repository module around (which is probably ok in situations like the weblogic
one mentioned).
I'd still be reluctant to build this right into Maven given the number of
alternatives available, though.
> Simple handling of external jars
> --------------------------------
>
> Key: MNG-3989
> URL: http://jira.codehaus.org/browse/MNG-3989
> Project: Maven 2
> Issue Type: New Feature
> Affects Versions: 2.0.9
> Reporter: Greg Wilkins
> Attachments: MNG-3989.zip
>
>
> For whatever reason, there will always be jars that don't exist in a maven
> repository.
> There are numerous techniques for these - installing them in your local repo
> (either manually or with
> some bootstrap.sh script or special profile activation). Checking in the
> jars into a local maven repository that is checked into svn
> and then point to it from your settings.xml and/or top level pom (with aid of
> an env variable).
> But all these methods lack a very important features. You can just do: "svn
> co http:/myproj.com/foo; cd foo; mvn"
> If the jars change, you can't just do "svn up; mvn", you have to re-run
> whatever script/profile installed the repo.
> It's all rather a PITA.
> What I want, is some way to have a module of a project that contains some
> non-maven jars that when I
> do a "mvn install" in that project, install those jars in my local repository
> for use by my other modules. If the
> jars are not updated, then nothing is done.
> With something like this, projects that have external dependencies could
> describe them to maven and
> make them available for use, without manual steps and special scripts.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
