You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Kek (JIRA)" <ji...@codehaus.org> on 2009/12/01 17:45:55 UTC
[jira] Created: (MSITE-438) dropped from
site.xml for pom.xml without section
<menu ref="modules"/> dropped from site.xml for pom.xml without <modules> section
----------------------------------------------------------------------------------
Key: MSITE-438
URL: http://jira.codehaus.org/browse/MSITE-438
Project: Maven 2.x Site Plugin
Issue Type: Bug
Components: inheritance, multi module
Affects Versions: 2.0.1
Environment: Windows XP, CentOS Linux, Maven 2.2.1, Sun JDK 1.6.0_u17
Reporter: Kek
Attachments: project.zip
We have common "pom-parent" artifact that defines repositories, pluginsManagement, distribution, etc. And there is defined the site.xml descriptor too.
The site.xml lokks like:
<body>
<menu ref="parent"/>
<menu ref="modules"/>
<menu ref="reports"/>
</body>
but when we build this artifact and deploy it to the repository, there is automaticaly generated and uploaded different site descriptor "pom-parent-1.0.0-site.xml" that contains only:
<body>
<menu ref="parent" />
<menu ref="reports" />
</body>
The "modules" menu was droped by maven.
After some investigation I found that the "modules" menu section is always dropped, when the pom.xml for pom-parent does not contains any submodule definition
<modules>
<module>some-submodule</module>
</modules>
But I don't want to specify any submodule for this common pom because it is used as "abstract" parent for all company projects. We want to have only one central site.xml descriptor definition managed in "pom-parent" project and avoid its duplication in each inherited project.
The workaround is create some "dummy-submodule" under "pom-parent" and define the <modules> section in pom.xml or define the site.xml descriptor for each inherited project.
--
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-438) dropped from
site.xml for pom.xml without section
Posted by "Juan Pablo Santos RodrÃguez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=233888#action_233888 ]
Juan Pablo Santos RodrÃguez commented on MSITE-438:
---------------------------------------------------
Hi,
the workaround described in comment #1 seems to cause a lock when doing mvn sonar:sonar (with sonar-2.2 and maven-2.2.1)
regards,
jp
> <menu ref="modules"/> dropped from site.xml for pom.xml without <modules> section
> ----------------------------------------------------------------------------------
>
> Key: MSITE-438
> URL: http://jira.codehaus.org/browse/MSITE-438
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Components: inheritance, multi module
> Affects Versions: 2.0.1
> Environment: Windows XP, CentOS Linux, Maven 2.2.1, Sun JDK 1.6.0_u17
> Reporter: Kek
> Attachments: project.zip
>
>
> We have common "pom-parent" artifact that defines repositories, pluginsManagement, distribution, etc. And there is defined the site.xml descriptor too.
> The site.xml lokks like:
> {code:xml} <body>
> <menu ref="parent"/>
> <menu ref="modules"/>
> <menu ref="reports"/>
> </body>{code}
> but when we build this artifact and deploy it to the repository, there is automaticaly generated and uploaded different site descriptor "pom-parent-1.0.0-site.xml" that contains only:
> {code:xml} <body>
> <menu ref="parent" />
> <menu ref="reports" />
> </body>{code}
> The "modules" menu was droped by maven.
> After some investigation I found that the "modules" menu section is always dropped, when the pom.xml for pom-parent does not contains any submodule definition
> {code:xml} <modules>
> <module>some-submodule</module>
> </modules>{code}
> But I don't want to specify any submodule for this common pom because it is used as "abstract" parent for all company projects. We want to have only one central site.xml descriptor definition managed in "pom-parent" project and avoid its duplication in each inherited project.
> The workaround is create some "dummy-submodule" under "pom-parent" and define the <modules> section in pom.xml or define the site.xml descriptor for each inherited project.
--
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] Updated: (MSITE-438) dropped from
site.xml for pom.xml without section
Posted by "Herve Boutemy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Herve Boutemy updated MSITE-438:
--------------------------------
Description:
We have common "pom-parent" artifact that defines repositories, pluginsManagement, distribution, etc. And there is defined the site.xml descriptor too.
The site.xml lokks like:
{code:xml} <body>
<menu ref="parent"/>
<menu ref="modules"/>
<menu ref="reports"/>
</body>{code}
but when we build this artifact and deploy it to the repository, there is automaticaly generated and uploaded different site descriptor "pom-parent-1.0.0-site.xml" that contains only:
{code:xml} <body>
<menu ref="parent" />
<menu ref="reports" />
</body>{code}
The "modules" menu was droped by maven.
After some investigation I found that the "modules" menu section is always dropped, when the pom.xml for pom-parent does not contains any submodule definition
{code:xml} <modules>
<module>some-submodule</module>
</modules>{code}
But I don't want to specify any submodule for this common pom because it is used as "abstract" parent for all company projects. We want to have only one central site.xml descriptor definition managed in "pom-parent" project and avoid its duplication in each inherited project.
The workaround is create some "dummy-submodule" under "pom-parent" and define the <modules> section in pom.xml or define the site.xml descriptor for each inherited project.
was:
We have common "pom-parent" artifact that defines repositories, pluginsManagement, distribution, etc. And there is defined the site.xml descriptor too.
The site.xml lokks like:
<body>
<menu ref="parent"/>
<menu ref="modules"/>
<menu ref="reports"/>
</body>
but when we build this artifact and deploy it to the repository, there is automaticaly generated and uploaded different site descriptor "pom-parent-1.0.0-site.xml" that contains only:
<body>
<menu ref="parent" />
<menu ref="reports" />
</body>
The "modules" menu was droped by maven.
After some investigation I found that the "modules" menu section is always dropped, when the pom.xml for pom-parent does not contains any submodule definition
<modules>
<module>some-submodule</module>
</modules>
But I don't want to specify any submodule for this common pom because it is used as "abstract" parent for all company projects. We want to have only one central site.xml descriptor definition managed in "pom-parent" project and avoid its duplication in each inherited project.
The workaround is create some "dummy-submodule" under "pom-parent" and define the <modules> section in pom.xml or define the site.xml descriptor for each inherited project.
> <menu ref="modules"/> dropped from site.xml for pom.xml without <modules> section
> ----------------------------------------------------------------------------------
>
> Key: MSITE-438
> URL: http://jira.codehaus.org/browse/MSITE-438
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Components: inheritance, multi module
> Affects Versions: 2.0.1
> Environment: Windows XP, CentOS Linux, Maven 2.2.1, Sun JDK 1.6.0_u17
> Reporter: Kek
> Attachments: project.zip
>
>
> We have common "pom-parent" artifact that defines repositories, pluginsManagement, distribution, etc. And there is defined the site.xml descriptor too.
> The site.xml lokks like:
> {code:xml} <body>
> <menu ref="parent"/>
> <menu ref="modules"/>
> <menu ref="reports"/>
> </body>{code}
> but when we build this artifact and deploy it to the repository, there is automaticaly generated and uploaded different site descriptor "pom-parent-1.0.0-site.xml" that contains only:
> {code:xml} <body>
> <menu ref="parent" />
> <menu ref="reports" />
> </body>{code}
> The "modules" menu was droped by maven.
> After some investigation I found that the "modules" menu section is always dropped, when the pom.xml for pom-parent does not contains any submodule definition
> {code:xml} <modules>
> <module>some-submodule</module>
> </modules>{code}
> But I don't want to specify any submodule for this common pom because it is used as "abstract" parent for all company projects. We want to have only one central site.xml descriptor definition managed in "pom-parent" project and avoid its duplication in each inherited project.
> The workaround is create some "dummy-submodule" under "pom-parent" and define the <modules> section in pom.xml or define the site.xml descriptor for each inherited project.
--
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-438) dropped from
site.xml for pom.xml without section
Posted by "Kek (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=200169#action_200169 ]
Kek commented on MSITE-438:
---------------------------
I found new workaround. Simly define
<modules>
<module></module> <!-- workaround for http://jira.codehaus.org/browse/MSITE-438 -->
</modules>
to pom.xml for parent-pom. This gives me the requested result.
> <menu ref="modules"/> dropped from site.xml for pom.xml without <modules> section
> ----------------------------------------------------------------------------------
>
> Key: MSITE-438
> URL: http://jira.codehaus.org/browse/MSITE-438
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Components: inheritance, multi module
> Affects Versions: 2.0.1
> Environment: Windows XP, CentOS Linux, Maven 2.2.1, Sun JDK 1.6.0_u17
> Reporter: Kek
> Attachments: project.zip
>
>
> We have common "pom-parent" artifact that defines repositories, pluginsManagement, distribution, etc. And there is defined the site.xml descriptor too.
> The site.xml lokks like:
> <body>
> <menu ref="parent"/>
> <menu ref="modules"/>
> <menu ref="reports"/>
> </body>
> but when we build this artifact and deploy it to the repository, there is automaticaly generated and uploaded different site descriptor "pom-parent-1.0.0-site.xml" that contains only:
> <body>
> <menu ref="parent" />
> <menu ref="reports" />
> </body>
> The "modules" menu was droped by maven.
> After some investigation I found that the "modules" menu section is always dropped, when the pom.xml for pom-parent does not contains any submodule definition
> <modules>
> <module>some-submodule</module>
> </modules>
> But I don't want to specify any submodule for this common pom because it is used as "abstract" parent for all company projects. We want to have only one central site.xml descriptor definition managed in "pom-parent" project and avoid its duplication in each inherited project.
> The workaround is create some "dummy-submodule" under "pom-parent" and define the <modules> section in pom.xml or define the site.xml descriptor for each inherited project.
--
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-438) dropped from
site.xml for pom.xml without section
Posted by "Lukas Theussl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lukas Theussl closed MSITE-438.
-------------------------------
Resolution: Duplicate
Assignee: Lukas Theussl
> <menu ref="modules"/> dropped from site.xml for pom.xml without <modules> section
> ----------------------------------------------------------------------------------
>
> Key: MSITE-438
> URL: http://jira.codehaus.org/browse/MSITE-438
> Project: Maven 2.x and 3.x Site Plugin
> Issue Type: Bug
> Components: inheritance, multi module
> Affects Versions: 2.0.1
> Environment: Windows XP, CentOS Linux, Maven 2.2.1, Sun JDK 1.6.0_u17
> Reporter: Kek
> Assignee: Lukas Theussl
> Attachments: project.zip
>
>
> We have common "pom-parent" artifact that defines repositories, pluginsManagement, distribution, etc. And there is defined the site.xml descriptor too.
> The site.xml lokks like:
> {code:xml} <body>
> <menu ref="parent"/>
> <menu ref="modules"/>
> <menu ref="reports"/>
> </body>{code}
> but when we build this artifact and deploy it to the repository, there is automaticaly generated and uploaded different site descriptor "pom-parent-1.0.0-site.xml" that contains only:
> {code:xml} <body>
> <menu ref="parent" />
> <menu ref="reports" />
> </body>{code}
> The "modules" menu was droped by maven.
> After some investigation I found that the "modules" menu section is always dropped, when the pom.xml for pom-parent does not contains any submodule definition
> {code:xml} <modules>
> <module>some-submodule</module>
> </modules>{code}
> But I don't want to specify any submodule for this common pom because it is used as "abstract" parent for all company projects. We want to have only one central site.xml descriptor definition managed in "pom-parent" project and avoid its duplication in each inherited project.
> The workaround is create some "dummy-submodule" under "pom-parent" and define the <modules> section in pom.xml or define the site.xml descriptor for each inherited project.
--
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