November 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-15594) Cannot connect to OpenShift DEVENV with hostname: javax.net.ssl.SSLProtocolException

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15594?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-15594: ---------------------------------------- Fix Version/s: 4.2.x > Cannot connect to OpenShift DEVENV with hostname: javax.net.ssl.SSLProtocolException > ------------------------------------------------------------------------------------ > > Key: JBIDE-15594 > URL: https://issues.jboss.org/browse/JBIDE-15594 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.Alpha2, 4.2.0.Alpha1 > Environment: jdk7 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.2.x > > Attachments: unknown-error.png > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15760) generated index.html facade should suppress link to features/ & site.properties for bundle-only sites

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15760?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-15760: ---------------------------------------- Fix Version/s: 4.2.x > generated index.html facade should suppress link to features/ & site.properties for bundle-only sites > ----------------------------------------------------------------------------------------------------- > > Key: JBIDE-15760 > URL: https://issues.jboss.org/browse/JBIDE-15760 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, maven > Affects Versions: 4.1.1.Beta1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.2.x > > > The generated index.html facade should not provide a link to features/ subfolder if the site only contains bundles (plugins/ subfolder), since the link is 404'd. > Example sites w/ no features: > http://download.jboss.org/jbosstools/updates/nightly/integration-stack-te... > http://download.jboss.org/jbosstools/updates/nightly/integration-stack-te... > Need to parameterize this bit of XSLT [0]: > [0] https://github.com/jbosstools/jbosstools-maven-plugins/blob/master/tycho-... > Also, we should probably not generate a site.properties file [1] for sites w/ no features as there's no features to list in the file. > [1] https://github.com/jbosstools/jbosstools-maven-plugins/blob/master/tycho-... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15167) Need more UI/integration testing on simpler Eclipse baselines, to catch missing runtime dependencies causing disabled/broken functionality

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15167?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-15167: ---------------------------------------- Fix Version/s: 4.2.x > Need more UI/integration testing on simpler Eclipse baselines, to catch missing runtime dependencies causing disabled/broken functionality > ------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-15167 > URL: https://issues.jboss.org/browse/JBIDE-15167 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-platform, testing-tools > Affects Versions: 4.1.0.CR1 > Reporter: Nick Boldt > Fix For: 4.2.x > > > As exposed in JBIDE-15156, it's possible to successfully install parts of JBT into an Eclipse instance, but then have the JBT functionality missing due to missing undeclared runtime dependencies. > Tycho will catch missing *build-time* dependencies, but doesn't know about *run-time* dependencies. > Thus, to avoid JBIDE-15156 and similar (or undiscovered) problems in future, we ought to have Jenkins jobs that do this: > a) for a given matrix of Eclipse platforms (platform runtime binary, Classic, Java, JavaEE), perform headless install (unpack) > b) install a group of JBT features (eg., Server features, Forge features, GWT features, etc.), or install each update site category (core tools, web tools, mobile tools, cloud tools, general tools, reporting tools, etc.) > c) run SWTBot JUnit tests in that Eclipse instance to verify that UI and functionality are present and working as expected. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15167) Need more UI/integration testing on simpler Eclipse baselines, to catch missing runtime dependencies causing disabled/broken functionality

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15167?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-15167: ---------------------------------------- Component/s: qa (was: testing-tools) (was: integration-platform) > Need more UI/integration testing on simpler Eclipse baselines, to catch missing runtime dependencies causing disabled/broken functionality > ------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-15167 > URL: https://issues.jboss.org/browse/JBIDE-15167 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: qa > Affects Versions: 4.1.0.CR1 > Reporter: Nick Boldt > Fix For: 4.2.x > > > As exposed in JBIDE-15156, it's possible to successfully install parts of JBT into an Eclipse instance, but then have the JBT functionality missing due to missing undeclared runtime dependencies. > Tycho will catch missing *build-time* dependencies, but doesn't know about *run-time* dependencies. > Thus, to avoid JBIDE-15156 and similar (or undiscovered) problems in future, we ought to have Jenkins jobs that do this: > a) for a given matrix of Eclipse platforms (platform runtime binary, Classic, Java, JavaEE), perform headless install (unpack) > b) install a group of JBT features (eg., Server features, Forge features, GWT features, etc.), or install each update site category (core tools, web tools, mobile tools, cloud tools, general tools, reporting tools, etc.) > c) run SWTBot JUnit tests in that Eclipse instance to verify that UI and functionality are present and working as expected. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15804) Repair failing tests in: http://machydra.brq.redhat.com:8080/job/jbosstools.mylyn.bot.tests.poc/

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15804?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-15804: ---------------------------------------- Component/s: qa > Repair failing tests in: http://machydra.brq.redhat.com:8080/job/jbosstools.mylyn.bot.tests.poc/ > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-15804 > URL: https://issues.jboss.org/browse/JBIDE-15804 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: qa > Reporter: Len DiMaggio > Assignee: Len DiMaggio > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15810) Issue on Smooks

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15810?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-15810: ---------------------------------------- Component/s: smooks > Issue on Smooks > --------------- > > Key: JBIDE-15810 > URL: https://issues.jboss.org/browse/JBIDE-15810 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: smooks > Reporter: siva maturi > > when i run sooks-config.xml i will get this error please tell me if any one know > Exception in thread "main" java.lang.IllegalArgumentException: ObjectSerializer argument 'object' is null. > at org.jboss.tools.smooks.launch.serialize.ObjectSerializer.assertNotNull(ObjectSerializer.java:278) > at org.jboss.tools.smooks.launch.serialize.ObjectSerializer.<init>(ObjectSerializer.java:56) > at org.jboss.tools.smooks.launch.serialize.ObjectSerializer.serialize(ObjectSerializer.java:79) > at org.jboss.tools.smooks.launch.SmooksLauncher.main(SmooksLauncher.java:103) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2818) Text in Early Access and Update page needs minor editing

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2818?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2818: ----------------------------- CDW devel_ack: ? (was: +) CDW release: ? (was: +) > Text in Early Access and Update page needs minor editing > -------------------------------------------------------- > > Key: JBDS-2818 > URL: https://issues.jboss.org/browse/JBDS-2818 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: documentation > Affects Versions: 7.0.1.GA > Reporter: Michelle Murray > Assignee: Nick Boldt > Fix For: 7.1.0.Beta1 > > > Both of these templates need the text modifying (to fit Red Hat writing style and 508 compliance): > https://devstudio.jboss.com/updates/7.0/ > https://devstudio.jboss.com/earlyaccess/7.0.0.GA.html > *Common text modifications:* > * Section "Installation :: Core Tooling" > {quote} > 1. If not already installed, download and install Oracle JDK or OpenJDK 7 (or 6). > 2. Download the JBDS universal installer from <link>. > 3. To start the installer, double-click the installer file or in a CLI enter java -jar jbdevstudio-*.jar > {quote} > * Section "Looking for JBoss EAP ..." > Logo has changed, now just logotype. Looking for link. > * Section "Getting Started Guide:" > {quote} > Adding *JBoss* EAP to JBDS > {quote} > *Early Access text modifications:* > * Title should be "*Red Hat* JBoss Developer Studio ......" > * Intro text > {quote} > We wish to give customers and users early access to *JBoss Developer Studio* so *that* we can make the next version of JBoss Developer Studio an even better environment for developing with and for Red Hat JBoss Middleware. > {quote} > *Updates text modifications* > * Why do we have this text? I ask because, for example, in https://devstudio.jboss.com/updates/7.0/, on the right-hand side the "installer" link in installation step 2 takes you to https://devstudio.jboss.com/earlyaccess/7.0.0.GA.html where you can download what looks like the GA version without subscription or opting in to a trial. Also you can get JBDS BYOE without subscription or trial on Eclipse marketplace. Seems the text is outdated but I don't know all the ins and outs of JBDS marketing and alike - hence asking the question. > {quote} > If you do not already have a copy of JBoss Developer Studio, you can purchase a subscription or get a > 30-day Free Trial from here: https://access.redhat.com/downloads/. > {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2818) Text in Early Access and Update page needs minor editing

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2818?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-2818: -------------------------------------- Component/s: documentation > Text in Early Access and Update page needs minor editing > -------------------------------------------------------- > > Key: JBDS-2818 > URL: https://issues.jboss.org/browse/JBDS-2818 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: documentation > Affects Versions: 7.0.1.GA > Reporter: Michelle Murray > Assignee: Nick Boldt > Fix For: 7.1.0.Beta1 > > > Both of these templates need the text modifying (to fit Red Hat writing style and 508 compliance): > https://devstudio.jboss.com/updates/7.0/ > https://devstudio.jboss.com/earlyaccess/7.0.0.GA.html > *Common text modifications:* > * Section "Installation :: Core Tooling" > {quote} > 1. If not already installed, download and install Oracle JDK or OpenJDK 7 (or 6). > 2. Download the JBDS universal installer from <link>. > 3. To start the installer, double-click the installer file or in a CLI enter java -jar jbdevstudio-*.jar > {quote} > * Section "Looking for JBoss EAP ..." > Logo has changed, now just logotype. Looking for link. > * Section "Getting Started Guide:" > {quote} > Adding *JBoss* EAP to JBDS > {quote} > *Early Access text modifications:* > * Title should be "*Red Hat* JBoss Developer Studio ......" > * Intro text > {quote} > We wish to give customers and users early access to *JBoss Developer Studio* so *that* we can make the next version of JBoss Developer Studio an even better environment for developing with and for Red Hat JBoss Middleware. > {quote} > *Updates text modifications* > * Why do we have this text? I ask because, for example, in https://devstudio.jboss.com/updates/7.0/, on the right-hand side the "installer" link in installation step 2 takes you to https://devstudio.jboss.com/earlyaccess/7.0.0.GA.html where you can download what looks like the GA version without subscription or opting in to a trial. Also you can get JBDS BYOE without subscription or trial on Eclipse marketplace. Seems the text is outdated but I don't know all the ins and outs of JBDS marketing and alike - hence asking the question. > {quote} > If you do not already have a copy of JBoss Developer Studio, you can purchase a subscription or get a > 30-day Free Trial from here: https://access.redhat.com/downloads/. > {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12860) JAX-RS validation problems are not linked

by Radoslav Rábara (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12860?page=com.atlassian.jira.plugi... ] Radoslav Rábara closed JBIDE-12860. ----------------------------------- In JBDS 7.1.0 Beta1-v20131102-1529-B493 there is no problem marker in web.xml. The validation is now testing if there are more classes extending Application (it doesn't matter if the application path is configured or not). So the linking of the validation problems is resolved. > JAX-RS validation problems are not linked > ----------------------------------------- > > Key: JBIDE-12860 > URL: https://issues.jboss.org/browse/JBIDE-12860 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.0.0.Beta1 > Reporter: Jaroslav Jankovič > Assignee: Xavier Coulon > Labels: respin-a > Fix For: 4.1.1.Beta1 > > > This case now fails: > STEP: Create jaxrs problem with Application problem (Multiple application definition - one class extending Application and one application servlet definition in web.xml) > STEP: comment servlet definition in web.xml > ASSERT: problem marker in web.xml disappears > ASSERT: problem marker in application class disappears > FAIL: problem marker in application class doesn't disappear, because problem markers are not linked now -> project has to be built to correctly remove both problem markers -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15793) Cordova Feature multiselection is not working

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15793?page=com.atlassian.jira.plugi... ] Vlado Pakan updated JBIDE-15793: -------------------------------- Attachment: overwritefilesdialog.png > Cordova Feature multiselection is not working > --------------------------------------------- > > Key: JBIDE-15793 > URL: https://issues.jboss.org/browse/JBIDE-15793 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.1.1.Beta1 > Environment: JBT 4.1.1 Beta1-v20131020-0207-B454 > Reporter: Vlado Pakan > Assignee: Gorkem Ercan > Labels: respin-b > Fix For: 4.1.1.Beta1 > > Attachments: overwritefilesdialog.png > > > 1. Create new Hybrid Mobile project > 2. Open config.xml file via Cordova Configuration Editor > 3. Choose Add.. to add features, select more than one feature and click Finish > ERROR: Only first selected feature is added to project and to config.xml file -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 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 November 2013