March 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1673) javax.sound.* classes cannot be resolved using ServiceLoader

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1673?page=com.atlassian.jira.plugin... ] Lincoln Baxter III closed FORGE-1673. ------------------------------------- Assignee: Lincoln Baxter III Resolution: Done Implemented by granting system classloader path access to META-INF/services > javax.sound.* classes cannot be resolved using ServiceLoader > ------------------------------------------------------------ > > Key: FORGE-1673 > URL: https://issues.jboss.org/browse/FORGE-1673 > Project: Forge > Issue Type: Feature Request > Components: Furnace (Container) > Affects Versions: 2.1.1.Final > Reporter: Lincoln Baxter III > Assignee: Lincoln Baxter III > Fix For: 2.2.0.Final > > -- 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

1
0
0 / 0

[JBoss JIRA] (FORGE-1673) javax.sound.* classes cannot be resolved using ServiceLoader

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-1673: ----------------------------------------- Summary: javax.sound.* classes cannot be resolved using ServiceLoader Key: FORGE-1673 URL: https://issues.jboss.org/browse/FORGE-1673 Project: Forge Issue Type: Feature Request Components: Furnace (Container) Affects Versions: 2.1.1.Final Reporter: Lincoln Baxter III Fix For: 2.2.0.Final -- 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

1
0
0 / 0

[JBoss JIRA] (FORGE-1666) Add BOM to new addon projects

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1666?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1666. ---------------------------------- Assignee: George Gastaldi Fix Version/s: 2.1.2.Final (was: 2.x Future) Resolution: Done > Add BOM to new addon projects > ----------------------------- > > Key: FORGE-1666 > URL: https://issues.jboss.org/browse/FORGE-1666 > Project: Forge > Issue Type: Enhancement > Components: Addon Development > Affects Versions: 2.1.1.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.1.2.Final > > > {{Project:New}} of type {{Forge Addon}} should add the BOM as a managed imported scope: > - in the addon project when using the simple layout > - in the parent project of the addon when using the complex layout -- 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

1
0
0 / 0

[JBoss JIRA] (FORGE-1566) Create a command to setup addon dependencies

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1566?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1566. ---------------------------------- Fix Version/s: 2.1.2.Final (was: 2.1.0.Final) Resolution: Done > Create a command to setup addon dependencies > -------------------------------------------- > > Key: FORGE-1566 > URL: https://issues.jboss.org/browse/FORGE-1566 > Project: Forge > Issue Type: Feature Request > Components: Addon Manager > Affects Versions: 2.0.0.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.1.2.Final > > > When you need an addon to depend on another addon, the following operations should be made: > - Add the addon to the parent's dependencyManagement section > - Add to the addon project > - Add to the api/impl/tests projects if available -- 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

1
0
0 / 0

[JBoss JIRA] (FORGE-1566) Create a command to setup addon dependencies

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1566?page=com.atlassian.jira.plugin... ] George Gastaldi reopened FORGE-1566: ------------------------------------ > Create a command to setup addon dependencies > -------------------------------------------- > > Key: FORGE-1566 > URL: https://issues.jboss.org/browse/FORGE-1566 > Project: Forge > Issue Type: Feature Request > Components: Addon Manager > Affects Versions: 2.0.0.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.1.0.Final > > > When you need an addon to depend on another addon, the following operations should be made: > - Add the addon to the parent's dependencyManagement section > - Add to the addon project > - Add to the api/impl/tests projects if available -- 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

1
0
0 / 0

[JBoss JIRA] (FORGE-877) Addon sub-module is not imported into eclipse workspace

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-877?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-877: ---------------------------------- Fix Version/s: 2.x Future > Addon sub-module is not imported into eclipse workspace > ------------------------------------------------------- > > Key: FORGE-877 > URL: https://issues.jboss.org/browse/FORGE-877 > Project: Forge > Issue Type: Bug > Components: UI - Eclipse > Affects Versions: 2.0.0.Alpha3 > Reporter: George Gastaldi > Fix For: 2.0.0.Alpha4, 2.x Future > > > When a new forge addon is created using the "New Project" addon, and the option "Split project" is chosen, the addon submodule is not imported -- 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

1
0
0 / 0

[JBoss JIRA] (FORGE-877) Addon sub-module is not imported into eclipse workspace

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-877?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-877: ---------------------------------- Component/s: UI - Eclipse > Addon sub-module is not imported into eclipse workspace > ------------------------------------------------------- > > Key: FORGE-877 > URL: https://issues.jboss.org/browse/FORGE-877 > Project: Forge > Issue Type: Bug > Components: UI - Eclipse > Affects Versions: 2.0.0.Alpha3 > Reporter: George Gastaldi > Fix For: 2.0.0.Alpha4 > > > When a new forge addon is created using the "New Project" addon, and the option "Split project" is chosen, the addon submodule is not imported -- 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

1
0
0 / 0

[JBoss JIRA] (FORGE-1672) Creating a nested "Forge Addon" project can break parent POM <modules> definition

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1672?page=com.atlassian.jira.plugin... ] Lincoln Baxter III closed FORGE-1672. ------------------------------------- Assignee: Lincoln Baxter III Fix Version/s: 2.1.2.Final Resolution: Done Done. > Creating a nested "Forge Addon" project can break parent POM <modules> definition > --------------------------------------------------------------------------------- > > Key: FORGE-1672 > URL: https://issues.jboss.org/browse/FORGE-1672 > Project: Forge > Issue Type: Bug > Reporter: Lincoln Baxter III > Assignee: Lincoln Baxter III > Fix For: 2.1.2.Final > > > gastaldi: i found a bug with creating a forge-addon project inside a parent maven project > 3:50 gastaldi: we rename the folder to projectx-parent sometimes > 3:50 gastaldi: that breaks the parent pom <modules> > {code} > project-new --named foo > project-new --named bar --type addon --furnaceContainer org.jboss.forge.furnace.container:cdi,2.1.2-SNAPSHOT --splitProjects --furnaceVersion 2.1.1.Final > {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

1
0
0 / 0

[JBoss JIRA] (FORGE-877) Addon sub-module is not imported into eclipse workspace

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-877?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III commented on FORGE-877: ------------------------------------------ Reverted and re-opened this due to the fact that it causes failure to create addon project in the Shell. > Addon sub-module is not imported into eclipse workspace > ------------------------------------------------------- > > Key: FORGE-877 > URL: https://issues.jboss.org/browse/FORGE-877 > Project: Forge > Issue Type: Bug > Affects Versions: 2.0.0.Alpha3 > Reporter: George Gastaldi > Fix For: 2.0.0.Alpha4 > > > When a new forge addon is created using the "New Project" addon, and the option "Split project" is chosen, the addon submodule is not imported -- 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

1
0
0 / 0

[JBoss JIRA] (FORGE-877) Addon sub-module is not imported into eclipse workspace

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-877?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III reopened FORGE-877: -------------------------------------- Assignee: (was: George Gastaldi) > Addon sub-module is not imported into eclipse workspace > ------------------------------------------------------- > > Key: FORGE-877 > URL: https://issues.jboss.org/browse/FORGE-877 > Project: Forge > Issue Type: Bug > Affects Versions: 2.0.0.Alpha3 > Reporter: George Gastaldi > Fix For: 2.0.0.Alpha4 > > > When a new forge addon is created using the "New Project" addon, and the option "Split project" is chosen, the addon submodule is not imported -- 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

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues March 2014