[JBoss JIRA] (JBIDE-21704) Server adaoter wizard: pod deployment path is not computed correctly if you switch connection
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21704?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21704:
-------------------------------------
Steps to Reproduce:
# ASSERT: make sure that you have 2 different connections with different projects and 2 different services: 1x node and 1x eap (which differ in deployment path)
!2-connections-and-services.png!
# EXEC: launch new OpenShift 3 server adapter wizard and pick 1st connection.
# EXEC: Pick the 1st service
# ASSERT: Pod deployment path is displayed correctly and differs from default /opt/app-root/src
# EXEC: get back to the connection page and pick your 2nd connection
# EXEC: Pick the 2st service
Result:
Pod deployment path is displayed incorrectly, it is diplaying the default which is /opt/app-root/src
was:
# ASSERT: make sure that you have 2 different connections with different projects and 2 different services: 1x node and 1x eap (which differ in deployment path)
{code}
connection1
|_project1
|_service1
connection2
|_project2
|_service2
{code}
# EXEC: launch new OpenShift 3 server adapter wizard and pick 1st connection.
# EXEC: Pick the 1st service
# ASSERT: Pod deployment path is displayed correctly and differs from default /opt/app-root/src
# EXEC: get back to the connection page and pick your 2nd connection
# EXEC: Pick the 2st service
Result:
Pod deployment path is displayed incorrectly, it is diplaying the default which is /opt/app-root/src
> Server adaoter wizard: pod deployment path is not computed correctly if you switch connection
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-21704
> URL: https://issues.jboss.org/browse/JBIDE-21704
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Andre Dietisheim
> Fix For: 4.3.1.CR1
>
> Attachments: 2-connections-and-services.png
>
>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21704) Server adaoter wizard: pod deployment path is not computed correctly if you switch connection
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21704?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21704:
-------------------------------------
Steps to Reproduce:
# ASSERT: make sure that you have 2 different connections with different projects and 2 different services: 1x node and 1x eap (which differ in deployment path)
{code}
connection1
|_project1
|_service1
connection2
|_project2
|_service2
{code}
# EXEC: launch new OpenShift 3 server adapter wizard and pick 1st connection.
# EXEC: Pick the 1st service
# ASSERT: Pod deployment path is displayed correctly and differs from default /opt/app-root/src
# EXEC: get back to the connection page and pick your 2nd connection
# EXEC: Pick the 2st service
Result:
Pod deployment path is displayed incorrectly, it is diplaying the default which is /opt/app-root/src
was:
# ASSERT: make sure that you have 2 different connections with different projects and 2 different services: 1x node and 1x eap (which differ in deployment path)
connection1
|_project1
|_service1
connection2
|_project2
|_service2
# EXEC: launch new OpenShift 3 server adapter wizard and pick 1st connection.
# EXEC: Pick the 1st service
# ASSERT: Pod deployment path is displayed correctly and differs from default /opt/app-root/src
# EXEC: get back to the connection page and pick your 2nd connection
# EXEC: Pick the 2st service
Result:
Pod deployment path is displayed incorrectly, it is diplaying the default which is /opt/app-root/src
> Server adaoter wizard: pod deployment path is not computed correctly if you switch connection
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-21704
> URL: https://issues.jboss.org/browse/JBIDE-21704
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Andre Dietisheim
>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBDS-3566) include AERI in JBDS
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3566?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-3566:
--------------------------------------
Priority: Blocker (was: Major)
> include AERI in JBDS
> --------------------
>
> Key: JBDS-3566
> URL: https://issues.jboss.org/browse/JBDS-3566
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: aeri, build, target-platform
> Affects Versions: 9.1.0.Beta1, 10.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 9.1.0.CR1, 10.0.0.Alpha1
>
> Attachments: error-prefs-jbds.png, error-prefs-jbt.png, error-reporting.png
>
>
> Include required bundles for AERI in JBDS. Details TBD.
> Maybe need these?
> {code}
> org.eclipse.epp.logging.aeri.feature_1.0.1.v20150913-0716
> org.eclipse.epp.logging.aeri.ide_1.0.1.v20150913-0657.jar
> org.eclipse.epp.logging.aeri.ui_1.0.1.v20150913-0716.jar
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBDS-3566) include AERI in JBDS
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3566?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-3566:
-------------------------------------------
This seem to still not be done. Cannot build usage plugin that uses "org.eclipse.epp.logging.aeri.core 1.100.0"
[~mickael_istria] [~nickboldt] any progress on this ? without this in TP we can't add aeri
> include AERI in JBDS
> --------------------
>
> Key: JBDS-3566
> URL: https://issues.jboss.org/browse/JBDS-3566
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: aeri, build, target-platform
> Affects Versions: 9.1.0.Beta1, 10.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 9.1.0.CR1, 10.0.0.Alpha1
>
> Attachments: error-prefs-jbds.png, error-prefs-jbt.png, error-reporting.png
>
>
> Include required bundles for AERI in JBDS. Details TBD.
> Maybe need these?
> {code}
> org.eclipse.epp.logging.aeri.feature_1.0.1.v20150913-0716
> org.eclipse.epp.logging.aeri.ide_1.0.1.v20150913-0657.jar
> org.eclipse.epp.logging.aeri.ui_1.0.1.v20150913-0716.jar
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month