2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-users March 2015

forge-users@lists.jboss.org

4 participants
7 discussions

Start a nNew thread

Who wants to review a tutorial on "Creating and testing a command that creates Java code" ?

by Antonio Goncalves

Hi all, We are working on a set of tutorials on "How to create and test a new command" so new comers can contribute better in an easier way. There are a few JIRAs here about this topic : https://issues.jboss.org/browse/FORGE-2231 This first tutorial is very basic but it allows answering a few bunch of questions, and show "reasonably easy" code : https://issues.jboss.org/browse/FORGE-2232 The tutorial is for now in a Google Doc document and we will need a couple of external eyes to review it : https://docs.google.com/document/d/11Y-zcl2-fp-Kxdq1wq8gM37_AUeWX6SQiYV65... Anybody interested ? We would give you write access to the document so you can change it, annotate it and question it. Thanks -- Antonio Goncalves Software architect and Java Champion Web site <http://www.antoniogoncalves.org/> | Twitter <http://twitter.com/agoncal> | LinkedIn <http://www.linkedin.com/in/agoncal> | Paris JUG <http://www.parisjug.org/> | Devoxx France <http://www.devoxx.fr/>

9 years, 1 month

2
9
0 / 0

Announcement : new addon : MetaForgeWizard

by forge-users＠lists.jboss.org

MetaForgeWizard is an addon that will save you time when creating a wizard-style addon. Take a look at wadael/MetaForgeWizard · GitHub (https://github.com/wadael/MetaForgeWizard) Thanks for your feedback. Jérôme Posted by forums Original post: https://developer.jboss.org/message/920529#920529

9 years, 1 month

2
2
0 / 0

How does Forge support Gradle

by forge-users＠lists.jboss.org

I tried giving Gradle dependency in my forge-addon parent pom.xml as <dependency> <groupId>org.jboss.forge.addon</groupId> <artifactId>gradle</artifactId> <classifier>forge-addon</classifier> <version>2.5.0.Final</version> </dependency> and i have written some code in this forge addon to do some functionality.And say i have registered "my-forge-command" in the addon Now my intention is when a user creates maven/gradle project and then when he gives (cntrl+Alt+4- in IntelliJ) my registered forge command "my-forge-command" should be visible .But only in case of Maven project the command is visible but not Gradle project.Is this expected? Or am i missing some thing.There is no error in log.And i don't think there is any fault with my code.Because this is working for Maven projects.I Assume that i am missing some configuration for Gradle to be supported. Please Help! Posted by forums Original post: https://developer.jboss.org/message/920381#920381

9 years, 1 month

1
0
0 / 0

How to give gradle addon dependency

by forge-users＠lists.jboss.org

*Hi,* *I want to add Gradle dependency through code like this* GradleModelBuilder builder = GradleModelBuilder.create(); model.addTask(GradleTaskBuilder.create() . setName("newTask") . setDependendsOn(GradleTaskBuilder.create(). setName("otherTask")) .setCode("println 'Hello!'")); But i know for that i have to add dependency in my forge addon pom.xml something like below one <dependency> <groupId>org.jboss.forge.addon</groupId> <artifactId>gradle</artifactId> <classifier>forge-addon</classifier> <version>${version}</version> </dependency> what could be the possible version for this!! Or is this way of doing is wrong? Please give me suggestion for how to give forge gradle dependency Posted by forums Original post: https://developer.jboss.org/message/920365#920365

9 years, 1 month

1
1
0 / 0

Problem creating test for a new addon I'm developing

by forge-users＠lists.jboss.org

I'm creating a forge addon and following the below folder structure of having seperate addon, impl, tests and api folders. I wrote my Facet implementation in Impl. I'm able to successfully execute the addon. However, I want to create some unit tests to test my addon. I haven't even come to stage of writing tests to my addon. I have followed http://forge.jboss.org/document/test-your-addonhttp://forge.jboss.org/doc... and created a sample test. This is what is there in my test @RunWith(Arquillian.class) public class FirstTest { @Deployment @Dependencies({ @AddonDependency(name = "org.codehaus.griffon.forge:griffon-forge-addon", version = "1.0.0-SNAPSHOT") }) public static ForgeArchive getDeployment() { ForgeArchive archive = ShrinkWrap.create(ForgeArchive.class) .addBeansXML() .addAsAddonDependencies(AddonDependencyEntry.create("org.codehaus.griffon.forge:griffon-forge-addon", "1.0.0-SNAPSHOT") ); return archive; } @Test public void testSomething() throws Exception { Assert.fail("Not implemented"); } } When I'm trying to run this test I'm getting the following error. h5. testSomething(org.codehaus.griffon.forge.FirstTest): Test runner could not locate test class [org.codehaus.griffon.forge.FirstTest] in any deployed Addon. Can anyone tell me what is the process to be followed when writing tests for our addons if we follow the structure addon, api, impl and tests? Do we have to install the addon to test it? Isn't there any way to test the addon without first installing? Is it possible to test a Facet directly without running through Forge? Posted by forums Original post: https://developer.jboss.org/message/920242#920242

9 years, 1 month

2
2
0 / 0

Build in error w. 2.13.0 , not with 2.14

by forge-users＠lists.jboss.org

Hello, I built an addon that does not build in JBDStudio (Forge 2.13.0) but builds and executes in a shell (Forge 2.14.0) In the error log view, I have org.jboss.forge.addon.projects.building.BuildException: Build failed. at org.jboss.forge.addon.maven.projects.MavenProjectBuilder.build(MavenProjectBuilder.java:102) at org.jboss.forge.addon.maven.projects.MavenProjectBuilder.build(MavenProjectBuilder.java:65) at org.jboss.forge.addon.manager.impl.ui.AddonBuildAndInstallCommand.execute(AddonBuildAndInstallCommand.java:79) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:87) at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42) at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:103) at org.jboss.forge.addon.manager.impl.ui.AddonBuildAndInstallCommand_$$_javassist_7abc5e8c-92e5-47ca-a679-97a07b1658b8.execute(AddonBuildAndInstallCommand_$$_javassist_7abc5e8c-92e5-47ca-a679-97a07b1658b8.java) at org.jboss.forge.addon.ui.impl.controller.SingleCommandControllerImpl.execute(SingleCommandControllerImpl.java:90) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:123) at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42) at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:96) at org.jboss.forge.addon.ui.controller.CommandController_$$_javassist_01609478-df41-492a-94e1-0faecf751e0a.execute(CommandController_$$_javassist_01609478-df41-492a-94e1-0faecf751e0a.java) at org.jboss.tools.forge.ui.internal.ext.wizards.ForgeWizard$1.run(ForgeWizard.java:113) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122) Which is of little help. Is there another place to look at ? My ~/.forge folder only contains the addons folder. I want to test how it behaves before to release it ( wadael/MetaForgeWizard · GitHub (https://github.com/wadael/MetaForgeWizard) ) https://github.com/wadael/MetaForgeWizard Thank you Jerome Posted by forums Original post: https://developer.jboss.org/message/920248#920248

9 years, 1 month

1
0
0 / 0

Need explanation for forge addon folder structure

by forge-users＠lists.jboss.org

I always have a doubt that why does a forge addon folder structure is something like * addon * impl * api * tests what is the relation between each other.And when we install addon why do we have to run install command on addon folder.Is there any meaning behind it?Please brief me about this folder structure. Thanks. Posted by forums Original post: https://developer.jboss.org/message/919743#919743

9 years, 2 months

1
4
0 / 0

← Newer
1
Older →