September 2013 - jbosstools-issues

[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 updated JBIDE-15261: ------------------------------------- Fix Version/s: 4.1.1.Alpha1 > 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.1.1.Alpha1, 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2767) Include org.jboss.tools.wtp.runtimes.tomcat.feature for EWP detection

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-2767?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-2767: -------------------------------------- PRs fixing this issues: * On master https://github.com/jbdevstudio/jbdevstudio-product/pull/68 * On jbosstools-4.1.x: https://github.com/jbdevstudio/jbdevstudio-product/pull/69 * On jbosstools-4.1.Alpha2x: https://github.com/jbdevstudio/jbdevstudio-product/pull/70 All of them work with a "mvn clean verify". > Include org.jboss.tools.wtp.runtimes.tomcat.feature for EWP detection > --------------------------------------------------------------------- > > Key: JBDS-2767 > URL: https://issues.jboss.org/browse/JBDS-2767 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: servers, updatesite > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 7.1.0.Alpha2 > > Attachments: 15498.png > > > Tomcat autodetection is available in JBoss Tools 4.1 but not in JBDS 7.0. > Suggestion is to include this feature so JBDS can automatically configure and setup JBoss EWP instances in addition to "plain" JBoss AS/EAP instances. > Original from Nick: > Noticed today that while org.jboss.tools.wtp.runtimes.tomcat.feature and org.jboss.tools.wtp.runtimes.tomcat.feature.source were added to JBoss Tools 4.1, it was omitted from JBDS 7. > Comparing the update sites for JBT 4.1.x and JBDS 7.1.x: > !15498.png! > Was it intentionally excluded from the update site, or forgotten? -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2767) Include org.jboss.tools.wtp.runtimes.tomcat.feature for EWP detection

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-2767?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-2767: -------------------------------------- There is no feature containing *detector* in it's ID, the only feature visible from JBDS build (exposed on JBT site) is org.jboss.tools.wtp.runtimes.tomcat.feature. > Include org.jboss.tools.wtp.runtimes.tomcat.feature for EWP detection > --------------------------------------------------------------------- > > Key: JBDS-2767 > URL: https://issues.jboss.org/browse/JBDS-2767 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: servers, updatesite > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 7.1.0.Alpha2 > > Attachments: 15498.png > > > Tomcat autodetection is available in JBoss Tools 4.1 but not in JBDS 7.0. > Suggestion is to include this feature so JBDS can automatically configure and setup JBoss EWP instances in addition to "plain" JBoss AS/EAP instances. > Original from Nick: > Noticed today that while org.jboss.tools.wtp.runtimes.tomcat.feature and org.jboss.tools.wtp.runtimes.tomcat.feature.source were added to JBoss Tools 4.1, it was omitted from JBDS 7. > Comparing the update sites for JBT 4.1.x and JBDS 7.1.x: > !15498.png! > Was it intentionally excluded from the update site, or forgotten? -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15372) Installed Software needs a Search box

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15372?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-15372: -------------------------------- Fix Version/s: 4.2.x > Installed Software needs a Search box > ------------------------------------- > > Key: JBIDE-15372 > URL: https://issues.jboss.org/browse/JBIDE-15372 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: upstream > Reporter: Burr Sutter > Assignee: Fred Bricon > Fix For: 4.2.x > > Attachments: 15372.png > > > With so many features installed it is getting harder to find the plugin/feature I wish to "uninstall" - a search solution would be very nice. > http://screencast.com/t/EPjgHbJPS -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15510) create new 4.1.0.x branch, then bump jbosstools-central/examples from 1.5.1 to 1.5.2 in 4.1.x branch

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15510?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-15510: -------------------------------- Release Notes Text: (was: I directly pushed your jbosstools-4.1.0.x branch to jbosstools-central. Version bump in 4.1.x was done and branched yesterday) > create new 4.1.0.x branch, then bump jbosstools-central/examples from 1.5.1 to 1.5.2 in 4.1.x branch > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-15510 > URL: https://issues.jboss.org/browse/JBIDE-15510 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Affects Versions: 4.1.1.Alpha2 > Reporter: Nick Boldt > Assignee: Fred Bricon > Fix For: 4.1.1.Alpha2 > > -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15510) create new 4.1.0.x branch, then bump jbosstools-central/examples from 1.5.1 to 1.5.2 in 4.1.x branch

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15510?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-15510: ------------------------------------- I directly pushed your jbosstools-4.1.0.x branch to jbosstools-central. Version bump in 4.1.x was done and branched yesterday > create new 4.1.0.x branch, then bump jbosstools-central/examples from 1.5.1 to 1.5.2 in 4.1.x branch > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-15510 > URL: https://issues.jboss.org/browse/JBIDE-15510 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Affects Versions: 4.1.1.Alpha2 > Reporter: Nick Boldt > Assignee: Fred Bricon > Fix For: 4.1.1.Alpha2 > > -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2767) Include org.jboss.tools.wtp.runtimes.tomcat.feature for EWP detection

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-2767?page=com.atlassian.jira.plugin.... ] Mickael Istria updated JBDS-2767: --------------------------------- Priority: Blocker (was: Major) > Include org.jboss.tools.wtp.runtimes.tomcat.feature for EWP detection > --------------------------------------------------------------------- > > Key: JBDS-2767 > URL: https://issues.jboss.org/browse/JBDS-2767 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: servers, updatesite > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 7.1.0.Alpha2 > > Attachments: 15498.png > > > Tomcat autodetection is available in JBoss Tools 4.1 but not in JBDS 7.0. > Suggestion is to include this feature so JBDS can automatically configure and setup JBoss EWP instances in addition to "plain" JBoss AS/EAP instances. > Original from Nick: > Noticed today that while org.jboss.tools.wtp.runtimes.tomcat.feature and org.jboss.tools.wtp.runtimes.tomcat.feature.source were added to JBoss Tools 4.1, it was omitted from JBDS 7. > Comparing the update sites for JBT 4.1.x and JBDS 7.1.x: > !15498.png! > Was it intentionally excluded from the update site, or forgotten? -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2767) Include org.jboss.tools.wtp.runtimes.tomcat.feature for EWP detection

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-2767?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-2767: -------------------------------------- Build is failing on CI. https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... I'm making this a blocker since it's blocking the 7.1.0.Alpha2 release. > Include org.jboss.tools.wtp.runtimes.tomcat.feature for EWP detection > --------------------------------------------------------------------- > > Key: JBDS-2767 > URL: https://issues.jboss.org/browse/JBDS-2767 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: servers, updatesite > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 7.1.0.Alpha2 > > Attachments: 15498.png > > > Tomcat autodetection is available in JBoss Tools 4.1 but not in JBDS 7.0. > Suggestion is to include this feature so JBDS can automatically configure and setup JBoss EWP instances in addition to "plain" JBoss AS/EAP instances. > Original from Nick: > Noticed today that while org.jboss.tools.wtp.runtimes.tomcat.feature and org.jboss.tools.wtp.runtimes.tomcat.feature.source were added to JBoss Tools 4.1, it was omitted from JBDS 7. > Comparing the update sites for JBT 4.1.x and JBDS 7.1.x: > !15498.png! > Was it intentionally excluded from the update site, or forgotten? -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2722) Include Kepler SR1 by default

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-2722?page=com.atlassian.jira.plugin.... ] Mickael Istria updated JBDS-2722: --------------------------------- Fix Version/s: 7.1.0.Alpha2 (was: 7.1.0.Alpha1) > Include Kepler SR1 by default > ------------------------------ > > Key: JBDS-2722 > URL: https://issues.jboss.org/browse/JBDS-2722 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: build, requirements > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 7.1.0.Alpha2 > > > Kepler SR1 has bugfixes - we should include it in upcoming release. > * Affects JBT TP, JBDS TP, and JBDS installer. > * Verification by comparing old TPs and installer contents to newer one, eg., using vwatch tool [1] or by scheduled job [2]. > [1] https://github.com/jbdevstudio/jbdevstudio-qa/tree/master/vwatch > [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-181) bump fuse to 7.2.0.Beta3 and JBTIS/JBDSIS to Beta4

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-181: -------------------------------- Summary: bump fuse to 7.2.0.Beta3 and JBTIS/JBDSIS to Beta4 Key: JBTIS-181 URL: https://issues.jboss.org/browse/JBTIS-181 Project: JBoss Tools Integration Stack Issue Type: Task Security Level: Public (Everyone can see) Reporter: Paul Leacu Assignee: Paul Leacu -- 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, 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 2013