September 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-15392) Add api in server needed for source lookup

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15392?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-15392: -------------------------------- Fix Version/s: 4.2.0.Alpha1 > Add api in server needed for source lookup > ------------------------------------------ > > Key: JBIDE-15392 > URL: https://issues.jboss.org/browse/JBIDE-15392 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: maven, server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Fix For: 4.2.0.Alpha1 > > > As uncovered in https://github.com/jbosstools/jbosstools-central/pull/128/files#L5L120 we got a problem with source lookup code always having to play catchup with server changes. > We need to define a stable api that can be used here. > lets outline what api is actually needed and then subjiras for the specifics. > For me it looks like server lookup needs a few things: > 0. know exact version of server > 1. know the file structure of a certain server > 2. get dir or directories that contain jar that is the "runtime" > My guess is that #2 might just be sufficient for source code lookup. > Any comments ? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-1958) EDS Teiid Designer Generating a RESTEasy War file returns no value

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-1958?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-1958: -------------------------------------- Fix Version/s: 7.0.0.GA (was: 5.x) > EDS Teiid Designer Generating a RESTEasy War file returns no value > ------------------------------------------------------------------ > > Key: JBDS-1958 > URL: https://issues.jboss.org/browse/JBDS-1958 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: teiid > Affects Versions: 4.1.0.GA > Reporter: Debbie Steigner > Assignee: Barry LaFond > Fix For: 7.0.0.GA > > Attachments: org.teiid.designer.dqp.ui.patch > > > When following the published Teiid Designer documentation on generating a RESTEasy War file, a WAR file is produced with no error and deploys successfully. When "hitting" the web service, the HTTP status of 200 is returned with an empty body when there should be a result returned. This looks to be somewhat related to: https://issues.jboss.org/browse/TEIIDDES-1124. However, when checking the generated source code, it appears to be correct. Not sure if the generated src file is the actual generated class file that is being referenced. The procedure being "wrapped" with the RESTful Web Service executes fine from a Java client. > This WAR file was generated on RHEL 6.1 (CSB) and the latest version of JBDS, 4.1.1. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-1958) EDS Teiid Designer Generating a RESTEasy War file returns no value

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-1958?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen resolved JBDS-1958. --------------------------------------- Resolution: Migrated to another ITS setting as 7.0 but marking as migrated to another its since JBDSIS isn't covered in JBDS core. Issue fixed via TEIDDES-1186 > EDS Teiid Designer Generating a RESTEasy War file returns no value > ------------------------------------------------------------------ > > Key: JBDS-1958 > URL: https://issues.jboss.org/browse/JBDS-1958 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: teiid > Affects Versions: 4.1.0.GA > Reporter: Debbie Steigner > Assignee: Barry LaFond > Fix For: 7.0.0.GA > > Attachments: org.teiid.designer.dqp.ui.patch > > > When following the published Teiid Designer documentation on generating a RESTEasy War file, a WAR file is produced with no error and deploys successfully. When "hitting" the web service, the HTTP status of 200 is returned with an empty body when there should be a result returned. This looks to be somewhat related to: https://issues.jboss.org/browse/TEIIDDES-1124. However, when checking the generated source code, it appears to be correct. Not sure if the generated src file is the actual generated class file that is being referenced. The procedure being "wrapped" with the RESTful Web Service executes fine from a Java client. > This WAR file was generated on RHEL 6.1 (CSB) and the latest version of JBDS, 4.1.1. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15261) Cannot create wordpress example

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15261?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-15261: ------------------------------------------ created a new PR for master to get the lastest changes in jbosstools-4.1.x: https://github.com/jbosstools/jbosstools-openshift/pull/216 > Cannot create wordpress example > ------------------------------- > > Key: JBIDE-15261 > URL: https://issues.jboss.org/browse/JBIDE-15261 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Beta2 > Reporter: nan wei > Assignee: Max Rydahl Andersen > Fix For: 4.2.0.Alpha1 > > Attachments: create-wordpress-example.png, initial-build-failed.png > > > Version: > JBoss Deverloper Studio 7 Beta > OpenShift Plugin: 2.5.0.Beta2-v20130621-1052-B65 > OpenShift Enterprise 1.2/2013-07-18.4 > How reproducible: > always > Steps to Reproduce: > 1. Create an app in the JBoss Deverloper Studio. > Name: mysqltest > Type: PHP 5.3(php-5.3) > Embeddable Cartridges: MySQL Database 5.1(mysql-5.1) > 2. Click Advanced > Add Source Code:https://github.com/openshift/wordpress-example > !create-wordpress-example.png! > Actual results: > When creating an app, check mysql cartridge and add source code together, it will fail, and return the following error: > !initial-build-failed.png! > {code} > Could not create application "a3" > Could not request https://broker.ose0717.com/broker/rest/domains/nwei/applications: The initial build for the application failed. Last 10 kB of build output: > httpd (no pid file) not running > Could not find mysql database. Please run: > rhc cartridge add -a a3 -c mysql-5.1 > then make a sample commit (add whitespace somewhere) and re-push > An error occurred executing 'gear postreceive' > For more details about the problem, try running the command again with the '--trace' option. > {code} > But if use rhc client, there is no such problem, it is created successfully. > # rhc app create mysqltest1 php-5.3 mysql-5.1 --from-code=https://github.com/openshift/wordpress-example -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15455) For JBIDE 4.1.1.Alpha1: Code Freeze + Branch [Freemarker]

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15455?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen closed JBIDE-15455. --------------------------------------- Resolution: Rejected I dont see any changes in freemarker 4.1.x branch. [~nickboldt] I assume this means you will just take the binaries from last release, correct ? (no rebuilds done) > For JBIDE 4.1.1.Alpha1: Code Freeze + Branch [Freemarker] > --------------------------------------------------------- > > Key: JBIDE-15455 > URL: https://issues.jboss.org/browse/JBIDE-15455 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: freemarker > Reporter: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.1.1.Alpha1 > > > For JBIDE 4.1.1.Alpha1: Please perform the following tasks: > 0. If nothing has changed in your component since the least GA release on this branch, *Reject this JIRA*. > Otherwise: > 1. Update your root pom to use parent pom version 4.1.1.Alpha1-SNAPSHOT; > 2. Ensure you've built & run your plugin tests using the latest target platform version 4.31.0.Alpha1; > 3. Branch from your existing jbosstools-4.1.x branch into a new jbosstools-4.1.1.Alpha1x branch; > 4. Close (not resolve) this JIRA when done. [Freemarker] > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Freemarker task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13790) Prepare fast-filter script for integration-stack-tests split

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13790?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-13790: --------------------------------------- [~maxandersen] as far as I remember last time we tried to do this we discussed it on irc, I verified with Andrej (soa team) and then you left irc for lunch and never came back :) So ok, I'll verify again next week that the filter is still working as expected and then let you know. > Prepare fast-filter script for integration-stack-tests split > ------------------------------------------------------------ > > Key: JBIDE-13790 > URL: https://issues.jboss.org/browse/JBIDE-13790 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.0.1.Final, 4.1.0.Alpha1, 4.1.0.Alpha2 > Reporter: Martin Malina > Assignee: Martin Malina > Priority: Blocker > Fix For: 4.1.1.Alpha1, 4.2.0.Alpha1 > > > As discussed in JBIDE-12974 and elsewhere, we need to split https://github.com/jbosstools/jbosstools-integration-tests in two: > - the current repo will contain tests for all features of JBT core > - the new repo - integration-stack-tests - will contain all soa/drools/teiid related tests > We need a fast-filter script to do the split while preserving history -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14917) Warings in console, when stacks.yaml isn't reachable

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14917?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-14917: -------------------------------- Fix Version/s: 4.1.1.Alpha2 4.2.0.Alpha1 (was: 4.1.x) (was: 4.2.x) > Warings in console, when stacks.yaml isn't reachable > ---------------------------------------------------- > > Key: JBIDE-14917 > URL: https://issues.jboss.org/browse/JBIDE-14917 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, project-examples > Affects Versions: 4.1.0.Beta2 > Reporter: Radim Hopp > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.1.1.Alpha2, 4.2.0.Alpha1 > > > {noformat} > $ eclipse/eclipse-jbt-4.1.0.Beta2/eclipse -data workspace-test > Jun 18, 2013 2:03:47 PM org.jboss.jdf.stacks.client.messages.JBossLoggingMessages showWarnMessage > WARN: It was not possible to contact the repository at https://raw.github.com/jboss-jdf/jdf-stack/1.0.0.Final/stacks.yaml . Cause raw.github.com > Jun 18, 2013 2:03:47 PM org.jboss.jdf.stacks.client.messages.JBossLoggingMessages showWarnMessage > WARN: Falling back to cache! > Jun 18, 2013 2:03:47 PM org.jboss.jdf.stacks.client.messages.JBossLoggingMessages showWarnMessage > WARN: Cache empty. Falling back to embed file > {noformat} > Is it possible to log these warnings to Error Log? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15261) Cannot create wordpress example

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15261?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-15261: ------------------------------------------ Max +1'ed my PR and Xavier tested it. Pushing https://github.com/jbosstools/jbosstools-openshift/pull/215 upstream to jbosstools-4.1.x > Cannot create wordpress example > ------------------------------- > > Key: JBIDE-15261 > URL: https://issues.jboss.org/browse/JBIDE-15261 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Beta2 > Reporter: nan wei > Assignee: Max Rydahl Andersen > Fix For: 4.2.0.Alpha1 > > Attachments: create-wordpress-example.png, initial-build-failed.png > > > Version: > JBoss Deverloper Studio 7 Beta > OpenShift Plugin: 2.5.0.Beta2-v20130621-1052-B65 > OpenShift Enterprise 1.2/2013-07-18.4 > How reproducible: > always > Steps to Reproduce: > 1. Create an app in the JBoss Deverloper Studio. > Name: mysqltest > Type: PHP 5.3(php-5.3) > Embeddable Cartridges: MySQL Database 5.1(mysql-5.1) > 2. Click Advanced > Add Source Code:https://github.com/openshift/wordpress-example > !create-wordpress-example.png! > Actual results: > When creating an app, check mysql cartridge and add source code together, it will fail, and return the following error: > !initial-build-failed.png! > {code} > Could not create application "a3" > Could not request https://broker.ose0717.com/broker/rest/domains/nwei/applications: The initial build for the application failed. Last 10 kB of build output: > httpd (no pid file) not running > Could not find mysql database. Please run: > rhc cartridge add -a a3 -c mysql-5.1 > then make a sample commit (add whitespace somewhere) and re-push > An error occurred executing 'gear postreceive' > For more details about the problem, try running the command again with the '--trace' option. > {code} > But if use rhc client, there is no such problem, it is created successfully. > # rhc app create mysqltest1 php-5.3 mysql-5.1 --from-code=https://github.com/openshift/wordpress-example -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13790) Prepare fast-filter script for integration-stack-tests split

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13790?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-13790: ---------------------------------------- Assignee: Martin Malina (was: Max Rydahl Andersen) Affects Version/s: 4.1.0.Alpha2 > Prepare fast-filter script for integration-stack-tests split > ------------------------------------------------------------ > > Key: JBIDE-13790 > URL: https://issues.jboss.org/browse/JBIDE-13790 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.0.1.Final, 4.1.0.Alpha1, 4.1.0.Alpha2 > Reporter: Martin Malina > Assignee: Martin Malina > Priority: Blocker > Fix For: 4.1.1.Alpha1, 4.2.0.Alpha1 > > > As discussed in JBIDE-12974 and elsewhere, we need to split https://github.com/jbosstools/jbosstools-integration-tests in two: > - the current repo will contain tests for all features of JBT core > - the new repo - integration-stack-tests - will contain all soa/drools/teiid related tests > We need a fast-filter script to do the split while preserving history -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13790) Prepare fast-filter script for integration-stack-tests split

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13790?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-13790: --------------------------------------------- Yes, but we left it with you working with soa QE team to verify the contents. Once that was done we could execute it. > Prepare fast-filter script for integration-stack-tests split > ------------------------------------------------------------ > > Key: JBIDE-13790 > URL: https://issues.jboss.org/browse/JBIDE-13790 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.0.1.Final, 4.1.0.Alpha1, 4.1.0.Alpha2 > Reporter: Martin Malina > Assignee: Martin Malina > Priority: Blocker > Fix For: 4.1.1.Alpha1, 4.2.0.Alpha1 > > > As discussed in JBIDE-12974 and elsewhere, we need to split https://github.com/jbosstools/jbosstools-integration-tests in two: > - the current repo will contain tests for all features of JBT core > - the new repo - integration-stack-tests - will contain all soa/drools/teiid related tests > We need a fast-filter script to do the split while preserving history -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 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 2013