[JBoss JIRA] (JBDS-4183) Installing from an update site into rpm install causes duplicate IUs to be installed - use constraint violations ensue
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4183?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4183:
-----------------------------
Description:
Steps to repro:
1. install from latest rpm, eg., 10.2.0.20161116.1342.el7
2. open Central > Software/Update, scroll down until you find the *Maven Integration for Eclipse JDT APT (m2e-apt)* connector
3. Install it. When prompted to restart, shut down Eclipse and check in your ~/.eclipse folder:
{code}
$➔ ll ~/.eclipse/org.eclipse.platform_*_linux_gtk_x86_64/plugins/
total 36K
-rw-rw-r-- 1 nboldt nboldt 34K Nov 16 10:54 org.slf4j.api_1.7.2.v20121108-1250.jar
{code}
But this plugin is already installed here:
{code}/opt/rh/rh-java-common/root/usr/share/java/slf4j/slf4j-api.jar
/opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/egit-mylyn/eclipse/plugins/slf4j.api_1.7.4.jar{code}
So even though the connector install doesn't install any new m2e-apt stuff (it's already installed too):
{code}
/opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.jboss.tools.maven.apt.ui_1.3.0.201610261805.jar
/opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.jboss.tools.maven.apt.core_1.3.0.201610261805.jar
/opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/features/org.jboss.tools.maven.apt.feature_1.3.0.201610261805
{code}
... the result of this install is to cause use constrain violations and break the devstudio install.
was:
Steps to repro:
1. install from latest rpm, eg., 10.2.0.20161116.1342.el7
2. open Central > Software/Update, scroll down until you find the *Maven Integration for Eclipse JDT APT (m2e-apt)* connector
3. Install it. When prompted to restart, shut down Eclipse and check in your ~/.eclipse folder:
{code}
$➔ ll ~/.eclipse/org.eclipse.platform_*_linux_gtk_x86_64/plugins/
total 36K
-rw-rw-r-- 1 nboldt nboldt 34K Nov 16 10:54 org.slf4j.api_1.7.2.v20121108-1250.jar
{code}
But this plugin is already installed here:
{code}/opt/rh/rh-java-common/root/usr/share/java/slf4j/slf4j-api.jar{code}
So even though the connector install doesn't install any new m2e-apt stuff (it's already installed too):
{code}
./rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.jboss.tools.maven.apt.ui_1.3.0.201610261805.jar
./rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.jboss.tools.maven.apt.core_1.3.0.201610261805.jar
./rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/features/org.jboss.tools.maven.apt.feature_1.3.0.201610261805
{code}
... the result of this install is to cause use constrain violations and break the devstudio install.
> Installing from an update site into rpm install causes duplicate IUs to be installed - use constraint violations ensue
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4183
> URL: https://issues.jboss.org/browse/JBDS-4183
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: rpm
> Affects Versions: 10.2.0.AM3
> Reporter: Nick Boldt
> Priority: Blocker
>
> Steps to repro:
> 1. install from latest rpm, eg., 10.2.0.20161116.1342.el7
> 2. open Central > Software/Update, scroll down until you find the *Maven Integration for Eclipse JDT APT (m2e-apt)* connector
> 3. Install it. When prompted to restart, shut down Eclipse and check in your ~/.eclipse folder:
> {code}
> $➔ ll ~/.eclipse/org.eclipse.platform_*_linux_gtk_x86_64/plugins/
> total 36K
> -rw-rw-r-- 1 nboldt nboldt 34K Nov 16 10:54 org.slf4j.api_1.7.2.v20121108-1250.jar
> {code}
> But this plugin is already installed here:
> {code}/opt/rh/rh-java-common/root/usr/share/java/slf4j/slf4j-api.jar
> /opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/egit-mylyn/eclipse/plugins/slf4j.api_1.7.4.jar{code}
> So even though the connector install doesn't install any new m2e-apt stuff (it's already installed too):
> {code}
> /opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.jboss.tools.maven.apt.ui_1.3.0.201610261805.jar
> /opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.jboss.tools.maven.apt.core_1.3.0.201610261805.jar
> /opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/features/org.jboss.tools.maven.apt.feature_1.3.0.201610261805
> {code}
> ... the result of this install is to cause use constrain violations and break the devstudio install.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4183) Installing from an update site into rpm install causes duplicate IUs to be installed - use constraint violations ensue
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4183?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4183:
-----------------------------
Priority: Blocker (was: Major)
> Installing from an update site into rpm install causes duplicate IUs to be installed - use constraint violations ensue
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4183
> URL: https://issues.jboss.org/browse/JBDS-4183
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: rpm
> Affects Versions: 10.2.0.AM3
> Reporter: Nick Boldt
> Priority: Blocker
>
> Steps to repro:
> 1. install from latest rpm, eg., 10.2.0.20161116.1342.el7
> 2. open Central > Software/Update, scroll down until you find the *Maven Integration for Eclipse JDT APT (m2e-apt)* connector
> 3. Install it. When prompted to restart, shut down Eclipse and check in your ~/.eclipse folder:
> {code}
> $➔ ll ~/.eclipse/org.eclipse.platform_*_linux_gtk_x86_64/plugins/
> total 36K
> -rw-rw-r-- 1 nboldt nboldt 34K Nov 16 10:54 org.slf4j.api_1.7.2.v20121108-1250.jar
> {code}
> But this plugin is already installed here:
> {code}/opt/rh/rh-java-common/root/usr/share/java/slf4j/slf4j-api.jar{code}
> So even though the connector install doesn't install any new m2e-apt stuff (it's already installed too):
> {code}
> ./rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.jboss.tools.maven.apt.ui_1.3.0.201610261805.jar
> ./rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.jboss.tools.maven.apt.core_1.3.0.201610261805.jar
> ./rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/features/org.jboss.tools.maven.apt.feature_1.3.0.201610261805
> {code}
> ... the result of this install is to cause use constrain violations and break the devstudio install.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4183) Installing from an update site into rpm install causes duplicate IUs to be installed - use constraint violations ensue
by Nick Boldt (JIRA)
Nick Boldt created JBDS-4183:
--------------------------------
Summary: Installing from an update site into rpm install causes duplicate IUs to be installed - use constraint violations ensue
Key: JBDS-4183
URL: https://issues.jboss.org/browse/JBDS-4183
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Bug
Components: rpm
Affects Versions: 10.2.0.AM3
Reporter: Nick Boldt
Steps to repro:
1. install from latest rpm, eg., 10.2.0.20161116.1342.el7
2. open Central > Software/Update, scroll down until you find the *Maven Integration for Eclipse JDT APT (m2e-apt)* connector
3. Install it. When prompted to restart, shut down Eclipse and check in your ~/.eclipse folder:
{code}
$➔ ll ~/.eclipse/org.eclipse.platform_*_linux_gtk_x86_64/plugins/
total 36K
-rw-rw-r-- 1 nboldt nboldt 34K Nov 16 10:54 org.slf4j.api_1.7.2.v20121108-1250.jar
{code}
But this plugin is already installed here:
{code}/opt/rh/rh-java-common/root/usr/share/java/slf4j/slf4j-api.jar{code}
So even though the connector install doesn't install any new m2e-apt stuff (it's already installed too):
{code}
./rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.jboss.tools.maven.apt.ui_1.3.0.201610261805.jar
./rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.jboss.tools.maven.apt.core_1.3.0.201610261805.jar
./rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/features/org.jboss.tools.maven.apt.feature_1.3.0.201610261805
{code}
... the result of this install is to cause use constrain violations and break the devstudio install.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23136) Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23136?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov commented on JBIDE-23136:
------------------------------------------
[~mlabuda] [~jeffmaury] it's strange but seems to be an intended behavior. See comments in PushImageToRegistryJob here: https://github.com/jbosstools/jbosstools-openshift/blob/master/plugins/or... :
{quote}
// first, we need to tag the image with the OpenShift target project
...
// then we can push that image with the new name
...
*// we need to untag the image, even if the push operation failed*
{quote}
It's made in [this PR|https://github.com/jbosstools/jbosstools-openshift/pull/1201] by [~xcoulon]. [~xcoulon], may i ask you to glance at this jira, please ? Is it really an issue or was made intentionally?
> Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-23136
> URL: https://issues.jboss.org/browse/JBIDE-23136
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.Final
> Reporter: Marián Labuda
> Assignee: Dmitrii Bocharov
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.4.x
>
> Attachments: eap64-basic-s2i-new-app-from-cli-1.png, eap64-basic-s2i-new-app-from-jbosstools-1.png, local-docker-images-after-pull-1.png
>
>
> I have a docker connection to local docker daemon and a CDK docker connection. I am pushing an image from a docker connection to CDK registry via Deploy Image to OpenShift wizard. Push of an image pass, but it results into an image with no tag, see:
> 172.30.192.49:5000/msa/msa <none> 238200ae067d 4 months ago 1.05 GB
> Such images are not shown in docker explorer under a docker connection because of upstream bug ERT-411
> Steps to reproduce:
> - have a project with a file named {{Dockerfile}} with the following content (1 line):
> {code}
> FROM fedora:latest
> {code}
> - Select the file in the project explorer, then {{Run As > Docker Image Build}}. Use the CDK connection and give it a name (eg: {{username/fedora}})
> - Select the image in the Docker Explorer view, then {{Deploy to OpenShift}}.
> - In the wizard, select the option to push the image to the registry (add a dummy port if needed)
> - once the operation completed, there's an unexpected image named like {{172.30.164.33:5000/<project>/fedora}} in the output of the {{docker images}} command (in CLI)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4179) DevStudio installer uses console installation instead of wizard
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4179?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-4179:
-------------------------------------
Nope, but the reason behind it is JDK GraphicsEnvironment.isHeadless() returning true and that is why IzPack decides it has no UI and switch to console mode.
> DevStudio installer uses console installation instead of wizard
> ---------------------------------------------------------------
>
> Key: JBDS-4179
> URL: https://issues.jboss.org/browse/JBDS-4179
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 10.2.0.GA
> Environment: openjdk version "1.8.0_102"
> OpenJDK Runtime Environment (build 1.8.0_102-b14)
> Reporter: Marián Labuda
> Assignee: Denis Golovin
>
> I tried to install latest DevStudio (devstudio-10.2.0.GA-v20161116-0039-B6472-installer-standalone.jar) but when I run installation as usual, I get console installation - at first whole license text and prompt to 1) Accept, 2) Reject, 3) Redisplay. After that installation unpack files to home and I am not able to select destination.
> This happens with older version of openjdk8. With latest available openjdk for fedora (1.8.0_111) it works.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBTIS-948) Runtime is not detected if the Devstudio was installed using the InstallConfigRecord.xml
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-948?page=com.atlassian.jira.plugin.... ]
Paul Leacu commented on JBTIS-948:
----------------------------------
[~rob.stryker] [~akazakov] - wdyt?
If I do a UI install with the existing devstudio installer it will add ~/devstudio/runtimes to the runtimes detection preferences *but* if I do an automatic non-UI shell based install it won't. The problem is that I'm counting on the autodetection of the Fuse Karaf runtime server that the installer puts into the runtime folder. The workaround would be for the user to manually edit their JBoss Runtime Detection preferences to add ~/devstudio/runtimes.
Leaving Denis off this since he's trying to complete his Mac work.
> 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.CR1
> Environment: devstudio-integration-stack-rt-10.0.0.CR1-standalone-installer.jar
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
> Attachments: ds-10.2-pref-cmd-install.png, ds-10.2-pref-gui-install.png
>
>
> 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
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23421) Terminating Server Adapter running in debug mode does not terminate Node.js debug session
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23421?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-23421:
------------------------------------------
tested it, works for me, +1
Thanks!
merged into master.
> Terminating Server Adapter running in debug mode does not terminate Node.js debug session
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-23421
> URL: https://issues.jboss.org/browse/JBIDE-23421
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: javascript, openshift
> Affects Versions: 4.4.2.AM2
> Reporter: Ilya Buziuk
> Assignee: Ilya Buziuk
> Labels: nodejs, openshift_v3, server_adapter
> Fix For: 4.4.2.Final
>
>
> Stopping server adapter will not stop the V8 debug session - one should still terminate it manually. This might be coupled with the replication controller issue - https://issues.jboss.org/browse/JBIDE-23412 due to the fact that after stopping server adapter app is still running in the DEV_MODE (which is unexpected behaviour IMO) and debug session is still alive. Moreover, If you try to restart the adapter the debug session will be terminated (expected behaviour), so it might be just a side effect of other issue
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4175) NPE/broken functionality/cannot start after install from Red Hat Central into rh-eclipse46-devstudio
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBDS-4175?page=com.atlassian.jira.plugin.... ]
Mickael Istria commented on JBDS-4175:
--------------------------------------
[~vkadlcik] Please clarify when you do get the error. Does the error show up when trying to install content, or restart after install, or when trying to use the plugins?
Comment form [~akazakov] on https://issues.jboss.org/browse/JBDS-4175?focusedCommentId=13321330&page=... seems correct.
It would be interesting to try an installation with regular p2, using directly some p2 site for, let's say, Spring IDE and install them with the regular p2 wizard, or even with the p2 headless director. I don't think Central itself is to blame here.
> NPE/broken functionality/cannot start after install from Red Hat Central into rh-eclipse46-devstudio
> ----------------------------------------------------------------------------------------------------
>
> Key: JBDS-4175
> URL: https://issues.jboss.org/browse/JBDS-4175
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: central-update, rpm
> Environment: RHEL 7.2 with RHSCL repositories available:
> * RHSCL 2.3 RC (http://download-node-02.eng.bos.redhat.com/rel-eng/RHSCL-2.3-RHEL-7-RC-1....)
> * update for RHBZ#1392095 (http://nest.test.redhat.com/mnt/qa/scratch/vkadlcik/eclipse/repos/rhscl23...)
> Reporter: Václav Kadlčík
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 10.2.0.GA
>
> Attachments: JBDS-4175_logs_first_half.tar.gz, rh-eclipse46-devstudio10.2.log.20161115-0953.txt, spring-ide-fail-aop.png, spring-ide-fail-list.png, spring-ide-fail-npe.png, spring-ide-fail-project-explorer-broken-package-explorer-OK.png, spring-ide-fail.png, spring-ide-view-fail.png, sw_to_install.txt, workspace.log, wst.xsd.core_diff.png
>
>
> I installed rh-eclipse46-devstudio-10.2-0.20161111.0219.el7.x86_64.rpm and followed Nick's scenario [1]. In Red Hat Central, I clicked "Select All" (it found 36 items), then "Install/Update", did all the confirmations, including a restart. After the restart, Eclipse died on java.lang.NullPointerException. I'm attaching the workspace log (aside from the NPE, it's full of "Could not resolve module").
> I reproduced the problem several times on two different machines. The update for RHBZ#1392095 (rh-eclipse46-eclipse-4.6.1-2.4.el7) isn't necessary, it just makes the reproduction much faster.
> Not sure how related it is, but rh-eclipse46 disallows updating packages installed from RPM [2]. But in the list of software to be installed/updated, I saw, among others, EGit and Mylyn, which are definitely included in rh-eclipse46-base. In any case, I'm attaching the list, too.
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1392095#c6
> [2] https://bugzilla.redhat.com/show_bug.cgi?id=1173024
> (copied from comment below to make it sticky)
> Results of installing first half of the items in Central:
> ||Item||Result||Description or Errors||
> |Android_Development_Tools|(/)||
> |JBoss_Hybrid_Mobile_Tools|(/)||
> |AngularJS_for_Web_Tools|(x)|IllegalStateException: BundleContext, NullPointerException|
> |JBoss_Arquillian_Tools|(/)||
> |JBoss_Forge_Tools|(/)||
> |JBoss_OpenShift_2_Tools|(x)|BundleException|
> |JBoss_OpenShift_3_Tools|(x)|BundleException|
> |JBoss_Portlet_Tools|(x)|BundleException, NullPointerException, eclipse didn't start|
> |JBoss_Seam_Tools|(x)|BundleException, NullPointerException, eclipse didn't start|
> |JBoss_Tools_LiveReload|(x)|BundleException|
> |JST_Server|(x)|BundleException|
> |Spring_IDE|(x)|BundleException, NullPointerException, eclipse didn't start|
> |Atlassian_Connector|(x)|BundleException, loader constraint violation|
> |Eclipse_EGit_Mylyn_Support|(x)|BundleException|
> |Subclipse_SVNKit|(/)|First attempt failed due to SocketTimeoutException but second passed|
> |Subclipse_SVNKit_Mylyn_Support|(x)|BundleException|
> |Eclipse_Checkstyle|(x)|NullPointerException|
> All logs [^JBDS-4175_logs_first_half.tar.gz].
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months