May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-157) add nexus releases to site projects

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-157?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-157. ----------------------------------- Closed as obsolete > add nexus releases to site projects > ----------------------------------- > > Key: JBTIS-157 > URL: https://issues.jboss.org/browse/JBTIS-157 > Project: JBoss Tools Integration Stack > Issue Type: Task > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 4.1.3.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-168) Add bpmn2 editor and upgrade fuseide for FSW 6.0 beta1

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-168?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-168. ----------------------------------- Closed as obsolete > 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 > Affects Versions: 4.0.0 > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 4.1.3.Final > > > Add BPMN2 as a composite component + discovery connector component. > Add new version of fuseide. > Bump the aggregate to version 4.1.3 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-162) Should JBTIS have a "unified" target platform which references a single URL instead of a myriad of them?

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-162?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-162. ----------------------------------- Closed as obsolete > Should JBTIS have a "unified" target platform which references a single URL instead of a myriad of them? > -------------------------------------------------------------------------------------------------------- > > Key: JBTIS-162 > URL: https://issues.jboss.org/browse/JBTIS-162 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: target-platform > Affects Versions: 4.0.0 > Reporter: Nick Boldt > Assignee: Paul Leacu > > JBT has two types of .target files: > * multiple [1], which references multiple upstream URLs from which its IUs are sourced, and > * unified [2], which references a single update site, which is the published site generated from materializing the multiple target, then replacing all the URLs w/ that new single, unified URL. > [1] https://repository.jboss.org/nexus/content/groups/public/org/jboss/tools/... > [2] https://repository.jboss.org/nexus/content/groups/public/org/jboss/tools/... > Should JBTIS have a similar notion? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-167) remove coretests from the JBTIS TP

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-167?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-167. ----------------------------------- Closed as obsolete > remove coretests from the JBTIS TP > ---------------------------------- > > Key: JBTIS-167 > URL: https://issues.jboss.org/browse/JBTIS-167 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: target-platform > Affects Versions: 4.1.6.Final-TP > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 4.1.6.Final-TP > > > remove: > <unit id="org.jboss.tools.tests" version="3.5.0.Final-v20130717-0450-B102"/> > <repository location="http://download.jboss.org/jbosstools/updates/nightly/coretests/4.1.kepler/"/> -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-199) Update category names for installer.

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-199?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-199. ----------------------------------- Verified with JBDS-IS 7.1.0.GA > Update category names for installer. > ------------------------------------ > > Key: JBTIS-199 > URL: https://issues.jboss.org/browse/JBTIS-199 > Project: JBoss Tools Integration Stack > Issue Type: Task > Affects Versions: 4.0.0 > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 4.1.3.Final > > > I've received two potentially contradictory BZs ([1], [2]) and there's been recent discussion > involving the JBDSIS 7.0.0.Beta4 category names. This would affect both equinox/p2 and JBoss > Central mylyn/discovery labelling. The issue is the following - currently the p2 installer presents > the user with this: > > JBoss Business Process and Rules development > > JBoss Data Virtualization development > > JBoss Fuse development > > JBoss SOA 5.x development > > JBoss SOA development > The site category name definitions are inconsistent because there's a mixture of product names and > abstract concept labelling. The idea was to have FuseSource users and legacy 5.x SOA users have > an easy time finding what they needed to install and a general user could figure out what they wanted > by the abstract concept label. These are expandable categories - if the user wants to know what their > getting they can expand the category. > BZ [1] suggests changing the following: > Option [A]: > > JBoss Business Process and Rules development > > JBoss Data Virtualization development > > JBoss Fuse development > > JBoss SOA 5.x development > > JBoss Fuse Service Works > That clearly leaves us with 2 "Fuse" categories, one of which doesn't contain the Fuse features, and > expands on the product name based category labelling. If you're installing 'Fuse Service Works' it > could be argued that you'd expect to find that as a choice. > Alan made an interesting suggestion to combine SOA and Fuse, keeping the abstract labelling and > resulting in the following: > Option [B]: > > JBoss Business Process and Rules development > > JBoss Data Virtualization development > > JBoss Integration development > > JBoss SOA 5.x development > That leaves the 'SOA 5.x' category as an outlier. Acceptable? Would something like this be better? > Option [C]: > > JBoss Business Process and Rules development > > JBoss Data Virtualization development > > JBoss Integration development > > JBoss Legacy Integration development > > Applying the combine Fuse algorithm to [A] you could also have this: > > Option [D]: > > JBoss Business Process and Rules development > > JBoss Data Virtualization development > > JBoss Fuse Service Works > > JBoss SOA 5.x development > So - we're post-beta and I'm happy to accommodate the consensus - WDYT? > Thanks, > --paull > [1] https://bugzilla.redhat.com/show_bug.cgi?id=1021282 > [2] https://bugzilla.redhat.com/show_bug.cgi?id=1021283 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-185) Bump community version to 4.1.3.Beta5 for beta refresh

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-185?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-185. ----------------------------------- Closed as obsolete > Bump community version to 4.1.3.Beta5 for beta refresh > ------------------------------------------------------ > > Key: JBTIS-185 > URL: https://issues.jboss.org/browse/JBTIS-185 > Project: JBoss Tools Integration Stack > Issue Type: Task > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 4.1.3.Final > > > Bump beta version for post initial beta (i.e. beta refresh) to beta5. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-172) "JBoss jbpm5 runtime extension feature" is not using Red Hat license text

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-172?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky commented on JBTIS-172: ----------------------------------------- [~bbrodt] could you have a look at it, please? > "JBoss jbpm5 runtime extension feature" is not using Red Hat license text > ------------------------------------------------------------------------- > > Key: JBTIS-172 > URL: https://issues.jboss.org/browse/JBTIS-172 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: drools/ jBPM > Affects Versions: 4.1.0.Final, 9.0.0.GA > Reporter: Max Rydahl Andersen > Assignee: Robert (Bob) Brodt > > When installing from Beta1 "JBoss jbpm5 runtime extension feature" uses Eclipse Foundation Software User Agreement. > It should be using Red Hat, Inc. instead. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-172) "JBoss jbpm5 runtime extension feature" is not using Red Hat license text

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-172?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-172: ------------------------------------ Affects Version/s: 9.0.0.GA > "JBoss jbpm5 runtime extension feature" is not using Red Hat license text > ------------------------------------------------------------------------- > > Key: JBTIS-172 > URL: https://issues.jboss.org/browse/JBTIS-172 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: drools/ jBPM > Affects Versions: 4.1.0.Final, 9.0.0.GA > Reporter: Max Rydahl Andersen > Assignee: Robert (Bob) Brodt > > When installing from Beta1 "JBoss jbpm5 runtime extension feature" uses Eclipse Foundation Software User Agreement. > It should be using Red Hat, Inc. instead. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22361) OpenShift Explorer: Watcher does not work

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22361?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-22361: --------------------------------------- Added steps to reproduce to have more descriptive and explicit workflow. > OpenShift Explorer: Watcher does not work > ----------------------------------------- > > Key: JBIDE-22361 > URL: https://issues.jboss.org/browse/JBIDE-22361 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Marián Labuda > Priority: Critical > Labels: explorer, openshift_v3 > > When I am trying to create a new application based on eap 6.4 template and I am having only one project in OpenShift Explorer view, watcher does not work. Once I create a new EAP 6.4 application there is eap-app-1-build pod all the time in running state. Once watcher should update resources automatically, service is collapsed, also project is collapsed, but after expanding those tree items, there is still old pod. Current pod is visible only upon refresh of a project. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22361) OpenShift Explorer: Watcher does not work

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22361?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-22361: ---------------------------------- Steps to Reproduce: ASSERT: Have an OpenSHift 3 connection. EXEC: Create new project for the connection. EXEC: Open New OpenShift Application wizard, use existing connection, select e.g. eap 6.4. basic s2i template and proceed to create a new application. ASSERT: There is a running Build pod under an EAP service in OpenShift Explorer view. RESULT: The build pod is still there in running state OR once the build is finished (you can check it via oc binary or web ui), project is collapsed but upon expanding a project there is still only build pod in running state (although application pod is up and running on OpenShift server). EXPECTED RESULT: Watcher updates view once a build is finished and shows application pod in its current state. > OpenShift Explorer: Watcher does not work > ----------------------------------------- > > Key: JBIDE-22361 > URL: https://issues.jboss.org/browse/JBIDE-22361 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Marián Labuda > Priority: Critical > Labels: explorer, openshift_v3 > > When I am trying to create a new application based on eap 6.4 template and I am having only one project in OpenShift Explorer view, watcher does not work. Once I create a new EAP 6.4 application there is eap-app-1-build pod all the time in running state. Once watcher should update resources automatically, service is collapsed, also project is collapsed, but after expanding those tree items, there is still old pod. Current pod is visible only upon refresh of a project. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues May 2016