On Wed, Nov 28, 2012 at 11:57 AM, Dominik Psenner <dpsen...@gmail.com> wrote:
> *hm* .. using maven 2.2.1 it seems to work flawlessly. At least it does not
> produce warnings. ;-) I checked the site and mostly only the dates are
> changed now. *yay!*

mvn 2 + 3 do need different things in the reporting section. Maybe we
(you? ;-)) should look into migrating to m3 for log4net

> The last problem I have now are the line endings in the generated site. I am
> on windows and I suppose the svn expects \n instead of \r\n line endings?

I wrote a blog on that because it bugged me often too:
http://www.grobmeier.de/svn-properties-client-config-05072009.html
Common usus is native style i think

> Will the site automatically be updated once I commit the updated site?

If you commit it to the svn site branch, then yes. It should be there
pretty quickly as it is picked up by svnpubsub

Cheers
Christian

>>-----Original Message-----
>>From: Dominik Psenner [mailto:dpsen...@gmail.com]
>>Sent: Wednesday, November 28, 2012 11:07 AM
>>To: 'Log4NET Dev'
>>Subject: RE: FW: Add new FAQ entry
>>
>>>Can you check your maven version? There was a change between 2 and 3.
>>>Maybe its related to that.
>>>
>>>mvn --version
>>
>>Apache Maven 3.0.3
>>
>>I found out that the <menu ref="reports"/>-snippet triggers mvn to generate
>>the projec documentation. But nonetheless mvn behaves really odd.
>>
>>When I build it first I get the RAT report. When I build it again I get the
>>Changes and JIRA reports but the RAT report is missing. Building it once
>>more brings back the RAT report but JIRA and Changes are missing again.
>>*huh?!*
>>
>>I am really afraid I could break something not obvious and this is what ist
>>he warning produced by maven:
>>
>>[INFO] Downloading from JIRA at:
>>https://issues.apache.org/jira/secure/IssueNavigator.jspa?view=rss&pid=1069
>>0
>>&statusIds=5&statusIds=6&resolutionIds=1&sorter/field=created&sorter/order=
>>D
>>ESC&sorter/field=priority&sorter/order=DESC&tempMax=100&reset=true&decorato
>>r
>>=none
>>[WARNING]
>>org.apache.maven.plugin.MojoExecutionException: Failed to parse JIRA XML.
>>        at org.apache.maven.plugin.jira.JiraXML.parse(JiraXML.java:132)
>>        at org.apache.maven.plugin.jira.JiraXML.parseXML(JiraXML.java:108)
>>        ...
>>Caused by: org.xml.sax.SAXParseException: The entity name must immediately
>>follow the '&' in the entity reference.
>
>



--
http://www.grobmeier.de
https://www.timeandbill.de

Reply via email to