[jira] Commented: (MECLIPSE-548) MECLIPSE-442 should be reverted. Classpath container entries should come before 3rd party jars in .classpath
[ http://jira.codehaus.org/browse/MECLIPSE-548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=172915#action_172915 ] Robert Newson commented on MECLIPSE-548: this also broke my project. I have a dependency on mx4j (it's transitive and shouldn't appear on here, but that's a different bug). It took a few frustrating hours to track down why I could not compile in Eclipse but could in Maven. Please revert this change. I have pinned to 2.5.1 for now. MECLIPSE-442 should be reverted. Classpath container entries should come before 3rd party jars in .classpath Key: MECLIPSE-548 URL: http://jira.codehaus.org/browse/MECLIPSE-548 Project: Maven 2.x Eclipse Plugin Issue Type: Bug Components: Core : Dependencies resolution and build path (.classpath) Affects Versions: 2.6 Environment: all Reporter: Joe Freeman Priority: Critical A patch was accepted into maven 2.6 as part of jiraMECLIPSE-442 that configures eclipse to compile with a different order than the jre will load with. This patch moved the container classpaths to the end of the classpath in eclipse. This behavior is incorrect. The JRE's jar files should come before any 3rd party libraries on the classpath because those classes will be loaded before any of the 3rd party jars and because the JRE's classes cannot be overridden by classes in a 3rd party jar. I understand why MECLIPSE-442 wanted to reverse the order so they could pick up the properties files. The best way to do this was to create properties files in the indvidual projects if he needed at run time or in the test/resources directory if it was only needed for unit testing. project resources come before everything in eclipse With this patch added to maven 2.6, we have a situation where eclipse tells us we have compiler error when maven command line compilations do not. -- 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] Updated: (MCLOVER-48) add support for block contexts.
[ http://jira.codehaus.org/browse/MCLOVER-48?page=all ] Robert Newson updated MCLOVER-48: - Attachment: contextFilter.patch Much simpler than I'd imagined. It works for me, here's my config; plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-clover-plugin/artifactId version2.3-SNAPSHOT/version configuration jdk1.5/jdk contextFilterassert/contextFilter /configuration /plugin add support for block contexts. --- Key: MCLOVER-48 URL: http://jira.codehaus.org/browse/MCLOVER-48 Project: Maven 2.x Clover Plugin Issue Type: New Feature Reporter: Robert Newson Attachments: contextFilter.patch We use a lot of asserts in our code. We would like to exclude the assert lines from our code coverage figures. The Ant, Eclipse and Maven 1.x plugin support Clover's block context feature. Can the Maven 2.x plugin be enhanced to support this? http://www.cenqua.com/clover/doc/adv/contexts.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: (MCLOVER-48) add support for block contexts.
[ http://jira.codehaus.org/browse/MCLOVER-48?page=comments#action_74130 ] Robert Newson commented on MCLOVER-48: -- Does anyone still maintain the clover plugin? add support for block contexts. --- Key: MCLOVER-48 URL: http://jira.codehaus.org/browse/MCLOVER-48 Project: Maven 2.x Clover Plugin Issue Type: New Feature Reporter: Robert Newson We use a lot of asserts in our code. We would like to exclude the assert lines from our code coverage figures. The Ant, Eclipse and Maven 1.x plugin support Clover's block context feature. Can the Maven 2.x plugin be enhanced to support this? http://www.cenqua.com/clover/doc/adv/contexts.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: (MCLOVER-48) add support for block contexts.
[ http://jira.codehaus.org/browse/MCLOVER-48?page=comments#action_74156 ] Robert Newson commented on MCLOVER-48: -- Hi! I was asking as there hasn't been much activity on the outstanding bugs that I can see. I may get time to work on a patch for this in the next few weeks, actually. I'd love to help out but I am kinda swamped right now (I'm sure you are too). I didn't mean to be critical and I'm glad you're still working on this. :) B. add support for block contexts. --- Key: MCLOVER-48 URL: http://jira.codehaus.org/browse/MCLOVER-48 Project: Maven 2.x Clover Plugin Issue Type: New Feature Reporter: Robert Newson We use a lot of asserts in our code. We would like to exclude the assert lines from our code coverage figures. The Ant, Eclipse and Maven 1.x plugin support Clover's block context feature. Can the Maven 2.x plugin be enhanced to support this? http://www.cenqua.com/clover/doc/adv/contexts.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
