September 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-20842) Need to implement npm support

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20842?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-20842: -------------------------------- Description: Initially npm support should include the following commands: 1) [init|https://docs.npmjs.com/cli/init] - package.json creation 2) [update|https://docs.npmjs.com/cli/update] - updates all the packages listed to the latest version 3) [install|https://docs.npmjs.com/cli/install] (no arguments) - Installs the dependencies in the local *node_modules* folder was: Initially npm support should include the following commands: 1) [init|https://docs.npmjs.com/cli/init] - package.json creation 2) [update|https://docs.npmjs.com/cli/update] - updates all the packages listed to the latest version 3) [install] (no arguments) - Installs the dependencies in the local *node_modules* folder > Need to implement npm support > ----------------------------- > > Key: JBIDE-20842 > URL: https://issues.jboss.org/browse/JBIDE-20842 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: javascript-bower > Affects Versions: 4.3.0.CR1 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Labels: new_and_noteworthy > Fix For: 4.4.0.Alpha1 > > > Initially npm support should include the following commands: > 1) [init|https://docs.npmjs.com/cli/init] - package.json creation > 2) [update|https://docs.npmjs.com/cli/update] - updates all the packages listed to the latest version > 3) [install|https://docs.npmjs.com/cli/install] (no arguments) - Installs the dependencies in the local *node_modules* folder -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20842) Need to implement npm support

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20842?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-20842: -------------------------------- Description: Initially npm support should include the following commands: 1) [init|https://docs.npmjs.com/cli/init] - package.json creation 2) [update|https://docs.npmjs.com/cli/update] - updates all the packages listed to the latest version 3) [install] (no arguments) - Installs the dependencies in the local *node_modules* folder > Need to implement npm support > ----------------------------- > > Key: JBIDE-20842 > URL: https://issues.jboss.org/browse/JBIDE-20842 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: javascript-bower > Affects Versions: 4.3.0.CR1 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Labels: new_and_noteworthy > Fix For: 4.4.0.Alpha1 > > > Initially npm support should include the following commands: > 1) [init|https://docs.npmjs.com/cli/init] - package.json creation > 2) [update|https://docs.npmjs.com/cli/update] - updates all the packages listed to the latest version > 3) [install] (no arguments) - Installs the dependencies in the local *node_modules* folder -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-508) integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBTIS-508?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBTIS-508: ------------------------------------------- btw. to be clear - i'm all +1 for merging into the minimal set of sites that makes sense; but just remember that even if we do the merge http://download.jboss.org/jbosstools/updates/stable/luna/integration-stack url still need to continue to exist since we now have users/customers with GA'ed versions that directly link to it. > integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism > -------------------------------------------------------------------------------------------------- > > Key: JBTIS-508 > URL: https://issues.jboss.org/browse/JBTIS-508 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: releng > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > > While reviewing JBIDE-20803 I noticed the following: > {code} > jboss.discovery.site.integration-stack.url|jbosstools|4.2.4=http://downlo... > {code} > The stable release for 4.2.4 is stated to point to the stable integration stack url which on surface looks good: > But there are a few problems: > 1) why not just point to http://download.jboss.org/jbosstools/updates/stable/luna/ and have the above internal detail url composited in ? > 2) the actual composite behind it right now is http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4... which links in http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4... (our main sites should never composite earlyaccees since then when users install supported versions they suddenly will now also have access to earlyaccess. > #1 is mainly just to reduce the number of updatesites actually necessary for users to work with > #2 seems to be something inherent broken in the IS build since earlyaccess shold *never* be aggregated into the release site. > Any earlyaccess connectors should explicitly point to a *separate* earlyaccess site. > I would also have expected that the discovery site with the discovery plugins was kept *separate* from the actual update sites to avoid any coupling between these. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-508) integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBTIS-508?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBTIS-508: ------------------------------------------- Yes, that is what we discussed we would do for devstudio 8 when we refactored central to be composited into the main updatesite. I don't see a problem in having IS have an empty EA site linked in if that makes publishing more uniform (no need to remove it if the content is just empty). > integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism > -------------------------------------------------------------------------------------------------- > > Key: JBTIS-508 > URL: https://issues.jboss.org/browse/JBTIS-508 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: releng > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > > While reviewing JBIDE-20803 I noticed the following: > {code} > jboss.discovery.site.integration-stack.url|jbosstools|4.2.4=http://downlo... > {code} > The stable release for 4.2.4 is stated to point to the stable integration stack url which on surface looks good: > But there are a few problems: > 1) why not just point to http://download.jboss.org/jbosstools/updates/stable/luna/ and have the above internal detail url composited in ? > 2) the actual composite behind it right now is http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4... which links in http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4... (our main sites should never composite earlyaccees since then when users install supported versions they suddenly will now also have access to earlyaccess. > #1 is mainly just to reduce the number of updatesites actually necessary for users to work with > #2 seems to be something inherent broken in the IS build since earlyaccess shold *never* be aggregated into the release site. > Any earlyaccess connectors should explicitly point to a *separate* earlyaccess site. > I would also have expected that the discovery site with the discovery plugins was kept *separate* from the actual update sites to avoid any coupling between these. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20842) Need to implement npm support

by Ilya Buziuk (JIRA)

Ilya Buziuk created JBIDE-20842: ----------------------------------- Summary: Need to implement npm support Key: JBIDE-20842 URL: https://issues.jboss.org/browse/JBIDE-20842 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: javascript-bower Affects Versions: 4.3.0.CR1 Reporter: Ilya Buziuk Assignee: Ilya Buziuk Fix For: 4.4.0.Alpha1 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19536) Infinite job loop when creating project

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19536?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19536: --------------------------------------------- this should be reported/opened on platfrom-dev mailinglist imo to raise awarenes if this happens often. > Infinite job loop when creating project > --------------------------------------- > > Key: JBIDE-19536 > URL: https://issues.jboss.org/browse/JBIDE-19536 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.3.0.Alpha1 > Reporter: Rastislav Wagner > Assignee: Rastislav Wagner > Priority: Critical > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > Attachments: building.png, cdi_jstack, jstack.out, threaddump-1440009974151.tdump, threaddump-1440009999047.tdump, threaddump-1440010035476.tdump, workspace_jbds9_endless_building_loop.rar > > > Sometimes i end up in infinite job loop after creating a CDI project. There's no description of what jobs are running, not exception in log. In progress view I can see only "Building workspace (sleeping)" -see on video https://vimeo.com/123634974 > I was able to reproduce on CDI projects (1.0,1.2) but not on any other (Dynamic Web..) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20707) Forge runs out of inotify watches on Fedora 21

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20707?page=com.atlassian.jira.plugi... ] Jan Richter updated JBIDE-20707: -------------------------------- Attachment: lsof_jbds I recently upgraded to Fedora 22, so right now I haven't run into this issue in a while. But anyway, I used lsof to get a list of files open by JBDS. I'll attach it here, but I don't really know if it's any help. > Forge runs out of inotify watches on Fedora 21 > ---------------------------------------------- > > Key: JBIDE-20707 > URL: https://issues.jboss.org/browse/JBIDE-20707 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.3.0.CR1 > Reporter: Jan Richter > Assignee: George Gastaldi > Fix For: 4.3.1.Final > > Attachments: lsof_jbds > > > Starting Forge on Fedora 21 produces the following error: > {noformat} > WARNING: File monitoring could not be started. > 16:41:20 java.io.IOException: User limit of inotify instances reached or too many open files > 16:41:20 at sun.nio.fs.LinuxWatchService.<init>(LinuxWatchService.java:64) > 16:41:20 at sun.nio.fs.LinuxFileSystem.newWatchService(LinuxFileSystem.java:47) > 16:41:20 at org.jboss.forge.furnace.impl.FurnaceImpl.<init>(FurnaceImpl.java:152) > 16:41:20 at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > 16:41:20 at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > 16:41:20 at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > 16:41:20 at java.lang.reflect.Constructor.newInstance(Constructor.java:422) > 16:41:20 at java.lang.Class.newInstance(Class.java:442) > 16:41:20 at org.jboss.forge.furnace.se.FurnaceFactory.getInstance(FurnaceFactory.java:63) > 16:41:20 at org.jboss.tools.forge.core.furnace.FurnaceProvider.createFurnace(FurnaceProvider.java:78) > 16:41:20 at org.jboss.tools.forge.core.furnace.FurnaceProvider.startFurnace(FurnaceProvider.java:110) > 16:41:20 at org.jboss.tools.forge.core.furnace.FurnaceRuntime.start(FurnaceRuntime.java:80) > 16:41:20 at org.jboss.tools.forge.ui.util.ForgeHelper$1.runInWorkspace(ForgeHelper.java:52) > 16:41:20 at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39) > 16:41:20 at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} > Forge then refuses to start properly, Eclipse gets stuck on the launching forge progress dialog. The inotify watch limit is set to default (8192 I think) which really should be enough. > So far we established, that this happens on Fedora 21 or occasionally on 20 (which is not supported anymore). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3533) Unable to update/install the plug-ins

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3533?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-3533: -------------------------------------- Ok, thanks for the details. Indeed it seems like those sites "only" contain org.apache.commons.io in version 2.0.1 (and not 2.4.0). But the installer doesn't contain it neither and AFAIK, there is nothing we ship as part of JBDS 8.x that requires org.apache.commons.io in version 2.4.0, so I don't get why your JBDS instance complain. [~psrna] Is this an issue you're familiar with? > Unable to update/install the plug-ins > ------------------------------------- > > Key: JBDS-3533 > URL: https://issues.jboss.org/browse/JBDS-3533 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Affects Versions: 8.0.0.GA > Environment: Development > Reporter: Vikram Jammula > Assignee: Mickael Istria > Attachments: check Updates.png > > > An error occurred while collecting items to be installed > session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). > No repository found containing: osgi.bundle,org.apache.commons.io,2.4.0 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3533) Unable to update/install the plug-ins

by Vikram Jammula (JIRA)

[ https://issues.jboss.org/browse/JBDS-3533?page=com.atlassian.jira.plugin.... ] Vikram Jammula commented on JBDS-3533: -------------------------------------- [~mickael_istria] I have the below two entries and I am able to access the below URLs also. JBoss Developer Studio 8.0 Updates https://devstudio.redhat.com/updates/8.0/ Enabled JBoss Developer Studio 8.x - Early Access https://devstudio.redhat.com/earlyaccess/8.0/ Enabled > Unable to update/install the plug-ins > ------------------------------------- > > Key: JBDS-3533 > URL: https://issues.jboss.org/browse/JBDS-3533 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Affects Versions: 8.0.0.GA > Environment: Development > Reporter: Vikram Jammula > Assignee: Mickael Istria > Attachments: check Updates.png > > > An error occurred while collecting items to be installed > session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). > No repository found containing: osgi.bundle,org.apache.commons.io,2.4.0 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20737) On Linux, non-root user us not able to use auto-detect to access running Docker instance

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20737?page=com.atlassian.jira.plugi... ] Misha Ali commented on JBIDE-20737: ----------------------------------- Added PR link to the JIRA, and the enterprise version is here: https://access.redhat.com/articles/1488373 > On Linux, non-root user us not able to use auto-detect to access running Docker instance > ----------------------------------------------------------------------------------------- > > Key: JBIDE-20737 > URL: https://issues.jboss.org/browse/JBIDE-20737 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker > Affects Versions: 4.3.0.CR1 > Environment: RHEL 7 > OpenJDK 1.8 > Version: 9.0.0.CR1 > Build id: CR1-v20150912-1100-B100 > Build date: 20150912-1100 > CR1 includes: > com.spotify.docker.client_3.1.1.jar > org.eclipse.linuxtools.docker.core_1.1.0.201509082008.jar > org.eclipse.linuxtools.docker.docs_1.1.0.201509082008.jar > org.eclipse.linuxtools.docker.ui_1.1.0.201509082008.jar > Reporter: Len DiMaggio > Assignee: Misha Ali > Fix For: 4.3.1.Final > > Attachments: nonroot_1.png, nonroot_2.png, nonroot_3.png, root.png > > > On linux, a root user is able to rely on autoconnect to automatically connect to a running Docker instance (at unix:///var/run/docker.sock) > A non-root user is not able to connect. No warning or error is written to the UI/dialog. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 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 September 2015