April 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19724) Provide bundled JBT releases

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19724?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-19724: ---------------------------------- Assignee: Max Rydahl Andersen (was: Nick Boldt) > Provide bundled JBT releases > ---------------------------- > > Key: JBIDE-19724 > URL: https://issues.jboss.org/browse/JBIDE-19724 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: ehsavoie Hugonnet > Assignee: Max Rydahl Andersen > Fix For: 4.3.0.Beta1 > > > As a participant of the jbosstools-cat project whenever a testing release is done I have to install all of it by hand to have a clean instance to test on. > Could you provide such a bundle à la JBDS during the testing periods ? > http://lists.jboss.org/pipermail/jbosstools-cat/2015-April/000027.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19724) Provide bundled JBT releases

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19724?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19724: ------------------------------- Summary: Provide bundled JBT releases (was: Provide public version of alpha releases for testing JBT) > Provide bundled JBT releases > ---------------------------- > > Key: JBIDE-19724 > URL: https://issues.jboss.org/browse/JBIDE-19724 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: ehsavoie Hugonnet > Assignee: Nick Boldt > Fix For: 4.3.0.Beta1 > > > As a participant of the jbosstools-cat project whenever a testing release is done I have to install all of it by hand to have a clean instance to test on. > Could you provide such a bundle à la JBDS during the testing periods ? > http://lists.jboss.org/pipermail/jbosstools-cat/2015-April/000027.html -- 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 with Android SDK not configured results in errors - written to .log, but 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 with Android SDK not configured results in errors - written to .log, but not communicated to the user via the UI (was: 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) > EasyImport of MobileHybrid project with Android SDK not configured results in errors - written to .log, but 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] (JBDS-2044) .eclipseproduct file no longer refers to JBDS

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-2044?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-2044: ------------------------------------- This .eclipseproduct marker file supposed to mark 'main product' among many possibly installed. see wiki article ["FAQ What is an Eclipse product?" | https://wiki.eclipse.org/FAQ_What_is_an_Eclipse_product%3F]. At the same time if one of included in product features has reference to "org.eclipse.platform.feature.grop" this file is installed as "root file" and there is no way to replace its content. It can be done after installation, but that would be overwritten during update from product p2.repositry. The only way to get rid of it is to remove reference to org.eclipse.platform feature and replace it with org.eclipse.platform bundle. It would work, but m2e* features for some reason has reference to org.eclipse.platform feature and that drags in .eclipseproduct file in JBDS installation. So it looks like we cannot fix it right now, but it does no harm to us because the name for final file to store state use not only product id but also installation folder hash. > .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} > Latest code in equinox.runtime master branch is located http://git.eclipse.org/c/equinox/rt.equinox.framework.git/tree/bundles/or... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19732) Misleading error logged when a new hybrid mobile engine configured

by Len DiMaggio (JIRA)

Len DiMaggio created JBIDE-19732: ------------------------------------ Summary: Misleading error logged when a new hybrid mobile engine configured Key: JBIDE-19732 URL: https://issues.jboss.org/browse/JBIDE-19732 Project: Tools (JBoss Tools) Issue Type: Bug Components: aerogear-hybrid Affects Versions: 4.3.0.Alpha2 Reporter: Len DiMaggio Priority: Minor There's no functional impact, but the error message is confusing. When a new mobile hybrid engine is configured, this error is logged: !ENTRY org.eclipse.thym.android.core 2 0 2015-04-28 14:38:54.071 !MESSAGE Missing Android engine file /home/ldimaggi/.cordova/lib/android/cordova/3.7.1/framework/cordova-3.7.1.jar The file, however, is right where it belongs: ll /home/ldimaggi/.cordova/lib/android/cordova/3.7.1/framework/cordova-3.7.1.jar -rw-rw-r--. 1 ldimaggi ldimaggi 357355 Apr 28 14:38 /home/ldimaggi/.cordova/lib/android/cordova/3.7.1/framework/cordova-3.7.1.jar -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19724) Provide public version of alpha releases for testing JBT

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19724?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-19724 at 4/28/15 2:46 PM: ------------------------------------------------------------- I doubt there's a plan to create "JBoss Tools w/ Eclipse" bundled installers. And, currently, it's not possible to provide pre-release JBDS installers. But starting from Beta1 we WILL have JBDS 9 installers available on http://tools.jboss.org/downloads/overview.html as we did for JBDS 8.x. was (Author: nickboldt): Currently, it's not possible to provide pre-release JBDS installers. But starting from Beta1 we WILL have JBDS 9 installers available on http://tools.jboss.org/downloads/overview.html as we did for JBDS 8.x. > Provide public version of alpha releases for testing JBT > -------------------------------------------------------- > > Key: JBIDE-19724 > URL: https://issues.jboss.org/browse/JBIDE-19724 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: ehsavoie Hugonnet > Assignee: Nick Boldt > Fix For: 4.3.0.Beta1 > > > As a participant of the jbosstools-cat project whenever a testing release is done I have to install all of it by hand to have a clean instance to test on. > Could you provide such a bundle à la JBDS during the testing periods ? > http://lists.jboss.org/pipermail/jbosstools-cat/2015-April/000027.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19724) Provide public version of alpha releases for testing JBT

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19724?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19724: ------------------------------- Fix Version/s: 4.3.0.Beta1 > Provide public version of alpha releases for testing JBT > -------------------------------------------------------- > > Key: JBIDE-19724 > URL: https://issues.jboss.org/browse/JBIDE-19724 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: ehsavoie Hugonnet > Fix For: 4.3.0.Beta1 > > > As a participant of the jbosstools-cat project whenever a testing release is done I have to install all of it by hand to have a clean instance to test on. > Could you provide such a bundle à la JBDS during the testing periods ? > http://lists.jboss.org/pipermail/jbosstools-cat/2015-April/000027.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19724) Provide public version of alpha releases for testing JBT

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19724?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-19724: ---------------------------------- Assignee: Nick Boldt > Provide public version of alpha releases for testing JBT > -------------------------------------------------------- > > Key: JBIDE-19724 > URL: https://issues.jboss.org/browse/JBIDE-19724 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: ehsavoie Hugonnet > Assignee: Nick Boldt > Fix For: 4.3.0.Beta1 > > > As a participant of the jbosstools-cat project whenever a testing release is done I have to install all of it by hand to have a clean instance to test on. > Could you provide such a bundle à la JBDS during the testing periods ? > http://lists.jboss.org/pipermail/jbosstools-cat/2015-April/000027.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19724) Provide public version of alpha releases for testing JBT

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19724?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19724: ------------------------------------ Currently, it's not possible to provide pre-release JBDS installers. But starting from Beta1 we WILL have JBDS 9 installers available on http://tools.jboss.org/downloads/overview.html as we did for JBDS 8.x. > Provide public version of alpha releases for testing JBT > -------------------------------------------------------- > > Key: JBIDE-19724 > URL: https://issues.jboss.org/browse/JBIDE-19724 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: ehsavoie Hugonnet > Fix For: 4.3.0.Beta1 > > > As a participant of the jbosstools-cat project whenever a testing release is done I have to install all of it by hand to have a clean instance to test on. > Could you provide such a bundle à la JBDS during the testing periods ? > http://lists.jboss.org/pipermail/jbosstools-cat/2015-April/000027.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19729) Version Auditing

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19729?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19729: ------------------------------- Epic Colour: ghx-label-6 (was: ghx-label-4) > Version Auditing > ---------------- > > Key: JBIDE-19729 > URL: https://issues.jboss.org/browse/JBIDE-19729 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > > Epic to track issues related to auditing and quality control. > This may include tools & workflows to ensure we're not building the wrong stuff, including too much (or incompatible versions) in target platforms, forgetting to upversion components, 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