[
http://jira.codehaus.org/browse/MNG-4599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=214533#action_214533
]
Jason van Zyl commented on MNG-4599:
------------------------------------
It's not a Sonatype decision, it's a Maven decision. For example Brett answered
you and he doesn't work for Sonatype. So I'm not sure where you get that notion
from. It's a goal of the Maven project as a whole to have people Mavenize their
projects.
Listing the dependencies in the POM is the point of Maven. Having correct
dependency information is one of the core tenets of Maven. In Maven 2.x for 5
years we allowed system scoped dependencies which allowed dependencies to be
pulled from the file system. In Maven 3.x we eliminated that.
Allowing random artifacts to be pulled from the system is not something that
will ever be provided for in Maven. It may, however, be something we
accommodate in Polyglot Maven to allow people to make a transition to a proper
repository structure.
There is a huge technical drawback to pulling in 200 JARs that have no
transitive dependency information, and this is not something most Maven users
want.
Write a proposal in the Maven User space and you can see if other users agree
with you. It will get lost here.
> 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
