[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
[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
[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
[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