January 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21233) remove need for a targetplatforms/jbosstoolstarget/neon site

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21233?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-21233: --------------------------------------------- " we never removed the associate sites for JBT. We only removed it for JBDS. This JIRA is concerned with doing the same thing we did for JBDS now for JBT. That's why I'm surprised you're so concerned about making a change for JBT which we all agreed was a benefit to JBDS. " that is the missing part. I had assumed and still is that we would not make JBDS and jboss tools diverge like this. The bug talked about removing a url that seemed and still seems useful but it is actually more about remove associate site references which I'm 100% for and thought we did many months if not years ago. > remove need for a targetplatforms/jbosstoolstarget/neon site > ------------------------------------------------------------ > > Key: JBIDE-21233 > URL: https://issues.jboss.org/browse/JBIDE-21233 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha1 > > Attachments: jbt-creeping-update-sites.png > > > For the last few years, we've had an associate site ref inside the JBT agg site, pointing at "the latest maximum TP", eg., http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/mars/ > But since we now always co-release JBT with its TP in the same URL, this is only useful for someone who wants to do an OFFLINE install using the zip, which will then go ONLINE to resolve TP dependencies. It's at best a broken use case, and at worst it's unnecessary cruft to maintain. > Therefore I propose we stop linking to this site. > We can build the aggregates using a specific TP (the one in the parent pom, natch), and simply NOT use an associate site in the JBT aggregate site build. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21405) Add RedDeer 1.0.1 to target platform

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21405?page=com.atlassian.jira.plugi... ] Rastislav Wagner commented on JBIDE-21405: ------------------------------------------ {quote} Btw. if we add this into the JBT TP, will jbosstools-integration-tests be able to remove its custom inclusion of reddeer ? {quote} Yes, we will be able to remove reddeer update site from jbosstools-integration-tests > Add RedDeer 1.0.1 to target platform > ------------------------------------ > > Key: JBIDE-21405 > URL: https://issues.jboss.org/browse/JBIDE-21405 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.3.1.Beta2 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.3.1.Beta2 > > > We would like to add RedDeer 1.0.1 to target platform. > Note that we don't have 1.0.1 ready yet, it will be released soon (should be in time to make it to Beta2). Currently we have 1.0.0. But I'm creating this JIRA now to find out if anything is needed to be done for this to happen. > Github repo: https://github.com/jboss-reddeer/reddeer > Wiki: https://github.com/jboss-reddeer/reddeer/wiki > 1.0.0 repo: http://download.jboss.org/jbosstools/updates/stable/mars/core/reddeer/1.0.0/ > 1.0.1 repo: http://download.jboss.org/jbosstools/updates/stable/mars/core/reddeer/1.0.1/ (not available yet) > Feature: org.jboss.reddeer.eclipse.feature -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2444) JBDS 5.0.2 Core + 5.0.2 tooling is unable to recognize the 4.11.1 ESB in SOA-P 5.3.1.ER2 and later

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBDS-2444?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBDS-2444: ----------------------------------------------- Andrej Podhradsky <apodhrad(a)redhat.com> changed the Status of [bug 894120|https://bugzilla.redhat.com/show_bug.cgi?id=894120] from VERIFIED to CLOSED > JBDS 5.0.2 Core + 5.0.2 tooling is unable to recognize the 4.11.1 ESB in SOA-P 5.3.1.ER2 and later > -------------------------------------------------------------------------------------------------- > > Key: JBDS-2444 > URL: https://issues.jboss.org/browse/JBDS-2444 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: integration-platform > Affects Versions: 5.0.2.GA-SOA > Environment: Version: 5.0.2.GA > Build id: v20130103-0154-H238-GA > Build date: 20130103-0154 > http://www.qa.jboss.com/binaries/RHDS/updates/development/5.0.2.GA.soa-to... > SOA-P 5.3.1.ER2 and later > Reporter: Len DiMaggio > Assignee: Douglas Palmer > Priority: Blocker > Labels: respin-b > Fix For: 5.0.3.GA-SOA > > Attachments: Screenshot.png > > > The error raised is: > Error occurred while loading JBoss ESB 4.11.1 runtime . Please select a correct JBoss ESB runtime or JBoss ESB server location > See attached screenshot. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21405) Add RedDeer 1.0.1 to target platform

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21405?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-21405: --------------------------------------- I used RedDeer in the past but that was to run tests on the glorious JUnit patch that I was working on, so this was out of the JBoss Tools scope. And I should probably convert those tests to SWTBot to include them in the patch. And for now I'm also using SWTBot for the Docker tooling because it's for Eclipse.org. That being said, having RedDeer in the TP makes sense to test wizards and other views in our plugin, but I won't use it in the short term because I'm still working full-time on the Docker tooling. > Add RedDeer 1.0.1 to target platform > ------------------------------------ > > Key: JBIDE-21405 > URL: https://issues.jboss.org/browse/JBIDE-21405 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.3.1.Beta2 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.3.1.Beta2 > > > We would like to add RedDeer 1.0.1 to target platform. > Note that we don't have 1.0.1 ready yet, it will be released soon (should be in time to make it to Beta2). Currently we have 1.0.0. But I'm creating this JIRA now to find out if anything is needed to be done for this to happen. > Github repo: https://github.com/jboss-reddeer/reddeer > Wiki: https://github.com/jboss-reddeer/reddeer/wiki > 1.0.0 repo: http://download.jboss.org/jbosstools/updates/stable/mars/core/reddeer/1.0.0/ > 1.0.1 repo: http://download.jboss.org/jbosstools/updates/stable/mars/core/reddeer/1.0.1/ (not available yet) > Feature: org.jboss.reddeer.eclipse.feature -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21408) JBDS frozen and CPU at 100% after running overnight

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21408?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-21408: ---------------------------------- Attachment: frozen_jbds_jstack.txt Here's log from jstack: [^frozen_jbds_jstack.txt] Can somebody look and it and see if they can see something? :) > JBDS frozen and CPU at 100% after running overnight > --------------------------------------------------- > > Key: JBIDE-21408 > URL: https://issues.jboss.org/browse/JBIDE-21408 > Project: Tools (JBoss Tools) > Issue Type: Bug > Affects Versions: 4.3.1.Beta1 > Reporter: Martin Malina > Attachments: frozen_jbds_jstack.txt > > > Yesterday I kept JBDS 9.1.0.Beta1 running on my laptop (OS X) and I locked the laptop when I left the office. I couldn't find any Wake entries in the logs, so I think it did not sleep, but I'm not 100% sure. > Today when I unlocked my laptop, the JBDS icon jumped in the Dock, meaning there was some pop up or something, but from then, the app is frozen and takes 100% CPU. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21408) JBDS frozen and CPU at 100% after running overnight

by Martin Malina (JIRA)

Martin Malina created JBIDE-21408: ------------------------------------- Summary: JBDS frozen and CPU at 100% after running overnight Key: JBIDE-21408 URL: https://issues.jboss.org/browse/JBIDE-21408 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 4.3.1.Beta1 Reporter: Martin Malina Yesterday I kept JBDS 9.1.0.Beta1 running on my laptop (OS X) and I locked the laptop when I left the office. I couldn't find any Wake entries in the logs, so I think it did not sleep, but I'm not 100% sure. Today when I unlocked my laptop, the JBDS icon jumped in the Dock, meaning there was some pop up or something, but from then, the app is frozen and takes 100% CPU. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21405) Add RedDeer 1.0.1 to target platform

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21405?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-21405: --------------------------------------------- [~mmalina] before we add stuff to the TP and do the overhead of maintaining it would be good we actually get someone to say he will use it so we don't just add it and don't know if it actually works. I suggest you reach out to [~xcoulon] or similar to see if anyone interested/need it. Btw. if we add this into the JBT TP, will jbosstools-integration-tests be able to *remove* its custom inclusion of reddeer ? That would for me be a benefit of this - that we don't have to be using different mix of reddeer versions as was the situation in the past. Is that feasible ? > Add RedDeer 1.0.1 to target platform > ------------------------------------ > > Key: JBIDE-21405 > URL: https://issues.jboss.org/browse/JBIDE-21405 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.3.1.Beta2 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.3.1.Beta2 > > > We would like to add RedDeer 1.0.1 to target platform. > Note that we don't have 1.0.1 ready yet, it will be released soon (should be in time to make it to Beta2). Currently we have 1.0.0. But I'm creating this JIRA now to find out if anything is needed to be done for this to happen. > Github repo: https://github.com/jboss-reddeer/reddeer > Wiki: https://github.com/jboss-reddeer/reddeer/wiki > 1.0.0 repo: http://download.jboss.org/jbosstools/updates/stable/mars/core/reddeer/1.0.0/ > 1.0.1 repo: http://download.jboss.org/jbosstools/updates/stable/mars/core/reddeer/1.0.1/ (not available yet) > Feature: org.jboss.reddeer.eclipse.feature -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21405) Add RedDeer 1.0.1 to target platform

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21405?page=com.atlassian.jira.plugi... ] Martin Malina edited comment on JBIDE-21405 at 1/6/16 4:56 AM: --------------------------------------------------------------- [~nickboldt], the idea was that once RedDeer is stable enough to depend on (in the past we were depending on the nightly which was changing all the time), we could move it to TP so that it was part of the release train and past builds (including tests) are easily reproducible. Also, once it's in the TP, devs may start to use it if interested - e.g. Xavier was looking at using it in the past but Max discouraged him from that because it was not stable enough and not in the TP. [~maxandersen], do you want to comment? And yes, we have the RedDeer repo set up in our root pom right now, but we can remove the repo definition once it's no longer needed. was (Author: mmalina): [~nickboldt], the idea was that once RedDeer is stable enough to depend on (in the past we were depending on the nightly which was changing all the time), we could move it to TP so that it was part of the release train and past builds (including tests) are easily reproducible. Also, once it's in the TP, devs may start to use it if interested - e.g. Xavier was looking at using it in the past but Max discouraged him from that because it was not stable enough and not in the TP. [~maxandersen], do you want to comment? > Add RedDeer 1.0.1 to target platform > ------------------------------------ > > Key: JBIDE-21405 > URL: https://issues.jboss.org/browse/JBIDE-21405 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.3.1.Beta2 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.3.1.Beta2 > > > We would like to add RedDeer 1.0.1 to target platform. > Note that we don't have 1.0.1 ready yet, it will be released soon (should be in time to make it to Beta2). Currently we have 1.0.0. But I'm creating this JIRA now to find out if anything is needed to be done for this to happen. > Github repo: https://github.com/jboss-reddeer/reddeer > Wiki: https://github.com/jboss-reddeer/reddeer/wiki > 1.0.0 repo: http://download.jboss.org/jbosstools/updates/stable/mars/core/reddeer/1.0.0/ > 1.0.1 repo: http://download.jboss.org/jbosstools/updates/stable/mars/core/reddeer/1.0.1/ (not available yet) > Feature: org.jboss.reddeer.eclipse.feature -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21405) Add RedDeer 1.0.1 to target platform

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21405?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-21405: --------------------------------------- [~nickboldt], the idea was that once RedDeer is stable enough to depend on (in the past we were depending on the nightly which was changing all the time), we could move it to TP so that it was part of the release train and past builds (including tests) are easily reproducible. Also, once it's in the TP, devs may start to use it if interested - e.g. Xavier was looking at using it in the past but Max discouraged him from that because it was not stable enough and not in the TP. [~maxandersen], do you want to comment? > Add RedDeer 1.0.1 to target platform > ------------------------------------ > > Key: JBIDE-21405 > URL: https://issues.jboss.org/browse/JBIDE-21405 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.3.1.Beta2 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.3.1.Beta2 > > > We would like to add RedDeer 1.0.1 to target platform. > Note that we don't have 1.0.1 ready yet, it will be released soon (should be in time to make it to Beta2). Currently we have 1.0.0. But I'm creating this JIRA now to find out if anything is needed to be done for this to happen. > Github repo: https://github.com/jboss-reddeer/reddeer > Wiki: https://github.com/jboss-reddeer/reddeer/wiki > 1.0.0 repo: http://download.jboss.org/jbosstools/updates/stable/mars/core/reddeer/1.0.0/ > 1.0.1 repo: http://download.jboss.org/jbosstools/updates/stable/mars/core/reddeer/1.0.1/ (not available yet) > Feature: org.jboss.reddeer.eclipse.feature -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21392) Composite install job is disabled and also component jobs are disabled therefore there is no nightly build

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21392?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-21392: --------------------------------------------- "Though you can also EDIT job configs yourself, my script makes it way less painful and time-consuming" - you are forgetting the biggest one: Error prone. If we started/kept to encourage and pushing for each individual to enable these jobs and hand edit whatever flags it needs we would eventually end up with some done right, some done wrong, some not changed....a much worse situation to be in. Generating task jira is a nice stop gap but really would be nicer if we could automate this more since it keeps happening (mainly because it is not automated imo). Anyway that is a long standing issue we keep battling. a repeated topic for upcoming f2f. > Composite install job is disabled and also component jobs are disabled therefore there is no nightly build > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21392 > URL: https://issues.jboss.org/browse/JBIDE-21392 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.3.1.Beta2 > > > Job https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite... is marked as disabled and also component jobs such as http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-openshift_... and others are disabled. There was no build since 2015-12-16. Maybe it was disabled as a consequence/side effect of JBIDE-21145. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 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 January 2016