[JBoss JIRA] (JBIDE-17628) Ctrl+4 does not open the default Forge runtime, but always 2.6.0
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17628?page=com.atlassian.jira.plugi... ]
Koen Aers resolved JBIDE-17628.
-------------------------------
Resolution: Done
> Ctrl+4 does not open the default Forge runtime, but always 2.6.0
> ----------------------------------------------------------------
>
> Key: JBIDE-17628
> URL: https://issues.jboss.org/browse/JBIDE-17628
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.2.0.Beta2
> Reporter: Martin Malina
> Assignee: Koen Aers
> Fix For: 4.2.0.CR1
>
>
> According to JBDS 8.0.0 Beta2 release notes:
> {quote}
> The default Forge runtime starts on pressing Ctrl+4. To change the default runtime, click Window→Preferences, expand Forge→Installed Forge Runtimes and select the check box of the runtime that you want to be default.
> {quote}
> This is not true. I changed the default to 1.x, started Forge using Ctrl+4, and it still starts 2.6.0.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-17656) Forge crashed Eclipse
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17656?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-17656:
---------------------------------------------
was the hs_err_pid dump crashing somewhere different than the other two ?
And yes, high GC activity and class trashing could definitely explain it.
> 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, 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-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: JVM-GCactivity-Linux.png
Attaching VisualVM analysis from Oracle Java 8 Update 5 on Fedora 20.
> 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, 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-18130) JBDS doesn't follow/honor <module-alias> of jboss modules
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18130?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-18130:
----------------------------------------
Component/s: server
> JBDS doesn't follow/honor <module-alias> of jboss modules
> ---------------------------------------------------------
>
> Key: JBIDE-18130
> URL: https://issues.jboss.org/browse/JBIDE-18130
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Reporter: Takayuki Konishi
> Attachments: modalias.zip
>
>
> JBDS 8 beta3 cannot resolve <module-alias> of jboss modules. For example, org.apache.log4j cannot resolved with these configurations [1][2][3]. They are valid; when I create a similar maven project, it can be deployed in EAP 6.3.0.
> [1]
> {code:title=MANIFEST.MF|borderStyle=solid}
> Manifest-Version: 1.0
> Class-Path:
> Dependencies: org.apache.log4j
> {code}
> [2]
> {code}
> import org.apache.log4j.Logger;
> ...
> public class SampleClass{
> private static final Logger logger = Logger.getLogger(SampleClass.class);
> ...
> {code}
> [3]
> {code:title=module.xml|borderStyle=solid}
> <module-alias xmlns="urn:jboss:module:1.1" name="org.apache.log4j" target-name="org.jboss.log4j.logmanager"/>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-18015) For JBIDE 4.2.0.CR1: Ensure copyrights and provider names are correct in all plugins and features [Hibernate]
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18015?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen resolved JBIDE-18015.
-----------------------------------------
Resolution: Rejected
current state of license/copyright is sufficient for CR1.
> For JBIDE 4.2.0.CR1: Ensure copyrights and provider names are correct in all plugins and features [Hibernate]
> -------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18015
> URL: https://issues.jboss.org/browse/JBIDE-18015
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: hibernate
> Reporter: Nick Boldt
> Assignee: Max Rydahl Andersen
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.CR1
>
>
> For JBIDE 4.2.0.CR1 [Hibernate]: Please perform the following *2* tasks:
> 1. Verify that all your plugin and feature copyright dates end in 2014, and that the copyright holder is *{color:red}Red Hat, Inc.{color}* or a variation similar to the examples below.
> Be sure to also include *translated* files, where they exist.
> *java files*
> {code:title=*.java}
> Copyright (c) 2010-2014 Red Hat, Inc. and others.
> {code}
> *html files*
> {code:title=about.html}
> © 2014 Red Hat, Inc. All rights reserved
> {code}
> *properties files*
> {code:title=about.properties}
> Copyright (c) Red Hat, Inc., contributors and others 2004 - 2014. All rights reserved
> {code}
> {code:title=about_fr.properties}
> Copyright (c) Red Hat, Inc., contributors and others 2004 - 2014. Tous droits r\u00E9serv\u00E9s.
> {code}
> {code:title=feature.properties}
> Copyright (c) 2010-2014 Red Hat, Inc. and others.
> {code}
> {code:title=Messages.properties}
> # Copyright (c) 2014 Red Hat, Inc. and others.
> {code}
> *xsd files*
> {code:title=jboss-as-naming_1_3.xsd}
> Copyright 2014, Red Hat, Inc., and individual contributors
> {code}
> 2. Verify that all your plugin and feature provider names are *{color:red}JBoss by Red Hat{color}*.
> Be sure to also include *translated* files, where they exist.
> *This step is particularly important for new plugins and features that have been added recently.*
> Depending on how your plugin is configured you should see something like this in your *plugin.properties* files:
> {code}BundleName = JMX Resources Bundle
> BundleProvider = JBoss by Red Hat{code}
> or
> {code}Bundle-Name.0 = JBossTools Archives Core Plugin
> Bundle-Vendor.0 = JBoss by Red Hat{code}
> Then in your MANIFEST.MF files, you will reference these variables like this.
> *Bundle-Localization* is required or your plugin won't see the values in your *plugin.properties* file!
> {code}Bundle-Localization: plugin
> Bundle-Name: %BundleName
> Bundle-Vendor: %BundleProvider{code}
> or
> {code}Bundle-Localization: plugin
> Bundle-Name: %Bundle-Name.0
> Bundle-Vendor: %Bundle-Vendor.0{code}
> For features, check that your *feature.properties* file contains good values too:
> {code}featureName=JMX Console
> featureProvider=JBoss by Red Hat{code}
> or
> {code}featureName=JBoss Archives Tools
> providerName=JBoss by Red Hat{code}
> Then in your feature.xml files, you will reference these variables like this:
> {code}<feature label="%featureName" provider-name="%featureProvider" ...>{code}
> or
> {code}<feature label="%featureName" provider-name="%providerName" ...>{code}
> 3. If you would like QE to review your changes, please *Resolve* this JIRA when done.
> 4. If you do not require QE to review your changes, please *Close* this JIRA when done.
> 5. If you have any questions, please contact [~nickboldt].
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Hibernate task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-18128) Jboss Eclipse Luna plugin doesn't deploy all .class
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18128?page=com.atlassian.jira.plugi... ]
Rob Stryker reassigned JBIDE-18128:
-----------------------------------
Assignee: Rob Stryker
> Jboss Eclipse Luna plugin doesn't deploy all .class
> ---------------------------------------------------
>
> Key: JBIDE-18128
> URL: https://issues.jboss.org/browse/JBIDE-18128
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta3
> Reporter: fede pia
> Assignee: Rob Stryker
> Priority: Blocker
>
> The problem I'm facing is that when I run/debug my aplication from Server view in Eclipse the jboss plugin doesn't deploy all the .class files, thus I get ClassNotFoundException.
> I've tried cleaning the project, cleaning jboss, remove temporaries but nothing works. The not found classes are random.
> For Eclipse 4.3 everything works fine, although this issue usually happens but I can solve it with a Project -> Clean
> As a context, I've installed Eclipse Luna (also tried STS 3.6) and added Jboss Tools plugin 4.2.0 Beta 3 (I've installed only Jboss AS component). The jboss servers I tested were JBoss 7.1 and Wildfly 8.1.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-18128) Jboss Eclipse Luna plugin doesn't deploy all .class
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18128?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-18128:
-------------------------------------
[~fedepia] Did your files have non-ascii filenames? If they did, then there's a related bug recently fixed: https://issues.jboss.org/browse/JBIDE-18095
If they didn't, and all filenames were ascii, then this will require more digging.
> Jboss Eclipse Luna plugin doesn't deploy all .class
> ---------------------------------------------------
>
> Key: JBIDE-18128
> URL: https://issues.jboss.org/browse/JBIDE-18128
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta3
> Reporter: fede pia
> Priority: Blocker
>
> The problem I'm facing is that when I run/debug my aplication from Server view in Eclipse the jboss plugin doesn't deploy all the .class files, thus I get ClassNotFoundException.
> I've tried cleaning the project, cleaning jboss, remove temporaries but nothing works. The not found classes are random.
> For Eclipse 4.3 everything works fine, although this issue usually happens but I can solve it with a Project -> Clean
> As a context, I've installed Eclipse Luna (also tried STS 3.6) and added Jboss Tools plugin 4.2.0 Beta 3 (I've installed only Jboss AS component). The jboss servers I tested were JBoss 7.1 and Wildfly 8.1.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[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: JVM-GCactivity.png
JVM-GCactivity-heap.png
Attaching files of VisualVM on Windows. Note the high GC activity during command execution, and the heap usage (and metaspace usage) during the same period.
> 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, JVM-GCactivity-heap.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-17656) Forge crashed Eclipse
by Vineet Reynolds (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17656?page=com.atlassian.jira.plugi... ]
Vineet Reynolds commented on JBIDE-17656:
-----------------------------------------
An update: I did manage to reproduce this once using Antonio's script. The hs_err_pid dump produced wasn't informative, except indicating that the JVM crashed.
I updated the JDK later to Oracle Java 8 update 20, and the crash seems to have disappeared. JVM runtime analysis however gives a hint as to why the crash might have occurred - GC activity is rather high (as low as 30% and even higher during scaffolding, only in Windows). I suspect a OS-contextual {{System.gc}} invocation is responsible for this. We should/must throttle this.
> 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
>
>
> 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-18026) For JBIDE 4.2.0.CR1: Ensure copyrights and provider names are correct in all plugins and features [Freemarker]
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18026?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen resolved JBIDE-18026.
-----------------------------------------
Resolution: Won't Fix
> For JBIDE 4.2.0.CR1: Ensure copyrights and provider names are correct in all plugins and features [Freemarker]
> --------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18026
> URL: https://issues.jboss.org/browse/JBIDE-18026
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: freemarker
> Reporter: Nick Boldt
> Assignee: Max Rydahl Andersen
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.CR1
>
>
> For JBIDE 4.2.0.CR1 [Freemarker]: Please perform the following *2* tasks:
> 1. Verify that all your plugin and feature copyright dates end in 2014, and that the copyright holder is *{color:red}Red Hat, Inc.{color}* or a variation similar to the examples below.
> Be sure to also include *translated* files, where they exist.
> *java files*
> {code:title=*.java}
> Copyright (c) 2010-2014 Red Hat, Inc. and others.
> {code}
> *html files*
> {code:title=about.html}
> © 2014 Red Hat, Inc. All rights reserved
> {code}
> *properties files*
> {code:title=about.properties}
> Copyright (c) Red Hat, Inc., contributors and others 2004 - 2014. All rights reserved
> {code}
> {code:title=about_fr.properties}
> Copyright (c) Red Hat, Inc., contributors and others 2004 - 2014. Tous droits r\u00E9serv\u00E9s.
> {code}
> {code:title=feature.properties}
> Copyright (c) 2010-2014 Red Hat, Inc. and others.
> {code}
> {code:title=Messages.properties}
> # Copyright (c) 2014 Red Hat, Inc. and others.
> {code}
> *xsd files*
> {code:title=jboss-as-naming_1_3.xsd}
> Copyright 2014, Red Hat, Inc., and individual contributors
> {code}
> 2. Verify that all your plugin and feature provider names are *{color:red}JBoss by Red Hat{color}*.
> Be sure to also include *translated* files, where they exist.
> *This step is particularly important for new plugins and features that have been added recently.*
> Depending on how your plugin is configured you should see something like this in your *plugin.properties* files:
> {code}BundleName = JMX Resources Bundle
> BundleProvider = JBoss by Red Hat{code}
> or
> {code}Bundle-Name.0 = JBossTools Archives Core Plugin
> Bundle-Vendor.0 = JBoss by Red Hat{code}
> Then in your MANIFEST.MF files, you will reference these variables like this.
> *Bundle-Localization* is required or your plugin won't see the values in your *plugin.properties* file!
> {code}Bundle-Localization: plugin
> Bundle-Name: %BundleName
> Bundle-Vendor: %BundleProvider{code}
> or
> {code}Bundle-Localization: plugin
> Bundle-Name: %Bundle-Name.0
> Bundle-Vendor: %Bundle-Vendor.0{code}
> For features, check that your *feature.properties* file contains good values too:
> {code}featureName=JMX Console
> featureProvider=JBoss by Red Hat{code}
> or
> {code}featureName=JBoss Archives Tools
> providerName=JBoss by Red Hat{code}
> Then in your feature.xml files, you will reference these variables like this:
> {code}<feature label="%featureName" provider-name="%featureProvider" ...>{code}
> or
> {code}<feature label="%featureName" provider-name="%providerName" ...>{code}
> 3. If you would like QE to review your changes, please *Resolve* this JIRA when done.
> 4. If you do not require QE to review your changes, please *Close* this JIRA when done.
> 5. If you have any questions, please contact [~nickboldt].
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Freemarker task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months