maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason van Zyl (JIRA)" <>
Subject [jira] Commented: (MNG-3989) Simple handling of external jars
Date Fri, 30 Jan 2009 02:00:19 GMT


Jason van Zyl commented on MNG-3989:

In what case can't you make it easier for your users by putting it in a repository? What's
the case that made you ask for this?

> Simple handling of external jars
> --------------------------------
>                 Key: MNG-3989
>                 URL:
>             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 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
> But all these methods lack a very important features.  You can just do: "svn co http:/;
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:
For more information on JIRA, see:


View raw message