October 2014 - forge-issues - Jboss List Archives

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

by Jeremie Bresson (JIRA)

Jeremie Bresson created ROASTER-40: -------------------------------------- Summary: 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)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2053) Upgrade IntelliJ Idea Plugin to Forge 2.11.0.Final

by Adam Wyłuda (JIRA)

[ https://issues.jboss.org/browse/FORGE-2053?page=com.atlassian.jira.plugin... ] Adam Wyłuda resolved FORGE-2053. -------------------------------- Resolution: Done Upgraded in 1.0.2.Final release. > Upgrade IntelliJ Idea Plugin to Forge 2.11.0.Final > -------------------------------------------------- > > Key: FORGE-2053 > URL: https://issues.jboss.org/browse/FORGE-2053 > Project: Forge > Issue Type: Enhancement > Components: UI - IntelliJ IDEA > Affects Versions: 2.11.0.Final > Reporter: Lincoln Baxter III > Assignee: Adam Wyłuda > Fix For: 2.x Future > > > {code} > 15:56:53 IllegalStateException > Cannot resolve Ambiguous dependencies: [org.jboss.forge.addon.projects.impl.ProjectFactoryImpl from addon org.jboss.forge.addon:projects,2.8.0.Final, > org.jboss.forge.addon.projects.impl.ProjectFactoryImpl from addon org.jboss.forge.addon:projects,2.8.0.Final]: Cannot resolve Ambiguous dependencies: [org.jboss.forge.addon.projects.impl.ProjectFactoryImpl from addon org.jboss.forge.addon:projects,2.8.0.Final, > org.jboss.forge.addon.projects.impl.ProjectFactoryImpl from addon org.jboss.forge.addon:projects,2.8.0.Final] > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2053) Upgrade IntelliJ Idea Plugin to Forge 2.11.0.Final

by Adam Wyłuda (JIRA)

[ https://issues.jboss.org/browse/FORGE-2053?page=com.atlassian.jira.plugin... ] Work on FORGE-2053 started by Adam Wyłuda. ------------------------------------------ > Upgrade IntelliJ Idea Plugin to Forge 2.11.0.Final > -------------------------------------------------- > > Key: FORGE-2053 > URL: https://issues.jboss.org/browse/FORGE-2053 > Project: Forge > Issue Type: Enhancement > Components: UI - IntelliJ IDEA > Affects Versions: 2.11.0.Final > Reporter: Lincoln Baxter III > Assignee: Adam Wyłuda > Fix For: 2.x Future > > > {code} > 15:56:53 IllegalStateException > Cannot resolve Ambiguous dependencies: [org.jboss.forge.addon.projects.impl.ProjectFactoryImpl from addon org.jboss.forge.addon:projects,2.8.0.Final, > org.jboss.forge.addon.projects.impl.ProjectFactoryImpl from addon org.jboss.forge.addon:projects,2.8.0.Final]: Cannot resolve Ambiguous dependencies: [org.jboss.forge.addon.projects.impl.ProjectFactoryImpl from addon org.jboss.forge.addon:projects,2.8.0.Final, > org.jboss.forge.addon.projects.impl.ProjectFactoryImpl from addon org.jboss.forge.addon:projects,2.8.0.Final] > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2054) UIInput<Boolean> is always defaulted (making requiring it as an input impossible)

by Jess Sightler (JIRA)

Jess Sightler created FORGE-2054: ------------------------------------ Summary: UIInput<Boolean> is always defaulted (making requiring it as an input impossible) Key: FORGE-2054 URL: https://issues.jboss.org/browse/FORGE-2054 Project: Forge Issue Type: Bug Components: UI - Shell Affects Versions: 2.10.1.Final Reporter: Jess Sightler If you set a UIInput<Boolean> as follows: @WithAttributes(label = "fake", required = true, description = "just put something") It will never require the user to enter a value. This is because the default is "false" even though no default was specified and the field is labelled as required. This should support tri-state booleans, and it should be possible to have a required boolean. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1029) Develop an Intellij Idea plugin as a Forge 2 UI Provider

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1029?page=com.atlassian.jira.plugin... ] Lincoln Baxter III closed FORGE-1029. ------------------------------------- Resolution: Done Awesome Job, Adam! > Develop an Intellij Idea plugin as a Forge 2 UI Provider > -------------------------------------------------------- > > Key: FORGE-1029 > URL: https://issues.jboss.org/browse/FORGE-1029 > Project: Forge > Issue Type: Feature Request > Components: UI - IntelliJ IDEA > Reporter: George Gastaldi > Assignee: Adam Wyłuda > Priority: Optional > Fix For: 2.x Future > > > This should allow us to execute Forge 2 under Idea. > GitHub repository: https://github.com/forge/intellij-idea-plugin -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2053) Upgrade IntelliJ Idea Plugin to Forge 2.11.0.Final

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-2053: ----------------------------------------- Summary: Upgrade IntelliJ Idea Plugin to Forge 2.11.0.Final Key: FORGE-2053 URL: https://issues.jboss.org/browse/FORGE-2053 Project: Forge Issue Type: Enhancement Components: UI - IntelliJ IDEA Affects Versions: 2.11.0.Final Reporter: Lincoln Baxter III Assignee: Adam Wyłuda Fix For: 2.x Future {code} 15:56:53 IllegalStateException Cannot resolve Ambiguous dependencies: [org.jboss.forge.addon.projects.impl.ProjectFactoryImpl from addon org.jboss.forge.addon:projects,2.8.0.Final, org.jboss.forge.addon.projects.impl.ProjectFactoryImpl from addon org.jboss.forge.addon:projects,2.8.0.Final]: Cannot resolve Ambiguous dependencies: [org.jboss.forge.addon.projects.impl.ProjectFactoryImpl from addon org.jboss.forge.addon:projects,2.8.0.Final, org.jboss.forge.addon.projects.impl.ProjectFactoryImpl from addon org.jboss.forge.addon:projects,2.8.0.Final] {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ROASTER-39) Support .addMethod(java.lang.reflect.Method method) and .addMethodOverride(java.lang.reflect.Method method)

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created ROASTER-39: ----------------------------------------- Summary: Support .addMethod(java.lang.reflect.Method method) and .addMethodOverride(java.lang.reflect.Method method) Key: ROASTER-39 URL: https://issues.jboss.org/browse/ROASTER-39 Project: Roaster Issue Type: Enhancement Components: API Affects Versions: 2.8.2.Final Reporter: Lincoln Baxter III Fix For: 2.x Future Should be able to easily define methods and method signatures using the java.lang.reflect.Method object as a starting point / reference. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2052) Website should support enhanced categories for documents

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-2052: ----------------------------------------- Summary: Website should support enhanced categories for documents Key: FORGE-2052 URL: https://issues.jboss.org/browse/FORGE-2052 Project: Forge Issue Type: Enhancement Components: Website Reporter: Lincoln Baxter III Fix For: 2.x Future Website needs to provide support for three dimensional document categories: Media type: (Video, Article, Blog) Source: (Community, Core) Content type: (Getting started, Tutorials, Advanced) Currently we only have the ability to show text documents from github. It would be nice to be able to embed and pop up into a modal window for videos (youtube, vimeo, etc), blogs from other sites in a modal iframe, etc. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2035) Forge does not resolve the tilde slash (~/) denoting a user home directory correctly

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-2035?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-2035: -------------------------------------- Priority: Critical (was: Major) > Forge does not resolve the tilde slash (~/) denoting a user home directory correctly > ------------------------------------------------------------------------------------ > > Key: FORGE-2035 > URL: https://issues.jboss.org/browse/FORGE-2035 > Project: Forge > Issue Type: Bug > Reporter: Sande Gilda > Priority: Critical > > When specifying the `~/` (tilde slash) in a path, the Linux "shortcut" to denote a user's home directory, Forge treats it as a character and creates a directory named '' relative to the directory where you run the 'forge' command. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2051) Installing various Java EE Facets duplicate dependencies in build descriptor

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-2051?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-2051: -------------------------------------- Description: {code} project-new --named blahhh javaee-setup --javaEEVersion 7 jpa-new-entity --named Blahhhhh {code} Even though the javax.enterprise:javaee-api is installed, individual specifications still add their own duplicate provided APIs. This should not be the case. EE* should satisfy all spec dependency requirements. {code} apply from: 'forge.gradle' apply plugin: 'war' apply plugin: 'java' repositories { mavenCentral() } version = "1.0.0-SNAPSHOT" group = "org.gradleTest" archiveName 'gradleTest' dependencies { direct group: "javax", name: "javaee-api" direct group: "org.hibernate.javax.persistence", name: "hibernate-jpa-2.0-api" direct group: "javax.enterprise", name: "cdi-api" direct group: "org.jboss.spec.javax.faces", name: "jboss-jsf-api_2.0_spec" } allprojects { dependencies { managed configuration: "compile", group: "javax", name: "javaee-api", version: "7.0" managed configuration: "import", group: "org.jboss.spec", name: "jboss-javaee-6.0", version: "3.0.2.Final", ext: "pom" managed configuration: "compile", group: "org.hibernate.javax.persistence", name: "hibernate-jpa-2.0-api", version: "1.0.1.Final" managed configuration: "compile", group: "javax.enterprise", name: "cdi-api", version: "1.0-SP4" managed configuration: "compile", group: "org.jboss.spec.javax.faces", name: "jboss-jsf-api_2.0_spec", version: "1.0.0.Final" } } {code} Should be: {code} apply from: 'forge.gradle' apply plugin: 'war' apply plugin: 'java' repositories { mavenCentral() } version = "1.0.0-SNAPSHOT" group = "org.gradleTest" archiveName 'gradleTest' dependencies { direct group: "javax", name: "javaee-api" } allprojects { dependencies { managed configuration: "compile", group: "javax", name: "javaee-api", version: "7.0" } } {code} was: {code} project-new --named blahhh javaee-setup --javaEEVersion 7 jpa-new-entity --named Blahhhhh {code} Even though the javax.enterprise:javaee-api is installed, individual specifications still add their own duplicate provided APIs. This should not be the case. EE* should satisfy all spec dependency requirements. {code} apply from: 'forge.gradle' apply plugin: 'war' apply plugin: 'java' repositories { mavenCentral() } version = "1.0.0-SNAPSHOT" group = "org.gradleTest" archiveName 'gradleTest' dependencies { direct group: "javax", name: "javaee-api" direct group: "org.hibernate.javax.persistence", name: "hibernate-jpa-2.0-api" direct group: "javax.enterprise", name: "cdi-api" direct group: "org.jboss.spec.javax.faces", name: "jboss-jsf-api_2.0_spec" } allprojects { dependencies { managed configuration: "compile", group: "javax", name: "javaee-api", version: "7.0" managed configuration: "import", group: "org.jboss.spec", name: "jboss-javaee-6.0", version: "3.0.2.Final", ext: "pom" managed configuration: "compile", group: "org.hibernate.javax.persistence", name: "hibernate-jpa-2.0-api", version: "1.0.1.Final" managed configuration: "compile", group: "javax.enterprise", name: "cdi-api", version: "1.0-SP4" managed configuration: "compile", group: "org.jboss.spec.javax.faces", name: "jboss-jsf-api_2.0_spec", version: "1.0.0.Final" } } {code} > Installing various Java EE Facets duplicate dependencies in build descriptor > ---------------------------------------------------------------------------- > > Key: FORGE-2051 > URL: https://issues.jboss.org/browse/FORGE-2051 > Project: Forge > Issue Type: Bug > Components: Builtin Plugins, Java EE > Affects Versions: 2.11.0.Final > Reporter: Lincoln Baxter III > Fix For: 2.x Future > > > {code} > project-new --named blahhh > javaee-setup --javaEEVersion 7 > jpa-new-entity --named Blahhhhh > {code} > Even though the javax.enterprise:javaee-api is installed, individual specifications still add their own duplicate provided APIs. This should not be the case. EE* should satisfy all spec dependency requirements. > {code} > apply from: 'forge.gradle' > apply plugin: 'war' > apply plugin: 'java' > repositories { > mavenCentral() > } > version = "1.0.0-SNAPSHOT" > group = "org.gradleTest" > archiveName 'gradleTest' > dependencies { > direct group: "javax", name: "javaee-api" > direct group: "org.hibernate.javax.persistence", name: "hibernate-jpa-2.0-api" > direct group: "javax.enterprise", name: "cdi-api" > direct group: "org.jboss.spec.javax.faces", name: "jboss-jsf-api_2.0_spec" > } > allprojects { > dependencies { > managed configuration: "compile", group: "javax", name: "javaee-api", version: "7.0" > managed configuration: "import", group: "org.jboss.spec", name: "jboss-javaee-6.0", version: "3.0.2.Final", ext: "pom" > managed configuration: "compile", group: "org.hibernate.javax.persistence", name: "hibernate-jpa-2.0-api", version: "1.0.1.Final" > managed configuration: "compile", group: "javax.enterprise", name: "cdi-api", version: "1.0-SP4" > managed configuration: "compile", group: "org.jboss.spec.javax.faces", name: "jboss-jsf-api_2.0_spec", version: "1.0.0.Final" > } > } > {code} > Should be: > {code} > apply from: 'forge.gradle' > apply plugin: 'war' > apply plugin: 'java' > repositories { > mavenCentral() > } > version = "1.0.0-SNAPSHOT" > group = "org.gradleTest" > archiveName 'gradleTest' > dependencies { > direct group: "javax", name: "javaee-api" > } > allprojects { > dependencies { > managed configuration: "compile", group: "javax", name: "javaee-api", version: "7.0" > } > } > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues October 2014