March 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18964) Changing bean discovery mode doesn't run validation for existing beans

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18964?page=com.atlassian.jira.plugi... ] Alexey Kazakov resolved JBIDE-18964. ------------------------------------ Resolution: Done > Changing bean discovery mode doesn't run validation for existing beans > ---------------------------------------------------------------------- > > Key: JBIDE-18964 > URL: https://issues.jboss.org/browse/JBIDE-18964 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Affects Versions: 4.2.0.Final, 4.2.1.Final > Reporter: Rastislav Wagner > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19474) org.jboss.tools.foundation.help.ui is not included into foundation feature

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19474?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19474: ------------------------------------ Because apparently headless installer install requires that the plugin be explicitly included in the JBDS core feature. See JBIDE-19509 for details. That said, I've worked around this problem so ... you could simply close this as rejected if you'd like. > org.jboss.tools.foundation.help.ui is not included into foundation feature > -------------------------------------------------------------------------- > > Key: JBIDE-19474 > URL: https://issues.jboss.org/browse/JBIDE-19474 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.3.0.Alpha2 > Reporter: Denis Golovin > Assignee: Denis Golovin > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3163) change publishing process so that JBDS staging builds go to devstudio.redhat.com instead of www.qa server

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3163?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3163: ---------------------------------- Another problem with this is that directories are not browseable. So, if I publish a snapshot discovery site, like https://devstudio.redhat.com/9.0/snapshots/builds/jbosstools-discovery_ma..., I can't see the contents to click on the devstudio-directory.xml file. Increasingly I think this is a non-starter - maybe we should keep publishing to www.qa since at least there (like with download.jboss.org) dirs are browseable. OR we can push JBDS snapshot update and discovery sites to download.jboss.org instead ? I'm inclined to use *download.jboss.org* for *snapshots and staging* of JBDS 9 bits, since it's unlikely we can get eng-ops to make dirs browseable on devstudio.redhat.com (due to security concerns). Then all we need to do is push those bits to devstudio.redhat.com when it's time to migrate from staging to /development/ and /stable/. > change publishing process so that JBDS staging builds go to devstudio.redhat.com instead of www.qa server > --------------------------------------------------------------------------------------------------------- > > Key: JBDS-3163 > URL: https://issues.jboss.org/browse/JBDS-3163 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 8.0.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 9.0.0.Alpha2 > > > To simplify release/publishing process, we ought to start publishing nightlies and builds staged for QE onto devstudio.redhat.com (filemgmt) instead of the internal www.qa box. This will also allow us to use nightly URLs in ide-config.properties. > See https://github.com/jbosstools/jbosstools-download.jboss.org/pull/409/files for a bad solution to this problem. > Better solution is to move that content onto the new filemgmt instance and update promote.sh to push to the new location. > --- > After much discussion it's been decided that: > * we can push only the nightly/staging update sites automatically onto devstudio.redhat.com. > * Installers will remain internal-only until they're released and available on CSP and www.jboss.org -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

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

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBDS-3268?page=com.atlassian.jira.plugin.... ] Gorkem Ercan commented on JBDS-3268: ------------------------------------ "only git push" is not technically possible. FH git repositories are per application so in order to have a git repo to push into we need to first provision the repository through API. We will limit the scope to Cordova apps only. > 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-18964) Changing bean discovery mode doesn't run validation for existing beans

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18964?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18964: ----------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-base/pull/363, https://github.com/jbosstools/jbosstools-javaee/pull/281, https://github.com/jbosstools/jbosstools-javaee/pull/309 (was: https://github.com/jbosstools/jbosstools-base/pull/363, https://github.com/jbosstools/jbosstools-javaee/pull/281) > Changing bean discovery mode doesn't run validation for existing beans > ---------------------------------------------------------------------- > > Key: JBIDE-18964 > URL: https://issues.jboss.org/browse/JBIDE-18964 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Affects Versions: 4.2.0.Final, 4.2.1.Final > Reporter: Rastislav Wagner > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18964) Changing bean discovery mode doesn't run validation for existing beans

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18964?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-18964: ----------------------------------------------- PR https://github.com/jbosstools/jbosstools-javaee/pull/309 > Changing bean discovery mode doesn't run validation for existing beans > ---------------------------------------------------------------------- > > Key: JBIDE-18964 > URL: https://issues.jboss.org/browse/JBIDE-18964 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Affects Versions: 4.2.0.Final, 4.2.1.Final > Reporter: Rastislav Wagner > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19515) Forge New and Noteworthy for 4.2.3.Final

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19515?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19515: ----------------------------------- Fix Version/s: 4.2.3.Final (was: 4.2.3.CR1) Description: This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. If Forge is not listed here check if there are issues that should be added and add them. Document the ones relevant for Forge by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. If no news for this component please reject and close this issue. was: This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. If Forge is not listed here check if there are issues that should be added and add them. Document the ones relevant for Forge by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. If no news for this component please reject and close this issue. Git Pull Request: (was: https://github.com/jbosstools/jbosstools-website/pull/358) > Forge New and Noteworthy for 4.2.3.Final > ---------------------------------------- > > Key: JBIDE-19515 > URL: https://issues.jboss.org/browse/JBIDE-19515 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: forge, website > Reporter: Alexey Kazakov > Assignee: George Gastaldi > Priority: Critical > Fix For: 4.2.3.Final > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Forge is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Forge by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19515) Forge New and Noteworthy for 4.2.3.Final

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-19515: -------------------------------------- Summary: Forge New and Noteworthy for 4.2.3.Final Key: JBIDE-19515 URL: https://issues.jboss.org/browse/JBIDE-19515 Project: Tools (JBoss Tools) Issue Type: Task Components: forge, website Reporter: Alexey Kazakov Assignee: George Gastaldi Priority: Critical Fix For: 4.2.3.CR1 This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. If Forge is not listed here check if there are issues that should be added and add them. Document the ones relevant for Forge by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19448) Performance problems with angular-phonecat project

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19448?page=com.atlassian.jira.plugi... ] Victor Rubezhny commented on JBIDE-19448: ----------------------------------------- [~dgolovin] Yes, it does. > Performance problems with angular-phonecat project > -------------------------------------------------- > > Key: JBIDE-19448 > URL: https://issues.jboss.org/browse/JBIDE-19448 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing, upstream > Affects Versions: 4.2.3.Final > Environment: Tern.java + AngularJS-Eclipse installed > Reporter: Victor Rubezhny > Assignee: Victor Rubezhny > Fix For: 4.3.0.Alpha2 > > Attachments: IncludePath.png > > > On angular-phonecat project with the dependencies added by 'npm install' (as well as some other projects where dependencies are taken by bower with 'bower install') there is performance problem occurs. > 'npm install' and 'bower install' command could add more than 1000 JavaScripts into the project's Include Path, so this could lead into a problem with Eclipse's performance. > The workaround for the issue is to exclude some directories from JSDT Include Path like 'node_modules/' (in case of 'npm install' is used), 'bower_components/' (in case of 'bower install' is used) as well as other service directories containing JavaScripts that aren't used in JS application: > !IncludePath.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19007) As a user, I want to retrieve the build hook URL for a build config so I can configure my git repo to trigger a build on commit

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19007?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-19007: --------------------------------------- [~adietish] added buildconfig webhook > As a user, I want to retrieve the build hook URL for a build config so I can configure my git repo to trigger a build on commit > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19007 > URL: https://issues.jboss.org/browse/JBIDE-19007 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.2.2.Final > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Fix For: 4.3.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

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 March 2015