April 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19476) Add label validation

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19476?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-19476: --------------------------------------- [~adietish] rebased after your merge to jbide-19009 create from template > Add label validation > -------------------- > > Key: JBIDE-19476 > URL: https://issues.jboss.org/browse/JBIDE-19476 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Priority: Blocker > Fix For: 4.3.0.Beta1 > > > Add label key and value validations to the 'label' page in accordance of what is valid in Kubernetes. This should be part of the 'edit label' page that will be presented to a user -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-431) Designer requires a new luna IS-TP complete with new version of LOCUS

by Paul Richardson (JIRA)

Paul Richardson created JBTIS-431: ------------------------------------- Summary: Designer requires a new luna IS-TP complete with new version of LOCUS Key: JBTIS-431 URL: https://issues.jboss.org/browse/JBTIS-431 Project: JBoss Tools Integration Stack Issue Type: Enhancement Components: target-platform Affects Versions: 4.2.0.Final-TP Reporter: Paul Richardson https://issues.jboss.org/browse/LOCUS-23 defines a new requirement in locus that results in a new version of the locus update site. Once a new build is available, Teiid Designer will need this locus version integrated into a new LUNA build of the IS-TP. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (LOCUS-41) New release of 4.2.x required to include new version of LOCUS

by Paul Richardson (JIRA)

Paul Richardson created LOCUS-41: ------------------------------------ Summary: New release of 4.2.x required to include new version of LOCUS Key: LOCUS-41 URL: https://issues.jboss.org/browse/LOCUS-41 Project: JBoss Tools Locus Issue Type: Enhancement Reporter: Paul Richardson https://issues.jboss.org/browse/LOCUS-23 defines a new requirement in locus that results in a new version of the locus update site. Once a new build is necessary, Designer will need this locus version integrated into a new LUNA build of the IS TP. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19716) JBoss Tools 4.3.0.Alpha2 does not recognize an installed Android SDK

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19716?page=com.atlassian.jira.plugi... ] Len DiMaggio commented on JBIDE-19716: -------------------------------------- This JIRA is a user error as while the SDK was downloaded, its installation was not completed. We should at least add a note to the user docs to remind the user that he/she must complete the install of the SDK. > JBoss Tools 4.3.0.Alpha2 does not recognize an installed Android SDK > -------------------------------------------------------------------- > > Key: JBIDE-19716 > URL: https://issues.jboss.org/browse/JBIDE-19716 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Gorkem Ercan > Attachments: Android_SDK.png, sdk_change.png > > > With 4.3.0.Alpha2: > * Install Android SDK from: http://dl.google.com/android/android-sdk_r24.1.2-linux.tgz > * Attempt to configure the installed SDK in Perferences->Hybrid Mobile->Android > * See the attached screen shot for the "Not a valid Android SDK directory" error. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19719) EasyImport of MobileHybrid project results in errors - lack of configured Andriod SDK is written to .log, but it is not communicated to the user via the UI

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19719?page=com.atlassian.jira.plugi... ] Len DiMaggio commented on JBIDE-19719: -------------------------------------- The solution to this JIRA will be to communication this error directly to the user in a dialog during the project import - and give him/her an opportunity to configure an already installed SDK during the project creation: org.eclipse.core.runtime.CoreException: Android SDK location is not defined > EasyImport of MobileHybrid project results in errors - lack of configured Andriod SDK is written to .log, but it is not communicated to the user via the UI > ----------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19719 > URL: https://issues.jboss.org/browse/JBIDE-19719 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-platform > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Gorkem Ercan > Attachments: jbosstools-diagnostics-20150427143128.zip, jbosstools-diagnostics-20150428105107.zip > > > This issue is related to JBIDE-19716 > Multiple errors are raised when a mobile hybrid project created in Central in JBoss Tools 4.3.0.alpha2 is exported and then imported from a directory using easy import. > See attached .zip for the error file (logs, etc..) > The error message logged is: > eclipse.core.runtime.CoreException: Android SDK location is not defined -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19719) EasyImport of MobileHybrid project results in errors - lack of configured Andriod SDK is written to .log, but it is not communicated to the user via the UI

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19719?page=com.atlassian.jira.plugi... ] Len DiMaggio edited comment on JBIDE-19719 at 4/28/15 11:39 AM: ---------------------------------------------------------------- Sorry that the steps were not clear - the steps that must be performed to avoid the errors are: * Starting with a clean install of JBoss Tools 4.3.0.alpha2, and a new/empty workspace * From JBoss Central, create a new Mobile Hybrid project ("start from scratch") ** In the process of the project creation, download a cordova mobile engine * Configure an already installed Android SDK (I used android-sdk_r24.1.2-linux) ** If this^ step is not performed at this point, the project creation will complete with errors * Export the project to a directory outside of the workspace * Delete the project from the workspace * Attempt to import the project using the "import from directory" option was (Author: ldimaggio): Sorry that the steps were not clear - the steps are: * From JBoss Central, create a new Mobile Hybrid project ("start from scratch") * Configure an Android SDK (I used android-sdk_r24.1.2-linux) * Export the project to a directory outside of the workspace * Delete the project from the workspace * Attempt to import the project using the "import from directory" option > EasyImport of MobileHybrid project results in errors - lack of configured Andriod SDK is written to .log, but it is not communicated to the user via the UI > ----------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19719 > URL: https://issues.jboss.org/browse/JBIDE-19719 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-platform > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Gorkem Ercan > Attachments: jbosstools-diagnostics-20150427143128.zip, jbosstools-diagnostics-20150428105107.zip > > > This issue is related to JBIDE-19716 > Multiple errors are raised when a mobile hybrid project created in Central in JBoss Tools 4.3.0.alpha2 is exported and then imported from a directory using easy import. > See attached .zip for the error file (logs, etc..) > The error message logged is: > eclipse.core.runtime.CoreException: Android SDK location is not defined -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19719) EasyImport of MobileHybrid project results in errors - lack of configured Andriod SDK is written to .log, but it is not communicated to the user via the UI

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19719?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-19719: --------------------------------- Summary: EasyImport of MobileHybrid project results in errors - lack of configured Andriod SDK is written to .log, but it is not communicated to the user via the UI (was: "EasyImport" of Mobile Hybrid project fails on JBoss Tools 4.3.0.Alpha2) Description: This issue is related to JBIDE-19716 Multiple errors are raised when a mobile hybrid project created in Central in JBoss Tools 4.3.0.alpha2 is exported and then imported from a directory using easy import. See attached .zip for the error file (logs, etc..) The error message logged is: eclipse.core.runtime.CoreException: Android SDK location is not defined was: This issue is related to JBIDE-19716 Multiple errors are raised when a mobile hybrid project created in Central in JBoss Tools 4.3.0.alpha2 is exported and then imported from a directory using easy import. See attached .zip for the error file (logs, etc..) > EasyImport of MobileHybrid project results in errors - lack of configured Andriod SDK is written to .log, but it is not communicated to the user via the UI > ----------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19719 > URL: https://issues.jboss.org/browse/JBIDE-19719 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-platform > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Gorkem Ercan > Attachments: jbosstools-diagnostics-20150427143128.zip, jbosstools-diagnostics-20150428105107.zip > > > This issue is related to JBIDE-19716 > Multiple errors are raised when a mobile hybrid project created in Central in JBoss Tools 4.3.0.alpha2 is exported and then imported from a directory using easy import. > See attached .zip for the error file (logs, etc..) > The error message logged is: > eclipse.core.runtime.CoreException: Android SDK location is not defined -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19719) "EasyImport" of Mobile Hybrid project fails on JBoss Tools 4.3.0.Alpha2

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19719?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-19719: --------------------------------- Attachment: jbosstools-diagnostics-20150428105107.zip > "EasyImport" of Mobile Hybrid project fails on JBoss Tools 4.3.0.Alpha2 > ----------------------------------------------------------------------- > > Key: JBIDE-19719 > URL: https://issues.jboss.org/browse/JBIDE-19719 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-platform > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Gorkem Ercan > Attachments: jbosstools-diagnostics-20150427143128.zip, jbosstools-diagnostics-20150428105107.zip > > > This issue is related to JBIDE-19716 > Multiple errors are raised when a mobile hybrid project created in Central in JBoss Tools 4.3.0.alpha2 is exported and then imported from a directory using easy import. > See attached .zip for the error file (logs, etc..) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19719) "EasyImport" of Mobile Hybrid project fails on JBoss Tools 4.3.0.Alpha2

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19719?page=com.atlassian.jira.plugi... ] Len DiMaggio commented on JBIDE-19719: -------------------------------------- The svn issues that Max referred to will be addressed in a separate JIRA. The JBoss Tools configuration used had all of JBoss Tools installed. The report file: jbosstools-diagnostics-20150428105107.zip - just attached to this JIRA reflects a JBoss Tools configuration with only "JBoss Tools Abridged" installed. The svn errors are not included in the log in this report file. > "EasyImport" of Mobile Hybrid project fails on JBoss Tools 4.3.0.Alpha2 > ----------------------------------------------------------------------- > > Key: JBIDE-19719 > URL: https://issues.jboss.org/browse/JBIDE-19719 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-platform > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Gorkem Ercan > Attachments: jbosstools-diagnostics-20150427143128.zip > > > This issue is related to JBIDE-19716 > Multiple errors are raised when a mobile hybrid project created in Central in JBoss Tools 4.3.0.alpha2 is exported and then imported from a directory using easy import. > See attached .zip for the error file (logs, etc..) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19719) "EasyImport" of Mobile Hybrid project fails on JBoss Tools 4.3.0.Alpha2

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19719?page=com.atlassian.jira.plugi... ] Len DiMaggio edited comment on JBIDE-19719 at 4/28/15 11:10 AM: ---------------------------------------------------------------- Sorry that the steps were not clear - the steps are: * From JBoss Central, create a new Mobile Hybrid project ("start from scratch") * Configure an Android SDK (I used android-sdk_r24.1.2-linux) * Export the project to a directory outside of the workspace * Delete the project from the workspace * Attempt to import the project using the "import from directory" option was (Author: ldimaggio): Sorry that the steps were not clear - the steps are: * From JBoss Central, create a new Mobile Hybrid project ("start from scratch") * Export the project to a directory outside of the workspace * Attempt to import the project using the "import from directory" option > "EasyImport" of Mobile Hybrid project fails on JBoss Tools 4.3.0.Alpha2 > ----------------------------------------------------------------------- > > Key: JBIDE-19719 > URL: https://issues.jboss.org/browse/JBIDE-19719 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-platform > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Gorkem Ercan > Attachments: jbosstools-diagnostics-20150427143128.zip > > > This issue is related to JBIDE-19716 > Multiple errors are raised when a mobile hybrid project created in Central in JBoss Tools 4.3.0.alpha2 is exported and then imported from a directory using easy import. > See attached .zip for the error file (logs, etc..) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 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 April 2015