[
http://jira.codehaus.org/browse/MNG-3989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163292#action_163292
]
Greg Wilkins commented on MNG-3989:
-----------------------------------
In many enterprises, getting permission to run a repository is difficult
(specially when you are trying to move to maven by stealth and converting
projects without high level permission as a proof of principal).
More over, I really like the ideal of maven for repeatable builds. I trust
that repo.maven.org is going to exist and be well managed into the foreseeable
future, but one can't expect enterprises to keep local repositories running
and/or consistent, specially in todays climate where said enterprises like to
lay-off technical staff using a megaphone!
So a local repository might give me a repeatable build for a week or a month,
but 1,2 or 5 years would be a harder to achieve.
> 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
>
> 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
