maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Herve Boutemy (JIRA)" <j...@codehaus.org>
Subject [jira] (MSITE-604) Properties from settings.xml are not recognized in site distribution management
Date Sun, 12 Oct 2014 10:05:11 GMT

    [ https://jira.codehaus.org/browse/MSITE-604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=354243#comment-354243
] 

Herve Boutemy edited comment on MSITE-604 at 10/12/14 5:04 AM:
---------------------------------------------------------------

thank you Jörg: I can reproduce a failure with the patched IT:
{noformat}[ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.4.1-SNAPSHOT:deploy
(default-cli) on project MSITE-604: Execution default-cli of goal org.apache.maven.plugins:maven-site-plugin:3.4.1-SNAPSHOT:deploy
failed: Base URI is not absolute: $%7bmsite604.siteRepositoryRoot%7d/$%7bmsite604.siteRepositoryBase%7d/parent
-> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.4.1-SNAPSHOT:deploy
(default-cli) on project MSITE-604: Execution default-cli of goal org.apache.maven.plugins:maven-site-plugin:3.4.1-SNAPSHOT:deploy
failed: Base URI is not absolute: $%7bmsite604.siteRepositoryRoot%7d/$%7bmsite604.siteRepositoryBase%7d/parent
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
	at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
	at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:347)
	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:154)
	at org.apache.maven.cli.MavenCli.execute(MavenCli.java:582)
	at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
	at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
	at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
	at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.PluginExecutionException: Execution default-cli of goal
org.apache.maven.plugins:maven-site-plugin:3.4.1-SNAPSHOT:deploy failed: Base URI is not absolute:
$%7bmsite604.siteRepositoryRoot%7d/$%7bmsite604.siteRepositoryBase%7d/parent
	at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:143)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
	... 19 more
Caused by: java.lang.IllegalArgumentException: Base URI is not absolute: $%7bmsite604.siteRepositoryRoot%7d/$%7bmsite604.siteRepositoryBase%7d/parent
	at org.apache.maven.doxia.site.decoration.inheritance.URIPathDescriptor.<init>(URIPathDescriptor.java:73)
	at org.apache.maven.plugins.site.deploy.AbstractDeployMojo.getTopLevelProject(AbstractDeployMojo.java:827)
	at org.apache.maven.plugins.site.deploy.SiteDeployMojo.determineDeploySite(SiteDeployMojo.java:67)
	at org.apache.maven.plugins.site.deploy.AbstractDeployMojo.getDeploySite(AbstractDeployMojo.java:235)
	at org.apache.maven.plugins.site.deploy.AbstractDeployMojo.execute(AbstractDeployMojo.java:166)
	at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
	... 20 more{noformat}

is it the failure everybody is experiencing in real world?


was (Author: hboutemy):
thank you Jörg: I can reproduce a failure with the patched IT:
{noformat}[ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.4.1-SNAPSHOT:deploy
(default-cli) on project MSITE-604: Execution default-cli of goal org.apache.maven.plugins:maven-site-plugin:3.4.1-SNAPSHOT:deploy
failed: Base URI is not absolute: $%7bmsite604.siteRepositoryRoot%7d/$%7bmsite604.siteRepositoryBase%7d/parent
-> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.4.1-SNAPSHOT:deploy
(default-cli) on project MSITE-604: Execution default-cli of goal org.apache.maven.plugins:maven-site-plugin:3.4.1-SNAPSHOT:deploy
failed: Base URI is not absolute: $%7bmsite604.siteRepositoryRoot%7d/$%7bmsite604.siteRepositoryBase%7d/parent
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
	at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
	at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:347)
	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:154)
	at org.apache.maven.cli.MavenCli.execute(MavenCli.java:582)
	at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
	at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
	at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
	at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.PluginExecutionException: Execution default-cli of goal
org.apache.maven.plugins:maven-site-plugin:3.4.1-SNAPSHOT:deploy failed: Base URI is not absolute:
$%7bmsite604.siteRepositoryRoot%7d/$%7bmsite604.siteRepositoryBase%7d/parent
	at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:143)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
	... 19 more
Caused by: java.lang.IllegalArgumentException: Base URI is not absolute: $%7bmsite604.siteRepositoryRoot%7d/$%7bmsite604.siteRepositoryBase%7d/parent
	at org.apache.maven.doxia.site.decoration.inheritance.URIPathDescriptor.<init>(URIPathDescriptor.java:73)
	at org.apache.maven.plugins.site.deploy.AbstractDeployMojo.getTopLevelProject(AbstractDeployMojo.java:827)
	at org.apache.maven.plugins.site.deploy.SiteDeployMojo.determineDeploySite(SiteDeployMojo.java:67)
	at org.apache.maven.plugins.site.deploy.AbstractDeployMojo.getDeploySite(AbstractDeployMojo.java:235)
	at org.apache.maven.plugins.site.deploy.AbstractDeployMojo.execute(AbstractDeployMojo.java:166)
	at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
	... 20 more{noformat}

is it the failure everybody see in real world?

> Properties from settings.xml are not recognized in site distribution management 
> --------------------------------------------------------------------------------
>
>                 Key: MSITE-604
>                 URL: https://jira.codehaus.org/browse/MSITE-604
>             Project: Maven Site Plugin
>          Issue Type: Bug
>          Components: site:deploy
>    Affects Versions: 3.0
>         Environment: Apache Maven 2.2.1 and 3.0.3
>            Reporter: Marcin Kuthan
>             Fix For: backlog
>
>         Attachments: MSITE-604-it.patch, MSITE-604-it.patch, MSITE-604-it.patch, MSITE-604-maven3-2.patch,
MSITE-604-maven3.patch, MSITE-604.tgz
>
>
> My distribution management section looks like:
> {code}
> <distributionManagement>
>    <site>
>        <id>${acme-corporate-pom.siteRepositoryId}</id>
>        <url>${acme-corporate-pom.siteRepositoryUrl}</url>
>    </site>
> </distributionManagement>
> {code}
> Where the default property values are defined in the pom:
> {code}
> <properties>
>     <acme-corporate-pom.siteRepositoryId>acme-site</acme-corporate-pom.siteRepositoryId>
>     <acme-corporate-pom.siteRepositoryUrl>scp://sites.intranet.acme.com/var/www</acme-corporate-pom.siteRepositoryUrl>
> </properties>
> {code}
> I'm able redefine properties from command line, the provided repository is used instead
default one:
> {code}
> mvn site:site site:deploy -Dacme-corporate-pom.siteRepositoryUrl=scp://somehost/var/www/sites
-Dacme-corporate-pom.siteRepositoryId=somehost
> {code}
> But when I redefine properties in the profile in {{settings.xml}}, they are ignored.
The profile is activated in {{<activeProfiles}} element. 
> It looks, than only m-site-p ignores properties defined in the {{settings.xml}} file.
m-deploy-p recognizes properties as I expected (distribution management section for articats
deployment is configured in similar way to site deployment). 
> --
> Marcin Kuthan
> Maven For Enterprise - http://code.google.com/p/m4enterprise/



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

Mime
View raw message