September 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-18316) Errors in project after import WildFly quickstarts (bundled XSD)

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18316?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-18316: --------------------------------------- [~maxandersen] I suggest we detach this issue from JBDS-2919 Epic. Ok for you ? > Errors in project after import WildFly quickstarts (bundled XSD) > ---------------------------------------------------------------- > > Key: JBIDE-18316 > URL: https://issues.jboss.org/browse/JBIDE-18316 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, upstream > Affects Versions: 4.2.0.Beta3 > Reporter: Xavier Coulon > Assignee: Max Rydahl Andersen > Priority: Critical > Fix For: 4.3.x > > > 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 (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18316) Errors in project after import WildFly quickstarts (bundled XSD)

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18316?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-18316: --------------------------------------- moving to {{4.3.x}} and {{upstream}} component because the validation problem seems to be at Eclipse WTP level, from what I and [~rob.stryker] could find: the following file {code} <jboss:ejb-jar xmlns:jboss="http://www.jboss.com/xml/ns/javaee" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:s="urn:security" xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd" version="3.1" impl-version="2.0"> <enterprise-beans> </enterprise-beans> <assembly-descriptor> </assembly-descriptor> </jboss:ejb-jar> {code} use an explicit schemaLocation, {{http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd}} and it seems that in that case, Eclipse WTP is not able to import the {{javaee_6.xsd}} file from {code} <xsd:include schemaLocation="javaee_6.xsd"/> {code} This seems to be in relation with https://bugs.eclipse.org/bugs/show_bug.cgi?id=315741 > Errors in project after import WildFly quickstarts (bundled XSD) > ---------------------------------------------------------------- > > Key: JBIDE-18316 > URL: https://issues.jboss.org/browse/JBIDE-18316 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, upstream > Affects Versions: 4.2.0.Beta3 > Reporter: Xavier Coulon > Assignee: Max Rydahl Andersen > Priority: Critical > Fix For: 4.3.x > > > 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 (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18444) jst.web.kb should not depend on org.codehaus.plexus.util

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18444?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-18444: -------------------------------- Description: On my local environment using m2e 1.6, I see some failure starting eclipse : {noformat} Unresolved requirement: Require-Bundle: org.jboss.tools.jst.web.kb; visibility:="reexport" -> Bundle-SymbolicName: org.jboss.tools.jst.web.kb; bundle-version="3.6.0.CR1-v20140711-0354-B645"; singleton:="true" org.jboss.tools.jst.web.kb [989] Unresolved requirement: Import-Package: org.codehaus.plexus.util {noformat} plexus is provided by the m2e runtime, so should not be a dependency of jst (which was added by this [commit|https://github.com/jbosstools/jbosstools-jst/commit/cd919ad62f2d5b...]). Apache commons-io should be used insted, as it is available in eclipse orbit. It provides the same capabilities. I'm not entirely sure why I see the error in my workspace, plexus should be available, but the real point here, is that this dependency should never be there in the first place. was: On my local environment using m2e 1.6, I see some failure starting eclipse : {noformat} Unresolved requirement: Require-Bundle: org.jboss.tools.jst.web.kb; visibility:="reexport" -> Bundle-SymbolicName: org.jboss.tools.jst.web.kb; bundle-version="3.6.0.CR1-v20140711-0354-B645"; singleton:="true" org.jboss.tools.jst.web.kb [989] Unresolved requirement: Import-Package: org.codehaus.plexus.util {noformat} plexus is provided by the m2e runtime, so should not be a dependency of jst. Apache commons-io should be used insted, as it is available in eclipse orbit. It provides the same capabilities. I'm not entirely sure why I see the error in my workspace, plexus should be available, but the real point here, is that this dependency should never be there in the first place. > jst.web.kb should not depend on org.codehaus.plexus.util > -------------------------------------------------------- > > Key: JBIDE-18444 > URL: https://issues.jboss.org/browse/JBIDE-18444 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.2.0.CR1 > Reporter: Fred Bricon > > On my local environment using m2e 1.6, I see some failure starting eclipse : > {noformat} > Unresolved requirement: Require-Bundle: org.jboss.tools.jst.web.kb; visibility:="reexport" > -> Bundle-SymbolicName: org.jboss.tools.jst.web.kb; bundle-version="3.6.0.CR1-v20140711-0354-B645"; singleton:="true" > org.jboss.tools.jst.web.kb [989] > Unresolved requirement: Import-Package: org.codehaus.plexus.util > {noformat} > plexus is provided by the m2e runtime, so should not be a dependency of jst (which was added by this [commit|https://github.com/jbosstools/jbosstools-jst/commit/cd919ad62f2d5b...]). > Apache commons-io should be used insted, as it is available in eclipse orbit. It provides the same capabilities. > I'm not entirely sure why I see the error in my workspace, plexus should be available, but the real point here, is that this dependency should never be there in the first place. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18444) jst.web.kb should not depend on org.codehaus.plexus.util

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-18444: ----------------------------------- Summary: jst.web.kb should not depend on org.codehaus.plexus.util Key: JBIDE-18444 URL: https://issues.jboss.org/browse/JBIDE-18444 Project: Tools (JBoss Tools) Issue Type: Bug Components: common/jst/core Affects Versions: 4.2.0.CR1 Reporter: Fred Bricon On my local environment using m2e 1.6, I see some failure starting eclipse : {noformat} Unresolved requirement: Require-Bundle: org.jboss.tools.jst.web.kb; visibility:="reexport" -> Bundle-SymbolicName: org.jboss.tools.jst.web.kb; bundle-version="3.6.0.CR1-v20140711-0354-B645"; singleton:="true" org.jboss.tools.jst.web.kb [989] Unresolved requirement: Import-Package: org.codehaus.plexus.util {noformat} plexus is provided by the m2e runtime, so should not be a dependency of jst. Apache commons-io should be used insted, as it is available in eclipse orbit. It provides the same capabilities. I'm not entirely sure why I see the error in my workspace, plexus should be available, but the real point here, is that this dependency should never be there in the first place. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18316) Errors in project after import WildFly quickstarts (bundled XSD)

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18316?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-18316: ---------------------------------- Component/s: upstream > Errors in project after import WildFly quickstarts (bundled XSD) > ---------------------------------------------------------------- > > Key: JBIDE-18316 > URL: https://issues.jboss.org/browse/JBIDE-18316 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, upstream > Affects Versions: 4.2.0.Beta3 > Reporter: Xavier Coulon > Assignee: Max Rydahl Andersen > Priority: Critical > Fix For: 4.3.x > > > 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 (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18316) Errors in project after import WildFly quickstarts (bundled XSD)

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18316?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-18316: ---------------------------------- Fix Version/s: 4.3.x (was: 4.2.0.CR2) > Errors in project after import WildFly quickstarts (bundled XSD) > ---------------------------------------------------------------- > > Key: JBIDE-18316 > URL: https://issues.jboss.org/browse/JBIDE-18316 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta3 > Reporter: Xavier Coulon > Assignee: Max Rydahl Andersen > Priority: Critical > Fix For: 4.3.x > > > 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 (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-330) verify JBTIS 4.2 refers to devstudio.redhat.com instead of deprecated domain devstudio.jboss.com

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-330?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBTIS-330: ----------------------------- Summary: verify JBTIS 4.2 refers to devstudio.redhat.com instead of deprecated domain devstudio.jboss.com (was: verify JBTIS for luna have its references to devstudio.jboss.com updated to devstudio.redhat.com) > verify JBTIS 4.2 refers to devstudio.redhat.com instead of deprecated domain devstudio.jboss.com > ------------------------------------------------------------------------------------------------ > > Key: JBTIS-330 > URL: https://issues.jboss.org/browse/JBTIS-330 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution, target-platform, testing > Affects Versions: 4.2.0.Alpha1 > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > > devstudio.jboss.com is deprecated and devstudio.redhat.com is the new host name for update sites. > This jira is just to do a check that all references to the server be updated to use *devstudio.redhat.com* instead of devstudio.jboss.com, but ONLY for devstudio 8 and later. > devstudio.jboss.com will still continue to exist (it is a cname of devstudio.redhat.com) thus older versions are not required or recommended to update. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-330) verify JBTIS 4.2 refers to devstudio.redhat.com instead of deprecated domain devstudio.jboss.com

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-330?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBTIS-330: ----------------------------- Affects Version/s: 4.2.0.Alpha1 > verify JBTIS 4.2 refers to devstudio.redhat.com instead of deprecated domain devstudio.jboss.com > ------------------------------------------------------------------------------------------------ > > Key: JBTIS-330 > URL: https://issues.jboss.org/browse/JBTIS-330 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution, target-platform, testing > Affects Versions: 4.2.0.Alpha1 > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > > devstudio.jboss.com is deprecated and devstudio.redhat.com is the new host name for update sites. > This jira is just to do a check that all references to the server be updated to use *devstudio.redhat.com* instead of devstudio.jboss.com, but ONLY for devstudio 8 and later. > devstudio.jboss.com will still continue to exist (it is a cname of devstudio.redhat.com) thus older versions are not required or recommended to update. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-330) verify JBTIS for luna have its references to devstudio.jboss.com updated to devstudio.redhat.com

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-330?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBTIS-330: ----------------------------- Description: devstudio.jboss.com is deprecated and devstudio.redhat.com is the new host name for update sites. This jira is just to do a check that all references to the server be updated to use *devstudio.redhat.com* instead of devstudio.jboss.com, but ONLY for devstudio 8 and later. devstudio.jboss.com will still continue to exist (it is a cname of devstudio.redhat.com) thus older versions are not required or recommended to update. was: devstudio.jboss.com is being "deprecated" and devstudio.redhat.com is the new host to use for things related to updatesites. This jira is just to do acheck that you get updatesite, docs,etc. updated to use devstudio.redhat.com instead of devstudio.jboss.com - note this is only required for things related to devstudio 8 and onwards. devstudio.jboss.com will still continue to exist (its cname of devstudio.redhat.com) thus older versions not required nor recommended to update to keep things clearly separated. > verify JBTIS for luna have its references to devstudio.jboss.com updated to devstudio.redhat.com > ------------------------------------------------------------------------------------------------ > > Key: JBTIS-330 > URL: https://issues.jboss.org/browse/JBTIS-330 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution, target-platform, testing > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > > devstudio.jboss.com is deprecated and devstudio.redhat.com is the new host name for update sites. > This jira is just to do a check that all references to the server be updated to use *devstudio.redhat.com* instead of devstudio.jboss.com, but ONLY for devstudio 8 and later. > devstudio.jboss.com will still continue to exist (it is a cname of devstudio.redhat.com) thus older versions are not required or recommended to update. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3128) verify JBTIS for luna have its references to devstudio.jboss.com updated to devstudio.redhat.com

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3128?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3128: ----------------------------- Parent: (was: JBDS-3009) Issue Type: Task (was: Sub-task) > verify JBTIS for luna have its references to devstudio.jboss.com updated to devstudio.redhat.com > ------------------------------------------------------------------------------------------------ > > Key: JBDS-3128 > URL: https://issues.jboss.org/browse/JBDS-3128 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: integration-platform > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > > devstudio.jboss.com is being "deprecated" and devstudio.redhat.com is the new host to use for things related to updatesites. > This jira is just to do acheck that you get updatesite, docs,etc. updated to use devstudio.redhat.com instead of devstudio.jboss.com - note this is only required for things related to devstudio 8 and onwards. > devstudio.jboss.com will still continue to exist (its cname of devstudio.redhat.com) thus older versions not required nor recommended to update to keep things clearly separated. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 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 September 2014