[JBoss JIRA] (FORGE-1604) JVM (stack guard) warning while loading xadisk native library.
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1604?page=com.atlassian.jira.plugin... ]
George Gastaldi closed FORGE-1604.
----------------------------------
Resolution: Won't Fix
Marking as won't fix
> JVM (stack guard) warning while loading xadisk native library.
> --------------------------------------------------------------
>
> Key: FORGE-1604
> URL: https://issues.jboss.org/browse/FORGE-1604
> Project: Forge
> Issue Type: Quality Risk
> Components: Resources
> Affects Versions: 2.0.0.Final
> Reporter: George Gastaldi
> Assignee: George Gastaldi
> Priority: Optional
> Fix For: 2.x Future
>
>
> The following warning is displayed in some OSes:
> {code}
> OpenJDK 64-Bit Server VM warning: You have loaded library /home/aslak/dev/source/forge/core/dev-tools-java/target/1393355046088-0/native/unix_32_xadisk.native which might have disabled stack guard. The VM will try to fix the stack guard now.
> It's highly recommended that you fix the library with 'execstack -c <libfile>', or link it with '-z noexecstack'.
> {code}
> Although it is harmless, it is quite annoying to see it in the logs.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (FORGE-988) Refactor AddonManager to support addon version conflicts
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-988?page=com.atlassian.jira.plugin.... ]
George Gastaldi updated FORGE-988:
----------------------------------
Priority: Major (was: Critical)
> Refactor AddonManager to support addon version conflicts
> --------------------------------------------------------
>
> Key: FORGE-988
> URL: https://issues.jboss.org/browse/FORGE-988
> Project: Forge
> Issue Type: Enhancement
> Components: Addon Manager
> Affects Versions: 2.0.0.Alpha6
> Reporter: George Gastaldi
> Fix For: 2.x Future
>
>
> Given that Addons A(1.0), B (1.0), C(1.0) are installed in an AddonRepository, and C(1.0) depends on B(1.0), when an addon D(1.0) to be installed requires B(1.1), there should be a way to warn against incompatibilities and let the user decide what to do. Same when D(1.0) depends on B(2.0)
> Basically an addon version is composed of Major.Minor.Micro
> In relation to the installed addon version and the requested addon version the following rules should be followed:
> - When Major version is different, the addons are assumed be completely incompatible (even if in practice that is not true). Fail installation
> - When Minor version is different, compatibility may be assured only if the requested version is less or equal to the required version. Prompt for installation of necessary version.
> - When Micro version is different, the addon is totally compatible, thus no compatibility check is required. No problem to install
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (FORGE-989) Support rollback of installed addons
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-989?page=com.atlassian.jira.plugin.... ]
George Gastaldi updated FORGE-989:
----------------------------------
Priority: Major (was: Critical)
> Support rollback of installed addons
> -------------------------------------
>
> Key: FORGE-989
> URL: https://issues.jboss.org/browse/FORGE-989
> Project: Forge
> Issue Type: Feature Request
> Components: Addon Manager
> Affects Versions: 2.0.0.Alpha6
> Reporter: George Gastaldi
> Fix For: 2.x Future
>
>
> After an installation is performed, it should be possible to revert the repository to a previous state.
> It should be possible to log every install/remove request for each addon and group them by transaction savepoints.
> Eg:
> - Install Addon A which depends on B,C,D ( C and D already installed)
> Log:
> Transaction #1
> Addon A: INSTALLED
> Addon B: INSTALLED
> - Install Addon E which depends on A
> Log:
> Transaction #2
> Addon E: INSTALLED
> Rollback of each transaction should have the following behavior:
> - Rollback of Transaction #2 should remove Addon E.
> - Rollback of Transaction #1 should remove A, B.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (FORGE-912) UI Scaffolding does not support entities with EmbeddedId
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-912?page=com.atlassian.jira.plugin.... ]
George Gastaldi updated FORGE-912:
----------------------------------
Priority: Major (was: Critical)
> UI Scaffolding does not support entities with EmbeddedId
> --------------------------------------------------------
>
> Key: FORGE-912
> URL: https://issues.jboss.org/browse/FORGE-912
> Project: Forge
> Issue Type: Enhancement
> Components: Scaffold
> Affects Versions: 1.3.0.Final
> Environment: Linux 3.8 - Firefox 20 - MySQL 5.5 - PostgresSQL 9.1
> Reporter: Hanine Hanynowsky
> Assignee: Vineet Reynolds
> Fix For: 2.x Future
>
>
> UI Scaffolding does not support Entities with EnbeddedId.
> The value of ID generated is always null and there is no way to view a corresponding object.
> The generated entity and EmbeddedId class seem fine to me. The issue is with the VIEW scaffolding (The beans and the way XHTML files values are binded).
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (FORGE-2164) Being able to create listeners defined in the Servlet spec
by George Gastaldi (JIRA)
George Gastaldi created FORGE-2164:
--------------------------------------
Summary: Being able to create listeners defined in the Servlet spec
Key: FORGE-2164
URL: https://issues.jboss.org/browse/FORGE-2164
Project: Forge
Issue Type: Sub-task
Components: Java EE
Affects Versions: 2.12.3.Final
Reporter: George Gastaldi
Fix For: 2.x Future
It should be possible to create classes implementing ServletContextListener or any other listener defined in the Servlet spec
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (FORGE-2163) 'addon-remove' error message is misleading when invalid coordinates are supplied
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-2163?page=com.atlassian.jira.plugin... ]
Lincoln Baxter III updated FORGE-2163:
--------------------------------------
Description:
See screenshot.
Error message should be more descriptive:
{code}***ERROR*** The specified addon coordinates [fooo, blah, bar ...] were not found within any configured furnace repository [repository locations] and cannot be removed.{code}
was:
See screenshot.
Error message should be more descriptive:
{code}***ERROR*** The specified addon coordinates [fooo, blah, bar ...] were not found within any configured furnace repository [repository locations]{code}
> 'addon-remove' error message is misleading when invalid coordinates are supplied
> --------------------------------------------------------------------------------
>
> Key: FORGE-2163
> URL: https://issues.jboss.org/browse/FORGE-2163
> Project: Forge
> Issue Type: Enhancement
> Components: Addon Manager, Builtin Plugins
> Affects Versions: 2.12.3.Final
> Reporter: Lincoln Baxter III
> Attachments: Screen Shot 2014-12-08 at 11.17.59 AM.png
>
>
> See screenshot.
> Error message should be more descriptive:
> {code}***ERROR*** The specified addon coordinates [fooo, blah, bar ...] were not found within any configured furnace repository [repository locations] and cannot be removed.{code}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (FORGE-2163) 'addon-remove' error message is misleading when invalid coordinates are supplied
by Lincoln Baxter III (JIRA)
Lincoln Baxter III created FORGE-2163:
-----------------------------------------
Summary: 'addon-remove' error message is misleading when invalid coordinates are supplied
Key: FORGE-2163
URL: https://issues.jboss.org/browse/FORGE-2163
Project: Forge
Issue Type: Enhancement
Components: Addon Manager, Builtin Plugins
Affects Versions: 2.12.3.Final
Reporter: Lincoln Baxter III
See screenshot.
Error message should be more descriptive:
{code}***ERROR*** The specified addon coordinates [fooo, blah, bar ...] were not found within any configured furnace repository [repository locations]{code}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months