[jira] Commented: (MPMD-92) Using JDK 1.6 causes ParseException: Can't use generics unless running in JDK 1.5 mode! unless set targetJdk to 1.5, not 1.6

[ http://jira.codehaus.org/browse/MPMD-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163180#action_163180 ] Paul Sundling commented on MPMD-92: --- You were totally right! MNG-3385 was what was really causing the

[jira] Created: (JXR-68) ignores classes with same name in other packages

ignores classes with same name in other packages Key: JXR-68 URL: http://jira.codehaus.org/browse/JXR-68 Project: Maven JXR Issue Type: Bug Components: maven2 jxr plugin Affects

[jira] Commented: (MNG-3336) site reporting causes release:perform to fail

[ http://jira.codehaus.org/browse/MNG-3336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161779#action_161779 ] Paul Sundling commented on MNG-3336: This branch was created to test releases. For more

[jira] Updated: (MNG-3336) site reporting causes release:perform to fail

[ http://jira.codehaus.org/browse/MNG-3336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Sundling updated MNG-3336: --- Attachment: minimal.zip This is the zip with working config. site reporting causes release:perform to fail

[jira] Commented: (MNG-3336) site reporting causes release:perform to fail

[ http://jira.codehaus.org/browse/MNG-3336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161783#action_161783 ] Paul Sundling commented on MNG-3336: Forgot to mention one thing. The working config has only

[jira] Created: (MPMD-92) Using JDK 1.6 causes ParseException: Can't use generics unless running in JDK 1.5 mode! unless set targetJdk to 1.5, not 1.6

Using JDK 1.6 causes ParseException: Can't use generics unless running in JDK 1.5 mode! unless set targetJdk to 1.5, not 1.6 --- Key: MPMD-92

[jira] Commented: (MPMD-67) Using JDK 1.6 causes ParseException: Can't use generics unless running in JDK 1.5 mode!

[ http://jira.codehaus.org/browse/MPMD-67?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161802#action_161802 ] Paul Sundling commented on MPMD-67: --- new related issue opened up to demonstrate my issue with PMD 2.4

[jira] Commented: (MPMD-67) Using JDK 1.6 causes ParseException: Can't use generics unless running in JDK 1.5 mode!

[ http://jira.codehaus.org/browse/MPMD-67?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161806#action_161806 ] Paul Sundling commented on MPMD-67: --- Forgot to mention that under further investigation, it doesn't

[jira] Commented: (MPMD-67) Using JDK 1.6 causes ParseException: Can't use generics unless running in JDK 1.5 mode!

[ http://jira.codehaus.org/browse/MPMD-67?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160864#action_160864 ] Paul Sundling commented on MPMD-67: --- I don't think the typo is the issue. I think you have to specify

[jira] Commented: (MPMD-86) Using JDK 1.5 causes ParseException: Can't use generics unless running in JDK 1.5 mode!

[ http://jira.codehaus.org/browse/MPMD-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160878#action_160878 ] Paul Sundling commented on MPMD-86: --- When running site, it can also give this error if using JDK 1.6

[jira] Commented: (MNG-3336) site reporting causes release:perform to fail

[ http://jira.codehaus.org/browse/MNG-3336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159651#action_159651 ] Paul Sundling commented on MNG-3336: It's been a year. Has anyone looked into the bug since then?

[jira] Commented: (MSITE-238) multi project default URL is wrong

[ http://jira.codehaus.org/browse/MSITE-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=138595#action_138595 ] Paul Sundling commented on MSITE-238: - It's confusing for a starting user that when you do mvn

[jira] Issue Comment Edited: (MSITE-238) multi project default URL is wrong

[ http://jira.codehaus.org/browse/MSITE-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=138595#action_138595 ] sundling edited comment on MSITE-238 at 6/13/08 7:13 PM: -- It's confusing

[jira] Created: (MNG-3336) site reporting causes release:perform to fail

site reporting causes release:perform to fail - Key: MNG-3336 URL: http://jira.codehaus.org/browse/MNG-3336 Project: Maven 2 Issue Type: Bug Reporter: Paul Sundling

[jira] Commented: (MNG-3336) site reporting causes release:perform to fail

[ http://jira.codehaus.org/browse/MNG-3336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_117809 ] Paul Sundling commented on MNG-3336: Forgot to mention, zip file contains code that reproduces issue with aggregate

[jira] Created: (MNG-3278) classifiers in dependencyManagement don't work

classifiers in dependencyManagement don't work -- Key: MNG-3278 URL: http://jira.codehaus.org/browse/MNG-3278 Project: Maven 2 Issue Type: Bug Reporter: Paul Sundling

[jira] Commented: (MCHANGELOG-66) changelog for perforce fails because of default clientspec

[ http://jira.codehaus.org/browse/MCHANGELOG-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103474 ] Paul Sundling commented on MCHANGELOG-66: - Doh! Just realized the changelog website hasn't been published since

[jira] Commented: (MCHANGELOG-65) documentation samples for working changelog reports for each supported SCM

[ http://jira.codehaus.org/browse/MCHANGELOG-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_102246 ] Paul Sundling commented on MCHANGELOG-65: - It's useful information, but Please check your changelog plugin

[jira] Commented: (MCHANGELOG-65) documentation samples for working changelog reports for each supported SCM

[ http://jira.codehaus.org/browse/MCHANGELOG-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_101878 ] Paul Sundling commented on MCHANGELOG-65: - OK perhaps it should be in the FAQ, but I posted on the user list

[jira] Created: (MCHANGELOG-65) documentation samples for working changelog reports for each supported SCM

documentation samples for working changelog reports for each supported SCM -- Key: MCHANGELOG-65 URL: http://jira.codehaus.org/browse/MCHANGELOG-65 Project: Maven 2.x Changelog

[jira] Commented: (MNG-1832) built-in property containing current timestamp

[ http://jira.codehaus.org/browse/MNG-1832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100300 ] Paul Sundling commented on MNG-1832: What happened to the buildinfo plugin? It was in the sandbox and now it

[jira] Created: (MSITE-238) multi project default URL is wrong

multi project default URL is wrong -- Key: MSITE-238 URL: http://jira.codehaus.org/browse/MSITE-238 Project: Maven 2.x Site Plugin Issue Type: Bug Reporter: Paul Sundling Priority:

[jira] Created: (MPIR-69) add anchors for developers

add anchors for developers -- Key: MPIR-69 URL: http://jira.codehaus.org/browse/MPIR-69 Project: Maven 2.x Project Info Reports Plugin Issue Type: Improvement Reporter: Paul Sundling Priority:

[jira] Commented: (MPIR-69) add anchors for developers

[ http://jira.codehaus.org/browse/MPIR-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100070 ] Paul Sundling commented on MPIR-69: --- To be more clear, what I'm asking for is that anchors be added, so the changes report

[jira] Commented: (MSITE-238) multi project default URL is wrong

[ http://jira.codehaus.org/browse/MSITE-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100084 ] Paul Sundling commented on MSITE-238: - workaround is to use the following for all childProjects (modules):