[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
[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
[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
[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