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-2181

Problem with reactor when using attached goal

  • Log In
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: None
  • Fix Version/s: Issues to be reviewed for 3.x
  • Component/s: Reactor and workspace
  • Labels:
    None
  • Complexity:
    Intermediate

Description

Here's my project dir structure:

trunk/
  |_ core/
    |_ api/
      |_ (several projects here)
    |_ uberjar/ (assembly project)
  |_ samples
    |_ testdata
      |_ empty-jar
      |_ (...)

If I build the trunk/core/ubjerjar project alone it works fine. Note: I have attached the "attached" goal to the verify phase so the assembly can be created when calling "mvn install".

If I build the project from the trunk by typing "mvn install", the uberjar/ project fails saying that the empty-jar artifact cannot be found in the local repository. That's normal it cannot be found because there are no dependencies on it in the core/ branch and it hasn't been built yet when the uberjar project executes. Of course there are no dependencies to it in the uberjar project.

It seems there's something fishy happening in the assembly plugin implementation...

Thanks

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

Attachments

  1. Text File
    log.txt
    27/Mar/06 6:44 AM
    307 kB
    Edwin Punzalan

Issue Links

is related to

Bug - A problem which impairs or prevents the functions of the product. MNG-1682 Plugins do not honor the correct extension when run as a part of a multiproject build

  • 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 - 25/Nov/05 6:33 PM

possibly related

Show
Brett Porter added a comment - 25/Nov/05 6:33 PM possibly related
Hide
Permalink
Edwin Punzalan added a comment - 27/Mar/06 6:44 AM

Looking at -X log, I see modules from the parent of the artifact's parent being resolved.

Attached is the log file and starting at line 3519, the projects being resolved are not part of the uberjar's dependencies.

Only api-generic and cargo-containers are the uberjar's dependencies.

Show
Edwin Punzalan added a comment - 27/Mar/06 6:44 AM Looking at -X log, I see modules from the parent of the artifact's parent being resolved. Attached is the log file and starting at line 3519, the projects being resolved are not part of the uberjar's dependencies. Only api-generic and cargo-containers are the uberjar's dependencies.

People

  • Assignee:
    Unassigned
    Reporter:
    Vincent Massol
Vote (4)
Watch (3)

Dates

  • Created:
    25/Nov/05 7:37 AM
    Updated:
    13/Dec/08 6:35 PM
  • 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.