March 2011 - forge-dev - Jboss List Archives

[JBoss JIRA] Created: (SEAMFORGE-36) Ability to backout of a command

by Paul Bakker (JIRA)

Ability to backout of a command ------------------------------- Key: SEAMFORGE-36 URL: https://issues.jboss.org/browse/SEAMFORGE-36 Project: Seam Forge Issue Type: Feature Request Reporter: Paul Bakker Priority: Minor The prompt should have the ability to cancel an action. In some cases you can get into situations where the prompt is blocking, but there is no possible correct input, and you can't get out of the prompt. For example when installing new maven dependencies the prompt will display a list of versions. If this list is empty, there is no possible correct value to get to the next step. In a normal shell you would type ctrl-c to cancel a command, but that would close Forge in this case. We need something like ctrl-c within Forge. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

3
9
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-61) Provide shortcuts navigation plugins for bookmarking resources / returning to bookmarks

by Lincoln Baxter III (JIRA)

Provide shortcuts navigation plugins for bookmarking resources / returning to bookmarks --------------------------------------------------------------------------------------- Key: SEAMFORGE-61 URL: https://issues.jboss.org/browse/SEAMFORGE-61 Project: Seam Forge Issue Type: Feature Request Components: Builtin Plugins Affects Versions: 1.0.0.Alpha2 Reporter: Lincoln Baxter III the "mark" and "go" commands would be useful $ go home $ go project $ mark javasrc $ cd ~/ $ go javasrc takes you back to that dir with tab-completion of course $ go java<TAB> $ go javasrc // go without an argument lists the available targets $ go home (global) project javasrc By default, "mark" adds the bookmark to the current project's /META-INF/forge.xml the --global command would redirect these settings to the ~/.forge/forge.xml or ~/.forge/config file $ mark {name} --global (default command?) $ mark add {name} --global $ mark del {name} --global $ mark list --global -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-62) JavaClass should support adding an interface

by Dan Allen (JIRA)

JavaClass should support adding an interface -------------------------------------------- Key: SEAMFORGE-62 URL: https://issues.jboss.org/browse/SEAMFORGE-62 Project: Seam Forge Issue Type: Feature Request Components: Parsers / File Manipulation Affects Versions: 1.0.0.Alpha2 Reporter: Dan Allen The JavaClass API should add support for adding interfaces to the Java source being generated. Perhaps add these methods to Extendable. void addInterface(String interface); void addInterface(Class<?> type); void hasInterface(String interface); void hasInterface(Class<?> type); List<String> getInterfaces(); ... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-60) Documentation issues

by Martin Gencur (JIRA)

Documentation issues -------------------- Key: SEAMFORGE-60 URL: https://issues.jboss.org/browse/SEAMFORGE-60 Project: Seam Forge Issue Type: Bug Affects Versions: 1.0.0.Alpha2 Reporter: Martin Gencur Fix For: 1.0.0.Alpha3 2) the same section - a typo - "This server will host your application once is is built." 3) typo - "4.1.2. With Maven)" 5) typo - section "4.6. Add commands to your plugin" - "in which case a the plugin..." 6) section "4.6." contains wrong link "described in detail" which points again to the top of the Seam Documentation 7) section "4.6.3" - there are outputs for executed commands combining --named and ordered option parameters. The outputs are the following: $ example-plugin --one cat --two dog bird lizard >> option one equals: cat >> option two equals: dog >> option one equals: bird >> option two equals: lizard I think it is wrong and it should be: $ example-plugin --one cat --two dog bird lizard >> option one equals: cat >> option two equals: dog >> option three equals: bird >> option four equals: lizard Note that there are two such snippets. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-51) Persistence plugin needs more informative help messages when prompting for container and provider types

by Lincoln Baxter III (JIRA)

Persistence plugin needs more informative help messages when prompting for container and provider types ------------------------------------------------------------------------------------------------------- Key: SEAMFORGE-51 URL: https://issues.jboss.org/browse/SEAMFORGE-51 Project: Seam Forge Issue Type: Enhancement Components: Builtin Plugins Affects Versions: 1.0.0.Alpha2 Reporter: Lincoln Baxter III These messages are misleading, and without tab-completion, it is next to impossible to tell what needs to be typed here. [MyApp] MyApp $ persistence setup [provider=ARG (org.jboss.seam.forge.spec.jpa.api.JPAProvider)]: org.jboss.seam.forge.spec.jpa.api.JPAProvider [container=ARG (org.jboss.seam.forge.spec.jpa.api.JPAContainer)]: org.jboss.seam.forge.spec.jpa.api.JPAContainer Wrote /forge-1.0.0.Alpha2/MyApp/src/main/resources/META-INF/persistence.xml ***SUCCESS*** Installed [forge.spec.jpa] successfully. ***ERROR*** [setup] null -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-58) Failing to install forge.api facet - missing Forge API version to choose

by Martin Gencur (JIRA)

Failing to install forge.api facet - missing Forge API version to choose ------------------------------------------------------------------------ Key: SEAMFORGE-58 URL: https://issues.jboss.org/browse/SEAMFORGE-58 Project: Seam Forge Issue Type: Bug Affects Versions: 1.0.0.Alpha2 Reporter: Martin Gencur When I generate a new project with $ new-project --named {name} --topLevelPackage {com.package} --projectFolder {/directory/path} and try to install forge.api facet via "install forge.api", I am prompted to choose a version of the Forge API but there is really NOT displayed any to choose: Install which version of the Forge API? <-- there is really nothing displayed here <-- there is really nothing displayed here Choose an option by typing the number of the selection: ...I tried to enter 0,1,2,..., 1.0.0.Alpha1, 1.0.0.Alpha2 , none of them works, I'm getting "Invalid selection, please try again." -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-53) Version range prompt is not querying remote repositories

by Lincoln Baxter III (JIRA)

Version range prompt is not querying remote repositories -------------------------------------------------------- Key: SEAMFORGE-53 URL: https://issues.jboss.org/browse/SEAMFORGE-53 Project: Seam Forge Issue Type: Enhancement Components: Plugin API Affects Versions: 1.0.0.Alpha2 Reporter: Lincoln Baxter III The maven artifact version prompt is looking only in the local repository (via aether) when it should instead be looking at configured remote repositores from the compiled POM hierarchy as well. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
1
0 / 0

[JBoss JIRA] Closed: (SEAMFORGE-19) mvn clean install: failing org.jboss.seam.forge.test.project.MavenFacetsTest (testAbsoluteUnknownProjectCannotInstantiate)

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/SEAMFORGE-19?page=com.atlassian.jira.plug... ] Lincoln Baxter III closed SEAMFORGE-19. --------------------------------------- Assignee: Lincoln Baxter III Fix Version/s: 1.0.0.Alpha2 Resolution: Done Verified this issue no longer occurs. > mvn clean install: failing org.jboss.seam.forge.test.project.MavenFacetsTest (testAbsoluteUnknownProjectCannotInstantiate) > -------------------------------------------------------------------------------------------------------------------------- > > Key: SEAMFORGE-19 > URL: https://issues.jboss.org/browse/SEAMFORGE-19 > Project: Seam Forge > Issue Type: Bug > Environment: Maven 3.0.1, Win7 64bit, jsk 1.6_21 > Reporter: Michael Schuetz > Assignee: Lincoln Baxter III > Fix For: 1.0.0.Alpha2 > > Attachments: log.txt > > > ------------------------------------------------------------------------------- > Test set: org.jboss.seam.forge.test.project.MavenFacetsTest > ------------------------------------------------------------------------------- > Tests run: 9, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.816 sec <<< FAILURE! > testAbsoluteUnknownProjectCannotInstantiate(org.jboss.seam.forge.test.project.MavenFacetsTest) Time elapsed: 0.156 sec <<< FAILURE! > java.lang.AssertionError: > at org.junit.Assert.fail(Assert.java:91) > at org.junit.Assert.assertTrue(Assert.java:43) > at org.junit.Assert.assertNull(Assert.java:549) > at org.junit.Assert.assertNull(Assert.java:560) > at org.jboss.seam.forge.test.project.MavenFacetsTest.testAbsoluteUnknownProjectCannotInstantiate(MavenFacetsTest.java:167) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) > at org.jboss.arquillian.junit.Arquillian$6$1.invoke(Arquillian.java:251) > at org.jboss.arquillian.protocol.local.LocalMethodExecutor.invoke(LocalMethodExecutor.java:40) > at org.jboss.arquillian.impl.handler.ContainerTestExecuter.callback(ContainerTestExecuter.java:50) > at org.jboss.arquillian.impl.handler.ContainerTestExecuter.callback(ContainerTestExecuter.java:40) > at org.jboss.arquillian.impl.event.MapEventManager.fire(MapEventManager.java:63) > at org.jboss.arquillian.impl.context.AbstractEventContext.fire(AbstractEventContext.java:115) > at org.jboss.arquillian.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:157) > at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:244) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:207) > at org.jboss.arquillian.junit.Arquillian$5$1.evaluate(Arquillian.java:225) > at org.jboss.arquillian.junit.Arquillian$MultiStatementExecutor.execute(Arquillian.java:297) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:221) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:163) > at org.jboss.arquillian.junit.Arquillian$3$1.evaluate(Arquillian.java:186) > at org.jboss.arquillian.junit.Arquillian$MultiStatementExecutor.execute(Arquillian.java:297) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:182) > at org.junit.runners.ParentRunner.run(ParentRunner.java:236) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:127) > at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:59) > at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:115) > at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:102) > at org.apache.maven.surefire.Surefire.run(Surefire.java:180) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:350) > at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1021) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] Moved: (SEAMFORGE-57) Multiple SLF4J bindings for Forge

by Shane Bryzak (JIRA)

[ https://issues.jboss.org/browse/SEAMFORGE-57?page=com.atlassian.jira.plug... ] Shane Bryzak moved SEAM-34 to SEAMFORGE-57: ------------------------------------------- Project: Seam Forge (was: Seam 3) Key: SEAMFORGE-57 (was: SEAM-34) Component/s: (was: Build Infrastructure) Fix Version/s: (was: 3.0.0.Final) > Multiple SLF4J bindings for Forge > --------------------------------- > > Key: SEAMFORGE-57 > URL: https://issues.jboss.org/browse/SEAMFORGE-57 > Project: Seam Forge > Issue Type: Bug > Reporter: Martin Gencur > Priority: Optional > > I'm getting the following WARNING when running the Forge from within Seam 3 distribution: > Using Forge at /home/mgencur/Java/seam3testing/cr2/seam-3.0.0.CR2 > SLF4J: Class path contains multiple SLF4J bindings. > SLF4J: Found binding in [jar:file:/home/mgencur/Java/seam3testing/cr2/seam-3.0.0.CR2/lib/weld-servlet.jar!/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: Found binding in [jar:file:/home/mgencur/Java/seam3testing/cr2/seam-3.0.0.CR2/lib/slf4j-log4j12.jar!/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

Re: [forge-dev] Hibernate reverse engineering

by Lincoln Baxter, III

Ok, in order to proceed with this, we need to deliver jboss hibernate-tools-core to the Nexus repository. Would you like me to add you to the Forge project and assign you the ticket? https://issues.jboss.org/browse/SEAMFORGE-46 In order to do this, add the jboss-parent POM to your parent pom. <parent> <groupId>org.jboss</groupId> <artifactId>jboss-parent</artifactId> <version>5</version> </parent> This is the first step in fixing up H-tools pom. Second, the source folders are in non-standard locations. This *should* be alright since maven delivers a JAR file, but it is a little confusing to maven hackers, and could break some plugins that make poor assumptions. I would recommend using the standard maven folder structure: /src/main/java ~Lincoln On Mon, Feb 7, 2011 at 10:15 AM, Max Rydahl Andersen < max.andersen(a)redhat.com> wrote: > Hi Lincoln, > > > Hey Max, > > > > I know you'd been working on reverse-engineering databases w/hibernate > tools in forge. > > > > Do you have that code somewhere? I'd like to try to get it integrated. > > sorry, haven't had time finishing it off; but the code is at > https://github.com/maxandersen/forge/tree/htools > > requires you to build hibernate tools core locally into your maven repo for > it to work. > > /max > > -- Lincoln Baxter, III http://ocpsoft.com http://scrumshark.com "Keep it Simple"

13 years, 9 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-dev March 2011