July 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGEPLUGINS-121) jQuery Mobile Scaffold

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-121?page=com.atlassian.jira.... ] George Gastaldi updated FORGEPLUGINS-121: ----------------------------------------- Labels: scaffold (was: ) > jQuery Mobile Scaffold > ---------------------- > > Key: FORGEPLUGINS-121 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-121 > Project: Forge Plugins > Issue Type: Feature Request > Reporter: Burr Sutter > Labels: scaffold > > jQuery Mobile or jQuery Mobile + Backbone (to give the resulting code some structure). My goal is to compliment the jQuery Mobile Palette in JBDS/JBoss Tools. This means the generated UIs should be editable in our HTML5 editor + jQuery Mobile Palette, the app should work well with BrowserSim + LiveReload. > https://vimeo.com/67480300 > The generated app should be "mobile first" and mobile only. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1038) AddonManager should not attempt to update addons from immutable repositories

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1038?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1038. ---------------------------------- Resolution: Done Fixed > AddonManager should not attempt to update addons from immutable repositories > ---------------------------------------------------------------------------- > > Key: FORGE-1038 > URL: https://issues.jboss.org/browse/FORGE-1038 > Project: Forge > Issue Type: Bug > Components: Addon Manager > Affects Versions: 2.0.0.Alpha7 > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.0.0.Alpha8 > > > If Addon A(1.0) exists in an immutable repository and an installation request for A(1.1) is issued, AddonManager should deploy the A(1.1) in the mutable repository. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1038) AddonManager should not attempt to update addons from immutable repositories

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1038: -------------------------------------- Summary: AddonManager should not attempt to update addons from immutable repositories Key: FORGE-1038 URL: https://issues.jboss.org/browse/FORGE-1038 Project: Forge Issue Type: Bug Components: Addon Manager Affects Versions: 2.0.0.Alpha7 Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 2.0.0.Alpha8 If Addon A(1.0) exists in an immutable repository and an installation request for A(1.1) is issued, AddonManager should deploy the A(1.1) in the mutable repository. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-121) jQuery Mobile Scaffold

by Burr Sutter (JIRA)

Burr Sutter created FORGEPLUGINS-121: ---------------------------------------- Summary: jQuery Mobile Scaffold Key: FORGEPLUGINS-121 URL: https://issues.jboss.org/browse/FORGEPLUGINS-121 Project: Forge Plugins Issue Type: Feature Request Reporter: Burr Sutter jQuery Mobile or jQuery Mobile + Backbone (to give the resulting code some structure). My goal is to compliment the jQuery Mobile Palette in JBDS/JBoss Tools. This means the generated UIs should be editable in our HTML5 editor + jQuery Mobile Palette, the app should work well with BrowserSim + LiveReload. https://vimeo.com/67480300 The generated app should be "mobile first" and mobile only. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1037) REGRESSION: Addon installed in different repository does not register @Exported instances in AddonRegistry

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1037?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1037: ----------------------------------- Fix Version/s: 2.0.0.Alpha8 > REGRESSION: Addon installed in different repository does not register @Exported instances in AddonRegistry > ---------------------------------------------------------------------------------------------------------- > > Key: FORGE-1037 > URL: https://issues.jboss.org/browse/FORGE-1037 > Project: Forge > Issue Type: Bug > Components: Furnace (Container) > Affects Versions: 2.0.0.Alpha7 > Reporter: George Gastaldi > Priority: Blocker > Fix For: 2.0.0.Alpha8 > > -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1037) REGRESSION: Addon installed in different repository does not register @Exported instances in AddonRegistry

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1037?page=com.atlassian.jira.plugin... ] George Gastaldi reassigned FORGE-1037: -------------------------------------- Assignee: Lincoln Baxter III Could you have a look at this ? Thanks > REGRESSION: Addon installed in different repository does not register @Exported instances in AddonRegistry > ---------------------------------------------------------------------------------------------------------- > > Key: FORGE-1037 > URL: https://issues.jboss.org/browse/FORGE-1037 > Project: Forge > Issue Type: Bug > Components: Furnace (Container) > Affects Versions: 2.0.0.Alpha7 > Reporter: George Gastaldi > Assignee: Lincoln Baxter III > Priority: Blocker > Fix For: 2.0.0.Alpha8 > > -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1037) REGRESSION: Addon installed in different repository does not register @Exported instances in AddonRegistry

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1037?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1037: ----------------------------------- Priority: Blocker (was: Major) > REGRESSION: Addon installed in different repository does not register @Exported instances in AddonRegistry > ---------------------------------------------------------------------------------------------------------- > > Key: FORGE-1037 > URL: https://issues.jboss.org/browse/FORGE-1037 > Project: Forge > Issue Type: Bug > Components: Furnace (Container) > Affects Versions: 2.0.0.Alpha7 > Reporter: George Gastaldi > Priority: Blocker > -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1037) REGRESSION: Addon installed in different repository does not register @Exported instances in AddonRegistry

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1037: -------------------------------------- Summary: REGRESSION: Addon installed in different repository does not register @Exported instances in AddonRegistry Key: FORGE-1037 URL: https://issues.jboss.org/browse/FORGE-1037 Project: Forge Issue Type: Bug Components: Furnace (Container) Affects Versions: 2.0.0.Alpha7 Reporter: George Gastaldi -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1036) REGRESSION: Buld and Install an addon fails

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1036?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1036: ----------------------------------- Fix Version/s: 2.0.0.Alpha8 > REGRESSION: Buld and Install an addon fails > ------------------------------------------- > > Key: FORGE-1036 > URL: https://issues.jboss.org/browse/FORGE-1036 > Project: Forge > Issue Type: Bug > Components: Build Tools - Maven > Affects Versions: 2.0.0.Alpha7 > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.0.0.Alpha8 > > > {code} > [INFO] Scanning for projects... > [WARNING] > [WARNING] Some problems were encountered while building the effective model for com.george.app:demo:jar:1.0.0-SNAPSHOT > [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-jar-plugin is missing. @ line 54, column 15 > [WARNING] > [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build. > [WARNING] > [WARNING] For this reason, future Maven versions might no longer support building such malformed projects. > [WARNING] > [INFO] > [INFO] ------------------------------------------------------------------------ > [INFO] Building demo 1.0.0-SNAPSHOT > [INFO] ------------------------------------------------------------------------ > [WARNING] The POM for org.apache.maven.plugins:maven-clean-plugin:jar:2.4.1 is missing, no dependency information available > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 0.267s > [INFO] Finished at: Thu Jul 25 08:52:44 BRT 2013 > [INFO] Final Memory: 4M/113M > [INFO] ------------------------------------------------------------------------ > [ERROR] Plugin org.apache.maven.plugins:maven-clean-plugin:2.4.1 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-clean-plugin:jar:2.4.1: The repository system is offline but the artifact org.apache.maven.plugins:maven-clean-plugin:pom:2.4.1 is not available in the local repository. -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException > !ENTRY org.jboss.tools.forge.ui.ext 4 1 2013-07-25 08:52:44.557 > !MESSAGE Error logged from Forge Plugin: > !STACK 0 > org.jboss.forge.addon.projects.building.BuildException: Build failed. > at org.jboss.forge.addon.maven.projects.MavenProjectBuilder.build(MavenProjectBuilder.java:84) > at org.jboss.forge.addon.manager.impl.commands.AddonBuildAndInstallCommand.execute(AddonBuildAndInstallCommand.java:78) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:52) > at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:34) > at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:64) > at org.jboss.forge.addon.manager.impl.commands.AddonBuildAndInstallCommand_$$_javassist_7fbe78ee-910c-4ba9-aa1b-dcf95619d99f.execute(AddonBuildAndInstallCommand_$$_javassist_7fbe78ee-910c-4ba9-aa1b-dcf95619d99f.java) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$1.call(ClassLoaderAdapterCallback.java:84) > at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:34) > at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:60) > at org.jboss.forge.addon.ui.UICommand_$$_javassist_f9b5ce0a-b954-4c61-97f6-930356fada4d.execute(UICommand_$$_javassist_f9b5ce0a-b954-4c61-97f6-930356fada4d.java) > at org.jboss.tools.forge.ui.ext.wizards.ForgeWizard$FinishJob.runInWorkspace(ForgeWizard.java:159) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) > {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

12 years, 8 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 updated FORGE-988: ---------------------------------- Fix Version/s: 2.0.0.Alpha8 (was: 2.0.0.Alpha7) > 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 > Assignee: George Gastaldi > Priority: Critical > Fix For: 2.0.0.Alpha8 > > > 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

12 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues July 2013