[JBoss JIRA] (JBIDE-18812) Unable to build Web Services
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18812?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-18812:
-----------------------------------
Fix Version/s: 4.3.0.Alpha1
> Unable to build Web Services
> ----------------------------
>
> Key: JBIDE-18812
> URL: https://issues.jboss.org/browse/JBIDE-18812
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform, webservices
> Affects Versions: 4.3.0.Alpha1
> Reporter: Xavier Coulon
> Fix For: 4.3.0.Alpha1
>
>
> When running a {{mvn clean verify}} on MacOSX, I get the following errors:
> {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.5...
> [INFO] Adding repository http://download.jboss.org/jbosstools/builds/staging/jbosstools-base_maste...
> [INFO] Adding repository http://download.jboss.org/jbosstools/builds/staging/jbosstools-server_mas...
> [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}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 9 months
[JBoss JIRA] (JBIDE-18812) Unable to build Web Services
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18812?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-18812:
-----------------------------------
Priority: Blocker (was: Major)
> Unable to build Web Services
> ----------------------------
>
> Key: JBIDE-18812
> URL: https://issues.jboss.org/browse/JBIDE-18812
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform, webservices
> Affects Versions: 4.3.0.Alpha1
> Reporter: Xavier Coulon
> Priority: Blocker
> Fix For: 4.3.0.Alpha1
>
>
> When running a {{mvn clean verify}} on MacOSX, I get the following errors:
> {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.5...
> [INFO] Adding repository http://download.jboss.org/jbosstools/builds/staging/jbosstools-base_maste...
> [INFO] Adding repository http://download.jboss.org/jbosstools/builds/staging/jbosstools-server_mas...
> [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}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 9 months
[JBoss JIRA] (JBIDE-18806) When discovery URL is not set, "Software/Updates" page is silently hidden
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18806?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-18806:
----------------------------------
Assignee: Nick Boldt
> When discovery URL is not set, "Software/Updates" page is silently hidden
> -------------------------------------------------------------------------
>
> Key: JBIDE-18806
> URL: https://issues.jboss.org/browse/JBIDE-18806
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: central
> Affects Versions: 4.2.0.Final
> Reporter: Mickael Istria
> Assignee: Nick Boldt
> Attachments: JBDS801-central-no-software-update-tab.png
>
>
> With latest CI build (in http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_8.... ), Central editor seems to miss the "Software/Updates" tab.
> Log mentions an error, which doesn't seem related at first sight:
> {code:none}
> !SESSION 2014-11-21 15:51:47.555 -----------------------------------------------
> eclipse.buildId=unknown
> java.version=1.8.0_11
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> !ENTRY org.jboss.tools.project.examples 4 0 2014-11-21 15:53:24.762
> !MESSAGE All attempts to discover connectors have failed
> !SUBENTRY 1 org.eclipse.mylyn.discovery.core 4 0 2014-11-21 15:53:24.762
> !MESSAGE Failed to get connectors from RemoteProxyWizardDiscoveryStrategy
> !STACK 0
> java.lang.NullPointerException
> at java.net.URI$Parser.parse(URI.java:3042)
> at java.net.URI.<init>(URI.java:588)
> at org.jboss.tools.project.examples.internal.discovery.xpl.RemoteExternalBundleDiscoveryStrategy.loadRegistry(RemoteExternalBundleDiscoveryStrategy.java:90)
> at org.jboss.tools.project.examples.internal.discovery.xpl.ExternalBundleDiscoveryStrategy.performDiscovery(ExternalBundleDiscoveryStrategy.java:117)
> at org.jboss.tools.project.examples.internal.discovery.ChainedDiscoveryStrategy.performDiscovery(ChainedDiscoveryStrategy.java:62)
> at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscovery.performDiscovery(ConnectorDiscovery.java:114)
> at org.jboss.tools.central.internal.discovery.wizards.ProxyWizardManager.loadWizards(ProxyWizardManager.java:107)
> at org.jboss.tools.central.internal.discovery.wizards.ProxyWizardUpdateJob.run(ProxyWizardUpdateJob.java:45)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 9 months
[JBoss JIRA] (JBIDE-18806) When discovery URL is not set, "Software/Updates" page is silently hidden
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18806?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-18806:
-------------------------------
Attachment: JBDS801-central-no-software-update-tab.png
> When discovery URL is not set, "Software/Updates" page is silently hidden
> -------------------------------------------------------------------------
>
> Key: JBIDE-18806
> URL: https://issues.jboss.org/browse/JBIDE-18806
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: central
> Affects Versions: 4.2.0.Final
> Reporter: Mickael Istria
> Attachments: JBDS801-central-no-software-update-tab.png
>
>
> With latest CI build (in http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_8.... ), Central editor seems to miss the "Software/Updates" tab.
> Log mentions an error, which doesn't seem related at first sight:
> {code:none}
> !SESSION 2014-11-21 15:51:47.555 -----------------------------------------------
> eclipse.buildId=unknown
> java.version=1.8.0_11
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> !ENTRY org.jboss.tools.project.examples 4 0 2014-11-21 15:53:24.762
> !MESSAGE All attempts to discover connectors have failed
> !SUBENTRY 1 org.eclipse.mylyn.discovery.core 4 0 2014-11-21 15:53:24.762
> !MESSAGE Failed to get connectors from RemoteProxyWizardDiscoveryStrategy
> !STACK 0
> java.lang.NullPointerException
> at java.net.URI$Parser.parse(URI.java:3042)
> at java.net.URI.<init>(URI.java:588)
> at org.jboss.tools.project.examples.internal.discovery.xpl.RemoteExternalBundleDiscoveryStrategy.loadRegistry(RemoteExternalBundleDiscoveryStrategy.java:90)
> at org.jboss.tools.project.examples.internal.discovery.xpl.ExternalBundleDiscoveryStrategy.performDiscovery(ExternalBundleDiscoveryStrategy.java:117)
> at org.jboss.tools.project.examples.internal.discovery.ChainedDiscoveryStrategy.performDiscovery(ChainedDiscoveryStrategy.java:62)
> at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscovery.performDiscovery(ConnectorDiscovery.java:114)
> at org.jboss.tools.central.internal.discovery.wizards.ProxyWizardManager.loadWizards(ProxyWizardManager.java:107)
> at org.jboss.tools.central.internal.discovery.wizards.ProxyWizardUpdateJob.run(ProxyWizardUpdateJob.java:45)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 9 months
[JBoss JIRA] (JBIDE-18748) Create and use an Eclipse Mars M3 target-platform
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18748?page=com.atlassian.jira.plugi... ]
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.5...
[INFO] Adding repository http://download.jboss.org/jbosstools/builds/staging/jbosstools-base_maste...
[INFO] Adding repository http://download.jboss.org/jbosstools/builds/staging/jbosstools-server_mas...
[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)
11 years, 9 months
[JBoss JIRA] (JBIDE-18812) Unable to build Web Services
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18812?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-18812:
----------------------------------
Description:
When running a {{mvn clean verify}} on MacOSX, I get the following errors:
{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.5...
[INFO] Adding repository http://download.jboss.org/jbosstools/builds/staging/jbosstools-base_maste...
[INFO] Adding repository http://download.jboss.org/jbosstools/builds/staging/jbosstools-server_mas...
[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}
was:
When running a {{mvn clean verify}} on MacOSX, I get the following errors:
{{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.5...
[INFO] Adding repository http://download.jboss.org/jbosstools/builds/staging/jbosstools-base_maste...
[INFO] Adding repository http://download.jboss.org/jbosstools/builds/staging/jbosstools-server_mas...
[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}}
> Unable to build Web Services
> ----------------------------
>
> Key: JBIDE-18812
> URL: https://issues.jboss.org/browse/JBIDE-18812
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform, webservices
> Affects Versions: 4.3.0.Alpha1
> Reporter: Xavier Coulon
>
> When running a {{mvn clean verify}} on MacOSX, I get the following errors:
> {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.5...
> [INFO] Adding repository http://download.jboss.org/jbosstools/builds/staging/jbosstools-base_maste...
> [INFO] Adding repository http://download.jboss.org/jbosstools/builds/staging/jbosstools-server_mas...
> [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}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 9 months
[JBoss JIRA] (JBIDE-18812) Unable to build Web Services
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18812?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-18812:
------------------------------------
Looks related to JBIDE-18748 and specifically to this commit by [~mickael_istria]:
https://github.com/jbosstools/jbosstools-build/commit/007b63530a5ec718d39...
based on [~dgolovin] 's suggestion:
https://issues.jboss.org/browse/JBIDE-18748?focusedCommentId=13021329&pag...
> Unable to build Web Services
> ----------------------------
>
> Key: JBIDE-18812
> URL: https://issues.jboss.org/browse/JBIDE-18812
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform, webservices
> Affects Versions: 4.3.0.Alpha1
> Reporter: Xavier Coulon
>
> When running a {{mvn clean verify}} on MacOSX, I get the following errors:
> {{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.5...
> [INFO] Adding repository http://download.jboss.org/jbosstools/builds/staging/jbosstools-base_maste...
> [INFO] Adding repository http://download.jboss.org/jbosstools/builds/staging/jbosstools-server_mas...
> [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}}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 9 months
[JBoss JIRA] (JBIDE-18813) Convert JBoss Central to an HTML5 page
by Fred Bricon (JIRA)
Fred Bricon created JBIDE-18813:
-----------------------------------
Summary: Convert JBoss Central to an HTML5 page
Key: JBIDE-18813
URL: https://issues.jboss.org/browse/JBIDE-18813
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: central
Affects Versions: 4.3.0.Alpha1
Reporter: Fred Bricon
Central Page requires new capabilities :
- needs more customization (display content depending on user preferences)
- needs to scale with JBDS-IS, Fuse content
- access to more examples, with filtering capabilities
Given that the existing page is pretty hard to maintain and suffers from scalability/UI bugs, we're heading towards an HTML5 approach :
- use an embedded SWT Browser widget (or Java FX), depending on the platform compatibility
- webpage and its content could be served remotely (as zip), and downloaded locally for offline use. this would give us more flexibility to update the content.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 9 months
[JBoss JIRA] (JBIDE-18813) Convert JBoss Central to an HTML5 page
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18813?page=com.atlassian.jira.plugi... ]
Fred Bricon reassigned JBIDE-18813:
-----------------------------------
Assignee: Fred Bricon
> Convert JBoss Central to an HTML5 page
> --------------------------------------
>
> Key: JBIDE-18813
> URL: https://issues.jboss.org/browse/JBIDE-18813
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: central
> Affects Versions: 4.3.0.Alpha1
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Fix For: 4.3.0.Alpha1
>
>
> Central Page requires new capabilities :
> - needs more customization (display content depending on user preferences)
> - needs to scale with JBDS-IS, Fuse content
> - access to more examples, with filtering capabilities
> Given that the existing page is pretty hard to maintain and suffers from scalability/UI bugs, we're heading towards an HTML5 approach :
> - use an embedded SWT Browser widget (or Java FX), depending on the platform compatibility
> - webpage and its content could be served remotely (as zip), and downloaded locally for offline use. this would give us more flexibility to update the content.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 9 months