[JBoss JIRA] (JBIDE-26065) Add RH Central connector for nodeclipse
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26065?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-26065:
-------------------------------
Fix Version/s: 4.6.0.AM3
> Add RH Central connector for nodeclipse
> ---------------------------------------
>
> Key: JBIDE-26065
> URL: https://issues.jboss.org/browse/JBIDE-26065
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build, central-update, updatesite, upstream
> Affects Versions: 4.6.0.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.6.0.AM3
>
>
> Steps to perform:
> a) mirror a copy of the latest Nodeclipse update site onto dl.jb.org for reproduceability
> b) add that to the 3rd party target platform used for building RH Central
> c) create a connector in Central for installing Nodeclipse into devstudio and jbosstools
> The list of features to include will be those recommended in the screenshots here [1], under the *B) UPDATE SITE (BIGGER CHOICE)* section, or can be collected based on the existing Eclipse Marketplace connector provided by nodeclipse.
>
> [1] http://www.nodeclipse.org/updates/
> If any of these assumptions / feature brief details are incorrect, please correct them in this description or add comments to this JIRA.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-26065) Add RH Central connector for nodeclipse
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-26065:
----------------------------------
Summary: Add RH Central connector for nodeclipse
Key: JBIDE-26065
URL: https://issues.jboss.org/browse/JBIDE-26065
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: build, central-update, updatesite, upstream
Affects Versions: 4.6.0.AM2
Reporter: Nick Boldt
Steps to perform:
a) mirror a copy of the latest Nodeclipse update site onto dl.jb.org for reproduceability
b) add that to the 3rd party target platform used for building RH Central
c) create a connector in Central for installing Nodeclipse into devstudio and jbosstools
The list of features to include will be those recommended in the screenshots here [1], under the *B) UPDATE SITE (BIGGER CHOICE)* section, or can be collected based on the existing Eclipse Marketplace connector provided by nodeclipse.
[1] http://www.nodeclipse.org/updates/
If any of these assumptions / feature brief details are incorrect, please correct them in this description or add comments to this JIRA.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-26064) Submit a patch that avoids Windows update to run as it is being re-enabled out of user control
by Ondrej Dockal (JIRA)
Ondrej Dockal created JBIDE-26064:
-------------------------------------
Summary: Submit a patch that avoids Windows update to run as it is being re-enabled out of user control
Key: JBIDE-26064
URL: https://issues.jboss.org/browse/JBIDE-26064
Project: Tools (JBoss Tools)
Issue Type: Patch
Components: integration-tests, qa
Affects Versions: 4.6.0.AM2
Environment: Openstack windows machines (8.1 and 10)
Reporter: Ondrej Dockal
Assignee: Ondrej Dockal
Priority: Critical
Fix For: 4.6.0.AM3
Due to occasional (probably periodical, dependent on system time, ie., midnight) re-enabling of windows update service, we still encounter ClosedChannelException on windows slaves on jenkinks.
Patch will be provided, test job set up and monitored.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-25916) OpenShift Server Adapter: Error in Log after "Restart in Debug"
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25916?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-25916:
----------------------------------------
Assignee: Andre Dietisheim (was: Jeff MAURY)
> OpenShift Server Adapter: Error in Log after "Restart in Debug"
> ---------------------------------------------------------------
>
> Key: JBIDE-25916
> URL: https://issues.jboss.org/browse/JBIDE-25916
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.3.Final
> Environment: F28 + Red Hat JBoss Developer Studio Build id: GA-v20180410-1152-B2341
> Reporter: Josef Kopriva
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: debugging, server_adapter
> Fix For: 4.6.0.AM2
>
> Attachments: error-launching-server.png
>
>
> An error occurs when restarting server adapter in debug:
> {code:java}
> eclipse.buildId=11.3.0.GA-v20180410-1152-B2341
> java.version=1.8.0_162
> 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: -data file:/home/jkopriva/devstudio_B2341/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> org.jboss.tools.openshift.core
> Warning
> Wed Apr 11 18:09:03 CEST 2018
> Error while publishing server eap-app (Service) at OpenShift 3 (api.engint.openshift.com). Could not sync all pods to folder /home/jkopriva/devstudio_B2341/workspace/.metadata/.plugins/org.jboss.ide.eclipse.as.core/oc2@eap-app/deploy
> org.eclipse.core.runtime.CoreException: Error while publishing server eap-app (Service) at OpenShift 3 (api.engint.openshift.com). Could not sync all pods to folder /home/jkopriva/devstudio_B2341/workspace/.metadata/.plugins/org.jboss.ide.eclipse.as.core/oc2@eap-app/deploy
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftPublishController.handleSyncDownFailure(OpenShiftPublishController.java:92)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftPublishController.publishStart(OpenShiftPublishController.java:61)
> at org.jboss.ide.eclipse.as.wtp.core.server.behavior.CachedPublisherProfileBehavior.publishStart(CachedPublisherProfileBehavior.java:47)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:942)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774)
> at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3182)
> at org.eclipse.wst.server.core.internal.Server.publish(Server.java:1340)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController$1.run(OpenShiftLaunchController.java:261)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> Contains: Syncing com.openshift.restclient.capability.resources.IRSyncable$PodPeer@e159132 to com.openshift.restclient.capability.resources.IRSyncable$LocalPeer@e822802 failed: could not make way for new regular file: ROOT.war
> rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1659) [generator=3.1.3]
> error: exit status 23
> {code}
> {code:java}
> eclipse.buildId=11.3.0.GA-v20180410-1152-B2341
> java.version=1.8.0_162
> 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: -data file:/home/jkopriva/devstudio_B2341/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> org.jboss.tools.openshift.core
> Error
> Wed Apr 11 18:09:03 CEST 2018
> Error while publishing server eap-app (Service) at OpenShift 3 (api.engint.openshift.com). Could not sync all pods to folder /home/jkopriva/devstudio_B2341/workspace/.metadata/.plugins/org.jboss.ide.eclipse.as.core/oc2@eap-app/deploy
> {code}
> {code:java}
> eclipse.buildId=11.3.0.GA-v20180410-1152-B2341
> java.version=1.8.0_162
> 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: -data file:/home/jkopriva/devstudio_B2341/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> org.jboss.tools.openshift.core
> Error
> Wed Apr 11 18:09:03 CEST 2018
> Syncing com.openshift.restclient.capability.resources.IRSyncable$PodPeer@e159132 to com.openshift.restclient.capability.resources.IRSyncable$LocalPeer@e822802 failed: could not make way for new regular file: ROOT.war
> rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1659) [generator=3.1.3]
> error: exit status 23
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-22138) Server adapter: doesn't respect openshift maven profile
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22138?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22138:
-------------------------------
Sprint: devex #150 June 2019
> Server adapter: doesn't respect openshift maven profile
> -------------------------------------------------------
>
> Key: JBIDE-22138
> URL: https://issues.jboss.org/browse/JBIDE-22138
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Environment: JBoss Developer Studio (Core Features) 9.1.0.GA-v20160403-1700-B477
> Openshift plugin 3.1.0.Final-v20160401-2357-B263
> Reporter: Rafael Benevides
> Assignee: Fred Bricon
> Labels: openshift_v3, server_adapter
> Fix For: 4.6.0.AM3
>
>
> This is a follow up on JBIDE-22128.
> The maven profile is never read to determine the actual archive name. That will require more coupling to m2e, in order to load the pom.xml model using the openshift profile, if it exists, in order to determine the archive name. This will be a long running operation and will require more significant changes
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-22138) Server adapter: doesn't respect openshift maven profile
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22138?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22138:
-------------------------------------
Fix Version/s: 4.6.0.AM3
(was: 4.6.x)
> Server adapter: doesn't respect openshift maven profile
> -------------------------------------------------------
>
> Key: JBIDE-22138
> URL: https://issues.jboss.org/browse/JBIDE-22138
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Environment: JBoss Developer Studio (Core Features) 9.1.0.GA-v20160403-1700-B477
> Openshift plugin 3.1.0.Final-v20160401-2357-B263
> Reporter: Rafael Benevides
> Assignee: Fred Bricon
> Labels: openshift_v3, server_adapter
> Fix For: 4.6.0.AM3
>
>
> This is a follow up on JBIDE-22128.
> The maven profile is never read to determine the actual archive name. That will require more coupling to m2e, in order to load the pom.xml model using the openshift profile, if it exists, in order to determine the archive name. This will be a long running operation and will require more significant changes
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-22138) Server adapter: doesn't respect openshift maven profile
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22138?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-22138:
----------------------------------------
Assignee: Andre Dietisheim (was: Fred Bricon)
> Server adapter: doesn't respect openshift maven profile
> -------------------------------------------------------
>
> Key: JBIDE-22138
> URL: https://issues.jboss.org/browse/JBIDE-22138
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Environment: JBoss Developer Studio (Core Features) 9.1.0.GA-v20160403-1700-B477
> Openshift plugin 3.1.0.Final-v20160401-2357-B263
> Reporter: Rafael Benevides
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter
> Fix For: 4.6.0.AM3
>
>
> This is a follow up on JBIDE-22128.
> The maven profile is never read to determine the actual archive name. That will require more coupling to m2e, in order to load the pom.xml model using the openshift profile, if it exists, in order to determine the archive name. This will be a long running operation and will require more significant changes
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-25616) [WATCHER] Server Adapter: Cannot start remote debugger for Fuse app deployed on open.paas.redhat.com
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25616?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-25616:
------------------------------------------
[~aurelien.pupier] thx for pointing out.
[~jkopriva] can you reverify this again, please?
> [WATCHER] Server Adapter: Cannot start remote debugger for Fuse app deployed on open.paas.redhat.com
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25616
> URL: https://issues.jboss.org/browse/JBIDE-25616
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.Final
> Environment: F27 + open.paas.redhat.com + Red Hat JBoss Developer Studio Build id: GA-v20180122-2025-B1884
> Reporter: Josef Kopriva
> Assignee: Jeff MAURY
> Labels: docker_image, fis, upstream
> Fix For: 4.6.x
>
> Attachments: java, screenshot-1.png
>
>
> Starting of server ends with error:
> {code:java}
> eclipse.buildId=11.2.0.GA-v20180122-2025-B1884
> java.version=1.8.0_151
> 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: -data file:/home/jkopriva/devstudio_B1884_jiras/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> org.jboss.tools.openshift.core
> Error
> Wed Jan 24 11:21:45 CET 2018
> 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 45933 on localhost
> at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.toCoreException(OpenShiftServerUtils.java:670)
> at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.toCoreException(OpenShiftServerUtils.java:674)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.attachRemoteDebugger(OpenShiftLaunchController.java:404)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.access$1(OpenShiftLaunchController.java:387)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController$2.onDebugChange(OpenShiftLaunchController.java:272)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.toggleDebugger(OpenShiftDebugMode.java:238)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:174)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:100)
> 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)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-26035) Convert SSP to function in an osgi environment
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26035?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-26035:
------------------------------------
I don't think Jigsaw provides isolation and not supporting multi version is a blocker
> Convert SSP to function in an osgi environment
> ----------------------------------------------
>
> Key: JBIDE-26035
> URL: https://issues.jboss.org/browse/JBIDE-26035
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: stack-server-protocol
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.6.0.AM2
>
>
> {code}
> mkdir felix
> cd felix
> wget http://download.nextag.com/apache/felix/org.apache.felix.main.distributio...
> unzip org.apache.felix.main.distribution-5.6.10.zip
> cd ../
> git clone git@github.com:robstryker/org.jboss.tools.ssp.git
> cd org.jboss.tools.ssp
> git checkout osgi_branch1
> mvn clean install
> #cp api/target/org.jboss.tools.ssp.api-0.8-SNAPSHOT.jar ../felix/felix-framework-5.6.10/bundle/
> #cp launching/target/org.jboss.tools.ssp.launching-0.8-SNAPSHOT.jar ../felix/felix-framework-5.6.10/bundle
> #cp server-spi/target/org.jboss.tools.ssp.server.spi-0.8-SNAPSHOT.jar ../felix/felix-framework-5.6.10/bundle/
> #cp server/target/org.jboss.tools.ssp.server-0.8-SNAPSHOT.jar ../felix/felix-framework-5.6.10/bundle/
> du -ah | grep "jar$" | grep "target/" | grep -v "test-classes" | grep -v "classes/" | grep -v "schema" | grep -v "client" | cut -c 1,2,3,4 --complement | awk '{ print "cp " $0 " ../felix/felix-framework-5.6.10/bundle/";}' | sh
> cd ../felix/felix-framework-5.6.10/
> java -jar bin/felix.jar
> {code}
> Note error:
> API Bundle Started
> Launching Bundle Started
> Server bundle started
> ERROR: Bundle org.jboss.tools.ssp.server.wildfly [11] Error starting file:/home/rob/tmp/ssp_osgi/felix/felix-framework-5.6.10/bundle/org.jboss.tools.ssp.server.wildfly-0.8-SNAPSHOT.jar (org.osgi.framework.BundleException: Activator start error in bundle org.jboss.tools.ssp.server.wildfly [11].)
> java.lang.NoClassDefFoundError: org/osgi/framework/BundleActivator
> at java.base/java.lang.ClassLoader.defineClass1(Native Method)
> at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1007)
> This is very strange. All the other bundles start fine. This bundle can't even find its osgi classes.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months