[
http://jira.codehaus.org/browse/MNG-4599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=215229#action_215229
]
Paul Benedict commented on MNG-4599:
------------------------------------
Ondrej, I think you are missing the point. Maven is a system thus there is a
systematic way of doing things. You are proposing alternatives, yes, but to the
detriment of the benefits which the system is intended to bring. Your opinions
are not necessarily wrong; just not how things should be done with Maven.
> 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
