You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Aleksander Adamowski (JIRA)" <ji...@codehaus.org> on 2009/04/07 12:59:12 UTC

[jira] Created: (MSITE-399) In a multi-module project, site plugin tries to get current project's artifacts from local repository (which may not be installed yet) even if relative paths are correctly set

In a multi-module project, site plugin tries to get current project's artifacts from local repository (which may not be installed yet) even if relative paths are correctly set
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

                 Key: MSITE-399
                 URL: http://jira.codehaus.org/browse/MSITE-399
             Project: Maven 2.x Site Plugin
          Issue Type: Bug
            Reporter: Aleksander Adamowski


As reported in MISTE-307 by distinct people:

http://jira.codehaus.org/browse/MSITE-307?focusedCommentId=138004&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_138004

http://jira.codehaus.org/browse/MSITE-307?focusedCommentId=138503&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_138503

The problem is that the site plugin tries to get artifacts of the current multi-module project from the repository instead of using the configured inter-module relative paths, which may lead to stale data being used (artifacts from the previous build) or even build errors (if the artifact's didn't get installed yet).




-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (MSITE-399) In a multi-module project, site plugin tries to get current project's artifacts from local repository (which may not be installed yet) even if relative paths are correctly set

Posted by "Michael Wenig (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MSITE-399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=212827#action_212827 ] 

Michael Wenig commented on MSITE-399:
-------------------------------------

I think this is the same problem as mentioned in MJAVADOC-275 (didn't try the test case there)

We have the same problem in every multi-module-project 

mvn clean install
mvn site

works, but

mvn clean install site

leads to build errors

I don't know if it is relevant but we are using two hierarchies of multimodule:

pom.xml (includes only modules/pom.xml)
./modules/pom.xml (includes module1 and module2)
./module1/pom.xml
./module2/pom.xml




> In a multi-module project, site plugin tries to get current project's artifacts from local repository (which may not be installed yet) even if relative paths are correctly set
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MSITE-399
>                 URL: http://jira.codehaus.org/browse/MSITE-399
>             Project: Maven 2.x Site Plugin
>          Issue Type: Bug
>            Reporter: Aleksander Adamowski
>
> As reported in MISTE-307 by distinct people:
> http://jira.codehaus.org/browse/MSITE-307?focusedCommentId=138004&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_138004
> http://jira.codehaus.org/browse/MSITE-307?focusedCommentId=138503&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_138503
> The problem is that the site plugin tries to get artifacts of the current multi-module project from the repository instead of using the configured inter-module relative paths, which may lead to stale data being used (artifacts from the previous build) or even build errors (if the artifact's didn't get installed yet).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (MSITE-399) In a multi-module project, site plugin tries to get current project's artifacts from local repository (which may not be installed yet) even if relative paths are correctly set

Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MSITE-399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=172360#action_172360 ] 

Dennis Lundberg commented on MSITE-399:
---------------------------------------

Can you please provide a test project that can be used to reproduce this issue?

> In a multi-module project, site plugin tries to get current project's artifacts from local repository (which may not be installed yet) even if relative paths are correctly set
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MSITE-399
>                 URL: http://jira.codehaus.org/browse/MSITE-399
>             Project: Maven 2.x Site Plugin
>          Issue Type: Bug
>            Reporter: Aleksander Adamowski
>
> As reported in MISTE-307 by distinct people:
> http://jira.codehaus.org/browse/MSITE-307?focusedCommentId=138004&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_138004
> http://jira.codehaus.org/browse/MSITE-307?focusedCommentId=138503&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_138503
> The problem is that the site plugin tries to get artifacts of the current multi-module project from the repository instead of using the configured inter-module relative paths, which may lead to stale data being used (artifacts from the previous build) or even build errors (if the artifact's didn't get installed yet).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Closed: (MSITE-399) In a multi-module project, site plugin tries to get current project's artifacts from local repository (which may not be installed yet) even if relative paths are correctly set

Posted by "Lukas Theussl (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MSITE-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lukas Theussl closed MSITE-399.
-------------------------------

    Resolution: Duplicate
      Assignee: Lukas Theussl

> In a multi-module project, site plugin tries to get current project's artifacts from local repository (which may not be installed yet) even if relative paths are correctly set
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MSITE-399
>                 URL: http://jira.codehaus.org/browse/MSITE-399
>             Project: Maven 2.x and 3.x Site Plugin
>          Issue Type: Bug
>          Components: multi module
>            Reporter: Aleksander Adamowski
>            Assignee: Lukas Theussl
>
> As reported in MISTE-307 by distinct people:
> http://jira.codehaus.org/browse/MSITE-307?focusedCommentId=138004&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_138004
> http://jira.codehaus.org/browse/MSITE-307?focusedCommentId=138503&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_138503
> The problem is that the site plugin tries to get artifacts of the current multi-module project from the repository instead of using the configured inter-module relative paths, which may lead to stale data being used (artifacts from the previous build) or even build errors (if the artifact's didn't get installed yet).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira