[jira] Commented: (MAVEN-1495) Test dependencies are NOT build / use dependencies

2005-02-10 Thread jira
The following comment has been added to this issue:

 Author: Jean-François Daune
Created: Thu, 10 Feb 2005 5:08 AM
   Body:
Another possibibility is to add a  tag under  tag.

Cheers,

J-F
-
View this comment:
  http://jira.codehaus.org/browse/MAVEN-1495?page=comments#action_29742

-
View the issue:
  http://jira.codehaus.org/browse/MAVEN-1495

Here is an overview of the issue:
-
Key: MAVEN-1495
Summary: Test dependencies are NOT build / use dependencies
   Type: Improvement

 Status: Unassigned
   Priority: Minor

 Original Estimate: 2 days
 Time Spent: Unknown
  Remaining: 2 days

Project: maven
 Components: 
 core

   Assignee: 
   Reporter: bryan thompson

Created: Fri, 5 Nov 2004 7:54 AM
Updated: Thu, 10 Feb 2005 5:08 AM
Environment: all

Description:
Feature: The POM  element should be modified to have an well-known 
attribute that identifies whether a dependency applies to the build, runtime, 
or tests.  The site generation plugin should be modified to reflect this 
distinction in the generated documentation.

Rationale:  I find that I need to include various jars for testing purposes 
that are not a dependency for building or otherwise using the artifact 
generated by my maven project.   At present, there is no way to mark a 
"dependency" as "test-only" such that it does not show up on the "Dependencies" 
report in the generated site documentation.  This results in misleading 
documentation (in the generated site) and confounds the notion of a project 
test dependency with a project build or runtime dependency.

Thanks,

-bryan


-
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[jira] Commented: (MAVEN-1495) Test dependencies are NOT build / use dependencies

2004-11-27 Thread jira
The following comment has been added to this issue:

 Author: Arik Kfir
Created: Sat, 27 Nov 2004 7:50 PM
   Body:
I agree - would love to see it implemented.

On another note - if we're speaking of dependency types including *runtime* 
dependencies, we should add a maven-run-plugin. Something along the lines of 
"check project type, run a mainclass, or start-web-start+activate browser" or 
something of the sort.

I'll dive into that...
-
View this comment:
  http://jira.codehaus.org/browse/MAVEN-1495?page=comments#action_27234

-
View the issue:
  http://jira.codehaus.org/browse/MAVEN-1495

Here is an overview of the issue:
-
Key: MAVEN-1495
Summary: Test dependencies are NOT build / use dependencies
   Type: Improvement

 Status: Unassigned
   Priority: Minor

 Original Estimate: 2 days
 Time Spent: Unknown
  Remaining: 2 days

Project: maven
 Components: 
 core

   Assignee: 
   Reporter: bryan thompson

Created: Fri, 5 Nov 2004 7:54 AM
Updated: Sat, 27 Nov 2004 7:50 PM
Environment: all

Description:
Feature: The POM  element should be modified to have an well-known 
attribute that identifies whether a dependency applies to the build, runtime, 
or tests.  The site generation plugin should be modified to reflect this 
distinction in the generated documentation.

Rationale:  I find that I need to include various jars for testing purposes 
that are not a dependency for building or otherwise using the artifact 
generated by my maven project.   At present, there is no way to mark a 
"dependency" as "test-only" such that it does not show up on the "Dependencies" 
report in the generated site documentation.  This results in misleading 
documentation (in the generated site) and confounds the notion of a project 
test dependency with a project build or runtime dependency.

Thanks,

-bryan


-
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[jira] Commented: (MAVEN-1495) Test dependencies are NOT build / use dependencies

2004-11-11 Thread jira
The following comment has been added to this issue:

 Author: Corey Scott
Created: Thu, 11 Nov 2004 10:32 AM
   Body:
I have to say, I agree with Bryan and there seems to be similar 
requests/musings in some of the mailings list (maven-users / commons-dev (i 
think)) regarding this.

I am happy to look into this if others agree that this is a useful feature?

Thanks,
-Corey
-
View this comment:
  http://jira.codehaus.org/browse/MAVEN-1495?page=comments#action_26331

-
View the issue:
  http://jira.codehaus.org/browse/MAVEN-1495

Here is an overview of the issue:
-
Key: MAVEN-1495
Summary: Test dependencies are NOT build / use dependencies
   Type: Improvement

 Status: Unassigned
   Priority: Minor

 Original Estimate: 2 days
 Time Spent: Unknown
  Remaining: 2 days

Project: maven
 Components: 
 core

   Assignee: 
   Reporter: bryan thompson

Created: Fri, 5 Nov 2004 7:54 AM
Updated: Thu, 11 Nov 2004 10:32 AM
Environment: all

Description:
Feature: The POM  element should be modified to have an well-known 
attribute that identifies whether a dependency applies to the build, runtime, 
or tests.  The site generation plugin should be modified to reflect this 
distinction in the generated documentation.

Rationale:  I find that I need to include various jars for testing purposes 
that are not a dependency for building or otherwise using the artifact 
generated by my maven project.   At present, there is no way to mark a 
"dependency" as "test-only" such that it does not show up on the "Dependencies" 
report in the generated site documentation.  This results in misleading 
documentation (in the generated site) and confounds the notion of a project 
test dependency with a project build or runtime dependency.

Thanks,

-bryan


-
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]