December 2013 - forge-dev - Jboss List Archives

by Vineet Reynolds Pereira

Hey all, I managed to get a beginner (who shall be anonymous for now), to try out Forge 2. It turned out to be rather interesting, since he managed to build it from source, install JBossTools-Forge into Eclipse, before running into some issues. I think some of these would affect how we look at usability of Forge in several areas - the tooling in Eclipse, the web site etc. Some of the questions that were asked were: 1. "Is there an overview or something of forge 1/2 ?" and later (in response to this: http://www.youtube.com/watch?v=Dpou-FWWatI): "not really, it tells me more about how powerful it is - but no overview, why I should do what, says I can use it from the command line but I did not spot how, ..." I think a beginner guide would help here, that would help users who're new to even Java EE. 2. Later on, when using Forge in Eclipse, this feedback was offered: "I noticed on the 'Forge Run Command' dialog, the Tooltip did not really add much to what could be gained from the command name! ... possible it might be a good idea to have a variable sized text panel in the bottom half to give a more detailed explanation" I'm not sure if the Eclipse UI guidelines allow for that, but it's something to consider. 3. Another interesting issue is that of the EE 6/7 POMs being installed into the project: * Selected 'JPA setup' version 2.1 * Selected Wildfly Aplication Server * Specified: Java EE, forge-default * Modified HSQLDB to POSTGRES using java:jboss/datasource/ExamplDS as datasource, * and now pom.xml has <artifactId>jboss-javaee-6.0</artifactId> and other changes The EE 7 APIs were expected to added here. I've also raised FORGE-1385 for Java 1.7 support, but that's fixed and should be out in the next release, so it is moot. Discuss! Vineet

11 years

2
1
0 / 0

The git-tools addon

by Ivan St. Ivanov

Hi everybody, A few hours before 2013 is over, I am very happy to announce that the git-tools plugin from Forge 1 is finally migrated to a Forge 2 addon. I have transformed the missing functionality and the tests in Forge core addon style: different projects for api, addon, impl (containing the UI commands) and tests. The tests are passing both in Eclipse and in Maven. I have added javadoc to the APIs, README.asciidoc file and some man commands. I haven't yet issued a pull request for two reasons: * I am not sure whether you will want git-tools in the core repository or you may want it in another one * I expect some feedback from your side on my work You can access the addon code here: https://github.com/ivannov/core/tree/FORGE-1128. Once you build it and install it in your local maven repository (Java 7 and Maven 3.1 required), you may install it by simply running (FORGE_HOME should be set to Forge 2): forge --install git-tools You can review the functionality in the README file: https://github.com/ivannov/core/tree/FORGE-1128/git-tools As I have promised, I will send my feedback about the development experience in Forge 2. I will also give you some feedback on the command line shell usage on Windows (and maybe add some JIRAs to Antonio's list). And, Lincoln, I haven't forgot this: https://bugs.eclipse.org/bugs/show_bug.cgi?id=368230. At the end, I wish all of you and your families a very happy, healthy and successful 2014! Cheers, Ivan

11 years

2
5
0 / 0

Missing commands on shell (jpa-setup wizard)

by Lincoln Baxter, III

So I don't forget by the time we get back from new-years- The bug is in ShellWizard.java: https://issues.jboss.org/browse/FORGE-1407 private CommandLineParser populate(ShellContext shellContext, String line, final Map<String, InputComponent<?, ?>> inputs) throws Exception { inputs.putAll(getController().getInputs()); CommandLineParser parser = commandLineUtil.generateParser(getController(), shellContext, inputs); CommandLine cmdLine = parser.parse(line, true); Map<String, InputComponent<?, ?>> populatedInputs = commandLineUtil.populateUIInputs(cmdLine, inputs); if (getController().isValid()) { if (getController().canMoveToNextStep()) { // The bug is here. we are immediately moving to the next step and removing all inputs that are not populated. // this really needs to know if we have defaulted to next step or actually moved there willingly // it should not remove old choices until a new choice has been made getController().next().initialize(); inputs.keySet().retainAll(populatedInputs.keySet()); parser = populate(shellContext, line, inputs); } } return parser; } -- Lincoln Baxter, III http://ocpsoft.org "Simpler is better."

11 years

2
2
0 / 0

JBoss Forge 2.0.0.Beta4 is available

by George Gastaldi

More info: http://forge.jboss.org/news/2013/12/26/post-forge-2.html Happy new year everyone! George Gastaldi

11 years

3
2
0 / 0

Forge Roadmap Update for Jan 15th release and beyond

by Lincoln Baxter, III

Please feel free to add or comment if I've missed anything or if there's anything you'd like to discuss. - Forge 2.0.0.FInal to be released Jan 15th - (Does not include plugins - to be released separately as completed as other projects/individuals can spend time working with us, or as we can spend time on them.) - Plugins that are being released (or near completion) - Build System Integration - Maven - Scaffold - JSF - Angular - Database reverse engineering - Wizards - Eclipse connection profile integration - Java EE developer tooling & quick-start plugins - Jax RX / REST - JSF - CDI - etc.. - Includes wizards/Forge menu integration into JBoss Tools - Forge 2 website, hopefully by March/April -- Lincoln Baxter, III http://ocpsoft.org "Simpler is better."

11 years, 1 month

4
3
0 / 0

Re: [forge-dev] [aerogear-dev] Aerogear.js for CRUD

by Vineet Reynolds Pereira

Adding forge-dev. ----- Original Message ----- > From: "Burr Sutter" <bsutter(a)redhat.com> > To: "AeroGear Developer Mailing List" <aerogear-dev(a)lists.jboss.org> > Sent: Tuesday, December 17, 2013 1:59:41 AM > Subject: Re: [aerogear-dev] Aerogear.js for CRUD > > That seems to do the trick - now, where do we apply the fix? :-) Well, ideally this would be a feature request in Forge to support a new type of a REST resource. But a couple of modified lines might not warrant it. It would be better to treat this as a flag to be enabled during REST resource scaffolding. It would allow users to choose how the resource behaves - * send a 201 response with Location header, * send a 201 response with Location header and also a response entity. It would most likely be addressed in Forge 2. > > On Dec 16, 2013, at 3:06 PM, Vineet Reynolds Pereira < vpereira(a)redhat.com > > wrote: > > > > > > > ----- Original Message ----- > > > From: "Lucas Holmquist" < lholmqui(a)redhat.com > > To: "AeroGear Developer Mailing List" < aerogear-dev(a)lists.jboss.org > > Cc: "Vineet Reynolds Pereira" < vpereira(a)redhat.com > > Sent: Tuesday, December 17, 2013 12:53:25 AM > Subject: Re: [aerogear-dev] Aerogear.js for CRUD > > > On Dec 16, 2013, at 1:52 PM, Burr Sutter < bsutter(a)redhat.com > wrote: > > > > Adding Vineet as he has spent time on the Forge REST scaffolding. > > On Dec 16, 2013, at 7:01 AM, Sebastien Blanc < scm.blanc(a)gmail.com > wrote: > > > > Burr, > I've added some logs statements on the client and basically it seems it > can not parse the response from the server : > > I/Web Console( 1386): textStatus: parsererror at > file:///android_asset/www/js/index.js:103 > I/Web Console( 1386): error: SyntaxError: Unexpected end of input at > file:///android_asset/www/js/index.js:104 > > If I do a CURL like this : > curl -v -b cookies.txt -c cookies.txt -H "Accept: application/json" -H > "Content-type: application/json" -X POST -d > '{"phoneNumber":"1234567890","email":"newTest(a)test.com","name":"newTest"}' > http://agmobile-html5.rhcloud.com/rest/forge/members > > I should have pointed to the sources to the REST endpoint: > https://github.com/burrsutter/agmobile/blob/master/src/main/java/com/burr... > This was generated by Forge as I am too lazy to type up a full CRUD REST > endpoint myself :-) > > > > I got an correct answer but the content type is 'text/plain' , please > check your rest endpoint to be sure it's producing json as output, that > should solve your issue. > It says > @POST > @Consumes("application/json") > > needs a @Produces("application/json") > > I'm not sure that will help. The response is a HTTP 201 with a Location > header. > Is the client expecting an entity of type application/json in the response ? > > If yes, then the method should look like: > > @POST > @Consumes("application/json") > public Response create(MemberDTO dto) > { > Member entity = dto.fromDTO(null, em); > em.persist(entity); > return > Response.created(UriBuilder.fromResource(MemberEndpoint.class).path(String.valueOf(entity.getId())).build()).entity(entity).build(); > } > > I've added : .entity(entity) in the above method to populate the response > with the entity. > > > > > > > > > > > Could you also paste the commands you used in Forge to scaffold the REST > endpoints so that we can check there hasn't been an incompatibility > introduced ? > I just used the Forge Wizard that is built into JBDS/Tools > http://screencast.com/t/QrKkCoFZMUn > > error.status is 201 > error.responseText is blank > > > > > > > > On Sat, Dec 14, 2013 at 6:06 PM, Burr Sutter <bsutter(a)redhat.com> wrote: > I am having a problem with pipe.save(), likely user error :-) > > For some reason, the POST is occurring, the save seems to work but the > error callback is invoked, not the success method. > > And I am doing all of this in the context of our tooling which has some > limitations (auto-closing console/firebug lite) > > http://screencast.com/t/gosd7Qnhz > > REST endpoint: > http://agmobile-html5.rhcloud.com/rest/forge/members > Use of Forge, with the Member.java entity to offer full CRUD capabilities > > Sources: > https://github.com/burrsutter/AGContacts/blob/master/www/js/index.js > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev

11 years, 1 month

10
18
0 / 0

Meeting cancelled today

by Lincoln Baxter, III

Few participants, the holidays begin to take their toll :) We will continue working toward 2.0 Final, and work on the website will commence once we have the wireframes and HTML. -- Lincoln Baxter, III http://ocpsoft.org "Simpler is better."

11 years, 1 month

1
0
0 / 0

Problems building connection-profiles branch of jbosstools-forge

by Lincoln Baxter, III

Any ideas? ------------------ [ERROR] Cannot resolve project dependencies: [ERROR] Software being installed: org.jboss.tools.forge.ui.ext 1.1.0.qualifier [ERROR] Missing requirement: org.jboss.tools.forge.ui.ext 1.1.0.qualifier requires 'bundle org.eclipse.datatools.connectivity 1.2.9' but it could not be found [ERROR] [ERROR] Internal error: java.lang.RuntimeException: No solution found because the problem is unsatisfiable.: [Unable to satisfy dependency from org.jboss.tools.forge.ui.ext 1.1.0.qualifier to bundle org.eclipse.datatools.connectivity 1.2.9.; No solution found because the problem is unsatisfiable.] -> [Help 1] org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: No solution found because the problem is unsatisfiable.: [Unable to satisfy dependency from org.jboss.tools.forge.ui.ext 1.1.0.qualifier to bundle org.eclipse.datatools.connectivity 1.2.9.; No solution found because the problem is unsatisfiable.] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:164) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214) at org.apache.maven.cli.MavenCli.main(MavenCli.java:158) 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:601) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) Caused by: java.lang.RuntimeException: No solution found because the problem is unsatisfiable.: [Unable to satisfy dependency from org.jboss.tools.forge.ui.ext 1.1.0.qualifier to bundle org.eclipse.datatools.connectivity 1.2.9.; No solution found because the problem is unsatisfiable.] at org.eclipse.tycho.p2.resolver.AbstractResolutionStrategy.newResolutionException(AbstractResolutionStrategy.java:98) at org.eclipse.tycho.p2.resolver.ProjectorResolutionStrategy.resolve(ProjectorResolutionStrategy.java:88) at org.eclipse.tycho.p2.resolver.AbstractResolutionStrategy.resolve(AbstractResolutionStrategy.java:63) at org.eclipse.tycho.p2.impl.resolver.P2ResolverImpl.resolveDependencies(P2ResolverImpl.java:134) at org.eclipse.tycho.p2.impl.resolver.P2ResolverImpl.resolveDependencies(P2ResolverImpl.java:87) at org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.doResolvePlatform(P2TargetPlatformResolver.java:369) at org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.resolveDependencies(P2TargetPlatformResolver.java:345) at org.eclipse.tycho.core.resolver.DefaultTychoDependencyResolver.resolveProject(DefaultTychoDependencyResolver.java:109) at org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:75) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:271) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152) ... 11 more [ERROR] -- Lincoln Baxter, III http://ocpsoft.org "Simpler is better."

11 years, 1 month

2
4
0 / 0

Meeting minutes 2013-12-11

by Lincoln Baxter, III

Minutes: http://transcripts.jboss.org/meeting/irc.freenode.org/forge/2013/forge.20... Minutes (text): http://transcripts.jboss.org/meeting/irc.freenode.org/forge/2013/forge.20... Log: http://transcripts.jboss.org/meeting/irc.freenode.org/forge/2013/forge.20... Meeting summary --------------- * Agenda (lincolnthree, 15:54:08) * Forge 2 Status (lincolnthree, 15:54:08) * Forge 2 Website (lincolnthree, 15:54:18) * Github Repository organization (vineetreynolds, 15:56:41) * AngularJS scaffolding Status (vineetreynolds, 15:57:13) * Forge 2 Status (lincolnthree, 15:57:45) * gastaldi and I will be pair programming the ui-controller today (lincolnthree, 15:58:09) * Forge 2 now requires JDK 7 (gastaldi, 15:58:42) * Forge 2 Website (lincolnthree, 16:03:57) * Github Repository organization (vineetreynolds, 16:16:05) * LINK: http://paste2.org/31bZ7GdV (lincolnthree, 16:22:28) * AngularJS scaffolding Status (vineetreynolds, 16:47:19) Meeting ended at 16:50:55 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * lincolnthree (119) * gastaldi (92) * vineetreynolds (54) * koentsje (26) * dbeer (5) * jbossbot (4) * jbott (4) * crobson (2) -- Lincoln Baxter, III http://ocpsoft.org "Simpler is better."

11 years, 1 month

1
0
0 / 0

Re: [forge-dev] Forge Teamcity build linking

by Lincoln Baxter

Thanks Tomaz, We have another question. We've started seeing this error. Any ideas what this is about? http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=6826&buildType... And a snippit for you: ------------------ [13:38:57][org.jboss.forge.furnace.container:cdi] Downloaded: http://repo1.maven.org/maven2/org/jboss/jboss-parent/12/jboss-parent-12.pom (0 B at 0.0 KB/sec) [13:38:57][org.jboss.forge.furnace.container:cdi] [main] WARN org.eclipse.aether.internal.impl.DefaultUpdateCheckManager - Failed to write tracking file /store/repository/org/jboss/jboss-parent/12/jboss-parent-12.pom.lastUpdated [13:38:57][org.jboss.forge.furnace.container:cdi] java.io.FileNotFoundException: /store/repository/org/jboss/jboss-parent/12/jboss-parent-12.pom.lastUpdated (Permission denied) [13:38:57][org.jboss.forge.furnace.container:cdi] at java.io.RandomAccessFile.open(Native Method) [13:38:57][org.jboss.forge.furnace.container:cdi] at java.io.RandomAccessFile.<init>(RandomAccessFile.java:233) ------------------ Thanks! ----- Original Message ----- From: "Tomaz Cerar" <tcerar(a)redhat.com> To: "Lincoln Baxter" <lbaxter(a)redhat.com> Sent: Monday, November 25, 2013 10:33:31 AM Subject: RE: Forge Teamcity build linking Hey, All you need to do is add dependencies under build configuration. Ping me on IRC -- tomaz > -----Original Message----- > From: Lincoln Baxter [mailto:lbaxter@redhat.com] > Sent: Friday, November 22, 2013 8:49 PM > To: Tomaz Cerar > Cc: George Gastaldi > Subject: Forge Teamcity build linking > > Hey Tomaz, > > I have a question about Teamcity. We are experiencing new build failures > (apparently due to the addition of a new build module "Furnace - Container > Simple"). > > How can we link the builds so that the Core - 2.0 build has access to the build > result artifacts of this build, like you did with the Furnace Runtime and > Container CDI builds? > > I'm hoping we can learn enough to prevent the need for you to have to do > this for us again in the future. > > Thanks very much! > > -- > Lincoln Baxter, III > JBoss, by Red Hat > lbaxter(a)redhat.com > > "If you want something, you'll find a way; if you don't, you'll find an excuse."

11 years, 1 month

2
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-dev December 2013