You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by bo...@werken.com on 2003/03/08 00:13:27 UTC
[maven-bug] Updated: (MAVEN-319) Add ability for clover to use a specific clover dep rather than just clover-1.0.jar
The following issue has been updated:
Updater: Ben Walding (mailto:jakarta@walding.com)
Date: Fri, 7 Mar 2003 5:13 PM
Changes:
[Status] changed from [Assigned] to [In Progress]
---------------------------------------------------------------------
For a full history of the issue, see:
http://jira.werken.com/secure/ViewIssue.jspa?key=MAVEN-319&page=history
---------------------------------------------------------------------
View the issue:
http://jira.werken.com/secure/ViewIssue.jspa?key=MAVEN-319
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-319
Summary: Add ability for clover to use a specific clover dep rather than just clover-1.0.jar
Type: Bug
Status: In Progress
Priority: Major
Time Spent: Unknown
Estimate: 2 hours
Project: maven
Component: None
Assignee: Ben Walding
Reporter: Ben Walding
Created: Fri, 7 Mar 2003 5:13 PM
Updated: Fri, 7 Mar 2003 5:13 PM
Description:
For users who have multiple OS projects, they will typically have multiple clover jars with licensing in each one.
My thoughts are to:
Add a property, eg.
maven.clover.jar=clover-1.0-dataforge.jar
So that clover now uses that jar from the repository. There is probably some validity to the argument that the jar should not necessarily be in the repo, but I don't want fight that one at the moment.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.werken.com/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira