[JBoss JIRA] (ERT-534) support building with Tycho 1.0 [EBZ#526333]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/ERT-534?page=com.atlassian.jira.plugin.sy... ]
Nick Boldt resolved ERT-534.
----------------------------
Resolution: Done
All wtp projects can now build with Tycho 1.0
> support building with Tycho 1.0 [EBZ#526333]
> --------------------------------------------
>
> Key: ERT-534
> URL: https://issues.jboss.org/browse/ERT-534
> Project: Eclipse Release Train
> Issue Type: Task
> Components: WTP Webservices
> Reporter: Friendly Jira Robot
> Assignee: Nick Boldt
> Labels: 3.10_M4, bzira, jst.ws
> Fix For: Photon (4.8) M4
>
>
> Quick hack to support Tycho 1.0 (instead of <= 0.26.0) is to enable tycho-compiler-plugin's useProjectSettings=false [1] so that things like API restrictions that SHOULD fail the build are allowed.
> Ultimately, these API violation should be fixed, but if your Eclipse settings are allowing these to be ignored as warnings instead of errors, then so too should Tycho do the same.
> Thus we need to add this to the root pom:
> <build>
> <plugins>
> <plugin>
> <groupId>org.eclipse.tycho</groupId>
> <artifactId>tycho-compiler-plugin</artifactId>
> <version>${tycho.version}</version>
> <configuration>
> <useProjectSettings>false</useProjectSettings>
> </configuration>
> </plugin>
> </plugins>
> </build>
> [1] https://wiki.eclipse.org/Tycho/Release_Notes/1.0.0#Compiler
> BTW, the Version here should be 3.10, but bugzilla needs to be updated to add that fixversion.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (JBIDE-25109) Server adapter editor: provide ability to only change debug port (and not the debug port key)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25109?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25109:
-------------------------------------
Sprint: (was: devex #141 December 2017)
> Server adapter editor: provide ability to only change debug port (and not the debug port key)
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-25109
> URL: https://issues.jboss.org/browse/JBIDE-25109
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.5.1.AM2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter_editor
> Fix For: 4.5.x
>
>
> Currently there's only 1 checkbox to allow the user to set the debugging key and port. If one only wants to set a custom debug port only, he cannot, he also has to provide the debug key at the same time. We should provide an additional checkbox to enable the debug port only, changing the existing one to only enable/disable the debug key.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (JBIDE-25258) Integration Tests: Server adapter wizard and editor dont allow invalid devmode-/debug-port-key nor debug port value
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25258?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25258:
-------------------------------------
Sprint: (was: devex #141 December 2017)
> Integration Tests: Server adapter wizard and editor dont allow invalid devmode-/debug-port-key nor debug port value
> -------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25258
> URL: https://issues.jboss.org/browse/JBIDE-25258
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: openshift
> Affects Versions: 4.5.1.AM2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter_editor, server_adapter_wizard
> Fix For: 4.5.x
>
> Attachments: server-adapter-wizard.png, server-adater-editor.png
>
>
> In JBIDE-25108 the server adapter wizard and -editor were changed so that they would only allow valid values for
> * devmode key
> * debug port key
> * debug port value
> The editor should not allow saving if there are invalid values, the wizard would not allow one to finish it.
> !server-adater-editor.png|thumbnail!
> !server-adapter-wizard.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (JBIDE-25375) Server adapter: Problem occured during debugging of Fuse app deployed on open.paas.redhat.com
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25375?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25375:
-------------------------------------
Sprint: devex #142 December 2017 (was: devex #141 December 2017)
> Server adapter: Problem occured during debugging of Fuse app deployed on open.paas.redhat.com
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-25375
> URL: https://issues.jboss.org/browse/JBIDE-25375
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.AM1
> Environment: F27 + open.paas.redhat.com + DevStudio 11.2.0.AM1-v20171106-0622-B1520
> Reporter: Josef Kopriva
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter
> Fix For: 4.5.2.AM3
>
>
> {code:java}
> Could not launch server camel-ose-springboot-xml (Service) at OpenShift 3 (open.paas.redhat.com)
> org.eclipse.core.runtime.CoreException: Could not start remote debugger to (forwarded) port 46271 on localhost
> at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.toCoreException(OpenShiftServerUtils.java:639)
> at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.toCoreException(OpenShiftServerUtils.java:643)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.attachRemoteDebugger(OpenShiftLaunchController.java:410)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.access$1(OpenShiftLaunchController.java:395)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController$2.onDebugChange(OpenShiftLaunchController.java:276)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.toggleDebugger(OpenShiftDebugMode.java:191)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:167)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:98)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> eclipse.buildId=11.2.0.AM1-v20171106-0622-B1520
> java.version=1.8.0_144
> 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
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (JBIDE-25111) Explorer, Properties: allow intellingent "Delete Resource" (via label-matching?)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25111?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25111:
-------------------------------------
Sprint: devex #142 December 2017 (was: devex #141 December 2017)
> Explorer, Properties: allow intellingent "Delete Resource" (via label-matching?)
> --------------------------------------------------------------------------------
>
> Key: JBIDE-25111
> URL: https://issues.jboss.org/browse/JBIDE-25111
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.5.1.AM2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.5.2.AM3
>
>
> OpenShift Online only allows you 1 project. Thus the usual approach to create a project per application and kill the project to remove all resources cannot be used in OpenShift online. We thus need a way to delete all resources that are related to an application. Ex. with a more powerful delete action that pops up a window with a filter-/query-parameter that would filter the list of available resources and then allow to delete all the visible (or selected ones)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (JBIDE-25501) Installer tests doesn't work on Ubuntu with OpenJDK
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25501?page=com.atlassian.jira.plugi... ]
Lukáš Valach commented on JBIDE-25501:
--------------------------------------
It seems that there are incompatible versions of OpenJDK and NSS (See bug \[1\]).
\[1\] https://bugzilla.redhat.com/show_bug.cgi?id=1332456
NSS RPM packages installed on Ubuntu 17.10:
{code}
hudson@ubuntu17:/tmp$ apt list --installed | grep nss
libjansson4/artful,now 2.10-1 amd64 [installed,automatic]
libnss-mdns/artful,now 0.10-8ubuntu1 amd64 [installed]
libnss-myhostname/artful-updates,artful-security,now 234-2ubuntu12.1 amd64 [installed,auto-removable]
libnss3/artful,now 2:3.32-1ubuntu3 amd64 [installed,automatic]
libxmlsec1-nss/artful,now 1.2.24-4 amd64 [installed,automatic]
libxmlsec1-openssl/artful,now 1.2.24-4 amd64 [installed]
openssh-client/artful,now 1:7.5p1-10 amd64 [installed]
openssh-server/artful,now 1:7.5p1-10 amd64 [installed]
openssh-sftp-server/artful,now 1:7.5p1-10 amd64 [installed]
openssl/artful-updates,artful-security,now 1.0.2g-1ubuntu13.3 amd64 [installed]
perl-openssl-defaults/artful,now 3 amd64 [installed,automatic]
{code}
OpenJDK on shared drive (which doesn't work):
{code}
hudson@ubuntu17:/tmp$ /qa/tools/opt/x86_64/openjdk-1.8.0/bin/java -version
openjdk version "1.8.0_131"
OpenJDK Runtime Environment (build 1.8.0_131-b11)
OpenJDK 64-Bit Server VM (build 25.131-b11, mixed mode)
{code}
Local installation of OpenJDK RPM which works fine:
{code}
hudson@ubuntu17:/tmp$ java -version
openjdk version "1.8.0_151"
OpenJDK Runtime Environment (build 1.8.0_151-8u151-b12-0ubuntu0.17.10.2-b12)
OpenJDK 64-Bit Server VM (build 25.151-b12, mixed mode)
{code}
So we probably need either to update OpenJDK or to downgrade NSS.
> Installer tests doesn't work on Ubuntu with OpenJDK
> ---------------------------------------------------
>
> Key: JBIDE-25501
> URL: https://issues.jboss.org/browse/JBIDE-25501
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: qa
> Affects Versions: 4.5.2.AM3
> Reporter: Lukáš Valach
> Assignee: Lukáš Valach
> Fix For: 4.5.2.AM3
>
>
> Installer tests doesn't work on Ubuntu with OpenJDK.
> Log snippet:
> {code}
> ...
> [ubuntu1710] $ /qa/tools/opt/groovy-2.4.3/bin/groovy -DuseWhiteSpace /mnt/hudson_workspace/workspace/Devstudio_Installation/Devstudio_installation/devstudio_installation_standalone_11.matrix-lvalach/jdk/openjdk-1.8/label/ubuntu1710/devstudio-installer.test/src/main/groovy/prepareJBDSInstall.groovy https://devstudio.redhat.com/11/snapshots/builds/devstudio.product_master... /mnt/hudson_workspace/workspace/Devstudio_Installation/Devstudio_installation/devstudio_installation_standalone_11.matrix-lvalach/jdk/openjdk-1.8/label/ubuntu1710
> Installer not found on local machine
> Attempting to download
> [get] Getting: https://devstudio.redhat.com/11/snapshots/builds/devstudio.product_master...
> [get] To: /mnt/hudson_workspace/workspace/Devstudio_Installation/Devstudio_installation/devstudio_installation_standalone_11.matrix-lvalach/jdk/openjdk-1.8/label/ubuntu1710/devstudio-11.2.0.AM2-v20171212-1017-B1750-installer-standalone.jar
> [get] Exception in thread "Thread-1" java.lang.InternalError
> [get] at sun.security.ec.SunEC.initialize(Native Method)
> [get] at sun.security.ec.SunEC.access$000(SunEC.java:49)
> [get] at sun.security.ec.SunEC$1.run(SunEC.java:61)
> [get] at sun.security.ec.SunEC$1.run(SunEC.java:58)
> [get] at java.security.AccessController.doPrivileged(Native Method)
> [get] at sun.security.ec.SunEC.<clinit>(SunEC.java:58)
> [get] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> [get] at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> [get] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> [get] at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> [get] at java.lang.Class.newInstance(Class.java:442)
> [get] at sun.security.jca.ProviderConfig$2.run(ProviderConfig.java:221)
> [get] at sun.security.jca.ProviderConfig$2.run(ProviderConfig.java:206)
> [get] at java.security.AccessController.doPrivileged(Native Method)
> [get] at sun.security.jca.ProviderConfig.doLoadProvider(ProviderConfig.java:206)
> [get] at sun.security.jca.ProviderConfig.getProvider(ProviderConfig.java:187)
> [get] at sun.security.jca.ProviderList.getProvider(ProviderList.java:233)
> [get] at sun.security.jca.ProviderList.getService(ProviderList.java:331)
> [get] at sun.security.jca.GetInstance.getInstance(GetInstance.java:157)
> [get] at javax.net.ssl.SSLContext.getInstance(SSLContext.java:156)
> [get] at javax.net.ssl.SSLContext.getDefault(SSLContext.java:96)
> [get] at javax.net.ssl.SSLSocketFactory.getDefault(SSLSocketFactory.java:122)
> [get] at javax.net.ssl.HttpsURLConnection.getDefaultSSLSocketFactory(HttpsURLConnection.java:332)
> [get] at javax.net.ssl.HttpsURLConnection.<init>(HttpsURLConnection.java:289)
> [get] at sun.net.www.protocol.https.HttpsURLConnectionImpl.<init>(HttpsURLConnectionImpl.java:85)
> [get] at sun.net.www.protocol.https.Handler.openConnection(Handler.java:62)
> [get] at sun.net.www.protocol.https.Handler.openConnection(Handler.java:57)
> [get] at java.net.URL.openConnection(URL.java:979)
> [get] at org.apache.tools.ant.taskdefs.Get$GetThread.openConnection(Get.java:680)
> [get] at org.apache.tools.ant.taskdefs.Get$GetThread.get(Get.java:626)
> [get] at org.apache.tools.ant.taskdefs.Get$GetThread.run(Get.java:616)
> {code}
> ...then the installer archive isn't downloaded.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (JBIDE-25000) Server adapter: starting into debugging fails initially (succeeds on a latter try)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25000?page=com.atlassian.jira.plugi... ]
Andre Dietisheim resolved JBIDE-25000.
--------------------------------------
Resolution: Done
Labels: openshift_v3 server_adapter (was: )
> Server adapter: starting into debugging fails initially (succeeds on a latter try)
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-25000
> URL: https://issues.jboss.org/browse/JBIDE-25000
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.0.AM2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: server_adapter, openshift_v3
> Fix For: 4.5.2.AM3
>
> Attachments: failed-to-connect-v8-vm.png
>
>
> # ASSERT: have an application running in OpenShift based on the "nodejs-mongo-persistent" template
> # ASSERT: have a server adapter for it
> # EXEC/ASSERT: have the adapter started in non-debugging/normal mode
> # EXEC: restart the adapter debugging
> Result:
> !failed-to-connect-v8-vm.png!
> {code}
> java.io.IOException: Failed to get version
> at org.eclipse.wst.jsdt.chromium.internal.v8native.JavascriptVmImpl.newIOException(JavascriptVmImpl.java:114)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:132)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attach(StandaloneVmImpl.java:79)
> at org.eclipse.wst.jsdt.chromium.debug.core.model.JavascriptVmEmbedderFactory$4$1.attach(JavascriptVmEmbedderFactory.java:207)
> at org.eclipse.wst.jsdt.chromium.debug.core.model.DebugTargetImpl.attach(DebugTargetImpl.java:74)
> at org.eclipse.wst.jsdt.chromium.debug.ui.launcher.LaunchTypeBase.launch(LaunchTypeBase.java:101)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> Caused by: java.util.concurrent.ExecutionException: java.io.IOException: End of stream
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:206)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:127)
> ... 9 more
> Caused by: java.io.IOException: End of stream
> at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:127)
> at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:1)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl.perform(Handshaker.java:104)
> at org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection$ReaderThread.run(SocketConnection.java:158)
> {code}
> ps. this can be simulated in the CDK, by having everything set and once the pod is up and ithe adapter is in debug, stopping the port forwarding.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months