September 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-21290) CDK 2 is detected as version 1.0

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21290?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-21290. --------------------------------- Resolution: Done This is a mix of done / wont-fix / duplicate issue. 1) It doesn't register as 1.0 anymore 2) We won't do any updates to discern cdk 1 vs cdk 2 3) CDK-15 is addressing adding versioning to cdk.zip > CDK 2 is detected as version 1.0 > -------------------------------- > > Key: JBIDE-21290 > URL: https://issues.jboss.org/browse/JBIDE-21290 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, runtime-detection, upstream > Affects Versions: 4.3.1.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.4.2.AM1 > > Attachments: cdk-runtime-detection.png, Screenshot 2016-01-07 09.16.12.png > > > When you detect CDK using runtime detection, it will show you the name cdk-v2 which clearly shows it's version 2 (this is actually just based on the folder it seems). But the Version column says Version 1.0. > !cdk-runtime-detection.png! > Could we change it to version 2? > I know that this probably doesn't have any meaning right now - I noticed there is no runtime anymore, so the version is nowhere to be seen once you create the cdk server adapter. But it would still be nicer to show the correct version if possible. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21290) CDK 2 is detected as version 1.0

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21290?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-21290: -------------------------------- Fix Version/s: 4.4.2.AM1 (was: 4.4.x) > CDK 2 is detected as version 1.0 > -------------------------------- > > Key: JBIDE-21290 > URL: https://issues.jboss.org/browse/JBIDE-21290 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, runtime-detection, upstream > Affects Versions: 4.3.1.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.4.2.AM1 > > Attachments: cdk-runtime-detection.png, Screenshot 2016-01-07 09.16.12.png > > > When you detect CDK using runtime detection, it will show you the name cdk-v2 which clearly shows it's version 2 (this is actually just based on the folder it seems). But the Version column says Version 1.0. > !cdk-runtime-detection.png! > Could we change it to version 2? > I know that this probably doesn't have any meaning right now - I noticed there is no runtime anymore, so the version is nowhere to be seen once you create the cdk server adapter. But it would still be nicer to show the correct version if possible. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22879) JavaEE jars files are built with another java version than used for compilation

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22879?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-22879: -------------------------------- Priority: Trivial (was: Major) > JavaEE jars files are built with another java version than used for compilation > ------------------------------------------------------------------------------- > > Key: JBIDE-22879 > URL: https://issues.jboss.org/browse/JBIDE-22879 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.3.Final, 4.4.0.Final > Environment: I've observed this problem on a Win7 64 bit machine with Oracle JRE 1.8.0_102 64 bit. It was present in both JBoss Developer Studio 8.1.0.GA and 10.0.0.GA when used in conjunction with embedded Maven installation and JBoss EAP 6.4 target runtime. > Reporter: Mikhail Kalkov > Assignee: Rob Stryker > Priority: Trivial > Fix For: LATER > > Attachments: test-projects.zip > > > I have installed system-wide JRE 8 in order to run all java applications with it. At the same time, out target platform is still based on Java 7 and that's why I've also downloaded JDK 7 and set JAVA_HOME path to it. > When I build test-ejb project from attached zip file on command line, maven both compiles and packages it with JDK 7 obtained from JAVA_HOME. When I build the same project with JBoss Developer Studio which was configured via Window > Preferences > Java > Installed JREs to use JDK 7 by default, class files get version 51 (java 7) but Build-Jdk stanza in MANIFEST.MF is set to 1.8.0_102 instead of 1.7. I've also observed that test-ear project is also packaged with Java 8 instead of Java 7. > This is not a big issue but is a bit worrying since for example jar tool from JDK 8 may contains bugfixes not present in JDK 7. This also makes me think that other tools may be fetched from wrong JDK version. Finally, I'm not even sure whether this is a JBoss Tools, Eclipse WTP or Eclipse M2E issue but it is clearly present in the latest stock version of JBoss Developer Studio. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23169) JMX Navigator 'Connect...' on disconnected local process throws exception

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23169?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-23169: -------------------------------- Sprint: devex #121 October 2016 > JMX Navigator 'Connect...' on disconnected local process throws exception > ------------------------------------------------------------------------- > > Key: JBIDE-23169 > URL: https://issues.jboss.org/browse/JBIDE-23169 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 4.4.1.Final > Reporter: Denis Golovin > Assignee: Rob Stryker > Fix For: 4.4.2.AM1 > > Attachments: connect.png > > > !connect.png! > {code}java.lang.NullPointerException: Null JMXServiceURL > at javax.management.remote.JMXConnectorFactory.connect(Unknown Source) > at javax.management.remote.JMXConnectorFactory.connect(Unknown Source) > at org.jboss.tools.jmx.jvmmonitor.internal.core.MBeanServer.connectToMBeanServer(MBeanServer.java:71) > at org.jboss.tools.jmx.jvmmonitor.internal.core.MBeanServer.createMBeanServerConnection(MBeanServer.java:86) > at org.jboss.tools.jmx.jvmmonitor.internal.core.AbstractMBeanServer.connect(AbstractMBeanServer.java:832) > at org.jboss.tools.jmx.jvmmonitor.internal.core.ActiveJvm.connect(ActiveJvm.java:238) > at org.jboss.tools.jmx.jvmmonitor.internal.core.ActiveJvm.connect(ActiveJvm.java:213) > at org.jboss.tools.jmx.local.internal.JvmConnectionWrapper.connect(JvmConnectionWrapper.java:121) > at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55){code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23166) MBean Stubs New Wizard cannot be open

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23166?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-23166: -------------------------------- Sprint: devex #121 October 2016 > MBean Stubs New Wizard cannot be open > ------------------------------------- > > Key: JBIDE-23166 > URL: https://issues.jboss.org/browse/JBIDE-23166 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.1.Final > Reporter: Denis Golovin > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.4.2.AM1 > > Attachments: mbinstubs.gif > > > It just throws exception below > {code}The selected wizard could not be started. > Plug-in org.jboss.ide.eclipse.as.ui.mbeans was unable to load class org.jboss.ide.eclipse.as.ui.mbeans.wizards.NewMBeanWizard. > org.jboss.ide.eclipse.as.ui.mbeans.wizards.NewMBeanWizard cannot be found by org.jboss.ide.eclipse.as.ui.mbeans_3.2.1.v20160607-2122{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23134) Improve UI of Deployment tab of Runtime Editor

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23134?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-23134: -------------------------------- Sprint: devex #121 October 2016 > Improve UI of Deployment tab of Runtime Editor > ---------------------------------------------- > > Key: JBIDE-23134 > URL: https://issues.jboss.org/browse/JBIDE-23134 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Reporter: Aurélien Pupier > Assignee: Rob Stryker > Fix For: 4.4.2.AM1 > > Attachments: screenshot-1.png > > > - Refresh table button is really strange > - there are some grey background around the sections -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23266) CDK Server adapter: keeps starting CDK not aborting it when cancel button is pushed

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23266?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-23266: -------------------------------- Priority: Trivial (was: Major) > CDK Server adapter: keeps starting CDK not aborting it when cancel button is pushed > ----------------------------------------------------------------------------------- > > Key: JBIDE-23266 > URL: https://issues.jboss.org/browse/JBIDE-23266 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.2.AM1 > Reporter: Jeff MAURY > Assignee: Rob Stryker > Priority: Trivial > Labels: cdk, server > Fix For: 4.4.2.AM2 > > > When the credential dialog is show when starting the CDK server, if the user push the Cancel button, then an error dialog is then show where the operation should be aborted. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ERT-425) Add Restart Container to Containers View toolbar [EBZ#502207]

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/ERT-425?page=com.atlassian.jira.plugin.sy... ] Jeff Johnston resolved ERT-425. ------------------------------- Resolution: Done > Add Restart Container to Containers View toolbar [EBZ#502207] > ------------------------------------------------------------- > > Key: ERT-425 > URL: https://issues.jboss.org/browse/ERT-425 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Jeff Johnston > Labels: 5.2.0, Docker, bzira > Fix For: Neon.2 (4.6) > > > Add a restart icon to Docker Containers View toolbar. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23135) EAP 7.1 Server adapter

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23135?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-23135: -------------------------------- Sprint: devex #121 October 2016 > EAP 7.1 Server adapter > ---------------------- > > Key: JBIDE-23135 > URL: https://issues.jboss.org/browse/JBIDE-23135 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Alexey Kazakov > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.4.2.AM3 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13661) Cannot create archive from archive in explorer

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13661?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-13661: -------------------------------- Sprint: devex #121 October 2016 (was: devex #120 September 2016) > Cannot create archive from archive in explorer > ---------------------------------------------- > > Key: JBIDE-13661 > URL: https://issues.jboss.org/browse/JBIDE-13661 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: archives > Affects Versions: 4.1.0.Alpha1 > Reporter: Jaroslav Jankovič > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.4.2.AM1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues September 2016