[JBoss JIRA] (JBTIS-63) Problem finding some links in process model
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-63?page=com.atlassian.jira.plugin.s... ]
Andrej Podhradsky closed JBTIS-63.
----------------------------------
Closed as obsolete
> Problem finding some links in process model
> -------------------------------------------
>
> Key: JBTIS-63
> URL: https://issues.jboss.org/browse/JBTIS-63
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: BPMN2
> Environment: Juno with BPMN2 modeller 0.2.4
> Reporter: Gary Brown
> Assignee: Gary Brown
> Fix For: 4.0.0
>
> Attachments: Purchasing_Store.bpmn, Purchasing_Store.txt, Screenshots.zip
>
>
> Following the change to generate explicit namespace declarations in the BPMN2 models produced by Savara, I noticed problems in displaying some process models in the BPMN2 modeller.
> I've included the model, a text version of it with annotations (beginning NOTE:) and some images of the warnings and resulting displayed model.
> I've checked the model and it appears to be correct - but just in case will hold off releasing savara until confirmed.
> Initially thought the SequenceFlow sourceRef/targetRef fields were missing the tns: prefix - but when I checked the schema these attributes are IDREF rather than QName.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBTIS-60) Modify devstudio site build to use jbosstools build as input
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-60?page=com.atlassian.jira.plugin.s... ]
Andrej Podhradsky closed JBTIS-60.
----------------------------------
Closed as obsolete
> Modify devstudio site build to use jbosstools build as input
> ------------------------------------------------------------
>
> Key: JBTIS-60
> URL: https://issues.jboss.org/browse/JBTIS-60
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Reporter: Rob Cernich
> Assignee: Paul Leacu
> Fix For: 4.1.0.Final
>
>
> Ideally, the devstudio build should pull in dependencies from the JBT-IS target platform and an existing JBT-IS update site. This removes the need for maintaining two sets of composite*.xml files. It also ensures that a JBT-IS build exists prior to building JBDS-IS.
> This can be accomplished by changing the URL of the repository being used to build devstudio from the local directory to a JBT-IS update site URL.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months