Maven 2 & 3

extensions stopped working in 2.0.5-SNAPSHOT

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Blocker Blocker
  • Resolution: Fixed
  • Affects Version/s: 2.0.5
  • Fix Version/s: 2.0.5
  • Component/s: Artifacts and Repositories
  • Labels:
    None
  • Complexity:
    Intermediate
  • Number of attachments :
    1

Description

We're testing our build with the latest 2.0.5-SNAPSHOT. We use the checkstyle config described here http://people.apache.org/%7Eoching/maven-checkstyle-plugin/examples/multi-module-config.html
and it works perfectly in 2.0.4. Switching to 2.0.5 causes this to not be available on the classpath anymore.

Issue Links

This issue is duplicated by:
MNG-2795 Classloader problem loading a resource from a build extension Jar : difference between 2.0.4 and (future) 2.0.5 Major Closed
This issue relates to:
MNG-3281 Revisit backwards compat of extensions (IT 0114) Major Closed

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Brian Fox added a comment -

The attached builds successfully when run with maven 2.0.4
but fails when run with 2.0.5-SNAPSHOT

[ERROR] BUILD ERROR
[INFO] ---------------------------------------------------------------
[INFO] An error has occurred in Checkstyle report generation.

Embedded error: Unable to find configuration file location.
Unable to find location 'stc_checks.xml' as URL, File or Resource.

Show
Brian Fox added a comment - The attached builds successfully when run with maven 2.0.4 but fails when run with 2.0.5-SNAPSHOT [ERROR] BUILD ERROR [INFO] --------------------------------------------------------------- [INFO] An error has occurred in Checkstyle report generation. Embedded error: Unable to find configuration file location. Unable to find location 'stc_checks.xml' as URL, File or Resource.
Hide
Permalink
Brett Porter added a comment -

this works if you use a plugin dependency instead, however I will try and provide a workaround for the old behaviour

Show
Brett Porter added a comment - this works if you use a plugin dependency instead, however I will try and provide a workaround for the old behaviour
Hide
Permalink
Brian Fox added a comment -

The extension was chosen because the dependency won't be found if the plugin repo is separate from the regular artifact repo.

Show
Brian Fox added a comment - The extension was chosen because the dependency won't be found if the plugin repo is separate from the regular artifact repo.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.