August 2012 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-511) Should be able to filter dependency versions when using DependencyInstaller or related APIs

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-511: ---------------------------------------- Summary: Should be able to filter dependency versions when using DependencyInstaller or related APIs Key: FORGE-511 URL: https://issues.jboss.org/browse/FORGE-511 Project: Forge Issue Type: Feature Request Components: Plugin API, Shell Reporter: Lincoln Baxter III {code} package org.jboss.forge.arquillian; import java.util.List; import org.jboss.forge.project.dependencies.Dependency; /** * DependencyUtil * * @author <a href="mailto:aslak@redhat.com">Aslak Knutsen</a> * @version $Revision: $ */ public class DependencyUtil { private DependencyUtil() {} public static Dependency getLatestNonSnapshotVersion(List<Dependency> dependencies) { if(dependencies == null) { return null; } for(int i = dependencies.size()-1; i >= 0; i--) { Dependency dep = dependencies.get(i); if(!dep.getVersion().endsWith("SNAPSHOT")) { return dep; } } return dependencies.get(dependencies.size()-1); } }{code} {code} 1 - [org.jboss.arquillian.container:arquillian-jetty-embedded-7:::1.0.0-SNAPSHOT] 2 - [org.jboss.arquillian.container:arquillian-jetty-embedded-7:::1.0.0.Alpha3] 3 - [org.jboss.arquillian.container:arquillian-jetty-embedded-7:::1.0.0.Alpha4] 4 - [org.jboss.arquillian.container:arquillian-jetty-embedded-7:::1.0.0.Alpha4.SP1] 5 - [org.jboss.arquillian.container:arquillian-jetty-embedded-7:::1.0.0.Alpha5] 6 - [org.jboss.arquillian.container:arquillian-jetty-embedded-7:::1.0.0.CR1]* 7 - [org.jboss.arquillian.container:arquillian-jetty-embedded-7:::1.0.0.Final-SNAPSHOT] {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
2
0 / 0

[JBoss JIRA] (FORGE-425) Provide a way to override plugin resources without coding

by Richard Kennard (Created) (JIRA)

Provide a way to override plugin resources without coding --------------------------------------------------------- Key: FORGE-425 URL: https://issues.jboss.org/browse/FORGE-425 Project: Forge Issue Type: Feature Request Reporter: Richard Kennard At present, Forge makes it easy for users to add their own plugins by writing some code. However this is onerous for use cases where users just want to tweak some static resource or template. For scaffolding specifically, but for plugins generally, it would be good to have a mechanism to allow users to easily 'drop in' replacement files. >From discussions on the mailing list, the consensus seems to be: 1. Plugins should keep their resources in as flat a structure as possible. For example at the moment scaffolding uses "resources/org/jboss/forge/scaffold/faces/scaffold/BackingBean.jv" but we should change this to, say, "resources/scaffold/BackingBean.jv" 2. Forge should provide a folder, say, /forge-distribution/resources where users can drop replacement files There is some disagreement over how this is to be implemented. The concerns are: 1. Richard would prefer that plugins did not have to explicitly worry about this 'replacement mechanism'. Lots of plugins already call .getResource, so it'd be good if this just magically checked /forge-distribution/resources for us. 2. Max does not want this 'replacement mechanism' to work by putting /forge-distribution/resources on the classpath (Max can explain why :) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

3
4
0 / 0

[JBoss JIRA] (FORGE-392) Scaffold API generateFromEntity should also create dependent entities

by Richard Kennard (Created) (JIRA)

Scaffold API generateFromEntity should also create dependent entities --------------------------------------------------------------------- Key: FORGE-392 URL: https://issues.jboss.org/browse/FORGE-392 Project: Forge Issue Type: Feature Request Reporter: Richard Kennard In org.jboss.forge.scaffold.plugins.ScaffoldPlugin there is a method 'generateFromEntity' which delegates to 'provider.generateFromEntity'. It calls 'provider.generateFromEntity' once for every JavaResource it is given. So for example if the user types: from-entity com.test.domain.Foo com.test.domain.Bar It will generate scaffolding for both Foo and Bar. However if Foo has some kind of relationship to Bar, then the scaffolding produced by Foo will internally refer to Bar. Therefore the generated project will be broken if the user simply does... from-entity com.test.domain.Foo ...because there will be no Bar scaffolding. It would be great if the Scaffold API could understand that Foo has related entities and automatically add those into the list before it calls 'provider.generateFromEntity' -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

3
3
0 / 0

[JBoss JIRA] (FORGE-245) Support structured options in @Commands

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-245?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-245: ---------------------------------- Fix Version/s: 2.0.0.Alpha1 (was: Future) > Support structured options in @Commands > --------------------------------------- > > Key: FORGE-245 > URL: https://issues.jboss.org/browse/FORGE-245 > Project: Forge > Issue Type: Feature Request > Reporter: Max Rydahl Andersen > Fix For: 2.0.0.Alpha1 > > > ver considered allowing something like > generateEntities(@Option String table, @Option String catalog, @Option @Option String schema, @NestedOption final JPADataSource datasource) > class DataSource { > public DataSource(@Option(...) String name, @Option(..) password, @Option(..) ..) > ... > ) > Which would actually provide some more nested structure and be useful in ui construction in IDE plus better naming of things even in shell ? > Would also be good to be able to reference "default" @JPADatasource should be "production", "dev" or "test" if SEAMFORGE-210 comes to life? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-85) Shell cannot parse command values containing '!' exclaimation points

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-85?page=com.atlassian.jira.plugin.s... ] George Gastaldi reassigned FORGE-85: ------------------------------------ Assignee: (was: Mike Brock) Moving issue back to pool > Shell cannot parse command values containing '!' exclaimation points > -------------------------------------------------------------------- > > Key: FORGE-85 > URL: https://issues.jboss.org/browse/FORGE-85 > Project: Forge > Issue Type: Bug > Components: Shell > Affects Versions: 1.0.0.Beta2 > Reporter: Lincoln Baxter III > Priority: Critical > Labels: HackNight > Attachments: Forge-85.patch > > > {code} > [pfdemo] pfdemo $ echo sdfdf! > sdfdf ! > [pfdemo] pfdemo $ echo sdfdf!sdf > ***ERROR*** Exception encountered: !sdf: event not found (type "set VERBOSE true" to enable stack traces) > [pfdemo] pfdemo $ > [pfdemo] pfdemo $ echo 'asdf!asdf` > ***ERROR*** Exception encountered: !asdf`: event not found (type "set VERBOSE true" to enable stack traces) > [pfdemo] pfdemo $ > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-318) Plugin: show me all the versions I have locally in my maven repository for a given artifact (GAV)

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-318?page=com.atlassian.jira.plugin.... ] George Gastaldi reassigned FORGE-318: ------------------------------------- Assignee: (was: Ivan St. Ivanov) Placing issue back to pool > Plugin: show me all the versions I have locally in my maven repository for a given artifact (GAV) > ------------------------------------------------------------------------------------------------- > > Key: FORGE-318 > URL: https://issues.jboss.org/browse/FORGE-318 > Project: Forge > Issue Type: Feature Request > Components: Brainstorming > Reporter: Lincoln Baxter III > Labels: HackNight, starter > > show-artifacts org.jboss.seam.servlet:seam-servlet > Wildcard support: > show-artifacts org.jboss.seam.*:seam-* -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-655) scaffold from entity: wrong brand link, missing jboss-logo, add mime-mapping in web.xml

by fiorenzo pizza (JIRA)

fiorenzo pizza created FORGE-655: ------------------------------------ Summary: scaffold from entity: wrong brand link, missing jboss-logo, add mime-mapping in web.xml Key: FORGE-655 URL: https://issues.jboss.org/browse/FORGE-655 Project: Forge Issue Type: Bug Components: Scaffold Affects Versions: 1.0.6.Final Reporter: fiorenzo pizza Priority: Minor Fix For: 1.0.7.Final 1) wrong brand link In pageTemplate (https://github.com/forge/core/blob/master/scaffold-faces/src/main/resourc...) the link should be: <h:link id="brandLink" outcome="@{targetDir}/index.xhtml" styleClass="brand"> <h:outputText value="@{appName}" /></h:link> in place of: <a href="@{targetDir}/index.xhtml" class="brand">@{appName}</a> [to avoid a wrong redirect to http://localhost:8080/index.xhtml] 2)missing resource jboss-community.png in the resource folder the image jboss-community.png doesn't exist (it's used in the error page: https://github.com/forge/core/blob/master/scaffold-faces/src/main/resourc...) 3) add mime-mapping in web.xml To eliminate the annoying log jboss server log: 23:59:54,914 AVVERTENZA [javax.enterprise.resource.webcontainer.jsf.context] (http--127.0.0.1-8080-1) JSF1091: No mime type could be found for file favicon.ico. To resolve this, add a mime-type mapping to the applications web.xml you should add on web.xml: <mime-mapping> <extension>ico</extension> <mime-type>image/x-icon</mime-type> </mime-mapping> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
1
0 / 0

[JBoss JIRA] (FORGE-625) Remove Maven exec plugin configuration from dist module

by George Gastaldi (JIRA)

George Gastaldi created FORGE-625: ------------------------------------- Summary: Remove Maven exec plugin configuration from dist module Key: FORGE-625 URL: https://issues.jboss.org/browse/FORGE-625 Project: Forge Issue Type: Enhancement Components: Documentation, Init Scripts Affects Versions: 1.0.5.Final Reporter: George Gastaldi Priority: Trivial As for now, the best way to start forge is to get into dist/target/forge-distribution-1.0.6-SNAPSHOT/bin and run ./forge. However, some time ago it used to be run using mvn exec:exec, which should no longer be used, since it has some issues with JBoss modules itself. The following should be removed from pom.xml in dist module and documentation should be properly updated: {code:xml} <profile> <id>runForge</id> <build> <plugins> <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>exec-maven-plugin</artifactId> <version>1.2.1</version> <configuration> <executable>java</executable> <workingDirectory>${java.io.tmpdir}</workingDirectory> <arguments> <argument>-cp</argument> <classpath /> <argument>org.jboss.modules.Main</argument> <argument>-modulepath</argument> <argument>${project.build.directory}/${project.artifactId}-${forge.release.version}/modules:${user.home}/.forge/plugins</argument> <argument>org.jboss.forge</argument> </arguments> </configuration> </plugin> </plugins> </build> </profile> <profile> <id>debugForge</id> <build> <plugins> <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>exec-maven-plugin</artifactId> <version>1.2.1</version> <configuration> <executable>java</executable> <workingDirectory>${java.io.tmpdir}</workingDirectory> <arguments> <argument>-Xdebug</argument> <argument>${debug.props}</argument> <argument>-cp</argument> <classpath /> <argument>org.jboss.modules.Main</argument> <argument>-modulepath</argument> <argument>${project.build.directory}/${project.artifactId}-${forge.release.version}/modules:${user.home}/.forge/plugins</argument> <argument>org.jboss.forge</argument> </arguments> </configuration> </plugin> </plugins> </build> </profile> {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
1
0 / 0

[JBoss JIRA] (FORGE-320) Git-powered "Undo" functionality in Forge

by Jevgeni Zelenkov (JIRA)

[ https://issues.jboss.org/browse/FORGE-320?page=com.atlassian.jira.plugin.... ] Jevgeni Zelenkov closed FORGE-320. ---------------------------------- > Git-powered "Undo" functionality in Forge > ----------------------------------------- > > Key: FORGE-320 > URL: https://issues.jboss.org/browse/FORGE-320 > Project: Forge > Issue Type: Feature Request > Components: Brainstorming > Environment: All > Reporter: Ian Hands > Assignee: Jevgeni Zelenkov > Priority: Minor > > Forge should support undo/redo of changes on the file system. Use of git would rock here, particularly cases where Forge is introduced to an existing project, and determining what actually changed during a plugin execution could be nasty. > Care should be taken to integrate with projects that are already using git as a version control mechanism. > For example: > {code}I see you are already using git, what branch should Forge use when modifying files? > 1 - org.jboss.forge.history > 2 - define your own?*{code} > After every successful command execution, changes should be committed to the history branch. If an undo is requested, users could be presented with a list of revisions, or simply pop the latest revision off the stack. If a command exits in failure state, the user should be prompted to either "Undo" or "Abort," in which case, if "Undo" is selected, changes made during the failed command execution should be reverted to the previous state - "Abort" simply does nothing. > {code}***ERROR*** Could not complete action [blah]... > ? Undo changes from previous command? [Y/n] {code} > Scenarios: > * Master/current branch is ahead of history branch > * Master/current branch is behind history branch > * How to handle running in detached state? > * How to handle rebasing of a branch to avoid merge commits? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-320) Git-powered "Undo" functionality in Forge

by Jevgeni Zelenkov (JIRA)

[ https://issues.jboss.org/browse/FORGE-320?page=com.atlassian.jira.plugin.... ] Jevgeni Zelenkov resolved FORGE-320. ------------------------------------ Resolution: Done https://github.com/forge/plugin-undo > Git-powered "Undo" functionality in Forge > ----------------------------------------- > > Key: FORGE-320 > URL: https://issues.jboss.org/browse/FORGE-320 > Project: Forge > Issue Type: Feature Request > Components: Brainstorming > Environment: All > Reporter: Ian Hands > Assignee: Jevgeni Zelenkov > Priority: Minor > > Forge should support undo/redo of changes on the file system. Use of git would rock here, particularly cases where Forge is introduced to an existing project, and determining what actually changed during a plugin execution could be nasty. > Care should be taken to integrate with projects that are already using git as a version control mechanism. > For example: > {code}I see you are already using git, what branch should Forge use when modifying files? > 1 - org.jboss.forge.history > 2 - define your own?*{code} > After every successful command execution, changes should be committed to the history branch. If an undo is requested, users could be presented with a list of revisions, or simply pop the latest revision off the stack. If a command exits in failure state, the user should be prompted to either "Undo" or "Abort," in which case, if "Undo" is selected, changes made during the failed command execution should be reverted to the previous state - "Abort" simply does nothing. > {code}***ERROR*** Could not complete action [blah]... > ? Undo changes from previous command? [Y/n] {code} > Scenarios: > * Master/current branch is ahead of history branch > * Master/current branch is behind history branch > * How to handle running in detached state? > * How to handle rebasing of a branch to avoid merge commits? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues August 2012