From forge-dev at lists.jboss.org Tue Jul 1 15:28:23 2014 From: forge-dev at lists.jboss.org (forge-dev at lists.jboss.org) Date: Tue, 01 Jul 2014 15:28:23 EDT Subject: [forge-dev] How do I install the Arquillian add-on from Git ? In-Reply-To: Message-ID: <237941715.21404242933273.JavaMail.jive@jive-app01.app.mwc.hst.phx2.redhat.com> I'm also getting a very similar error. It seems like forge cannot resolve plugins that are compiled and put on the local maven repository. I tried with the Arquillian addone, but I get the same problem with any plugin I try to add from git, because i then tried the plugins for TOMEE and SLF4J. I looks to me, that after the plugin clones and then compiles the plugin, it is somehow looking directly to the maven central repository instead of looking in the local (cache) repository. Maybe it's a maven configuration problem?? Posted by forums Original post: https://community.jboss.org/message/880150#880150 From lincolnbaxter at gmail.com Wed Jul 2 11:40:50 2014 From: lincolnbaxter at gmail.com (Lincoln Baxter, III) Date: Wed, 2 Jul 2014 11:40:50 -0400 Subject: [forge-dev] Forge Meeting Minutes - 2014-07-02 Message-ID: Minutes: http://transcripts.jboss.org/meeting/irc.freenode.org/forge/2014/forge.2014-07-02-14.45.html Minutes (text): http://transcripts.jboss.org/meeting/irc.freenode.org/forge/2014/forge.2014-07-02-14.45.txt Log: http://transcripts.jboss.org/meeting/irc.freenode.org/forge/2014/forge.2014-07-02-14.45.log.html Meeting summary --------------- * Agenda (lincolnthree, 14:45:21) * JBT Beta3 Lockdown Tasks (lincolnthree, 14:47:46) * codefreeze for JBT Beta3 is today (gastaldi, 14:48:00) * LINK: https://issues.jboss.org/browse/JBIDE-17723 (lincolnthree, 14:50:03) * LINK: https://issues.jboss.org/browse/JBIDE-17622 (lincolnthree, 14:50:27) * LINK: https://issues.jboss.org/browse/JBIDE-17008?filter=12321870&jql=project%20%3D%20JBIDE%20AND%20affectedVersion%20%3E%3D%204.2.0.Beta1%20and%20status%20not%20in%20(Resolved%2C%20Closed%2C%20Done)%20AND%20component%20%3D%20forge%20ORDER%20BY%20status%20ASC (lincolnthree, 14:51:46) * 2.7.0.Final release (lincolnthree, 15:09:06) * 2.7.0.Final will be released today (gastaldi, 15:10:02) * Website status (gastaldi, 15:11:21) * waiting on eng-ops to update CNAME to new site (lincolnthree, 15:15:48) * designer is working on new visual theme, will apply once completed (lincolnthree, 15:16:02) * new visual design target date is August 15 (lincolnthree, 15:16:10) * Windows issues (yet again) (lincolnthree, 15:16:19) * Forge 2.7.0.Final will be in JBT Beta3 (lincolnthree, 15:21:42) Meeting ended at 15:21:44 UTC. -- Lincoln Baxter, III http://ocpsoft.org "Simpler is better." -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20140702/fa3cf1f4/attachment.html From ggastald at redhat.com Wed Jul 2 21:10:44 2014 From: ggastald at redhat.com (George Gastaldi) Date: Wed, 2 Jul 2014 21:10:44 -0400 (EDT) Subject: [forge-dev] Forge 2.7.0.Final released Message-ID: Hello everyone! JBoss Forge 2.7.0.Final was just released. Blog post in the works. Forge on! George Gastaldi From danielsoro at gmail.com Wed Jul 2 21:22:46 2014 From: danielsoro at gmail.com (Daniel Cunha) Date: Wed, 2 Jul 2014 22:22:46 -0300 Subject: [forge-dev] [forge-users] Forge 2.7.0.Final released In-Reply-To: References: Message-ID: +1 On Wed, Jul 2, 2014 at 10:10 PM, George Gastaldi wrote: > Hello everyone! > > JBoss Forge 2.7.0.Final was just released. > > Blog post in the works. > > Forge on! > > George Gastaldi > _______________________________________________ > forge-users mailing list > forge-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/forge-users > -- Daniel Cunha (soro) Blog: http://www.danielsoro.com.br Twitter: https://twitter.com/dvlc_ GitHub: https://github.com/danielsoro LinkedIn: http://www.linkedin.com/in/danielvlcunha -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20140702/cafe2962/attachment-0001.html From antonio.mailing at gmail.com Thu Jul 3 04:34:13 2014 From: antonio.mailing at gmail.com (Antonio Goncalves) Date: Thu, 3 Jul 2014 10:34:13 +0200 Subject: [forge-dev] [forge-users] Forge 2.7.0.Final released In-Reply-To: References: Message-ID: And the new website too with documentation !!!! 2014-07-03 3:22 GMT+02:00 Daniel Cunha : > +1 > > > On Wed, Jul 2, 2014 at 10:10 PM, George Gastaldi > wrote: > >> Hello everyone! >> >> JBoss Forge 2.7.0.Final was just released. >> >> Blog post in the works. >> >> Forge on! >> >> George Gastaldi >> _______________________________________________ >> forge-users mailing list >> forge-users at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/forge-users >> > > > > -- > Daniel Cunha (soro) > Blog: http://www.danielsoro.com.br > Twitter: https://twitter.com/dvlc_ > GitHub: https://github.com/danielsoro > LinkedIn: http://www.linkedin.com/in/danielvlcunha > > _______________________________________________ > forge-users mailing list > forge-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/forge-users > -- Antonio Goncalves Software architect and Java Champion Web site | Twitter | LinkedIn | Paris JUG | Devoxx France -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20140703/562ae3bf/attachment.html From lincolnbaxter at gmail.com Thu Jul 3 13:55:59 2014 From: lincolnbaxter at gmail.com (Lincoln Baxter, III) Date: Thu, 3 Jul 2014 13:55:59 -0400 Subject: [forge-dev] [forge-users] Forge 2.7.0.Final released In-Reply-To: References: Message-ID: Thanks everyone for all of your hard work on this release! This really is the best release yet! On Thu, Jul 3, 2014 at 4:34 AM, Antonio Goncalves wrote: > And the new website too with documentation !!!! > > > 2014-07-03 3:22 GMT+02:00 Daniel Cunha : > > +1 >> >> >> On Wed, Jul 2, 2014 at 10:10 PM, George Gastaldi >> wrote: >> >>> Hello everyone! >>> >>> JBoss Forge 2.7.0.Final was just released. >>> >>> Blog post in the works. >>> >>> Forge on! >>> >>> George Gastaldi >>> _______________________________________________ >>> forge-users mailing list >>> forge-users at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/forge-users >>> >> >> >> >> -- >> Daniel Cunha (soro) >> Blog: http://www.danielsoro.com.br >> Twitter: https://twitter.com/dvlc_ >> GitHub: https://github.com/danielsoro >> LinkedIn: http://www.linkedin.com/in/danielvlcunha >> >> _______________________________________________ >> forge-users mailing list >> forge-users at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/forge-users >> > > > > -- > Antonio Goncalves > Software architect and Java Champion > > Web site | Twitter > | LinkedIn > | Paris JUG > | Devoxx France > > _______________________________________________ > forge-users mailing list > forge-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/forge-users > -- Lincoln Baxter, III http://ocpsoft.org "Simpler is better." -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20140703/849b7a80/attachment.html From danielsoro at gmail.com Thu Jul 3 20:45:54 2014 From: danielsoro at gmail.com (Daniel Cunha) Date: Thu, 3 Jul 2014 21:45:54 -0300 Subject: [forge-dev] [Roaster] Type instanceof Message-ID: Hi folks, I want do that: type instanceof Number. That case, my type can be AtomicInteger, AtomicLong, BigDecimal, BigInteger, Byte, Double, Float, Integer, Long and Short Eg:. public static Type getIdType(JavaClass entity) { for (Member member : entity.getMembers()) { if (member.hasAnnotation(Id.class)) { if (member instanceof Method) { return ((Method) member).getReturnType(); } if (member instanceof Field) { return ((Field) member).getType(); } } } return null; } public static boolean isNumberIdType(JavaClass entity) { return getIdType(entity) instanceof Number; } I see the code and I don?t see a simple form to do it. How I do that with Roaster Type? I thought to do that in Types (roaster util): public static boolean isNumber(final String type) { if (isBasicType(type)) { if (isPrimitive(type)) { return Arrays.asList("int", "long", "float", "double", "short").contains(type); } return Arrays.asList("Boolean", "Byte", "Double", "Float", "Integer", "Long", "Short").contains( type); } return false; } But, it isn?t good. ? -- Daniel Cunha (soro) Blog: http://www.danielsoro.com.br Twitter: https://twitter.com/dvlc_ GitHub: https://github.com/danielsoro LinkedIn: http://www.linkedin.com/in/danielvlcunha -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20140703/3b8d611c/attachment.html From ggastald at redhat.com Thu Jul 3 23:06:42 2014 From: ggastald at redhat.com (George Gastaldi) Date: Thu, 3 Jul 2014 23:06:42 -0400 (EDT) Subject: [forge-dev] [Roaster] Type instanceof In-Reply-To: References: Message-ID: <2104CFFE-7E0C-42F9-81B3-DE5DB310836A@redhat.com> Hi Daniel, You could try to load the class using: Class.forName and then attempt to check if the class isAssignableFrom(Number.class) This will not work if the class does not belong to the current classloader, but I am not sure if you're going to run into this issue specifically. > Em 03/07/2014, ?s 21:46, Daniel Cunha escreveu: > > Hi folks, > > I want do that: > > type instanceof Number. > That case, my type can be AtomicInteger, AtomicLong, BigDecimal, BigInteger, Byte, Double, Float, Integer, Long and Short > > Eg:. > > public static Type getIdType(JavaClass entity) > { > for (Member member : entity.getMembers()) > { > if (member.hasAnnotation(Id.class)) > { > if (member instanceof Method) > { > return ((Method) member).getReturnType(); > } > if (member instanceof Field) > { > return ((Field) member).getType(); > } > } > } > return null; > } > public static boolean isNumberIdType(JavaClass entity) > { > return getIdType(entity) instanceof Number; > } > I see the code and I don?t see a simple form to do it. > How I do that with Roaster Type? > > I thought to do that in Types (roaster util): > > public static boolean isNumber(final String type) > { > if (isBasicType(type)) > { > if (isPrimitive(type)) > { > return Arrays.asList("int", "long", "float", "double", "short").contains(type); > } > return Arrays.asList("Boolean", "Byte", "Double", "Float", "Integer", "Long", "Short").contains( > type); > } > return false; > } > But, it isn?t good. > > ? > -- > Daniel Cunha (soro) > Blog: http://www.danielsoro.com.br > Twitter: https://twitter.com/dvlc_ > GitHub: https://github.com/danielsoro > LinkedIn: http://www.linkedin.com/in/danielvlcunha > _______________________________________________ > forge-dev mailing list > forge-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/forge-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20140703/e75c0391/attachment-0001.html From danielsoro at gmail.com Fri Jul 4 05:27:19 2014 From: danielsoro at gmail.com (Daniel Cunha) Date: Fri, 4 Jul 2014 06:27:19 -0300 Subject: [forge-dev] [Roaster] Type instanceof In-Reply-To: <2104CFFE-7E0C-42F9-81B3-DE5DB310836A@redhat.com> References: <2104CFFE-7E0C-42F9-81B3-DE5DB310836A@redhat.com> Message-ID: Hmmm, Ok. Thank you very much George. :) On Fri, Jul 4, 2014 at 12:06 AM, George Gastaldi wrote: > Hi Daniel, > > You could try to load the class using: Class.forName and then attempt to > check if the class isAssignableFrom(Number.class) > > This will not work if the class does not belong to the current > classloader, but I am not sure if you're going to run into this issue > specifically. > > Em 03/07/2014, ?s 21:46, Daniel Cunha escreveu: > > Hi folks, > > I want do that: > > type instanceof Number. > > That case, my type can be AtomicInteger, AtomicLong, BigDecimal, > BigInteger, Byte, Double, Float, Integer, Long and Short > > Eg:. > > public static Type getIdType(JavaClass entity) > { > for (Member member : entity.getMembers()) > { > if (member.hasAnnotation(Id.class)) > { > if (member instanceof Method) > { > return ((Method) member).getReturnType(); > } > if (member instanceof Field) > { > return ((Field) member).getType(); > } > } > } > return null; > } > > public static boolean isNumberIdType(JavaClass entity) > { > return getIdType(entity) instanceof Number; > } > > I see the code and I don?t see a simple form to do it. > How I do that with Roaster Type? > > I thought to do that in Types (roaster util): > > public static boolean isNumber(final String type) > { > if (isBasicType(type)) > { > if (isPrimitive(type)) > { > return Arrays.asList("int", "long", "float", "double", "short").contains(type); > } > return Arrays.asList("Boolean", "Byte", "Double", "Float", "Integer", "Long", "Short").contains( > type); > } > return false; > } > > But, it isn?t good. > ? > -- > Daniel Cunha (soro) > Blog: http://www.danielsoro.com.br > Twitter: https://twitter.com/dvlc_ > GitHub: https://github.com/danielsoro > LinkedIn: http://www.linkedin.com/in/danielvlcunha > > _______________________________________________ > forge-dev mailing list > forge-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/forge-dev > > > _______________________________________________ > forge-dev mailing list > forge-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/forge-dev > -- Daniel Cunha (soro) Blog: http://www.danielsoro.com.br Twitter: https://twitter.com/dvlc_ GitHub: https://github.com/danielsoro LinkedIn: http://www.linkedin.com/in/danielvlcunha -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20140704/e6d19d54/attachment.html From lincolnbaxter at gmail.com Mon Jul 7 11:42:04 2014 From: lincolnbaxter at gmail.com (Lincoln Baxter, III) Date: Mon, 7 Jul 2014 11:42:04 -0400 Subject: [forge-dev] Forge and Camel Archetypes In-Reply-To: <53907F17.8090105@redhat.com> References: <2F7EFE57-E1BF-4CD7-AA38-B67609975F79@redhat.com> <1F080CFD-FBA6-4E7B-978C-D5A34ABD3ED4@redhat.com> <537464FD.5050803@redhat.com> <0DA46515-0768-4E4F-8D36-8667FA11D212@redhat.com> <537466BA.1070505@redhat.com> <537C8EFB.7010809@redhat.com> <2D86C31E-3FCF-4E7F-BB0A-CFE89939FA3C@redhat.com> <53907F17.8090105@redhat.com> Message-ID: Hi Grzegorz, I'm sorry for dropping the ball on this. For Forge, I've set up a repository for you in https://github.com/forge/addon-maven-archetype. I've also created an empty Forge command for you to use as a starting point. Note, the project is split into addon/api/impl/spi/tests. The addon/ project is classified as a 'forge-addon' JAR. More details on addon development can be found here: http://forge.jboss.org/document/develop-an-addon and info about the UI addon (used to create commands), can be found here: http://forge.jboss.org/addon/org.jboss.forge.addon:ui Please find me on #forge IRC if you get stuck, or reply here! ~Lincoln On Thu, Jun 5, 2014 at 10:30 AM, Grzegorz Grzybek wrote: > Hello > > Finally I have time to start the discussion about the use of Maven > Archetypes in both JBoss Fuse and JBoss Fabric. > > Here are the links to relevant issues: > - https://issues.jboss.org/browse/FORGE-273 > - https://github.com/fabric8io/fabric8/issues/1091 > > Currently we have (here: > https://github.com/fabric8io/fabric8/blob/master/tooling/camel-tooling-util/src/main/java/io/fabric8/camel/tooling/util/ArchetypeHelper.java) > a helper which can unpack maven archetype and correctly replace ${VAR} > variables in archetype resources. > > Let's first say what we want to achieve. I'd say (please provide comments > if I misunderstood something): > Basic: > - to be able to unpack any Maven Archetype JAR and create working ("mvn > clean install"able) project in FileSystem *without* using Maven > archetype-related libraries > - to be able to replace variables in archetype resources > - to be able to evaluate Velocity expressions (they may be present in the > archetypes) > Discovery: > - to be able to read list of available archetypes > - to be able to discover available archetypes and create the above list > (explicit distinction to free ourselves from finding the archetypes in > M2_REPO each time) > Help: > - to be able to discover archetype parameters (this is the main goal - to > make something more user/tab-completion friendly than "mvn > archetype:create" with millions of options) > - to provide commands (Karaf/Gogo or JBoss Forge) for project creation > - to ask users (GUI? Console? Hawt.io?) for required archetype:create > params > > OK. I'd like to start a project (https://github.com/forge/ or > https://github.com/fusesource/ or https://github.com/jboss/ or > https://github.com/jboss-fuse/ - any suggestions?) which will do most of > the above and will be a foundation of: > - karaf/fabric command > - Forge addon(?) > > Any suggestions? > > --- > regards > Grzegorz Grzybek > > > That sounds good. Please post to forge-dev at lists.jboss.org when you want > help getting this rolling! > > > On Wed, May 21, 2014 at 9:10 AM, James Strachan > wrote: > >> Hey :) >> >> The scala code is ported to Java now; why don?t we get the little >> ?project creator? command in fabric8 working; then when its there, we could >> post it to the forge list to see about including/sharing/reusing the same >> stuff there too? >> >> On 21 May 2014, at 12:33, Grzegorz Grzybek wrote: >> >> Hello - sorry I couldn't start the discussion... But I still remember >> that it's quite important ;) >> >> regards >> Grzegorz Grzybek >> >> I think that sounds like a good idea. If we can consume this as a >> library, it would make things very easy to implement. It would also >> probably give you guys a migration path so you don't immediately have to >> jump to Forge on drop 0. >> >> Forge has a number of ways of locating resources, we can come up with a >> nice pattern for this :) >> >> Shall we move this discussion to forge-dev at lists.jboss.org or #forge on >> irc.freenode.net and get started? >> >> ~Lincoln >> >> >> On Thu, May 15, 2014 at 3:13 AM, James Strachan >> wrote: >> >>> Yeah, we might wanna polish the archetype generator code into its own >>> jar/bundle thats got minimal dependencies & is easier to use stand alone >>> (so it could be more easily consumed from inside Forge). >>> >>> For the ?create project? command/plugin I figured we?d discover the >>> available archetypes on the classpath somehow; in Fuse IDE (the Fuse/Camel >>> plugins now in JBDS) we just did a bit of code generation to put the >>> archetype jars inside the plugin. Something a bit more extensible, >>> eventually, might be nice for Forge; though for fabric8 just having a >>> curated list of archetypes from the fabric8 project itself will be fine for >>> us for a while ;) >>> >>> >>> On 15 May 2014, at 08:03, Grzegorz Grzybek wrote: >>> >>> Hello! >>> >>> Awesome, thanks Grzegorz! >>> >>> BTW a bit of background for you, sorry I should have said - there?s >>> been discussions in the past of adding a nice ability to create new >>> projects from archetypes nicely into JBoss Forge: >>> https://issues.jboss.org/browse/FORGE-273 >>> >>> http://forge.jboss.org/ >>> >>> the mvn command line to generate archetypes isn?t awesome ;) and we >>> could curate a nice default set with auto-completion of all the known jboss >>> archetypes from our projects (and maybe have a nice little way to filter >>> them by tag/project name/tech etc) with tab completion etc >>> >>> Thanks for links - so another item on my TODO list ;) >>> I'll think about how to make it easier both for Forge and commands >>> inside Fabric8. >>> >>> regards >>> Grzegorz >>> >>> >>> On 15 May 2014, at 07:55, Grzegorz Grzybek wrote: >>> >>> Hello! >>> >>> I successfully ported insight-maven stuff from Scala (it's Maven's >>> Aether concept to deal with repositories). But now I'm 30% in >>> camel-tooling-util. Scala is not really needed here and I see it has much >>> more cons than pros! >>> I know that for Scala ninjas this language is the ultimate expression >>> tool, but reading it after few years is not such a Zen experience after all. >>> >>> As someone said - Java8 is the new Java, not Scala. Of course I don't >>> want to rewrite all this code into lambda-spaghetti, but good old Java6 >>> syntax is enough :) >>> >>> And after porting camel-tooling-util back to Java, I'll look at >>> https://github.com/fabric8io/fabric8/issues/1091 which is about making >>> creating projects from archetypes much easier. >>> >>> regards >>> Grzegorz >>> >>> Cool; wanna CC Grzegorz and myself?; am hoping at some point Grzegorz >>> gets the chance to port the existing Archetype creation code from scala to >>> java so its a little leaner & meaner and easier to reuse in Forge. >>> >>> On 14 May 2014, at 20:31, Lincoln Baxter, III >>> wrote: >>> >>> Okay cool. We'll continue to go down the archetype route and see if we >>> can get that working for you guys. It would help if we had someone on your >>> team who could take point on this so we can assist. Is that possible? >>> >>> >>> On Wed, May 14, 2014 at 3:29 PM, James Strachan >>> wrote: >>> >>>> Ah yeah - just chatted to Dave; this is some gem based stuff for >>>> generating projects from templates; which is cool too. We went the maven >>>> archetype direction in Fuse IDE (now the Fuse / Camel tooling in JBDS) and >>>> now have lots of archetypes (both on upstream projects like camel & cxf and >>>> in JBoss Fuse); so I?m personally more keen to support archetypes ASAP; but >>>> the more tooling and options the better! :) >>>> >>>> On 14 May 2014, at 17:58, Lincoln Baxter, III >>>> wrote: >>>> >>>> https://issues.jboss.org/browse/FORGE-273 >>>> >>>> Also just got contacted by some people from GSS who are working on >>>> fusegen and want to merge that into Forge. Do you know anything about that? >>>> >>>> Wai Chun Hoi, and Dave Stanley. >>>> >>>> ~Lincoln >>>> >>>> >>>> On Wed, Apr 16, 2014 at 11:50 AM, James Strachan >>>> wrote: >>>> >>>>> Sounds cool; am around until about 2-3pm I think so late morning >>>>> sounds cool. >>>>> >>>>> FWIW we added an archetype generator a while back into eclipse so it >>>>> was easy for folks to start projects & we pre-baked all our camel/fuse >>>>> archetypes - as using the maven archetype:generate command line is so >>>>> utterly awful. >>>>> >>>>> Here?s the code to create an archetype from the mvn coordinates of >>>>> the archetype distro: >>>>> >>>>> https://github.com/fabric8io/fabric8/blob/master/tooling/camel-tooling-util/src/main/scala/io/fabric8/camel/tooling/util/ArchetypeHelper.scala#L45 >>>>> >>>>> e.g. here?s a test case that creates a bunch of archetypes - no >>>>> maven is required etc: >>>>> >>>>> https://github.com/fabric8io/fabric8/blob/master/tooling/camel-tooling-util/src/test/scala/io/fabric8/camel/tooling/util/ArchetypeTest.scala#L29 >>>>> >>>>> I was hoping we could cobble something like this into a standard >>>>> command; then have nice tab completion on the list of archetypes we ship by >>>>> default in Forge which groks all the jboss / fuse / apache archetypes we >>>>> want to prime it with; and make it easy for folks to add/load/configure >>>>> others. e.g. JBoss Fuse ships with a bunch of archetypes (but they are not >>>>> sync?d to maven central); so it?d be nice if all jboss products that have >>>>> archetypes were baked into Forge (e.g. EAP / Fuse / Fuse Service Works / >>>>> BRMS etc). >>>>> >>>>> Hope that helps - would love to port the code to plain java ;) but I >>>>> guess whats another massive jar dependency on spring-library between >>>>> friends ;) >>>>> >>>>> Anyway - hope to see you around this morning. Go Errai! :) >>>>> >>>>> >>>>> >>>>> On 16 Apr 2014, at 02:52, Lincoln Baxter, III < >>>>> lincolnbaxter at gmail.com> wrote: >>>>> >>>>> Let's talk about this tomorrow (today.) I'll be over at the conference >>>>> in the late morning. And I'll be at the hack-fest. >>>>> >>>>> -- >>>>> Lincoln Baxter, III >>>>> http://ocpsoft.org >>>>> "Simpler is better." >>>>> >>>>> >>>>> >>>>> James >>>>> ------- >>>>> Red Hat >>>>> >>>>> Email: jstracha at redhat.com >>>>> Web: http://fusesource.com >>>>> Twitter: jstrachan, fusenews >>>>> Blog: http://macstrac.blogspot.com/ >>>>> >>>>> Open Source Integration >>>>> >>>>> >>>> >>>> >>>> -- >>>> Lincoln Baxter, III >>>> http://ocpsoft.org >>>> "Simpler is better." >>>> >>>> >>>> >>>> James >>>> ------- >>>> Red Hat >>>> >>>> Twitter: @jstrachan >>>> Email: jstracha at redhat.com >>>> Blog: http://macstrac.blogspot.com/ >>>> >>>> hawtio: http:/ /hawt.io/ >>>> fabric8: http:/ /fabric8.io/ >>>> >>>> Open Source Integration >>>> >>>> >>> >>> >>> -- >>> Lincoln Baxter, III >>> http://ocpsoft.org >>> "Simpler is better." >>> >>> >>> >>> James >>> ------- >>> Red Hat >>> >>> Twitter: @jstrachan >>> Email: jstracha at redhat.com >>> Blog: http://macstrac.blogspot.com/ >>> >>> hawtio: http:/ /hawt.io/ >>> fabric8: http:/ /fabric8.io/ >>> >>> Open Source Integration >>> >>> >>> >>> >>> James >>> ------- >>> Red Hat >>> >>> Twitter: @jstrachan >>> Email: jstracha at redhat.com >>> Blog: http://macstrac.blogspot.com/ >>> >>> hawtio: http:/ /hawt.io/ >>> fabric8: http:/ /fabric8.io/ >>> >>> Open Source Integration >>> >>> >>> >>> >>> James >>> ------- >>> Red Hat >>> >>> Twitter: @jstrachan >>> Email: jstracha at redhat.com >>> Blog: http://macstrac.blogspot.com/ >>> >>> hawtio: http:/ /hawt.io/ >>> fabric8: http:/ /fabric8.io/ >>> >>> Open Source Integration >>> >>> >> >> >> -- >> Lincoln Baxter, III >> http://ocpsoft.org >> "Simpler is better." >> >> >> >> >> James >> ------- >> Red Hat >> >> Twitter: @jstrachan >> Email: jstracha at redhat.com >> Blog: http://macstrac.blogspot.com/ >> >> hawtio: http:/ /hawt.io/ >> fabric8: http:/ /fabric8.io/ >> >> Open Source Integration >> >> > > > -- > Lincoln Baxter, III > http://ocpsoft.org > "Simpler is better." > > > -- Lincoln Baxter, III http://ocpsoft.org "Simpler is better." -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20140707/75f60997/attachment-0001.html From ggrzybek at redhat.com Tue Jul 8 02:29:16 2014 From: ggrzybek at redhat.com (Grzegorz Grzybek) Date: Tue, 08 Jul 2014 08:29:16 +0200 Subject: [forge-dev] Forge and Camel Archetypes In-Reply-To: References: <2F7EFE57-E1BF-4CD7-AA38-B67609975F79@redhat.com> <1F080CFD-FBA6-4E7B-978C-D5A34ABD3ED4@redhat.com> <537464FD.5050803@redhat.com> <0DA46515-0768-4E4F-8D36-8667FA11D212@redhat.com> <537466BA.1070505@redhat.com> <537C8EFB.7010809@redhat.com> <2D86C31E-3FCF-4E7F-BB0A-CFE89939FA3C@redhat.com> <53907F17.8090105@redhat.com> Message-ID: <53BB8FBC.7050705@redhat.com> Hello Lincoln! Thanks for the skeleton project! That'll sure help me start moving what I've done in Fabric8 into Forge. Currently we have 3 commands in Fabric: - list available archetypes (only a list included with Fabric8 distro) - show details about single archetype - generate project from one of the archetypes into specified directory. User is asked to specify (or accept default) parameters of archetype + of course groupId/artifactId/version/package Give me a little time to read about developing addons for Forge! best regards Grzegorz Grzybek > Hi Grzegorz, > > I'm sorry for dropping the ball on this. For Forge, I've set up a > repository for you in https://github.com/forge/addon-maven-archetype. > I've also created an empty Forge command for you to use as a starting point. > > Note, the project is split into addon/api/impl/spi/tests. The addon/ > project is classified as a 'forge-addon' JAR. More details on addon > development can be found here: > http://forge.jboss.org/document/develop-an-addon and info about the UI > addon (used to create commands), can be found here: > http://forge.jboss.org/addon/org.jboss.forge.addon:ui > > Please find me on #forge IRC if you get stuck, or reply here! > > ~Lincoln > > > On Thu, Jun 5, 2014 at 10:30 AM, Grzegorz Grzybek > wrote: > > Hello > > Finally I have time to start the discussion about the use of Maven > Archetypes in both JBoss Fuse and JBoss Fabric. > > Here are the links to relevant issues: > - https://issues.jboss.org/browse/FORGE-273 > - https://github.com/fabric8io/fabric8/issues/1091 > > Currently we have (here: > https://github.com/fabric8io/fabric8/blob/master/tooling/camel-tooling-util/src/main/java/io/fabric8/camel/tooling/util/ArchetypeHelper.java) > a helper which can unpack maven archetype and correctly replace > ${VAR} variables in archetype resources. > > Let's first say what we want to achieve. I'd say (please provide > comments if I misunderstood something): > Basic: > - to be able to unpack any Maven Archetype JAR and create working > ("mvn clean install"able) project in FileSystem *without* using > Maven archetype-related libraries > - to be able to replace variables in archetype resources > - to be able to evaluate Velocity expressions (they may be present > in the archetypes) > Discovery: > - to be able to read list of available archetypes > - to be able to discover available archetypes and create the above > list (explicit distinction to free ourselves from finding the > archetypes in M2_REPO each time) > Help: > - to be able to discover archetype parameters (this is the main > goal - to make something more user/tab-completion friendly than "mvn > archetype:create" with millions of options) > - to provide commands (Karaf/Gogo or JBoss Forge) for project creation > - to ask users (GUI? Console? Hawt.io?) for required > archetype:create params > > OK. I'd like to start a project (https://github.com/forge/ or > https://github.com/fusesource/ or https://github.com/jboss/ or > https://github.com/jboss-fuse/ - any suggestions?) which will do > most of the above and will be a foundation of: > - karaf/fabric command > - Forge addon(?) > > Any suggestions? > > --- > regards > Grzegorz Grzybek > > >> That sounds good. Please post to forge-dev at lists.jboss.org >> when you want help getting this >> rolling! >> >> >> On Wed, May 21, 2014 at 9:10 AM, James Strachan >> > wrote: >> >> Hey :) >> >> The scala code is ported to Java now; why don?t we get the >> little ?project creator? command in fabric8 working; then when >> its there, we could post it to the forge list to see about >> including/sharing/reusing the same stuff there too? >> >> On 21 May 2014, at 12:33, Grzegorz Grzybek >> > wrote: >>> Hello - sorry I couldn't start the discussion... But I still >>> remember that it's quite important ;) >>> >>> regards >>> Grzegorz Grzybek >>>> I think that sounds like a good idea. If we can consume this >>>> as a library, it would make things very easy to implement. >>>> It would also probably give you guys a migration path so you >>>> don't immediately have to jump to Forge on drop 0. >>>> >>>> Forge has a number of ways of locating resources, we can >>>> come up with a nice pattern for this :) >>>> >>>> Shall we move this discussion to forge-dev at lists.jboss.org >>>> or #forge on >>>> irc.freenode.net and get started? >>>> >>>> ~Lincoln >>>> >>>> >>>> On Thu, May 15, 2014 at 3:13 AM, James Strachan >>>> > wrote: >>>> >>>> Yeah, we might wanna polish the archetype generator code >>>> into its own jar/bundle thats got minimal dependencies & >>>> is easier to use stand alone (so it could be more easily >>>> consumed from inside Forge). >>>> >>>> For the ?create project? command/plugin I figured we?d >>>> discover the available archetypes on the classpath >>>> somehow; in Fuse IDE (the Fuse/Camel plugins now in >>>> JBDS) we just did a bit of code generation to put the >>>> archetype jars inside the plugin. Something a bit more >>>> extensible, eventually, might be nice for Forge; though >>>> for fabric8 just having a curated list of archetypes >>>> from the fabric8 project itself will be fine for us for >>>> a while ;) >>>> >>>> >>>> On 15 May 2014, at 08:03, Grzegorz Grzybek >>>> > wrote: >>>>> Hello! >>>>>> Awesome, thanks Grzegorz! >>>>>> >>>>>> BTW a bit of background for you, sorry I should have >>>>>> said - there?s been discussions in the past of adding >>>>>> a nice ability to create new projects from archetypes >>>>>> nicely into JBoss Forge: >>>>>> https://issues.jboss.org/browse/FORGE-273 >>>>>> >>>>>> http://forge.jboss.org/ >>>>>> >>>>>> the mvn command line to generate archetypes isn?t >>>>>> awesome ;) and we could curate a nice default set with >>>>>> auto-completion of all the known jboss archetypes from >>>>>> our projects (and maybe have a nice little way to >>>>>> filter them by tag/project name/tech etc) with tab >>>>>> completion etc >>>>> Thanks for links - so another item on my TODO list ;) >>>>> I'll think about how to make it easier both for Forge >>>>> and commands inside Fabric8. >>>>> >>>>> regards >>>>> Grzegorz >>>>>> >>>>>> On 15 May 2014, at 07:55, Grzegorz Grzybek >>>>>> > wrote: >>>>>>> Hello! >>>>>>> >>>>>>> I successfully ported insight-maven stuff from Scala >>>>>>> (it's Maven's Aether concept to deal with >>>>>>> repositories). But now I'm 30% in camel-tooling-util. >>>>>>> Scala is not really needed here and I see it has much >>>>>>> more cons than pros! >>>>>>> I know that for Scala ninjas this language is the >>>>>>> ultimate expression tool, but reading it after few >>>>>>> years is not such a Zen experience after all. >>>>>>> >>>>>>> As someone said - Java8 is the new Java, not Scala. >>>>>>> Of course I don't want to rewrite all this code into >>>>>>> lambda-spaghetti, but good old Java6 syntax is enough :) >>>>>>> >>>>>>> And after porting camel-tooling-util back to Java, >>>>>>> I'll look at >>>>>>> https://github.com/fabric8io/fabric8/issues/1091 >>>>>>> which is about making creating projects from >>>>>>> archetypes much easier. >>>>>>> >>>>>>> regards >>>>>>> Grzegorz >>>>>>>> Cool; wanna CC Grzegorz and myself?; am hoping at >>>>>>>> some point Grzegorz gets the chance to port the >>>>>>>> existing Archetype creation code from scala to java >>>>>>>> so its a little leaner & meaner and easier to reuse >>>>>>>> in Forge. >>>>>>>> >>>>>>>> On 14 May 2014, at 20:31, Lincoln Baxter, III >>>>>>>> >>>>>>> > wrote: >>>>>>>>> Okay cool. We'll continue to go down the archetype >>>>>>>>> route and see if we can get that working for you >>>>>>>>> guys. It would help if we had someone on your team >>>>>>>>> who could take point on this so we can assist. Is >>>>>>>>> that possible? >>>>>>>>> >>>>>>>>> >>>>>>>>> On Wed, May 14, 2014 at 3:29 PM, James Strachan >>>>>>>>> > >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>> Ah yeah - just chatted to Dave; this is some >>>>>>>>> gem based stuff for generating projects from >>>>>>>>> templates; which is cool too. We went the maven >>>>>>>>> archetype direction in Fuse IDE (now the Fuse / >>>>>>>>> Camel tooling in JBDS) and now have lots of >>>>>>>>> archetypes (both on upstream projects like >>>>>>>>> camel & cxf and in JBoss Fuse); so I?m >>>>>>>>> personally more keen to support archetypes >>>>>>>>> ASAP; but the more tooling and options the >>>>>>>>> better! :) >>>>>>>>> >>>>>>>>> On 14 May 2014, at 17:58, Lincoln Baxter, III >>>>>>>>> >>>>>>>> > wrote: >>>>>>>>> >>>>>>>>>> https://issues.jboss.org/browse/FORGE-273 >>>>>>>>>> >>>>>>>>>> Also just got contacted by some people from >>>>>>>>>> GSS who are working on fusegen and want to >>>>>>>>>> merge that into Forge. Do you know anything >>>>>>>>>> about that? >>>>>>>>>> Wai Chun Hoi, and Dave Stanley. >>>>>>>>>> >>>>>>>>>> ~Lincoln >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Wed, Apr 16, 2014 at 11:50 AM, James >>>>>>>>>> Strachan >>>>>>>>> > wrote: >>>>>>>>>> >>>>>>>>>> Sounds cool; am around until about 2-3pm I >>>>>>>>>> think so late morning sounds cool. >>>>>>>>>> >>>>>>>>>> FWIW we added an archetype generator a >>>>>>>>>> while back into eclipse so it was easy for >>>>>>>>>> folks to start projects & we pre-baked all >>>>>>>>>> our camel/fuse archetypes - as using the >>>>>>>>>> maven archetype:generate command line is >>>>>>>>>> so utterly awful. >>>>>>>>>> >>>>>>>>>> Here?s the code to create an archetype >>>>>>>>>> from the mvn coordinates of the archetype >>>>>>>>>> distro: >>>>>>>>>> https://github.com/fabric8io/fabric8/blob/master/tooling/camel-tooling-util/src/main/scala/io/fabric8/camel/tooling/util/ArchetypeHelper.scala#L45 >>>>>>>>>> >>>>>>>>>> e.g. here?s a test case that creates a >>>>>>>>>> bunch of archetypes - no maven is required >>>>>>>>>> etc: >>>>>>>>>> https://github.com/fabric8io/fabric8/blob/master/tooling/camel-tooling-util/src/test/scala/io/fabric8/camel/tooling/util/ArchetypeTest.scala#L29 >>>>>>>>>> >>>>>>>>>> I was hoping we could cobble something >>>>>>>>>> like this into a standard command; then >>>>>>>>>> have nice tab completion on the list of >>>>>>>>>> archetypes we ship by default in Forge >>>>>>>>>> which groks all the jboss / fuse / apache >>>>>>>>>> archetypes we want to prime it with; and >>>>>>>>>> make it easy for folks to >>>>>>>>>> add/load/configure others. e.g. JBoss Fuse >>>>>>>>>> ships with a bunch of archetypes (but they >>>>>>>>>> are not sync?d to maven central); so it?d >>>>>>>>>> be nice if all jboss products that have >>>>>>>>>> archetypes were baked into Forge (e.g. EAP >>>>>>>>>> / Fuse / Fuse Service Works / BRMS etc). >>>>>>>>>> >>>>>>>>>> Hope that helps - would love to port the >>>>>>>>>> code to plain java ;) but I guess whats >>>>>>>>>> another massive jar dependency on >>>>>>>>>> spring-library between friends ;) >>>>>>>>>> >>>>>>>>>> Anyway - hope to see you around this >>>>>>>>>> morning. Go Errai! :) >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On 16 Apr 2014, at 02:52, Lincoln Baxter, >>>>>>>>>> III >>>>>>>>> > wrote: >>>>>>>>>>> Let's talk about this tomorrow (today.) >>>>>>>>>>> I'll be over at the conference in the >>>>>>>>>>> late morning. And I'll be at the hack-fest. >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> Lincoln Baxter, III >>>>>>>>>>> http://ocpsoft.org >>>>>>>>>>> "Simpler is better." >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> James >>>>>>>>>> ------- >>>>>>>>>> Red Hat >>>>>>>>>> >>>>>>>>>> Email: jstracha at redhat.com >>>>>>>>>> >>>>>>>>>> Web: http://fusesource.com >>>>>>>>>> >>>>>>>>>> Twitter: jstrachan, fusenews >>>>>>>>>> Blog: http://macstrac.blogspot.com/ >>>>>>>>>> >>>>>>>>>> Open Source Integration >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Lincoln Baxter, III >>>>>>>>>> http://ocpsoft.org >>>>>>>>>> "Simpler is better." >>>>>>>>> >>>>>>>>> >>>>>>>>> James >>>>>>>>> ------- >>>>>>>>> Red Hat >>>>>>>>> >>>>>>>>> Twitter: @jstrachan >>>>>>>>> Email: jstracha at redhat.com >>>>>>>>> >>>>>>>>> Blog: http://macstrac.blogspot.com/ >>>>>>>>> >>>>>>>>> hawtio: http:/ >>>>>>>>> /hawt.io/ >>>>>>>>> >>>>>>>>> fabric8: http:/ >>>>>>>>> /fabric8.io/ >>>>>>>>> >>>>>>>>> >>>>>>>>> Open Source Integration >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Lincoln Baxter, III >>>>>>>>> http://ocpsoft.org >>>>>>>>> "Simpler is better." >>>>>>>> >>>>>>>> >>>>>>>> James >>>>>>>> ------- >>>>>>>> Red Hat >>>>>>>> >>>>>>>> Twitter: @jstrachan >>>>>>>> Email: jstracha at redhat.com >>>>>>>> Blog: http://macstrac.blogspot.com/ >>>>>>>> >>>>>>>> hawtio: http:/ /hawt.io/ >>>>>>>> >>>>>>>> fabric8: http:/ /fabric8.io/ >>>>>>>> >>>>>>>> >>>>>>>> Open Source Integration >>>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> James >>>>>> ------- >>>>>> Red Hat >>>>>> >>>>>> Twitter: @jstrachan >>>>>> Email: jstracha at redhat.com >>>>>> Blog: http://macstrac.blogspot.com/ >>>>>> >>>>>> hawtio: http:/ /hawt.io/ >>>>>> >>>>>> fabric8: http:/ /fabric8.io/ >>>>>> >>>>>> >>>>>> Open Source Integration >>>>>> >>>>> >>>> >>>> >>>> James >>>> ------- >>>> Red Hat >>>> >>>> Twitter: @jstrachan >>>> Email: jstracha at redhat.com >>>> Blog: http://macstrac.blogspot.com/ >>>> >>>> hawtio: http:/ /hawt.io/ >>>> >>>> fabric8: http:/ /fabric8.io/ >>>> >>>> >>>> Open Source Integration >>>> >>>> >>>> >>>> >>>> -- >>>> Lincoln Baxter, III >>>> http://ocpsoft.org >>>> "Simpler is better." >>> >> >> >> James >> ------- >> Red Hat >> >> Twitter: @jstrachan >> Email: jstracha at redhat.com >> Blog: http://macstrac.blogspot.com/ >> >> hawtio: http:/ /hawt.io/ >> >> fabric8: http:/ /fabric8.io/ >> >> >> Open Source Integration >> >> >> >> >> -- >> Lincoln Baxter, III >> http://ocpsoft.org >> "Simpler is better." > > > > > -- > Lincoln Baxter, III > http://ocpsoft.org > "Simpler is better." From ggastald at redhat.com Wed Jul 9 12:24:35 2014 From: ggastald at redhat.com (George Gastaldi) Date: Wed, 09 Jul 2014 13:24:35 -0300 Subject: [forge-dev] Forge Meeting minutes 2014-07-09 Message-ID: <53BD6CC3.6000706@redhat.com> ============== #forge Meeting ============== Meeting started by gastaldi at 15:02:08 UTC. The full logs are available at http://transcripts.jboss.org/meeting/irc.freenode.org/forge/2014/forge.2014-07-09-15.02.log.html . Meeting summary --------------- * Agenda (gastaldi, 15:03:15) * JBT status (gastaldi, 15:04:38) * gastaldi will work on FORGE-1802 (gastaldi, 15:13:32) * LINK: https://issues.jboss.org/browse/JBIDE-17700 (lincolnthree, 15:15:35) * They thought JBIDE-17700 was a possible forge issue, but I don't think it is. (lincolnthree, 15:15:57) * Roadmap (gastaldi, 15:17:14) * Forge 2.7.1.Final is targeted to be released on July, 15th, but I guess we need to postpone until we have more fixed issues (gastaldi, 15:18:06) * LINK: http://forge.jboss.org/document/how-to-get-your-addon-listed-in-the-forge-website (gastaldi, 15:21:36) * Documentation (a.k.a website) (gastaldi, 15:42:22) * the website should display the news in the front page (or/and have a news section). (gastaldi, 15:57:10) * maybe ^^ (lincolnthree, 15:59:31) Meeting ended at 16:05:03 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * gastaldi (71) * lincolnthree (48) * agoncal (20) * jbossbot (14) * koentsje (11) * jbott (7) * rajmahen_ (6) * rajmahendra (2) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot From lincolnbaxter at gmail.com Wed Jul 16 11:54:42 2014 From: lincolnbaxter at gmail.com (Lincoln Baxter, III) Date: Wed, 16 Jul 2014 11:54:42 -0400 Subject: [forge-dev] Forge Meeting Minutes: 2014-07-16 Message-ID: Minutes: http://transcripts.jboss.org/meeting/irc.freenode.org/forge/2014/forge.2014-07-16-14.47.html Minutes (text): http://transcripts.jboss.org/meeting/irc.freenode.org/forge/2014/forge.2014-07-16-14.47.txt Log: http://transcripts.jboss.org/meeting/irc.freenode.org/forge/2014/forge.2014-07-16-14.47.log.html ============== #forge Meeting ============== Meeting started by lincolnthree at 14:47:02 UTC. The full logs are available athttp://transcripts.jboss.org/meeting/irc.freenode.org/forge/2014/forge.2014-07-16-14.47.log.html . Meeting summary --------------- * Agenda (lincolnthree, 14:47:22) * Forge 2.7.1.Final release (lincolnthree, 14:53:31) * ACTION: Forge 2.7.1.Final will be released today (Jul16th) (gastaldi, 15:03:41) * JBT status (gastaldi, 15:11:06) Meeting ended at 15:33:06 UTC. Action Items ------------ * Forge 2.7.1.Final will be released today (Jul16th) Action Items, by person ----------------------- * **UNASSIGNED** * Forge 2.7.1.Final will be released today (Jul16th) People Present (lines said) --------------------------- * gastaldi (43) * lincolnthree (16) * agoncal (11) * mbriskar (9) * jbossbot (7) * jbott (7) * nchal (5) * adamw_ (5) * emmanuel (1) -- Lincoln Baxter, III http://ocpsoft.org "Simpler is better." -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20140716/e49d7782/attachment.html From rmpestano at gmail.com Tue Jul 22 10:22:28 2014 From: rmpestano at gmail.com (Rafael Pestano) Date: Tue, 22 Jul 2014 11:22:28 -0300 Subject: [forge-dev] Work offline with forge Message-ID: Hi guys, there is a way in forge1 or forge2 to work offline? EG: i have a presentation using forge and the internet is slow, i already have all maven dependencies i will use in the presentation on my local maven repo and want my forge commands to run without querying dependencies on any external maven repo. is it possible? now if i run arquillian setup command without an internet connection i get an exception at: DependencyUtil.getLastestNonSnapshotVersion(line 56) thanks in advance! -- Att, Rafael M. Pestano Desenvolvedor Java Cia. de Processamento de Dados do Rio Grande do Sul Graduando em Ci?ncia da Computa??o UFRGS http://conventionsframework.org http://rpestano.wordpress.com/ @realpestano -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20140722/f6eaeccb/attachment-0001.html From ggastald at redhat.com Tue Jul 22 10:29:48 2014 From: ggastald at redhat.com (George Gastaldi) Date: Tue, 22 Jul 2014 11:29:48 -0300 Subject: [forge-dev] Work offline with forge In-Reply-To: References: Message-ID: <53CE755C.40504@redhat.com> Hi Rafael, Try adding to your settings.xml and see if that works for you. Thanks On 07/22/2014 11:22 AM, Rafael Pestano wrote: > Hi guys, > > there is a way in forge1 or forge2 to work offline? > > EG: i have a presentation using forge and the internet is slow, i > already have all maven dependencies i will use in the presentation on > my local maven repo and want my forge commands to run without querying > dependencies on any external maven repo. > > is it possible? > > now if i run arquillian setup command without an internet connection i > get an exception at: > DependencyUtil.getLastestNonSnapshotVersion(line 56) > > > thanks in advance! > > > -- > Att, > > Rafael M. Pestano > > Desenvolvedor Java Cia. de Processamento de Dados do Rio Grande do Sul > Graduando em Ci?ncia da Computa??o UFRGS > http://conventionsframework.org > http://rpestano.wordpress.com/ > @realpestano > > > _______________________________________________ > forge-dev mailing list > forge-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/forge-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20140722/a6fdbc8c/attachment.html From rmpestano at gmail.com Tue Jul 22 12:59:05 2014 From: rmpestano at gmail.com (Rafael Pestano) Date: Tue, 22 Jul 2014 13:59:05 -0300 Subject: [forge-dev] Work offline with forge In-Reply-To: <53CE755C.40504@redhat.com> References: <53CE755C.40504@redhat.com> Message-ID: Hey George, thanks for the hint, it works very well. but i still got a problem with arquillian setup command for weld EE: arquillian setup --containerName WELD_EE_EMBEDDED_1.1 java.lang.ArrayIndexOutOfBoundsException: -1 at java.util.ArrayList.elementData(ArrayList.java:371) at java.util.ArrayList.get(ArrayList.java:384) at org.jboss.forge.arquillian.DependencyUtil.getLatestNonSnapshotVersion(DependencyUtil.java:56) at org.jboss.forge.arquillian.ContainerInstaller.resolveVersion(ContainerInstaller.java:63) at org.jboss.forge.arquillian.ContainerInstaller.installContainer(ContainerInstaller.java:42) at org.jboss.forge.arquillian.ArquillianPlugin.installContainer(ArquillianPlugin.java:147) at org.jboss.forge.arquillian.ArquillianPlugin.installContainer(ArquillianPlugin.java:126) 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.jboss.forge.shell.command.Execution.perform(Execution.java:160) at org.jboss.forge.shell.command.fshparser.FSHRuntime.run(FSHRuntime.java:109) at org.jboss.forge.shell.command.fshparser.FSHRuntime.run(FSHRuntime.java:47) at org.jboss.forge.shell.ShellImpl$ExecutorThread.run(ShellImpl.java:796) at org.jboss.forge.shell.ShellImpl.execute(ShellImpl.java:819) at org.jboss.forge.shell.ShellImpl.doShell(ShellImpl.java:609) 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.jboss.weld.bean.proxy.AbstractBeanInstance.invoke(AbstractBeanInstance.java:48) at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:125) at org.jboss.forge.shell.ShellImpl$Proxy$_$$_WeldClientProxy.doShell(ShellImpl$Proxy$_$$_WeldClientProxy.java) 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.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:305) at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:54) at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:163) at org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:299) at org.jboss.weld.introspector.jlr.WeldMethodImpl.invokeOnInstance(WeldMethodImpl.java:188) at org.jboss.weld.introspector.ForwardingWeldMethod.invokeOnInstance(ForwardingWeldMethod.java:59) at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:198) at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:282) at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:265) at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:234) at org.jboss.weld.manager.BeanManagerImpl.notifyObservers(BeanManagerImpl.java:635) at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:622) at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:616) at org.jboss.forge.shell.Bootstrap$1.run(Bootstrap.java:186) at java.lang.Thread.run(Thread.java:722) Wrote /home/rmpestano/workspace/rsjug2/pom.xml other containers, including weld se are working. the strange thing is that i remember using it a few days ago without problems, anyone can try it? im using forge 1.4.4. thanks again. 2014-07-22 11:29 GMT-03:00 George Gastaldi : > Hi Rafael, > > Try adding to your settings.xml and see if that works for you. > > Thanks > > > On 07/22/2014 11:22 AM, Rafael Pestano wrote: > > Hi guys, > > there is a way in forge1 or forge2 to work offline? > > EG: i have a presentation using forge and the internet is slow, i already > have all maven dependencies i will use in the presentation on my local > maven repo and want my forge commands to run without querying dependencies > on any external maven repo. > > is it possible? > > now if i run arquillian setup command without an internet connection i > get an exception at: > DependencyUtil.getLastestNonSnapshotVersion(line 56) > > > thanks in advance! > > > -- > Att, > > Rafael M. Pestano > > Desenvolvedor Java Cia. de Processamento de Dados do Rio Grande do Sul > Graduando em Ci?ncia da Computa??o UFRGS > http://conventionsframework.org > http://rpestano.wordpress.com/ > @realpestano > > > _______________________________________________ > forge-dev mailing listforge-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/forge-dev > > > > _______________________________________________ > forge-dev mailing list > forge-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/forge-dev > -- Att, Rafael M. Pestano Desenvolvedor Java Cia. de Processamento de Dados do Rio Grande do Sul Graduando em Ci?ncia da Computa??o UFRGS http://conventionsframework.org http://rpestano.wordpress.com/ @realpestano -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20140722/87691c4b/attachment.html From ggastald at redhat.com Wed Jul 23 12:14:56 2014 From: ggastald at redhat.com (George Gastaldi) Date: Wed, 23 Jul 2014 12:14:56 -0400 (EDT) Subject: [forge-dev] Forge meeting minutes Message-ID: #forge Meeting Meeting started by gegastaldi at 14:47:52 UTC (full logs). Meeting summary Agenda (gegastaldi, 14:48:43) JBDS status (lincolnthree, 14:53:19) https://issues.jboss.org/browse/JBIDE-14375 sounds like similar to maven that george solved (maxandersen, 15:01:34) https://issues.jboss.org/browse/JBIDE-13486 is a duplicate of the issue we discussed at face2face (maxandersen, 15:01:58) https://github.com/forge/core/blob/master/configuration/impl/src/main/java/org/jboss/forge/addon/configuration/proxy/ProxySettings.java(gegastaldi, 15:07:11) https://issues.jboss.org/issues/?jql=project%20in%20(JBIDE%2C%20JBDS)%20and%20component%20%3D%20forge%20and%20resolution%20%3D%20unresolved%20order%20by%20fixVersion%2C%20priority(maxandersen, 15:16:44) how to handle missing pickup command (maxandersen, 15:18:04) Forge 1 wizards should they stay or go (maxandersen, 15:20:48) Meeting ended at 15:52:55 UTC (full logs). Action items (none) People present (lines said) maxandersen (92) lincolnthree (89) gegastaldi (59) vineetreynolds (23) jbossbot (13) koentsje (13) jbott (8) agoncal (1) Generated by MeetBot 0.1.4. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20140723/6da04ebd/attachment-0001.html From ggastald at redhat.com Wed Jul 30 12:01:50 2014 From: ggastald at redhat.com (George Gastaldi) Date: Wed, 30 Jul 2014 13:01:50 -0300 Subject: [forge-dev] Forge meeting minutes - 2014-07-30 Message-ID: <53D916EE.3070708@redhat.com> ============== #forge Meeting ============== Meeting started by gastaldi at 15:00:59 UTC. The full logs are available at http://transcripts.jboss.org/meeting/irc.freenode.org/forge/2014/forge.2014-07-30-15.00.log.html . Meeting summary --------------- * Agenda (gastaldi, 15:01:05) * JBDS issues status (gastaldi, 15:03:47) * gastaldi managed to resolve 11 issues so far (gastaldi, 15:04:55) * when an issue is fixed for QE, put comments about what was done/changed and if any special steps needed to test (gastaldi, 15:07:54) * the issues in JBIDE and JBDS are our top priority items to fix (gastaldi, 15:12:33) * Windows build issues (gastaldi, 15:22:38) * ACTION: ivannov will run clean build of Forge (furnace + core) on Windows (ivannov, 15:34:04) * ACTION: ivannov will run clean build of Forge (furnace + core) on Windows (gastaldi, 15:34:48) * To reproduce the build issue, delete ~/.m2/repository/org/jboss/forge and run furnace, furnace-simple, furnace-cdi and forge/core builds respectively (gastaldi, 15:35:13) * Roadmap (gastaldi, 15:35:21) * Cordova Support (gastaldi, 15:42:28) * LINK: http://www.scottlogic.com/blog/2012/06/29/using-phonegap-build-with-maven.html (gastaldi, 15:49:17) * Outstanding issues (gastaldi, 15:54:34) * ACTION: vineetreynolds will release a new version of the AngularJS addon using Forge 2.7.2.Final (gastaldi, 15:58:55) Meeting ended at 16:00:10 UTC. Action Items ------------ * ivannov will run clean build of Forge (furnace + core) on Windows * ivannov will run clean build of Forge (furnace + core) on Windows * vineetreynolds will release a new version of the AngularJS addon using Forge 2.7.2.Final Action Items, by person ----------------------- * ivannov * ivannov will run clean build of Forge (furnace + core) on Windows * ivannov will run clean build of Forge (furnace + core) on Windows * vineetreynolds * vineetreynolds will release a new version of the AngularJS addon using Forge 2.7.2.Final * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * gastaldi (87) * vineetreynolds (44) * ivannov (18) * jbossbot (13) * maxandersen (10) * jbott (10) * koentsje (2) * adamw_ (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot From ivan.st.ivanov at gmail.com Thu Jul 31 03:45:57 2014 From: ivan.st.ivanov at gmail.com (Ivan St. Ivanov) Date: Thu, 31 Jul 2014 10:45:57 +0300 Subject: [forge-dev] Running the build on Windows Message-ID: Hey everybody, As we discussed yesterday, a promised to run the build locally on my Windows computer to see if we have any issues there, fix them and only then address the failing builds on the build server. I did that, and I have the following observations: 1) The text addon tests failed, mostly because the patterns that recognize the different language elements for YAML, Groovy, JavaScript and HTML are built with the assumption that the end of line character is \n. You know, on Windows it is \r\n. So there were some tests failures. I decided to fix them and only then to continue. But after it took me more than two hours debugging and trying without much progress (fixed only YAML and most of the Groovy) I gave up. I then cloned the repo with git's autocrlf set to false and the tests passed. Nevertheless, we should fix these I guess, if we want our text addon to work on Windows 2) The JavaEE addon failed with a JVM crash (I attached the generated dump files from the three runs that I did). I tried to run it both as part of the build of the whole Forge core, as well as individually. In both cases it failed. I will install a newer version of the JDK and will try again. That is for the moment from my side. Unfortunately I spent all the time debugging the text addon, so didn't spend any effort on the JUnit command and no email for utility methods so far from me. Cheers, Ivan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20140731/3a9f65ef/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: hs_err_pid15024.log Type: application/octet-stream Size: 26121 bytes Desc: not available Url : http://lists.jboss.org/pipermail/forge-dev/attachments/20140731/3a9f65ef/attachment-0003.obj -------------- next part -------------- A non-text attachment was scrubbed... Name: hs_err_pid16220.log Type: application/octet-stream Size: 26320 bytes Desc: not available Url : http://lists.jboss.org/pipermail/forge-dev/attachments/20140731/3a9f65ef/attachment-0004.obj -------------- next part -------------- A non-text attachment was scrubbed... Name: hs_err_pid16560.log Type: application/octet-stream Size: 28697 bytes Desc: not available Url : http://lists.jboss.org/pipermail/forge-dev/attachments/20140731/3a9f65ef/attachment-0005.obj From danielsoro at gmail.com Thu Jul 31 05:54:27 2014 From: danielsoro at gmail.com (Daniel Cunha) Date: Thu, 31 Jul 2014 06:54:27 -0300 Subject: [forge-dev] Running the build on Windows In-Reply-To: References: Message-ID: Hi Ivan, I don't know if aesh work ok on windows. In my last test I had many problem and that can be the answer about forge don't run ok on windows. On Thu, Jul 31, 2014 at 4:45 AM, Ivan St. Ivanov wrote: > Hey everybody, > > As we discussed yesterday, a promised to run the build locally on my > Windows computer to see if we have any issues there, fix them and only then > address the failing builds on the build server. > > I did that, and I have the following observations: > > 1) The text addon tests failed, mostly because the patterns that recognize > the different language elements for YAML, Groovy, JavaScript and HTML are > built with the assumption that the end of line character is \n. You know, > on Windows it is \r\n. So there were some tests failures. I decided to fix > them and only then to continue. But after it took me more than two hours > debugging and trying without much progress (fixed only YAML and most of the > Groovy) I gave up. I then cloned the repo with git's autocrlf set to false > and the tests passed. Nevertheless, we should fix these I guess, if we want > our text addon to work on Windows > > 2) The JavaEE addon failed with a JVM crash (I attached the generated dump > files from the three runs that I did). I tried to run it both as part of > the build of the whole Forge core, as well as individually. In both cases > it failed. I will install a newer version of the JDK and will try again. > > That is for the moment from my side. Unfortunately I spent all the time > debugging the text addon, so didn't spend any effort on the JUnit command > and no email for utility methods so far from me. > > Cheers, > Ivan > > _______________________________________________ > forge-dev mailing list > forge-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/forge-dev > -- Daniel Cunha (soro) Blog: http://www.danielsoro.com.br Twitter: https://twitter.com/dvlc_ GitHub: https://github.com/danielsoro LinkedIn: http://www.linkedin.com/in/danielvlcunha -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20140731/83b549a0/attachment.html From ivan.st.ivanov at gmail.com Thu Jul 31 07:28:06 2014 From: ivan.st.ivanov at gmail.com (Ivan St. Ivanov) Date: Thu, 31 Jul 2014 14:28:06 +0300 Subject: [forge-dev] Running the build on Windows In-Reply-To: References: Message-ID: Hey Daniel, The idea of this effort is just to make sure Forge tests run locally on Windows. And then to investigate why the central build fails. I.e. first clean up your own garden and only then look in the public park ;) If you have any special issues with Aesh, please share them (probably in another thread). I also had some, but I thought they were resolved. The thing is that I don't use Windows at home any more (switched to Fedora), so I can't catch problems with the rate I used to do before ;) Cheers, Ivan On Thu, Jul 31, 2014 at 12:54 PM, Daniel Cunha wrote: > Hi Ivan, > > I don't know if aesh work ok on windows. In my last test I had many > problem and that can be the answer about forge don't run ok on windows. > > > On Thu, Jul 31, 2014 at 4:45 AM, Ivan St. Ivanov > wrote: > >> Hey everybody, >> >> As we discussed yesterday, a promised to run the build locally on my >> Windows computer to see if we have any issues there, fix them and only then >> address the failing builds on the build server. >> >> I did that, and I have the following observations: >> >> 1) The text addon tests failed, mostly because the patterns that >> recognize the different language elements for YAML, Groovy, JavaScript and >> HTML are built with the assumption that the end of line character is \n. >> You know, on Windows it is \r\n. So there were some tests failures. I >> decided to fix them and only then to continue. But after it took me more >> than two hours debugging and trying without much progress (fixed only YAML >> and most of the Groovy) I gave up. I then cloned the repo with git's >> autocrlf set to false and the tests passed. Nevertheless, we should fix >> these I guess, if we want our text addon to work on Windows >> >> 2) The JavaEE addon failed with a JVM crash (I attached the generated >> dump files from the three runs that I did). I tried to run it both as part >> of the build of the whole Forge core, as well as individually. In both >> cases it failed. I will install a newer version of the JDK and will try >> again. >> >> That is for the moment from my side. Unfortunately I spent all the time >> debugging the text addon, so didn't spend any effort on the JUnit command >> and no email for utility methods so far from me. >> >> Cheers, >> Ivan >> >> _______________________________________________ >> forge-dev mailing list >> forge-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/forge-dev >> > > > > -- > Daniel Cunha (soro) > Blog: http://www.danielsoro.com.br > Twitter: https://twitter.com/dvlc_ > GitHub: https://github.com/danielsoro > LinkedIn: http://www.linkedin.com/in/danielvlcunha > > _______________________________________________ > forge-dev mailing list > forge-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/forge-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20140731/2cab3993/attachment.html From ggastald at redhat.com Thu Jul 31 08:23:32 2014 From: ggastald at redhat.com (George Gastaldi) Date: Thu, 31 Jul 2014 08:23:32 -0400 (EDT) Subject: [forge-dev] Running the build on Windows In-Reply-To: References: Message-ID: Hey Ivan, Good catch! You're the man! In my previous attempt to find out what the problem was, I had to ignore the text addon tests on Windows to proceed. The JVM crash is reported in JIRA also, I think Antonio Goncalves experienced something like that. Let me know if you find somehing else. Best Regards, George > Em 31/07/2014, ?s 08:28, "Ivan St. Ivanov" escreveu: > > Hey Daniel, > > The idea of this effort is just to make sure Forge tests run locally on Windows. And then to investigate why the central build fails. I.e. first clean up your own garden and only then look in the public park ;) > > If you have any special issues with Aesh, please share them (probably in another thread). I also had some, but I thought they were resolved. The thing is that I don't use Windows at home any more (switched to Fedora), so I can't catch problems with the rate I used to do before ;) > > Cheers, > Ivan > > >> On Thu, Jul 31, 2014 at 12:54 PM, Daniel Cunha wrote: >> Hi Ivan, >> >> I don't know if aesh work ok on windows. In my last test I had many problem and that can be the answer about forge don't run ok on windows. >> >> >>> On Thu, Jul 31, 2014 at 4:45 AM, Ivan St. Ivanov wrote: >>> Hey everybody, >>> >>> As we discussed yesterday, a promised to run the build locally on my Windows computer to see if we have any issues there, fix them and only then address the failing builds on the build server. >>> >>> I did that, and I have the following observations: >>> >>> 1) The text addon tests failed, mostly because the patterns that recognize the different language elements for YAML, Groovy, JavaScript and HTML are built with the assumption that the end of line character is \n. You know, on Windows it is \r\n. So there were some tests failures. I decided to fix them and only then to continue. But after it took me more than two hours debugging and trying without much progress (fixed only YAML and most of the Groovy) I gave up. I then cloned the repo with git's autocrlf set to false and the tests passed. Nevertheless, we should fix these I guess, if we want our text addon to work on Windows >>> >>> 2) The JavaEE addon failed with a JVM crash (I attached the generated dump files from the three runs that I did). I tried to run it both as part of the build of the whole Forge core, as well as individually. In both cases it failed. I will install a newer version of the JDK and will try again. >>> >>> That is for the moment from my side. Unfortunately I spent all the time debugging the text addon, so didn't spend any effort on the JUnit command and no email for utility methods so far from me. >>> >>> Cheers, >>> Ivan >>> >>> _______________________________________________ >>> forge-dev mailing list >>> forge-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/forge-dev >> >> >> >> -- >> Daniel Cunha (soro) >> Blog: http://www.danielsoro.com.br >> Twitter: https://twitter.com/dvlc_ >> GitHub: https://github.com/danielsoro >> LinkedIn: http://www.linkedin.com/in/danielvlcunha >> >> _______________________________________________ >> forge-dev mailing list >> forge-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/forge-dev > > _______________________________________________ > forge-dev mailing list > forge-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/forge-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20140731/b3f1ffc0/attachment-0001.html From ivan.st.ivanov at gmail.com Thu Jul 31 08:32:21 2014 From: ivan.st.ivanov at gmail.com (Ivan St. Ivanov) Date: Thu, 31 Jul 2014 15:32:21 +0300 Subject: [forge-dev] Running the build on Windows In-Reply-To: References: Message-ID: Hey George, Thanks! What do you think, should we fix the text issues on Windows? I think yes. If you agree with me, I will at least create a JIRA for that. Regards, Ivan On Thu, Jul 31, 2014 at 3:23 PM, George Gastaldi wrote: > Hey Ivan, > > Good catch! You're the man! > > In my previous attempt to find out what the problem was, I had to ignore > the text addon tests on Windows to proceed. > > The JVM crash is reported in JIRA also, I think Antonio Goncalves > experienced something like that. > > Let me know if you find somehing else. > > Best Regards, > > George > > Em 31/07/2014, ?s 08:28, "Ivan St. Ivanov" > escreveu: > > Hey Daniel, > > The idea of this effort is just to make sure Forge tests run locally on > Windows. And then to investigate why the central build fails. I.e. first > clean up your own garden and only then look in the public park ;) > > If you have any special issues with Aesh, please share them (probably in > another thread). I also had some, but I thought they were resolved. The > thing is that I don't use Windows at home any more (switched to Fedora), so > I can't catch problems with the rate I used to do before ;) > > Cheers, > Ivan > > > On Thu, Jul 31, 2014 at 12:54 PM, Daniel Cunha > wrote: > >> Hi Ivan, >> >> I don't know if aesh work ok on windows. In my last test I had many >> problem and that can be the answer about forge don't run ok on windows. >> >> >> On Thu, Jul 31, 2014 at 4:45 AM, Ivan St. Ivanov < >> ivan.st.ivanov at gmail.com> wrote: >> >>> Hey everybody, >>> >>> As we discussed yesterday, a promised to run the build locally on my >>> Windows computer to see if we have any issues there, fix them and only then >>> address the failing builds on the build server. >>> >>> I did that, and I have the following observations: >>> >>> 1) The text addon tests failed, mostly because the patterns that >>> recognize the different language elements for YAML, Groovy, JavaScript and >>> HTML are built with the assumption that the end of line character is \n. >>> You know, on Windows it is \r\n. So there were some tests failures. I >>> decided to fix them and only then to continue. But after it took me more >>> than two hours debugging and trying without much progress (fixed only YAML >>> and most of the Groovy) I gave up. I then cloned the repo with git's >>> autocrlf set to false and the tests passed. Nevertheless, we should fix >>> these I guess, if we want our text addon to work on Windows >>> >>> 2) The JavaEE addon failed with a JVM crash (I attached the generated >>> dump files from the three runs that I did). I tried to run it both as part >>> of the build of the whole Forge core, as well as individually. In both >>> cases it failed. I will install a newer version of the JDK and will try >>> again. >>> >>> That is for the moment from my side. Unfortunately I spent all the time >>> debugging the text addon, so didn't spend any effort on the JUnit command >>> and no email for utility methods so far from me. >>> >>> Cheers, >>> Ivan >>> >>> _______________________________________________ >>> forge-dev mailing list >>> forge-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/forge-dev >>> >> >> >> >> -- >> Daniel Cunha (soro) >> Blog: http://www.danielsoro.com.br >> Twitter: https://twitter.com/dvlc_ >> GitHub: https://github.com/danielsoro >> LinkedIn: http://www.linkedin.com/in/danielvlcunha >> >> _______________________________________________ >> forge-dev mailing list >> forge-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/forge-dev >> > > _______________________________________________ > forge-dev mailing list > forge-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/forge-dev > > > _______________________________________________ > forge-dev mailing list > forge-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/forge-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20140731/c42b556b/attachment.html From ggastald at redhat.com Thu Jul 31 08:46:03 2014 From: ggastald at redhat.com (George Gastaldi) Date: Thu, 31 Jul 2014 08:46:03 -0400 (EDT) Subject: [forge-dev] Running the build on Windows In-Reply-To: References: Message-ID: <11D87593-4856-407A-A1EF-AEB37976B254@redhat.com> Hi Ivan, That would be good if the fix is trivial. Otherwise we can add an Assume.assumeFalse(OperatingSystemUtils.isWindows()); in a @Before method in the scanner tests. > Em 31/07/2014, ?s 09:32, "Ivan St. Ivanov" escreveu: > > Hey George, > > Thanks! > > What do you think, should we fix the text issues on Windows? I think yes. If you agree with me, I will at least create a JIRA for that. > > Regards, > Ivan > > >> On Thu, Jul 31, 2014 at 3:23 PM, George Gastaldi wrote: >> Hey Ivan, >> >> Good catch! You're the man! >> >> In my previous attempt to find out what the problem was, I had to ignore the text addon tests on Windows to proceed. >> >> The JVM crash is reported in JIRA also, I think Antonio Goncalves experienced something like that. >> >> Let me know if you find somehing else. >> >> Best Regards, >> >> George >> >>> Em 31/07/2014, ?s 08:28, "Ivan St. Ivanov" escreveu: >>> >>> Hey Daniel, >>> >>> The idea of this effort is just to make sure Forge tests run locally on Windows. And then to investigate why the central build fails. I.e. first clean up your own garden and only then look in the public park ;) >>> >>> If you have any special issues with Aesh, please share them (probably in another thread). I also had some, but I thought they were resolved. The thing is that I don't use Windows at home any more (switched to Fedora), so I can't catch problems with the rate I used to do before ;) >>> >>> Cheers, >>> Ivan >>> >>> >>>> On Thu, Jul 31, 2014 at 12:54 PM, Daniel Cunha wrote: >>>> Hi Ivan, >>>> >>>> I don't know if aesh work ok on windows. In my last test I had many problem and that can be the answer about forge don't run ok on windows. >>>> >>>> >>>>> On Thu, Jul 31, 2014 at 4:45 AM, Ivan St. Ivanov wrote: >>>>> Hey everybody, >>>>> >>>>> As we discussed yesterday, a promised to run the build locally on my Windows computer to see if we have any issues there, fix them and only then address the failing builds on the build server. >>>>> >>>>> I did that, and I have the following observations: >>>>> >>>>> 1) The text addon tests failed, mostly because the patterns that recognize the different language elements for YAML, Groovy, JavaScript and HTML are built with the assumption that the end of line character is \n. You know, on Windows it is \r\n. So there were some tests failures. I decided to fix them and only then to continue. But after it took me more than two hours debugging and trying without much progress (fixed only YAML and most of the Groovy) I gave up. I then cloned the repo with git's autocrlf set to false and the tests passed. Nevertheless, we should fix these I guess, if we want our text addon to work on Windows >>>>> >>>>> 2) The JavaEE addon failed with a JVM crash (I attached the generated dump files from the three runs that I did). I tried to run it both as part of the build of the whole Forge core, as well as individually. In both cases it failed. I will install a newer version of the JDK and will try again. >>>>> >>>>> That is for the moment from my side. Unfortunately I spent all the time debugging the text addon, so didn't spend any effort on the JUnit command and no email for utility methods so far from me. >>>>> >>>>> Cheers, >>>>> Ivan >>>>> >>>>> _______________________________________________ >>>>> forge-dev mailing list >>>>> forge-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/forge-dev >>>> >>>> >>>> >>>> -- >>>> Daniel Cunha (soro) >>>> Blog: http://www.danielsoro.com.br >>>> Twitter: https://twitter.com/dvlc_ >>>> GitHub: https://github.com/danielsoro >>>> LinkedIn: http://www.linkedin.com/in/danielvlcunha >>>> >>>> _______________________________________________ >>>> forge-dev mailing list >>>> forge-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/forge-dev >>> >>> _______________________________________________ >>> forge-dev mailing list >>> forge-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/forge-dev >> >> _______________________________________________ >> forge-dev mailing list >> forge-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/forge-dev > > _______________________________________________ > forge-dev mailing list > forge-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/forge-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20140731/9194a79c/attachment-0001.html From ivan.st.ivanov at gmail.com Thu Jul 31 08:54:21 2014 From: ivan.st.ivanov at gmail.com (Ivan St. Ivanov) Date: Thu, 31 Jul 2014 15:54:21 +0300 Subject: [forge-dev] Running the build on Windows In-Reply-To: <11D87593-4856-407A-A1EF-AEB37976B254@redhat.com> References: <11D87593-4856-407A-A1EF-AEB37976B254@redhat.com> Message-ID: George, I think that it is not the test that do not work on Windows, but the whole text addon is broken. I mean, the patterns that rely on \n are there. I fixed easily the YAML patterns, but I stuck in the Groovy ones - too few knowledge in RegExp :) On Thu, Jul 31, 2014 at 3:46 PM, George Gastaldi wrote: > Hi Ivan, > > That would be good if the fix is trivial. Otherwise we can add an > Assume.assumeFalse(OperatingSystemUtils.isWindows()); in a @Before method > in the scanner tests. > > > Em 31/07/2014, ?s 09:32, "Ivan St. Ivanov" > escreveu: > > Hey George, > > Thanks! > > What do you think, should we fix the text issues on Windows? I think yes. > If you agree with me, I will at least create a JIRA for that. > > Regards, > Ivan > > > On Thu, Jul 31, 2014 at 3:23 PM, George Gastaldi > wrote: > >> Hey Ivan, >> >> Good catch! You're the man! >> >> In my previous attempt to find out what the problem was, I had to ignore >> the text addon tests on Windows to proceed. >> >> The JVM crash is reported in JIRA also, I think Antonio Goncalves >> experienced something like that. >> >> Let me know if you find somehing else. >> >> Best Regards, >> >> George >> >> Em 31/07/2014, ?s 08:28, "Ivan St. Ivanov" >> escreveu: >> >> Hey Daniel, >> >> The idea of this effort is just to make sure Forge tests run locally on >> Windows. And then to investigate why the central build fails. I.e. first >> clean up your own garden and only then look in the public park ;) >> >> If you have any special issues with Aesh, please share them (probably in >> another thread). I also had some, but I thought they were resolved. The >> thing is that I don't use Windows at home any more (switched to Fedora), so >> I can't catch problems with the rate I used to do before ;) >> >> Cheers, >> Ivan >> >> >> On Thu, Jul 31, 2014 at 12:54 PM, Daniel Cunha >> wrote: >> >>> Hi Ivan, >>> >>> I don't know if aesh work ok on windows. In my last test I had many >>> problem and that can be the answer about forge don't run ok on windows. >>> >>> >>> On Thu, Jul 31, 2014 at 4:45 AM, Ivan St. Ivanov < >>> ivan.st.ivanov at gmail.com> wrote: >>> >>>> Hey everybody, >>>> >>>> As we discussed yesterday, a promised to run the build locally on my >>>> Windows computer to see if we have any issues there, fix them and only then >>>> address the failing builds on the build server. >>>> >>>> I did that, and I have the following observations: >>>> >>>> 1) The text addon tests failed, mostly because the patterns that >>>> recognize the different language elements for YAML, Groovy, JavaScript and >>>> HTML are built with the assumption that the end of line character is \n. >>>> You know, on Windows it is \r\n. So there were some tests failures. I >>>> decided to fix them and only then to continue. But after it took me more >>>> than two hours debugging and trying without much progress (fixed only YAML >>>> and most of the Groovy) I gave up. I then cloned the repo with git's >>>> autocrlf set to false and the tests passed. Nevertheless, we should fix >>>> these I guess, if we want our text addon to work on Windows >>>> >>>> 2) The JavaEE addon failed with a JVM crash (I attached the generated >>>> dump files from the three runs that I did). I tried to run it both as part >>>> of the build of the whole Forge core, as well as individually. In both >>>> cases it failed. I will install a newer version of the JDK and will try >>>> again. >>>> >>>> That is for the moment from my side. Unfortunately I spent all the time >>>> debugging the text addon, so didn't spend any effort on the JUnit command >>>> and no email for utility methods so far from me. >>>> >>>> Cheers, >>>> Ivan >>>> >>>> _______________________________________________ >>>> forge-dev mailing list >>>> forge-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/forge-dev >>>> >>> >>> >>> >>> -- >>> Daniel Cunha (soro) >>> Blog: http://www.danielsoro.com.br >>> Twitter: https://twitter.com/dvlc_ >>> GitHub: https://github.com/danielsoro >>> LinkedIn: http://www.linkedin.com/in/danielvlcunha >>> >>> _______________________________________________ >>> forge-dev mailing list >>> forge-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/forge-dev >>> >> >> _______________________________________________ >> forge-dev mailing list >> forge-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/forge-dev >> >> >> _______________________________________________ >> forge-dev mailing list >> forge-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/forge-dev >> > > _______________________________________________ > forge-dev mailing list > forge-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/forge-dev > > > _______________________________________________ > forge-dev mailing list > forge-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/forge-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20140731/e4b8ce8e/attachment.html From ggastald at redhat.com Thu Jul 31 09:32:27 2014 From: ggastald at redhat.com (George Gastaldi) Date: Thu, 31 Jul 2014 09:32:27 -0400 (EDT) Subject: [forge-dev] Running the build on Windows In-Reply-To: References: <11D87593-4856-407A-A1EF-AEB37976B254@redhat.com> Message-ID: <2361F9A9-6E94-4F1F-B889-11448DFE7699@redhat.com> Hey Ivan, When you refer to the "whole text addon is broken" you mean the Scanner tests or the Inflector too? I ask this because the Inflector tests pass in my local box. > Em 31/07/2014, ?s 09:55, "Ivan St. Ivanov" escreveu: > > George, I think that it is not the test that do not work on Windows, but the whole text addon is broken. I mean, the patterns that rely on \n are there. I fixed easily the YAML patterns, but I stuck in the Groovy ones - too few knowledge in RegExp :) > > >> On Thu, Jul 31, 2014 at 3:46 PM, George Gastaldi wrote: >> Hi Ivan, >> >> That would be good if the fix is trivial. Otherwise we can add an Assume.assumeFalse(OperatingSystemUtils.isWindows()); in a @Before method in the scanner tests. >> >> >>> Em 31/07/2014, ?s 09:32, "Ivan St. Ivanov" escreveu: >>> >> >>> Hey George, >>> >>> Thanks! >>> >>> What do you think, should we fix the text issues on Windows? I think yes. If you agree with me, I will at least create a JIRA for that. >>> >>> Regards, >>> Ivan >>> >>> >>>> On Thu, Jul 31, 2014 at 3:23 PM, George Gastaldi wrote: >>>> Hey Ivan, >>>> >>>> Good catch! You're the man! >>>> >>>> In my previous attempt to find out what the problem was, I had to ignore the text addon tests on Windows to proceed. >>>> >>>> The JVM crash is reported in JIRA also, I think Antonio Goncalves experienced something like that. >>>> >>>> Let me know if you find somehing else. >>>> >>>> Best Regards, >>>> >>>> George >>>> >>>>> Em 31/07/2014, ?s 08:28, "Ivan St. Ivanov" escreveu: >>>>> >>>>> Hey Daniel, >>>>> >>>>> The idea of this effort is just to make sure Forge tests run locally on Windows. And then to investigate why the central build fails. I.e. first clean up your own garden and only then look in the public park ;) >>>>> >>>>> If you have any special issues with Aesh, please share them (probably in another thread). I also had some, but I thought they were resolved. The thing is that I don't use Windows at home any more (switched to Fedora), so I can't catch problems with the rate I used to do before ;) >>>>> >>>>> Cheers, >>>>> Ivan >>>>> >>>>> >>>>>> On Thu, Jul 31, 2014 at 12:54 PM, Daniel Cunha wrote: >>>>>> Hi Ivan, >>>>>> >>>>>> I don't know if aesh work ok on windows. In my last test I had many problem and that can be the answer about forge don't run ok on windows. >>>>>> >>>>>> >>>>>>> On Thu, Jul 31, 2014 at 4:45 AM, Ivan St. Ivanov wrote: >>>>>>> Hey everybody, >>>>>>> >>>>>>> As we discussed yesterday, a promised to run the build locally on my Windows computer to see if we have any issues there, fix them and only then address the failing builds on the build server. >>>>>>> >>>>>>> I did that, and I have the following observations: >>>>>>> >>>>>>> 1) The text addon tests failed, mostly because the patterns that recognize the different language elements for YAML, Groovy, JavaScript and HTML are built with the assumption that the end of line character is \n. You know, on Windows it is \r\n. So there were some tests failures. I decided to fix them and only then to continue. But after it took me more than two hours debugging and trying without much progress (fixed only YAML and most of the Groovy) I gave up. I then cloned the repo with git's autocrlf set to false and the tests passed. Nevertheless, we should fix these I guess, if we want our text addon to work on Windows >>>>>>> >>>>>>> 2) The JavaEE addon failed with a JVM crash (I attached the generated dump files from the three runs that I did). I tried to run it both as part of the build of the whole Forge core, as well as individually. In both cases it failed. I will install a newer version of the JDK and will try again. >>>>>>> >>>>>>> That is for the moment from my side. Unfortunately I spent all the time debugging the text addon, so didn't spend any effort on the JUnit command and no email for utility methods so far from me. >>>>>>> >>>>>>> Cheers, >>>>>>> Ivan >>>>>>> >>>>>>> _______________________________________________ >>>>>>> forge-dev mailing list >>>>>>> forge-dev at lists.jboss.org >>>>>>> https://lists.jboss.org/mailman/listinfo/forge-dev >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Daniel Cunha (soro) >>>>>> Blog: http://www.danielsoro.com.br >>>>>> Twitter: https://twitter.com/dvlc_ >>>>>> GitHub: https://github.com/danielsoro >>>>>> LinkedIn: http://www.linkedin.com/in/danielvlcunha >>>>>> >>>>>> _______________________________________________ >>>>>> forge-dev mailing list >>>>>> forge-dev at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/forge-dev >>>>> >>>>> _______________________________________________ >>>>> forge-dev mailing list >>>>> forge-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/forge-dev >>>> >>>> _______________________________________________ >>>> forge-dev mailing list >>>> forge-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/forge-dev >>> >>> _______________________________________________ >>> forge-dev mailing list >>> forge-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/forge-dev >> >> _______________________________________________ >> forge-dev mailing list >> forge-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/forge-dev > > _______________________________________________ > forge-dev mailing list > forge-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/forge-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20140731/4838daee/attachment-0001.html From adamwyl92 at gmail.com Thu Jul 31 09:51:19 2014 From: adamwyl92 at gmail.com (=?UTF-8?B?QWRhbSBXecWCdWRh?=) Date: Thu, 31 Jul 2014 15:51:19 +0200 Subject: [forge-dev] IntelliJ Forge plugin pre-release Message-ID: Hello, For anyone interested in IntelliJ-Forge integration progress, it is now possible to test the pre-release version of the plugin. To install the plugin, go to IntelliJ Settings -> Plugins -> Browse Repositories and search for JBoss Forge IDEA Plugin. To start interacting with Forge press Ctrl+Alt+4. Plugin can be also downloaded from: http://plugins.jetbrains.com/plugin/7515 I'd be more than happy to hear your feedback! Thanks, Adam Wy?uda -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20140731/edc9a8ab/attachment.html From ggastald at redhat.com Thu Jul 31 10:05:28 2014 From: ggastald at redhat.com (George Gastaldi) Date: Thu, 31 Jul 2014 10:05:28 -0400 (EDT) Subject: [forge-dev] IntelliJ Forge plugin pre-release In-Reply-To: References: Message-ID: Adam is a GSoC student working in the Forge Intellij integration and this is the result of his work so far. Good job Adam, you rock! > Em 31/07/2014, ?s 10:52, Adam Wy?uda escreveu: > > Hello, > > For anyone interested in IntelliJ-Forge integration progress, it is now possible to test the pre-release version of the plugin. > > To install the plugin, go to IntelliJ Settings -> Plugins -> Browse Repositories and search for JBoss Forge IDEA Plugin. To start interacting with Forge press Ctrl+Alt+4. > > Plugin can be also downloaded from: > http://plugins.jetbrains.com/plugin/7515 > > I'd be more than happy to hear your feedback! > > Thanks, > Adam Wy?uda > _______________________________________________ > forge-dev mailing list > forge-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/forge-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20140731/9947e0b3/attachment.html From ivan.st.ivanov at gmail.com Thu Jul 31 10:10:37 2014 From: ivan.st.ivanov at gmail.com (Ivan St. Ivanov) Date: Thu, 31 Jul 2014 17:10:37 +0300 Subject: [forge-dev] IntelliJ Forge plugin pre-release In-Reply-To: References: Message-ID: You are awesome, Adam! On Jul 31, 2014 5:05 PM, "George Gastaldi" wrote: > Adam is a GSoC student working in the Forge Intellij integration and this > is the result of his work so far. > > Good job Adam, you rock! > > Em 31/07/2014, ?s 10:52, Adam Wy?uda escreveu: > > Hello, > > For anyone interested in IntelliJ-Forge integration progress, it is now > possible to test the pre-release version of the plugin. > > To install the plugin, go to IntelliJ Settings -> Plugins -> Browse > Repositories and search for JBoss Forge IDEA Plugin. To start interacting > with Forge press Ctrl+Alt+4. > > Plugin can be also downloaded from: > http://plugins.jetbrains.com/plugin/7515 > > I'd be more than happy to hear your feedback! > > Thanks, > Adam Wy?uda > > _______________________________________________ > forge-dev mailing list > forge-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/forge-dev > > > _______________________________________________ > forge-dev mailing list > forge-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/forge-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20140731/10ee484d/attachment.html From ivan.st.ivanov at gmail.com Thu Jul 31 11:53:57 2014 From: ivan.st.ivanov at gmail.com (Ivan St. Ivanov) Date: Thu, 31 Jul 2014 18:53:57 +0300 Subject: [forge-dev] Running the build on Windows In-Reply-To: <2361F9A9-6E94-4F1F-B889-11448DFE7699@redhat.com> References: <11D87593-4856-407A-A1EF-AEB37976B254@redhat.com> <2361F9A9-6E94-4F1F-B889-11448DFE7699@redhat.com> Message-ID: George, I didn't mean tests at all here. I meant that whenever you want to use the text addon to parse something for you, you will have troubles on Windows, because the RegEx patterns in the productive code do not work on Windows. And the tests are there to prove that, not to be ignored by us. I will create the JIRA issue and will assign it to me. I guess it has higher prio than JUnit command. On Thu, Jul 31, 2014 at 4:32 PM, George Gastaldi wrote: > Hey Ivan, > > When you refer to the "whole text addon is broken" you mean the Scanner > tests or the Inflector too? I ask this because the Inflector tests pass in > my local box. > > Em 31/07/2014, ?s 09:55, "Ivan St. Ivanov" > escreveu: > > George, I think that it is not the test that do not work on Windows, but > the whole text addon is broken. I mean, the patterns that rely on \n are > there. I fixed easily the YAML patterns, but I stuck in the Groovy ones - > too few knowledge in RegExp :) > > > On Thu, Jul 31, 2014 at 3:46 PM, George Gastaldi > wrote: > >> Hi Ivan, >> >> That would be good if the fix is trivial. Otherwise we can add an >> Assume.assumeFalse(OperatingSystemUtils.isWindows()); in a @Before method >> in the scanner tests. >> >> >> Em 31/07/2014, ?s 09:32, "Ivan St. Ivanov" >> escreveu: >> >> Hey George, >> >> Thanks! >> >> What do you think, should we fix the text issues on Windows? I think yes. >> If you agree with me, I will at least create a JIRA for that. >> >> Regards, >> Ivan >> >> >> On Thu, Jul 31, 2014 at 3:23 PM, George Gastaldi >> wrote: >> >>> Hey Ivan, >>> >>> Good catch! You're the man! >>> >>> In my previous attempt to find out what the problem was, I had to ignore >>> the text addon tests on Windows to proceed. >>> >>> The JVM crash is reported in JIRA also, I think Antonio Goncalves >>> experienced something like that. >>> >>> Let me know if you find somehing else. >>> >>> Best Regards, >>> >>> George >>> >>> Em 31/07/2014, ?s 08:28, "Ivan St. Ivanov" >>> escreveu: >>> >>> Hey Daniel, >>> >>> The idea of this effort is just to make sure Forge tests run locally on >>> Windows. And then to investigate why the central build fails. I.e. first >>> clean up your own garden and only then look in the public park ;) >>> >>> If you have any special issues with Aesh, please share them (probably in >>> another thread). I also had some, but I thought they were resolved. The >>> thing is that I don't use Windows at home any more (switched to Fedora), so >>> I can't catch problems with the rate I used to do before ;) >>> >>> Cheers, >>> Ivan >>> >>> >>> On Thu, Jul 31, 2014 at 12:54 PM, Daniel Cunha >>> wrote: >>> >>>> Hi Ivan, >>>> >>>> I don't know if aesh work ok on windows. In my last test I had many >>>> problem and that can be the answer about forge don't run ok on windows. >>>> >>>> >>>> On Thu, Jul 31, 2014 at 4:45 AM, Ivan St. Ivanov < >>>> ivan.st.ivanov at gmail.com> wrote: >>>> >>>>> Hey everybody, >>>>> >>>>> As we discussed yesterday, a promised to run the build locally on my >>>>> Windows computer to see if we have any issues there, fix them and only then >>>>> address the failing builds on the build server. >>>>> >>>>> I did that, and I have the following observations: >>>>> >>>>> 1) The text addon tests failed, mostly because the patterns that >>>>> recognize the different language elements for YAML, Groovy, JavaScript and >>>>> HTML are built with the assumption that the end of line character is \n. >>>>> You know, on Windows it is \r\n. So there were some tests failures. I >>>>> decided to fix them and only then to continue. But after it took me more >>>>> than two hours debugging and trying without much progress (fixed only YAML >>>>> and most of the Groovy) I gave up. I then cloned the repo with git's >>>>> autocrlf set to false and the tests passed. Nevertheless, we should fix >>>>> these I guess, if we want our text addon to work on Windows >>>>> >>>>> 2) The JavaEE addon failed with a JVM crash (I attached the generated >>>>> dump files from the three runs that I did). I tried to run it both as part >>>>> of the build of the whole Forge core, as well as individually. In both >>>>> cases it failed. I will install a newer version of the JDK and will try >>>>> again. >>>>> >>>>> That is for the moment from my side. Unfortunately I spent all the >>>>> time debugging the text addon, so didn't spend any effort on the JUnit >>>>> command and no email for utility methods so far from me. >>>>> >>>>> Cheers, >>>>> Ivan >>>>> >>>>> _______________________________________________ >>>>> forge-dev mailing list >>>>> forge-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/forge-dev >>>>> >>>> >>>> >>>> >>>> -- >>>> Daniel Cunha (soro) >>>> Blog: http://www.danielsoro.com.br >>>> Twitter: https://twitter.com/dvlc_ >>>> GitHub: https://github.com/danielsoro >>>> LinkedIn: http://www.linkedin.com/in/danielvlcunha >>>> >>>> _______________________________________________ >>>> forge-dev mailing list >>>> forge-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/forge-dev >>>> >>> >>> _______________________________________________ >>> forge-dev mailing list >>> forge-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/forge-dev >>> >>> >>> _______________________________________________ >>> forge-dev mailing list >>> forge-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/forge-dev >>> >> >> _______________________________________________ >> forge-dev mailing list >> forge-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/forge-dev >> >> >> _______________________________________________ >> forge-dev mailing list >> forge-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/forge-dev >> > > _______________________________________________ > forge-dev mailing list > forge-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/forge-dev > > > _______________________________________________ > forge-dev mailing list > forge-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/forge-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20140731/73e3d4b7/attachment-0001.html From ggastald at redhat.com Thu Jul 31 12:36:01 2014 From: ggastald at redhat.com (George Gastaldi) Date: Thu, 31 Jul 2014 12:36:01 -0400 (EDT) Subject: [forge-dev] Running the build on Windows In-Reply-To: References: <11D87593-4856-407A-A1EF-AEB37976B254@redhat.com> <2361F9A9-6E94-4F1F-B889-11448DFE7699@redhat.com> Message-ID: <786AB487-275C-4C14-A2C9-89F4D6B15B3B@redhat.com> Right, sounds good. Thanks for the help, you are awesome! :) George > Em 31/07/2014, ?s 12:54, "Ivan St. Ivanov" escreveu: > > George, I didn't mean tests at all here. > > I meant that whenever you want to use the text addon to parse something for you, you will have troubles on Windows, because the RegEx patterns in the productive code do not work on Windows. And the tests are there to prove that, not to be ignored by us. > > I will create the JIRA issue and will assign it to me. I guess it has higher prio than JUnit command. > > >> On Thu, Jul 31, 2014 at 4:32 PM, George Gastaldi wrote: >> Hey Ivan, >> >> When you refer to the "whole text addon is broken" you mean the Scanner tests or the Inflector too? I ask this because the Inflector tests pass in my local box. >> >>> Em 31/07/2014, ?s 09:55, "Ivan St. Ivanov" escreveu: >>> >> >>> George, I think that it is not the test that do not work on Windows, but the whole text addon is broken. I mean, the patterns that rely on \n are there. I fixed easily the YAML patterns, but I stuck in the Groovy ones - too few knowledge in RegExp :) >>> >>> >>>> On Thu, Jul 31, 2014 at 3:46 PM, George Gastaldi wrote: >>>> Hi Ivan, >>>> >>>> That would be good if the fix is trivial. Otherwise we can add an Assume.assumeFalse(OperatingSystemUtils.isWindows()); in a @Before method in the scanner tests. >>>> >>>> >>>>> Em 31/07/2014, ?s 09:32, "Ivan St. Ivanov" escreveu: >>>>> >>>> >>>>> Hey George, >>>>> >>>>> Thanks! >>>>> >>>>> What do you think, should we fix the text issues on Windows? I think yes. If you agree with me, I will at least create a JIRA for that. >>>>> >>>>> Regards, >>>>> Ivan >>>>> >>>>> >>>>>> On Thu, Jul 31, 2014 at 3:23 PM, George Gastaldi wrote: >>>>>> Hey Ivan, >>>>>> >>>>>> Good catch! You're the man! >>>>>> >>>>>> In my previous attempt to find out what the problem was, I had to ignore the text addon tests on Windows to proceed. >>>>>> >>>>>> The JVM crash is reported in JIRA also, I think Antonio Goncalves experienced something like that. >>>>>> >>>>>> Let me know if you find somehing else. >>>>>> >>>>>> Best Regards, >>>>>> >>>>>> George >>>>>> >>>>>>> Em 31/07/2014, ?s 08:28, "Ivan St. Ivanov" escreveu: >>>>>>> >>>>>>> Hey Daniel, >>>>>>> >>>>>>> The idea of this effort is just to make sure Forge tests run locally on Windows. And then to investigate why the central build fails. I.e. first clean up your own garden and only then look in the public park ;) >>>>>>> >>>>>>> If you have any special issues with Aesh, please share them (probably in another thread). I also had some, but I thought they were resolved. The thing is that I don't use Windows at home any more (switched to Fedora), so I can't catch problems with the rate I used to do before ;) >>>>>>> >>>>>>> Cheers, >>>>>>> Ivan >>>>>>> >>>>>>> >>>>>>>> On Thu, Jul 31, 2014 at 12:54 PM, Daniel Cunha wrote: >>>>>>>> Hi Ivan, >>>>>>>> >>>>>>>> I don't know if aesh work ok on windows. In my last test I had many problem and that can be the answer about forge don't run ok on windows. >>>>>>>> >>>>>>>> >>>>>>>>> On Thu, Jul 31, 2014 at 4:45 AM, Ivan St. Ivanov wrote: >>>>>>>>> Hey everybody, >>>>>>>>> >>>>>>>>> As we discussed yesterday, a promised to run the build locally on my Windows computer to see if we have any issues there, fix them and only then address the failing builds on the build server. >>>>>>>>> >>>>>>>>> I did that, and I have the following observations: >>>>>>>>> >>>>>>>>> 1) The text addon tests failed, mostly because the patterns that recognize the different language elements for YAML, Groovy, JavaScript and HTML are built with the assumption that the end of line character is \n. You know, on Windows it is \r\n. So there were some tests failures. I decided to fix them and only then to continue. But after it took me more than two hours debugging and trying without much progress (fixed only YAML and most of the Groovy) I gave up. I then cloned the repo with git's autocrlf set to false and the tests passed. Nevertheless, we should fix these I guess, if we want our text addon to work on Windows >>>>>>>>> >>>>>>>>> 2) The JavaEE addon failed with a JVM crash (I attached the generated dump files from the three runs that I did). I tried to run it both as part of the build of the whole Forge core, as well as individually. In both cases it failed. I will install a newer version of the JDK and will try again. >>>>>>>>> >>>>>>>>> That is for the moment from my side. Unfortunately I spent all the time debugging the text addon, so didn't spend any effort on the JUnit command and no email for utility methods so far from me. >>>>>>>>> >>>>>>>>> Cheers, >>>>>>>>> Ivan >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> forge-dev mailing list >>>>>>>>> forge-dev at lists.jboss.org >>>>>>>>> https://lists.jboss.org/mailman/listinfo/forge-dev >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Daniel Cunha (soro) >>>>>>>> Blog: http://www.danielsoro.com.br >>>>>>>> Twitter: https://twitter.com/dvlc_ >>>>>>>> GitHub: https://github.com/danielsoro >>>>>>>> LinkedIn: http://www.linkedin.com/in/danielvlcunha >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> forge-dev mailing list >>>>>>>> forge-dev at lists.jboss.org >>>>>>>> https://lists.jboss.org/mailman/listinfo/forge-dev >>>>>>> >>>>>>> _______________________________________________ >>>>>>> forge-dev mailing list >>>>>>> forge-dev at lists.jboss.org >>>>>>> https://lists.jboss.org/mailman/listinfo/forge-dev >>>>>> >>>>>> _______________________________________________ >>>>>> forge-dev mailing list >>>>>> forge-dev at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/forge-dev >>>>> >>>>> _______________________________________________ >>>>> forge-dev mailing list >>>>> forge-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/forge-dev >>>> >>>> _______________________________________________ >>>> forge-dev mailing list >>>> forge-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/forge-dev >>> >>> _______________________________________________ >>> forge-dev mailing list >>> forge-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/forge-dev >> >> _______________________________________________ >> forge-dev mailing list >> forge-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/forge-dev > > _______________________________________________ > forge-dev mailing list > forge-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/forge-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20140731/4756cc65/attachment.html From manderse at redhat.com Thu Jul 31 18:25:57 2014 From: manderse at redhat.com (Max Rydahl Andersen) Date: Fri, 01 Aug 2014 00:25:57 +0200 Subject: [forge-dev] IntelliJ Forge plugin pre-release In-Reply-To: References: Message-ID: <1995F2EB-BF99-4459-B76F-F6DE4E223191@redhat.com> On 31 Jul 2014, at 15:51, Adam Wy?uda wrote: > Hello, > > For anyone interested in IntelliJ-Forge integration progress, it is > now > possible to test the pre-release version of the plugin. > > To install the plugin, go to IntelliJ Settings -> Plugins -> Browse > Repositories and search for JBoss Forge IDEA Plugin. To start > interacting > with Forge press Ctrl+Alt+4. > > Plugin can be also downloaded from: > http://plugins.jetbrains.com/plugin/7515 > > I'd be more than happy to hear your feedback! really cool - maybe add a page somewhere with some screenshots and examples of what can be done ? also just because i'm curious - how is the feature comparison with this plugin for intellij vs eclipse plugin ? Does it have a console, suport for cd #/, "linked editors" etc. or is currently purely what corresponds to Ctrl+4 in eclipse ? /max http://about.me/maxandersen From ggastald at redhat.com Thu Jul 31 20:32:48 2014 From: ggastald at redhat.com (George Gastaldi) Date: Thu, 31 Jul 2014 20:32:48 -0400 (EDT) Subject: [forge-dev] IntelliJ Forge plugin pre-release In-Reply-To: <1995F2EB-BF99-4459-B76F-F6DE4E223191@redhat.com> References: <1995F2EB-BF99-4459-B76F-F6DE4E223191@redhat.com> Message-ID: I am preparing a video about this plugin. Had to find how to change IDEA to use JDK1.7 on Mac first (it's in the info.plist file inside the package btw). There isn't a console support yet, but IDEA has a Terminal window that allows you to run the console version natively. Therefore some of the commands that exist in eclipse (cd #/) and the linked editors do not exist. > Em 31/07/2014, ?s 19:26, "Max Rydahl Andersen" escreveu: > >> On 31 Jul 2014, at 15:51, Adam Wy?uda wrote: >> >> Hello, >> >> For anyone interested in IntelliJ-Forge integration progress, it is >> now >> possible to test the pre-release version of the plugin. >> >> To install the plugin, go to IntelliJ Settings -> Plugins -> Browse >> Repositories and search for JBoss Forge IDEA Plugin. To start >> interacting >> with Forge press Ctrl+Alt+4. >> >> Plugin can be also downloaded from: >> http://plugins.jetbrains.com/plugin/7515 >> >> I'd be more than happy to hear your feedback! > > really cool - maybe add a page somewhere with some screenshots and > examples of > what can be done ? > > also just because i'm curious - how is the feature comparison with this > plugin for intellij > vs eclipse plugin ? > > Does it have a console, suport for cd #/, "linked editors" etc. or is > currently purely > what corresponds to Ctrl+4 in eclipse ? > > /max > http://about.me/maxandersen > _______________________________________________ > forge-dev mailing list > forge-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/forge-dev