August 2013 - forge-issues - Jboss List Archives

[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 reassigned FORGE-896: ---------------------------------------- Assignee: Lincoln Baxter III > 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.x Future > > > 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-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 updated FORGE-896: ------------------------------------- Fix Version/s: 2.0.0.Alpha10 (was: 2.x Future) > 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-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 closed FORGE-896. ------------------------------------ Resolution: Done Done. > 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-510) Create automated routine for checking plugin version compliance of plugins in Central Plugin Index

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-510?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-510: ------------------------------------- Parent: FORGE-991 Issue Type: Sub-task (was: Task) > Create automated routine for checking plugin version compliance of plugins in Central Plugin Index > -------------------------------------------------------------------------------------------------- > > Key: FORGE-510 > URL: https://issues.jboss.org/browse/FORGE-510 > Project: Forge > Issue Type: Sub-task > Components: Plugin Repository > Affects Versions: 1.0.6.Final > Reporter: Ivan St. Ivanov > Fix For: 2.x Future > > > Create a routine, executed by the build server, that checks a predefined set of Forge plugins for version consistency with Forge core. In order to satisfy this check, for each major version of the core there should be at least one plugin branch or tag that specifies the same major version. If the check fails, the plugin author should receive an email asking them to fix the inconcistency. -- 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-721) When using scheduling can't change default directory from com.example

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-721?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III closed FORGE-721. ------------------------------------ Resolution: Out of Date Reporter did not respond to request for details. > When using scheduling can't change default directory from com.example > --------------------------------------------------------------------- > > Key: FORGE-721 > URL: https://issues.jboss.org/browse/FORGE-721 > Project: Forge > Issue Type: Bug > Components: Scaffold > Affects Versions: 1.1.2.Final > Environment: Forge 1.1.2 on MAC with JDK 1.7 > Reporter: Robb Greathouse > Fix For: 1.x Future > > > When I use forge to create a project this is under a directory structure other than com.example.[project name] for example com.jboss is still creates the view and rest components under com.example -- 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-184) Add 'plugins register-plugin', 'update-registration' style commands for updating the central plugin repository index

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-184?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-184: ------------------------------------- Parent: FORGE-991 Issue Type: Sub-task (was: Feature Request) > Add 'plugins register-plugin', 'update-registration' style commands for updating the central plugin repository index > -------------------------------------------------------------------------------------------------------------------- > > Key: FORGE-184 > URL: https://issues.jboss.org/browse/FORGE-184 > Project: Forge > Issue Type: Sub-task > Components: Brainstorming, Builtin Plugins, Plugin Repository > Affects Versions: 1.0.0.Alpha4 > Reporter: Lincoln Baxter III > Fix For: 2.x Future > > > Forge should provide commands to simplify the process of registering a plugin with the central repository. > The command should verify all metadata by attempting to build/install the plugin before allowing an update request to be sent. -- 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-724) FieldPlugin could be used without JPA

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-724?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III closed FORGE-724. ------------------------------------ Resolution: Won't Fix I think the better solution here is to create a field plugin that does not do anything with JPA, then re-use that in the JPA plugin which will simply annotate the appropriate fields/methods after the FieldPlugin has done its work. This is easier to solve in Forge 2 than in Forge 1. > FieldPlugin could be used without JPA > ------------------------------------- > > Key: FORGE-724 > URL: https://issues.jboss.org/browse/FORGE-724 > Project: Forge > Issue Type: Enhancement > Components: Builtin Plugins > Affects Versions: 1.1.3.Final > Reporter: George Gastaldi > Labels: starter > Fix For: 2.x Future > > > The FieldPlugin could be used for creating simple fields on JavaBeans, instead of using it only if the PersistenceFacet is enabled. -- 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-724) FieldPlugin could be used without JPA

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-724?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-724: ------------------------------------- Fix Version/s: 2.x Future (was: 1.x Future) > FieldPlugin could be used without JPA > ------------------------------------- > > Key: FORGE-724 > URL: https://issues.jboss.org/browse/FORGE-724 > Project: Forge > Issue Type: Enhancement > Components: Builtin Plugins > Affects Versions: 1.1.3.Final > Reporter: George Gastaldi > Labels: starter > Fix For: 2.x Future > > > The FieldPlugin could be used for creating simple fields on JavaBeans, instead of using it only if the PersistenceFacet is enabled. -- 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-569) Skipping an installed plugin when asking to install a plugin or provide a test for installed plugins

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-569?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III closed FORGE-569. ------------------------------------ Fix Version/s: (was: 1.x Future) Resolution: Won't Fix Since we are using a completely new addon distribution mechanism in Forge 2 that addresses this problem (only snapshot addons are overwritten, other versions are upgraded and can live side-by-side), I don't think we will be fixing this issue in Forge 1. > Skipping an installed plugin when asking to install a plugin or provide a test for installed plugins > ---------------------------------------------------------------------------------------------------- > > Key: FORGE-569 > URL: https://issues.jboss.org/browse/FORGE-569 > Project: Forge > Issue Type: Enhancement > Components: Usability > Affects Versions: 1.0.4.Final > Reporter: Jason Porter > > When you install a plugin there should be a way to tell it to skip the install if the plugin has been installed already, or provide a command to test for the existence of a 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] (FORGEPLUGINS-128) AngularJS scaffold facet is deactivated on exit from the project context

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-128?page=com.atlassian.jira.... ] Vineet Reynolds closed FORGEPLUGINS-128. ---------------------------------------- Resolution: Done > AngularJS scaffold facet is deactivated on exit from the project context > ------------------------------------------------------------------------ > > Key: FORGEPLUGINS-128 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-128 > Project: Forge Plugins > Issue Type: Bug > Components: AngularJS Scaffold > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > > After incorporating the fix for FORGEPLUGINS-124, the following behavior is observed. Exiting from the project context either by changing the directory or by restarting Forge, the AngularJS facet installed in the project is lost and the scaffolding needs to be setup once again. > This is due to the project-scoped configuration not being activated before invocation of {{Facet.isInstalled()}}. -- 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