August 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-789) Forge does not reload resources in JAR files in windows

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-789?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III closed FORGE-789. ------------------------------------ Resolution: Done Solved by manually closing the JAR files and correctly cleaning up ModuleClassLoader instances in Furnace. > Forge does not reload resources in JAR files in windows > ------------------------------------------------------- > > Key: FORGE-789 > URL: https://issues.jboss.org/browse/FORGE-789 > Project: Forge > Issue Type: Bug > Components: Usability, Windows > Reporter: John Ament > Assignee: Lincoln Baxter III > Fix For: 2.0.0.Alpha10 > > > I am building a plugin, so when I make changes to template files or code changes I rebuild my plugin using > forge source-plugin <<path to plugin>> > This does recompile the code but does not update the resources contained in that module. I have to exit the forge shell and reenter to have them apply. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-789) Forge does not reload resources in JAR files in windows

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-789?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III reassigned FORGE-789: ---------------------------------------- Assignee: Lincoln Baxter III > Forge does not reload resources in JAR files in windows > ------------------------------------------------------- > > Key: FORGE-789 > URL: https://issues.jboss.org/browse/FORGE-789 > Project: Forge > Issue Type: Bug > Components: Usability, Windows > Reporter: John Ament > Assignee: Lincoln Baxter III > Fix For: 2.0.0.Alpha10 > > > I am building a plugin, so when I make changes to template files or code changes I rebuild my plugin using > forge source-plugin <<path to plugin>> > This does recompile the code but does not update the resources contained in that module. I have to exit the forge shell and reenter to have them apply. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-789) Forge does not reload resources in JAR files in windows

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-789?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-789: ------------------------------------- Fix Version/s: 2.0.0.Alpha10 (was: 1.x Future) > Forge does not reload resources in JAR files in windows > ------------------------------------------------------- > > Key: FORGE-789 > URL: https://issues.jboss.org/browse/FORGE-789 > Project: Forge > Issue Type: Bug > Components: Usability, Windows > Reporter: John Ament > Fix For: 2.0.0.Alpha10 > > > I am building a plugin, so when I make changes to template files or code changes I rebuild my plugin using > forge source-plugin <<path to plugin>> > This does recompile the code but does not update the resources contained in that module. I have to exit the forge shell and reenter to have them apply. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-896) Different Facets for main and test sources/resources

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-896?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III reopened FORGE-896: -------------------------------------- Oops. > Different Facets for main and test sources/resources > ---------------------------------------------------- > > Key: FORGE-896 > URL: https://issues.jboss.org/browse/FORGE-896 > Project: Forge > Issue Type: Enhancement > Components: Build Tools - Maven > Affects Versions: 2.0.0.Alpha3 > Reporter: George Gastaldi > Assignee: Lincoln Baxter III > Fix For: 2.0.0.Alpha10 > > > It should be possible to have a facet to create the src/main/* structure and another facet for src/test/*. > JavaSourceFacet and ResourceFacet should be split into two different interfaces to allow that -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-832) Review modules loaded as system paths in the AbstractModuleLoaderProvider

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-832?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III closed FORGE-832. ------------------------------------ Fix Version/s: 2.0.0.Alpha10 (was: 2.x Future) Resolution: Done Done. > Review modules loaded as system paths in the AbstractModuleLoaderProvider > ------------------------------------------------------------------------- > > Key: FORGE-832 > URL: https://issues.jboss.org/browse/FORGE-832 > Project: Forge > Issue Type: Task > Components: Furnace (Container) > Reporter: James Perkins > Assignee: Lincoln Baxter III > Fix For: 2.0.0.Alpha10 > > > The modules loaded in the {{org.jboss.forge.container.modules.providers.AbstractModuleSpecProvider}} should be reviewed and unneeded modules should be removed. > Currently the following paths appear as if they can be removed: > * log4j > * commons-logging > * cglib -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-852) RSS based news mechanism

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-852?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-852: ------------------------------------- Fix Version/s: 2.x Future (was: 1.x Future) > RSS based news mechanism > ------------------------ > > Key: FORGE-852 > URL: https://issues.jboss.org/browse/FORGE-852 > Project: Forge > Issue Type: Feature Request > Components: Builtin Plugins, Usability > Affects Versions: 1.2.2.Final > Reporter: Michal Matloka > Fix For: 2.x Future > > > On Forge startup user could see a message e.g. taken from Forge RSS. This could help in such situations like this: http://forge.jboss.org/news/2013/04/08/forge-update.html > Possible workflow: > run forge -> request to rss/sth -> retrieved important messages -> show to user in e.g. console > Console is a starting point. It possibly could be developed into a more generic mechanism which could be used under different interfaces. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-852) RSS based news mechanism

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-852?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-852: ------------------------------------- Parent: FORGE-991 Issue Type: Sub-task (was: Feature Request) > RSS based news mechanism > ------------------------ > > Key: FORGE-852 > URL: https://issues.jboss.org/browse/FORGE-852 > Project: Forge > Issue Type: Sub-task > Components: Builtin Plugins, Usability > Affects Versions: 1.2.2.Final > Reporter: Michal Matloka > Fix For: 2.x Future > > > On Forge startup user could see a message e.g. taken from Forge RSS. This could help in such situations like this: http://forge.jboss.org/news/2013/04/08/forge-update.html > Possible workflow: > run forge -> request to rss/sth -> retrieved important messages -> show to user in e.g. console > Console is a starting point. It possibly could be developed into a more generic mechanism which could be used under different interfaces. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-832) Review modules loaded as system paths in the AbstractModuleLoaderProvider

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-832?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III reassigned FORGE-832: ---------------------------------------- Assignee: Lincoln Baxter III > Review modules loaded as system paths in the AbstractModuleLoaderProvider > ------------------------------------------------------------------------- > > Key: FORGE-832 > URL: https://issues.jboss.org/browse/FORGE-832 > Project: Forge > Issue Type: Task > Components: Furnace (Container) > Reporter: James Perkins > Assignee: Lincoln Baxter III > Fix For: 2.x Future > > > The modules loaded in the {{org.jboss.forge.container.modules.providers.AbstractModuleSpecProvider}} should be reviewed and unneeded modules should be removed. > Currently the following paths appear as if they can be removed: > * log4j > * commons-logging > * cglib -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-847) Add an option to the DependencyResolver to resolve a single artifact (no version range)

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-847?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-847: ------------------------------------- Fix Version/s: 2.x Future (was: 1.x Future) > Add an option to the DependencyResolver to resolve a single artifact (no version range) > --------------------------------------------------------------------------------------- > > Key: FORGE-847 > URL: https://issues.jboss.org/browse/FORGE-847 > Project: Forge > Issue Type: Feature Request > Components: Build Tools - Maven > Affects Versions: 1.2.2.Final > Reporter: James Perkins > Fix For: 2.x Future > > > Currently {{org.jboss.forge.project.dependencies.DependencyResolver}} only has a option to return a list of dependencies. This results in version range query which requires the repository to have a {{maven-metadata.xml}} file. It would be useful to have something like: > {code:java} > public DependencyResource resolveArtifact(Dependency dependency) > {code} > This would allow for a specific version to be looked up. It also would have better performance when a dependency version is defined. > Currently using a repository that does not have metadata files does not work. For example http://maven.repository.redhat.com/earlyaccess/all/ cannot be used due to this issue. Which means no EAP dependencies cannot be downloaded from a Forge plugin. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-847) Add an option to the DependencyResolver to resolve a single artifact (no version range)

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-847?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-847: ------------------------------------- Labels: starter (was: ) > Add an option to the DependencyResolver to resolve a single artifact (no version range) > --------------------------------------------------------------------------------------- > > Key: FORGE-847 > URL: https://issues.jboss.org/browse/FORGE-847 > Project: Forge > Issue Type: Feature Request > Components: Build Tools - Maven > Affects Versions: 1.2.2.Final > Reporter: James Perkins > Labels: starter > Fix For: 2.x Future > > > Currently {{org.jboss.forge.project.dependencies.DependencyResolver}} only has a option to return a list of dependencies. This results in version range query which requires the repository to have a {{maven-metadata.xml}} file. It would be useful to have something like: > {code:java} > public DependencyResource resolveArtifact(Dependency dependency) > {code} > This would allow for a specific version to be looked up. It also would have better performance when a dependency version is defined. > Currently using a repository that does not have metadata files does not work. For example http://maven.repository.redhat.com/earlyaccess/all/ cannot be used due to this issue. Which means no EAP dependencies cannot be downloaded from a Forge plugin. -- 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

10 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues August 2013