June 2016 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-2652) Upgrade to Furnace 2.23.5.Final

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2652?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2652. ---------------------------------- Resolution: Done > Upgrade to Furnace 2.23.5.Final > ------------------------------- > > Key: FORGE-2652 > URL: https://issues.jboss.org/browse/FORGE-2652 > Project: Forge > Issue Type: Component Upgrade > Components: Furnace (Container) > Affects Versions: 3.2.0.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 3.2.1.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2652) Upgrade to Furnace 2.23.5.Final

by George Gastaldi (JIRA)

George Gastaldi created FORGE-2652: -------------------------------------- Summary: Upgrade to Furnace 2.23.5.Final Key: FORGE-2652 URL: https://issues.jboss.org/browse/FORGE-2652 Project: Forge Issue Type: Component Upgrade Components: Furnace (Container) Affects Versions: 3.2.0.Final Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 3.2.1.Final -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FURNACE-114) Dirty checking mechanism

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FURNACE-114?page=com.atlassian.jira.plugi... ] George Gastaldi closed FURNACE-114. ----------------------------------- Fix Version/s: 2.23.5.Final Assignee: George Gastaldi Resolution: Done > Dirty checking mechanism > ------------------------ > > Key: FURNACE-114 > URL: https://issues.jboss.org/browse/FURNACE-114 > Project: Forge: Furnace > Issue Type: Feature Request > Components: Runtime > Reporter: Sergei Egorov > Assignee: George Gastaldi > Fix For: 2.23.5.Final > > > Right now Furnace by default does two types of dirty checking - version checking and file system watching. These can be extracted, plus dirty checking mechanism can be pluggable, i.e. for non-filesystem implementations of the storage. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FURNACE-112) Separate deploy/enable/disable methods from AddonRepository/MutableAddonRepository

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FURNACE-112?page=com.atlassian.jira.plugi... ] George Gastaldi closed FURNACE-112. ----------------------------------- Fix Version/s: 2.23.5.Final Assignee: George Gastaldi Resolution: Done > Separate deploy/enable/disable methods from AddonRepository/MutableAddonRepository > ---------------------------------------------------------------------------------- > > Key: FURNACE-112 > URL: https://issues.jboss.org/browse/FURNACE-112 > Project: Forge: Furnace > Issue Type: Enhancement > Components: Addon Manager > Affects Versions: 2.23.4.Final > Reporter: Sergei Egorov > Assignee: George Gastaldi > Fix For: 2.23.5.Final > > > Hi! > Looks like AddonRepository is doing two different jobs - addons repository *and* storing the state. But if one wants to store the state of deployed & enabled addons, there is no interface to implement to keep filesystem storage of artifacts, but having state somewhere else (DB, in memory data grid, just in memory, not the file system) > I think following methods should have their own interface: > isEnabled() > listAll() > listEnabled() > listEnabledCompatibleWithVersion() > enable() > disable() > it will make it possible to provide non-FS implementation of the state storage. > Thanks! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ROASTER-103) compute serialUID incomplete

by Nicolas Challut (JIRA)

Nicolas Challut created ROASTER-103: --------------------------------------- Summary: compute serialUID incomplete Key: ROASTER-103 URL: https://issues.jboss.org/browse/ROASTER-103 Project: Roaster Issue Type: Bug Affects Versions: 2.18.7.Final Reporter: Nicolas Challut If I extend a class which implements Serializable, I have to have a serialVersionUID even if I don't implements Serializable myself. But SerialVersionUIDComputer.compute() returrn 0... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues June 2016