May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18743) write tests for download.jboss.org & devstudio.redhat.com xmlunit test cases; validate composite*.xml; *.properties validation -- check if all properties are defined (avoid boss.* vs. jboss.*)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18743?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18743: ------------------------------- Fix Version/s: 4.4.0.Alpha2 (was: 4.4.0.Alpha1) > write tests for download.jboss.org & devstudio.redhat.com xmlunit test cases; validate composite*.xml; *.properties validation -- check if all properties are defined (avoid boss.* vs. jboss.*) > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-18743 > URL: https://issues.jboss.org/browse/JBIDE-18743 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.0.Final > Reporter: Nick Boldt > Fix For: 4.4.0.Alpha2 > > > We need to write tests for download.jboss.org & devstudio.redhat.com: > * xmlunit test cases > ** validate composite*.xml > ** unit testing for discovery plugin.xml, update site category.xml (avoid bad URLs like 8.0-staging in a milestone release) > * other test cases > ** \*.properties validation -- check if all properties are defined (avoid boss.* vs. jboss.*) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15332) stop linking skipRequirements and tests.skip to download of requirements

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15332?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-15332: ------------------------------- Fix Version/s: 4.4.0.Alpha2 (was: 4.4.0.Alpha1) > stop linking skipRequirements and tests.skip to download of requirements > ------------------------------------------------------------------------- > > Key: JBIDE-15332 > URL: https://issues.jboss.org/browse/JBIDE-15332 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.0.Beta1 > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Minor > Labels: f2f2014 > Fix For: 4.4.0.Alpha2 > > > I stumbled on [~dgolovin]'s patch for livreload at https://github.com/jbosstools/jbosstools-livereload/pull/54/files > This is not the first time i've seen skip having to be enabled for plain normal mvn dependencies. > skipRequirements are supposed to only cover big downloads (like EAP, jboss etc.) - things done via non-maven download mechanism. > Why is this applied to mvn dependency downloads ? > The culprit for needing this line is at: > https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... > and a bugzilla (*not* jira?!) is referenced as the reason for this back in 2012: https://github.com/jbosstools/jbosstools-build/commit/2e18baaf88e0cd73b3b... > I understand why the explicit google download plugin (why is there two versions used btw?) but why is skipTests controlling normal mvn dependency download ? Which requirements are using this for download ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20753) Text flickering when selecting server types in New Server wizard

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20753?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20753: ------------------------------- Fix Version/s: 4.4.0.Alpha2 (was: 4.4.0.Alpha1) > Text flickering when selecting server types in New Server wizard > ---------------------------------------------------------------- > > Key: JBIDE-20753 > URL: https://issues.jboss.org/browse/JBIDE-20753 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, upstream > Affects Versions: 4.3.0.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > Labels: regression > Fix For: 4.4.0.Alpha2 > > > When you open the New Server wizard and select a server type, There will be some elements rendered for a fraction of a second. It's Server Runtime Environment and a dropdown menu - it will disappear again, but it's not nice to see something quickly appear and disappear again. You can keep selecting server types and it will keep happening. All of this is on the first page of the dialog. > I checked and this did not happen in Beta2. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20742) jboss-kitchensink-angularjs project has error after imported from JBoss Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20742?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20742: ------------------------------- Fix Version/s: 4.4.0.Alpha2 (was: 4.4.0.Alpha1) > jboss-kitchensink-angularjs project has error after imported from JBoss Central > ------------------------------------------------------------------------------- > > Key: JBIDE-20742 > URL: https://issues.jboss.org/browse/JBIDE-20742 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript, upstream > Affects Versions: 4.3.0.CR1 > Environment: JBDS 9.0.0.CR1-v20150918-0257-B105 with bundled EAP > Reporter: Vlado Pakan > Assignee: Victor Rubezhny > Labels: regression > Fix For: 4.3.x, 4.4.0.Alpha2 > > Attachments: angularjserror.png > > > 1. Install AngularJS from JBoss Central Early access > 2. Import jboss-kitchensink-angularjs from JBoss Central > ERROR: > !angularjserror.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20540) Upstream WTP bundled xsd using relative path for ejb-jar_3_1.xsd

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20540?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20540: ------------------------------- Fix Version/s: 4.4.0.Alpha2 (was: 4.4.0.Alpha1) > Upstream WTP bundled xsd using relative path for ejb-jar_3_1.xsd > ---------------------------------------------------------------- > > Key: JBIDE-20540 > URL: https://issues.jboss.org/browse/JBIDE-20540 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server, upstream > Affects Versions: 4.3.0.CR1 > Reporter: Rob Stryker > Fix For: 4.4.0.Alpha2 > > > See bug as described here: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=476274 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20538) wildfly-ejb-multi-server-app-one-ejb quickstart upstream schema error

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20538?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20538: ------------------------------- Fix Version/s: 4.4.0.Alpha2 (was: 4.4.0.Alpha1) > wildfly-ejb-multi-server-app-one-ejb quickstart upstream schema error > --------------------------------------------------------------------- > > Key: JBIDE-20538 > URL: https://issues.jboss.org/browse/JBIDE-20538 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Reporter: Rob Stryker > Labels: xml_validation_schema_error > Fix For: 4.4.0.Alpha2 > > > Root cause here seems to be that the xsd on the web url http://www.jboss.org/schema/jbossas/jboss-ejb3-spec-2_0.xsd has a schemaLocation=jboss-ejb3-2_0.xsd relative path -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20536) Several quickstarts fail; jboss-ejb3-2_0.xsd cannot resolve jboss elements

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20536?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20536: ------------------------------- Fix Version/s: 4.4.0.Alpha2 (was: 4.4.0.Alpha1) > Several quickstarts fail; jboss-ejb3-2_0.xsd cannot resolve jboss elements > --------------------------------------------------------------------------- > > Key: JBIDE-20536 > URL: https://issues.jboss.org/browse/JBIDE-20536 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server, upstream > Reporter: Rob Stryker > Labels: xml_validation_quickstarts_eap7, xml_validation_quickstarts_wildfly, xml_validation_schema_error > Fix For: 4.4.0.Alpha2 > > > Several errors fail with the following error message: > Referenced file contains errors (file:/home/rob/code/fuseide/fuseide/targetplatform/target/org.fusesource.ide.targetplatform.target.repo/../../../../../jbtools/github/jbosstools-server/as/plugins/org.jboss.tools.as.catalog/schema/xsd/jboss-ejb3-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." > The schema seems to fail to resolve any elements that have 'jboss' in them, for example: > {code} > <xs:element name="enterprise-beans" type="javaee:jboss-enterprise-beansType"/> > {code} > When looking at the entire xsd space, I see no attempt to reference or import any remote schema or any jboss schema url or namespace. > The offending schema file is here: > {code}<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" > targetNamespace="http://www.jboss.com/xml/ns/javaee" > xmlns="http://www.jboss.com/xml/ns/javaee" > xmlns:javaee="http://java.sun.com/xml/ns/javaee" > elementFormDefault="qualified" > attributeFormDefault="unqualified" > version="2.0"> >  >  > <xs:import namespace="http://java.sun.com/xml/ns/javaee"/> > <xs:element name="ejb" type="javaee:jboss-ejb-beanType"/> > <xs:element name="ejb-jar" type="javaee:jboss-ejb-jarType"/> > <xs:element name="enterprise-beans" type="javaee:jboss-enterprise-beansType"/> > <xs:element name="destination-jndi-name" type="xs:string" /> > <xs:element name="distinct-name" type="xs:string"> > <xs:annotation> > <xs:documentation> > The distinct-name for this EJB module. > </xs:documentation> > </xs:annotation> > </xs:element> > </xs:schema> > {code} > Perhaps I'm not understanding xml enough, but I kinda agree with the validator here, in that there's no clear way to resolve any of the jboss-* elements. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20468) [FeedHenry] CordovaApp doesn't talk to FH cloud with cordova.js >= 4.0.0

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20468?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20468: ------------------------------- Fix Version/s: 4.4.0.Alpha2 (was: 4.4.0.Alpha1) > [FeedHenry] CordovaApp doesn't talk to FH cloud with cordova.js >= 4.0.0 > ------------------------------------------------------------------------ > > Key: JBIDE-20468 > URL: https://issues.jboss.org/browse/JBIDE-20468 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.3.0.Beta2 > Reporter: Pavol Srna > Assignee: Gorkem Ercan > Priority: Critical > Fix For: 4.3.x, 4.4.0.Alpha2 > > Attachments: remote.png, scree-fh-browsersim.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21134) Move easymport plugins from playground component

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21134?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21134: ------------------------------- Fix Version/s: 4.4.0.Alpha2 (was: 4.4.0.Alpha1) > Move easymport plugins from playground component > ------------------------------------------------ > > Key: JBIDE-21134 > URL: https://issues.jboss.org/browse/JBIDE-21134 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: easymport > Affects Versions: 4.4.0.Alpha1 > Reporter: Lucia Jelinkova > Assignee: Mickael Istria > Fix For: 4.4.0.Alpha2 > > > Easymport is in the default installation of JBDS so it might be time to move it from playground component? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20996) DV 6.2 is shipped withou EAP. Can we do something about it in context of Download Runtime wizard?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20996?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20996: ------------------------------- Fix Version/s: 4.4.0.Alpha2 (was: 4.4.0.Alpha1) > DV 6.2 is shipped withou EAP. Can we do something about it in context of Download Runtime wizard? > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-20996 > URL: https://issues.jboss.org/browse/JBIDE-20996 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: runtime-detection > Affects Versions: 4.3.0.Final > Reporter: Radim Hopp > Assignee: Rob Stryker > Fix For: 4.4.0.Alpha2 > > > It's great that now, with JBIDE-19852 and JBIDE-20769 resolved, one can download DV 6.2 using Download Runtimes wizard and have the installation path pre-filled. But the DV 6.2 installator requires EAP 6.4 already present on user's machine (and the installation path must point to its JBOSS_HOME). If user does not have EAP 6.4, he has to exit wizard, install EAP 6.4 and then download (again) and install DV 6.2. > Is there anything we could do to make this workflow easier. > Maybe at least tell user to install EAP 6.4 prior downloading DV 6.2? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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 May 2016