[
https://issues.jboss.org/browse/JBTIS-11?page=com.atlassian.jira.plugin.s...
]
Gary Brown commented on JBTIS-11:
---------------------------------
Hi Paul
Could you remove the pi4soa feature from site.xml.
compositeArtifacts.xml - looks fine, although found it interesting that all other urls
were
download.jboss.org, except savara which was
downloads.jboss.org. Both seem to map
onto the same location though, so it is fine, or you might want to change it to be
consistent with the others.
The target platform looks ok - although worried about the BPMN2 feature still being based
on a nightly build. I think we need to coordinate with Bob Brodt to make sure there is a
stable release of this project (although Bob is not the lead he may be able to help), and
also that the latest version of the BPMN2 modeler is released before the integration stack
is released.
JBossTools Integration Stack :: savara: Verify the component
configuration of the initial IS tooling release
------------------------------------------------------------------------------------------------------------
Key: JBTIS-11
URL:
https://issues.jboss.org/browse/JBTIS-11
Project: JBoss Tools Integration Stack
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: savara
Environment: JBT 4.0
Reporter: Paul Leacu
Assignee: Gary Brown
Please verify your component configuration of the JBoss Integration Stack for a JBoss
Tools 4.0 target.
Also check that all components are compatible with the upstream components defined in the
target platform.
ref:
https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/...
https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/...
- compositeContent.xml
https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/...
I'm working on getting this project promoted to jbosstools in github. Unitl then
please refer to/fork the urls above. There is a best-guess already specified for each
component.
--
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