[JBoss JIRA] (JBDS-4077) Cannot run integration tests against Devstudio with latest target platform
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4077?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-4077 at 10/24/16 12:07 PM:
-------------------------------------------------------------
So comparing the screenshots above I see that in the broken case (devstudio 10.2.AM2) the window title, icon, toolbar items, and even a perspective icon missing.
Good vs. bad:
!https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Developer%20Studio%20Integration%20Tests/job/deltaspike.102AM1/2/jdk=jdk1.8,label=rhel7/artifact/jbosstools-integration-tests/tests/org.jboss.tools.deltaspike.ui.bot.test/target/screenshots/wildfly-10.xml/org.jboss.tools.deltaspike.ui.bot.test.ConfigPropertyAnnotationTest.testInjectUnsupportedConfigProperty.png|thumbnail! !https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Developer%20Studio%20Integration%20Tests/job/deltaspike.102AM2/1/jdk=jdk1.8,label=rhel7/artifact/jbosstools-integration-tests/tests/org.jboss.tools.deltaspike.ui.bot.test/target/screenshots/wildfly-10.xml/org.jboss.tools.deltaspike.ui.bot.test.ExceptionHandlerAnnotationTest@ServerRequirement.png|thumbnail!
This to me suggests that either the bad one is just Eclipse (but then we'd see "data -- JavaEE -- Eclipse" as the product name in the window title instead of "data -- JavaEE -- ") or else it's devstudio but a ton of plugins haven't been enabled/activated. Could be because if an invalid install, or because of missing OS-level deps (like GTK2? GTK3? SWT?) or maybe it's launching with a JDK lower than 1.8 so JDK8-dependent stuff isn't loading.
Point is ... we need to figure out what's broken in the AM2 devstudio install on that slave. Can we start devstudio with {code}
-debug -console -consolelog{code} to get more details about what's (not) happening?
Or, can someone run these tests locally and debug them in Eclipse?
http://maven.apache.org/surefire/maven-surefire-plugin/examples/debugging...
was (Author: nickboldt):
So comparing the screenshots above I see that in the broken case (devstudio 10.2.AM2) the window title, icon, toolbar items, and even a perspective icon missing.
Good vs. bad:
!https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Developer%20Studio%20Integration%20Tests/job/deltaspike.102AM1/2/jdk=jdk1.8,label=rhel7/artifact/jbosstools-integration-tests/tests/org.jboss.tools.deltaspike.ui.bot.test/target/screenshots/wildfly-10.xml/org.jboss.tools.deltaspike.ui.bot.test.ConfigPropertyAnnotationTest.testInjectUnsupportedConfigProperty.png|thumbnail! !https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Developer%20Studio%20Integration%20Tests/job/deltaspike.102AM2/1/jdk=jdk1.8,label=rhel7/artifact/jbosstools-integration-tests/tests/org.jboss.tools.deltaspike.ui.bot.test/target/screenshots/wildfly-10.xml/org.jboss.tools.deltaspike.ui.bot.test.ExceptionHandlerAnnotationTest@ServerRequirement.png|thumbnail!
This to me suggests that either the bad one is just Eclipse (but then we'd see "data -- JavaEE -- Eclipse" as the product name in the window title instead of "data -- JavaEE -- ") or else it's devstudio but a ton of plugins haven't been enabled/activated. Could be because if an invalid install, or because of missing OS-level deps (like GTK2? GTK3? SWT?) or maybe it's launching with a JDK lower than 1.8 so JDK8-dependent stuff isn't loading.
Point is ... we need to figure out what's broken in the AM2 devstudio install on that slave. Can we start devstudio with {code}
-debug -console -consolelog{code} to get more details about what's (not) happening?
> Cannot run integration tests against Devstudio with latest target platform
> --------------------------------------------------------------------------
>
> Key: JBDS-4077
> URL: https://issues.jboss.org/browse/JBDS-4077
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, target-platform
> Affects Versions: 10.2.0.AM1
> Reporter: Jan Richter
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 10.2.0.AM3
>
> Attachments: .log, jbosstools-integration-tests.log.txt.zip, no_devstudio.jpg, no_devstudio.png, org.jboss.tools.deltaspike.ui.bot.test.DeltaspikeAllBotTests.txt, org.jboss.tools.deltaspike.ui.bot.test.log.txt, org.jboss.tools.deltaspike.ui.bot.test.log_0.txt, Screenshot_2016-10-05_10-00-03.png, Screenshot_2016-10-05_10-00-21.png, Screenshot_2016-10-05_10-00-28.png, Screenshot_2016-10-05_10-00-57.png, Screenshot_2016-10-05_10-01-14.png, Screenshot_2016-10-05_10-01-32.png, shell.png, TEST-org.jboss.tools.deltaspike.ui.bot.test.DeltaspikeAllBotTests.xml, tpfail.png
>
>
> Integration tests run from maven against Devstudio, which was built using the latest target platform (4.61.0.AM1-SNAPSHOT), cannot properly launch all the plugins and fail afterwards.
> A full devstudio should open when the tests are run. Instead it looks like this:
> !tpfail.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-22362) Server Adapter: Static changes done to nodejs application are not visible
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22362?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-22362 at 10/24/16 12:07 PM:
---------------------------------------------------------------------
[~ibuziuk] I noticed one error:
ASSERT: have a nodejs app running in OpenShift and the project imported to the Eclipse workspace
EXEC: Open nodejs in context menu of the "nodejs-example" server adapter Show In > Web Browser
EXEC: Restart nodejs-example in debug mode via context menu of the server adapter "Restart in Debug"
EXEC: modify workspace project "nodejs-ex/views/index.html": change title "<h1>Welcome....</h1>"
EXEC: refresh browser
ASSERT: change is visible in browser
EXEC: pick "Restart" in context menu of the "nodejs-example" server adapter.
Result:
Error pops up "Enabling 'DEV_MODE' for deployment config nodejs-example" has encountered an error
!enabling-dev-mode-has-encountered-an-error.png!
In Eclipse log there's the following output:
{code}
com.openshift.restclient.OpenShiftException: Exception trying to PUT https://192.168.121.152:8443/oapi/v1/namespaces/test/deploymentconfigs/no... response code: 409 Operation cannot be fulfilled on deploymentconfigs "nodejs-example": the object has been modified; please apply your changes to the latest version and try again
at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.createOpenShiftException(ResponseCodeInterceptor.java:114)
at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.intercept(ResponseCodeInterceptor.java:65)
at okhttp3.RealCall$ApplicationInterceptorChain.proceed(RealCall.java:190)
at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:163)
at okhttp3.RealCall.execute(RealCall.java:57)
at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:217)
at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:194)
at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:183)
at com.openshift.internal.restclient.DefaultClient.update(DefaultClient.java:275)
at org.jboss.tools.openshift.core.connection.Connection.updateResource(Connection.java:451)
at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController$1.run(OpenShiftLaunchController.java:159)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
!ENTRY org.jboss.tools.openshift.core 4 0 2016-10-24 18:03:41.308
!MESSAGE Unable to enable 'DEV_MODE' for deployment config nodejs-example
!STACK 0
com.openshift.restclient.OpenShiftException: Exception trying to PUT https://192.168.121.152:8443/oapi/v1/namespaces/test/deploymentconfigs/no... response code: 409 Operation cannot be fulfilled on deploymentconfigs "nodejs-example": the object has been modified; please apply your changes to the latest version and try again
at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.createOpenShiftException(ResponseCodeInterceptor.java:114)
at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.intercept(ResponseCodeInterceptor.java:65)
at okhttp3.RealCall$ApplicationInterceptorChain.proceed(RealCall.java:190)
at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:163)
at okhttp3.RealCall.execute(RealCall.java:57)
at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:217)
at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:194)
at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:183)
at com.openshift.internal.restclient.DefaultClient.update(DefaultClient.java:275)
at org.jboss.tools.openshift.core.connection.Connection.updateResource(Connection.java:451)
at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController$1.run(OpenShiftLaunchController.java:159)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
{code}
was (Author: adietish):
[~ibuziuk] I noticed one error:
ASSERT: have a nodejs app running in OpenShift and the project imported to the Eclipse workspace
EXEC: Open nodejs in context menu of the "nodejs-example" server adapter Show In > Web Browser
EXEC: Restart nodejs-example in debug mode via context menu of the server adapter "Restart in Debug"
EXEC: modify workspace project "nodejs-ex/views/index.html": change title "<h1>Welcome....</h1>"
EXEC: refresh browser
ASSERT: change is visible in browser
EXEC: pick "Restart" in context menu of the "nodejs-example" server adapter.
Result:
Error pops up "Enabling 'DEV_MODE' for deployment config nodejs-example" has encountered an error
!enabling-dev-mode-has-encountered-an-error.png!
> Server Adapter: Static changes done to nodejs application are not visible
> -------------------------------------------------------------------------
>
> Key: JBIDE-22362
> URL: https://issues.jboss.org/browse/JBIDE-22362
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: javascript, openshift
> Affects Versions: 4.4.0.Alpha2
> Reporter: Marián Labuda
> Assignee: Ilya Buziuk
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.2.AM3
>
> Attachments: enabling-dev-mode-has-encountered-an-error.png
>
>
> I am having an OpenShift application based either on nodejs-example or nodejs-mongodb-example template. Once application is up and running I create a new server adapter and perform changes in index.html. These changes are static and should be (?) immediately visible on OpenShift server, but they are not. I have checked whether changes were published, but rsync in console shows expected output also changes done manually on the server side to index.html are not visible in browser (even when cache overwritten is triggered - so there is no caching problem in browser). This seems to be upstream issues, but requires investigating.
> So far I have tried it on CDK OpenShift. It would be nice to test it on other OpenShift instances, also on templates using different base docker image.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-22362) Server Adapter: Static changes done to nodejs application are not visible
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22362?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-22362:
------------------------------------------
[~ibuziuk] I noticed one error:
ASSERT: have a nodejs app running in OpenShift and the project imported to the Eclipse workspace
EXEC: Open nodejs in context menu of the "nodejs-example" server adapter Show In > Web Browser
EXEC: Restart nodejs-example in debug mode via context menu of the server adapter "Restart in Debug"
EXEC: modify workspace project "nodejs-ex/views/index.html": change title "<h1>Welcome....</h1>"
EXEC: refresh browser
ASSERT: change is visible in browser
EXEC: pick "Restart" in context menu of the "nodejs-example" server adapter.
Result:
Error pops up "Enabling 'DEV_MODE' for deployment config nodejs-example" has encountered an error
!enabling-dev-mode-has-encountered-an-error.png!
> Server Adapter: Static changes done to nodejs application are not visible
> -------------------------------------------------------------------------
>
> Key: JBIDE-22362
> URL: https://issues.jboss.org/browse/JBIDE-22362
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: javascript, openshift
> Affects Versions: 4.4.0.Alpha2
> Reporter: Marián Labuda
> Assignee: Ilya Buziuk
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.2.AM3
>
>
> I am having an OpenShift application based either on nodejs-example or nodejs-mongodb-example template. Once application is up and running I create a new server adapter and perform changes in index.html. These changes are static and should be (?) immediately visible on OpenShift server, but they are not. I have checked whether changes were published, but rsync in console shows expected output also changes done manually on the server side to index.html are not visible in browser (even when cache overwritten is triggered - so there is no caching problem in browser). This seems to be upstream issues, but requires investigating.
> So far I have tried it on CDK OpenShift. It would be nice to test it on other OpenShift instances, also on templates using different base docker image.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBDS-4077) Cannot run integration tests against Devstudio with latest target platform
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4077?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4077:
----------------------------------
So comparing the screenshots above I see that in the broken case (devstudio 10.2.AM2) the window title, icon, toolbar items, and even a perspective icon missing.
Good vs. bad:
!https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Developer%20Studio%20Integration%20Tests/job/deltaspike.102AM1/2/jdk=jdk1.8,label=rhel7/artifact/jbosstools-integration-tests/tests/org.jboss.tools.deltaspike.ui.bot.test/target/screenshots/wildfly-10.xml/org.jboss.tools.deltaspike.ui.bot.test.ConfigPropertyAnnotationTest.testInjectUnsupportedConfigProperty.png|thumbnail! !https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Developer%20Studio%20Integration%20Tests/job/deltaspike.102AM2/1/jdk=jdk1.8,label=rhel7/artifact/jbosstools-integration-tests/tests/org.jboss.tools.deltaspike.ui.bot.test/target/screenshots/wildfly-10.xml/org.jboss.tools.deltaspike.ui.bot.test.ExceptionHandlerAnnotationTest@ServerRequirement.png|thumbnail!
This to me suggests that either the bad one is just Eclipse (but then we'd see "data -- JavaEE -- Eclipse" as the product name in the window title instead of "data -- JavaEE -- ") or else it's devstudio but a ton of plugins haven't been enabled/activated. Could be because if an invalid install, or because of missing OS-level deps (like GTK2? GTK3? SWT?) or maybe it's launching with a JDK lower than 1.8 so JDK8-dependent stuff isn't loading.
Point is ... we need to figure out what's broken in the AM2 devstudio install on that slave. Can we start devstudio with {code}
-debug -console -consolelog{code} to get more details about what's (not) happening?
> Cannot run integration tests against Devstudio with latest target platform
> --------------------------------------------------------------------------
>
> Key: JBDS-4077
> URL: https://issues.jboss.org/browse/JBDS-4077
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, target-platform
> Affects Versions: 10.2.0.AM1
> Reporter: Jan Richter
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 10.2.0.AM3
>
> Attachments: .log, jbosstools-integration-tests.log.txt.zip, no_devstudio.jpg, no_devstudio.png, org.jboss.tools.deltaspike.ui.bot.test.DeltaspikeAllBotTests.txt, org.jboss.tools.deltaspike.ui.bot.test.log.txt, org.jboss.tools.deltaspike.ui.bot.test.log_0.txt, Screenshot_2016-10-05_10-00-03.png, Screenshot_2016-10-05_10-00-21.png, Screenshot_2016-10-05_10-00-28.png, Screenshot_2016-10-05_10-00-57.png, Screenshot_2016-10-05_10-01-14.png, Screenshot_2016-10-05_10-01-32.png, shell.png, TEST-org.jboss.tools.deltaspike.ui.bot.test.DeltaspikeAllBotTests.xml, tpfail.png
>
>
> Integration tests run from maven against Devstudio, which was built using the latest target platform (4.61.0.AM1-SNAPSHOT), cannot properly launch all the plugins and fail afterwards.
> A full devstudio should open when the tests are run. Instead it looks like this:
> !tpfail.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBTIS-950) Cannot connect to fuse runtime after installing by the installer
by Andrej Podhradsky (JIRA)
Andrej Podhradsky created JBTIS-950:
---------------------------------------
Summary: Cannot connect to fuse runtime after installing by the installer
Key: JBTIS-950
URL: https://issues.jboss.org/browse/JBTIS-950
Project: JBoss Tools Integration Stack
Issue Type: Bug
Components: distribution
Affects Versions: 10.0.0.GA
Environment: devstudio-integration-stack-rt-10.0.0.CR1-standalone-installer.jar
Reporter: Andrej Podhradsky
Priority: Critical
Cannot connect to fuse runtime after installing by the installer. The problem is that the runtime doesn't specify any user by default. This is important if you need to execute a command in the terminal (Terminal view).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBTIS-949) Rename the name of the installer with runtime
by Andrej Podhradsky (JIRA)
Andrej Podhradsky created JBTIS-949:
---------------------------------------
Summary: Rename the name of the installer with runtime
Key: JBTIS-949
URL: https://issues.jboss.org/browse/JBTIS-949
Project: JBoss Tools Integration Stack
Issue Type: Enhancement
Components: distribution
Affects Versions: 10.0.0.GA
Environment: devstudio-integration-stack-rt-10.0.0.CR1-standalone-installer.jar
Reporter: Andrej Podhradsky
Priority: Minor
Rename the name of the installer with runtime. I suggest
{code}
devstudio-integration-stack-10.0.0.CR1-runtime-installer.jar
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBTIS-948) Runtime is not detected if the Devstudio was installed using the InstallConfigRecord.xml
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-948?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky updated JBTIS-948:
------------------------------------
Steps to Reproduce:
# Install the Devstudio manually
# In the folder 'devstudio' you can find the file InstallConfigRecord.xml
# Delete the folder 'devstudio' and install it from cmd as follows
{code}
java -jar devstudio-integration-stack-rt-10.0.0.CR1-standalone-installer.jar InstallConfigRecord.xml
{code}
was:
# Install the Devstudio manually
# In the folder 'devstudio' you can find the file InstallConfigRecord.xml
# Delete the folder 'devstudio' and install it from cmd as follows
{code}
java -jar devstudio-integration-stack-rt-10.0.0.CR1-standalone-installer.jar ./InstallConfigRecord.xml
{code}
> Runtime is not detected if the Devstudio was installed using the InstallConfigRecord.xml
> ----------------------------------------------------------------------------------------
>
> Key: JBTIS-948
> URL: https://issues.jboss.org/browse/JBTIS-948
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Affects Versions: 10.0.0.GA
> Environment: devstudio-integration-stack-rt-10.0.0.CR1-standalone-installer.jar
> Reporter: Andrej Podhradsky
>
> Runtime is not detected if the Devstudio was installed using the InstallConfigRecord.xml. It seems that the folder for runtime detection is set to {{<user>/jboss-runtimes}}.
> The above folder can be found at Preferences > JBoss Tools > JBoss Runtime Detection
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBTIS-948) Runtime is not detected if the Devstudio was installed using the InstallConfigRecord.xml
by Andrej Podhradsky (JIRA)
Andrej Podhradsky created JBTIS-948:
---------------------------------------
Summary: Runtime is not detected if the Devstudio was installed using the InstallConfigRecord.xml
Key: JBTIS-948
URL: https://issues.jboss.org/browse/JBTIS-948
Project: JBoss Tools Integration Stack
Issue Type: Bug
Components: distribution
Affects Versions: 10.0.0.GA
Environment: devstudio-integration-stack-rt-10.0.0.CR1-standalone-installer.jar
Reporter: Andrej Podhradsky
Runtime is not detected if the Devstudio was installed using the InstallConfigRecord.xml. It seems that the folder for runtime detection is set to {{<user>/jboss-runtimes}}.
The above folder can be found at Preferences > JBoss Tools > JBoss Runtime Detection
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBDS-4134) missing require-bundles in rpm install
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4134?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-4134 at 10/24/16 11:37 AM:
-------------------------------------------------------------
Alternatively, we could make the devstudio rpm depend on eclipse-tm-terminal-connectors, which will also install eclipse-cdt, eclipse-rse, eclipse-launchbar, eclipse-remote. This might allow us to remove more org.eclipse.* stuff from the devstudio RPM as it's available from upstream rpms.
{code}
dnf whatprovides */org.eclipse.tm.terminal.connector.local*
* rh-eclipse46-eclipse-tm-terminal-connectors
* eclipse-tm-terminal-connectors
* eclipse-tm-terminal{code}
and
{code}
#➔ yum remove install rh-eclipse46-eclipse-tm-terminal-connectors
Redirecting to '/usr/bin/dnf install rh-eclipse46-eclipse-tm-terminal-connectors' (see 'man yum2dnf')
Last metadata expiration check: 0:38:50 ago on Mon Oct 24 10:57:44 2016.
Dependencies resolved.
==============================================================================================================================================================================================
Package Arch Version Repository Size
==============================================================================================================================================================================================
Installing:
gcc-c++ x86_64 6.2.1-2.fc24 updates 11 M
libstdc++-devel x86_64 6.2.1-2.fc24 updates 1.8 M
libtool x86_64 2.4.6-12.fc24 updates 707 k
rh-eclipse46-eclipse-cdt x86_64 1:9.1.0-1.2.el7 rh-eclipse46-build 43 M
rh-eclipse46-eclipse-launchbar noarch 1:2.0.1-1.1.el7 rh-eclipse46-build 239 k
rh-eclipse46-eclipse-remote noarch 2.1.1-1.1.el7 rh-eclipse46-build 1.0 M
rh-eclipse46-eclipse-rse noarch 3.7.1-1.1.el7 rh-eclipse46-build 5.4 M
rh-eclipse46-eclipse-tm-terminal-connectors noarch 4.1.0-3.1.el7 rh-eclipse46-build 89 k
rh-eclipse46-freemarker noarch 2.3.23-2.2.el7 rh-eclipse46-build 952 k
Transaction Summary
==============================================================================================================================================================================================
Install 9 Packages
{code}
was (Author: nickboldt):
Alternatively, we could make the devstudio rpm depend on eclipse-tm-terminal-connectors, which will also install eclipse-cdt, eclipse-rse, eclipse-launchbar, eclipse-remote. This might allow us to remove more org.eclipse.* stuff from the devstudio RPM as it's available from upstream rpms.
{code}
dnf whatprovides */org.eclipse.tm.terminal.connector.local*
* rh-eclipse46-eclipse-tm-terminal-connectors
* eclipse-tm-terminal-connectors
* eclipse-tm-terminal{code}
and
{code}
#➔ yum install rh-eclipse46-eclipse-tm-terminal-connectors
Redirecting to '/usr/bin/dnf install rh-eclipse46-eclipse-tm-terminal-connectors' (see 'man yum2dnf')
Last metadata expiration check: 0:37:53 ago on Mon Oct 24 10:57:44 2016.
Dependencies resolved.
==============================================================================================================================================================================================
Package Arch Version Repository Size
==============================================================================================================================================================================================
Installing:
gcc-c++ x86_64 6.2.1-2.fc24 updates 11 M
libstdc++-devel x86_64 6.2.1-2.fc24 updates 1.8 M
libtool x86_64 2.4.6-12.fc24 updates 707 k
rh-eclipse46-eclipse-cdt x86_64 1:9.1.0-1.2.el7 rh-eclipse46-build 43 M
rh-eclipse46-eclipse-launchbar noarch 1:2.0.1-1.1.el7 rh-eclipse46-build 239 k
rh-eclipse46-eclipse-remote noarch 2.1.1-1.1.el7 rh-eclipse46-build 1.0 M
rh-eclipse46-eclipse-tm-terminal-connectors noarch 4.1.0-3.1.el7 rh-eclipse46-build 89 k
rh-eclipse46-freemarker noarch 2.3.23-2.2.el7 rh-eclipse46-build 952 k
Transaction Summary
==============================================================================================================================================================================================
Install 8 Packages
{code}
> missing require-bundles in rpm install
> --------------------------------------
>
> Key: JBDS-4134
> URL: https://issues.jboss.org/browse/JBDS-4134
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Sub-task
> Components: build, rpm
> Affects Versions: 10.2.0.AM2
> Reporter: Nick Boldt
> Fix For: 10.2.0.AM3
>
> Attachments: rh-eclipse46-devstudio10.2.log.20161022-1233.grepped.txt, rh-eclipse46-devstudio10.2.log.20161022-1233.txt, unresolved-requirements.txt
>
>
> Digested from the log attached to JBDS-3141, here's a list of all the missing require-bundles as reported by Eclipse on startup of the rh-eclipse46-devstudio install. See attached.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBDS-4134) missing require-bundles in rpm install
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4134?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-4134 at 10/24/16 11:36 AM:
-------------------------------------------------------------
Alternatively, we could make the devstudio rpm depend on eclipse-tm-terminal-connectors, which will also install eclipse-cdt, eclipse-rse, eclipse-launchbar, eclipse-remote. This might allow us to remove more org.eclipse.* stuff from the devstudio RPM as it's available from upstream rpms.
{code}
dnf whatprovides */org.eclipse.tm.terminal.connector.local*
* rh-eclipse46-eclipse-tm-terminal-connectors
* eclipse-tm-terminal-connectors
* eclipse-tm-terminal{code}
and
{code}
#➔ yum install rh-eclipse46-eclipse-tm-terminal-connectors
Redirecting to '/usr/bin/dnf install rh-eclipse46-eclipse-tm-terminal-connectors' (see 'man yum2dnf')
Last metadata expiration check: 0:37:53 ago on Mon Oct 24 10:57:44 2016.
Dependencies resolved.
==============================================================================================================================================================================================
Package Arch Version Repository Size
==============================================================================================================================================================================================
Installing:
gcc-c++ x86_64 6.2.1-2.fc24 updates 11 M
libstdc++-devel x86_64 6.2.1-2.fc24 updates 1.8 M
libtool x86_64 2.4.6-12.fc24 updates 707 k
rh-eclipse46-eclipse-cdt x86_64 1:9.1.0-1.2.el7 rh-eclipse46-build 43 M
rh-eclipse46-eclipse-launchbar noarch 1:2.0.1-1.1.el7 rh-eclipse46-build 239 k
rh-eclipse46-eclipse-remote noarch 2.1.1-1.1.el7 rh-eclipse46-build 1.0 M
rh-eclipse46-eclipse-tm-terminal-connectors noarch 4.1.0-3.1.el7 rh-eclipse46-build 89 k
rh-eclipse46-freemarker noarch 2.3.23-2.2.el7 rh-eclipse46-build 952 k
Transaction Summary
==============================================================================================================================================================================================
Install 8 Packages
{code}
was (Author: nickboldt):
Alternatively, we could make the devstudio rpm depend on eclipse-tm-terminal-connectors, which will also install eclipse-cdt, eclipse-rse, eclipse-launchbar, eclipse-remote. This might allow us to remove more org.eclipse.* stuff from the devstudio RPM as it's available from upstream rpms.
> missing require-bundles in rpm install
> --------------------------------------
>
> Key: JBDS-4134
> URL: https://issues.jboss.org/browse/JBDS-4134
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Sub-task
> Components: build, rpm
> Affects Versions: 10.2.0.AM2
> Reporter: Nick Boldt
> Fix For: 10.2.0.AM3
>
> Attachments: rh-eclipse46-devstudio10.2.log.20161022-1233.grepped.txt, rh-eclipse46-devstudio10.2.log.20161022-1233.txt, unresolved-requirements.txt
>
>
> Digested from the log attached to JBDS-3141, here's a list of all the missing require-bundles as reported by Eclipse on startup of the rh-eclipse46-devstudio install. See attached.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months