April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3644) Document installer/cdk/devstudio basic workflow

by Jiri Pallich (JIRA)

[ https://issues.jboss.org/browse/JBDS-3644?page=com.atlassian.jira.plugin.... ] Jiri Pallich updated JBDS-3644: ------------------------------- Target Release: 9.1.0.GA > Document installer/cdk/devstudio basic workflow > ----------------------------------------------- > > Key: JBDS-3644 > URL: https://issues.jboss.org/browse/JBDS-3644 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: documentation, installer > Reporter: Max Rydahl Andersen > Priority: Blocker > Fix For: 9.1.0.GA > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22133) Get error "UnsupportedMediaType' when create project/applications from JBT on Mac

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22133?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-22133: ------------------------------------- Could you provide the local template you've been using? > Get error "UnsupportedMediaType' when create project/applications from JBT on Mac > --------------------------------------------------------------------------------- > > Key: JBIDE-22133 > URL: https://issues.jboss.org/browse/JBIDE-22133 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Environment: JBDS 9.1.0 Beta2-v20160127-2213-B262 > Mac OS > Reporter: Xia Zhao > Labels: openshift_v3 > > Get error "UnsupportedMediaType" when create project and applications from JBT on Mac -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22118) Openshift 3 plugin should support "builder" images

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22118?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22118: ------------------------------------- Issue Type: Feature Request (was: Enhancement) > Openshift 3 plugin should support "builder" images > -------------------------------------------------- > > Key: JBIDE-22118 > URL: https://issues.jboss.org/browse/JBIDE-22118 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Environment: JBoss Developer Studio (Core Features) 9.1.0.GA-v20160403-1700-B477 > Openshift plugin 3.1.0.Final-v20160401-2357-B263 > Reporter: Rafael Benevides > Assignee: Jeff Cantrill > Fix For: 4.4.x > > > I installed the following image stream: https://raw.githubusercontent.com/jboss-openshift/application-templates/m... > It contains several "builder" images. I would like to use jboss-eap70-openshift:1.3-Beta to build a JavaEE 7 application available at https://github.com/redhat-helloworld-msa/hello . But the Openshift plugin only shows "templates". > Openshift plugin should support "builder" images. These images contain "builder" on their tags. > Ref: Jan-5-2016 discussion: http://etherpad.corp.redhat.com/OpenShiftAndJBossStudio -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-646) Do not include BPMN2 features in the JBoss Fuse category

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-646?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-646: ---------------------------------- I'm not sure. I definitely don't want to put bpmn2 back into the TP - it changes a lot and usually late in the cycle. We don't want the TP changing too much - it can be risky. I can try removing the bpmn2 components from the fuse category - see if it still works. > Do not include BPMN2 features in the JBoss Fuse category > -------------------------------------------------------- > > Key: JBTIS-646 > URL: https://issues.jboss.org/browse/JBTIS-646 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: distribution > Environment: JBDS-IS 9.0.0.CR1a > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Attachments: jbdsis_fuse_category.png > > > The category JBoss Fuse Development should contain only the following features > - Fuse tooling > - SwitchYard tooling (+ BPEL/BPMN2 support) > All its dependencies such as BPMN2 should be included in the site without specifying in any category (they could be included in the target platform such as BPEL). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-646) Do not include BPMN2 features in the JBoss Fuse category

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-646?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky commented on JBTIS-646: ----------------------------------------- Or maybe the BPMN2 features could be included in the site but the would not be in any category. My point is not to mess the JBoss Fuse categore with the BPMN2 features. Lets have them hidden from the user's view. [~pleacu] is that possible? > Do not include BPMN2 features in the JBoss Fuse category > -------------------------------------------------------- > > Key: JBTIS-646 > URL: https://issues.jboss.org/browse/JBTIS-646 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: distribution > Environment: JBDS-IS 9.0.0.CR1a > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Attachments: jbdsis_fuse_category.png > > > The category JBoss Fuse Development should contain only the following features > - Fuse tooling > - SwitchYard tooling (+ BPEL/BPMN2 support) > All its dependencies such as BPMN2 should be included in the site without specifying in any category (they could be included in the target platform such as BPEL). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-646) Do not include BPMN2 features in the JBoss Fuse category

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-646?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky edited comment on JBTIS-646 at 4/7/16 8:50 AM: ----------------------------------------------------------------- Or maybe the BPMN2 features could be included in the site but they would not be in any category. My point is not to mess the JBoss Fuse categore with the BPMN2 features. Lets have them hidden from the user's view. [~pleacu] is that possible? was (Author: apodhrad): Or maybe the BPMN2 features could be included in the site but the would not be in any category. My point is not to mess the JBoss Fuse categore with the BPMN2 features. Lets have them hidden from the user's view. [~pleacu] is that possible? > Do not include BPMN2 features in the JBoss Fuse category > -------------------------------------------------------- > > Key: JBTIS-646 > URL: https://issues.jboss.org/browse/JBTIS-646 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: distribution > Environment: JBDS-IS 9.0.0.CR1a > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Attachments: jbdsis_fuse_category.png > > > The category JBoss Fuse Development should contain only the following features > - Fuse tooling > - SwitchYard tooling (+ BPEL/BPMN2 support) > All its dependencies such as BPMN2 should be included in the site without specifying in any category (they could be included in the target platform such as BPEL). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-641) create both master and staging discovery composites/ metadata

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-641?page=com.atlassian.jira.plugin.... ] Paul Leacu closed JBTIS-641. ---------------------------- Resolution: Done Modified discovery composites generation and and script to support creation of both a 'master' snapshot composite and staging/build-type based composites. https://github.com/jbosstools/jbosstools-integration-stack/commit/41a57d1... > create both master and staging discovery composites/ metadata > ------------------------------------------------------------- > > Key: JBTIS-641 > URL: https://issues.jboss.org/browse/JBTIS-641 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 4.3.0.Final, 9.0.0.GA > > > Modify the discovery generation utility to create both 'master' and staging composites/ metadata. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-641) create both master and staging discovery composites/ metadata

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-641?page=com.atlassian.jira.plugin.... ] Paul Leacu updated JBTIS-641: ----------------------------- Summary: create both master and staging discovery composites/ metadata (was: create both master and staging discovery compoistes/ metadata) > create both master and staging discovery composites/ metadata > ------------------------------------------------------------- > > Key: JBTIS-641 > URL: https://issues.jboss.org/browse/JBTIS-641 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 4.3.0.Final, 9.0.0.GA > > > Modify the discovery generation utility to create both 'master' and staging composites/ metadata. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-646) Do not include BPMN2 features in the JBoss Fuse category

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-646?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky commented on JBTIS-646: ----------------------------------------- It is completely ok that SY depends on BPMN2. It also depends on BPEL but the BPEL depedencies are not included in any category on early access. I suggest to have the BPMN2 dependencies as the BPEL ones. If you look at https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/earl... then you can see that all needed dependencies are located in the target platform folder which is the folder where I want to move the BPMN2 bundles into. > Do not include BPMN2 features in the JBoss Fuse category > -------------------------------------------------------- > > Key: JBTIS-646 > URL: https://issues.jboss.org/browse/JBTIS-646 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: distribution > Environment: JBDS-IS 9.0.0.CR1a > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Attachments: jbdsis_fuse_category.png > > > The category JBoss Fuse Development should contain only the following features > - Fuse tooling > - SwitchYard tooling (+ BPEL/BPMN2 support) > All its dependencies such as BPMN2 should be included in the site without specifying in any category (they could be included in the target platform such as BPEL). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-640) Cannot install JBDS-IS EA in offline mode

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-640?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-640. ------------------------------ Fix Version/s: 9.0.0.CR1a Resolution: Done Corrected - see: https://github.com/jbosstools/jbosstools-integration-stack/commit/b80d747... > Cannot install JBDS-IS EA in offline mode > ----------------------------------------- > > Key: JBTIS-640 > URL: https://issues.jboss.org/browse/JBTIS-640 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 9.0.0.CR1 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Blocker > Fix For: 9.0.0.CR1a > > > When installing JBDS-IS 9.0.0.CR1 EA from the zip file I'm getting the following > {code} > Cannot complete the install because one or more required items could not be found. > Software being installed: JBoss Fuse Tooling Core Bundles 8.0.0.Beta2-v20160401-1305-B821 (org.fusesource.ide.core.feature.feature.group 8.0.0.Beta2-v20160401-1305-B821) > Missing requirement: JBoss Fuse Tooling Core Bundles 8.0.0.Beta2-v20160401-1305-B821 (org.fusesource.ide.core.feature.feature.group 8.0.0.Beta2-v20160401-1305-B821) requires 'org.eclipse.zest.core 1.5.100' but it could not be found > {code} > EDIT: this can be resolved by adding JBDS-IS 9.0.0.CR1 zip file (the GA one) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

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 April 2016