[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-5546) Unable to import SOA-P quickstarts
[
https://jira.jboss.org/jira/browse/JBIDE-5546?page=com.atlassian.jira.plu...
]
Martin Malina commented on JBIDE-5546:
--------------------------------------
You're right, the problem is not in the editor but in the quickstarts which
weren't made to work with JBDS. I made a bug in both JBIDE and SOA to make sure it is
tracked. It hasn't been decided yet how to resolve this, but probably the quickstarts
will need to be modified.
Unable to import SOA-P quickstarts
----------------------------------
Key: JBIDE-5546
URL: https://jira.jboss.org/jira/browse/JBIDE-5546
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: esb
Affects Versions: 3.1.0.M4
Environment: JBossTools-Update-3.1.0.v200912141523M-H176-RC1.zip
or
jbdevstudio-macosx-carbon-3.0.0.v200912182118M-H46-CR1.jar
SOA-P 5.0 ER5
Reporter: Martin Malina
Fix For: 3.2.next
Currently the SOA-P quickstarts store the jboss-esb.xml in the root dir of each
quickstart under jboss-as/samples/quickstarts. When you run a quickstart using the
supplied ant script, jboss-esb.xml is first moved to META-INF which is the required
location for it.
If you only try to import such a project to JBoss Tools/JBDS it won't work since it
won't look for the jboss-esb.xml in the root dir.
This is not exactly a problem of JBoss Tools as such, but I'm reporting it here for a
reference.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira