[
https://issues.jboss.org/browse/JBDS-1819?page=com.atlassian.jira.plugin....
]
Len DiMaggio commented on JBDS-1819:
------------------------------------
The problem with the quickstarts containing .project and .settings files
(
https://issues.jboss.org/browse/SOA-2954) is:
* Only a few of the 100+ quickstarts had these files
* Some of the affected quickstarts only included one of the files
* The quickstarts were not changed (to include client code that could be run in eclipse)
from the generic SOA-P quickstarts - I'm guessing that the .project and/or .settings
files were included unintentionally.
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