You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Stefano Bagnara (JIRA)" <ji...@codehaus.org> on 2007/05/31 17:37:58 UTC
[jira] Created: (MSITE-234) Maven skin / version as plugin
parameters
Maven skin / version as plugin parameters
-----------------------------------------
Key: MSITE-234
URL: http://jira.codehaus.org/browse/MSITE-234
Project: Maven 2.x Site Plugin
Issue Type: Improvement
Affects Versions: 2.0-beta-5
Reporter: Stefano Bagnara
I have an m2 reactor project where one of the modules is the skin used
by one of the other modules (and every of its children).
root
|- maven-skin
'- module1 (using maven-skin)
The problem is that module1 declare the skin in its site.xml file and
this way the version is not updated when I use the release:prepare to
update my poms.
So I checked the site plugin searching for a way to declare the skin in
the plugin configuration instead of the site.xml descriptor but there is
no such option.
I think that a good solution would be to use something like the remote
resource plugin (used for LICENSE/NOTICE) also for the skin declaration.
--
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-234) Maven skin / version as plugin
parameters
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=142497#action_142497 ]
Dennis Lundberg commented on MSITE-234:
---------------------------------------
So what you really would like to happen is that the Release Plugin should update the version of the skin in the site.xml of module1 during release:prepare?
> Maven skin / version as plugin parameters
> -----------------------------------------
>
> Key: MSITE-234
> URL: http://jira.codehaus.org/browse/MSITE-234
> Project: Maven 2.x Site Plugin
> Issue Type: Improvement
> Affects Versions: 2.0-beta-5
> Reporter: Stefano Bagnara
>
> I have an m2 reactor project where one of the modules is the skin used
> by one of the other modules (and every of its children).
> {noformat}
> root
> |- maven-skin
> '- module1 (using maven-skin)
> {noformat}
> The problem is that module1 declare the skin in its site.xml file and
> this way the version is not updated when I use the release:prepare to
> update my poms.
> So I checked the site plugin searching for a way to declare the skin in
> the plugin configuration instead of the site.xml descriptor but there is
> no such option.
> I think that a good solution would be to use something like the remote
> resource plugin (used for LICENSE/NOTICE) also for the skin declaration.
--
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-234) Maven skin / version as plugin
parameters
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg updated MSITE-234:
----------------------------------
Description:
I have an m2 reactor project where one of the modules is the skin used
by one of the other modules (and every of its children).
{noformat}
root
|- maven-skin
'- module1 (using maven-skin)
{noformat}
The problem is that module1 declare the skin in its site.xml file and
this way the version is not updated when I use the release:prepare to
update my poms.
So I checked the site plugin searching for a way to declare the skin in
the plugin configuration instead of the site.xml descriptor but there is
no such option.
I think that a good solution would be to use something like the remote
resource plugin (used for LICENSE/NOTICE) also for the skin declaration.
was:
I have an m2 reactor project where one of the modules is the skin used
by one of the other modules (and every of its children).
root
|- maven-skin
'- module1 (using maven-skin)
The problem is that module1 declare the skin in its site.xml file and
this way the version is not updated when I use the release:prepare to
update my poms.
So I checked the site plugin searching for a way to declare the skin in
the plugin configuration instead of the site.xml descriptor but there is
no such option.
I think that a good solution would be to use something like the remote
resource plugin (used for LICENSE/NOTICE) also for the skin declaration.
Add formating.
> Maven skin / version as plugin parameters
> -----------------------------------------
>
> Key: MSITE-234
> URL: http://jira.codehaus.org/browse/MSITE-234
> Project: Maven 2.x Site Plugin
> Issue Type: Improvement
> Affects Versions: 2.0-beta-5
> Reporter: Stefano Bagnara
>
> I have an m2 reactor project where one of the modules is the skin used
> by one of the other modules (and every of its children).
> {noformat}
> root
> |- maven-skin
> '- module1 (using maven-skin)
> {noformat}
> The problem is that module1 declare the skin in its site.xml file and
> this way the version is not updated when I use the release:prepare to
> update my poms.
> So I checked the site plugin searching for a way to declare the skin in
> the plugin configuration instead of the site.xml descriptor but there is
> no such option.
> I think that a good solution would be to use something like the remote
> resource plugin (used for LICENSE/NOTICE) also for the skin declaration.
--
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] (MSITE-234) Maven skin / version as plugin parameters
Posted by "Herve Boutemy (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MSITE-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Herve Boutemy closed MSITE-234.
-------------------------------
Resolution: Fixed
Assignee: Herve Boutemy
just use ${project.version} in your site.xml
FYI, this is actually used by skins to generate their site with their actual build result: see [maven-fluido-skin's site.xml|http://svn.apache.org/viewvc/maven/skins/tags/maven-fluido-skin-1.3.0/src/site/site.xml?view=markup] for example
> Maven skin / version as plugin parameters
> -----------------------------------------
>
> Key: MSITE-234
> URL: https://jira.codehaus.org/browse/MSITE-234
> Project: Maven 2.x and 3.x Site Plugin
> Issue Type: Improvement
> Affects Versions: 2.0-beta-5
> Reporter: Stefano Bagnara
> Assignee: Herve Boutemy
>
> I have an m2 reactor project where one of the modules is the skin used
> by one of the other modules (and every of its children).
> {noformat}
> root
> |- maven-skin
> '- module1 (using maven-skin)
> {noformat}
> The problem is that module1 declare the skin in its site.xml file and
> this way the version is not updated when I use the release:prepare to
> update my poms.
> So I checked the site plugin searching for a way to declare the skin in
> the plugin configuration instead of the site.xml descriptor but there is
> no such option.
> I think that a good solution would be to use something like the remote
> resource plugin (used for LICENSE/NOTICE) also for the skin declaration.
--
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] Issue Comment Edited: (MSITE-234) Maven skin / version as
plugin parameters
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=97736#action_97736 ]
dennislundberg edited comment on MSITE-234 at 7/20/08 7:38 AM:
----------------------------------------------------------------
Sorry.. the tree has been changed by the JIRA formater
{noformat}
| root (1.0-SNAPSHOT)
| - maven-skin (1.1-SNAPSHOT)
| - module1 (using maven-skin - 1.1-SNAPSHOT)
{noformat}
was (Author: bago):
Sorry.. the tree has been changed by the JIRA formater
| root (1.0-SNAPSHOT)
| - maven-skin (1.1-SNAPSHOT)
| - module1 (using maven-skin - 1.1-SNAPSHOT)
> Maven skin / version as plugin parameters
> -----------------------------------------
>
> Key: MSITE-234
> URL: http://jira.codehaus.org/browse/MSITE-234
> Project: Maven 2.x Site Plugin
> Issue Type: Improvement
> Affects Versions: 2.0-beta-5
> Reporter: Stefano Bagnara
>
> I have an m2 reactor project where one of the modules is the skin used
> by one of the other modules (and every of its children).
> root
> |- maven-skin
> '- module1 (using maven-skin)
> The problem is that module1 declare the skin in its site.xml file and
> this way the version is not updated when I use the release:prepare to
> update my poms.
> So I checked the site plugin searching for a way to declare the skin in
> the plugin configuration instead of the site.xml descriptor but there is
> no such option.
> I think that a good solution would be to use something like the remote
> resource plugin (used for LICENSE/NOTICE) also for the skin declaration.
--
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-234) Maven skin / version as plugin
parameters
Posted by "Stefano Bagnara (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_97736 ]
Stefano Bagnara commented on MSITE-234:
---------------------------------------
Sorry.. the tree has been changed by the JIRA formater
| root (1.0-SNAPSHOT)
| - maven-skin (1.1-SNAPSHOT)
| - module1 (using maven-skin - 1.1-SNAPSHOT)
> Maven skin / version as plugin parameters
> -----------------------------------------
>
> Key: MSITE-234
> URL: http://jira.codehaus.org/browse/MSITE-234
> Project: Maven 2.x Site Plugin
> Issue Type: Improvement
> Affects Versions: 2.0-beta-5
> Reporter: Stefano Bagnara
>
> I have an m2 reactor project where one of the modules is the skin used
> by one of the other modules (and every of its children).
> root
> |- maven-skin
> '- module1 (using maven-skin)
> The problem is that module1 declare the skin in its site.xml file and
> this way the version is not updated when I use the release:prepare to
> update my poms.
> So I checked the site plugin searching for a way to declare the skin in
> the plugin configuration instead of the site.xml descriptor but there is
> no such option.
> I think that a good solution would be to use something like the remote
> resource plugin (used for LICENSE/NOTICE) also for the skin declaration.
--
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-234) Maven skin / version as plugin
parameters
Posted by "Stefano Bagnara (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=143361#action_143361 ]
Stefano Bagnara commented on MSITE-234:
---------------------------------------
Dennis: I'm not an m2 guru, but that's what I expected. It's the same of having a dependency between the 2 modules. Currently the "direct" dependency would be updated while the skin dependency is ignored.
> Maven skin / version as plugin parameters
> -----------------------------------------
>
> Key: MSITE-234
> URL: http://jira.codehaus.org/browse/MSITE-234
> Project: Maven 2.x Site Plugin
> Issue Type: Improvement
> Affects Versions: 2.0-beta-5
> Reporter: Stefano Bagnara
>
> I have an m2 reactor project where one of the modules is the skin used
> by one of the other modules (and every of its children).
> {noformat}
> root
> |- maven-skin
> '- module1 (using maven-skin)
> {noformat}
> The problem is that module1 declare the skin in its site.xml file and
> this way the version is not updated when I use the release:prepare to
> update my poms.
> So I checked the site plugin searching for a way to declare the skin in
> the plugin configuration instead of the site.xml descriptor but there is
> no such option.
> I think that a good solution would be to use something like the remote
> resource plugin (used for LICENSE/NOTICE) also for the skin declaration.
--
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