February 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-19086) use delegating progress monitor in foundation.core (was: common.ui)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19086?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19086: ------------------------------------- Comment: was deleted (was: This was caused by JBIDE-15058 which replaced the DelegatingProgressMonitor in common.ui with the one in foundation.core) > use delegating progress monitor in foundation.core (was: common.ui) > ------------------------------------------------------------------- > > Key: JBIDE-19086 > URL: https://issues.jboss.org/browse/JBIDE-19086 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: common/jst/core > Affects Versions: 4.2.2.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Alpha1 > > > WizardUtils is using *org.jboss.tools.common.ui.* DelegatingProgressMonitor. The DelegatingProgressMonitor was moved to *org.jboss.tools.common.core* while keeping an empty class in common.ui for compatibility reasons. We should now use the "new" class in core. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19086) use delegating progress monitor in foundation.core (was: common.ui)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19086?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-19086 at 2/13/15 7:05 PM: ------------------------------------------------------------------- This was caused by JBIDE-15058 which replaced the DelegatingProgressMonitor in common.ui with the one in foundation.core was (Author: adietish): This was caused by JBIDE-15058 > use delegating progress monitor in foundation.core (was: common.ui) > ------------------------------------------------------------------- > > Key: JBIDE-19086 > URL: https://issues.jboss.org/browse/JBIDE-19086 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: common/jst/core > Affects Versions: 4.2.2.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Alpha1 > > > WizardUtils is using *org.jboss.tools.common.ui.* DelegatingProgressMonitor. The DelegatingProgressMonitor was moved to *org.jboss.tools.common.core* while keeping an empty class in common.ui for compatibility reasons. We should now use the "new" class in core. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19086) use delegating progress monitor in foundation.core (was: common.ui)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19086?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19086: ------------------------------------------ This was caused by JBIDE-15058 > use delegating progress monitor in foundation.core (was: common.ui) > ------------------------------------------------------------------- > > Key: JBIDE-19086 > URL: https://issues.jboss.org/browse/JBIDE-19086 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: common/jst/core > Affects Versions: 4.2.2.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Alpha1 > > > WizardUtils is using *org.jboss.tools.common.ui.* DelegatingProgressMonitor. The DelegatingProgressMonitor was moved to *org.jboss.tools.common.core* while keeping an empty class in common.ui for compatibility reasons. We should now use the "new" class in core. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19267) OpenOns for batch artifacts

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-19267: -------------------------------------- Summary: OpenOns for batch artifacts Key: JBIDE-19267 URL: https://issues.jboss.org/browse/JBIDE-19267 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: batch Reporter: Alexey Kazakov Assignee: Daniel Azarov Fix For: 4.3.0.Alpha2 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19266) Batch validation problems QuickFixes

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-19266: -------------------------------------- Summary: Batch validation problems QuickFixes Key: JBIDE-19266 URL: https://issues.jboss.org/browse/JBIDE-19266 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: batch Reporter: Alexey Kazakov Assignee: Daniel Azarov Fix For: 4.3.0.Alpha2 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19162) add new plugins to openshift pom and create feature

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19162?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen reassigned JBIDE-19162: ------------------------------------------- Resolution: (was: Done) Assignee: Andre Dietisheim (was: Nick Boldt) After some basic testing and discussion we are rolling this back. Connections were not possible to create at all for neither v2 nor v3 thus nothing can really be tested. > add new plugins to openshift pom and create feature > --------------------------------------------------- > > Key: JBIDE-19162 > URL: https://issues.jboss.org/browse/JBIDE-19162 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 4.3.0.Alpha1 > > > In JBIDE-19048 we created new plugins for the OpenShift v3 tooling and moved reusable parts to common plugins. We now need to get the maven build working (add the new modules) and create a v3 feature. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19158) Batch Validation

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19158?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich updated JBIDE-19158: ------------------------------------------ Description: Validation rules for job xml 1. Attribute 'ref' should refer by name to existing type that implements batch artifact interface assumed by the parent xml element. 2. Attribute 'properties/property/@name' either refers by batch property name a field in Java type for the batch artifact, or it is used by 'properties/property/@value' through substitution \#\{jobProperties['%name%']\} . Validation will set warning markers for unused properties and error markers for substitution calling an unknown name. 3. Attributes 'step/@next', 'split/@next', 'flow/@next', 'flow/next/@to', 'step/next/@to', should refer to id of step | split | flow | decision at the same level as the current execution element. Values @id of execution elements should be unique within the same level where they can transit one to another. 4. Attributes 'flow/stop/@restart', 'step/stop/@restart' should refer to id of step | split | flow | decision at the job level. 5. Sequence of execution elements defined by @next and @to should not loop. 6. Value of attribute 'include/@class' and 'exclude/@class' is qualified name of an exception class. was: Validation rules for job xml 1. Attribute 'ref' should refer by name to existing type that implements batch artifact interface assumed by the parent xml element. 2. Attribute 'properties/property/@name' either refers by batch property name a field in Java type for the batch artifact, or it is used by 'properties/property/@value' through substitution \#\{jobProperties['%name%']\} . Validation will set warning markers for unused properties and error markers for substitution calling an unknown name. 3. Attributes 'step/@next', 'split/@next', 'flow/@next', 'flow/next/@to', 'step/next/@to', 'flow/stop/@restart', 'step/stop/@restart' should refer to id of step | split | flow | decision at the same level as the current execution element. Values @id of execution elements should be unique within the same level where they can transit one to another. 4. Sequence of execution elements defined by @next and @to should not loop. 5. Value of attribute 'include/@class' and 'exclude/@class' is qualified name of an exception class. > Batch Validation > ---------------- > > Key: JBIDE-19158 > URL: https://issues.jboss.org/browse/JBIDE-19158 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: batch > Affects Versions: 4.3.0.Alpha1 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Labels: new_and_noteworthy > Fix For: 4.3.0.Alpha2 > > > Validation rules for job xml > 1. Attribute 'ref' should refer by name to existing type that implements batch artifact interface assumed by the parent xml element. > 2. Attribute 'properties/property/@name' either refers by batch property name a field in Java type for the batch artifact, or it is used by 'properties/property/@value' through substitution \#\{jobProperties['%name%']\} . Validation will set warning markers for unused properties and error markers for substitution calling an unknown name. > 3. Attributes 'step/@next', 'split/@next', 'flow/@next', 'flow/next/@to', 'step/next/@to', should refer to id of step | split | flow | decision at the same level as the current execution element. Values @id of execution elements should be unique within the same level where they can transit one to another. > 4. Attributes 'flow/stop/@restart', 'step/stop/@restart' should refer to id of step | split | flow | decision at the job level. > 5. Sequence of execution elements defined by @next and @to should not loop. > 6. Value of attribute 'include/@class' and 'exclude/@class' is qualified name of an exception class. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19265) Not able to deploy an archive packaged as a jboss-sar

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19265?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-19265: ----------------------------------- Assignee: Fred Bricon > Not able to deploy an archive packaged as a jboss-sar > ------------------------------------------------------ > > Key: JBIDE-19265 > URL: https://issues.jboss.org/browse/JBIDE-19265 > Project: Tools (JBoss Tools) > Issue Type: Bug > Reporter: Sande Gilda > Assignee: Fred Bricon > > The `helloworld-mbean` quickstart project contains 2 subprojects: a `war` archive and a `jboss-sar` archive. You can deploy the WAR, but It is not possible to deploy the SAR. > > See https://bugzilla.redhat.com/show_bug.cgi?id=1191485 > The source is located here: https://github.com/jboss-developer/jboss-eap-quickstarts/tree/6.4.x-devel... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19265) Not able to deploy an archive packaged as a jboss-sar

by Sande Gilda (JIRA)

Sande Gilda created JBIDE-19265: ----------------------------------- Summary: Not able to deploy an archive packaged as a jboss-sar Key: JBIDE-19265 URL: https://issues.jboss.org/browse/JBIDE-19265 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Sande Gilda The `helloworld-mbean` quickstart project contains 2 subprojects: a `war` archive and a `jboss-sar` archive. You can deploy the WAR, but It is not possible to deploy the SAR. See https://bugzilla.redhat.com/show_bug.cgi?id=1191485 The source is located here: https://github.com/jboss-developer/jboss-eap-quickstarts/tree/6.4.x-devel... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19262) CordovaSim: widget disposed while skin changing

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19262?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-19262: ------------------------------------- we do not have that problem in 4.2.x > CordovaSim: widget disposed while skin changing > ----------------------------------------------- > > Key: JBIDE-19262 > URL: https://issues.jboss.org/browse/JBIDE-19262 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cordovasim > Affects Versions: 4.3.0.Alpha1 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Priority: Critical > Fix For: 4.3.0.Alpha1 > > > 1. Run CordovaSim > 2. Change device > 3. Error widget is disposed -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 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 February 2015