[ 
http://jira.codehaus.org/browse/MNG-4599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=216301#action_216301
 ] 

Ralph Goers commented on MNG-4599:
----------------------------------

I'm going to point you back to Brett's response. Instead of insisting on a 
solution, go to the mailing list with your problem and ask there for 
recommendations on how to resolve it. After you've expended a bit of effort 
with that and if no one proposes a workable solution then you should open a 
Jira describing the problem, some of the alternatives that were suggested and 
why they don't work and then propose something. As it stands, I really don't 
understand what the problem you are trying to solve is because all you have 
said so far is "I have come across numerous cases when I desperately needed to 
turn a simple .jar file into a dependency" without explanation as to why that 
is necessary or even what you were trying to do.

> 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

        

Reply via email to