[jira] (MSITE-501) Properties overwritten by settings.xml are ignored when creating parent-links
[
https://jira.codehaus.org/browse/MSITE-501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MSITE-501.
Resolution: Cannot Reproduce
Closing this, test project has not been provided in 1.5 years.
> Properties overwritten by settings.xml are ignored when creating parent-links
> -
>
> Key: MSITE-501
> URL: https://jira.codehaus.org/browse/MSITE-501
> Project: Maven Site Plugin
> Issue Type: Bug
> Components: property interpolation
>Affects Versions: 2.1.1
> Environment: Maven 2.2.1, Site-Plugin 2.1.1, Linux x86_64
>Reporter: Michael Wenig
>
> Our Parent has a url defined by
> {code:xml}${site.access.url}{code}
> where
> {code:xml}
> http://testdoku.ourdomain.de/mvn-sites/${groupId}/${artifactId}/${version}
> {code}
> this site.access-url is overwritten by settings.xml on our production server
> to the production-server:
> {code:xml}http://doku.ourdomain.de/mvn-sites/${groupId}/${artifactId}/${version}{code}
> (this is for security reasons to avoid productive-changes on misconfigured
> testing-systems)
> Unfortunately on our production-server links to the parentPom are generated
> only by the properties of the parentPom ignoring the settings.xml (which is
> used everywhere else). Therefore the parent-links are pointing to the testing
> system and not to production system!
> As we are not generating releasePoms (as we need some properties to be
> present in order to allow changing by children) we have no chance to generate
> correct links without putting them directly in the pom :-(
> Steps to Reproduce:
> Generate a parentPom:
> {code:xml}
> http://testdoku.ourdomain.de/mvn-sites/${groupId}/${artifactId}/${version}
>
> ${site.access.url}{code}
> Generate a second project using the parent
> put in your settings.xml:
> {code:xml}http://doku.ourdomain.de/mvn-sites/${groupId}/${artifactId}/${version}{code}
> an run site for the child - the parentLink is wrong!
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MSITE-501) Properties overwritten by settings.xml are ignored when creating parent-links
[
https://jira.codehaus.org/browse/MSITE-501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=325584#comment-325584
]
Herve Boutemy commented on MSITE-501:
-
can you provide a test zip?
I can't reproduce (and will be forced to close the issue as "cannot reproduce")
> Properties overwritten by settings.xml are ignored when creating parent-links
> -
>
> Key: MSITE-501
> URL: https://jira.codehaus.org/browse/MSITE-501
> Project: Maven 2.x and 3.x Site Plugin
> Issue Type: Bug
> Components: property interpolation
>Affects Versions: 2.1.1
> Environment: Maven 2.2.1, Site-Plugin 2.1.1, Linux x86_64
>Reporter: Michael Wenig
>
> Our Parent has a url defined by
> {code:xml}${site.access.url}{code}
> where
> {code:xml}
> http://testdoku.ourdomain.de/mvn-sites/${groupId}/${artifactId}/${version}
> {code}
> this site.access-url is overwritten by settings.xml on our production server
> to the production-server:
> {code:xml}http://doku.ourdomain.de/mvn-sites/${groupId}/${artifactId}/${version}{code}
> (this is for security reasons to avoid productive-changes on misconfigured
> testing-systems)
> Unfortunately on our production-server links to the parentPom are generated
> only by the properties of the parentPom ignoring the settings.xml (which is
> used everywhere else). Therefore the parent-links are pointing to the testing
> system and not to production system!
> As we are not generating releasePoms (as we need some properties to be
> present in order to allow changing by children) we have no chance to generate
> correct links without putting them directly in the pom :-(
> Steps to Reproduce:
> Generate a parentPom:
> {code:xml}
> http://testdoku.ourdomain.de/mvn-sites/${groupId}/${artifactId}/${version}
>
> ${site.access.url}{code}
> Generate a second project using the parent
> put in your settings.xml:
> {code:xml}http://doku.ourdomain.de/mvn-sites/${groupId}/${artifactId}/${version}{code}
> an run site for the child - the parentLink is wrong!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSITE-501) Properties overwritten by settings.xml are ignored when creating parent-links
[
https://jira.codehaus.org/browse/MSITE-501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MSITE-501:
Description:
Our Parent has a url defined by
{code:xml}${site.access.url}{code}
where
{code:xml}
http://testdoku.ourdomain.de/mvn-sites/${groupId}/${artifactId}/${version}
{code}
this site.access-url is overwritten by settings.xml on our production server to
the production-server:
{code:xml}http://doku.ourdomain.de/mvn-sites/${groupId}/${artifactId}/${version}{code}
(this is for security reasons to avoid productive-changes on misconfigured
testing-systems)
Unfortunately on our production-server links to the parentPom are generated
only by the properties of the parentPom ignoring the settings.xml (which is
used everywhere else). Therefore the parent-links are pointing to the testing
system and not to production system!
As we are not generating releasePoms (as we need some properties to be present
in order to allow changing by children) we have no chance to generate correct
links without putting them directly in the pom :-(
Steps to Reproduce:
Generate a parentPom:
{code:xml}
http://testdoku.ourdomain.de/mvn-sites/${groupId}/${artifactId}/${version}
${site.access.url}{code}
Generate a second project using the parent
put in your settings.xml:
{code:xml}http://doku.ourdomain.de/mvn-sites/${groupId}/${artifactId}/${version}{code}
an run site for the child - the parentLink is wrong!
was:
Our Parent has a url defined by
${site.access.url}
where
http://testdoku.ourdomain.de/mvn-sites/${groupId}/${artifactId}/${version}
this site.access-url is overwritten by settings.xml on our production server to
the production-server:
http://doku.ourdomain.de/mvn-sites/${groupId}/${artifactId}/${version}
(this is for security reasons to avoid productive-changes on misconfigured
testing-systems)
Unfortunately on our production-server links to the parentPom are generated
only by the properties of the parentPom ignoring the settings.xml (which is
used everywhere else). Therefore the parent-links are pointing to the testing
system and not to production system!
As we are not generating releasePoms (as we need some properties to be present
in order to allow changing by children) we have no chance to generate correct
links without putting them directly in the pom :-(
Steps to Reproduce:
Generate a parentPom:
http://testdoku.ourdomain.de/mvn-sites/${groupId}/${artifactId}/${version}
${site.access.url}
Generate a second project using the parent
put in your settings.xml:
http://doku.ourdomain.de/mvn-sites/${groupId}/${artifactId}/${version}
an run site for the child - the parentLink is wrong!
> Properties overwritten by settings.xml are ignored when creating parent-links
> -
>
> Key: MSITE-501
> URL: https://jira.codehaus.org/browse/MSITE-501
> Project: Maven 2.x and 3.x Site Plugin
> Issue Type: Bug
> Components: property interpolation
>Affects Versions: 2.1.1
> Environment: Maven 2.2.1, Site-Plugin 2.1.1, Linux x86_64
>Reporter: Michael Wenig
>
> Our Parent has a url defined by
> {code:xml}${site.access.url}{code}
> where
> {code:xml}
> http://testdoku.ourdomain.de/mvn-sites/${groupId}/${artifactId}/${version}
> {code}
> this site.access-url is overwritten by settings.xml on our production server
> to the production-server:
> {code:xml}http://doku.ourdomain.de/mvn-sites/${groupId}/${artifactId}/${version}{code}
> (this is for security reasons to avoid productive-changes on misconfigured
> testing-systems)
> Unfortunately on our production-server links to the parentPom are generated
> only by the properties of the parentPom ignoring the settings.xml (which is
> used everywhere else). Therefore the parent-links are pointing to the testing
> system and not to production system!
> As we are not generating releasePoms (as we need some properties to be
> present in order to allow changing by children) we have no chance to generate
> correct links without putting them directly in the pom :-(
> Steps to Reproduce:
> Generate a parentPom:
> {code:xml}
> http://testdoku.ourdomain.de/mvn-sites/${groupId}/${artifactId}/${version}
>
> ${site.access.url}{code}
> Generate a second project using the parent
> put in your settings.xml:
> {code:xml}http://doku.ourdomain.de/mvn-sites/${groupId}/${artifactId}/${version}{code}
> an run site for the child - the parentLink is wrong!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
