June 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1889) Upgrade to Roaster 2.6.0.Final

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1889?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1889: ----------------------------------- Summary: Upgrade to Roaster 2.6.0.Final (was: Upgrade to Roaster 2.5.2.Final) > Upgrade to Roaster 2.6.0.Final > ------------------------------ > > Key: FORGE-1889 > URL: https://issues.jboss.org/browse/FORGE-1889 > Project: Forge > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Parsers / File Manipulation > Affects Versions: 2.6.0.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.x Future > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1895) Furnace maven plugin should provide an option to clean the target repository before deploying

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1895?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1895. ---------------------------------- Assignee: George Gastaldi Fix Version/s: 2.7.0.Final (was: 2.x Future) Resolution: Done Created overwrite flag > Furnace maven plugin should provide an option to clean the target repository before deploying > --------------------------------------------------------------------------------------------- > > Key: FORGE-1895 > URL: https://issues.jboss.org/browse/FORGE-1895 > Project: Forge > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Addon Manager > Affects Versions: 2.6.0.Final > Reporter: Lincoln Baxter III > Assignee: George Gastaldi > Fix For: 2.7.0.Final > > > This would prevent dirty left-over artifacts lingering in the repository. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1895) Furnace maven plugin should provide an option to clean the target repository before deploying

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-1895: ----------------------------------------- Summary: Furnace maven plugin should provide an option to clean the target repository before deploying Key: FORGE-1895 URL: https://issues.jboss.org/browse/FORGE-1895 Project: Forge Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Addon Manager Affects Versions: 2.6.0.Final Reporter: Lincoln Baxter III Fix For: 2.x Future This would prevent dirty left-over artifacts lingering in the repository. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1881) Add support for Furnace.get()

by Matej Briskar (JIRA)

[ https://issues.jboss.org/browse/FORGE-1881?page=com.atlassian.jira.plugin... ] Matej Briskar reassigned FORGE-1881: ------------------------------------ Assignee: Matej Briskar > Add support for Furnace.get() > ----------------------------- > > Key: FORGE-1881 > URL: https://issues.jboss.org/browse/FORGE-1881 > Project: Forge > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Furnace (Container) > Affects Versions: 2.6.0.Final > Reporter: Lincoln Baxter III > Assignee: Matej Briskar > Fix For: 2.x Future > > > It should be possible to get Furnace in a "relatively safe" static way. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1894) AbstractFileResource.getChild() should not throw exceptions when children do not exist

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1894?page=com.atlassian.jira.plugin... ] Lincoln Baxter III closed FORGE-1894. ------------------------------------- Fix Version/s: 2.7.0.Final (was: 2.x Future) Resolution: Done > AbstractFileResource.getChild() should not throw exceptions when children do not exist > -------------------------------------------------------------------------------------- > > Key: FORGE-1894 > URL: https://issues.jboss.org/browse/FORGE-1894 > Project: Forge > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Resources > Affects Versions: 2.6.0.Final > Reporter: Lincoln Baxter III > Assignee: Lincoln Baxter III > Fix For: 2.7.0.Final > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1894) AbstractFileResource.getChild() should not throw exceptions when children do not exist

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-1894: ----------------------------------------- Summary: AbstractFileResource.getChild() should not throw exceptions when children do not exist Key: FORGE-1894 URL: https://issues.jboss.org/browse/FORGE-1894 Project: Forge Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Resources Affects Versions: 2.6.0.Final Reporter: Lincoln Baxter III Assignee: Lincoln Baxter III Fix For: 2.x Future -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1892) REST endpoint should also consume/produce JSon

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1892?page=com.atlassian.jira.plugin... ] Antonio Goncalves commented on FORGE-1892: ------------------------------------------ Yes, I need XML and JSon actually. It would be good to be able to specify a list of content types > REST endpoint should also consume/produce JSon > ---------------------------------------------- > > Key: FORGE-1892 > URL: https://issues.jboss.org/browse/FORGE-1892 > Project: Forge > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Scaffold > Affects Versions: 2.6.0.Final > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > When a REST endoint is generated, there is only support for XML MIMETYPE > {code} > @GET > @Produces("application/xml") > public List<Book> listAll(@QueryParam("start") Integer startPosition, @QueryParam("max") Integer maxResult) > {code} > It would be good to have both XML and JSON > {code} > @GET > @Produces({"application/xml","application/json"}) > public List<Book> listAll(@QueryParam("start") Integer startPosition, @QueryParam("max") Integer maxResult) > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1892) REST endpoint should also consume/produce JSon

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-1892?page=com.atlassian.jira.plugin... ] Vineet Reynolds commented on FORGE-1892: ---------------------------------------- The {{--contentType}} flag can be used to specify {{application/json}}, but only either content type can be specified. If I'm not wrong, you need both? > REST endpoint should also consume/produce JSon > ---------------------------------------------- > > Key: FORGE-1892 > URL: https://issues.jboss.org/browse/FORGE-1892 > Project: Forge > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Scaffold > Affects Versions: 2.6.0.Final > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > When a REST endoint is generated, there is only support for XML MIMETYPE > {code} > @GET > @Produces("application/xml") > public List<Book> listAll(@QueryParam("start") Integer startPosition, @QueryParam("max") Integer maxResult) > {code} > It would be good to have both XML and JSON > {code} > @GET > @Produces({"application/xml","application/json"}) > public List<Book> listAll(@QueryParam("start") Integer startPosition, @QueryParam("max") Integer maxResult) > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1825) Remove the overwrite flag in the Scaffold commands

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-1825?page=com.atlassian.jira.plugin... ] Vineet Reynolds closed FORGE-1825. ---------------------------------- > Remove the overwrite flag in the Scaffold commands > -------------------------------------------------- > > Key: FORGE-1825 > URL: https://issues.jboss.org/browse/FORGE-1825 > Project: Forge > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Scaffold > Affects Versions: 2.5.0.Final > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Fix For: 2.6.0.Final > > > The overwrite flag in the scaffold commands makes sense if individual overwrites to existing files could be ignored. But this is not the case, since the flag. We should therefore remove the flag. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1825) Remove the overwrite flag in the Scaffold commands

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-1825?page=com.atlassian.jira.plugin... ] Vineet Reynolds resolved FORGE-1825. ------------------------------------ Fix Version/s: 2.6.0.Final Resolution: Done Resolved: https://github.com/forge/core/commit/a36327cad4bb67f20a3051ea6e35cfb986c2... > Remove the overwrite flag in the Scaffold commands > -------------------------------------------------- > > Key: FORGE-1825 > URL: https://issues.jboss.org/browse/FORGE-1825 > Project: Forge > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Scaffold > Affects Versions: 2.5.0.Final > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Fix For: 2.6.0.Final > > > The overwrite flag in the scaffold commands makes sense if individual overwrites to existing files could be ignored. But this is not the case, since the flag. We should therefore remove the flag. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues June 2014