April 2015 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-2303) Automatically generate OSGi Manifest.mf and export all packages in addonX-api

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2303?page=com.atlassian.jira.plugin... ] Work on FORGE-2303 stopped by George Gastaldi. ---------------------------------------------- > Automatically generate OSGi Manifest.mf and export all packages in addonX-api > ----------------------------------------------------------------------------- > > Key: FORGE-2303 > URL: https://issues.jboss.org/browse/FORGE-2303 > Project: Forge > Issue Type: Feature Request > Components: Usability > Affects Versions: 2.15.2.Final > Reporter: Lincoln Baxter III > Assignee: George Gastaldi > Fix For: 2.x Future > > > The Forge APIs (org.jboss.forge.addon:resources-api, etc) should (as a part of the build process) automatically generate an OSGi Manifest.mf file to mark all packages provided by the API as exported. > The benefit of this is that consumers in an OSGi environment will automatically export necessary addon packages/types to dependent bundles without needing to explicitly do so in their manifest. (This should prevent common bugs with OSGi exports.) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years

1
0
0 / 0

[JBoss JIRA] (FURNACE-41) Slow performance when installing add-ons with many add-on dependencies

by George Gastaldi (JIRA)

George Gastaldi created FURNACE-41: -------------------------------------- Summary: Slow performance when installing add-ons with many add-on dependencies Key: FURNACE-41 URL: https://issues.jboss.org/browse/FURNACE-41 Project: Forge: Furnace Issue Type: Enhancement Components: Addon Manager Affects Versions: 2.15.4.Final Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 2.x Future When an add-on is installed that depends on add-ons already installed, the AddonManager does a full scan on the dependency tree. This hurts performance badly. When installing an add-on, the AddonDependencyResolver should not care about all the transitive addon dependencies, only the ones that are not already installed. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years

1
0
0 / 0

[JBoss JIRA] (FURNACE-40) Add OSGi Manifest.mf and export all packages in furnace-api and furnace-proxy

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FURNACE-40?page=com.atlassian.jira.plugin... ] George Gastaldi closed FURNACE-40. ---------------------------------- Fix Version/s: 2.15.5.Final (was: 2.x Future) Resolution: Done > Add OSGi Manifest.mf and export all packages in furnace-api and furnace-proxy > ----------------------------------------------------------------------------- > > Key: FURNACE-40 > URL: https://issues.jboss.org/browse/FURNACE-40 > Project: Forge: Furnace > Issue Type: Feature Request > Components: Build > Affects Versions: 2.15.4.Final > Reporter: Lincoln Baxter III > Assignee: George Gastaldi > Fix For: 2.15.5.Final > > > Furnace-SE/Api/Proxy JARs should include OSGi Metadata that exports relevant types (like the proxies), everything in Furnace-API and Furnace-Proxy etc. > Ideally this should be auto-generated so that it does not go out-of-sync over time. > This should make it harder to make mistakes when embedding Furnace in OSGi bundles. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years

1
0
0 / 0

[JBoss JIRA] (FURNACE-40) Add OSGi Manifest.mf and export all packages in furnace-api and furnace-proxy

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FURNACE-40: ----------------------------------------- Summary: Add OSGi Manifest.mf and export all packages in furnace-api and furnace-proxy Key: FURNACE-40 URL: https://issues.jboss.org/browse/FURNACE-40 Project: Forge: Furnace Issue Type: Feature Request Components: Build Affects Versions: 2.15.4.Final Reporter: Lincoln Baxter III Assignee: George Gastaldi Fix For: 2.x Future Furnace-SE/Api/Proxy JARs should include OSGi Metadata that exports relevant types (like the proxies), everything in Furnace-API and Furnace-Proxy etc. Ideally this should be auto-generated so that it does not go out-of-sync over time. This should make it harder to make mistakes when embedding Furnace in OSGi bundles. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years

1
0
0 / 0

[JBoss JIRA] (FORGE-2303) Automatically generate OSGi Manifest.mf and export all packages in addonX-api

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2303?page=com.atlassian.jira.plugin... ] Work on FORGE-2303 started by George Gastaldi. ---------------------------------------------- > Automatically generate OSGi Manifest.mf and export all packages in addonX-api > ----------------------------------------------------------------------------- > > Key: FORGE-2303 > URL: https://issues.jboss.org/browse/FORGE-2303 > Project: Forge > Issue Type: Feature Request > Components: Usability > Affects Versions: 2.15.2.Final > Reporter: Lincoln Baxter III > Assignee: George Gastaldi > Fix For: 2.x Future > > > The Forge APIs (org.jboss.forge.addon:resources-api, etc) should (as a part of the build process) automatically generate an OSGi Manifest.mf file to mark all packages provided by the API as exported. > The benefit of this is that consumers in an OSGi environment will automatically export necessary addon packages/types to dependent bundles without needing to explicitly do so in their manifest. (This should prevent common bugs with OSGi exports.) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years

1
0
0 / 0

[JBoss JIRA] (FORGE-2303) Automatically generate OSGi Manifest.mf and export all packages in addonX-api

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-2303: ----------------------------------------- Summary: Automatically generate OSGi Manifest.mf and export all packages in addonX-api Key: FORGE-2303 URL: https://issues.jboss.org/browse/FORGE-2303 Project: Forge Issue Type: Feature Request Components: Usability Affects Versions: 2.15.2.Final Reporter: Lincoln Baxter III Assignee: George Gastaldi Fix For: 2.x Future The Forge APIs (org.jboss.forge.addon:resources-api, etc) should (as a part of the build process) automatically generate an OSGi Manifest.mf file to mark all packages provided by the API as exported. The benefit of this is that consumers in an OSGi environment will automatically export necessary addon packages/types to dependent bundles without needing to explicitly do so in their manifest. (This should prevent common bugs with OSGi exports.) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years

1
0
0 / 0

[JBoss JIRA] (FURNACE-39) Furnace API and Proxy jars are being bundled in the container impls

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FURNACE-39?page=com.atlassian.jira.plugin... ] George Gastaldi closed FURNACE-39. ---------------------------------- Resolution: Done > Furnace API and Proxy jars are being bundled in the container impls > ------------------------------------------------------------------- > > Key: FURNACE-39 > URL: https://issues.jboss.org/browse/FURNACE-39 > Project: Forge: Furnace > Issue Type: Enhancement > Components: Container - CDI, Container - Simple > Affects Versions: 2.15.4.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Priority: Minor > Fix For: 2.15.5.Final > > > furnace-proxy should be in provided scope -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years

1
0
0 / 0

[JBoss JIRA] (FURNACE-39) Furnace API and Proxy jars are being bundled in the container impls

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FURNACE-39?page=com.atlassian.jira.plugin... ] George Gastaldi updated FURNACE-39: ----------------------------------- Priority: Minor (was: Major) > Furnace API and Proxy jars are being bundled in the container impls > ------------------------------------------------------------------- > > Key: FURNACE-39 > URL: https://issues.jboss.org/browse/FURNACE-39 > Project: Forge: Furnace > Issue Type: Enhancement > Components: Container - CDI, Container - Simple > Affects Versions: 2.15.4.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Priority: Minor > Fix For: 2.15.5.Final > > > furnace-proxy should be in provided scope -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years

1
0
0 / 0

[JBoss JIRA] (FURNACE-39) Furnace API and Proxy jars are being bundled in the container impls

by George Gastaldi (JIRA)

George Gastaldi created FURNACE-39: -------------------------------------- Summary: Furnace API and Proxy jars are being bundled in the container impls Key: FURNACE-39 URL: https://issues.jboss.org/browse/FURNACE-39 Project: Forge: Furnace Issue Type: Enhancement Components: Container - CDI, Container - Simple Affects Versions: 2.15.4.Final Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 2.15.5.Final furnace-proxy should be in provided scope -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years

1
0
0 / 0

[JBoss JIRA] (FORGE-2302) Cat -c always chops the last line

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2302?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2302. ---------------------------------- Resolution: Done > Cat -c always chops the last line > --------------------------------- > > Key: FORGE-2302 > URL: https://issues.jboss.org/browse/FORGE-2302 > Project: Forge > Issue Type: Bug > Components: UI - Shell > Affects Versions: 2.15.2.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Priority: Trivial > Fix For: 2.15.3.Final > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues April 2015