[JBoss JIRA] (JBIDE-18576) Additional validation errors in WildFly quickstarts
by Jiri Peterka (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18576?page=com.atlassian.jira.plugi... ]
Jiri Peterka closed JBIDE-18576.
--------------------------------
closed (duplicate)
> Additional validation errors in WildFly quickstarts
> ---------------------------------------------------
>
> Key: JBIDE-18576
> URL: https://issues.jboss.org/browse/JBIDE-18576
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 4.2.0.CR2
> Reporter: Jiri Peterka
> Assignee: Xavier Coulon
> Fix For: 4.2.0.CR2
>
>
> When importing Wildfly quickstarts from https://github.com/wildfly/quickstart (master branch), there are still several validation errors:
> {code}
> Description Resource Path Location Type
> cvc-complex-type.2.4.a: Invalid content was found starting with element 'iiop:iiop'. One of '{"http://java.sun.com/xml/ns/javaee":security-role, "http://java.sun.com/xml/ns/javaee":method-permission, "http://java.sun.com/xml/ns/javaee":container-transaction, "http://java.sun.com/xml/ns/javaee":interceptor-binding, "http://java.sun.com/xml/ns/javaee":message-destination, "http://java.sun.com/xml/ns/javaee":exclude-list, "http://java.sun.com/xml/ns/javaee":application-exception, "http://java.sun.com/xml/ns/javaee":assembly-descriptor-entry}' is expected. jboss-ejb3.xml /wildfly-jts-application-component-2/src/main/resources/META-INF line 28 XML Problem
> cvc-complex-type.2.4.a: Invalid content was found starting with element 'jee:interceptor-binding'. One of '{"http://java.sun.com/xml/ns/javaee":description, "http://java.sun.com/xml/ns/javaee":ejb-name}' is expected. jboss-ejb3.xml /wildfly-ejb-security-interceptors/src/main/resources/META-INF line 26 XML Problem
> cvc-complex-type.2.4.a: Invalid content was found starting with element 'jee:interceptor-binding'. One of '{"http://java.sun.com/xml/ns/javaee":description, "http://java.sun.com/xml/ns/javaee":ejb-name}' is expected. jboss-ejb3.xml /wildfly-ejb-security-plus/src/main/resources/META-INF line 26 XML Problem
> cvc-elt.1: Cannot find the declaration of element 'jboss'. jboss-ejb3.xml /wildfly-ejb-security-interceptors/src/main/resources/META-INF line 20 XML Problem
> cvc-elt.1: Cannot find the declaration of element 'jboss'. jboss-ejb3.xml /wildfly-ejb-security-plus/src/main/resources/META-INF line 20 XML Problem
> Endorsed directory '/home/jpeterka/data/repo/github.com/wildfly/quickstart/ejb-multi-server/app-main/web/target/endorsed' is missing. You may need to a perform a Maven command line build in order to create it. pom.xml /jboss-ejb-multi-server-app-main-web line 110 Maven Configuration Problem
> Referenced file contains errors (jar:file:/home/jpeterka/data/ide/test/jbds8cr2/studio/plugins/org.jboss.tools.as.catalog_3.0.0.CR2-v20141003-1627-B87.jar!/schema/xsd/jboss-ejb3-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." jboss-ejb3.xml /jboss-ejb-multi-server-app-one-ejb/src/main/resources/META-INF line 1 XML Problem
> Referenced file contains errors (jar:file:/home/jpeterka/data/ide/test/jbds8cr2/studio/plugins/org.jboss.tools.as.catalog_3.0.0.CR2-v20141003-1627-B87.jar!/schema/xsd/jboss-ejb3-spec-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." jboss-ejb3.xml /wildfly-ejb-security-interceptors/src/main/resources/META-INF line 1 XML Problem
> Referenced file contains errors (jar:file:/home/jpeterka/data/ide/test/jbds8cr2/studio/plugins/org.jboss.tools.as.catalog_3.0.0.CR2-v20141003-1627-B87.jar!/schema/xsd/jboss-ejb3-spec-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." jboss-ejb3.xml /wildfly-ejb-security-plus/src/main/resources/META-INF line 1 XML Problem
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (JBDS-3191) Improve the way we switch between development and GA
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBDS-3191?page=com.atlassian.jira.plugin.... ]
Mickael Istria commented on JBDS-3191:
--------------------------------------
{quote}Please note that the first line item in the release guide for JBDS 8 milestones...{quote}
Ok, but in that case, I only followed the "staging" document. And this step you mention is more about preparing the build for a .GA candidate. This should be mentioned earlier, at least at the beginning of the Staging documentation.
{quote}Having the stable site in there from day 1 (I assume you mean the day Beta1 is pushed to https://www.jboss.org/products/devstudio ) will mean that everyone using the Betas won't be able to see updates, and won't be able to automatically move up to CR or GA.{quote}
The idea isn't to populate the final URL from day 1, but reference it systematically, even if it is empty.
{quote}I think it's better to define maven enforcer rules which run at build-time to cause the build to fail if parent pom version is Final and the above files still contain development milestone (not release/stable) URLs. {quote}
Compared to the startup extension looking at version of com.jboss.devstudio.core feature to decide how to populate the available sites?
If yes, what are the benfit/inconvenients of one approach on the other.
What I see as a benefit of having it at runtime using regular Eclipse code is that anyone could contribute patches to this piece of code. Also, if we drop Maven one day, it would still work. It's even testable from the IDE. Another benefit is that if this is well implemented, we'll never need to change again. Whereas even if we have an enforcer rule but still rely on properties in pom files, we'll have to make a commit to change stuff in pom or to tweak a CI job.
> Improve the way we switch between development and GA
> ----------------------------------------------------
>
> Key: JBDS-3191
> URL: https://issues.jboss.org/browse/JBDS-3191
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Components: build
> Reporter: Mickael Istria
>
> JBDS-3190 has shown that there are too many changes to perform when willing to create a GA candidate, and it's almost certain that we'll forever forget to change one or some of them when switching between GA and development stream.
> We need to improve that.
> Changes are necessary in:
> * features/com.jboss.devstudio.core/feature/p2.inf
> * site/associate.properties
> * results/pom.xml
> As an alternative, I suggest that the final site be ALWAYS added to the referenced site, even if it's empty. This has no cost for build nor user, and this would simplify a few things here and there.
> Also, instead of a p2.inf, we could think a a "startup" extension that would add reference to development site in case qualifier for the feature doesn't contain GA.
> The property to the "current site" (GA or development) could be factorized in JBDS parent pom. so that both results/pom.xml and site/pom.xml could use it (instead of associateSites.properties).
> CC [~nickboldt] [~maxandersen]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (JBDS-3191) Improve the way we switch between development and GA
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3191?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-3191 at 10/20/14 8:44 AM:
------------------------------------------------------------
Please note that the first line item in the release guide for JBDS 8 milestones is (re: JBDS-3190):
{quote}
TODO: when releasing GA make sure to :%s/development/stable/g and :%s/8.0-staging/8.0/g in product/features/com.jboss.jbds.product.feature/p2.inf
{quote}
Having the stable site in there from day 1 (I assume you mean the day Beta1 is pushed to https://www.jboss.org/products/devstudio ) will mean that everyone using the Betas won't be able to see updates, and won't be able to automatically move up to CR or GA.
Alternatively, if you add BOTH the release site and the milestone site, you still need to configure p2.inf to remove the development site when updating to GA from an earlier milestone. And worse, Max will complain that there are too many sites listed in the Available Software Sites view. :D
I think it's better to define maven enforcer rules which run at build-time to cause the build to fail if parent pom version is Final and the above files still contain development milestone (not release/stable) URLs.
But yes, factorizing the update site URL (https://devstudio.redhat.com/updates/8.0-development/ or https://devstudio.redhat.com/updates/8.0/ ) into a single variable is a good idea.
was (Author: nickboldt):
Please note that the first line item in the release guide for JBDS 8 milestones is (re: JBDS-3190):
{quote}
TODO: when releasing GA make sure to :%s/development/stable/g and :%s/8.0-staging/8.0/g in product/features/com.jboss.jbds.product.feature/p2.inf
{quote}
Having the stable site in there from day 1 (I assume you mean the day Beta1 is pushed to https://www.jboss.org/products/devstudio ) will mean that everyone using the Betas won't be able to see updates, and won't be able to automatically move up to CR or GA.
I think it's better to define maven enforcer rules which run at build-time to cause the build to fail if parent pom version is Final and the above files still contain development milestone (not release/stable) URLs.
But yes, factorizing the update site URL (https://devstudio.redhat.com/updates/8.0-development/ or https://devstudio.redhat.com/updates/8.0/ ) into a single variable is a good idea.
> Improve the way we switch between development and GA
> ----------------------------------------------------
>
> Key: JBDS-3191
> URL: https://issues.jboss.org/browse/JBDS-3191
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Components: build
> Reporter: Mickael Istria
>
> JBDS-3190 has shown that there are too many changes to perform when willing to create a GA candidate, and it's almost certain that we'll forever forget to change one or some of them when switching between GA and development stream.
> We need to improve that.
> Changes are necessary in:
> * features/com.jboss.devstudio.core/feature/p2.inf
> * site/associate.properties
> * results/pom.xml
> As an alternative, I suggest that the final site be ALWAYS added to the referenced site, even if it's empty. This has no cost for build nor user, and this would simplify a few things here and there.
> Also, instead of a p2.inf, we could think a a "startup" extension that would add reference to development site in case qualifier for the feature doesn't contain GA.
> The property to the "current site" (GA or development) could be factorized in JBDS parent pom. so that both results/pom.xml and site/pom.xml could use it (instead of associateSites.properties).
> CC [~nickboldt] [~maxandersen]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (JBDS-3191) Improve the way we switch between development and GA
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3191?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3191:
-----------------------------
Description:
JBDS-3190 has shown that there are too many changes to perform when willing to create a GA candidate, and it's almost certain that we'll forever forget to change one or some of them when switching between GA and development stream.
We need to improve that.
Changes are necessary in:
* features/com.jboss.devstudio.core/feature/p2.inf
* site/associate.properties
* results/pom.xml
As an alternative, I suggest that the final site be ALWAYS added to the referenced site, even if it's empty. This has no cost for build nor user, and this would simplify a few things here and there.
Also, instead of a p2.inf, we could think a a "startup" extension that would add reference to development site in case qualifier for the feature doesn't contain GA.
The property to the "current site" (GA or development) could be factorized in JBDS parent pom. so that both results/pom.xml and site/pom.xml could use it (instead of associateSites.properties).
CC [~nickboldt] [~maxandersen]
was:
JBDS-3190 has shown that there are too many changes to perform when willing to create a GA candidate, and it's almost certain that we'll forever forget to change one or some of them when switching between GA and development stream.
We need to improve that.
Changes are necessary in:
* features/com.jboss.devstudio.core/feature/p2.inf
* site/associateSites.properties
* results/pom.xml
As an alternative, I suggest that the final site be ALWAYS added to the referenced site, even if it's empty. This has no cost for build nor user, and this would simplify a few things here and there.
Also, instead of a p2.inf, we could think a a "startup" extension that would add reference to development site in case qualifier for the feature doesn't contain GA.
The property to the "current site" (GA or development) could be factorized in JBDS parent pom. so that both results/pom.xml and site/pom.xml could use it (instead of associateSites.properties).
CC [~nickboldt] [~maxandersen]
> Improve the way we switch between development and GA
> ----------------------------------------------------
>
> Key: JBDS-3191
> URL: https://issues.jboss.org/browse/JBDS-3191
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Components: build
> Reporter: Mickael Istria
>
> JBDS-3190 has shown that there are too many changes to perform when willing to create a GA candidate, and it's almost certain that we'll forever forget to change one or some of them when switching between GA and development stream.
> We need to improve that.
> Changes are necessary in:
> * features/com.jboss.devstudio.core/feature/p2.inf
> * site/associate.properties
> * results/pom.xml
> As an alternative, I suggest that the final site be ALWAYS added to the referenced site, even if it's empty. This has no cost for build nor user, and this would simplify a few things here and there.
> Also, instead of a p2.inf, we could think a a "startup" extension that would add reference to development site in case qualifier for the feature doesn't contain GA.
> The property to the "current site" (GA or development) could be factorized in JBDS parent pom. so that both results/pom.xml and site/pom.xml could use it (instead of associateSites.properties).
> CC [~nickboldt] [~maxandersen]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (JBDS-3191) Improve the way we switch between development and GA
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3191?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3191:
----------------------------------
Please note that the first line item in the release guide for JBDS 8 milestones is (re: JBDS-3190):
{quote}
TODO: when releasing GA make sure to :%s/development/stable/g and :%s/8.0-staging/8.0/g in product/features/com.jboss.jbds.product.feature/p2.inf
{quote}
Having the stable site in there from day 1 (I assume you mean the day Beta1 is pushed to https://www.jboss.org/products/devstudio ) will mean that everyone using the Betas won't be able to see updates, and won't be able to automatically move up to CR or GA.
I think it's better to define maven enforcer rules which run at build-time to cause the build to fail if parent pom version is Final and the above files still contain development milestone (not release/stable) URLs.
But yes, factorizing the update site URL (https://devstudio.redhat.com/updates/8.0-development/ or https://devstudio.redhat.com/updates/8.0/ ) into a single variable is a good idea.
> Improve the way we switch between development and GA
> ----------------------------------------------------
>
> Key: JBDS-3191
> URL: https://issues.jboss.org/browse/JBDS-3191
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Components: build
> Reporter: Mickael Istria
>
> JBDS-3190 has shown that there are too many changes to perform when willing to create a GA candidate, and it's almost certain that we'll forever forget to change one or some of them when switching between GA and development stream.
> We need to improve that.
> Changes are necessary in:
> * features/com.jboss.devstudio.core/feature/p2.inf
> * site/associateSites.properties
> * results/pom.xml
> As an alternative, I suggest that the final site be ALWAYS added to the referenced site, even if it's empty. This has no cost for build nor user, and this would simplify a few things here and there.
> Also, instead of a p2.inf, we could think a a "startup" extension that would add reference to development site in case qualifier for the feature doesn't contain GA.
> The property to the "current site" (GA or development) could be factorized in JBDS parent pom. so that both results/pom.xml and site/pom.xml could use it (instead of associateSites.properties).
> CC [~nickboldt] [~maxandersen]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (JBDS-3189) AngularJS for Web Tools cannot be installed
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3189?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-3189:
--------------------------------------
Fix Version/s: 8.0.0.CR2
> AngularJS for Web Tools cannot be installed
> -------------------------------------------
>
> Key: JBDS-3189
> URL: https://issues.jboss.org/browse/JBDS-3189
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: central
> Affects Versions: 8.0.0.CR2
> Environment: JBDS 8.0.0.CR2b
> Reporter: Rastislav Wagner
> Assignee: Mickael Istria
> Priority: Blocker
> Labels: respin-c
> Fix For: 8.0.0.CR2
>
>
> {code}
> Cannot complete the install because of a conflicting dependency.
> Software being installed: JBoss Tools Java Standard Tools AngularJS 3.6.0.CR2-v20141003-2041-B74 (org.jboss.tools.jst.angularjs.feature.feature.group 3.6.0.CR2-v20141003-2041-B74)
> Software currently installed: JBoss Developer Studio (Branded Product) 8.0.0.GA-v20141017-1111-B314 (com.jboss.devstudio.core.package 8.0.0.GA-v20141017-1111-B314)
> Only one of the following can be installed at once:
> JBoss Tools Java Standard Tools - Tern Project Adapter 3.6.0.Final-v20141016-0045-B76 (org.jboss.tools.jst.jsdt 3.6.0.Final-v20141016-0045-B76)
> JBoss Tools Java Standard Tools - Tern Project Adapter 3.6.0.CR2-v20141003-2041-B74 (org.jboss.tools.jst.jsdt 3.6.0.CR2-v20141003-2041-B74)
> Cannot satisfy dependency:
> From: JBoss Developer Studio (Core Features) 8.0.0.GA-v20141017-1111-B314 (com.jboss.devstudio.core.feature.feature.group 8.0.0.GA-v20141017-1111-B314)
> To: org.jboss.tools.jst.jsdt.feature.feature.group [3.6.0.Final-v20141016-0045-B76]
> Cannot satisfy dependency:
> From: JBoss Developer Studio (Branded Product) 8.0.0.GA-v20141017-1111-B314 (com.jboss.devstudio.core.package 8.0.0.GA-v20141017-1111-B314)
> To: com.jboss.devstudio.core.feature.feature.group [8.0.0.GA-v20141017-1111-B314]
> Cannot satisfy dependency:
> From: JBoss Tools Java Standard Tools AngularJS 3.6.0.CR2-v20141003-2041-B74 (org.jboss.tools.jst.angularjs.feature.feature.group 3.6.0.CR2-v20141003-2041-B74)
> To: org.jboss.tools.jst.jsdt.feature.feature.group [3.6.0.CR2-v20141003-2041-B74]
> Cannot satisfy dependency:
> From: JBoss Tools Java Standard Tools Tern.java Adapter 3.6.0.CR2-v20141003-2041-B74 (org.jboss.tools.jst.jsdt.feature.feature.group 3.6.0.CR2-v20141003-2041-B74)
> To: org.jboss.tools.jst.jsdt [3.6.0.CR2-v20141003-2041-B74]
> Cannot satisfy dependency:
> From: JBoss Tools Java Standard Tools Tern.java Adapter 3.6.0.Final-v20141016-0045-B76 (org.jboss.tools.jst.jsdt.feature.feature.group 3.6.0.Final-v20141016-0045-B76)
> To: org.jboss.tools.jst.jsdt [3.6.0.Final-v20141016-0045-B76]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (JBDS-3189) AngularJS for Web Tools cannot be installed
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBDS-3189?page=com.atlassian.jira.plugin.... ]
Mickael Istria commented on JBDS-3189:
--------------------------------------
Issue is actually resolved, the the CDW workflow prevents me from keeping it Open and Resolved at the same time.
> AngularJS for Web Tools cannot be installed
> -------------------------------------------
>
> Key: JBDS-3189
> URL: https://issues.jboss.org/browse/JBDS-3189
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: central
> Affects Versions: 8.0.0.CR2
> Environment: JBDS 8.0.0.CR2b
> Reporter: Rastislav Wagner
> Assignee: Mickael Istria
> Priority: Blocker
> Labels: respin-c
>
> {code}
> Cannot complete the install because of a conflicting dependency.
> Software being installed: JBoss Tools Java Standard Tools AngularJS 3.6.0.CR2-v20141003-2041-B74 (org.jboss.tools.jst.angularjs.feature.feature.group 3.6.0.CR2-v20141003-2041-B74)
> Software currently installed: JBoss Developer Studio (Branded Product) 8.0.0.GA-v20141017-1111-B314 (com.jboss.devstudio.core.package 8.0.0.GA-v20141017-1111-B314)
> Only one of the following can be installed at once:
> JBoss Tools Java Standard Tools - Tern Project Adapter 3.6.0.Final-v20141016-0045-B76 (org.jboss.tools.jst.jsdt 3.6.0.Final-v20141016-0045-B76)
> JBoss Tools Java Standard Tools - Tern Project Adapter 3.6.0.CR2-v20141003-2041-B74 (org.jboss.tools.jst.jsdt 3.6.0.CR2-v20141003-2041-B74)
> Cannot satisfy dependency:
> From: JBoss Developer Studio (Core Features) 8.0.0.GA-v20141017-1111-B314 (com.jboss.devstudio.core.feature.feature.group 8.0.0.GA-v20141017-1111-B314)
> To: org.jboss.tools.jst.jsdt.feature.feature.group [3.6.0.Final-v20141016-0045-B76]
> Cannot satisfy dependency:
> From: JBoss Developer Studio (Branded Product) 8.0.0.GA-v20141017-1111-B314 (com.jboss.devstudio.core.package 8.0.0.GA-v20141017-1111-B314)
> To: com.jboss.devstudio.core.feature.feature.group [8.0.0.GA-v20141017-1111-B314]
> Cannot satisfy dependency:
> From: JBoss Tools Java Standard Tools AngularJS 3.6.0.CR2-v20141003-2041-B74 (org.jboss.tools.jst.angularjs.feature.feature.group 3.6.0.CR2-v20141003-2041-B74)
> To: org.jboss.tools.jst.jsdt.feature.feature.group [3.6.0.CR2-v20141003-2041-B74]
> Cannot satisfy dependency:
> From: JBoss Tools Java Standard Tools Tern.java Adapter 3.6.0.CR2-v20141003-2041-B74 (org.jboss.tools.jst.jsdt.feature.feature.group 3.6.0.CR2-v20141003-2041-B74)
> To: org.jboss.tools.jst.jsdt [3.6.0.CR2-v20141003-2041-B74]
> Cannot satisfy dependency:
> From: JBoss Tools Java Standard Tools Tern.java Adapter 3.6.0.Final-v20141016-0045-B76 (org.jboss.tools.jst.jsdt.feature.feature.group 3.6.0.Final-v20141016-0045-B76)
> To: org.jboss.tools.jst.jsdt [3.6.0.Final-v20141016-0045-B76]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months