[JBoss JIRA] (JBIDE-15880) openshift-java-client: provide its own lib specific timeout that may be set via system properties
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15880?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-15880:
------------------------------------------
and deployed library to repository.jboss.org
> openshift-java-client: provide its own lib specific timeout that may be set via system properties
> -------------------------------------------------------------------------------------------------
>
> Key: JBIDE-15880
> URL: https://issues.jboss.org/browse/JBIDE-15880
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.1.1.Beta1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.1.CR1
>
>
> client timeouts when talking to OpenShift are unfortunaltey still a topic and cause errors (JBIDE-15835, JBIDE-15831) when OpenShift is installed on systems with poor performance. We should thus provide a client-lib specific default timeout that a user may override by setting it in the system properties.
> The timeout-setting order would thus then be:
> 1) specific operation timeout (ex. JBT is currently using a specific creation timeout)
> 2) client-lib default timeout (which may be set by a system property)
> 3) HttpUrlConnection default timeout (jdk timeout: -Dsun.net.client.defaultConnectTimeout=600000)
--
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, 5 months
[JBoss JIRA] (JBIDE-15895) Cordova API not working when added widget from jQuery Mobile palette
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15895?page=com.atlassian.jira.plugi... ]
Gorkem Ercan commented on JBIDE-15895:
--------------------------------------
hybrid tools is not involved here especially when testing with CordovaSim. My wild guess is, this is actually broken on the upstream (either Cordova or jqm) but we need to confirm.
> Cordova API not working when added widget from jQuery Mobile palette
> --------------------------------------------------------------------
>
> Key: JBIDE-15895
> URL: https://issues.jboss.org/browse/JBIDE-15895
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid, browsersim
> Affects Versions: 4.1.1.Beta1
> Environment: JBDS7.1.0.Beta1b Beta1-v20131102-1529-B493
> Reporter: Vlado Pakan
> Fix For: 4.1.1.CR1
>
>
> 1. Create Mobile Hybrid Project
> 2. Add Accelerometer testing page as described on phonegap wep page
> 3. Run Project on CordovaSim and/or Emulator and/or Android device
> 4. Open Acceleromer page
> ASSERT: App is displaying data from Accelerometer
> 5. Open index.html page add some widget from jQuery Mobile pallete and save
> 6. Repeat step 3. and 4.
> ERROR: App is not displaying data from Accelerometer. Event DeviceReady is not fired
> When adding widget from jQuery Mobile pallete also this reference to jQuery Mobile java script file is added
> {noformat}
> <script src="http://code.jquery.com/mobile/1.3.1/jquery.mobile-1.3.1.min.js"></script>
> {noformat}
> and it seems is somehow breaking Cordova API functionality. Once removed from index.html application is displaying data from Acceleromer again
--
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, 5 months
[JBoss JIRA] (JBDS-2801) Investigate use of GWT/GPE 3.4 in JBT/JBDS Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2801?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-2801:
----------------------------------
Further testing:
{code}
(2013-11-07 13:20:53) fbricon: I can't upgrade from gep 3.2 e42 to 3.4 e43
(2013-11-07 13:24:23) nboldt: how about 3.2 e42 -> 3.4 e42 (not e43) ?
(2013-11-07 13:25:11) fbricon: nboldt: p2 accepts
(2013-11-07 13:31:22) fbricon: nboldt: so I guess we should stick to e42 for jbds 7.1.x, move to e43(e44?) for jbds 8.0. Anyone willing to upgrade from 7.1.x+gpe-e42 to 8.x+gpe-e43/44 will see the remediation screen asking to remove gpe. THEN reinstalling e43/44 should work
(2013-11-07 13:34:59) nboldt: can't we remediate from e42 to e43 in 7.0 -> 7.1?
(2013-11-07 13:39:54) fbricon: nboldt: yes we can remediate in 7.1 too. Someone needs to make that decision
{code}
[~ldimaggio], [~maxandersen], [~burrsutter], WDYT?
> Investigate use of GWT/GPE 3.4 in JBT/JBDS Central
> --------------------------------------------------
>
> Key: JBDS-2801
> URL: https://issues.jboss.org/browse/JBDS-2801
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification, 3rd-party-dependencies, central
> Reporter: Nick Boldt
> Assignee: Fred Bricon
> Fix For: 7.1.0.CR1
>
>
> New 3.4.2 mirrors:
> http://download.jboss.org/jbosstools/updates/requirements/gwt/3.4.2.v2013...
> http://download.jboss.org/jbosstools/updates/requirements/gwt/3.4.2.v2013...
> Note that at least one IU had been renamed:
> OLD:
> * com.google.gdt.eclipse.suite.e42.feature_3.4.2.v201310081840-rel-r42.jar
> * com.google.gdt.eclipse.platform.e42_3.4.2.v201310081840-rel-r42.jar
> NEW:
> * com.google.gdt.eclipse.suite.e43.feature_3.4.2.v201310081834-rel-r43.jar (now e43)
> * com.google.gdt.eclipse.platform.e42_3.4.2.v201310081834-rel-r43.jar (still e42)
> If we decide to move to e43, we will have to rebuild jbosstools-central due to this requirement:
> {code:title=https://github.com/jbosstools/jbosstools-central/blob/jbosstools-4.1.x/maven/features/org.jboss.tools.maven.gwt.feature/feature.xml#L24}
> <import feature="com.google.gdt.eclipse.suite.e42.feature" version="3.0.1" match="greaterOrEqual"/>
> {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, 5 months
[JBoss JIRA] (JBIDE-15895) Cordova API not working when added widget from jQuery Mobile palette
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15895?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-15895:
----------------------------------------
I don't see any problems in HTML Editor/Palette here. So I removed visual-page-editor-core component.
[~gercan], what is the problem with jquery.mobile-1.3.1.min.js? Is it not related to aerogear-hybrid tools?
> Cordova API not working when added widget from jQuery Mobile palette
> --------------------------------------------------------------------
>
> Key: JBIDE-15895
> URL: https://issues.jboss.org/browse/JBIDE-15895
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid, browsersim
> Affects Versions: 4.1.1.Beta1
> Environment: JBDS7.1.0.Beta1b Beta1-v20131102-1529-B493
> Reporter: Vlado Pakan
> Fix For: 4.1.1.CR1
>
>
> 1. Create Mobile Hybrid Project
> 2. Add Accelerometer testing page as described on phonegap wep page
> 3. Run Project on CordovaSim and/or Emulator and/or Android device
> 4. Open Acceleromer page
> ASSERT: App is displaying data from Accelerometer
> 5. Open index.html page add some widget from jQuery Mobile pallete and save
> 6. Repeat step 3. and 4.
> ERROR: App is not displaying data from Accelerometer. Event DeviceReady is not fired
> When adding widget from jQuery Mobile pallete also this reference to jQuery Mobile java script file is added
> {noformat}
> <script src="http://code.jquery.com/mobile/1.3.1/jquery.mobile-1.3.1.min.js"></script>
> {noformat}
> and it seems is somehow breaking Cordova API functionality. Once removed from index.html application is displaying data from Acceleromer again
--
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, 5 months
[JBoss JIRA] (JBIDE-15889) Typo in project explorer context menu : plugin > plug-in
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15889?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-15889:
--------------------------------------
Assignee: Daniel Azarov (was: Alexey Kazakov)
> Typo in project explorer context menu : plugin > plug-in
> --------------------------------------------------------
>
> Key: JBIDE-15889
> URL: https://issues.jboss.org/browse/JBIDE-15889
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.Beta1
> Reporter: Michelle Murray
> Assignee: Daniel Azarov
> Fix For: 4.1.1.CR1
>
>
> When right-click the plugin folder of a hybrid mobile project in project explorer tab there is the 'Install Cordova Plugin' menu option.
> Similarly when right-click a plug-in in project explorer tab there is the 'Remove Cordova Plugin' menu option.
> As per JBIDE-15748, 'Plugin' should be spelled *Plug-in*.
--
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, 5 months
[JBoss JIRA] (JBTIS-113) Improve ability to configure dependent hudson jobs and provide accessable documentation
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-113?page=com.atlassian.jira.plugin.... ]
Paul Leacu resolved JBTIS-113.
------------------------------
Resolution: Out of Date
Consider - the Integration Stack is designed to use a fixed target platform and a fixed JBT core. Components like Teiid can add to the "collective" and update the target dependencies if need be. The component leads are then free to bump the JBTIS version. The IS build establishes compatibility at a package level. There's really no need for a "nightly" of the IS. The Jenkins jobs are clear and allow for some variability (other variables like target dependency must be done in the JBTIS target platform).
See https://docspace.corp.redhat.com/docs/DOC-147850
> Improve ability to configure dependent hudson jobs and provide accessable documentation
> ---------------------------------------------------------------------------------------
>
> Key: JBTIS-113
> URL: https://issues.jboss.org/browse/JBTIS-113
> Project: JBoss Tools Integration Stack
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Reporter: Barry LaFond
> Assignee: Paul Leacu
>
> SOA decoupling has elevated the need to have more configurable control over upstream and downstream dependencies.
> Notes from Nick:
> * a number of jobs are now set to build only when triggered by upstream, but SOA stuff is not as well handled
> * ideally you'd want: a) check svn every N hours (usually 6) and b) upstream should use Parameterized Trigger to cause downstream to fire
> * you can also ensure that you're building against a stable aggregate using an override like the one I've set up for SOA Tooling aggregate...
> * in your maven invocation, under Properties, you can do this: # use latest upstream nightly Core update site instead of "wild components" in the composite staging site jbosstools-nightly-staging-composite=http://download.jboss.org/jbosstools...
> * that way you pull from the aggregate (updates weekly) instead of the composite (updates every time a component respins)
> * means if you depended on something like tests/common/jst/vpe/jsf/seam/maven/central/usage stack, you wouldn't need to worry about getting incompatible pieces
--
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, 5 months
[JBoss JIRA] (JBDS-2801) Investigate use of GWT/GPE 3.4 in JBT/JBDS Central
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-2801?page=com.atlassian.jira.plugin.... ]
Fred Bricon edited comment on JBDS-2801 at 11/7/13 1:24 PM:
------------------------------------------------------------
After removing the e42 feature requirement, I installed the maven.gwt plugin on JBDS 7.0.1.
Then I installed the GWT connector 3.2 (e42)
Then tried installing 3.4 (e43) from http://download.jboss.org/jbosstools/updates/requirements/gwt/3.4.2.v2013...
got :
{noformat}
Cannot complete the install because of a conflicting dependency.
Software being installed: Google Plugin for Eclipse 4.3 3.4.2.v201310081834-rel-r43 (com.google.gdt.eclipse.suite.e43.feature.feature.group 3.4.2.v201310081834-rel-r43)
Software currently installed: Google Plugin for Eclipse 4.2 3.2.3.v201304260926-rel-r42 (com.google.gdt.eclipse.suite.e42.feature.feature.group 3.2.3.v201304260926-rel-r42)
Only one of the following can be installed at once:
Google Suite Plugin 3.4.2.v201310081834-rel-r43 (com.google.gdt.eclipse.suite.ext 3.4.2.v201310081834-rel-r43)
Google Suite Plugin 3.2.3.v201304260926-rel-r42 (com.google.gdt.eclipse.suite.ext 3.2.3.v201304260926-rel-r42)
Cannot satisfy dependency:
From: Google Plugin for Eclipse 4.2 3.2.3.v201304260926-rel-r42 (com.google.gdt.eclipse.suite.e42.feature.feature.group 3.2.3.v201304260926-rel-r42)
To: com.google.gdt.eclipse.suite.ext [3.2.3.v201304260926-rel-r42]
Cannot satisfy dependency:
From: Google Plugin for Eclipse 4.3 3.4.2.v201310081834-rel-r43 (com.google.gdt.eclipse.suite.e43.feature.feature.group 3.4.2.v201310081834-rel-r43)
To: com.google.gdt.eclipse.suite.ext [3.4.2.v201310081834-rel-r43]
{noformat}
was (Author: fbricon):
After removing the e42 feature requirement, I installed the maven.gwt plugin on JBDS 7.0.1.
Then I installed the GWT connector 3.2 (e42)
Then tried installing from http://download.jboss.org/jbosstools/updates/requirements/gwt/3.4.2.v2013...
got :
{noformat}
Cannot complete the install because of a conflicting dependency.
Software being installed: Google Plugin for Eclipse 4.3 3.4.2.v201310081834-rel-r43 (com.google.gdt.eclipse.suite.e43.feature.feature.group 3.4.2.v201310081834-rel-r43)
Software currently installed: Google Plugin for Eclipse 4.2 3.2.3.v201304260926-rel-r42 (com.google.gdt.eclipse.suite.e42.feature.feature.group 3.2.3.v201304260926-rel-r42)
Only one of the following can be installed at once:
Google Suite Plugin 3.4.2.v201310081834-rel-r43 (com.google.gdt.eclipse.suite.ext 3.4.2.v201310081834-rel-r43)
Google Suite Plugin 3.2.3.v201304260926-rel-r42 (com.google.gdt.eclipse.suite.ext 3.2.3.v201304260926-rel-r42)
Cannot satisfy dependency:
From: Google Plugin for Eclipse 4.2 3.2.3.v201304260926-rel-r42 (com.google.gdt.eclipse.suite.e42.feature.feature.group 3.2.3.v201304260926-rel-r42)
To: com.google.gdt.eclipse.suite.ext [3.2.3.v201304260926-rel-r42]
Cannot satisfy dependency:
From: Google Plugin for Eclipse 4.3 3.4.2.v201310081834-rel-r43 (com.google.gdt.eclipse.suite.e43.feature.feature.group 3.4.2.v201310081834-rel-r43)
To: com.google.gdt.eclipse.suite.ext [3.4.2.v201310081834-rel-r43]
{noformat}
> Investigate use of GWT/GPE 3.4 in JBT/JBDS Central
> --------------------------------------------------
>
> Key: JBDS-2801
> URL: https://issues.jboss.org/browse/JBDS-2801
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification, 3rd-party-dependencies, central
> Reporter: Nick Boldt
> Assignee: Fred Bricon
> Fix For: 7.1.0.CR1
>
>
> New 3.4.2 mirrors:
> http://download.jboss.org/jbosstools/updates/requirements/gwt/3.4.2.v2013...
> http://download.jboss.org/jbosstools/updates/requirements/gwt/3.4.2.v2013...
> Note that at least one IU had been renamed:
> OLD:
> * com.google.gdt.eclipse.suite.e42.feature_3.4.2.v201310081840-rel-r42.jar
> * com.google.gdt.eclipse.platform.e42_3.4.2.v201310081840-rel-r42.jar
> NEW:
> * com.google.gdt.eclipse.suite.e43.feature_3.4.2.v201310081834-rel-r43.jar (now e43)
> * com.google.gdt.eclipse.platform.e42_3.4.2.v201310081834-rel-r43.jar (still e42)
> If we decide to move to e43, we will have to rebuild jbosstools-central due to this requirement:
> {code:title=https://github.com/jbosstools/jbosstools-central/blob/jbosstools-4.1.x/maven/features/org.jboss.tools.maven.gwt.feature/feature.xml#L24}
> <import feature="com.google.gdt.eclipse.suite.e42.feature" version="3.0.1" match="greaterOrEqual"/>
> {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, 5 months
[JBoss JIRA] (JBDS-2801) Investigate use of GWT/GPE 3.4 in JBT/JBDS Central
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-2801?page=com.atlassian.jira.plugin.... ]
Fred Bricon commented on JBDS-2801:
-----------------------------------
After removing the e42 feature requirement, I installed the maven.gwt plugin on JBDS 7.0.1.
Then I installed the GWT connector 3.2 (e42)
Then tried installing from http://download.jboss.org/jbosstools/updates/requirements/gwt/3.4.2.v2013...
got :
{noformat}
Cannot complete the install because of a conflicting dependency.
Software being installed: Google Plugin for Eclipse 4.3 3.4.2.v201310081834-rel-r43 (com.google.gdt.eclipse.suite.e43.feature.feature.group 3.4.2.v201310081834-rel-r43)
Software currently installed: Google Plugin for Eclipse 4.2 3.2.3.v201304260926-rel-r42 (com.google.gdt.eclipse.suite.e42.feature.feature.group 3.2.3.v201304260926-rel-r42)
Only one of the following can be installed at once:
Google Suite Plugin 3.4.2.v201310081834-rel-r43 (com.google.gdt.eclipse.suite.ext 3.4.2.v201310081834-rel-r43)
Google Suite Plugin 3.2.3.v201304260926-rel-r42 (com.google.gdt.eclipse.suite.ext 3.2.3.v201304260926-rel-r42)
Cannot satisfy dependency:
From: Google Plugin for Eclipse 4.2 3.2.3.v201304260926-rel-r42 (com.google.gdt.eclipse.suite.e42.feature.feature.group 3.2.3.v201304260926-rel-r42)
To: com.google.gdt.eclipse.suite.ext [3.2.3.v201304260926-rel-r42]
Cannot satisfy dependency:
From: Google Plugin for Eclipse 4.3 3.4.2.v201310081834-rel-r43 (com.google.gdt.eclipse.suite.e43.feature.feature.group 3.4.2.v201310081834-rel-r43)
To: com.google.gdt.eclipse.suite.ext [3.4.2.v201310081834-rel-r43]
{noformat}
> Investigate use of GWT/GPE 3.4 in JBT/JBDS Central
> --------------------------------------------------
>
> Key: JBDS-2801
> URL: https://issues.jboss.org/browse/JBDS-2801
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification, 3rd-party-dependencies, central
> Reporter: Nick Boldt
> Assignee: Fred Bricon
> Fix For: 7.1.0.CR1
>
>
> New 3.4.2 mirrors:
> http://download.jboss.org/jbosstools/updates/requirements/gwt/3.4.2.v2013...
> http://download.jboss.org/jbosstools/updates/requirements/gwt/3.4.2.v2013...
> Note that at least one IU had been renamed:
> OLD:
> * com.google.gdt.eclipse.suite.e42.feature_3.4.2.v201310081840-rel-r42.jar
> * com.google.gdt.eclipse.platform.e42_3.4.2.v201310081840-rel-r42.jar
> NEW:
> * com.google.gdt.eclipse.suite.e43.feature_3.4.2.v201310081834-rel-r43.jar (now e43)
> * com.google.gdt.eclipse.platform.e42_3.4.2.v201310081834-rel-r43.jar (still e42)
> If we decide to move to e43, we will have to rebuild jbosstools-central due to this requirement:
> {code:title=https://github.com/jbosstools/jbosstools-central/blob/jbosstools-4.1.x/maven/features/org.jboss.tools.maven.gwt.feature/feature.xml#L24}
> <import feature="com.google.gdt.eclipse.suite.e42.feature" version="3.0.1" match="greaterOrEqual"/>
> {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, 5 months