October 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-513) JBDS-IS 8.0.4.CR1 doesn't include all drools plugins such as kie

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-513?page=com.atlassian.jira.plugin.... ] Paul Leacu reassigned JBTIS-513: -------------------------------- Assignee: Paul Leacu > JBDS-IS 8.0.4.CR1 doesn't include all drools plugins such as kie > ---------------------------------------------------------------- > > Key: JBTIS-513 > URL: https://issues.jboss.org/browse/JBTIS-513 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution, drools/ jBPM > Affects Versions: 8.0.4.CR1 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Blocker > > At http://download.jboss.org/drools/release/6.3.0.Final/org.drools.updatesite/ you can see that there are also kie plugins which are not included in JBDS-IS 8.0.4.CR1 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20844) kitchensink-cordova project examples are not imported into the workspace

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20844?page=com.atlassian.jira.plugi... ] Snjezana Peco reassigned JBIDE-20844: ------------------------------------- Assignee: Alexey Kazakov (was: Snjezana Peco) Could you, please, review the PR? > kitchensink-cordova project examples are not imported into the workspace > ------------------------------------------------------------------------ > > Key: JBIDE-20844 > URL: https://issues.jboss.org/browse/JBIDE-20844 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.3.0.CR2 > Reporter: Pavol Srna > Assignee: Alexey Kazakov > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > Attachments: cordova.txt, screen.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20844) kitchensink-cordova project examples are not imported into the workspace

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20844?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-20844: --------------------------------------- The PR fixes the issue in the following way: - if the maven importer hasn't imported a project (the project doesn't contain pom.xml, for instance), check if the project contains the .project file and, if it does, import it as a simple Eclipse project - if the project hasn't been imported, the Project Ready wizard will write the following message: 'XXX' project hasn't been imported. Check if it is defined correctly. > kitchensink-cordova project examples are not imported into the workspace > ------------------------------------------------------------------------ > > Key: JBIDE-20844 > URL: https://issues.jboss.org/browse/JBIDE-20844 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.3.0.CR2 > Reporter: Pavol Srna > Assignee: Snjezana Peco > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > Attachments: cordova.txt, screen.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20844) kitchensink-cordova project examples are not imported into the workspace

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20844?page=com.atlassian.jira.plugi... ] Snjezana Peco edited comment on JBIDE-20844 at 10/2/15 9:13 AM: ---------------------------------------------------------------- The PR fixes the issue in the following way: - if the maven importer hasn't imported a project (the project doesn't contain pom.xml, for instance), check if the project contains the .project file and, if it does, import it as a simple Eclipse project - if the project hasn't been imported yet, the Project Ready wizard will write the following message: 'XXX' project hasn't been imported. Check if it is defined correctly. was (Author: snjeza): The PR fixes the issue in the following way: - if the maven importer hasn't imported a project (the project doesn't contain pom.xml, for instance), check if the project contains the .project file and, if it does, import it as a simple Eclipse project - if the project hasn't been imported, the Project Ready wizard will write the following message: 'XXX' project hasn't been imported. Check if it is defined correctly. > kitchensink-cordova project examples are not imported into the workspace > ------------------------------------------------------------------------ > > Key: JBIDE-20844 > URL: https://issues.jboss.org/browse/JBIDE-20844 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.3.0.CR2 > Reporter: Pavol Srna > Assignee: Snjezana Peco > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > Attachments: cordova.txt, screen.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2948) Improve Performance of small and large projects

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBDS-2948?page=com.atlassian.jira.plugin.... ] Rastislav Wagner commented on JBDS-2948: ---------------------------------------- [~akazakov] Can we move this JIRA to target 9.x ? > Improve Performance of small and large projects > ----------------------------------------------- > > Key: JBDS-2948 > URL: https://issues.jboss.org/browse/JBDS-2948 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: integration > Reporter: Max Rydahl Andersen > Assignee: Rastislav Wagner > Labels: f2f2014 > Fix For: 9.0.0.GA > > > Users have had noticable issues when importing projects having many schemas, many annotations and dependencies in past. Our and WTP validators seem to be causing issues - some are actual performance issues and others seem to be more perceived than actual issues. > Unfortunately perceived issues for the user feels just as slow as real issues. > Suggestion: > Look in jira for performance issues and add "performance" label to them > Allocate dev to use profiler to spot hotspots and get these findings reported/documented and then triage based on these findings > Work with QE to setup performance measurements for end user common operations related to these issues (example: import project, run validation etc.) for small (quickstarts), medium (ticketmonster) and large (wildfly) projects and publish these numbers over time and keep track if getting better/worse. > Setup goals to reach for these performance measurements. > Don’t add new features that make performance worse. For example don’t introduce one more slow validation feature to the validator which already has performance issues until those issues are solved. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-504) publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-504?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-504: ---------------------------------- Hey [~nickboldt] - It's time to enable the EA components. So clearly I'll re-enable them in the early access discovery plugin.xml. My question is what to do with the existing "not available" released-side discovery plugin.xml. See comment: https://issues.jboss.org/browse/JBIDE-20100?focusedCommentId=13110988&pag... If I just eliminate all of the certificationId="org.jboss.tools.discovery.certification.notavailable" connectors then the user will have no idea that "Fuse Tooling" is available under early access. Or does "not available" only apply to the release discovery plugin - thus I would keep all of the "not available" connectors and simply change the descriptor text to something like "Select the 'Enable Early Access' check box for an early access installation. Also available in Red Hat JBoss Developer Studio 8.x" > publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available > ----------------------------------------------------------------------------------- > > Key: JBTIS-504 > URL: https://issues.jboss.org/browse/JBTIS-504 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Paul Leacu > Fix For: 4.3.0.Alpha2 > > Attachments: is-in-dev.png, is-in-dev_JBDS.png > > > Per the details in JBIDE-20100, when IS is ready to go, it needs to provide the discovery jars into the JBT/JBDS CR1 site so that the "not available" connectors will be seen in JBT/JBDS. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20842) Need to implement npm support

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20842?page=com.atlassian.jira.plugi... ] Ilya Buziuk edited comment on JBIDE-20842 at 10/2/15 8:42 AM: -------------------------------------------------------------- After some npm investigation I can claim that npm support covered in the issue description can be implemented pretty easily. However, in order to make the implementation generic I do believe that *org.jboss.tools.jst.js* plugin must be refactored. My proposal is to split it to: * *org.jboss.tools.jst.js.node* (plugin with generic node tools launch, which will be subclassed for bower, npm etc. Node preferences + some utilities) * *org.jsboss.tools.jst.js.bower* (bower specific stuff, will have org.jboss.tools.jst.js.node as required bundle ) I think it will simplify the implementation of not only npm but also other node dependent tools (grunt, gulp etc.). It it sounds good I will create another issue for refactoring. was (Author: ibuziuk): After some npm investigation I can claim that npm support covered in the issue description can be implemented pretty easily. However, in order to make the implementation generic I do believe that *org.jboss.tools.jst.js* plugin must be refactored. My proposal is to split it to: * org.jboss.tools.jst.js.node (plugin with generic node tools launch, which will be subclassed for bower, npm etc. Node preferences + some utilities) * org.jsboss.tools.jst.js.bower (bower specific stuff, will have org.jboss.tools.jst.js.node as required bundle ) I think it will simplify the implementation of not only npm but also other node dependent tools (grunt, gulp etc.). It it sounds good I will create another issue for refactoring. > Need to implement npm support > ----------------------------- > > Key: JBIDE-20842 > URL: https://issues.jboss.org/browse/JBIDE-20842 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: javascript > Affects Versions: 4.3.0.CR1 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Labels: new_and_noteworthy > Fix For: 4.4.0.Alpha1 > > > Initially npm support should include the following commands: > 1) [init|https://docs.npmjs.com/cli/init] - package.json creation > 2) [update|https://docs.npmjs.com/cli/update] - updates all the packages listed to the latest version > 3) [install|https://docs.npmjs.com/cli/install] (no arguments) - Installs the dependencies in the local *node_modules* folder -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20842) Need to implement npm support

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20842?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-20842: ------------------------------------- After some npm investigation I can claim that npm support covered in the issue description can be implemented pretty easily. However, in order to make the implementation generic I do believe that *org.jboss.tools.jst.js* plugin must be refactored. My proposal is to split it to: * org.jboss.tools.jst.js.node (plugin with generic node tools launch, which will be subclassed for bower, npm etc. Node preferences + some utilities) * org.jsboss.tools.jst.js.bower (bower specific stuff, will have org.jboss.tools.jst.js.node as required bundle ) I think it will simplify the implementation of not only npm but also other node dependent tools (grunt, gulp etc.). It it sounds good I will create another issue for refactoring. > Need to implement npm support > ----------------------------- > > Key: JBIDE-20842 > URL: https://issues.jboss.org/browse/JBIDE-20842 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: javascript > Affects Versions: 4.3.0.CR1 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Labels: new_and_noteworthy > Fix For: 4.4.0.Alpha1 > > > Initially npm support should include the following commands: > 1) [init|https://docs.npmjs.com/cli/init] - package.json creation > 2) [update|https://docs.npmjs.com/cli/update] - updates all the packages listed to the latest version > 3) [install|https://docs.npmjs.com/cli/install] (no arguments) - Installs the dependencies in the local *node_modules* folder -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-513) JBDS-IS 8.0.4.CR1 doesn't include all drools plugins such as kie

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-513?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-513: ------------------------------------ Description: At http://download.jboss.org/drools/release/6.3.0.Final/org.drools.updatesite/ you can see that there are also kie plugins which are not included in JBDS-IS 8.0.4.CR1 (was: At http://download.jboss.org/drools/release/6.3.0.Final/org.drools.updatesite/ you can see the there are also kie plugins which are not included in JBDS-IS 8.0.4.CR1) > JBDS-IS 8.0.4.CR1 doesn't include all drools plugins such as kie > ---------------------------------------------------------------- > > Key: JBTIS-513 > URL: https://issues.jboss.org/browse/JBTIS-513 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution, drools/ jBPM > Affects Versions: 8.0.4.CR1 > Reporter: Andrej Podhradsky > Priority: Blocker > > At http://download.jboss.org/drools/release/6.3.0.Final/org.drools.updatesite/ you can see that there are also kie plugins which are not included in JBDS-IS 8.0.4.CR1 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-513) JBDS-IS 8.0.4.CR1 doesn't include all drools plugins such as kie

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBTIS-513: --------------------------------------- Summary: JBDS-IS 8.0.4.CR1 doesn't include all drools plugins such as kie Key: JBTIS-513 URL: https://issues.jboss.org/browse/JBTIS-513 Project: JBoss Tools Integration Stack Issue Type: Bug Components: distribution, drools/ jBPM Affects Versions: 8.0.4.CR1 Reporter: Andrej Podhradsky Priority: Blocker At http://download.jboss.org/drools/release/6.3.0.Final/org.drools.updatesite/ you can see the there are also kie plugins which are not included in JBDS-IS 8.0.4.CR1 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 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 October 2015