May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22362) Static changes done to nodejs application are not visible

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22362?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-22362: ---------------------------------- Labels: openshift_v3 (was: ) > Static changes done to nodejs application are not visible > --------------------------------------------------------- > > Key: JBIDE-22362 > URL: https://issues.jboss.org/browse/JBIDE-22362 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.4.0.Alpha2 > Reporter: Marián Labuda > Priority: Critical > Labels: openshift_v3 > > I am having an OpenShift application based either on nodejs-example or nodejs-mongodb-example template. Once application is up and running I create a new server adapter and perform changes in index.html. These changes are static and should be (?) immediately visible on OpenShift server, but they are not. I have checked whether changes were published, but rsync in console shows expected output also changes done manually on the server side to index.html are not visible in browser (even when cache overwritten is triggered - so there is no caching problem in browser). This seems to be upstream issues, but requires investigating. > So far I have tried it on CDK OpenShift. It would be nice to test it on other OpenShift instances, also on templates using different base docker image. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1) Generate target platforms for JBT/JBDS SOA Tooling which include: JBT/JBDS Core TP + last stable Core milestone

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1?page=com.atlassian.jira.plugin.sy... ] Andrej Podhradsky closed JBTIS-1. --------------------------------- Closed as obsolete > Generate target platforms for JBT/JBDS SOA Tooling which include: JBT/JBDS Core TP + last stable Core milestone > --------------------------------------------------------------------------------------------------------------- > > Key: JBTIS-1 > URL: https://issues.jboss.org/browse/JBTIS-1 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Reporter: Nick Boldt > Assignee: Paul Leacu > Labels: f2f2012 > Fix For: 4.0.0 > > Attachments: JBIDE-11121.tweak.txt, ModeShapeToolsBuildLog.txt > > > Generate target platforms for JBT/JBDS SOA Tooling which include: > 1. JBT Core TP + last stable JBT Core milestone. > 2. JBDS Core TP + last stable JBDS Core milestone. > Then, all SOA Component jobs should be rekeyed to use these new TPs when building instead of the JBT/JBDS Core ones. > This includes Drools, which currently builds against Helios instead of Indigo, and Savara, which has requirements which are not as yet in the JBT/JBDS Core TPs (eg., GMF and Graphiti). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22183) Local folder not saved when creating an Openshift application

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22183?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22183: -------------------------------- Affects Version/s: 4.4.0.Alpha1 (was: 4.4.x) > Local folder not saved when creating an Openshift application > ------------------------------------------------------------- > > Key: JBIDE-22183 > URL: https://issues.jboss.org/browse/JBIDE-22183 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Minor > Fix For: 4.4.0.Alpha2 > > > When a new Openshift application is created, the git repo is cloned onto the local machine but the user must select the local folder each time because the dialog does not save/remember the last used value -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-2) ensure all ten (10) JBT SOA components have published exploded update sites on http://download.jboss.org/jbosstools/updates/

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-2?page=com.atlassian.jira.plugin.sy... ] Andrej Podhradsky closed JBTIS-2. --------------------------------- Closed as obsolete > ensure all ten (10) JBT SOA components have published exploded update sites on http://download.jboss.org/jbosstools/updates/ > ---------------------------------------------------------------------------------------------------------------------------- > > Key: JBTIS-2 > URL: https://issues.jboss.org/browse/JBTIS-2 > Project: JBoss Tools Integration Stack > Issue Type: Task > Reporter: Nick Boldt > Assignee: Paul Leacu > > For each of the JBT SOA components, we should ensure that they're all publishing into standard locations on http://download.jboss.org/jbosstools/updates/. > This issue should be a container for child issues assigned to each project's releng person. > Most important part of this is the documentation of process / rules / expecations / nomenclature, and creation of tooling to make it simple for project leads to publish & promote their bits: > * JBIDE-12220 create generic publishing job which takes as input three parameters > Done: > * SwitchYard - JBIDE-10672 - http://download.jboss.org/jbosstools/updates/stable/indigo/soa-tooling/sw... > * Modeshape Tools - JBBUILD-720, MODE-1506 > *- http://download.jboss.org/jbosstools/updates/development/indigo/soa-tooli... and > *- http://download.jboss.org/jbosstools/updates/development/juno/soa-tooling... > Publishes elsewhere, manually symlinked: > * Drools/jbpm5 - JBRULES-3470 - http://download.jboss.org/jbosstools/updates/stable/indigo/soa-tooling/dr... > Publishes elsewhere: > * Savara - http://download.jboss.org/savara/releases/updates/2.0.x/ > * pi4soa - http://pi4soa.sourceforge.net/updates/ > Publishes as zip only: > * Teiid Designer - https://www.jboss.org/teiiddesigner/downloads/ -> http://sourceforge.net/projects/teiid/files/teiid-designer/7.7/teiid_desi... > No publishing or archiving strategy (staging only): > * SOA Runtime Detection - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk.... > * ESB - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk.... > * jbpm3 - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk.... > --> see also https://issues.jboss.org/browse/JBIDE-12631 > * JBoss BPEL - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk.... > --- > Once all the components are publishing sites, they can > a) easily link to those individual sites from their download pages on www.jboss.org/{projectname} > b) easily composite those sites into a single site and reference that site from www.jboss.org/tools/ > c) more easily aggregate the components into a single site & zip, proving that the content can be co-installed via p2 and that there are no unmet or conflicting dependencies > d) (with a through c met) therefore provide additional stability checking for JBDS SOA/BRMS tooling, provided individually via JBDS Central. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22183) Local folder not saved when creating an Openshift application

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22183?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22183: -------------------------------- Story Points: 1 > Local folder not saved when creating an Openshift application > ------------------------------------------------------------- > > Key: JBIDE-22183 > URL: https://issues.jboss.org/browse/JBIDE-22183 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Minor > Fix For: 4.4.0.Alpha2 > > > When a new Openshift application is created, the git repo is cloned onto the local machine but the user must select the local folder each time because the dialog does not save/remember the last used value -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-8) JBossTools Integration Stack :: drools: Verify the component configuration of the initial IS tooling release.

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-8?page=com.atlassian.jira.plugin.sy... ] Andrej Podhradsky closed JBTIS-8. --------------------------------- Closed as obsolete > JBossTools Integration Stack :: drools: Verify the component configuration of the initial IS tooling release. > ------------------------------------------------------------------------------------------------------------- > > Key: JBTIS-8 > URL: https://issues.jboss.org/browse/JBTIS-8 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Components: drools/ jBPM > Environment: JBT 4.0 > Reporter: Paul Leacu > Assignee: Kris Verlaenen > > Please verify your component configuration of the JBoss Integration Stack for a JBoss Tools 4.0 target. > Also check that all components are compatible with the upstream components defined in the target platform. > ref: > https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/... > https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/... - compositeContent.xml > https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/... > I'm working on getting this project promoted to jbosstools in github. Unitl then please refer to/fork the urls above. There is a best-guess already specified for each component. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-7) JBossTools Integration Stack :: ESB: Verify the component configuration of the initial IS tooling release.

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-7?page=com.atlassian.jira.plugin.sy... ] Andrej Podhradsky closed JBTIS-7. --------------------------------- Closed as obsolete > JBossTools Integration Stack :: ESB: Verify the component configuration of the initial IS tooling release. > ---------------------------------------------------------------------------------------------------------- > > Key: JBTIS-7 > URL: https://issues.jboss.org/browse/JBTIS-7 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Components: ESB > Environment: JBT 4.0 > Reporter: Paul Leacu > Assignee: Brian Fitzpatrick > > Please verify your component configuration of the JBoss Integration Stack for a JBoss Tools 4.0 target. > Also check that all components are compatible with the upstream components defined in the target platform. > ref: > https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/... > https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/... - compositeContent.xml > https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/... > I'm working on getting this project promoted to jbosstools in github. Unitl then please refer to/fork the urls above. There is a best-guess already specified for each component. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-6) JBossTools Integration Stack :: BPMN2: Verify the component configuration of the initial IS tooling release.

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-6?page=com.atlassian.jira.plugin.sy... ] Andrej Podhradsky closed JBTIS-6. --------------------------------- Closed as obsolete > JBossTools Integration Stack :: BPMN2: Verify the component configuration of the initial IS tooling release. > ------------------------------------------------------------------------------------------------------------ > > Key: JBTIS-6 > URL: https://issues.jboss.org/browse/JBTIS-6 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Components: BPMN2 > Environment: JBT 4.0 > Reporter: Paul Leacu > Assignee: Paul Leacu > > Please verify your component configuration of the JBoss Integration Stack for a JBoss Tools 4.0 target. > Also check that all components are compatible with the upstream components defined in the target platform. > ref: > https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/... > https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/... - compositeContent.xml > https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/... > I'm working on getting this project promoted to jbosstools in github. Unitl then please refer to/fork the urls above. There is a best-guess already specified for each component. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-5) JBossTools Integration Stack :: BPEL: Verify the component configuration of the initial IS tooling release.

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-5?page=com.atlassian.jira.plugin.sy... ] Andrej Podhradsky closed JBTIS-5. --------------------------------- Closed as obsolete > JBossTools Integration Stack :: BPEL: Verify the component configuration of the initial IS tooling release. > ----------------------------------------------------------------------------------------------------------- > > Key: JBTIS-5 > URL: https://issues.jboss.org/browse/JBTIS-5 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Components: BPEL > Environment: JBT 4.0 > Reporter: Paul Leacu > Assignee: Paul Leacu > > Please verify your component configuration of the JBoss Integration Stack for a JBoss Tools 4.0 target. > Also check that all components are compatible with the upstream components defined in the target platform. > ref: > https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/... > https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/... - compositeContent.xml > https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/... > I'm working on getting this project promoted to jbosstools in github. Unitl then please refer to/fork the urls above. There is a best-guess already specified for each component. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-4) Verify the component configuration of the initial Integration Stack tooling release.

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-4?page=com.atlassian.jira.plugin.sy... ] Andrej Podhradsky closed JBTIS-4. --------------------------------- Closed as obsolete > Verify the component configuration of the initial Integration Stack tooling release. > ------------------------------------------------------------------------------------ > > Key: JBTIS-4 > URL: https://issues.jboss.org/browse/JBTIS-4 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: BPEL, BPMN2, ESB, jBPM3, modeshape, runtime-soa, savara, switchyard, teiid > Environment: JBT 4.0 > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 4.0.0 > > > Please verify your component configuration of the JBoss Integration Stack for a JBoss Tools 4.0 target. > ref: > https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/... > https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/... - compositeContent.xml > https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/... > I'm working on getting this project promoted to jbosstools in github. Unitl then please refer to/fork the urls above. There is a best-guess already specified for each component. -- 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