[JBoss JIRA] (JBIDE-19542) Installing "JBoss Tools Common - Mylyn" from JBoss Tools result in errors being logged until "Mylyn Issue Tracker Connectors" is installed from Central
by Len DiMaggio (JIRA)
Len DiMaggio created JBIDE-19542:
------------------------------------
Summary: Installing "JBoss Tools Common - Mylyn" from JBoss Tools result in errors being logged until "Mylyn Issue Tracker Connectors" is installed from Central
Key: JBIDE-19542
URL: https://issues.jboss.org/browse/JBIDE-19542
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: central
Affects Versions: 4.2.3.Final
Reporter: Len DiMaggio
Steps to recreate the error:
* Install Eclipse (eclipse-jee-luna-SR2-linux-gtk-x86_64.tar.gz)
* Configure JBoss Tools as an update site (http://download.jboss.org/jbosstools/updates/staging/luna/)
* Install JBoss Tools Common - Mylyn (3.6.2.Final-v20150325-0456-B99, org.jboss.tools.common.mylyn.feature.feature.group)
* Whenever eclipse is started, this error is written to the .log
============================================================================
cat .log
!SESSION 2015-03-31 14:33:50.481 -----------------------------------------------
eclipse.buildId=4.4.2.M20150204-1700
java.version=1.7.0_55
java.vendor=Oracle Corporation
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Framework arguments: -product org.eclipse.epp.package.jee.product
Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.jee.product
!ENTRY org.eclipse.mylyn.tasks.core 4 0 2015-03-31 14:34:00.231
!MESSAGE Unexpected error while loading repository template extensions
!SUBENTRY 1 org.eclipse.mylyn.tasks.core 4 0 2015-03-31 14:34:00.231
!MESSAGE Could not load repository template extension contributed by 'org.jboss.tools.common.mylyn' with connectorKind 'jira'
============================================================================
Workaround:
* From JBoss Central, install: "Mylyn Issue Tracker Connectors"
* This results in the following packages being installed
* Mylyn Commons 3.14.2.v20150217-2244 org.eclipse.mylyn.commons.feature.group
* Mylyn Context Connector: Eclipse IDE 3.14.2.v20150218-0125 org.eclipse.mylyn.ide_feature.feature.group
* Mylyn Context Connector: Java Development 3.14.2.v20150218-0125 org.eclipse.mylyn.java_feature.feature.group
* Mylyn Context Connector: Plug-in Development 3.14.2.v20150218-0125 org.eclipse.mylyn.pde_feature.feature.group
* Mylyn Context Connector: Team Support 3.14.2.v20150218-0125 org.eclipse.mylyn.team_feature.feature.group
* Mylyn Task List 3.14.2.v20150217-2341 org.eclipse.mylyn_feature.feature.group
* Mylyn Task-Focused Interface 3.14.2.v20150218-0125 org.eclipse.mylyn.context_feature.feature.group
* Mylyn Tasks Connector: Bugzilla 3.14.2.v20150217-2341 org.eclipse.mylyn.bugzilla_feature.feature.group
* Mylyn Versions 1.6.2.v20150217-2249 org.eclipse.mylyn.versions.feature.group
After installing this^, the error is not generated
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 1 month
[JBoss JIRA] (JBIDE-19038) Arquillian should not be in JBT EA catalog
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19038?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-19038:
----------------------------------------
[~rhopp] [~ldimaggio] Can you please report that in a seprated Jira so it's clearer what's working and what's not? (I mean Arquillian Central connector works, but is missing an icon, is that it?). Also, please set a dedicated criticity and target-version for this icon issue. and we'll discuss whether we need/can respin the catalog on the dedicated entry.
> Arquillian should not be in JBT EA catalog
> ------------------------------------------
>
> Key: JBIDE-19038
> URL: https://issues.jboss.org/browse/JBIDE-19038
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: updatesite
> Affects Versions: 4.2.2.Final
> Reporter: Radim Hopp
> Assignee: Nick Boldt
> Fix For: 4.2.3.Final
>
> Attachments: JBDS_810_GA.png
>
>
> In JBIDE-18995 Arquillian was removed from EA (by removing it from jbosstools-earlyaccess.properties), but on Software/Update page it is still displayed under EA features.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 1 month
[JBoss JIRA] (JBIDE-19513) multiple versions of jetty and java.servlet plugins in JBDS 9
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19513?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-19513:
----------------------------------------
Additionally to org.eclipse.jetty.websocket.client, Is there any other bundle you need?
Please list them on JBIDE-19497 directly.
> multiple versions of jetty and java.servlet plugins in JBDS 9
> -------------------------------------------------------------
>
> Key: JBIDE-19513
> URL: https://issues.jboss.org/browse/JBIDE-19513
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, qa, target-platform, updatesite
> Affects Versions: 4.3.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Ilya Buziuk
> Fix For: 4.3.0.Alpha2
>
>
> These plugins versions are included in JBDS 9 with multiple versions. We need to decide if this is acceptable / intentional, or something to fix.
> {code}
> org.eclipse.jetty.http_8.1.14.v20131031 and 9.2.5
> org.eclipse.jetty.servlet_8.1.14.v20131031 and 9.2.5
> org.eclipse.jetty.server_8.1.14.v20131031 and 9.2.5
> org.eclipse.jetty.security_8.1.14.v20131031 and 9.2.5
> org.eclipse.jetty.continuation_8.1.14.v20131031 and 9.2.5
> org.eclipse.jetty.util_8.1.14.v20131031 and 9.2.5
> org.eclipse.jetty.io_8.1.14.v20131031 and 9.2.5
> - and -
> javax.servlet_3.1.0.v201410161800 and 3.0.0{code}
> Pre-existing ignored/known issues:
> {code}
> org.eclipse.jdt.annotation_1.1.100.v20140704-0625
> com.jcraft.jsch_0.1.50.v201403120620
> org.apache.commons.logging_1.0.4.v201101211617
> javax.wsdl_1.5.1.v201012040544 {code}
> See detailed reports here:
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 1 month
[JBoss JIRA] (JBIDE-19038) Arquillian should not be in JBT EA catalog
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19038?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-19038:
----------------------------------------
[~rhopp] Better late than sorry ;) Do you have any idea why the previous fix isn't enough? (see PR)
> Arquillian should not be in JBT EA catalog
> ------------------------------------------
>
> Key: JBIDE-19038
> URL: https://issues.jboss.org/browse/JBIDE-19038
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: updatesite
> Affects Versions: 4.2.2.Final
> Reporter: Radim Hopp
> Assignee: Nick Boldt
> Fix For: 4.2.3.Final
>
> Attachments: JBDS_810_GA.png
>
>
> In JBIDE-18995 Arquillian was removed from EA (by removing it from jbosstools-earlyaccess.properties), but on Software/Update page it is still displayed under EA features.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 1 month
[JBoss JIRA] (JBDS-3391) Installer should not require UI to report errors in automated mode
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3391?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3391:
--------------------------------
Workaround Description:
run installer as
{code}java -DTRACE=true -jar installer-XXXX.jar{code}
to see error messages for p2 director
was:
run installer as
{code}java -DTRACE=true -jar installer-XXXX.jar
> Installer should not require UI to report errors in automated mode
> ------------------------------------------------------------------
>
> Key: JBDS-3391
> URL: https://issues.jboss.org/browse/JBDS-3391
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.0.0.Alpha1
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 9.0.0.Alpha2
>
>
> Currently if installer has problems installing JBDS in headless (automated) mode it tries to show error dialog. It works for normal installation when it is called with GUI available, but if fails if GUI is not available.
> {code}Exception in thread "IzPack - Unpacker thread" java.lang.InternalError: Can't connect to X11 window server using '' as the value of the DISPLAY variable.
> at sun.awt.X11GraphicsEnvironment.initDisplay(Native Method)
> at sun.awt.X11GraphicsEnvironment.access$200(X11GraphicsEnvironment.java:65)
> at sun.awt.X11GraphicsEnvironment$1.run(X11GraphicsEnvironment.java:110)
> at java.security.AccessController.doPrivileged(Native Method)
> at sun.awt.X11GraphicsEnvironment.<clinit>(X11GraphicsEnvironment.java:74)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:191)
> at java.awt.GraphicsEnvironment.createGE(GraphicsEnvironment.java:102)
> at java.awt.GraphicsEnvironment.getLocalGraphicsEnvironment(GraphicsEnvironment.java:81)
> at sun.awt.X11.XToolkit.<clinit>(XToolkit.java:120)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:191)
> at java.awt.Toolkit$2.run(Toolkit.java:869)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.awt.Toolkit.getDefaultToolkit(Toolkit.java:861)
> at javax.swing.ImageIcon.<init>(ImageIcon.java:186)
> at javax.swing.ImageIcon.<init>(ImageIcon.java:205)
> at com.izforge.izpack.installer.ResourceManager.getImageIconResource(Unknown Source)
> at com.izforge.izpack.installer.Unpacker.run(Unpacker.java:614)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> Most resent example is installer headless tests was failing to show installation error and we had to enable tracing to find the reason. Installer should recognize automated mode, print error message to standard error output and return appropriate error code.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 1 month
[JBoss JIRA] (JBDS-3391) Installer should not require UI to report errors in automated mode
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3391?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3391:
--------------------------------
Description:
Currently if installer has problems installing JBDS in headless (automated) mode it tries to show error dialog. It works for normal installation when it is called with GUI available, but if fails if GUI is not available.
{code}Exception in thread "IzPack - Unpacker thread" java.lang.InternalError: Can't connect to X11 window server using '' as the value of the DISPLAY variable.
at sun.awt.X11GraphicsEnvironment.initDisplay(Native Method)
at sun.awt.X11GraphicsEnvironment.access$200(X11GraphicsEnvironment.java:65)
at sun.awt.X11GraphicsEnvironment$1.run(X11GraphicsEnvironment.java:110)
at java.security.AccessController.doPrivileged(Native Method)
at sun.awt.X11GraphicsEnvironment.<clinit>(X11GraphicsEnvironment.java:74)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:191)
at java.awt.GraphicsEnvironment.createGE(GraphicsEnvironment.java:102)
at java.awt.GraphicsEnvironment.getLocalGraphicsEnvironment(GraphicsEnvironment.java:81)
at sun.awt.X11.XToolkit.<clinit>(XToolkit.java:120)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:191)
at java.awt.Toolkit$2.run(Toolkit.java:869)
at java.security.AccessController.doPrivileged(Native Method)
at java.awt.Toolkit.getDefaultToolkit(Toolkit.java:861)
at javax.swing.ImageIcon.<init>(ImageIcon.java:186)
at javax.swing.ImageIcon.<init>(ImageIcon.java:205)
at com.izforge.izpack.installer.ResourceManager.getImageIconResource(Unknown Source)
at com.izforge.izpack.installer.Unpacker.run(Unpacker.java:614)
at java.lang.Thread.run(Thread.java:745)
{code}
Most resent example is installer headless tests was failing to show installation error and we had to enable tracing to find the reason. Installer should recognize automated mode, print error message to standard error output and return appropriate error code.
was:Currently if installer has problems installing JBDS in headless (automated) mode it tries to show error dialog. It works for normal installation when it is called with GUI available, but if fails if GUI is not available. Most resent example is installer headless tests was failing to show installation error and we had to enable tracing to find the reason. Installer should recognize automated mode, print error message to standard error output and return appropriate error code.
Steps to Reproduce:
1. Remove plugins folder form installer jar so installation would fail.
2. Run installer without UI like:
{code}DISPLAY="" java -jar installer-XXXX.jar{code}
3. ASSSERT: It shows errors about missing artifacts to standard output
Workaround Description:
run installer as
{code}java -DTRACE=true -jar installer-XXXX.jar
> Installer should not require UI to report errors in automated mode
> ------------------------------------------------------------------
>
> Key: JBDS-3391
> URL: https://issues.jboss.org/browse/JBDS-3391
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.0.0.Alpha1
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 9.0.0.Alpha2
>
>
> Currently if installer has problems installing JBDS in headless (automated) mode it tries to show error dialog. It works for normal installation when it is called with GUI available, but if fails if GUI is not available.
> {code}Exception in thread "IzPack - Unpacker thread" java.lang.InternalError: Can't connect to X11 window server using '' as the value of the DISPLAY variable.
> at sun.awt.X11GraphicsEnvironment.initDisplay(Native Method)
> at sun.awt.X11GraphicsEnvironment.access$200(X11GraphicsEnvironment.java:65)
> at sun.awt.X11GraphicsEnvironment$1.run(X11GraphicsEnvironment.java:110)
> at java.security.AccessController.doPrivileged(Native Method)
> at sun.awt.X11GraphicsEnvironment.<clinit>(X11GraphicsEnvironment.java:74)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:191)
> at java.awt.GraphicsEnvironment.createGE(GraphicsEnvironment.java:102)
> at java.awt.GraphicsEnvironment.getLocalGraphicsEnvironment(GraphicsEnvironment.java:81)
> at sun.awt.X11.XToolkit.<clinit>(XToolkit.java:120)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:191)
> at java.awt.Toolkit$2.run(Toolkit.java:869)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.awt.Toolkit.getDefaultToolkit(Toolkit.java:861)
> at javax.swing.ImageIcon.<init>(ImageIcon.java:186)
> at javax.swing.ImageIcon.<init>(ImageIcon.java:205)
> at com.izforge.izpack.installer.ResourceManager.getImageIconResource(Unknown Source)
> at com.izforge.izpack.installer.Unpacker.run(Unpacker.java:614)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> Most resent example is installer headless tests was failing to show installation error and we had to enable tracing to find the reason. Installer should recognize automated mode, print error message to standard error output and return appropriate error code.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 1 month
[JBoss JIRA] (JBDS-3391) Installer should not require UI to report errors in automated mode
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3391?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3391:
--------------------------------
Issue Type: Bug (was: Enhancement)
> Installer should not require UI to report errors in automated mode
> ------------------------------------------------------------------
>
> Key: JBDS-3391
> URL: https://issues.jboss.org/browse/JBDS-3391
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.0.0.Alpha1
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 9.0.0.Alpha2
>
>
> Currently if installer has problems installing JBDS in headless (automated) mode it tries to show error dialog. It works for normal installation when it is called with GUI available, but if fails if GUI is not available. Most resent example is installer headless tests was failing to show installation error and we had to enable tracing to find the reason. Installer should recognize automated mode, print error message to standard error output and return appropriate error code.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 1 month
[JBoss JIRA] (JBDS-3391) Installer should not require UI to report errors in automated mode
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3391?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-3391:
-----------------------------
CDW release: + (was: ?)
> Installer should not require UI to report errors in automated mode
> ------------------------------------------------------------------
>
> Key: JBDS-3391
> URL: https://issues.jboss.org/browse/JBDS-3391
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Components: installer
> Affects Versions: 9.0.0.Alpha1
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 9.0.0.Alpha2
>
>
> Currently if installer has problems installing JBDS in headless (automated) mode it tries to show error dialog. It works for normal installation when it is called with GUI available, but if fails if GUI is not available. Most resent example is installer headless tests was failing to show installation error and we had to enable tracing to find the reason. Installer should recognize automated mode, print error message to standard error output and return appropriate error code.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 1 month