[JBoss JIRA] (JBIDE-17656) Forge crashed Eclipse
by Vineet Reynolds (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17656?page=com.atlassian.jira.plugi... ]
Vineet Reynolds updated JBIDE-17656:
------------------------------------
Attachment: hs_err_pid640.log
Yes, attaching the file. It was in some daemon thread.
However, I can confirm that Forge does invoke {{System.gc}} rather vigorously on Windows. On Antonio's script alone, it exceeds 200.
Scaffolding being File I/O intensive would explain why the GC activity peaks during scaffolding.
> Forge crashed Eclipse
> ---------------------
>
> Key: JBIDE-17656
> URL: https://issues.jboss.org/browse/JBIDE-17656
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.2.0.Beta3
> Environment: Windows 7 64bits, JDK 8.0.0, JBDS 8.0.0.Beta2
> Reporter: Fred Bricon
> Assignee: Vineet Reynolds
> Fix For: 4.2.0.CR1
>
> Attachments: generate.fsh, hs_err_pid4536.log, hs_err_pid5320.log, hs_err_pid640.log, JVM-GCactivity-heap.png, JVM-GCactivity-Linux.png, JVM-GCactivity.png
>
>
> I tried to reproduce the steps from JBIDE-17655 a 2nd time, Eclipse crashed while forge was scaffolding
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-5130) JBoss Tools HTML Editor doesn't accept accents in preview mode.
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-5130?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen resolved JBIDE-5130.
----------------------------------------
Resolution: Won't Fix
probably still an issue but this is in xulrunner which wuold require changes in native code and there are a workaround by just usingthe source editor.
marking as wont fix since requires xulrunner changes.
> JBoss Tools HTML Editor doesn't accept accents in preview mode.
> ---------------------------------------------------------------
>
> Key: JBIDE-5130
> URL: https://issues.jboss.org/browse/JBIDE-5130
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 3.1.0.M3
> Reporter: Joao Viragine
> Assignee: Konstantin Marmalyukov
> Priority: Optional
> Labels: xulrunner
> Fix For: LATER
>
>
> JBoss Tools HTML Editor doesn't accept accents in preview mode.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-18135) License header plugin
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18135?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-18135:
---------------------------------------------
suggested implementation is to add custom variable resolver like shown at http://web.archive.org/web/20100414054049/http://dev.eclipse.org/blogs/jd... and http://thomaswabner.wordpress.com/2009/08/21/use-your-own-variable-in-ecl... that would insert the right license based on context.
i.e.
${license} would locate nearest LICENSE.header in the filesystem (even beyond the project root since it might be in a multi-module project) and insert its content.
Could also take argument to control the file:
${license:java.license}
note: This file would then need to have the proper comment syntax already applied (unless we make a ${comment:${license}} that would handle comments dynamically based on file type.
> License header plugin
> ---------------------
>
> Key: JBIDE-18135
> URL: https://issues.jboss.org/browse/JBIDE-18135
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Reporter: Kabir Khan
>
> In WIldFly we have split out the core from the EE part of the project, and there is a plan to relicense the core. I and others who work on WildFly using Eclipse seem to like having both the 'core' and 'EE' projects open in the same workspace. once the relicensing has happened, it will become problematic to maintain the licenses in the mixed workspace.
> We would like to be able to configure some code templates adding the 'core' licenses when a new file is added to the 'core' projects, and to add the lgpl header when a new file is added to the the 'ee' projects.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-6096) Hibernate Code Generation Configuration in standard Run Configuration list
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-6096?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen commented on JBIDE-6096:
--------------------------------------------
[~jpeterka] I'm not really following what you see as a problem here ?
A hibernate code gen launch is *not* a normal runnable configuration. It has its own type.
Run configurations can has notion of run, debug, profile etc. hibernate code gen does not have that.
and if we added it in hibernate code gen laucnhces would be mixed with your java or run on server launch calls - that does not sound right does it ?
> Hibernate Code Generation Configuration in standard Run Configuration list
> --------------------------------------------------------------------------
>
> Key: JBIDE-6096
> URL: https://issues.jboss.org/browse/JBIDE-6096
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: hibernate
> Affects Versions: 3.1.0.GA
> Reporter: Jiri Peterka
> Assignee: Koen Aers
> Priority: Optional
> Labels: new_and_noteworthy
> Fix For: 4.3.x
>
> Attachments: screenshot-1.jpg
>
>
> Hibernate Code generation configuration is separated from other run configuration. I can't see any reason why it's not part of other standard run configurations. It should be moved there.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-18135) License header plugin
by Kabir Khan (JIRA)
Kabir Khan created JBIDE-18135:
----------------------------------
Summary: License header plugin
Key: JBIDE-18135
URL: https://issues.jboss.org/browse/JBIDE-18135
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Reporter: Kabir Khan
In WIldFly we have split out the core from the EE part of the project, and there is a plan to relicense the core. I and others who work on WildFly using Eclipse seem to like having both the 'core' and 'EE' projects open in the same workspace. once the relicensing has happened, it will become problematic to maintain the licenses in the mixed workspace.
We would like to be able to configure some code templates adding the 'core' licenses when a new file is added to the 'core' projects, and to add the lgpl header when a new file is added to the the 'ee' projects.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months