jira.codehaus.org

  • Log In Access more options
    • Online Help
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What?s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
  • Maven 2.x JAR Plugin
  • MJAR-13

configure test-jar to include only special classes of the test source

  • Log In
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Duplicate
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: None
  • Labels:
    None

Description

The test-jar currently contains all test classes, but often you just want to share only some parts of it, e.g. a specialized abstract TestCase or a test toolkit or some mock classes, but not the complete unit test for an asrtifact. The plugin configuration shoulds contain a section with an includes/excludes pattern set.

Issue Links

is related to

Improvement - An improvement or enhancement to an existing feature or task. MJAR-30 Allow includes/excludes specification

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Improvement - An improvement or enhancement to an existing feature or task. SUREFIRE-180 Ability to add additions to classpath

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.
relates to

New Feature - A new feature of the product, which has yet to be developed. MNG-1330 direct support for mock classes

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
  • All
  • Comments
  • Work Log
  • History
  • Activity
Hide
Permalink
Brett Porter added a comment - 24/Nov/05 4:41 PM

I think there is an open issue to do this WRT mock classes and maybe actually creating a mock source directory.

Other than that, I think adding features like this is a slippery slope. A lot of Maven's features work and are simple because of the 1 source directory, 1 artifact rule. Anything that starts to product multiple artifacts with a subset of a source directory might not integrate well with other features.

Show
Brett Porter added a comment - 24/Nov/05 4:41 PM I think there is an open issue to do this WRT mock classes and maybe actually creating a mock source directory. Other than that, I think adding features like this is a slippery slope. A lot of Maven's features work and are simple because of the 1 source directory, 1 artifact rule. Anything that starts to product multiple artifacts with a subset of a source directory might not integrate well with other features.
Hide
Permalink
Joerg Schaible added a comment - 25/Nov/05 1:32 AM

Well, regarding the 1-source-1-artifact rule, the complete concept of the subtypes is flawed ... but they're a pragmatic solution for special cases. Normally I agree, but in this case you have that circular dependency and you cannot avoid it. The standard way seems something like (see the build section): http://svn.picocontainer.codehaus.org/java/picocontainer/trunk/tck/pom.xml?rev=2755&view=markup

With test-jar you already have 2/3 of the solution, why not complete it ?

Show
Joerg Schaible added a comment - 25/Nov/05 1:32 AM Well, regarding the 1-source-1-artifact rule, the complete concept of the subtypes is flawed ... but they're a pragmatic solution for special cases. Normally I agree, but in this case you have that circular dependency and you cannot avoid it. The standard way seems something like (see the build section): http://svn.picocontainer.codehaus.org/java/picocontainer/trunk/tck/pom.xml?rev=2755&view=markup With test-jar you already have 2/3 of the solution, why not complete it ?
Hide
Permalink
Joerg Schaible added a comment - 25/Nov/05 1:35 AM

Related issue: MNG-1330
(BTW: why can a user not create real JIRA links between issues ??)

Show
Joerg Schaible added a comment - 25/Nov/05 1:35 AM Related issue: MNG-1330 (BTW: why can a user not create real JIRA links between issues ??)
Hide
Permalink
Brett Porter added a comment - 25/Nov/05 6:02 PM

added ability to link, and yes thats the related issue I was referring to.

Show
Brett Porter added a comment - 25/Nov/05 6:02 PM added ability to link, and yes thats the related issue I was referring to.
Hide
Permalink
Olivier Lamy added a comment - 28/Dec/07 6:31 PM - edited

fix of MJAR-30 should fix this ?

Show
Olivier Lamy added a comment - 28/Dec/07 6:31 PM - edited fix of MJAR-30 should fix this ?
Hide
Permalink
Joerg Schaible added a comment - 30/Dec/07 11:04 AM

Duplicated by XSTR-30

Show
Joerg Schaible added a comment - 30/Dec/07 11:04 AM Duplicated by XSTR-30
Hide
Permalink
Dennis Lundberg added a comment - 30/Dec/07 11:31 AM

Did you really mean XSTR-30 ?

Show
Dennis Lundberg added a comment - 30/Dec/07 11:31 AM Did you really mean XSTR-30 ?
Hide
Permalink
Joerg Schaible added a comment - 30/Dec/07 11:39 AM

Sorry, no, MJAR-30

Show
Joerg Schaible added a comment - 30/Dec/07 11:39 AM Sorry, no, MJAR-30

People

  • Assignee:
    Unassigned
    Reporter:
    Joerg Schaible
Vote (0)
Watch (0)

Dates

  • Created:
    24/Nov/05 4:58 AM
    Updated:
    30/Dec/07 11:39 AM
    Resolved:
    30/Dec/07 11:04 AM
  • Atlassian JIRA (v5.0.4#731-sha1:3aa7374)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.