[JBoss JIRA] (JBTIS-386) Target Platform is missing some source plugins when generating with sources
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBTIS-386?page=com.atlassian.jira.plugin.... ]
Mickael Istria edited comment on JBTIS-386 at 2/10/15 9:08 AM:
---------------------------------------------------------------
Concretely, here are the steps I suggest. The final one is still running locally.
{code}
$ git clone git@github.com:jbosstools/jbosstools-integration-stack.git
$ cd jbosstools-integration-stack/target-platform/
$ sed -i -e "s/4.2.1.CR1/4.2.1.CR2-SNAPSHOT/g" -e "s/unified/multiple/g" pom.xml
$ mvn install
$ cd ../..
$ git clone git@github.com:fusesource/fuseide.git
$ cd fuseide/targetplatform/
$ mvn clean verify -Pmultiple2repo -Dmirror-target-to-repo.includeSources=true -Djbtis.version=4.2.1.CR2-SNAPSHOT
{code}
was (Author: mickael_istria):
Concretely, here are the steps I suggest. The final one is still running locally.
{code}
$ git clone git@github.com:jbosstools/jbosstools-integration-stack.git
$ cd jbosstools-integration-stack/target-platform/
$ sed -i -e "s/4.2.1.CR1/4.2.1.CR2-SNAPSHOT/g" -e "s/unified/multiple/g" pom.xml
$ git diff
$ git clone git@github.com:jbosstools/jbosstools-integration-stack.git
$ cd jbosstools-integration-stack/target-platform/
$ sed -i -e "s/4.2.1.CR1/4.2.1.CR2-SNAPSHOT/g" -e "s/unified/multiple/g" pom.xml
$ git diff
$ mvn install
$ cd ../..
$ git clone git@github.com:fusesource/fuseide.git
$ cd fuseide/targetplatform/
$ mvn clean verify -Pmultiple2repo -Dmirror-target-to-repo.includeSources=true -Djbtis.version=4.2.1.CR2-SNAPSHOT
{code}
> Target Platform is missing some source plugins when generating with sources
> ---------------------------------------------------------------------------
>
> Key: JBTIS-386
> URL: https://issues.jboss.org/browse/JBTIS-386
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 4.2.0.Final-TP
> Reporter: Lars Heinemann
> Assignee: Paul Leacu
> Priority: Critical
>
> when mirroring the TP locally with sources some of the source plugins are missing. for instance org.eclipse.wst.server.ui.source.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19184) Threadlock when JS autocomplete turned on
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19184?page=com.atlassian.jira.plugi... ]
Vlado Pakan commented on JBIDE-19184:
-------------------------------------
OK I will try more till now I was not successful.
> Threadlock when JS autocomplete turned on
> -----------------------------------------
>
> Key: JBIDE-19184
> URL: https://issues.jboss.org/browse/JBIDE-19184
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing, upstream
> Affects Versions: 4.2.2.Final
> Environment: JBDS 8.0.2
> Reporter: Mustafa Musaji
> Assignee: Victor Rubezhny
> Priority: Critical
> Fix For: 4.2.3.Beta1, 4.3.0.Alpha2
>
> Attachments: threaddump_jdk1.7.0_71_1422011702000.txt
>
>
> Seeing a thread lock when using large JS projects when trying to autocomplete. Please refer to attached thread dump.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBTIS-386) Target Platform is missing some source plugins when generating with sources
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBTIS-386?page=com.atlassian.jira.plugin.... ]
Mickael Istria commented on JBTIS-386:
--------------------------------------
Concretely, here are the steps I suggest. The final one is still running locally.
{code}
$ git clone git@github.com:jbosstools/jbosstools-integration-stack.git
$ cd jbosstools-integration-stack/target-platform/
$ sed -i -e "s/4.2.1.CR1/4.2.1.CR2-SNAPSHOT/g" -e "s/unified/multiple/g" pom.xml
$ git diff
$ git clone git@github.com:jbosstools/jbosstools-integration-stack.git
$ cd jbosstools-integration-stack/target-platform/
$ sed -i -e "s/4.2.1.CR1/4.2.1.CR2-SNAPSHOT/g" -e "s/unified/multiple/g" pom.xml
$ git diff
$ mvn install
$ cd ../..
$ git clone git@github.com:fusesource/fuseide.git
$ cd fuseide/targetplatform/
$ mvn clean verify -Pmultiple2repo -Dmirror-target-to-repo.includeSources=true -Djbtis.version=4.2.1.CR2-SNAPSHOT
{code}
> Target Platform is missing some source plugins when generating with sources
> ---------------------------------------------------------------------------
>
> Key: JBTIS-386
> URL: https://issues.jboss.org/browse/JBTIS-386
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 4.2.0.Final-TP
> Reporter: Lars Heinemann
> Assignee: Paul Leacu
> Priority: Critical
>
> when mirroring the TP locally with sources some of the source plugins are missing. for instance org.eclipse.wst.server.ui.source.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19184) Threadlock when JS autocomplete turned on
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19184?page=com.atlassian.jira.plugi... ]
Victor Rubezhny commented on JBIDE-19184:
-----------------------------------------
[~vpakan], you're correct - we shouldn't use debugger when trying to reproduce 'deadlock' issues. IMHO, the setting breakpoint itself might cause a deadlock.
Use Denis's way: play with content assist and hovering over variables/functions while playing with a big project (I mean a project with pretty big number of JavaScript files).
> Threadlock when JS autocomplete turned on
> -----------------------------------------
>
> Key: JBIDE-19184
> URL: https://issues.jboss.org/browse/JBIDE-19184
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing, upstream
> Affects Versions: 4.2.2.Final
> Environment: JBDS 8.0.2
> Reporter: Mustafa Musaji
> Assignee: Victor Rubezhny
> Priority: Critical
> Fix For: 4.2.3.Beta1, 4.3.0.Alpha2
>
> Attachments: threaddump_jdk1.7.0_71_1422011702000.txt
>
>
> Seeing a thread lock when using large JS projects when trying to autocomplete. Please refer to attached thread dump.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19194) FeedHenry requires minimal-json, but it was removed from TP
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19194?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-19194:
------------------------------------
Back story:
{quote}
(2015-02-09 16:37:47) gercan: nickboldt: https://github.com/ralfstx/minimal-json seems to be missing from the latest TP
(2015-02-09 16:38:06) nickboldt: aw, crap.
(2015-02-09 16:38:40) gercan: nickboldt: feedhenry uses it
(2015-02-09 16:39:09) nickboldt: ok - didn't know it was used for anything but Tern
(2015-02-09 16:42:04) nickboldt: gercan: you need this for 4.2.3 and 4.3.0, right?
(2015-02-09 16:42:59) gercan: nickboldt: yes, but 4.2.x seems to have it somehow
(2015-02-09 16:44:11) nickboldt: tp prolly hasn't finished rebuilding, or you're using the older tp
(2015-02-09 16:44:28) nickboldt: only removed it in the 4.42.x TP; still in the 4.40 and 4.41 versions
(2015-02-09 16:44:50) gercan: nickboldt: I had 4.41
(2015-02-09 16:47:01) nickboldt: gercan: can you just include it in your root pom? https://github.com/ralfstx/minimal-json#include
(2015-02-09 16:48:07) gercan: nickboldt: I could... you don't want it on TP?
(2015-02-09 16:48:18) nickboldt: *shrug*
(2015-02-09 16:48:30) nickboldt: well, I'm trying to find a stable update site
(2015-02-09 16:48:57) nickboldt: and the version we had in Tern was older than the version on https://github.com/ralfstx/minimal-json#include (0.9.1 vs. 0.9.2)
16:55
(2015-02-09 16:55:25) nickboldt: gercan: benefit to being in the TP is it's avail at install time for all projects (including Aerogear)
(2015-02-09 16:55:54) nickboldt: but we could also include it in the Aerogear update site, and aggregate it into JBT like we do for Tern (it's actually already there)
(2015-02-09 16:57:40) gercan: nickboldt: why is this not in eclipse orbit?
(2015-02-09 17:02:21) nickboldt: gercan: I don't know. Why isn't it?
(2015-02-09 17:02:40) gercan: nickboldt: I thought Eclipse RAP is using it
(2015-02-09 17:02:54) nickboldt: yes. doesn't mean it's in orbit{quote}
> FeedHenry requires minimal-json, but it was removed from TP
> -----------------------------------------------------------
>
> Key: JBIDE-19194
> URL: https://issues.jboss.org/browse/JBIDE-19194
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 4.2.3.Beta1, 4.3.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.2.3.Beta1, 4.3.0.Alpha1
>
>
> When moving Tern from the 4.42.x and 4.50.x target platforms into JST, we also moved minimal-json assuming nothing else required it.
> But turns out that Feedhenry (Aerogear) also needs minimal-json.
> So... we need to add that plugin back into the TPs, and make sure that the version we include works with both Aerogear/FeedHenry (0.9.2, same code base in both 4.2.3 and 4.3.0, currently) and JST/Tern (0.9.1 in JBT 4.2, 0.9.2 in JBT 4.3).
> [~maxandersen] [~gercan] [~dgolovin] [~akazakov]
> In JBT 4.2.0-2 we include Tern 0.6 and minimal-json 0.9.1.
> In JBT 4.2.3 we include Tern 0.7 and minimal-json 0.9.1.
> In JBT 4.3.0 we _currently_ include Tern 0.8 and minimal-json 0.9.2.
> Which version should we include in the target platforms for JBT 4.2.3 (4.42.0.Beta1) and JBT 4.3.0 (4.50.0.Alpha1) ?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19184) Threadlock when JS autocomplete turned on
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19184?page=com.atlassian.jira.plugi... ]
Vlado Pakan commented on JBIDE-19184:
-------------------------------------
I would prefer use case scenario instead setting breakpoints to be able to verify/replicate this issue if it would be possible. Anyway thanks for help.
Setting breakpoints is more scenario for devs to be able to work on issue IMHO.
> Threadlock when JS autocomplete turned on
> -----------------------------------------
>
> Key: JBIDE-19184
> URL: https://issues.jboss.org/browse/JBIDE-19184
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing, upstream
> Affects Versions: 4.2.2.Final
> Environment: JBDS 8.0.2
> Reporter: Mustafa Musaji
> Assignee: Victor Rubezhny
> Priority: Critical
> Fix For: 4.2.3.Beta1, 4.3.0.Alpha2
>
> Attachments: threaddump_jdk1.7.0_71_1422011702000.txt
>
>
> Seeing a thread lock when using large JS projects when trying to autocomplete. Please refer to attached thread dump.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19045) Update Tern.java (TP) and AngularJS (Central - Early Access) to 0.7 in 4.2.3, 0.8 in 4.3.0
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19045?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-19045:
-------------------------------
Summary: Update Tern.java (TP) and AngularJS (Central - Early Access) to 0.7 in 4.2.3, 0.8 in 4.3.0 (was: Update Tern.java (TP) and AngularJS (Central) IDE v.0.7)
> Update Tern.java (TP) and AngularJS (Central - Early Access) to 0.7 in 4.2.3, 0.8 in 4.3.0
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-19045
> URL: https://issues.jboss.org/browse/JBIDE-19045
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: central, jsp/jsf/xml/html source editing, target-platform
> Reporter: Alexey Kazakov
> Assignee: Denis Golovin
> Priority: Critical
> Fix For: 4.2.3.Beta1
>
>
> We are going to update Tern to v0.7.0 for 4.2.x.
> Master will be updated to the latest 0.8.0 (see the corresponding issue JBIDE-19002)
> p2diff output:
> {code}
> ./jbosstools-target-platforms/jbosstools/multiple/target/jbosstools-multiple.target.repo http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4...
> < tern.eclipse.ide.tools.core [0.7.0.201412012159]
> < tern.eclipse.ide.server.nodejs.ui [0.7.0.201412012159]
> < tern.eclipse.ide.tools.ui [0.7.0.201412012159]
> < tern.eclipse.ide.server.nodejs.embed.win32.win32.x86_64 [0.7.0.201412012159]
> < tern-jsdt-feature.feature.jar [0.7.0.201412012159]
> < tern.server.nodejs [0.7.0.201412012159]
> < tern-server-nodejs-feature.feature.jar [0.7.0.201412012159]
> < tern.core [0.7.0.201412012159]
> < tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86 [0.7.0.201412012159]
> < tern.eclipse.ide.server.nodejs.embed.win32.win32.x86 [0.7.0.201412012159]
> < tern.eclipse.ide.core [0.7.0.201412012159]
> < tern-server-nodejs-feature.feature.group [0.7.0.201412012159]
> < tern-feature.feature.group [0.7.0.201412012159]
> < tern.eclipse.ide.server.nodejs.core [0.7.0.201412012159]
> < tern.eclipse.ide.server.nodejs.embed.feature.jar [0.7.0.201412012159]
> < tern.eclipse.ide.ui [0.7.0.201412012159]
> < tern.eclipse.ide.tools.feature.feature.jar [0.7.0.201412012159]
> < tern.eclipse.ide.server.nodejs.embed.macosx.cocoa.x86_64 [0.7.0.201412012159]
> < tern-jsdt-feature.feature.group [0.7.0.201412012159]
> < tern-feature.feature.jar [0.7.0.201412012159]
> < tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86_64 [0.7.0.201412012159]
> < tern.eclipse.ide.server.nodejs.embed.feature.group [0.7.0.201412012159]
> < tern.eclipse.ide.jsdt [0.7.0.201412012159]
> < tern.eclipse.ide.tools.feature.feature.group [0.7.0.201412012159]
> < tern.eclipse [0.7.0.201412012159]
> > tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86_64 [0.6.0.201409231610]
> > tern.eclipse.ide.core [0.6.0.201409231610]
> > tern-feature.feature.jar [0.6.0.201409231610]
> > tern.eclipse.ide.tools.feature.feature.group [0.6.0.201409231610]
> > tern.server.nodejs [0.6.0.201409231610]
> > tern.eclipse.ide.server.nodejs.embed.win32.win32.x86 [0.6.0.201409231610]
> > tern-jsdt-feature.feature.jar [0.6.0.201409231610]
> > tern-feature.feature.group [0.6.0.201409231610]
> > tern.eclipse.ide.tools.ui [0.6.0.201409231610]
> > tern-jsdt-feature.feature.group [0.6.0.201409231610]
> > tern.eclipse.ide.server.nodejs.ui [0.6.0.201409231610]
> > tern.eclipse.ide.server.nodejs.embed.win32.win32.x86_64 [0.6.0.201409231610]
> > tern-server-nodejs-feature.feature.jar [0.6.0.201409231610]
> > tern.eclipse.ide.server.nodejs.embed.feature.group [0.6.0.201409231610]
> > tern.eclipse [0.6.0.201409231610]
> > tern.eclipse.ide.server.nodejs.core [0.6.0.201409231610]
> > tern.eclipse.ide.ui [0.6.0.201409231610]
> > tern.core [0.6.0.201409231610]
> > tern-server-nodejs-feature.feature.group [0.6.0.201409231610]
> > tern.eclipse.ide.tools.core [0.6.0.201409231610]
> > tern.eclipse.ide.jsdt [0.6.0.201409231610]
> > tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86 [0.6.0.201409231610]
> > tern.eclipse.ide.tools.feature.feature.jar [0.6.0.201409231610]
> > tern.eclipse.ide.server.nodejs.embed.macosx.cocoa.x86_64 [0.6.0.201409231610]
> > tern.eclipse.ide.server.nodejs.embed.feature.jar [0.6.0.201409231610]
> === Summary ===
> ./jbosstools-target-platforms/jbosstools/multiple/target/jbosstools-multiple.target.repo contains 25 unique IUs
> http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4... contains 25 unique IUs
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19194) FeedHenry requires minimal-json, but it was removed from TP
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19194?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-19194:
------------------------------------
Reason we no longer have Tern in the TPs: JBIDE-19045 (issue was about dealing w/ Tern 0.6 vs. Tern 0.7, but was applied in master branch too).
> FeedHenry requires minimal-json, but it was removed from TP
> -----------------------------------------------------------
>
> Key: JBIDE-19194
> URL: https://issues.jboss.org/browse/JBIDE-19194
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 4.2.3.Beta1, 4.3.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.2.3.Beta1, 4.3.0.Alpha1
>
>
> When moving Tern from the 4.42.x and 4.50.x target platforms into JST, we also moved minimal-json assuming nothing else required it.
> But turns out that Feedhenry (Aerogear) also needs minimal-json.
> So... we need to add that plugin back into the TPs, and make sure that the version we include works with both Aerogear/FeedHenry (0.9.2, same code base in both 4.2.3 and 4.3.0, currently) and JST/Tern (0.9.1 in JBT 4.2, 0.9.2 in JBT 4.3).
> [~maxandersen] [~gercan] [~dgolovin] [~akazakov]
> In JBT 4.2.0-2 we include Tern 0.6 and minimal-json 0.9.1.
> In JBT 4.2.3 we include Tern 0.7 and minimal-json 0.9.1.
> In JBT 4.3.0 we _currently_ include Tern 0.8 and minimal-json 0.9.2.
> Which version should we include in the target platforms for JBT 4.2.3 (4.42.0.Beta1) and JBT 4.3.0 (4.50.0.Alpha1) ?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19194) FeedHenry requires minimal-json, but it was removed from TP
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19194?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-19194:
------------------------------------
Link to JBIDE-19115, wherein we added FH to JBDS/JBT Central.
> FeedHenry requires minimal-json, but it was removed from TP
> -----------------------------------------------------------
>
> Key: JBIDE-19194
> URL: https://issues.jboss.org/browse/JBIDE-19194
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 4.2.3.Beta1, 4.3.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.2.3.Beta1, 4.3.0.Alpha1
>
>
> When moving Tern from the 4.42.x and 4.50.x target platforms into JST, we also moved minimal-json assuming nothing else required it.
> But turns out that Feedhenry (Aerogear) also needs minimal-json.
> So... we need to add that plugin back into the TPs, and make sure that the version we include works with both Aerogear/FeedHenry (0.9.2, same code base in both 4.2.3 and 4.3.0, currently) and JST/Tern (0.9.1 in JBT 4.2, 0.9.2 in JBT 4.3).
> [~maxandersen] [~gercan] [~dgolovin] [~akazakov]
> In JBT 4.2.0-2 we include Tern 0.6 and minimal-json 0.9.1.
> In JBT 4.2.3 we include Tern 0.7 and minimal-json 0.9.1.
> In JBT 4.3.0 we _currently_ include Tern 0.8 and minimal-json 0.9.2.
> Which version should we include in the target platforms for JBT 4.2.3 (4.42.0.Beta1) and JBT 4.3.0 (4.50.0.Alpha1) ?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months