April 2015 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-2074) easy way to auto-reload addons being developed

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2074?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-2074: ----------------------------------- Fix Version/s: 2.x Future > easy way to auto-reload addons being developed > ---------------------------------------------- > > Key: FORGE-2074 > URL: https://issues.jboss.org/browse/FORGE-2074 > Project: Forge > Issue Type: Feature Request > Reporter: James Strachan > Fix For: 2.x Future > > > So Apache Karaf has a nice command "dev:watch *" > http://karaf.apache.org/manual/latest-2.x/commands/dev-watch.html > which looks at all the currently installed bundles; figures out the mvn coords and where they are in the ~/.m2/repository; then any which are SNAPSHOT versions it watches them; if they get rebuilt it auto-reloads them. > It'd be great to have the same kinda thing in Forge for when you're working on an addon; then every time you do a mvn build, forge would reload it on the fly so you could try it out for real in a forge shell. > Right now it seems pretty slow to install newly built addons; anything to make the development a bit more RAD would be really cool. > e.g. a new command, something like... > {code} > addon-watch * > {code} > which uses the currently loaded jars and applies the wildcard to filter the SNAPSHOT builds to watch in ~/.m2/repository to detect if a build is done; then it'd invoke the addon-install command with the updated jar -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2200) Unable to fully remove addon in Windows

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2200?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-2200: ----------------------------------- Summary: Unable to fully remove addon in Windows (was: Unable to fully remove addon) > Unable to fully remove addon in Windows > --------------------------------------- > > Key: FORGE-2200 > URL: https://issues.jboss.org/browse/FORGE-2200 > Project: Forge > Issue Type: Bug > Components: Addon Development, Windows > Affects Versions: 2.13.0.Final > Environment: Eclipse CLI > Reporter: Michael Schwartz > Priority: Minor > Fix For: 2.x Future > > > as reported here: https://developer.jboss.org/thread/251850 > While developing addon's it is important to constantly redeploying the addon without changing the version number for each deploy. Currently this is not possible without closing/opening eclipse between each redeploy. After a while I found the following: > When executing "addon-remove" in Eclipse Luna the specified addon gets removed in the installed.xml file in the user's .forge directory. > The corresponding class-files in .forge directory however are still there and cannot be deleted under windows which is an indicator of an open file pointer. > When stopping forge console the directory still cannot be deleted. One have to close eclipse in order to delete the directory. > I assume that this is the cause of not being able to update the addon without exiting eclipse. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-693) Need an auto-update feature for plugins

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-693?page=com.atlassian.jira.plugin.... ] George Gastaldi closed FORGE-693. --------------------------------- Fix Version/s: (was: 2.x Future) Resolution: Duplicate Issue Duplicated by FORGE-1610 > Need an auto-update feature for plugins > --------------------------------------- > > Key: FORGE-693 > URL: https://issues.jboss.org/browse/FORGE-693 > Project: Forge > Issue Type: Feature Request > Components: Builtin Plugins > Reporter: George Gastaldi > > FORGE-217 auto-updates the core and the core plugins. There should be a way to update the current installed plugins. > Depending on the time taken to check, this could be done in the Forge startup. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1610) Introduce an Update addon

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1610?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1610. ---------------------------------- Assignee: Matej Briskar (was: Ivan St. Ivanov) Fix Version/s: 2.15.3.Final (was: 2.x Future) Resolution: Done > Introduce an Update addon > ------------------------- > > Key: FORGE-1610 > URL: https://issues.jboss.org/browse/FORGE-1610 > Project: Forge > Issue Type: Feature Request > Components: Usability > Affects Versions: 2.0.0.Final > Reporter: George Gastaldi > Assignee: Matej Briskar > Fix For: 2.15.3.Final > > > It would be nice to have an Update addon to allow update of addons and the Forge version itself. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2283) Provide a method for updating the user's installation automatically.

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2283?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-2283: ---------------------------------------- My point is that if this issue intends to update the whole user installation, it should upgrade the Furnace runtime, as well as other addons. I believe the simplest way to do that would be to download the offline ZIP and replace the current installation with it. > Provide a method for updating the user's installation automatically. > -------------------------------------------------------------------- > > Key: FORGE-2283 > URL: https://issues.jboss.org/browse/FORGE-2283 > Project: Forge > Issue Type: Feature Request > Reporter: Lincoln Baxter III > Assignee: Matej Briskar > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2283) Provide a method for updating the user's installation automatically.

by Matej Briskar (JIRA)

[ https://issues.jboss.org/browse/FORGE-2283?page=com.atlassian.jira.plugin... ] Matej Briskar commented on FORGE-2283: -------------------------------------- This was mainly referencing ruleset in the windup. In Forge you mean updating just every single addon? > Provide a method for updating the user's installation automatically. > -------------------------------------------------------------------- > > Key: FORGE-2283 > URL: https://issues.jboss.org/browse/FORGE-2283 > Project: Forge > Issue Type: Feature Request > Reporter: Lincoln Baxter III > Assignee: Matej Briskar > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2283) Provide a method for updating the user's installation automatically.

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2283?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-2283: ---------------------------------------- The provided PR will update a single addon, not the whole installation > Provide a method for updating the user's installation automatically. > -------------------------------------------------------------------- > > Key: FORGE-2283 > URL: https://issues.jboss.org/browse/FORGE-2283 > Project: Forge > Issue Type: Feature Request > Reporter: Lincoln Baxter III > Assignee: Matej Briskar > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues April 2015