September 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1164) `project remove-managed-dependency` does not remove managed dependency

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1164?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1164: -------------------------------------- Summary: `project remove-managed-dependency` does not remove managed dependency (was: Cannot remove managed dependency) > `project remove-managed-dependency` does not remove managed dependency > ---------------------------------------------------------------------- > > Key: FORGE-1164 > URL: https://issues.jboss.org/browse/FORGE-1164 > Project: Forge > Issue Type: Bug > Affects Versions: 1.4.0.Final > Reporter: Antonio Goncalves > > I want to turn a Forge project from being Java EE 6 to Java EE 7 centric. One of these tasks is to change the dependencies in the {{pom.xml}}. So I add the {{javax:javaee-api:7.0}} to the pom and list the managed dependencies : > {code} > $ project list-managed-dependencies > org.jboss.spec : jboss-javaee-6.0 : 3.0.2.Final : pom : import > org.hibernate : hibernate-validator : 5.1.0.Alpha1 : jar : provided > javax : javaee-api : 7.0 : jar : provided > {code} > If I remove the added {{javax:javaee-api:7.0}}, it works. But if I want to remove the {{org.jboss.spec:jboss-javaee-6.0}}, the console says it doesn't exist : > {code} > $ project remove-managed-dependency org.jboss.spec:jboss-javaee-6.0 > Managed dependency [org.jboss.spec:jboss-javaee-6.0:::] not found in project... > {code} > I even tried adding version, scope and so on, but it doesn't work : > {code} > $ project remove-managed-dependency > ? [[ groupId :artifactId {:version :scope :packaging} ] (of type org.jboss.forge.project.dependencies.Dependency)]: org.jboss.spec:jboss-javaee-6.0:3.0.2.Final:pom:import > Managed dependency [org.jboss.spec:jboss-javaee-6.0:import::3.0.2.Final] not found in project... > {code} > PS : same occur in Forge 1.3.3-Final -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1030) Support multi-module Forge plugins

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1030?page=com.atlassian.jira.plugin... ] Lincoln Baxter III commented on FORGE-1030: ------------------------------------------- Right, but there is no 1.4.1.Final dependency so if he tries to depend on one in any of his POMs, it will fail. > Support multi-module Forge plugins > ---------------------------------- > > Key: FORGE-1030 > URL: https://issues.jboss.org/browse/FORGE-1030 > Project: Forge > Issue Type: Bug > Components: Documentation, Plugin API, Plugin Repository > Affects Versions: 1.3.3.Final, 1.4.0.Final > Reporter: Lennart Jörelid > Assignee: George Gastaldi > Priority: Blocker > Fix For: 1.4.1.Final > > Attachments: forge_1030_codeAnalysis.png > > > It seems that Forge really needs better support for the default Maven > development process. In repository.yaml, Forge plugins are defined by giving > a Maven project GAV for the project holding the forge plugin definitions, as well as the GitHub repository holding the plugin source. > Yet, Forge seems to ignore the Maven GAV information given in repository.yaml when checking out and building the plugin locally. > This is a rather nasty bug, which in its current state effectively prevents anyone from using a multi-module build for their plugins (and it is also undocumented). > An example is shown below: > {code} > [no project] Nazgul $ forge install-plugin nazgul > ***INFO*** Preparing to install plugin: nazgul > ***INFO*** Checking out plugin source files to [/var/folders/6g/9n7r543d2bv9n2qjvnvf_hsh0000gn/T/forgetemp6186363544408555570] via 'git' > ***INFO*** Switching to branch/tag [refs/heads/1.3.3.Final] > ? The project does not appear to be a Forge Plugin Project, install anyway? [y/N] > {code} > While this analysis by Forge is incorrect (the Maven GAV given in the repository.yaml is indeed a project which holds plugins), it gets worse after installation: > {code} > [INFO] ------------------------------------------------------------------------ > [INFO] Reactor Summary: > [INFO] > [INFO] nazgul-forge-parent ............................... SUCCESS [7.921s] > [INFO] nazgul-forge-api-parent ........................... SUCCESS [4.345s] > [INFO] nazgul-forge-model-parent ......................... SUCCESS [1.274s] > [INFO] nazgul-forge-reactor .............................. SUCCESS [0.847s] > [INFO] nazgul-forge-poms-reactor ......................... SUCCESS [0.058s] > [INFO] nazgul-forge-analyzer-api ......................... SUCCESS [5.562s] > [INFO] nazgul-forge-analyzer-impl-nazgul ................. SUCCESS [1.666s] > [INFO] nazgul-forge-analyzer-reactor ..................... SUCCESS [0.020s] > [INFO] nazgul-forge-factory-model ........................ SUCCESS [2.434s] > [INFO] nazgul-forge-factory-api .......................... SUCCESS [7.634s] > [INFO] nazgul-forge-factory-impl-nazgul .................. SUCCESS [2.724s] > [INFO] nazgul-forge-factory-reactor ...................... SUCCESS [0.032s] > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD SUCCESS > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 36.580s > [INFO] Finished at: Mon Jul 22 07:46:48 CEST 2013 > [INFO] Final Memory: 49M/247M > [INFO] ------------------------------------------------------------------------ > ***INFO*** Cleaning up temp workspace [/var/folders/6g/9n7r543d2bv9n2qjvnvf_hsh0000gn/T/forgetemp6186363544408555570] > Deleted /var/folders/6g/9n7r543d2bv9n2qjvnvf_hsh0000gn/T/forgetemp6186363544408555570 > ***ERROR*** Exception encountered: Build artifact [nazgul-forge-reactor-1.0.1-SNAPSHOT.pom] is missing and cannot be installed. Please resolve build errors and try again. (type "set VERBOSE true" to enable stack traces) > {code} > So ... > # The repository.yaml includes a full Maven GAV to the project which holds Forge plugins. > # Forge uses repository.yaml to download the source from GitHub and build it > # Forge ignores the Maven GAV given in repository.yaml, and simply uses the root reactor project to inspect and attempt to install the plugins. > To fix this bug, Forge needs to find the project given within the repository.yaml within the downloaded reactor and install the plugins from *that* project. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1164) Cannot remove managed dependency

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1164?page=com.atlassian.jira.plugin... ] Lincoln Baxter III commented on FORGE-1164: ------------------------------------------- As a workaround, I'd obviously recommend just deleting the appropriate entry from your POM :) > Cannot remove managed dependency > -------------------------------- > > Key: FORGE-1164 > URL: https://issues.jboss.org/browse/FORGE-1164 > Project: Forge > Issue Type: Bug > Affects Versions: 1.4.0.Final > Reporter: Antonio Goncalves > > I want to turn a Forge project from being Java EE 6 to Java EE 7 centric. One of these tasks is to change the dependencies in the {{pom.xml}}. So I add the {{javax:javaee-api:7.0}} to the pom and list the managed dependencies : > {code} > $ project list-managed-dependencies > org.jboss.spec : jboss-javaee-6.0 : 3.0.2.Final : pom : import > org.hibernate : hibernate-validator : 5.1.0.Alpha1 : jar : provided > javax : javaee-api : 7.0 : jar : provided > {code} > If I remove the added {{javax:javaee-api:7.0}}, it works. But if I want to remove the {{org.jboss.spec:jboss-javaee-6.0}}, the console says it doesn't exist : > {code} > $ project remove-managed-dependency org.jboss.spec:jboss-javaee-6.0 > Managed dependency [org.jboss.spec:jboss-javaee-6.0:::] not found in project... > {code} > I even tried adding version, scope and so on, but it doesn't work : > {code} > $ project remove-managed-dependency > ? [[ groupId :artifactId {:version :scope :packaging} ] (of type org.jboss.forge.project.dependencies.Dependency)]: org.jboss.spec:jboss-javaee-6.0:3.0.2.Final:pom:import > Managed dependency [org.jboss.spec:jboss-javaee-6.0:import::3.0.2.Final] not found in project... > {code} > PS : same occur in Forge 1.3.3-Final -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1164) Cannot remove managed dependency

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1164?page=com.atlassian.jira.plugin... ] Lincoln Baxter III commented on FORGE-1164: ------------------------------------------- I believe the real issue here is that the `project remove-managed-dependency` command is not properly parsing the coordinates of your `pom` import. This is probably a bug in that command. > Cannot remove managed dependency > -------------------------------- > > Key: FORGE-1164 > URL: https://issues.jboss.org/browse/FORGE-1164 > Project: Forge > Issue Type: Bug > Affects Versions: 1.4.0.Final > Reporter: Antonio Goncalves > > I want to turn a Forge project from being Java EE 6 to Java EE 7 centric. One of these tasks is to change the dependencies in the {{pom.xml}}. So I add the {{javax:javaee-api:7.0}} to the pom and list the managed dependencies : > {code} > $ project list-managed-dependencies > org.jboss.spec : jboss-javaee-6.0 : 3.0.2.Final : pom : import > org.hibernate : hibernate-validator : 5.1.0.Alpha1 : jar : provided > javax : javaee-api : 7.0 : jar : provided > {code} > If I remove the added {{javax:javaee-api:7.0}}, it works. But if I want to remove the {{org.jboss.spec:jboss-javaee-6.0}}, the console says it doesn't exist : > {code} > $ project remove-managed-dependency org.jboss.spec:jboss-javaee-6.0 > Managed dependency [org.jboss.spec:jboss-javaee-6.0:::] not found in project... > {code} > I even tried adding version, scope and so on, but it doesn't work : > {code} > $ project remove-managed-dependency > ? [[ groupId :artifactId {:version :scope :packaging} ] (of type org.jboss.forge.project.dependencies.Dependency)]: org.jboss.spec:jboss-javaee-6.0:3.0.2.Final:pom:import > Managed dependency [org.jboss.spec:jboss-javaee-6.0:import::3.0.2.Final] not found in project... > {code} > PS : same occur in Forge 1.3.3-Final -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1179) Port the Bean validation commands

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGE-1179: -------------------------------------- Summary: Port the Bean validation commands Key: FORGE-1179 URL: https://issues.jboss.org/browse/FORGE-1179 Project: Forge Issue Type: Sub-task Reporter: Vineet Reynolds Commands in Forge 1: * validation setup * constraint Valid * constraint Null * constraint NotNull * constraint AssertTrue * constraint AssertFalse * constraint MinConstraint * constraint MaxConstraint * constraint DecimalMin * constraint DecimalMax * constraint Size * constraint Digits * constraint Past * constraint Future * constraint Pattern -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1176) Port the JAX-RS (REST) commands

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-1176?page=com.atlassian.jira.plugin... ] Vineet Reynolds updated FORGE-1176: ----------------------------------- Summary: Port the JAX-RS (REST) commands (was: Port the REST (JAX-RS) commands) > Port the JAX-RS (REST) commands > ------------------------------- > > Key: FORGE-1176 > URL: https://issues.jboss.org/browse/FORGE-1176 > Project: Forge > Issue Type: Sub-task > Components: Builtin Plugins > Reporter: Vineet Reynolds > Fix For: 2.0.0.Final > > > Commands in Forge 1: > * rest setup > * rest endpoint-from-entity -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1161) REGRESSION: Projects are no longer imported after CLAC fix

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1161?page=com.atlassian.jira.plugin... ] Lincoln Baxter III closed FORGE-1161. ------------------------------------- Resolution: Done Done. > REGRESSION: Projects are no longer imported after CLAC fix > ---------------------------------------------------------- > > Key: FORGE-1161 > URL: https://issues.jboss.org/browse/FORGE-1161 > Project: Forge > Issue Type: Bug > Components: Furnace (Container) > Affects Versions: 2.0.0.Alpha12 > Reporter: George Gastaldi > Assignee: Lincoln Baxter III > Priority: Blocker > Fix For: 2.0.0.Alpha12 > > > After FORGE-1159 changes were applied, no projects are imported after the New Project wizard finishes. > This is due that the following code now throws an IllegalArgumentException while debugging: > https://github.com/jbosstools/jbosstools-forge/blob/master/plugins/org.jb... > Reverting commit d3daf36b5c59d63ed11752092fdb5a028fdcabb1 in forge/furnace seems to solve the problem -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1178) Port the JAX-WS (SOAP) commands

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGE-1178: -------------------------------------- Summary: Port the JAX-WS (SOAP) commands Key: FORGE-1178 URL: https://issues.jboss.org/browse/FORGE-1178 Project: Forge Issue Type: Sub-task Reporter: Vineet Reynolds Commands in Forge 1: * soap setup -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1177) Port the Servlet commands

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGE-1177: -------------------------------------- Summary: Port the Servlet commands Key: FORGE-1177 URL: https://issues.jboss.org/browse/FORGE-1177 Project: Forge Issue Type: Sub-task Reporter: Vineet Reynolds Commands in Forge 1: * list-web-resources * servlet <default_command> * servlet setup -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1176) Port the REST (JAX-RS) commands

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGE-1176: -------------------------------------- Summary: Port the REST (JAX-RS) commands Key: FORGE-1176 URL: https://issues.jboss.org/browse/FORGE-1176 Project: Forge Issue Type: Sub-task Reporter: Vineet Reynolds Commands in Forge 1: * rest setup * rest endpoint-from-entity -- 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

10 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues September 2013