[jira] (MAVEN-1868) building jira from source and maven error

2012-04-05 Thread samira akhavan (JIRA)
samira akhavan created MAVEN-1868:
-

 Summary: building jira from source and maven error
 Key: MAVEN-1868
 URL: https://jira.codehaus.org/browse/MAVEN-1868
 Project: Maven 1
  Issue Type: Bug
Reporter: samira akhavan
Priority: Critical
 Attachments: build.properties, settings.xml

i am about building jira from source and i should install maven 1 and maven 2.
i folowed from this documentattion: 
http://confluence.atlassian.com/display/JIRA042/Building+JIRA+from+Source

but when i run maven in jira directory i got this error:

You have encountered an unknown error running Maven

when i use maven --info i got this:

|  \/  |__ _Apache__ ___

| |\/| / _` \ V / -_) ' \  ~ intelligent projects ~

|_|  |_\__,_|\_/\___|_||_|  v. 1.0

 

# BEGIN: Which report

Which.version=Which.java:($Revision: 1.2 $) WhichJar.java:($Revision: 1.2 $)

java.version=1.6.0_16

file.encoding=Cp1256

java.ext.dirs=C:\Program Files\Java\jdk1.6.0_16\jre\lib\ext;C:\WINDOWS\Sun\Java\

lib\ext

java.class.path=C:\dev2\test\maven-1.0\lib\forehead-1.0-beta-5.jar

os.name=Windows XP

java.vendor=Sun Microsystems Inc.

sun.boot.class.path=C:\dev2\test\maven-1.0\lib\endorsed\xerces-2.4.0.jar;C:\dev2

\test\maven-1.0\lib\endorsed\xml-apis-1.0.b2.jar;C:\Program Files\Java\jdk1.6.0_

16\jre\lib\resources.jar;C:\Program Files\Java\jdk1.6.0_16\jre\lib\rt.jar;C:\Pro

gram Files\Java\jdk1.6.0_16\jre\lib\sunrsasign.jar;C:\Program Files\Java\jdk1.6.

0_16\jre\lib\jsse.jar;C:\Program Files\Java\jdk1.6.0_16\jre\lib\jce.jar;C:\Progr

am Files\Java\jdk1.6.0_16\jre\lib\charsets.jar;C:\Program Files\Java\jdk1.6.0_16

\jre\classes

java.runtime.name=Java(TM) SE Runtime Environment

#   END: Which report

 

Installed plugins:

  maven-abbot-plugin-1.0

  maven-announcement-plugin-1.2

  maven-ant-plugin-1.7

  maven-antlr-plugin-1.2.1

  maven-appserver-plugin-2.0

  maven-artifact-plugin-1.4

  maven-ashkelon-plugin-1.2

  maven-aspectj-plugin-3.1.1

  maven-aspectwerkz-plugin-1.2

  maven-caller-plugin-1.1

  maven-castor-plugin-1.2

  maven-changelog-plugin-1.7.1

  maven-changes-plugin-1.5

  maven-checkstyle-plugin-2.4.1

  maven-clean-plugin-1.3

  maven-clover-plugin-1.5

  maven-console-plugin-1.1

  maven-cruisecontrol-plugin-1.4

  maven-dashboard-plugin-1.3

  maven-developer-activity-plugin-1.5

  maven-dist-plugin-1.6

  maven-docbook-plugin-1.2

  maven-ear-plugin-1.5

  maven-eclipse-plugin-1.7

  maven-ejb-plugin-1.5

  maven-faq-plugin-1.4

  maven-file-activity-plugin-1.5

  maven-genapp-plugin-2.2

  maven-gump-plugin-1.4

  maven-hibernate-plugin-1.1

  maven-html2xdoc-plugin-1.3

  maven-idea-plugin-1.5

  maven-j2ee-plugin-1.5

  maven-jalopy-plugin-1.3

  maven-jar-plugin-1.6

  maven-java-plugin-1.4

  maven-javacc-plugin-1.1

  maven-javadoc-plugin-1.6.1

  maven-jboss-plugin-1.5

  maven-jbuilder-plugin-1.5

  maven-jcoverage-plugin-1.0.7

  maven-jdee-plugin-1.1

  maven-jdepend-plugin-1.5

  maven-jdeveloper-plugin-1.4

  maven-jdiff-plugin-1.4

  maven-jellydoc-plugin-1.3

  maven-jetty-plugin-1.1

  maven-jira-plugin-1.1.1

  maven-jnlp-plugin-1.4

  maven-junit-doclet-plugin-1.2

  maven-junit-report-plugin-1.5

  maven-jxr-plugin-1.4.1

  maven-latex-plugin-1.4.1

  maven-latka-plugin-1.4.1

  maven-license-plugin-1.2

  maven-linkcheck-plugin-1.3.2

  maven-multichanges-plugin-1.1

  maven-multiproject-plugin-1.3.1

  maven-native-plugin-1.1

  maven-nsis-plugin-1.1

  maven-pdf-plugin-2.1

  maven-plugin-plugin-1.5.1

  maven-pmd-plugin-1.5

  maven-pom-plugin-1.4.1

  maven-rar-plugin-1.0

  maven-release-plugin-1.4

  maven-repository-plugin-1.2

  maven-scm-plugin-1.4

  maven-shell-plugin-1.1

  maven-simian-plugin-1.4

  maven-site-plugin-1.5.1

  maven-struts-plugin-1.3

  maven-tasklist-plugin-2.3

  maven-test-plugin-1.6.2

  maven-tjdo-plugin-1.0.0

  maven-uberjar-plugin-1.2

  maven-vdoclet-plugin-1.2

  maven-war-plugin-1.6

  maven-webserver-plugin-2.0

  maven-wizard-plugin-1.1

  maven-xdoc-plugin-1.8

Exception reading build.properties: C:\Documents and 
Settings\S.Akhavan\build.properties (The system cannot find the file specified)

Home Build properties: {}
i attach build.properties in jira directory and settings.xml in .m2 directory. 
i just copy them and dont make any modification.perhaps in did wrong in this 
part.

how can i resolve this problem?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (MAVEN-1868) building jira from source and maven error

2012-04-05 Thread samira akhavan (JIRA)

[ 
https://jira.codehaus.org/browse/MAVEN-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=295883#comment-295883
 ] 

samira akhavan commented on MAVEN-1868:
---

if it is needed i can explain step by step of my installation?!

 building jira from source and maven error
 -

 Key: MAVEN-1868
 URL: https://jira.codehaus.org/browse/MAVEN-1868
 Project: Maven 1
  Issue Type: Bug
Reporter: samira akhavan
Priority: Critical
 Attachments: build.properties, settings.xml


 i am about building jira from source and i should install maven 1 and maven 2.
 i folowed from this documentattion: 
 http://confluence.atlassian.com/display/JIRA042/Building+JIRA+from+Source
 but when i run maven in jira directory i got this error:
 You have encountered an unknown error running Maven
 when i use maven --info i got this:
 |  \/  |__ _Apache__ ___
 | |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
 |_|  |_\__,_|\_/\___|_||_|  v. 1.0
  
 # BEGIN: Which report
 Which.version=Which.java:($Revision: 1.2 $) WhichJar.java:($Revision: 1.2 $)
 java.version=1.6.0_16
 file.encoding=Cp1256
 java.ext.dirs=C:\Program 
 Files\Java\jdk1.6.0_16\jre\lib\ext;C:\WINDOWS\Sun\Java\
 lib\ext
 java.class.path=C:\dev2\test\maven-1.0\lib\forehead-1.0-beta-5.jar
 os.name=Windows XP
 java.vendor=Sun Microsystems Inc.
 sun.boot.class.path=C:\dev2\test\maven-1.0\lib\endorsed\xerces-2.4.0.jar;C:\dev2
 \test\maven-1.0\lib\endorsed\xml-apis-1.0.b2.jar;C:\Program 
 Files\Java\jdk1.6.0_
 16\jre\lib\resources.jar;C:\Program 
 Files\Java\jdk1.6.0_16\jre\lib\rt.jar;C:\Pro
 gram Files\Java\jdk1.6.0_16\jre\lib\sunrsasign.jar;C:\Program 
 Files\Java\jdk1.6.
 0_16\jre\lib\jsse.jar;C:\Program 
 Files\Java\jdk1.6.0_16\jre\lib\jce.jar;C:\Progr
 am Files\Java\jdk1.6.0_16\jre\lib\charsets.jar;C:\Program 
 Files\Java\jdk1.6.0_16
 \jre\classes
 java.runtime.name=Java(TM) SE Runtime Environment
 #   END: Which report
  
 Installed plugins:
   maven-abbot-plugin-1.0
   maven-announcement-plugin-1.2
   maven-ant-plugin-1.7
   maven-antlr-plugin-1.2.1
   maven-appserver-plugin-2.0
   maven-artifact-plugin-1.4
   maven-ashkelon-plugin-1.2
   maven-aspectj-plugin-3.1.1
   maven-aspectwerkz-plugin-1.2
   maven-caller-plugin-1.1
   maven-castor-plugin-1.2
   maven-changelog-plugin-1.7.1
   maven-changes-plugin-1.5
   maven-checkstyle-plugin-2.4.1
   maven-clean-plugin-1.3
   maven-clover-plugin-1.5
   maven-console-plugin-1.1
   maven-cruisecontrol-plugin-1.4
   maven-dashboard-plugin-1.3
   maven-developer-activity-plugin-1.5
   maven-dist-plugin-1.6
   maven-docbook-plugin-1.2
   maven-ear-plugin-1.5
   maven-eclipse-plugin-1.7
   maven-ejb-plugin-1.5
   maven-faq-plugin-1.4
   maven-file-activity-plugin-1.5
   maven-genapp-plugin-2.2
   maven-gump-plugin-1.4
   maven-hibernate-plugin-1.1
   maven-html2xdoc-plugin-1.3
   maven-idea-plugin-1.5
   maven-j2ee-plugin-1.5
   maven-jalopy-plugin-1.3
   maven-jar-plugin-1.6
   maven-java-plugin-1.4
   maven-javacc-plugin-1.1
   maven-javadoc-plugin-1.6.1
   maven-jboss-plugin-1.5
   maven-jbuilder-plugin-1.5
   maven-jcoverage-plugin-1.0.7
   maven-jdee-plugin-1.1
   maven-jdepend-plugin-1.5
   maven-jdeveloper-plugin-1.4
   maven-jdiff-plugin-1.4
   maven-jellydoc-plugin-1.3
   maven-jetty-plugin-1.1
   maven-jira-plugin-1.1.1
   maven-jnlp-plugin-1.4
   maven-junit-doclet-plugin-1.2
   maven-junit-report-plugin-1.5
   maven-jxr-plugin-1.4.1
   maven-latex-plugin-1.4.1
   maven-latka-plugin-1.4.1
   maven-license-plugin-1.2
   maven-linkcheck-plugin-1.3.2
   maven-multichanges-plugin-1.1
   maven-multiproject-plugin-1.3.1
   maven-native-plugin-1.1
   maven-nsis-plugin-1.1
   maven-pdf-plugin-2.1
   maven-plugin-plugin-1.5.1
   maven-pmd-plugin-1.5
   maven-pom-plugin-1.4.1
   maven-rar-plugin-1.0
   maven-release-plugin-1.4
   maven-repository-plugin-1.2
   maven-scm-plugin-1.4
   maven-shell-plugin-1.1
   maven-simian-plugin-1.4
   maven-site-plugin-1.5.1
   maven-struts-plugin-1.3
   maven-tasklist-plugin-2.3
   maven-test-plugin-1.6.2
   maven-tjdo-plugin-1.0.0
   maven-uberjar-plugin-1.2
   maven-vdoclet-plugin-1.2
   maven-war-plugin-1.6
   maven-webserver-plugin-2.0
   maven-wizard-plugin-1.1
   maven-xdoc-plugin-1.8
 Exception reading build.properties: C:\Documents and 
 Settings\S.Akhavan\build.properties (The system cannot find the file 
 specified)
 Home Build properties: {}
 i attach build.properties in jira directory and settings.xml in .m2 
 directory. i just copy them and dont make any modification.perhaps in did 
 wrong in this part.
 how can i resolve this problem?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on 

[jira] (SUREFIRE-857) Non-ASCII source and name in ReportEntry are escaped unicode on fork.

2012-04-05 Thread kayakiss (JIRA)
kayakiss created SUREFIRE-857:
-

 Summary: Non-ASCII source and name in ReportEntry are escaped 
unicode on fork.
 Key: SUREFIRE-857
 URL: https://jira.codehaus.org/browse/SUREFIRE-857
 Project: Maven Surefire
  Issue Type: Bug
  Components: process forking
Affects Versions: 2.12, 2.11, 2.10, 2.9
Reporter: kayakiss
 Attachments: unescape.patch

Non-ASCII source and name in ReportEntry are escaped unicode on fork. For 
example 'À'(A with grave) is replaced \u00C0.
{noformat}
public class EscapeÀTest {
@Test
public void testÀTest() {
}
}
{noformat}
XML report of this test class is following.
{noformat}
testcase time=0.010 classname=Escape\u00C0Test name=test\u00C0Test
{noformat}
This problem is that 
*org.apache.maven.plugin.surefire.booterclient.outpu.ForkClient* is not 
unescape for ReportEntry source and name. Because these are escaped with 
*org.apache.maven.surefire.booter.ForingRunListener*, *ForkClient* must be 
unescaped.

In the attached patch for 2.12 I fixed this problem.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (MRELEASE-745) Property suppressCommitBeforeBranch also suppresses trunk commit AFTER branching.

2012-04-05 Thread Stefan Eder (JIRA)

 [ 
https://jira.codehaus.org/browse/MRELEASE-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Eder updated MRELEASE-745:
-

Attachment: maven-release-manager.patch

I switched the phase scm-commit-release with scm-commit-development in 
components-fragment.xml and now it works.

The main difference between those to phases is, that scm-commit-release only 
uses suppressCommitBeforeBranch to determine whether to check in or not. 
Whereas scm-commit-development uses updateWorkingCopyVersions. Therefore I 
think scm-commit-development is the right phase here.

Additionally I provided a patch file which changes the phase and the message 
mentioned in my last post. Can't guarantee that this is 100% right but it works 
for me.

 Property suppressCommitBeforeBranch also suppresses trunk commit AFTER 
 branching.
 -

 Key: MRELEASE-745
 URL: https://jira.codehaus.org/browse/MRELEASE-745
 Project: Maven 2.x Release Plugin
  Issue Type: Bug
  Components: branch
Affects Versions: 2.1
 Environment: Windows (7, Server 2003), Maven 2.2.1, Jenkins 1.420
Reporter: Chris Wilton
 Attachments: maven-release-manager.patch


 I have a multi-module maven project. I create 'release branches' for testing, 
 then once testing is complete, I create the release tag from the branch.
 In order to work around the subversion 1.5.x problem 
 (http://jira.codehaus.org/browse/SCM-515) I have the following properties set:
 suppressCommitBeforeBranch=true
 suppressCommitBeforeTag=true
 remoteTagging=false
 Implicit (as default) values are:
 updateBranchVersions=false
 updateWorkingCopyVersions=true
 The intention is to create a branch with the same pom versions as the trunk, 
 without committing any modifications to the trunk (in order to avoid the SCM 
 section for the branch ending up in the trunk poms), then to bump up the 
 trunk versions and commit them. But although the trunk pom versions are 
 modified, they are not committed.
 I want commit suppressed BEFORE branching, not AFTER, else I have to run 
 release:update-versions afterwards and perform a manual commit, to bump up 
 the trunk versions. I should mention that this is being run as a 
 (parameterized) Jenkins task, so it is not simply a case of manually 
 committing my working copy to the trunk after the branching process is 
 complete.
 Am I doing something wrong?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (MAVEN-1868) building jira from source and maven error

2012-04-05 Thread Dennis Lundberg (JIRA)

[ 
https://jira.codehaus.org/browse/MAVEN-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=295925#comment-295925
 ] 

Dennis Lundberg commented on MAVEN-1868:


Hi,

You can start by upgrading to Maven 1.0.2 which is the last version of Maven 1. 
Please note that Maven 1 is no longer being developed.

You should also contact Atlassian and ask them for help. I find it odd that 
you'd still need Maven 1 to build JIRA today.

 building jira from source and maven error
 -

 Key: MAVEN-1868
 URL: https://jira.codehaus.org/browse/MAVEN-1868
 Project: Maven 1
  Issue Type: Bug
Reporter: samira akhavan
Priority: Critical
 Attachments: build.properties, settings.xml


 i am about building jira from source and i should install maven 1 and maven 2.
 i folowed from this documentattion: 
 http://confluence.atlassian.com/display/JIRA042/Building+JIRA+from+Source
 but when i run maven in jira directory i got this error:
 You have encountered an unknown error running Maven
 when i use maven --info i got this:
 {noformat}
 |  \/  |__ _Apache__ ___
 | |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
 |_|  |_\__,_|\_/\___|_||_|  v. 1.0
 {noformat}
  
 Which report
 {noformat}
 Which.version=Which.java:($Revision: 1.2 $) WhichJar.java:($Revision: 1.2 $)
 java.version=1.6.0_16
 file.encoding=Cp1256
 java.ext.dirs=C:\Program 
 Files\Java\jdk1.6.0_16\jre\lib\ext;C:\WINDOWS\Sun\Java\
 lib\ext
 java.class.path=C:\dev2\test\maven-1.0\lib\forehead-1.0-beta-5.jar
 os.name=Windows XP
 java.vendor=Sun Microsystems Inc.
 sun.boot.class.path=C:\dev2\test\maven-1.0\lib\endorsed\xerces-2.4.0.jar;C:\dev2
 \test\maven-1.0\lib\endorsed\xml-apis-1.0.b2.jar;C:\Program 
 Files\Java\jdk1.6.0_
 16\jre\lib\resources.jar;C:\Program 
 Files\Java\jdk1.6.0_16\jre\lib\rt.jar;C:\Pro
 gram Files\Java\jdk1.6.0_16\jre\lib\sunrsasign.jar;C:\Program 
 Files\Java\jdk1.6.
 0_16\jre\lib\jsse.jar;C:\Program 
 Files\Java\jdk1.6.0_16\jre\lib\jce.jar;C:\Progr
 am Files\Java\jdk1.6.0_16\jre\lib\charsets.jar;C:\Program 
 Files\Java\jdk1.6.0_16
 \jre\classes
 java.runtime.name=Java(TM) SE Runtime Environment
 {noformat}
  
 Installed plugins:
   maven-abbot-plugin-1.0
   maven-announcement-plugin-1.2
   maven-ant-plugin-1.7
   maven-antlr-plugin-1.2.1
   maven-appserver-plugin-2.0
   maven-artifact-plugin-1.4
   maven-ashkelon-plugin-1.2
   maven-aspectj-plugin-3.1.1
   maven-aspectwerkz-plugin-1.2
   maven-caller-plugin-1.1
   maven-castor-plugin-1.2
   maven-changelog-plugin-1.7.1
   maven-changes-plugin-1.5
   maven-checkstyle-plugin-2.4.1
   maven-clean-plugin-1.3
   maven-clover-plugin-1.5
   maven-console-plugin-1.1
   maven-cruisecontrol-plugin-1.4
   maven-dashboard-plugin-1.3
   maven-developer-activity-plugin-1.5
   maven-dist-plugin-1.6
   maven-docbook-plugin-1.2
   maven-ear-plugin-1.5
   maven-eclipse-plugin-1.7
   maven-ejb-plugin-1.5
   maven-faq-plugin-1.4
   maven-file-activity-plugin-1.5
   maven-genapp-plugin-2.2
   maven-gump-plugin-1.4
   maven-hibernate-plugin-1.1
   maven-html2xdoc-plugin-1.3
   maven-idea-plugin-1.5
   maven-j2ee-plugin-1.5
   maven-jalopy-plugin-1.3
   maven-jar-plugin-1.6
   maven-java-plugin-1.4
   maven-javacc-plugin-1.1
   maven-javadoc-plugin-1.6.1
   maven-jboss-plugin-1.5
   maven-jbuilder-plugin-1.5
   maven-jcoverage-plugin-1.0.7
   maven-jdee-plugin-1.1
   maven-jdepend-plugin-1.5
   maven-jdeveloper-plugin-1.4
   maven-jdiff-plugin-1.4
   maven-jellydoc-plugin-1.3
   maven-jetty-plugin-1.1
   maven-jira-plugin-1.1.1
   maven-jnlp-plugin-1.4
   maven-junit-doclet-plugin-1.2
   maven-junit-report-plugin-1.5
   maven-jxr-plugin-1.4.1
   maven-latex-plugin-1.4.1
   maven-latka-plugin-1.4.1
   maven-license-plugin-1.2
   maven-linkcheck-plugin-1.3.2
   maven-multichanges-plugin-1.1
   maven-multiproject-plugin-1.3.1
   maven-native-plugin-1.1
   maven-nsis-plugin-1.1
   maven-pdf-plugin-2.1
   maven-plugin-plugin-1.5.1
   maven-pmd-plugin-1.5
   maven-pom-plugin-1.4.1
   maven-rar-plugin-1.0
   maven-release-plugin-1.4
   maven-repository-plugin-1.2
   maven-scm-plugin-1.4
   maven-shell-plugin-1.1
   maven-simian-plugin-1.4
   maven-site-plugin-1.5.1
   maven-struts-plugin-1.3
   maven-tasklist-plugin-2.3
   maven-test-plugin-1.6.2
   maven-tjdo-plugin-1.0.0
   maven-uberjar-plugin-1.2
   maven-vdoclet-plugin-1.2
   maven-war-plugin-1.6
   maven-webserver-plugin-2.0
   maven-wizard-plugin-1.1
   maven-xdoc-plugin-1.8
 Exception reading build.properties: C:\Documents and 
 Settings\S.Akhavan\build.properties (The system cannot find the file 
 specified)
 Home Build properties: {}
 i attach build.properties in jira directory and settings.xml in .m2 
 directory. i just copy them and dont make any modification.perhaps in did 
 wrong in this part.
 how can i resolve this problem?

--
This message 

[jira] (MAVEN-1868) building jira from source and maven error

2012-04-05 Thread Dennis Lundberg (JIRA)

 [ 
https://jira.codehaus.org/browse/MAVEN-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Lundberg updated MAVEN-1868:
---

Description: 
i am about building jira from source and i should install maven 1 and maven 2.
i folowed from this documentattion: 
http://confluence.atlassian.com/display/JIRA042/Building+JIRA+from+Source

but when i run maven in jira directory i got this error:

You have encountered an unknown error running Maven

when i use maven --info i got this:

{noformat}
|  \/  |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
|_|  |_\__,_|\_/\___|_||_|  v. 1.0

{noformat}
 

Which report
{noformat}

Which.version=Which.java:($Revision: 1.2 $) WhichJar.java:($Revision: 1.2 $)

java.version=1.6.0_16

file.encoding=Cp1256

java.ext.dirs=C:\Program Files\Java\jdk1.6.0_16\jre\lib\ext;C:\WINDOWS\Sun\Java\

lib\ext

java.class.path=C:\dev2\test\maven-1.0\lib\forehead-1.0-beta-5.jar

os.name=Windows XP

java.vendor=Sun Microsystems Inc.

sun.boot.class.path=C:\dev2\test\maven-1.0\lib\endorsed\xerces-2.4.0.jar;C:\dev2

\test\maven-1.0\lib\endorsed\xml-apis-1.0.b2.jar;C:\Program Files\Java\jdk1.6.0_

16\jre\lib\resources.jar;C:\Program Files\Java\jdk1.6.0_16\jre\lib\rt.jar;C:\Pro

gram Files\Java\jdk1.6.0_16\jre\lib\sunrsasign.jar;C:\Program Files\Java\jdk1.6.

0_16\jre\lib\jsse.jar;C:\Program Files\Java\jdk1.6.0_16\jre\lib\jce.jar;C:\Progr

am Files\Java\jdk1.6.0_16\jre\lib\charsets.jar;C:\Program Files\Java\jdk1.6.0_16

\jre\classes

java.runtime.name=Java(TM) SE Runtime Environment
{noformat}

 

Installed plugins:

  maven-abbot-plugin-1.0

  maven-announcement-plugin-1.2

  maven-ant-plugin-1.7

  maven-antlr-plugin-1.2.1

  maven-appserver-plugin-2.0

  maven-artifact-plugin-1.4

  maven-ashkelon-plugin-1.2

  maven-aspectj-plugin-3.1.1

  maven-aspectwerkz-plugin-1.2

  maven-caller-plugin-1.1

  maven-castor-plugin-1.2

  maven-changelog-plugin-1.7.1

  maven-changes-plugin-1.5

  maven-checkstyle-plugin-2.4.1

  maven-clean-plugin-1.3

  maven-clover-plugin-1.5

  maven-console-plugin-1.1

  maven-cruisecontrol-plugin-1.4

  maven-dashboard-plugin-1.3

  maven-developer-activity-plugin-1.5

  maven-dist-plugin-1.6

  maven-docbook-plugin-1.2

  maven-ear-plugin-1.5

  maven-eclipse-plugin-1.7

  maven-ejb-plugin-1.5

  maven-faq-plugin-1.4

  maven-file-activity-plugin-1.5

  maven-genapp-plugin-2.2

  maven-gump-plugin-1.4

  maven-hibernate-plugin-1.1

  maven-html2xdoc-plugin-1.3

  maven-idea-plugin-1.5

  maven-j2ee-plugin-1.5

  maven-jalopy-plugin-1.3

  maven-jar-plugin-1.6

  maven-java-plugin-1.4

  maven-javacc-plugin-1.1

  maven-javadoc-plugin-1.6.1

  maven-jboss-plugin-1.5

  maven-jbuilder-plugin-1.5

  maven-jcoverage-plugin-1.0.7

  maven-jdee-plugin-1.1

  maven-jdepend-plugin-1.5

  maven-jdeveloper-plugin-1.4

  maven-jdiff-plugin-1.4

  maven-jellydoc-plugin-1.3

  maven-jetty-plugin-1.1

  maven-jira-plugin-1.1.1

  maven-jnlp-plugin-1.4

  maven-junit-doclet-plugin-1.2

  maven-junit-report-plugin-1.5

  maven-jxr-plugin-1.4.1

  maven-latex-plugin-1.4.1

  maven-latka-plugin-1.4.1

  maven-license-plugin-1.2

  maven-linkcheck-plugin-1.3.2

  maven-multichanges-plugin-1.1

  maven-multiproject-plugin-1.3.1

  maven-native-plugin-1.1

  maven-nsis-plugin-1.1

  maven-pdf-plugin-2.1

  maven-plugin-plugin-1.5.1

  maven-pmd-plugin-1.5

  maven-pom-plugin-1.4.1

  maven-rar-plugin-1.0

  maven-release-plugin-1.4

  maven-repository-plugin-1.2

  maven-scm-plugin-1.4

  maven-shell-plugin-1.1

  maven-simian-plugin-1.4

  maven-site-plugin-1.5.1

  maven-struts-plugin-1.3

  maven-tasklist-plugin-2.3

  maven-test-plugin-1.6.2

  maven-tjdo-plugin-1.0.0

  maven-uberjar-plugin-1.2

  maven-vdoclet-plugin-1.2

  maven-war-plugin-1.6

  maven-webserver-plugin-2.0

  maven-wizard-plugin-1.1

  maven-xdoc-plugin-1.8

Exception reading build.properties: C:\Documents and 
Settings\S.Akhavan\build.properties (The system cannot find the file specified)

Home Build properties: {}
i attach build.properties in jira directory and settings.xml in .m2 directory. 
i just copy them and dont make any modification.perhaps in did wrong in this 
part.

how can i resolve this problem?

  was:
i am about building jira from source and i should install maven 1 and maven 2.
i folowed from this documentattion: 
http://confluence.atlassian.com/display/JIRA042/Building+JIRA+from+Source

but when i run maven in jira directory i got this error:

You have encountered an unknown error running Maven

when i use maven --info i got this:

|  \/  |__ _Apache__ ___

| |\/| / _` \ V / -_) ' \  ~ intelligent projects ~

|_|  |_\__,_|\_/\___|_||_|  v. 1.0

 

# BEGIN: Which report

Which.version=Which.java:($Revision: 1.2 $) WhichJar.java:($Revision: 1.2 $)

java.version=1.6.0_16

file.encoding=Cp1256

java.ext.dirs=C:\Program Files\Java\jdk1.6.0_16\jre\lib\ext;C:\WINDOWS\Sun\Java\

lib\ext


[jira] (MECLIPSE-459) missing artifact references with pde mode enabled

2012-04-05 Thread David Boden (JIRA)

 [ 
https://jira.codehaus.org/browse/MECLIPSE-459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Boden updated MECLIPSE-459:
-

Attachment: pde.patch.txt

Patch file that's working for me.

 missing artifact references with pde mode enabled
 -

 Key: MECLIPSE-459
 URL: https://jira.codehaus.org/browse/MECLIPSE-459
 Project: Maven 2.x Eclipse Plugin
  Issue Type: Bug
  Components: Core : Dependencies resolution and build path 
 (.classpath), PDE support
Affects Versions: 2.0, 2.1, 2.2, 2.3, 2.4, 2.5, 2.5.1
 Environment: Maven version: 2.0.9
 Java version: 1.5.0_11
 OS name: linux version: 2.6.15-51-686 arch: i386 Family: unix
Reporter: Benjamin Voigt
Priority: Critical
 Attachments: pde_dep_missing.zip, pde.patch.txt


 Some artifacts are not referenced after executing mvn eclipse:eclipse and 
 having pde mode enabled. The strange thing is, that this does only happen for 
 particluar versions of an artifact.
 Two artifacts that I found with this problem are jetty (org.mortbay.jetty) 
 and slf4j-log4j12 (org.slf4j-log4j12). Jetty versions beyond 6.1.5 work with 
 pde enabled, higher versions do not. Same for slf4j-log4j12 versions = 1.1.0.
 Attached is an example project demonstrating the problem. Turn pde mode 
 on/off in the pom and execute mvn eclipse:eclipse.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (DOXIASITETOOLS-70) Html title of generated pages does not include project name

2012-04-05 Thread Dennis Lundberg (JIRA)

 [ 
https://jira.codehaus.org/browse/DOXIASITETOOLS-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Lundberg updated DOXIASITETOOLS-70:
--

Component/s: Site renderer

 Html title of generated pages does not include project name
 ---

 Key: DOXIASITETOOLS-70
 URL: https://jira.codehaus.org/browse/DOXIASITETOOLS-70
 Project: Maven Doxia Sitetools
  Issue Type: Bug
  Components: Site renderer
Affects Versions: 1.2
 Environment: Apache Maven 3.0.3 
 (rNON-CANONICAL_2011-04-10_05-06_zfsdt; 2011-04-10 05:06:31+0200)
 Maven home: /usr/local/apache-maven/apache-maven-3.0.3
 Java version: 1.6.0_18, vendor: Sun Microsystems Inc.
 Java home: /usr/lib/jvm/java-6-openjdk/jre
 Default locale: en_US, platform encoding: ANSI_X3.4-1968
 OS name: linux, version: 2.6.18-028stab092.1, arch: amd64, family: 
 unix
Reporter: Heinrich Schuchardt
 Attachments: pom.xml


 Dear maintainer,
 according to 
 http://maven.apache.org/plugins/maven-site-plugin/examples/sitedescriptor.html
  the title of each page should be the concatenation of the site title and the 
 title of the current page. E.g. if in pom.xml the name element is:
 nameSite Plugin Test/name
 then target/site/index.html should have a line
 titleSite Plugin Test - Abouttitle
 This is not working. The site title is missing and the created index.html 
 only contains
 titleAbout/title
 This effects how the page is shown in Google, Bing and other search engines. 
 To have the page correctly related in search machines with the project it is 
 desirable to have the project name in the HTML title.
 For testing you can use the appended pom.xml
 Best regards
 Heinrich Schuchardt

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (DOXIASITETOOLS-70) Html title of generated pages does not include project name

2012-04-05 Thread Dennis Lundberg (JIRA)

 [ 
https://jira.codehaus.org/browse/DOXIASITETOOLS-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Lundberg moved MSITE-635 to DOXIASITETOOLS-70:
-

Affects Version/s: (was: 3.0)
   1.2
  Key: DOXIASITETOOLS-70  (was: MSITE-635)
  Project: Maven Doxia Sitetools  (was: Maven 2.x and 3.x Site 
Plugin)

 Html title of generated pages does not include project name
 ---

 Key: DOXIASITETOOLS-70
 URL: https://jira.codehaus.org/browse/DOXIASITETOOLS-70
 Project: Maven Doxia Sitetools
  Issue Type: Bug
  Components: Site renderer
Affects Versions: 1.2
 Environment: Apache Maven 3.0.3 
 (rNON-CANONICAL_2011-04-10_05-06_zfsdt; 2011-04-10 05:06:31+0200)
 Maven home: /usr/local/apache-maven/apache-maven-3.0.3
 Java version: 1.6.0_18, vendor: Sun Microsystems Inc.
 Java home: /usr/lib/jvm/java-6-openjdk/jre
 Default locale: en_US, platform encoding: ANSI_X3.4-1968
 OS name: linux, version: 2.6.18-028stab092.1, arch: amd64, family: 
 unix
Reporter: Heinrich Schuchardt
 Attachments: pom.xml


 Dear maintainer,
 according to 
 http://maven.apache.org/plugins/maven-site-plugin/examples/sitedescriptor.html
  the title of each page should be the concatenation of the site title and the 
 title of the current page. E.g. if in pom.xml the name element is:
 nameSite Plugin Test/name
 then target/site/index.html should have a line
 titleSite Plugin Test - Abouttitle
 This is not working. The site title is missing and the created index.html 
 only contains
 titleAbout/title
 This effects how the page is shown in Google, Bing and other search engines. 
 To have the page correctly related in search machines with the project it is 
 desirable to have the project name in the HTML title.
 For testing you can use the appended pom.xml
 Best regards
 Heinrich Schuchardt

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (DOXIASITETOOLS-70) Html title of generated pages does not include project name

2012-04-05 Thread Dennis Lundberg (JIRA)

[ 
https://jira.codehaus.org/browse/DOXIASITETOOLS-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=295933#comment-295933
 ] 

Dennis Lundberg commented on DOXIASITETOOLS-70:
---

The reason for the change in behavior compared to previous versions can most 
likely be found in this commit:
https://svn.apache.org/viewvc?view=revisionrevision=1054241

 Html title of generated pages does not include project name
 ---

 Key: DOXIASITETOOLS-70
 URL: https://jira.codehaus.org/browse/DOXIASITETOOLS-70
 Project: Maven Doxia Sitetools
  Issue Type: Bug
  Components: Site renderer
Affects Versions: 1.2
 Environment: Apache Maven 3.0.3 
 (rNON-CANONICAL_2011-04-10_05-06_zfsdt; 2011-04-10 05:06:31+0200)
 Maven home: /usr/local/apache-maven/apache-maven-3.0.3
 Java version: 1.6.0_18, vendor: Sun Microsystems Inc.
 Java home: /usr/lib/jvm/java-6-openjdk/jre
 Default locale: en_US, platform encoding: ANSI_X3.4-1968
 OS name: linux, version: 2.6.18-028stab092.1, arch: amd64, family: 
 unix
Reporter: Heinrich Schuchardt
 Attachments: pom.xml


 Dear maintainer,
 according to 
 http://maven.apache.org/plugins/maven-site-plugin/examples/sitedescriptor.html
  the title of each page should be the concatenation of the site title and the 
 title of the current page. E.g. if in pom.xml the name element is:
 nameSite Plugin Test/name
 then target/site/index.html should have a line
 titleSite Plugin Test - Abouttitle
 This is not working. The site title is missing and the created index.html 
 only contains
 titleAbout/title
 This effects how the page is shown in Google, Bing and other search engines. 
 To have the page correctly related in search machines with the project it is 
 desirable to have the project name in the HTML title.
 For testing you can use the appended pom.xml
 Best regards
 Heinrich Schuchardt

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (DOXIASITETOOLS-70) Html title of generated pages does not include project name

2012-04-05 Thread Dennis Lundberg (JIRA)

 [ 
https://jira.codehaus.org/browse/DOXIASITETOOLS-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Lundberg closed DOXIASITETOOLS-70.
-

   Resolution: Fixed
Fix Version/s: 1.3
 Assignee: Dennis Lundberg

The problem was that the $title property was used for 2 different things in the 
velocity template: the title and the name of the last breadcrumb. They want 
different titles. The page title should include the project name, but the 
breadcrumb should not. I solved this by a adding a new property called 
$shortTitle that is now used by the breadcrumb generation.

Fixed in [r1309906|http://svn.apache.org/viewvc?view=revisionrevision=1309906].

Change your pom.xml to this:
{code}
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-site-plugin/artifactId
version3.0/version
dependencies
  dependency
groupIdorg.apache.maven.doxia/groupId
artifactIddoxia-site-renderer/artifactId
version1.3-SNAPSHOT/version
  /dependency
/dependencies
/plugin
{code}

 Html title of generated pages does not include project name
 ---

 Key: DOXIASITETOOLS-70
 URL: https://jira.codehaus.org/browse/DOXIASITETOOLS-70
 Project: Maven Doxia Sitetools
  Issue Type: Bug
  Components: Site renderer
Affects Versions: 1.2
 Environment: Apache Maven 3.0.3 
 (rNON-CANONICAL_2011-04-10_05-06_zfsdt; 2011-04-10 05:06:31+0200)
 Maven home: /usr/local/apache-maven/apache-maven-3.0.3
 Java version: 1.6.0_18, vendor: Sun Microsystems Inc.
 Java home: /usr/lib/jvm/java-6-openjdk/jre
 Default locale: en_US, platform encoding: ANSI_X3.4-1968
 OS name: linux, version: 2.6.18-028stab092.1, arch: amd64, family: 
 unix
Reporter: Heinrich Schuchardt
Assignee: Dennis Lundberg
 Fix For: 1.3

 Attachments: pom.xml


 Dear maintainer,
 according to 
 http://maven.apache.org/plugins/maven-site-plugin/examples/sitedescriptor.html
  the title of each page should be the concatenation of the site title and the 
 title of the current page. E.g. if in pom.xml the name element is:
 nameSite Plugin Test/name
 then target/site/index.html should have a line
 titleSite Plugin Test - Abouttitle
 This is not working. The site title is missing and the created index.html 
 only contains
 titleAbout/title
 This effects how the page is shown in Google, Bing and other search engines. 
 To have the page correctly related in search machines with the project it is 
 desirable to have the project name in the HTML title.
 For testing you can use the appended pom.xml
 Best regards
 Heinrich Schuchardt

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (MSKINS-42) Make skins future compatible with Site Plugin 3.1

2012-04-05 Thread Dennis Lundberg (JIRA)
Dennis Lundberg created MSKINS-42:
-

 Summary: Make skins future compatible with Site Plugin 3.1
 Key: MSKINS-42
 URL: https://jira.codehaus.org/browse/MSKINS-42
 Project: Maven Skins
  Issue Type: Improvement
  Components: Fluido Skin, Stylus Skin
Affects Versions: fluido-1.2.1, stylus-1.4
Reporter: Dennis Lundberg


The handling of the $title property will change in Maven Site Plugin 3.1. 
Changes need to be made in Fluido and Stylus skins to take advantage of the new 
behavior, while still preserving backwards compatobility with older versions.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (MSKINS-43) Invalid html code generated for breadcrumbs

2012-04-05 Thread Dennis Lundberg (JIRA)
Dennis Lundberg created MSKINS-43:
-

 Summary: Invalid html code generated for breadcrumbs
 Key: MSKINS-43
 URL: https://jira.codehaus.org/browse/MSKINS-43
 Project: Maven Skins
  Issue Type: Bug
  Components: Fluido Skin
Affects Versions: fluido-1.2.1
Reporter: Dennis Lundberg


The issue can be seen in the IT mskins-24, which has this code in it:
{code}
  div id=breadcrumbs
ul class=breadcrumb


  li class=
a href=http://www.apache.org/; class=externalLink 
title=ApacheApache/a
li class=divider //li
  /li
li class=
a href=../../../index.html title=MavenMaven/a
li class=divider //li
  /li
li class=
a href=skins/ title=skinsskins/a
li class=divider //li
  /li
li class=
a href=skins/maven-fluido-skin/ 
title=maven-fluido-skinmaven-fluido-skin/a
li class=divider //li
  /li
li class=Apache Maven Fluido Skin IT, MSKINS-24/li
  


  li id=publishDate class=pull-rightLast Published: 
2012-03-31/li li class=divider pull-right|/li
  li id=projectVersion class=pull-rightVersion: 
1.0-SNAPSHOT/li

  /ul
  /div
{code}

The problem is an li element (with class=divider) inside another li 
element. This can probably be solved by changing the inner li to a span 
instead.

We also need to check the css, to see if there are any rules like this
{code}
li.divider {...}
{code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (MSKINS-44) Not checking for null everywhere in site.vm

2012-04-05 Thread Dennis Lundberg (JIRA)
Dennis Lundberg created MSKINS-44:
-

 Summary: Not checking for null everywhere in site.vm
 Key: MSKINS-44
 URL: https://jira.codehaus.org/browse/MSKINS-44
 Project: Maven Skins
  Issue Type: Bug
  Components: Fluido Skin
Affects Versions: fluido-1.2.1
Reporter: Dennis Lundberg


When generating a site that has a site.xml file that doesn't have any 
breadcrumbs, a bunch of errors are generated on the command line.

{noformat}
[INFO] Rendering site with org.apache.maven.skins:maven-fluido-skin:jar:1.2.1 
skin.
[INFO] Generating Distribution Management report--- Maven Project Info 
Reports Plugin 2.4
[ERROR] Left side ($decoration.body.links.size()) of '' operation has null 
value. Operation not possible. META-INF/maven/site.vm [line 914, column 67]
[INFO] Generating About report--- Maven Project Info Reports Plugin 2.4
[ERROR] Left side ($decoration.body.links.size()) of '' operation has null 
value. Operation not possible. META-INF/maven/site.vm [line 914, column 67]
[INFO] Generating Dependencies report--- Maven Project Info Reports 
Plugin 2.4
[ERROR] Left side ($decoration.body.links.size()) of '' operation has null 
value. Operation not possible. META-INF/maven/site.vm [line 914, column 67]
[INFO] Generating Issue Tracking report--- Maven Project Info Reports 
Plugin 2.4
[ERROR] Left side ($decoration.body.links.size()) of '' operation has null 
value. Operation not possible. META-INF/maven/site.vm [line 914, column 67]
[INFO] Generating Project Plugins report--- Maven Project Info Reports 
Plugin 2.4
[ERROR] Left side ($decoration.body.links.size()) of '' operation has null 
value. Operation not possible. META-INF/maven/site.vm [line 914, column 67]
[INFO] Generating Continuous Integration report--- Maven Project Info 
Reports Plugin 2.4
[ERROR] Left side ($decoration.body.links.size()) of '' operation has null 
value. Operation not possible. META-INF/maven/site.vm [line 914, column 67]
[INFO] Generating Project License report--- Maven Project Info Reports 
Plugin 2.4
[ERROR] Left side ($decoration.body.links.size()) of '' operation has null 
value. Operation not possible. META-INF/maven/site.vm [line 914, column 67]
[INFO] Generating Mailing Lists report--- Maven Project Info Reports 
Plugin 2.4
[ERROR] Left side ($decoration.body.links.size()) of '' operation has null 
value. Operation not possible. META-INF/maven/site.vm [line 914, column 67]
[INFO] Generating Project Team report--- Maven Project Info Reports 
Plugin 2.4
[ERROR] Left side ($decoration.body.links.size()) of '' operation has null 
value. Operation not possible. META-INF/maven/site.vm [line 914, column 67]
[INFO] Generating Source Repository report--- Maven Project Info Reports 
Plugin 2.4
[ERROR] Left side ($decoration.body.links.size()) of '' operation has null 
value. Operation not possible. META-INF/maven/site.vm [line 914, column 67]
[INFO] Generating Plugin Management report--- Maven Project Info Reports 
Plugin 2.4
[ERROR] Left side ($decoration.body.links.size()) of '' operation has null 
value. Operation not possible. META-INF/maven/site.vm [line 914, column 67]
[INFO] Generating Project Summary report--- Maven Project Info Reports 
Plugin 2.4
[ERROR] Left side ($decoration.body.links.size()) of '' operation has null 
value. Operation not possible. META-INF/maven/site.vm [line 914, column 67]
[ERROR] Left side ($decoration.body.links.size()) of '' operation has null 
value. Operation not possible. META-INF/maven/site.vm [line 914, column 67]
{noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (MSKINS-42) Make skins future compatible with Site Plugin 3.1

2012-04-05 Thread Dennis Lundberg (JIRA)

 [ 
https://jira.codehaus.org/browse/MSKINS-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Lundberg closed MSKINS-42.
-

   Resolution: Fixed
Fix Version/s: fluido-1.2.2
   stylus-1.5
 Assignee: Dennis Lundberg

Fixed in [r1309961|http://svn.apache.org/viewvc?view=revisionrevision=1309961].

 Make skins future compatible with Site Plugin 3.1
 -

 Key: MSKINS-42
 URL: https://jira.codehaus.org/browse/MSKINS-42
 Project: Maven Skins
  Issue Type: Improvement
  Components: Fluido Skin, Stylus Skin
Affects Versions: stylus-1.4, fluido-1.2.1
Reporter: Dennis Lundberg
Assignee: Dennis Lundberg
 Fix For: stylus-1.5, fluido-1.2.2


 The handling of the $title property will change in Maven Site Plugin 3.1. 
 Changes need to be made in Fluido and Stylus skins to take advantage of the 
 new behavior, while still preserving backwards compatobility with older 
 versions.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (MSKINS-44) Not checking if decoration.body.links is null in site.vm

2012-04-05 Thread Dennis Lundberg (JIRA)

 [ 
https://jira.codehaus.org/browse/MSKINS-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Lundberg updated MSKINS-44:
--

Summary: Not checking if decoration.body.links is null in site.vm  (was: 
Not checking for null everywhere in site.vm)

 Not checking if decoration.body.links is null in site.vm
 

 Key: MSKINS-44
 URL: https://jira.codehaus.org/browse/MSKINS-44
 Project: Maven Skins
  Issue Type: Bug
  Components: Fluido Skin
Affects Versions: fluido-1.2.1
Reporter: Dennis Lundberg
 Fix For: fluido-1.2.2


 When generating a site that has a site.xml file that doesn't have any 
 breadcrumbs, a bunch of errors are generated on the command line.
 {noformat}
 [INFO] Rendering site with org.apache.maven.skins:maven-fluido-skin:jar:1.2.1 
 skin.
 [INFO] Generating Distribution Management report--- Maven Project Info 
 Reports Plugin 2.4
 [ERROR] Left side ($decoration.body.links.size()) of '' operation has null 
 value. Operation not possible. META-INF/maven/site.vm [line 914, column 67]
 [INFO] Generating About report--- Maven Project Info Reports Plugin 2.4
 [ERROR] Left side ($decoration.body.links.size()) of '' operation has null 
 value. Operation not possible. META-INF/maven/site.vm [line 914, column 67]
 [INFO] Generating Dependencies report--- Maven Project Info Reports 
 Plugin 2.4
 [ERROR] Left side ($decoration.body.links.size()) of '' operation has null 
 value. Operation not possible. META-INF/maven/site.vm [line 914, column 67]
 [INFO] Generating Issue Tracking report--- Maven Project Info Reports 
 Plugin 2.4
 [ERROR] Left side ($decoration.body.links.size()) of '' operation has null 
 value. Operation not possible. META-INF/maven/site.vm [line 914, column 67]
 [INFO] Generating Project Plugins report--- Maven Project Info Reports 
 Plugin 2.4
 [ERROR] Left side ($decoration.body.links.size()) of '' operation has null 
 value. Operation not possible. META-INF/maven/site.vm [line 914, column 67]
 [INFO] Generating Continuous Integration report--- Maven Project Info 
 Reports Plugin 2.4
 [ERROR] Left side ($decoration.body.links.size()) of '' operation has null 
 value. Operation not possible. META-INF/maven/site.vm [line 914, column 67]
 [INFO] Generating Project License report--- Maven Project Info Reports 
 Plugin 2.4
 [ERROR] Left side ($decoration.body.links.size()) of '' operation has null 
 value. Operation not possible. META-INF/maven/site.vm [line 914, column 67]
 [INFO] Generating Mailing Lists report--- Maven Project Info Reports 
 Plugin 2.4
 [ERROR] Left side ($decoration.body.links.size()) of '' operation has null 
 value. Operation not possible. META-INF/maven/site.vm [line 914, column 67]
 [INFO] Generating Project Team report--- Maven Project Info Reports 
 Plugin 2.4
 [ERROR] Left side ($decoration.body.links.size()) of '' operation has null 
 value. Operation not possible. META-INF/maven/site.vm [line 914, column 67]
 [INFO] Generating Source Repository report--- Maven Project Info 
 Reports Plugin 2.4
 [ERROR] Left side ($decoration.body.links.size()) of '' operation has null 
 value. Operation not possible. META-INF/maven/site.vm [line 914, column 67]
 [INFO] Generating Plugin Management report--- Maven Project Info 
 Reports Plugin 2.4
 [ERROR] Left side ($decoration.body.links.size()) of '' operation has null 
 value. Operation not possible. META-INF/maven/site.vm [line 914, column 67]
 [INFO] Generating Project Summary report--- Maven Project Info Reports 
 Plugin 2.4
 [ERROR] Left side ($decoration.body.links.size()) of '' operation has null 
 value. Operation not possible. META-INF/maven/site.vm [line 914, column 67]
 [ERROR] Left side ($decoration.body.links.size()) of '' operation has null 
 value. Operation not possible. META-INF/maven/site.vm [line 914, column 67]
 {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (MSKINS-44) Not checking if decoration.body.links is null in site.vm

2012-04-05 Thread Dennis Lundberg (JIRA)

 [ 
https://jira.codehaus.org/browse/MSKINS-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Lundberg closed MSKINS-44.
-

   Resolution: Fixed
Fix Version/s: fluido-1.2.2
 Assignee: Dennis Lundberg

Fixed in [r1309968|http://svn.apache.org/viewvc?view=revisionrevision=1309968].

 Not checking if decoration.body.links is null in site.vm
 

 Key: MSKINS-44
 URL: https://jira.codehaus.org/browse/MSKINS-44
 Project: Maven Skins
  Issue Type: Bug
  Components: Fluido Skin
Affects Versions: fluido-1.2.1
Reporter: Dennis Lundberg
Assignee: Dennis Lundberg
 Fix For: fluido-1.2.2


 When generating a site that has a site.xml file that doesn't have any 
 breadcrumbs, a bunch of errors are generated on the command line.
 {noformat}
 [INFO] Rendering site with org.apache.maven.skins:maven-fluido-skin:jar:1.2.1 
 skin.
 [INFO] Generating Distribution Management report--- Maven Project Info 
 Reports Plugin 2.4
 [ERROR] Left side ($decoration.body.links.size()) of '' operation has null 
 value. Operation not possible. META-INF/maven/site.vm [line 914, column 67]
 [INFO] Generating About report--- Maven Project Info Reports Plugin 2.4
 [ERROR] Left side ($decoration.body.links.size()) of '' operation has null 
 value. Operation not possible. META-INF/maven/site.vm [line 914, column 67]
 [INFO] Generating Dependencies report--- Maven Project Info Reports 
 Plugin 2.4
 [ERROR] Left side ($decoration.body.links.size()) of '' operation has null 
 value. Operation not possible. META-INF/maven/site.vm [line 914, column 67]
 [INFO] Generating Issue Tracking report--- Maven Project Info Reports 
 Plugin 2.4
 [ERROR] Left side ($decoration.body.links.size()) of '' operation has null 
 value. Operation not possible. META-INF/maven/site.vm [line 914, column 67]
 [INFO] Generating Project Plugins report--- Maven Project Info Reports 
 Plugin 2.4
 [ERROR] Left side ($decoration.body.links.size()) of '' operation has null 
 value. Operation not possible. META-INF/maven/site.vm [line 914, column 67]
 [INFO] Generating Continuous Integration report--- Maven Project Info 
 Reports Plugin 2.4
 [ERROR] Left side ($decoration.body.links.size()) of '' operation has null 
 value. Operation not possible. META-INF/maven/site.vm [line 914, column 67]
 [INFO] Generating Project License report--- Maven Project Info Reports 
 Plugin 2.4
 [ERROR] Left side ($decoration.body.links.size()) of '' operation has null 
 value. Operation not possible. META-INF/maven/site.vm [line 914, column 67]
 [INFO] Generating Mailing Lists report--- Maven Project Info Reports 
 Plugin 2.4
 [ERROR] Left side ($decoration.body.links.size()) of '' operation has null 
 value. Operation not possible. META-INF/maven/site.vm [line 914, column 67]
 [INFO] Generating Project Team report--- Maven Project Info Reports 
 Plugin 2.4
 [ERROR] Left side ($decoration.body.links.size()) of '' operation has null 
 value. Operation not possible. META-INF/maven/site.vm [line 914, column 67]
 [INFO] Generating Source Repository report--- Maven Project Info 
 Reports Plugin 2.4
 [ERROR] Left side ($decoration.body.links.size()) of '' operation has null 
 value. Operation not possible. META-INF/maven/site.vm [line 914, column 67]
 [INFO] Generating Plugin Management report--- Maven Project Info 
 Reports Plugin 2.4
 [ERROR] Left side ($decoration.body.links.size()) of '' operation has null 
 value. Operation not possible. META-INF/maven/site.vm [line 914, column 67]
 [INFO] Generating Project Summary report--- Maven Project Info Reports 
 Plugin 2.4
 [ERROR] Left side ($decoration.body.links.size()) of '' operation has null 
 value. Operation not possible. META-INF/maven/site.vm [line 914, column 67]
 [ERROR] Left side ($decoration.body.links.size()) of '' operation has null 
 value. Operation not possible. META-INF/maven/site.vm [line 914, column 67]
 {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (MSKINS-43) Invalid html code generated for breadcrumbs

2012-04-05 Thread Dennis Lundberg (JIRA)

 [ 
https://jira.codehaus.org/browse/MSKINS-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Lundberg closed MSKINS-43.
-

   Resolution: Fixed
Fix Version/s: fluido-1.2.2
 Assignee: Dennis Lundberg

Fixed in [r1309972|http://svn.apache.org/viewvc?view=revisionrevision=1309972].

It was a simple matter of moving out the inner li and putting it after the 
outer li.

 Invalid html code generated for breadcrumbs
 ---

 Key: MSKINS-43
 URL: https://jira.codehaus.org/browse/MSKINS-43
 Project: Maven Skins
  Issue Type: Bug
  Components: Fluido Skin
Affects Versions: fluido-1.2.1
Reporter: Dennis Lundberg
Assignee: Dennis Lundberg
 Fix For: fluido-1.2.2


 The issue can be seen in the IT mskins-24, which has this code in it:
 {code}
   div id=breadcrumbs
 ul class=breadcrumb
 
 
   li class=
 a href=http://www.apache.org/; class=externalLink 
 title=ApacheApache/a
 li class=divider //li
   /li
 li class=
 a href=../../../index.html title=MavenMaven/a
 li class=divider //li
   /li
 li class=
 a href=skins/ title=skinsskins/a
 li class=divider //li
   /li
 li class=
 a href=skins/maven-fluido-skin/ 
 title=maven-fluido-skinmaven-fluido-skin/a
 li class=divider //li
   /li
 li class=Apache Maven Fluido Skin IT, MSKINS-24/li
   
 
 
   li id=publishDate class=pull-rightLast Published: 
 2012-03-31/li li class=divider pull-right|/li
   li id=projectVersion class=pull-rightVersion: 
 1.0-SNAPSHOT/li
 
   /ul
   /div
 {code}
 The problem is an li element (with class=divider) inside another li 
 element. This can probably be solved by changing the inner li to a span 
 instead.
 We also need to check the css, to see if there are any rules like this
 {code}
 li.divider {...}
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (MSKINS-45) Add support for Google Analytics

2012-04-05 Thread Dennis Lundberg (JIRA)
Dennis Lundberg created MSKINS-45:
-

 Summary: Add support for Google Analytics
 Key: MSKINS-45
 URL: https://jira.codehaus.org/browse/MSKINS-45
 Project: Maven Skins
  Issue Type: New Feature
  Components: Stylus Skin
Affects Versions: stylus-1.4
Reporter: Dennis Lundberg


In maven-parent we define a couple of extra  body/head/script elements in 
the site.xml file, to insert Google Analytics into the generated site. Maven 
Site Plugin has built-in support for Google Analytics nowadays, so we should 
use that instead. In order for that to work we need to add GA-support in Maven 
Stylus Skin, similar to what is in Maven Fluido Skin.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (MSKINS-45) Add support for Google Analytics

2012-04-05 Thread Dennis Lundberg (JIRA)

 [ 
https://jira.codehaus.org/browse/MSKINS-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Lundberg closed MSKINS-45.
-

   Resolution: Fixed
Fix Version/s: stylus-1.5
 Assignee: Dennis Lundberg

Fixed in [r1309984|http://svn.apache.org/viewvc?view=revisionrevision=1309984].

 Add support for Google Analytics
 

 Key: MSKINS-45
 URL: https://jira.codehaus.org/browse/MSKINS-45
 Project: Maven Skins
  Issue Type: New Feature
  Components: Stylus Skin
Affects Versions: stylus-1.4
Reporter: Dennis Lundberg
Assignee: Dennis Lundberg
 Fix For: stylus-1.5


 In maven-parent we define a couple of extra  body/head/script elements 
 in the site.xml file, to insert Google Analytics into the generated site. 
 Maven Site Plugin has built-in support for Google Analytics nowadays, so we 
 should use that instead. In order for that to work we need to add GA-support 
 in Maven Stylus Skin, similar to what is in Maven Fluido Skin.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (DOXIATOOLS-18) Doxia Maven Plugin should copy resources

2012-04-05 Thread Dennis Lundberg (JIRA)

 [ 
https://jira.codehaus.org/browse/DOXIATOOLS-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Lundberg moved DOXIA-355 to DOXIATOOLS-18:
-

  Component/s: (was: Maven plugin)
   (was: Book)
   Doxia Book Maven Plugin
   Book
Affects Version/s: (was: 1.1.1)
  Key: DOXIATOOLS-18  (was: DOXIA-355)
  Project: Maven Doxia Tools  (was: Maven Doxia)

 Doxia Maven Plugin should copy resources
 

 Key: DOXIATOOLS-18
 URL: https://jira.codehaus.org/browse/DOXIATOOLS-18
 Project: Maven Doxia Tools
  Issue Type: Bug
  Components: Book, Doxia Book Maven Plugin
Reporter: Lukas Theussl

 To include images in books, etc.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (DOXIATOOLS-21) Problem to create a book with Maven 3

2012-04-05 Thread Dennis Lundberg (JIRA)

 [ 
https://jira.codehaus.org/browse/DOXIATOOLS-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Lundberg moved DOXIA-438 to DOXIATOOLS-21:
-

  Component/s: (was: Book)
   Book
Affects Version/s: (was: 1.2)
   1.2
  Key: DOXIATOOLS-21  (was: DOXIA-438)
  Project: Maven Doxia Tools  (was: Maven Doxia)

 Problem to create a book with Maven 3
 -

 Key: DOXIATOOLS-21
 URL: https://jira.codehaus.org/browse/DOXIATOOLS-21
 Project: Maven Doxia Tools
  Issue Type: Bug
  Components: Book
Affects Versions: 1.2
 Environment: Maven 3
Reporter: Andres Gomez Casanova
 Attachments: pom.xml


 I had a project configured for Maven 2 and everything worked perfectly. 
 Today, I was trying to update it to Maven 3 and all plugin to newer versions. 
 However, I found that I cannot use doxia-maven-plugin 1.2 to create the book.
 After executing
 mvn doxia:render-books
 I got
 {noformat}
 [ERROR] Failed to execute goal 
 org.apache.maven.doxia:doxia-maven-plugin:1.2:render-books (default-cli) on 
 project user-site: Execution default-cli of goal 
 org.apache.maven.doxia:doxia-maven-plugin:1.2:render-books failed: Unable to 
 load the mojo 'render-books' in the plugin 
 'org.apache.maven.doxia:doxia-maven-plugin:1.2'. A required class is missing: 
 org/codehaus/plexus/util/interpolation/ValueSource
 [ERROR] -
 [ERROR] realm =pluginorg.apache.maven.doxia:doxia-maven-plugin:1.2
 [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
 [ERROR] urls[0] = 
 file:/C:/Users/Andres/.m2/repository/org/apache/maven/doxia/doxia-maven-plugin/1.2/doxia-maven-plugin-1.2.jar
 [ERROR] urls[1] = 
 file:/C:/Users/Andres/.m2/repository/org/apache/maven/doxia/doxia-book/1.2/doxia-book-1.2.jar
 ...
 [ERROR] urls[24] = 
 file:/C:/Users/Andres/.m2/repository/org/apache/maven/reporting/maven-reporting-api/2.0.4/maven-reporting-api-2.0.4.jar
 [ERROR] Number of foreign imports: 1
 [ERROR] import: Entry[import  from realm ClassRealm[maven.api, parent: null]]
 [ERROR]
 [ERROR] -: 
 org.codehaus.plexus.util.interpolation.ValueSource
 {noformat}
 My pom.xml is
 {code:xml}
 project
 ...
   !-- Build Settings --
   build
 plugins
   !-- mvn doxia:render-books --
   plugin
 groupIdorg.apache.maven.doxia/groupId
 artifactIddoxia-maven-plugin/artifactId
 version1.2/version
 executions
   execution
 phasepre-site/phase
 goals
   goalrender-books/goal
 /goals
   /execution
 /executions
 configuration
   books
 book
   directorysrc/site/apt/directory
   descriptorsrc/books/usersManual.xml/descriptor
   formats
 format
   idpdf/id
 /format
   /formats
 /book
 book
   directorysrc/site/es/apt/directory
   descriptorsrc/books/usersManual_es.xml/descriptor
   formats
 format
   idpdf/id
 /format
   /formats
 /book
   /books
 /configuration
   /plugin
 ...
 /plugins
   /build
 /project
 {code}
 What is the problem?
 If I change the Doxia version to 1.1, it works normally.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (DOXIATOOLS-19) totally no rich formatting in generated PDFs/RTFs

2012-04-05 Thread Dennis Lundberg (JIRA)

 [ 
https://jira.codehaus.org/browse/DOXIATOOLS-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Lundberg moved DOXIA-419 to DOXIATOOLS-19:
-

  Component/s: (was: Book)
   Book
Affects Version/s: (was: 1.1.3)
  Key: DOXIATOOLS-19  (was: DOXIA-419)
  Project: Maven Doxia Tools  (was: Maven Doxia)

 totally no rich formatting in generated PDFs/RTFs
 -

 Key: DOXIATOOLS-19
 URL: https://jira.codehaus.org/browse/DOXIATOOLS-19
 Project: Maven Doxia Tools
  Issue Type: Bug
  Components: Book
Reporter: Lazy Coder
 Attachments: ugly_pdf_in_doxia.zip


 We've decided to use Maven Doxia back in 2008.
 2,5 years have passed but generated PDFs/RTFs still look unacceptably ugly.
 Please see attached project.
 PDFs/RTFs built from content
 {code:xml}
 pNo formatting./p
 pfont size 1: font size=1this/font/p
 pfont size 20: font size=20this/font/p
 pfont size=small: font size=smallsmall/font /p
 p small: smallthis/small /p
 p font color red: font color=redthis/font /p
 p strike: sstrike/s /p
 psource code line XXX /source /p
 {code}
 have totally no formatting while xhtml looks fine.
 Frankly speaking I just can't believe Doxia Books plugin is so lame \- could 
 there be a misconfiguration in my sample project?
 At least is there a workaround to make source code formatting differ from 
 main text in PDF (e.g. have smaller size)? We need this badly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (DOXIATOOLS-20) APT anchors are parsed to invalid XML in xdoc book

2012-04-05 Thread Dennis Lundberg (JIRA)

 [ 
https://jira.codehaus.org/browse/DOXIATOOLS-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Lundberg moved DOXIA-368 to DOXIATOOLS-20:
-

  Component/s: (was: Module - Xdoc)
   (was: Book)
   Book
Affects Version/s: (was: 1.1.1)
  Key: DOXIATOOLS-20  (was: DOXIA-368)
  Project: Maven Doxia Tools  (was: Maven Doxia)

 APT anchors are parsed to invalid XML in xdoc book
 --

 Key: DOXIATOOLS-20
 URL: https://jira.codehaus.org/browse/DOXIATOOLS-20
 Project: Maven Doxia Tools
  Issue Type: Bug
  Components: Book
Reporter: Dave Syer

 APT anchors are parsed to invalid XML in xdoc book.  E.g. start with APT like 
 this
 {code}
 {Section Title}
   La la la la
 {code}
 and then include this document in a book with xdoc format.  You get an 
 invalid XML document which then fails when it is being turned into HTML for 
 the site:
 {noformat}
 [ERROR] Error parsing 
 /home/dsyer/dev/admin/code/target/generated-site/xdoc/reference/jobs.xml: 
 line [-1] Error parsing the model: markup not allowed inside attribute value 
 - illegal   (position: END_TAG seen ...section name=... @1:676) 
 org.apache.maven.doxia.parser.ParseException: Error parsing the model: markup 
 not allowed inside attribute value - illegal   (position: END_TAG seen 
 ...section name=Add your Own ... @1:676) 
   at 
 org.apache.maven.doxia.parser.AbstractXmlParser.parse(AbstractXmlParser.java:57)
   at 
 org.apache.maven.doxia.module.xdoc.XdocParser.parse(XdocParser.java:99)
   at org.apache.maven.doxia.DefaultDoxia.parse(DefaultDoxia.java:59)
   at 
 org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:342)
 {noformat}
 The xml is invlaid because it has {{section name=a 
 name=Section_Title/.../}}.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (DOXIATOOLS-17) validation message is lost for the end user

2012-04-05 Thread Dennis Lundberg (JIRA)

 [ 
https://jira.codehaus.org/browse/DOXIATOOLS-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Lundberg moved DOXIA-396 to DOXIATOOLS-17:
-

  Component/s: (was: Book)
   Book
Affects Version/s: (was: 1.1.3)
  Key: DOXIATOOLS-17  (was: DOXIA-396)
  Project: Maven Doxia Tools  (was: Maven Doxia)

 validation message is lost for the end user
 ---

 Key: DOXIATOOLS-17
 URL: https://jira.codehaus.org/browse/DOXIATOOLS-17
 Project: Maven Doxia Tools
  Issue Type: Bug
  Components: Book
 Environment: windows, mvn2, mvn3
Reporter: Ivica Loncar

 When doxia validates invalid configuration file (for example chapter id is 
 missing) validator adds correct message (Each chapter has to have an id. ) 
 to the list of errors.
 Unfortunately this helpful message is lost for the end user and all she sees 
 is:
 {noformat}
 [ERROR] Failed to execute goal 
 org.apache.maven.doxia:doxia-maven-plugin:1.1.3:render-books (default-cli) on 
 project XYZ
 : Error while generating book in format 'pdf'. Invalid book descriptor. - 
 [Help 1]
 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
 goal org.apache.maven.doxia:doxia-maven-plugin:1.1.3:render-books
 (default-cli) on project B24ZiiscB2GDocumentation: Error while generating 
 book in format 'pdf'.
 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:570)
 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:317)
 at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:247)
 at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:104)
 at 
 org.sonatype.maven.shell.maven.MavenSystemImpl$MavenRuntimeImpl.doExecute(MavenSystemImpl.java:476)
 at 
 org.sonatype.maven.shell.maven.MavenSystemImpl$MavenRuntimeImpl.execute(MavenSystemImpl.java:252)
 at 
 org.sonatype.maven.shell.commands.maven.MavenCommand.execute(MavenCommand.java:425)
 at 
 org.sonatype.gshell.execute.CommandExecutorImpl.execute(CommandExecutorImpl.java:175)
 at 
 org.sonatype.gshell.parser.impl.visitor.ExecutingVisitor.visit(ExecutingVisitor.java:95)
 at 
 org.sonatype.gshell.parser.impl.ASTExpression.jjtAccept(ASTExpression.java:18)
 at 
 org.sonatype.gshell.parser.impl.SimpleNode.childrenAccept(SimpleNode.java:65)
 at 
 org.sonatype.gshell.parser.impl.visitor.ExecutingVisitor.visit(ExecutingVisitor.java:75)
 at 
 org.sonatype.gshell.parser.impl.ASTCommandLine.jjtAccept(ASTCommandLine.java:18)
 at 
 org.sonatype.gshell.parser.CommandLineParserImpl$1.execute(CommandLineParserImpl.java:68)
 at 
 org.sonatype.gshell.execute.CommandExecutorImpl.execute(CommandExecutorImpl.java:91)
 at org.sonatype.gshell.shell.ShellImpl.execute(ShellImpl.java:215)
 at 
 org.sonatype.gshell.shell.ShellImpl$1$1.doExecute(ShellImpl.java:246)
 at 
 org.sonatype.gshell.console.ConsoleTask.execute(ConsoleTask.java:108)
 at org.sonatype.gshell.console.Console.work(Console.java:198)
 at org.sonatype.gshell.console.Console.run(Console.java:135)
 at org.sonatype.gshell.shell.ShellImpl.run(ShellImpl.java:293)
 at org.sonatype.gshell.MainSupport.boot(MainSupport.java:279)
 at org.sonatype.maven.shell.Main.main(Main.java:67)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at org.sonatype.gshell.launcher.Launcher.launch(Launcher.java:76)
 at org.sonatype.gshell.launcher.Launcher.run(Launcher.java:48)
 at org.sonatype.gshell.launcher.Launcher.main(Launcher.java:39)
 Caused by: org.apache.maven.plugin.MojoExecutionException: Error while 
 generating book in format 'pdf'.
 at 
 org.apache.maven.doxia.plugin.DoxiaRenderBooksMojo.execute(DoxiaRenderBooksMojo.java:270)
 at 
 org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:105)
 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:562)
 ... 29 more
 Caused by: org.apache.maven.doxia.book.InvalidBookDescriptorException: 
 Invalid book descriptor.
 at 
 org.apache.maven.doxia.book.DefaultBookDoxia.renderBook(DefaultBookDoxia.java:100)
 at 
 org.apache.maven.doxia.plugin.DoxiaRenderBooksMojo.execute(DoxiaRenderBooksMojo.java:265)
 ... 31 more
 {noformat}
 Example of invalid configuration:
 {code:xml}
 

[jira] (DOXIATOOLS-23) Nested APT file directories and PDF generation

2012-04-05 Thread Dennis Lundberg (JIRA)

 [ 
https://jira.codehaus.org/browse/DOXIATOOLS-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Lundberg moved DOXIA-347 to DOXIATOOLS-23:
-

  Component/s: (was: Book)
   Book
Affects Version/s: (was: 1.2)
   1.2
  Key: DOXIATOOLS-23  (was: DOXIA-347)
  Project: Maven Doxia Tools  (was: Maven Doxia)

 Nested APT file directories and PDF generation
 --

 Key: DOXIATOOLS-23
 URL: https://jira.codehaus.org/browse/DOXIATOOLS-23
 Project: Maven Doxia Tools
  Issue Type: New Feature
  Components: Book
Affects Versions: 1.2
 Environment: OSX 10.5.7, Java 5, Maven 2.2
Reporter: Nathan Sowatskey

 Hi
 I have a chapter declared like this in xxx.xml:
 chapter
  idxxx_Integration/id
  titlexxx Integration/title
  sections
   section
idxxx/index/id
   /section
  /sections
 /chapter
 Where:
 src/site/apt/xxx/integraion
 Contains some documentation specific to xxx.
 When I try to use mvn site with this config in pom.xml:
 book
   directorysrc/site/apt/directory
  descriptorsrc/site/xxx.xml/descriptor
  formats
   format
idpdf/id
   /format
  /formats
 /book
 I get this error:
 ERROR] BUILD ERROR
 [INFO] 
 
 [INFO] Error while generating book in format 'pdf'.
 Embedded error: No document that matches section with id=xxx/index.
 I don't know whether this *should* work, or whether this is a new feature 
 request.
 Thanks
 Nathan

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (DOXIATOOLS-22) Local links are not resolved in book (between source documents)

2012-04-05 Thread Dennis Lundberg (JIRA)

 [ 
https://jira.codehaus.org/browse/DOXIATOOLS-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Lundberg moved DOXIA-369 to DOXIATOOLS-22:
-

  Component/s: (was: Book)
   Book
Affects Version/s: (was: 1.1.1)
  Key: DOXIATOOLS-22  (was: DOXIA-369)
  Project: Maven Doxia Tools  (was: Maven Doxia)

 Local links are not resolved in book (between source documents)
 ---

 Key: DOXIATOOLS-22
 URL: https://jira.codehaus.org/browse/DOXIATOOLS-22
 Project: Maven Doxia Tools
  Issue Type: Bug
  Components: Book
Reporter: Dave Syer

 Local links are not resolved in book (between source documents).  This is 
 really a showstopper for producing high quality documents using doxia book.  
 Links to anchors in the same source document work (pdf and xdoc except for 
 DOXIA-368).  But I can't see a way to create links between source documents 
 that work in all book formats.  Maybe I missed a trick?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (DOXIATOOLS-24) Add images to example-book

2012-04-05 Thread Dennis Lundberg (JIRA)

 [ 
https://jira.codehaus.org/browse/DOXIATOOLS-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Lundberg moved DOXIA-354 to DOXIATOOLS-24:
-

  Component/s: (was: Book)
   Book
Affects Version/s: (was: 1.1.1)
  Key: DOXIATOOLS-24  (was: DOXIA-354)
  Project: Maven Doxia Tools  (was: Maven Doxia)

 Add images to example-book
 --

 Key: DOXIATOOLS-24
 URL: https://jira.codehaus.org/browse/DOXIATOOLS-24
 Project: Maven Doxia Tools
  Issue Type: Improvement
  Components: Book
Reporter: Steven Swor

 Images are an important feature of a technical manual or book, yet try as I 
 might, I cannot get them to work with a Doxia book.  Could someone please 
 update the example-book to include at least one image, so that the rest of 
 the world may benefit from knowing how to properly add images to a Doxia book?
 It would be beneficial if the example could show how to add an image from a 
 local file as well as from a URL.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (DOXIATOOLS-25) Make BookRenderers configurable from pom in site generation

2012-04-05 Thread Dennis Lundberg (JIRA)

 [ 
https://jira.codehaus.org/browse/DOXIATOOLS-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Lundberg moved DOXIA-188 to DOXIATOOLS-25:
-

  Component/s: (was: Book)
   Book
Affects Version/s: (was: 1.0-alpha-10)
  Key: DOXIATOOLS-25  (was: DOXIA-188)
  Project: Maven Doxia Tools  (was: Maven Doxia)

 Make BookRenderers configurable from pom in site generation
 ---

 Key: DOXIATOOLS-25
 URL: https://jira.codehaus.org/browse/DOXIATOOLS-25
 Project: Maven Doxia Tools
  Issue Type: Improvement
  Components: Book
Reporter: Dave Syer

 .Make BookRenderers configurable from pom in site generation.  E.g. there are 
 loads of properties in a DocBookSink (used by the DocBookRenderer) that are 
 important to be able to control

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (DOXIATOOLS-26) Locales and Encoding params are ignored by plugin

2012-04-05 Thread Dennis Lundberg (JIRA)

 [ 
https://jira.codehaus.org/browse/DOXIATOOLS-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Lundberg moved DOXIA-375 to DOXIATOOLS-26:
-

  Component/s: (was: Maven plugin)
   Doxia Book Maven Plugin
Affects Version/s: (was: 1.1.2)
  Key: DOXIATOOLS-26  (was: DOXIA-375)
  Project: Maven Doxia Tools  (was: Maven Doxia)

 Locales and Encoding params are ignored by plugin
 -

 Key: DOXIATOOLS-26
 URL: https://jira.codehaus.org/browse/DOXIATOOLS-26
 Project: Maven Doxia Tools
  Issue Type: Bug
  Components: Doxia Book Maven Plugin
 Environment: doxia-maven-plugin (1.1.2)
Reporter: Cleverson Sacramento

 I'm using doxia-maven-plugin to generate the project documentation site. 
 This is the plugin session of my pom.xml:
 {code:xml}   ...
   properties
   
 project.build.sourceEncodingUTF-8/project.build.sourceEncoding
   project.reporting.outputEncodingUTF-8
   /project.reporting.outputEncoding
   /properties
 ...
   plugin
   groupIdorg.apache.maven.doxia/groupId
   artifactIddoxia-maven-plugin/artifactId
   version1.1.2/version
   executions
   execution
   phasepre-site/phase
   goals
   
 goalrender-books/goal
   /goals
   /execution
   /executions
   configuration
   localespt_BR/locales
   
 inputEncoding${project.build.sourceEncoding}/inputEncoding
   
 outputEncoding${project.reporting.outputEncoding}
   /outputEncoding
   books
   book
   
 directorysrc/site/directory
   
 descriptorsrc/site/book-reference.xml/descriptor
   formats
   format
   
 idxdoc/id
   /format
   /formats
   /book
   /books
   /configuration
   /plugin
 ...{code}
 The content auto-generated by the plugin presents two problems:
 1) The locale pt_br was ignored, generating words in english instead of 
 brazilian portuguese;
 2) The encoding UFT-8 was apparently ignored too, generating unwished chars;
 {noformat}Next: Configurações
 Referência - Table Of Content
 Configurações
Servidor
   Introdu#8730;ß#8730;£o
   Administra#8730;ß#8730;£o
   E-mail
   Banco de Dados
   Base de Usu#8730;°rios
   Base LDAP
   Base Personalizada
Agente
   Introdu#8730;ß#8730;£o
 Next: Configurações{noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (DOXIATOOLS-27) problems with book and vm template for apt

2012-04-05 Thread Dennis Lundberg (JIRA)

 [ 
https://jira.codehaus.org/browse/DOXIATOOLS-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Lundberg moved DOXIA-378 to DOXIATOOLS-27:
-

Affects Version/s: (was: 1.1.1)
  Key: DOXIATOOLS-27  (was: DOXIA-378)
  Project: Maven Doxia Tools  (was: Maven Doxia)

 problems with book and vm template for apt
 --

 Key: DOXIATOOLS-27
 URL: https://jira.codehaus.org/browse/DOXIATOOLS-27
 Project: Maven Doxia Tools
  Issue Type: Bug
  Components: Book
 Environment: linux - maven 2.2.1.
Reporter: Pablo Graña

 I am trying to generate a latex doc from my apt documentation. Everything 
 works 
 fine except until I decided to use a vm template for one of my apt docs. Here 
 are some relevant fragments of files: 
 The book configuration: 
 user-manual.xml 
  
  chapter 
idgetting-started/id 
titleGetting started/title 
sections 
  section 
idgetting-started/id 
  /section 
/sections 
  /chapter 
  
 I have in the src/site/apt directory I have a file named 
 getting-started.apt.vm. 
 building the site (mvn site) fails with: 
 [ERROR] BUILD ERROR 
 [INFO] 
  
 [INFO] Error while generating book in format 'latex'. 
 Embedded error: No document that matches section with id=getting-started. 
 [INFO] 
  
 If I just use getting-started.apt, everything works fine. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (DOXIATOOLS-27) problems with book and vm template for apt

2012-04-05 Thread Dennis Lundberg (JIRA)

 [ 
https://jira.codehaus.org/browse/DOXIATOOLS-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Lundberg updated DOXIATOOLS-27:
--

Component/s: Book

 problems with book and vm template for apt
 --

 Key: DOXIATOOLS-27
 URL: https://jira.codehaus.org/browse/DOXIATOOLS-27
 Project: Maven Doxia Tools
  Issue Type: Bug
  Components: Book
 Environment: linux - maven 2.2.1.
Reporter: Pablo Graña

 I am trying to generate a latex doc from my apt documentation. Everything 
 works 
 fine except until I decided to use a vm template for one of my apt docs. Here 
 are some relevant fragments of files: 
 The book configuration: 
 user-manual.xml 
  
  chapter 
idgetting-started/id 
titleGetting started/title 
sections 
  section 
idgetting-started/id 
  /section 
/sections 
  /chapter 
  
 I have in the src/site/apt directory I have a file named 
 getting-started.apt.vm. 
 building the site (mvn site) fails with: 
 [ERROR] BUILD ERROR 
 [INFO] 
  
 [INFO] Error while generating book in format 'latex'. 
 Embedded error: No document that matches section with id=getting-started. 
 [INFO] 
  
 If I just use getting-started.apt, everything works fine. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (DOXIATOOLS-28) Book- and/or Site-Tile missing on all pages

2012-04-05 Thread Dennis Lundberg (JIRA)

 [ 
https://jira.codehaus.org/browse/DOXIATOOLS-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Lundberg moved DOXIA-411 to DOXIATOOLS-28:
-

Key: DOXIATOOLS-28  (was: DOXIA-411)
Project: Maven Doxia Tools  (was: Maven Doxia)

 Book- and/or Site-Tile missing on all pages
 ---

 Key: DOXIATOOLS-28
 URL: https://jira.codehaus.org/browse/DOXIATOOLS-28
 Project: Maven Doxia Tools
  Issue Type: Bug
  Components: Book
Reporter: Michael Wenig
 Attachments: DOXIA_411.png, doxia411.zip


 On a rendered book there is no title - neither of the book nor of the page on 
 the top of the page
 (See screenshot)
 An empty h2-Tag is rendered - so I assume it is just a bug that this is 
 missing.
 I would assume that there are one of the following
 h1[book-title]/h1
 h2[page.title]/h2
 or
 h2[book-title] - [page title]
 or h2[page title]/h2
 Currently we are in need to repeat the page title as a section name at the 
 top of the page - which leads to (optical) duplicate entries in the structure

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (DOXIATOOLS-28) Book- and/or Site-Tile missing on all pages

2012-04-05 Thread Dennis Lundberg (JIRA)

 [ 
https://jira.codehaus.org/browse/DOXIATOOLS-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Lundberg updated DOXIATOOLS-28:
--

Component/s: Book

 Book- and/or Site-Tile missing on all pages
 ---

 Key: DOXIATOOLS-28
 URL: https://jira.codehaus.org/browse/DOXIATOOLS-28
 Project: Maven Doxia Tools
  Issue Type: Bug
  Components: Book
Reporter: Michael Wenig
 Attachments: DOXIA_411.png, doxia411.zip


 On a rendered book there is no title - neither of the book nor of the page on 
 the top of the page
 (See screenshot)
 An empty h2-Tag is rendered - so I assume it is just a bug that this is 
 missing.
 I would assume that there are one of the following
 h1[book-title]/h1
 h2[page.title]/h2
 or
 h2[book-title] - [page title]
 or h2[page title]/h2
 Currently we are in need to repeat the page title as a section name at the 
 top of the page - which leads to (optical) duplicate entries in the structure

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (DOXIATOOLS-29) Another incomplete fix for the resource leak bugs in XHtmlBookRenderer.java

2012-04-05 Thread Dennis Lundberg (JIRA)

 [ 
https://jira.codehaus.org/browse/DOXIATOOLS-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Lundberg moved DOXIA-462 to DOXIATOOLS-29:
-

Key: DOXIATOOLS-29  (was: DOXIA-462)
Project: Maven Doxia Tools  (was: Maven Doxia)

 Another incomplete fix for the resource leak bugs in XHtmlBookRenderer.java
 ---

 Key: DOXIATOOLS-29
 URL: https://jira.codehaus.org/browse/DOXIATOOLS-29
 Project: Maven Doxia Tools
  Issue Type: Bug
  Components: Book
Reporter: Guangtai Liang
Priority: Critical

 The fix revision 740164 was aimed to remove resource leak bugs on the 
 FileWriter object fileWriter 
 (created in line 84) in the method renderBookof the file 
 /maven/doxia/doxia/trunk/doxia-
 book/src/main/java/org/apache/maven/doxia/book/services/renderer/XHtmlBookRenderer.java
  , but it is 
 incomplete. 
 There are some problems: 
 1. when the statements at lines 91 throw some exception, fileWriter will be 
 leaked. 
 The best way to close such resource objects is putting such close operations 
 for all resource 
 objects in the finaly block of a try-catch-finally structure and then putting 
 all other code in a 
 try block.
 The problem still exists in the head revision. The buggy code is copied as 
 bellows:
   public void renderBook( BookContext context )
 throws BookDoxiaException
 {
 BookModel book = context.getBook();
 if ( !context.getOutputDirectory().exists() )
 {
 if ( !context.getOutputDirectory().mkdirs() )
 {
 throw new BookDoxiaException( Could not make directory: 
 + context.getOutputDirectory().getAbsolutePath() 
 + . );
 }
 }
 File bookFile = new File( context.getOutputDirectory(), book.getId() 
 + .xhtml );
 Writer fileWriter;
 try
 {
  84   fileWriter = new FileWriter( bookFile );
 }
 catch ( IOException e )
 {
 throw new BookDoxiaException( Error while opening file., e );
 }
 91XhtmlBookSink sink = new XhtmlBookSink( fileWriter,
   new RenderingContext( context.getOutputDirectory(), 
 bookFile.getAbsolutePath() ) );
 try
 {
 sink.bookHead();
 ..
 }
 finally
 {
 sink.flush();
 sink.close();
 IOUtil.close( fileWriter );
 }
 }

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (DOXIATOOLS-29) Another incomplete fix for the resource leak bugs in XHtmlBookRenderer.java

2012-04-05 Thread Dennis Lundberg (JIRA)

 [ 
https://jira.codehaus.org/browse/DOXIATOOLS-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Lundberg updated DOXIATOOLS-29:
--

Component/s: Book

 Another incomplete fix for the resource leak bugs in XHtmlBookRenderer.java
 ---

 Key: DOXIATOOLS-29
 URL: https://jira.codehaus.org/browse/DOXIATOOLS-29
 Project: Maven Doxia Tools
  Issue Type: Bug
  Components: Book
Reporter: Guangtai Liang
Priority: Critical

 The fix revision 740164 was aimed to remove resource leak bugs on the 
 FileWriter object fileWriter 
 (created in line 84) in the method renderBookof the file 
 /maven/doxia/doxia/trunk/doxia-
 book/src/main/java/org/apache/maven/doxia/book/services/renderer/XHtmlBookRenderer.java
  , but it is 
 incomplete. 
 There are some problems: 
 1. when the statements at lines 91 throw some exception, fileWriter will be 
 leaked. 
 The best way to close such resource objects is putting such close operations 
 for all resource 
 objects in the finaly block of a try-catch-finally structure and then putting 
 all other code in a 
 try block.
 The problem still exists in the head revision. The buggy code is copied as 
 bellows:
   public void renderBook( BookContext context )
 throws BookDoxiaException
 {
 BookModel book = context.getBook();
 if ( !context.getOutputDirectory().exists() )
 {
 if ( !context.getOutputDirectory().mkdirs() )
 {
 throw new BookDoxiaException( Could not make directory: 
 + context.getOutputDirectory().getAbsolutePath() 
 + . );
 }
 }
 File bookFile = new File( context.getOutputDirectory(), book.getId() 
 + .xhtml );
 Writer fileWriter;
 try
 {
  84   fileWriter = new FileWriter( bookFile );
 }
 catch ( IOException e )
 {
 throw new BookDoxiaException( Error while opening file., e );
 }
 91XhtmlBookSink sink = new XhtmlBookSink( fileWriter,
   new RenderingContext( context.getOutputDirectory(), 
 bookFile.getAbsolutePath() ) );
 try
 {
 sink.bookHead();
 ..
 }
 finally
 {
 sink.flush();
 sink.close();
 IOUtil.close( fileWriter );
 }
 }

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (DOXIATOOLS-31) An incomplete fix for the resource leak bugs in XdocBookRenderer.java

2012-04-05 Thread Dennis Lundberg (JIRA)

 [ 
https://jira.codehaus.org/browse/DOXIATOOLS-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Lundberg moved DOXIA-464 to DOXIATOOLS-31:
-

Key: DOXIATOOLS-31  (was: DOXIA-464)
Project: Maven Doxia Tools  (was: Maven Doxia)

 An incomplete fix for the resource leak bugs in XdocBookRenderer.java
 -

 Key: DOXIATOOLS-31
 URL: https://jira.codehaus.org/browse/DOXIATOOLS-31
 Project: Maven Doxia Tools
  Issue Type: Bug
Reporter: Guangtai Liang
Priority: Critical

 The fix revision 1003021 was aimed to remove resource leak bugs on the 
 SectionXdocBookSink  object sink  (created in line 409) in the method 
 renderSectionof the file 
 /maven/doxia/doxia/trunk/doxia-book/src/main/java/org/apache/maven/doxia/book/services/renderer/XdocBookRenderer.java
  , but it is incomplete.
 There are some problems: 
 1. when the statements at lines 411-418 throw some exception, sink will be 
 leaked. 
 The best way to close such resource objects is putting such close operations 
 for all resource objects in the finaly block of a try-catch-finally structure 
 and then putting all other code in a try block.
 The problem still exists in the head revision.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (DOXIATOOLS-30) An incomplete fix for the resource leak bugs in XdocBookRenderer.java

2012-04-05 Thread Dennis Lundberg (JIRA)

 [ 
https://jira.codehaus.org/browse/DOXIATOOLS-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Lundberg moved DOXIA-463 to DOXIATOOLS-30:
-

Key: DOXIATOOLS-30  (was: DOXIA-463)
Project: Maven Doxia Tools  (was: Maven Doxia)

 An incomplete fix for the resource leak bugs in XdocBookRenderer.java
 -

 Key: DOXIATOOLS-30
 URL: https://jira.codehaus.org/browse/DOXIATOOLS-30
 Project: Maven Doxia Tools
  Issue Type: Bug
Reporter: Guangtai Liang
Priority: Critical

 The fix revision 740164 was aimed to remove resource leak bugs on the Writer 
 object writer (created in line 177) in the method writeBookIndexof the 
 file /maven/doxia/doxia/trunk/doxia-
 book/src/main/java/org/apache/maven/doxia/book/services/renderer/XdocBookRenderer.java
  , but it is incomplete. 
 There are some problems: 
 1. when the statements at lines 177 throw some exception, writer will be 
 leaked. 
 The best way to close such resource objects is putting such close operations 
 for all resource objects in the finaly block of a try-catch-finally structure 
 and then putting all other code in a try block.
 The problem still exists in the head revision (when the statements at line 
 171 throws some exception, writer will be leaked). The buggy code is copied 
 as bellows:
 private void writeBookIndex( File index, BookModel book, BookContext context )
 throws IOException
 {
 169Writer writer = WriterFactory.newXmlWriter( index );
 171XdocSink sink = new IndexXdocBookSink( writer, 
 context.getIndex().getFirstEntry(), i18n, 
 context.getLocale() );
 try
 {
 ..
 sink.body_();
 }
 finally
 {
 211sink.flush();
 213sink.close();
 215IOUtil.close( writer );
 }
 }

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (DOXIATOOLS-9) Linkcheck: ability to run more than one Validator

2012-04-05 Thread Dennis Lundberg (JIRA)

 [ 
https://jira.codehaus.org/browse/DOXIATOOLS-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Lundberg updated DOXIATOOLS-9:
-

Component/s: linkcheck

 Linkcheck: ability to run more than one Validator
 -

 Key: DOXIATOOLS-9
 URL: https://jira.codehaus.org/browse/DOXIATOOLS-9
 Project: Maven Doxia Tools
  Issue Type: Improvement
  Components: linkcheck
Reporter: Lukas Theussl

 Currently every link is checked by exactly one Validator, eg 
 FileLinkValidator or HTTPLinkValidator. In a multiproject build some links 
 never exist locally but only after deployment. The basedir solution is not 
 ideal because it forces one to use absolute links. It would be better to be 
 able to (optionally) run other validators if a specific one fails.
 See the discussion: 
 http://www.mail-archive.com/dev@maven.apache.org/msg69705.html

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (DOXIATOOLS-31) An incomplete fix for the resource leak bugs in XdocBookRenderer.java

2012-04-05 Thread Dennis Lundberg (JIRA)

 [ 
https://jira.codehaus.org/browse/DOXIATOOLS-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Lundberg updated DOXIATOOLS-31:
--

Component/s: Book

 An incomplete fix for the resource leak bugs in XdocBookRenderer.java
 -

 Key: DOXIATOOLS-31
 URL: https://jira.codehaus.org/browse/DOXIATOOLS-31
 Project: Maven Doxia Tools
  Issue Type: Bug
  Components: Book
Reporter: Guangtai Liang
Priority: Critical

 The fix revision 1003021 was aimed to remove resource leak bugs on the 
 SectionXdocBookSink  object sink  (created in line 409) in the method 
 renderSectionof the file 
 /maven/doxia/doxia/trunk/doxia-book/src/main/java/org/apache/maven/doxia/book/services/renderer/XdocBookRenderer.java
  , but it is incomplete.
 There are some problems: 
 1. when the statements at lines 411-418 throw some exception, sink will be 
 leaked. 
 The best way to close such resource objects is putting such close operations 
 for all resource objects in the finaly block of a try-catch-finally structure 
 and then putting all other code in a try block.
 The problem still exists in the head revision.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (DOXIATOOLS-30) An incomplete fix for the resource leak bugs in XdocBookRenderer.java

2012-04-05 Thread Dennis Lundberg (JIRA)

 [ 
https://jira.codehaus.org/browse/DOXIATOOLS-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Lundberg updated DOXIATOOLS-30:
--

Component/s: Book

 An incomplete fix for the resource leak bugs in XdocBookRenderer.java
 -

 Key: DOXIATOOLS-30
 URL: https://jira.codehaus.org/browse/DOXIATOOLS-30
 Project: Maven Doxia Tools
  Issue Type: Bug
  Components: Book
Reporter: Guangtai Liang
Priority: Critical

 The fix revision 740164 was aimed to remove resource leak bugs on the Writer 
 object writer (created in line 177) in the method writeBookIndexof the 
 file /maven/doxia/doxia/trunk/doxia-
 book/src/main/java/org/apache/maven/doxia/book/services/renderer/XdocBookRenderer.java
  , but it is incomplete. 
 There are some problems: 
 1. when the statements at lines 177 throw some exception, writer will be 
 leaked. 
 The best way to close such resource objects is putting such close operations 
 for all resource objects in the finaly block of a try-catch-finally structure 
 and then putting all other code in a try block.
 The problem still exists in the head revision (when the statements at line 
 171 throws some exception, writer will be leaked). The buggy code is copied 
 as bellows:
 private void writeBookIndex( File index, BookModel book, BookContext context )
 throws IOException
 {
 169Writer writer = WriterFactory.newXmlWriter( index );
 171XdocSink sink = new IndexXdocBookSink( writer, 
 context.getIndex().getFirstEntry(), i18n, 
 context.getLocale() );
 try
 {
 ..
 sink.body_();
 }
 finally
 {
 211sink.flush();
 213sink.close();
 215IOUtil.close( writer );
 }
 }

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (DOXIATOOLS-16) NullPointerException when site URL is being generated

2012-04-05 Thread Dennis Lundberg (JIRA)

 [ 
https://jira.codehaus.org/browse/DOXIATOOLS-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Lundberg updated DOXIATOOLS-16:
--

Component/s: Doxia Integration Tools

 NullPointerException when site URL is being generated
 -

 Key: DOXIATOOLS-16
 URL: https://jira.codehaus.org/browse/DOXIATOOLS-16
 Project: Maven Doxia Tools
  Issue Type: Bug
  Components: Doxia Integration Tools
 Environment: environment independent
Reporter: Marc Claessens

 We have a parent POM where the site url is generated via the Maven Groovy 
 plugin, unless it is explicitly defined in the child POM
 i.e.
 site
idproject-sites/id
nameOur project Nexus server Site/name
!-- URL is built dynamically by groovy plugin --
 /site
 ...
 plugin
groupIdorg.codehaus.groovy.maven/groupId
artifactIdgmaven-plugin/artifactId
executions
   execution
   phasepre-site/phase
   goals
  goalexecute/goal
   /goals
   configuration
   source
   ![CDATA[
if(!project.distributionManagement.site.url){
 String version = new String(project.version)
 String path = new String(project.artifactId)+'/'+version
 project.distributionManagement.site.url 
 ='dav:'+project.properties['siteBaseURL'] + path
}
   ]]
   /source
   /configuration
   /execution
/executions
 /plugin
  }
 This leads to a NullPointerException in DefaultSiteTool.java:
 at java.io.File.init(File.java:222)
 at 
 org.apache.maven.doxia.tools.DefaultSiteTool.urlEncode(DefaultSiteTool.java:1478)
 at 
 org.apache.maven.doxia.tools.DefaultSiteTool.getDistMgmntSiteUrl(DefaultSiteTool.java:1451)
 The if statement in getDistMgntSiteUrl (for both methods) should test for 
 null on project.getDistributionManagement().getSite().getUrl()

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (DOXIATOOLS-34) Separate inheritance and interpolation

2012-04-05 Thread Dennis Lundberg (JIRA)

 [ 
https://jira.codehaus.org/browse/DOXIATOOLS-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Lundberg moved MSHARED-217 to DOXIATOOLS-34:
---

Fix Version/s: (was: maven-doxia-tools-1.5)
   doxia-integration-tools-1.5
  Component/s: (was: maven-doxia-tools)
   Doxia Integration Tools
Affects Version/s: (was: maven-doxia-tools-1.4)
   doxia-integration-tools-1.4
  Key: DOXIATOOLS-34  (was: MSHARED-217)
  Project: Maven Doxia Tools  (was: Maven Shared Components)

 Separate inheritance and interpolation 
 ---

 Key: DOXIATOOLS-34
 URL: https://jira.codehaus.org/browse/DOXIATOOLS-34
 Project: Maven Doxia Tools
  Issue Type: Improvement
  Components: Doxia Integration Tools
Affects Versions: doxia-integration-tools-1.4
Reporter: Robert Scholte
Assignee: Robert Scholte
 Fix For: doxia-integration-tools-1.5


 The implementation uses recursion to get an inherited model of the site.xml, 
 but every step does the interpolation too.
 So if the parent site.xml contains something like ${project.name}, its value 
 will be an ancestor project name, often an unexpected value.
 By moving the interpolation from the recursive method to the method-caller 
 you will get the name of the active project.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (DOXIATOOLS-33) DefaultSiteTool.getRelativePath does not work between files

2012-04-05 Thread Dennis Lundberg (JIRA)

 [ 
https://jira.codehaus.org/browse/DOXIATOOLS-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Lundberg moved MSHARED-208 to DOXIATOOLS-33:
---

  Component/s: (was: maven-doxia-tools)
   Doxia Integration Tools
Affects Version/s: (was: maven-doxia-tools-1.4)
   doxia-integration-tools-1.4
  Key: DOXIATOOLS-33  (was: MSHARED-208)
  Project: Maven Doxia Tools  (was: Maven Shared Components)

 DefaultSiteTool.getRelativePath does not work between files
 ---

 Key: DOXIATOOLS-33
 URL: https://jira.codehaus.org/browse/DOXIATOOLS-33
 Project: Maven Doxia Tools
  Issue Type: Bug
  Components: Doxia Integration Tools
Affects Versions: doxia-integration-tools-1.4
Reporter: Lukas Theussl

 See test case committed in 
 [r1174674|http://svn.apache.org/viewvc?rev=1174674view=rev]. Given
 {code}
 to = http://maven.apache.org/downloads.html;;
 from = http://maven.apache.org/index.html;;
 {code}
 getRelativePath( to, from ) returns ../downloads.html instead of 
 downloads.html. It seems like the 'from' parameter is always supposed to be 
 a directory. That's confusing and not very useful, also the 
 [javadocs|http://maven.apache.org/shared/maven-doxia-tools/apidocs/org/apache/maven/doxia/tools/SiteTool.html#getRelativePath%28java.lang.String,%20java.lang.String%29]
  state that the method should 'Calculate the relative path between two URLs 
 or between two files.'.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (DOXIATOOLS-32) DefaultSiteTool.getRelativePath returns nonsense if both paths are absolute with different scheme

2012-04-05 Thread Dennis Lundberg (JIRA)

 [ 
https://jira.codehaus.org/browse/DOXIATOOLS-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Lundberg moved MSHARED-203 to DOXIATOOLS-32:
---

  Component/s: (was: maven-doxia-tools)
   Doxia Integration Tools
Affects Version/s: (was: maven-doxia-tools-1.2.1)
   doxia-integration-tools-1.4
  Key: DOXIATOOLS-32  (was: MSHARED-203)
  Project: Maven Doxia Tools  (was: Maven Shared Components)

 DefaultSiteTool.getRelativePath returns nonsense if both paths are absolute 
 with different scheme
 -

 Key: DOXIATOOLS-32
 URL: https://jira.codehaus.org/browse/DOXIATOOLS-32
 Project: Maven Doxia Tools
  Issue Type: Bug
  Components: Doxia Integration Tools
Affects Versions: doxia-integration-tools-1.4
Reporter: Lukas Theussl

 See MSITE-600: for the two method parameters from = 
 scp://localhost:/tmp/blop and to = file:///tmp/bloop the result is a 
 relative path that is plain nonsense. It should return just the 'to' 
 argument, since both paths are absolute.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (DOXIATOOLS-35) [PATCH] Migration from obsolete plexus-maven-plugin to plexus-containers-component-metadata

2012-04-05 Thread Dennis Lundberg (JIRA)

 [ 
https://jira.codehaus.org/browse/DOXIATOOLS-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Lundberg moved MSHARED-200 to DOXIATOOLS-35:
---

Fix Version/s: (was: maven-doxia-tools-1.5)
   doxia-integration-tools-1.5
  Component/s: (was: maven-doxia-tools)
   Doxia Integration Tools
Affects Version/s: (was: maven-doxia-tools-1.4)
   doxia-integration-tools-1.4
  Key: DOXIATOOLS-35  (was: MSHARED-200)
  Project: Maven Doxia Tools  (was: Maven Shared Components)

 [PATCH] Migration from obsolete plexus-maven-plugin to 
 plexus-containers-component-metadata
 ---

 Key: DOXIATOOLS-35
 URL: https://jira.codehaus.org/browse/DOXIATOOLS-35
 Project: Maven Doxia Tools
  Issue Type: Improvement
  Components: Doxia Integration Tools
Affects Versions: doxia-integration-tools-1.4
 Environment: Fedora Rawhide
Reporter: Jaromír Cápík
Assignee: Robert Scholte
 Fix For: doxia-integration-tools-1.5

 Attachments: maven-doxia-tools-migration-to-component-metadata.patch


 The attached patch retires the obsolete plexus-maven-plugin and generates the 
 metadata with plexus-containers-component-metadata instead.
 NOTE : The result XML file can have a different order of elements, but all of 
 them should be present.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (DOXIASITETOOLS-51) site.xml custom parameter and template variables not documented

2012-04-05 Thread Dennis Lundberg (JIRA)

 [ 
https://jira.codehaus.org/browse/DOXIASITETOOLS-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Lundberg updated DOXIASITETOOLS-51:
--

Component/s: Decoration model

 site.xml custom parameter and template variables not documented
 -

 Key: DOXIASITETOOLS-51
 URL: https://jira.codehaus.org/browse/DOXIASITETOOLS-51
 Project: Maven Doxia Sitetools
  Issue Type: Bug
  Components: Decoration model
Reporter: SebbASF

 There's no proper documentation on the Maven site descriptor custom tag.
 It's not mentioned in the main documentation [1], and is only mentioned in 
 passing in [2] - which in turn is not referenced from [1]
 Here are the full details from [2]:
 customDOM Custom configuration for use with customized 
 Velocity templates
 The DOM reference above appears to be an instance of Xpp3Dom [3].
 Also, the Doxia code sets various context variables (in DefaultSiteRenderer 
 ?).
 This should all be documented, along with some simple examples, and 
 referenced as necessary from the Maven site plugin documentation
 [1] 
 http://maven.apache.org/plugins/maven-site-plugin/examples/sitedescriptor.html
 [2] 
 http://maven.apache.org/doxia/doxia-sitetools/doxia-decoration-model/decoration.html
 [3] 
 http://plexus.codehaus.org/plexus-utils/apidocs/org/codehaus/plexus/util/xml/Xpp3Dom.html

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (DOXIATOOLS-6) Review Doxia generation for Apt and Docbook

2012-04-05 Thread Dennis Lundberg (JIRA)

 [ 
https://jira.codehaus.org/browse/DOXIATOOLS-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Lundberg updated DOXIATOOLS-6:
-

Fix Version/s: (was: doxia-linkcheck-1.1)
   doxia-converter-1.1

 Review Doxia generation for Apt and Docbook
 ---

 Key: DOXIATOOLS-6
 URL: https://jira.codehaus.org/browse/DOXIATOOLS-6
 Project: Maven Doxia Tools
  Issue Type: Bug
Reporter: Vincent Siveton
Assignee: Lukas Theussl
 Fix For: doxia-converter-1.1


 Doxia converter tests failed when converting Apt = xhtml = apt. See the 
 TODO in ConverterTest class.
 Same for docbook.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (DOXIATOOLS-23) Nested APT file directories and PDF generation

2012-04-05 Thread Dennis Lundberg (JIRA)

 [ 
https://jira.codehaus.org/browse/DOXIATOOLS-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Lundberg updated DOXIATOOLS-23:
--

Affects Version/s: (was: doxia-linkcheck-1.2)
   doxia-book-1.2

 Nested APT file directories and PDF generation
 --

 Key: DOXIATOOLS-23
 URL: https://jira.codehaus.org/browse/DOXIATOOLS-23
 Project: Maven Doxia Tools
  Issue Type: New Feature
  Components: Book
Affects Versions: doxia-book-1.2
 Environment: OSX 10.5.7, Java 5, Maven 2.2
Reporter: Nathan Sowatskey

 Hi
 I have a chapter declared like this in xxx.xml:
 chapter
  idxxx_Integration/id
  titlexxx Integration/title
  sections
   section
idxxx/index/id
   /section
  /sections
 /chapter
 Where:
 src/site/apt/xxx/integraion
 Contains some documentation specific to xxx.
 When I try to use mvn site with this config in pom.xml:
 book
   directorysrc/site/apt/directory
  descriptorsrc/site/xxx.xml/descriptor
  formats
   format
idpdf/id
   /format
  /formats
 /book
 I get this error:
 ERROR] BUILD ERROR
 [INFO] 
 
 [INFO] Error while generating book in format 'pdf'.
 Embedded error: No document that matches section with id=xxx/index.
 I don't know whether this *should* work, or whether this is a new feature 
 request.
 Thanks
 Nathan

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (DOXIATOOLS-21) Problem to create a book with Maven 3

2012-04-05 Thread Dennis Lundberg (JIRA)

 [ 
https://jira.codehaus.org/browse/DOXIATOOLS-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Lundberg updated DOXIATOOLS-21:
--

Affects Version/s: (was: doxia-linkcheck-1.2)
   doxia-book-1.2

 Problem to create a book with Maven 3
 -

 Key: DOXIATOOLS-21
 URL: https://jira.codehaus.org/browse/DOXIATOOLS-21
 Project: Maven Doxia Tools
  Issue Type: Bug
  Components: Book
Affects Versions: doxia-book-1.2
 Environment: Maven 3
Reporter: Andres Gomez Casanova
 Attachments: pom.xml


 I had a project configured for Maven 2 and everything worked perfectly. 
 Today, I was trying to update it to Maven 3 and all plugin to newer versions. 
 However, I found that I cannot use doxia-maven-plugin 1.2 to create the book.
 After executing
 mvn doxia:render-books
 I got
 {noformat}
 [ERROR] Failed to execute goal 
 org.apache.maven.doxia:doxia-maven-plugin:1.2:render-books (default-cli) on 
 project user-site: Execution default-cli of goal 
 org.apache.maven.doxia:doxia-maven-plugin:1.2:render-books failed: Unable to 
 load the mojo 'render-books' in the plugin 
 'org.apache.maven.doxia:doxia-maven-plugin:1.2'. A required class is missing: 
 org/codehaus/plexus/util/interpolation/ValueSource
 [ERROR] -
 [ERROR] realm =pluginorg.apache.maven.doxia:doxia-maven-plugin:1.2
 [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
 [ERROR] urls[0] = 
 file:/C:/Users/Andres/.m2/repository/org/apache/maven/doxia/doxia-maven-plugin/1.2/doxia-maven-plugin-1.2.jar
 [ERROR] urls[1] = 
 file:/C:/Users/Andres/.m2/repository/org/apache/maven/doxia/doxia-book/1.2/doxia-book-1.2.jar
 ...
 [ERROR] urls[24] = 
 file:/C:/Users/Andres/.m2/repository/org/apache/maven/reporting/maven-reporting-api/2.0.4/maven-reporting-api-2.0.4.jar
 [ERROR] Number of foreign imports: 1
 [ERROR] import: Entry[import  from realm ClassRealm[maven.api, parent: null]]
 [ERROR]
 [ERROR] -: 
 org.codehaus.plexus.util.interpolation.ValueSource
 {noformat}
 My pom.xml is
 {code:xml}
 project
 ...
   !-- Build Settings --
   build
 plugins
   !-- mvn doxia:render-books --
   plugin
 groupIdorg.apache.maven.doxia/groupId
 artifactIddoxia-maven-plugin/artifactId
 version1.2/version
 executions
   execution
 phasepre-site/phase
 goals
   goalrender-books/goal
 /goals
   /execution
 /executions
 configuration
   books
 book
   directorysrc/site/apt/directory
   descriptorsrc/books/usersManual.xml/descriptor
   formats
 format
   idpdf/id
 /format
   /formats
 /book
 book
   directorysrc/site/es/apt/directory
   descriptorsrc/books/usersManual_es.xml/descriptor
   formats
 format
   idpdf/id
 /format
   /formats
 /book
   /books
 /configuration
   /plugin
 ...
 /plugins
   /build
 /project
 {code}
 What is the problem?
 If I change the Doxia version to 1.1, it works normally.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (DOXIASITETOOLS-71) Add the version of doxia-site-renderer that is used to the generated site

2012-04-05 Thread Dennis Lundberg (JIRA)
Dennis Lundberg created DOXIASITETOOLS-71:
-

 Summary: Add the version of doxia-site-renderer that is used to 
the generated site
 Key: DOXIASITETOOLS-71
 URL: https://jira.codehaus.org/browse/DOXIASITETOOLS-71
 Project: Maven Doxia Sitetools
  Issue Type: New Feature
  Components: Site renderer
Affects Versions: 1.2
Reporter: Dennis Lundberg


In a comment in the generated site documents we currently have this:
{noformat}
Generated by Apache Maven Doxia $currentDate
{noformat}

We should also add the version, like this:
{noformat}
Generated by Apache Maven Doxia $doxiaVersion at $currentDate
{noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (DOXIASITETOOLS-71) Add the version of doxia-site-renderer that is used to the generated site

2012-04-05 Thread Dennis Lundberg (JIRA)

 [ 
https://jira.codehaus.org/browse/DOXIASITETOOLS-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Lundberg closed DOXIASITETOOLS-71.
-

   Resolution: Fixed
Fix Version/s: 1.3
 Assignee: Dennis Lundberg

Fixed in [r1310041|http://svn.apache.org/viewvc?view=revisionrevision=1310041].

 Add the version of doxia-site-renderer that is used to the generated site
 -

 Key: DOXIASITETOOLS-71
 URL: https://jira.codehaus.org/browse/DOXIASITETOOLS-71
 Project: Maven Doxia Sitetools
  Issue Type: New Feature
  Components: Site renderer
Affects Versions: 1.2
Reporter: Dennis Lundberg
Assignee: Dennis Lundberg
 Fix For: 1.3


 In a comment in the generated site documents we currently have this:
 {noformat}
 Generated by Apache Maven Doxia $currentDate
 {noformat}
 We should also add the version, like this:
 {noformat}
 Generated by Apache Maven Doxia $doxiaVersion at $currentDate
 {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (MSITE-636) Upgrade to doxia-1.3

2012-04-05 Thread Dennis Lundberg (JIRA)
Dennis Lundberg created MSITE-636:
-

 Summary: Upgrade to doxia-1.3
 Key: MSITE-636
 URL: https://jira.codehaus.org/browse/MSITE-636
 Project: Maven 2.x and 3.x Site Plugin
  Issue Type: Task
Affects Versions: 3.0
Reporter: Dennis Lundberg




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (MSITE-637) Upgrade to doxia-sitetools-1.3

2012-04-05 Thread Dennis Lundberg (JIRA)
Dennis Lundberg created MSITE-637:
-

 Summary: Upgrade to doxia-sitetools-1.3
 Key: MSITE-637
 URL: https://jira.codehaus.org/browse/MSITE-637
 Project: Maven 2.x and 3.x Site Plugin
  Issue Type: Task
Affects Versions: 3.0
Reporter: Dennis Lundberg




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (MSITE-636) Upgrade to doxia-1.3

2012-04-05 Thread Dennis Lundberg (JIRA)

 [ 
https://jira.codehaus.org/browse/MSITE-636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Lundberg updated MSITE-636:
--

Fix Version/s: 3.1

 Upgrade to doxia-1.3
 

 Key: MSITE-636
 URL: https://jira.codehaus.org/browse/MSITE-636
 Project: Maven 2.x and 3.x Site Plugin
  Issue Type: Task
Affects Versions: 3.0
Reporter: Dennis Lundberg
Assignee: Dennis Lundberg
 Fix For: 3.1




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (MSITE-637) Upgrade to doxia-sitetools-1.3

2012-04-05 Thread Dennis Lundberg (JIRA)

 [ 
https://jira.codehaus.org/browse/MSITE-637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Lundberg updated MSITE-637:
--

Fix Version/s: 3.1

 Upgrade to doxia-sitetools-1.3
 --

 Key: MSITE-637
 URL: https://jira.codehaus.org/browse/MSITE-637
 Project: Maven 2.x and 3.x Site Plugin
  Issue Type: Task
Affects Versions: 3.0
Reporter: Dennis Lundberg
Assignee: Dennis Lundberg
 Fix For: 3.1




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (DOXIASITETOOLS-54) site.xml should also have title attribute for all elements that have alt attributes

2012-04-05 Thread Dennis Lundberg (JIRA)

 [ 
https://jira.codehaus.org/browse/DOXIASITETOOLS-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Lundberg closed DOXIASITETOOLS-54.
-

   Resolution: Fixed
Fix Version/s: 1.3
 Assignee: Dennis Lundberg

Fixed in [r1310063|http://svn.apache.org/viewvc?view=revisionrevision=1310063].

I have added title attribute for bannerLeft, bannerRight, linkItem (used by 
menuItem, breadcrumb and poweredBy) and menu.

Note that this will require the use of version 1.3.0 of the site.xml schema.

 site.xml should also have title attribute for all elements that have alt 
 attributes
 ---

 Key: DOXIASITETOOLS-54
 URL: https://jira.codehaus.org/browse/DOXIASITETOOLS-54
 Project: Maven Doxia Sitetools
  Issue Type: Bug
  Components: Decoration model
Reporter: SebbASF
Assignee: Dennis Lundberg
 Fix For: 1.3


 site.xml allows alt attributes for all elements that relate to images. To 
 provide hover text, images need the title attribute. This may require 
 different text from the alt attribute.
 Note:
 The alt attribute is intended for display if the image is not present.
 The title attribute is intended to provide hover text.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (DOXIASITETOOLS-65) footer declared in the site.xml is not inherited in multi-module sites

2012-04-05 Thread Dennis Lundberg (JIRA)

 [ 
https://jira.codehaus.org/browse/DOXIASITETOOLS-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Lundberg closed DOXIASITETOOLS-65.
-

   Resolution: Fixed
Fix Version/s: 1.3
 Assignee: Dennis Lundberg

Fixed in [r1310075|http://svn.apache.org/viewvc?view=revisionrevision=1310075].

 footer declared in the site.xml is not inherited in multi-module sites
 --

 Key: DOXIASITETOOLS-65
 URL: https://jira.codehaus.org/browse/DOXIASITETOOLS-65
 Project: Maven Doxia Sitetools
  Issue Type: Bug
  Components: Site renderer
Affects Versions: 1.2
Reporter: Simone Tripodi
Assignee: Dennis Lundberg
 Fix For: 1.3


 attaching a {{site.xml}} descriptor to a parent pom, while the {{body.head}} 
 element is inherited from children, {{body.footer}} is not.
 Quoting Lukas from dev@ ML,
 {quote}
 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.
 {quote}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (DOXIASITETOOLS-69) ConcurrentModificationException when using site:run

2012-04-05 Thread Dennis Lundberg (JIRA)

[ 
https://jira.codehaus.org/browse/DOXIASITETOOLS-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=295969#comment-295969
 ] 

Dennis Lundberg commented on DOXIASITETOOLS-69:
---

Can you please put together a sample project that shows this problem.

 ConcurrentModificationException when using site:run
 ---

 Key: DOXIASITETOOLS-69
 URL: https://jira.codehaus.org/browse/DOXIASITETOOLS-69
 Project: Maven Doxia Sitetools
  Issue Type: Bug
  Components: Site renderer
Affects Versions: 1.2
 Environment: Maven 2.2.1 with maven-site-plugin 3.0
Reporter: Christof Schöll

 When using maven with site:run I get the following exception, which seem to 
 originate from the Doxia Site Renderer
 2012-04-04 12:27:07.653:WARN::/css/maven-theme.css
 java.util.ConcurrentModificationException
 at 
 java.util.AbstractList$Itr.checkForComodification(AbstractList.java:372)
 at java.util.AbstractList$Itr.next(AbstractList.java:343)
 at 
 org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.locateDocumentFiles(DefaultSiteRenderer.java:149)
 at 
 org.apache.maven.plugins.site.webapp.DoxiaFilter.doFilter(DoxiaFilter.java:174)
 at 
 org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
 at 
 org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388)
 at 
 org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
 at 
 org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
 at 
 org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
 at 
 org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:440)
 at 
 org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
 at 
 org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
 at org.mortbay.jetty.Server.handle(Server.java:326)
 at 
 org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
 at 
 org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:926)
 at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549)
 at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
 at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
 at 
 org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410)
 at 
 org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
 2012-04-04 12:27:07.656:WARN::/images/logos/maven-feather.png
 java.util.ConcurrentModificationException
 at 
 java.util.AbstractList$Itr.checkForComodification(AbstractList.java:372)
 at java.util.AbstractList$Itr.next(AbstractList.java:343)
 at 
 org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.locateDocumentFiles(DefaultSiteRenderer.java:149)
 at 
 org.apache.maven.plugins.site.webapp.DoxiaFilter.doFilter(DoxiaFilter.java:174)
 at 
 org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
 at 
 org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388)
 at 
 org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
 at 
 org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
 at 
 org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
 at 
 org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:440)
 at 
 org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
 at 
 org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
 at org.mortbay.jetty.Server.handle(Server.java:326)
 at 
 org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
 at 
 org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:926)
 at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549)
 at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
 at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
 at 
 org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410)
 at 
 org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
 The following source code in 
 org.apache.maven.doxia.siterenderer.DefaultSiteRenderer (line 149) seems to 
 contain the problem:
 149  for ( File siteDirectory : siteRenderingContext.getSiteDirectories() )
 150 {
 151 if ( siteDirectory.exists() )
 152 {
 153 CollectionSiteModule modules = 
 siteModuleManager.getSiteModules();
 154   

[jira] (MSITE-638) site.xml custom parameter and template variables not documented

2012-04-05 Thread Dennis Lundberg (JIRA)

 [ 
https://jira.codehaus.org/browse/MSITE-638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Lundberg moved DOXIASITETOOLS-51 to MSITE-638:
-

Component/s: (was: Decoration model)
 site descriptor
 documentation
Key: MSITE-638  (was: DOXIASITETOOLS-51)
Project: Maven 2.x and 3.x Site Plugin  (was: Maven Doxia Sitetools)

 site.xml custom parameter and template variables not documented
 -

 Key: MSITE-638
 URL: https://jira.codehaus.org/browse/MSITE-638
 Project: Maven 2.x and 3.x Site Plugin
  Issue Type: Bug
  Components: documentation, site descriptor
Reporter: SebbASF

 There's no proper documentation on the Maven site descriptor custom tag.
 It's not mentioned in the main documentation [1], and is only mentioned in 
 passing in [2] - which in turn is not referenced from [1]
 Here are the full details from [2]:
 customDOM Custom configuration for use with customized 
 Velocity templates
 The DOM reference above appears to be an instance of Xpp3Dom [3].
 Also, the Doxia code sets various context variables (in DefaultSiteRenderer 
 ?).
 This should all be documented, along with some simple examples, and 
 referenced as necessary from the Maven site plugin documentation
 [1] 
 http://maven.apache.org/plugins/maven-site-plugin/examples/sitedescriptor.html
 [2] 
 http://maven.apache.org/doxia/doxia-sitetools/doxia-decoration-model/decoration.html
 [3] 
 http://plexus.codehaus.org/plexus-utils/apidocs/org/codehaus/plexus/util/xml/Xpp3Dom.html

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (MRELEASE-645) Allow File/Directory Patterns for the checkModificationExcludes Option

2012-04-05 Thread James Levinson (JIRA)

[ 
https://jira.codehaus.org/browse/MRELEASE-645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=295972#comment-295972
 ] 

James Levinson commented on MRELEASE-645:
-

What are the steps to get this patch into the 2.3 pipeline ?

 Allow File/Directory Patterns for the checkModificationExcludes Option
 --

 Key: MRELEASE-645
 URL: https://jira.codehaus.org/browse/MRELEASE-645
 Project: Maven 2.x Release Plugin
  Issue Type: Improvement
  Components: branch, prepare, scm
Affects Versions: 2.1
 Environment: all
Reporter: Stefan Ferstl
Priority: Minor
 Attachments: modification-excludes.patch


 The {{checkModificationExcludes}} option does currently only allow the 
 definition single files to be excluded from the SCM modification check. If 
 this option is defined, all files anywhere in the maven project structure 
 with the specified name will be excluded from the check. It is currently not 
 possible to exclude files only within a specific directory or to exclude 
 classes of files, i.e. all files matching a specific file name pattern.
 If the {{checkModificationExcludes}} option allowed the definition of file 
 and directory patterns, these things would be possible.
 *Example 1*: I'd like to exclude a test resource 
 {{src/test/resources/foo.properties}} from the modification check but the 
 real foo.properties in {{src/main/resources}} should still be checked.
 {code:xml} 
 checkModificationExcludes
   
 checkModificationExcludesrc/test/resources/foo.properties/checkModificationExclude
 /checkModificationExcludes
 {code}
 *Example 2*: I'd like to exclude all properties files with the prefix {{bar}} 
 from the modification check:
 {code:xml} 
 checkModificationExcludes
   checkModificationExclude**/bar*.properties/checkModificationExclude
 /checkModificationExcludes
 {code}
 The attached patch modifies the {{ScmCheckModificationsPhase}} to use the 
 {{DirectoryScanner}} from plexus-utils instead of doing a strict file name 
 comparison. The patch does not provide more unit tests for this feature but 
 it adjusts the existing tests to run without any failures.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (MSITE-638) site.xml custom parameter and template variables not documented

2012-04-05 Thread Dennis Lundberg (JIRA)

 [ 
https://jira.codehaus.org/browse/MSITE-638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Lundberg closed MSITE-638.
-

   Resolution: Fixed
Fix Version/s: 3.1
 Assignee: Dennis Lundberg

Fixed in [r1310089|http://svn.apache.org/viewvc?view=revisionrevision=1310089].

 site.xml custom parameter and template variables not documented
 -

 Key: MSITE-638
 URL: https://jira.codehaus.org/browse/MSITE-638
 Project: Maven 2.x and 3.x Site Plugin
  Issue Type: Bug
  Components: documentation, site descriptor
Reporter: SebbASF
Assignee: Dennis Lundberg
 Fix For: 3.1


 There's no proper documentation on the Maven site descriptor custom tag.
 It's not mentioned in the main documentation [1], and is only mentioned in 
 passing in [2] - which in turn is not referenced from [1]
 Here are the full details from [2]:
 customDOM Custom configuration for use with customized 
 Velocity templates
 The DOM reference above appears to be an instance of Xpp3Dom [3].
 Also, the Doxia code sets various context variables (in DefaultSiteRenderer 
 ?).
 This should all be documented, along with some simple examples, and 
 referenced as necessary from the Maven site plugin documentation
 [1] 
 http://maven.apache.org/plugins/maven-site-plugin/examples/sitedescriptor.html
 [2] 
 http://maven.apache.org/doxia/doxia-sitetools/doxia-decoration-model/decoration.html
 [3] 
 http://plexus.codehaus.org/plexus-utils/apidocs/org/codehaus/plexus/util/xml/Xpp3Dom.html

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (DOXIATOOLS-16) NullPointerException when site URL is being generated

2012-04-05 Thread Dennis Lundberg (JIRA)

 [ 
https://jira.codehaus.org/browse/DOXIATOOLS-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Lundberg closed DOXIATOOLS-16.
-

   Resolution: Fixed
Fix Version/s: doxia-integration-tools-1.5
 Assignee: Dennis Lundberg

Fixed in [r1310106|http://svn.apache.org/viewvc?view=revisionrevision=1310106].

 NullPointerException when site URL is being generated
 -

 Key: DOXIATOOLS-16
 URL: https://jira.codehaus.org/browse/DOXIATOOLS-16
 Project: Maven Doxia Tools
  Issue Type: Bug
  Components: Doxia Integration Tools
 Environment: environment independent
Reporter: Marc Claessens
Assignee: Dennis Lundberg
 Fix For: doxia-integration-tools-1.5


 We have a parent POM where the site url is generated via the Maven Groovy 
 plugin, unless it is explicitly defined in the child POM
 i.e.
 site
idproject-sites/id
nameOur project Nexus server Site/name
!-- URL is built dynamically by groovy plugin --
 /site
 ...
 plugin
groupIdorg.codehaus.groovy.maven/groupId
artifactIdgmaven-plugin/artifactId
executions
   execution
   phasepre-site/phase
   goals
  goalexecute/goal
   /goals
   configuration
   source
   ![CDATA[
if(!project.distributionManagement.site.url){
 String version = new String(project.version)
 String path = new String(project.artifactId)+'/'+version
 project.distributionManagement.site.url 
 ='dav:'+project.properties['siteBaseURL'] + path
}
   ]]
   /source
   /configuration
   /execution
/executions
 /plugin
  }
 This leads to a NullPointerException in DefaultSiteTool.java:
 at java.io.File.init(File.java:222)
 at 
 org.apache.maven.doxia.tools.DefaultSiteTool.urlEncode(DefaultSiteTool.java:1478)
 at 
 org.apache.maven.doxia.tools.DefaultSiteTool.getDistMgmntSiteUrl(DefaultSiteTool.java:1451)
 The if statement in getDistMgntSiteUrl (for both methods) should test for 
 null on project.getDistributionManagement().getSite().getUrl()

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (SUREFIRE-857) Non-ASCII source and name in ReportEntry are escaped unicode on fork.

2012-04-05 Thread Seiji KOMATSU (JIRA)

[ 
https://jira.codehaus.org/browse/SUREFIRE-857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=295983#comment-295983
 ] 

Seiji KOMATSU commented on SUREFIRE-857:


I've also been embarrassed with this behavior.
I think this behavior is much problem for non-ascii language region people.

I'm Japanese, so I usually use multibyte characters for test case methods.

Example:
{code}
public void 
testExecute_#26908;#35388;#22833;#25943;_#12525;#12464;#12452;#12531;#65321;#65316;#19981;#27491;()
 throws Example {
}
{code}

The above case can be written in only ascii characters, as follows:
{code}
public void testExecute_ValidationFailed_LoginIdIsWrong() throws Example {
}
{code}

But, prior to version 2.9 (I've confirmed at version 2.8.1), the result of the 
first case is good,
and from version 2.9 the result of that is escaped, and human-unreadable.

I hope the patch the ticket owner attached will be applied as soon as possible.

 Non-ASCII source and name in ReportEntry are escaped unicode on fork.
 -

 Key: SUREFIRE-857
 URL: https://jira.codehaus.org/browse/SUREFIRE-857
 Project: Maven Surefire
  Issue Type: Bug
  Components: process forking
Affects Versions: 2.9, 2.10, 2.11, 2.12
Reporter: kayakiss
 Attachments: unescape.patch


 Non-ASCII source and name in ReportEntry are escaped unicode on fork. For 
 example 'À'(A with grave) is replaced \u00C0.
 {noformat}
 public class EscapeÀTest {
 @Test
 public void testÀTest() {
 }
 }
 {noformat}
 XML report of this test class is following.
 {noformat}
 testcase time=0.010 classname=Escape\u00C0Test name=test\u00C0Test
 {noformat}
 This problem is that 
 *org.apache.maven.plugin.surefire.booterclient.outpu.ForkClient* is not 
 unescape for ReportEntry source and name. Because these are escaped with 
 *org.apache.maven.surefire.booter.ForingRunListener*, *ForkClient* must be 
 unescaped.
 In the attached patch for 2.12 I fixed this problem.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (SUREFIRE-857) Non-ASCII source and name in ReportEntry are escaped unicode on fork.

2012-04-05 Thread Seiji KOMATSU (JIRA)

[ 
https://jira.codehaus.org/browse/SUREFIRE-857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=295983#comment-295983
 ] 

Seiji KOMATSU edited comment on SUREFIRE-857 at 4/5/12 11:28 PM:
-

I've also been embarrassed with this behavior.
I think this behavior is much problem for non-ascii language region people.

I'm Japanese, so I usually use multibyte characters for test case methods.

Example:
{code}
public void 
testExecute_#26908;#35388;#22833;#25943;_#12525;#12464;#12452;#12531;ID#19981;#27491;()
 throws Exception {
}
{code}

The above case can be written in only ascii characters, as follows:
{code}
public void testExecute_ValidationFailed_LoginIdIsWrong() throws Exception {
}
{code}

But, prior to version 2.9 (I've confirmed at version 2.8.1), the result of the 
first case is good,
and from version 2.9 the result of that is escaped, and human-unreadable.

I hope the patch the ticket owner attached will be applied as soon as possible.

  was (Author: skomatsu):
I've also been embarrassed with this behavior.
I think this behavior is much problem for non-ascii language region people.

I'm Japanese, so I usually use multibyte characters for test case methods.

Example:
{code}
public void 
testExecute_#26908;#35388;#22833;#25943;_#12525;#12464;#12452;#12531;#65321;#65316;#19981;#27491;()
 throws Example {
}
{code}

The above case can be written in only ascii characters, as follows:
{code}
public void testExecute_ValidationFailed_LoginIdIsWrong() throws Example {
}
{code}

But, prior to version 2.9 (I've confirmed at version 2.8.1), the result of the 
first case is good,
and from version 2.9 the result of that is escaped, and human-unreadable.

I hope the patch the ticket owner attached will be applied as soon as possible.
  
 Non-ASCII source and name in ReportEntry are escaped unicode on fork.
 -

 Key: SUREFIRE-857
 URL: https://jira.codehaus.org/browse/SUREFIRE-857
 Project: Maven Surefire
  Issue Type: Bug
  Components: process forking
Affects Versions: 2.9, 2.10, 2.11, 2.12
Reporter: kayakiss
 Attachments: unescape.patch


 Non-ASCII source and name in ReportEntry are escaped unicode on fork. For 
 example 'À'(A with grave) is replaced \u00C0.
 {noformat}
 public class EscapeÀTest {
 @Test
 public void testÀTest() {
 }
 }
 {noformat}
 XML report of this test class is following.
 {noformat}
 testcase time=0.010 classname=Escape\u00C0Test name=test\u00C0Test
 {noformat}
 This problem is that 
 *org.apache.maven.plugin.surefire.booterclient.outpu.ForkClient* is not 
 unescape for ReportEntry source and name. Because these are escaped with 
 *org.apache.maven.surefire.booter.ForingRunListener*, *ForkClient* must be 
 unescaped.
 In the attached patch for 2.12 I fixed this problem.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (SUREFIRE-857) Non-ASCII source and name in ReportEntry are escaped unicode on fork.

2012-04-05 Thread Seiji KOMATSU (JIRA)

[ 
https://jira.codehaus.org/browse/SUREFIRE-857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=295983#comment-295983
 ] 

Seiji KOMATSU edited comment on SUREFIRE-857 at 4/5/12 11:32 PM:
-

I've also been embarrassed with this behavior.
I think this behavior is much problem for non-ascii language region people.

I'm Japanese, so I usually use multibyte characters for test case methods.

Example:
see https://gist.github.com/2316871

Prior to version 2.9 (I've confirmed at version 2.8.1), the result of the first 
case is good,
and from version 2.9 the result of that is escaped, and human-unreadable.

I hope the patch the ticket owner attached will be applied as soon as possible.

  was (Author: skomatsu):
I've also been embarrassed with this behavior.
I think this behavior is much problem for non-ascii language region people.

I'm Japanese, so I usually use multibyte characters for test case methods.

Example:
{code}
public void 
testExecute_#26908;#35388;#22833;#25943;_#12525;#12464;#12452;#12531;ID#19981;#27491;()
 throws Exception {
}
{code}

The above case can be written in only ascii characters, as follows:
{code}
public void testExecute_ValidationFailed_LoginIdIsWrong() throws Exception {
}
{code}

But, prior to version 2.9 (I've confirmed at version 2.8.1), the result of the 
first case is good,
and from version 2.9 the result of that is escaped, and human-unreadable.

I hope the patch the ticket owner attached will be applied as soon as possible.
  
 Non-ASCII source and name in ReportEntry are escaped unicode on fork.
 -

 Key: SUREFIRE-857
 URL: https://jira.codehaus.org/browse/SUREFIRE-857
 Project: Maven Surefire
  Issue Type: Bug
  Components: process forking
Affects Versions: 2.9, 2.10, 2.11, 2.12
Reporter: kayakiss
 Attachments: unescape.patch


 Non-ASCII source and name in ReportEntry are escaped unicode on fork. For 
 example 'À'(A with grave) is replaced \u00C0.
 {noformat}
 public class EscapeÀTest {
 @Test
 public void testÀTest() {
 }
 }
 {noformat}
 XML report of this test class is following.
 {noformat}
 testcase time=0.010 classname=Escape\u00C0Test name=test\u00C0Test
 {noformat}
 This problem is that 
 *org.apache.maven.plugin.surefire.booterclient.outpu.ForkClient* is not 
 unescape for ReportEntry source and name. Because these are escaped with 
 *org.apache.maven.surefire.booter.ForingRunListener*, *ForkClient* must be 
 unescaped.
 In the attached patch for 2.12 I fixed this problem.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (DOXIASITETOOLS-70) Html title of generated pages does not include project name

2012-04-05 Thread Heinrich Schuchardt (JIRA)

 [ 
https://jira.codehaus.org/browse/DOXIASITETOOLS-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Heinrich Schuchardt updated DOXIASITETOOLS-70:
--

Attachment: pom.xml

Pom with dependency added.

 Html title of generated pages does not include project name
 ---

 Key: DOXIASITETOOLS-70
 URL: https://jira.codehaus.org/browse/DOXIASITETOOLS-70
 Project: Maven Doxia Sitetools
  Issue Type: Bug
  Components: Site renderer
Affects Versions: 1.2
 Environment: Apache Maven 3.0.3 
 (rNON-CANONICAL_2011-04-10_05-06_zfsdt; 2011-04-10 05:06:31+0200)
 Maven home: /usr/local/apache-maven/apache-maven-3.0.3
 Java version: 1.6.0_18, vendor: Sun Microsystems Inc.
 Java home: /usr/lib/jvm/java-6-openjdk/jre
 Default locale: en_US, platform encoding: ANSI_X3.4-1968
 OS name: linux, version: 2.6.18-028stab092.1, arch: amd64, family: 
 unix
Reporter: Heinrich Schuchardt
Assignee: Dennis Lundberg
 Fix For: 1.3

 Attachments: pom.xml, pom.xml


 Dear maintainer,
 according to 
 http://maven.apache.org/plugins/maven-site-plugin/examples/sitedescriptor.html
  the title of each page should be the concatenation of the site title and the 
 title of the current page. E.g. if in pom.xml the name element is:
 nameSite Plugin Test/name
 then target/site/index.html should have a line
 titleSite Plugin Test - Abouttitle
 This is not working. The site title is missing and the created index.html 
 only contains
 titleAbout/title
 This effects how the page is shown in Google, Bing and other search engines. 
 To have the page correctly related in search machines with the project it is 
 desirable to have the project name in the HTML title.
 For testing you can use the appended pom.xml
 Best regards
 Heinrich Schuchardt

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (DOXIASITETOOLS-70) Html title of generated pages does not include project name

2012-04-05 Thread Heinrich Schuchardt (JIRA)

 [ 
https://jira.codehaus.org/browse/DOXIASITETOOLS-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Heinrich Schuchardt reopened DOXIASITETOOLS-70:
---


I added the dependency as proposed. The bug still occurs.

 Html title of generated pages does not include project name
 ---

 Key: DOXIASITETOOLS-70
 URL: https://jira.codehaus.org/browse/DOXIASITETOOLS-70
 Project: Maven Doxia Sitetools
  Issue Type: Bug
  Components: Site renderer
Affects Versions: 1.2
 Environment: Apache Maven 3.0.3 
 (rNON-CANONICAL_2011-04-10_05-06_zfsdt; 2011-04-10 05:06:31+0200)
 Maven home: /usr/local/apache-maven/apache-maven-3.0.3
 Java version: 1.6.0_18, vendor: Sun Microsystems Inc.
 Java home: /usr/lib/jvm/java-6-openjdk/jre
 Default locale: en_US, platform encoding: ANSI_X3.4-1968
 OS name: linux, version: 2.6.18-028stab092.1, arch: amd64, family: 
 unix
Reporter: Heinrich Schuchardt
Assignee: Dennis Lundberg
 Fix For: 1.3

 Attachments: pom.xml, pom.xml


 Dear maintainer,
 according to 
 http://maven.apache.org/plugins/maven-site-plugin/examples/sitedescriptor.html
  the title of each page should be the concatenation of the site title and the 
 title of the current page. E.g. if in pom.xml the name element is:
 nameSite Plugin Test/name
 then target/site/index.html should have a line
 titleSite Plugin Test - Abouttitle
 This is not working. The site title is missing and the created index.html 
 only contains
 titleAbout/title
 This effects how the page is shown in Google, Bing and other search engines. 
 To have the page correctly related in search machines with the project it is 
 desirable to have the project name in the HTML title.
 For testing you can use the appended pom.xml
 Best regards
 Heinrich Schuchardt

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira