[JBoss JIRA] (JBIDE-25170) Using empty profile in CDK 3.2+ server adapter should work with cdk's default profile (minishift)
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25170?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-25170:
----------------------------------
Steps to Reproduce:
1. EXEC: Have cdk 3.2.x binary downloaded
2. EXEC: Create CDK 3.2+ adapter with no profile set
3. EXEC: Prepare cdk: call setup-cdk on cli
4. ASSERT: calling 'minishift profile list' returns '- minishift Does Not Exist (active)'
5. EXEC: Start CDK 3.2+ server adapter
6. ASSERT: Adapter is started, 'minishift profile list' returns '- minishift Running (active)'
7. EXEC: Add new CDK 3.2+ called test and set profile to ie. 'test'
8. EXEC: call 'minishift setup-cdk --profile test'
9. EXEC: Start CDK 3.2+ test server adapter -> this should set profile 'test' as active
10. ASSERT: CDK 3.2+ test SA is started
11. ASSERT: 'minishift profile list' shows two running profiles and 'test' is active
12. EXEC: Stop CDK 3.2+ default server adapter (the one without profile set)
13. ASSERT: CDK 3.2+ adapter is stopped - This shows adapter's state as stopped, which is false positive information
14. ASSERT: 'minishift profile list' shows that default 'minishift' profile is stopped - FAIL
Instead, active profile 'test' was stopped, because stop operation was not passed with --profile ProfileName flag, which should be in this case 'minishift' to stop proper adapter/profile.
was:
1. EXEC: Have cdk 3.2.x binary downloaded
2. EXEC: Create CDK 3.2+ adapter with no profile set
3. EXEC: Prepare cdk: call setup-cdk on cli
4. ASSERT: calling 'minishift profile list' returns '- minishift Does Not Exist (active)'
5. EXEC: Start CDK 3.2+ server adapter
6. ASSERT: Adapter is started, 'minishift profile list' returns '- minishift Running (active)'
7. EXEC: Add new CDK 3.2+ called test and set profile to ie. 'test'
8. EXEC: call 'minishift setup-cdk --profile test'
9. EXEC: Start CDK 3.2+ test server adapter -> this should set profile 'test' as active
10. ASSERT: CDK 3.2+ test SA is started
11. ASSERT: 'minishift profile list' shows two running profiles and 'test' is active
12. EXEC: Stop CDK 3.2+ default server adapter (the one without profile set)
13. ASSERT: CDK 3.2+ adapter is stopped - FAIL
14. ASSERT: 'minishift profile list' shows that default 'minishift' profile is stopped - FAIL
Instead, active profile 'test' was stopped, because stop operation was not passed with --profile ProfileName flag, which should be in this case 'minishift' to stop proper adapter/profile.
> Using empty profile in CDK 3.2+ server adapter should work with cdk's default profile (minishift)
> -------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25170
> URL: https://issues.jboss.org/browse/JBIDE-25170
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.5.1.AM3
> Reporter: Ondrej Dockal
>
> I have two running CDK 3.2+ server adapters, and if I operate the one where profile is not defined (I would expect that it is set to default one aka 'minishift') it works with actually active profile.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 6 months
[JBoss JIRA] (JBDS-4103) Install JDK and force usage of it for JBDS even if a JRE is available
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBDS-4103?page=com.atlassian.jira.plugin.... ]
Aurélien Pupier updated JBDS-4103:
----------------------------------
Summary: Install JDK and force usage of it for JBDS even if a JRE is available (was: Install JDK and force usage of it even if a JRE is available)
> Install JDK and force usage of it for JBDS even if a JRE is available
> ---------------------------------------------------------------------
>
> Key: JBDS-4103
> URL: https://issues.jboss.org/browse/JBDS-4103
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Affects Versions: 10.1.0.GA
> Reporter: Aurélien Pupier
> Assignee: Denis Golovin
> Fix For: 11.x
>
>
> When using JBDS, a lot of people will use Maven and having a JDK by default is better.
> It allows to launch Maven install with java compilation directly, without extra configuration.
> (as a side note, do we really want to set a vm in .ini? when the Vm is updated, the link is broken and we need to update it)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 6 months
[JBoss JIRA] (JBIDE-25170) Using empty profile in CDK 3.2+ server adapter should work with cdk's default profile (minishift)
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25170?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-25170:
----------------------------------
Steps to Reproduce:
1. EXEC: Have cdk 3.2.x binary downloaded
2. EXEC: Create CDK 3.2+ adapter with no profile set
3. EXEC: Prepare cdk: call setup-cdk on cli
4. ASSERT: calling 'minishift profile list' returns '- minishift Does Not Exist (active)'
5. EXEC: Start CDK 3.2+ server adapter
6. ASSERT: Adapter is started, 'minishift profile list' returns '- minishift Running (active)'
7. EXEC: Add new CDK 3.2+ called test and set profile to ie. 'test'
8. EXEC: call 'minishift setup-cdk --profile test'
9. EXEC: Start CDK 3.2+ test server adapter -> this should set profile 'test' as active
10. ASSERT: CDK 3.2+ test SA is started
11. ASSERT: 'minishift profile list' shows two running profiles and 'test' is active
12. EXEC: Stop CDK 3.2+ default server adapter (the one without profile set)
13. ASSERT: CDK 3.2+ adapter is stopped - FAIL
14. ASSERT: 'minishift profile list' shows that default 'minishift' profile is stopped - FAIL
Instead, active profile 'test' was stopped, because stop operation was not passed with --profile ProfileName flag, which should be in this case 'minishift' to stop proper adapter/profile.
was:
1. EXEC: Have cdk 3.2.x binary downloaded
2. EXEC: Create CDK 3.2+ adapter with no profile set
3. EXEC: Prepare cdk: call setup-cdk on cli
4. ASSERT: calling 'minishift profile list' returns '- minishift Does Not Exist (active)'
5. EXEC: Start CDK 3.2+ server adapter
6. ASSERT: Adapter is started, 'minishift profile list' returns '- minishift Running (active)'
7. EXEC: Add new CDK 3.2+ called test and set profile to ie. 'test'
8. EXEC: call 'minishift setup-cdk --profile test' -> this will set active profile to 'test'
9. ASSERT: 'minishift profile list' returns two profiles where profile 'test' is active
10. EXEC: Start CDK 3.2+ test server adapter
11. ASSERT: CDK 3.2+ test SA is started
12. ASSERT: 'minishift profile list' shows two running profiles and 'test' is active
13. EXEC: Stop CDK 3.2+ default server adapter (the one without profile set)
14. ASSERT: CDK 3.2+ adapter is stopped - FAIL
15. ASSERT: 'minishift profile list' shows that default 'minishift' profile is stopped - FAIL
Instead, active profile 'test' was stopped, because stop operation was not passed with --profile ProfileName flag, which should be in this case 'minishift' to stop proper adapter/profile.
> Using empty profile in CDK 3.2+ server adapter should work with cdk's default profile (minishift)
> -------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25170
> URL: https://issues.jboss.org/browse/JBIDE-25170
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.5.1.AM3
> Reporter: Ondrej Dockal
>
> I have two running CDK 3.2+ server adapters, and if I operate the one where profile is not defined (I would expect that it is set to default one aka 'minishift') it works with actually active profile.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 6 months
[JBoss JIRA] (JBDS-4103) Install JDK and force usage of it even if a JRE is available
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBDS-4103?page=com.atlassian.jira.plugin.... ]
Aurélien Pupier commented on JBDS-4103:
---------------------------------------
another argument to force JDK: some m2e connectors are silently stopping to work when only a JRE is available (maven-bundle-plugin is not generating MANIFEST.MF for instance)
> Install JDK and force usage of it even if a JRE is available
> ------------------------------------------------------------
>
> Key: JBDS-4103
> URL: https://issues.jboss.org/browse/JBDS-4103
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Affects Versions: 10.1.0.GA
> Reporter: Aurélien Pupier
> Assignee: Denis Golovin
> Fix For: 11.x
>
>
> When using JBDS, a lot of people will use Maven and having a JDK by default is better.
> It allows to launch Maven install with java compilation directly, without extra configuration.
> (as a side note, do we really want to set a vm? when the Vm is updated, the link is broken and we need to update it)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 6 months
[JBoss JIRA] (JBDS-4103) Install JDK and force usage of it even if a JRE is available
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBDS-4103?page=com.atlassian.jira.plugin.... ]
Aurélien Pupier updated JBDS-4103:
----------------------------------
Description:
When using JBDS, a lot of people will use Maven and having a JDK by default is better.
It allows to launch Maven install with java compilation directly, without extra configuration.
(as a side note, do we really want to set a vm in .ini? when the Vm is updated, the link is broken and we need to update it)
was:
When using JBDS, a lot of people will use Maven and having a JDK by default is better.
It allows to launch Maven install with java compilation directly, without extra configuration.
(as a side note, do we really want to set a vm? when the Vm is updated, the link is broken and we need to update it)
> Install JDK and force usage of it even if a JRE is available
> ------------------------------------------------------------
>
> Key: JBDS-4103
> URL: https://issues.jboss.org/browse/JBDS-4103
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Affects Versions: 10.1.0.GA
> Reporter: Aurélien Pupier
> Assignee: Denis Golovin
> Fix For: 11.x
>
>
> When using JBDS, a lot of people will use Maven and having a JDK by default is better.
> It allows to launch Maven install with java compilation directly, without extra configuration.
> (as a side note, do we really want to set a vm in .ini? when the Vm is updated, the link is broken and we need to update it)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 6 months
[JBoss JIRA] (JBDS-4103) Install JDK and force usage of it even if a JRE is available
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBDS-4103?page=com.atlassian.jira.plugin.... ]
Aurélien Pupier updated JBDS-4103:
----------------------------------
Summary: Install JDK and force usage of it even if a JRE is available (was: Prefer JDK over JRE as VM set in devstudio.ini)
> Install JDK and force usage of it even if a JRE is available
> ------------------------------------------------------------
>
> Key: JBDS-4103
> URL: https://issues.jboss.org/browse/JBDS-4103
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Affects Versions: 10.1.0.GA
> Reporter: Aurélien Pupier
> Assignee: Denis Golovin
> Fix For: 11.x
>
>
> When using JBDS, a lot of people will use Maven and having a JDK by default is better.
> It allows to launch Maven install with java compilation directly, without extra configuration.
> (as a side note, do we really want to set a vm? when the Vm is updated, the link is broken and we need to update it)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 6 months
[JBoss JIRA] (JBIDE-25170) Using empty profile in CDK 3.2+ server adapter should work with cdk's default profile (minishift)
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25170?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-25170:
----------------------------------
Steps to Reproduce:
1. EXEC: Have cdk 3.2.x binary downloaded
2. EXEC: Create CDK 3.2+ adapter with no profile set
3. EXEC: Prepare cdk: call setup-cdk on cli
4. ASSERT: calling 'minishift profile list' returns '- minishift Does Not Exist (active)'
5. EXEC: Start CDK 3.2+ server adapter
6. ASSERT: Adapter is started, 'minishift profile list' returns '- minishift Running (active)'
7. EXEC: Add new CDK 3.2+ called test and set profile to ie. 'test'
8. EXEC: call 'minishift setup-cdk --profile test' -> this will set active profile to 'test'
9. ASSERT: 'minishift profile list' returns two profiles where profile 'test' is active
10. EXEC: Start CDK 3.2+ test server adapter
11. ASSERT: CDK 3.2+ test SA is started
12. ASSERT: 'minishift profile list' shows two running profiles and 'test' is active
13. EXEC: Stop CDK 3.2+ default server adapter (the one without profile set)
14. ASSERT: CDK 3.2+ adapter is stopped - FAIL
15. ASSERT: 'minishift profile list' shows that default 'minishift' profile is stopped - FAIL
Instead, active profile 'test' was stopped, because stop operation was not passed with --profile ProfileName flag, which should be in this case 'minishift' to stop proper adapter/profile.
was:
1. EXEC: Have cdk 3.2.x binary downloaded
2. EXEC: Create CDK 3.2+ adapter with no profile set
3. EXEC: Prepare cdk: call setup-cdk on cli
4. ASSERT: calling 'minishift profile list' returns ''
5. EXEC: Start CDK 3.2+ server adapter
6. ASSERT: Adapter is started, 'minishift profile list' returns '- minishift Running (active)'
7. EXEC: Add new CDK 3.2+ called test and set profile to ie. 'test'
8. EXEC: call 'minishift setup-cdk --profile test' -> this will set active profile to 'test'
9. ASSERT: 'minishift profile list' returns two profiles where profile 'test' is active
10. EXEC: Start CDK 3.2+ test server adapter
11. ASSERT: CDK 3.2+ test SA is started
12. ASSERT: 'minishift profile list' shows two running profiles and 'test' is active
13. EXEC: Stop CDK 3.2+ default server adapter (the one without profile set)
14. ASSERT: CDK 3.2+ adapter is stopped - FAIL
15. ASSERT: 'minishift profile list' shows that default 'minishift' profile is stopped - FAIL
Instead, active profile 'test' was stopped, because stop operation was not passed with --profile ProfileName flag, which should be in this case 'minishift' to stop proper adapter/profile.
> Using empty profile in CDK 3.2+ server adapter should work with cdk's default profile (minishift)
> -------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25170
> URL: https://issues.jboss.org/browse/JBIDE-25170
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.5.1.AM3
> Reporter: Ondrej Dockal
>
> I have two running CDK 3.2+ server adapters, and if I operate the one where profile is not defined (I would expect that it is set to default one aka 'minishift') it works with actually active profile.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 6 months
[JBoss JIRA] (JBIDE-25170) Using empty profile in CDK 3.2+ server adapter should work with cdk's default profile (minishift)
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25170?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-25170:
----------------------------------
Steps to Reproduce:
1. EXEC: Have cdk 3.2.x binary downloaded
2. EXEC: Create CDK 3.2+ adapter with no profile set
3. EXEC: Prepare cdk: call setup-cdk on cli
4. ASSERT: calling 'minishift profile list' returns ''
5. EXEC: Start CDK 3.2+ server adapter
6. ASSERT: Adapter is started, 'minishift profile list' returns '- minishift Running (active)'
7. EXEC: Add new CDK 3.2+ called test and set profile to ie. 'test'
8. EXEC: call 'minishift setup-cdk --profile test' -> this will set active profile to 'test'
9. ASSERT: 'minishift profile list' returns two profiles where profile 'test' is active
10. EXEC: Start CDK 3.2+ test server adapter
11. ASSERT: CDK 3.2+ test SA is started
12. ASSERT: 'minishift profile list' shows two running profiles and 'test' is active
13. EXEC: Stop CDK 3.2+ default server adapter (the one without profile set)
14. ASSERT: CDK 3.2+ adapter is stopped - FAIL
15. ASSERT: 'minishift profile list' shows that default 'minishift' profile is stopped - FAIL
Instead, active profile 'test' was stopped, because stop operation was not passed with --profile ProfileName flag, which should be in this case 'minishift' to stop proper adapter/profile.
> Using empty profile in CDK 3.2+ server adapter should work with cdk's default profile (minishift)
> -------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25170
> URL: https://issues.jboss.org/browse/JBIDE-25170
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.5.1.AM3
> Reporter: Ondrej Dockal
>
> I have two running CDK 3.2+ server adapters, and if I operate the one where profile is not defined (I would expect that it is set to default one aka 'minishift') it works with actually active profile.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 6 months