[
http://jira.codehaus.org/browse/MNG-3989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163310#action_163310
]
Greg Wilkins commented on MNG-3989:
-----------------------------------
Jason,
it's not just for pilot projects. Let's say that I have a huge project with
many modules with many dependencies, most of which are available in
repo.maven.org
But I have just a few jars that are not available in repo.maven.org. This may
be because they just have not been published, or it may be that they are
proprietary binary only jars with limited availability, or who knows the reason.
I really do not want to have to setup a local repository just for these few
jars.
If there is the ability to have a few jars checked into SCM, that is far
simpler and more reliable than creating and securing a private repository. It
also means the source can be delivered across organizational boundaries without
requiring a repository to be setup.
Now I hate jars checked into SCM, but for better or for worse, it is a common
practise.
However, I hate seeing things like "../../repo" in all poms even more!
I've seen maven dropped by a large investment bank because of issues with a
local repository.
I've frequently faced opposition to introducing maven simply because svn co;
cd; mvn is not
sufficient to build.
I do recognize that a tool such as I'm suggesting could be misued really really
badly, but then so
can many things in every project. I do think such a tools would help the
adoption of maven by
many organizations and/or projects.
cheers
> 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
