Community
Participate
Working Groups
Here is the catalog entry for groovy-eclipse. I am not sure what should go where the ??? are, so please help me fill in with something reasonable. <catalogItem> <categoryId>???</categoryId> <description>Groovy-Eclipse m2e configurator</description> <groupId>???</groupId> <id>org.codehaus.groovy.m2eclipse</id> <kind>???</kind> <license>EPL</license> <name>Groovy-Eclipse</name> <provider>the Codehaus</provider> <p2> <repositoryUrl>http://dist.codehaus.org/groovy/distributions/greclipse/snapshot/e3.7</repositoryUrl> <iuId>org.codehaus.groovy.m2eclipse.feature.group</iuId> <lifecycleMappingIU> <iuId>org.codehaus.groovy.m2eclipse</iuId> </lifecycleMappingIU> </p2> <overview> <summary>Maven Integration for Grooovy-Eclipse</summary> <url>http://docs.codehaus.org/display/GROOVY/Groovy-Eclipse+compiler+plugin+for+Maven</url> </overview> </catalogItem>
Do you have a sample project I can use to make sure everything works end-to-end? The idea is that users should be able to point maven import wizard at a groovy project and everything needed to work on that project should be installed and configured as part of the import flow. I am not saying this does not happen already, just that I don't use groovy ;-).
Created attachment 203269 [details] Sample m2e groovy-eclipse project This is a maven project that use the groovy-eclipse-compiler. It should be imported into the workspace as a groovy project. An additional requirement is that you must have Groovy-Eclipse installed in your workbench. The update site is here: http://dist.codehaus.org/groovy/distributions/greclipse/snapshot/e3.7/
(In reply to comment #2) > > An additional requirement is that you must have Groovy-Eclipse installed in > your workbench. The update site is here: > > http://dist.codehaus.org/groovy/distributions/greclipse/snapshot/e3.7/ Can you change groovy project configurator feature to require Groovy-Eclipse feature? This will enable automatic installation of everything required to work on maven groovy projects as part of maven project import flow.
Done. (Or will be done when I push out the change.)
Should be there now. Sorry for the delay, we have some issues with catalog publishing scripts.
thanks,
Andrew, is there a chance you can move Groovy-Eclipse m2e configurator off dist.codehaus.org to a more reliable host? For some reason I can't access it from our datacenter and it is quite flaky from my home too.
Try using this update site instead: http://dist.springsource.org/release/GRECLIPSE/e3.7/
Andrew, I tested this locally : <catalogItem> <categoryId>org.eclipse.m2e.discovery.category.lifecycles</categoryId> <description>Groovy-Eclipse m2e configurator</description> <groupId>lifecycles</groupId> <id>org.codehaus.groovy.m2eclipse</id> <kind>lifecycles</kind> <license>EPL</license> <name>Groovy-Eclipse</name> <provider>the Codehaus</provider> <p2> <repositoryUrl>http://dist.springsource.org/release/GRECLIPSE/e3.7/</repositoryUrl> <iuId>org.codehaus.groovy.m2eclipse.feature.group</iuId> <iuVersion>2.6.1.xx-20120301-1000-e37-RELEASE</iuVersion> <lifecycleMappingIU> <iuId>org.codehaus.groovy.m2eclipse</iuId> </lifecycleMappingIU> </p2> <overview> <summary>Maven Integration for Grooovy-Eclipse</summary> <url>http://docs.codehaus.org/display/GROOVY/Groovy-Eclipse+compiler+plugin+for+Maven</url> </overview> </catalogItem> But when installing on Juno (Java IDE) M7, the connector doesn't appear in the discovery catalog or when I import your test project. If I try to manually install the m2e groovy configurator from http://dist.springsource.org/release/GRECLIPSE/e3.7/, I get : Cannot complete the install because of a conflicting dependency. Software being installed: Groovy-Eclipse M2E integration 2.6.1.xx-20120301-1000-e37-RELEASE (org.codehaus.groovy.m2eclipse.feature.group 2.6.1.xx-20120301-1000-e37-RELEASE) Software currently installed: Eclipse IDE for Java Developers 1.5.0.20120507-1216 (epp.package.java 1.5.0.20120507-1216) Software currently installed: Tycho Project Configurators 0.6.0.201112050222 (org.sonatype.tycho.m2e.feature.feature.group 0.6.0.201112050222) Only one of the following can be installed at once: Java Development Tools Core 3.8.1.v20120516-1705 (org.eclipse.jdt.core 3.8.1.v20120516-1705) Java Development Tools Core 3.7.3.xx-20120301-1000-e37-RELEASE (org.eclipse.jdt.core 3.7.3.xx-20120301-1000-e37-RELEASE) Object Teams Development Tooling Core 3.8.1.v_OTDT_r210_201205221318 (org.eclipse.jdt.core 3.8.1.v_OTDT_r210_201205221318) Java Development Tools Core 3.8.1.v20120502-0834 (org.eclipse.jdt.core 3.8.1.v20120502-0834) Cannot satisfy dependency: From: Eclipse IDE for Java Developers 1.5.0.20120507-1216 (epp.package.java 1.5.0.20120507-1216) To: org.eclipse.epp.package.java.feature.feature.group [1.5.0.20120507-1216] Cannot satisfy dependency: From: Groovy-Eclipse Feature 2.6.1.xx-20120301-1000-e37-RELEASE (org.codehaus.groovy.eclipse.feature.feature.group 2.6.1.xx-20120301-1000-e37-RELEASE) To: org.codehaus.groovy.jdt.patch.feature.group [2.6.1.xx-20120301-1000-e37-RELEASE] Cannot satisfy dependency: From: Groovy-Eclipse M2E integration 2.6.1.xx-20120301-1000-e37-RELEASE (org.codehaus.groovy.m2eclipse.feature.group 2.6.1.xx-20120301-1000-e37-RELEASE) To: org.codehaus.groovy.eclipse.feature.feature.group 0.0.0 Cannot satisfy dependency: From: EPP Java Package 1.5.0.20120507-1216 (org.eclipse.epp.package.java.feature.feature.group 1.5.0.20120507-1216) To: org.eclipse.jdt.feature.group 3.8.0 Cannot satisfy dependency: From: Java Development Tools Launching Support 3.6.100.v20120430-2105 (org.eclipse.jdt.launching 3.6.100.v20120430-2105) To: bundle org.eclipse.jdt.core [3.8.0,4.0.0) Cannot satisfy dependency: From: Tycho Project Configurators 0.6.0.201112050222 (org.sonatype.tycho.m2e 0.6.0.201112050222) To: bundle org.eclipse.jdt.launching 0.0.0 Cannot satisfy dependency: From: Tycho Project Configurators 0.6.0.201112050222 (org.sonatype.tycho.m2e.feature.feature.group 0.6.0.201112050222) To: org.sonatype.tycho.m2e [0.6.0.201112050222] Cannot satisfy dependency: From Patch: org.codehaus.groovy.jdt.patch.feature.group 2.6.1.xx-20120301-1000-e37-RELEASE Eclipse Java Development Tools 3.8.0.v20120429-1635-8-8nFpCFNOfwK7Wad4VDgZ7BC834 (org.eclipse.jdt.feature.group 3.8.0.v20120429-1635-8-8nFpCFNOfwK7Wad4VDgZ7BC834) To: org.eclipse.jdt.core [3.7.3.xx-20120301-1000-e37-RELEASE] Cannot satisfy dependency: From Patch: org.codehaus.groovy.jdt.patch.feature.group 2.6.1.xx-20120301-1000-e37-RELEASE Eclipse Java Development Tools 3.8.0.v20120429-1635-8-8nFpCFNOfwK9UsfRVGGNOBC834 (org.eclipse.jdt.feature.group 3.8.0.v20120429-1635-8-8nFpCFNOfwK9UsfRVGGNOBC834) To: org.eclipse.jdt.core [3.7.3.xx-20120301-1000-e37-RELEASE]
That's right. The update site is only applicable for indigo (more specifically, JDT core 3.7.x). The Indigo update site will be at http://dist.springsource.org/release/GRECLIPSE/e4.2, but it has not been released yet and is not yet available. Currently, you can use http://dist.codehaus.org/groovy/distributions/greclipse/snapshot/e4.2, but this is only the snapshot release. As far as configurator discovery goes, I don't know if it is a requirement to have only one entry for each configurator, but I hope it would be possible to have one targeting e37 and another targeting e42/e38.
It is possible to have multiple entries of the same configurator with different <m2e-versions> in the catalog, see buildhelper entries for example.
OK, at this point I am unsure what I should do. 1. Where do I find the buildHelper example? 2. But more than that, the m2e version is not relevant here since my understanding is that v1.1 can be installed into any of Helios, Indigo and Juno, same with 1.2. It's not the m2e version that matters, but the jdt version. 3. Some users are already on Juno (but none have asked for m2e configurator discovery support yet). So, it would be nice to update the entry with the snapshot update site, and once the final release is available, change to the permanent update site.
I misunderstood the question, sorry. I do not know if it is possible to define different versions of configurator entries for different eclipse versions.
Andrew : so my understanding is you want to see the snapshot, e4.2 compatible version of the groovy configurator available for m2e 1.1 users? m2e 1.0 users would see the Indigo based version?
(In reply to comment #14) > Andrew : so my understanding is you want to see the snapshot, e4.2 compatible > version of the groovy configurator available for m2e 1.1 users? m2e 1.0 users > would see the Indigo based version? Maybe that's right. Is it possible to install m2e 1.1 on indigo or 1.0 onto Juno? If the answer is no, then I agree with your statement. If the answer is yes, then there is a problem. Groovy-Eclipse versions are specific to an Eclipse version (more specifically, a JDT version). So, e37 groovy-eclipse needs JDT 3.7.x and e42 groovy-eclipse needs JDT 3.8.x.
It is possible to install m2e 1.1 on Indigo and it is also possible to install 1.0 on Juno, although that won't work well due to breaking "fixes" in 4.2.
So, you're saying that even though 1.1 on indigo is possible (and vice versa), it's not recommended (and not officially supported?). This makes things easier for me and the greclipse catalog can work within the existing api. At this point, though I'm a little unsure what needs to happen next. What do you need from me to move forward? You are more familiar with the catalog syntax than I am and you know the different update sites for the different m2e versions. Is there anything else?
1.1 is supported both on Juno and Indigo. 1.0 is supported on Indigo and Helios (or whatever name 3.6 had). 1.0 is not supported on Juno and there are known incompatibilities.
closing old/stale bugreports
Moved to https://github.com/eclipse-m2e/m2e-core/issues/
