April 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-16957) no difference between beta1 and beta1a updatesites

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16957?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-16957: ------------------------------- Attachment: diff_Beta1_B90_with_Beta1aprime_B95.png Beta1 and Beta1a are now different: !diff_Beta1_B90_with_Beta1aprime_B95.png! > no difference between beta1 and beta1a updatesites > -------------------------------------------------- > > Key: JBIDE-16957 > URL: https://issues.jboss.org/browse/JBIDE-16957 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: updatesite > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.2.0.Beta1 > > Attachments: diff_Beta1_B90_with_Beta1aprime_B95.png > > > something is funky here. > eclipse doesn't give me any updates for this new beta1a site. > Thus I tried running p2diff and browse via p2browser. The binary content except the category are identical. > See difference at https://gist.github.com/maxandersen/352153881b657fbe2ecb > none of the plugins like open shift or server has changed. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16957) no difference between beta1 and beta1a updatesites

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16957?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-16957. ------------------------------ Resolution: Done Creation of better tests & automated tooling will be handled in JBIDE-16970 and JBIDE-16971. Closing. > no difference between beta1 and beta1a updatesites > -------------------------------------------------- > > Key: JBIDE-16957 > URL: https://issues.jboss.org/browse/JBIDE-16957 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: updatesite > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.2.0.Beta1 > > Attachments: diff_Beta1_B90_with_Beta1aprime_B95.png > > > something is funky here. > eclipse doesn't give me any updates for this new beta1a site. > Thus I tried running p2diff and browse via p2browser. The binary content except the category are identical. > See difference at https://gist.github.com/maxandersen/352153881b657fbe2ecb > none of the plugins like open shift or server has changed. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16960) with GPE feature removed from JBT 4.40.0.Beta2-SNAPSHOT targetplatform, JBT agg site won't build

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16960?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-16960. ------------------------------ > with GPE feature removed from JBT 4.40.0.Beta2-SNAPSHOT targetplatform, JBT agg site won't build > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-16960 > URL: https://issues.jboss.org/browse/JBIDE-16960 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.2.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.2.0.Beta2 > > > I removed the deprecated GPE feature [1] because it can't be installed onto Luna (JBIDE-16910). > [1] https://github.com/jbosstools/jbosstools-target-platforms/pull/48/files#d... > So now we get this: > {code:title=http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sites.aggregate.site_master/8748/console} > [ERROR] Cannot resolve project dependencies: > [ERROR] Software being installed: org.jboss.tools.site.core raw:4.2.0.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):4.2.0-SNAPSHOT > [ERROR] Missing requirement: org.jboss.tools.gwt.core 1.1.0.Final-v20130205-2223-B78 requires 'bundle com.google.gdt.eclipse.suite 3.0.1' but it could not be found > [ERROR] Cannot satisfy dependency: org.jboss.tools.gwt.feature.feature.group 1.1.0.Final-v20130205-2223-B78 depends on: org.jboss.tools.gwt.core [1.1.0.Final-v20130205-2223-B78] > [ERROR] Cannot satisfy dependency: org.jboss.tools.site.core raw:4.2.0.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):4.2.0-SNAPSHOT depends on: org.jboss.tools.gwt.feature.feature.group 0.0.0 > [ERROR] > [ERROR] Internal error: java.lang.RuntimeException: No solution found because the problem is unsatisfiable.: [Unable to satisfy dependency from org.jboss.tools.gwt.core 1.1.0.Final-v20130205-2223-B78 to bundle com.google.gwt.eclipse.core 0.0.0.; Unable to satisfy dependency from org.jboss.tools.gwt.core 1.1.0.Final-v20130205-2223-B78 to bundle com.google.gdt.eclipse.suite 3.0.1.; Unable to satisfy dependency from org.jboss.tools.maven.gwt 1.6.0.Beta2-v20140321-0445-B465 to bundle com.google.gwt.eclipse.core 2.5.0.; Unable to satisfy dependency from org.jboss.tools.maven.gwt 1.6.0.Beta2-v20140321-0445-B465 to bundle com.google.gwt.eclipse.oophm 3.0.0.; No solution found because the problem is unsatisfiable.] -> [Help 1]{code} > At the moment, only com.google.gwt.eclipse.sdkbundle_2.5.1 is present in the Beta2-SNAPSHOT target platform [2]. In the previous TP [3], we had more: > {code:title=http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.40.0.Beta1/REPO/plugins/} > com.google.appengine.* > com.google.gdt.eclipse.* > com.google.gwt.eclipse.core_3.4.2.v201310081834-rel-r43.jar > com.google.gwt.eclipse.oophm_3.4.2.v201310081834-rel-r43.jar > com.google.gwt.eclipse.sdkbundle_2.5.1.jar > {code} > [2] http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4... > [3] http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4... > ---- > *QUESTIONS*: > Does the *org.jboss.tools.gwt.feature* need to remain in the JBT update site? > Or... should I add the com.google.gwt.eclipse.core plugin back into the JBoss Tools 4.40.0.Beta2-SNAPSHOT target platform [2]? -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16967) Failure to replace Variables on Config xml files for Cordova plug-ins

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16967?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-16967 at 4/1/14 10:49 PM: ------------------------------------------------------------- Resolving. Committed in Beta1x branch and picked up in this build: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBo... Also included here: http://download.jboss.org/jbosstools/builds/development/4.2.0.Beta1a.core... and http://www.qa.jboss.com/binaries/RHDS/updates/development/8.0.0.Beta1a.core/ was (Author: nickboldt): Resolving. Committed in Beta1x branch and picked up in this build: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBo... Also included here: http://download.jboss.org/jbosstools/builds/development/4.2.0.Beta1a.core... > Failure to replace Variables on Config xml files for Cordova plug-ins > --------------------------------------------------------------------- > > Key: JBIDE-16967 > URL: https://issues.jboss.org/browse/JBIDE-16967 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.2.0.Beta1 > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Priority: Critical > Labels: respin-a > Fix For: 4.2.0.Beta1 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > HMT fails to replace the variable values on config.xml fails when installing cordova plugins. For example if a variable such as $PACKAGE_NAME needs to be replaced on AndroidManifest.xml it is skipped and not replaced. On android this causes apk not installed error on most occasions. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16974) 'Syntax error on token "continue", Identifier expected' when Adding Cordova Contacts plugin

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16974?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-16974: -------------------------------------- I do not think I can do anything for this on HMT. I could remove plugin folders from the javascript sourcepath but that will also remove any chance of codeassist for plugins [~maxandersen] do you want someone to look from JS validation perspective? > 'Syntax error on token "continue", Identifier expected' when Adding Cordova Contacts plugin > ------------------------------------------------------------------------------------------- > > Key: JBIDE-16974 > URL: https://issues.jboss.org/browse/JBIDE-16974 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Reporter: Burr Sutter > > Adding the org.apache.cordova.contacts plugin gives me the following error in JBDS8 (about Beta 1) > http://screencast.com/t/XH8Q6HbL -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16974) 'Syntax error on token "continue", Identifier expected' when Adding Cordova Contacts plugin

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16974?page=com.atlassian.jira.plugi... ] Burr Sutter commented on JBIDE-16974: ------------------------------------- No runtime error - the project deployed fine to both iOS and Android > 'Syntax error on token "continue", Identifier expected' when Adding Cordova Contacts plugin > ------------------------------------------------------------------------------------------- > > Key: JBIDE-16974 > URL: https://issues.jboss.org/browse/JBIDE-16974 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Reporter: Burr Sutter > > Adding the org.apache.cordova.contacts plugin gives me the following error in JBDS8 (about Beta 1) > http://screencast.com/t/XH8Q6HbL -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16967) Failure to replace Variables on Config xml files for Cordova plug-ins

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16967?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-16967. -------------------------------- Resolution: Done Resolving. Committed in Beta1x branch and picked up in this build: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBo... Also included here: http://download.jboss.org/jbosstools/builds/development/4.2.0.Beta1a.core... > Failure to replace Variables on Config xml files for Cordova plug-ins > --------------------------------------------------------------------- > > Key: JBIDE-16967 > URL: https://issues.jboss.org/browse/JBIDE-16967 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.2.0.Beta1 > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Priority: Critical > Labels: respin-a > Fix For: 4.2.0.Beta1 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > HMT fails to replace the variable values on config.xml fails when installing cordova plugins. For example if a variable such as $PACKAGE_NAME needs to be replaced on AndroidManifest.xml it is skipped and not replaced. On android this causes apk not installed error on most occasions. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16967) Failure to replace Variables on Config xml files for Cordova plug-ins

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16967?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-16967: ------------------------------- Labels: respin-a (was: respin-b) > Failure to replace Variables on Config xml files for Cordova plug-ins > --------------------------------------------------------------------- > > Key: JBIDE-16967 > URL: https://issues.jboss.org/browse/JBIDE-16967 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.2.0.Beta1 > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Priority: Critical > Labels: respin-a > Fix For: 4.2.0.Beta1 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > HMT fails to replace the variable values on config.xml fails when installing cordova plugins. For example if a variable such as $PACKAGE_NAME needs to be replaced on AndroidManifest.xml it is skipped and not replaced. On android this causes apk not installed error on most occasions. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-483) Add info on LiveReload refresh delay option

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-483?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-483: ------------------------------------- Assignee: Suz Dorfield (was: Michelle Murray) > Add info on LiveReload refresh delay option > ------------------------------------------- > > Key: TOOLSDOC-483 > URL: https://issues.jboss.org/browse/TOOLSDOC-483 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: User Guide - LiveReload Tools > Affects Versions: 4.2.0.Beta1 > Reporter: Michelle Murray > Assignee: Suz Dorfield > Fix For: 4.2.0.Beta1 > > Original Estimate: 45 minutes > Time Spent: 30 minutes > Remaining Estimate: 15 minutes > > Use Case: It was reported that in some cases the server would return an error because of resources or libraries still being reloaded when the requests arrived. Some application servers need additional time to take the changes fully into account before the browsers send their request. > Feature: The LiveReload Server Configuration Editor now provides users with a "Reload Delay" option to set the number of seconds to wait before "reload" messages are sent to the browsers. In the Server Editor under LiveReload Server Configuration, in the Reload delay field modify the length of time in seconds the IDE should wait before sending the LiveReload request to browsers. By default, the reload delay is set to 0. Once the configuration is saved, there is no need to restart the LiveReload server to take the new value into account. The delay appears as a job running in the Progress View and it can be cancelled if is the wait period was set too high (in which case the "reload" messages will be sent to the browsers without further waiting). > Writer task: Edit topic 22835. Modify the topic text to include the new option. Create a new screen cap for the figure 'LiveReload Server Options in the Server Editor'. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-483) Add info on LiveReload refresh delay option

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-483?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-483: ------------------------------------------ [~sdorfiel], i have updated the text. Please complete the changes for the new screencap. > Add info on LiveReload refresh delay option > ------------------------------------------- > > Key: TOOLSDOC-483 > URL: https://issues.jboss.org/browse/TOOLSDOC-483 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: User Guide - LiveReload Tools > Affects Versions: 4.2.0.Beta1 > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.2.0.Beta1 > > Original Estimate: 45 minutes > Time Spent: 30 minutes > Remaining Estimate: 15 minutes > > Use Case: It was reported that in some cases the server would return an error because of resources or libraries still being reloaded when the requests arrived. Some application servers need additional time to take the changes fully into account before the browsers send their request. > Feature: The LiveReload Server Configuration Editor now provides users with a "Reload Delay" option to set the number of seconds to wait before "reload" messages are sent to the browsers. In the Server Editor under LiveReload Server Configuration, in the Reload delay field modify the length of time in seconds the IDE should wait before sending the LiveReload request to browsers. By default, the reload delay is set to 0. Once the configuration is saved, there is no need to restart the LiveReload server to take the new value into account. The delay appears as a job running in the Progress View and it can be cancelled if is the wait period was set too high (in which case the "reload" messages will be sent to the browsers without further waiting). > Writer task: Edit topic 22835. Modify the topic text to include the new option. Create a new screen cap for the figure 'LiveReload Server Options in the Server Editor'. -- 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, 2 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 April 2014