June 2015 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-2357) Invalid endpoint name in the rest-new-endpoint command

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-2357?page=com.atlassian.jira.plugin... ] Antonio Goncalves commented on FORGE-2357: ------------------------------------------ I thought it was a bug, but no : the string "Endpoint" is taken out, which is good. I just added an extra test. > Invalid endpoint name in the rest-new-endpoint command > ------------------------------------------------------ > > Key: FORGE-2357 > URL: https://issues.jboss.org/browse/FORGE-2357 > Project: Forge > Issue Type: Bug > Components: Java EE > Affects Versions: 2.16.1.Final > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > When you type the following command : > {code} > rest-new-endpoint --named MyEndpoint > {code} > The value of the {{@Path}} is {{my}} instead of {{myEndpoint}} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2357) Invalid endpoint name in the rest-new-endpoint command

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-2357: ---------------------------------------- Summary: Invalid endpoint name in the rest-new-endpoint command Key: FORGE-2357 URL: https://issues.jboss.org/browse/FORGE-2357 Project: Forge Issue Type: Bug Components: Java EE Affects Versions: 2.16.1.Final Reporter: Antonio Goncalves Fix For: 2.x Future When you type the following command : {code} rest-new-endpoint --named MyEndpoint {code} The value of the {{@Path}} is {{my}} instead of {{myEndpoint}} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-148) Got java runtime exception "unknow request parameter type integer" when run rhc setup in forge shell

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-148?page=com.atlassian.jira.... ] RH Bugzilla Integration commented on FORGEPLUGINS-148: ------------------------------------------------------ Dan McPherson <dmcphers(a)redhat.com> changed the Status of [bug 1020283|https://bugzilla.redhat.com/show_bug.cgi?id=1020283] from NEW to CLOSED > Got java runtime exception "unknow request parameter type integer" when run rhc setup in forge shell > ---------------------------------------------------------------------------------------------------- > > Key: FORGEPLUGINS-148 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-148 > Project: Forge Plugins/Addons > Issue Type: Bug > Components: OpenShift Plugin > Environment: JDK 1.7.0_45 & git 1.8.0 > windows 7& fedora 19 > Reporter: weiweijiang jiang > Priority: Blocker > > when rhc setup in forge shell, it got java runtime error message "unknow request parameter type integer". > And according to https://bugzilla.redhat.com/show_bug.cgi?id=1020283#c1 the issue has been fixed in client version pre-2.4.0, but the forge-plugin-openshift still use client version 2.0.1 > [no project] forge-distribution-1.4.2.Final $ forge find-plugin openshift > Connecting to remote repository [https://raw.github.com/forge/plugin-repository/ > master/repository.yaml]... connected! > - openshift (com.redhat.openshift:forge-openshift-plugin:::) > Author: Pete Muir <pmuir(a)redhat.com> > Website: http://openshift.com > Location: https://github.com/forge/plugin-openshift.git > Tags: cloud, openshift, redhat, jboss, deploy, rhc > Description: Plugins for creating cloud instances, managing existing clo > uds, and deploying applications to the Red Hat express cloud. > And the following is https://raw.github.com/forge/plugin-openshift/master/pom.xml > <?xml version="1.0" encoding="UTF-8"?> > <project > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd" > xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> > <modelVersion>4.0.0</modelVersion> > <groupId>com.redhat.openshift</groupId> > <artifactId>forge-openshift-plugin</artifactId> > <version>1.0.6.Final</version> > <properties> > <forge.api.version>1.0.6.Final</forge.api.version> > <jgit.version>2.0.0.201206130900-r</jgit.version> > <log4j.extras.version>1.1</log4j.extras.version> > <openshift.client.version>2.0.1</openshift.client.version> > <jsch.version>0.1.48</jsch.version> > </properties> > ... > <build> > <finalName>forge-openshift-plugin</finalName> > <plugins> > <plugin> > <artifactId>maven-compiler-plugin</artifactId> > <version>2.3.2</version> > <configuration> > <source>1.6</source> > <target>1.6</target> > </configuration> > </plugin> > </plugins> > </build> -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2149) validation.xml doesn't have the version="1.1" in the xml

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2149?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2149. ---------------------------------- Assignee: George Gastaldi Fix Version/s: 2.16.2.Final (was: 2.x Future) Resolution: Done > validation.xml doesn't have the version="1.1" in the xml > --------------------------------------------------------- > > Key: FORGE-2149 > URL: https://issues.jboss.org/browse/FORGE-2149 > Project: Forge > Issue Type: Bug > Components: Java EE > Affects Versions: 2.12.2.Final > Reporter: Antonio Goncalves > Assignee: George Gastaldi > Fix For: 2.16.2.Final > > > When Bean Validation is setup, here is the generated {{META-INF/validation.xml}} file: > {code} > <validation-config xmlns="http://jboss.org/xml/ns/javax/validation/configuration" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://jboss.org/xml/ns/javax/validation/configuration validation-configuration-1.1.xsd"/> > {code} > It misses the {{version}} attribute and should be : > {code} > <validation-config xmlns="http://jboss.org/xml/ns/javax/validation/configuration" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://jboss.org/xml/ns/javax/validation/configuration validation-configuration-1.1.xsd" version="1.1"/> > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2356) The scaffold provider should be mandatory when there are more than one

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-2356: ---------------------------------------- Summary: The scaffold provider should be mandatory when there are more than one Key: FORGE-2356 URL: https://issues.jboss.org/browse/FORGE-2356 Project: Forge Issue Type: Enhancement Components: Scaffold Affects Versions: 2.16.1.Final Reporter: Antonio Goncalves Fix For: 2.x Future After installing a few addons, including Angular, I use the {{scaffold-generate}} command thinking that it would use Faces, but it generates an Angular app. In this cas, the {{provider}} attribute should become mandatory . {code} $ scaffold-generate --provider --webRoot --targets --generateRestResources {code} Script that reproduces it : {code} $ addon-list org.jboss.forge.addon:angularjs,2.1.5-SNAPSHOT org.jboss.forge.addon:scaffold,2.16.1.Final org.jboss.forge.addon:scaffold-faces,2.16.1.Final org.jboss.forge.addon:scaffold-spi,2.16.1.Final $ project-new --named demo $ jpa-new-entity --named MyEntity $ scaffold-generate --targets org.demo.model.MyEntity ***SUCCESS*** CDI has been installed. ***SUCCESS*** EJB has been installed. ***SUCCESS*** Servlet API has been installed. ***SUCCESS*** JAX-RS has been installed. ***SUCCESS*** Scaffold was generated successfully. {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-191) Rename some Arquillian commands

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGEPLUGINS-191: ---------------------------------------------- Summary: Rename some Arquillian commands Key: FORGEPLUGINS-191 URL: https://issues.jboss.org/browse/FORGEPLUGINS-191 Project: Forge Plugins/Addons Issue Type: Enhancement Components: Arquillian Plugin Reporter: Antonio Goncalves Assignee: Aslak Knutsen To follow the Forge command naming conventions, some arquillian commands should be renamed || Command || To be renammed in || | arquillian-container-setup | arquillian-setup-container | | arquillian-container-configuration | arquillian-add-container | | arquillian-create-test | arquillian-new-test | -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

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

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2056?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-2056: ----------------------------------- Component/s: Build Tools - Maven (was: UI - Shell) > 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: Build Tools - Maven > Affects Versions: 2.12.0.Final > Reporter: Antonio Goncalves > Labels: starter > 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.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1874) Migrate Maven commands from Forge 1

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1874?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-1874: ---------------------------------------- What do you mean about treating Maven as an addon? Maven is already in it's own addon. > Migrate Maven commands from Forge 1 > ----------------------------------- > > Key: FORGE-1874 > URL: https://issues.jboss.org/browse/FORGE-1874 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.6.0.Final > Reporter: Antonio Goncalves > Assignee: George Gastaldi > > In Forge 1.x we had Maven commands, it would be good to have the same capabilities in Forge 2.x > {code} > [test] $ mvn > [ARG (of type java.lang.String[])] > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1874) Migrate Maven commands from Forge 1

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1874?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-1874: ---------------------------------------- Hi [~agoncal], Have you tried {{build test --profile arquillian-wildfly-remote}} ? That should work afaik. > Migrate Maven commands from Forge 1 > ----------------------------------- > > Key: FORGE-1874 > URL: https://issues.jboss.org/browse/FORGE-1874 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.6.0.Final > Reporter: Antonio Goncalves > Assignee: George Gastaldi > > In Forge 1.x we had Maven commands, it would be good to have the same capabilities in Forge 2.x > {code} > [test] $ mvn > [ARG (of type java.lang.String[])] > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-190) The default version of WildFly should be 8.2.0.Final instead of 8.1.0.Final

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGEPLUGINS-190: ---------------------------------------------- Summary: The default version of WildFly should be 8.2.0.Final instead of 8.1.0.Final Key: FORGEPLUGINS-190 URL: https://issues.jboss.org/browse/FORGEPLUGINS-190 Project: Forge Plugins/Addons Issue Type: Enhancement Components: JBoss AS Plugin Reporter: Antonio Goncalves Assignee: James Perkins When you setup WildFly 8 using all the defaults : {code} as-setup --server wildfly8 {code} The installed version is 8.1.0.Final but it should be 8.2.0.Final, the last one -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues June 2015