[JBoss JIRA] (JBIDE-18341) angularjs not getting activated
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18341?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-18341:
----------------------------------------
OK. Let's move to 4.2.1 and see what we can improve in this area for the next version.
> angularjs not getting activated
> -------------------------------
>
> Key: JBIDE-18341
> URL: https://issues.jboss.org/browse/JBIDE-18341
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.2.0.CR1
> Reporter: Max Rydahl Andersen
> Assignee: Alexey Kazakov
> Priority: Blocker
> Fix For: 4.2.1.Final
>
>
> [~burrsutter] and [~sebastienblanc] reports angularjs is not getting activated in latest build.
> need to test since if not that seems like a blocker.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18239) Create new update site zip(s) (rather than target platform zip) for JBT content needed for Central/EA site
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18239?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-18239:
-------------------------------
Attachment: JBIDE18239-proposed.png
Re-read Max's comments above and now I'm even more confused what he wants:
{quote}
1. TP containing only 3rd party pieces that do not move often
2. Update site containing what is in #1
{quote}
We already have an update site containing what is in the Central TP. Every TP is built as an update site. In this case, the latest is here:
http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/4.4...
{quote}
i'm suggesting the creation of the update site(s) could be done so we do not need to list the exact versions of JBoss Tools provided content.
{quote}
So in other words you want a TP we can validate which includes 0.0.0, as Mickael suggested. Can't recall if Tycho supports validation of TPs with 0.0.0 in them. Pretty sure the validator chokes on that, or we would have that in place for JBTIS.
Or you want a Central TP site + a second update site built from category.xml (which includes NO versions at all, not even 0.0.0), and that these two be composited together. This IMHO is the best solution as it fully compartmentalizes the stuff in JBDS Central which comes from JBT.
Alternatively, we could have a JBT Central .target and a JBDS Central .target, but that's even more on-disk footprint and more .target files to maintain and publish to Nexus.
{quote}i'm suggesting we make it part of the jbds site.{quote}
That's a completely different suggestion -- if I read you correctly (and I'm probably not) then you're NOW asking that the JBT content currently in Central TP which is NOT part of JBDS be added to the JBDS update site so that it's available to Central, and removed from the Central TP. Sure, we can do that ... but it will mean the JBT content that SHOULD be located in the Central update site zip (for offline users) will instead be part of the JBDS update site zip.
Won't that cause confusion / imply a different level of support than GSS intends?
----
Long story short (TL;DR): I think we need a new category.xml for the stuff that's NOT in JBDS. Here's a visual representation of this new site:
!JBIDE18239-proposed.png!
> Create new update site zip(s) (rather than target platform zip) for JBT content needed for Central/EA site
> ----------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18239
> URL: https://issues.jboss.org/browse/JBIDE-18239
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, central, discovery, updatesite
> Affects Versions: 4.2.0.CR1
> Reporter: Nick Boldt
> Labels: f2f2014
> Fix For: 4.3.0.Alpha1
>
> Attachments: JBIDE18239-proposed.png
>
>
> In order to simplify the process for getting JBT features into Central (for JBDS) and EA (for both JBT/JBDS), it's been suggested (by [~maxandersen], who doesn't like opening JIRAs :D) that instead of a target platform which needs to be updated every time we spin or respin a build, we could instead just produce an update site containing the handful of IUs (cordovasim, arquillian, etc.).
> We could further extend this idea to include all the things that currently are in BOTH JBT or JBDS and in Central, such as TestNG.
> These would be produced as new zips using the JBT aggregate builder:
> https://github.com/jbosstools/jbosstools-build-sites/tree/master/aggregate/
> Need to decide what to call this... "Extras" "JBT-not-in-JBDS" "Shared" ...?
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18419) CordovaSim can't handle cordova-3.6.3
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18419?page=com.atlassian.jira.plugi... ]
Ilya Buziuk updated JBIDE-18419:
--------------------------------
Description:
No errors when running against *cordova-3.5.0*. However with *cordova-3.6.3* getting the error with the following stack trace:
{code}
2014-09-23 13:40:23.731:INFO:oejs.Server:jetty-8.1.14.v20131031
2014-09-23 13:40:23.781:INFO:oejs.AbstractConnector:Started SelectChannelConnector@0.0.0.0:54262
!JavaScript ERROR: TypeError: 'undefined' is not a function (evaluating 'exec.init()') on line 1483 for http://localhost:54243/cordova.js
!JavaScript LOG: deviceready has not fired after 5 seconds.
!JavaScript LOG: Channel not fired: onNativeReady
!JavaScript LOG: Channel not fired: onPluginsReady
!JavaScript LOG: Channel not fired: onCordovaReady
{code}
the upstream issue for apache ripple - https://issues.apache.org/jira/browse/RIPPLE-69
was:
No errors when running against *cordova-3.5.0*. However with *cordova-3.6.3* getting the error with the following stack trace:
{code}
2014-09-23 13:40:23.731:INFO:oejs.Server:jetty-8.1.14.v20131031
2014-09-23 13:40:23.781:INFO:oejs.AbstractConnector:Started SelectChannelConnector@0.0.0.0:54262
!JavaScript ERROR: TypeError: 'undefined' is not a function (evaluating 'exec.init()') on line 1483 for http://localhost:54243/cordova.js
!JavaScript LOG: deviceready has not fired after 5 seconds.
!JavaScript LOG: Channel not fired: onNativeReady
!JavaScript LOG: Channel not fired: onPluginsReady
!JavaScript LOG: Channel not fired: onCordovaReady
{code}
> CordovaSim can't handle cordova-3.6.3
> -------------------------------------
>
> Key: JBIDE-18419
> URL: https://issues.jboss.org/browse/JBIDE-18419
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 4.2.0.CR1
> Reporter: Ilya Buziuk
> Assignee: Ilya Buziuk
> Priority: Blocker
> Fix For: 4.2.0.CR2
>
>
> No errors when running against *cordova-3.5.0*. However with *cordova-3.6.3* getting the error with the following stack trace:
> {code}
> 2014-09-23 13:40:23.731:INFO:oejs.Server:jetty-8.1.14.v20131031
> 2014-09-23 13:40:23.781:INFO:oejs.AbstractConnector:Started SelectChannelConnector@0.0.0.0:54262
> !JavaScript ERROR: TypeError: 'undefined' is not a function (evaluating 'exec.init()') on line 1483 for http://localhost:54243/cordova.js
> !JavaScript LOG: deviceready has not fired after 5 seconds.
> !JavaScript LOG: Channel not fired: onNativeReady
> !JavaScript LOG: Channel not fired: onPluginsReady
> !JavaScript LOG: Channel not fired: onCordovaReady
> {code}
> the upstream issue for apache ripple - https://issues.apache.org/jira/browse/RIPPLE-69
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBDS-3159) Usage dialog is not displayed for user after initial install
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3159?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov commented on JBDS-3159:
--------------------------------------
{quote}i think the PR makes sense to put in anyways{quote}
In master only or 4.2.x too?
> Usage dialog is not displayed for user after initial install
> ------------------------------------------------------------
>
> Key: JBDS-3159
> URL: https://issues.jboss.org/browse/JBDS-3159
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: usage
> Affects Versions: 8.0.0.CR1
> Reporter: Len DiMaggio
> Assignee: Alexey Kazakov
> Priority: Blocker
> Fix For: 8.0.0.CR2
>
>
> I'm seeing this after an install - and after opening a new workspace - no usage dialog and:
> grep -r usage_reporting_enabled *
> studio/configuration/org.eclipse.osgi/5/0/.cp/plugin_customization.ini:org.tigris.subversion.subclipse.tools.usage/usage_reporting_enabled=false
> I am not seeing this problem with JBT and CR1.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18410) XCode 6 support
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18410?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-18410:
---------------------------------------------
my initial gut feeling is that we need to support both but I can understand we can maybe only support one and if we have to choose then xcode 6 it must be as otherwise we are dead with latest iphone6/ios8 push.
Does Xcode 6 require Yosemite or does it work with previous versions ?
if it works with previous versions I'm fine with going for ios-sim 3.
> XCode 6 support
> ---------------
>
> Key: JBIDE-18410
> URL: https://issues.jboss.org/browse/JBIDE-18410
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: aerogear-hybrid
> Affects Versions: 4.2.0.CR1
> Reporter: Gorkem Ercan
> Assignee: Gorkem Ercan
> Priority: Critical
> Fix For: 4.2.0.CR2
>
>
> Run on Simulator is broken for XCode 6. The solution is to update ios-sim to version 3.0 however ios-sim only supports XCode 6
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18239) Create new update site zip(s) (rather than target platform zip) for JBT content needed for Central/EA site
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18239?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-18239:
------------------------------------
Only problem w/ Max's new plan is that:
a) JBDS Central will need to point at JBT Aggregate site to resolve the missing JBT pieces, which is a no-no (can't install from .org into .com)
- or -
b) JBDS Central will need to point at A COPY OF the JBT Aggregate site to resolve the missing JBT pieces, which sucks as it means we'll be putting JBT site on both .org and .com server.
Max said above, "why have the content duplicated?" Because we have to according to the "don't cross the streams" rule.
Still, this is simpler. But it means that EVERYTHING in JBT will be theoretically browsable by a JBDS user if they look at the composite site (that contains JBT Central + JBT Aggregate) within their Eclipse/JBDS via Help > Install New.
Are we ok with exposing ALL of JBT from within JBDS? If not, then we *need* a new update site and can't just reuse the existing JBT aggregate within the JBDS Central composite.
[~maxandersen] [~mickael_istria] wdyt?
> Create new update site zip(s) (rather than target platform zip) for JBT content needed for Central/EA site
> ----------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18239
> URL: https://issues.jboss.org/browse/JBIDE-18239
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, central, discovery, updatesite
> Affects Versions: 4.2.0.CR1
> Reporter: Nick Boldt
> Labels: f2f2014
> Fix For: 4.3.0.Alpha1
>
>
> In order to simplify the process for getting JBT features into Central (for JBDS) and EA (for both JBT/JBDS), it's been suggested (by [~maxandersen], who doesn't like opening JIRAs :D) that instead of a target platform which needs to be updated every time we spin or respin a build, we could instead just produce an update site containing the handful of IUs (cordovasim, arquillian, etc.).
> We could further extend this idea to include all the things that currently are in BOTH JBT or JBDS and in Central, such as TestNG.
> These would be produced as new zips using the JBT aggregate builder:
> https://github.com/jbosstools/jbosstools-build-sites/tree/master/aggregate/
> Need to decide what to call this... "Extras" "JBT-not-in-JBDS" "Shared" ...?
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months