[JBoss JIRA] (JBDS-3769) Remove JSPM from dependencies
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/JBDS-3769?page=com.atlassian.jira.plugin.... ]
Pavol Pitonak commented on JBDS-3769:
-------------------------------------
+1 for removing JSPM
# JSPM bring modules into web apps, since we run inside Electron exclusively, we already have this feature so we don't need JSPM
# JSPM manages client-side dependencies (downloads them from npm/Github) - we can download them directly from npm repo, don't need JSPM
# JSPM causes "Github rate limit reached" error, we can solve it on our dev machines and CI but it's not friendly to new contributors, JSPM 0.17 should solve it
# we cannot upgrade to Babel 6 because JSPM 0.16 doesn't support it
# by removing JSPM, we can remove other dependencies (namely karma-jspm) so our test configuration will be easier to understand and debug (karma-jspm causes some problems)
> Remove JSPM from dependencies
> -----------------------------
>
> Key: JBDS-3769
> URL: https://issues.jboss.org/browse/JBDS-3769
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Components: installer
> Affects Versions: 9.1.0.CR1
> Reporter: Jan Richter
> Priority: Critical
> Labels: havoc
>
> After a change introduced in jspm 0.16.32 which caused our builds to fail (JBDS-3747) now another issue has arisen causing errors on npm install (both local and in CI environment). Even if this new issue is fixed in jspm, we would still have to face the first issue after updating.
> Therefore I propose to remove jspm entirely. We only use a small fraction of its functionality and it needlessly complicates the build + causes major issues. Since such change is likely to be quite complex, we should slip it after the April release and use an existing quick fix in the mean time.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3769) Remove JSPM from dependencies
by Jan Richter (JIRA)
Jan Richter created JBDS-3769:
---------------------------------
Summary: Remove JSPM from dependencies
Key: JBDS-3769
URL: https://issues.jboss.org/browse/JBDS-3769
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Task
Components: installer
Affects Versions: 9.1.0.CR1
Reporter: Jan Richter
Priority: Critical
After a change introduced in jspm 0.16.32 which caused our builds to fail (JBDS-3747) now another issue has arisen causing errors on npm install (both local and in CI environment). Even if this new issue is fixed in jspm, we would still have to face the first issue after updating.
Therefore I propose to remove jspm entirely. We only use a small fraction of its functionality and it needlessly complicates the build + causes major issues. Since such change is likely to be quite complex, we should slip it after the April release and use an existing quick fix in the mean time.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21781) Running Cordova projects with Cordova plugins fails on iOS simulators
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21781?page=com.atlassian.jira.plugi... ]
Pavol Srna closed JBIDE-21781.
------------------------------
Verified in JBT 4.3.1.CR1 respin-a build.
> Running Cordova projects with Cordova plugins fails on iOS simulators
> ---------------------------------------------------------------------
>
> Key: JBIDE-21781
> URL: https://issues.jboss.org/browse/JBIDE-21781
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.3.1.Beta2
> Environment: Mac OS X 10.11.3 (El Capitan);
> XCode 7.2.1;
> JBDS 9.1.0 Beta2
> iPhone 6 Simulator (iOS 9.2) among others
> Reporter: Vineet Reynolds
> Assignee: Gorkem Ercan
> Priority: Blocker
> Fix For: 4.3.1.CR1
>
>
> Cordova projects with Cordova plugins fail to run correctly when started with the iOS simulator through JBDS.
> This appears to be related to JBIDE-21780 where a default config.xml file is created on the fly in the exported XCode project before the project is built and deployed on the simulator.
> Attaching a JavaScript debugger using Safari indicates that Cordova was not initialized successfully. The following messages are reported:
> {{deviceready has not fired after 5 seconds.}}
> {{Channel not fired: onCordovaInfoReady}}
> which indicates that Cordova failed to initialise.
> As indicated previously, this appears to be related to JBIDE-21780. The config.xml file should be in the location (of the XCode project) as indicated in https://github.com/VineetReynolds/cordova-test/tree/master/demo-ios-worki... instead of https://github.com/VineetReynolds/cordova-test/tree/master/demo-ios-not-w...
> In the working version, config.xml is at {{demo-ios-working/demo/ios/demo/config.xml}} only whereas in the non-working one, it is at {{demo-ios-not-working/demo/ios/demo/config.xml}} (notice lack of Cordova plugin info) and {{demo-ios-not-working/demo/ios/www/config.xml}}.
> A workaround could be obtained by exporting the project and modifying the config.xml, but that basically renders the JBDS tooling moot.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22107) Show In - Web Browser from context menu of J2EE module on OS3 Server Adapter opens localhost
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22107?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-22107:
----------------------------------
Fix Version/s: 4.4.0.Alpha1
(was: 4.3.1.CR1)
> Show In - Web Browser from context menu of J2EE module on OS3 Server Adapter opens localhost
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-22107
> URL: https://issues.jboss.org/browse/JBIDE-22107
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Rob Stryker
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.0.Alpha1
>
>
> When selecting Show In - Web Browser from context menu of Java EE module under an OpenShift 3 connection, it opens a localhost, what is wrong (it does not use root). Such module can be e.g. jboss-kitchensink when using application based on eap s2i template with param CONTEXT_DIR kitchensink.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22107) Show In - Web Browser from context menu of J2EE module on OS3 Server Adapter opens localhost
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-22107:
-------------------------------------
Summary: Show In - Web Browser from context menu of J2EE module on OS3 Server Adapter opens localhost
Key: JBIDE-22107
URL: https://issues.jboss.org/browse/JBIDE-22107
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.CR1
Reporter: Marián Labuda
Assignee: Rob Stryker
Priority: Critical
Fix For: 4.3.1.CR1
When selecting Show In - Web Browser from context menu of Java EE module under an OpenShift 3 connection, it opens a localhost, what is wrong (it does not use root). Such module can be e.g. jboss-kitchensink when using application based on eap s2i template with param CONTEXT_DIR kitchensink.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years