You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Richard van der Hoff (JIRA)" <ji...@codehaus.org> on 2007/03/30 03:35:34 UTC
[jira] Created: (MNG-2915) No way to avoid adding artifactId to
site urls
No way to avoid adding artifactId to site urls
----------------------------------------------
Key: MNG-2915
URL: http://jira.codehaus.org/browse/MNG-2915
Project: Maven 2
Issue Type: Bug
Components: Sites & Reporting
Affects Versions: 2.0.5
Reporter: Richard van der Hoff
Currently, whenever a child pom inherits from a parent (and doesn't override the relevant settings), both project.url and project.distributionManagement.site.url have the name of the child artifact appended.
It would be nice to be able to have something like
:code:
<url>scpexe://host/blah/${project.artifactId}/${project.version}</url>
:code:
and have this inherited to all child poms in the obvious way.
My usecase for this is that we have a single parent pom for all our projects, with useful settings such as distributionManagement, and I'd like to be able to deploy their sites to a single directory and have Apache generate me a directory listing for all the child projects. However, I curently have no way of releasing the parent project without obliterating the list of child projects.
--
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: (MNG-2915) No way to avoid adding artifactId to
site urls
Posted by "Paul Harrison (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=174940#action_174940 ]
Paul Harrison commented on MNG-2915:
------------------------------------
I would like to add a plea for this behaviour to be modified - we too have a similar 3 level pom inheritance hierarchy, and it is irritating to have to specify the URLs in the final level when the root is specified in the top level because the intermedate level is automactically inserted. I think that the problems come about here because there is not a clear distinction made between pom inhertance and project aggregation - typically if a project only inherits from another project then the values should only be inherited, without modification - it a project is an aggregated child as well, then various URLs can have artifactIds automatically added to the end.
Even with this modification to behaviour I would also support the suggestion above that automatic appending of artifactId only occurs when the URL ends explictly with a "/" - this allows for more complex URL layouts to be specified in the root POM with the use of variables such as the
<url>scpexe://host/blah/${project.artifactId}/${project.version}</url>
which I think is a rather commonly desired layout.
> No way to avoid adding artifactId to site urls
> ----------------------------------------------
>
> Key: MNG-2915
> URL: http://jira.codehaus.org/browse/MNG-2915
> Project: Maven 2
> Issue Type: Improvement
> Components: Sites & Reporting
> Affects Versions: 2.0.5
> Reporter: Richard van der Hoff
> Priority: Minor
> Fix For: 3.x
>
>
> Currently, whenever a child pom inherits from a parent (and doesn't override the relevant settings), both project.url and project.distributionManagement.site.url have the name of the child artifact appended.
> It would be nice to be able to have something like
> :code:
> <url>scpexe://host/blah/${project.artifactId}/${project.version}</url>
> :code:
> and have this inherited to all child poms in the obvious way.
> My usecase for this is that we have a single parent pom for all our projects, with useful settings such as distributionManagement, and I'd like to be able to deploy their sites to a single directory and have Apache generate me a directory listing for all the child projects. However, I curently have no way of releasing the parent project without obliterating the list of child projects.
--
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: (MNG-2915) No way to avoid adding artifactId to
site urls
Posted by "Kenney Westerhof (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99680 ]
Kenney Westerhof commented on MNG-2915:
---------------------------------------
Place to fix: maven-project/src/main/java/org/apache/maven/project/inheritance/DefaultModelInheritanceAssembler.java
perhaps check wheter the parentpath already contains an expression for artifactId, or maybe add a decision
whether to append based on the path ending in a slash or not.
> No way to avoid adding artifactId to site urls
> ----------------------------------------------
>
> Key: MNG-2915
> URL: http://jira.codehaus.org/browse/MNG-2915
> Project: Maven 2
> Issue Type: Improvement
> Components: Sites & Reporting
> Affects Versions: 2.0.5
> Reporter: Richard van der Hoff
> Priority: Minor
> Fix For: Reviewed Pending Version Assignment
>
>
> Currently, whenever a child pom inherits from a parent (and doesn't override the relevant settings), both project.url and project.distributionManagement.site.url have the name of the child artifact appended.
> It would be nice to be able to have something like
> :code:
> <url>scpexe://host/blah/${project.artifactId}/${project.version}</url>
> :code:
> and have this inherited to all child poms in the obvious way.
> My usecase for this is that we have a single parent pom for all our projects, with useful settings such as distributionManagement, and I'd like to be able to deploy their sites to a single directory and have Apache generate me a directory listing for all the child projects. However, I curently have no way of releasing the parent project without obliterating the list of child projects.
--
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] Moved: (MSITE-449) No way to avoid adding artifactId to site
urls
Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason van Zyl moved MNG-2915 to MSITE-449:
------------------------------------------
Complexity: (was: Intermediate)
Component/s: (was: Sites & Reporting)
Fix Version/s: (was: 3.x)
Affects Version/s: (was: 2.0.5)
Key: MSITE-449 (was: MNG-2915)
Project: Maven 2.x Site Plugin (was: Maven 2 & 3)
> No way to avoid adding artifactId to site urls
> ----------------------------------------------
>
> Key: MSITE-449
> URL: http://jira.codehaus.org/browse/MSITE-449
> Project: Maven 2.x Site Plugin
> Issue Type: Improvement
> Reporter: Richard van der Hoff
> Priority: Minor
>
> Currently, whenever a child pom inherits from a parent (and doesn't override the relevant settings), both project.url and project.distributionManagement.site.url have the name of the child artifact appended.
> It would be nice to be able to have something like
> :code:
> <url>scpexe://host/blah/${project.artifactId}/${project.version}</url>
> :code:
> and have this inherited to all child poms in the obvious way.
> My usecase for this is that we have a single parent pom for all our projects, with useful settings such as distributionManagement, and I'd like to be able to deploy their sites to a single directory and have Apache generate me a directory listing for all the child projects. However, I curently have no way of releasing the parent project without obliterating the list of child projects.
--
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] (MNG-4508) No way to avoid adding artifactId to site urls
Posted by "Darryl L. Miles (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MNG-4508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=315317#comment-315317 ]
Darryl L. Miles commented on MNG-4508:
--------------------------------------
Remove the inheritance rules but provide a maven configured variable ${maven.project.path} or something that will becomes "/parent-parent/parent" in deepest level of a 3 level project. The super POM will be an empty string. The mid-level will be "/parent-parent". Now users get the best of both worlds without being chained to the convention.
> No way to avoid adding artifactId to site urls
> ----------------------------------------------
>
> Key: MNG-4508
> URL: https://jira.codehaus.org/browse/MNG-4508
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Inheritance and Interpolation
> Reporter: Richard van der Hoff
> Priority: Minor
> Fix For: 3.2
>
>
> Currently, whenever a child pom inherits from a parent (and doesn't override the relevant settings), both project.url and project.distributionManagement.site.url have the name of the child artifact appended.
> It would be nice to be able to have something like
> :code:
> <url>scpexe://host/blah/${project.artifactId}/${project.version}</url>
> :code:
> and have this inherited to all child poms in the obvious way.
> My usecase for this is that we have a single parent pom for all our projects, with useful settings such as distributionManagement, and I'd like to be able to deploy their sites to a single directory and have Apache generate me a directory listing for all the child projects. However, I curently have no way of releasing the parent project without obliterating the list of child projects.
--
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: (MNG-2915) No way to avoid adding
artifactId to site urls
Posted by "Cyril ADRIAN (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_115388 ]
cadrian edited comment on MNG-2915 at 11/29/07 10:40 AM:
--------------------------------------------------------------
Good idea, thanks :-)
Although I still need a proper fix because we usually have two levels:
- our "enterprise" pom
- an "application head" containing all the modules an dinheritting from the "enterprise" pom
- the application modules inheritting from the "application head"
Anyway, thanks for the idea. Maybe I can refine it to use our two levels (if the names of the flag files are well defined it may be simple enough to put everything in the "enterprise" pom).
UPDATE: it does not work... I cannot put an <scm> within a <profile> :-(
was (Author: cadrian):
Good idea, thanks :-)
Although I still need a proper fix because we usually have two levels:
- our "enterprise" pom
- an "application head" containing all the modules an dinheritting from the "enterprise" pom
- the application modules inheritting from the "application head"
Anyway, thanks for the idea. Maybe I can refine it to use our two levels (if the names of the flag files are well defined it may be simple enough to put everything in the "enterprise" pom).
> No way to avoid adding artifactId to site urls
> ----------------------------------------------
>
> Key: MNG-2915
> URL: http://jira.codehaus.org/browse/MNG-2915
> Project: Maven 2
> Issue Type: Improvement
> Components: Sites & Reporting
> Affects Versions: 2.0.5
> Reporter: Richard van der Hoff
> Priority: Minor
> Fix For: 2.1
>
>
> Currently, whenever a child pom inherits from a parent (and doesn't override the relevant settings), both project.url and project.distributionManagement.site.url have the name of the child artifact appended.
> It would be nice to be able to have something like
> :code:
> <url>scpexe://host/blah/${project.artifactId}/${project.version}</url>
> :code:
> and have this inherited to all child poms in the obvious way.
> My usecase for this is that we have a single parent pom for all our projects, with useful settings such as distributionManagement, and I'd like to be able to deploy their sites to a single directory and have Apache generate me a directory listing for all the child projects. However, I curently have no way of releasing the parent project without obliterating the list of child projects.
--
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: (MNG-2915) No way to avoid adding artifactId to
site urls
Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason van Zyl updated MNG-2915:
-------------------------------
Fix Version/s: (was: 2.1-alpha-1)
2.1.x
> No way to avoid adding artifactId to site urls
> ----------------------------------------------
>
> Key: MNG-2915
> URL: http://jira.codehaus.org/browse/MNG-2915
> Project: Maven 2
> Issue Type: Improvement
> Components: Sites & Reporting
> Affects Versions: 2.0.5
> Reporter: Richard van der Hoff
> Priority: Minor
> Fix For: 2.1.x
>
>
> Currently, whenever a child pom inherits from a parent (and doesn't override the relevant settings), both project.url and project.distributionManagement.site.url have the name of the child artifact appended.
> It would be nice to be able to have something like
> :code:
> <url>scpexe://host/blah/${project.artifactId}/${project.version}</url>
> :code:
> and have this inherited to all child poms in the obvious way.
> My usecase for this is that we have a single parent pom for all our projects, with useful settings such as distributionManagement, and I'd like to be able to deploy their sites to a single directory and have Apache generate me a directory listing for all the child projects. However, I curently have no way of releasing the parent project without obliterating the list of child projects.
--
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: (MNG-4508) No way to avoid adding artifactId to
site urls
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MNG-4508:
------------------------------
Fix Version/s: 3.1.alpha1
correct. This requires a model change - probably by a combination of two things:
# the facility for the site and reporting plugins to intelligently create a multi-module site map with equivalent functionality to the current URL extension
# removal of the inheritance rules (or site elements) from the POM in a new model version
We can keep this issue to the latter
> No way to avoid adding artifactId to site urls
> ----------------------------------------------
>
> Key: MNG-4508
> URL: http://jira.codehaus.org/browse/MNG-4508
> Project: Maven 2 & 3
> Issue Type: Improvement
> Reporter: Richard van der Hoff
> Priority: Minor
> Fix For: 3.1.alpha1
>
>
> Currently, whenever a child pom inherits from a parent (and doesn't override the relevant settings), both project.url and project.distributionManagement.site.url have the name of the child artifact appended.
> It would be nice to be able to have something like
> :code:
> <url>scpexe://host/blah/${project.artifactId}/${project.version}</url>
> :code:
> and have this inherited to all child poms in the obvious way.
> My usecase for this is that we have a single parent pom for all our projects, with useful settings such as distributionManagement, and I'd like to be able to deploy their sites to a single directory and have Apache generate me a directory listing for all the child projects. However, I curently have no way of releasing the parent project without obliterating the list of child projects.
--
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: (MNG-2915) No way to avoid adding artifactId to
site urls
Posted by "Kenney Westerhof (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kenney Westerhof updated MNG-2915:
----------------------------------
Fix Version/s: (was: Reviewed Pending Version Assignment)
2.1-alpha-1
> No way to avoid adding artifactId to site urls
> ----------------------------------------------
>
> Key: MNG-2915
> URL: http://jira.codehaus.org/browse/MNG-2915
> Project: Maven 2
> Issue Type: Improvement
> Components: Sites & Reporting
> Affects Versions: 2.0.5
> Reporter: Richard van der Hoff
> Priority: Minor
> Fix For: 2.1-alpha-1
>
>
> Currently, whenever a child pom inherits from a parent (and doesn't override the relevant settings), both project.url and project.distributionManagement.site.url have the name of the child artifact appended.
> It would be nice to be able to have something like
> :code:
> <url>scpexe://host/blah/${project.artifactId}/${project.version}</url>
> :code:
> and have this inherited to all child poms in the obvious way.
> My usecase for this is that we have a single parent pom for all our projects, with useful settings such as distributionManagement, and I'd like to be able to deploy their sites to a single directory and have Apache generate me a directory listing for all the child projects. However, I curently have no way of releasing the parent project without obliterating the list of child projects.
--
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: (MNG-2915) No way to avoid adding artifactId to
site urls
Posted by "Cyril ADRIAN (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_115388 ]
Cyril ADRIAN commented on MNG-2915:
-----------------------------------
Good idea, thanks :-)
Although I still need a proper fix because we usually have two levels:
- our "enterprise" pom
- an "application head" containing all the modules an dinheritting from the "enterprise" pom
- the application modules inheritting from the "application head"
Anyway, thanks for the idea. Maybe I can refine it to use our two levels (if the names of the flag files are well defined it may be simple enough to put everything in the "enterprise" pom).
> No way to avoid adding artifactId to site urls
> ----------------------------------------------
>
> Key: MNG-2915
> URL: http://jira.codehaus.org/browse/MNG-2915
> Project: Maven 2
> Issue Type: Improvement
> Components: Sites & Reporting
> Affects Versions: 2.0.5
> Reporter: Richard van der Hoff
> Priority: Minor
> Fix For: 2.1
>
>
> Currently, whenever a child pom inherits from a parent (and doesn't override the relevant settings), both project.url and project.distributionManagement.site.url have the name of the child artifact appended.
> It would be nice to be able to have something like
> :code:
> <url>scpexe://host/blah/${project.artifactId}/${project.version}</url>
> :code:
> and have this inherited to all child poms in the obvious way.
> My usecase for this is that we have a single parent pom for all our projects, with useful settings such as distributionManagement, and I'd like to be able to deploy their sites to a single directory and have Apache generate me a directory listing for all the child projects. However, I curently have no way of releasing the parent project without obliterating the list of child projects.
--
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] (MNG-4508) No way to avoid adding artifactId to site urls
Posted by "Hannes Kogler (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MNG-4508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308696#comment-308696 ]
Hannes Kogler commented on MNG-4508:
------------------------------------
It seems that the problem described here is responsible for my current problem when trying to use the maven-release-plugin ... :-(
I linked the following issue: MRELEASE-331
> No way to avoid adding artifactId to site urls
> ----------------------------------------------
>
> Key: MNG-4508
> URL: https://jira.codehaus.org/browse/MNG-4508
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Inheritance and Interpolation
> Reporter: Richard van der Hoff
> Priority: Minor
> Fix For: 3.1
>
>
> Currently, whenever a child pom inherits from a parent (and doesn't override the relevant settings), both project.url and project.distributionManagement.site.url have the name of the child artifact appended.
> It would be nice to be able to have something like
> :code:
> <url>scpexe://host/blah/${project.artifactId}/${project.version}</url>
> :code:
> and have this inherited to all child poms in the obvious way.
> My usecase for this is that we have a single parent pom for all our projects, with useful settings such as distributionManagement, and I'd like to be able to deploy their sites to a single directory and have Apache generate me a directory listing for all the child projects. However, I curently have no way of releasing the parent project without obliterating the list of child projects.
--
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] Updated: (MNG-4508) No way to avoid adding artifactId to
site urls
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann updated MNG-4508:
-----------------------------------
Component/s: Inheritance and Interpolation
> No way to avoid adding artifactId to site urls
> ----------------------------------------------
>
> Key: MNG-4508
> URL: http://jira.codehaus.org/browse/MNG-4508
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Inheritance and Interpolation
> Reporter: Richard van der Hoff
> Priority: Minor
> Fix For: 3.1
>
>
> Currently, whenever a child pom inherits from a parent (and doesn't override the relevant settings), both project.url and project.distributionManagement.site.url have the name of the child artifact appended.
> It would be nice to be able to have something like
> :code:
> <url>scpexe://host/blah/${project.artifactId}/${project.version}</url>
> :code:
> and have this inherited to all child poms in the obvious way.
> My usecase for this is that we have a single parent pom for all our projects, with useful settings such as distributionManagement, and I'd like to be able to deploy their sites to a single directory and have Apache generate me a directory listing for all the child projects. However, I curently have no way of releasing the parent project without obliterating the list of child projects.
--
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] Moved: (MNG-4508) No way to avoid adding artifactId to site
urls
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter moved MSITE-449 to MNG-4508:
-----------------------------------------
Complexity: Intermediate
Key: MNG-4508 (was: MSITE-449)
Project: Maven 2 & 3 (was: Maven 2.x Site Plugin)
> No way to avoid adding artifactId to site urls
> ----------------------------------------------
>
> Key: MNG-4508
> URL: http://jira.codehaus.org/browse/MNG-4508
> Project: Maven 2 & 3
> Issue Type: Improvement
> Reporter: Richard van der Hoff
> Priority: Minor
> Fix For: 3.1.alpha1
>
>
> Currently, whenever a child pom inherits from a parent (and doesn't override the relevant settings), both project.url and project.distributionManagement.site.url have the name of the child artifact appended.
> It would be nice to be able to have something like
> :code:
> <url>scpexe://host/blah/${project.artifactId}/${project.version}</url>
> :code:
> and have this inherited to all child poms in the obvious way.
> My usecase for this is that we have a single parent pom for all our projects, with useful settings such as distributionManagement, and I'd like to be able to deploy their sites to a single directory and have Apache generate me a directory listing for all the child projects. However, I curently have no way of releasing the parent project without obliterating the list of child projects.
--
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] Issue Comment Edited: (MNG-2915) No way to avoid adding
artifactId to site urls
Posted by "Cyril ADRIAN (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_115366 ]
cadrian edited comment on MNG-2915 at 11/29/07 8:27 AM:
-------------------------------------------------------------
Hello,
I have the same problem with scm URLs which have the artifactId appended too. That's extremely disturbing because we don't want to nest projects with an scm repository (FWIW it's svn).
We prefer a flat structure even if we have parent-child dependancies. And of course, we don't want to duplicate the <scm> section in each and every POM (which we currently have to do).
I think the priority of this bug should be more important.
Is there a way we can help with the issue?
Thanks
was (Author: cadrian):
Hello,
I have the same problem with scm URLs which have the artifactId appended too. That's extremely disturbing because we don't want to nest projects with an scm repository (FWIW it's svn). We prefer a flat structure even if we have parent-child dependancies.
I think the priority of this bug should be more important.
Is there a way we can help with the issue?
Thanks
> No way to avoid adding artifactId to site urls
> ----------------------------------------------
>
> Key: MNG-2915
> URL: http://jira.codehaus.org/browse/MNG-2915
> Project: Maven 2
> Issue Type: Improvement
> Components: Sites & Reporting
> Affects Versions: 2.0.5
> Reporter: Richard van der Hoff
> Priority: Minor
> Fix For: 2.1
>
>
> Currently, whenever a child pom inherits from a parent (and doesn't override the relevant settings), both project.url and project.distributionManagement.site.url have the name of the child artifact appended.
> It would be nice to be able to have something like
> :code:
> <url>scpexe://host/blah/${project.artifactId}/${project.version}</url>
> :code:
> and have this inherited to all child poms in the obvious way.
> My usecase for this is that we have a single parent pom for all our projects, with useful settings such as distributionManagement, and I'd like to be able to deploy their sites to a single directory and have Apache generate me a directory listing for all the child projects. However, I curently have no way of releasing the parent project without obliterating the list of child projects.
--
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-449) No way to avoid adding artifactId to
site urls
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=204615#action_204615 ]
Dennis Lundberg commented on MSITE-449:
---------------------------------------
Is this really an issue for the Site Plugin? The comments seem to indicate that it has to do with how maven-model works (or doesn't work) with properties.
> No way to avoid adding artifactId to site urls
> ----------------------------------------------
>
> Key: MSITE-449
> URL: http://jira.codehaus.org/browse/MSITE-449
> Project: Maven 2.x Site Plugin
> Issue Type: Improvement
> Reporter: Richard van der Hoff
> Priority: Minor
>
> Currently, whenever a child pom inherits from a parent (and doesn't override the relevant settings), both project.url and project.distributionManagement.site.url have the name of the child artifact appended.
> It would be nice to be able to have something like
> :code:
> <url>scpexe://host/blah/${project.artifactId}/${project.version}</url>
> :code:
> and have this inherited to all child poms in the obvious way.
> My usecase for this is that we have a single parent pom for all our projects, with useful settings such as distributionManagement, and I'd like to be able to deploy their sites to a single directory and have Apache generate me a directory listing for all the child projects. However, I curently have no way of releasing the parent project without obliterating the list of child projects.
--
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: (MNG-2915) No way to avoid adding artifactId to
site urls
Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carlos Sanchez updated MNG-2915:
--------------------------------
Priority: Minor (was: Major)
Issue Type: Improvement (was: Bug)
> No way to avoid adding artifactId to site urls
> ----------------------------------------------
>
> Key: MNG-2915
> URL: http://jira.codehaus.org/browse/MNG-2915
> Project: Maven 2
> Issue Type: Improvement
> Components: Sites & Reporting
> Affects Versions: 2.0.5
> Reporter: Richard van der Hoff
> Priority: Minor
>
> Currently, whenever a child pom inherits from a parent (and doesn't override the relevant settings), both project.url and project.distributionManagement.site.url have the name of the child artifact appended.
> It would be nice to be able to have something like
> :code:
> <url>scpexe://host/blah/${project.artifactId}/${project.version}</url>
> :code:
> and have this inherited to all child poms in the obvious way.
> My usecase for this is that we have a single parent pom for all our projects, with useful settings such as distributionManagement, and I'd like to be able to deploy their sites to a single directory and have Apache generate me a directory listing for all the child projects. However, I curently have no way of releasing the parent project without obliterating the list of child projects.
--
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: (MNG-2915) No way to avoid adding artifactId to
site urls
Posted by "Richard van der Hoff (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_115385 ]
Richard van der Hoff commented on MNG-2915:
-------------------------------------------
We actually found a workaround for this problem in our particular usecase.
The main distributionManagement section in our parent-pom has the url ready to be appended to by child poms, and the parent-pom also has a profile which overrides it just for that one pom; thus:
{code:xml}
<profiles>
<profile>
<id>deploying-base-pom-itself</id>
<activation>
<file>
<exists>THIS-IS-base-pom</exists>
</file>
</activation>
<distributionManagement>
<site>
<id>mx-release</id>
<url>scpexe://host/blah/base-pom</url>
</site>
</distributionManagement>
</profile>
</profiles>
{code}
This profile is then enabled for the base pom by creating a file entitled THIS-IS-base-pom.
I think this might also work for the scm url.
Obviously this becomes a less useful solution for deeper project heirarchies, but it works pretty well for us.
> No way to avoid adding artifactId to site urls
> ----------------------------------------------
>
> Key: MNG-2915
> URL: http://jira.codehaus.org/browse/MNG-2915
> Project: Maven 2
> Issue Type: Improvement
> Components: Sites & Reporting
> Affects Versions: 2.0.5
> Reporter: Richard van der Hoff
> Priority: Minor
> Fix For: 2.1
>
>
> Currently, whenever a child pom inherits from a parent (and doesn't override the relevant settings), both project.url and project.distributionManagement.site.url have the name of the child artifact appended.
> It would be nice to be able to have something like
> :code:
> <url>scpexe://host/blah/${project.artifactId}/${project.version}</url>
> :code:
> and have this inherited to all child poms in the obvious way.
> My usecase for this is that we have a single parent pom for all our projects, with useful settings such as distributionManagement, and I'd like to be able to deploy their sites to a single directory and have Apache generate me a directory listing for all the child projects. However, I curently have no way of releasing the parent project without obliterating the list of child projects.
--
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: (MNG-2915) No way to avoid adding artifactId to
site urls
Posted by "Cyril ADRIAN (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_115366 ]
Cyril ADRIAN commented on MNG-2915:
-----------------------------------
Hello,
I have the same problem with scm URLs which have the artifactId appended too. That's extremely disturbing because we don't want to nest projects with an scm repository (FWIW it's svn). We prefer a flat structure even if we have parent-child dependancies.
I think the priority of this bug should be more important.
Is there a way we can help with the issue?
Thanks
> No way to avoid adding artifactId to site urls
> ----------------------------------------------
>
> Key: MNG-2915
> URL: http://jira.codehaus.org/browse/MNG-2915
> Project: Maven 2
> Issue Type: Improvement
> Components: Sites & Reporting
> Affects Versions: 2.0.5
> Reporter: Richard van der Hoff
> Priority: Minor
> Fix For: 2.1
>
>
> Currently, whenever a child pom inherits from a parent (and doesn't override the relevant settings), both project.url and project.distributionManagement.site.url have the name of the child artifact appended.
> It would be nice to be able to have something like
> :code:
> <url>scpexe://host/blah/${project.artifactId}/${project.version}</url>
> :code:
> and have this inherited to all child poms in the obvious way.
> My usecase for this is that we have a single parent pom for all our projects, with useful settings such as distributionManagement, and I'd like to be able to deploy their sites to a single directory and have Apache generate me a directory listing for all the child projects. However, I curently have no way of releasing the parent project without obliterating the list of child projects.
--
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