[
http://jira.codehaus.org/browse/MNG-4599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=214882#action_214882
]
Brett Porter commented on MNG-4599:
-----------------------------------
Ondrej, rather than posting your solution to a particular problem, you'll
probably get a better response by posting your scenario to
us...@maven.apache.org and seeing how others deal with it. With more details I
could think of ways of addressing that use case without any changes to Maven (I
can only see that you want to replace dependencies with different versions for
integration purposes, but don't quite understand the process beyond that).
We had jarPath in Maven 1 and it caused problems in a number of regards, which
is why it was removed. It certainly isn't a good idea for reproducibility. It
would too easily be misused.
> Provide a way to create "virtual artifacts" out of plain .jar file.
> -------------------------------------------------------------------
>
> Key: MNG-4599
> URL: http://jira.codehaus.org/browse/MNG-4599
> Project: Maven 2 & 3
> Issue Type: Improvement
> Reporter: Ondrej Zizka
> Assignee: Brett Porter
>
> During the time I have been using Maven, I have come across numerous cases
> when I desperately needed to turn a simple .jar file into a dependency.
> Currently, this involves installing it properly to the repository first, and
> only then it can be used.
> I suggest to introduce some construct which would take a list of .jar files
> and turn them into dependencies in the sense they would be added to the
> classpaths, could be used for WAR overlays, etc. Of course, they would not
> have any transitional dependencies.
> <dependencyManagement>
> <jarPaths>
> <jarPath>../../releases/50GAAS/jboss-as/common/lib</jarPath>
> </jarPaths>
> ...
> </dependencyManagement>
> This would greately improve Maven's openness to non-mavenized world, and
> usability in cases when you really get a plain .jar/.war/.ear/... before
> every build cycle.
--
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
