July 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20212) For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [Central]

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20212?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-20212: ----------------------------------- Assignee: Fred Bricon > For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [Central] > ----------------------------------------------------------------------------------- > > Key: JBIDE-20212 > URL: https://issues.jboss.org/browse/JBIDE-20212 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central, maven, project-examples > Reporter: Nick Boldt > Assignee: Fred Bricon > Priority: Blocker > Labels: task > Fix For: 4.3.0.CR1 > > > For JBIDE 4.3.0.CR1 [Central]: Please perform the following tasks: > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100. > 2. Switch to using the new o.j.t.foundation.license.feature. Instructions here: > https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... > 2. Resolve this JIRA when done. QE can then verify and close it later. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Central task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20238) Maven New and Noteworthy for 4.3.0.Beta2

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20238?page=com.atlassian.jira.plugi... ] Fred Bricon closed JBIDE-20238. ------------------------------- Resolution: Rejected > Maven New and Noteworthy for 4.3.0.Beta2 > ---------------------------------------- > > Key: JBIDE-20238 > URL: https://issues.jboss.org/browse/JBIDE-20238 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: maven > Reporter: Max Rydahl Andersen > Priority: Critical > Fix For: 4.3.0.Beta2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Maven is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Maven by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20240) Project Examples New and Noteworthy for 4.3.0.Beta2

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20240?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-20240: ----------------------------------- Assignee: Fred Bricon > Project Examples New and Noteworthy for 4.3.0.Beta2 > --------------------------------------------------- > > Key: JBIDE-20240 > URL: https://issues.jboss.org/browse/JBIDE-20240 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: project-examples > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.3.0.Beta2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Project Examples is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Project Examples by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20246) JBoss Central New and Noteworthy for 4.3.0.Beta2

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20246?page=com.atlassian.jira.plugi... ] Fred Bricon closed JBIDE-20246. ------------------------------- Resolution: Rejected > JBoss Central New and Noteworthy for 4.3.0.Beta2 > ------------------------------------------------ > > Key: JBIDE-20246 > URL: https://issues.jboss.org/browse/JBIDE-20246 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central > Reporter: Max Rydahl Andersen > Priority: Critical > Fix For: 4.3.0.Beta2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If JBoss Central is not listed here check if there are issues that should be added and add them. > Document the ones relevant for JBoss Central by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 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.CR1 (was: 4.3.0.Beta2) > Additional javaee7-samples import issues > ---------------------------------------- > > Key: JBIDE-18578 > URL: https://issues.jboss.org/browse/JBIDE-18578 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, upstream > Affects Versions: 4.2.0.CR2 > Environment: JBDS 8.0.0.CR2 > Reporter: Jiri Peterka > Assignee: Fred Bricon > Fix For: 4.3.0.CR1 > > > 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.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20129) Application wizard: Allow users to edit template parameters by double clicking

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20129?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-20129: -------------------------------- Fix Version/s: 4.3.0.CR1 (was: 4.3.0.Beta2) > Application wizard: Allow users to edit template parameters by double clicking > ------------------------------------------------------------------------------ > > Key: JBIDE-20129 > URL: https://issues.jboss.org/browse/JBIDE-20129 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Fred Bricon > Labels: application_wizard, openshift_v3 > Fix For: 4.3.0.CR1 > > Attachments: edit-template-parameters.png > > > Steps: > # EXEC: launch v3 application wizard, select a template and get to page 2 > # EXEC: try to edit template parameters. > Result: > !edit-template-parameters.png! > You can only edit parameters by selecting them then and then hitting "Edit". > It would be handy if we could allow the user to edit via double-clicking onto items -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20187) "SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder"" error appears when trying to run script to work offline

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20187?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-20187: ------------------------------------- This is a minor error caused by the errai archetype. Given that errai/gwt is not supported anymore, I'll exclude it from the offline script > "SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder"" error appears when trying to run script to work offline > -------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20187 > URL: https://issues.jboss.org/browse/JBIDE-20187 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.3.0.Beta1 > Reporter: Misha Ali > Assignee: Fred Bricon > Fix For: 4.3.0.Beta2 > > > I'm trying to test the Working Offline instructions for JBDS 9.0 Beta1 and coming across an odd error. I've checked with Len and Martin and they are also encountering this error and have recommended filing a bug. > Steps to reproduce: > 1. Follow the steps here: https://access.redhat.com/articles/1367643 > Details: JBDS Beta1, Groovy version 2.4.3 JVM: 1.7.0_79 Vendor: Oracle Corporation OS: Linux > The step where a groovy script is run results in the following output, which ends with an error: > << internal link removed >> Error is available here: http://pastebin.com/3XKt9x5i > Please let me know if any further information is required for this bug. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20187) "SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder"" error appears when trying to run script to work offline

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20187?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-20187: ----------------------------------- Assignee: Fred Bricon > "SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder"" error appears when trying to run script to work offline > -------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20187 > URL: https://issues.jboss.org/browse/JBIDE-20187 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.3.0.Beta1 > Reporter: Misha Ali > Assignee: Fred Bricon > Fix For: 4.3.0.Beta2 > > > I'm trying to test the Working Offline instructions for JBDS 9.0 Beta1 and coming across an odd error. I've checked with Len and Martin and they are also encountering this error and have recommended filing a bug. > Steps to reproduce: > 1. Follow the steps here: https://access.redhat.com/articles/1367643 > Details: JBDS Beta1, Groovy version 2.4.3 JVM: 1.7.0_79 Vendor: Oracle Corporation OS: Linux > The step where a groovy script is run results in the following output, which ends with an error: > << internal link removed >> Error is available here: http://pastebin.com/3XKt9x5i > Please let me know if any further information is required for this bug. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20187) "SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder"" error appears when trying to run script to work offline

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20187?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-20187: -------------------------------- Fix Version/s: 4.3.0.Beta2 > "SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder"" error appears when trying to run script to work offline > -------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20187 > URL: https://issues.jboss.org/browse/JBIDE-20187 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.3.0.Beta1 > Reporter: Misha Ali > Assignee: Fred Bricon > Fix For: 4.3.0.Beta2 > > > I'm trying to test the Working Offline instructions for JBDS 9.0 Beta1 and coming across an odd error. I've checked with Len and Martin and they are also encountering this error and have recommended filing a bug. > Steps to reproduce: > 1. Follow the steps here: https://access.redhat.com/articles/1367643 > Details: JBDS Beta1, Groovy version 2.4.3 JVM: 1.7.0_79 Vendor: Oracle Corporation OS: Linux > The step where a groovy script is run results in the following output, which ends with an error: > << internal link removed >> Error is available here: http://pastebin.com/3XKt9x5i > Please let me know if any further information is required for this bug. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20187) "SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder"" error appears when trying to run script to work offline

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20187?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-20187: -------------------------------- Component/s: project-examples (was: central) > "SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder"" error appears when trying to run script to work offline > -------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20187 > URL: https://issues.jboss.org/browse/JBIDE-20187 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.3.0.Beta1 > Reporter: Misha Ali > > I'm trying to test the Working Offline instructions for JBDS 9.0 Beta1 and coming across an odd error. I've checked with Len and Martin and they are also encountering this error and have recommended filing a bug. > Steps to reproduce: > 1. Follow the steps here: https://access.redhat.com/articles/1367643 > Details: JBDS Beta1, Groovy version 2.4.3 JVM: 1.7.0_79 Vendor: Oracle Corporation OS: Linux > The step where a groovy script is run results in the following output, which ends with an error: > << internal link removed >> Error is available here: http://pastebin.com/3XKt9x5i > Please let me know if any further information is required for this bug. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 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 July 2015