April 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3446) Add support for IzPack INSTALL_PATH property to predefine installation path

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3446?page=com.atlassian.jira.plugin.... ] Martin Malina closed JBDS-3446. ------------------------------- > Add support for IzPack INSTALL_PATH property to predefine installation path > --------------------------------------------------------------------------- > > Key: JBDS-3446 > URL: https://issues.jboss.org/browse/JBDS-3446 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: installer > Affects Versions: 8.1.0.GA > Reporter: Martin Malina > Assignee: Denis Golovin > Fix For: 11.3.0.GA > > > In a recent discussion around JBIDE-19852 , it was pointed out that IzPack supports supplying properties to the installer, so that some values are predefined. > Details are here: > http://docs.codehaus.org/display/IZPACK/Unattended+Installations > The idea is that you could run this: > java -DINSTALL_PATH=/default/path -jar installer.jar > And this would pre-fill the installation path to the path given in the command. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3446) Add support for IzPack INSTALL_PATH property to predefine installation path

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3446?page=com.atlassian.jira.plugin.... ] Martin Malina resolved JBDS-3446. --------------------------------- Fix Version/s: 11.3.0.GA (was: 12.x) Resolution: Won't Fix [~jrichter1] and I agreed that this is not needed and can be closed. It was never a requirement and was just an optional thing. > Add support for IzPack INSTALL_PATH property to predefine installation path > --------------------------------------------------------------------------- > > Key: JBDS-3446 > URL: https://issues.jboss.org/browse/JBDS-3446 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: installer > Affects Versions: 8.1.0.GA > Reporter: Martin Malina > Assignee: Denis Golovin > Fix For: 11.3.0.GA > > > In a recent discussion around JBIDE-19852 , it was pointed out that IzPack supports supplying properties to the installer, so that some values are predefined. > Details are here: > http://docs.codehaus.org/display/IZPACK/Unattended+Installations > The idea is that you could run this: > java -DINSTALL_PATH=/default/path -jar installer.jar > And this would pre-fill the installation path to the path given in the command. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23285) integration tests should share runtime downloads so that each test doesn't have to re-download the same runtime zips, and no longer use EOL'd runtimes

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23285?page=com.atlassian.jira.plugi... ] Martin Malina resolved JBIDE-23285. ----------------------------------- Fix Version/s: 4.5.3.Final (was: 4.6.x) Resolution: Out of Date > integration tests should share runtime downloads so that each test doesn't have to re-download the same runtime zips, and no longer use EOL'd runtimes > ------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-23285 > URL: https://issues.jboss.org/browse/JBIDE-23285 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: integration-tests > Affects Versions: 4.4.2.AM1 > Reporter: Nick Boldt > Assignee: Martin Malina > Fix For: 4.5.3.Final > > > While running the integration tests today to investigate JBDS-4077, I discovered that: > * org.jboss.ide.eclipse.as.ui.bot.test requires 11 runtimes, some of which are well past their EOL date [1]: > {code}jboss-3.2.8.SP1 jboss-4.2.3.GA jboss-5.1.0.GA jboss-as-7.0.2.Final wildfly-10.0.0.CR2 wildfly-9.0.1.Final > jboss-4.0.5.GA jboss-5.0.1.GA jboss-6.1.0.Final jboss-as-7.1.1.Final wildfly-8.2.0.Final{code} > * org.jboss.tools.deltaspike.ui.bot.test requires 1 runtime, wildfly-10.0.0.Final > [1] https://access.redhat.com/support/policy/updates/jboss_notes/eol vs. https://access.redhat.com/support/policy/updates/jboss_notes/ > So, three problems here: > a) different tests use different versions of the same runtime (WFLY 10.0.0.CR2 vs. Final) > b) different tests re-download their runtimes every time you do a clean, instead of fetching runtimes from a cache. So the same 160M of WFLY 10 gets downloaded twice. > c) we still test on runtimes that have been EOL'd years ago, such as AS 4.0 and earlier. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23285) integration tests should share runtime downloads so that each test doesn't have to re-download the same runtime zips, and no longer use EOL'd runtimes

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23285?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-23285. --------------------------------- > integration tests should share runtime downloads so that each test doesn't have to re-download the same runtime zips, and no longer use EOL'd runtimes > ------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-23285 > URL: https://issues.jboss.org/browse/JBIDE-23285 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: integration-tests > Affects Versions: 4.4.2.AM1 > Reporter: Nick Boldt > Assignee: Martin Malina > Fix For: 4.5.3.Final > > > While running the integration tests today to investigate JBDS-4077, I discovered that: > * org.jboss.ide.eclipse.as.ui.bot.test requires 11 runtimes, some of which are well past their EOL date [1]: > {code}jboss-3.2.8.SP1 jboss-4.2.3.GA jboss-5.1.0.GA jboss-as-7.0.2.Final wildfly-10.0.0.CR2 wildfly-9.0.1.Final > jboss-4.0.5.GA jboss-5.0.1.GA jboss-6.1.0.Final jboss-as-7.1.1.Final wildfly-8.2.0.Final{code} > * org.jboss.tools.deltaspike.ui.bot.test requires 1 runtime, wildfly-10.0.0.Final > [1] https://access.redhat.com/support/policy/updates/jboss_notes/eol vs. https://access.redhat.com/support/policy/updates/jboss_notes/ > So, three problems here: > a) different tests use different versions of the same runtime (WFLY 10.0.0.CR2 vs. Final) > b) different tests re-download their runtimes every time you do a clean, instead of fetching runtimes from a cache. So the same 160M of WFLY 10 gets downloaded twice. > c) we still test on runtimes that have been EOL'd years ago, such as AS 4.0 and earlier. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25971) Add Red Hat Developers sign up link to CDK New Server wizard

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25971?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-25971: --------------------------------------- FYI, the devsuite installer points here for the registration: https://developers.redhat.com/auth/realms/rhd/protocol/openid-connect/reg... > Add Red Hat Developers sign up link to CDK New Server wizard > ------------------------------------------------------------ > > Key: JBIDE-25971 > URL: https://issues.jboss.org/browse/JBIDE-25971 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Affects Versions: 4.5.3.Final > Reporter: Martin Malina > Assignee: Rob Stryker > Attachments: new-server-cdk.png > > > While reviewing documentation updates for cdk installation in devstudio, we noticed a thing that is not ideal in the workflow. > Imagine you don't have an account on developers.redhat.com yet. > You go to New Server -> CDK 3.2+. > On the next page, you're supposed to fill out your credentials, but you don't have any. Yes, you could argue that there is a way to get there: If you don't have an account, that probably also means that you don't have a cdk binary either - you need the account to download it. So you need to click Download and install runtime... and that will offer you a link to register. So once cdk is downloaded, you can then add the credentials. But that's pretty cumbersome. > So I would suggest we add a Register link somewhere - either on the New Server wizard's second page. Or once you click Add.. to add credentials. > That's issue 1. > !new-server-cdk.png! > There are also a few side issues: > 2. I would suggest you remove the Domain field/dropdown from the wizard. It's always just greyed out. If we ever want to support more of them we can add it back. And when you add the credentials you will see the domain there too, which is enough. > 3. When you click Download and install runtime..., select a version and then go to the next page, this page is called JBoss.org Credentials - it's actually access.redhat.com credentials, can you change the title? > 3.a Also, the link for signing up leads to access.redhat.com. Wouldn't it be better to point to developers.redhat.com sign up page? That's what devsuite installer does. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25971) Add Red Hat Developers sign up link to CDK New Server wizard

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25971?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-25971: --------------------------------------- Once this is done, it may require further changes for RHDEVDOCS-724 . > Add Red Hat Developers sign up link to CDK New Server wizard > ------------------------------------------------------------ > > Key: JBIDE-25971 > URL: https://issues.jboss.org/browse/JBIDE-25971 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Affects Versions: 4.5.3.Final > Reporter: Martin Malina > Assignee: Rob Stryker > Attachments: new-server-cdk.png > > > While reviewing documentation updates for cdk installation in devstudio, we noticed a thing that is not ideal in the workflow. > Imagine you don't have an account on developers.redhat.com yet. > You go to New Server -> CDK 3.2+. > On the next page, you're supposed to fill out your credentials, but you don't have any. Yes, you could argue that there is a way to get there: If you don't have an account, that probably also means that you don't have a cdk binary either - you need the account to download it. So you need to click Download and install runtime... and that will offer you a link to register. So once cdk is downloaded, you can then add the credentials. But that's pretty cumbersome. > So I would suggest we add a Register link somewhere - either on the New Server wizard's second page. Or once you click Add.. to add credentials. > That's issue 1. > !new-server-cdk.png! > There are also a few side issues: > 2. I would suggest you remove the Domain field/dropdown from the wizard. It's always just greyed out. If we ever want to support more of them we can add it back. And when you add the credentials you will see the domain there too, which is enough. > 3. When you click Download and install runtime..., select a version and then go to the next page, this page is called JBoss.org Credentials - it's actually access.redhat.com credentials, can you change the title? > 3.a Also, the link for signing up leads to access.redhat.com. Wouldn't it be better to point to developers.redhat.com sign up page? That's what devsuite installer does. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25971) Add Red Hat Developers sign up link to CDK New Server wizard

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25971?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-25971: ---------------------------------- Attachment: new-server-cdk.png > Add Red Hat Developers sign up link to CDK New Server wizard > ------------------------------------------------------------ > > Key: JBIDE-25971 > URL: https://issues.jboss.org/browse/JBIDE-25971 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Affects Versions: 4.5.3.Final > Reporter: Martin Malina > Assignee: Rob Stryker > Attachments: new-server-cdk.png > > > While reviewing documentation updates for cdk installation in devstudio, we noticed a thing that is not ideal in the workflow. > Imagine you don't have an account on developers.redhat.com yet. > You go to New Server -> CDK 3.2+. > On the next page, you're supposed to fill out your credentials, but you don't have any. Yes, you could argue that there is a way to get there: If you don't have an account, that probably also means that you don't have a cdk binary either - you need the account to download it. So you need to click Download and install runtime... and that will offer you a link to register. So once cdk is downloaded, you can then add the credentials. But that's pretty cumbersome. > So I would suggest we add a Register link somewhere - either on the New Server wizard's second page. Or once you click Add.. to add credentials. > That's issue 1. > There are also a few side issues: > 2. I would suggest you remove the Domain field/dropdown from the wizard. It's always just greyed out. If we ever want to support more of them we can add it back. And when you add the credentials you will see the domain there too, which is enough. > 3. When you click Download and install runtime..., select a version and then go to the next page, this page is called JBoss.org Credentials - it's actually access.redhat.com credentials, can you change the title? > 3.a Also, the link for signing up leads to access.redhat.com. Wouldn't it be better to point to developers.redhat.com sign up page? That's what devsuite installer does. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25971) Add Red Hat Developers sign up link to CDK New Server wizard

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25971?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-25971: ---------------------------------- Description: While reviewing documentation updates for cdk installation in devstudio, we noticed a thing that is not ideal in the workflow. Imagine you don't have an account on developers.redhat.com yet. You go to New Server -> CDK 3.2+. On the next page, you're supposed to fill out your credentials, but you don't have any. Yes, you could argue that there is a way to get there: If you don't have an account, that probably also means that you don't have a cdk binary either - you need the account to download it. So you need to click Download and install runtime... and that will offer you a link to register. So once cdk is downloaded, you can then add the credentials. But that's pretty cumbersome. So I would suggest we add a Register link somewhere - either on the New Server wizard's second page. Or once you click Add.. to add credentials. That's issue 1. !new-server-cdk.png! There are also a few side issues: 2. I would suggest you remove the Domain field/dropdown from the wizard. It's always just greyed out. If we ever want to support more of them we can add it back. And when you add the credentials you will see the domain there too, which is enough. 3. When you click Download and install runtime..., select a version and then go to the next page, this page is called JBoss.org Credentials - it's actually access.redhat.com credentials, can you change the title? 3.a Also, the link for signing up leads to access.redhat.com. Wouldn't it be better to point to developers.redhat.com sign up page? That's what devsuite installer does. was: While reviewing documentation updates for cdk installation in devstudio, we noticed a thing that is not ideal in the workflow. Imagine you don't have an account on developers.redhat.com yet. You go to New Server -> CDK 3.2+. On the next page, you're supposed to fill out your credentials, but you don't have any. Yes, you could argue that there is a way to get there: If you don't have an account, that probably also means that you don't have a cdk binary either - you need the account to download it. So you need to click Download and install runtime... and that will offer you a link to register. So once cdk is downloaded, you can then add the credentials. But that's pretty cumbersome. So I would suggest we add a Register link somewhere - either on the New Server wizard's second page. Or once you click Add.. to add credentials. That's issue 1. There are also a few side issues: 2. I would suggest you remove the Domain field/dropdown from the wizard. It's always just greyed out. If we ever want to support more of them we can add it back. And when you add the credentials you will see the domain there too, which is enough. 3. When you click Download and install runtime..., select a version and then go to the next page, this page is called JBoss.org Credentials - it's actually access.redhat.com credentials, can you change the title? 3.a Also, the link for signing up leads to access.redhat.com. Wouldn't it be better to point to developers.redhat.com sign up page? That's what devsuite installer does. > Add Red Hat Developers sign up link to CDK New Server wizard > ------------------------------------------------------------ > > Key: JBIDE-25971 > URL: https://issues.jboss.org/browse/JBIDE-25971 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Affects Versions: 4.5.3.Final > Reporter: Martin Malina > Assignee: Rob Stryker > Attachments: new-server-cdk.png > > > While reviewing documentation updates for cdk installation in devstudio, we noticed a thing that is not ideal in the workflow. > Imagine you don't have an account on developers.redhat.com yet. > You go to New Server -> CDK 3.2+. > On the next page, you're supposed to fill out your credentials, but you don't have any. Yes, you could argue that there is a way to get there: If you don't have an account, that probably also means that you don't have a cdk binary either - you need the account to download it. So you need to click Download and install runtime... and that will offer you a link to register. So once cdk is downloaded, you can then add the credentials. But that's pretty cumbersome. > So I would suggest we add a Register link somewhere - either on the New Server wizard's second page. Or once you click Add.. to add credentials. > That's issue 1. > !new-server-cdk.png! > There are also a few side issues: > 2. I would suggest you remove the Domain field/dropdown from the wizard. It's always just greyed out. If we ever want to support more of them we can add it back. And when you add the credentials you will see the domain there too, which is enough. > 3. When you click Download and install runtime..., select a version and then go to the next page, this page is called JBoss.org Credentials - it's actually access.redhat.com credentials, can you change the title? > 3.a Also, the link for signing up leads to access.redhat.com. Wouldn't it be better to point to developers.redhat.com sign up page? That's what devsuite installer does. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25971) Add Red Hat Developers sign up link to CDK New Server wizard

by Martin Malina (JIRA)

Martin Malina created JBIDE-25971: ------------------------------------- Summary: Add Red Hat Developers sign up link to CDK New Server wizard Key: JBIDE-25971 URL: https://issues.jboss.org/browse/JBIDE-25971 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: cdk Affects Versions: 4.5.3.Final Reporter: Martin Malina Assignee: Rob Stryker While reviewing documentation updates for cdk installation in devstudio, we noticed a thing that is not ideal in the workflow. Imagine you don't have an account on developers.redhat.com yet. You go to New Server -> CDK 3.2+. On the next page, you're supposed to fill out your credentials, but you don't have any. Yes, you could argue that there is a way to get there: If you don't have an account, that probably also means that you don't have a cdk binary either - you need the account to download it. So you need to click Download and install runtime... and that will offer you a link to register. So once cdk is downloaded, you can then add the credentials. But that's pretty cumbersome. So I would suggest we add a Register link somewhere - either on the New Server wizard's second page. Or once you click Add.. to add credentials. That's issue 1. There are also a few side issues: 2. I would suggest you remove the Domain field/dropdown from the wizard. It's always just greyed out. If we ever want to support more of them we can add it back. And when you add the credentials you will see the domain there too, which is enough. 3. When you click Download and install runtime..., select a version and then go to the next page, this page is called JBoss.org Credentials - it's actually access.redhat.com credentials, can you change the title? 3.a Also, the link for signing up leads to access.redhat.com. Wouldn't it be better to point to developers.redhat.com sign up page? That's what devsuite installer does. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25968) Downloaded CDK runtimes artifacts in /tmp folder are not given executable rights nor are copied into installation folder

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25968?page=com.atlassian.jira.plugi... ] Ondrej Dockal commented on JBIDE-25968: --------------------------------------- [~mmalina] Yes, it is exactly what Supriya saw. I did reproduced it on fedora, so it seems to be connected to linux only (and if you use default /tmp) as I tried it as well on windows 10 and it worked just well, on windows default temp folder is at C:\Users\user\AppData\Local\Temp. Not sure that removing anything from trash, configs, etc. helped, as I did try everything and only changing /tmp dolder helped. > Downloaded CDK runtimes artifacts in /tmp folder are not given executable rights nor are copied into installation folder > ------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-25968 > URL: https://issues.jboss.org/browse/JBIDE-25968 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.5.3.Final > Environment: Fedora 27 > Reporter: Ondrej Dockal > Assignee: Rob Stryker > Priority: Critical > Attachments: downloading_cdk_runtime.gif > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 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 April 2018