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 & 3
  • MNG-3420

In a reactor, attached artifacts with classifier should be used when generating classpath, instead of the whole output directory of the related project

  • Log In
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Duplicate
  • Affects Version/s: 2.0.5, 2.0.6, 2.0.7, 2.0.8
  • Fix Version/s: None
  • Component/s: Reactor and workspace
  • Labels:
    None
  • Patch Submitted:
    Yes

Description

In a reactor, when a project depends on attached artifacts with classifier of other projects (such as jar assemblies), the generated classpath includes all the output directory of the related projects.
This can lead to problems for example if these attached artifacts contains only a subset of the output directory of the related project.

I attached an example that shows this problem :
1/ launch "mvn install" in the "test-classifier" directory (POM project basedir), you'll get a compilation failure for module3.
2/ launch "mvn install" in the "module3" directory, it works.

I also attached a patch (it affects only MavenProject class).

  • Options
    • Sort By Name
    • Sort By Date
    • Ascending
    • Descending
    • Download All

Attachments

  1. Text File
    MavenProject-patch.txt
    26/Feb/08 5:22 AM
    0.7 kB
    Nicolas Rougé
  2. GZip Archive
    test-classifier.tar.gz
    26/Feb/08 5:22 AM
    1 kB
    Nicolas Rougé

Issue Links

duplicates

Bug - A problem which impairs or prevents the functions of the product. MNG-2720 Multiproject dependencies not accurate for project.compileClasspathElements when run from root project

  • 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

Bug - A problem which impairs or prevents the functions of the product. MNG-2871 Subartifact (ejb-client, test-jar etc.) are not reselved as active project artifacts in build phases prior to package

  • 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
Dimitar Raynov added a comment - 15/Apr/08 10:45 AM

I have this error too so i hope it will be resolved in the next version !

Show
Dimitar Raynov added a comment - 15/Apr/08 10:45 AM I have this error too so i hope it will be resolved in the next version !
Hide
Permalink
Brett Porter added a comment - 12/Jun/08 8:29 PM

can you confirm whether 2.0.9 resolved this issue? There were related changes.

Show
Brett Porter added a comment - 12/Jun/08 8:29 PM can you confirm whether 2.0.9 resolved this issue? There were related changes.
Hide
Permalink
Nicolas Rougé added a comment - 16/Jun/08 7:40 AM

2.0.9 didn't resolve this issue (same error when testing).

Show
Nicolas Rougé added a comment - 16/Jun/08 7:40 AM 2.0.9 didn't resolve this issue (same error when testing).

People

  • Assignee:
    Brett Porter
    Reporter:
    Nicolas Rougé
Vote (3)
Watch (5)

Dates

  • Created:
    26/Feb/08 5:22 AM
    Updated:
    07/Mar/09 5:50 AM
    Resolved:
    26/Feb/09 5:01 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.