[ http://jira.codehaus.org/browse/MNG-4599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=216262#action_216262 ]
Ondrej Zizka edited comment on MNG-4599 at 3/31/10 5:16 PM: ------------------------------------------------------------ The point is that I must have been meeting and working with a completely different Maven community than the developers of Maven. Everyone I discussed this and other ignored deature requests with considers these typical "640 kb should be enough for anyone" stances as detrimental, and I can only agree. Maven has a strong point in the repos and a slight standardization, but then it has 1001 usability flaws, which are being claimed as systematic way of doing things and marked Won'tFix. All right then. But I am getting off-topic... was (Author: pekarna): The point is that I must have been meeting and working with a completely different Maven community than the developers of Maven. Everyone I discussed this with considers these typical "640 kb should be enough for anyone" stances as detrimental, and I can only agree. Maven has a strong point in the repos and a slight standardization, but then it has 1001 usability flaws, which are being claimed as systematic way of doing things. All right then. But I am getting off-topic... > 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