|
[
Permalink
| « Hide
]
Archimedes Trajano added a comment - 14/May/04 05:19 AM
Patch to ArtifactListBuilder to implement property driven paths
Updated project-descriptor.xml file containing text.
Having trouble with CVS and cannot do a patch Updated patch, delete the old one.
Better patch, puts in the path separator automatically instead of having to prefix the project paths with a "/"
Patch for eclipse plugin
How is maven.jar.override undocumented?
According to http://maven.apache.org/reference/user-guide.html#Overriding_Stated_Dependencies the <id> you mention is artifactId, not id. But where would you specify the groupId? One of the reasons for the patch was to allow
<groupId>struts</groupId> <groupId>myclosedsourcecompany</groupId> Also its not documented in the list of properties here
http://maven.apache.org/reference/user-guide.html#Behavioural_Properties I think most people if they find out about this list would go there to find out some of the core properties of maven and may not look further down. That document is getting long already as well anyway, perhaps if it was broken down as well for the next release (though the long version of the page is still provided for printing purposes). we need to use a proper id for jar overrides and document it in 1.1.
I'd suggest maven.jar.groupId.artifactId (but also look for just artifactId to be backwards compatible). eg Not sure about your example.
Since you have maven.jar.org.apache.maven.maven should it just be maven.jar.maven.maven ? Remember to allow other dependency types
maven.war.[] maven.ejb.[] Archimedas: yes, now it is maven.maven. Sorry, I was thinking in future-tense
Carlos: good point. To make it more clear, perhaps: I know its long, but it should suffice. |
|||||||||||||||||||||||||||||||||||||||||||||