April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-660) Add test for Http Digest REST import

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-660?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-660. ----------------------------------- pushed > Add test for Http Digest REST import > ------------------------------------ > > Key: JBTIS-660 > URL: https://issues.jboss.org/browse/JBTIS-660 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: QE, teiid > Affects Versions: 4.3.0.Beta1 > Reporter: Matus Makovy > Assignee: Matus Makovy > Fix For: 4.3.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-575) Adapt 'CamelEditorTest' to 8.0.0

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-575?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-575. ----------------------------------- pushed > Adapt 'CamelEditorTest' to 8.0.0 > -------------------------------- > > Key: JBTIS-575 > URL: https://issues.jboss.org/browse/JBTIS-575 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Components: Fuse IDE, QE > Affects Versions: 4.3.0.Alpha2 > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > Priority: Critical > Fix For: 4.3.0.CR1 > > Time Spent: 1 day, 1 hour > Remaining Estimate: 0 minutes > > SSIA -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22171) Change to cdk launch config is not persisted

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22171?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-22171: --------------------------------------- Yes, or just make this a general issue. But in any case, this is nothing critical to get fixed right now. > Change to cdk launch config is not persisted > -------------------------------------------- > > Key: JBIDE-22171 > URL: https://issues.jboss.org/browse/JBIDE-22171 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.3.1.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > > I had a cdk server set up and I wanted to change it to point to another directory. > So I opened the server editor, opened launch config, changed the Working Directory path, clicked Apply, OK, closed the server editor. > But it turns out this changed was not persisted. > If I open the launch config again, the old path is still there. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3748) Installer - We need to define/document the minimum hardware requirements for the installer (and packages installed by the installer)

by Hardy Ferentschik (JIRA)

[ https://issues.jboss.org/browse/JBDS-3748?page=com.atlassian.jira.plugin.... ] Hardy Ferentschik commented on JBDS-3748: ----------------------------------------- Right the latest setting in the default _Vagrantfile_ is 3GB which can be changed via an env variable as well: {code} ... VM_MEMORY = ENV['VM_MEMORY'] || 3072 ... {code} > Installer - We need to define/document the minimum hardware requirements for the installer (and packages installed by the installer) > ------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBDS-3748 > URL: https://issues.jboss.org/browse/JBDS-3748 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: documentation, installer > Affects Versions: 9.1.0.GA > Reporter: Len DiMaggio > Assignee: Misha Ali > Labels: havoc > Fix For: 9.1.0.GA > > > The latest information that I can find for JBDS is: > https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Stu... > This is not adequate for the CDK, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22171) Change to cdk launch config is not persisted

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22171?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-22171: ------------------------------------- The same could be said for all other server adapters. So we can probably make duplicate issues for other server adapters as well. > Change to cdk launch config is not persisted > -------------------------------------------- > > Key: JBIDE-22171 > URL: https://issues.jboss.org/browse/JBIDE-22171 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.3.1.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > > I had a cdk server set up and I wanted to change it to point to another directory. > So I opened the server editor, opened launch config, changed the Working Directory path, clicked Apply, OK, closed the server editor. > But it turns out this changed was not persisted. > If I open the launch config again, the old path is still there. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22171) Change to cdk launch config is not persisted

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22171?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-22171: --------------------------------------- OK, looking again now, I can see that I can expand CDK Details in the server editor and edit the path there directly. I didn't see this before, so the obvious way for me to change an existing cdk adapter was to go to launch config. Perhaps the path in launch config should then be disabled for editing or something? The way it works now is clearly not very user friendly. > Change to cdk launch config is not persisted > -------------------------------------------- > > Key: JBIDE-22171 > URL: https://issues.jboss.org/browse/JBIDE-22171 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.3.1.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > > I had a cdk server set up and I wanted to change it to point to another directory. > So I opened the server editor, opened launch config, changed the Working Directory path, clicked Apply, OK, closed the server editor. > But it turns out this changed was not persisted. > If I open the launch config again, the old path is still there. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22171) Change to cdk launch config is not persisted

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22171?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-22171: ------------------------------------- The directory is pulled from the server editor every time. As with all server adapters, changing items in the launch configuration directly is only supported for some usecases, specifically things that tools doesn't also need to know about. So if you wanted to add some flags to the launch command, that's fine. But if you want to change the directory, that setting must be changed in the server editor. This is the same as all server adapters. > Change to cdk launch config is not persisted > -------------------------------------------- > > Key: JBIDE-22171 > URL: https://issues.jboss.org/browse/JBIDE-22171 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.3.1.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > > I had a cdk server set up and I wanted to change it to point to another directory. > So I opened the server editor, opened launch config, changed the Working Directory path, clicked Apply, OK, closed the server editor. > But it turns out this changed was not persisted. > If I open the launch config again, the old path is still there. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3652) Installer - Replace use of JBDS installer with JBDS product archive - to save time

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3652?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3652: ----------------------------- Priority: Minor (was: Major) > Installer - Replace use of JBDS installer with JBDS product archive - to save time > ---------------------------------------------------------------------------------- > > Key: JBDS-3652 > URL: https://issues.jboss.org/browse/JBDS-3652 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: installer > Affects Versions: 9.1.0.GA > Reporter: Len DiMaggio > Assignee: Denis Golovin > Priority: Minor > Labels: havoc, performance > Fix For: 10.0.0.Alpha1 > > > The current installer runs for several minutes when it invokes the JBDS installer - can we replace this a JBDS product archive and some follow-on tasks (such as setting the JDK location)? Thx! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3652) Installer - Replace use of JBDS installer with JBDS product archive - to save time

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3652?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3652: ---------------------------------- It might be faster to simply: unzip jbds.zip -d c:\devplatform vs. java -jar jbds.jar install.xml because the installer process has to unpack the jar, then unpack some of the jars in the jar (features + some plugins), then generate metadata & other files. So we could do all the installation up front when CREATING the devplatform installer, then simply zip up the results and embed THAT in the devplatform installer. So we'd still be using the installer the same way a normal user would, but we'd be then MOVING that install from a temp location into the dp installer and then out onto the user's disk. PROBABLY would work fine assuming no network drives, user permission issues, nothing installed into ~/.eclipse, and no spaces-in-paths issues. -- But to your point, it might be better to not precache that because a user might choose to install onto d:\dp or a network drive, in which case SOME of the installation process might end up in ~/.eclipse rather than in that user's d:\dp folder. So... yeah, I'd say we're better off letting the JBDS installation happen live, rather than pre-canning it and hoping it all goes to plan. > Installer - Replace use of JBDS installer with JBDS product archive - to save time > ---------------------------------------------------------------------------------- > > Key: JBDS-3652 > URL: https://issues.jboss.org/browse/JBDS-3652 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: installer > Affects Versions: 9.1.0.GA > Reporter: Len DiMaggio > Assignee: Denis Golovin > Labels: havoc, performance > Fix For: 10.0.0.Alpha1 > > > The current installer runs for several minutes when it invokes the JBDS installer - can we replace this a JBDS product archive and some follow-on tasks (such as setting the JDK location)? Thx! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3652) Installer - Replace use of JBDS installer with JBDS product archive - to save time

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3652?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-3652 at 4/13/16 10:29 AM: ------------------------------------------------------------ It might be faster to simply: unzip jbds.zip -d c:\devplatform vs. java -jar jbds.jar install.xml because the installer process has to unpack the jar, then unpack some of the jars in the jar (features + some plugins), then generate metadata & other files. So we could do all the installation up front when CREATING the devplatform installer, then simply zip up the results and embed THAT in the devplatform installer. So we'd still be using the installer the same way a normal user would, but we'd be then MOVING that install from a temp location into the dp installer and then out onto the user's disk. PROBABLY would work fine assuming no network drives, user permission issues, nothing installed into ~/.eclipse, and no spaces-in-paths issues. -- But to your point, it might be better to not precache that because a user might choose to install onto d:\dp or a network drive, in which case SOME of the installation process might end up in ~/.eclipse rather than in that user's d:\dp folder. So... yeah, I'd say we're better off letting the JBDS installation happen live, rather than pre-canning it and hoping it all goes to plan. -- I vote this should be a "WONTFIX". was (Author: nickboldt): It might be faster to simply: unzip jbds.zip -d c:\devplatform vs. java -jar jbds.jar install.xml because the installer process has to unpack the jar, then unpack some of the jars in the jar (features + some plugins), then generate metadata & other files. So we could do all the installation up front when CREATING the devplatform installer, then simply zip up the results and embed THAT in the devplatform installer. So we'd still be using the installer the same way a normal user would, but we'd be then MOVING that install from a temp location into the dp installer and then out onto the user's disk. PROBABLY would work fine assuming no network drives, user permission issues, nothing installed into ~/.eclipse, and no spaces-in-paths issues. -- But to your point, it might be better to not precache that because a user might choose to install onto d:\dp or a network drive, in which case SOME of the installation process might end up in ~/.eclipse rather than in that user's d:\dp folder. So... yeah, I'd say we're better off letting the JBDS installation happen live, rather than pre-canning it and hoping it all goes to plan. > Installer - Replace use of JBDS installer with JBDS product archive - to save time > ---------------------------------------------------------------------------------- > > Key: JBDS-3652 > URL: https://issues.jboss.org/browse/JBDS-3652 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: installer > Affects Versions: 9.1.0.GA > Reporter: Len DiMaggio > Assignee: Denis Golovin > Labels: havoc, performance > Fix For: 10.0.0.Alpha1 > > > The current installer runs for several minutes when it invokes the JBDS installer - can we replace this a JBDS product archive and some follow-on tasks (such as setting the JDK location)? Thx! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 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 April 2016