rategies to make this configurable in Maven 2.1.
- Brett
On 19/09/2006, at 12:58 AM, Mike Perham wrote:
> We constantly have version selection problems where Maven's random
> version selection bites us. This would almost always be solved if
> Maven would select the greater of
Mike Perham wrote:
> That's too bad. I think deps at the same level should pick the
> greater, not randomly. MNG-1577 would help a lot here.
>
> I'm also finding that exclusions are insideous - I can't see where an
> exclusion is coming from so I can't determine which module is
> erroneously ex
he conflict resolution
strategies to make this configurable in Maven 2.1.
- Brett
On 19/09/2006, at 12:58 AM, Mike Perham wrote:
> We constantly have version selection problems where Maven's random
> version selection bites us. This would almost always be solved if
> Maven would sel
gurable in Maven 2.1.
- Brett
On 19/09/2006, at 12:58 AM, Mike Perham wrote:
We constantly have version selection problems where Maven's random
version selection bites us. This would almost always be solved if
Maven would select the greater of the two versions. Why doesn't Maven
do th
We constantly have version selection problems where Maven's random
version selection bites us. This would almost always be solved if
Maven would select the greater of the two versions. Why doesn't Maven
do this instead of pickin
project.properties for version selection.
Type: Improvement
Status: Closed
Priority: Major
Resolution: FIXED
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-xdoc-plugin
Assignee: Jason van Zyl
Reporter: Jason van Zyl
Created: Tue, 6
:
-
Key: MPXDOC-74
Summary: Remove the requirement of having to use ${pom} properties in
project.properties for version selection.
Type: Improvement
Status: Open
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project
