May 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-4403) An error when installing Devstudio 10.4.0.GA from Marketplace

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBDS-4403?page=com.atlassian.jira.plugin.... ] Lukáš Valach commented on JBDS-4403: ------------------------------------ I am satisfied. > An error when installing Devstudio 10.4.0.GA from Marketplace > ------------------------------------------------------------- > > Key: JBDS-4403 > URL: https://issues.jboss.org/browse/JBDS-4403 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: marketplace > Affects Versions: 10.4.0.GA > Environment: Eclipse Neon.3 for JavaEE Developers > Reporter: Andrej Podhradsky > Assignee: Nick Boldt > Fix For: 10.4.0.GA > > > The following error occurs when installing Devstudio 10.4.0.GA from Marketplace > {code} > Cannot complete the install because of a conflicting dependency. > Software being installed: Red Hat JBoss Developer Studio (Core Features) 10.4.0.v20170511-1748 (com.jboss.devstudio.core.feature.feature.group 10.4.0.v20170511-1748) > Software currently installed: m2e - Maven Integration for Eclipse (includes Incubating components) 1.7.0.20160603-1933 (org.eclipse.m2e.feature.feature.group 1.7.0.20160603-1933) > Only one of the following can be installed at once: > Maven Project Model Edit Bundle 1.7.0.20160603-1933 (org.eclipse.m2e.model.edit 1.7.0.20160603-1933) > Maven Project Model Edit Bundle 1.7.1.20161104-1805 (org.eclipse.m2e.model.edit 1.7.1.20161104-1805) > Cannot satisfy dependency: > From: Red Hat JBoss Developer Studio (Core Features) 10.4.0.v20170511-1748 (com.jboss.devstudio.core.feature.feature.group 10.4.0.v20170511-1748) > To: com.jboss.devstudio.core.rpmdeps.feature.feature.group [10.4.0.v20170504-1343] > Cannot satisfy dependency: > From: Red Hat JBoss Developer Studio (Feature Dependencies) 10.4.0.v20170504-1343 (com.jboss.devstudio.core.rpmdeps.feature.feature.group 10.4.0.v20170504-1343) > To: org.eclipse.m2e.feature.feature.group 1.7.1.20161104-1805 > Cannot satisfy dependency: > From: m2e - Maven Integration for Eclipse (includes Incubating components) 1.7.0.20160603-1933 (org.eclipse.m2e.feature.feature.group 1.7.0.20160603-1933) > To: org.eclipse.m2e.model.edit [1.7.0.20160603-1933] > Cannot satisfy dependency: > From: m2e - Maven Integration for Eclipse (includes Incubating components) 1.7.1.20161104-1805 (org.eclipse.m2e.feature.feature.group 1.7.1.20161104-1805) > To: org.eclipse.m2e.model.edit [1.7.1.20161104-1805] > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24484) deprecate jbosstools projects / move to Central ?

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24484?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-24484: ------------------------------------ [~nickboldt] ok for freemarker and arquillian but I would keep browsersim the same as livereload and xulrunner, waiting for [~akazakov] feedback > deprecate jbosstools projects / move to Central ? > ------------------------------------------------- > > Key: JBIDE-24484 > URL: https://issues.jboss.org/browse/JBIDE-24484 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.AM2 > > > With the upcoming plan for devstudio 11 / jbosstools 4.5, it may be time to consider moving parts of jbosstools / devstudio out of the Core Tools category and into Central as optional installs. Then in future we can deprecate them / remove them. > Here's the list of projects in jbosstools: > https://github.com/jbosstools/jbosstools-devdoc/blob/master/list_of_proje... > https://issues.jboss.org/projects/JBIDE?selectedItem=com.atlassian.jira.j... > Once we have an idea of which projects could be moved/removed/deprecated, we can open subtasks for those projects. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3822) Disable "This program might not have installed correctly" on cancelation

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3822?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3822. ----------------------------- Closing as done, at last :) > Disable "This program might not have installed correctly" on cancelation > ------------------------------------------------------------------------ > > Key: JBDS-3822 > URL: https://issues.jboss.org/browse/JBDS-3822 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: havoc > Fix For: 11.0.0.AM1 > > Attachments: devsuite.manifest > > > Upon closing/cancelling the installer before going through the entire installation process, Windows will open a dialog saying "This program might not have installed correctly" and the user has to somehow confirm it. > This should be avoided by providing an application manifest that indicates support for certain Windows versions. > Docs here: > https://msdn.microsoft.com/en-us/library/dd371711%28VS.85%29.aspx -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24512) Remove m2e-jdt-compiler from devstudio/jbt sites/distros

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24512?page=com.atlassian.jira.plugi... ] Lukáš Valach closed JBIDE-24512. -------------------------------- Verified in devstudio-11.0.0.AM1-v20170531-1042-B189 and in TP using p2browser, closing. > Remove m2e-jdt-compiler from devstudio/jbt sites/distros > -------------------------------------------------------- > > Key: JBIDE-24512 > URL: https://issues.jboss.org/browse/JBIDE-24512 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, central > Reporter: Fred Bricon > Assignee: Nick Boldt > Fix For: 4.5.0.AM1 > > > m2e 1.8 (Oxygen) now provides lifecycle mappings for maven-compiler-plugin compilerIds eclipse, jdt, javac-with-errorprone. The 1st two conflict with https://github.com/jbosstools/m2e-jdt-compiler, so org.jboss.tools.m2e.jdt.feature should be wipe out from our oxygen compatible update sites/distros. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4414) Add DevSuite Installation to Windows Control Panel

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-4414?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-4414. ----------------------------- Closing as done. > Add DevSuite Installation to Windows Control Panel > -------------------------------------------------- > > Key: JBDS-4414 > URL: https://issues.jboss.org/browse/JBDS-4414 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: New_and_noteworthy, Sprint_Demo > Fix For: 11.0.0.AM1 > > Attachments: rhdevsuite-control-panel.png > > > Dev Suite Uninstaller now can be called form Windows Control Panel > !rhdevsuite-control-panel.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3632) Using a pre packaged version of Cygwin that doesn't require the installer to download packages

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3632?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3632. ----------------------------- Closing as done. > Using a pre packaged version of Cygwin that doesn't require the installer to download packages > ---------------------------------------------------------------------------------------------- > > Key: JBDS-3632 > URL: https://issues.jboss.org/browse/JBDS-3632 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Reporter: Ken Finnigan > Assignee: Denis Golovin > Labels: New_and_noteworthy, Sprint_Demo > Fix For: 11.0.0.AM1 > > > It should be possible to install Cygwin, and then package that install in such a way that we can do a more silent install that doesn't require packages to be downloaded. > Some clues can be found here: https://cygwin.com/ml/cygwin/2010-03/msg00877.html > The fix should modify the bundle build to download packages into temp folder and then zip them. This zip then included into bundle installer. > {code}c:\DevelopmentSuite\cygwin\setup-x86_64.exe -D --no-admin --quiet-mode --only-site -l c:\DevelopmentSuite\cygwin\packages --site http://mirrors.xmission.com/cygwin --categories Base --packages openssh,rsync --root c:\DevelopmentSuite{code} > Another modification should be done to cygwin installer to check for included zip with packages, unpack it and do installation from local folder instead > {code}c:\DevelopmentSuite\cygwin\setup-x86_64.exe --no-admin --quiet-mode -L -l c:\DevelopmentSuite\cygwin\packages --categories Base --packages openssh,rsync --root c:\DevelopmentSuite\cygwin{code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4400) Uninstaller fails to remove Virtualbox

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-4400?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-4400. ----------------------------- Verified in build #240 > Uninstaller fails to remove Virtualbox > -------------------------------------- > > Key: JBDS-4400 > URL: https://issues.jboss.org/browse/JBDS-4400 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 11.0.0.AM1 > Environment: Windows > Reporter: Denis Golovin > Assignee: Sudhir Verma > Fix For: 11.0.0.AM1 > > > When running uninstall.ps1 from user home folder > {code}powershell -ExecutionPolicy bypass -File c:\DevelopmentSuite\uninstaller\uninstall.ps1 > C:\Users\Eskimo>powershell -ExecutionPolicy bypass -File c:\DevelopmentSuite\uninstaller\uninstall.ps1 > Copy-Item : Cannot find path 'C:\Users\Eskimo\uninstall-helper.ps1' because it does not exist. > At C:\DevelopmentSuite\uninstaller\uninstall.ps1:3 char:1 > + Copy-Item ./uninstall-helper.ps1 $env:TEMP/uninstall-helper.ps1 > + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > + CategoryInfo : ObjectNotFound: (C:\Users\Eskimo\uninstall-helper.ps1:String) [Copy-Item], ItemNotFoundE > xception > + FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.CopyItemCommand > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4214) use devstudioReleaseVersion=11 and path segment = /11/ for the devstudio update & build folders

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBDS-4214?page=com.atlassian.jira.plugin.... ] Lukáš Valach closed JBDS-4214. ------------------------------ Verified, closing. > use devstudioReleaseVersion=11 and path segment = /11/ for the devstudio update & build folders > ----------------------------------------------------------------------------------------------- > > Key: JBDS-4214 > URL: https://issues.jboss.org/browse/JBDS-4214 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, rpm, updatesite > Affects Versions: 10.2.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 11.0.0.AM1 > > > Alexey and Tim think that using https://devstudio.jboss.com/10.0/stable/updates/ for the update site that contains 10.0, 10.1, 10.2, 10.3 updates... is confusing. > So, for devstudio 11, we could use: > * /11/ > * /11.x/ > * /oxygen/ (because this is based on Eclipse Oxygen) > * /e47/ (because this is based on Eclipse 4.7) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4394) Add requirement rh-java-common-google-gson

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBDS-4394?page=com.atlassian.jira.plugin.... ] Lukáš Valach commented on JBDS-4394: ------------------------------------ Hmm, it didn't help. Yum isn't upgrading rh-java-common-google-gson. In the RPM documentation \[1\] is written that we should specify version of RPM on which we would like depend, otherwise any version will be accepted. \[1\] https://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/... Possibly we could try: {code} Requires: rh-java-common-google-gson >= 2.2.4, rh-java-common-google-gson < 3.0.0 {code} I have discussed this topic with [~vkadlcik]. He said that it's known issue. It is hard to maintain list of versions in spec file so they are ignoring this problem. Then said that users shoud keep they system up to date. So it's up to you. We can either maintain versions in spec file or mention in install guide that it is necessary to update whole system. > Add requirement rh-java-common-google-gson > ------------------------------------------ > > Key: JBDS-4394 > URL: https://issues.jboss.org/browse/JBDS-4394 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: build, rpm > Affects Versions: 11.0.0.AM1 > Reporter: Lukáš Valach > Assignee: Nick Boldt > Fix For: 11.0.0.AM1 > > > Add requirement rh-java-common-google-gson to the RPM spec file \[1\]. > \[1\] https://github.com/jbdevstudio/jbdevstudio-product/blob/master/rpm/devstu... > ---- > *Reason:* > After update form Devstudio 10.2 to 10.4 I had this error in the eclipse log: > {code} > !ENTRY org.eclipse.jgit.pgm 4 0 2017-05-12 14:03:44.808 > !MESSAGE FrameworkEvent ERROR > !STACK 0 > org.osgi.framework.BundleException: Could not resolve module: org.eclipse.jgit.pgm [231] > Unresolved requirement: Import-Package: org.eclipse.jgit.lfs.server.fs; version="[4.6.1,4.7.0)" > -> Export-Package: org.eclipse.jgit.lfs.server.fs; bundle-symbolic-name="org.eclipse.jgit.lfs.server"; bundle-version="4.6.1.201703071140-r"; version="4.6.1"; uses:="javax.servlet, javax.servlet.http, org.eclipse.jgit.lfs.server, org.eclipse.jgit.lfs.lib" > org.eclipse.jgit.lfs.server [230] > Unresolved requirement: Import-Package: com.google.gson; version="[2.2.4,3.0.0)" > Unresolved requirement: Import-Package: org.eclipse.jgit.lfs.server; version="[4.6.1,4.7.0)" > -> Export-Package: org.eclipse.jgit.lfs.server; bundle-symbolic-name="org.eclipse.jgit.lfs.server"; bundle-version="4.6.1.201703071140-r"; version="4.6.1"; uses:="javax.servlet.http, org.eclipse.jgit.lfs.lib" > ... > ... > !ENTRY org.eclipse.wst.jsdt.js.node 4 0 2017-05-12 14:03:46.661 > !MESSAGE FrameworkEvent ERROR > !STACK 0 > org.osgi.framework.BundleException: Could not resolve module: org.eclipse.wst.jsdt.js.node [653] > Unresolved requirement: Require-Bundle: com.google.gson; bundle-version="[2.2.4,3.0.0)" > {code} > Steps to reproduce: > # Disable RHSCL 2.4 and Devstudio snapshot repo > # Add RHSCL 2.3 and Devstudio stable repo > # yum remove rh-* > # yum install rh-eclipse46-devstudio (should install 10.2.0.GA) > # check if eclipse works (I had no errors in the log) > # Disable RHSCL 2.3 and Devstudio stable repo > # Enable RHSCL 2.4 and Devstudio snapshot repo > # rm -rf ~/.eclipse > # Start the Eclipse with -clean > # There should be error I mentioned above. I didn't see any impact to users, egit worked fine. > # sudo yum update "rh-*" > {code} > Updating: > rh-java-common-google-gson noarch 2.2.4-1.el7 rh-eclipse46-build 177 k > rh-java-common-javapackages-tools noarch 4.3.2-1.14.el7 rh-eclipse46-build 95 k > rh-java-common-lucene5 noarch 5.4.1-2.3.el7 rh-eclipse46-build 2.2 M > rh-java-common-lucene5-analysis noarch 5.4.1-2.3.el7 rh-eclipse46-build 1.3 M > rh-java-common-lucene5-analyzers-smartcn noarch 5.4.1-2.3.el7 rh-eclipse46-build 3.4 M > rh-java-common-lucene5-queries noarch 5.4.1-2.3.el7 rh-eclipse46-build 211 k > rh-java-common-lucene5-queryparser noarch 5.4.1-2.3.el7 rh-eclipse46-build 339 k > rh-java-common-lucene5-sandbox noarch 5.4.1-2.3.el7 rh-eclipse46-build 246 k > rh-java-common-python-javapackages noarch 4.3.2-1.14.el7 rh-eclipse46-build 87 k > rh-maven33-runtime > {code} > # Restart Eclipse, it will start without errors. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24524) a TypeScript editor (BlueSky)

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24524?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-24524: ---------------------------------- Assignee: Nick Boldt > a TypeScript editor (BlueSky) > ----------------------------- > > Key: JBIDE-24524 > URL: https://issues.jboss.org/browse/JBIDE-24524 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jst > Reporter: Mickael Istria > Assignee: Nick Boldt > > BlueSky plugin ( https://marketplace.eclipse.org/content/bluesky-web-development-eclipse-i... ) brings support for TypeScript edition in Eclipse IDE relying on included language server. JBoss Tools should probably include it. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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