[ https://issues.jboss.org/browse/JBTIS-20?page=com.atlassian.jira.plugin.s... ]
Paul Leacu reassigned JBTIS-20:
-------------------------------
Assignee: Paul Leacu (was: Douglas Palmer)
> aggregate SOA source features into a single site
> ------------------------------------------------
>
> Key: JBTIS-20
> URL: https://issues.jboss.org/browse/JBTIS-20
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: releng
> Reporter: Nick Boldt
> Assignee: Paul Leacu
> Priority: Blocker
>
--
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
[ https://issues.jboss.org/browse/JBTIS-178?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on JBTIS-178:
-----------------------------------------------
Len DiMaggio <ldimaggi(a)redhat.com> made a comment on [bug 1008611|https://bugzilla.redhat.com/show_bug.cgi?id=1008611]
> In JBTIS 4.1.3.beta2 - The SOA5 category includes Drools6 which may be incompatible with BRMS5 and SOA5
> -------------------------------------------------------------------------------------------------------
>
> Key: JBTIS-178
> URL: https://issues.jboss.org/browse/JBTIS-178
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: drools/ jBPM5
> Reporter: Len DiMaggio
> Assignee: Kris Verlaenen
> Attachments: drools1.png
>
>
> See the attached screenshot - how can JBTIS support both SOA5/BRMS5 and 6?
--
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
[ https://issues.jboss.org/browse/JBTIS-171?page=com.atlassian.jira.plugin.... ]
Paul Leacu commented on JBTIS-171:
----------------------------------
Verified the discovery composite site now contains the "extras" defined by the Jenkins build:
<child location="https://devstudio.jboss.com/updates/7.0/extras/4.30.5/"/>
<child location="https://devstudio.jboss.com/updates/7.0.0/7.0.0.GA.core/"/>
<child location="https://devstudio.jboss.com/updates/7.0.0/7.0.0.GA.target-platform/"/>
<child location="http://www.qa.jboss.com/binaries/RHDS/builds/staging/JBDSIS-aggregate-dis..."/>
<child location="https://devstudio.jboss.com/updates/7.0.0/7.0.0.Beta2.jbds-is-target-plat..."/>
Any further comments/discussion on this one?
> Don't override other connectors in discovery.xml
> ------------------------------------------------
>
> Key: JBTIS-171
> URL: https://issues.jboss.org/browse/JBTIS-171
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: distribution
> Reporter: Max Rydahl Andersen
> Assignee: Paul Leacu
>
> Currently this is in discovery plugin:
> siteUrl="$\{jboss.discovery.site.url:https://devstudio.jboss.com/updates/7.0-development/central/integration-stack/}"
>
> And instructions to test it says:
> -vmargs -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/7.0.0.Beta1/devstudio-integration-stack-directory.xml -Djboss.discovery.site.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/7.0.0.Beta1
> This is all great but it disables all other connectors in JBDS/eclipse thus it makes it hard to get together.
> I suggest you use your own specific site url instead, something like:
> siteUrl="$\{jboss.discovery.integration-stack.site.url:https://devstudio.jboss.com/updates/7.0-development/central/integration-stack/}"
> Then the base connectors will still work.
> We might even consider using recursive properties to allow for a global override, this would need changing in both IS And core discovery.xml to the tune of:
> in core: siteUrl="$\{jboss.global.discovery.site.url,jboss.discovery.site.url:https://devstudio.jboss.com/updates/7.0-development/central/core}"
> in stack:
> siteUrl="$\{jboss.global.discovery.site.url,jboss.discovery.integration-stack.site.url:https://devstudio.jboss.com/updates/7.0-development/central/integration-stack/}"
--
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
[ https://issues.jboss.org/browse/JBTIS-168?page=com.atlassian.jira.plugin.... ]
Paul Leacu resolved JBTIS-168.
------------------------------
Resolution: Done
bpmn2 editor updated for JBTIS 4.1.3.Beta2/ JBDSIS 7.0.0.Beta2
https://github.com/jbosstools/jbosstools-integration-stack/pull/120
> Add bpmn2 editor and upgrade fuseide for FSW 6.0 beta1
> ------------------------------------------------------
>
> Key: JBTIS-168
> URL: https://issues.jboss.org/browse/JBTIS-168
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Affects Versions: 4.1.3
> Reporter: Paul Leacu
> Assignee: Paul Leacu
> Fix For: 4.1.3
>
>
> Add BPMN2 as a composite component + discovery connector component.
> Add new version of fuseide.
> Bump the aggregate to version 4.1.3
--
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
[ https://issues.jboss.org/browse/JBTIS-177?page=com.atlassian.jira.plugin.... ]
Paul Leacu updated JBTIS-177:
-----------------------------
Assignee: Paul Leacu
> Cannot save process definition which contains a local variable
> --------------------------------------------------------------
>
> Key: JBTIS-177
> URL: https://issues.jboss.org/browse/JBTIS-177
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: BPMN2
> Reporter: Len DiMaggio
> Assignee: Paul Leacu
>
> Eclipse bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=417203 Will be resolved in JBTIS 4.1.3.beta2 and JBDSIS 7.0.0.beta2
--
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
[ https://issues.jboss.org/browse/JBTIS-169?page=com.atlassian.jira.plugin.... ]
Paul Leacu resolved JBTIS-169.
------------------------------
Assignee: Paul Leacu
Fix Version/s: 4.1.3
Resolution: Done
Fuse runtime was added to 4.1.3.Beta2 for FSW 6.0 Beta1.
> Missing fuse runtime feature
> ----------------------------
>
> Key: JBTIS-169
> URL: https://issues.jboss.org/browse/JBTIS-169
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Fuse IDE
> Affects Versions: 4.1.2
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
> Priority: Blocker
> Fix For: 4.1.3
>
>
> JBTIS 4.1.2 only these two fuse feature
> * org.fusesource.ide.camel.editor.feature
> * org.fusesource.ide.server.extensions.feature
> but the following one is missing
> * org.fusesource.ide.runtimes.feature
> All fuse features are available at
> http://download.jboss.org/jbosstools/updates/integration/kepler/soa-tooli...
--
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
[ https://issues.jboss.org/browse/JBTIS-178?page=com.atlassian.jira.plugin.... ]
Paul Leacu updated JBTIS-178:
-----------------------------
Component/s: drools/ jBPM5
(was: ESB)
> In JBTIS 4.1.3.beta2 - The SOA5 category includes Drools6 which may be incompatible with BRMS5 and SOA5
> -------------------------------------------------------------------------------------------------------
>
> Key: JBTIS-178
> URL: https://issues.jboss.org/browse/JBTIS-178
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: drools/ jBPM5
> Reporter: Len DiMaggio
> Assignee: Kris Verlaenen
> Attachments: drools1.png
>
>
> See the attached screenshot - how can JBTIS support both SOA5/BRMS5 and 6?
--
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
[ https://issues.jboss.org/browse/JBTIS-178?page=com.atlassian.jira.plugin.... ]
Paul Leacu commented on JBTIS-178:
----------------------------------
Hey Kris -
The question is:
Will the 6.0.0 JBoss Drools works okay with the SOA 5.x compatibility installation (any server incompatibilities, etc)?
Thanks
> In JBTIS 4.1.3.beta2 - The SOA5 category includes Drools6 which may be incompatible with BRMS5 and SOA5
> -------------------------------------------------------------------------------------------------------
>
> Key: JBTIS-178
> URL: https://issues.jboss.org/browse/JBTIS-178
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: ESB
> Reporter: Len DiMaggio
> Assignee: Kris Verlaenen
> Attachments: drools1.png
>
>
> See the attached screenshot - how can JBTIS support both SOA5/BRMS5 and 6?
--
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
[ https://issues.jboss.org/browse/JBTIS-178?page=com.atlassian.jira.plugin.... ]
Paul Leacu updated JBTIS-178:
-----------------------------
Assignee: Kris Verlaenen
> In JBTIS 4.1.3.beta2 - The SOA5 category includes Drools6 which may be incompatible with BRMS5 and SOA5
> -------------------------------------------------------------------------------------------------------
>
> Key: JBTIS-178
> URL: https://issues.jboss.org/browse/JBTIS-178
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: ESB
> Reporter: Len DiMaggio
> Assignee: Kris Verlaenen
> Attachments: drools1.png
>
>
> See the attached screenshot - how can JBTIS support both SOA5/BRMS5 and 6?
--
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
[ https://issues.jboss.org/browse/JBTIS-178?page=com.atlassian.jira.plugin.... ]
Paul Leacu updated JBTIS-178:
-----------------------------
Attachment: drools1.png
JBDSIS 7.0.0.Beta2 p2 update site installation screen capture.
> In JBTIS 4.1.3.beta2 - The SOA5 category includes Drools6 which may be incompatible with BRMS5 and SOA5
> -------------------------------------------------------------------------------------------------------
>
> Key: JBTIS-178
> URL: https://issues.jboss.org/browse/JBTIS-178
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: ESB
> Reporter: Len DiMaggio
> Assignee: Kris Verlaenen
> Attachments: drools1.png
>
>
> See the attached screenshot - how can JBTIS support both SOA5/BRMS5 and 6?
--
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