January 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1371) A newly created project is not imported into Eclipse when the project location is non-existent

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1371?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1371: -------------------------------------- Fix Version/s: 2.x Future > A newly created project is not imported into Eclipse when the project location is non-existent > ---------------------------------------------------------------------------------------------- > > Key: FORGE-1371 > URL: https://issues.jboss.org/browse/FORGE-1371 > Project: Forge > Issue Type: Bug > Affects Versions: 2.0.0.Beta3 > Reporter: Vineet Reynolds > Fix For: 2.x Future > > > When a non-existent location is specified in Eclipse, Forge creates the project, but fails to import the project into the Eclipse workspace. > This also seems to be related to an issue where the Location field is not pre-filled (not sure why; I'm reporting this bug on behalf of a user, so I'm hoping to get more details). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1346) Introduce wildcards to the CLI

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1346?page=com.atlassian.jira.plugin... ] Lincoln Baxter III closed FORGE-1346. ------------------------------------- Resolution: Won't Fix Since we have the bayesian distance feature implemented "Did you mean?" I think that we are OK without this one. It would also be difficult to implement and not a huge benefit as it would have to be learned (aka, non-intuitive) as a feature. > Introduce wildcards to the CLI > ------------------------------ > > Key: FORGE-1346 > URL: https://issues.jboss.org/browse/FORGE-1346 > Project: Forge > Issue Type: Enhancement > Components: UI - Shell > Affects Versions: 2.x Future > Reporter: Antonio Goncalves > > At the moment you start typing a command, you hit TAB, and you get all the possible hints : > {code} > > jpa- TAB > jpa-new-entity jpa-new-field > {code} > If wildcards are introduced, you could then do : > {code} > > *scaffold* TAB > jpa-scaffold-from-db rest-scaffold-from-jpa rest-scaffold-from-ejb > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1360) Review Property and Field Access support for JPA and related specs

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1360?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1360: -------------------------------------- Fix Version/s: 2.x Future > Review Property and Field Access support for JPA and related specs > ------------------------------------------------------------------ > > Key: FORGE-1360 > URL: https://issues.jboss.org/browse/FORGE-1360 > Project: Forge > Issue Type: Task > Components: Blessed Plugins > Affects Versions: 2.0.0.Beta3 > Reporter: Vineet Reynolds > Fix For: 2.x Future > > > Annotations should be written to the fielld or the getter, based on whether property or field access is used in JPA entities. Likewise, the presence of the annotation should also be flagged based on property vs field access used for the entity. > Note that there are different rules for JPA 1.0 and 2/0 entities. Different rules may also exist for other addons that support other specifications/JSRs involving beans. > This task is to conduct a review of the behavior of Forge addons for scenarios involving property vs field access. Raise additional feature requests or bugs as necessary. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1345) Unable to use --strategy ROOT_AND_NESTED_DTO for rest endpoint generation

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1345?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1345: -------------------------------------- Fix Version/s: 2.x Future > Unable to use --strategy ROOT_AND_NESTED_DTO for rest endpoint generation > ------------------------------------------------------------------------- > > Key: FORGE-1345 > URL: https://issues.jboss.org/browse/FORGE-1345 > Project: Forge > Issue Type: Feature Request > Components: Scaffold > Environment: JBDS 7.1.0.CR1 > Reporter: Pete Muir > Fix For: 2.x Future > > > Using this script - https://github.com/jboss-jdf/jdf-collateral/blob/master/scripts/forge_htm... - but with the new strategy suggested by Vineet, I get this error: > {code} > [rhsessions] rhsessions $ rest endpoint-from-entity --contentType application/json com.redhat.sessions.model.* --strategy ROOT_AND_NESTED_DTO > ? An action has requested to install the following facets into your project [interface org.jboss.forge.spec.javaee.JTAFacet, interface org.jboss.forge.spec.javaee.EJBFacet, interface org.jboss.forge.spec.javaee.PersistenceFacet] continue? [Y/n] > ***SUCCESS*** Installed [forge.spec.jta] successfully. > ***SUCCESS*** Installed [forge.spec.ejb] successfully. > ***SUCCESS*** Generated REST endpoint for [com.redhat.sessions.model.Attendee] > Wrote /Users/pmuir/workspace-demos/rhsessions/pom.xml > Wrote /Users/pmuir/workspace-demos/rhsessions/src/main/java/com/redhat/sessions/rest/dto/AttendeeDTO.java > Wrote /Users/pmuir/workspace-demos/rhsessions/src/main/java/com/redhat/sessions/rest/AttendeeEndpoint.java > Wrote /Users/pmuir/workspace-demos/rhsessions/src/main/java/com/redhat/sessions/rest/dto/NestedAttendeeDTO.java > ***ERROR*** Exception encountered: Attempted to import the illegal type [null] (type "set VERBOSE true" to enable stack traces) > [rhsessions] rhsessions $ > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1500) ProjectFactoryImpl.findProject() should iterate over directories first then over build systems

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1500?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1500: -------------------------------------- Fix Version/s: 2.x Future > ProjectFactoryImpl.findProject() should iterate over directories first then over build systems > ---------------------------------------------------------------------------------------------- > > Key: FORGE-1500 > URL: https://issues.jboss.org/browse/FORGE-1500 > Project: Forge > Issue Type: Bug > Components: Builtin Plugins > Affects Versions: 2.0.0.CR1 > Reporter: Adam Wyłuda > Fix For: 2.x Future > > > https://github.com/forge/core/blob/2.0/projects/impl/src/main/java/org/jb... > In case we have a project structure: > a/pom.xml > a/b/build.gradle > Starting from a/b/, if registry.getServices(BuildSystem.class) returns MavenBuildSystem as first, then it will pick up a/pom.xml. > My solution is inverting loops: > for (each build system) { for (each directory) { ... } } ---> for (each dir) { for (each build system) { ... } } > This causes problems in Gradle addon Maven build as temporary projects are run inside target/ directory, which has always pom.xml above. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1432) run command is missing (and with it, scripting)

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1432?page=com.atlassian.jira.plugin... ] Lincoln Baxter III commented on FORGE-1432: ------------------------------------------- So ';' doesn't appear to be the problem. Looking deeper. > run command is missing (and with it, scripting) > ----------------------------------------------- > > Key: FORGE-1432 > URL: https://issues.jboss.org/browse/FORGE-1432 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.0.0.Beta4 > Reporter: Antonio Goncalves > Assignee: Lincoln Baxter III > Fix For: 2.0.0.Final > > > I use a lot of scripts to start my projects, add/remove Maven dependencies.... So when I'm in Forge console, I type {{run ../myScript.fsh}}. For example, here is a script I use to get ride of EE 6 dependencies and add EE7 : > {code} > @/* ====================================== */; > @/* == From Java EE 6 to 7 Dependencies == */; > @/* ====================================== */; > project remove-dependency org.hibernate.javax.persistence:hibernate-jpa-2.0-api ; > project remove-dependency javax.validation:validation-api ; > project remove-dependency org.hibernate:hibernate-validator ; > project remove-dependency javax.enterprise:cdi-api ; > project remove-dependency org.jboss.spec.javax.annotation:jboss-annotations-api_1.1_spec ; > project remove-dependency org.jboss.spec.javax.ws.rs:jboss-jaxrs-api_1.1_spec ; > project remove-dependency org.jboss.spec.javax.transaction:jboss-transaction-api_1.1_spec ; > project remove-dependency org.jboss.spec.javax.ejb:jboss-ejb-api_3.1_spec ; > project remove-dependency org.jboss.spec.javax.faces:jboss-jsf-api_2.1_spec ; > project remove-dependency org.jboss.spec.javax.servlet:jboss-servlet-api_3.0_spec ; > project add-dependency javax:javaee-api:7.0:provided ; > project add-dependency org.primefaces:primefaces:4.0 ; > project add-repository primefaces-repo http://repository.primefaces.org ; > {code} > I have other scripts like that. The good this is, without leaving the console, I can write : > {code} > [Forge]$ run script1.fsh > [Forge]$ run script2.fsh > [Forge]$ run script3.fsh > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1454) project-remove-dependency command is missing

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1454?page=com.atlassian.jira.plugin... ] Lincoln Baxter III closed FORGE-1454. ------------------------------------- Assignee: Lincoln Baxter III Fix Version/s: 2.0.0.Final (was: 2.x Future) Resolution: Done > project-remove-dependency command is missing > -------------------------------------------- > > Key: FORGE-1454 > URL: https://issues.jboss.org/browse/FORGE-1454 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.0.0.CR1 > Reporter: Antonio Goncalves > Assignee: Lincoln Baxter III > Fix For: 2.0.0.Final > > > This command is similar to the following on in Forge 1.x > {code} > project remove-dependency org.hibernate.javax.persistence:hibernate-jpa-2.0-api ; > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1386) JPA setup should avoid adding Java EE 6 API POM/BOM when EE 7 APIs are present

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1386?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1386: -------------------------------------- Fix Version/s: 2.x Future > JPA setup should avoid adding Java EE 6 API POM/BOM when EE 7 APIs are present > ------------------------------------------------------------------------------ > > Key: FORGE-1386 > URL: https://issues.jboss.org/browse/FORGE-1386 > Project: Forge > Issue Type: Feature Request > Components: Builtin Plugins > Affects Versions: 2.0.0.Beta4 > Reporter: Vineet Reynolds > Fix For: 2.x Future > > > When the JPA setup wizard is run, and the WildFly container is chosen, the EE 6 APIs should not be added to the project POM unless they were already present. > I think the default behavior should be to add the dependencies for the most recent version of the supported EE version (EE 7 APIs) to the POM, unless a lower supported version (EE 6) is available in the POM. This needn't be desirable always, but should be considered. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1500) ProjectFactoryImpl.findProject() should iterate over directories first then over build systems

by Adam Wyłuda (JIRA)

Adam Wyłuda created FORGE-1500: ---------------------------------- Summary: ProjectFactoryImpl.findProject() should iterate over directories first then over build systems Key: FORGE-1500 URL: https://issues.jboss.org/browse/FORGE-1500 Project: Forge Issue Type: Bug Components: Builtin Plugins Affects Versions: 2.0.0.CR1 Reporter: Adam Wyłuda https://github.com/forge/core/blob/2.0/projects/impl/src/main/java/org/jb... In case we have a project structure: a/pom.xml a/b/build.gradle Starting from a/b/, if registry.getServices(BuildSystem.class) returns MavenBuildSystem as first, then it will pick up a/pom.xml. My solution is inverting loops: for (each build system) { for (each directory) { ... } } ---> for (each dir) { for (each build system) { ... } } This causes problems in Gradle addon Maven build as temporary projects are run inside target/ directory, which has always pom.xml above. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1456) project-add/remove-repository command is missing

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1456?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1456. ---------------------------------- Fix Version/s: 2.0.0.Final (was: 2.x Future) Resolution: Done > project-add/remove-repository command is missing > ------------------------------------------------ > > Key: FORGE-1456 > URL: https://issues.jboss.org/browse/FORGE-1456 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.0.0.CR1 > Reporter: Antonio Goncalves > Assignee: George Gastaldi > Fix For: 2.0.0.Final > > > This command is similar to the following on in Forge 1.x > {code} > project add-repository primefaces-repo http://repository.primefaces.org > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues January 2014