March 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23823) Move forge.reddeer plugin from jbosstools-integration-tests to jbosstools-forge

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23823?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-23823: ------------------------------- Fix Version/s: 4.4.4.AM2 (was: 4.4.4.AM1) > Move forge.reddeer plugin from jbosstools-integration-tests to jbosstools-forge > ------------------------------------------------------------------------------- > > Key: JBIDE-23823 > URL: https://issues.jboss.org/browse/JBIDE-23823 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: forge, integration-tests > Affects Versions: 4.4.3.AM2 > Reporter: Pavol Srna > Assignee: Pavol Srna > Fix For: 4.4.4.AM2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23824) Move hibernate.reddeer + itests from jbosstools-integration-tests to jbosstools-hibernate

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23824?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-23824: ------------------------------- Fix Version/s: 4.4.4.AM2 (was: 4.4.4.AM1) > Move hibernate.reddeer + itests from jbosstools-integration-tests to jbosstools-hibernate > ----------------------------------------------------------------------------------------- > > Key: JBIDE-23824 > URL: https://issues.jboss.org/browse/JBIDE-23824 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate, integration-tests > Affects Versions: 4.4.3.AM2 > Reporter: Pavol Srna > Assignee: Pavol Srna > Fix For: 4.4.4.AM2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23826) Move {batch/cdi/seam}.reddeer plugins from jbosstools-integration-tests to jbosstools-javaee

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23826?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-23826: ------------------------------- Fix Version/s: 4.4.4.AM2 (was: 4.4.4.AM1) > Move {batch/cdi/seam}.reddeer plugins from jbosstools-integration-tests to jbosstools-javaee > -------------------------------------------------------------------------------------------- > > Key: JBIDE-23826 > URL: https://issues.jboss.org/browse/JBIDE-23826 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: batch, cdi, integration-tests > Reporter: Pavol Srna > Assignee: Pavol Srna > Fix For: 4.4.4.AM2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23829) Move browsersim.reddeer plugins from jbosstool-integration-tests to jbosstools-browsersim

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23829?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-23829: ------------------------------- Fix Version/s: 4.4.4.AM2 (was: 4.4.4.AM1) > Move browsersim.reddeer plugins from jbosstool-integration-tests to jbosstools-browsersim > ----------------------------------------------------------------------------------------- > > Key: JBIDE-23829 > URL: https://issues.jboss.org/browse/JBIDE-23829 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: browsersim, integration-tests > Reporter: Pavol Srna > Assignee: Pavol Srna > Fix For: 4.4.4.AM2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23830) Move cordovasim.reddeer aerogear.reddeer from jbosstools-integration-tests to jbosstools-aerogear

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23830?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-23830: ------------------------------- Fix Version/s: 4.4.4.AM2 (was: 4.4.4.AM1) > Move cordovasim.reddeer aerogear.reddeer from jbosstools-integration-tests to jbosstools-aerogear > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-23830 > URL: https://issues.jboss.org/browse/JBIDE-23830 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: aerogear-hybrid, cordovasim, integration-tests > Affects Versions: 4.4.3.AM2 > Reporter: Pavol Srna > Assignee: Pavol Srna > Fix For: 4.4.4.AM2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23831) Move arquillian.reddeer from jbosstools-integration-tests for jbosstools-arquillian

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23831?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-23831: ------------------------------- Fix Version/s: 4.4.4.AM2 (was: 4.4.4.AM1) > Move arquillian.reddeer from jbosstools-integration-tests for jbosstools-arquillian > ----------------------------------------------------------------------------------- > > Key: JBIDE-23831 > URL: https://issues.jboss.org/browse/JBIDE-23831 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: arquillian, integration-tests > Affects Versions: 4.4.3.AM2 > Reporter: Pavol Srna > Assignee: Pavol Srna > Fix For: 4.4.4.AM2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24048) Import application: would like to be able to provide context-dir and branch

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24048?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24048: ------------------------------------- Description: We're missing the ability to provide a context dir within a git repo when importing an application from OpenShift. The application wizard allows the user to set a context dir, which is used when importing right after the successfull creation. The (standalone) import is lacking this. steps to reproduce: # EXEC: launch openshift application wizard and pick "eap64-basic-s2i" # ASSERT: in the next page make sure there is "kitchensink" set to the CONTEXT_DIR template parameter !CONTEXT_DIR.png! # ASSERT: in the parameters, make sure that the SOURCE_REPOSITORY_REF is set to "6.4.x" # EXEC: finish the wizard and once the resources are created, simply confirm the import dialog that pops up # ASSERT: you get a "jboss-kitchensink" in your workspace. The import actually cloned the whole repo "jboss-eap-quickstarts" and imported the project within the "kitchensink" (the CONTEXT_DIR) folder as a workspace project !jboss-kitchensink.png! # EXEC: in OpenShift Explorer: kill your workspace project, select the "eap-app" service and choose "Import Application" in the context-menu. # EXEC: in the upcoming import wizard, check "reuse existing repository" and then hit "Finish" Result: You get a project "jboss-eap-quickstart". !jboss-eap-quickstarts.png! There was no way to provide a context dir. To get the kitchensink project you need to remove the jboss-eap-quickstart" project, checkout the correct branch and reimport "kitchensink" (kitchensink only exists in the 6.4.x branch, not in the 7.x branches) manually as an existing maven project. was: We're missing the ability to provide a context dir within a git repo when importing an application from OpenShift. The application wizard allows the user to set a context dir, which is used when importing right after the successfull creation. The (standalone) import is lacking this. steps to reproduce: # EXEC: launch openshift application wizard and pick "eap64-basic-s2i" # ASSERT: in the next page make sure there is "kitchensink" set to the CONTEXT_DIR template parameter !CONTEXT_DIR.png! # EXEC: finish the wizard and once the resources are created, simply confirm the import dialog that pops up # ASSERT: you get a "jboss-kitchensink" in your workspace. The import actually cloned the whole repo "jboss-eap-quickstarts" and imported the project within the "kitchensink" (the CONTEXT_DIR) folder as a workspace project !jboss-kitchensink.png! # EXEC: in OpenShift Explorer: kill your workspace project, select the "eap-app" service and choose "Import Application" in the context-menu. # EXEC: in the upcoming import wizard, check "reuse existing repository" and then hit "Finish" Result: You get a project "jboss-eap-quickstart". !jboss-eap-quickstarts.png! There was no way to provide a context dir. To get the kitchensink project you need to remove the jboss-eap-quickstart" project, checkout the correct branch and reimport "kitchensink" (kitchensink only exists in the 6.4.x branch, not in the 7.x branches) manually as an existing maven project. > Import application: would like to be able to provide context-dir and branch > --------------------------------------------------------------------------- > > Key: JBIDE-24048 > URL: https://issues.jboss.org/browse/JBIDE-24048 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.4.AM1 > Reporter: Andre Dietisheim > Attachments: CONTEXT_DIR.png, SOURCE_REPOSITORY_REF.png, jboss-eap-quickstarts.png, jboss-kitchensink.png > > > We're missing the ability to provide a context dir within a git repo when importing an application from OpenShift. The application wizard allows the user to set a context dir, which is used when importing right after the successfull creation. The (standalone) import is lacking this. > steps to reproduce: > # EXEC: launch openshift application wizard and pick "eap64-basic-s2i" > # ASSERT: in the next page make sure there is "kitchensink" set to the CONTEXT_DIR template parameter > !CONTEXT_DIR.png! > # ASSERT: in the parameters, make sure that the SOURCE_REPOSITORY_REF is set to "6.4.x" > # EXEC: finish the wizard and once the resources are created, simply confirm the import dialog that pops up > # ASSERT: you get a "jboss-kitchensink" in your workspace. The import actually cloned the whole repo "jboss-eap-quickstarts" and imported the project within the "kitchensink" (the CONTEXT_DIR) folder as a workspace project > !jboss-kitchensink.png! > # EXEC: in OpenShift Explorer: kill your workspace project, select the "eap-app" service and choose "Import Application" in the context-menu. > # EXEC: in the upcoming import wizard, check "reuse existing repository" and then hit "Finish" > Result: > You get a project "jboss-eap-quickstart". > !jboss-eap-quickstarts.png! > There was no way to provide a context dir. To get the kitchensink project you need to remove the jboss-eap-quickstart" project, checkout the correct branch and reimport "kitchensink" (kitchensink only exists in the 6.4.x branch, not in the 7.x branches) manually as an existing maven project. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24048) Import application: would like to be able to provide context-dir and branch

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24048?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24048: ------------------------------------- Attachment: SOURCE_REPOSITORY_REF.png > Import application: would like to be able to provide context-dir and branch > --------------------------------------------------------------------------- > > Key: JBIDE-24048 > URL: https://issues.jboss.org/browse/JBIDE-24048 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.4.AM1 > Reporter: Andre Dietisheim > Attachments: CONTEXT_DIR.png, SOURCE_REPOSITORY_REF.png, jboss-eap-quickstarts.png, jboss-kitchensink.png > > > We're missing the ability to provide a context dir within a git repo when importing an application from OpenShift. The application wizard allows the user to set a context dir, which is used when importing right after the successfull creation. The (standalone) import is lacking this. > steps to reproduce: > # EXEC: launch openshift application wizard and pick "eap64-basic-s2i" > # ASSERT: in the next page make sure there is "kitchensink" set to the CONTEXT_DIR template parameter > !CONTEXT_DIR.png! > # ASSERT: in the parameters, make sure that the SOURCE_REPOSITORY_REF is set to "6.4.x" > # EXEC: finish the wizard and once the resources are created, simply confirm the import dialog that pops up > # ASSERT: you get a "jboss-kitchensink" in your workspace. The import actually cloned the whole repo "jboss-eap-quickstarts" and imported the project within the "kitchensink" (the CONTEXT_DIR) folder as a workspace project > !jboss-kitchensink.png! > # EXEC: in OpenShift Explorer: kill your workspace project, select the "eap-app" service and choose "Import Application" in the context-menu. > # EXEC: in the upcoming import wizard, check "reuse existing repository" and then hit "Finish" > Result: > You get a project "jboss-eap-quickstart". > !jboss-eap-quickstarts.png! > There was no way to provide a context dir. To get the kitchensink project you need to remove the jboss-eap-quickstart" project, checkout the correct branch and reimport "kitchensink" (kitchensink only exists in the 6.4.x branch, not in the 7.x branches) manually as an existing maven project. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24048) Import application: would like to be able to provide context-dir and branch

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24048?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24048: ------------------------------------- Description: We're missing the ability to provide a context dir within a git repo when importing an application from OpenShift. The application wizard allows the user to set a context dir, which is used when importing right after the successfull creation. The (standalone) import is lacking this. steps to reproduce: # EXEC: launch openshift application wizard and pick "eap64-basic-s2i" # ASSERT: in the next page make sure there is "kitchensink" set to the CONTEXT_DIR template parameter !CONTEXT_DIR.png! # ASSERT: in the parameters, make sure that the SOURCE_REPOSITORY_REF is set to "6.4.x" !SOURCE_REPOSITORY_REF.png! # EXEC: finish the wizard and once the resources are created, simply confirm the import dialog that pops up # ASSERT: you get a "jboss-kitchensink" in your workspace. The import actually cloned the whole repo "jboss-eap-quickstarts" and imported the project within the "kitchensink" (the CONTEXT_DIR) folder as a workspace project !jboss-kitchensink.png! # EXEC: in OpenShift Explorer: kill your workspace project, select the "eap-app" service and choose "Import Application" in the context-menu. # EXEC: in the upcoming import wizard, check "reuse existing repository" and then hit "Finish" Result: You get a project "jboss-eap-quickstart". !jboss-eap-quickstarts.png! There was no way to provide a context dir. To get the kitchensink project you need to remove the jboss-eap-quickstart" project, checkout the correct branch and reimport "kitchensink" (kitchensink only exists in the 6.4.x branch, not in the 7.x branches) manually as an existing maven project. was: We're missing the ability to provide a context dir within a git repo when importing an application from OpenShift. The application wizard allows the user to set a context dir, which is used when importing right after the successfull creation. The (standalone) import is lacking this. steps to reproduce: # EXEC: launch openshift application wizard and pick "eap64-basic-s2i" # ASSERT: in the next page make sure there is "kitchensink" set to the CONTEXT_DIR template parameter !CONTEXT_DIR.png! # ASSERT: in the parameters, make sure that the SOURCE_REPOSITORY_REF is set to "6.4.x" # EXEC: finish the wizard and once the resources are created, simply confirm the import dialog that pops up # ASSERT: you get a "jboss-kitchensink" in your workspace. The import actually cloned the whole repo "jboss-eap-quickstarts" and imported the project within the "kitchensink" (the CONTEXT_DIR) folder as a workspace project !jboss-kitchensink.png! # EXEC: in OpenShift Explorer: kill your workspace project, select the "eap-app" service and choose "Import Application" in the context-menu. # EXEC: in the upcoming import wizard, check "reuse existing repository" and then hit "Finish" Result: You get a project "jboss-eap-quickstart". !jboss-eap-quickstarts.png! There was no way to provide a context dir. To get the kitchensink project you need to remove the jboss-eap-quickstart" project, checkout the correct branch and reimport "kitchensink" (kitchensink only exists in the 6.4.x branch, not in the 7.x branches) manually as an existing maven project. > Import application: would like to be able to provide context-dir and branch > --------------------------------------------------------------------------- > > Key: JBIDE-24048 > URL: https://issues.jboss.org/browse/JBIDE-24048 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.4.AM1 > Reporter: Andre Dietisheim > Attachments: CONTEXT_DIR.png, SOURCE_REPOSITORY_REF.png, jboss-eap-quickstarts.png, jboss-kitchensink.png > > > We're missing the ability to provide a context dir within a git repo when importing an application from OpenShift. The application wizard allows the user to set a context dir, which is used when importing right after the successfull creation. The (standalone) import is lacking this. > steps to reproduce: > # EXEC: launch openshift application wizard and pick "eap64-basic-s2i" > # ASSERT: in the next page make sure there is "kitchensink" set to the CONTEXT_DIR template parameter > !CONTEXT_DIR.png! > # ASSERT: in the parameters, make sure that the SOURCE_REPOSITORY_REF is set to "6.4.x" > !SOURCE_REPOSITORY_REF.png! > # EXEC: finish the wizard and once the resources are created, simply confirm the import dialog that pops up > # ASSERT: you get a "jboss-kitchensink" in your workspace. The import actually cloned the whole repo "jboss-eap-quickstarts" and imported the project within the "kitchensink" (the CONTEXT_DIR) folder as a workspace project > !jboss-kitchensink.png! > # EXEC: in OpenShift Explorer: kill your workspace project, select the "eap-app" service and choose "Import Application" in the context-menu. > # EXEC: in the upcoming import wizard, check "reuse existing repository" and then hit "Finish" > Result: > You get a project "jboss-eap-quickstart". > !jboss-eap-quickstarts.png! > There was no way to provide a context dir. To get the kitchensink project you need to remove the jboss-eap-quickstart" project, checkout the correct branch and reimport "kitchensink" (kitchensink only exists in the 6.4.x branch, not in the 7.x branches) manually as an existing maven project. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24048) Import application: would like to be able to provide context-dir and branch

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24048?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24048: ------------------------------------- Summary: Import application: would like to be able to provide context-dir and branch (was: Import application: would like to be able to provide context-dir) > Import application: would like to be able to provide context-dir and branch > --------------------------------------------------------------------------- > > Key: JBIDE-24048 > URL: https://issues.jboss.org/browse/JBIDE-24048 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.4.AM1 > Reporter: Andre Dietisheim > Attachments: CONTEXT_DIR.png, jboss-eap-quickstarts.png, jboss-kitchensink.png > > > We're missing the ability to provide a context dir within a git repo when importing an application from OpenShift. The application wizard allows the user to set a context dir, which is used when importing right after the successfull creation. The (standalone) import is lacking this. > steps to reproduce: > # EXEC: launch openshift application wizard and pick "eap64-basic-s2i" > # ASSERT: in the next page make sure there is "kitchensink" set to the CONTEXT_DIR template parameter > !CONTEXT_DIR.png! > # EXEC: finish the wizard and once the resources are created, simply confirm the import dialog that pops up > # ASSERT: you get a "jboss-kitchensink" in your workspace. The import actually cloned the whole repo "jboss-eap-quickstarts" and imported the project within the "kitchensink" (the CONTEXT_DIR) folder as a workspace project > !jboss-kitchensink.png! > # EXEC: in OpenShift Explorer: kill your workspace project, select the "eap-app" service and choose "Import Application" in the context-menu. > # EXEC: in the upcoming import wizard, check "reuse existing repository" and then hit "Finish" > Result: > You get a project "jboss-eap-quickstart". > !jboss-eap-quickstarts.png! > There was no way to provide a context dir. To get the kitchensink project you need to remove the jboss-eap-quickstart" project, checkout the correct branch and reimport "kitchensink" (kitchensink only exists in the 6.4.x branch, not in the 7.x branches) manually as an existing maven project. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 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 March 2017