January 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (LOCUS-50) Locus bundle for jsonschema2pojo has corrupted Export-Package statement

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/LOCUS-50?page=com.atlassian.jira.plugin.s... ] Brian Fitzpatrick edited comment on LOCUS-50 at 1/21/16 11:04 AM: ------------------------------------------------------------------ And another issue with the jaxb-xjc bundle. The com.sun.xml.txw2 packages aren't exported from jaxb-core: {code} Caused by: java.lang.ClassNotFoundException: com.sun.xml.txw2.output.XmlSerializer cannot be found by org.jboss.tools.locus.jaxb-xjc_2.2.7.v20160113-1915 at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:439) 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:357) ... 126 more {code} was (Author: bfitzpat): And another issue with the jaxb-xjc bundle: {code} Caused by: java.lang.ClassNotFoundException: com.sun.xml.txw2.output.XmlSerializer cannot be found by org.jboss.tools.locus.jaxb-xjc_2.2.7.v20160113-1915 at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:439) 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:357) ... 126 more {code} > Locus bundle for jsonschema2pojo has corrupted Export-Package statement > ----------------------------------------------------------------------- > > Key: LOCUS-50 > URL: https://issues.jboss.org/browse/LOCUS-50 > Project: JBoss Tools Locus > Issue Type: Bug > Affects Versions: 1.5.0 > Reporter: Lars Heinemann > Assignee: Nick Boldt > Priority: Blocker > Fix For: 1.6.0 > > > see https://gist.github.com/lhein/47405c1fcb9dc2a7138e > Bundle: > org.jboss.tools.locus.jsonschema2pojo.jsonschema2pojo-core 0.4.13 from 20150709-1710 > When trying to resolve classes from this bundle it fails. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21531) New Application wizard: Template parameter with empty/generated value has wrong validation

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21531?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21531: -------------------------------- Fix Version/s: 4.3.1.CR1 > New Application wizard: Template parameter with empty/generated value has wrong validation > ------------------------------------------------------------------------------------------ > > Key: JBIDE-21531 > URL: https://issues.jboss.org/browse/JBIDE-21531 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Marián Labuda > Labels: application_wizard, openshift_v3 > Fix For: 4.3.1.CR1 > > > In New OpenShift application wizard on the wizard page with template parameters when I select to edit a parameter with empty ("") or generated ("(generated)") value, text widget to enter new value is marked with error validation mark, that new value is required, but OK button is enabled. It either should be without validation mark or OK button should be disabled, if confirmation is meant to be allowed only for a new value. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (LOCUS-50) Locus bundle for jsonschema2pojo has corrupted Export-Package statement

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/LOCUS-50?page=com.atlassian.jira.plugin.s... ] Brian Fitzpatrick commented on LOCUS-50: ---------------------------------------- And another issue with the jaxb-xjc bundle: {code} Caused by: java.lang.ClassNotFoundException: com.sun.xml.txw2.output.XmlSerializer cannot be found by org.jboss.tools.locus.jaxb-xjc_2.2.7.v20160113-1915 at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:439) 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:357) ... 126 more {code} > Locus bundle for jsonschema2pojo has corrupted Export-Package statement > ----------------------------------------------------------------------- > > Key: LOCUS-50 > URL: https://issues.jboss.org/browse/LOCUS-50 > Project: JBoss Tools Locus > Issue Type: Bug > Affects Versions: 1.5.0 > Reporter: Lars Heinemann > Assignee: Nick Boldt > Priority: Blocker > Fix For: 1.6.0 > > > see https://gist.github.com/lhein/47405c1fcb9dc2a7138e > Bundle: > org.jboss.tools.locus.jsonschema2pojo.jsonschema2pojo-core 0.4.13 from 20150709-1710 > When trying to resolve classes from this bundle it fails. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (LOCUS-50) Locus bundle for jsonschema2pojo has corrupted Export-Package statement

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/LOCUS-50?page=com.atlassian.jira.plugin.s... ] Brian Fitzpatrick commented on LOCUS-50: ---------------------------------------- There's another issue with the jaxb-core bundle as well. The com.sun.istack packages are not exported. {code} Caused by: java.lang.ClassNotFoundException: com.sun.istack.SAXParseException2 cannot be found by org.jboss.tools.locus.jaxb-xjc_2.2.7.v20160113-1915 at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:439) 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:357) ... 107 more {code} > Locus bundle for jsonschema2pojo has corrupted Export-Package statement > ----------------------------------------------------------------------- > > Key: LOCUS-50 > URL: https://issues.jboss.org/browse/LOCUS-50 > Project: JBoss Tools Locus > Issue Type: Bug > Affects Versions: 1.5.0 > Reporter: Lars Heinemann > Assignee: Nick Boldt > Priority: Blocker > Fix For: 1.6.0 > > > see https://gist.github.com/lhein/47405c1fcb9dc2a7138e > Bundle: > org.jboss.tools.locus.jsonschema2pojo.jsonschema2pojo-core 0.4.13 from 20150709-1710 > When trying to resolve classes from this bundle it fails. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (LOCUS-50) Locus bundle for jsonschema2pojo has corrupted Export-Package statement

by Lars Heinemann (JIRA)

[ https://issues.jboss.org/browse/LOCUS-50?page=com.atlassian.jira.plugin.s... ] Lars Heinemann commented on LOCUS-50: ------------------------------------- There is at least one issue with the jaxb-xjc bundle. {noformat} Caused by: java.lang.ClassNotFoundException: com.sun.xml.bind.api.ErrorListener cannot be found by org.jboss.tools.locus.jaxb-xjc_2.2.7.v20160113-1915 at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:439) 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:357) ... 119 more {noformat} It tries to resolve a class from jaxb-core but it has no require-bundle entry nor import package. > Locus bundle for jsonschema2pojo has corrupted Export-Package statement > ----------------------------------------------------------------------- > > Key: LOCUS-50 > URL: https://issues.jboss.org/browse/LOCUS-50 > Project: JBoss Tools Locus > Issue Type: Bug > Affects Versions: 1.5.0 > Reporter: Lars Heinemann > Assignee: Nick Boldt > Priority: Blocker > Fix For: 1.6.0 > > > see https://gist.github.com/lhein/47405c1fcb9dc2a7138e > Bundle: > org.jboss.tools.locus.jsonschema2pojo.jsonschema2pojo-core 0.4.13 from 20150709-1710 > When trying to resolve classes from this bundle it fails. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20726) Docker explorer - Default setting should be to display and not hide stopped containers

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20726?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-20726. --------------------------------- Verified in JBDS 9.1.0.Beta2 B237 > Docker explorer - Default setting should be to display and not hide stopped containers > -------------------------------------------------------------------------------------- > > Key: JBIDE-20726 > URL: https://issues.jboss.org/browse/JBIDE-20726 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker, upstream > Affects Versions: 4.3.0.CR1 > Reporter: Len DiMaggio > Assignee: Xavier Coulon > Labels: new_and_noteworthy > Fix For: 4.3.1.Beta2 > > > By default, only running containers are shown in the Docker explorer view - I think that users will expect to see all containers by default. The OOTB default setting should be changed to show all containers. Thx! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21531) New Application wizard: Template parameter with empty/generated value has wrong validation

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21531?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21531: ---------------------------------- Labels: application_wizard openshift_v3 (was: ) > New Application wizard: Template parameter with empty/generated value has wrong validation > ------------------------------------------------------------------------------------------ > > Key: JBIDE-21531 > URL: https://issues.jboss.org/browse/JBIDE-21531 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Marián Labuda > Labels: application_wizard, openshift_v3 > > In New OpenShift application wizard on the wizard page with template parameters when I select to edit a parameter with empty ("") or generated ("(generated)") value, text widget to enter new value is marked with error validation mark, that new value is required, but OK button is enabled. It either should be without validation mark or OK button should be disabled, if confirmation is meant to be allowed only for a new value. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21531) New Application wizard: Template parameter with empty/generated value has wrong validation

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-21531: ------------------------------------- Summary: New Application wizard: Template parameter with empty/generated value has wrong validation Key: JBIDE-21531 URL: https://issues.jboss.org/browse/JBIDE-21531 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.Beta2 Reporter: Marián Labuda In New OpenShift application wizard on the wizard page with template parameters when I select to edit a parameter with empty ("") or generated ("(generated)") value, text widget to enter new value is marked with error validation mark, that new value is required, but OK button is enabled. It either should be without validation mark or OK button should be disabled, if confirmation is meant to be allowed only for a new value. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21042) Jiralint email template says to set assignee when blank, but we use blank assignee to know what issues are not yet being worked

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21042?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-21042. --------------------------------- Verified in a recent email from jiralint. > Jiralint email template says to set assignee when blank, but we use blank assignee to know what issues are not yet being worked > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21042 > URL: https://issues.jboss.org/browse/JBIDE-21042 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Fix For: 4.3.1.Beta2 > > Attachments: jiralint1.png > > > Jiralint email template says to set assignee when blank, but we use blank assignee to know what issues are not yet being worked. > Therefore the template used to generate jiralint emails should remove this: > {quote}Assignee: None set - please fix.{quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21056) Application wizard: Read-only labels should have a visual hint they're read-only

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21056?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21056. --------------------------------- Verified in nigthly build of JBT with OpenShift tools plugin of version 3.1.0.Beta2-v20160121-0335-B154. > Application wizard: Read-only labels should have a visual hint they're read-only > -------------------------------------------------------------------------------- > > Key: JBIDE-21056 > URL: https://issues.jboss.org/browse/JBIDE-21056 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta1 > Environment: Nightly JBT. OpenShift tooling build Version: 3.1.0.Beta1-v20151104-0336-B66 > Reporter: Marián Labuda > Assignee: Fred Bricon > Priority: Minor > Labels: application_wizard, openshift_v3 > Fix For: 4.3.1.Beta2 > > > Labels in a New OpenShift Application wizard on the page containing label managing are not treated equally. When application is build on a template with more predefined labels, the first one listed in the table with labels is read-only, but the second one (maybe also further labels) are editable and removable. We should treat all labels equally. Either take them as read only from templates or allow user to modify them. As an testing example was used template located at https://github.com/jboss-openshift/application-templates/blob/master/eap/... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 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 January 2016