Re: [VOTE] Release Maven Javadoc Plugin version 2.8.1

2012-01-18 Thread Olivier Lamy 
+1

--
Olivier
Le 17 janv. 2012 21:19, "John Casey"  a écrit :

> Hi,
>
> We solved 8 issues:
>
> http://jira.codehaus.org/**secure/ReleaseNote.jspa?**
> projectId=11138&version=17354
>
> There are still plenty of issues left in JIRA:
>
> http://jira.codehaus.org/**secure/IssueNavigator.jspa?**
> reset=true&jqlQuery=project+%**3D+MJAVADOC+AND+resolution+%**
> 3D+Unresolved+ORDER+BY+**updated+DESC
>
> Staging repo:
> https://repository.apache.org/**content/repositories/maven-**083/
>
> Staging site (pending sync):
> http://maven.apache.org/**plugins/maven-javadoc-plugin-**2.8.1/
>
>
> Guide to testing staged releases:
> http://maven.apache.org/**guides/development/guide-**testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> Here's my +1
>
> -john
>
> --
> John Casey
> Developer, PMC Chair - Apache Maven (http://maven.apache.org)
> Blog: http://www.johnofalltrades.**name/
>
> --**--**-
> To unsubscribe, e-mail: 
> dev-unsubscribe@maven.apache.**org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: [VOTE] Release Maven Javadoc Plugin version 2.8.1

2012-01-18 Thread Paul Gier 
+1

The new javadoc plugin works fine for me.

On 01/17/2012 02:18 PM, John Casey wrote:
> Hi,
> 
> We solved 8 issues:
> 
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11138&version=17354
> 
> 
> There are still plenty of issues left in JIRA:
> 
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+MJAVADOC+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC
> 
> 
> Staging repo:
> https://repository.apache.org/content/repositories/maven-083/
> 
> Staging site (pending sync):
> http://maven.apache.org/plugins/maven-javadoc-plugin-2.8.1/
> 
> 
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
> 
> Vote open for 72 hours.
> 
> [ ] +1
> [ ] +0
> [ ] -1
> 
> Here's my +1
> 
> -john
> 

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Apache Maven 3.0.4

2012-01-18 Thread Wayne Fay 
+1 binding

Tested on a few work and personal projects with no regressions noted.
Not doing anything particularly complicated in those builds.

Wayne

On Tue, Jan 17, 2012 at 4:14 AM, Olivier Lamy  wrote:
> Hello,
>
> After some RCs, it's now time to cut the release. So I start the vote
> for Apache Maven 3.0.4.
>
> The release notes is available here:
> http://maven.apache.org/docs/3.0.4/release-notes.html
>
> The staging repo: 
> https://repository.apache.org/content/repositories/maven-081/
>
> For convenience builds are available here:
> http://people.apache.org/~olamy/maven/3.0.4/
>
> [+1]
> [0]
> [-1]
>
> Vote open for 72H.
>
> Here my +1
>
> Thanks,
> --
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Apache Maven 3.0.4

2012-01-18 Thread Robert Scholte 

+1

-Robert

On Wed, 18 Jan 2012 08:32:54 +0100, Anders Hammar   
wrote:



+1 non-binding

Tested Snapshot deploy to Codehaus Nexus. Tested that site now works
out-of-the-box (MNG-5221, MNG-5225). Also verified using new Maven
version properties in jar manifest (MNG-4112).

/Anders
On Wed, Jan 18, 2012 at 01:56, Mark Derricutt  wrote:

+1 Non binding.

--
"Great artists are extremely selfish and arrogant things" — Steven  
Wilson,

Porcupine Tree


On Tue, Jan 17, 2012 at 11:14 PM, Olivier Lamy  wrote:


Hello,

After some RCs, it's now time to cut the release. So I start the vote
for Apache Maven 3.0.4.

The release notes is available here:
http://maven.apache.org/docs/3.0.4/release-notes.html

The staging repo:
https://repository.apache.org/content/repositories/maven-081/

For convenience builds are available here:
http://people.apache.org/~olamy/maven/3.0.4/

[+1]
[0]
[-1]

Vote open for 72H.

Here my +1

Thanks,
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org




-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: svn commit: r1232972 - in /maven/surefire/trunk: maven-failsafe-plugin/src/main/java/org/apache/maven/plugin/failsafe/ maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/ maven-s

2012-01-18 Thread John Casey 

On 1/18/12 4:33 PM, John Casey wrote:

On 1/18/12 2:01 PM, Stephen Connolly wrote:

Do we need corresponding tests for this on failsafe


Yeah, probably. I'll take a look at that today/tomorrow. I'm working on
SUREFIRE-803 now, and having some trouble getting the ITs to find the
failsafe plugin in the build...I suppose figuring that out will help my
ability to test this too.


Not sure whether this is cool or not, but I added a dependency on the 
failsafe plugin to the surefire-setup-integration-tests module. After 
doing this, it appears that the failsafe plugin is available for testing.


Of course, all of this is in my Git branch (I haven't migrated it back 
to trunk yet).




-j



- Stephen

---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct result of using swype to type on
the
screen
On Jan 18, 2012 5:54 p.m., wrote:


Author: jdcasey
Date: Wed Jan 18 17:53:39 2012
New Revision: 1232972

URL: http://svn.apache.org/viewvc?rev=1232972&view=rev
Log:
[SUREFIRE-806] Detect when multiple test executions are configured,
and if
only a single execution is present, use specified tests for includes (if
they're available), which is the old behavior. If multiple test
executions
are specified, then use the specified tests as a filter for the existing
includes/excludes, to make sure each specified test executes in the
appropriate configuration.

Also, adding three integration tests to verify these include/exclude
conditions, plus the functioning of the new failIfNoSpecifiedTests
parameter.

Added:

maven/surefire/trunk/surefire-integration-tests/src/test/java/org/apache/maven/surefire/its/CheckSingleTestIT.java.orig


maven/surefire/trunk/surefire-integration-tests/src/test/java/org/apache/maven/surefire/its/jiras/Surefire806SpecifiedTestControlsIT.java

(with props)

maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-multi/


maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-multi/pom.xml

(with props)

maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-multi/src/


maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-multi/src/test/


maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-multi/src/test/java/


maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-multi/src/test/java/defaultConfiguration/


maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-multi/src/test/java/defaultConfiguration/FirstTest.java

(with props)

maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-multi/src/test/java/defaultConfiguration/FourthTest.java

(with props)

maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-multi/src/test/java/defaultConfiguration/SecondTest.java

(with props)

maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-multi/src/test/java/defaultConfiguration/ThirdTest.java

(with props)

maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-single/


maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-single/pom.xml

(with props)

maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-single/src/


maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-single/src/test/


maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-single/src/test/java/


maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-single/src/test/java/defaultConfiguration/


maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-single/src/test/java/defaultConfiguration/FirstTest.java

(with props)

maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-single/src/test/java/defaultConfiguration/FourthTest.java

(with props)

maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-single/src/test/java/defaultConfiguration/SecondTest.java

(with props)

maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-single/src/test/java/defaultConfiguration/ThirdTest.java

(with props)
Modified:

maven/surefire/trunk/maven-failsafe-plugin/src/main/java/org/apache/maven/plugin/failsafe/IntegrationTestMojo.java


maven/surefire/trunk/maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/AbstractSurefireMojo.java


maven/surefire/trunk/maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/SurefireExecutionParameters.java


maven/surefire/trunk

Re: svn commit: r1232972 - in /maven/surefire/trunk: maven-failsafe-plugin/src/main/java/org/apache/maven/plugin/failsafe/ maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/ maven-s

2012-01-18 Thread John Casey 

On 1/18/12 2:01 PM, Stephen Connolly wrote:

Do we need corresponding tests for this on failsafe


Yeah, probably. I'll take a look at that today/tomorrow. I'm working on 
SUREFIRE-803 now, and having some trouble getting the ITs to find the 
failsafe plugin in the build...I suppose figuring that out will help my 
ability to test this too.


-j



- Stephen

---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct result of using swype to type on the
screen
On Jan 18, 2012 5:54 p.m.,  wrote:


Author: jdcasey
Date: Wed Jan 18 17:53:39 2012
New Revision: 1232972

URL: http://svn.apache.org/viewvc?rev=1232972&view=rev
Log:
[SUREFIRE-806] Detect when multiple test executions are configured, and if
only a single execution is present, use specified tests for includes (if
they're available), which is the old behavior. If multiple test executions
are specified, then use the specified tests as a filter for the existing
includes/excludes, to make sure each specified test executes in the
appropriate configuration.

Also, adding three integration tests to verify these include/exclude
conditions, plus the functioning of the new failIfNoSpecifiedTests
parameter.

Added:

  
maven/surefire/trunk/surefire-integration-tests/src/test/java/org/apache/maven/surefire/its/CheckSingleTestIT.java.orig

  
maven/surefire/trunk/surefire-integration-tests/src/test/java/org/apache/maven/surefire/its/jiras/Surefire806SpecifiedTestControlsIT.java
   (with props)

  
maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-multi/

  
maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-multi/pom.xml
   (with props)

  
maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-multi/src/

  
maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-multi/src/test/

  
maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-multi/src/test/java/

  
maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-multi/src/test/java/defaultConfiguration/

  
maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-multi/src/test/java/defaultConfiguration/FirstTest.java
   (with props)

  
maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-multi/src/test/java/defaultConfiguration/FourthTest.java
   (with props)

  
maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-multi/src/test/java/defaultConfiguration/SecondTest.java
   (with props)

  
maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-multi/src/test/java/defaultConfiguration/ThirdTest.java
   (with props)

  
maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-single/

  
maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-single/pom.xml
   (with props)

  
maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-single/src/

  
maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-single/src/test/

  
maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-single/src/test/java/

  
maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-single/src/test/java/defaultConfiguration/

  
maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-single/src/test/java/defaultConfiguration/FirstTest.java
   (with props)

  
maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-single/src/test/java/defaultConfiguration/FourthTest.java
   (with props)

  
maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-single/src/test/java/defaultConfiguration/SecondTest.java
   (with props)

  
maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-single/src/test/java/defaultConfiguration/ThirdTest.java
   (with props)
Modified:

  
maven/surefire/trunk/maven-failsafe-plugin/src/main/java/org/apache/maven/plugin/failsafe/IntegrationTestMojo.java

  
maven/surefire/trunk/maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/AbstractSurefireMojo.java

  
maven/surefire/trunk/maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/SurefireExecutionParameters.java

  
maven/surefire/trunk/maven-surefire-plugin/src/main/java/org/apache/maven/plugin/surefire/SurefirePlugin.java

  
maven/surefire/trunk/surefire-integration-tests/src/test/java/org/apache/maven/surefire/its/fixture/SurefireLauncher.java

Modified:
maven/surefire/trunk/maven-fail

[VOTE] Release Maven Skins version 6 based on RC2

2012-01-18 Thread Simone Tripodi 
Hi all guys,
I am here to propose the RC2 Maven Skins version 6, that includes

 * Maven Application Skin 1.0
 * Maven Default Skin 1.1
 * Maven Classic Skin 1.1
 * Maven Stylus Skin 1.4
 * Maven Fluido Skin 1.1

We solved 16 
issues:http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=project%20=%20MSKINS%20AND%20fixVersion%20in%20(%22fluido-1.1%22,%20%22application-1.0%22,%20%22default-1.1%22,%20%22stylus-1.4%22,%20%22classic-1.1%22)%20ORDER%20BY%20component,%20key

There is still one issues left in
JIRA:http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=project%20=%20MSKINS%20AND%20status%20=%20Open


Staging repo:

https://repository.apache.org/content/repositories/maven-090/

Staging sites:

http://maven.apache.org/skins/maven-application-skin-1.0/
http://maven.apache.org/skins/maven-default-skin-1.1/
http://maven.apache.org/skins/maven-classic-skin-1.1/
http://maven.apache.org/skins/maven-stylus-skin-1.4/
http://maven.apache.org/skins/maven-fluido-skin-1.1/


"Dank je wel" once again to Robert Scholte and Dennis Lundberg for the
priceless support!

This vote is open for 72 hours and closes on January 21th, at ~8:50pm CET.

[ ] +1 release it
[ ] +0 go ahead I don't care
[ ] -1 no, do not release it because...

Thanks in advance for reviewing!
-Simo

http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: svn commit: r1232972 - in /maven/surefire/trunk: maven-failsafe-plugin/src/main/java/org/apache/maven/plugin/failsafe/ maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/ maven-s

2012-01-18 Thread Stephen Connolly 
Do we need corresponding tests for this on failsafe

- Stephen

---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct result of using swype to type on the
screen
On Jan 18, 2012 5:54 p.m.,  wrote:

> Author: jdcasey
> Date: Wed Jan 18 17:53:39 2012
> New Revision: 1232972
>
> URL: http://svn.apache.org/viewvc?rev=1232972&view=rev
> Log:
> [SUREFIRE-806] Detect when multiple test executions are configured, and if
> only a single execution is present, use specified tests for includes (if
> they're available), which is the old behavior. If multiple test executions
> are specified, then use the specified tests as a filter for the existing
> includes/excludes, to make sure each specified test executes in the
> appropriate configuration.
>
> Also, adding three integration tests to verify these include/exclude
> conditions, plus the functioning of the new failIfNoSpecifiedTests
> parameter.
>
> Added:
>
>  
> maven/surefire/trunk/surefire-integration-tests/src/test/java/org/apache/maven/surefire/its/CheckSingleTestIT.java.orig
>
>  
> maven/surefire/trunk/surefire-integration-tests/src/test/java/org/apache/maven/surefire/its/jiras/Surefire806SpecifiedTestControlsIT.java
>   (with props)
>
>  
> maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-multi/
>
>  
> maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-multi/pom.xml
>   (with props)
>
>  
> maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-multi/src/
>
>  
> maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-multi/src/test/
>
>  
> maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-multi/src/test/java/
>
>  
> maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-multi/src/test/java/defaultConfiguration/
>
>  
> maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-multi/src/test/java/defaultConfiguration/FirstTest.java
>   (with props)
>
>  
> maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-multi/src/test/java/defaultConfiguration/FourthTest.java
>   (with props)
>
>  
> maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-multi/src/test/java/defaultConfiguration/SecondTest.java
>   (with props)
>
>  
> maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-multi/src/test/java/defaultConfiguration/ThirdTest.java
>   (with props)
>
>  
> maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-single/
>
>  
> maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-single/pom.xml
>   (with props)
>
>  
> maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-single/src/
>
>  
> maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-single/src/test/
>
>  
> maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-single/src/test/java/
>
>  
> maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-single/src/test/java/defaultConfiguration/
>
>  
> maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-single/src/test/java/defaultConfiguration/FirstTest.java
>   (with props)
>
>  
> maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-single/src/test/java/defaultConfiguration/FourthTest.java
>   (with props)
>
>  
> maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-single/src/test/java/defaultConfiguration/SecondTest.java
>   (with props)
>
>  
> maven/surefire/trunk/surefire-integration-tests/src/test/resources/surefire-806-specifiedTests-single/src/test/java/defaultConfiguration/ThirdTest.java
>   (with props)
> Modified:
>
>  
> maven/surefire/trunk/maven-failsafe-plugin/src/main/java/org/apache/maven/plugin/failsafe/IntegrationTestMojo.java
>
>  
> maven/surefire/trunk/maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/AbstractSurefireMojo.java
>
>  
> maven/surefire/trunk/maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/SurefireExecutionParameters.java
>
>  
> maven/surefire/trunk/maven-surefire-plugin/src/main/java/org/apache/maven/plugin/surefire/SurefirePlugin.java
>
>  
> maven/surefire/trunk/surefire-integration-tests/src/test/java/org/apache/maven/surefire/its/fixture/SurefireLauncher.java
>
> Modified:
> maven/surefire/trunk/maven-failsafe-plugin/src/main/java/org/apache/maven/plugin/failsafe/IntegrationTestMojo.java
> URL:
> http://svn.apache.org/viewvc/maven/surefire/tru

Re: deploy maven site on SVN

2012-01-18 Thread Olivier Lamy 
2012/1/18 Benson Margulies :
> On Wed, Jan 18, 2012 at 9:22 AM, Simone Tripodi
>  wrote:
>> Salut Arnaud,
>>
>> yes via Git is fast, I am using the
>> org.kathrynhuxtable.maven.wagon:wagon-gitsite and I can confirm it is
>> faster than SVN!
>
>
> Not for really big sites. it takes forever.
agree should be as fast as wagon-scm via git :-).

@Simo
Regarding deploying to asf svn, I tend to say we should have a kind of
server to put a zip and this server must be an app which unzip then
commit to svn.
Something I have in mind is to add in Archiva a feature which could be
able to receive a zipped site then unzip etc... (but that's an other
story :-) ).

>
>>
>> All the best!
>> -Simo
>>
>> http://people.apache.org/~simonetripodi/
>> http://simonetripodi.livejournal.com/
>> http://twitter.com/simonetripodi
>> http://www.99soft.org/
>>
>>
>>
>> 2012/1/18 Arnaud Héritier :
>>> Perhaps if the SCM was GIT instead of SVN it could be faster ?
>>> It's not a short term solution but it can be another reason to use Git ASAP.
>>>
>>> Arnaud
>>>
>>>
>>> On Wed, Jan 18, 2012 at 8:39 AM, Simone Tripodi 
>>> wrote:
>>>
 Hi all!

 thanks for the feedbacks - we are using indeed the Kohsuke's wagon but
 to deploy to ASF svn space it takes almost 3secs/page (it could be an
 issue of my ADSL upload band) but since javadoc is really big, it
 takes too much time :(

 wagon-ssh is still the faster :)

 all the best, have a nice day!
 -Simo

 http://people.apache.org/~simonetripodi/
 http://simonetripodi.livejournal.com/
 http://twitter.com/simonetripodi
 http://www.99soft.org/



 On Wed, Jan 18, 2012 at 2:13 AM, Stephen Connolly
  wrote:
 > if the deps are cat a/b i can see about getting kk to donate the code
 > here... but i think it uses svnkit so probably out of luck. (kk is an asf
 > committer on one of the commons projects, so cla on file)
 >
 > - Stephen
 >
 > ---
 > Sent from my Android phone, so random spelling mistakes, random nonsense
 > words and other nonsense are a direct result of using swype to type on
 the
 > screen
 > On 18 Jan 2012 00:27, "Brett Porter"  wrote:
 >
 >> wagon-svn by Kohsuke is much faster, but both should work.
 >>
 >> Either way, I think the main thing we need to do is make sure repeated
 >> identical executions of the site don't change files needlessly, so that
 the
 >> upload is minimal.
 >>
 >> On 18/01/2012, at 7:04 AM, Olivier Lamy wrote:
 >>
 >> > 2012/1/17 Simone Tripodi :
 >> >> Hi all guys,
 >> >> ASF requirements for new incubating podlings requires that sites are
 >> managed
 >> >>
 >> >>  * via the SCM
 >> >>  * via svnpubsub
 >> >>
 >> >> At Apache Any23 we want to keep the mvn generated site for clear
 >> >> reasons - the problem is that using a 3rd part ftp-wagon the deploy
 >> >> procedure is slow and takes too much time :S
 >> >
 >> > Agree that wagon scm is slow
 >> > (http://maven.apache.org/wagon/wagon-providers/wagon-scm/usage.html)
 >> > as it's a per file deploy/commit.
 >> >
 >> >>
 >> >> Can you suggest us please an automated site-deploy procedure using
 mvn
 >> >> - that doesn't involve manual steps?
 >> >> A turnaround would be svn checking out the target dir, deploying the
 >> >> site there, then committing, but I don't think it is a friendly
 >> >> procedure...
 >> > I don't see better solution :-(
 >> >>
 >> >> Many thanks in advance, all the best
 >> >> -Simo
 >> >>
 >> >> http://people.apache.org/~simonetripodi/
 >> >> http://simonetripodi.livejournal.com/
 >> >> http://twitter.com/simonetripodi
 >> >> http://www.99soft.org/
 >> >>
 >> >> -
 >> >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 >> >> For additional commands, e-mail: dev-h...@maven.apache.org
 >> >>
 >> >
 >> >
 >> >
 >> > --
 >> > Olivier Lamy
 >> > Talend: http://coders.talend.com
 >> > http://twitter.com/olamy | http://linkedin.com/in/olamy
 >> >
 >> > -
 >> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 >> > For additional commands, e-mail: dev-h...@maven.apache.org
 >> >
 >>
 >> --
 >> Brett Porter
 >> br...@apache.org
 >> http://brettporter.wordpress.com/
 >> http://au.linkedin.com/in/brettporter
 >> http://twitter.com/brettporter
 >>
 >>
 >>
 >>
 >>
 >>
 >> -
 >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 >> For additional commands, e-mail: dev-h...@maven.apache.org
 >>
 >>

Re: deploy maven site on SVN

2012-01-18 Thread Benson Margulies 
On Wed, Jan 18, 2012 at 9:22 AM, Simone Tripodi
 wrote:
> Salut Arnaud,
>
> yes via Git is fast, I am using the
> org.kathrynhuxtable.maven.wagon:wagon-gitsite and I can confirm it is
> faster than SVN!


Not for really big sites. it takes forever.

>
> All the best!
> -Simo
>
> http://people.apache.org/~simonetripodi/
> http://simonetripodi.livejournal.com/
> http://twitter.com/simonetripodi
> http://www.99soft.org/
>
>
>
> 2012/1/18 Arnaud Héritier :
>> Perhaps if the SCM was GIT instead of SVN it could be faster ?
>> It's not a short term solution but it can be another reason to use Git ASAP.
>>
>> Arnaud
>>
>>
>> On Wed, Jan 18, 2012 at 8:39 AM, Simone Tripodi 
>> wrote:
>>
>>> Hi all!
>>>
>>> thanks for the feedbacks - we are using indeed the Kohsuke's wagon but
>>> to deploy to ASF svn space it takes almost 3secs/page (it could be an
>>> issue of my ADSL upload band) but since javadoc is really big, it
>>> takes too much time :(
>>>
>>> wagon-ssh is still the faster :)
>>>
>>> all the best, have a nice day!
>>> -Simo
>>>
>>> http://people.apache.org/~simonetripodi/
>>> http://simonetripodi.livejournal.com/
>>> http://twitter.com/simonetripodi
>>> http://www.99soft.org/
>>>
>>>
>>>
>>> On Wed, Jan 18, 2012 at 2:13 AM, Stephen Connolly
>>>  wrote:
>>> > if the deps are cat a/b i can see about getting kk to donate the code
>>> > here... but i think it uses svnkit so probably out of luck. (kk is an asf
>>> > committer on one of the commons projects, so cla on file)
>>> >
>>> > - Stephen
>>> >
>>> > ---
>>> > Sent from my Android phone, so random spelling mistakes, random nonsense
>>> > words and other nonsense are a direct result of using swype to type on
>>> the
>>> > screen
>>> > On 18 Jan 2012 00:27, "Brett Porter"  wrote:
>>> >
>>> >> wagon-svn by Kohsuke is much faster, but both should work.
>>> >>
>>> >> Either way, I think the main thing we need to do is make sure repeated
>>> >> identical executions of the site don't change files needlessly, so that
>>> the
>>> >> upload is minimal.
>>> >>
>>> >> On 18/01/2012, at 7:04 AM, Olivier Lamy wrote:
>>> >>
>>> >> > 2012/1/17 Simone Tripodi :
>>> >> >> Hi all guys,
>>> >> >> ASF requirements for new incubating podlings requires that sites are
>>> >> managed
>>> >> >>
>>> >> >>  * via the SCM
>>> >> >>  * via svnpubsub
>>> >> >>
>>> >> >> At Apache Any23 we want to keep the mvn generated site for clear
>>> >> >> reasons - the problem is that using a 3rd part ftp-wagon the deploy
>>> >> >> procedure is slow and takes too much time :S
>>> >> >
>>> >> > Agree that wagon scm is slow
>>> >> > (http://maven.apache.org/wagon/wagon-providers/wagon-scm/usage.html)
>>> >> > as it's a per file deploy/commit.
>>> >> >
>>> >> >>
>>> >> >> Can you suggest us please an automated site-deploy procedure using
>>> mvn
>>> >> >> - that doesn't involve manual steps?
>>> >> >> A turnaround would be svn checking out the target dir, deploying the
>>> >> >> site there, then committing, but I don't think it is a friendly
>>> >> >> procedure...
>>> >> > I don't see better solution :-(
>>> >> >>
>>> >> >> Many thanks in advance, all the best
>>> >> >> -Simo
>>> >> >>
>>> >> >> http://people.apache.org/~simonetripodi/
>>> >> >> http://simonetripodi.livejournal.com/
>>> >> >> http://twitter.com/simonetripodi
>>> >> >> http://www.99soft.org/
>>> >> >>
>>> >> >> -
>>> >> >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>>> >> >> For additional commands, e-mail: dev-h...@maven.apache.org
>>> >> >>
>>> >> >
>>> >> >
>>> >> >
>>> >> > --
>>> >> > Olivier Lamy
>>> >> > Talend: http://coders.talend.com
>>> >> > http://twitter.com/olamy | http://linkedin.com/in/olamy
>>> >> >
>>> >> > -
>>> >> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>>> >> > For additional commands, e-mail: dev-h...@maven.apache.org
>>> >> >
>>> >>
>>> >> --
>>> >> Brett Porter
>>> >> br...@apache.org
>>> >> http://brettporter.wordpress.com/
>>> >> http://au.linkedin.com/in/brettporter
>>> >> http://twitter.com/brettporter
>>> >>
>>> >>
>>> >>
>>> >>
>>> >>
>>> >>
>>> >> -
>>> >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>>> >> For additional commands, e-mail: dev-h...@maven.apache.org
>>> >>
>>> >>
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: dev-h...@maven.apache.org
>>>
>>>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@m

Re: deploy maven site on SVN

2012-01-18 Thread Simone Tripodi 
Hi Ant :)

I got a reply from danielsh on JIRA[1] that simpli didn't allow me
publishing the site via scp. I would really appreciate if you could
help me to fix the misunderstanding, if any!!!

Thanks in advance, all the best!
-Simo

[1] https://issues.apache.org/jira/browse/INFRA-4329

http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/



On Wed, Jan 18, 2012 at 10:19 AM, ant elder  wrote:
> On Tue, Jan 17, 2012 at 5:32 PM, Simone Tripodi
>  wrote:
>> Hi all guys,
>> ASF requirements for new incubating podlings requires that sites are managed
>>
>>  * via the SCM
>>  * via svnpubsub
>>
>
> Do you have any links to something that says that, I didn't think
> there were any Incubator rules about what poddlings must do for
> websites.
>
>   ...ant
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: deploy maven site on SVN

2012-01-18 Thread Simone Tripodi 
Salut Arnaud,

yes via Git is fast, I am using the
org.kathrynhuxtable.maven.wagon:wagon-gitsite and I can confirm it is
faster than SVN!

All the best!
-Simo

http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/



2012/1/18 Arnaud Héritier :
> Perhaps if the SCM was GIT instead of SVN it could be faster ?
> It's not a short term solution but it can be another reason to use Git ASAP.
>
> Arnaud
>
>
> On Wed, Jan 18, 2012 at 8:39 AM, Simone Tripodi 
> wrote:
>
>> Hi all!
>>
>> thanks for the feedbacks - we are using indeed the Kohsuke's wagon but
>> to deploy to ASF svn space it takes almost 3secs/page (it could be an
>> issue of my ADSL upload band) but since javadoc is really big, it
>> takes too much time :(
>>
>> wagon-ssh is still the faster :)
>>
>> all the best, have a nice day!
>> -Simo
>>
>> http://people.apache.org/~simonetripodi/
>> http://simonetripodi.livejournal.com/
>> http://twitter.com/simonetripodi
>> http://www.99soft.org/
>>
>>
>>
>> On Wed, Jan 18, 2012 at 2:13 AM, Stephen Connolly
>>  wrote:
>> > if the deps are cat a/b i can see about getting kk to donate the code
>> > here... but i think it uses svnkit so probably out of luck. (kk is an asf
>> > committer on one of the commons projects, so cla on file)
>> >
>> > - Stephen
>> >
>> > ---
>> > Sent from my Android phone, so random spelling mistakes, random nonsense
>> > words and other nonsense are a direct result of using swype to type on
>> the
>> > screen
>> > On 18 Jan 2012 00:27, "Brett Porter"  wrote:
>> >
>> >> wagon-svn by Kohsuke is much faster, but both should work.
>> >>
>> >> Either way, I think the main thing we need to do is make sure repeated
>> >> identical executions of the site don't change files needlessly, so that
>> the
>> >> upload is minimal.
>> >>
>> >> On 18/01/2012, at 7:04 AM, Olivier Lamy wrote:
>> >>
>> >> > 2012/1/17 Simone Tripodi :
>> >> >> Hi all guys,
>> >> >> ASF requirements for new incubating podlings requires that sites are
>> >> managed
>> >> >>
>> >> >>  * via the SCM
>> >> >>  * via svnpubsub
>> >> >>
>> >> >> At Apache Any23 we want to keep the mvn generated site for clear
>> >> >> reasons - the problem is that using a 3rd part ftp-wagon the deploy
>> >> >> procedure is slow and takes too much time :S
>> >> >
>> >> > Agree that wagon scm is slow
>> >> > (http://maven.apache.org/wagon/wagon-providers/wagon-scm/usage.html)
>> >> > as it's a per file deploy/commit.
>> >> >
>> >> >>
>> >> >> Can you suggest us please an automated site-deploy procedure using
>> mvn
>> >> >> - that doesn't involve manual steps?
>> >> >> A turnaround would be svn checking out the target dir, deploying the
>> >> >> site there, then committing, but I don't think it is a friendly
>> >> >> procedure...
>> >> > I don't see better solution :-(
>> >> >>
>> >> >> Many thanks in advance, all the best
>> >> >> -Simo
>> >> >>
>> >> >> http://people.apache.org/~simonetripodi/
>> >> >> http://simonetripodi.livejournal.com/
>> >> >> http://twitter.com/simonetripodi
>> >> >> http://www.99soft.org/
>> >> >>
>> >> >> -
>> >> >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> >> >> For additional commands, e-mail: dev-h...@maven.apache.org
>> >> >>
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > Olivier Lamy
>> >> > Talend: http://coders.talend.com
>> >> > http://twitter.com/olamy | http://linkedin.com/in/olamy
>> >> >
>> >> > -
>> >> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> >> > For additional commands, e-mail: dev-h...@maven.apache.org
>> >> >
>> >>
>> >> --
>> >> Brett Porter
>> >> br...@apache.org
>> >> http://brettporter.wordpress.com/
>> >> http://au.linkedin.com/in/brettporter
>> >> http://twitter.com/brettporter
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> -
>> >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> >> For additional commands, e-mail: dev-h...@maven.apache.org
>> >>
>> >>
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>>

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Where Do Full System Integration Tests Belong...?

2012-01-18 Thread Olivier Lamy 
Hello,
I tend to say wagon-scm is very low on unit/it tests.
Sources are here:
http://svn.apache.org/repos/asf/maven/wagon/trunk/wagon-providers/wagon-scm/

BTW I think it's a *very* slow mode to publish a maven site.
Regarding it test, the best is probably to provide a sample project
which reproduce the issue.

2012/1/18 Robert Burrell Donkin :
> Hi
>
> Rat now has a variety of components built using a variety of tools in
> a variety of languages.We're looking to move to Apache CMS at the
> project level, integrating Maven site builds into subversion. The
> extension mechanism plugging subversion into wagon scm seems to be a
> little buggy. Easier to explain with an integration test than in words
> on a bug report, and given an integration test we'd probably be able
> to come up with a patch.
>
> I'm a little confused where integration tests which cover multiple
> pluggable extensible elements in Maven should live, and so a little
> uncertain about which component to target for submission. Does Maven
> have a continuous-delivery-style downstream bank of course grain
> integration tests? Other ideas?
>
> Robert
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>



-- 
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: deploy maven site on SVN

2012-01-18 Thread ant elder 
On Tue, Jan 17, 2012 at 5:32 PM, Simone Tripodi
 wrote:
> Hi all guys,
> ASF requirements for new incubating podlings requires that sites are managed
>
>  * via the SCM
>  * via svnpubsub
>

Do you have any links to something that says that, I didn't think
there were any Incubator rules about what poddlings must do for
websites.

   ...ant

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Where Do Full System Integration Tests Belong...?

2012-01-18 Thread Robert Burrell Donkin 
Hi

Rat now has a variety of components built using a variety of tools in
a variety of languages.We're looking to move to Apache CMS at the
project level, integrating Maven site builds into subversion. The
extension mechanism plugging subversion into wagon scm seems to be a
little buggy. Easier to explain with an integration test than in words
on a bug report, and given an integration test we'd probably be able
to come up with a patch.

I'm a little confused where integration tests which cover multiple
pluggable extensible elements in Maven should live, and so a little
uncertain about which component to target for submission. Does Maven
have a continuous-delivery-style downstream bank of course grain
integration tests? Other ideas?

Robert

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: deploy maven site on SVN

2012-01-18 Thread Arnaud Héritier 
Perhaps if the SCM was GIT instead of SVN it could be faster ?
It's not a short term solution but it can be another reason to use Git ASAP.

Arnaud


On Wed, Jan 18, 2012 at 8:39 AM, Simone Tripodi wrote:

> Hi all!
>
> thanks for the feedbacks - we are using indeed the Kohsuke's wagon but
> to deploy to ASF svn space it takes almost 3secs/page (it could be an
> issue of my ADSL upload band) but since javadoc is really big, it
> takes too much time :(
>
> wagon-ssh is still the faster :)
>
> all the best, have a nice day!
> -Simo
>
> http://people.apache.org/~simonetripodi/
> http://simonetripodi.livejournal.com/
> http://twitter.com/simonetripodi
> http://www.99soft.org/
>
>
>
> On Wed, Jan 18, 2012 at 2:13 AM, Stephen Connolly
>  wrote:
> > if the deps are cat a/b i can see about getting kk to donate the code
> > here... but i think it uses svnkit so probably out of luck. (kk is an asf
> > committer on one of the commons projects, so cla on file)
> >
> > - Stephen
> >
> > ---
> > Sent from my Android phone, so random spelling mistakes, random nonsense
> > words and other nonsense are a direct result of using swype to type on
> the
> > screen
> > On 18 Jan 2012 00:27, "Brett Porter"  wrote:
> >
> >> wagon-svn by Kohsuke is much faster, but both should work.
> >>
> >> Either way, I think the main thing we need to do is make sure repeated
> >> identical executions of the site don't change files needlessly, so that
> the
> >> upload is minimal.
> >>
> >> On 18/01/2012, at 7:04 AM, Olivier Lamy wrote:
> >>
> >> > 2012/1/17 Simone Tripodi :
> >> >> Hi all guys,
> >> >> ASF requirements for new incubating podlings requires that sites are
> >> managed
> >> >>
> >> >>  * via the SCM
> >> >>  * via svnpubsub
> >> >>
> >> >> At Apache Any23 we want to keep the mvn generated site for clear
> >> >> reasons - the problem is that using a 3rd part ftp-wagon the deploy
> >> >> procedure is slow and takes too much time :S
> >> >
> >> > Agree that wagon scm is slow
> >> > (http://maven.apache.org/wagon/wagon-providers/wagon-scm/usage.html)
> >> > as it's a per file deploy/commit.
> >> >
> >> >>
> >> >> Can you suggest us please an automated site-deploy procedure using
> mvn
> >> >> - that doesn't involve manual steps?
> >> >> A turnaround would be svn checking out the target dir, deploying the
> >> >> site there, then committing, but I don't think it is a friendly
> >> >> procedure...
> >> > I don't see better solution :-(
> >> >>
> >> >> Many thanks in advance, all the best
> >> >> -Simo
> >> >>
> >> >> http://people.apache.org/~simonetripodi/
> >> >> http://simonetripodi.livejournal.com/
> >> >> http://twitter.com/simonetripodi
> >> >> http://www.99soft.org/
> >> >>
> >> >> -
> >> >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> >> >> For additional commands, e-mail: dev-h...@maven.apache.org
> >> >>
> >> >
> >> >
> >> >
> >> > --
> >> > Olivier Lamy
> >> > Talend: http://coders.talend.com
> >> > http://twitter.com/olamy | http://linkedin.com/in/olamy
> >> >
> >> > -
> >> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> >> > For additional commands, e-mail: dev-h...@maven.apache.org
> >> >
> >>
> >> --
> >> Brett Porter
> >> br...@apache.org
> >> http://brettporter.wordpress.com/
> >> http://au.linkedin.com/in/brettporter
> >> http://twitter.com/brettporter
> >>
> >>
> >>
> >>
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> >> For additional commands, e-mail: dev-h...@maven.apache.org
> >>
> >>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: [site] site.xml head/footer inheritance

2012-01-18 Thread Simone Tripodi 
Hi again,
just to let you know the issue is DOXIASITETOOLS-65
Thanks a lot in advance for your help!!!
All the best,
-Simo

http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/



On Wed, Jan 18, 2012 at 9:31 AM, Simone Tripodi
 wrote:
> Hi Lukas!
>
> thanks for your feedback, I'm filling the issue right now!
>
> All the best, have a nice day,
> -Simo
>
> http://people.apache.org/~simonetripodi/
> http://simonetripodi.livejournal.com/
> http://twitter.com/simonetripodi
> http://www.99soft.org/
>
>
>
> On Wed, Jan 18, 2012 at 8:49 AM, Lukas Theussl  wrote:
>>
>> A quick look at the source code shows that the footer is not taken care of
>> in doxia-decoration-model's DefaultDecorationModelInheritanceAssembler. The
>> footer was only introduced in the last doxia release and this was apparently
>> overlooked. So the only thing to do is file an issue... :)
>>
>> -Lukas
>>
>>
>> Simone Tripodi wrote:
>>>
>>> Hi all guys,
>>>
>>> I am having troubles with the skin (lst check before re-proposing the
>>> skins releases) and while trying to apply fluido on Apache Commons I
>>> noticed that, attaching a site.xml descriptor to a parent, while the
>>> body.head element is inherited from cildren, body.footer is not.
>>>
>>> Did I miss something or this is the right behavior? Is there something
>>> to set or I have to provide an additional feature to the skin?
>>>
>>> Many thanks in advance, all the best!
>>> -Simo
>>>
>>> http://people.apache.org/~simonetripodi/
>>> http://simonetripodi.livejournal.com/
>>> http://twitter.com/simonetripodi
>>> http://www.99soft.org/
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: dev-h...@maven.apache.org
>>>
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [site] site.xml head/footer inheritance

2012-01-18 Thread Simone Tripodi 
Hi Lukas!

thanks for your feedback, I'm filling the issue right now!

All the best, have a nice day,
-Simo

http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/



On Wed, Jan 18, 2012 at 8:49 AM, Lukas Theussl  wrote:
>
> A quick look at the source code shows that the footer is not taken care of
> in doxia-decoration-model's DefaultDecorationModelInheritanceAssembler. The
> footer was only introduced in the last doxia release and this was apparently
> overlooked. So the only thing to do is file an issue... :)
>
> -Lukas
>
>
> Simone Tripodi wrote:
>>
>> Hi all guys,
>>
>> I am having troubles with the skin (lst check before re-proposing the
>> skins releases) and while trying to apply fluido on Apache Commons I
>> noticed that, attaching a site.xml descriptor to a parent, while the
>> body.head element is inherited from cildren, body.footer is not.
>>
>> Did I miss something or this is the right behavior? Is there something
>> to set or I have to provide an additional feature to the skin?
>>
>> Many thanks in advance, all the best!
>> -Simo
>>
>> http://people.apache.org/~simonetripodi/
>> http://simonetripodi.livejournal.com/
>> http://twitter.com/simonetripodi
>> http://www.99soft.org/
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org