December 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-21314) Cannot deploy mvn module of an existing git-based application to OpenShift 3 server

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-21314: ------------------------------------- Summary: Cannot deploy mvn module of an existing git-based application to OpenShift 3 server Key: JBIDE-21314 URL: https://issues.jboss.org/browse/JBIDE-21314 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.Beta1 Reporter: Marián Labuda Assignee: Fred Bricon Priority: Critical Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 If a git-based project it maven module and it has some parent (like eap quickstarts available at https://github.com/jboss-developer/jboss-eap-quickstarts) it is not possible to deploy such a project. There is an error in New OpenShift Application wizard telling that a project is not git project, although it is. There was similar issue with OpenShift 2 and with deploying projects which did not have .git folder in itself but it was in parent. See following screenshot: !application_wizard.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21314) Cannot deploy mvn module of an existing git-based application to OpenShift 3 server

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21314?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21314: ---------------------------------- Fix Version/s: (was: 4.4.0.Alpha1) > Cannot deploy mvn module of an existing git-based application to OpenShift 3 server > ----------------------------------------------------------------------------------- > > Key: JBIDE-21314 > URL: https://issues.jboss.org/browse/JBIDE-21314 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.3.1.Beta1 > > Attachments: application_wizard.png > > > If a git-based project it maven module and it has some parent (like eap quickstarts available at https://github.com/jboss-developer/jboss-eap-quickstarts) it is not possible to deploy such a project. There is an error in New OpenShift Application wizard telling that a project is not git project, although it is. There was similar issue with OpenShift 2 and with deploying projects which did not have .git folder in itself but it was in parent. See following screenshot: > !application_wizard.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21313) No web console URL for connection, project and resources

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21313?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21313: ---------------------------------- Priority: Major (was: Critical) > No web console URL for connection, project and resources > -------------------------------------------------------- > > Key: JBIDE-21313 > URL: https://issues.jboss.org/browse/JBIDE-21313 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Attachments: no_web_console_url.png > > > When trying to open OpenShift 3 connection, project or any resource in web console via context menu Show In - Web Console, there is following error: > !no_web_console_url.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21313) No web console URL for connection, project and resources

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-21313: ------------------------------------- Summary: No web console URL for connection, project and resources Key: JBIDE-21313 URL: https://issues.jboss.org/browse/JBIDE-21313 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.Beta1 Reporter: Marián Labuda Priority: Critical Attachments: no_web_console_url.png When trying to open OpenShift 3 connection, project or any resource in web console via context menu Show In - Web Console, there is following error: !no_web_console_url.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3575) Add Fedora 22 and 23 to the support matrix

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3575?page=com.atlassian.jira.plugin.... ] Martin Malina commented on JBDS-3575: ------------------------------------- It's a bit too late to do this in JBDS 9.1.0.Beta1 now. So we can target 9.1.0.Beta2. And also 10.0.0.Alpha1. I'm not sure if we need two separate JIRAs. > Add Fedora 22 and 23 to the support matrix > ------------------------------------------ > > Key: JBDS-3575 > URL: https://issues.jboss.org/browse/JBDS-3575 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements > Affects Versions: 9.1.0.Beta1 > Reporter: Martin Malina > Fix For: 9.1.0.Beta2, 10.0.0.Alpha1 > > > We should update the support matrix of JBDS to include the latest Fedora releases: 22 and 23. At the same time, 21 can be dropped. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3575) Add Fedora 22 and 23 to the support matrix

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3575?page=com.atlassian.jira.plugin.... ] Martin Malina updated JBDS-3575: -------------------------------- Fix Version/s: 10.0.0.Alpha1 > Add Fedora 22 and 23 to the support matrix > ------------------------------------------ > > Key: JBDS-3575 > URL: https://issues.jboss.org/browse/JBDS-3575 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements > Affects Versions: 9.1.0.Beta1 > Reporter: Martin Malina > Fix For: 9.1.0.Beta2, 10.0.0.Alpha1 > > > We should update the support matrix of JBDS to include the latest Fedora releases: 22 and 23. At the same time, 21 can be dropped. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3575) Add Fedora 22 and 23 to the support matrix

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3575?page=com.atlassian.jira.plugin.... ] Martin Malina updated JBDS-3575: -------------------------------- Fix Version/s: 9.1.0.Beta2 > Add Fedora 22 and 23 to the support matrix > ------------------------------------------ > > Key: JBDS-3575 > URL: https://issues.jboss.org/browse/JBDS-3575 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements > Affects Versions: 9.1.0.Beta1 > Reporter: Martin Malina > Fix For: 9.1.0.Beta2 > > > We should update the support matrix of JBDS to include the latest Fedora releases: 22 and 23. At the same time, 21 can be dropped. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3575) Add Fedora 22 and 23 to the support matrix

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3575?page=com.atlassian.jira.plugin.... ] Martin Malina updated JBDS-3575: -------------------------------- Affects: Documentation (Ref Guide, User Guide, etc.) > Add Fedora 22 and 23 to the support matrix > ------------------------------------------ > > Key: JBDS-3575 > URL: https://issues.jboss.org/browse/JBDS-3575 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements > Affects Versions: 9.1.0.Beta1 > Reporter: Martin Malina > Fix For: 9.1.0.Beta2 > > > We should update the support matrix of JBDS to include the latest Fedora releases: 22 and 23. At the same time, 21 can be dropped. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3575) Add Fedora 22 and 23 to the support matrix

by Martin Malina (JIRA)

Martin Malina created JBDS-3575: ----------------------------------- Summary: Add Fedora 22 and 23 to the support matrix Key: JBDS-3575 URL: https://issues.jboss.org/browse/JBDS-3575 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: requirements Affects Versions: 9.1.0.Beta1 Reporter: Martin Malina We should update the support matrix of JBDS to include the latest Fedora releases: 22 and 23. At the same time, 21 can be dropped. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21266) For JBIDE 4.3.1.Beta1: Code Freeze + Branch [Integration Tests]

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21266?page=com.atlassian.jira.plugi... ] Pavol Srna commented on JBIDE-21266: ------------------------------------ I've created jbosstools-4.3.1.Beta1x branch for integration-test repository. However I'll bump the parent pom version to Beta2 in 4.3.x branch after the beta1 release. Because now it is overhead for us, since we would need to update all of our jobs to use another branch, but the tests are the same. > For JBIDE 4.3.1.Beta1: Code Freeze + Branch [Integration Tests] > --------------------------------------------------------------- > > Key: JBIDE-21266 > URL: https://issues.jboss.org/browse/JBIDE-21266 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: qa > Reporter: Nick Boldt > Assignee: Pavol Srna > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [Integration Tests]: Please perform the following tasks: > 0. If nothing has changed in your component since the release of JBoss Tools 4.3.0.Final (eg., Portal, Freemarker?), *{color:red}Reject this JIRA{color}*. > Otherwise: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.Beta1 > [Unresolved JIRAs with fixVersion = 4.3.1.Beta1, 9.1.0.Beta1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...] > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.3.1, 1.2.3 to 1.2.100, or 2.3.100 to 2.3.101 > *NOTE:* If you already did this earlier when we were preparing for Beta1 (after 4.3.0.Final was released), you do *not* need to do so again. > Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.3.x branch. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.24.0:set-version -DnewVersion=4.3.1-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.3.1.Beta1-SNAPSHOT. > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.1.Beta1-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.2.Beta1 (or 4.50.2.Beta1-SNAPSHOT). > {code} > mvn clean verify -Dtpc.version=4.50.2.Beta1-SNAPSHOT # (if the TP is still a SNAPSHOT) > or > mvn clean verify -Dtpc.version=4.50.2.Beta1 # (if the TP is already released) > {code} > 4. Branch from your existing jbosstools-4.3.x branch into a new *{color:blue}jbosstools-4.3.1.Beta1x{color}* branch; > {code} > git checkout jbosstools-4.3.x > git pull origin jbosstools-4.3.x > git checkout -b jbosstools-4.3.1.Beta1x > git push origin jbosstools-4.3.1.Beta1x > {code} > 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}jbosstools-4.3.x branch{color}*. > {code} > git checkout jbosstools-4.3.x > git pull origin jbosstools-4.3.x > {code} > 6. Update your *{color:orange}jbosstools-4.3.x branch{color}* parent pom to use the latest version, *{color:orange}4.3.1.Beta2-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.1.Beta2-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.1.Beta1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.1.Beta1x{color}* branch, and > * *{color:orange}4.3.1.Beta2-SNAPSHOT{color}* in your *{color:orange}jbosstools-4.3.x{color}* branch. > 7. Close (do not resolve) this JIRA when done. > 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] 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 Integration Tests 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)

10 years, 3 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 December 2015