July 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20405) Improve the display of the error message resulting from trying to create new OpenShift v3 application when launching wizard from Central in 4.3.0.beta2

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20405?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-20405: --------------------------------- Attachment: Screenshot-5.png Screenshot-4.png > Improve the display of the error message resulting from trying to create new OpenShift v3 application when launching wizard from Central in 4.3.0.beta2 > ------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20405 > URL: https://issues.jboss.org/browse/JBIDE-20405 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Len DiMaggio > Attachments: Screenshot-4.png, Screenshot-5.png > > > See attached screenshots -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20405) Improve the display of the error message resulting from trying to create new OpenShift v3 application when launching wizard from Central in 4.3.0.beta2

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20405?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-20405: --------------------------------- Description: See attached screenshots - can we provide a more descriptive, and better formatted, error message? Thx! (was: See attached screenshots) > Improve the display of the error message resulting from trying to create new OpenShift v3 application when launching wizard from Central in 4.3.0.beta2 > ------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20405 > URL: https://issues.jboss.org/browse/JBIDE-20405 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Len DiMaggio > Attachments: Screenshot-4.png, Screenshot-5.png > > > See attached screenshots - can we provide a more descriptive, and better formatted, error message? Thx! -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20405) Improve the display of the error message resulting from trying to create new OpenShift v3 application when launching wizard from Central in 4.3.0.beta2

by Len DiMaggio (JIRA)

Len DiMaggio created JBIDE-20405: ------------------------------------ Summary: Improve the display of the error message resulting from trying to create new OpenShift v3 application when launching wizard from Central in 4.3.0.beta2 Key: JBIDE-20405 URL: https://issues.jboss.org/browse/JBIDE-20405 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Reporter: Len DiMaggio See attached screenshots -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20350) Port forwarding wizard: Dont see what pod I am forwarding ports for

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20350?page=com.atlassian.jira.plugi... ] Jeff Cantrill resolved JBIDE-20350. ----------------------------------- Resolution: Done Fixed in this commit: https://github.com/jbosstools/jbosstools-openshift/commit/ba8281059329991... > Port forwarding wizard: Dont see what pod I am forwarding ports for > ------------------------------------------------------------------- > > Key: JBIDE-20350 > URL: https://issues.jboss.org/browse/JBIDE-20350 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Andre Dietisheim > Assignee: Jeff Cantrill > Labels: openshift_v3, port_forwarding_wizard > Fix For: 4.3.0.CR1 > > Attachments: what-pod-am-i-forwarding.png > > > # ASSERT: make sure that you have a pod running > # EXEC: in OpenShift explorer: select your pod and pick "Port Forwarding" from context menu. > # ASSERT: port forwarding wizard pops up. > Result: > !what-pod-am-i-forwarding.png! > The port forwarding wizard wont tell you what pod you're forwarding ports for. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-467) Pull in graphiti 0.13.0 into JBTIS TP from JBoss mirror

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-467: -------------------------------- Summary: Pull in graphiti 0.13.0 into JBTIS TP from JBoss mirror Key: JBTIS-467 URL: https://issues.jboss.org/browse/JBTIS-467 Project: JBoss Tools Integration Stack Issue Type: Feature Request Components: target-platform Affects Versions: 4.3.0.Beta1c-TP Reporter: Paul Leacu Assignee: Paul Leacu Fuse Tooling needs the latest graphiti (0.13.0). It will be available in Eclipse Mars SR1. Until then - take it from a local JBoss mirror. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16158) Investigate tools/processes to "templatize" CI jobs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16158?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-16158: ------------------------------------ [~maxandersen] I've verified the instructions work for installation and production of config files. I've updated (and renamed - to adhere to standard uppercase convention) the README file with missing details (like running pip as root): https://github.com/jbosstools/jbosstools-build-ci/tree/jbosstools-4.3.x/b... -- Also cleaned up the todirformat.sh script. https://github.com/jbosstools/jbosstools-build-ci/commit/5828f7e571f405ab... -- When I'm back from PTO I can start diffing the output between this and the hardcoded config.xml files we have in here: * https://github.com/jbdevstudio/jbdevstudio-ci/tree/master/cache/https/jen... * https://github.com/jbdevstudio/jbdevstudio-ci/tree/master/cache/https/jen... > Investigate tools/processes to "templatize" CI jobs > --------------------------------------------------- > > Key: JBIDE-16158 > URL: https://issues.jboss.org/browse/JBIDE-16158 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Mickael Istria > Assignee: Max Rydahl Andersen > Fix For: 4.3.0.CR1 > > > Found something a bit more complete than the maven plugin - haven't tried it yet but its examples looks extremely clean. > python script for creating jobs (linked to puppet but can be used standalone) > http://ci.openstack.org/jenkins-job-builder/installation.html > Example: https://github.com/adaptivelab/jenkins-build/blob/develop/template.yaml > Article: http://techs.enovance.com/6006/manage-jenkins-jobs-with-yaml -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16158) Investigate tools/processes to "templatize" CI jobs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16158?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-16158: ---------------------------------- Assignee: Nick Boldt (was: Max Rydahl Andersen) > Investigate tools/processes to "templatize" CI jobs > --------------------------------------------------- > > Key: JBIDE-16158 > URL: https://issues.jboss.org/browse/JBIDE-16158 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 4.3.0.CR1 > > > Found something a bit more complete than the maven plugin - haven't tried it yet but its examples looks extremely clean. > python script for creating jobs (linked to puppet but can be used standalone) > http://ci.openstack.org/jenkins-job-builder/installation.html > Example: https://github.com/adaptivelab/jenkins-build/blob/develop/template.yaml > Article: http://techs.enovance.com/6006/manage-jenkins-jobs-with-yaml -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20350) Port forwarding wizard: Dont see what pod I am forwarding ports for

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20350?page=com.atlassian.jira.plugi... ] Jeff Cantrill reassigned JBIDE-20350: ------------------------------------- Assignee: Jeff Cantrill > Port forwarding wizard: Dont see what pod I am forwarding ports for > ------------------------------------------------------------------- > > Key: JBIDE-20350 > URL: https://issues.jboss.org/browse/JBIDE-20350 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Andre Dietisheim > Assignee: Jeff Cantrill > Labels: openshift_v3, port_forwarding_wizard > Fix For: 4.3.0.CR1 > > Attachments: what-pod-am-i-forwarding.png > > > # ASSERT: make sure that you have a pod running > # EXEC: in OpenShift explorer: select your pod and pick "Port Forwarding" from context menu. > # ASSERT: port forwarding wizard pops up. > Result: > !what-pod-am-i-forwarding.png! > The port forwarding wizard wont tell you what pod you're forwarding ports for. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19940) Detector of non-compatilbe JVMs may miss UnsupportedClassVersionError(s)

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19940?page=com.atlassian.jira.plugi... ] Daniel Azarov edited comment on JBIDE-19940 at 7/30/15 1:24 PM: ---------------------------------------------------------------- I did some investigation. This exception is thrown when you run code which was compiled with higher java version. Possible major/minor value : ||major||minor||Java platform version|| |45|3|1.0| |45|3|1.1| |46|0|1.2| |47|0|1.3| |48|0|1.4| |49|0|1.5| |50|0|1.6| |51|0|1.7| |52|0|1.8| So it is really make sens to react on this exception just like we did for "org.osgi.framework.BundleException: Could not resolve module:" But probably we should show different message in this case was (Author: dazarov): I did some investigation. This exception is thrown when you run code which was compiled with higher java version. Possible major/minor value : ||major||minor||Java platform version|| |45|3|1.0| |45|3|1.1| |46|0|1.2| |47|0|1.3| |48|0|1.4| |49|0|1.5| |50|0|1.6| |51|0|1.7| |52|0|1.8| > Detector of non-compatilbe JVMs may miss UnsupportedClassVersionError(s) > ------------------------------------------------------------------------ > > Key: JBIDE-19940 > URL: https://issues.jboss.org/browse/JBIDE-19940 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.3.0.Beta1 > Reporter: Alexey Kazakov > Assignee: Daniel Azarov > Fix For: 4.3.0.CR1 > > > When testing JBIDE-19500 (warn/inform users running on non-compatilbe JVMs they are loosing out on features) on some old workspaces I got a situation when Eclipse didn't report a usual error saying "Unresolved requirement: Require-Capability: osgi.ee; filter:="(&(osgi.ee=JavaSE)(version=1.8))" but I got UnsupportedClassVersionErrors like: > {code} > Caused by: java.lang.UnsupportedClassVersionError: org/jboss/tools/usage/event/UsageEventType : Unsupported major.minor version 52.0 > at java.lang.ClassLoader.defineClass1(Native Method) > at java.lang.ClassLoader.defineClass(ClassLoader.java:800) > at org.eclipse.osgi.internal.loader.ModuleClassLoader.defineClass(ModuleClassLoader.java:272) > at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.defineClass(ClasspathManager.java:632) > at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findClassImpl(ClasspathManager.java:588) > at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClassImpl(ClasspathManager.java:540) > at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClass(ClasspathManager.java:527) > at org.eclipse.osgi.internal.loader.ModuleClassLoader.findLocalClass(ModuleClassLoader.java:324) > at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:327) > at org.eclipse.osgi.internal.loader.sources.SingleSourcePackage.loadClass(SingleSourcePackage.java:36) > at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:398) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:352) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:344) > at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160) > at java.lang.ClassLoader.loadClass(ClassLoader.java:358) > at org.jboss.tools.forge.core.internal.ForgeCorePlugin.initializeUsageReporting(ForgeCorePlugin.java:48) > at org.jboss.tools.forge.core.internal.ForgeCorePlugin.start(ForgeCorePlugin.java:44) > at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:771) > at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1) > at java.security.AccessController.doPrivileged(Native Method) > at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:764) > {code} > Maybe it's because I was running JBT from my dev eclipse environment and Eclipse used some cashed Require-Capability's of load plugins and we won't have such problems in real world when problematic plugins are installed/updated but not modified in dev environment. > But anyway, this is worth investigation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19940) Detector of non-compatilbe JVMs may miss UnsupportedClassVersionError(s)

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19940?page=com.atlassian.jira.plugi... ] Daniel Azarov commented on JBIDE-19940: --------------------------------------- I did some investigation. This exception is thrown when you run code which was compiled with higher java version. Possible major/minor value : ||major||minor||Java platform version|| |45|3|1.0| |45|3|1.1| |46|0|1.2| |47|0|1.3| |48|0|1.4| |49|0|1.5| |50|0|1.6| |51|0|1.7| |52|0|1.8| > Detector of non-compatilbe JVMs may miss UnsupportedClassVersionError(s) > ------------------------------------------------------------------------ > > Key: JBIDE-19940 > URL: https://issues.jboss.org/browse/JBIDE-19940 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.3.0.Beta1 > Reporter: Alexey Kazakov > Assignee: Daniel Azarov > Fix For: 4.3.0.CR1 > > > When testing JBIDE-19500 (warn/inform users running on non-compatilbe JVMs they are loosing out on features) on some old workspaces I got a situation when Eclipse didn't report a usual error saying "Unresolved requirement: Require-Capability: osgi.ee; filter:="(&(osgi.ee=JavaSE)(version=1.8))" but I got UnsupportedClassVersionErrors like: > {code} > Caused by: java.lang.UnsupportedClassVersionError: org/jboss/tools/usage/event/UsageEventType : Unsupported major.minor version 52.0 > at java.lang.ClassLoader.defineClass1(Native Method) > at java.lang.ClassLoader.defineClass(ClassLoader.java:800) > at org.eclipse.osgi.internal.loader.ModuleClassLoader.defineClass(ModuleClassLoader.java:272) > at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.defineClass(ClasspathManager.java:632) > at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findClassImpl(ClasspathManager.java:588) > at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClassImpl(ClasspathManager.java:540) > at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClass(ClasspathManager.java:527) > at org.eclipse.osgi.internal.loader.ModuleClassLoader.findLocalClass(ModuleClassLoader.java:324) > at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:327) > at org.eclipse.osgi.internal.loader.sources.SingleSourcePackage.loadClass(SingleSourcePackage.java:36) > at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:398) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:352) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:344) > at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160) > at java.lang.ClassLoader.loadClass(ClassLoader.java:358) > at org.jboss.tools.forge.core.internal.ForgeCorePlugin.initializeUsageReporting(ForgeCorePlugin.java:48) > at org.jboss.tools.forge.core.internal.ForgeCorePlugin.start(ForgeCorePlugin.java:44) > at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:771) > at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1) > at java.security.AccessController.doPrivileged(Native Method) > at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:764) > {code} > Maybe it's because I was running JBT from my dev eclipse environment and Eclipse used some cashed Require-Capability's of load plugins and we won't have such problems in real world when problematic plugins are installed/updated but not modified in dev environment. > But anyway, this is worth investigation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 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 July 2015