February 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-19346) jbosstools-earlyaccess.properties contains old versions of tern, angular, jetty, and vjet

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19346?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19346: ------------------------------- Fix Version/s: 4.3.0.Alpha2 > jbosstools-earlyaccess.properties contains old versions of tern, angular, jetty, and vjet > ----------------------------------------------------------------------------------------- > > Key: JBIDE-19346 > URL: https://issues.jboss.org/browse/JBIDE-19346 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Fix For: 4.3.0.Alpha2 > > > While promoting JBT 4.3.0.Alpha1 to /development/ I realized that jbosstools-earlyaccess.properties contains old versions. We should have tern/angular 0.8 in there, right [~dgolovin] ? > {code} > $➔ cat jbosstools-earlyaccess.properties > #Mon Sep 01 18:54:14 CEST 2014 > org.eclipse.vjet.rt.feature.group=[0.10.0.201403201656,0.10.0.201403201656] > org.jboss.tools.arquillian.feature.feature.group=[1.1.2.CR1-v20140830-0003-B63,1.1.2.CR1-v20140830-0003-B63] > org.eclipse.vjet.extmod.jsdt.feature.group=[0.10.0.201403201656,0.10.0.201403201656] > org.eclipse.vjet.web.feature.group=[0.10.0.201403201656,0.10.0.201403201656] > org.eclipse.vjet.extmod.dltk.core.feature.group=[0.10.0.201403201656,0.10.0.201403201656] > org.eclipse.vjet.codegen.feature.group=[0.10.0.201403201656,0.10.0.201403201656] > tern-server-nodejs-feature.feature.group=[0.5.0.201408272110,0.5.0.201408272110] > org.eclipse.vjet.eclipse.feature.group=[0.10.0.201403201656,0.10.0.201403201656] > tern.eclipse.ide.tools.feature.feature.group=[0.5.0.201408272110,0.5.0.201408272110] > tern.eclipse.ide.server.nodejs.embed.feature.group=[0.5.0.201408272110,0.5.0.201408272110] > org.eclipse.vjet.vsf.domkit.feature.group=[0.10.0.201403201656,0.10.0.201403201656] > org.eclipse.equinox.server.jetty.feature.group=[1.1.100.v20140416-1649,1.1.100.v20140416-1649] > org.eclipse.vjet.extmod.rhino.feature.group=[0.10.0.201403201656,0.10.0.201403201656] > tern-feature.feature.group=[0.5.0.201408272110,0.5.0.201408272110] > org.eclipse.vjet.core.feature.group=[0.10.0.201403201656,0.10.0.201403201656] > tern-jsdt-feature.feature.group=[0.5.0.201408272110,0.5.0.201408272110] > angularjs-eclipse-feature.feature.group=[0.5.0.201408281218,0.5.0.201408281218] > {code} > -- http://download.jboss.org/jbosstools/discovery/staging/4.3.0.Alpha1/jboss... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19346) jbosstools-earlyaccess.properties contains old versions of tern, angular, jetty, and vjet

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-19346: ---------------------------------- Summary: jbosstools-earlyaccess.properties contains old versions of tern, angular, jetty, and vjet Key: JBIDE-19346 URL: https://issues.jboss.org/browse/JBIDE-19346 Project: Tools (JBoss Tools) Issue Type: Bug Components: build Affects Versions: 4.3.0.Alpha1 Reporter: Nick Boldt While promoting JBT 4.3.0.Alpha1 to /development/ I realized that jbosstools-earlyaccess.properties contains old versions. We should have tern/angular 0.8 in there, right [~dgolovin] ? {code} $➔ cat jbosstools-earlyaccess.properties #Mon Sep 01 18:54:14 CEST 2014 org.eclipse.vjet.rt.feature.group=[0.10.0.201403201656,0.10.0.201403201656] org.jboss.tools.arquillian.feature.feature.group=[1.1.2.CR1-v20140830-0003-B63,1.1.2.CR1-v20140830-0003-B63] org.eclipse.vjet.extmod.jsdt.feature.group=[0.10.0.201403201656,0.10.0.201403201656] org.eclipse.vjet.web.feature.group=[0.10.0.201403201656,0.10.0.201403201656] org.eclipse.vjet.extmod.dltk.core.feature.group=[0.10.0.201403201656,0.10.0.201403201656] org.eclipse.vjet.codegen.feature.group=[0.10.0.201403201656,0.10.0.201403201656] tern-server-nodejs-feature.feature.group=[0.5.0.201408272110,0.5.0.201408272110] org.eclipse.vjet.eclipse.feature.group=[0.10.0.201403201656,0.10.0.201403201656] tern.eclipse.ide.tools.feature.feature.group=[0.5.0.201408272110,0.5.0.201408272110] tern.eclipse.ide.server.nodejs.embed.feature.group=[0.5.0.201408272110,0.5.0.201408272110] org.eclipse.vjet.vsf.domkit.feature.group=[0.10.0.201403201656,0.10.0.201403201656] org.eclipse.equinox.server.jetty.feature.group=[1.1.100.v20140416-1649,1.1.100.v20140416-1649] org.eclipse.vjet.extmod.rhino.feature.group=[0.10.0.201403201656,0.10.0.201403201656] tern-feature.feature.group=[0.5.0.201408272110,0.5.0.201408272110] org.eclipse.vjet.core.feature.group=[0.10.0.201403201656,0.10.0.201403201656] tern-jsdt-feature.feature.group=[0.5.0.201408272110,0.5.0.201408272110] angularjs-eclipse-feature.feature.group=[0.5.0.201408281218,0.5.0.201408281218] {code} -- http://download.jboss.org/jbosstools/discovery/staging/4.3.0.Alpha1/jboss... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3268) Export a Cordova Application created using JBDS to FeedHenry

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3268?page=com.atlassian.jira.plugin.... ] Burr Sutter commented on JBDS-3268: ----------------------------------- [~rruss] I do not see "deeper integration" being a requirement at this time, with that said, I do welcome Gorkem's thoughts and if he would like to create another jira for us to track then I think that would make sense to at least have things written down. > Export a Cordova Application created using JBDS to FeedHenry > ------------------------------------------------------------ > > Key: JBDS-3268 > URL: https://issues.jboss.org/browse/JBDS-3268 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: aerogear-hybrid, requirements > Reporter: Burr Sutter > Assignee: Gorkem Ercan > Fix For: 9.0.0.CR1 > > > As a HTML5-focused mobile application developer, I wish to use JBoss Tools and JBDS to craft my AngularJS+Ionic or jQuery Mobile-based application, testing it via CordovaSim, deploy the application to my iOS and/or Android phone and when I feel it is "about right", push it to FeedHenry's git URL. > It is currently unclear how an end-user takes his/her JBDS Hybrid Mobile (Cordova) project and sets it up to support a git push to FH. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[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 edited comment on JBIDE-19184 at 2/20/15 3:28 PM: ------------------------------------------------------------------ [~dgolovin] AngularJS-Eclipse has changes against the previous versions (because the API is changed in Tern.java 0.8.2). I've made the PR: https://github.com/angelozerr/angularjs-eclipse/pull/144 So we still have to wait for Pascal to make the release of 0.8.2. As a one-minute replacement we can use the following snapshot: http://oss.opensagres.fr/angularjs-eclipse/0.8.2-SNAPSHOT/ which is based on the release of Tern.java v.0.8.2 (but itself is only a candidate to be released. was (Author: vrubezhny): [~dgolovin] AngularJS-Eclipse has changes against the previous versions (because the API is changed in Tern.java 0.8.2). I've made the PR: https://github.com/angelozerr/angularjs-eclipse/pull/144 So we still have to wait for Pascal to make the release of 0.8.2. As a one-minute replacement we can use the following snapshot: http://oss.opensagres.fr/angularjs-eclipse/0.8.2-SNAPSHOT/ which is based on the release of Tern.java v.0.8.2 (but itself is the only a candidate to be released. > 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: Blocker > 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

1
0
0 / 0

[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 edited comment on JBIDE-19184 at 2/20/15 3:28 PM: ------------------------------------------------------------------ [~dgolovin] AngularJS-Eclipse has changes against the previous versions (because the API is changed in Tern.java 0.8.2). I've made the PR: https://github.com/angelozerr/angularjs-eclipse/pull/144 So we still have to wait for Pascal to make the release of 0.8.2. As a one-minute replacement we can use the following snapshot: http://oss.opensagres.fr/angularjs-eclipse/0.8.2-SNAPSHOT/ which is based on the release of Tern.java v.0.8.2 (but itself is only a candidate to be released). was (Author: vrubezhny): [~dgolovin] AngularJS-Eclipse has changes against the previous versions (because the API is changed in Tern.java 0.8.2). I've made the PR: https://github.com/angelozerr/angularjs-eclipse/pull/144 So we still have to wait for Pascal to make the release of 0.8.2. As a one-minute replacement we can use the following snapshot: http://oss.opensagres.fr/angularjs-eclipse/0.8.2-SNAPSHOT/ which is based on the release of Tern.java v.0.8.2 (but itself is only a candidate to be released. > 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: Blocker > 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

1
0
0 / 0

[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: ----------------------------------------- [~dgolovin] AngularJS-Eclipse has changes against the previous versions (because the API is changed in Tern.java 0.8.2). I've made the PR: https://github.com/angelozerr/angularjs-eclipse/pull/144 So we still have to wait for Pascal to make the release of 0.8.2. As a one-minute replacement we can use the following snapshot: http://oss.opensagres.fr/angularjs-eclipse/0.8.2-SNAPSHOT/ which is based on the release of Tern.java v.0.8.2 (but itself is the only a candidate to be released. > 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: Blocker > 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

1
0
0 / 0

[JBoss JIRA] (JBDS-3271) Cordova App Splash Screen Support

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3271?page=com.atlassian.jira.plugin.... ] Burr Sutter commented on JBDS-3271: ----------------------------------- We should await FH, no need in trying to time it for perfect alignment nor "get out in front" of FH. > Cordova App Splash Screen Support > --------------------------------- > > Key: JBDS-3271 > URL: https://issues.jboss.org/browse/JBDS-3271 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: aerogear-hybrid, requirements > Reporter: Burr Sutter > Assignee: Gorkem Ercan > Fix For: 9.0.0.CR1 > > > As a HTML5+Cordova mobile app developer, I need to change the splash screen associated with the application launch. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3285) Git: Easy Import

by Rodney Russ (JIRA)

[ https://issues.jboss.org/browse/JBDS-3285?page=com.atlassian.jira.plugin.... ] Rodney Russ updated JBDS-3285: ------------------------------ CDW devel_ack: + (was: ?) > Git: Easy Import > ---------------- > > Key: JBDS-3285 > URL: https://issues.jboss.org/browse/JBDS-3285 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements, upstream > Affects Versions: 8.0.0.GA > Reporter: Burr Sutter > Assignee: Burr Sutter > Labels: usability > Fix For: 9.0.x > > > As a Java EE developer, in some cases using Git for the first time (or only familiar with command line git), I find it very difficult to clone and import a project correctly into JBDS, having the appropriate facets configured, if it has a maven pom.xml, correctly setting the build path, where it is easily deployable to a localhost EAP instance. > The mission here is to make the Git experience much more user friendly. > Progress/Status (updated progressively): > {quote} > Easymport framework has been contributed to e4 (Platform Incubator): in http://git.eclipse.org/c/e4/org.eclipse.e4.ui.git/tree/bundles , see all org.eclipse.e4.ui.importer* . You can install it in your IDE from http://download.eclipse.org/e4/snapshots/org.eclipse.e4.ui . The entry-points are either the new menu "File > Import projects from folder..." or from legacy import wizard under "General > Local folder(s) as project into workspace". > We have working extensions that allow to import Java EE & Maven: https://github.com/jbosstools/jbosstools-playground/tree/master/plugins (install from http://download.jboss.org/jbosstools/builds/staging/jbosstools-playground... ) , that we plan to contribute upstream when projects such as m2e and WTP when the framework seems mature enough. > There is not yet an easy link from the EGit wizard to the Easymport one, nor an easy link from SVN wizard to Easymport. > There is almost no chance that this can be included in Eclipse IDE for Mars release in June. But we could already think about including it in next JBoss Tools and JBoss Developer Studio milestones, so that we'd get more feedback. At this point, feedback from users and adopters is the key point. > I invite you to give it a try, and to report issues here. > {quote} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3285) Git: Easy Import

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3285?page=com.atlassian.jira.plugin.... ] Burr Sutter commented on JBDS-3285: ----------------------------------- @rruss I believe it is for now - ideally we would work hard to get some end-user feedback - run some "usability labs" but I do not think we would get funding for such a thing. > Git: Easy Import > ---------------- > > Key: JBDS-3285 > URL: https://issues.jboss.org/browse/JBDS-3285 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements, upstream > Affects Versions: 8.0.0.GA > Reporter: Burr Sutter > Assignee: Burr Sutter > Labels: usability > Fix For: 9.0.x > > > As a Java EE developer, in some cases using Git for the first time (or only familiar with command line git), I find it very difficult to clone and import a project correctly into JBDS, having the appropriate facets configured, if it has a maven pom.xml, correctly setting the build path, where it is easily deployable to a localhost EAP instance. > The mission here is to make the Git experience much more user friendly. > Progress/Status (updated progressively): > {quote} > Easymport framework has been contributed to e4 (Platform Incubator): in http://git.eclipse.org/c/e4/org.eclipse.e4.ui.git/tree/bundles , see all org.eclipse.e4.ui.importer* . You can install it in your IDE from http://download.eclipse.org/e4/snapshots/org.eclipse.e4.ui . The entry-points are either the new menu "File > Import projects from folder..." or from legacy import wizard under "General > Local folder(s) as project into workspace". > We have working extensions that allow to import Java EE & Maven: https://github.com/jbosstools/jbosstools-playground/tree/master/plugins (install from http://download.jboss.org/jbosstools/builds/staging/jbosstools-playground... ) , that we plan to contribute upstream when projects such as m2e and WTP when the framework seems mature enough. > There is not yet an easy link from the EGit wizard to the Easymport one, nor an easy link from SVN wizard to Easymport. > There is almost no chance that this can be included in Eclipse IDE for Mars release in June. But we could already think about including it in next JBoss Tools and JBoss Developer Studio milestones, so that we'd get more feedback. At this point, feedback from users and adopters is the key point. > I invite you to give it a try, and to report issues here. > {quote} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19345) allow NN to be filtered/redefined for NN

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19345?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-19345: ---------------------------------------- Fix Version/s: 4.2.3.CR1 4.3.0.CR1 > allow NN to be filtered/redefined for NN > ---------------------------------------- > > Key: JBIDE-19345 > URL: https://issues.jboss.org/browse/JBIDE-19345 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: website > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > Priority: Critical > Fix For: 4.2.3.CR1, 4.3.0.CR1 > > > there been examples of auto aggregation of NN be a hit or miss for how much it makes sense in the release. > For example: > Beta1: Added a few components to the Ionic Palette: <c1> <c2> <c3> > Beta2: Added a few components to the Ionic: <c4> <c5> > Alexey Kazakov: But in the final verision I would like to have: Added new components: <c1>,...<c5>. > One suggestion been to have ability to rewrite the full NN version at final but I just know that will kill us becase it is going to be a pain to copy/paste right. > Alternative suggestion is: > A) during rendering of the "final" aggregation set a asciidoc variable (i.e. "finalnn") allowing us to use asciidoc conditionals like > {code} > ifndef::finalnn[] > This piece of news was only relevant for Beta1 > endif::finalnn[] > {code} > See: http://mrhaki.blogspot.ch/2014/08/awesome-asciidoc-using-conditional.html > B) allow to add a .Final newnoteworthy adoc to use as place to write the aggregated news ..note, these should still be merged with the former NN's. so you only need to write the sections that are actually different. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 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 February 2015