Maven 2.x Antrun Plugin

maven.test.classpath doesn't contain test scope dependancies

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: 1.1
  • Labels:
    None
  • Number of attachments :
    2

Description

maven.test.classpath only has things in compile scope, not in test scope.

  1. Text File
    MANTRUN-28.patch
    23/Dec/05 9:21 AM
    0.5 kB
    Gilles Scokart
  2. XML File
    pom.xml
    10/Nov/05 2:30 PM
    1 kB
    Brian Fox

Issue Links

duplicates

Bug - A problem which impairs or prevents the functions of the product. MANTRUN-21 maven.test.classpath is not correctly set

  • 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
Hide
Permalink
Brian Fox added a comment -

Run this pom and see that the echo'd classpath contains target/classes but not target/test-classes and also the junit jar is missing, but other compile scope ones are there.

Show
Brian Fox added a comment - Run this pom and see that the echo'd classpath contains target/classes but not target/test-classes and also the junit jar is missing, but other compile scope ones are there.
Hide
Permalink
Kenney Westerhof added a comment -

That's because the ant plugin only has @requiresDependencyResolution compile.
I was hoping there would be a way to specify the desired scope at runtime or configuration time
easily, but I'll have to look into that. I only intended the antrun plugin for quick 'normal' usage, not for
tests, but it could be useful there too.

Show
Kenney Westerhof added a comment - That's because the ant plugin only has @requiresDependencyResolution compile. I was hoping there would be a way to specify the desired scope at runtime or configuration time easily, but I'll have to look into that. I only intended the antrun plugin for quick 'normal' usage, not for tests, but it could be useful there too.
Hide
Permalink
Brian Fox added a comment -

Yes, very usefull there. We are using it in lieu of a testNG plugin for now.

Show
Brian Fox added a comment - Yes, very usefull there. We are using it in lieu of a testNG plugin for now.
Hide
Permalink
John Casey added a comment -

wouldn't a stop-gap fix be to add @requiresDependencyResolution test?

Show
John Casey added a comment - wouldn't a stop-gap fix be to add @requiresDependencyResolution test?
Hide
Permalink
Brian Fox added a comment -

any chance this can get fixed in the current plugin release cycle? We currently need to have a bunch of test dependancies placed in the compile scope to work around. Consequently they get packaged into wars unless manually excluding them.

Show
Brian Fox added a comment - any chance this can get fixed in the current plugin release cycle? We currently need to have a bunch of test dependancies placed in the compile scope to work around. Consequently they get packaged into wars unless manually excluding them.
Hide
Permalink
Gilles Scokart added a comment -

I have similar problem. I provide the patch just in case it could accelerate the fix.

Without this patch, the reference maven.test.classpath is simply useless.

Show
Gilles Scokart added a comment - I have similar problem. I provide the patch just in case it could accelerate the fix. Without this patch, the reference maven.test.classpath is simply useless.

People

  • Assignee:
    Carlos Sanchez
    Reporter:
    Brian Fox
Vote (2)
Watch (2)

Dates

  • Created:
    Updated:
    Resolved: