[jira] Commented: (MCHECKSTYLE-163) Test classpath resolution fails in mvn check:check when includeTestSourceDirectory = true

[ https://jira.codehaus.org/browse/MCHECKSTYLE-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274868#comment-274868 ] Chris Whelan commented on MCHECKSTYLE-163: -- Example log with patch applied. Note tha

[jira] Commented: (MCHECKSTYLE-163) Test classpath resolution fails in mvn check:check when includeTestSourceDirectory = true

[ https://jira.codehaus.org/browse/MCHECKSTYLE-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274866#comment-274866 ] Chris Whelan commented on MCHECKSTYLE-163: -- Example log running attached project with

[jira] Updated: (MCHECKSTYLE-163) Test classpath resolution fails in mvn check:check when includeTestSourceDirectory = true

[ https://jira.codehaus.org/browse/MCHECKSTYLE-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Whelan updated MCHECKSTYLE-163: - Attachment: MCHECKSTYLE-163.zip Attaching an example project > Test classpath resolution

[jira] Created: (MCOMPILER-158) Symbol name should be displayed during compiler error using Java 7

Symbol name should be displayed during compiler error using Java 7 -- Key: MCOMPILER-158 URL: https://jira.codehaus.org/browse/MCOMPILER-158 Project: Maven 2.x Compiler Plugin I

[jira] Commented: (MCHECKSTYLE-111) More information on issue: "Got an exception - java.lang.RuntimeException: Unable to get class information for [exception]"

[ https://jira.codehaus.org/browse/MCHECKSTYLE-111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274861#comment-274861 ] Niraj Tolia commented on MCHECKSTYLE-111: - We ran into this at work too. Evidently che

[jira] Created: (MDOCCK-23) Invocation fails with "com.thoughtworks.qdox.parser.ParseException: syntax error"

Invocation fails with "com.thoughtworks.qdox.parser.ParseException: syntax error" - Key: MDOCCK-23 URL: https://jira.codehaus.org/browse/MDOCCK-23 Project: Maven 2.x Docu

[jira] Updated: (MSHARED-131) Maven archiver does not manage empty classifier correctly in manifest.mf classpath

[ https://jira.codehaus.org/browse/MSHARED-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MSHARED-131: -- Description: When I have a dependency {code:xml} com.almerys.pec ws-ag2r-client

[jira] Updated: (MVERIFIER-10) Print the absolute path to the input file when verification fails

[ https://jira.codehaus.org/browse/MVERIFIER-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MVERIFIER-10: --- Affects Version/s: 1.3 Fix Version/s: 1.4 > Print the absolute path to the input file wh

[jira] Created: (MSITE-602) The staged site is deployed to the wrong place

The staged site is deployed to the wrong place -- Key: MSITE-602 URL: https://jira.codehaus.org/browse/MSITE-602 Project: Maven 2.x and 3.x Site Plugin Issue Type: Bug Components: site:st

[jira] Commented: (MCHECKSTYLE-163) Test classpath resolution fails in mvn check:check when includeTestSourceDirectory = true

[ https://jira.codehaus.org/browse/MCHECKSTYLE-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274842#comment-274842 ] Olivier Lamy commented on MCHECKSTYLE-163: -- could you please provide a sample project

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

[ https://jira.codehaus.org/browse/MPMD-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274821#comment-274821 ] Scott MacDonald commented on MPMD-86: - How is this closed as "Not a bug" while simultaneously prov

[jira] Closed: (MCOMPILER-87) Compiler errors display as INFO level messages

[ https://jira.codehaus.org/browse/MCOMPILER-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg closed MCOMPILER-87. -- Resolution: Cannot Reproduce I tried that out today and I clearly get compilation errors reported

[jira] Commented: (MCHECKSTYLE-159) Optional treeWalker.cacheFile property must not be required

[ https://jira.codehaus.org/browse/MCHECKSTYLE-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274817#comment-274817 ] Filip van Laenen commented on MCHECKSTYLE-159: -- There's a small type in the Check

[jira] Created: (MASSEMBLY-568) Dependency missing in assembled archive in multi-project build for certain scope combination

Dependency missing in assembled archive in multi-project build for certain scope combination Key: MASSEMBLY-568 URL: https://jira.codehaus.org/browse/MASSEMBLY-568

[jira] Commented: (MECLIPSE-587) maven-eclipse-plugin creates wrong org.eclipse.wst.common.project.facet.core.xml for ear-projects when javaee:javaee-api s used

[ https://jira.codehaus.org/browse/MECLIPSE-587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274813#comment-274813 ] Nadeem M Nayeck commented on MECLIPSE-587: -- This issue is quite important, I wonder why

[jira] Commented: (SCM-508) Wrong scm url validation for mercurial provider

[ https://jira.codehaus.org/browse/SCM-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274812#comment-274812 ] Lóránt Pintér commented on SCM-508: --- Using http://localhost:8000 is not a solution when you want to

[jira] Commented: (MASSEMBLY-561) Encoding is broken when filtering is enabled

[ https://jira.codehaus.org/browse/MASSEMBLY-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274811#comment-274811 ] Julien HENRY commented on MASSEMBLY-561: Hi John, Did you have a chance to complete the

[jira] Created: (MRESOURCES-151) Path for "filters" parameter is relative to the place from where the build was run

Path for "filters" parameter is relative to the place from where the build was run -- Key: MRESOURCES-151 URL: https://jira.codehaus.org/browse/MRESOURCES-151 Project: Ma

[jira] Commented: (MSITE-601) Period added to URL prevents proper cloning with Mercurial

[ https://jira.codehaus.org/browse/MSITE-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274806#comment-274806 ] Leon Blakey commented on MSITE-601: --- This is an issue with Google's new namespace overlap though.