March 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1661) project-add-dependency ignore new scope

by Aslak Knutsen (JIRA)

Aslak Knutsen created FORGE-1661: ------------------------------------ Summary: project-add-dependency ignore new scope Key: FORGE-1661 URL: https://issues.jboss.org/browse/FORGE-1661 Project: Forge Issue Type: Bug Components: Projects Affects Versions: 2.1.1.Final Reporter: Aslak Knutsen Assignee: Aslak Knutsen Fix For: 2.x Future When you have a bom defined in depmgm that include the dep you're trying to add as a direct dependency, you will get the question: This is a managed resource, would you like to include this version? When you attempt to add a reference to a managed dependency in a given scope, the new scope is ignored if you say yes to not override the managed version. Take Arquillian as an example, arquillian-bom is defined in depmgm. project-add-dependencies org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-depchain::test:pom Do you like to use managed version? Y Results in: org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-depchain:::pom Resolver is now in Compile scope. Wanted Test scope. -- 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 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1660) Add project-has(-managed)-dependencies command

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1660?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1660: ----------------------------------- Status: Closed (was: Pull Request Sent) Fix Version/s: 2.1.2.Final Resolution: Done Merged, thanks! > Add project-has(-managed)-dependencies command > ---------------------------------------------- > > Key: FORGE-1660 > URL: https://issues.jboss.org/browse/FORGE-1660 > Project: Forge > Issue Type: Feature Request > Components: Projects > Affects Versions: 2.1.1.Final > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: 2.1.2.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 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1660) Add project-has(-managed)-dependencies command

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/FORGE-1660?page=com.atlassian.jira.plugin... ] Aslak Knutsen updated FORGE-1660: --------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/forge/core/pull/401 > Add project-has(-managed)-dependencies command > ---------------------------------------------- > > Key: FORGE-1660 > URL: https://issues.jboss.org/browse/FORGE-1660 > Project: Forge > Issue Type: Feature Request > Components: Projects > Affects Versions: 2.1.1.Final > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > -- 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 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1660) Add project-has(-managed)-dependencies command

by Aslak Knutsen (JIRA)

Aslak Knutsen created FORGE-1660: ------------------------------------ Summary: Add project-has(-managed)-dependencies command Key: FORGE-1660 URL: https://issues.jboss.org/browse/FORGE-1660 Project: Forge Issue Type: Feature Request Components: Projects Affects Versions: 2.1.1.Final Reporter: Aslak Knutsen -- 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 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1660) Add project-has(-managed)-dependencies command

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/FORGE-1660?page=com.atlassian.jira.plugin... ] Aslak Knutsen reassigned FORGE-1660: ------------------------------------ Assignee: Aslak Knutsen > Add project-has(-managed)-dependencies command > ---------------------------------------------- > > Key: FORGE-1660 > URL: https://issues.jboss.org/browse/FORGE-1660 > Project: Forge > Issue Type: Feature Request > Components: Projects > Affects Versions: 2.1.1.Final > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > -- 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 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1644) Addons should have a storage area

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/FORGE-1644?page=com.atlassian.jira.plugin... ] Aslak Knutsen commented on FORGE-1644: -------------------------------------- The AddonRepository is associated with a Single Addon in a specific version isn't it? How would you deal with stored data across Addon versions? How do you get access to your own Addon info? > Addons should have a storage area > --------------------------------- > > Key: FORGE-1644 > URL: https://issues.jboss.org/browse/FORGE-1644 > Project: Forge > Issue Type: Feature Request > Components: Furnace (Container) > Affects Versions: 2.1.1.Final > Reporter: George Gastaldi > > If would be nice if each addon had a storage area (not temporary) to store files relevant to the addon execution. This area could live under {{USER_HOME/.forge/store/addon_name}}. > Here is an example code on how to access it: > {code} > @Inject Addon addon; > File storageArea = addon.getStorageDirectory(); > {code} > Examples: > - The current config.xml file could be in the storage directory of the configuration addon > - The shell specific files (export, alias, history) could be in the storage directory of the shell addon -- 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 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1656) Migrate core addons to simple container

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1656?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1656: ----------------------------------- Description: Add here the addons that could be changed to use the simple container (does not use CDI explicit features) > Migrate core addons to simple container > --------------------------------------- > > Key: FORGE-1656 > URL: https://issues.jboss.org/browse/FORGE-1656 > Project: Forge > Issue Type: Enhancement > Components: Builtin Plugins > Affects Versions: 2.1.1.Final > Reporter: George Gastaldi > Fix For: 2.x Future > > > Add here the addons that could be changed to use the simple container (does not use CDI explicit features) -- 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 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1659) Migrate templates addon to simple container

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1659?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1659: ----------------------------------- Description: Add here the addons that could be changed to use the simple container (does not use CDI explicit features) > Migrate templates addon to simple container > ------------------------------------------- > > Key: FORGE-1659 > URL: https://issues.jboss.org/browse/FORGE-1659 > Project: Forge > Issue Type: Sub-task > Components: Templates > Affects Versions: 2.1.1.Final > Reporter: George Gastaldi > Fix For: 2.x Future > > > Add here the addons that could be changed to use the simple container (does not use CDI explicit features) -- 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 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1659) Migrate templates addon to simple container

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1659?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1659: ----------------------------------- Description: Add here the addons that could be changed to use the simple container (does not use CDI explicit features) > Migrate templates addon to simple container > ------------------------------------------- > > Key: FORGE-1659 > URL: https://issues.jboss.org/browse/FORGE-1659 > Project: Forge > Issue Type: Sub-task > Components: Templates > Affects Versions: 2.1.1.Final > Reporter: George Gastaldi > Fix For: 2.x Future > > > Add here the addons that could be changed to use the simple container (does not use CDI explicit features) -- 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 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1659) Migrate templates addon to simple container

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1659: -------------------------------------- Summary: Migrate templates addon to simple container Key: FORGE-1659 URL: https://issues.jboss.org/browse/FORGE-1659 Project: Forge Issue Type: Sub-task Components: Templates Affects Versions: 2.1.1.Final Reporter: George Gastaldi Fix For: 2.x Future -- 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 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues March 2014