Joerg Hohwiller wrote: > > 2. m2eclipse is a nice idea and about what I am dreaming of. However it is > so entirely full of bugs that it is completely useless for complex > projects. >
I guess this require more detailed response. Please see below. This is probably more appropriate for m2eclipse mailing list, but because you asked here, I have no choice to send my response into this mailing list too. Joerg Hohwiller wrote: > > Since my bug report was just rejected I stopped reporting bugs. > I suppose I owe you an apology for closing that issue submitted year and a half ago. Apparently I misread your comment where you said "this issue is an invalid bug report" http://jira.codehaus.org/browse/MNGECLIPSE-219 By all means, please feel free to reopen it if it is still present in the recent versions. There isn't really any point to be upset about this. I actually would like to encourage everyone to not keep your pain for yourself and share it with m2eclipse developers, by submitting bug reports and providing test cases. It would be enormous help for the project and this way you can actually see those issues fixed. Joerg Hohwiller wrote: > > But just to mention some here is that it automatically sets the "JRE > System Library". In my case it has to be java6 for development. However > the plugin is always smarter than I am and sets it back to java5 causing > compilation errors. > The main reason to use compiler settings to set execution environment is to make sure that project won't accidentally pickup API that does not exist in earlier versions. It seem logical that when you compiling for Java 5, you are not supposed to use Java 6 JVM. This is especially critical for the projects that have multiple components that have different modules with different JVM compatibility (Apache Wicket project comes to mind). Please also note that there is a simple workaround for your issue. Basically you can disable those compiler errors in workbench preferences / Java / Compiler / Errors/Warnings / Deprecated and Restricted API / Forbidden references (access rules) and you can set it to Warning or Ignore. Same setting can be also configured for individual projects. See more detailed discussion in JIRA issue at http://jira.codehaus.org/browse/MNGECLIPSE-774 Joerg Hohwiller wrote: > > Further in another project I get ClassNotFoundErrors when launching from > eclipse because m2eclipse misscalculates the classpath. > There been several reports like that and most of them been resolved after running "Maven / Update project configuration" action and in some cases also recreating launch configuration for that case. If that doesn't help for your project, it would be a huge help if you can open new jira issue and provide us test project that would allow to reproduce this. Joerg Hohwiller wrote: > > Then if I use filtering and edit a filtered source-file m2eclipse does NOT > update it (BTW there is a funny workaround to make > filtering acceptable with mvn eclipse:eclipse). > I don't quite understand what you referring to, but if you can submit jira issue with simple test project that would show the issue we can see what we can do about it. Please also note that Maven does not provide enough infrastructure to implement efficient resource processing, so m2eclipse only tracking changes in resource source folders and full filtering is only done when you run Project / Clean... See more details about integration with Maven build lifecycle at http://docs.codehaus.org/display/M2ECLIPSE/Maven+build+lifecycle Joerg Hohwiller wrote: > > In the end using this plugin makes working with eclipse sometimes even > slower than with 1. (eclipse:eclipse). While I edit some file, everything > blocks and eclipse says it is "updating maven dependencies". Log says it > is porcessing *javadoc.jar files - I dont want them. Too much magic as it > seems... > This may happen if you have javadoc generation bound to one of the Maven lifecycle phases executed on resource changes. You can try to move javadoc plugin binding to "package" phase. If that won't help, please open JIRA issue and provide sample test project that would allow us to reproduce. Thanks Eugene -- View this message in context: http://www.nabble.com/Any-chance-for-maven-and-IDE-%28eclipse%29--tp18659892p18727487.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
