June 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24511) Errors occurred during the build.Errors running builder 'CDI (Contexts and Dependency Injection) Builder' on project 'fuse-camel-cbr'.Unknown tag! pos=18 poolCount = 48

by NITISH NAWAL (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24511?page=com.atlassian.jira.plugi... ] NITISH NAWAL commented on JBIDE-24511: -------------------------------------- I am using windows 10 and fuse 6.3... after installing fuse on my system i tried to create a bundle and this issue encountered... > Errors occurred during the build.Errors running builder 'CDI (Contexts and Dependency Injection) Builder' on project 'fuse-camel-cbr'.Unknown tag! pos=18 poolCount = 48 > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-24511 > URL: https://issues.jboss.org/browse/JBIDE-24511 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Reporter: NITISH NAWAL > Fix For: 4.5.x > > Attachments: 12.png > > > Errors occurred during the build. > Errors running builder 'CDI (Contexts and Dependency Injection) Builder' on project 'fuse-camel-cbr'. > Unknown tag! pos=18 poolCount = 48 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24548) Server adapter: Automatic syncing of code with the pod doesn't work with Wildfly

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24548?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-24548: ------------------------------------- Sprint: devex #134 Jun 2017 (was: devex #133 Jun 2017) > Server adapter: Automatic syncing of code with the pod doesn't work with Wildfly > -------------------------------------------------------------------------------- > > Key: JBIDE-24548 > URL: https://issues.jboss.org/browse/JBIDE-24548 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.Final > Environment: Running on Mac 10.12.4 > JBDS > Version: 10.3.0.GA > Build id: GA-v20170218-1636-B94 > Build date: 20170218-1636 > Installed minishift v1.0.1 > Reporter: Veer Muchandi > Assignee: Dmitrii Bocharov > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.5.0.AM2 > > > * Created a Wildfly application on openshift web-ui > * Setup a server adapter > * Imported application to JBDS > * Made code changes and saved. > Result: > While the data seems to be exchanged, the changes are not synced with the pod and the application is not updated. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4451) What is the official name of JBoss Fuse?

by Lars Heinemann (JIRA)

[ https://issues.jboss.org/browse/JBDS-4451?page=com.atlassian.jira.plugin.... ] Lars Heinemann commented on JBDS-4451: -------------------------------------- If we are talking about the runtime side then the name is "JBoss Fuse". If we talk about the Eclipse Tooling then the name is "JBoss Fuse Tooling". What Andrej probably meant is that our repo name changed from fuseide to jbosstools-fuse. Keep in mind those are product names. Our community repo and Jira project have different naming. > What is the official name of JBoss Fuse? > ---------------------------------------- > > Key: JBDS-4451 > URL: https://issues.jboss.org/browse/JBDS-4451 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: fuse-tooling > Affects Versions: 11.0.0.AM2 > Reporter: Lukáš Valach > Priority: Minor > Fix For: 11.0.0.AM2 > > > Recently, the JBoss Fuse was migrated from IS to JBDS. [~apodhrad] said that there was a discusion about renaming Fuse during the migration. > I have noticed that we are using couple of different names for Fuse. > JBDS -> Help -> Install New Software: *Red Hat JBoss Fuse Tools* > Jar installer -> Select Additional Features: *JBoss Fuse Tools* > Jar installer -> Summary Information: *Red Hat JBoss Fuse Developement* > [www.redhat.com|https://www.redhat.com/en/technologies/jboss-middleware/fuse]: *Red Hat JBoss Fuse* > [Product page|https://pp.engineering.redhat.com/pp/product/jbds/release/jbds-10-0/...]: *Red Hat JBoss Fuse* > So, what is the official name of Fuse? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4451) What is the official name of JBoss Fuse?

by Lukáš Valach (JIRA)

Lukáš Valach created JBDS-4451: ---------------------------------- Summary: What is the official name of JBoss Fuse? Key: JBDS-4451 URL: https://issues.jboss.org/browse/JBDS-4451 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Task Components: fuse-tooling Affects Versions: 11.0.0.AM2 Reporter: Lukáš Valach Priority: Minor Fix For: 11.0.0.AM2 Recently, the JBoss Fuse was migrated from IS to JBDS. [~apodhrad] said that there was a discusion about renaming Fuse during the migration. I have noticed that we are using couple of different names for Fuse. JBDS -> Help -> Install New Software: *Red Hat JBoss Fuse Tools* Jar installer -> Select Additional Features: *JBoss Fuse Tools* Jar installer -> Summary Information: *Red Hat JBoss Fuse Developement* [www.redhat.com|https://www.redhat.com/en/technologies/jboss-middleware/fuse]: *Red Hat JBoss Fuse* [Product page|https://pp.engineering.redhat.com/pp/product/jbds/release/jbds-10-0/...]: *Red Hat JBoss Fuse* So, what is the official name of Fuse? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24289) Update JBoss Tools features page

by Lars Heinemann (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24289?page=com.atlassian.jira.plugi... ] Lars Heinemann commented on JBIDE-24289: ---------------------------------------- Are these pages still actively maintained? I thought everything moves to Red Hat Developer site? > Update JBoss Tools features page > -------------------------------- > > Key: JBIDE-24289 > URL: https://issues.jboss.org/browse/JBIDE-24289 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: website > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Lars Heinemann > Fix For: 4.5.0.AM2 > > > Once Fuse Tooling is in JBT, we'll have to update http://tools.jboss.org/features/index.html to reflect that fact. > See https://github.com/jbosstools/jbosstools-website/blob/master/features/apa... for source of the page to update. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18316) Errors in project after import WildFly quickstarts (bundled jboss-ejb3-2_0.xsd)

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18316?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-18316: -------------------------------- Fix Version/s: LATER (was: 4.4.x) Bulk move all schema issues to 'LATER' because they take a lot of time to re-verify and they rarely make any progress. :| > Errors in project after import WildFly quickstarts (bundled jboss-ejb3-2_0.xsd) > ------------------------------------------------------------------------------- > > Key: JBIDE-18316 > URL: https://issues.jboss.org/browse/JBIDE-18316 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server, upstream > Affects Versions: 4.2.0.Beta3 > Reporter: Xavier Coulon > Assignee: Rob Stryker > Priority: Critical > Fix For: LATER > > > After importing all modules from https://github.com/wildfly/quickstart into JBDS 8.0.0.CR1b, a few projects have errors because of XML validation, such as: > {code} > Referenced file contains errors (jar:file:/Users/xcoulon/DevToolz/ide/jbossdevstudio800CR1b/studio/plugins/org.jboss.tools.as.catalog_3.0.0.CR1-v20140905-1648-B75.jar!/schema/xsd/jboss-ejb3-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22055) Import spring-petclinic validation errors

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22055?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-22055: -------------------------------- Fix Version/s: LATER (was: 4.4.x) Bulk move all schema issues to 'LATER' because they take a lot of time to re-verify and they rarely make any progress. :| > Import spring-petclinic validation errors > ------------------------------------------ > > Key: JBIDE-22055 > URL: https://issues.jboss.org/browse/JBIDE-22055 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: project-examples > Affects Versions: 4.3.1.CR1 > Reporter: Josef Kopriva > Assignee: Rob Stryker > Fix For: LATER > > > Importing of spring-petclinic is with XSD errors: > Open quote is expected for attribute "border" associated with an element type "img". index.html /jboss-spring-petclinic/src/main/webapp/vendors/jquery/speed line 65 > The content of elements must consist of well-formed character data or markup. index.html /jboss-spring-petclinic/src/main/webapp/vendors/jquery/test line 44 > XML document structures must start and end within the same entity. localfile.html /jboss-spring-petclinic/src/main/webapp/vendors/jquery/test line 76 > The element type "meta" must be terminated by the matching end-tag "</meta>". absolute.html /jboss-spring-petclinic/src/main/webapp/vendors/jquery/test/data/offset line 29 > The element type "meta" must be terminated by the matching end-tag "</meta>". body.html /jboss-spring-petclinic/src/main/webapp/vendors/jquery/test/data/offset line 21 > The element type "meta" must be terminated by the matching end-tag "</meta>". fixed.html /jboss-spring-petclinic/src/main/webapp/vendors/jquery/test/data/offset line 25 > The element type "meta" must be terminated by the matching end-tag "</meta>". relative.html /jboss-spring-petclinic/src/main/webapp/vendors/jquery/test/data/offset line 24 > The element type "meta" must be terminated by the matching end-tag "</meta>". scroll.html /jboss-spring-petclinic/src/main/webapp/vendors/jquery/test/data/offset line 28 > The element type "meta" must be terminated by the matching end-tag "</meta>". static.html /jboss-spring-petclinic/src/main/webapp/vendors/jquery/test/data/offset line 24 > The element type "meta" must be terminated by the matching end-tag "</meta>". table.html /jboss-spring-petclinic/src/main/webapp/vendors/jquery/test/data/offset line 22 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22180) Import wildfly-contacts-jquerymobile XML problem

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22180?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-22180: -------------------------------- Fix Version/s: LATER (was: 4.4.x) Bulk move all schema issues to 'LATER' because they take a lot of time to re-verify and they rarely make any progress. :| > Import wildfly-contacts-jquerymobile XML problem > ------------------------------------------------ > > Key: JBIDE-22180 > URL: https://issues.jboss.org/browse/JBIDE-22180 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: project-examples > Affects Versions: 4.3.1.CR1 > Reporter: Josef Kopriva > Assignee: Rob Stryker > Fix For: LATER > > > Erron when importing wildfly-contacts-jquerymobile quickstart: > {code:java} > cvc-complex-type.2.4.a: Invalid content was found starting with element 'relativePath'. One of '{"http://maven.apache.org/POM/4.0.0":parent, > "http://maven.apache.org/POM/4.0.0":packaging, "http://maven.apache.org/POM/4.0.0":name, "http://maven.apache.org/POM/4.0.0":description, > "http://maven.apache.org/POM/4.0.0":url, "http://maven.apache.org/POM/4.0.0":prerequisites, "http://maven.apache.org/POM/4.0.0":issueManagement, > "http://maven.apache.org/POM/4.0.0":ciManagement, "http://maven.apache.org/POM/4.0.0":inceptionYear, > "http://maven.apache.org/POM/4.0.0":mailingLists, "http://maven.apache.org/POM/4.0.0":developers, "http://maven.apache.org/POM/4.0.0":contributors, > "http://maven.apache.org/POM/4.0.0":licenses, "http://maven.apache.org/POM/4.0.0":scm, "http://maven.apache.org/POM/4.0.0":organization, > "http://maven.apache.org/POM/4.0.0":build, "http://maven.apache.org/POM/4.0.0":profiles, "http://maven.apache.org/POM/4.0.0":modules, > "http://maven.apache.org/POM/4.0.0":repositories, "http://maven.apache.org/POM/4.0.0":pluginRepositories, > "http://maven.apache.org/POM/4.0.0":dependencies, "http://maven.apache.org/POM/4.0.0":reports, "http://maven.apache.org/POM/4.0.0":reporting, > "http://maven.apache.org/POM/4.0.0":dependencyManagement, "http://maven.apache.org/POM/4.0.0":distributionManagement, > "http://maven.apache.org/POM/4.0.0":properties}' is expected. > pom.xml > /wildfly-contacts-jquerymobile/functional-tests line 23 > XML Problem > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

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

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20540?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-20540: -------------------------------- Fix Version/s: LATER (was: 4.4.x) Bulk move all schema issues to 'LATER' because they take a lot of time to re-verify and they rarely make any progress. :| > 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: LATER > > > See bug as described here: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=476274 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

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

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20536?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-20536: -------------------------------- Fix Version/s: LATER (was: 4.4.x) Bulk move all schema issues to 'LATER' because they take a lot of time to re-verify and they rarely make any progress. :| > 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: LATER > > > 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 (v7.2.3#72005)

8 years, 9 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 June 2017