Yeah that sounds suspect ;) I'd expect this to break a lot of things when installing new addons. We really at some point should get multi-addon/instance working. Even though it would create bloat. It would make Furnace a true graph classloader.

Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."

On Mon, Jan 18, 2016 at 8:57 AM, George Gastaldi <gegastaldi@gmail.com> wrote:

Branch: refs/heads/master
Home: https://github.com/forge/furnace
Commit: 5ad248177cd6c127a7955f0c12c8130420cf8a06
https://github.com/forge/furnace/commit/5ad248177cd6c127a7955f0c12c8130420cf8a06
Author: George Gastaldi <gegastaldi@gmail.com>
Date: 2016-01-18 (Mon, 18 Jan 2016)

Changed paths:
M manager/impl/src/main/java/org/jboss/forge/furnace/manager/impl/AddonManagerImpl.java

Log Message:
-----------
Revert "FURNACE-50: Core addons should never be updated"

This reverts commit 638787d5b10624f5b8bd25aef9285b3dc51777da.

_______________________________________________
forge-commits mailing list
forge-commits@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-commits