[ https://issues.jboss.org/browse/JBTIS-225?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky closed JBTIS-225.
-----------------------------------
Closed as obsolete
> Respin bpmn2 modeler 1.0.1
> --------------------------
>
> Key: JBTIS-225
> URL: https://issues.jboss.org/browse/JBTIS-225
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Components: BPMN2, distribution, target-platform
> Affects Versions: 4.1.6.Final-TP, 4.1.3.Final
> Reporter: Paul Leacu
> Assignee: Paul Leacu
>
> Can you please do another refresh of the JBTIS mirror from here [2]
> This fixes the following BZs:
> Bug 423809: BPMN2 diagram not displayed if location missing from import element
> Bug 423638: Can't see the name of tasks dragged into expanded sub-process
> Bug 423426: Cannot add interfaces and datatype/message/error/...
> Bug 423752: Import interface to process generates an XML which cannot be parsed
> [2] http://download.eclipse.org/bpmn2-modeler/updates/kepler/1.0.1/
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[ https://issues.jboss.org/browse/JBTIS-230?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky closed JBTIS-230.
-----------------------------------
Closed as obsolete
> Please update target platform dependencies to .Final
> ----------------------------------------------------
>
> Key: JBTIS-230
> URL: https://issues.jboss.org/browse/JBTIS-230
> Project: JBoss Tools Integration Stack
> Issue Type: Sub-task
> Components: modeshape
> Affects Versions: 7.0.0.GA
> Reporter: Paul Leacu
> Assignee: Dan Florian
> Fix For: 4.1.3.Final, 7.0.0.GA
>
>
> Please respin your component to include JBTIS TP 4.1.5.Final
> On Dec. 8 JBossTools released version 4.1.1.Final of core and coretests:
> http://download.jboss.org/jbosstools/updates/JBossTools-4.1.1.Final.core/
> http://download.jboss.org/jbosstools/updates/JBossTools-4.1.1.Final.coret...
> These (and some other) changes have been picked up by the JBTIS TP 4.1.5.Final release (also by JBTIS TP 4.1.5.CR3):
> https://repository.jboss.org/nexus/content/repositories/releases/org/jbos...
> Most of the aggregate components pick up the nexus version of the JBTIS target platform. We need for you to rebuild and resubmit your component built using the .Final JBTIS TP (which gets you JBDS core/coretests .Final) so we:
> 1. Know as early as possible if the .Final broke anyone
> 2. Establish a stable TP for subsequent kepler releases
> This needs to be done for the Jan. 8 DV/FSW 6.0 tooling capture.
> Thanks!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[ https://issues.jboss.org/browse/JBTIS-229?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky closed JBTIS-229.
-----------------------------------
Closed as obsolete
> Please update target platform dependencies to .Final
> ----------------------------------------------------
>
> Key: JBTIS-229
> URL: https://issues.jboss.org/browse/JBTIS-229
> Project: JBoss Tools Integration Stack
> Issue Type: Sub-task
> Components: ESB
> Affects Versions: 7.0.0.GA
> Reporter: Paul Leacu
> Assignee: Brian Fitzpatrick
> Fix For: 4.1.3.Final, 7.0.0.GA
>
>
> Please respin your component to include JBTIS TP 4.1.5.Final
> On Dec. 8 JBossTools released version 4.1.1.Final of core and coretests:
> http://download.jboss.org/jbosstools/updates/JBossTools-4.1.1.Final.core/
> http://download.jboss.org/jbosstools/updates/JBossTools-4.1.1.Final.coret...
> These (and some other) changes have been picked up by the JBTIS TP 4.1.5.Final release (also by JBTIS TP 4.1.5.CR3):
> https://repository.jboss.org/nexus/content/repositories/releases/org/jbos...
> Most of the aggregate components pick up the nexus version of the JBTIS target platform. We need for you to rebuild and resubmit your component built using the .Final JBTIS TP (which gets you JBDS core/coretests .Final) so we:
> 1. Know as early as possible is the .Final broke anyone
> 2. Establish a stable TP for subsequent kepler releases
> This needs to be done for the Jan. 8 DV/FSW 6.0 tooling capture.
> Thanks!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[ https://issues.jboss.org/browse/JBTIS-228?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky closed JBTIS-228.
-----------------------------------
Closed as obsolete
> Please update target platform dependencies to .Final
> ----------------------------------------------------
>
> Key: JBTIS-228
> URL: https://issues.jboss.org/browse/JBTIS-228
> Project: JBoss Tools Integration Stack
> Issue Type: Sub-task
> Components: drools/ jBPM
> Affects Versions: 7.0.0.GA
> Reporter: Paul Leacu
> Assignee: Kris Verlaenen
>
> Please respin your component to include JBTIS TP 4.1.5.Final
> On Dec. 8 JBossTools released version 4.1.1.Final of core and coretests:
> http://download.jboss.org/jbosstools/updates/JBossTools-4.1.1.Final.core/
> http://download.jboss.org/jbosstools/updates/JBossTools-4.1.1.Final.coret...
> These (and some other) changes have been picked up by the JBTIS TP 4.1.5.Final release (also by JBTIS TP 4.1.5.CR3):
> https://repository.jboss.org/nexus/content/repositories/releases/org/jbos...
> Most of the aggregate components pick up the nexus version of the JBTIS target platform. We need for you to rebuild and resubmit your component built using the .Final JBTIS TP (which gets you JBDS core/coretests .Final) so we:
> 1. Know as early as possible is the .Final broke anyone
> 2. Establish a stable TP for subsequent kepler releases
> This needs to be done for the Jan. 8 DV/FSW 6.0 tooling capture.
> Thanks!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[ https://issues.jboss.org/browse/JBTIS-231?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky closed JBTIS-231.
-----------------------------------
Closed as obsolete
> Please update target platform dependencies to .Final
> ----------------------------------------------------
>
> Key: JBTIS-231
> URL: https://issues.jboss.org/browse/JBTIS-231
> Project: JBoss Tools Integration Stack
> Issue Type: Sub-task
> Components: switchyard
> Affects Versions: 7.0.0.GA
> Reporter: Paul Leacu
> Assignee: Rob Cernich
> Fix For: 4.1.3.Final, 7.0.0.GA
>
>
> Please respin your component to include JBTIS TP 4.1.5.Final
> On Dec. 8 JBossTools released version 4.1.1.Final of core and coretests:
> http://download.jboss.org/jbosstools/updates/JBossTools-4.1.1.Final.core/
> http://download.jboss.org/jbosstools/updates/JBossTools-4.1.1.Final.coret...
> These (and some other) changes have been picked up by the JBTIS TP 4.1.5.Final release (also by JBTIS TP 4.1.5.CR3):
> https://repository.jboss.org/nexus/content/repositories/releases/org/jbos...
> Most of the aggregate components pick up the nexus version of the JBTIS target platform. We need for you to rebuild and resubmit your component built using the .Final JBTIS TP (which gets you JBDS core/coretests .Final) so we:
> 1. Know as early as possible if the .Final broke anyone
> 2. Establish a stable TP for subsequent kepler releases
> This needs to be done for the Jan. 8 DV/FSW 6.0 tooling capture.
> Thanks!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[ https://issues.jboss.org/browse/JBTIS-240?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky closed JBTIS-240.
-----------------------------------
Verified with http://download.jboss.org/jbosstools/updates/stable/kepler/integration-st...
> JBTIS Stable Kepler update site contains children which are not update sites
> ----------------------------------------------------------------------------
>
> Key: JBTIS-240
> URL: https://issues.jboss.org/browse/JBTIS-240
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Affects Versions: 4.1.3.Final
> Reporter: Nick Boldt
> Assignee: Paul Leacu
> Fix For: 4.1.4.Final
>
>
> http://download.jboss.org/jbosstools/updates/stable/kepler/integration-st... contains composite metadata which reads:
> {code}
> <children size="2">
> <child location="jbosstools-integration-stack-sources-4.1.3.Final.zip.MD5/"/>
> <child location="4.1.3.Final/"/>
> </children>
> {code}
> Was this generated by a script or manually produced?
> If scripted, looks like a bug upstream in my code - please reassign this to me so we can ensure that MD5 is not seen a child folder to be composited into the site.
> If manual, you should remove the link to the MD5 file as it's not an update site.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)