[JBoss JIRA] (JBIDE-19018) JBT Central Discovery staging site contains early access child site in its composite*.xml
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19018?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-19018:
---------------------------------------------
yes I agree the confusion is co-locating things in staging that are not co-located at release time.
But it is not only a problem if someone browses the updatesite - it hides or rather makes things work that should not work. like if we had a bug in discoery site and marked something without earlyaccess flag this would now be able to install ....if ea site was not included this would fail and QE would more likely notice that something is wrong.
We did this split to ensure things would fail if we did mess things up ;)
> JBT Central Discovery staging site contains early access child site in its composite*.xml
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-19018
> URL: https://issues.jboss.org/browse/JBIDE-19018
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Reporter: Max Rydahl Andersen
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 4.2.2.Final, 4.2.3.Final
>
>
> http://download.jboss.org/jbosstools/discovery/staging/4.2.1.Final/ composites early access site into the main update site, so anyone using that site as an update site (rather than simply as the back end to Central) will see EA content as if it's from Central.
> If we stop publishing this staging discovery site that includes EA content, the release process will need to be updated to pull the EA plugin from another place.
> Related to JBIDE-18984
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBIDE-19017) Prepare for 4.2.2.Final release
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19017?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-19017:
------------------------------------
When the correct version bumps are done, project leads should ensure that their projects' jobs are built to pick up the changes. After that, the rest of the jobs listed above should build automatically, as soon as composite-install notices the new bits.
> Prepare for 4.2.2.Final release
> -------------------------------
>
> Key: JBIDE-19017
> URL: https://issues.jboss.org/browse/JBIDE-19017
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.2.2.Final
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Priority: Blocker
> Fix For: 4.2.2.Final
>
>
> TODOs for preparing for the 4.2.2 release.
> For components that contribute to this release (and only these): Central, WS, Forge, JBT aggregates, JBDS:
> a) ensure we're all using the right TP (4.40.0.Final, 4.41.1.Final) & parent pom version 4.2.1.Final-SNAPSHOT - NO CHANGE SINCE 4.2.1 release; all projects OK
> b) ensure components have properly upversioned to 4.2.2/8.0.2, etc.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBIDE-18999) As a user I want to connect to a v3 OpenShift instance
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18999?page=com.atlassian.jira.plugi... ]
Jeff Cantrill updated JBIDE-18999:
----------------------------------
Description:
Add a wizard and supporting types to represent and create a connection to a v3 OpenShift instance. Assumptions:
* Ignore auth for now
* The connection should be usable to retrieve Kubernetes resources.
was:
* Ignore auth for now
* The connection should be usable to retrieve Kubernetes resources.
> As a user I want to connect to a v3 OpenShift instance
> ------------------------------------------------------
>
> Key: JBIDE-18999
> URL: https://issues.jboss.org/browse/JBIDE-18999
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Reporter: Jeff Cantrill
> Labels: openshift_v3
> Attachments: 2015-01-06 22.09.bmml
>
>
> Add a wizard and supporting types to represent and create a connection to a v3 OpenShift instance. Assumptions:
> * Ignore auth for now
> * The connection should be usable to retrieve Kubernetes resources.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBTIS-378) Update bpmn2 for IS beta2 TP and aggregate - bpmn2 feature source bundle
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-378?page=com.atlassian.jira.plugin.... ]
Paul Leacu resolved JBTIS-378.
------------------------------
Resolution: Done
https://github.com/jbosstools/jbosstools-integration-stack/commit/aefc587...
> Update bpmn2 for IS beta2 TP and aggregate - bpmn2 feature source bundle
> ------------------------------------------------------------------------
>
> Key: JBTIS-378
> URL: https://issues.jboss.org/browse/JBTIS-378
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: BPMN2, distribution
> Reporter: Paul Leacu
> Assignee: Paul Leacu
> Fix For: 4.2.0.Final-TP
>
>
> *Reason:* Create .Final - pick up a bpmn2 feature source bundle.
> *Project page/sources:*
> *Version:* 4.2.0.Final
> *License and owner:* EPL
> *Original p2 repo:*
> *JBoss mirror:*
> *Include Sources:* Yes
> *Affected projects:* JBDSIS 8.0.0.GA
> *Include in JBDS:* No
> *Type of dependency:* distribution
> *List of bundles added/removed:*
> < org.eclipse.bpmn2.editor [0.7.0.201308220617]
> < org.eclipse.bpmn2.edit [0.7.0.201308220617]
> < org.eclipse.bpmn2.modeler.runtime.jboss.feature.jar [1.1.1.201412181844]
> < org.eclipse.bpmn2.feature.feature.jar [0.7.0.201308220617]
> < org.eclipse.bpmn2 [0.7.0.201308220617]
> < org.eclipse.bpmn2.modeler.help [1.1.1.201412181844]
> < org.eclipse.bpmn2.feature.feature.group [0.7.0.201308220617]
> < org.eclipse.bpmn2.modeler.runtime.jboss.feature.group [1.1.1.201412181844]
> < org.eclipse.bpmn2.modeler.feature.jar [1.1.1.201412181844]
> < org.eclipse.bpmn2.modeler.feature.group [1.1.1.201412181844]
> < org.eclipse.bpmn2.modeler.core [1.1.1.201412181844]
> < org.eclipse.bpmn2.modeler.runtime.jboss.jbpm5 [1.1.1.201412181844]
> < org.eclipse.bpmn2.modeler.ui [1.1.1.201412181844]
> > org.eclipse.bpmn2.modeler.help [1.1.1.201501081320]
> > org.eclipse.bpmn2 [1.0.0.201412192138]
> > org.eclipse.bpmn2.modeler.runtime.jboss.feature.jar [1.1.1.201501081320]
> > org.eclipse.bpmn2.modeler.runtime.jboss.jbpm5 [1.1.1.201501081320]
> > org.eclipse.bpmn2.editor [1.0.0.201412192138]
> > org.eclipse.bpmn2.modeler.feature.group [1.1.1.201501081320]
> > org.eclipse.bpmn2.modeler.ui [1.1.1.201501081320]
> > org.eclipse.bpmn2.modeler.core [1.1.1.201501081320]
> > org.eclipse.bpmn2.edit [1.0.0.201412192138]
> > org.eclipse.bpmn2.feature.jar [1.0.0.201412192138]
> > org.eclipse.bpmn2.feature.group [1.0.0.201412192138]
> > org.eclipse.bpmn2.modeler.runtime.jboss.feature.group [1.1.1.201501081320]
> > org.eclipse.bpmn2.modeler.feature.jar [1.1.1.201501081320]
> === Summary ===
> file:///home/pleacu/git-clone/jbosstools-integration-stack.orig/target-platform/target/target-platform.target.repo contains 13 unique IUs
> file:///home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform.target.repo contains 13 unique IUs
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months