[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 commented on JBIDE-18812:
---------------------------------------
[~mickael_istria],
Yes, that's the whole point I think.
I'm running a Java 8 64bits, as shown below:
{code}
$> mvn -version
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
Apache Maven 3.2.3 (33f8c3e1027c3ddde99d3cdebad2656a31e8fdf4; 2014-08-11T22:58:10+02:00)
Maven home: /usr/local/Cellar/maven/3.2.3/libexec
Java version: 1.8.0_25, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_25.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.10.1", arch: "x86_64", family: "mac"
{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
> 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, 8 months
[JBoss JIRA] (JBIDE-18704) Application wizard, Embed wizard: Cartridge details are black in Win8
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18704?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-18704:
----------------------------------
Fix Version/s: (was: 4.2.1.CR1)
> Application wizard, Embed wizard: Cartridge details are black in Win8
> ---------------------------------------------------------------------
>
> Key: JBIDE-18704
> URL: https://issues.jboss.org/browse/JBIDE-18704
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: application_wizard
> Fix For: 4.3.0.Alpha1
>
> Attachments: application-wizard-black-details.png, application-wizard-fixed-details.png, embed-cartridges-black-details.png, embed-cartridges-fixed-details.png
>
>
> The details group which shows the details for the selected cartridge or quickstart are black in win8:
> !application-wizard-black-details.png!
> !embed-cartridges-black-details.png!
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 8 months
[JBoss JIRA] (JBIDE-18812) Unable to build Web Services
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18812?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-18812:
----------------------------------------
Eclipse Mars drops support for macosx 32-bits. Is you JVM a 32-bits one or a 64-bits one?
> 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, 8 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 commented on JBIDE-18812:
---------------------------------------
[~mickael_istria],
No, I'm on MacOSX and it doesn't work on this platform:
{code}
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}
{code}
I may not be running the build job locally with the {{x86_64}} architecture, and IIRC, there were some SWT removal for 32bit architectures on MacOSX, right ?
> 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, 8 months
[JBoss JIRA] (JBIDE-18820) define how to handle ide.properties and avoid parent pom to always change
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18820?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-18820:
---------------------------------------------
Yes, devstudio should just use the product version which is defined in the pom of that.
The "unhandled" situation is where to define jboss tools version used when devstudio is *not* present. This was previously defined in a foundation plugin but last minutes commits rolling that back to be globally defined. See https://github.com/jbosstools/jbosstools-base/pull/353/files
The intent is/was that we would just rebuild the base plugins between maintanence builds *NOT* triggering a full rebuild.
> define how to handle ide.properties and avoid parent pom to always change
> -------------------------------------------------------------------------
>
> Key: JBIDE-18820
> URL: https://issues.jboss.org/browse/JBIDE-18820
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Reporter: Max Rydahl Andersen
>
> As illustrated in JBIDE-18806 our current setup of how ide.properties and project versioning are not working or at least we seem to not get it updated right.
> Current workaround applied is that parent pom now again defines the global version even though this is not reliable at all since not all plugins will be rebuilt. (see JBIDE-13452 for earlier attempts on this)
> Opening this jira to make sure we walkthrough and write down which values should be in ide.properties and what level (4.2.0.CR1, 4.2.0 or 4.2. etc), when they get updated (hopefully rarely) and how to avoid parent pom from always having to respin because of a maintanence release.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 8 months
[JBoss JIRA] (JBIDE-18806) When discovery URL is not set, "Software/Updates" page is silently hidden
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18806?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-18806:
---------------------------------------------
see https://issues.jboss.org/browse/JBIDE-18820 so we don't continue mixing concerns together in same jira.
> 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
> Fix For: 4.2.1.CR1, 4.3.0.Alpha1
>
> Attachments: JBDS801-central-no-software-update-tab.png, JBIDE18806-fixed-jbds.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, 8 months
[JBoss JIRA] (JBIDE-18806) When discovery URL is not set, "Software/Updates" page is silently hidden
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18806?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-18806:
---------------------------------------------
[~mickael_istria] yes, completely agree with your observations.
> 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
> Fix For: 4.2.1.CR1, 4.3.0.Alpha1
>
> Attachments: JBDS801-central-no-software-update-tab.png, JBIDE18806-fixed-jbds.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, 8 months
[JBoss JIRA] (JBIDE-18820) define how to handle ide.properties and avoid parent pom to always change
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18820?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-18820:
----------------------------------------
Where are the jbosstools.version and jbdevstudio.version actually used? IMO, they shouldn't be used by the properties mechanism, which should instead rely on some other metadata that's accessible at build time (such as a bundle version or product version).
> define how to handle ide.properties and avoid parent pom to always change
> -------------------------------------------------------------------------
>
> Key: JBIDE-18820
> URL: https://issues.jboss.org/browse/JBIDE-18820
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Reporter: Max Rydahl Andersen
>
> As illustrated in JBIDE-18806 our current setup of how ide.properties and project versioning are not working or at least we seem to not get it updated right.
> Current workaround applied is that parent pom now again defines the global version even though this is not reliable at all since not all plugins will be rebuilt. (see JBIDE-13452 for earlier attempts on this)
> Opening this jira to make sure we walkthrough and write down which values should be in ide.properties and what level (4.2.0.CR1, 4.2.0 or 4.2. etc), when they get updated (hopefully rarely) and how to avoid parent pom from always having to respin because of a maintanence release.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 8 months
[JBoss JIRA] (JBIDE-18806) When discovery URL is not set, "Software/Updates" page is silently hidden
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18806?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-18806:
----------------------------------------
Also, the appropriate fix for this issue would have been to simply update the properties. Refactoring them should have been tracked separately has it's something that has side-effects on how we update a stream.
> 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
> Fix For: 4.2.1.CR1, 4.3.0.Alpha1
>
> Attachments: JBDS801-central-no-software-update-tab.png, JBIDE18806-fixed-jbds.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, 8 months
[JBoss JIRA] (JBIDE-13445) Enable possibility of deployment scanner additions for remote servers
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13445?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-13445:
-------------------------------------
[~mmalina] Can you replicate this using either master or the 4.2.1 branch build?
> Enable possibility of deployment scanner additions for remote servers
> ---------------------------------------------------------------------
>
> Key: JBIDE-13445
> URL: https://issues.jboss.org/browse/JBIDE-13445
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: server
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.2.x
>
>
> Currently, additions tot he deployment scanners are limited to locally running servers. This is due to a lack of API allowing accurate discovery of what folders need to be added for remote servers, specifically no way for as.core classes to discover what the remote server home is, what the remote configuration folder is, etc. There is a lack of api here, and that will need to be fixed before this issue can work.
> Remember: If a remote server is not running with its management ports exposed, do not attempt to add the scanners, as the management connections will fail.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 8 months