May 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-399) Cannot install JBDS-IS in offline mode

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-399?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-399: ------------------------------------ Summary: Cannot install JBDS-IS in offline mode (was: Cannot install JBDS-IS earlyaccess in offline mode) > Cannot install JBDS-IS in offline mode > -------------------------------------- > > Key: JBTIS-399 > URL: https://issues.jboss.org/browse/JBTIS-399 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 8.0.0.GA > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Critical > Fix For: 9.0.0.Alpha1 > > Attachments: error.txt, oi1.png, oi2.png, oi3.png > > > Cannot install JBDS-IS 8.0.0.GA early access in offline mode. Note that DV tooling (Teiid Designer and ModeShape) can be installed without any problem. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19737) Add template info page after template list in create from app flow

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19737?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19737: ------------------------------------------ thanks! merged and pushed to upstream/master > Add template info page after template list in create from app flow > ------------------------------------------------------------------ > > Key: JBIDE-19737 > URL: https://issues.jboss.org/browse/JBIDE-19737 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Fix For: 4.3.0.Beta1 > > > Add a template info page that identifies key aspects of a template that a user has choosen so they can ensure they want to continue -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3345) Errors when starting FSW 6.0.0.GA from JBDS 8.0.2.GA with JDK 1.8

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBDS-3345?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated JBDS-3345: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1215031 > Errors when starting FSW 6.0.0.GA from JBDS 8.0.2.GA with JDK 1.8 > ----------------------------------------------------------------- > > Key: JBDS-3345 > URL: https://issues.jboss.org/browse/JBDS-3345 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: server > Affects Versions: 8.0.2.GA > Environment: Fedora 21 x86_64 > JBDS 8.0.2.GA with Oracle JDK 1.8.0_25 and Oracle JDK 1.7.0_71 > Reporter: Andrej Podhradsky > Priority: Critical > Attachments: compiler.png, console.png, errors.txt, error_log.txt, installed_jre.png, run.sh, runtime_jre.png, server.log > > > FSW 6.0.0.GA supports java 6 and 7, so if we want to run this server on JBDS 8 with jdk 8 we need to add another jdk to the JBDS, e.g. jdk 7. But this doesn't work, see errors in the attached file. > Moreover, we are not able to stop the server from IDE, the process is still alive and we have to kill it manually. > Note that this happens only when we install JBDS 8.0.2 with jdk 8, if we install it with jdk 7 the server works fine. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3345) Errors when starting FSW 6.0.0.GA from JBDS 8.0.2.GA with JDK 1.8

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBDS-3345?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBDS-3345: ------------------------------------ Attachment: run.sh > Errors when starting FSW 6.0.0.GA from JBDS 8.0.2.GA with JDK 1.8 > ----------------------------------------------------------------- > > Key: JBDS-3345 > URL: https://issues.jboss.org/browse/JBDS-3345 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: server > Affects Versions: 8.0.2.GA > Environment: Fedora 21 x86_64 > JBDS 8.0.2.GA with Oracle JDK 1.8.0_25 and Oracle JDK 1.7.0_71 > Reporter: Andrej Podhradsky > Priority: Critical > Attachments: compiler.png, console.png, errors.txt, error_log.txt, installed_jre.png, run.sh, runtime_jre.png, server.log > > > FSW 6.0.0.GA supports java 6 and 7, so if we want to run this server on JBDS 8 with jdk 8 we need to add another jdk to the JBDS, e.g. jdk 7. But this doesn't work, see errors in the attached file. > Moreover, we are not able to stop the server from IDE, the process is still alive and we have to kill it manually. > Note that this happens only when we install JBDS 8.0.2 with jdk 8, if we install it with jdk 7 the server works fine. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3345) Errors when starting FSW 6.0.0.GA from JBDS 8.0.2.GA with JDK 1.8

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBDS-3345?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky commented on JBDS-3345: ----------------------------------------- [~rob.stryker] what configuration did you use during installing the FSW server? Now, I tried to install only "SwitchYard" + "RT-Gov Client-only" and it works as expected (I didn't get the error), so I assume that you used this configuration. But when I install FSW as "SwitchYard + "RT-Gov Server+Client" then I get the error. Nevertheless, the problem seems to be in the FSW server itself, I'm able to reproduce this issue using the attached {{run.sh}} script. > Errors when starting FSW 6.0.0.GA from JBDS 8.0.2.GA with JDK 1.8 > ----------------------------------------------------------------- > > Key: JBDS-3345 > URL: https://issues.jboss.org/browse/JBDS-3345 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: server > Affects Versions: 8.0.2.GA > Environment: Fedora 21 x86_64 > JBDS 8.0.2.GA with Oracle JDK 1.8.0_25 and Oracle JDK 1.7.0_71 > Reporter: Andrej Podhradsky > Priority: Critical > Attachments: compiler.png, console.png, errors.txt, error_log.txt, installed_jre.png, run.sh, runtime_jre.png, server.log > > > FSW 6.0.0.GA supports java 6 and 7, so if we want to run this server on JBDS 8 with jdk 8 we need to add another jdk to the JBDS, e.g. jdk 7. But this doesn't work, see errors in the attached file. > Moreover, we are not able to stop the server from IDE, the process is still alive and we have to kill it manually. > Note that this happens only when we install JBDS 8.0.2 with jdk 8, if we install it with jdk 7 the server works fine. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-641) How-to configure a remote server with JBDS 8.1

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-641?page=com.atlassian.jira.plug... ] Martin Malina reassigned TOOLSDOC-641: -------------------------------------- Assignee: Misha Ali (was: Martin Malina) Hi Misha, here are some comments: 4. b. For the Controlled by: field, click the Filesystem and shell operations radio button option. - why limit users to this? I understand that this article probably intentionally only describes how to use the filesystem mode and not the management operations mode. But in this case I suggest mentioning it in the article at the beginning of the document. c. Select the check box for the Server is externally managed. Assume server is started. field. - why? It is a relevant use case to use this, but why not instruct them to use the adapter fully (including server start/stop)? Again, if we only want to introduce this limited functionality, then I suggest we say that in the introduction. d. "A server runtime environment must be selected before you can successfully create a server adapter and complete the server definition." - this is not true. Server runtime is not required for remote servers. Especially if you're trying to create a server that is externally managed with file system operations, all you really need is a connection to the remote host and the deployment location on the remote host. I would probably suggest to instruct users to create the remote server without a runtime. 5. a. In the drop down menu, select the appropriate host in the Host field The default host is Local.. - when a user tries this for the first time, most likely they will need to create a new host definition, so we should at least say something like "You may need to create a new host." or better, we could walk them through that dialog also (or at least briefly explain what types of servers are supported). 5. b. b. Specify the remote server’s base directory (the default value for this is the standalone directory within server home directory) in the Remote Server Base Directory field. - it would be good to point out here that it's a path relative to the one above. So the default is simply "standalone" and not the whole path as reading this text may suggest (but the screenshot does a good job clearing this up). 5. b. d. Click Next > to continue or Finish to conclude the new remote server configuration. - this sounds a little confusing - continue how? later I could see that this refers to step 6., but at the time of reading this it wasn't clear. Perhaps just add something like: to continue (optional step 6 - see below)? 6. - I would switch a. and b. to first say how to add a resource - at first you won't have anything to remote. But that's a minor thing. Result: You have successfully configured a remote server. The new server is listed in the Servers tab. Right click the server to view operations, including Start to start the server. - here you suggest users use the Start operation, but if your server is "externally managed" - as you suggested in 4. c., then it has some implications - the Start operation will not actually start the server, but will just mark it as started and the web poller will check that the server is really running. But anyway, I recommend not instructing users to check that checkbox in 4. c. Feel free to ping me if you have any questions. > How-to configure a remote server with JBDS 8.1 > ---------------------------------------------- > > Key: TOOLSDOC-641 > URL: https://issues.jboss.org/browse/TOOLSDOC-641 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Sub-task > Components: General documentation issues > Affects Versions: 4.2.3.Final > Reporter: Misha Ali > Assignee: Misha Ali > Fix For: 4.2.3.Final > > > Requesting QE review for the following content: > https://docs.google.com/a/redhat.com/document/d/1sd5_RaThCjbRxeA4D-YcYjXL... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-433) MASTER build of Fuse tooling in JBDS-IS 8.0.2.ER1

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-433?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-433: ---------------------------------- I'll clean this up in the next Fuse Tooling jenkins build. > MASTER build of Fuse tooling in JBDS-IS 8.0.2.ER1 > ------------------------------------------------- > > Key: JBTIS-433 > URL: https://issues.jboss.org/browse/JBTIS-433 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 8.0.2.CR1 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > > Current build of JBDS-IS 8.0.2.ER1 contains MASTER build of Fuse tooling, namely 7.3.0.v20150428-1634-H488-MASTER. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3408) installer is trying to reach download.jboss.org for content

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3408?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-3408 at 5/5/15 9:23 AM: ---------------------------------------------------------- Proposed PR to use devstudio URL instead of jbosstools URL for stat tracker. Also replaces JOB_NAME with local for local builds (like we already do for jbosstools aggregate builds). https://github.com/jbdevstudio/jbdevstudio-product/pull/305 [~dgolovin] [~maxandersen] WDYT? was (Author: nickboldt): Proposed PR to use devstudio URL instead of jbosstools URL for stat tracker. Also replaces JOB_NAME with local for local builds (like we already do for jbosstools aggregate builds). https://github.com/jbdevstudio/jbdevstudio-product/pull/305 > installer is trying to reach download.jboss.org for content > ----------------------------------------------------------- > > Key: JBDS-3408 > URL: https://issues.jboss.org/browse/JBDS-3408 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 8.0.0.Alpha2 > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Critical > Fix For: 9.0.0.Beta1 > > Attachments: JBDS3408.install.jboss-devstudio-9.0.0.Beta1-v20150430-1113-B3095-installer-standalone.jar.log.txt > > > Running latest devstudio 9 installer I caught it in reaching out to download.jboss.org which it should have *zero* links/dependency on. > My guess is there is an updatesite that have bad reference to download.jboss.org that we need fixing. > See screenshot at https://www.dropbox.com/s/wkr30jlvdc7d8wu/Screenshot%202015-04-15%2013.11... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3408) installer is trying to reach download.jboss.org for content

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3408?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3408: ---------------------------------- 1. What URL should we ping for locally-built installers? As you can see above it's TRYING to use JOB_NAME but Denis' local build didn't set that value via -DJOB_NAME="whatever" so it left the unresolved variables in the URLs. For builds built in Jenkins this value DOES exist. 2. It should be relatively easy to replace "http://download.jboss.org/jbosstools/" with "https://devstudio.redhat.com" if you want to have JBDS ping that server instead of dl.jb. Previous discussions about p2 stats collection: * JBIDE-12432 Investigate enabling p2 download statistics (4.1.0.Alpha2) * JBIDE-14016 Improve p2 download stat collection (4.1.0.Alpha2) * JBIDE-14381 Verify that p2.statsURI appears in artifacts.xml for Beta1 stable branch update site builds (4.1.0.Beta1) * JBIDE-17546 Download stat metadata should omit JOB_NAME from locally-built aggregate sites (4.2.0.Beta3) -- seems this was only done for JBT, not JBDS. See https://github.com/jbosstools/jbosstools-build-sites/pull/150/files#diff-... * JBIDE-15005 Provide UI, parser & anonymiser for download stats (4.3.x) > installer is trying to reach download.jboss.org for content > ----------------------------------------------------------- > > Key: JBDS-3408 > URL: https://issues.jboss.org/browse/JBDS-3408 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 8.0.0.Alpha2 > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Critical > Fix For: 9.0.0.Beta1 > > Attachments: JBDS3408.install.jboss-devstudio-9.0.0.Beta1-v20150430-1113-B3095-installer-standalone.jar.log.txt > > > Running latest devstudio 9 installer I caught it in reaching out to download.jboss.org which it should have *zero* links/dependency on. > My guess is there is an updatesite that have bad reference to download.jboss.org that we need fixing. > See screenshot at https://www.dropbox.com/s/wkr30jlvdc7d8wu/Screenshot%202015-04-15%2013.11... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19754) Red Deer using very old target platforms from Eclipse 4.3 (Kepler)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19754?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-19754. ------------------------------ Work done, closing. > Red Deer using very old target platforms from Eclipse 4.3 (Kepler) > ------------------------------------------------------------------ > > Key: JBIDE-19754 > URL: https://issues.jboss.org/browse/JBIDE-19754 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Assignee: Martin Malina > > Noticed today that the RedDeer master branch job, https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/RedDeer_master/ , uses TARGET_PLATFORM_VERSION = 4.30.6.Final and TARGET_PLATFORM_VERSION_MAXIMUM = 4.32.0.Final, which are from the JBoss Tools 4.1 (Eclipse 4.3 Kepler) days. > Shouldn't you be building with Eclipse 4.5 Mars, or at least Eclipse 4.4 Luna? > cc: [~mmalina] [~maxandersen] -- 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 May 2015