April 2015 - jbosstools-issues - Jboss List Archives

[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: -------------------------------------- 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: build > 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] (LOCUS-23) New version of Saxon-HE required in locus

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/LOCUS-23?page=com.atlassian.jira.plugin.s... ] Max Rydahl Andersen commented on LOCUS-23: ------------------------------------------ [~phantomjinx] to get into integration-stack you need to open bug for JBTIS (as always ;) and be specific about what versions needs this. I assume this is just for Mars based version thus this should be fairly easy to get in but that is [~pleacu] that manage JBTIS TP. btw. please do not publish stuff to locations like nightly/locus/provisional when you can just use a local generated one. By you doing this you triggered regen of http://download.jboss.org/jbosstools/updates/nightly/locus/ which now includes your experiment despite its not yet included. > New version of Saxon-HE required in locus > ----------------------------------------- > > Key: LOCUS-23 > URL: https://issues.jboss.org/browse/LOCUS-23 > Project: JBoss Tools Locus > Issue Type: Feature Request > Affects Versions: 1.1.0 > Reporter: Paul Richardson > Assignee: Mickael Istria > Fix For: 1.2.0 > > > The Teiid Server project has updated their dependencies, including increasing the Saxon-HE version to 9.1.5-6j. > Since Teiid Designer takes a cut of the Teiid Server's client, it is necessary to update the Saxon-HE dependency in the former in order to remain in sync. Designer gets it Saxon library from the Locus repository. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19721) look at fixing quickaccess resizing bug

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-19721: ------------------------------------------- Summary: look at fixing quickaccess resizing bug Key: JBIDE-19721 URL: https://issues.jboss.org/browse/JBIDE-19721 Project: Tools (JBoss Tools) Issue Type: Bug Components: upstream Reporter: Max Rydahl Andersen Assignee: Koen Aers See https://bugs.eclipse.org/bugs/show_bug.cgi?id=432688 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (LOCUS-23) New version of Saxon-HE required in locus

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/LOCUS-23?page=com.atlassian.jira.plugin.s... ] Paul Richardson commented on LOCUS-23: -------------------------------------- [~mickael_istria] Have tested the PR. * Built it in jenkins under the jbosstools-locus.site_branch-testing project (build #2) - successful * Build published to http://download.jboss.org/jbosstools/updates/nightly/locus/provisional - successful * Re-generated Teiid Designer's target locally against this new provisional build and validated - successful * Executed Designer build and tests - successful On that basic happy for it to be merged. Assuming it is merged, what is the turnaround going to be for seeing this in the integration-stack? > New version of Saxon-HE required in locus > ----------------------------------------- > > Key: LOCUS-23 > URL: https://issues.jboss.org/browse/LOCUS-23 > Project: JBoss Tools Locus > Issue Type: Feature Request > Affects Versions: 1.1.0 > Reporter: Paul Richardson > Assignee: Mickael Istria > Fix For: 1.2.0 > > > The Teiid Server project has updated their dependencies, including increasing the Saxon-HE version to 9.1.5-6j. > Since Teiid Designer takes a cut of the Teiid Server's client, it is necessary to update the Saxon-HE dependency in the former in order to remain in sync. Designer gets it Saxon library from the Locus repository. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2044) .eclipseproduct file no longer refers to JBDS

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2044?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-2044: ------------------------------------------- but because its used there it should be using our product id should it not ? > .eclipseproduct file no longer refers to JBDS > --------------------------------------------- > > Key: JBDS-2044 > URL: https://issues.jboss.org/browse/JBDS-2044 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 5.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Denis Golovin > Labels: discuss > Fix For: 8.x > > > Before, with the linux x64 installer (jbdevstudio-product-linux-gtk-x86_64-5.0.0.v201202271832M-H79-Beta1.jar) the .eclipseproduct file read: > {code} > name=JBoss Developer Studio > id=com.jboss.jbds.all > version=5.0.0.v201202271832M-H79-Beta1 > {code} > Now, with the universal installer (jbdevstudio-product-universal-5.0.0.v201202271832M-H79-Beta1.jar), it reads: > {code} > name=Eclipse Platform > id=org.eclipse.platform > version=3.7.0 > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19007) As a user, I want to retrieve the build hook URL for a build config so I can configure my git repo to trigger a build on commit

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19007?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19007: ------------------------------------------ [~jcantrill] [~mlabuda] wants to verify this jira and is wondering how to test this. Can you please provide steps so that he can reproduce and verify it? > As a user, I want to retrieve the build hook URL for a build config so I can configure my git repo to trigger a build on commit > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19007 > URL: https://issues.jboss.org/browse/JBIDE-19007 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.2.2.Final > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: explorer > Fix For: 4.3.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19007) As a user, I want to retrieve the build hook URL for a build config so I can configure my git repo to trigger a build on commit

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19007?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-19007 at 4/28/15 6:51 AM: ------------------------------------------------------------------- [~jcantrill]: [~mlabuda] wants to verify this jira and is wondering how to test this. Can you please provide steps so that he can reproduce and verify it? was (Author: adietish): [~jcantrill] [~mlabuda] wants to verify this jira and is wondering how to test this. Can you please provide steps so that he can reproduce and verify it? > As a user, I want to retrieve the build hook URL for a build config so I can configure my git repo to trigger a build on commit > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19007 > URL: https://issues.jboss.org/browse/JBIDE-19007 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.2.2.Final > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: explorer > Fix For: 4.3.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19190) migrate VersionWatch to jbosstools-* repo

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19190?page=com.atlassian.jira.plugi... ] Jiri Peterka commented on JBIDE-19190: -------------------------------------- PRs are applied. Cleanup is finished IMHO. > migrate VersionWatch to jbosstools-* repo > ----------------------------------------- > > Key: JBIDE-19190 > URL: https://issues.jboss.org/browse/JBIDE-19190 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: qa > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Jiri Peterka > Priority: Minor > Fix For: 4.3.0.Beta1 > > > 0. decide where to put this... under jbosstools-ci or some new repo? Create a new component in JIRA accordingly. > 1. remove all refs to QA Jenkins file paths to make this more generic > 2. migrate those internal file paths into jenkins config.xml files > 3. document how to do installs for Eclipse, JBT or JBDS BYOE via commandline for setting up the footprint of installs against which to do baseline version watches -- pre-existing doc here: > http://download.jboss.org/jbosstools/updates/scripted-installation/ > https://devstudio.redhat.com/download/scripted-install/ > 4. test #3 to ensure it works, and that a mix of "studio" and "eclipse" folders can be used in a vwatch report -- 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 Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19719?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19719: --------------------------------------------- The relevant errors are this: {code} !ENTRY org.eclipse.thym.ui 2 0 2015-04-27 14:16:05.461 !MESSAGE Pre-compilation for engine cordova-android 3.6.4 has failed !STACK 1 org.eclipse.core.runtime.CoreException: Android SDK location is not defined at org.eclipse.thym.android.core.adt.AndroidSDKManager.getManager(AndroidSDKManager.java:263) at org.eclipse.thym.android.core.adt.AndroidProjectUtils.selectBestValidTarget(AndroidProjectUtils.java:69) at org.eclipse.thym.android.core.adt.AndroidLibraryResolver.preCompile(AndroidLibraryResolver.java:101) at org.eclipse.thym.core.engine.HybridMobileEngine.preCompile(HybridMobileEngine.java:102) at org.eclipse.thym.ui.internal.engine.AvailableCordovaEnginesSection$6.run(AvailableCordovaEnginesSection.java:400) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) !SUBENTRY 1 org.eclipse.thym.android.core 4 200 2015-04-27 14:16:05.461 !MESSAGE Android SDK location is not defined !ENTRY org.tigris.subversion.subclipse.core 4 0 2015-04-27 14:16:34.335 !MESSAGE Could not auto-share project SimpleHybridProject !STACK 1 org.tigris.subversion.subclipse.core.SVNException: Provided SVN information does not match that on disk for project 'SimpleHybridProject'. at org.tigris.subversion.subclipse.core.resources.SVNWorkspaceRoot.setSharing(SVNWorkspaceRoot.java:206) at org.tigris.subversion.subclipse.core.SVNTeamProviderType$AutoShareJob.autoconnectSVNProject(SVNTeamProviderType.java:140) at org.tigris.subversion.subclipse.core.SVNTeamProviderType$AutoShareJob.run(SVNTeamProviderType.java:106) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) !SUBENTRY 1 org.tigris.subversion.subclipse.core 4 4 2015-04-27 14:16:34.335 !MESSAGE Provided SVN information does not match that on disk for project 'SimpleHybridProject'. {code} I agree that aerogear should not be logging errors just because default SDK is not set - that should be a warning on the project, not a error in the logs (but I believe that is a separate issue) But what I do not get is why svn is triggered for you [~ldimaggio] can you proivde the exact steps you did to do this easyimport ? > "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: build > 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-19716) JBoss Tools 4.3.0.Alpha2 does not recognize an installed Android SDK

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19716?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-19716: -------------------------------- Attachment: sdk_change.png Directory structure has changed drastically. I guess that's the issue - !sdk_change.png|thumbnail! > 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

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