February 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-19377) JBDS update site build sometimes fails with a dirty Jenkins workspace

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19377?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-19377: ---------------------------------- Assignee: Nick Boldt Fix Version/s: 4.2.3.Beta1 4.3.0.Alpha2 Resolution: Done Builds are blue, giggity-goo. > JBDS update site build sometimes fails with a dirty Jenkins workspace > --------------------------------------------------------------------- > > Key: JBIDE-19377 > URL: https://issues.jboss.org/browse/JBIDE-19377 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.2.3.Beta1, 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.2.3.Beta1, 4.3.0.Alpha2 > > > {code} > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.3:run (install) on project com.jboss.devstudio.core.site: An Ant BuildException has occured: The following error occurred while executing this line: > [ERROR] /mnt/hudson_workspace/workspace/devstudio.product_8.0.luna/sources/product/site/build.xml:113: /mnt/hudson_workspace/workspace/devstudio.product_8.0.luna/results/target not found. > [ERROR] -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.3:run (install) on project com.jboss.devstudio.core.site: An Ant BuildException has occured: The following error occurred while executing this line: > /mnt/hudson_workspace/workspace/devstudio.product_8.0.luna/sources/product/site/build.xml:113: /mnt/hudson_workspace/workspace/devstudio.product_8.0.luna/results/target not found. > {code} -- https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > Caused by this: > https://github.com/jbdevstudio/jbdevstudio-product/blob/master/site/build... > So... working on a fix in 4.2.x and master now which defines a better default path. > {code} <property name="output.dir" value="${basedir}"/> > {code} > Building locally to verify. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3364) Include JBT sources in JBDS source zip

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3364?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3364: ---------------------------------- First fresh bits: http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_ma... http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_8.... (BTW, I realized this used to work in JBDS 6, too, but broke when we refactored the old "grab some zips" into "grab sources from github SHAs", but no one noticed the downstream impact until now. If anyone can suggest a good test to avoid missing this rather important detail in future, that we can implement as a maven enforcer rule, I'm happy to codify that.) > Include JBT sources in JBDS source zip > -------------------------------------- > > Key: JBDS-3364 > URL: https://issues.jboss.org/browse/JBDS-3364 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 8.0.2.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 8.1.0.Beta1, 9.0.0.Alpha2 > > > 1. Include the contents of the JBT source zip inside the JBDS one so all the sources for everything in JBDS (except third party stuff) can be seen in a single artifact. > 2. Ensure that the release guide has a step for pushing this zip to the FTP site, even for service releases. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3364) Include JBT sources in JBDS source zip

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3364?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3364: ----------------------------- Fix Version/s: 8.1.0.Beta1 9.0.0.Alpha2 > Include JBT sources in JBDS source zip > -------------------------------------- > > Key: JBDS-3364 > URL: https://issues.jboss.org/browse/JBDS-3364 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 8.0.2.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 8.1.0.Beta1, 9.0.0.Alpha2 > > > 1. Include the contents of the JBT source zip inside the JBDS one so all the sources for everything in JBDS (except third party stuff) can be seen in a single artifact. > 2. Ensure that the release guide has a step for pushing this zip to the FTP site, even for service releases. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3363) Remove Portlet tooling from default JBDS installation

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3363?page=com.atlassian.jira.plugin.... ] Nick Boldt resolved JBDS-3363. ------------------------------ Resolution: Done PRs applied in master. Building: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... >=2787 https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... >=3375 > Remove Portlet tooling from default JBDS installation > ----------------------------------------------------- > > Key: JBDS-3363 > URL: https://issues.jboss.org/browse/JBDS-3363 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: central, installer, requirements > Affects Versions: 9.0.0.Alpha1 > Reporter: Fred Bricon > Assignee: Nick Boldt > Fix For: 9.0.0.Alpha2 > > > Portlet tools currently has a hard dependency on Seam, which kinda bothers us with JBDS-3286. > While severing this dependency is a WIP (JBIDE-19316), another question comes to mind : is portlet still necessary? > It doesn't seem like a technology we're trying to promote, tooling has been in maintenance mode for months if not years. Is it not time to [let it go|https://www.youtube.com/watch?v=moSFlvxnbgk&t=56s]? > > [~burrsutter], [~maxandersen], [~ldimaggio], [~akazakov], [~mmurray], [~snjeza] : WDYT? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3360) Align bits offered in JBoss Central with installed version of JBDS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3360?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3360: ----------------------------- Fix Version/s: 8.1.0.CR1 > Align bits offered in JBoss Central with installed version of JBDS > ------------------------------------------------------------------ > > Key: JBDS-3360 > URL: https://issues.jboss.org/browse/JBDS-3360 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: central, updatesite > Affects Versions: 8.0.2.GA > Reporter: Martin Malina > Fix For: 8.1.0.CR1 > > > The problem in JBDS-3359 shows a broader issue. > (That one is about issues when clicking on an example in Central in JBDS 8.0.0 when 8.0.2 has already been released and central points to it.) > Currently when you install JBDS 8.0.0, it will contain this update site in Preferences -> Available Software Sites: > https://devstudio.redhat.com/updates/8.0/ > Initially this update site contained JBDS 8.0.0 core + 8.0.0 central. > But once we released JBDS 8.0.1, the update site was updated with 8.0.1 and this update was offered to users in Eclipse. And we started to have two groups of users: > 1. Those who stayed on JBDS 8.0.0, but their Central already pointed to 8.0.1 bits > 2. Those who update to JBDS 8.0.1 (and their Central also pointed to 8.0.1 bits) > Wouldn't it make more sense if central used the same version that is currently installed? I.e. if a user stays with JBDS 8.0.0, the bits offered in Central are 8.0.0 also. > I'm not sure if this is doable or makes sense at all, so I'm looking forward to feedback :) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-396) JBoss Central doesn't recognise that a category item is already installed

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-396?page=com.atlassian.jira.plugin.... ] Paul Leacu reassigned JBTIS-396: -------------------------------- Assignee: Paul Leacu > JBoss Central doesn't recognise that a category item is already installed > ------------------------------------------------------------------------- > > Key: JBTIS-396 > URL: https://issues.jboss.org/browse/JBTIS-396 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Reporter: Michelle Murray > Assignee: Paul Leacu > > I have JBDS 8.0.2 installed. > In JBoss Central Software/Update tab, I enabled Early Access. I then selected the check box for 'JBoss Data Virtualization Developer' and clicked installed. I chose to only install ModeShape Client and followed the install through including restarting JBDS. > In JBoss Central Software/Update tab, 'JBoss Data Virtualization Developer' was still shown as uninstalled - as expected from JBTIS-363. I selected the check box for 'JBoss Data Virtualization Developer' and clicked installed. ModeShape Client is listed and check box autoselected along with all of the Teiid items as available to install. BUT I just installed it!? > 1) I chose to only install the ModeShape Client again but then get an error message "Cannot complete the request. See the error log for details." > 2) So I chose to install all, including ModeShape Client, and the install proceeds to the next window without the error message but is listing that it will install ModeShape Client again. > As a user, this looks like a bug to me. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3360) Align bits offered in JBoss Central with installed version of JBDS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3360?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3360: ---------------------------------- Having a mix of 8.0.0, 8.0.1, 8.0.2, 8.1.0, 8.1.x in the same site will impact performance (more metadata = slower to parse when looking for updates). But it would also allow us to empower users to rollback from 8.1 to 8.0, or to install an older version of Tern/Thym/AngularJS than what's in the latest JBDS 8.1 if they want something compatible w/ an older release. So... there are pros and cons here. Perhaps this question needs to be put to GSS (more support scenarios like "I was running 8.0, updated to 8.1, then rolled back and now I can't use AngularJS" [for example]) as well as QE (more testcase scenarios). OTOH, if there's no reason to upgrade, people won't. So we might end up with lots of duplicate GSS support questions around problems in Eclipse Luna R or SR1 which were fixed in SR2. If we encourage/force users to upgrade, they get a better JBDS, and the reports of problems in old versions SHOULD go away. I'm not adverse to the idea, I just want everyone to know what COULD be the consequence of doing so. :D > Align bits offered in JBoss Central with installed version of JBDS > ------------------------------------------------------------------ > > Key: JBDS-3360 > URL: https://issues.jboss.org/browse/JBDS-3360 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: central, updatesite > Affects Versions: 8.0.2.GA > Reporter: Martin Malina > > The problem in JBDS-3359 shows a broader issue. > (That one is about issues when clicking on an example in Central in JBDS 8.0.0 when 8.0.2 has already been released and central points to it.) > Currently when you install JBDS 8.0.0, it will contain this update site in Preferences -> Available Software Sites: > https://devstudio.redhat.com/updates/8.0/ > Initially this update site contained JBDS 8.0.0 core + 8.0.0 central. > But once we released JBDS 8.0.1, the update site was updated with 8.0.1 and this update was offered to users in Eclipse. And we started to have two groups of users: > 1. Those who stayed on JBDS 8.0.0, but their Central already pointed to 8.0.1 bits > 2. Those who update to JBDS 8.0.1 (and their Central also pointed to 8.0.1 bits) > Wouldn't it make more sense if central used the same version that is currently installed? I.e. if a user stays with JBDS 8.0.0, the bits offered in Central are 8.0.0 also. > I'm not sure if this is doable or makes sense at all, so I'm looking forward to feedback :) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-397) Missing source bundle for org.teiid.designer.webservice.lib

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-397?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-397: ---------------------------------- No source bundle for org.teiid.designer.webservice.lib in 4.2.0.Final as well. > Missing source bundle for org.teiid.designer.webservice.lib > ----------------------------------------------------------- > > Key: JBTIS-397 > URL: https://issues.jboss.org/browse/JBTIS-397 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 8.0.0.CR2 > Reporter: Andrej Podhradsky > Assignee: Barry LaFond > Priority: Minor > > Source bundle for org.teiid.designer.webservice.lib is missing in JBDS-IS 8.0.0.CR3. Notice that this bundle contains only two classes > * org/teiid/designer/webservice/lib/WebServiceLibPlugin.class > * org/teiid/designer/webservice/lib/WebServiceLibConstants.class > so I set the priority as minor. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-397) Missing source bundle for org.teiid.designer.webservice.lib

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-397?page=com.atlassian.jira.plugin.... ] Paul Leacu reassigned JBTIS-397: -------------------------------- Assignee: Barry LaFond > Missing source bundle for org.teiid.designer.webservice.lib > ----------------------------------------------------------- > > Key: JBTIS-397 > URL: https://issues.jboss.org/browse/JBTIS-397 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 8.0.0.CR2 > Reporter: Andrej Podhradsky > Assignee: Barry LaFond > Priority: Minor > > Source bundle for org.teiid.designer.webservice.lib is missing in JBDS-IS 8.0.0.CR3. Notice that this bundle contains only two classes > * org/teiid/designer/webservice/lib/WebServiceLibPlugin.class > * org/teiid/designer/webservice/lib/WebServiceLibConstants.class > so I set the priority as minor. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3301) include support for windows in Thym/mobile tooling

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3301?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3301: --------------------------------- Fix Version/s: 8.1.0.Beta1 (was: 8.1.0.GA) > include support for windows in Thym/mobile tooling > -------------------------------------------------- > > Key: JBDS-3301 > URL: https://issues.jboss.org/browse/JBDS-3301 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: aerogear-hybrid, requirements > Reporter: Max Rydahl Andersen > Assignee: Gorkem Ercan > Fix For: 8.1.0.Beta1 > > > Thym upstream has recently received Windows support. > Would be great to include it in update to JBDS. > Any objections ? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

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 February 2015