> <content>${project.build.directory}/staging/${maven.site.path}</content>
is not really necessary here, since skins are never multi-module, then no need
to site:stage
that's not a blocking issue, since it will work: just need to do extra
site:stage step, not usually needed
Regards,
Hervé
Le lundi 9 décembre 2013 14:08:29 [email protected] a écrit :
> Author: michaelo
> Date: Mon Dec 9 14:08:28 2013
> New Revision: 1549574
>
> URL: http://svn.apache.org/r1549574
> Log:
> Align ${maven.site.path} and <content> style with the rest of the Maven
> components.
>
> Modified:
> maven/skins/trunk/maven-skins/pom.xml
>
> Modified: maven/skins/trunk/maven-skins/pom.xml
> URL:
> http://svn.apache.org/viewvc/maven/skins/trunk/maven-skins/pom.xml?rev=1549
> 574&r1=1549573&r2=1549574&view=diff
> ===========================================================================
> === --- maven/skins/trunk/maven-skins/pom.xml (original)
> +++ maven/skins/trunk/maven-skins/pom.xml Mon Dec 9 14:08:28 2013
> @@ -60,7 +60,7 @@ under the License.
> </distributionManagement>
>
> <properties>
> -
> <maven.site.path>skins-archives/${project.artifactId}-LATEST</maven.site.pa
> th> +
> <maven.site.path>skins-archives/maven-skins-LATEST</maven.site.path>
> <sitePluginVersion>3.3</sitePluginVersion>
> </properties>
>
> @@ -91,7 +91,7 @@ under the License.
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-scm-publish-plugin</artifactId>
> <configuration>
> - <content>${project.reporting.outputDirectory}</content>
> +
> <content>${project.build.directory}/staging/${maven.site.path}</content>
> <pubScmUrl>scm:svn:https://svn.apache.org/repos/infra/websites/production/m
> aven/content/${maven.site.path}</pubScmUrl>
> <checkoutDirectory>${maven.site.cache}/${maven.site.path}</checkoutDirector
> y> <tryUpdate>true</tryUpdate>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
