[jira] (DOXIA-484) pegdown dependency is 3 revisions out of date

2013-04-04 Thread Malachi de AElfweald (JIRA) 

[ 
https://jira.codehaus.org/browse/DOXIA-484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=323195#comment-323195
 ] 

Malachi de AElfweald commented on DOXIA-484:


Sorry, I haven't had a chance to work on it.  The tests are the real problem 
for me.  What is the correct process for updating the list of tests?

 pegdown dependency is 3 revisions out of date
 -

 Key: DOXIA-484
 URL: https://jira.codehaus.org/browse/DOXIA-484
 Project: Maven Doxia
  Issue Type: Improvement
  Components: Module - Markdown
Affects Versions: 1.3
 Environment: Apache Maven 3.0.4 (r1232337; 2012-01-17 00:44:56-0800)
 Maven home: /usr/local/maven
 Java version: 1.6.0_41, vendor: Sun Microsystems Inc.
 Java home: /usr/lib/jvm/java-6-oracle/jre
 Default locale: en_US, platform encoding: UTF-8
 OS name: linux, version: 3.5.0-25-generic, arch: amd64, family: unix
Reporter: Malachi de AElfweald
Priority: Minor

 From the CHANGELOG
 {noformat}
 Version 1.2.1 (2011-11-27)
 --
 - Upgraded to parboiled 1.1.4
 - Added support for caption on tables (thx to Geoffrey Picron)
 Version 1.2.0 (2011-10-05)
 --
 - Upgraded to parboiled 1.1.3
 - Implemented parsing timeout, closes #42
 - Fixed IndexOutOfBoundsException in ToHtmlSerializer, closes #39
 - Changed parser to not swallow backslash before non-special characters, 
 fixes #35
 - Added test for fenced code blocks containing an empty line, closes #61
 - Migrated all tests from TestNG to specs2
 - Switched build tool from Apache Buildr to SBT
 Version 1.1.0 (2011-10-05)
 --
 - Upgraded to parboiled 1.0.2
 - Introduced LinkRenderer layer for easy customization of HTML link rendering
 - Added support for [[Wiki-style]] links, thx to Brett Porter
 - Fixed #27 (Missing emphasis when paragraph has multiple lines)
 - Fixed #28 (Parser not fully extensible)
 - Fixed #32, #33 (HTML tags with attribute names containing underscores are 
 not recognized as tags, thx to Edward Samson)
 - Fixed #34 (Pathologically slow parsing when strong and italics emphasis are 
 applied together)
 {noformat}

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

[jira] (DOXIA-484) pegdown dependency is 3 revisions out of date

2013-04-04 Thread Malachi de AElfweald (JIRA) 

[ 
https://jira.codehaus.org/browse/DOXIA-484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=323200#comment-323200
 ] 

Malachi de AElfweald commented on DOXIA-484:


Yeah I saw that. It looked like it tried to concatenate all their tests into 
one file.  I managed to finagle that into happening, but the tests didn't pass.

Is there maybe a better option?  Should we modify existing test to pass the new 
code?

 pegdown dependency is 3 revisions out of date
 -

 Key: DOXIA-484
 URL: https://jira.codehaus.org/browse/DOXIA-484
 Project: Maven Doxia
  Issue Type: Improvement
  Components: Module - Markdown
Affects Versions: 1.3
 Environment: Apache Maven 3.0.4 (r1232337; 2012-01-17 00:44:56-0800)
 Maven home: /usr/local/maven
 Java version: 1.6.0_41, vendor: Sun Microsystems Inc.
 Java home: /usr/lib/jvm/java-6-oracle/jre
 Default locale: en_US, platform encoding: UTF-8
 OS name: linux, version: 3.5.0-25-generic, arch: amd64, family: unix
Reporter: Malachi de AElfweald
Priority: Minor

 From the CHANGELOG
 {noformat}
 Version 1.2.1 (2011-11-27)
 --
 - Upgraded to parboiled 1.1.4
 - Added support for caption on tables (thx to Geoffrey Picron)
 Version 1.2.0 (2011-10-05)
 --
 - Upgraded to parboiled 1.1.3
 - Implemented parsing timeout, closes #42
 - Fixed IndexOutOfBoundsException in ToHtmlSerializer, closes #39
 - Changed parser to not swallow backslash before non-special characters, 
 fixes #35
 - Added test for fenced code blocks containing an empty line, closes #61
 - Migrated all tests from TestNG to specs2
 - Switched build tool from Apache Buildr to SBT
 Version 1.1.0 (2011-10-05)
 --
 - Upgraded to parboiled 1.0.2
 - Introduced LinkRenderer layer for easy customization of HTML link rendering
 - Added support for [[Wiki-style]] links, thx to Brett Porter
 - Fixed #27 (Missing emphasis when paragraph has multiple lines)
 - Fixed #28 (Parser not fully extensible)
 - Fixed #32, #33 (HTML tags with attribute names containing underscores are 
 not recognized as tags, thx to Edward Samson)
 - Fixed #34 (Pathologically slow parsing when strong and italics emphasis are 
 applied together)
 {noformat}

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

[jira] (DOXIA-484) pegdown dependency is 3 revisions out of date

2013-03-13 Thread Malachi de AElfweald (JIRA) 

[ 
https://jira.codehaus.org/browse/DOXIA-484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=321909#comment-321909
 ] 

Malachi de AElfweald commented on DOXIA-484:


I spent a little time between meetings looking at this yesterday.  There wasn't 
much code change required (copying one method from a prior tag, removing a 
parameter from another call, etc).  It compiled OK, but the tests didn't pass.  
I'll try to look into it some more if I get a chance.

 pegdown dependency is 3 revisions out of date
 -

 Key: DOXIA-484
 URL: https://jira.codehaus.org/browse/DOXIA-484
 Project: Maven Doxia
  Issue Type: Improvement
  Components: Module - Markdown
Affects Versions: 1.3
 Environment: Apache Maven 3.0.4 (r1232337; 2012-01-17 00:44:56-0800)
 Maven home: /usr/local/maven
 Java version: 1.6.0_41, vendor: Sun Microsystems Inc.
 Java home: /usr/lib/jvm/java-6-oracle/jre
 Default locale: en_US, platform encoding: UTF-8
 OS name: linux, version: 3.5.0-25-generic, arch: amd64, family: unix
Reporter: Malachi de AElfweald
Priority: Minor

 From the CHANGELOG
 {noformat}
 Version 1.2.1 (2011-11-27)
 --
 - Upgraded to parboiled 1.1.4
 - Added support for caption on tables (thx to Geoffrey Picron)
 Version 1.2.0 (2011-10-05)
 --
 - Upgraded to parboiled 1.1.3
 - Implemented parsing timeout, closes #42
 - Fixed IndexOutOfBoundsException in ToHtmlSerializer, closes #39
 - Changed parser to not swallow backslash before non-special characters, 
 fixes #35
 - Added test for fenced code blocks containing an empty line, closes #61
 - Migrated all tests from TestNG to specs2
 - Switched build tool from Apache Buildr to SBT
 Version 1.1.0 (2011-10-05)
 --
 - Upgraded to parboiled 1.0.2
 - Introduced LinkRenderer layer for easy customization of HTML link rendering
 - Added support for [[Wiki-style]] links, thx to Brett Porter
 - Fixed #27 (Missing emphasis when paragraph has multiple lines)
 - Fixed #28 (Parser not fully extensible)
 - Fixed #32, #33 (HTML tags with attribute names containing underscores are 
 not recognized as tags, thx to Edward Samson)
 - Fixed #34 (Pathologically slow parsing when strong and italics emphasis are 
 applied together)
 {noformat}

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

[jira] (DOXIA-484) pegdown dependency is 3 revisions out of date

2013-03-12 Thread Malachi de AElfweald (JIRA) 
Malachi de AElfweald created DOXIA-484:
--

 Summary: pegdown dependency is 3 revisions out of date
 Key: DOXIA-484
 URL: https://jira.codehaus.org/browse/DOXIA-484
 Project: Maven Doxia
  Issue Type: Improvement
  Components: Module - Markdown
Affects Versions: 1.3
 Environment: Apache Maven 3.0.4 (r1232337; 2012-01-17 00:44:56-0800)
Maven home: /usr/local/maven
Java version: 1.6.0_41, vendor: Sun Microsystems Inc.
Java home: /usr/lib/jvm/java-6-oracle/jre
Default locale: en_US, platform encoding: UTF-8
OS name: linux, version: 3.5.0-25-generic, arch: amd64, family: unix
Reporter: Malachi de AElfweald
Priority: Minor


From the CHANGELOG

{noformat}
Version 1.2.1 (2011-11-27)
--
- Upgraded to parboiled 1.1.4
- Added support for caption on tables (thx to Geoffrey Picron)


Version 1.2.0 (2011-10-05)
--
- Upgraded to parboiled 1.1.3
- Implemented parsing timeout, closes #42
- Fixed IndexOutOfBoundsException in ToHtmlSerializer, closes #39
- Changed parser to not swallow backslash before non-special characters, fixes 
#35
- Added test for fenced code blocks containing an empty line, closes #61
- Migrated all tests from TestNG to specs2
- Switched build tool from Apache Buildr to SBT


Version 1.1.0 (2011-10-05)
--
- Upgraded to parboiled 1.0.2
- Introduced LinkRenderer layer for easy customization of HTML link rendering
- Added support for [[Wiki-style]] links, thx to Brett Porter
- Fixed #27 (Missing emphasis when paragraph has multiple lines)
- Fixed #28 (Parser not fully extensible)
- Fixed #32, #33 (HTML tags with attribute names containing underscores are not 
recognized as tags, thx to Edward Samson)
- Fixed #34 (Pathologically slow parsing when strong and italics emphasis are 
applied together)

{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] (JXR-69) fails to create cross links in multi-module project

2012-12-02 Thread Malachi de AElfweald (JIRA) 

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

Malachi de AElfweald updated JXR-69:


Attachment: jxrtest.jar

Example source and output file showing that it doesn't work.  You'll notice in 
jxr-site/module2/xref/org/eoti/test/jxr/Module2.html that line 7 is not linked.

With an apklib/apk combo, this is even worse because the source of the apklib 
is actually used instead of the raw binary jar.  But the results are the same.

 fails to create cross links in multi-module project
 ---

 Key: JXR-69
 URL: https://jira.codehaus.org/browse/JXR-69
 Project: Maven JXR
  Issue Type: Bug
  Components: maven2 jxr plugin
Affects Versions: 2.1
Reporter: Giovanni Azua
 Fix For: 2.3

 Attachments: jxrtest.jar


 My build pulls jxr 2.1. Although I set the aggregate parameter to true, I 
 still don't get linked cross module references say e.g.
 Module A
 Interface X
 Module B (depends on A)
 Class Y implements X
 In the aggregate reports Class Y will not link to X.

--
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] (JXR-69) fails to create cross links in multi-module project

2012-12-02 Thread Malachi de AElfweald (JIRA) 

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

Malachi de AElfweald commented on JXR-69:
-

malachi@methe:~$ mvn --version
Apache Maven 3.0.4 (r1232337; 2012-01-17 00:44:56-0800)
Maven home: /usr/local/maven
Java version: 1.8.0-ea, vendor: Oracle Corporation
Java home: /usr/local/jdk1.8.0/jre
Default locale: en_US, platform encoding: UTF-8
OS name: linux, version: 3.2.0-3-rt-amd64, arch: amd64, family: unix

Here's the commands I was running:
mvn clean install site:site
mvn site:stage -DstagingDirectory=/home/malachi/work/test/jxr-site

I just tried with and without aggregation.  If I use aggregation, the source is 
at the top-level instead of the module level; but the linkage is the same.

 fails to create cross links in multi-module project
 ---

 Key: JXR-69
 URL: https://jira.codehaus.org/browse/JXR-69
 Project: Maven JXR
  Issue Type: Bug
  Components: maven2 jxr plugin
Affects Versions: 2.1
Reporter: Giovanni Azua
 Fix For: 2.3

 Attachments: jxrtest.jar


 My build pulls jxr 2.1. Although I set the aggregate parameter to true, I 
 still don't get linked cross module references say e.g.
 Module A
 Interface X
 Module B (depends on A)
 Class Y implements X
 In the aggregate reports Class Y will not link to X.

--
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] (JXR-69) fails to create cross links in multi-module project

2012-11-30 Thread Malachi de AElfweald (JIRA) 

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

Malachi de AElfweald commented on JXR-69:
-

This is still broken in 2.3

 fails to create cross links in multi-module project
 ---

 Key: JXR-69
 URL: https://jira.codehaus.org/browse/JXR-69
 Project: Maven JXR
  Issue Type: Bug
  Components: maven2 jxr plugin
Affects Versions: 2.1
Reporter: Giovanni Azua
 Fix For: 2.3


 My build pulls jxr 2.1. Although I set the aggregate parameter to true, I 
 still don't get linked cross module references say e.g.
 Module A
 Interface X
 Module B (depends on A)
 Class Y implements X
 In the aggregate reports Class Y will not link to X.

--
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] (JXR-69) fails to create cross links in multi-module project

2012-11-30 Thread Malachi de AElfweald (JIRA) 

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

Malachi de AElfweald commented on JXR-69:
-

I'll try to put one together for you.  In my current use-case, module1 is an 
apklib and module2 is an apk.  Maybe that's part of it?

 fails to create cross links in multi-module project
 ---

 Key: JXR-69
 URL: https://jira.codehaus.org/browse/JXR-69
 Project: Maven JXR
  Issue Type: Bug
  Components: maven2 jxr plugin
Affects Versions: 2.1
Reporter: Giovanni Azua
 Fix For: 2.3


 My build pulls jxr 2.1. Although I set the aggregate parameter to true, I 
 still don't get linked cross module references say e.g.
 Module A
 Interface X
 Module B (depends on A)
 Class Y implements X
 In the aggregate reports Class Y will not link to X.

--
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] Reopened: (MSITE-424) Unable to perform release

2009-12-09 Thread Malachi de AElfweald (JIRA) 

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

Malachi de AElfweald reopened MSITE-424:



This should not have been closed as duplicate. MSITE-419 is now done but only 
fixed 1/2 the problem. Releases still can not be done until the site plugin is 
released / tagged.

 Unable to perform release
 -

 Key: MSITE-424
 URL: http://jira.codehaus.org/browse/MSITE-424
 Project: Maven 2.x Site Plugin
  Issue Type: Task
  Components: doxia integration
Affects Versions: 2.1
Reporter: Malachi de AElfweald
Priority: Blocker

 I am unable to perform a release because I depend on doxia 1.1.1 for 
 DOXIA-309, DOXIA-310 and DOXIA-311
 The last tagged version of the site plugin is 2.0.1 which relies on doxia 1.0
 The current trunk version depends on doxia 1.1.2-SNAPSHOT
 I need a tagged version of the site plugin built against doxia 1.1.1 or later 
 so that I can perform a release

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Created: (MSITE-424) Unable to perform release

2009-08-21 Thread Malachi de AElfweald (JIRA) 
Unable to perform release
-

 Key: MSITE-424
 URL: http://jira.codehaus.org/browse/MSITE-424
 Project: Maven 2.x Site Plugin
  Issue Type: Task
  Components: doxia integration
Affects Versions: 2.1
Reporter: Malachi de AElfweald
Priority: Blocker


I am unable to perform a release because I depend on doxia 1.1.1 for DOXIA-309, 
DOXIA-310 and DOXIA-311

The last tagged version of the site plugin is 2.0.1 which relies on doxia 1.0
The current trunk version depends on doxia 1.1.2-SNAPSHOT

I need a tagged version of the site plugin built against doxia 1.1.1 or later 
so that I can perform a release

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (MJAVADOC-246) ExceptionInInitializerError

2009-08-11 Thread Malachi de AElfweald (JIRA) 

[ 
http://jira.codehaus.org/browse/MJAVADOC-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=186699#action_186699
 ] 

Malachi de AElfweald commented on MJAVADOC-246:
---

I misspoke earlier.  In addition to changing to 2.6-SNAPSHOT I had changed the 
maven-site-plugin version (and thus broke other parts of the site). Changing 
the maven-site-plugin back to 2.1-SNAPSHOT w/ javadoc at 2.6-SNAPSHOT I still 
get the error.

 ExceptionInInitializerError
 ---

 Key: MJAVADOC-246
 URL: http://jira.codehaus.org/browse/MJAVADOC-246
 Project: Maven 2.x Javadoc Plugin
  Issue Type: Bug
Affects Versions: 2.6
 Environment: Hudson or command-line
 Maven 2.1.0 or 2.2.0
 JDK 1.6 or JDK 1.7
 OpenSolaris
Reporter: Malachi de AElfweald
Priority: Blocker
 Fix For: 2.6.1


 This bug only happens if I have maven-javadoc-plugin enabled. If I comment it 
 out site generation works.  The POM is not specifying a particular version so 
 I am not sure which one it is using.
 These bugs seem to report the same problem against other plugins:
 http://jira.codehaus.org/browse/MOJO-1118
 http://jira.codehaus.org/browse/MOJO-1101
 Based on the error message, I checked the repository after successfully 
 building without JavaDoc and it shows these versions of commons-logging were 
 used:
   1.0
   1.0.3
   1.0.4
   1.1
 The only SNAPSHOT dependency is 2.1-SNAPSHOT of the maven-site-plugin (to get 
 around site generation bugs).  I am using the -U during building.
 [INFO] Generating JavaDocs report.
 [FATAL ERROR] org.apache.maven.plugins.site.SiteMojo#execute() caused a 
 linkage error (java.lang.ExceptionInInitializerError) and may be out-of-date. 
 Check the realms:
 [FATAL ERROR] Plugin realm = 
 app0.child-container[org.apache.maven.plugins:maven-site-plugin:2.1-SNAPSHOT]
 urls[0] = 
 file:/home/hudson/.m2/repository/org/apache/maven/plugins/maven-site-plugin/2.1-SNAPSHOT/maven-site-plugin-2.1-SNAPSHOT.jar
 urls[1] = 
 file:/home/hudson/.m2/repository/org/codehaus/plexus/plexus-utils/1.5.1/plexus-utils-1.5.1.jar
 urls[2] = 
 file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-module-xhtml/1.1.2-SNAPSHOT/doxia-module-xhtml-1.1.2-SNAPSHOT.jar
 urls[3] = 
 file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-core/1.1.2-SNAPSHOT/doxia-core-1.1.2-SNAPSHOT.jar
 urls[4] = 
 file:/home/hudson/.m2/repository/xerces/xercesImpl/2.8.1/xercesImpl-2.8.1.jar
 urls[5] = 
 file:/home/hudson/.m2/repository/xml-apis/xml-apis/1.3.03/xml-apis-1.3.03.jar
 urls[6] = 
 file:/home/hudson/.m2/repository/commons-lang/commons-lang/2.4/commons-lang-2.4.jar
 urls[7] = 
 file:/home/hudson/.m2/repository/commons-httpclient/commons-httpclient/3.1/commons-httpclient-3.1.jar
 urls[8] = 
 file:/home/hudson/.m2/repository/commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.jar
 urls[9] = 
 file:/home/hudson/.m2/repository/commons-codec/commons-codec/1.2/commons-codec-1.2.jar
 urls[10] = 
 file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-module-apt/1.1.2-SNAPSHOT/doxia-module-apt-1.1.2-SNAPSHOT.jar
 urls[11] = 
 file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-module-xdoc/1.1.2-SNAPSHOT/doxia-module-xdoc-1.1.2-SNAPSHOT.jar
 urls[12] = 
 file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-module-fml/1.1.2-SNAPSHOT/doxia-module-fml-1.1.2-SNAPSHOT.jar
 urls[13] = 
 file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-decoration-model/1.1.2-SNAPSHOT/doxia-decoration-model-1.1.2-SNAPSHOT.jar
 urls[14] = 
 file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-site-renderer/1.1.2-SNAPSHOT/doxia-site-renderer-1.1.2-SNAPSHOT.jar
 urls[15] = 
 file:/home/hudson/.m2/repository/org/codehaus/plexus/plexus-i18n/1.0-beta-7/plexus-i18n-1.0-beta-7.jar
 urls[16] = 
 file:/home/hudson/.m2/repository/org/codehaus/plexus/plexus-velocity/1.1.7/plexus-velocity-1.1.7.jar
 urls[17] = 
 file:/home/hudson/.m2/repository/org/apache/velocity/velocity/1.5/velocity-1.5.jar
 urls[18] = 
 file:/home/hudson/.m2/repository/commons-collections/commons-collections/3.2/commons-collections-3.2.jar
 urls[19] = file:/home/hudson/.m2/repository/oro/oro/2.0.8/oro-2.0.8.jar
 urls[20] = 
 file:/home/hudson/.m2/repository/org/apache/maven/shared/maven-doxia-tools/1.1-SNAPSHOT/maven-doxia-tools-1.1-SNAPSHOT.jar
 urls[21] = 
 file:/home/hudson/.m2/repository/commons-io/commons-io/1.4/commons-io-1.4.jar
 urls[22] = 
 file:/home/hudson/.m2/repository/org/codehaus/plexus/plexus-archiver/1.0-alpha-7/plexus-archiver-1.0-alpha-7.jar
 urls[23] = 
 file:/home/hudson/.m2/repository/org/mortbay/jetty/jetty/6.1.5/jetty-6.1.5.jar
 urls[24] = 
 file:/home/hudson/.m2/repository/org/mortbay/jetty/jetty-util/6.1.5/jetty-util-6.1.5.jar
 urls[25] =

[jira] Commented: (MJAVADOC-246) ExceptionInInitializerError

2009-08-03 Thread Malachi de AElfweald (JIRA) 

[ 
http://jira.codehaus.org/browse/MJAVADOC-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=185759#action_185759
 ] 

Malachi de AElfweald commented on MJAVADOC-246:
---

2.6-SNAPSHOT does appear to have fixed that issue; leaving behind a weird side 
effect:

[INFO] Generating JavaDocs report.
Aug 3, 2009 10:15:45 AM org.apache.commons.httpclient.HttpMethodBase 
processCookieHeaders
WARNING: Cookie rejected: $Version=0; 
JSESSIONID=50AF6CD52E5016EFA7D533AF6DD95394; $Path=/servlets. Illegal path 
attribute /servlets. Path of origin: /nonav/maven/apidocs/package-list
[INFO] The goal 
'org.apache.maven.plugins:maven-javadoc-plugin:2.6-SNAPSHOT:javadoc' has not be 
previously called for the project: 
'org.eoti.maven.skins:ljod:jar:2.3-SNAPSHOT'. Trying to invoke it...
[INFO] The goal 
'org.apache.maven.plugins:maven-javadoc-plugin:2.6-SNAPSHOT:javadoc' has not be 
previously called for the project: 'org.eoti:seshat:jar:2.3-SNAPSHOT'. Trying 
to invoke it...
[INFO] The goal 
'org.apache.maven.plugins:maven-javadoc-plugin:2.6-SNAPSHOT:javadoc' has not be 
previously called for the project: 'org.eoti:clotho:jar:2.3-SNAPSHOT'. Trying 
to invoke it...
[INFO] The goal 
'org.apache.maven.plugins:maven-javadoc-plugin:2.6-SNAPSHOT:javadoc' has not be 
previously called for the project: 'org.eoti:lachesis:jar:2.3-SNAPSHOT'. Trying 
to invoke it...
[INFO] The goal 
'org.apache.maven.plugins:maven-javadoc-plugin:2.6-SNAPSHOT:javadoc' has not be 
previously called for the project: 'org.eoti:atropos:jar:2.3-SNAPSHOT'. Trying 
to invoke it...
Loading source files for package org.eoti.rei.cmp...


 ExceptionInInitializerError
 ---

 Key: MJAVADOC-246
 URL: http://jira.codehaus.org/browse/MJAVADOC-246
 Project: Maven 2.x Javadoc Plugin
  Issue Type: Bug
Affects Versions: 2.6
 Environment: Hudson or command-line
 Maven 2.1.0 or 2.2.0
 JDK 1.6 or JDK 1.7
 OpenSolaris
Reporter: Malachi de AElfweald
Priority: Blocker
 Fix For: 2.6.1


 This bug only happens if I have maven-javadoc-plugin enabled. If I comment it 
 out site generation works.  The POM is not specifying a particular version so 
 I am not sure which one it is using.
 These bugs seem to report the same problem against other plugins:
 http://jira.codehaus.org/browse/MOJO-1118
 http://jira.codehaus.org/browse/MOJO-1101
 Based on the error message, I checked the repository after successfully 
 building without JavaDoc and it shows these versions of commons-logging were 
 used:
   1.0
   1.0.3
   1.0.4
   1.1
 The only SNAPSHOT dependency is 2.1-SNAPSHOT of the maven-site-plugin (to get 
 around site generation bugs).  I am using the -U during building.
 [INFO] Generating JavaDocs report.
 [FATAL ERROR] org.apache.maven.plugins.site.SiteMojo#execute() caused a 
 linkage error (java.lang.ExceptionInInitializerError) and may be out-of-date. 
 Check the realms:
 [FATAL ERROR] Plugin realm = 
 app0.child-container[org.apache.maven.plugins:maven-site-plugin:2.1-SNAPSHOT]
 urls[0] = 
 file:/home/hudson/.m2/repository/org/apache/maven/plugins/maven-site-plugin/2.1-SNAPSHOT/maven-site-plugin-2.1-SNAPSHOT.jar
 urls[1] = 
 file:/home/hudson/.m2/repository/org/codehaus/plexus/plexus-utils/1.5.1/plexus-utils-1.5.1.jar
 urls[2] = 
 file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-module-xhtml/1.1.2-SNAPSHOT/doxia-module-xhtml-1.1.2-SNAPSHOT.jar
 urls[3] = 
 file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-core/1.1.2-SNAPSHOT/doxia-core-1.1.2-SNAPSHOT.jar
 urls[4] = 
 file:/home/hudson/.m2/repository/xerces/xercesImpl/2.8.1/xercesImpl-2.8.1.jar
 urls[5] = 
 file:/home/hudson/.m2/repository/xml-apis/xml-apis/1.3.03/xml-apis-1.3.03.jar
 urls[6] = 
 file:/home/hudson/.m2/repository/commons-lang/commons-lang/2.4/commons-lang-2.4.jar
 urls[7] = 
 file:/home/hudson/.m2/repository/commons-httpclient/commons-httpclient/3.1/commons-httpclient-3.1.jar
 urls[8] = 
 file:/home/hudson/.m2/repository/commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.jar
 urls[9] = 
 file:/home/hudson/.m2/repository/commons-codec/commons-codec/1.2/commons-codec-1.2.jar
 urls[10] = 
 file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-module-apt/1.1.2-SNAPSHOT/doxia-module-apt-1.1.2-SNAPSHOT.jar
 urls[11] = 
 file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-module-xdoc/1.1.2-SNAPSHOT/doxia-module-xdoc-1.1.2-SNAPSHOT.jar
 urls[12] = 
 file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-module-fml/1.1.2-SNAPSHOT/doxia-module-fml-1.1.2-SNAPSHOT.jar
 urls[13] = 
 file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-decoration-model/1.1.2-SNAPSHOT/doxia-decoration-model-1.1.2-SNAPSHOT.jar
 urls[14] =

[jira] Created: (MJAVADOC-246) ExceptionInInitializerError

2009-07-29 Thread Malachi de AElfweald (JIRA) 
ExceptionInInitializerError
---

 Key: MJAVADOC-246
 URL: http://jira.codehaus.org/browse/MJAVADOC-246
 Project: Maven 2.x Javadoc Plugin
  Issue Type: Bug
 Environment: Hudson or command-line
Maven 2.1.0 or 2.2.0
JDK 1.6 or JDK 1.7
OpenSolaris
Reporter: Malachi de AElfweald


This bug only happens if I have maven-javadoc-plugin enabled. If I comment it 
out site generation works.  The POM is not specifying a particular version so I 
am not sure which one it is using.

These bugs seem to report the same problem against other plugins:
http://jira.codehaus.org/browse/MOJO-1118
http://jira.codehaus.org/browse/MOJO-1101

Based on the error message, I checked the repository after successfully 
building without JavaDoc and it shows these versions of commons-logging were 
used:
1.0
1.0.3
1.0.4
1.1

The only SNAPSHOT dependency is 2.1-SNAPSHOT of the maven-site-plugin (to get 
around site generation bugs).  I am using the -U during building.

[INFO] Generating JavaDocs report.
[FATAL ERROR] org.apache.maven.plugins.site.SiteMojo#execute() caused a linkage 
error (java.lang.ExceptionInInitializerError) and may be out-of-date. Check the 
realms:
[FATAL ERROR] Plugin realm = 
app0.child-container[org.apache.maven.plugins:maven-site-plugin:2.1-SNAPSHOT]
urls[0] = 
file:/home/hudson/.m2/repository/org/apache/maven/plugins/maven-site-plugin/2.1-SNAPSHOT/maven-site-plugin-2.1-SNAPSHOT.jar
urls[1] = 
file:/home/hudson/.m2/repository/org/codehaus/plexus/plexus-utils/1.5.1/plexus-utils-1.5.1.jar
urls[2] = 
file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-module-xhtml/1.1.2-SNAPSHOT/doxia-module-xhtml-1.1.2-SNAPSHOT.jar
urls[3] = 
file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-core/1.1.2-SNAPSHOT/doxia-core-1.1.2-SNAPSHOT.jar
urls[4] = 
file:/home/hudson/.m2/repository/xerces/xercesImpl/2.8.1/xercesImpl-2.8.1.jar
urls[5] = 
file:/home/hudson/.m2/repository/xml-apis/xml-apis/1.3.03/xml-apis-1.3.03.jar
urls[6] = 
file:/home/hudson/.m2/repository/commons-lang/commons-lang/2.4/commons-lang-2.4.jar
urls[7] = 
file:/home/hudson/.m2/repository/commons-httpclient/commons-httpclient/3.1/commons-httpclient-3.1.jar
urls[8] = 
file:/home/hudson/.m2/repository/commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.jar
urls[9] = 
file:/home/hudson/.m2/repository/commons-codec/commons-codec/1.2/commons-codec-1.2.jar
urls[10] = 
file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-module-apt/1.1.2-SNAPSHOT/doxia-module-apt-1.1.2-SNAPSHOT.jar
urls[11] = 
file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-module-xdoc/1.1.2-SNAPSHOT/doxia-module-xdoc-1.1.2-SNAPSHOT.jar
urls[12] = 
file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-module-fml/1.1.2-SNAPSHOT/doxia-module-fml-1.1.2-SNAPSHOT.jar
urls[13] = 
file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-decoration-model/1.1.2-SNAPSHOT/doxia-decoration-model-1.1.2-SNAPSHOT.jar
urls[14] = 
file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-site-renderer/1.1.2-SNAPSHOT/doxia-site-renderer-1.1.2-SNAPSHOT.jar
urls[15] = 
file:/home/hudson/.m2/repository/org/codehaus/plexus/plexus-i18n/1.0-beta-7/plexus-i18n-1.0-beta-7.jar
urls[16] = 
file:/home/hudson/.m2/repository/org/codehaus/plexus/plexus-velocity/1.1.7/plexus-velocity-1.1.7.jar
urls[17] = 
file:/home/hudson/.m2/repository/org/apache/velocity/velocity/1.5/velocity-1.5.jar
urls[18] = 
file:/home/hudson/.m2/repository/commons-collections/commons-collections/3.2/commons-collections-3.2.jar
urls[19] = file:/home/hudson/.m2/repository/oro/oro/2.0.8/oro-2.0.8.jar
urls[20] = 
file:/home/hudson/.m2/repository/org/apache/maven/shared/maven-doxia-tools/1.1-SNAPSHOT/maven-doxia-tools-1.1-SNAPSHOT.jar
urls[21] = 
file:/home/hudson/.m2/repository/commons-io/commons-io/1.4/commons-io-1.4.jar
urls[22] = 
file:/home/hudson/.m2/repository/org/codehaus/plexus/plexus-archiver/1.0-alpha-7/plexus-archiver-1.0-alpha-7.jar
urls[23] = 
file:/home/hudson/.m2/repository/org/mortbay/jetty/jetty/6.1.5/jetty-6.1.5.jar
urls[24] = 
file:/home/hudson/.m2/repository/org/mortbay/jetty/jetty-util/6.1.5/jetty-util-6.1.5.jar
urls[25] = 
file:/home/hudson/.m2/repository/org/mortbay/jetty/servlet-api-2.5/6.1.5/servlet-api-2.5-6.1.5.jar
[FATAL ERROR] Container realm = plexus.core
urls[0] = file:/opt/apache-maven-2.1.0/lib/maven-2.1.0-uber.jar
[INFO] 
[ERROR] FATAL ERROR
[INFO] 
[INFO] null
Invalid class loader hierarchy.  You have more than one version of 
'org.apache.commons.logging.Log' visible, which is not allowed.
[INFO] 
[INFO] Trace
java.lang.ExceptionInInitializerError
at

[jira] Commented: (DOXIA-309) Ligature in author name shows up on page

2009-05-04 Thread Malachi de AElfweald (JIRA) 

[ 
http://jira.codehaus.org/browse/DOXIA-309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=175041#action_175041
 ] 

Malachi de AElfweald commented on DOXIA-309:


Verified that ligature in author is fixed

 Ligature in author name shows up on page
 

 Key: DOXIA-309
 URL: http://jira.codehaus.org/browse/DOXIA-309
 Project: Maven Doxia
  Issue Type: Bug
  Components: Core
Affects Versions: 1.1.1
 Environment: maven-site-plugin 2.1-SNAPSHOT w/ XDOC
Reporter: Malachi de AElfweald
Assignee: Vincent Siveton
Priority: Minor
 Fix For: 1.1.1

 Attachments: testcase.tgz


 followed these instructions to include the entity references:
 http://svn.apache.org/viewvc/maven/doxia/site/src/site/fml/faq.fml?annotate=739143pathrev=739143
 tried to set the author property:
 author email=malac...@gmail.comMalachi de AElig;lfweald/author
 The AE-ligature shows up as the first character on the page (top-left corner)
 Testcase attached
 testcase.html shows:
 link rel=stylesheet href=./css/print.css type=text/css 
 media=print /
   meta name=author content=
 Malachi de lfweald /
 #198;

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (DOXIA-310) Unable to get custom entity references to work

2009-05-04 Thread Malachi de AElfweald (JIRA) 

[ 
http://jira.codehaus.org/browse/DOXIA-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=175042#action_175042
 ] 

Malachi de AElfweald commented on DOXIA-310:


verified that customized entity names work now

 Unable to get custom entity references to work
 --

 Key: DOXIA-310
 URL: http://jira.codehaus.org/browse/DOXIA-310
 Project: Maven Doxia
  Issue Type: Bug
  Components: Core
Affects Versions: 1.1.1
 Environment: maven-site-plugin 2.1-SNAPSHOT w/ XDOC
Reporter: Malachi de AElfweald
Assignee: Vincent Siveton
 Fix For: 1.1.1

 Attachments: testcase.tgz


 followed these instructions:
 http://svn.apache.org/viewvc/maven/doxia/site/src/site/fml/faq.fml?annotate=739143pathrev=739143
 to include these entity references:
 http://kallisti.eoti.org/ambrosia/kallisti/trit.ent
 included test case has 3 different examples:
 1. using the character references defined in the trit.ent. Character 
 references were removed from the table during site:site
 2. using the character references by number. Character references were 
 replaced with '?' during site:site
 3. copied site generated test2 and added the character references in by hand. 
 That is the only one that works.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Created: (DOXIA-312) comments in meta properties end up in author content

2009-05-04 Thread Malachi de AElfweald (JIRA) 
comments in meta properties end up in author content


 Key: DOXIA-312
 URL: http://jira.codehaus.org/browse/DOXIA-312
 Project: Maven Doxia
  Issue Type: Bug
  Components: Core
Affects Versions: 1.1.1
 Environment: xdoc
Reporter: Malachi de AElfweald
Priority: Minor


I was getting ready to remove the xhtml comment from this snippet:
  properties
titleBalanced Ternary/title
!-- not using ligature because of 
http://jira.codehaus.org/browse/DOXIA-309 --
author email=malac...@gmail.comMalachi de AElig;lfweald/author
  /properties


and noticed that page source now shows:
  meta name=author content=lt;!-- not using ligature because of 
http://jira.codehaus.org/browse/DOXIA-309 --gt;
Malachi de #198;lfweald /


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Created: (DOXIA-313) subsection is printing name instead of title to page

2009-05-04 Thread Malachi de AElfweald (JIRA) 
subsection is printing name instead of title to page


 Key: DOXIA-313
 URL: http://jira.codehaus.org/browse/DOXIA-313
 Project: Maven Doxia
  Issue Type: Bug
  Components: Module - Xdoc
Affects Versions: 1.1.1
Reporter: Malachi de AElfweald


Doing something like subsection name=SomeName title=Some longer descriptive 
name.../subsection
prints SomeName in the box

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (DOXIA-313) subsection is printing name instead of title to page

2009-05-04 Thread Malachi de AElfweald (JIRA) 

[ 
http://jira.codehaus.org/browse/DOXIA-313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=175100#action_175100
 ] 

Malachi de AElfweald commented on DOXIA-313:


Here's what it is actually generating:

div class=section title=Comparison to Decimalh3a 
name=DecimalComparison/aDecimalComparison/h3

I think this is what it should be generating:

div class=section title=Comparison to Decimalh3a 
name=DecimalComparisonComparison to Decimal/a/h3


 subsection is printing name instead of title to page
 

 Key: DOXIA-313
 URL: http://jira.codehaus.org/browse/DOXIA-313
 Project: Maven Doxia
  Issue Type: Bug
  Components: Module - Xdoc
Affects Versions: 1.1.1
Reporter: Malachi de AElfweald
Assignee: Lukas Theussl

 Doing something like subsection name=SomeName title=Some longer 
 descriptive name.../subsection
 prints SomeName in the box

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (DOXIA-313) subsection is printing name instead of title to page

2009-05-04 Thread Malachi de AElfweald (JIRA) 

[ 
http://jira.codehaus.org/browse/DOXIA-313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=175101#action_175101
 ] 

Malachi de AElfweald commented on DOXIA-313:


It is listed in the attributes if you click on The full documentation is 
available here. 

http://maven.apache.org/doxia/doxia/doxia-modules/doxia-module-xdoc/xsddoc/http___maven.apache.org_XDOC_2.0/element/section.html#attr_title


 subsection is printing name instead of title to page
 

 Key: DOXIA-313
 URL: http://jira.codehaus.org/browse/DOXIA-313
 Project: Maven Doxia
  Issue Type: Bug
  Components: Module - Xdoc
Affects Versions: 1.1.1
Reporter: Malachi de AElfweald
Assignee: Lukas Theussl

 Doing something like subsection name=SomeName title=Some longer 
 descriptive name.../subsection
 prints SomeName in the box

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Issue Comment Edited: (DOXIA-313) subsection is printing name instead of title to page

2009-05-04 Thread Malachi de AElfweald (JIRA) 

[ 
http://jira.codehaus.org/browse/DOXIA-313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=175101#action_175101
 ] 

Malachi de AElfweald edited comment on DOXIA-313 at 5/5/09 12:03 AM:
-

It is listed in the attributes if you click on The full documentation is 
available here. 

http://maven.apache.org/doxia/doxia/doxia-modules/doxia-module-xdoc/xsddoc/http___maven.apache.org_XDOC_2.0/element/subsection.html#attr_title


  was (Author: malachid69):
It is listed in the attributes if you click on The full documentation is 
available here. 

http://maven.apache.org/doxia/doxia/doxia-modules/doxia-module-xdoc/xsddoc/http___maven.apache.org_XDOC_2.0/element/section.html#attr_title

  
 subsection is printing name instead of title to page
 

 Key: DOXIA-313
 URL: http://jira.codehaus.org/browse/DOXIA-313
 Project: Maven Doxia
  Issue Type: Bug
  Components: Module - Xdoc
Affects Versions: 1.1.1
Reporter: Malachi de AElfweald
Assignee: Lukas Theussl

 Doing something like subsection name=SomeName title=Some longer 
 descriptive name.../subsection
 prints SomeName in the box

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (DOXIA-313) subsection is printing name instead of title to page

2009-05-04 Thread Malachi de AElfweald (JIRA) 

[ 
http://jira.codehaus.org/browse/DOXIA-313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=175102#action_175102
 ] 

Malachi de AElfweald commented on DOXIA-313:


Actually, no worries I'll just use the name attribute. We probably 
shouldn't list the title attribute in the javadocs though as it is misleading 
for anyone using those for reference.

 subsection is printing name instead of title to page
 

 Key: DOXIA-313
 URL: http://jira.codehaus.org/browse/DOXIA-313
 Project: Maven Doxia
  Issue Type: Bug
  Components: Module - Xdoc
Affects Versions: 1.1.1
Reporter: Malachi de AElfweald
Assignee: Lukas Theussl

 Doing something like subsection name=SomeName title=Some longer 
 descriptive name.../subsection
 prints SomeName in the box

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (MCHANGES-142) Support Google Code

2009-05-03 Thread Malachi de AElfweald (JIRA) 

[ 
http://jira.codehaus.org/browse/MCHANGES-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=174973#action_174973
 ] 

Malachi de AElfweald commented on MCHANGES-142:
---

The documentation is misleading.  According to the documentation at
http://maven.apache.org/plugins/maven-changes-plugin/usage.html

It says:
If you use the issue attribute in your changes.xml file and have the 
issueManagement element configured in your pom.xml, the report will contain 
links to the issues in your issue management system. The default configuration 
produces links to JIRA, but that can be configured.
Note: If you have another issue tracker, make sure that your 
issueManagement/url is correct. In particular, make sure that it has a 
trailing slash if it needs one. The plugin can't add this for you, because it 
needs to handle different issue management systems. If your issue management 
system is at http://www.company.com/bugzilla/ the links will not work if you 
enter http://www.company.com/bugzilla in your pom.xml.

but it generates:
[ERROR] The JIRA Report only supports JIRA.  No JIRA Report will be generated.

Probably should change the documentation to not state that you can use another 
issue tracker


 Support Google Code
 ---

 Key: MCHANGES-142
 URL: http://jira.codehaus.org/browse/MCHANGES-142
 Project: Maven 2.x Changes Plugin
  Issue Type: New Feature
  Components: other issue-trackers
Reporter: Jeff Jensen

 Another tracker gaining popularity.
 Found this that someone had started:
 http://code.google.com/p/maven-googlecode/

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Created: (DOXIA-309) Ligature in author name shows up on page

2009-04-30 Thread Malachi de AElfweald (JIRA) 
Ligature in author name shows up on page


 Key: DOXIA-309
 URL: http://jira.codehaus.org/browse/DOXIA-309
 Project: Maven Doxia
  Issue Type: Bug
  Components: Core
Affects Versions: 1.1.1
 Environment: maven-site-plugin 2.1-SNAPSHOT w/ XDOC
Reporter: Malachi de AElfweald
Priority: Minor
 Attachments: testcase.tgz

followed these instructions to include the entity references:
http://svn.apache.org/viewvc/maven/doxia/site/src/site/fml/faq.fml?annotate=739143pathrev=739143

tried to set the author property:
author email=malac...@gmail.comMalachi de AElig;lfweald/author

The AE-ligature shows up as the first character on the page (top-left corner)


Testcase attached
testcase.html shows:

link rel=stylesheet href=./css/print.css type=text/css media=print 
/
  meta name=author content=
Malachi de lfweald /
#198;


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Created: (DOXIA-310) Unable to get custom entity references to work

2009-04-30 Thread Malachi de AElfweald (JIRA) 
Unable to get custom entity references to work
--

 Key: DOXIA-310
 URL: http://jira.codehaus.org/browse/DOXIA-310
 Project: Maven Doxia
  Issue Type: Bug
  Components: Core
Affects Versions: 1.1.1
 Environment: maven-site-plugin 2.1-SNAPSHOT w/ XDOC
Reporter: Malachi de AElfweald
 Attachments: testcase.tgz

followed these instructions:
http://svn.apache.org/viewvc/maven/doxia/site/src/site/fml/faq.fml?annotate=739143pathrev=739143

to include these entity references:
http://kallisti.eoti.org/ambrosia/kallisti/trit.ent

included test case has 3 different examples:
1. using the character references defined in the trit.ent. Character references 
were removed from the table during site:site
2. using the character references by number. Character references were replaced 
with '?' during site:site
3. copied site generated test2 and added the character references in by hand. 
That is the only one that works.



-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Created: (DOXIA-311) Character references do not work in xdoc section titles

2009-04-30 Thread Malachi de AElfweald (JIRA) 
Character references do not work in xdoc section titles
---

 Key: DOXIA-311
 URL: http://jira.codehaus.org/browse/DOXIA-311
 Project: Maven Doxia
  Issue Type: Bug
  Components: Core
Affects Versions: 1.1.1
 Environment: maven-site-plugin 2.1-SNAPSHOT w/ XDOC
Reporter: Malachi de AElfweald
Priority: Minor
 Attachments: testcase.tgz

In the attached testcase, you will see that the pi; reference works in the 
paragraph content but is replaced with amp;pi; in the section title.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (DOXIA-310) Unable to get custom entity references to work

2009-04-30 Thread Malachi de AElfweald (JIRA) 

[ 
http://jira.codehaus.org/browse/DOXIA-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=174836#action_174836
 ] 

Malachi de AElfweald commented on DOXIA-310:


This should not be 'major' priority. Sorry, forgot to set that.

 Unable to get custom entity references to work
 --

 Key: DOXIA-310
 URL: http://jira.codehaus.org/browse/DOXIA-310
 Project: Maven Doxia
  Issue Type: Bug
  Components: Core
Affects Versions: 1.1.1
 Environment: maven-site-plugin 2.1-SNAPSHOT w/ XDOC
Reporter: Malachi de AElfweald
 Attachments: testcase.tgz


 followed these instructions:
 http://svn.apache.org/viewvc/maven/doxia/site/src/site/fml/faq.fml?annotate=739143pathrev=739143
 to include these entity references:
 http://kallisti.eoti.org/ambrosia/kallisti/trit.ent
 included test case has 3 different examples:
 1. using the character references defined in the trit.ent. Character 
 references were removed from the table during site:site
 2. using the character references by number. Character references were 
 replaced with '?' during site:site
 3. copied site generated test2 and added the character references in by hand. 
 That is the only one that works.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (JXR-38) View Javadoc link invalid

2009-04-29 Thread Malachi de AElfweald (JIRA) 

[ 
http://jira.codehaus.org/browse/JXR-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=174684#action_174684
 ] 

Malachi de AElfweald commented on JXR-38:
-

crossposting to:
http://jira.codehaus.org/browse/JXR-6
http://jira.codehaus.org/browse/JXR-40
http://jira.codehaus.org/browse/JXR-38 

the root cause of this seems to be that the JXR plugin and the JAVADOC plugin 
have different expectations

the javadoc plugin needs:
destDirapidocs/destDir

the jxr plugin needs:
javadocDirtarget/site/apidocs/javadocDir 

 View Javadoc link invalid
 -

 Key: JXR-38
 URL: http://jira.codehaus.org/browse/JXR-38
 Project: Maven JXR
  Issue Type: Bug
  Components: maven2 jxr plugin
Affects Versions: 2.0
 Environment: 2.0.4
Reporter: John Allen
Assignee: Fabrice BELLINGARD
 Fix For: 2.1


 JXR View JavaDoc link is invalid
 JXR page URL: 
 http://foo.com/projects/snapshots/examples/utils/xml/xref/index.html
 JXR page HTML: 
 {noformat}
 !DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN 
 http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd;
 html xmlns=http://www.w3.org/1999/xhtml; xml:lang=en lang=en
 head
 meta http-equiv=content-type content=text/html; charset=ISO-8859-1 
 /titleApp xref/title
 link type=text/css rel=stylesheet href=../../../../../stylesheet.css /
 /head
 body
 div id=overviewa 
 href=../../../../../../../../../../../../apidocs/com/aelitis/common/utils/xml/App.htmlView
  Javadoc/a/divpre
 a name=1 href=#11/a   strongpackage/strong 
 com.aelitis.common.utils.xml;
 a name=2 href=#22/a   
 [snip]
 /html
 {noformat}
 The JavaDoc URL used is:
 a 
 href=../../../../../../../../../../../../apidocs/com/aelitis/common/utils/xml/App.htmlView
  Javadoc/a/divpre
 However that takes us all the way back to the server root, mapping to the URL:
 http://foo.com/apidocs/com/aelitis/common/utils/xml/App.html
 When it should be the URL:
 http://foo.com/projects/snapshots/examples/utils/xml/apidocs/index.html

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (JXR-6) Javadoc linked incorrectly

2009-04-29 Thread Malachi de AElfweald (JIRA) 

[ 
http://jira.codehaus.org/browse/JXR-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=174682#action_174682
 ] 

Malachi de AElfweald commented on JXR-6:


crossposting to:
http://jira.codehaus.org/browse/JXR-6
http://jira.codehaus.org/browse/JXR-40
http://jira.codehaus.org/browse/JXR-38 

the root cause of this seems to be that the JXR plugin and the JAVADOC plugin 
have different expectations

the javadoc plugin needs:
destDirapidocs/destDir

the jxr plugin needs:
javadocDirtarget/site/apidocs/javadocDir 

 Javadoc linked incorrectly
 --

 Key: JXR-6
 URL: http://jira.codehaus.org/browse/JXR-6
 Project: Maven JXR
  Issue Type: Bug
  Components: jxr
Affects Versions: 1.0-beta-1
Reporter: Mike Perham
Assignee: fabrizio giustina
 Fix For: 1.0

 Attachments: jxr.javadoc.txt


 Javadocs are being linked incorrectly from the JXR output.  This patch fixes 
 the links on our projects.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (JXR-40) maven 2 jxr plugin puts wrong javadoc link

2009-04-29 Thread Malachi de AElfweald (JIRA) 

[ 
http://jira.codehaus.org/browse/JXR-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=174683#action_174683
 ] 

Malachi de AElfweald commented on JXR-40:
-

crossposting to:
http://jira.codehaus.org/browse/JXR-6
http://jira.codehaus.org/browse/JXR-40
http://jira.codehaus.org/browse/JXR-38 

the root cause of this seems to be that the JXR plugin and the JAVADOC plugin 
have different expectations

the javadoc plugin needs:
destDirapidocs/destDir

the jxr plugin needs:
javadocDirtarget/site/apidocs/javadocDir 

 maven 2 jxr plugin puts wrong javadoc link
 --

 Key: JXR-40
 URL: http://jira.codehaus.org/browse/JXR-40
 Project: Maven JXR
  Issue Type: Bug
  Components: maven2 jxr plugin
Reporter: Lee Meador
Assignee: Brett Porter
Priority: Minor

 There are too many '../'s in the link to the javadocs that is generated at 
 the top of each page of java class source code. I have moved the javadocs to 
 ${project.build.directory}/site/javadoc/ (which is given to the javadoc 
 plugin and then told the jxr plugin that they were at 
 ${project.build.directory}/site/javadoc/apidocs/ which takes into account how 
 the javadocs are built. The link has way too many .. parts to the path and 
 backs up all the way to the top of my web site instead of just to the folder 
 equivalent to site 
 The xml is:
   reporting
   plugins
   plugin
   groupIdorg.codehaus.mojo/groupId
   artifactIdjxr-maven-plugin/artifactId
   configuration
   
 javadocDir${project.build.directory}/site/javadoc/apidocs//javadocDir
   /configuration
   /plugin
   plugin
   groupIdorg.apache.maven.plugins/groupId
   artifactIdmaven-javadoc-plugin/artifactId
   configuration
   
 destDir${project.build.directory}/site/javadoc//destDir
   /configuration
   /plugin
 ...
 Sorry to put this issue here. It needs moving but there is no MNGJXR and 
 MPJXR seemed to be the maven1 jxr plugin. I assume it will be moved to the 
 right place. (and thanks)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (MNG-4137) NPE in DefaultLIfecycleExecutor when run from within Hudson builds

2009-04-23 Thread Malachi de AElfweald (JIRA) 

[ 
http://jira.codehaus.org/browse/MNG-4137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=174053#action_174053
 ] 

Malachi de AElfweald commented on MNG-4137:
---

I am still getting it as well

[INFO] Preparing surefire-report:report
[HUDSON] Archiving 
/home/hudson/jobs/ambrosia-jdk6-standalone/workspace/kallisti/pom.xml to 
/home/hudson/jobs/ambrosia-jdk6-standalone/modules/org.eoti$kallisti/builds/2009-04-23_09-52-29/archive/org.eoti/kallisti/2.2-SNAPSHOT/pom.xml
[HUDSON] Archiving 
/home/hudson/jobs/ambrosia-jdk6-standalone/workspace/kallisti/target/kallisti-2.2-SNAPSHOT.jar
 to 
/home/hudson/jobs/ambrosia-jdk6-standalone/modules/org.eoti$kallisti/builds/2009-04-23_09-52-29/archive/org.eoti/kallisti/2.2-20090423.165239-12/kallisti-2.2-SNAPSHOT.jar
[INFO] 
[ERROR] FATAL ERROR
[INFO] 
[INFO] null
[INFO] 
[DEBUG] Trace
java.lang.NullPointerException
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.calculateConcreteConfiguration(DefaultLifecycleExecutor.java:747)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:578)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:1168)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:1009)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:647)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:519)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
at 
org.apache.maven.lifecycle.LifecycleExecutorInterceptor.execute(LifecycleExecutorInterceptor.java:65)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:356)
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.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at hudson.maven.agent.Main.launch(Main.java:158)
at hudson.maven.MavenBuilder.call(MavenBuilder.java:162)
at 
hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:578)
at 
hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:524)
at hudson.remoting.UserRequest.perform(UserRequest.java:97)
at hudson.remoting.UserRequest.perform(UserRequest.java:46)
at hudson.remoting.Request$2.run(Request.java:236)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
[INFO] 
[INFO] Total time: 39 seconds
[INFO] Finished at: Thu Apr 23 09:53:10 PDT 2009
[INFO] Final Memory: 71M/208M
[INFO] 
channel stopped
Finished: FAILURE

Hudson ver. 1.300 (private-04/17/2009 11:02-kohsuke)

 NPE in DefaultLIfecycleExecutor when run from within Hudson builds
 --

 Key: MNG-4137
 URL: http://jira.codehaus.org/browse/MNG-4137
 Project: Maven 2
  Issue Type: Bug
  Components: Plugins and Lifecycle
Affects Versions: 2.1.0
 Environment: Hudson ver. 1.299
 Apache Maven 2.1.0

[jira] Commented: (MNG-4137) NPE in DefaultLIfecycleExecutor when run from within Hudson builds

2009-04-23 Thread Malachi de AElfweald (JIRA) 

[ 
http://jira.codehaus.org/browse/MNG-4137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=174055#action_174055
 ] 

Malachi de AElfweald commented on MNG-4137:
---

Looking at all the google hits everywhere, it seems to be a consistent pattern 
for this bug...

[INFO] Preparing SOME_REPORT
[HUDSON] Archiving SOMETHING
[INFO] 
[ERROR] FATAL ERROR
[INFO] 
[INFO] null
[INFO] 
[DEBUG] Trace
java.lang.NullPointerException
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.calculateConcreteConfiguration(DefaultLifecycleExecutor.java:747)

 NPE in DefaultLIfecycleExecutor when run from within Hudson builds
 --

 Key: MNG-4137
 URL: http://jira.codehaus.org/browse/MNG-4137
 Project: Maven 2
  Issue Type: Bug
  Components: Plugins and Lifecycle
Affects Versions: 2.1.0
 Environment: Hudson ver. 1.299
 Apache Maven 2.1.0 (r755702; 2009-03-18 15:10:27-0400)
 Java version: 1.6.0_12
 Java home: /usr/java/jdk1.6.0_12/jre
 Default locale: en_US, platform encoding: UTF-8
 OS name: linux version: 2.6.18-92.1.18.el5 arch: i386 Family: unix
Reporter: Jonathan Johnson

 Since upgrading from Maven 2.0.10 to 2.1.0 my Hudson midnight job that runs 
 clean site fails with a NullPointerException at 
 DefaultLifecycleExecutor.java:747 exception.  See below.
 This is related, if not the same bug that was claimed fixed in 2.1.0 M1 - 
 http://jira.codehaus.org/browse/MNG-3704
 I though its was an issue with the Cobertura plugin - See 
 https://hudson.dev.java.net/issues/show_bug.cgi?id=3468 but once I remove 
 Cobertura I now get the same stack trace after [INFO] Preparing 
 surefire-report:report:
 [INFO] Preparing surefire-report:report
 [HUDSON] Archiving [...omittted for this posting...]
 [INFO] 
 
 [ERROR] FATAL ERROR
 [INFO] 
 
 [INFO] null
 [INFO] 
 
 [INFO] Trace
 java.lang.NullPointerException
   at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.calculateConcreteConfiguration(DefaultLifecycleExecutor.java:747)
   at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:578)
   at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540)
   at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:1168)
   at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:1009)
   at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:647)
   at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540)
   at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:519)
   at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
   at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
   at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
   at 
 org.apache.maven.lifecycle.LifecycleExecutorInterceptor.execute(LifecycleExecutorInterceptor.java:65)
   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
   at org.apache.maven.cli.MavenCli.main(MavenCli.java:356)
   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.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
   at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
   at hudson.maven.agent.Main.launch(Main.java:158)
   at hudson.maven.MavenBuilder.call(MavenBuilder.java:162)
   at 
 hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:578)
   at 
 hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:524)
   at hudson.remoting.UserRequest.perform(UserRequest.java:97)
   at hudson.remoting.UserRequest.perform(UserRequest.java:46)

[jira] Commented: (MCHANGELOG-91) mvn changelog:changelog svn --non-interactive fails under Mac OSX 10.5 (svn: PROPFIND authorization failed)

2009-04-16 Thread Malachi de AElfweald (JIRA) 

[ 
http://jira.codehaus.org/browse/MCHANGELOG-91?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=173183#action_173183
 ] 

Malachi de AElfweald commented on MCHANGELOG-91:


I am getting the same thing on Solaris once I change my password to be 
encrypted.

 mvn changelog:changelog svn --non-interactive fails under Mac OSX 10.5 (svn: 
 PROPFIND authorization failed)
 ---

 Key: MCHANGELOG-91
 URL: http://jira.codehaus.org/browse/MCHANGELOG-91
 Project: Maven 2.x Changelog Plugin
  Issue Type: Bug
 Environment: OSX 10.5
Reporter: Laurent Perez
Priority: Critical

 hi
 mvn changelog:changelog svn --non-interactive fails under Mac OSX 10.5, stack 
 below :
 [INFO] Executing: svn --non-interactive log -v -r {2008-11-12 22:21:45 
 +}:{2008-12-13 22:21:45 +} http://xx/
 [INFO] Working directory: /Users/laurent/Desktop/x
 [ERROR] Provider message:
 [ERROR] The svn command failed.
 [ERROR] Command output:
 [ERROR] svn: PROPFIND request failed on '/'
 svn: PROPFIND of '/x': authorization failed (http://x)
 I believe this may be linked to http://jira.codehaus.org/browse/SCM-402 , 
 however, I am using maven-scm-plugin version 1.1 in my pom.xml, but perhaps 
 the changelog plugin does not use this 1.1 version.
 Can anyone confirm ?
 thanks
 laurent

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (MSOURCES-8) maven-source-plugin causes generate-sources phase to execute twice

2009-02-27 Thread Malachi de AElfweald (JIRA) 

[ 
http://jira.codehaus.org/browse/MSOURCES-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=167337#action_167337
 ] 

Malachi de AElfweald commented on MSOURCES-8:
-

I agree. In my case, it forces initialize to run twice which is causing the 
build to fail.  Since this is to not be fixed, I guess the only workaround is 
to quit using the maven-source-plugin.

 maven-source-plugin causes generate-sources phase to execute twice
 --

 Key: MSOURCES-8
 URL: http://jira.codehaus.org/browse/MSOURCES-8
 Project: Maven 2.x Source Plugin
  Issue Type: Bug
Affects Versions: 2.0.1
Reporter: Andreas Schildbach

 Due to the lack of documentation, I configured the plugin as follows, in 
 order to install sources when doing mvn install:
   plugin
   groupIdorg.apache.maven.plugins/groupId
   artifactIdmaven-source-plugin/artifactId
   executions
   execution
   phaseinstall/phase
   goals
   goaljar/goal
   /goals
   /execution
   /executions
   /plugin
 Unfortunately, mvn install causes the generate-sources phase to execute 
 twice, which can manifest for example in an antrun-task executing twice.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Created: (MENFORCER-69) requireFilesDontExist doesn't work against symlinks

2009-02-26 Thread Malachi de AElfweald (JIRA) 
requireFilesDontExist doesn't work against symlinks
---

 Key: MENFORCER-69
 URL: http://jira.codehaus.org/browse/MENFORCER-69
 Project: Maven 2.x Enforcer Plugin
  Issue Type: Bug
  Components: Standard Rules
Affects Versions: 1.0-beta-1
 Environment: [INFO] [enforcer:display-info {execution: 
enforce-display}]
[INFO] Maven Version: 2.1.0-M1
[INFO] JDK Version: 1.6.0_11 normalized as: 1.6.0-11
[INFO] OS Info: Arch: x86 Family: unix Name: sunos Version: 5.11

Reporter: Malachi de AElfweald
Priority: Minor


I created a symlink, say /opt/FAKE pointing to something in my work directory

The requireFilesDontExist rule fails if I check against /opt, but not when 
checking against /opt/FAKE

It should fail against symlinks



-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira