August 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-133) Task created instead of SwitchYard Service Task in BPMN process

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-133?page=com.atlassian.jira.plugin.... ] Paul Leacu updated JBTIS-133: ----------------------------- Assignee: Robert (Bob) Brodt > Task created instead of SwitchYard Service Task in BPMN process > --------------------------------------------------------------- > > Key: JBTIS-133 > URL: https://issues.jboss.org/browse/JBTIS-133 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BPMN2, switchyard > Environment: JBDS 7.0.0.beta2, SOA tooling http://download.jboss.org/jbosstools/updates/integration/kepler/integrati..., SwitchYard 1.0.0 > Reporter: Lucie Fabrikova > Assignee: Robert (Bob) Brodt > > If I want to append a "switchyard service task" in a BPMN process by following steps, just a "task" is created. > Ie. the created task lacks possibility to define "on enter/exit scripts", "attributes". -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2737) Archive old JBDS docs on devstudio.jboss.com

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-2737?page=com.atlassian.jira.plugin.... ] Michelle Murray commented on JBDS-2737: --------------------------------------- As Max says, this should be an archive only. It is simply a store so that old docs remain available on the internet. Otherwise, as small updates are published to current docs they will have to copied to this new location too. I prefer [0] as an archive. Can we just leave it at that? With some intro text: "This is an archive of the documentation accompanying JBoss Developer Studio releases. For the most up-to-date documentation see https://access.redhat.com/site/documentation/Red_Hat_JBoss_Developer_Studio/." If others want to keep the html too, we don't need both [1] and [2]. [1] has all the docs and [2] only has some. [1] is the archive page we need with the 3.0 and 4.0 docs that are going to disappear from access.redhat. Not sure about the HTML versions as they've lost all the Red Hat branding. Also while first page of each doc is there, subsequent pages seem to be missing. For example, [3]. [0] https://devstudio.jboss.com/download/documentation/ [1] https://devstudio.jboss.com/site/documentation/en-US/JBoss_Developer_Studio/ [2] https://devstudio.jboss.com/site/documentation/en-US/Red_Hat_JBoss_Develo... [3] https://devstudio.jboss.com/site/documentation//en-US/JBoss_Developer_Stu... > Archive old JBDS docs on devstudio.jboss.com > --------------------------------------------- > > Key: JBDS-2737 > URL: https://issues.jboss.org/browse/JBDS-2737 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: documentation > Affects Versions: 3.0.1.GA, 4.0.1.GA, 4.1.3.GA, 5.0.2.GA, 6.0.0.GA, 7.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Attachments: JBDS2737_draft-css.png > > > This is a workaround for https://bugzilla.redhat.com/show_bug.cgi?id=983934 because it's easier to download the internet (apparently) than to fix portal code. *sigh* > Docs will be posted to devstudio.jboss.com/site/documentation/ as they include absolute path references. > _Hack: 1. Proper solution: 0._ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-70) JBTIS Kepler component content

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-70?page=com.atlassian.jira.plugin.s... ] Paul Leacu resolved JBTIS-70. ----------------------------- Fix Version/s: 4.1.2 (was: 4.1.0.Beta1) Resolution: Done All Kepler IS component content accounted for - FSW 6.0 Beta1. > JBTIS Kepler component content > ------------------------------ > > Key: JBTIS-70 > URL: https://issues.jboss.org/browse/JBTIS-70 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: BPEL, BPMN2, drools/ jBPM5, ESB, Fuse IDE, modeshape, savara, switchyard, teiid > Affects Versions: 4.1.0.Beta1 > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 4.1.2 > > > Welcome to Kepler. > JBTIS 4.1.0/JBDSIS 7.0.0 is now available on master/trunk. This is needed for JBDS 7.0 in SOA-P 6.0 Beta. Please specify your compatible component for Kepler and update your contribution to the integration stack. The release procedure is here: > https://community.jboss.org/wiki/IntegrationToolingReleaseProcess > The specific files to change are: > https://github.com/jbosstools/jbosstools-integration-stack/blob/master/jb... > https://github.com/jbosstools/jbosstools-integration-stack/blob/master/jb... > https://github.com/jbosstools/jbosstools-integration-stack/blob/master/de... > https://github.com/jbosstools/jbosstools-integration-stack/blob/master/de... > The Kepler JBTIS target platform is here: > https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... > I'll process the PR and regenerate the aggregate update site. > Thanks! > --paull -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-71) BPEL/BPMN2 - Kepler component content - JBTIS 4.1.0

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-71?page=com.atlassian.jira.plugin.s... ] Paul Leacu resolved JBTIS-71. ----------------------------- Fix Version/s: 4.1.2 (was: 4.1.0.Beta1) Resolution: Done Kepler content updated - ref JBTIS-149 > BPEL/BPMN2 - Kepler component content - JBTIS 4.1.0 > --------------------------------------------------- > > Key: JBTIS-71 > URL: https://issues.jboss.org/browse/JBTIS-71 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: BPEL, BPMN2 > Affects Versions: 4.1.0.Beta1 > Reporter: Paul Leacu > Assignee: Robert (Bob) Brodt > Fix For: 4.1.2 > > > Welcome to Kepler. > JBTIS 4.1.0/JBDSIS 7.0.0 is now available on master/trunk. This is needed for JBDS 7.0 in SOA-P 6.0 Beta. Please specify your compatible component for Kepler and update your contribution to the integration stack. The release procedure is here: > https://community.jboss.org/wiki/IntegrationToolingReleaseProcess > The specific files to change are: > https://github.com/jbosstools/jbosstools-integration-stack/blob/master/jb... > https://github.com/jbosstools/jbosstools-integration-stack/blob/master/jb... > https://github.com/jbosstools/jbosstools-integration-stack/blob/master/de... > https://github.com/jbosstools/jbosstools-integration-stack/blob/master/de... > The Kepler JBTIS target platform is here: > https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... > I'll process the PR and regenerate the aggregate update site. > Thanks! > --paull -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-135) JBDSIS - filter out non-production components (i.e. Savara)

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-135?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-135. ------------------------------ Fix Version/s: 4.1.2 Resolution: Done Updated site category.xml. https://github.com/jbosstools/jbosstools-integration-stack/commit/ad59d4d... > JBDSIS - filter out non-production components (i.e. Savara) > ----------------------------------------------------------- > > Key: JBTIS-135 > URL: https://issues.jboss.org/browse/JBTIS-135 > Project: JBoss Tools Integration Stack > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 4.1.0.Beta1 > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 4.1.2 > > > The JBDSIS production build draws from the community (JBTIS) build. Not all community components belong in the production build (i.e. savara). Filter out savara and anything else that does not belong. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14506) CordovaSim: need to implement Phonegap's Card Reader plugin

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14506?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-14506: -------------------------------- Description: Credit card scanning for mobile apps - https://www.card.io/ Plug-in exposes card.io credit card scanning -https://github.com/phonegap/phonegap-plugins/tree/master/Android/card.io was:Plug-in exposes card.io credit card scanning -https://github.com/phonegap/phonegap-plugins/tree/master/Android/card.io > CordovaSim: need to implement Phonegap's Card Reader plugin > ----------------------------------------------------------- > > Key: JBIDE-14506 > URL: https://issues.jboss.org/browse/JBIDE-14506 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.2.x > > > Credit card scanning for mobile apps - https://www.card.io/ > Plug-in exposes card.io credit card scanning -https://github.com/phonegap/phonegap-plugins/tree/master/Android/card.io -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14506) CordovaSim: need to implement Phonegap's Card Reader plugin

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14506?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-14506: -------------------------------- Description: Plug-in exposes card.io credit card scanning -https://github.com/phonegap/phonegap-plugins/tree/master/Android/card.io (was: Here is a description of card.io iOS plug-in for PhoneGap (plugin is IOS specific) https://github.com/phonegap/phonegap-plugins/tree/master/iOS/card.io) > CordovaSim: need to implement Phonegap's Card Reader plugin > ----------------------------------------------------------- > > Key: JBIDE-14506 > URL: https://issues.jboss.org/browse/JBIDE-14506 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.2.x > > > Plug-in exposes card.io credit card scanning -https://github.com/phonegap/phonegap-plugins/tree/master/Android/card.io -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2739) Support per-application environment variables for OpenShift

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2739?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-2739: ------------------------------------------- note - we already support listing env variables, but that is currently done via ssh. This feature means using the API to get it but is not available in the supported api yet. > Support per-application environment variables for OpenShift > ----------------------------------------------------------- > > Key: JBDS-2739 > URL: https://issues.jboss.org/browse/JBDS-2739 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Andy Goldstein > Assignee: Andre Dietisheim > Labels: openshift > > OpenShift will soon add support for per-application environment variables. This includes: > - specifying 1 or more environment variables at app creation > - adding 1 or more environment variables to an app > - deleting 1 or more environment variables from an app > - listing an app's environment variables > - showing the values of 1 or more environment variables for an app -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2740) Support multiple namespaces in OpenShift

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-2740?page=com.atlassian.jira.plugin.... ] Andre Dietisheim reassigned JBDS-2740: -------------------------------------- Assignee: Andre Dietisheim > Support multiple namespaces in OpenShift > ---------------------------------------- > > Key: JBDS-2740 > URL: https://issues.jboss.org/browse/JBDS-2740 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Andy Goldstein > Assignee: Andre Dietisheim > Labels: openshift > > OpenShift will soon add support for a user to have access to multiple namespaces. This includes: > - a user creates and owns multiple namespaces > - a user has permission to work with a domain owned by another user (with differing permission levels) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2739) Support per-application environment variables for OpenShift

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-2739?page=com.atlassian.jira.plugin.... ] Andre Dietisheim reassigned JBDS-2739: -------------------------------------- Assignee: Andre Dietisheim > Support per-application environment variables for OpenShift > ----------------------------------------------------------- > > Key: JBDS-2739 > URL: https://issues.jboss.org/browse/JBDS-2739 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Andy Goldstein > Assignee: Andre Dietisheim > Labels: openshift > > OpenShift will soon add support for per-application environment variables. This includes: > - specifying 1 or more environment variables at app creation > - adding 1 or more environment variables to an app > - deleting 1 or more environment variables from an app > - listing an app's environment variables > - showing the values of 1 or more environment variables for an app -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues August 2013