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/02/03 11:19:35 UTC
[maven-bug] Closed: (MAVEN-247) Eclipse plugin should add junit to classpath if test cases exist
Message:
The following issue has been closed.
Resolver: Ben Walding
Date: Mon, 3 Feb 2003 4:19 AM
If a test directory is defined, and maven.eclipse.junit is not empty (it can't be null, the plugin defines it). Then junit-${maven.eclipse.junit}.jar is added to classpath.
---------------------------------------------------------------------
View the issue:
http://jira.werken.com/secure/ViewIssue.jspa?key=MAVEN-247
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-247
Summary: Eclipse plugin should add junit to classpath if test cases exist
Type: Improvement
Status: Closed
Priority: Trivial
Resolution: FIXED
Time Spent: Unknown
Estimate: 1 hour
Project: maven
Component: None
Assignee: Ben Walding
Reporter: Ben Walding
Created: Sun, 2 Feb 2003 6:58 PM
Updated: Mon, 3 Feb 2003 4:19 AM
Description:
When the eclipse plugin generates the project file, it neglects to add
junit to the classpath. As such, there are compile errors in the test cases due to the missing dependency.
1. Add the junit dep as defined by the test plugin if and only if the src/test or equivalent is being added to the classpath.
Will this need a disabler property?
---------------------------------------------------------------------
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