[jira] Commented: (MNG-2915) No way to avoid adding artifactId to site urls
[
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
scpexe://host/blah/${project.artifactId}/${project.version}
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:
> scpexe://host/blah/${project.artifactId}/${project.version}
> :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
[
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:
> scpexe://host/blah/${project.artifactId}/${project.version}
> :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
[
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}
deploying-base-pom-itself
THIS-IS-base-pom
mx-release
scpexe://host/blah/base-pom
{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:
> scpexe://host/blah/${project.artifactId}/${project.version}
> :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
[
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:
> scpexe://host/blah/${project.artifactId}/${project.version}
> :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
[
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:
> scpexe://host/blah/${project.artifactId}/${project.version}
> :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
