[JBoss JIRA] (JBIDE-22478) For JBIDE 4.4.0.Final: Prepare for Final/GA [Aerogear]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22478?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-22478:
--------------------------------------
Assignee: Gorkem Ercan
> For JBIDE 4.4.0.Final: Prepare for Final/GA [Aerogear]
> ------------------------------------------------------
>
> Key: JBIDE-22478
> URL: https://issues.jboss.org/browse/JBIDE-22478
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: aerogear-hybrid, cordovasim
> Reporter: Nick Boldt
> Assignee: Gorkem Ercan
> Priority: Blocker
> Labels: task
> Fix For: 4.4.0.Final
>
>
> For JBIDE 4.4.0.Final [Aerogear]: Please perform the following tasks:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.0.Final or 10.0.0.GA
> [Unresolved JIRAs with fixVersion = 4.4.0.Final, 10.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...]
> 1. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.0.Final-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.4.0.Final-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:orange}4.4.0.Final-SNAPSHOT{color}* in your *{color:orange}jbosstools-4.4.x{color}* branch
> 2. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.x{color}* branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.4.x
> git push origin jbosstools-4.4.x
> {code}
> Now, your root pom will use parent pom version:
> * *{color:orange}4.4.0.Final-SNAPSHOT{color}* in your *{color:blue}master{color}* branch (we'll move to 4.5.0.Alpha1 later!)
> * *{color:blue}4.4.0.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.x{color}* branch
> 3. Ensure you've *built your code* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0)
> {code}
> mvn clean verify -Dtpc.version=4.60.0.Final-SNAPSHOT
> {code}
> 4. Close (do not resolve) this JIRA when done.
> 5. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Aerogear task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22497) Import wizard: if launched from existing application, all projects are imported, not the context-dir only
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22497?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22497:
-------------------------------------
Steps to Reproduce:
# ASSERT: make sure that you have an existing service running in OpenShift (ex. eap-app, created via the eap template)
# EXEC: in OpenShift explorer: pick "Import Application" in the context menu of your service
# ASSERT: the import wizard pops up populated with sensible defaults
# EXEC: hit "Finish" in the import wizard
Result:
you get all the projects within jboss-eap-quickstarts imported to your workspace, not just the kitchensink project which the CONTEXT_DIR template parameter is pointing to.
Expected result:
The import wizard only imports the "kitchensink" project to your workspace.
If you create a new application by using the eap64-basic-s2i template, the import wizard is launched after the resources were created in OpenShift and it will (clone the whole git repository with the jboss-eap-quickstarts from //github.com/jboss-developer/jboss-eap-quickstarts but) will import only the "kitchensink" project to your workspace.
If you look at the build config for your service you'll find that the context directory is pointing to kitchensink, but is looks as if the import wizard was ignoring it:
{code}
"source" : {
"type" : "Git",
"git" : {
"uri" : "https://github.com/jboss-developer/jboss-eap-quickstarts",
"ref" : "7.0.x-develop"
},
"contextDir" : "kitchensink"
{code}
was:
# ASSERT: make sure that you have an existing service running in OpenShift (ex. eap-app, created via the eap template)
# EXEC: in OpenShift explorer: pick "Import Application" in the context menu of your service
# ASSERT: the import wizard pops up populated with sensible defaults
# EXEC: hit "Finish" in the import wizard
Result:
you get all the projects within jboss-eap-quickstarts imported to your workspace, not just the kitchensink project which the CONTEXT_DIR template parameter is pointing to.
Expected result:
The import wizard only imports the "kitchensink" project to your workspace.
If you create a new application by using the eap64-basic-s2i template, the import wizard is launched after the resources were created in OpenShift and it will (clone the whole git repository with the jboss-eap-quickstarts from //github.com/jboss-developer/jboss-eap-quickstarts but) will import only the "kitchensink" project to your workspace.
> Import wizard: if launched from existing application, all projects are imported, not the context-dir only
> ---------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22497
> URL: https://issues.jboss.org/browse/JBIDE-22497
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha2
> Reporter: Andre Dietisheim
> Labels: import_wizard, openshift_v3
> Fix For: 4.4.0.Final
>
>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months