July 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1004) Display a descriptive text for dependencies in the New Forge Addon dialog

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1004?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1004: -------------------------------------- Fix Version/s: 2.x Future > Display a descriptive text for dependencies in the New Forge Addon dialog > ------------------------------------------------------------------------- > > Key: FORGE-1004 > URL: https://issues.jboss.org/browse/FORGE-1004 > Project: Forge > Issue Type: Feature Request > Components: UI - API > Affects Versions: 2.0.0.Alpha5 > Reporter: Vineet Reynolds > Priority: Minor > Fix For: 2.x Future > > > It would be better to have some descriptive text that provide information about each addon that can be added as a dependency when creating a new Forge addon project. > At the moment, only the GAV of the addon is displayed which is not informative to beginners. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-997) "beans new-bean" command should better validate user input of restricted Java keywords

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-997?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-997: ------------------------------------- Fix Version/s: 1.x Future > "beans new-bean" command should better validate user input of restricted Java keywords > -------------------------------------------------------------------------------------- > > Key: FORGE-997 > URL: https://issues.jboss.org/browse/FORGE-997 > Project: Forge > Issue Type: Bug > Affects Versions: 1.3.2.Final > Environment: Eclipse Kepler + Jboss tools 4 > Reporter: Hubert Schumacher > Priority: Minor > Fix For: 1.x Future > > > forge command "beans new-bean --type abc.import.cde.ExampleJava" throws exception if type has 'import' in its path. Maybe other magic words as well?! -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-997) bean new-bean not working for all types

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-997?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III commented on FORGE-997: ------------------------------------------ Yes, I think it would be appropriate to notify the user that they are using a reserved word. > bean new-bean not working for all types > --------------------------------------- > > Key: FORGE-997 > URL: https://issues.jboss.org/browse/FORGE-997 > Project: Forge > Issue Type: Bug > Affects Versions: 1.3.2.Final > Environment: Eclipse Kepler + Jboss tools 4 > Reporter: Hubert Schumacher > > forge command "beans new-bean --type abc.import.cde.ExampleJava" throws exception if type has 'import' in its path. Maybe other magic words as well?! -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-997) "beans new-bean" command should better validate user input of restricted Java keywords

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-997?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-997: ------------------------------------- Priority: Minor (was: Major) > "beans new-bean" command should better validate user input of restricted Java keywords > -------------------------------------------------------------------------------------- > > Key: FORGE-997 > URL: https://issues.jboss.org/browse/FORGE-997 > Project: Forge > Issue Type: Bug > Affects Versions: 1.3.2.Final > Environment: Eclipse Kepler + Jboss tools 4 > Reporter: Hubert Schumacher > Priority: Minor > > forge command "beans new-bean --type abc.import.cde.ExampleJava" throws exception if type has 'import' in its path. Maybe other magic words as well?! -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-997) "beans new-bean" command should better validate user input of restricted Java keywords

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-997?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-997: ------------------------------------- Summary: "beans new-bean" command should better validate user input of restricted Java keywords (was: bean new-bean not working for all types) > "beans new-bean" command should better validate user input of restricted Java keywords > -------------------------------------------------------------------------------------- > > Key: FORGE-997 > URL: https://issues.jboss.org/browse/FORGE-997 > Project: Forge > Issue Type: Bug > Affects Versions: 1.3.2.Final > Environment: Eclipse Kepler + Jboss tools 4 > Reporter: Hubert Schumacher > > forge command "beans new-bean --type abc.import.cde.ExampleJava" throws exception if type has 'import' in its path. Maybe other magic words as well?! -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-993) Support for multi project: So forge can understand the parent and child modules resource/source

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-993?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-993: ------------------------------------- Fix Version/s: 2.x Future > Support for multi project: So forge can understand the parent and child modules resource/source > ----------------------------------------------------------------------------------------------- > > Key: FORGE-993 > URL: https://issues.jboss.org/browse/FORGE-993 > Project: Forge > Issue Type: Feature Request > Components: Plugin API > Affects Versions: 1.3.2.Final > Reporter: Rajmahendra Hegde > Fix For: 2.x Future > > > Assuming we have a maven project > MyProj - (parent) > MyProj-JPA > MyProj-Web > JPA contains JPA entities > Web contains JSF > Now user want to create a rest-services in Web or in a separate module say, MyProj-Rest. > The current forge is working completely isolated without knowing the sub-modules of the current maven project. (or its not accessing the resource/source of the sub-project its currently running. > Some time user want to create modular based development like above project structure. We need to provide a feature to access sub project resources/source also. So user can work in multi-project support environment to modularize his component. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-993) Support for multi project: So forge can understand the parent and child modules resource/source

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-993?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III commented on FORGE-993: ------------------------------------------ Yes, the Project API should probably also support sub-projects. This is an important enhancement and should probably go into Forge 2. > Support for multi project: So forge can understand the parent and child modules resource/source > ----------------------------------------------------------------------------------------------- > > Key: FORGE-993 > URL: https://issues.jboss.org/browse/FORGE-993 > Project: Forge > Issue Type: Feature Request > Components: Plugin API > Affects Versions: 1.3.2.Final > Reporter: Rajmahendra Hegde > > Assuming we have a maven project > MyProj - (parent) > MyProj-JPA > MyProj-Web > JPA contains JPA entities > Web contains JSF > Now user want to create a rest-services in Web or in a separate module say, MyProj-Rest. > The current forge is working completely isolated without knowing the sub-modules of the current maven project. (or its not accessing the resource/source of the sub-project its currently running. > Some time user want to create modular based development like above project structure. We need to provide a feature to access sub project resources/source also. So user can work in multi-project support environment to modularize his component. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-980) Failed retrieving forge modules (ClassNotFoundException: org.jboss.forge.maven.plugins.Configuration)

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-980?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III commented on FORGE-980: ------------------------------------------ Just checking in on this. We can close this issue with your usage of the "dependencies-as-resource-root" flag and module layout, right? Sorry again for the trouble. > Failed retrieving forge modules (ClassNotFoundException: org.jboss.forge.maven.plugins.Configuration) > ----------------------------------------------------------------------------------------------------- > > Key: FORGE-980 > URL: https://issues.jboss.org/browse/FORGE-980 > Project: Forge > Issue Type: Bug > Reporter: Lennart Jörelid > Attachments: jbossForgeClassLoadingDebugging_1_incorrectRejectionMaybe.png, jbossForgeClassLoadingDebugging_2_okModuleClassLoader.png, jbossForgePlugin.txt > > > https://community.jboss.org/message/825612 > Following a successful build, including unit tests for the Forge plugin, the installation (forge source-install . ) fails with a ClassNotFoundException: org.jboss.forge.maven.plugins.Configuration within the ~/.forge/runtime.log. > This class is located in forge-maven-api, which should be available for all plugins being installed. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-770) Ability to restrict ServiceRegistry and AddonRegistry services by version

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-770?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III closed FORGE-770. ------------------------------------ Resolution: Done Done! > Ability to restrict ServiceRegistry and AddonRegistry services by version > ------------------------------------------------------------------------- > > Key: FORGE-770 > URL: https://issues.jboss.org/browse/FORGE-770 > Project: Forge > Issue Type: Feature Request > Components: Container > Affects Versions: 2.0.0.Alpha1 > Reporter: Lincoln Baxter III > Assignee: Lincoln Baxter III > Fix For: 2.0.0.Alpha7 > > > Like in OSGi (shudder,) when looking up services from the ServiceRegistry, it should be possible to require that services retrieved from the ServiceRegistry be locked to a specific addon API version (via addon-dependency/classloader mapping.) > {code} > (A) -> (B, v1) > -> Service 1 > (B, v2) > -> Service 1v2 > -> Service 2v1 > {code} > A should receive only the instance of Service 1 from (B, v1) -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-770) Ability to restrict ServiceRegistry and AddonRegistry services by version

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-770?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III commented on FORGE-770: ------------------------------------------ Solved by always depending on the highest version of an installed Addon by name. The container builds graphs to represent the addon state, and links the appropriate versions. The restriction component is accomplished by a new feature called AddonView - this allows the API consumer to request a view of the configured AddonRepository instances and obtain addon instances from one or several specific repositories, while the master or ROOT view continues to operate on all repositories. > Ability to restrict ServiceRegistry and AddonRegistry services by version > ------------------------------------------------------------------------- > > Key: FORGE-770 > URL: https://issues.jboss.org/browse/FORGE-770 > Project: Forge > Issue Type: Feature Request > Components: Container > Affects Versions: 2.0.0.Alpha1 > Reporter: Lincoln Baxter III > Assignee: Lincoln Baxter III > Fix For: 2.0.0.Alpha7 > > > Like in OSGi (shudder,) when looking up services from the ServiceRegistry, it should be possible to require that services retrieved from the ServiceRegistry be locked to a specific addon API version (via addon-dependency/classloader mapping.) > {code} > (A) -> (B, v1) > -> Service 1 > (B, v2) > -> Service 1v2 > -> Service 2v1 > {code} > A should receive only the instance of Service 1 from (B, v1) -- 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, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues July 2013