October 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-2057) Attributes of Mapped Superclass should be protected and not private

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-2057: ---------------------------------------- Summary: Attributes of Mapped Superclass should be protected and not private Key: FORGE-2057 URL: https://issues.jboss.org/browse/FORGE-2057 Project: Forge Issue Type: Feature Request Components: Java EE Affects Versions: 2.12.0.Final Reporter: Antonio Goncalves When creating a new Mapped Superclass, attributes are private. So the following command : {code} jpa-new-mapped-superclass --named Person ; jpa-new-field --named firstName --length 50 --columnName first_name ; {code} Will generate : {code} @MappedSuperclass public class Person { @Column(length = 50, name = "first_name") private String firstName; ... } {code} Because mapped superclass are to be inherited, it would be better to have protected attributes so subclasses could use the attributes {code} @MappedSuperclass public class Person { @Column(length = 50, name = "first_name") protected String firstName; ... } {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2057) Attributes of Mapped Superclass should be protected and not private

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-2057?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-2057: ------------------------------------- Fix Version/s: 2.x Future > Attributes of Mapped Superclass should be protected and not private > ------------------------------------------------------------------- > > Key: FORGE-2057 > URL: https://issues.jboss.org/browse/FORGE-2057 > Project: Forge > Issue Type: Feature Request > Components: Java EE > Affects Versions: 2.12.0.Final > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > When creating a new Mapped Superclass, attributes are private. So the following command : > {code} > jpa-new-mapped-superclass --named Person ; > jpa-new-field --named firstName --length 50 --columnName first_name ; > {code} > Will generate : > {code} > @MappedSuperclass > public class Person { > @Column(length = 50, name = "first_name") > private String firstName; > ... > } > {code} > Because mapped superclass are to be inherited, it would be better to have protected attributes so subclasses could use the attributes > {code} > @MappedSuperclass > public class Person { > @Column(length = 50, name = "first_name") > protected String firstName; > ... > } > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2056) Commands to add and remove plugins repository into pom.xml

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-2056: ---------------------------------------- Summary: Commands to add and remove plugins repository into pom.xml Key: FORGE-2056 URL: https://issues.jboss.org/browse/FORGE-2056 Project: Forge Issue Type: Sub-task Components: UI - Shell Affects Versions: 2.12.0.Final Reporter: Antonio Goncalves Fix For: 2.x Future Today we have commands to add/remove dependencies into a `pom.xml` : {code} project-add-repository project-remove-repository {code} We need to same functionnalites but for plugin repositories. Commands such as : {code} project-add-plugin-repository project-remove-plugin-repository {code} So a command like this : {code} project-add-plugin-repository --named jboss-public --url https://repository.jboss.org/nexus/content/groups/public/ ; {code} Would add the following to the {{pom.xml}} : {code} <pluginRepositories > <pluginRepository > <id>jboss-public</id> <url>https://repository.jboss.org/nexus/content/groups/public/</url> </pluginRepository > </pluginRepositories > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2019) Compilation errors in JDK 1.8.0_20

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2019?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-2019: ---------------------------------------- I am not sure this is a good idea as it defeats the purpose of modularity and container isolation on each addon (Eg: addons using cdi container should not care about other containers). > Compilation errors in JDK 1.8.0_20 > ---------------------------------- > > Key: FORGE-2019 > URL: https://issues.jboss.org/browse/FORGE-2019 > Project: Forge > Issue Type: Bug > Components: Forge Build > Affects Versions: 2.10.1.Final > Environment: Fedora 20 > java version "1.8.0_20" > Java(TM) SE Runtime Environment (build 1.8.0_20-b26) > Java HotSpot(TM) 64-Bit Server VM (build 25.20-b23, mixed mode) > Reporter: George Gastaldi > Priority: Blocker > Fix For: 2.x Future > > > {code} > [ERROR] /usr/local/workspace/forge-core-2.0/shell/impl/src/main/java/org/jboss/forge/addon/shell/command/CatCommand.java:[89,27] cannot access org.jboss.forge.furnace.container.simple.Service > class file for org.jboss.forge.furnace.container.simple.Service not found > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on project javaee-impl: Compilation failure > [ERROR] /usr/local/workspace/forge-core-2.0/javaee/impl/src/main/java/org/jboss/forge/addon/javaee/rest/generator/ResourceGeneratorUtil.java:[42,65] cannot access org.jboss.forge.furnace.container.simple.Service > [ERROR] class file for org.jboss.forge.furnace.container.simple.Service not found > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2019) Compilation errors in JDK 1.8.0_20

by Adam Siemion (JIRA)

[ https://issues.jboss.org/browse/FORGE-2019?page=com.atlassian.jira.plugin... ] Adam Siemion commented on FORGE-2019: ------------------------------------- I have also encountered this issue. How about just adding the org.jboss.forge.furnace.container:simple-api maven dependency with the provided scope, this fixes the issue: {code} diff --git a/javaee/impl/pom.xml b/javaee/impl/pom.xml index 231bc20..6e4747f 100644 --- a/javaee/impl/pom.xml +++ b/javaee/impl/pom.xml @@ -11,6 +11,12 @@ <dependencies> <dependency> <groupId>org.jboss.forge.furnace.container</groupId> + <artifactId>simple-api</artifactId> + <scope>provided</scope> + </dependency> + + <dependency> + <groupId>org.jboss.forge.furnace.container</groupId> <artifactId>cdi-api</artifactId> <scope>provided</scope> </dependency> diff --git a/shell/impl/pom.xml b/shell/impl/pom.xml index 26a5b4d..8fbbd28 100644 --- a/shell/impl/pom.xml +++ b/shell/impl/pom.xml @@ -12,6 +12,11 @@ <dependencies> <dependency> + <groupId>org.jboss.forge.furnace.container</groupId> + <artifactId>simple-api</artifactId> + <scope>provided</scope> + </dependency> + <dependency> <groupId>org.jboss.forge.addon</groupId> <artifactId>shell-api</artifactId> <scope>provided</scope> {code} > Compilation errors in JDK 1.8.0_20 > ---------------------------------- > > Key: FORGE-2019 > URL: https://issues.jboss.org/browse/FORGE-2019 > Project: Forge > Issue Type: Bug > Components: Forge Build > Affects Versions: 2.10.1.Final > Environment: Fedora 20 > java version "1.8.0_20" > Java(TM) SE Runtime Environment (build 1.8.0_20-b26) > Java HotSpot(TM) 64-Bit Server VM (build 25.20-b23, mixed mode) > Reporter: George Gastaldi > Priority: Blocker > Fix For: 2.x Future > > > {code} > [ERROR] /usr/local/workspace/forge-core-2.0/shell/impl/src/main/java/org/jboss/forge/addon/shell/command/CatCommand.java:[89,27] cannot access org.jboss.forge.furnace.container.simple.Service > class file for org.jboss.forge.furnace.container.simple.Service not found > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on project javaee-impl: Compilation failure > [ERROR] /usr/local/workspace/forge-core-2.0/javaee/impl/src/main/java/org/jboss/forge/addon/javaee/rest/generator/ResourceGeneratorUtil.java:[42,65] cannot access org.jboss.forge.furnace.container.simple.Service > [ERROR] class file for org.jboss.forge.furnace.container.simple.Service not found > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-171) Create an Asciidoctor Addon

by Maxime Gréau (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-171?page=com.atlassian.jira.... ] Maxime Gréau commented on FORGEPLUGINS-171: ------------------------------------------- There are more samples and documentation here : https://gist.github.com/mgreau/d5abc0a3246f1bd784a2 I plan to write a blog post about it. > Create an Asciidoctor Addon > --------------------------- > > Key: FORGEPLUGINS-171 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-171 > Project: Forge Plugins/Addons > Issue Type: Feature Request > Reporter: Maxime Gréau > > Create an addon to handle Asciidoctor configuration. > The highest value is simply bypassing the copy-and-paste task currently required to setup the pom for Asciidcotor configuration for Maven Project. > There are two distinct needs here : > 1) the first is setting up the regular plugin for processing src/main/asciidoc into one or more output formats. > 2) the second is setting up the site plugin. > Both plugins are setup in the example you can find here: > https://github.com/asciidoctor/asciidoctor-maven-example/blob/master/pom.xml > I've started to develop this addon here (early version) : > https://github.com/mgreau/asciidoctor-forge-addon > You can install it and try the feature 1) like this for example : > asciidoctor-setup --asciiDocFile manual.adoc --converter HTML5 --docWriter Max --toc left --sourceHighlighter coderay > I'd love to have your feedback about it. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1848) IDE loses defaultValue on dependent field update

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1848?page=com.atlassian.jira.plugin... ] Lincoln Baxter III closed FORGE-1848. ------------------------------------- Fix Version/s: (was: 2.x Future) Resolution: Cannot Reproduce Bug > IDE loses defaultValue on dependent field update > ------------------------------------------------ > > Key: FORGE-1848 > URL: https://issues.jboss.org/browse/FORGE-1848 > Project: Forge > Issue Type: Bug > Components: UI - Eclipse > Reporter: Aslak Knutsen > Assignee: Lincoln Baxter III > > Setup: > 2 DropDown lists, where the second DropDown's value depend on the value of the first DropDown. > Steps: > 1. Select a value from DropDown 1 > 2. DropDown 2 now has the defaultValue selected > 3. Select a new value from DropDown 1 > Step 4 - Expected: > DropDown 2 should now have the new defaultValue selected > Step 4 - Behavior: > DropDown 2's valueChoices are updated, but no defaultSelection is done > Example command: > https://github.com/aslakknutsen/plugin-arquillian/blob/8e3dfd162126cada80... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2055) Introduce caching in CommandFactory to improve performance

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2055?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2055. ---------------------------------- Fix Version/s: 2.11.1.Final Resolution: Done > Introduce caching in CommandFactory to improve performance > ---------------------------------------------------------- > > Key: FORGE-2055 > URL: https://issues.jboss.org/browse/FORGE-2055 > Project: Forge > Issue Type: Feature Request > Components: UI - API > Affects Versions: 2.11.0.Final > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Fix For: 2.11.1.Final > > > Currently {{UICommands}} are not cached, especially in scenarios where commands need to be looked up for metadata. For instance, in the Eclipse Quick Action menu, every launch of the menu, creates new {{UICommand}} instances and invokes the {{isEnabled}} method on them. We should minimize the number of times this occurs, since it is wasteful and results in slower launch times. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2055) Introduce caching in CommandFactory to improve performance

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGE-2055: -------------------------------------- Summary: Introduce caching in CommandFactory to improve performance Key: FORGE-2055 URL: https://issues.jboss.org/browse/FORGE-2055 Project: Forge Issue Type: Feature Request Components: UI - API Affects Versions: 2.11.0.Final Reporter: Vineet Reynolds Assignee: Vineet Reynolds Currently {{UICommands}} are not cached, especially in scenarios where commands need to be looked up for metadata. For instance, in the Eclipse Quick Action menu, every launch of the menu, creates new {{UICommand}} instances and invokes the {{isEnabled}} method on them. We should minimize the number of times this occurs, since it is wasteful and results in slower launch times. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ROASTER-40) Fixes in README.asciidoc

by Jeremie Bresson (JIRA)

[ https://issues.jboss.org/browse/ROASTER-40?page=com.atlassian.jira.plugin... ] Jeremie Bresson updated ROASTER-40: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/forge/roaster/pull/28 Pull request #28 contains some minor changes to the file. > Fixes in README.asciidoc > ------------------------ > > Key: ROASTER-40 > URL: https://issues.jboss.org/browse/ROASTER-40 > Project: Roaster > Issue Type: Enhancement > Reporter: Jeremie Bresson > Priority: Trivial > > The Roaster README should produce a nice output on the GitHub homepage. > https://github.com/forge/roaster > With commit 67c806a5d437eb0c931012ce560ff37ae98d4bad the file README.me has been moved to README.asciidoc and the markup-language has changed. > Related issue: ROASTER-31 (this was for the README.md file). -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues October 2014