[JBoss JIRA] (JBDS-2044) .eclipseproduct file no longer refers to JBDS
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2044?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-2044:
----------------------------------
Turns out this PR does nothing because devstudio includes a number of features which depend explicitly on org.eclipse.platform feature, not just the org.eclipse.platform plugin:
{code}
o.e.m2e.wtp.feature
o.e.m2e.jaxrs.feature
o.e.m2e.jpa.feature
o.e.m2e.jsf.feature
o.j.t.maven.cdi.feature
o.j.t.maven.feature
o.j.t.maven.hibernatefeature
o.j.t.maven.project.examples.feature
o.j.t.maven.sourcelookup.feature
o.sonatype.m2e.egit.feature
{code}
> .eclipseproduct file no longer refers to JBDS
> ---------------------------------------------
>
> Key: JBDS-2044
> URL: https://issues.jboss.org/browse/JBDS-2044
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 5.0.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Optional
> Labels: discuss
> Fix For: 10.1.0.Alpha1
>
>
> Before, with the linux x64 installer (jbdevstudio-product-linux-gtk-x86_64-5.0.0.v201202271832M-H79-Beta1.jar) the .eclipseproduct file read:
> {code}
> name=JBoss Developer Studio
> id=com.jboss.jbds.all
> version=5.0.0.v201202271832M-H79-Beta1
> {code}
> Now, with the universal installer (jbdevstudio-product-universal-5.0.0.v201202271832M-H79-Beta1.jar), it reads:
> {code}
> name=Eclipse Platform
> id=org.eclipse.platform
> version=3.7.0
> {code}
> Latest code in equinox.runtime master branch is located http://git.eclipse.org/c/equinox/rt.equinox.framework.git/tree/bundles/or...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[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 closed JBIDE-20707.
-------------------------------
Resolution: Out of Date
I had to run the following at the same time to get the error again:
- 2 instances of devstudio with populated workspaces
- forge (3.2.1.Final) run from both studios
- firefox
- maven build of integration tests
That is good enough for me. I'll close this issue then.
> 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.x, 4.4.x
>
> 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)
9 years, 10 months
[JBoss JIRA] (JBIDE-22418) Update AERI Eclipse IDE Client to 2.0
by Marcel Bruch (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22418?page=com.atlassian.jira.plugi... ]
Marcel Bruch commented on JBIDE-22418:
--------------------------------------
Yes, it will be part of the Neon.0.rc4 update site. An update of the version constraint will suffice (I assume it will work even w/o updating the version).
> Update AERI Eclipse IDE Client to 2.0
> -------------------------------------
>
> Key: JBIDE-22418
> URL: https://issues.jboss.org/browse/JBIDE-22418
> Project: Tools (JBoss Tools)
> Issue Type: Component Upgrade
> Components: aeri, target-platform
> Affects Versions: 4.4.0.Final
> Reporter: Marcel Bruch
> Assignee: Nick Boldt
> Fix For: 4.4.0.Final
>
>
> I'm about to release 2.0.0 for Neon.0.
> [~nickboldt], what is the earliest release of JBIDE / Devstudio that will pick up 2.0.0?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months