the ideal situation would be a site:deploy goal that does all the magic incase of scm: dist management site url
anybody interested in trying to do it with me?

Sure, I'd like to help

Robert

Op Tue, 10 Dec 2013 01:54:14 +0100 schreef Hervé BOUTEMY <[email protected]>:

Le mardi 10 décembre 2013 01:05:30 Michael-O a écrit :
Am 2013-12-10 00:58, schrieb Hervé BOUTEMY:
>> <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

I am aware of that. That change was intentional. It conforms to all
other POMs and to the procedure described in the docs. Nothing more,
nothing less.
not really what I wanted to express with "if the component has multiple
modules, locally stage the site:"
but staging in every situation has the advantage that instructions would not
be different for mono-module and multi-module

I don't know what you all prefer: simpler instructions for mono-module (but require a little thinking to know in which situation a build is) or uniform instructions (even if it is a little more complex than absolutely necessary
for mono-modules)

the ideal situation would be a site:deploy goal that does all the magic in
case of scm: dist management site url
anybody interested in trying to do it with me?

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=15
>> 49
>> 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}</checkoutDirect
>> or
>> y> <tryUpdate>true</tryUpdate>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to