tag:blogger.com,1999:blog-27773736.post4910485178741194513..comments2021-11-23T18:17:56.007+01:00Comments on Too Loud a Solitude: Eclipse, you are so boring sometime ...Emmanuel Lécharnyhttp://www.blogger.com/profile/00606458715529159834noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-27773736.post-70091290605534574272009-04-30T01:59:00.000+02:002009-04-30T01:59:00.000+02:00FWIW, both of these issues are handled correctly b...FWIW, both of these issues are handled correctly by m2eclipse.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-27773736.post-64354923354066460482009-04-29T19:39:00.000+02:002009-04-29T19:39:00.000+02:00First, thanks for the hard work on Apache DS. Yes,...First, thanks for the hard work on Apache DS. Yes, you rock.<br /><br />And +1 for this. I reported or loudly complained about this on the related bug (which was marked as a duplicate), and nothing's been done so far: https://bugs.eclipse.org/bugs/show_bug.cgi?id=163601Antoine Toulméhttps://www.blogger.com/profile/10554078579336455758noreply@blogger.comtag:blogger.com,1999:blog-27773736.post-23466009088940970342009-04-29T17:37:00.000+02:002009-04-29T17:37:00.000+02:00Let say I want to work on a project (say, MINA), a...Let say I want to work on a project (say, MINA), and on a previous version of this project (a branch). When I import the first one, no problem. When I import the second one, as all the .project and .classpath are generated by Maven, the name collide.Emmanuel Lécharnyhttps://www.blogger.com/profile/00606458715529159834noreply@blogger.comtag:blogger.com,1999:blog-27773736.post-76589161796516593162009-04-29T16:20:00.000+02:002009-04-29T16:20:00.000+02:00"there is no way to work with two versions of the ..."there is no way to work with two versions of the same project without having to switch the workspace (painful, to say the least !)"<br /><br />I can't follow you on this. I am doing this all the time?Jochen Wiedmannhttps://www.blogger.com/profile/09855969156780632315noreply@blogger.com