[JBoss JIRA] (JBIDE-18306) The obsoleted cartridges are still shown
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18306?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-18306:
-------------------------------------
Steps to Reproduce:
# EXEC: Open OpenShift New Application Wizard: File -> New -> Other... -> OpenShift Application
# EXEC: Provide your access credentials
# EXEC: Check the cartridge list for *zend-5.6*
Result:
You can still see the obsolete cartridge *zend-5.6* (standalone-, web-cartridge)
!application-wizard-obsolete-cartridge.png!
# ASSERT: make sure that you have an application running on OpenShift
# EXEC: in OpenShift Explorer: pick "Edit Embeddable Cartridges..." from the context menu of your application
# ASSERT: the wizard to edit the embedded cartridges shows up and lists the available cartridges
# EXEC: check the list of available cartridges
Result:
You can still see the obsolete cartridge *metrics-0.1*
!edit-embedded-cartridges.png!
ps. it's especially important to verify that the tooling still works fine if it doesnt show the obsolete standalone- and embedded cartridges (application- and embedded cartridges wizards). To achieve this have a devenv, ssh to it (you need root access) and do the following:
# in ssh: edit /usr/libexec/openshift/cartridges/metrics/metadata/manifest.yml -> Obsolete: false
service ruby193-mcollective restart
oo-broker
oo-admin-ctl-cartridge -c import-node --activate --obsolete
# EXEC: in Eclipse: create an application using the mock standalone cartridge and embed the metrics cartridge to it
# ASSERT: the application is created and shows up in the Explorer
# EXEC: in ssh: edit /usr/libexec/openshift/cartridges/metrics/metadata/manifest.yml -> Obsolete: true
service ruby193-mcollective restart
oo-broker
oo-admin-ctl-cartridge -c import-node --activate --obsolete
# EXEC: in ssh: edit /usr/libexec/openshift/cartridges/mock/metadata/manifest.yml -> Obsolete: true
service ruby193-mcollective restart
oo-broker
oo-admin-ctl-cartridge -c import-node --activate --obsolete
# EXEC: restart Eclipse (Eclipse caches the lists of available cartridges)
# EXEC: in Eclipse: the application still shows up in Explorer but:
** *mock* cartridge wont show up in the "Basic Cartridges" in application wizard (File->New->OpenShift->New Application)
** *metrics* cartridge wont show up in the embed cartridges wizard (Explorer: Edit Embedded Cartridges)
and:
** you can still import the *mock*-cartridge (we obsoleted it in the steps above) application to your workspace
** you still have the *metrics* cartridge listed in the embedded cartridges
was:
# EXEC: Open OpenShift New Application Wizard: File -> New -> Other... -> OpenShift Application
# EXEC: Provide your access credentials
# EXEC: Check the cartridge list for *zend-5.6*
Result:
You can still see the obsolete cartridge *zend-5.6* (standalone-, web-cartridge)
!application-wizard-obsolete-cartridge.png!
# ASSERT: make sure that you have an application running on OpenShift
# EXEC: in OpenShift Explorer: pick "Edit Embeddable Cartridges..." from the context menu of your application
# ASSERT: the wizard to edit the embedded cartridges shows up and lists the available cartridges
# EXEC: check the list of available cartridges
Result:
You can still see the obsolete cartridge *metrics-0.1*
!edit-embedded-cartridges.png!
ps. it's especially important to verify that the tooling still works fine if it doesnt show the obsolete standalone- and embedded cartridges (application- and embedded cartridges wizards). To achieve this have a devenv, ssh to it and do the following:
# in ssh: edit /usr/libexec/openshift/cartridges/metrics/metadata/manifest.yml -> Obsolete: false
service ruby193-mcollective restart
oo-broker
oo-admin-ctl-cartridge -c import-node --activate --obsolete
# EXEC: in Eclipse: create an application using the mock standalone cartridge and embed the metrics cartridge to it
# ASSERT: the application is created and shows up in the Explorer
# EXEC: in ssh: edit /usr/libexec/openshift/cartridges/metrics/metadata/manifest.yml -> Obsolete: true
service ruby193-mcollective restart
oo-broker
oo-admin-ctl-cartridge -c import-node --activate --obsolete
# EXEC: in ssh: edit /usr/libexec/openshift/cartridges/mock/metadata/manifest.yml -> Obsolete: true
service ruby193-mcollective restart
oo-broker
oo-admin-ctl-cartridge -c import-node --activate --obsolete
# EXEC: restart Eclipse (Eclipse caches the lists of available cartridges)
# EXEC: in Eclipse: the application still shows up in Explorer but:
** *mock* cartridge wont show up in the "Basic Cartridges" in application wizard (File->New->OpenShift->New Application)
** *metrics* cartridge wont show up in the embed cartridges wizard (Explorer: Edit Embedded Cartridges)
and:
** you can still import the *mock*-cartridge (we obsoleted it in the steps above) application to your workspace
** you still have the *metrics* cartridge listed in the embedded cartridges
> The obsoleted cartridges are still shown
> ----------------------------------------
>
> Key: JBIDE-18306
> URL: https://issues.jboss.org/browse/JBIDE-18306
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.2.Final
> Reporter: Chunyun Chen
> Assignee: Andre Dietisheim
> Priority: Critical
> Fix For: 4.2.0.CR2
>
> Attachments: application-wizard-obsolete-cartridge.png, edit-embedded-cartridges.png, error-create-obsolete-cartridge.png
>
>
> The obsoleted cartridges are still shown in the cartridge list, like obsoleted cartridge zend-5.6, nodejs-0.6 and metrics-0.1, they should not be shown any more in the list.
> the issue may due to java-client not using the latest 1.7 version restapi.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18368) An internal error occurred during: "Computing connector status".
by Jiri Peterka (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18368?page=com.atlassian.jira.plugi... ]
Jiri Peterka commented on JBIDE-18368:
--------------------------------------
Yes, just this NPE was thrown, everything else looked quite normal.
> An internal error occurred during: "Computing connector status".
> ----------------------------------------------------------------
>
> Key: JBIDE-18368
> URL: https://issues.jboss.org/browse/JBIDE-18368
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.2.0.CR1
> Environment: JBDS 8.0.0.CR1b, F20_64
> Reporter: Jiri Peterka
> Assignee: Mickael Istria
> Fix For: 4.2.0.CR2
>
>
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi.resolveProfileUnits(ConnectorDescriptorItemUi.java:393)
> at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi.access$6(ConnectorDescriptorItemUi.java:390)
> at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi$6.run(ConnectorDescriptorItemUi.java:311)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18434) Remove discovery "unified" target
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18434?page=com.atlassian.jira.plugi... ]
Mickael Istria reassigned JBIDE-18434:
--------------------------------------
Assignee: Mickael Istria
> Remove discovery "unified" target
> ---------------------------------
>
> Key: JBIDE-18434
> URL: https://issues.jboss.org/browse/JBIDE-18434
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: discovery
> Affects Versions: 4.2.0.CR1
> Reporter: Mickael Istria
> Assignee: Mickael Istria
>
> Currently, the unified targets for discovery are not used in order to build any plugin. Only the "multiple" ones are used in order to generate the necessary p2 repo, and the validation they're running is enough to guarantee that content on discovery files can install (if composited with TP).
> So the unified don't provide any value, and even worse, the way they're validated can produce errors whereas it should work, I suggest we just delete them.
> [~nickboldt] WDYT? Do you see any utility to those unified targets?
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18368) An internal error occurred during: "Computing connector status".
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18368?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-18368:
----------------------------------------
Yes, I think it can be a timing issue. By details, I'm interested to know what is happening/has happened when you restard. For example, is the catalog still loading or fully loaded?
> An internal error occurred during: "Computing connector status".
> ----------------------------------------------------------------
>
> Key: JBIDE-18368
> URL: https://issues.jboss.org/browse/JBIDE-18368
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.2.0.CR1
> Environment: JBDS 8.0.0.CR1b, F20_64
> Reporter: Jiri Peterka
> Assignee: Mickael Istria
> Fix For: 4.2.0.CR2
>
>
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi.resolveProfileUnits(ConnectorDescriptorItemUi.java:393)
> at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi.access$6(ConnectorDescriptorItemUi.java:390)
> at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi$6.run(ConnectorDescriptorItemUi.java:311)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18368) An internal error occurred during: "Computing connector status".
by Jiri Peterka (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18368?page=com.atlassian.jira.plugi... ]
Jiri Peterka commented on JBIDE-18368:
--------------------------------------
[~fbricon] ID means IDE, sorry for typo, fixed. Mickael, what do you mean by more details, steps should be quite clear. Problem is that reproducibility might be an issue base on specific timing.
> An internal error occurred during: "Computing connector status".
> ----------------------------------------------------------------
>
> Key: JBIDE-18368
> URL: https://issues.jboss.org/browse/JBIDE-18368
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.2.0.CR1
> Environment: JBDS 8.0.0.CR1b, F20_64
> Reporter: Jiri Peterka
> Assignee: Mickael Istria
> Fix For: 4.2.0.CR2
>
>
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi.resolveProfileUnits(ConnectorDescriptorItemUi.java:393)
> at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi.access$6(ConnectorDescriptorItemUi.java:390)
> at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi$6.run(ConnectorDescriptorItemUi.java:311)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18368) An internal error occurred during: "Computing connector status".
by Jiri Peterka (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18368?page=com.atlassian.jira.plugi... ]
Jiri Peterka updated JBIDE-18368:
---------------------------------
Steps to Reproduce:
STEP: Install JBDS 8.0.0.CR1
STEP: Open JBoss Central software/update tab
STEP: Restart IDE
STEP: Check Error Log
ASSERT: No errors expected
was:
STEP: Install JBDS 8.0.0.CR1
STEP: Open JBoss Central software/update tab
STEP: Restart ID
STEP: Check Error Log
ASSERT: No errors expected
> An internal error occurred during: "Computing connector status".
> ----------------------------------------------------------------
>
> Key: JBIDE-18368
> URL: https://issues.jboss.org/browse/JBIDE-18368
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.2.0.CR1
> Environment: JBDS 8.0.0.CR1b, F20_64
> Reporter: Jiri Peterka
> Assignee: Mickael Istria
> Fix For: 4.2.0.CR2
>
>
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi.resolveProfileUnits(ConnectorDescriptorItemUi.java:393)
> at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi.access$6(ConnectorDescriptorItemUi.java:390)
> at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi$6.run(ConnectorDescriptorItemUi.java:311)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBDS-3165) JBDS crashes when editor is opened on RHEL 6
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBDS-3165?page=com.atlassian.jira.plugin.... ]
Mickael Istria updated JBDS-3165:
---------------------------------
Assignee: Rastislav Wagner
> JBDS crashes when editor is opened on RHEL 6
> --------------------------------------------
>
> Key: JBDS-3165
> URL: https://issues.jboss.org/browse/JBDS-3165
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: target-platform, upstream
> Environment: RHEL 6.6 Beta
> JBDS 8.0.0.Beta3 (also happening for JBDS 7 and 6)
> Reporter: Rastislav Wagner
> Assignee: Rastislav Wagner
> Priority: Blocker
> Fix For: 8.0.0.CR2
>
>
> JBDS is crashing when I try to open any file in editor or start EAP server (when console is trying to show output).
> The only thing I can see is in terminal
> {code}
> java: cairo-misc.c:380: _cairo_operator_bounded_by_source: Assertion 'NOT_REACHED' failed.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBDS-3165) JBDS crashes when editor is opened on RHEL 6
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBDS-3165?page=com.atlassian.jira.plugin.... ]
Mickael Istria commented on JBDS-3165:
--------------------------------------
With recent update, JBDS nightly from http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_8.... now includes org.eclipse.swt.gtk.linux.x86_64_3.103.1.v20140903-1947.jar , which AFAIK from [~akurtakov]'s comment should have this fixes.
[~rawagner] Can you please give a try to the nightly and check whether updating to Luna SR1 was enough to fix that?
> JBDS crashes when editor is opened on RHEL 6
> --------------------------------------------
>
> Key: JBDS-3165
> URL: https://issues.jboss.org/browse/JBDS-3165
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: target-platform, upstream
> Environment: RHEL 6.6 Beta
> JBDS 8.0.0.Beta3 (also happening for JBDS 7 and 6)
> Reporter: Rastislav Wagner
> Priority: Blocker
> Fix For: 8.0.0.CR2
>
>
> JBDS is crashing when I try to open any file in editor or start EAP server (when console is trying to show output).
> The only thing I can see is in terminal
> {code}
> java: cairo-misc.c:380: _cairo_operator_bounded_by_source: Assertion 'NOT_REACHED' failed.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18435) Validation errors in WildFly quickstarts
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18435?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-18435:
----------------------------------
Description:
when importing Wildfly quickstarts from https://github.com/wildfly/quickstart ({{master}} branch), there are some XML files on which some errors are reported by our tooling:
- {{ejb-multi-server/app-one/ejb/src/main/resources/META-INF/jboss-ejb3.xml}}
- {{ejb-multi-server/app-main/web/src/main/webapp/WEB-INF/faces-config.xml}}
- {{cdi-alternative/src/main/webapp/WEB-INF/beans.xml}}
- {{wsat-simple/src/main/webapp/WEB-INF/classes/context-handlers.xml}}
Also, a project had a bad packaging type: jts/application-component-2/pom.xml b/jts/application-component-2/pom.xml ({{jar}} instead of {{ejb}})
was:
when importing Wildfly quickstarts, there are some XML files on which some errors are reported by our tooling:
- {{ejb-multi-server/app-one/ejb/src/main/resources/META-INF/jboss-ejb3.xml}}
- {{ejb-multi-server/app-main/web/src/main/webapp/WEB-INF/faces-config.xml}}
- {{cdi-alternative/src/main/webapp/WEB-INF/beans.xml}}
- {{wsat-simple/src/main/webapp/WEB-INF/classes/context-handlers.xml}}
Also, a project had a bad packaging type: jts/application-component-2/pom.xml b/jts/application-component-2/pom.xml ({{jar}} instead of {{ejb}})
> Validation errors in WildFly quickstarts
> ----------------------------------------
>
> Key: JBIDE-18435
> URL: https://issues.jboss.org/browse/JBIDE-18435
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 4.2.0.CR1
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 4.2.0.CR2
>
>
> when importing Wildfly quickstarts from https://github.com/wildfly/quickstart ({{master}} branch), there are some XML files on which some errors are reported by our tooling:
> - {{ejb-multi-server/app-one/ejb/src/main/resources/META-INF/jboss-ejb3.xml}}
> - {{ejb-multi-server/app-main/web/src/main/webapp/WEB-INF/faces-config.xml}}
> - {{cdi-alternative/src/main/webapp/WEB-INF/beans.xml}}
> - {{wsat-simple/src/main/webapp/WEB-INF/classes/context-handlers.xml}}
> Also, a project had a bad packaging type: jts/application-component-2/pom.xml b/jts/application-component-2/pom.xml ({{jar}} instead of {{ejb}})
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months