February 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-19162) add new plugins to openshift pom and create feature

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19162?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19162: --------------------------------------------- [~nickboldt] this is no different than IS having Savara in tools but not in devstudio not that earlyaccess Angular connector installs additional plugin to non-earlyaccess angular. Same concept. we've done this before and will do so in future. And there are no different proxywizards for Openshift v2 or v3. It just means v3 is not enabled in JBDS for now. please remember that connector id != single features/plugins but more connector id = "plugins related to certain functionality" what we do not want is that devstudio using a *different* connection id for the same functionality as tools - this is what was initially suggested for JBTIS connectors and *that* would screw things up. Here we use the same connectorid and dependent on earlyacces or not, tools or devstudio what it can/will install is variable. > add new plugins to openshift pom and create feature > --------------------------------------------------- > > Key: JBIDE-19162 > URL: https://issues.jboss.org/browse/JBIDE-19162 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.3.0.Alpha1 > > > In JBIDE-19048 we created new plugins for the OpenShift v3 tooling and moved reusable parts to common plugins. We now need to get the maven build working (add the new modules) and create a v3 feature. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3345) Errors when starting FSW 6.0.0.GA from JBDS 8.0.2.GA with JDK 1.8

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3345?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3345: ------------------------------------------- So i'm not following what your error is. Title says you cannot start FSW 6.0 but the logs show a starting and running server. The error logs show that you got code deployed that is compiled with Java 8 (major.minor version 52.0) thus for me this looks like your project have been configured to compile with Java 8 giving you something that cannot run on FSW 6 if you run it with Java 7. Please make sure you have not mixed something that is incompatible or otherwise outline *exact* steps to reproduce this and with example project. > Errors when starting FSW 6.0.0.GA from JBDS 8.0.2.GA with JDK 1.8 > ----------------------------------------------------------------- > > Key: JBDS-3345 > URL: https://issues.jboss.org/browse/JBDS-3345 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: runtime > Affects Versions: 8.0.2.GA > Environment: Fedora 21 x86_64 > JBDS 8.0.2.GA with Oracle JDK 1.8.0_25 and Oracle JDK 1.7.0_71 > Reporter: Andrej Podhradsky > Priority: Critical > Attachments: errors.txt > > > FSW 6.0.0.GA supports java 6 and 7, so if we want to run this server on JBDS 8 with jdk 8 we need to add another jdk to the JBDS, e.g. jdk 7. But this doesn't work, see errors in the attached file. > Moreover, we are not able to stop the server from IDE, the process is still alive and we have to kill it manually. > Note that this happens only when we install JBDS 8.0.2 with jdk 8, if we install it with jdk 7 the server works fine. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17035) Simplify .md5 file names in products.yml

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17035?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-17035: ---------------------------------------- Fix Version/s: 4.3.0.Alpha2 (was: 4.3.0.Alpha1) bump to alpha 2 > Simplify .md5 file names in products.yml > ---------------------------------------- > > Key: JBIDE-17035 > URL: https://issues.jboss.org/browse/JBIDE-17035 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: website > Affects Versions: 4.2.0.Beta1 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.3.0.Alpha2 > > > Assuming the .md5 files have the same name as regular files (plus the '.md5' extension), we could avoid the file names duplication in products.yml -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18792) Add link to comments at the bottom of blog posts on /blog

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18792?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-18792: ---------------------------------------- Fix Version/s: 4.3.0.Alpha2 (was: 4.3.0.Alpha1) bump to alpha 2 > Add link to comments at the bottom of blog posts on /blog > --------------------------------------------------------- > > Key: JBIDE-18792 > URL: https://issues.jboss.org/browse/JBIDE-18792 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: website > Affects Versions: 4.2.0.Final > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.3.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19085) tools.jboss.org devstudio downloads does not mention it is update site content only and to use 8.0.0 installer

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19085?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-19085: ---------------------------------------- Fix Version/s: 4.3.0.Alpha2 (was: 4.3.0.Alpha1) bump to alpha 2 > tools.jboss.org devstudio downloads does not mention it is update site content only and to use 8.0.0 installer > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19085 > URL: https://issues.jboss.org/browse/JBIDE-19085 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: website > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > Fix For: 4.3.0.Alpha2 > > > from grdryn on irc: > "Hi folks, tools.jboss.org/downloads/ shows latest devstudio as 8.0.2.GA, but jboss.org/products/devstudio/download/ still lists 8.0.0.GA > ^Just FYI...I'm not sure if that's normal, or if the latter should be updated" > and yes, we should look at making it possible to mark an install as "updatesite" only or somehow refer to the "nearest" installer. > i.e. maybe something like: > {code} > updatesite_only: true > {code} > and then just refer to old installer link in the download ? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18791) Include share buttons on pages

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18791?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-18791: ---------------------------------------- Fix Version/s: 4.3.0.Alpha2 (was: 4.3.0.Alpha1) bump to alpha 2 > Include share buttons on pages > ------------------------------- > > Key: JBIDE-18791 > URL: https://issues.jboss.org/browse/JBIDE-18791 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: website > Affects Versions: 4.2.0.Final > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.3.0.Alpha2 > > > See http://schier.co/blog/2014/10/22/pure-html-share-buttons.html -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18421) New and noteworthy for latest major version is available only for latest release

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18421?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-18421: ---------------------------------------- Fix Version/s: 4.3.0.Alpha2 (was: 4.3.0.Alpha1) bump to alpha 2 > New and noteworthy for latest major version is available only for latest release > -------------------------------------------------------------------------------- > > Key: JBIDE-18421 > URL: https://issues.jboss.org/browse/JBIDE-18421 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Affects Versions: 4.2.0.CR1 > Reporter: Marián Labuda > Assignee: Xavier Coulon > Fix For: 4.3.0.Alpha2 > > > New and noteworthy on the website are available for the major version (e.g. JBT 4.2.x) only for the latest release (e.g. 4.2.0.CR1). Older releases from the given version is hidden (see http://tools.jboss.org/documentation/whatsnew/jbosstools/4.2.0.Beta3.html which is accessible only via direct link). Once it gets final, I think that it's ok, but while it is in dev phase, it hide significant information because N&N is cumulative. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17037) Add a toggle button to show/hide intermediate versions on "all downloads"

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17037?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-17037: ---------------------------------------- Fix Version/s: 4.3.0.Alpha2 (was: 4.3.0.Alpha1) bump to alpha 2 > Add a toggle button to show/hide intermediate versions on "all downloads" > ------------------------------------------------------------------------- > > Key: JBIDE-17037 > URL: https://issues.jboss.org/browse/JBIDE-17037 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: website > Affects Versions: 4.2.0.Beta1 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.3.0.Alpha2 > > > quoting [~maxandersen] on IRC: > {quote} > for all download page i think we would be better off having it show all stable (no matter archive statues) and any non-archived release. That would by default hide all the intermediate/"dead" milestones. would make [~nickboldt] happy > {quote} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17053) images on whatssnew would be great to have an easy way to show "full resolution"

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17053?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-17053: ---------------------------------------- Fix Version/s: 4.3.0.Alpha2 (was: 4.3.0.Alpha1) bump to alpha 2 > images on whatssnew would be great to have an easy way to show "full resolution" > -------------------------------------------------------------------------------- > > Key: JBIDE-17053 > URL: https://issues.jboss.org/browse/JBIDE-17053 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: website > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > Fix For: 4.3.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18578) Additional javaee7-samples import issues

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18578?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-18578: -------------------------------- Fix Version/s: 4.3.0.Alpha2 (was: 4.3.0.Alpha1) > Additional javaee7-samples import issues > ---------------------------------------- > > Key: JBIDE-18578 > URL: https://issues.jboss.org/browse/JBIDE-18578 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.2.0.CR2 > Environment: JBDS 8.0.0.CR2 > Reporter: Jiri Peterka > Fix For: 4.3.0.Alpha2 > > > Additional javaee7-samples import issues > Clone and import https://github.com/javaee-samples/javaee7-samples as maven projects > They should import nicely (without errors) into JBT/JBDS and deploy to a JBT/JBDS managed Wildfly. > There are still some Java Problems, Maven Problems and XML Problems after import, most projects are without errors. Project should be imported without errors > Java Problems > {code} > Description Resource Path Location Type > EBook cannot be resolved to a type EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 71 Java Problem > EBook cannot be resolved to a type EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 71 Java Problem > EBook cannot be resolved to a type EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 76 Java Problem > EBook cannot be resolved to a type EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 85 Java Problem > EBookStore cannot be resolved to a type EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 63 Java Problem > EBookStore cannot be resolved to a type EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 69 Java Problem > EBookStore cannot be resolved to a type EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 69 Java Problem > EBookStoreImplService cannot be resolved to a type EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 35 Java Problem > EBookStoreImplService cannot be resolved to a type EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 56 Java Problem > EBookStoreImplService cannot be resolved to a type EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 56 Java Problem > EBookStoreImplService cannot be resolved to a type EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 63 Java Problem > EBookStoreImplService cannot be resolved to a type EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 69 Java Problem > Greeting cannot be resolved to a type GreetingTest.java /bean-discovery-all/src/test/java/org/javaee7/cdi/nobeans/xml line 28 Java Problem > Greeting cannot be resolved to a type GreetingTest.java /bean-discovery-all/src/test/java/org/javaee7/cdi/nobeans/xml line 32 Java Problem > Greeting cannot be resolved to a type GreetingTest.java /bean-discovery-all/src/test/java/org/javaee7/cdi/nobeans/xml line 36 Java Problem > Greeting cannot be resolved to a type GreetingTest.java /bean-discovery-all/src/test/java/org/javaee7/cdi/nobeans/xml line 37 Java Problem > SimpleGreeting cannot be resolved to a type GreetingTest.java /bean-discovery-all/src/test/java/org/javaee7/cdi/nobeans/xml line 28 Java Problem > SimpleGreeting cannot be resolved to a type GreetingTest.java /bean-discovery-all/src/test/java/org/javaee7/cdi/nobeans/xml line 37 Java Problem > The declared package "org.javaee7.cdi.bean.discovery" does not match the expected package "main.java.org.javaee7.cdi.bean.discovery" Greeting.java /bean-discovery-all/src/main/java/org/javaee7/cdi/bean/discovery line 1 Java Problem > The declared package "org.javaee7.cdi.bean.discovery" does not match the expected package "main.java.org.javaee7.cdi.bean.discovery" SimpleGreeting.java /bean-discovery-all/src/main/java/org/javaee7/cdi/bean/discovery line 1 Java Problem > The declared package "org.javaee7.cdi.nobeans.xml" does not match the expected package "test.java.org.javaee7.cdi.nobeans.xml" GreetingTest.java /bean-discovery-all/src/test/java/org/javaee7/cdi/nobeans/xml line 1 Java Problem > The import org.javaee7 cannot be resolved GreetingTest.java /bean-discovery-all/src/test/java/org/javaee7/cdi/nobeans/xml line 3 Java Problem > The import org.javaee7 cannot be resolved GreetingTest.java /bean-discovery-all/src/test/java/org/javaee7/cdi/nobeans/xml line 4 Java Problem > The import org.javaee7.jaxws.client.gen cannot be resolved EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 12 Java Problem > The import org.javaee7.jaxws.client.gen cannot be resolved EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 13 Java Problem > The import org.javaee7.jaxws.client.gen cannot be resolved EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 14 Java Problem > {code} > Maven Problems: > {code} > Description Resource Path Location Type > Plugin execution not covered by lifecycle configuration: org.codehaus.mojo:jaxws-maven-plugin:1.11:wsgen (execution: default, phase: process-classes) pom.xml /jaxws-endpoint line 21 Maven Project Build Lifecycle Mapping Problem > Plugin execution not covered by lifecycle configuration: org.codehaus.mojo:jaxws-maven-plugin:1.11:wsimport (execution: default, phase: generate-sources) pom.xml /jaxws-client line 21 Maven Project Build Lifecycle Mapping Problem > {code} > and xml problems > {code} > Description Resource Path Location Type > cvc-complex-type.2.1: Element 'jboss' must have no character or element information item [children], because the type's content type is empty. enforce-beans.xml /jax-rs-angularjs/src/test/resources line 4 XML Problem > cvc-complex-type.2.2: Element 'value' must have no element [children], and the value must be valid. flow1-flow.xml /flows-declarative/src/main/webapp/flow1 line 31 XML Problem > cvc-complex-type.2.2: Element 'value' must have no element [children], and the value must be valid. flow1-flow.xml /flows-declarative/src/main/webapp/flow1 line 35 XML Problem > cvc-complex-type.2.2: Element 'value' must have no element [children], and the value must be valid. flow2-flow.xml /flows-declarative/src/main/webapp/flow2 line 31 XML Problem > cvc-complex-type.2.2: Element 'value' must have no element [children], and the value must be valid. flow2-flow.xml /flows-declarative/src/main/webapp/flow2 line 35 XML Problem > cvc-complex-type.2.2: Element 'value' must have no element [children], and the value must be valid. flow2-flow.xml /flows-mixed/src/main/webapp/flow2 line 34 XML Problem > cvc-complex-type.2.2: Element 'value' must have no element [children], and the value must be valid. flow2-flow.xml /flows-mixed/src/main/webapp/flow2 line 38 XML Problem > cvc-complex-type.2.4.a: Invalid content was found starting with element 'flow-call'. One of '{"http://xmlns.jcp.org/xml/ns/javaee":inbound-parameter}' is expected. flow1-flow.xml /flows-declarative/src/main/webapp/flow1 line 25 XML Problem > cvc-complex-type.2.4.a: Invalid content was found starting with element 'flow-call'. One of '{"http://xmlns.jcp.org/xml/ns/javaee":inbound-parameter}' is expected. flow2-flow.xml /flows-declarative/src/main/webapp/flow2 line 25 XML Problem > cvc-complex-type.2.4.a: Invalid content was found starting with element 'flow-call'. One of '{"http://xmlns.jcp.org/xml/ns/javaee":inbound-parameter}' is expected. flow2-flow.xml /flows-mixed/src/main/webapp/flow2 line 28 XML Problem > cvc-elt.1: Cannot find the declaration of element 'arquillian'. arquillian.xml /jaxrs-endpoint/src/test/resources line 3 XML Problem > cvc-elt.1: Cannot find the declaration of element 'arquillian'. arquillian.xml /jpa-converter/src/test/resources-glassfish-embedded line 5 XML Problem > cvc-elt.1: Cannot find the declaration of element 'arquillian'. arquillian.xml /jpa-converter/src/test/resources-glassfish-remote line 5 XML Problem > cvc-elt.1: Cannot find the declaration of element 'arquillian'. arquillian.xml /jpa-converter/src/test/resources-jbosseap-remote line 5 XML Problem > cvc-elt.1: Cannot find the declaration of element 'arquillian'. arquillian.xml /send-receive/src/test/resources line 3 XML Problem > cvc-elt.1: Cannot find the declaration of element 'arquillian'. arquillian.xml /standalone/src/test/resources line 3 XML Problem > cvc-elt.1: Cannot find the declaration of element 'arquillian'. arquillian.xml /transactional/src/test/resources line 3 XML Problem > cvc-elt.1: Cannot find the declaration of element 'arquillian'. arquillian.xml /user-transaction/src/test/resources line 3 XML Problem > cvc-pattern-valid: Value 'param1 flow1 value' is not facet-valid with respect to pattern '#\{.*\}' for type 'faces-config-el-expressionType'. flow1-flow.xml /flows-declarative/src/main/webapp/flow1 line 31 XML Problem > cvc-pattern-valid: Value 'param1 flow2 value' is not facet-valid with respect to pattern '#\{.*\}' for type 'faces-config-el-expressionType'. flow2-flow.xml /flows-declarative/src/main/webapp/flow2 line 31 XML Problem > cvc-pattern-valid: Value 'param1 flow2 value' is not facet-valid with respect to pattern '#\{.*\}' for type 'faces-config-el-expressionType'. flow2-flow.xml /flows-mixed/src/main/webapp/flow2 line 34 XML Problem > cvc-pattern-valid: Value 'param2 flow1 value' is not facet-valid with respect to pattern '#\{.*\}' for type 'faces-config-el-expressionType'. flow1-flow.xml /flows-declarative/src/main/webapp/flow1 line 35 XML Problem > cvc-pattern-valid: Value 'param2 flow2 value' is not facet-valid with respect to pattern '#\{.*\}' for type 'faces-config-el-expressionType'. flow2-flow.xml /flows-declarative/src/main/webapp/flow2 line 35 XML Problem > cvc-pattern-valid: Value 'param2 flow2 value' is not facet-valid with respect to pattern '#\{.*\}' for type 'faces-config-el-expressionType'. flow2-flow.xml /flows-mixed/src/main/webapp/flow2 line 38 XML Problem > {code} > Additional issues: > https://issues.jboss.org/browse/JBIDE-18352 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 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 February 2015