[
http://jira.codehaus.org/browse/MNG-4599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=214531#action_214531
]
Ondrej Zizka commented on MNG-4599:
-----------------------------------
I know this is a common feature request, which Maven devs ignore.
I understand that this is Sonatype's business decision, aimed to force people
to Mavenize everything and to strenghten the need for a good local repository.
But from the usability POV, it's a bad decision.
The suggested solution is not appropriate, because what bothers me (and 80 % of
Maven users) is the need to create the artifact and to list each of them in POM.
* This requires another pre-build step every time I perform the build -
creating a maven artifact out of the .jar created by some other tool.
* Since the dependency must be ready BEFORE calling Maven, this can't be done
in POM.
* If I have 200 .jars, I need to create 200 artifacts for each build WHICH
WILL NEVER BE USED AGAIN. More than that, I have to list 200 dependencies in
POM. This is ridiculous, totally useless, and the only reason is this bad
"deliberate design decision".
It's time to change the design desicion. There's no technical drawback. It will
be backward compatible, so it won't harm anything. And I don't believe people
would start misusing it as it's not easier than mavenizing some persistent
artifact. It would only serve for cases when you need to use too many .jars
which are not in the repository (for whatever reason).
I am filing this feature request just to assure that the need of most Maven
users is really disregarded and disdained, before we start to patch Maven four
ourselves.
> 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
