You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Adrian Shum (JIRA)" <ji...@codehaus.org> on 2012/07/18 12:31:21 UTC

[jira] (MNG-5316) Build Extension not resolved from reactor

Adrian Shum created MNG-5316:
--------------------------------

             Summary: Build Extension not resolved from reactor
                 Key: MNG-5316
                 URL: https://jira.codehaus.org/browse/MNG-5316
             Project: Maven 2 & 3
          Issue Type: Bug
    Affects Versions: 3.0.4
         Environment: Windows XP, JDK 1.6.0_30
            Reporter: Adrian Shum
         Attachments: exttest.zip

This seems to be what described in another bug MNG-1323.

I encountered this issue when I am trying out what described in FindBugs multi-module configuration:
http://mojo.codehaus.org/findbugs-maven-plugin/examples/multi-module-config.html

Attached please find a sample project which I skimmed from my existing project.  

exttest is a multi-module project
exttest-qa module is the module aimed to be included as extension.  This module is not having any dependency, and it is intentionally not inheriting from exttest-parent to avoid cyclic dependency
exttest-parent is the parent POM for the whole project, and it add exttest-qa as a build extension.
exttest-main did nothing in this test. I put it in just to make the whole project looks more reasonable :)

Simply mvn clean will shows the error of :
[ERROR]     Unresolveable build extension: Plugin com.foo:exttest-qa:1.0-SNAPSHOT or one of its dependencies could not be resolved: Failure to find com.foo:exttest-qa:jar:1.0-SNAPSHOT in ....


However I expect exttest-qa should be resolved from the reactor.



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] (MNG-5316) Build Extension not resolved from reactor

Posted by "Adrian Shum (JIRA)" <ji...@codehaus.org>.
     [ https://jira.codehaus.org/browse/MNG-5316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Adrian Shum updated MNG-5316:
-----------------------------

    Attachment: exttest.zip
    
> Build Extension not resolved from reactor
> -----------------------------------------
>
>                 Key: MNG-5316
>                 URL: https://jira.codehaus.org/browse/MNG-5316
>             Project: Maven 2 & 3
>          Issue Type: Bug
>    Affects Versions: 3.0.4
>         Environment: Windows XP, JDK 1.6.0_30
>            Reporter: Adrian Shum
>         Attachments: exttest.zip
>
>
> This seems to be what described in another bug MNG-1323.
> I encountered this issue when I am trying out what described in FindBugs multi-module configuration:
> http://mojo.codehaus.org/findbugs-maven-plugin/examples/multi-module-config.html
> Attached please find a sample project which I skimmed from my existing project.  
> exttest is a multi-module project
> exttest-qa module is the module aimed to be included as extension.  This module is not having any dependency, and it is intentionally not inheriting from exttest-parent to avoid cyclic dependency
> exttest-parent is the parent POM for the whole project, and it add exttest-qa as a build extension.
> exttest-main did nothing in this test. I put it in just to make the whole project looks more reasonable :)
> Simply mvn clean will shows the error of :
> [ERROR]     Unresolveable build extension: Plugin com.foo:exttest-qa:1.0-SNAPSHOT or one of its dependencies could not be resolved: Failure to find com.foo:exttest-qa:jar:1.0-SNAPSHOT in ....
> However I expect exttest-qa should be resolved from the reactor.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] (MNG-5316) Build Extension not resolved from reactor

Posted by "Adrian Shum (JIRA)" <ji...@codehaus.org>.
    [ https://jira.codehaus.org/browse/MNG-5316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308966#comment-308966 ] 

Adrian Shum commented on MNG-5316:
----------------------------------

Any comments or update on this issue?  I am a bit worried that this issue tracker is not actually in use, is it?
                
> Build Extension not resolved from reactor
> -----------------------------------------
>
>                 Key: MNG-5316
>                 URL: https://jira.codehaus.org/browse/MNG-5316
>             Project: Maven 2 & 3
>          Issue Type: Bug
>    Affects Versions: 3.0.4
>         Environment: Windows XP, JDK 1.6.0_30
>            Reporter: Adrian Shum
>         Attachments: exttest.zip
>
>
> This seems to be what described in another bug MNG-1323.
> I encountered this issue when I am trying out what described in FindBugs multi-module configuration:
> http://mojo.codehaus.org/findbugs-maven-plugin/examples/multi-module-config.html
> Attached please find a sample project which I skimmed from my existing project.  
> exttest is a multi-module project
> exttest-qa module is the module aimed to be included as extension.  This module is not having any dependency, and it is intentionally not inheriting from exttest-parent to avoid cyclic dependency
> exttest-parent is the parent POM for the whole project, and it add exttest-qa as a build extension.
> exttest-main did nothing in this test. I put it in just to make the whole project looks more reasonable :)
> Simply mvn clean will shows the error of :
> [ERROR]     Unresolveable build extension: Plugin com.foo:exttest-qa:1.0-SNAPSHOT or one of its dependencies could not be resolved: Failure to find com.foo:exttest-qa:jar:1.0-SNAPSHOT in ....
> However I expect exttest-qa should be resolved from the reactor.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira