Hi all, Here is a proposal for a new 4.40.0.Alpha1-SNAPSHOT target platform: https://github.com/jbosstools/jbosstools-target-platforms/pull/30 . It consists in the following changes: * JBIDE-16073: Move to Luna M3 ** most projects have contributed a new M3 build ** SWT migrated to GTK+ 3, which is a major change on which one we should provide feedback Please review this PR and yell if there is anything shocking. You can use the following stuff to try to build build the TP locally and try out against your component: Build target-platform: $ cd jbosstools-target-platforms $ git fetch mistria JBIDE-16073 $ git checkout FETCH_HEAD $ cd jbosstools/multiple $ mvn clean install -P \!multiple2repo Then, try to built your component with this local build of the target-platform: $ cd /path/to/your/component $ mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT -Pmultiple In case you notice any issue for you component with Luna M3, create a dedicated bug to track the migration, and link it as a dependency from JBIDE-15639, so we now which projects require migration effort. In case you're not working on JBoss Tools 4.1.1 any more, please make the migration to Luna your top-priority before implementing new features in 4.2.0.Alpha1, as we'd like to release a 4.2.0.Alpha1 soon, hopefully against Luna. Cheers, -- Mickael Istria Eclipse developer at JBoss, by Red Hat My blog - My Tweets _______________________________________________ jbosstools-dev mailing list jbosstools-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev

Sorry, I did not check the command-line and just copied it from template. The command to use is $ mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT -Pmultiple.target and replaces the multiple profile by multiple.target (which exists). -- Mickael Istria Eclipse developer at JBoss, by Red Hat My blog - My Tweets

On 11/22/2013 12:11 PM, Xavier Coulon wrote: > Thanks, Mickael, > > I now have the following dependency resolution problem on the webservices component: > > [INFO] Resolving dependencies of MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.creation.core:1.6.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.creation.core/pom.xml > [INFO] Cannot complete the request. Generating details. > [INFO] Cannot complete the request. Generating details. > [INFO] {osgi.ws=cocoa, osgi.os=macosx, osgi.arch=x86, org.eclipse.update.install.features=true} > [ERROR] Cannot resolve project dependencies: > [ERROR] Software being installed: org.jboss.tools.ws.creation.core 1.6.0.qualifier > [ERROR] Missing requirement: org.jboss.tools.ws.creation.core 1.6.0.qualifier requires 'bundle org.apache.ant [1.8.2,1.9.0)' but it could not be found > [ERROR] > [ERROR] Internal error: java.lang.RuntimeException: No solution found because the problem is unsatisfiable.: [Unable to satisfy dependency from org.jboss.tools.ws.creation.core 1.6.0.qualifier to bundle org.apache.ant [1.8.2,1.9.0).; No solution found because the problem is unsatisfiable.] -> [Help 1] > org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: No solution found because the problem is unsatisfiable.: [Unable to satisfy dependency from org.jboss.tools.ws.creation.core 1.6.0.qualifier to bundle org.apache.ant [1.8.2,1.9.0).; No solution found because the problem is unsatisfiable.] > > > Can you tell me if org.apache.ant is part of the TP or not ? If it is, which version is it ? If not, can it be included (in which case I'll fill a JIRA in relation with JBIDE-15639 as mentionned in your first mail) Can you put this is JBIDE-15639? Jira makes tracking much easier. -- Mickael Istria Eclipse developer at JBoss, by Red Hat My blog - My Tweets

Hi all, Here is a proposal for a new 4.40.0.Alpha1-SNAPSHOT target platform: https://github.com/jbosstools/jbosstools-target-platforms/pull/30 . It consists in the following changes: * JBIDE-16073: Move to Luna M3 ** most projects have contributed a new M3 build ** SWT migrated to GTK+ 3, which is a major change on which one we should provide feedback Please review this PR and yell if there is anything shocking. You can use the following stuff to try to build build the TP locally and try out against your component: Build target-platform: $ cd jbosstools-target-platforms $ git fetch mistria JBIDE-16073 $ git checkout FETCH_HEAD $ cd jbosstools/multiple $ mvn clean install -P \!multiple2repo Then, try to built your component with this local build of the target-platform: $ cd /path/to/your/component $ mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT -Pmultiple In case you notice any issue for you component with Luna M3, create a dedicated bug to track the migration, and link it as a dependency from JBIDE-15639, so we now which projects require migration effort. In case you're not working on JBoss Tools 4.1.1 any more, please make the migration to Luna your top-priority before implementing new features in 4.2.0.Alpha1, as we'd like to release a 4.2.0.Alpha1 soon, hopefully against Luna. Cheers, -- Mickael Istria Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools> My blog <http://mickaelistria.wordpress.com> - My Tweets <http://twitter.com/mickaelistria> _______________________________________________ jbosstools-dev mailing list jbosstools-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev

Denis, thanks for the pointer. I tried your solution (thanks to Mickaël's help) and it actually removed the message I had, but did not fix the problem :-( I opened https://issues.jboss.org/browse/JBIDE-16137 to track that problem. Max did not have the problem on his machine (more recent update of MacOSX). Best regards, /Xavier On Nov 26, 2013, at 6:31 PM, Denis Golovin wrote: > The reason could be: >> In Luna the Equinox framework no longer publishes the PlatformAdmin service. This causes the method org.eclipse.core.runtime.Platform.getPlatformAdmin() to return null unless the compatibility fragment org.eclipse.osgi.compatibility.state is installed. > Not sure if adding this o.e.o.c.state bundle it test plug-in dependencies would help, could you try? > > Denis > > On 11/26/2013 01:43 AM, Xavier Coulon wrote: >> Hello, >> >> Web Services component build hangs on my machine (MacOSX) during some tests, as explained in this comment: https://issues.jboss.org/browse/JBIDE-16088?focusedCommentId=12926216&... >> >> Can anyone running on MacOSX try and let me know if it works or hangs ? >> >> Thanks. >> Best regards, >> /Xavier >> >> >> >> On Nov 25, 2013, at 7:28 AM, Denis Golovin wrote: >> >>> >>> base, server, jst, vpe, arquillian, portlet, birt, javaee, freemarker, webservices, livereload, openshift, central, aerogear are fine with Luna M3 TP. >>> >>> hibernate build is failing because of compilation errors. >>> >>> gwt build fails with >>> >>> [INFO] gwt.all ........................................... SUCCESS [0.347s] >>> [INFO] gwt.plugins ....................................... SUCCESS [0.008s] >>> [INFO] org.jboss.tools.gwt.core .......................... FAILURE [1.804s] >>> [INFO] org.jboss.tools.gwt.ui ............................ SKIPPED >>> [INFO] gwt.tests ......................................... SKIPPED >>> [INFO] org.jboss.tools.gwt.test .......................... SKIPPED >>> [INFO] gwt.features ...................................... SKIPPED >>> [INFO] org.jboss.tools.gwt.feature ....................... SKIPPED >>> [INFO] gwt.site .......................................... SKIPPED >>> [INFO] ------------------------------------------------------------------------ >>> [INFO] BUILD FAILURE >>> [INFO] ------------------------------------------------------------------------ >>> [INFO] Total time: 3:15.319s >>> [INFO] Finished at: Fri Nov 22 18:14:46 PST 2013 >>> [INFO] Final Memory: 57M/532M >>> [INFO] ------------------------------------------------------------------------ >>> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-packaging-plugin:0.19.0:package-plugin (default-package-plugin) on project org.jboss.tools.gwt.core: Error assembling JAR: Eclipse-SourceReferences header should be generated but ${tycho.scmUrl} is not set -> [Help 1] >>> >>> forge fails with maven 3.1.1 >>> >>> /home/eskimo/Java/apache-maven-3.1.1/bin/mvn clean install -Dmaven.repo.local=.m2/luna-m3 -Dtpc.version=4.40.0.Alpha1-SNAPSHOT -Pmultiple.target -f forge/pom.xml -DtychoVersion=0.19.0 >>> [INFO] Scanning for projects... >>> [WARNING] The POM for org.apache.maven.plugins:maven-site-plugin:jar:3.3 is invalid, transitive dependencies (if any) will not be available, enable debug logging for more details >>> [ERROR] Internal error: java.lang.RuntimeException: org.apache.maven.MavenExecutionException: Could not setup plugin ClassRealm: Plugin org.apache.maven.plugins:maven-site-plugin:3.3 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-site-plugin:jar:3.3: 1 problem was encountered while building the effective model >>> [ERROR] [FATAL] Non-readable POM /home/eskimo/Projects/jbds/jbosstools-submodules/.m2/luna-m3/org/apache/maven/plugins/maven-site-plugin/3.3/maven-site-plugin-3.3.pom: input contained no data @ >>> [ERROR] -> [Help 1] >>> org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: org.apache.maven.MavenExecutionException: Could not setup plugin ClassRealm >>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:164) >>> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555) >>> >>> >>> Denis >>> >>> >>> On 11/21/2013 07:43 AM, Mickael Istria wrote: >>>> Hi all, >>>> Here is a proposal for a new 4.40.0.Alpha1-SNAPSHOT target platform: https://github.com/jbosstools/jbosstools-target-platforms/pull/30 . >>>> It consists in the following changes: >>>> * JBIDE-16073: Move to Luna M3 >>>> ** most projects have contributed a new M3 build >>>> ** SWT migrated to GTK+ 3, which is a major change on which one we should provide feedback >>>> >>>> Please review this PR and yell if there is anything shocking. You can use the following stuff to try to build build the TP locally and try out against your component: >>>> Build target-platform: >>>> $ cd jbosstools-target-platforms >>>> $ git fetch mistria JBIDE-16073 >>>> $ git checkout FETCH_HEAD >>>> $ cd jbosstools/multiple >>>> $ mvn clean install -P \!multiple2repo >>>> Then, try to built your component with this local build of the target-platform: >>>> $ cd /path/to/your/component >>>> $ mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT -Pmultiple >>>> >>>> In case you notice any issue for you component with Luna M3, create a dedicated bug to track the migration, and link it as a dependency from JBIDE-15639, so we now which projects require migration effort. >>>> In case you're not working on JBoss Tools 4.1.1 any more, please make the migration to Luna your top-priority before implementing new features in 4.2.0.Alpha1, as we'd like to release a 4.2.0.Alpha1 soon, hopefully against Luna. >>>> >>>> Cheers, >>>> >>>> -- >>>> >>>> Mickael Istria >>>> Eclipse developer at JBoss, by Red Hat >>>> My blog - My Tweets >>>> >>>> >>>> _______________________________________________ >>>> jbosstools-dev mailing list >>>> jbosstools-dev(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >>> >>> _______________________________________________ >>> jbosstools-dev mailing list >>> jbosstools-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >> > _______________________________________________ jbosstools-dev mailing list jbosstools-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev

I verified everything again: