March 2015 - forge-issues - Jboss List Archives

[JBoss JIRA] (FURNACE-38) Generate addon metadata

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FURNACE-38?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FURNACE-38: ---------------------------------------- A suggestion is to have the interface name as the ArtifactId, like: {{Ui.ADDON_NAME}} > Generate addon metadata > ----------------------- > > Key: FURNACE-38 > URL: https://issues.jboss.org/browse/FURNACE-38 > Project: Forge: Furnace > Issue Type: Feature Request > Components: Maven, Test Harness > Affects Versions: 2.15.4.Final > Reporter: George Gastaldi > Fix For: 2.x Future > > > It would be nice to have a Mojo (Maven plugin) that could generate the Metadata for a given addon. Eg: > {code:java} > package org.jboss.forge.addon.ui; > import javax.annotation.Generated; > @Generated("DO NOT MODIFY THIS FILE, as it is generated automatically by the Furnace Maven Plugin") > public interface AddonMetadata > { > public static final String NAME = "org.jboss.forge.addon:ui"; > public static final String VERSION = "2.15.3-SNAPSHOT"; > public static final String ID = NAME + "," + VERSION; > } > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FURNACE-38) Generate addon metadata

by George Gastaldi (JIRA)

George Gastaldi created FURNACE-38: -------------------------------------- Summary: Generate addon metadata Key: FURNACE-38 URL: https://issues.jboss.org/browse/FURNACE-38 Project: Forge: Furnace Issue Type: Feature Request Components: Maven, Test Harness Affects Versions: 2.15.4.Final Reporter: George Gastaldi Fix For: 2.x Future It would be nice to have a Mojo (Maven plugin) that could generate the Metadata for a given addon. Eg: {code:java} package org.jboss.forge.addon.ui; import javax.annotation.Generated; @Generated("DO NOT MODIFY THIS FILE, as it is generated automatically by the Furnace Maven Plugin") public interface AddonMetadata { public static final String NAME = "org.jboss.forge.addon:ui"; public static final String VERSION = "2.15.3-SNAPSHOT"; public static final String ID = NAME + "," + VERSION; } {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FURNACE-37) Include the cause in "Test runner could not locate test class..."

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FURNACE-37?page=com.atlassian.jira.plugin... ] George Gastaldi updated FURNACE-37: ----------------------------------- Component/s: Test Harness > Include the cause in "Test runner could not locate test class..." > ----------------------------------------------------------------- > > Key: FURNACE-37 > URL: https://issues.jboss.org/browse/FURNACE-37 > Project: Forge: Furnace > Issue Type: Feature Request > Components: Test Harness > Affects Versions: 2.15.4.Final > Reporter: Ondrej Zizka > Priority: Critical > Fix For: 2.x Future > > > There are two ways to get the exception ""Test runner could not locate test class...". Both have the same text, only differ by cause. > For better readability, the earlier could include the FQCN and message of the cause. > How it is now: > {code:java} > throw new IllegalStateException( > "Test runner could not locate test class [" + testClassName + "] in any deployed Addon.", > e.getCause()); > {code} > Thanks for considering. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FURNACE-37) Include the cause in "Test runner could not locate test class..."

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FURNACE-37?page=com.atlassian.jira.plugin... ] George Gastaldi moved FORGE-2288 to FURNACE-37: ----------------------------------------------- Project: Forge: Furnace (was: Forge) Key: FURNACE-37 (was: FORGE-2288) Affects Version/s: 2.15.4.Final (was: 2.15.2.Final) Fix Version/s: 2.x Future (was: 2.x Future) > Include the cause in "Test runner could not locate test class..." > ----------------------------------------------------------------- > > Key: FURNACE-37 > URL: https://issues.jboss.org/browse/FURNACE-37 > Project: Forge: Furnace > Issue Type: Feature Request > Affects Versions: 2.15.4.Final > Reporter: Ondrej Zizka > Priority: Critical > Fix For: 2.x Future > > > There are two ways to get the exception ""Test runner could not locate test class...". Both have the same text, only differ by cause. > For better readability, the earlier could include the FQCN and message of the cause. > How it is now: > {code:java} > throw new IllegalStateException( > "Test runner could not locate test class [" + testClassName + "] in any deployed Addon.", > e.getCause()); > {code} > Thanks for considering. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2288) Include the cause in "Test runner could not locate test class..."

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2288?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-2288: ----------------------------------- Priority: Critical (was: Major) > Include the cause in "Test runner could not locate test class..." > ----------------------------------------------------------------- > > Key: FORGE-2288 > URL: https://issues.jboss.org/browse/FORGE-2288 > Project: Forge > Issue Type: Feature Request > Affects Versions: 2.15.2.Final > Reporter: Ondrej Zizka > Priority: Critical > Fix For: 2.x Future > > > There are two ways to get the exception ""Test runner could not locate test class...". Both have the same text, only differ by cause. > For better readability, the earlier could include the FQCN and message of the cause. > How it is now: > {code:java} > throw new IllegalStateException( > "Test runner could not locate test class [" + testClassName + "] in any deployed Addon.", > e.getCause()); > {code} > Thanks for considering. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2288) Include the cause in "Test runner could not locate test class..."

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2288?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-2288: ----------------------------------- Affects Version/s: 2.15.2.Final > Include the cause in "Test runner could not locate test class..." > ----------------------------------------------------------------- > > Key: FORGE-2288 > URL: https://issues.jboss.org/browse/FORGE-2288 > Project: Forge > Issue Type: Feature Request > Affects Versions: 2.15.2.Final > Reporter: Ondrej Zizka > Priority: Critical > Fix For: 2.x Future > > > There are two ways to get the exception ""Test runner could not locate test class...". Both have the same text, only differ by cause. > For better readability, the earlier could include the FQCN and message of the cause. > How it is now: > {code:java} > throw new IllegalStateException( > "Test runner could not locate test class [" + testClassName + "] in any deployed Addon.", > e.getCause()); > {code} > Thanks for considering. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2288) Include the cause in "Test runner could not locate test class..."

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2288?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-2288: ----------------------------------- Fix Version/s: 2.x Future > Include the cause in "Test runner could not locate test class..." > ----------------------------------------------------------------- > > Key: FORGE-2288 > URL: https://issues.jboss.org/browse/FORGE-2288 > Project: Forge > Issue Type: Feature Request > Affects Versions: 2.15.2.Final > Reporter: Ondrej Zizka > Priority: Critical > Fix For: 2.x Future > > > There are two ways to get the exception ""Test runner could not locate test class...". Both have the same text, only differ by cause. > For better readability, the earlier could include the FQCN and message of the cause. > How it is now: > {code:java} > throw new IllegalStateException( > "Test runner could not locate test class [" + testClassName + "] in any deployed Addon.", > e.getCause()); > {code} > Thanks for considering. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2295) Upgrade to Furnace 2.15.4.Final

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2295?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2295. ---------------------------------- Resolution: Done > Upgrade to Furnace 2.15.4.Final > ------------------------------- > > Key: FORGE-2295 > URL: https://issues.jboss.org/browse/FORGE-2295 > Project: Forge > Issue Type: Component Upgrade > Components: Furnace (Container), UI - NetBeans > Affects Versions: 2.15.2.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.15.3.Final > > > This is needed to upgrade the Netbeans plugin to a single NBM (See FURNACE-36) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2299) No such child when doing a --targetClass

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2299?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2299. ---------------------------------- Fix Version/s: 2.15.3.Final (was: 2.x Future) Resolution: Done > No such child when doing a --targetClass > ---------------------------------------- > > Key: FORGE-2299 > URL: https://issues.jboss.org/browse/FORGE-2299 > Project: Forge > Issue Type: Bug > Components: UI - API > Affects Versions: 2.15.2.Final > Reporter: Antonio Goncalves > Assignee: George Gastaldi > Priority: Critical > Fix For: 2.15.3.Final > > > The {{JavaAddAnnotationCommandImpl}} command adds an annotation to an existing class : > {code} > @FacetConstraint(JavaSourceFacet.class) > public class JavaAddAnnotationCommandImpl extends AbstractProjectCommand implements JavaAddAnnotationCommand > { > @Inject > @WithAttributes(label = "Target Class", description = "The class where the annotation will be added", required = true, type = InputType.DROPDOWN) > private UISelectOne<JavaResource> targetClass; > {code} > But when the parameter {{targetClass}} is used, there is a {{no such child}} > {code} > [bin]$ project-new --named test > ***SUCCESS*** Project named 'test' has been created. > [test]$ java-new-class --named MyClass > ***SUCCESS*** Class org.test.MyClass was created > [MyClass.java]$ java-add-annotation --annotation java.lang.annotation.Documented --targetClass org.test.MyClass > Exception when parsing/running: java-add-annotation --annotation java.lang.annotation.Documented --targetClass org.test.MyClass , no such child: org.test.MyClass > ***INFO*** (type "export VERBOSE=true" to enable stack traces) > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2299) No such child when doing a --targetClass

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2299?page=com.atlassian.jira.plugin... ] Work on FORGE-2299 started by George Gastaldi. ---------------------------------------------- > No such child when doing a --targetClass > ---------------------------------------- > > Key: FORGE-2299 > URL: https://issues.jboss.org/browse/FORGE-2299 > Project: Forge > Issue Type: Bug > Components: UI - API > Affects Versions: 2.15.2.Final > Reporter: Antonio Goncalves > Assignee: George Gastaldi > Priority: Critical > Fix For: 2.x Future > > > The {{JavaAddAnnotationCommandImpl}} command adds an annotation to an existing class : > {code} > @FacetConstraint(JavaSourceFacet.class) > public class JavaAddAnnotationCommandImpl extends AbstractProjectCommand implements JavaAddAnnotationCommand > { > @Inject > @WithAttributes(label = "Target Class", description = "The class where the annotation will be added", required = true, type = InputType.DROPDOWN) > private UISelectOne<JavaResource> targetClass; > {code} > But when the parameter {{targetClass}} is used, there is a {{no such child}} > {code} > [bin]$ project-new --named test > ***SUCCESS*** Project named 'test' has been created. > [test]$ java-new-class --named MyClass > ***SUCCESS*** Class org.test.MyClass was created > [MyClass.java]$ java-add-annotation --annotation java.lang.annotation.Documented --targetClass org.test.MyClass > Exception when parsing/running: java-add-annotation --annotation java.lang.annotation.Documented --targetClass org.test.MyClass , no such child: org.test.MyClass > ***INFO*** (type "export VERBOSE=true" to enable stack traces) > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues March 2015