July 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24743) JBT 4.5.0.AM2 - restart with different workspace hangs

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24743?page=com.atlassian.jira.plugi... ] Paul Leacu commented on JBIDE-24743: ------------------------------------ [~apodhrad] - There's a check box on the workspace dialog that says 'dont ask me again'. See your ~/.eclipse - it's got to be a [pref in there somewhere. > JBT 4.5.0.AM2 - restart with different workspace hangs > ------------------------------------------------------ > > Key: JBIDE-24743 > URL: https://issues.jboss.org/browse/JBIDE-24743 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.5.0.AM2 > Reporter: Paul Leacu > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.5.0.Final > > > Simple to reproduce: > 1. Install eclipse-jee-oxygen-R-linux-gtk-x86_64.tar.gz > 2. Run Eclipse and install http://download.jboss.org/jbosstools/oxygen/development/updates/ > 3. Restart and specify a different workspace - the Devstudio UI will hang > 4. Force Quit > 5. Re-run devstudio with the updated workspace > 6. It comes up fine -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24743) JBT 4.5.0.AM2 - restart with different workspace hangs

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24743?page=com.atlassian.jira.plugi... ] Andrej Podhradsky commented on JBIDE-24743: ------------------------------------------- [~pleacu] how to you change the workspace? Eclipse doesn't ask for a workspace after restart (cold or warm). > JBT 4.5.0.AM2 - restart with different workspace hangs > ------------------------------------------------------ > > Key: JBIDE-24743 > URL: https://issues.jboss.org/browse/JBIDE-24743 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.5.0.AM2 > Reporter: Paul Leacu > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.5.0.Final > > > Simple to reproduce: > 1. Install eclipse-jee-oxygen-R-linux-gtk-x86_64.tar.gz > 2. Run Eclipse and install http://download.jboss.org/jbosstools/oxygen/development/updates/ > 3. Restart and specify a different workspace - the Devstudio UI will hang > 4. Force Quit > 5. Re-run devstudio with the updated workspace > 6. It comes up fine -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-520) Escape characters not processed when building images [EBZ#504484]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-520: --------------------------------------- Summary: Escape characters not processed when building images [EBZ#504484] Key: ERT-520 URL: https://issues.jboss.org/browse/ERT-520 Project: Eclipse Release Train Issue Type: Task Components: Linux Tools Reporter: Friendly Jira Robot Created attachment 264654 Docker image build output in Eclipse console When building an image, the output may generate escape characters (yum/apt, downloads) that pollute the console. Maybe worth trying to use the terminal (cdt ?) instead of the Eclipse standard console -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4257) rh-eclipse46-devstudio provides packages that are dependencies of rh-eclipse46

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBDS-4257?page=com.atlassian.jira.plugin.... ] Lukáš Valach commented on JBDS-4257: ------------------------------------ According to the documentation \[1\], when a package is built by RPM the list of provided packages is generated automatically by default. This behaviour can be disabled using tag "autoprov". So I have added this line to devstudio.spec.template {code} # Disable automatic provision generation AutoProv: no {code} Then I build RPM and check what the RPM provides {code} rpm -qp --provides ./rh-eclipse47-devstudio-11.0-0.20170721.0905.el7.x86_64.rpm rh-eclipse47-devstudio = 11.0-0.20170721.0905.el7 rh-eclipse47-devstudio(x86-64) = 11.0-0.20170721.0905.el7 {code} I tried to install rh-eclipse47 and I see that problem is resolved. Then I installed rh-eclipse47-devstudio and I don't see any problems. Possible PR: https://github.com/jbdevstudio/jbdevstudio-product/pull/466 \[1\] http://ftp.rpm.org/max-rpm/s1-rpm-depend-auto-depend.html > rh-eclipse46-devstudio provides packages that are dependencies of rh-eclipse46 > ------------------------------------------------------------------------------ > > Key: JBDS-4257 > URL: https://issues.jboss.org/browse/JBDS-4257 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, rpm > Affects Versions: 10.3.0.AM2 > Environment: RHEL7 > Reporter: Lukáš Valach > Assignee: Nick Boldt > Fix For: 11.0.0.GA > > Attachments: rh-eclipse46-devstudio_provides.txt, rh-eclipse46_provides.txt, yum_install_rh-eclipse46.png > > > I noticed rh-eclipse46-devstudio is installed as dependenci when installing rh-eclipse46. > !yum_install_rh-eclipse46.png|thumbnail! > [~vkadlcik] said that it is because rh-eclipse46-devstudio offers some package which rh-eclipse46 needs, so yum decides to use devstudio as library. > He said that the best practice for end-user application like rh-eclipse46-devstudio is to have less amount of stuff in "rpm -q --provides". Rh-eclipse46 provides 4 packages, devstudio provides 539 packages. > [^rh-eclipse46_provides.txt] > [^rh-eclipse46-devstudio_provides.txt] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24755) jpa-setup failed

by Jochen Buchholz (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24755?page=com.atlassian.jira.plugi... ] Jochen Buchholz resolved JBIDE-24755. ------------------------------------- Resolution: Done The problem are \r\n at the end of line in my maven settings.xml. The Jboss Forge Version in the actual Jboss Developer Studio Version in my Eclipse Neon installation does not care about the special characters. I cleaned up my maven settings.xml (normal unix cr's at end of line) and jboss forge works. This error also influences addon-install. I have no Idea how the special characters go into my maven settings.xml. > jpa-setup failed > ---------------- > > Key: JBIDE-24755 > URL: https://issues.jboss.org/browse/JBIDE-24755 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.5.0.AM1 > Environment: Gentoo Linux - oracle jdk 1.8.0.131 - Forge 3.7.1.Final > Reporter: Jochen Buchholz > > jpa-setup fail in forge console. When I use the "Open Command Selection Dialog" the jpa-setup runs with no error, but there are no jpa dependencies in the pom.xml. All described commands work without problems in the old eclipse neon version. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24755) jpa-setup failed

by Jochen Buchholz (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24755?page=com.atlassian.jira.plugi... ] Jochen Buchholz updated JBIDE-24755: ------------------------------------ Description: jpa-setup fail in forge console. When I use the "Open Command Selection Dialog" the jpa-setup runs with no error, but there are no jpa dependencies in the pom.xml. All described commands work without problems in the old eclipse neon version. (was: jpa-setup failin forge cponsole. When I use the "Open Command Selection Dialog" the jpa-setup runs with no error, but there are no jpa dependencies in the pom.xml. All described commands work without problems in the old eclipse neon version.) > jpa-setup failed > ---------------- > > Key: JBIDE-24755 > URL: https://issues.jboss.org/browse/JBIDE-24755 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.5.0.AM1 > Environment: Gentoo Linux - oracle jdk 1.8.0.131 - Forge 3.7.1.Final > Reporter: Jochen Buchholz > > jpa-setup fail in forge console. When I use the "Open Command Selection Dialog" the jpa-setup runs with no error, but there are no jpa dependencies in the pom.xml. All described commands work without problems in the old eclipse neon version. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24755) jpa-setup failed

by Jochen Buchholz (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24755?page=com.atlassian.jira.plugi... ] Jochen Buchholz updated JBIDE-24755: ------------------------------------ Environment: Gentoo Linux - oracle jdk 1.8.0.131 - Forge 3.7.1.Final (was: Gentoo Linux - oracle jdk 1.8.0.131) > jpa-setup failed > ---------------- > > Key: JBIDE-24755 > URL: https://issues.jboss.org/browse/JBIDE-24755 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.5.0.AM1 > Environment: Gentoo Linux - oracle jdk 1.8.0.131 - Forge 3.7.1.Final > Reporter: Jochen Buchholz > > jpa-setup failin forge cponsole. When I use the "Open Command Selection Dialog" the jpa-setup runs with no error, but there are no jpa dependencies in the pom.xml. All described commands work without problems in the old eclipse neon version. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24755) jpa-setup failed

by Jochen Buchholz (JIRA)

Jochen Buchholz created JBIDE-24755: --------------------------------------- Summary: jpa-setup failed Key: JBIDE-24755 URL: https://issues.jboss.org/browse/JBIDE-24755 Project: Tools (JBoss Tools) Issue Type: Bug Components: forge Affects Versions: 4.5.0.AM1 Environment: Gentoo Linux - oracle jdk 1.8.0.131 Reporter: Jochen Buchholz jpa-setup failin forge cponsole. When I use the "Open Command Selection Dialog" the jpa-setup runs with no error, but there are no jpa dependencies in the pom.xml. All described commands work without problems in the old eclipse neon version. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24663) Try to fix javaee7 examples tests

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24663?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-24663. --------------------------------- Resolution: Done PR is merged:) > Try to fix javaee7 examples tests > --------------------------------- > > Key: JBIDE-24663 > URL: https://issues.jboss.org/browse/JBIDE-24663 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-tests > Affects Versions: 4.5.0.AM1 > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Fix For: 4.5.0.AM2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22436) Intermittent NullPointerException upon opening helloworld, kitchensink cheat sheets in JBDS

by Michal Jurc (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22436?page=com.atlassian.jira.plugi... ] Michal Jurc edited comment on JBIDE-22436 at 7/21/17 4:21 AM: -------------------------------------------------------------- [~nickboldt]: Reproduced with JBDS 11.0.0.AM2. Please see the attached log: [^npe-jbds11-fedora26-x64.log] was (Author: mjurc): [~nickboldt]: Reproduced with JBDS 11.0.0.AM2. > Intermittent NullPointerException upon opening helloworld, kitchensink cheat sheets in JBDS > ------------------------------------------------------------------------------------------- > > Key: JBIDE-22436 > URL: https://issues.jboss.org/browse/JBIDE-22436 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples, upstream > Affects Versions: 4.3.1.Final > Reporter: Michal Jurc > Assignee: Snjezana Peco > Fix For: 4.4.x > > Attachments: JBIDE-22436-10.0-helloworld.log, JBIDE-22436-9.1-helloworld.log, helloworld-cheatsheet.xml, jbds104-cheat-sheet-npe.log, kitchensink-cheatsheet.xml, npe-jbds11-fedora26-x64.log, org.jboss.tools.cheatsheet.test.zip > > > After finishing the import of {{helloworld}} and {{kitchensink}} quickstarts, the user is prompted whether the cheat sheet for the project should be opened. Upon opening it, JBDS 9.0 and 9.1 produces the following error message: > {quote}An error has occurred. See error log for more details. > java.lang.NullPointerException{quote} > The detailed error log produces the same message. > The quickstarts and their cheat sheets work even after the prompt with NullPointerException message. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 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 July 2017