September 2011 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-9119) helloworld_mail_testclient does not get preconfigured soa runtime

by Libor Zoubek (JIRA)

helloworld_mail_testclient does not get preconfigured soa runtime ----------------------------------------------------------------- Key: JBIDE-9119 URL: https://issues.jboss.org/browse/JBIDE-9119 Project: Tools (JBoss Tools) Issue Type: Bug Components: project-examples Affects Versions: 3.3.0.M1 Reporter: Libor Zoubek Assignee: Snjezana Peco Fix For: 3.3.0.Final Project examples works this way: if examle requires a runtime and user has defined same runtime with different name, runtime is assigned and there is no need to fix it manually. This does not seem to work for some non-faceted projects (helloworld ESB example works fine) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
5
0 / 0

[JBoss JIRA] Created: (JBIDE-9361) Imported project examples with multiple projects don't have build path set correctly

by Brian Fitzpatrick (JIRA)

Imported project examples with multiple projects don't have build path set correctly ------------------------------------------------------------------------------------ Key: JBIDE-9361 URL: https://issues.jboss.org/browse/JBIDE-9361 Project: Tools (JBoss Tools) Issue Type: Bug Components: project-examples Affects Versions: 3.2.1.CR3, 3.3.0.M3 Environment: Windows 7, JBDS 4.1 CR3 build installed, 32-bit JDK Reporter: Brian Fitzpatrick Assignee: Snjezana Peco While doing some testing of one of the ESB project examples (ESB for SOA-P 5.0 -> JBoss ESB HelloWorld Action Example - ESB and ESB for SOA-P 5.0 -> JBoss ESB Web Service consumer1 Example) in conjunction with JBDS-1716, I discovered an interesting issue when there are multiple projects in the project-example zip being imported. The first project in the zip being imported (i.e. helloworld_action) is imported correctly with the runtime set properly in the build path. But the second project (i.e. helloworld_action_client) is not updated correctly and still pointing to the wrong runtime. To reproduce: 1) In a new workspace with no SOA/EAP 5.x runtime defined, create a new EAP 5.x server in the Servers view. Name the server "one" and the server runtime "two". 2) Click on Help->Project Examples->ESB for SOA-P 5.0->JBoss ESB HelloWorld Action Example - ESB. 3) Note that when the projects are imported, helloworld_action is setup correctly and helloworld_action_client is not. Now, is this a bug? Or is it working as designed? I would hope that the project examples code would peer into each project being imported to see if the build path needed to be updated. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
10
0 / 0

[JBoss JIRA] Created: (JBIDE-8542) Display remote server log in console view

by Libor Zoubek (JIRA)

Display remote server log in console view ----------------------------------------- Key: JBIDE-8542 URL: https://issues.jboss.org/browse/JBIDE-8542 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS Affects Versions: 3.2.0.Final Reporter: Libor Zoubek Assignee: Rob Stryker It would be nice if we were able to redirect remote server's output to console view (same as local server does) Currently developer needs to open terminal and tail -f server's log by hand. It would also help our to run bot tests (that we now run with local servers) with remote server. These test always analyze server's log to determine successful deployment etc. My suggestions is (when server is started via tools): If server is already running: {{cat server.log}}, and than run {{tail -n0 -f server.log}} If it isn't: just {{tail -f server.log}} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
8
0 / 0

[JBoss JIRA] Created: (JBIDE-9607) AS7 Managed Service poller does not detect server running

by Libor Zoubek (JIRA)

AS7 Managed Service poller does not detect server running --------------------------------------------------------- Key: JBIDE-9607 URL: https://issues.jboss.org/browse/JBIDE-9607 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.3.0.M3 Environment: AS 7.0, 7.0.1 Reporter: Libor Zoubek Assignee: Rob Stryker Fix For: 3.3.0.M4 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (JBIDE-9616) CLONE - CLONE - CLONE - Hibernate Component N&N

by Max Rydahl Andersen (JIRA)

CLONE - CLONE - CLONE - Hibernate Component N&N ----------------------------------------------- Key: JBIDE-9616 URL: https://issues.jboss.org/browse/JBIDE-9616 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: Hibernate Reporter: Denis Golovin Assignee: Dmitry Geraskov Fix For: 3.3.0.M2 https://issues.jboss.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=p... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBDS-1692) Runtime detector plugins are missing

by Libor Zoubek (JIRA)

Runtime detector plugins are missing ------------------------------------ Key: JBDS-1692 URL: https://issues.jboss.org/browse/JBDS-1692 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: Build Affects Versions: 5.0.0.M2 Reporter: Libor Zoubek Assignee: Snjezana Peco Priority: Blocker Fix For: 5.0.0.M2 Folder with runtime is searched, but nothing found. There is nothing special in .log. IMHO following features are missing: JBoss Runtime AS Detector org.jboss.tools.runtime.as.detector.feature JBoss Runtime Seam Detector org.jboss.tools.runtime.seam.detector.feature (These ones are present in my JBT 3.3.0.M2) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

4
10
0 / 0

[JBoss JIRA] Created: (JBDS-1824) JBDS M3 built from branch has M4 version

by Libor Zoubek (JIRA)

JBDS M3 built from branch has M4 version ---------------------------------------- Key: JBDS-1824 URL: https://issues.jboss.org/browse/JBDS-1824 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: Build Affects Versions: 5.0.0.M3 Reporter: Libor Zoubek Assignee: Nick Boldt I just installed 5.0.0/M3 build from http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-5.0_stable... Instalator shows 5.0.0.M3 but slash & About JBDS is showing M4. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

5
8
0 / 0

[JBoss JIRA] Created: (JBDS-1790) CLONE - Unable to install BPEL extras - cannot find BPEL examples (JBDS 5)

by Brian Fitzpatrick (JIRA)

CLONE - Unable to install BPEL extras - cannot find BPEL examples (JBDS 5) -------------------------------------------------------------------------- Key: JBDS-1790 URL: https://issues.jboss.org/browse/JBDS-1790 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: updatesite Affects Versions: 4.1.0.CR2, 5.0.0.M3 Reporter: Libor Zoubek Assignee: Denis Golovin Priority: Blocker Fix For: 4.1.0.CR2, 5.0.0.M3 Attachments: Screenshot.png I cannot install BPEL extra plugins from http://www.qa.jboss.com/binaries/RHDS/updates/development/4.1.0.CR2_extras/ on top of http://machydra.brq.redhat.com/www.qa.jboss.com/binaries/RHDS/builds/deve... {noformat} Cannot complete the install because one or more required items could not be found. Software being installed: BPEL Editor (Certified) 1.0.0.v20110705-1603-H948-CR2 (com.jboss.jbds.bpel.feature.feature.group 1.0.0.v20110705-1603-H948-CR2) Missing requirement: BPEL Editor (Certified) 1.0.0.v20110705-1603-H948-CR2 (com.jboss.jbds.bpel.feature.feature.group 1.0.0.v20110705-1603-H948-CR2) requires 'com.jboss.jbds.bpel.examples 0.0.0' but it could not be found {noformat} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

4
19
0 / 0

[JBoss JIRA] Created: (JBIDE-9618) CLONE - CLONE - CLONE - AS Component N&N

by Max Rydahl Andersen (JIRA)

CLONE - CLONE - CLONE - AS Component N&N ---------------------------------------- Key: JBIDE-9618 URL: https://issues.jboss.org/browse/JBIDE-9618 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: JBossAS Affects Versions: 3.3.0.M2 Reporter: Denis Golovin Assignee: Andre Dietisheim Fix For: 3.3.0.M2 project = "Tools (JBoss Tools)" AND component = JBossAS AND fixVersion = "3.3.0.M2" -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
2
0 / 0

[JBoss JIRA] Commented: (JBDS-1819) Configure SOA-P quickstarts to be run OOTB in JBDS 4.1.1 with SOA-P 5.2

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-1819?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-1819: ------------------------------------------- note: just to be clear, my confusion is about who maintains these going forward and how these quickstarts are to used by user - is a new plugin/feature required or will they just add this quickstart.xml for now and thus we leave the full integrated solution for JBDS 5 or how? > Configure SOA-P quickstarts to be run OOTB in JBDS 4.1.1 with SOA-P 5.2 > ----------------------------------------------------------------------- > > Key: JBDS-1819 > URL: https://issues.jboss.org/browse/JBDS-1819 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Security Level: Public(Everyone can see) > Components: SOA Platform > Affects Versions: 4.1.0.CR3 > Reporter: Len DiMaggio > Assignee: Brian Fitzpatrick > Fix For: 4.1.1.Final > > Attachments: bfitzpat_examples.png, product_examples.png, runtimes.png > > > Changed to: > Need to verify that all JBDS supplied sample ESB quickstarts run cleanly with SOA-P 5.2 on JBDS 4.1.1 > Was: > This subject comes up now and then - it would be very useful to new users to have the full set of SOA-P quickstarts configured to run OOTB from JBDS. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 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 2011