[jbosstools-issues] [JBoss JIRA] (JBIDE-18748) Create and use an Eclipse Mars M3 target-platform

[Xavier Coulon (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-18748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022108#comment-13022108 ] 

Xavier Coulon commented on JBIDE-18748:
---------------------------------------

I can't build Web Services with TP 4.3.0.Alpha1 (as shown in JBIDE-18812):

{code}
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=128m; support was removed in 8.0
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
[INFO] Scanning for projects...
[WARNING] Could not transfer metadata org.jboss.tools:parent:4.3.0.Alpha1-SNAPSHOT/maven-metadata.xml from/to jbosstools-base (${jbosstools-base-site}): No connector available to access repository jbosstools-base (${jbosstools-base-site}) of type p2 using the available factories WagonRepositoryConnectorFactory
[WARNING] Could not transfer metadata org.jboss.tools:parent:4.3.0.Alpha1-SNAPSHOT/maven-metadata.xml from/to jbosstools-server (${jbosstools-server-site}): No connector available to access repository jbosstools-server (${jbosstools-server-site}) of type p2 using the available factories WagonRepositoryConnectorFactory
[INFO] Computing target platform for MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.core:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.core/pom.xml
[INFO] Adding repository http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.50.0.Alpha1-SNAPSHOT/REPO
[INFO] Adding repository http://download.jboss.org/jbosstools/builds/staging/jbosstools-base_master/all/repo
[INFO] Adding repository http://download.jboss.org/jbosstools/builds/staging/jbosstools-server_master/all/repo
[INFO] Resolving dependencies of MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.core:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.core/pom.xml
[INFO] Resolving class path of MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.core:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.core/pom.xml
[INFO] Computing target platform for MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.creation.core:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.creation.core/pom.xml
[INFO] Resolving dependencies of MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.creation.core:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.creation.core/pom.xml
[INFO] Resolving class path of MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.creation.core:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.creation.core/pom.xml
[INFO] Computing target platform for MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.creation.ui:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.creation.ui/pom.xml
[INFO] Resolving dependencies of MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.creation.ui:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.creation.ui/pom.xml
[INFO] Resolving class path of MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.creation.ui:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.creation.ui/pom.xml
[INFO] Computing target platform for MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.ui:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.ui/pom.xml
[INFO] Resolving dependencies of MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.ui:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.ui/pom.xml
[INFO] Resolving class path of MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.ui:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.ui/pom.xml
[INFO] Computing target platform for MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.jaxrs.core:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.jaxrs.core/pom.xml
[INFO] Resolving dependencies of MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.jaxrs.core:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.jaxrs.core/pom.xml
[ERROR] Internal error: java.lang.RuntimeException: Could not determine SWT implementation fragment bundle for environment {osgi.os=macosx, osgi.ws=cocoa, org.eclipse.update.install.features=true, osgi.arch=x86} -> [Help 1]
org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: Could not determine SWT implementation fragment bundle for environment {osgi.os=macosx, osgi.ws=cocoa, org.eclipse.update.install.features=true, osgi.arch=x86}
	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:166)
	at org.apache.maven.cli.MavenCli.execute(MavenCli.java:582)
	at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
	at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:483)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
	at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
	at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: java.lang.RuntimeException: Could not determine SWT implementation fragment bundle for environment {osgi.os=macosx, osgi.ws=cocoa, org.eclipse.update.install.features=true, osgi.arch=x86}
	at org.eclipse.tycho.p2.util.resolution.ProjectorResolutionStrategy.fixSWT(ProjectorResolutionStrategy.java:155)
	at org.eclipse.tycho.p2.util.resolution.ProjectorResolutionStrategy.resolve(ProjectorResolutionStrategy.java:95)
	at org.eclipse.tycho.p2.util.resolution.AbstractResolutionStrategy.resolve(AbstractResolutionStrategy.java:63)
	at org.eclipse.tycho.p2.resolver.P2ResolverImpl.resolveDependencies(P2ResolverImpl.java:166)
	at org.eclipse.tycho.p2.resolver.P2ResolverImpl.resolveDependencies(P2ResolverImpl.java:103)
	at org.eclipse.tycho.p2.resolver.P2DependencyResolver.doResolveDependencies(P2DependencyResolver.java:352)
	at org.eclipse.tycho.p2.resolver.P2DependencyResolver.resolveDependencies(P2DependencyResolver.java:325)
	at org.eclipse.tycho.core.resolver.DefaultTychoResolver.resolveProject(DefaultTychoResolver.java:107)
	at org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:75)
	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:310)
	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:154)
	... 11 more
{code}

> Create and use an Eclipse Mars M3 target-platform
> -------------------------------------------------
>
>                 Key: JBIDE-18748
>                 URL: https://issues.jboss.org/browse/JBIDE-18748
>             Project: Tools (JBoss Tools)
>          Issue Type: Task
>          Components: build, discovery, target-platform
>    Affects Versions: 4.3.0.Alpha1
>            Reporter: Mickael Istria
>            Assignee: Mickael Istria
>            Priority: Blocker
>             Fix For: 4.3.0.Alpha1
>
>
> Eclipse Mars M3 is already there. We should adopt it ASAP in order to be able to make tests and contribute early enough.



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)