August 2016 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-2307) Merge the default test configuration into one annotation

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2307?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2307. ---------------------------------- Fix Version/s: (was: 3.x Future) Resolution: Won't Do > Merge the default test configuration into one annotation > -------------------------------------------------------- > > Key: FORGE-2307 > URL: https://issues.jboss.org/browse/FORGE-2307 > Project: Forge > Issue Type: Feature Request > Reporter: Matej Briskar > Priority: Minor > > Introduce @FurnaceDeployment that will group @Deployment and @AddonDependnecies -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2152) [Developing Forge] Create a test for the Envers addon

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2152?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2152. ---------------------------------- Fix Version/s: (was: 3.x Future) Resolution: Out of Date Closing as Out of Date > [Developing Forge] Create a test for the Envers addon > ----------------------------------------------------- > > Key: FORGE-2152 > URL: https://issues.jboss.org/browse/FORGE-2152 > Project: Forge > Issue Type: Sub-task > Components: Documentation > Reporter: Ivan St. Ivanov > Assignee: Ivan St. Ivanov > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2153) [Infra] Add a script to create the PDF and HTML files out of asciidoc

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2153?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2153. ---------------------------------- Resolution: Done It's in the README: {code} ruby ASCIIDOCTOR_PDF/bin/asciidoctor-pdf FORGE_HOL_PATH/forge-hol.adoc {code} > [Infra] Add a script to create the PDF and HTML files out of asciidoc > --------------------------------------------------------------------- > > Key: FORGE-2153 > URL: https://issues.jboss.org/browse/FORGE-2153 > Project: Forge > Issue Type: Sub-task > Components: Documentation > Reporter: Ivan St. Ivanov > Assignee: Ivan St. Ivanov > Fix For: 3.x Future > > > Support Windows and Linux (bash) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1145) Maven addon needs to allow configuration of native vs. embedded

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1145?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1145. ---------------------------------- Fix Version/s: (was: 3.x Future) Resolution: Out of Date Closing as Out of Date. Reopen if still needed > Maven addon needs to allow configuration of native vs. embedded > --------------------------------------------------------------- > > Key: FORGE-1145 > URL: https://issues.jboss.org/browse/FORGE-1145 > Project: Forge > Issue Type: Feature Request > Components: Build Tools - Maven, UI - Eclipse > Affects Versions: 2.0.0.Alpha11 > Reporter: Lincoln Baxter III > > Need a way of configuring/selecting the maven version to use, either via users .profile environment by default. Other configurators should include things like inheriting the native eclipse configuration for m2e plugin, and custom config. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1605) Pack JAX-RS libraries with the application for containers that don't support JAX-RS

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1605?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1605. ---------------------------------- Fix Version/s: (was: 3.x Future) Resolution: Won't Do Closing issue as Won't Do for now. Reopen if still needed > Pack JAX-RS libraries with the application for containers that don't support JAX-RS > ----------------------------------------------------------------------------------- > > Key: FORGE-1605 > URL: https://issues.jboss.org/browse/FORGE-1605 > Project: Forge > Issue Type: Feature Request > Components: Java EE, Scaffold > Affects Versions: 2.0.0.Final > Reporter: Ivan St. Ivanov > > The JAX-RS spec is not part of the Java EE 6 Web Profile. So when an addon generates REST endpoints it should check whether the target container has support for JAX-RS and if not, it should make sure that the jars are packed together with the application (in its WEB-INF\lib directory). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2230) CoordinateBuilder should set null for empty parts of G:A:P:C:V

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2230?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2230. ---------------------------------- Fix Version/s: (was: 3.x Future) Resolution: Won't Do They should probably assume {{Optional}} at some point. Not for now as it would break backwards compatibility. Closing as Won't Do. > CoordinateBuilder should set null for empty parts of G:A:P:C:V > -------------------------------------------------------------- > > Key: FORGE-2230 > URL: https://issues.jboss.org/browse/FORGE-2230 > Project: Forge > Issue Type: Enhancement > Components: Dependencies > Affects Versions: 2.14.0.Final > Reporter: Ondrej Zizka > Labels: starter > > CoordinateBuilder, when given "G:A:::V", should set P and C to null. Having them empty strings is no good. > Consider machine-provided lists contaning: > org.foo:foo-bar:::4.1.2 > This should end with the same result as parsing > org.foo:foo-bar:4.1.2 > whereas it ends up with P and C set to empty strings, and forces the user of the api to do extra check for an empty string value. > Related: > "Malformed coordinate. Should be groupId:artifactId:[packaging]:[classifier]:[version]"); > should read > "Malformed coordinate. Should be groupId:artifactId:[packaging:[classifier:]][version]"); > And javadoc's > <groupId>:<artifactId>[:<packaging>[:<classifier>]]:<version> > should read > <groupId>:<artifactId>[:<packaging>[:<classifier>]]:[<version>] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2404) 'addon-install' command should accept simpler (consolidated) arguments

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2404?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2404. ---------------------------------- Fix Version/s: 3.3.0.Final (was: 3.x Future) Assignee: George Gastaldi Resolution: Done > 'addon-install' command should accept simpler (consolidated) arguments > ---------------------------------------------------------------------- > > Key: FORGE-2404 > URL: https://issues.jboss.org/browse/FORGE-2404 > Project: Forge > Issue Type: Enhancement > Components: Addon Manager > Reporter: Lincoln Baxter III > Assignee: George Gastaldi > Labels: starter > Fix For: 3.3.0.Final > > > this command should accept: > {code}addon-install org.jboss.forge.addon:core,2.x.x-SNAPSHOT > addon-install core,2.x.x-SNAPSHOT > addon-install core > {code} > instead of forcing: > {code}addon-install --groupId org.demo.addon --name demo-addon --version 1.0.0-SNAPSHOT > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2380) Brainstorming on Addon Management

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2380?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2380. ---------------------------------- Fix Version/s: (was: 3.x Future) Resolution: Done Closing it as Done > Brainstorming on Addon Management > --------------------------------- > > Key: FORGE-2380 > URL: https://issues.jboss.org/browse/FORGE-2380 > Project: Forge > Issue Type: Task > Components: Addon Manager > Affects Versions: 2.16.2.Final > Reporter: Antonio Goncalves > > One of the strength of Forge, are addons. The problem is they are spread though repositories, difficult to find, and you never know if they are supported with the latest Forge version of not. I created a JIRA about creating a Deltaspike addon ([FORGEPLUGINS-193]) and found out it was created somewhere. > In the new website, the addon page is divided in > * COMMUNITY CONTRIBUTED > * CORE ADDONS > But plenty of "community" addons are missing (deltaspike, batch...). So it would be good to have *all* the addons here. > Then, we need to know if the addon is working with the latest Forge version. The perfect situation is to ask addon developers to have 20/30% of code coverage, and have continuous integration with all the addons : update each addon to the latest Forge version, run all the tests, if the test passes or fails, the information should be available on the plugin page. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2665) addon-watch command for developer mode where we can make the forge container watch for rebuilds of addons and auto-reload them

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2665?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2665. ---------------------------------- Resolution: Done > addon-watch command for developer mode where we can make the forge container watch for rebuilds of addons and auto-reload them > ------------------------------------------------------------------------------------------------------------------------------ > > Key: FORGE-2665 > URL: https://issues.jboss.org/browse/FORGE-2665 > Project: Forge > Issue Type: Feature Request > Components: Addon Development > Affects Versions: 3.2.2.Final > Reporter: James Strachan > Assignee: George Gastaldi > Fix For: 3.x Future > > > its kinda clumsy and slow when working on a Forge addon; you try some code, rebuild it, then in your Forge app you run the remove / install commands to get the new code into your CLI install of Forge (or your web app running Forge, or your IDE etc...) > What would be cooler is if we had an 'addon-watch wildcard' command. That lets you start/stop watching addons that have SNAPSHOT versions. Even ignore the wildcard and just watch all SNAPSHOT addons. > When watching, every installed addon of version SNAPSHOT, we'd watch ~/.m2/repository for the builds of the addons. If you then rebuild an addon, it'd reload the addon automatically (remove it first, then re-install it)! > This would make it much quicker and simpler to try things out! Its especially painful when testing out changes to Forge commands in a web app (e.g. hawtio-forge) as you typically need to build the addons then rebuild the addon repo then rebuild/restart the web app etc! > So this simple approach would help folks get more rapid feedback on building any addon - however you run them (CLI, web, IDE) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ROASTER-109) Method static modifier not being parsed correctly

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/ROASTER-109?page=com.atlassian.jira.plugi... ] George Gastaldi deleted ROASTER-109: ------------------------------------ > Method static modifier not being parsed correctly > ------------------------------------------------- > > Key: ROASTER-109 > URL: https://issues.jboss.org/browse/ROASTER-109 > Project: Roaster > Issue Type: Bug > Reporter: Kevin Mian Kraiker > > For some reason, when parsing a complete unit, sometimes static methods don't have the "isStatic" reading properly... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues August 2016