December 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1359) `forge --install core` SNAPSHOTS causes infinite loop

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1359?page=com.atlassian.jira.plugin... ] George Gastaldi edited comment on FORGE-1359 at 12/13/13 8:26 AM: ------------------------------------------------------------------ I tried to reproduce the issue, but failed to do so. Can you give more details? Have you installed the snapshots in the local maven repository before attempting to install them? was (Author: gastaldi): I tried to reproduce the issue, but failed to do so. Can you give more details? Have you installed the snapshots before attempting to install them? > `forge --install core` SNAPSHOTS causes infinite loop > ----------------------------------------------------- > > Key: FORGE-1359 > URL: https://issues.jboss.org/browse/FORGE-1359 > Project: Forge > Issue Type: Bug > Components: Addon Manager > Reporter: Lincoln Baxter III > Fix For: 2.x Future > > > With the latest snapshots, the following command causes the install to hang forever: > {code}forge --install org.jboss.forge.addon:core,2.0.0-SNAPSHOT{code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1359) `forge --install core` SNAPSHOTS causes infinite loop

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1359?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-1359: ---------------------------------------- I tried to reproduce the issue, but failed to do so. Can you give more details? Have you installed the snapshots before attempting to install them? > `forge --install core` SNAPSHOTS causes infinite loop > ----------------------------------------------------- > > Key: FORGE-1359 > URL: https://issues.jboss.org/browse/FORGE-1359 > Project: Forge > Issue Type: Bug > Components: Addon Manager > Reporter: Lincoln Baxter III > Fix For: 2.x Future > > > With the latest snapshots, the following command causes the install to hang forever: > {code}forge --install org.jboss.forge.addon:core,2.0.0-SNAPSHOT{code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1359) `forge --install core` SNAPSHOTS causes infinite loop

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-1359: ----------------------------------------- Summary: `forge --install core` SNAPSHOTS causes infinite loop Key: FORGE-1359 URL: https://issues.jboss.org/browse/FORGE-1359 Project: Forge Issue Type: Bug Components: Addon Manager Reporter: Lincoln Baxter III Fix For: 2.x Future With the latest snapshots, the following command causes the install to hang forever: {code}forge --install org.jboss.forge.addon:core,2.0.0-SNAPSHOT{code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[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 reassigned FORGE-988: ------------------------------------- Assignee: (was: George Gastaldi) > 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 > Priority: Critical > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-158) Upgrade jQuery to 2.x

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-158?page=com.atlassian.jira.... ] Vineet Reynolds updated FORGEPLUGINS-158: ----------------------------------------- Description: Going by the [jQuery 2.0 release notes|http://blog.jquery.com/2013/04/18/jquery-2-0-released/], we should aim to use jQuery 2.x for several types of environments, due to the lack of support available for the 1.x baseline. PhoneGap/Cordova apps would be of concern to us. To allow the generated scaffold to be of use in Cordova apps, we'll upgrade to jQuery 2.x. was: Going by the [jQuery 2.0 release notes|http://blog.jquery.com/2013/04/18/jquery-2-0-released/], we should aim to use jQuery 2.x for several types of environments, due to the lack of support available for the 1.x baseline. PhoneGap/Cordova apps would be of concern to us. This would deprecate jQuery 1.x usage in the quickstarts. For now. the plan is to continue using jQuery 1.x in non-Cordova quickstarts and examples. Sites and apps are still expected to use jQuery 1.x since it carries IE6+ support. Upgrading jQuery usage in TicketMonster might prove to be a more complicated affair since it would require the Cordova dependent bits to run with jQuery 2.x, but also require the other bits (the desktop and mobile browsers based components) to use jQuery 1.x. > Upgrade jQuery to 2.x > --------------------- > > Key: FORGEPLUGINS-158 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-158 > Project: Forge Plugins > Issue Type: Task > Components: AngularJS Scaffold > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > > Going by the [jQuery 2.0 release notes|http://blog.jquery.com/2013/04/18/jquery-2-0-released/], we should aim to use jQuery 2.x for several types of environments, due to the lack of support available for the 1.x baseline. PhoneGap/Cordova apps would be of concern to us. > To allow the generated scaffold to be of use in Cordova apps, we'll upgrade to jQuery 2.x. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-158) Upgrade jQuery to 2.x

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-158?page=com.atlassian.jira.... ] Vineet Reynolds resolved FORGEPLUGINS-158. ------------------------------------------ Resolution: Done Pushed upstream: https://github.com/forge/angularjs-scaffoldx-plugin/commit/2d6baafce3daaa... > Upgrade jQuery to 2.x > --------------------- > > Key: FORGEPLUGINS-158 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-158 > Project: Forge Plugins > Issue Type: Task > Components: AngularJS Scaffold > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > > Going by the [jQuery 2.0 release notes|http://blog.jquery.com/2013/04/18/jquery-2-0-released/], we should aim to use jQuery 2.x for several types of environments, due to the lack of support available for the 1.x baseline. PhoneGap/Cordova apps would be of concern to us. > To allow the generated scaffold to be of use in Cordova apps, we'll upgrade to jQuery 2.x. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-158) Upgrade jQuery to 2.x

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-158?page=com.atlassian.jira.... ] Vineet Reynolds moved WFK2-372 to FORGEPLUGINS-158: --------------------------------------------------- Project: Forge Plugins (was: JBoss WFK 2) Key: FORGEPLUGINS-158 (was: WFK2-372) Issue Type: Task (was: Requirement) Workflow: GIT Pull Request workflow (was: CDW v1) Component/s: AngularJS Scaffold (was: JavaScript Libraries) Security: (was: JBoss Internal) Target Release: (was: 2.5.0.GA) > Upgrade jQuery to 2.x > --------------------- > > Key: FORGEPLUGINS-158 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-158 > Project: Forge Plugins > Issue Type: Task > Components: AngularJS Scaffold > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > > Going by the [jQuery 2.0 release notes|http://blog.jquery.com/2013/04/18/jquery-2-0-released/], we should aim to use jQuery 2.x for several types of environments, due to the lack of support available for the 1.x baseline. PhoneGap/Cordova apps would be of concern to us. > This would deprecate jQuery 1.x usage in the quickstarts. For now. the plan is to continue using jQuery 1.x in non-Cordova quickstarts and examples. Sites and apps are still expected to use jQuery 1.x since it carries IE6+ support. > Upgrading jQuery usage in TicketMonster might prove to be a more complicated affair since it would require the Cordova dependent bits to run with jQuery 2.x, but also require the other bits (the desktop and mobile browsers based components) to use jQuery 1.x. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1358) Prevent Forge Addons to Issue System.exit(0)

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1358?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1358. ---------------------------------- Resolution: Won't Fix The solution is to set up a SecurityManager as indicated in http://docs.oracle.com/javase/7/docs/technotes/guides/security/PolicyFile... This is out of scope of Furnace/Forge > Prevent Forge Addons to Issue System.exit(0) > --------------------------------------------- > > Key: FORGE-1358 > URL: https://issues.jboss.org/browse/FORGE-1358 > Project: Forge > Issue Type: Feature Request > Components: Furnace (Container) > Affects Versions: 2.0.0.Beta3 > Reporter: Koen Aers > > Right now it's possible to write a rogue add-on that while executing calls 'System.exit(0)'. If Forge 2 is embedded in Eclipse (or in any other application), this brings down the VM of the hosting application. This should be avoided. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1358) Prevent Forge Addons to Issue System.exit(0)

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1358?page=com.atlassian.jira.plugin... ] George Gastaldi edited comment on FORGE-1358 at 12/11/13 12:54 PM: ------------------------------------------------------------------- I don't think this can be solved in Forge itself. The Eclipse VM (as well as the shell UI) should start with a {{java.security.policy}} parameter to enable a Security Manager. More information: http://docs.oracle.com/javase/7/docs/technotes/guides/security/PolicyFile... was (Author: gastaldi): I don't think this can be solved in Forge itself. The Eclipse VM (as well as the shell UI) should start with a {{java.policy}} parameter to enable a Security Manager. More information: http://docs.oracle.com/javase/7/docs/technotes/guides/security/PolicyFile... > Prevent Forge Addons to Issue System.exit(0) > --------------------------------------------- > > Key: FORGE-1358 > URL: https://issues.jboss.org/browse/FORGE-1358 > Project: Forge > Issue Type: Feature Request > Components: Furnace (Container) > Affects Versions: 2.0.0.Beta3 > Reporter: Koen Aers > > Right now it's possible to write a rogue add-on that while executing calls 'System.exit(0)'. If Forge 2 is embedded in Eclipse (or in any other application), this brings down the VM of the hosting application. This should be avoided. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1358) Prevent Forge Addons to Issue System.exit(0)

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1358?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-1358: ---------------------------------------- I don't think this can be solved in Forge itself. The Eclipse VM (as well as the shell UI) should start with a {{java.policy}} parameter to enable a Security Manager. More information: http://docs.oracle.com/javase/7/docs/technotes/guides/security/PolicyFile... > Prevent Forge Addons to Issue System.exit(0) > --------------------------------------------- > > Key: FORGE-1358 > URL: https://issues.jboss.org/browse/FORGE-1358 > Project: Forge > Issue Type: Feature Request > Components: Furnace (Container) > Affects Versions: 2.0.0.Beta3 > Reporter: Koen Aers > > Right now it's possible to write a rogue add-on that while executing calls 'System.exit(0)'. If Forge 2 is embedded in Eclipse (or in any other application), this brings down the VM of the hosting application. This should be avoided. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues December 2013