[jira] Created: (MECLIPSE-547) Maven Eclipse plugin 2.6 with AJDT changes are not backwards compatible.
Maven Eclipse plugin 2.6 with AJDT changes are not backwards compatible. Key: MECLIPSE-547 URL: http://jira.codehaus.org/browse/MECLIPSE-547 Project: Maven 2.x Eclipse Plugin Issue Type: Improvement Components: AJDT support Affects Versions: 2.6 Reporter: Tan Quach Priority: Minor Since upgrading to version 2.6 of the plugin, my projects are all now failing because of this issue: http://jira.codehaus.org/browse/MECLIPSE-544 I understand there is a workaround but now, i have to go through all of my projects to add this configuration element. It would better if the addition for AJDT support was not so disruptive to existing projects. Could we not have the default configuration to be the workaround? (e.g. use default ajdtVersionnone/ajdtVersion) -- 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: (MECLIPSE-200) Please add support for the AJDT plugin
[ http://jira.codehaus.org/browse/MECLIPSE-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=172218#action_172218 ] Tan Quach commented on MECLIPSE-200: I agree with Alexander, and I've created a new issue: http://jira.codehaus.org/browse/MECLIPSE-547 Please add support for the AJDT plugin -- Key: MECLIPSE-200 URL: http://jira.codehaus.org/browse/MECLIPSE-200 Project: Maven 2.x Eclipse Plugin Issue Type: New Feature Components: AJDT support Affects Versions: 2.2 Reporter: Eric Berry Assignee: Arnaud Heritier Fix For: 2.6 Attachments: ajdt.patch, maven-eclipse-plugin.zip, maven-eclipse-plugin.zip Please add support for the AJDT plugin. I have modified the eclipse plugin for our site with the needed changes. I have attached the modifications that I made for someone to look at and incorporate into the plugin. -- 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-214) test javadoc goal uses incorrect dependency classpath
[ http://jira.codehaus.org/browse/MJAVADOC-214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=146095#action_146095 ] Tan Quach commented on MJAVADOC-214: I am getting these same errors, however here is some additional information: When I run mvn javadoc:test-javadoc from within either a standalone project or sub-module project that has test sources, it works fine. When I run mvn javadoc:test-javadoc from a parent project, it fails when it gets to the sub-module. test javadoc goal uses incorrect dependency classpath - Key: MJAVADOC-214 URL: http://jira.codehaus.org/browse/MJAVADOC-214 Project: Maven 2.x Javadoc Plugin Issue Type: Bug Affects Versions: 2.4 Reporter: Brett Porter according to this report: http://www.nabble.com/JavaDoc-Report-crashes-with-TestNG-tp19139379p19158787.html The test javadoc goal is not using the test classpath dependencies. -- 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