August 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-15158) if I create a scalable application I get a non-useful dialog about HAProxy (watcher)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15158?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBIDE-15158: ------------------------------------------------- Dan McPherson <dmcphers(a)redhat.com> changed the Status of [bug 982615|https://bugzilla.redhat.com/show_bug.cgi?id=982615] from VERIFIED to CLOSED > if I create a scalable application I get a non-useful dialog about HAProxy (watcher) > ------------------------------------------------------------------------------------ > > Key: JBIDE-15158 > URL: https://issues.jboss.org/browse/JBIDE-15158 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.1.0.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.2.x > > Attachments: ha-proxy-started.png > > > How to reproduce: > # ASSERT: make sure that you dont have any scalable application in your domain > # EXEC: launch OpenShift application wizard and provide some name, type and check *enable Scaling* > Result: > You get a dialog which informs you that the HAProxy was started: > !ha-proxy-started.png! -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-117) Update SwtichYard to 1.0.0.Final

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-117?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-117: ---------------------------------- JBTIS-4.0.2 https://github.com/jbosstools/jbosstools-integration-stack/pull/67 > Update SwtichYard to 1.0.0.Final > -------------------------------- > > Key: JBTIS-117 > URL: https://issues.jboss.org/browse/JBTIS-117 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Rob Cernich > Assignee: Rob Cernich > Fix For: 4.1.1 > > > Update JBTIS to include SwitchYard 1.0.0.Final. > This applies to both the 4.0.x and 4.1.x branches (as SwitchYard 1.0.0.Final should be compatible with both Juno and Kepler releases) -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15326) openshift-java-client: Push 2.3.0 to maven central

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-15326: ---------------------------------------- Summary: openshift-java-client: Push 2.3.0 to maven central Key: JBIDE-15326 URL: https://issues.jboss.org/browse/JBIDE-15326 Project: Tools (JBoss Tools) Issue Type: Task Components: openshift Affects Versions: 4.1.0.Final Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 4.2.0.Alpha1 In JBT 4.1.0.Final we used openshift-java-client v2.3.0. The code was branched and tagged. Now we need to push the maven artifact to maven central -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15318) Import Maven Archetype Project Example ignores JBoss Maven Integration preferences

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15318?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15318: --------------------------------------------- [~snjeza] do you know why the configurator was disabled explicitly ? > Import Maven Archetype Project Example ignores JBoss Maven Integration preferences > ---------------------------------------------------------------------------------- > > Key: JBIDE-15318 > URL: https://issues.jboss.org/browse/JBIDE-15318 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, project-examples > Affects Versions: 4.1.0.Beta2 > Reporter: Denis Golovin > Priority: Critical > Fix For: 4.1.1.Final, 4.2.0.Alpha1 > > > Creating projects out of JBoss Central doesn't enable JBoss Tools features like CDI. > This bag is regression of JBIDE-14807 where mandatory execution [Maven->Update Project...] was replaced to update only for projects with "out of date" markers. ArchetypeExamplesWizardPage.finishPage() method disable all configurators before importing projects into workspace and with fix of JBIDE-14807 it leads to new problem when configurators are never being called. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14765) Support <weld:exclude>

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14765?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich edited comment on JBIDE-14765 at 8/6/13 8:16 PM: ----------------------------------------------------------------------- I suggest supporting <exclude> as it is defined in CDI 1.1, and supporting <weld:exclude> in only what is common in these definitions. For example, exclude in CDI 1.1 does not support attribute 'pattern', sequences * and ** may only occur as the ending of attribute 'name', character '?' is not supported, etc. I think that we have to ignore enabling condition 'if-system-property' as there is no way to know system properties at application runtime. Or, we might add a preference page to CDI preferences for design-time system properties, but will it not became a dead-and-forgotten feature? was (Author: scabanovich): I suggest supporting <exclude> as it is defined in CDI 1.1, and supporting <weld:exclude> in only what is common in these definitions. For example, exclude in CDI 1.1 does not support attribute 'pattern', sequences '*' and '**' may only occur as the ending of attribute 'name', character '?' is not supported, etc. I think that we have to ignore enabling condition 'if-system-property' as there is no way to know system properties at application runtime. Or, we might add a preference page to CDI preferences for design-time system properties, but will it not became a dead-and-forgotten feature? > Support <weld:exclude> > ---------------------- > > Key: JBIDE-14765 > URL: https://issues.jboss.org/browse/JBIDE-14765 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: CDI extensions > Reporter: Alexey Kazakov > Assignee: Viacheslav Kabanovich > Fix For: 4.2.x > > > See http://docs.jboss.org/weld/reference/latest/en-US/html/configure.html -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14765) Support <weld:exclude>

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14765?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich edited comment on JBIDE-14765 at 8/6/13 8:17 PM: ----------------------------------------------------------------------- I suggest supporting <exclude> as it is defined in CDI 1.1, and supporting <weld:exclude> in only what is common in these definitions. For example, exclude in CDI 1.1 does not support attribute 'pattern', sequences * and ** may only occur as the ending of attribute 'name', character '?' is not supported, etc. I think that we have to ignore enabling condition 'if-system-property' as there is no way to know system properties at application runtime. Or, we might add a preference page to CDI preferences for design-time system properties, but will it not become a dead-and-forgotten feature? was (Author: scabanovich): I suggest supporting <exclude> as it is defined in CDI 1.1, and supporting <weld:exclude> in only what is common in these definitions. For example, exclude in CDI 1.1 does not support attribute 'pattern', sequences * and ** may only occur as the ending of attribute 'name', character '?' is not supported, etc. I think that we have to ignore enabling condition 'if-system-property' as there is no way to know system properties at application runtime. Or, we might add a preference page to CDI preferences for design-time system properties, but will it not became a dead-and-forgotten feature? > Support <weld:exclude> > ---------------------- > > Key: JBIDE-14765 > URL: https://issues.jboss.org/browse/JBIDE-14765 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: CDI extensions > Reporter: Alexey Kazakov > Assignee: Viacheslav Kabanovich > Fix For: 4.2.x > > > See http://docs.jboss.org/weld/reference/latest/en-US/html/configure.html -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14765) Support <weld:exclude>

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14765?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-14765: ----------------------------------------------- I suggest supporting <exclude> as it is defined in CDI 1.1, and supporting <weld:exclude> in only what is common in these definitions. For example, exclude in CDI 1.1 does not support attribute 'pattern', sequences '*' and '**' may only occur as the ending of attribute 'name', character '?' is not supported, etc. I think that we have to ignore enabling condition 'if-system-property' as there is no way to know system properties at application runtime. Or, we might add a preference page to CDI preferences for design-time system properties, but will it not became a dead-and-forgotten feature? > Support <weld:exclude> > ---------------------- > > Key: JBIDE-14765 > URL: https://issues.jboss.org/browse/JBIDE-14765 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: CDI extensions > Reporter: Alexey Kazakov > Assignee: Viacheslav Kabanovich > Fix For: 4.2.x > > > See http://docs.jboss.org/weld/reference/latest/en-US/html/configure.html -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14366) openshift-java-client: add method overloads that allow users to provide specific timeouts to specific operations

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14366?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-14366: ------------------------------------- Fix Version/s: 4.2.0.Alpha1 (was: 4.2.x) > openshift-java-client: add method overloads that allow users to provide specific timeouts to specific operations > ---------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-14366 > URL: https://issues.jboss.org/browse/JBIDE-14366 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.1.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.2.0.Alpha1 > > > We need to have means for users to provide specific timeouts for specific operations. Ex. to create an application we'd call > {code} > domain.createApplication(name, cartridge, scale, gear) > {code} > If we want to increase timeouts for this specific operation, we cannot. We have to increase the url connection timeouts via the system properties. We should therefore offer > {code} > domain.createApplication(name, cartridge, scale, gear, TIMEOUT) > {code} -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14366) openshift-java-client: add method overloads that allow users to provide specific timeouts to specific operations

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14366?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-14366: ------------------------------------- Fix Version/s: 4.1.1.Final > openshift-java-client: add method overloads that allow users to provide specific timeouts to specific operations > ---------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-14366 > URL: https://issues.jboss.org/browse/JBIDE-14366 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.1.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.1.Final, 4.2.0.Alpha1 > > > We need to have means for users to provide specific timeouts for specific operations. Ex. to create an application we'd call > {code} > domain.createApplication(name, cartridge, scale, gear) > {code} > If we want to increase timeouts for this specific operation, we cannot. We have to increase the url connection timeouts via the system properties. We should therefore offer > {code} > domain.createApplication(name, cartridge, scale, gear, TIMEOUT) > {code} -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14726) Cannot run Cordova project on iOS Emulator

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14726?page=com.atlassian.jira.plugi... ] Gorkem Ercan edited comment on JBIDE-14726 at 8/6/13 3:46 PM: -------------------------------------------------------------- [~sbunciak] Just released a possible fix for this on the nightly builds, can you possibly try the nightlies as I am not able to create the exact same case over here. was (Author: gercan): Just released a possible fix for this on the nightly builds, can you possibly try the nightlies as I am not able to create the exact same case over here. > Cannot run Cordova project on iOS Emulator > ------------------------------------------ > > Key: JBIDE-14726 > URL: https://issues.jboss.org/browse/JBIDE-14726 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.1.0.Beta1 > Environment: Darwin machydra.brq.redhat.com 12.3.0 Darwin Kernel Version 12.3.0: Sun Jan 6 22:37:10 PST 2013; root:xnu-2050.22.13~1/RELEASE_X86_64 x86_64 > Reporter: Stefan Bunciak > Assignee: Gorkem Ercan > Priority: Critical > Fix For: 4.1.x, 4.2.x > > Attachments: screenshot.png > > > {code} > dyld: Library not loaded: @rpath/iPhoneSimulatorRemoteClient.framework/Versions/A/iPhoneSimulatorRemoteClient > Referenced from: /Users/jbossqa/Downloads/eclipse/configuration/org.eclipse.osgi/bundles/264/data//ios-sim > Reason: image not found > {code} > The files seems to be present: > !screenshot.png|thumbnail! -- 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

12 years, 8 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 August 2013