From benevides at redhat.com Mon Dec 1 09:43:17 2014 From: benevides at redhat.com (Rafael Benevides) Date: Mon, 01 Dec 2014 12:43:17 -0200 Subject: [jbossdeveloper] Update JBoss Developer Materials to Java EE 7 In-Reply-To: References: <53FB2B23.6090802@redhat.com> <540DF5BC.3020103@redhat.com> Message-ID: <547C7E85.60007@redhat.com> Hi all, I'm pleased to announce that we have now the first Java EE 7 feature shown as a JBoss Developer Quickstart: JDF-765 - Websocket server endpoint - https://github.com/jboss-developer/jboss-sandbox-quickstarts/tree/master/websocket-endpoint It is published at http://websocket-benevides.rhcloud.com if you want to try it. On 9/9/14 01:29, Arun Gupta wrote: > Hi Rafael, > > If you are looking for the top 5 features that should be highlighted > in Java EE 7, then they would be: > > - WebSocket server endpoint > - Chunk style batch processing > - Object-based JSON generation and Stream-based JSON consuming > - ManagedExecutorService > - JAX-RS Client API > > There are samples for each one of these at: > > https://github.com/javaee-samples/javaee7-samples > > I had some basic discussions with Vineet last week on where some of > these usecases can be incorporated in Ticket Monster. Please keep me > involved in the design of how TiMo is going to evolve for Java EE 7 > support. Some of the documents that would be very useful from that > process are: > > - How to migrate an existing Java EE 6 application to EE 7 ? This > would be very useful to our customers as well. > - Compare LOC/deployment descriptors between the EE 6 and 7 versions. > These would make nice graphs. > - Before/after code fragment for different pieces that were migrated. > - What proprietary technologies were replaced with standards-based > when using EE 7 > > Cheers > Arun > > On Mon, Sep 8, 2014 at 9:30 PM, Rafael Benevides > wrote: > > Returning the discussion about JBoss Developer Material for Java EE 7, > > Arun, > > Do you have the list of the 5 features/use cases/quickstarts that > we want to show, right? Can you share it? > > Thanks > > Em 8/25/14, 9:25, Rafael Benevides escreveu: >> Hi All, >> >> We're about to start the update process of JBoss Developer >> Materials to Java EE 7. But before put the hands on it I talked >> with Pete and we decided that it's better to bring this $subject >> to discussion with everyone on this list. >> >> Ticket Monster already started to be updated >> https://issues.jboss.org/browse/JDF-754 >> >> Actually our jboss-eap-quickstarts have been updated to Java EE >> 7.0 on https://github.com/wildfly/quickstart. Anyway we still >> miss some Java EE 7 specific features/use cases on these quickstarts. >> >> It seems that Arun Gupta has a list of about 5 features/use >> cases/quickstarts that we want to show. The idea is to have these >> Java EE 7 specific quickstarts to be available at www.jboss.org >> >> >> The main point that we should discuss are: >> >> - What are those quickstarts/features? >> - Where will we host those Java EE 7 quickstarts? >> https://github.com/jboss-developer/jboss-sandbox-quickstarts ? >> - Paul Robinson, >> >> Considering that the jboss-sandbox-quickstarts github structure, >> do you think that it could have any issues with it? Can we choose >> just specific quickstarts to be present at www.jboss.org >> >> >> Well, >> >> This is just a starting point, so we can discuss about this >> update process until we have a detailed plan. >> >> The Google docs with the plan is available at: >> https://docs.google.com/document/d/1n0uVG2rhDf1eSp0b4MhggdIxNa3cthnuWaj2OjBpxoY/edit >> >> >> -- >> >> *Rafael Benevides | Senior Software Engineer* >> JBoss Developer >> M: +55-61-9269-6576 >> >> Red Hat >> >> Better technology. Faster innovation. Powered by community >> collaboration. >> See how it works at www.redhat.com >> >> LinkedIn Youtube >> >> >> >> _______________________________________________ >> jbossdeveloper mailing list >> jbossdeveloper at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbossdeveloper > > > _______________________________________________ > jbossdeveloper mailing list > jbossdeveloper at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbossdeveloper > > > > > -- > http://blog.arungupta.me > http://twitter.com/arungupta -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20141201/6d17e7ab/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 4815 bytes Desc: not available Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20141201/6d17e7ab/attachment-0001.jpe -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 597 bytes Desc: not available Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20141201/6d17e7ab/attachment-0002.png -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 616 bytes Desc: not available Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20141201/6d17e7ab/attachment-0003.png From pmuir at redhat.com Mon Dec 1 12:47:51 2014 From: pmuir at redhat.com (Pete Muir) Date: Mon, 1 Dec 2014 17:47:51 +0000 Subject: [jbossdeveloper] on quickstarts pom.xml In-Reply-To: <54770FAE.9060007@redhat.com> References: <53FB3100.4020501@redhat.com> <5453BDCB.1060104@redhat.com> <0FDD180A-039B-4D66-9B8F-A54DB12F627D@redhat.com> <5453C21D.5040203@redhat.com>

<547391C5.60106@redhat.com> <3C0DDFD6-5952-4638-810C-6891E310B980@redhat.com> <151036514.11189408.1417082760553.JavaMail.zimbra@redhat.com> <54770FAE.9060007@redhat.com> Message-ID: Agreed. I thought that was always the plan? > On 27 Nov 2014, at 11:49, Rafael Benevides wrote: > > That's an excellent proposal since we are thinking on users that goes directly to github. > > Anyway we shouldn't use SNAPSHOTs artifacts on -devel branch. Every "staging" release should be placed at http://jboss-developer.github.io/temp-maven-repo/ using the "-build-x" suffix. That's one of the reasons that I placed that repo as an approved one on QSTools, so we can add it on "-develop" branch. But unfortunately it seems that nobody is using it anymore since it's not being updated since July. > > Besides that proposal, We also should ask to have the x.y.Final tag for each release. > > > > On 11/27/14 08:06, Vineet Reynolds Pereira wrote: >> I have a follow-up question - should we also change the default branch to x.y.Final instead of x.y-develop ? >> This naturally follows from our need to not have users perform any special configuration to get started. >> End-users who clone the repo do not have to figure out how to get the SNAPSHOT artifacts. >> >> >> ----- Original Message ----- >>> From: "Pete Muir" >>> To: "Sande Gilda" >>> Cc: "Max Rydahl Andersen" , jbossdeveloper at lists.jboss.org, "Alexandre Porcelli" >>> , "Tomas Repel" , "Nikoleta Ziakova" >>> Sent: Tuesday, November 25, 2014 3:51:48 PM >>> Subject: Re: [jbossdeveloper] on quickstarts pom.xml >>> >>> Ideally sooner rather than later, but I think it?s too late for EAP 6.4 >>> >>> >>> >>> >>> On 24 Nov 2014, at 20:15, Sande Gilda < sgilda at redhat.com > wrote: >>> >>> What is the timeline for this? Am I supposed to do this for the JBoss EAP 6.4 >>> quickstarts or for the EAP 7 release? I think it will have a pretty big QE >>> impact. Plus, this change not only impacts the quickstarts, but the >>> documentation. >>> >>> On 11/17/2014 06:00 AM, Pete Muir wrote: >>> >>> >>> Agreed, and it was this logic that led to us deciding to introduce the repo >>> into the POM. >>> >>> >>> >>> >>> On 11 Nov 2014, at 14:37, Alexandre Porcelli < alexandre.porcelli at gmail.com > >>> wrote: >>> >>> Sorry for my late reply... I was on PTO (in fact I return tomorrow) >>> >>> First of all... I understand all the reasoning behind the issues that makes >>> us avoid use maven central for our stuff, I'm also a seasoned developer with >>> good expirience on maven config - so touch my settings.xml isn't a problem, >>> or even change myself some POMs wouldn't be a problem too. >>> >>> So what's the problem? Simplicity (or lack of it)! If Ticketmonster is our >>> `petclinic`, we should make it easy to build and deploy as spring's >>> petclinic is... git clone; mvn clean install and done! >>> >>> Ticketmonster uses a default branch called "2.7.x-develop" (after cloning and >>> I had to double check if I did anything wrong... I questioned myself if I >>> cloned the right project; if i had changed branches accidently; and finally >>> if 2.7.x was really the latest version); then I tried to build, no pom.xml >>> on the root (fine, it was quick to find the real sources directory); finally >>> I run the build (tried the innocent `mvn clean install`) - and got lots of >>> error messages. You can arguee that I didn't follow the tutorial... and >>> you're right! But how many developers are also skiping the tutorial and are >>> trying to build the app directly? How many people we're loosing on this >>> process? >>> >>> If we want to make our technology accessible to people, we should try to make >>> it simple as possible... we should try to remove all barriers, and make our >>> things as easy to consume as others are doing. >>> >>> btw: I was trying to use ticketmonster to record a demo of our UberFire based >>> Web IDE: https://www.youtube.com/watch?v=UG4pqk2r70Q >>> >>> []s >>> ___________________ >>> Alexandre Porcelli >>> F: +55 11 98159-9725 >>> http://about.me/porcelli >>> >>> On Fri, Oct 31, 2014 at 3:08 PM, Rafael Benevides < benevides at redhat.com > >>> wrote: >>> >>> >>> We stopped at which repos should be included. >>> >>> Them in the other email thread I proposed to have a list of approved repos >>> and its id, them QSTools can be used to update those repo definitions. >>> >>> >>> On 10/31/14 15:07, Max Rydahl Andersen wrote: >>> >>> >>> Anything holding us back for doing it for quick starts and ticketmonster? >>> >>> I feel we had this discussion in past but I only remember "just not done yet" >>> ...or was there something beyond that ? >>> >>> /max >>> http://about.me/maxandersen >>> >>> >>> >>> >>> On 31 Oct 2014, at 17:50, Rafael Benevides < benevides at redhat.com > wrote: >>> >>> This was only done for the archetypes >>> >>> >>> >>> On 10/31/14 13:44, Max Rydahl Andersen wrote: >>> Didn't we do inject of these when Productization built them ? >>> >>> Or was this only done for the archetypes ? >>> >>> >>> >>> /max >>> http://about.me/maxandersen >>> >>> >>> >>> >>> On 31 Oct 2014, at 14:36, Vineet Reynolds Pereira < vpereira at redhat.com > >>> wrote: >>> >>> >>> >>> ----- Original Message ----- >>> >>> >>> From: "Max Rydahl Andersen" < max.andersen at redhat.com > >>> To: "Rafael Benevides" < benevides at redhat.com > >>> Cc: jbossdeveloper at lists.jboss.org , "Alexandre Porcelli" < >>> alexandre.porcelli at gmail.com >, "Tomas Repel" >>> < trepel at redhat.com >, "Nikoleta Ziakova" < nziakova at redhat.com > >>> Sent: Friday, October 31, 2014 6:53:43 PM >>> Subject: Re: [jbossdeveloper] on quickstarts pom.xml >>> >>> >>> >>> On 31 Oct 2014, at 13:58, Rafael Benevides wrote: >>> >>> I know which dependencies were causing the build to fail and where to >>> find them, but it seems that Alexandre wanted to show users how to run >>> a >>> project as easy as clone, build and run. >>> >>> If I'm not wrong, this discussion started with similar issues in this >>> Arun Gupta Twitter thread: >>> https://twitter.com/arungupta/status/502854638832730112 >>> so this is a different question. >>> >>> Question is if we should add the techpreview/all to >>> quickstarts/examples. >>> >>> Not about earlyaccess. >>> >>> And afaik we already did this for quickstarts with a clear warning, >>> right ? >>> AFAIK, they're not in the POM of the quickstarts. A settings.xml is supplied >>> instead: >>> https://github.com/jboss-developer/jboss-wfk-quickstarts/blob/2.6.0.Final/settings.xml >>> >>> But, that would deflect the original question on whether we should add it to >>> POM. >>> Honestly, I dont mind adding it, with the warning that for a real-world >>> project, the repo should instead be in the settings.xml. >>> >>> >>> >>> Thus if ticketmonster does not have that in there I would say it would >>> make sense to add it >>> with similar warning/text as the quickstarts. >>> >>> /max >>> >>> >>> >>> As I also told Alexandre that we were having this discussion, I >>> invited >>> him to give his feedback on this Thread so he can provide more >>> details. >>> >>> Alexandre, >>> >>> Do you mind to share your restrictions and perceptions about the build >>> process ? >>> >>> On 10/31/14 06:47, Marek Novotny wrote: >>> >>> >>> >>> >>> >>> >>> What restrictions does he have ? >>> >>> And I guess the issue here is ticketmonster master needs the >>> earlyaccess bits ? >>> >>> I think ticketmonster master could add the earlyaccess to its pom >>> but >>> then just make sure once it is releaesed it gets removed which >>> should >>> be fine since then it should be using any earlyaccess bundles, >>> right ? >>> Not really, ticket-monster master branch doesn't exist. The closest >>> to >>> master is 2.6.0.Final - >>> https://github.com/jboss-developer/ticket-monster/tree/2.6.0.Final - >>> which is the tight to WFK 2.6.0.GA and all GAVs should be resolvable >>> fromhttp:// maven.repository.redhat.com/techpreview/all/ >>> >>> I think that Rafael knows that 2.7.x-develop is unstable and includes >>> internal product GAVs which are not in all or earlyaccess. >>> >>> So if Alexandre uses 2.6.0.Final branch/tag he should get it to work >>> just with online redhat repository >>> http://maven.repository.redhat.com/techpreview/all/ . If not please >>> advice him to send errors to Vineet or me. >>> _______________________________________________ >>> jbossdeveloper mailing list >>> jbossdeveloper at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper >>> /max >>> http://about.me/maxandersen >>> _______________________________________________ >>> jbossdeveloper mailing list >>> jbossdeveloper at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper >>> _______________________________________________ >>> jbossdeveloper mailing list >>> jbossdeveloper at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper >>> _______________________________________________ >>> jbossdeveloper mailing list >>> jbossdeveloper at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper >>> >>> >>> _______________________________________________ >>> jbossdeveloper mailing list >>> jbossdeveloper at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper >>> >>> >>> >>> _______________________________________________ >>> jbossdeveloper mailing list jbossdeveloper at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper >>> >>> >>> >>> _______________________________________________ >>> jbossdeveloper mailing list >>> jbossdeveloper at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper >> _______________________________________________ >> jbossdeveloper mailing list >> jbossdeveloper at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbossdeveloper > From arun.gupta at gmail.com Mon Dec 1 16:29:20 2014 From: arun.gupta at gmail.com (Arun Gupta) Date: Mon, 1 Dec 2014 13:29:20 -0800 Subject: [jbossdeveloper] Update JBoss Developer Materials to Java EE 7 In-Reply-To: <547C7E85.60007@redhat.com> References: <53FB2B23.6090802@redhat.com> <540DF5BC.3020103@redhat.com> <547C7E85.60007@redhat.com> Message-ID: Good one! "designed to be run on Red Hat JBoss Enterprise Application Platform 7" can be confusing. Change "Wildfly" to "WildFly" Change "Java SDK 6.0" to "JDK 7.0" - this is a requirement for WildFly anyway. Arun On Mon, Dec 1, 2014 at 6:43 AM, Rafael Benevides wrote: > Hi all, > > I'm pleased to announce that we have now the first Java EE 7 feature shown > as a JBoss Developer Quickstart: JDF-765 - Websocket server endpoint - > https://github.com/jboss-developer/jboss-sandbox-quickstarts/tree/master/websocket-endpoint > > It is published at http://websocket-benevides.rhcloud.com if you want to > try it. > > > > On 9/9/14 01:29, Arun Gupta wrote: > > Hi Rafael, > > If you are looking for the top 5 features that should be highlighted in > Java EE 7, then they would be: > > - WebSocket server endpoint > - Chunk style batch processing > - Object-based JSON generation and Stream-based JSON consuming > - ManagedExecutorService > - JAX-RS Client API > > There are samples for each one of these at: > > https://github.com/javaee-samples/javaee7-samples > > I had some basic discussions with Vineet last week on where some of > these usecases can be incorporated in Ticket Monster. Please keep me > involved in the design of how TiMo is going to evolve for Java EE 7 > support. Some of the documents that would be very useful from that process > are: > > - How to migrate an existing Java EE 6 application to EE 7 ? This would > be very useful to our customers as well. > - Compare LOC/deployment descriptors between the EE 6 and 7 versions. > These would make nice graphs. > - Before/after code fragment for different pieces that were migrated. > - What proprietary technologies were replaced with standards-based when > using EE 7 > > Cheers > Arun > > On Mon, Sep 8, 2014 at 9:30 PM, Rafael Benevides > wrote: > >> Returning the discussion about JBoss Developer Material for Java EE 7, >> >> Arun, >> >> Do you have the list of the 5 features/use cases/quickstarts that we want >> to show, right? Can you share it? >> >> Thanks >> >> Em 8/25/14, 9:25, Rafael Benevides escreveu: >> >> Hi All, >> >> We're about to start the update process of JBoss Developer Materials to >> Java EE 7. But before put the hands on it I talked with Pete and we decided >> that it's better to bring this $subject to discussion with everyone on this >> list. >> >> Ticket Monster already started to be updated >> https://issues.jboss.org/browse/JDF-754 >> >> Actually our jboss-eap-quickstarts have been updated to Java EE 7.0 on >> https://github.com/wildfly/quickstart. Anyway we still miss some Java EE >> 7 specific features/use cases on these quickstarts. >> >> It seems that Arun Gupta has a list of about 5 features/use >> cases/quickstarts that we want to show. The idea is to have these Java EE 7 >> specific quickstarts to be available at www.jboss.org >> >> The main point that we should discuss are: >> >> - What are those quickstarts/features? >> - Where will we host those Java EE 7 quickstarts? >> https://github.com/jboss-developer/jboss-sandbox-quickstarts ? >> - Paul Robinson, >> >> Considering that the jboss-sandbox-quickstarts github structure, do you >> think that it could have any issues with it? Can we choose just specific >> quickstarts to be present at www.jboss.org >> >> Well, >> >> This is just a starting point, so we can discuss about this update >> process until we have a detailed plan. >> >> The Google docs with the plan is available at: >> https://docs.google.com/document/d/1n0uVG2rhDf1eSp0b4MhggdIxNa3cthnuWaj2OjBpxoY/edit >> >> >> -- >> >> *Rafael Benevides | Senior Software Engineer* >> JBoss Developer >> M: +55-61-9269-6576 >> >> [image: Red Hat] >> >> Better technology. Faster innovation. Powered by community collaboration. >> See how it works at www.redhat.com >> >> [image: LinkedIn] [image: >> Youtube] >> >> >> _______________________________________________ >> jbossdeveloper mailing listjbossdeveloper at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/jbossdeveloper >> >> >> >> _______________________________________________ >> jbossdeveloper mailing list >> jbossdeveloper at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbossdeveloper >> > > > > -- > http://blog.arungupta.me > http://twitter.com/arungupta > > > -- http://blog.arungupta.me http://twitter.com/arungupta -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20141201/afcb5ce2/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 616 bytes Desc: not available Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20141201/afcb5ce2/attachment-0002.png -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 4815 bytes Desc: not available Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20141201/afcb5ce2/attachment-0001.jpe -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 597 bytes Desc: not available Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20141201/afcb5ce2/attachment-0003.png From benevides at redhat.com Tue Dec 2 05:57:24 2014 From: benevides at redhat.com (Rafael Benevides) Date: Tue, 02 Dec 2014 08:57:24 -0200 Subject: [jbossdeveloper] Update JBoss Developer Materials to Java EE 7 In-Reply-To: References: <53FB2B23.6090802@redhat.com> <540DF5BC.3020103@redhat.com> <547C7E85.60007@redhat.com> Message-ID: <547D9B14.3040308@redhat.com> Thanks Arun! Updated! On 12/1/14 19:29, Arun Gupta wrote: > Good one! > > "designed to be run on Red Hat JBoss Enterprise Application Platform > 7" can be confusing. > Change "Wildfly" to "WildFly" > Change "Java SDK 6.0" to "JDK 7.0" - this is a requirement for WildFly > anyway. > > Arun > > On Mon, Dec 1, 2014 at 6:43 AM, Rafael Benevides > wrote: > > Hi all, > > I'm pleased to announce that we have now the first Java EE 7 > feature shown as a JBoss Developer Quickstart: JDF-765 - Websocket > server endpoint - > https://github.com/jboss-developer/jboss-sandbox-quickstarts/tree/master/websocket-endpoint > > It is published at http://websocket-benevides.rhcloud.com if you > want to try it. > > > > On 9/9/14 01:29, Arun Gupta wrote: >> Hi Rafael, >> >> If you are looking for the top 5 features that should be >> highlighted in Java EE 7, then they would be: >> >> - WebSocket server endpoint >> - Chunk style batch processing >> - Object-based JSON generation and Stream-based JSON consuming >> - ManagedExecutorService >> - JAX-RS Client API >> >> There are samples for each one of these at: >> >> https://github.com/javaee-samples/javaee7-samples >> >> I had some basic discussions with Vineet last week on where some >> of these usecases can be incorporated in Ticket Monster. Please >> keep me involved in the design of how TiMo is going to evolve for >> Java EE 7 support. Some of the documents that would be very >> useful from that process are: >> >> - How to migrate an existing Java EE 6 application to EE 7 ? This >> would be very useful to our customers as well. >> - Compare LOC/deployment descriptors between the EE 6 and 7 >> versions. These would make nice graphs. >> - Before/after code fragment for different pieces that were migrated. >> - What proprietary technologies were replaced with >> standards-based when using EE 7 >> >> Cheers >> Arun >> >> On Mon, Sep 8, 2014 at 9:30 PM, Rafael Benevides >> > wrote: >> >> Returning the discussion about JBoss Developer Material for >> Java EE 7, >> >> Arun, >> >> Do you have the list of the 5 features/use cases/quickstarts >> that we want to show, right? Can you share it? >> >> Thanks >> >> Em 8/25/14, 9:25, Rafael Benevides escreveu: >>> Hi All, >>> >>> We're about to start the update process of JBoss Developer >>> Materials to Java EE 7. But before put the hands on it I >>> talked with Pete and we decided that it's better to bring >>> this $subject to discussion with everyone on this list. >>> >>> Ticket Monster already started to be updated >>> https://issues.jboss.org/browse/JDF-754 >>> >>> Actually our jboss-eap-quickstarts have been updated to Java >>> EE 7.0 on https://github.com/wildfly/quickstart. Anyway we >>> still miss some Java EE 7 specific features/use cases on >>> these quickstarts. >>> >>> It seems that Arun Gupta has a list of about 5 features/use >>> cases/quickstarts that we want to show. The idea is to have >>> these Java EE 7 specific quickstarts to be available at >>> www.jboss.org >>> >>> The main point that we should discuss are: >>> >>> - What are those quickstarts/features? >>> - Where will we host those Java EE 7 quickstarts? >>> https://github.com/jboss-developer/jboss-sandbox-quickstarts ? >>> - Paul Robinson, >>> >>> Considering that the jboss-sandbox-quickstarts github >>> structure, do you think that it could have any issues with >>> it? Can we choose just specific quickstarts to be present at >>> www.jboss.org >>> >>> Well, >>> >>> This is just a starting point, so we can discuss about this >>> update process until we have a detailed plan. >>> >>> The Google docs with the plan is available at: >>> https://docs.google.com/document/d/1n0uVG2rhDf1eSp0b4MhggdIxNa3cthnuWaj2OjBpxoY/edit >>> >>> >>> -- >>> >>> *Rafael Benevides | Senior Software Engineer* >>> JBoss Developer >>> M: +55-61-9269-6576 >>> >>> Red Hat >>> >>> Better technology. Faster innovation. Powered by community >>> collaboration. >>> See how it works at www.redhat.com >>> >>> LinkedIn Youtube >>> >>> >>> >>> _______________________________________________ >>> jbossdeveloper mailing list >>> jbossdeveloper at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper >> >> >> _______________________________________________ >> jbossdeveloper mailing list >> jbossdeveloper at lists.jboss.org >> >> https://lists.jboss.org/mailman/listinfo/jbossdeveloper >> >> >> >> >> -- >> http://blog.arungupta.me >> http://twitter.com/arungupta > > > > > -- > http://blog.arungupta.me > http://twitter.com/arungupta -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20141202/f6796f21/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 4815 bytes Desc: not available Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20141202/f6796f21/attachment-0001.jpe -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 597 bytes Desc: not available Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20141202/f6796f21/attachment-0002.png -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 616 bytes Desc: not available Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20141202/f6796f21/attachment-0003.png From pmuir at redhat.com Tue Dec 2 12:29:43 2014 From: pmuir at redhat.com (Pete Muir) Date: Tue, 2 Dec 2014 17:29:43 +0000 Subject: [jbossdeveloper] Update JBoss Developer Materials to Java EE 7 In-Reply-To: <547D9B14.3040308@redhat.com> References: <53FB2B23.6090802@redhat.com> <540DF5BC.3020103@redhat.com> <547C7E85.60007@redhat.com> <547D9B14.3040308@redhat.com> Message-ID: Looks good! > On 2 Dec 2014, at 10:57, Rafael Benevides wrote: > > Thanks Arun! > > Updated! > > On 12/1/14 19:29, Arun Gupta wrote: >> Good one! >> >> "designed to be run on Red Hat JBoss Enterprise Application Platform 7" can be confusing. >> Change "Wildfly" to "WildFly" >> Change "Java SDK 6.0" to "JDK 7.0" - this is a requirement for WildFly anyway. >> >> Arun >> >> On Mon, Dec 1, 2014 at 6:43 AM, Rafael Benevides > wrote: >> Hi all, >> >> I'm pleased to announce that we have now the first Java EE 7 feature shown as a JBoss Developer Quickstart: JDF-765 - Websocket server endpoint - https://github.com/jboss-developer/jboss-sandbox-quickstarts/tree/master/websocket-endpoint >> >> It is published at http://websocket-benevides.rhcloud.com if you want to try it. >> >> >> >> On 9/9/14 01:29, Arun Gupta wrote: >>> Hi Rafael, >>> >>> If you are looking for the top 5 features that should be highlighted in Java EE 7, then they would be: >>> >>> - WebSocket server endpoint >>> - Chunk style batch processing >>> - Object-based JSON generation and Stream-based JSON consuming >>> - ManagedExecutorService >>> - JAX-RS Client API >>> >>> There are samples for each one of these at: >>> >>> https://github.com/javaee-samples/javaee7-samples >>> >>> I had some basic discussions with Vineet last week on where some of these usecases can be incorporated in Ticket Monster. Please keep me involved in the design of how TiMo is going to evolve for Java EE 7 support. Some of the documents that would be very useful from that process are: >>> >>> - How to migrate an existing Java EE 6 application to EE 7 ? This would be very useful to our customers as well. >>> - Compare LOC/deployment descriptors between the EE 6 and 7 versions. These would make nice graphs. >>> - Before/after code fragment for different pieces that were migrated. >>> - What proprietary technologies were replaced with standards-based when using EE 7 >>> >>> Cheers >>> Arun >>> >>> On Mon, Sep 8, 2014 at 9:30 PM, Rafael Benevides > wrote: >>> Returning the discussion about JBoss Developer Material for Java EE 7, >>> >>> Arun, >>> >>> Do you have the list of the 5 features/use cases/quickstarts that we want to show, right? Can you share it? >>> >>> Thanks >>> >>> Em 8/25/14, 9:25, Rafael Benevides escreveu: >>>> Hi All, >>>> >>>> We're about to start the update process of JBoss Developer Materials to Java EE 7. But before put the hands on it I talked with Pete and we decided that it's better to bring this $subject to discussion with everyone on this list. >>>> >>>> Ticket Monster already started to be updated https://issues.jboss.org/browse/JDF-754 >>>> >>>> Actually our jboss-eap-quickstarts have been updated to Java EE 7.0 on https://github.com/wildfly/quickstart . Anyway we still miss some Java EE 7 specific features/use cases on these quickstarts. >>>> >>>> It seems that Arun Gupta has a list of about 5 features/use cases/quickstarts that we want to show. The idea is to have these Java EE 7 specific quickstarts to be available at www.jboss.org >>>> >>>> The main point that we should discuss are: >>>> >>>> - What are those quickstarts/features? >>>> - Where will we host those Java EE 7 quickstarts? https://github.com/jboss-developer/jboss-sandbox-quickstarts ? >>>> - Paul Robinson, >>>> >>>> Considering that the jboss-sandbox-quickstarts github structure, do you think that it could have any issues with it? Can we choose just specific quickstarts to be present at www.jboss.org >>>> >>>> Well, >>>> >>>> This is just a starting point, so we can discuss about this update process until we have a detailed plan. >>>> >>>> The Google docs with the plan is available at: https://docs.google.com/document/d/1n0uVG2rhDf1eSp0b4MhggdIxNa3cthnuWaj2OjBpxoY/edit >>>> >>>> >>>> -- >>>> >>>> Rafael Benevides | Senior Software Engineer >>>> JBoss Developer >>>> M: +55-61-9269-6576 >>>> >>>> >>>> >>>> Better technology. Faster innovation. Powered by community collaboration. >>>> See how it works at www.redhat.com >>>> >>>> >>>> >>>> _______________________________________________ >>>> jbossdeveloper mailing list >>>> jbossdeveloper at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper >>> >>> _______________________________________________ >>> jbossdeveloper mailing list >>> jbossdeveloper at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper >>> >>> >>> >>> -- >>> http://blog.arungupta.me >>> http://twitter.com/arungupta >> >> >> >> -- >> http://blog.arungupta.me >> http://twitter.com/arungupta > _______________________________________________ > jbossdeveloper mailing list > jbossdeveloper at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbossdeveloper -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20141202/4da185ba/attachment.html From sgilda at redhat.com Wed Dec 3 18:38:13 2014 From: sgilda at redhat.com (Sande Gilda) Date: Wed, 03 Dec 2014 18:38:13 -0500 Subject: [jbossdeveloper] Update JBoss Developer Materials to Java EE 7 In-Reply-To: References: <53FB2B23.6090802@redhat.com> <540DF5BC.3020103@redhat.com> <547C7E85.60007@redhat.com> <547D9B14.3040308@redhat.com> Message-ID: <547F9EE5.2050304@redhat.com> Rafael, this quickstart looks great! I wish everyone wrote such a good description of what's going on in the code. I issued a pull with some minor changes if you'd like to review. On 12/02/2014 12:29 PM, Pete Muir wrote: > Looks good! > >> On 2 Dec 2014, at 10:57, Rafael Benevides > > wrote: >> >> Thanks Arun! >> >> Updated! >> >> On 12/1/14 19:29, Arun Gupta wrote: >>> Good one! >>> >>> "designed to be run on Red Hat JBoss Enterprise Application Platform >>> 7" can be confusing. >>> Change "Wildfly" to "WildFly" >>> Change "Java SDK 6.0" to "JDK 7.0" - this is a requirement for >>> WildFly anyway. >>> >>> Arun >>> >>> On Mon, Dec 1, 2014 at 6:43 AM, Rafael Benevides >>> > wrote: >>> >>> Hi all, >>> >>> I'm pleased to announce that we have now the first Java EE 7 >>> feature shown as a JBoss Developer Quickstart: JDF-765 - >>> Websocket server endpoint - >>> https://github.com/jboss-developer/jboss-sandbox-quickstarts/tree/master/websocket-endpoint >>> >>> It is published at http://websocket-benevides.rhcloud.com >>> if you want to try it. >>> >>> >>> >>> On 9/9/14 01:29, Arun Gupta wrote: >>>> Hi Rafael, >>>> >>>> If you are looking for the top 5 features that should be >>>> highlighted in Java EE 7, then they would be: >>>> >>>> - WebSocket server endpoint >>>> - Chunk style batch processing >>>> - Object-based JSON generation and Stream-based JSON consuming >>>> - ManagedExecutorService >>>> - JAX-RS Client API >>>> >>>> There are samples for each one of these at: >>>> >>>> https://github.com/javaee-samples/javaee7-samples >>>> >>>> I had some basic discussions with Vineet last week on where >>>> some of these usecases can be incorporated in Ticket Monster. >>>> Please keep me involved in the design of how TiMo is going to >>>> evolve for Java EE 7 support. Some of the documents that would >>>> be very useful from that process are: >>>> >>>> - How to migrate an existing Java EE 6 application to EE 7 ? >>>> This would be very useful to our customers as well. >>>> - Compare LOC/deployment descriptors between the EE 6 and 7 >>>> versions. These would make nice graphs. >>>> - Before/after code fragment for different pieces that were >>>> migrated. >>>> - What proprietary technologies were replaced with >>>> standards-based when using EE 7 >>>> >>>> Cheers >>>> Arun >>>> >>>> On Mon, Sep 8, 2014 at 9:30 PM, Rafael Benevides >>>> > wrote: >>>> >>>> Returning the discussion about JBoss Developer Material for >>>> Java EE 7, >>>> >>>> Arun, >>>> >>>> Do you have the list of the 5 features/use >>>> cases/quickstarts that we want to show, right? Can you >>>> share it? >>>> >>>> Thanks >>>> >>>> Em 8/25/14, 9:25, Rafael Benevides escreveu: >>>>> Hi All, >>>>> >>>>> We're about to start the update process of JBoss Developer >>>>> Materials to Java EE 7. But before put the hands on it I >>>>> talked with Pete and we decided that it's better to bring >>>>> this $subject to discussion with everyone on this list. >>>>> >>>>> Ticket Monster already started to be updated >>>>> https://issues.jboss.org/browse/JDF-754 >>>>> >>>>> Actually our jboss-eap-quickstarts have been updated to >>>>> Java EE 7.0 on https://github.com/wildfly/quickstart. >>>>> Anyway we still miss some Java EE 7 specific features/use >>>>> cases on these quickstarts. >>>>> >>>>> It seems that Arun Gupta has a list of about 5 >>>>> features/use cases/quickstarts that we want to show. The >>>>> idea is to have these Java EE 7 specific quickstarts to be >>>>> available at www.jboss.org >>>>> >>>>> The main point that we should discuss are: >>>>> >>>>> - What are those quickstarts/features? >>>>> - Where will we host those Java EE 7 quickstarts? >>>>> https://github.com/jboss-developer/jboss-sandbox-quickstarts ? >>>>> - Paul Robinson, >>>>> >>>>> Considering that the jboss-sandbox-quickstarts github >>>>> structure, do you think that it could have any issues with >>>>> it? Can we choose just specific quickstarts to be present >>>>> at www.jboss.org >>>>> >>>>> Well, >>>>> >>>>> This is just a starting point, so we can discuss about >>>>> this update process until we have a detailed plan. >>>>> >>>>> The Google docs with the plan is available at: >>>>> https://docs.google.com/document/d/1n0uVG2rhDf1eSp0b4MhggdIxNa3cthnuWaj2OjBpxoY/edit >>>>> >>>>> >>>>> -- >>>>> >>>>> *Rafael Benevides | Senior Software Engineer* >>>>> JBoss Developer >>>>> M: +55-61-9269-6576 >>>>> >>>>> >>>>> >>>>> Better technology. Faster innovation. Powered by community >>>>> collaboration. >>>>> See how it works at www.redhat.com >>>>> >>>>> >>>>> >>>> Attachment.png> >>>>> >>>>> >>>>> _______________________________________________ >>>>> jbossdeveloper mailing list >>>>> jbossdeveloper at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper >>>> >>>> >>>> _______________________________________________ >>>> jbossdeveloper mailing list >>>> jbossdeveloper at lists.jboss.org >>>> >>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper >>>> >>>> >>>> >>>> >>>> -- >>>> http://blog.arungupta.me >>>> http://twitter.com/arungupta >>> >>> >>> >>> >>> -- >>> http://blog.arungupta.me >>> http://twitter.com/arungupta >> >> _______________________________________________ >> jbossdeveloper mailing list >> jbossdeveloper at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbossdeveloper > > > > _______________________________________________ > jbossdeveloper mailing list > jbossdeveloper at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbossdeveloper -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20141203/9d19ef73/attachment-0001.html From benevides at redhat.com Thu Dec 4 06:41:02 2014 From: benevides at redhat.com (Rafael Benevides) Date: Thu, 04 Dec 2014 09:41:02 -0200 Subject: [jbossdeveloper] Update JBoss Developer Materials to Java EE 7 In-Reply-To: <547F9EE5.2050304@redhat.com> References: <53FB2B23.6090802@redhat.com> <540DF5BC.3020103@redhat.com> <547C7E85.60007@redhat.com> <547D9B14.3040308@redhat.com> <547F9EE5.2050304@redhat.com> Message-ID: <5480484E.8060103@redhat.com> Thanks! :) PR merged! On 12/3/14 21:38, Sande Gilda wrote: > Rafael, this quickstart looks great! I wish everyone wrote such a good > description of what's going on in the code. I issued a pull with some > minor changes if you'd like to review. > > On 12/02/2014 12:29 PM, Pete Muir wrote: >> Looks good! >> >>> On 2 Dec 2014, at 10:57, Rafael Benevides >> > wrote: >>> >>> Thanks Arun! >>> >>> Updated! >>> >>> On 12/1/14 19:29, Arun Gupta wrote: >>>> Good one! >>>> >>>> "designed to be run on Red Hat JBoss Enterprise Application >>>> Platform 7" can be confusing. >>>> Change "Wildfly" to "WildFly" >>>> Change "Java SDK 6.0" to "JDK 7.0" - this is a requirement for >>>> WildFly anyway. >>>> >>>> Arun >>>> >>>> On Mon, Dec 1, 2014 at 6:43 AM, Rafael Benevides >>>> > wrote: >>>> >>>> Hi all, >>>> >>>> I'm pleased to announce that we have now the first Java EE 7 >>>> feature shown as a JBoss Developer Quickstart: JDF-765 - >>>> Websocket server endpoint - >>>> https://github.com/jboss-developer/jboss-sandbox-quickstarts/tree/master/websocket-endpoint >>>> >>>> It is published at http://websocket-benevides.rhcloud.com >>>> if you want to try it. >>>> >>>> >>>> >>>> On 9/9/14 01:29, Arun Gupta wrote: >>>>> Hi Rafael, >>>>> >>>>> If you are looking for the top 5 features that should be >>>>> highlighted in Java EE 7, then they would be: >>>>> >>>>> - WebSocket server endpoint >>>>> - Chunk style batch processing >>>>> - Object-based JSON generation and Stream-based JSON consuming >>>>> - ManagedExecutorService >>>>> - JAX-RS Client API >>>>> >>>>> There are samples for each one of these at: >>>>> >>>>> https://github.com/javaee-samples/javaee7-samples >>>>> >>>>> I had some basic discussions with Vineet last week on where >>>>> some of these usecases can be incorporated in Ticket Monster. >>>>> Please keep me involved in the design of how TiMo is going to >>>>> evolve for Java EE 7 support. Some of the documents that would >>>>> be very useful from that process are: >>>>> >>>>> - How to migrate an existing Java EE 6 application to EE 7 ? >>>>> This would be very useful to our customers as well. >>>>> - Compare LOC/deployment descriptors between the EE 6 and 7 >>>>> versions. These would make nice graphs. >>>>> - Before/after code fragment for different pieces that were >>>>> migrated. >>>>> - What proprietary technologies were replaced with >>>>> standards-based when using EE 7 >>>>> >>>>> Cheers >>>>> Arun >>>>> >>>>> On Mon, Sep 8, 2014 at 9:30 PM, Rafael Benevides >>>>> > wrote: >>>>> >>>>> Returning the discussion about JBoss Developer Material >>>>> for Java EE 7, >>>>> >>>>> Arun, >>>>> >>>>> Do you have the list of the 5 features/use >>>>> cases/quickstarts that we want to show, right? Can you >>>>> share it? >>>>> >>>>> Thanks >>>>> >>>>> Em 8/25/14, 9:25, Rafael Benevides escreveu: >>>>>> Hi All, >>>>>> >>>>>> We're about to start the update process of JBoss >>>>>> Developer Materials to Java EE 7. But before put the >>>>>> hands on it I talked with Pete and we decided that it's >>>>>> better to bring this $subject to discussion with everyone >>>>>> on this list. >>>>>> >>>>>> Ticket Monster already started to be updated >>>>>> https://issues.jboss.org/browse/JDF-754 >>>>>> >>>>>> Actually our jboss-eap-quickstarts have been updated to >>>>>> Java EE 7.0 on https://github.com/wildfly/quickstart. >>>>>> Anyway we still miss some Java EE 7 specific features/use >>>>>> cases on these quickstarts. >>>>>> >>>>>> It seems that Arun Gupta has a list of about 5 >>>>>> features/use cases/quickstarts that we want to show. The >>>>>> idea is to have these Java EE 7 specific quickstarts to >>>>>> be available at www.jboss.org >>>>>> >>>>>> The main point that we should discuss are: >>>>>> >>>>>> - What are those quickstarts/features? >>>>>> - Where will we host those Java EE 7 quickstarts? >>>>>> https://github.com/jboss-developer/jboss-sandbox-quickstarts >>>>>> ? >>>>>> - Paul Robinson, >>>>>> >>>>>> Considering that the jboss-sandbox-quickstarts github >>>>>> structure, do you think that it could have any issues >>>>>> with it? Can we choose just specific quickstarts to be >>>>>> present at www.jboss.org >>>>>> >>>>>> Well, >>>>>> >>>>>> This is just a starting point, so we can discuss about >>>>>> this update process until we have a detailed plan. >>>>>> >>>>>> The Google docs with the plan is available at: >>>>>> https://docs.google.com/document/d/1n0uVG2rhDf1eSp0b4MhggdIxNa3cthnuWaj2OjBpxoY/edit >>>>>> >>>>>> >>>>>> -- >>>>>> >>>>>> *Rafael Benevides | Senior Software Engineer* >>>>>> JBoss Developer >>>>>> M: +55-61-9269-6576 >>>>>> >>>>>> >>>>>> >>>>>> Better technology. Faster innovation. Powered by >>>>>> community collaboration. >>>>>> See how it works at www.redhat.com >>>>>> >>>>>> >>>>>> >>>>> Attachment.png> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> jbossdeveloper mailing list >>>>>> jbossdeveloper at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper >>>>> >>>>> >>>>> _______________________________________________ >>>>> jbossdeveloper mailing list >>>>> jbossdeveloper at lists.jboss.org >>>>> >>>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper >>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> http://blog.arungupta.me >>>>> http://twitter.com/arungupta >>>> >>>> >>>> >>>> >>>> -- >>>> http://blog.arungupta.me >>>> http://twitter.com/arungupta >>> >>> _______________________________________________ >>> jbossdeveloper mailing list >>> jbossdeveloper at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper >> >> >> >> _______________________________________________ >> jbossdeveloper mailing list >> jbossdeveloper at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbossdeveloper > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20141204/6e2e70be/attachment-0001.html From paul.robinson at redhat.com Wed Dec 10 08:46:17 2014 From: paul.robinson at redhat.com (Paul Robinson) Date: Wed, 10 Dec 2014 13:46:17 +0000 Subject: [jbossdeveloper] Doing a Staging build locally Message-ID: All, Is anyone doing a staging build of the site on their local machine? You?d probably be using this command: rake preview[staging] We are seeing some odd data appear in the DCP server used by the staging sites. I?m trying to track down where it is coming from. Paul. -- Paul Robinson JBoss Developer Team Lead (www.jboss.org) JBoss, a Division of Red Hat Registered in England and Wales under Company Registration No. 03798903 Directors:Michael Cunningham (US), Charles Peters (US), Matt Parson (US), Paul Hickey (Ireland) -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20141210/9f9a995d/attachment.html From paul.robinson at redhat.com Wed Dec 10 08:50:46 2014 From: paul.robinson at redhat.com (Paul Robinson) Date: Wed, 10 Dec 2014 13:50:46 +0000 Subject: [jbossdeveloper] Doing a Staging build locally In-Reply-To: References: Message-ID: <8D1AF40F-4675-49C5-9FC4-306D05C5C6F5@redhat.com> I forgot to say, One such build occurred today at "2014-12-10T11:15:09.790Z? UTC time. This is about 2.5hrs ago. Paul. > On 10 Dec 2014, at 13:46, Paul Robinson wrote: > > All, > > Is anyone doing a staging build of the site on their local machine? You?d probably be using this command: > > rake preview[staging] > > We are seeing some odd data appear in the DCP server used by the staging sites. I?m trying to track down where it is coming from. > > Paul. > > -- > Paul Robinson > JBoss Developer Team Lead (www.jboss.org ) > > JBoss, a Division of Red Hat > Registered in England and Wales under Company Registration No. 03798903 > Directors:Michael Cunningham (US), Charles Peters (US), Matt Parson (US), Paul Hickey (Ireland) > > _______________________________________________ > jbossdeveloper mailing list > jbossdeveloper at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbossdeveloper Paul. -- Paul Robinson JBoss Developer Team Lead (www.jboss.org) JBoss, a Division of Red Hat Registered in England and Wales under Company Registration No. 03798903 Directors:Michael Cunningham (US), Charles Peters (US), Matt Parson (US), Paul Hickey (Ireland) -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20141210/aa5ef943/attachment.html From paul.robinson at redhat.com Wed Dec 10 11:39:50 2014 From: paul.robinson at redhat.com (Paul Robinson) Date: Wed, 10 Dec 2014 16:39:50 +0000 Subject: [jbossdeveloper] Production and Staging builds disabled Message-ID: All, I?ve disabled the Production and Staging CI builds for about 18hours. It should be back on by 10:00 UTC on Thursday. This is to confirm that the bad data, we are seeing, is not being put into the DCP by our CI. If anyone needs these to run, before then, please let me know. Paul. -- Paul Robinson JBoss Developer Team Lead (www.jboss.org) JBoss, a Division of Red Hat Registered in England and Wales under Company Registration No. 03798903 Directors:Michael Cunningham (US), Charles Peters (US), Matt Parson (US), Paul Hickey (Ireland) -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20141210/35735497/attachment.html From paul.robinson at redhat.com Wed Dec 10 12:39:09 2014 From: paul.robinson at redhat.com (Paul Robinson) Date: Wed, 10 Dec 2014 17:39:09 +0000 Subject: [jbossdeveloper] Doing a Staging build locally In-Reply-To: References: Message-ID: <2FF5649F-8AC7-4030-B431-8D48F3EB107B@redhat.com> Looks like Jason has figured it out. We?ve not confirmed it yet, but it?s pretty clear that it?s a bug... A bit of code that is pushing to the DCP didn?t have a guard on it: https://github.com/jboss-developer/www.jboss.org/blob/master/_ext/connectors.rb#L31 . This is what it should look like: https://github.com/jboss-developer/www.jboss.org/blob/master/_ext/stacks.rb#L157 Paul. > On 10 Dec 2014, at 13:46, Paul Robinson wrote: > > All, > > Is anyone doing a staging build of the site on their local machine? You?d probably be using this command: > > rake preview[staging] > > We are seeing some odd data appear in the DCP server used by the staging sites. I?m trying to track down where it is coming from. > > Paul. > > -- > Paul Robinson > JBoss Developer Team Lead (www.jboss.org ) > > JBoss, a Division of Red Hat > Registered in England and Wales under Company Registration No. 03798903 > Directors:Michael Cunningham (US), Charles Peters (US), Matt Parson (US), Paul Hickey (Ireland) > Paul. -- Paul Robinson JBoss Developer Team Lead (www.jboss.org) JBoss, a Division of Red Hat Registered in England and Wales under Company Registration No. 03798903 Directors:Michael Cunningham (US), Charles Peters (US), Matt Parson (US), Paul Hickey (Ireland) -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20141210/da24a97f/attachment-0001.html From paul.robinson at redhat.com Wed Dec 10 12:39:23 2014 From: paul.robinson at redhat.com (Paul Robinson) Date: Wed, 10 Dec 2014 17:39:23 +0000 Subject: [jbossdeveloper] Production and Staging builds disabled In-Reply-To: References: Message-ID: CI is back on now. > On 10 Dec 2014, at 16:39, Paul Robinson wrote: > > All, > > I?ve disabled the Production and Staging CI builds for about 18hours. It should be back on by 10:00 UTC on Thursday. This is to confirm that the bad data, we are seeing, is not being put into the DCP by our CI. > > If anyone needs these to run, before then, please let me know. > > Paul. > > -- > Paul Robinson > JBoss Developer Team Lead (www.jboss.org ) > > JBoss, a Division of Red Hat > Registered in England and Wales under Company Registration No. 03798903 > Directors:Michael Cunningham (US), Charles Peters (US), Matt Parson (US), Paul Hickey (Ireland) > Paul. -- Paul Robinson JBoss Developer Team Lead (www.jboss.org) JBoss, a Division of Red Hat Registered in England and Wales under Company Registration No. 03798903 Directors:Michael Cunningham (US), Charles Peters (US), Matt Parson (US), Paul Hickey (Ireland) -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20141210/14c95230/attachment.html From benevides at redhat.com Wed Dec 10 20:14:26 2014 From: benevides at redhat.com (Rafael Benevides) Date: Wed, 10 Dec 2014 23:14:26 -0200 Subject: [jbossdeveloper] Fwd: BRMS 6 Quickstarts In-Reply-To: <5328428C.9060901@redhat.com> References: <52B84D8A.2080907@redhat.com> <52C6DBDE.7020708@redhat.com> <52CAABBC.7010304@redhat.com> <5328428C.9060901@redhat.com> Message-ID: <5488EFF2.7000506@redhat.com> Hi all, Since this email in March, the BRMS/BPMS Quickstarts become part of product release since version 6.0.2+ On the latest meeting with Geoffrey and Petr we discussed about the "owner" of these Quickstarts. As conclusion, we decided to formalize the donation of them to BRMS/BRPMS team. I'd like to ask that the person from BPMS/BRMS team that will take responsibility on them, to join jbossdeveloper at lists.jboss.org ( https://lists.jboss.org/mailman/listinfo/jbossdeveloper ) so he can be aware of the latest discussion about JBoss Developer Materials. Thanks BRMS/BPMS team for the support that I received during Quickstarts development. Rafael On 3/18/14 09:56, Rafael Benevides wrote: > Hi all, > > After a long development cycle and review and some feedbacks ( Thanks > Sande, Burr, Geoffrey ), the BRMS Quickstarts ( > https://github.com/jboss-developer/jboss-brms-quickstarts ) are ready! > > From now, I think they can be included as part of BRMS distro for 6.1 > > Feel free to poke it. > > Em 06/01/14 11:12, Rafael Benevides escreveu: >> I opened the following Jiras, so we can discuss over them individually. >> >> [JDF-581] Create Beginner BRMS Quicsktart: helloworld-drl >> [JDF-582] Create an Intermediate BRMS Quickstart: helloworld-stateful >> [JDF-583] Create an Intermediate BRMS Quickstart: helloworld-brms >> [JDF-584] Create an Intermediate BRMS Quickstart: decision-table >> [JDF-585] Create an Advanced BRMS Quickstart: store-dsl >> [JDF-586] Create an Advanced BRMS Quickstart: helloworld-cep >> [JDF-587] Create an Advanced BRMS Quickstart: brms-integration >> [JDF-588] Create an Advanced BRMS Quickstart: brms-planner >> [JDF-589] Create an Intermediate BPMS Quickstart: brms-bpms >> [JDF-590] Create an Advanced BPMS Quickstart: brms-bpms-task >> >> Em 03/01/14 13:48, Rafael Benevides escreveu: >>> Hi all, >>> >>> Today I talked to Edson Tirelli on #droolsdev so the Drools team can >>> be aware of this effort by our side. >>> >>> I also discovered that they already have their Maven BOMs on >>> https://github.com/droolsjbpm/droolsjbpm-build-bootstrap . It was >>> discussed that we could move this repo to >>> https://github.com/jboss-developer/jboss-brms-boms for BRMS 6.1 >>> >>> Anyway the JBoss Developer materials uses a little bit different >>> GAV: org.jboss.bom.brms:jboss-javaee-6.0-with-drools:6.1-redhat-X - >>> Probably wrapping the existing BRMS BOMs should be better to avoid >>> too much changes for BRMS 6.1. Don't you agree ? But if we do it, we >>> will have two BRMS BOMs ( the one provided by Drools and one >>> provided by JBoss Developer Materials). Any comments on this are >>> welcome! >>> >>> I'm copying them so they can be evolved on the discussion and >>> provide any feedback. Edson, Mark, feel free also to give any >>> feedback on the proposed Quickstarts below. >>> >>> >>> >>> -------- Mensagem original -------- >>> Assunto: BRMS 6 Quickstarts >>> Data: Mon, 23 Dec 2013 12:49:46 -0200 >>> De: Rafael Benevides >>> Empresa: Red Hat >>> Para: Peter Muir , Burr Sutter >>> >>> >>> >>> Hi Pete/Burr >>> >>> I'm starting to plan BRMS 6 Quickstarts and besides the BRMS BOM ( >>> https://github.com/jboss-developer/jboss-brms-boms ), I also would >>> like to included the following quickstarts that I'm planning: >>> >>> The idea is to discuss/check if the features covered are OK and also >>> hear any kind of feedback about the possible uses cases. >>> >>> Note: 1- Some of them I didn't think yet about what use cases to >>> show, but the idea is to focus on the feature. >>> 2 - I'm not familiar with BPM (last BPM project that I used was jBPM >>> 3), so it is possible that the features are not well covered, so any >>> feedback are welcome! >>> >>> Basic >>> helloworld-drl: Basic - A simple helloworld reading a DRL from >>> Classpath integrated with CDI >>> >>> Intermediate >>> helloworld-stateful: Intermediate - A use case for Stateful session. >>> Maybe Stock Monitoring >>> helloworld-brms: Intermediate - The same application reading the DRL >>> from the BRMS server using the Agent >>> decision-table: Intermediate - Any use case reading a Decision Table >>> from BRMS server >>> >>> Advanced: >>> store-dsl: Advanced - A DSL rule using Type Declaration and Functions >>> helloworld-cep: Advanced: Check for fraudulent credidt card >>> transaction based on amount paid in a time frame. >>> brms-integration: Advanced: Use case to show Drools Commands >>> brms-planner: Advanced: Use case for planning a routing example. >>> >>> BPMS: >>> brms-bpms: Intermediate: Use case for bpms >>> brms-bpms-task: Advanced: Use case for bpms with Human Tasks >>> >>> - >>> -- >>> >>> *Rafael Benevides | Senior Software Engineer* >>> JBoss Developer >>> M: +55-61-9269-6576 >>> >>> Red Hat >>> >>> Better technology. Faster innovation. Powered by community >>> collaboration. >>> See how it works at www.redhat.com >>> >>> LinkedIn Youtube >>> >>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20141210/bf5279b3/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 4815 bytes Desc: not available Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20141210/bf5279b3/attachment-0001.jpe -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 597 bytes Desc: not available Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20141210/bf5279b3/attachment-0002.png -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 616 bytes Desc: not available Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20141210/bf5279b3/attachment-0003.png From paul.robinson at redhat.com Thu Dec 18 06:02:00 2014 From: paul.robinson at redhat.com (Paul Robinson) Date: Thu, 18 Dec 2014 11:02:00 +0000 Subject: [jbossdeveloper] Pruning old data from the DCP Message-ID: All, I?ve put together a proposal for how to remove old data from the DCP: https://issues.jboss.org/browse/DEVELOPER-1164 Essentially, we delete all JBoss Developer content that was not updated during the current production build. Does this seem feasible? Am I missing something? Paul. -- Paul Robinson JBoss Developer Team Lead (www.jboss.org) Free/busy info: https://www.google.com/calendar/embed?src=probinso%40redhat.com&ctz=Europe/London JBoss, a Division of Red Hat Registered in England and Wales under Company Registration No. 03798903 Directors:Michael Cunningham (US), Charles Peters (US), Matt Parson (US), Paul Hickey (Ireland) -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20141218/d35c700e/attachment.html From pmuir at redhat.com Thu Dec 18 08:11:34 2014 From: pmuir at redhat.com (Pete Muir) Date: Thu, 18 Dec 2014 13:11:34 +0000 Subject: [jbossdeveloper] Pruning old data from the DCP In-Reply-To: References: Message-ID: <993C010A-70C4-4000-BF7B-1E8CD3DB785D@redhat.com> I think this proposal looks good, but it would be great to get e.g. Lukas, Vlastimil etc. to comment on it. > On 18 Dec 2014, at 11:02, Paul Robinson wrote: > > All, > > I?ve put together a proposal for how to remove old data from the DCP: https://issues.jboss.org/browse/DEVELOPER-1164 > > Essentially, we delete all JBoss Developer content that was not updated during the current production build. > > Does this seem feasible? Am I missing something? > > Paul. > > -- > Paul Robinson > JBoss Developer Team Lead (www.jboss.org ) > > Free/busy info: https://www.google.com/calendar/embed?src=probinso%40redhat.com&ctz=Europe/London > > JBoss, a Division of Red Hat > Registered in England and Wales under Company Registration No. 03798903 > Directors:Michael Cunningham (US), Charles Peters (US), Matt Parson (US), Paul Hickey (Ireland) > > _______________________________________________ > jbossdeveloper mailing list > jbossdeveloper at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbossdeveloper -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20141218/5acaa13e/attachment.html From paul.robinson at redhat.com Thu Dec 18 08:33:26 2014 From: paul.robinson at redhat.com (Paul Robinson) Date: Thu, 18 Dec 2014 13:33:26 +0000 Subject: [jbossdeveloper] Pruning old data from the DCP In-Reply-To: <993C010A-70C4-4000-BF7B-1E8CD3DB785D@redhat.com> References: <993C010A-70C4-4000-BF7B-1E8CD3DB785D@redhat.com> Message-ID: Absolutely. I had assumed they would be on this list. Paul. > On 18 Dec 2014, at 13:11, Pete Muir wrote: > > I think this proposal looks good, but it would be great to get e.g. Lukas, Vlastimil etc. to comment on it. > >> On 18 Dec 2014, at 11:02, Paul Robinson > wrote: >> >> All, >> >> I?ve put together a proposal for how to remove old data from the DCP: https://issues.jboss.org/browse/DEVELOPER-1164 >> >> Essentially, we delete all JBoss Developer content that was not updated during the current production build. >> >> Does this seem feasible? Am I missing something? >> >> Paul. >> >> -- >> Paul Robinson >> JBoss Developer Team Lead (www.jboss.org ) >> >> Free/busy info: https://www.google.com/calendar/embed?src=probinso%40redhat.com&ctz=Europe/London >> >> JBoss, a Division of Red Hat >> Registered in England and Wales under Company Registration No. 03798903 >> Directors:Michael Cunningham (US), Charles Peters (US), Matt Parson (US), Paul Hickey (Ireland) >> >> _______________________________________________ >> jbossdeveloper mailing list >> jbossdeveloper at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbossdeveloper > Paul. -- Paul Robinson JBoss Developer Team Lead (www.jboss.org) Free/busy info: https://www.google.com/calendar/embed?src=probinso%40redhat.com&ctz=Europe/London JBoss, a Division of Red Hat Registered in England and Wales under Company Registration No. 03798903 Directors:Michael Cunningham (US), Charles Peters (US), Matt Parson (US), Paul Hickey (Ireland) -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20141218/70369da9/attachment.html From paul.robinson at redhat.com Fri Dec 19 10:43:38 2014 From: paul.robinson at redhat.com (Paul Robinson) Date: Fri, 19 Dec 2014 15:43:38 +0000 Subject: [jbossdeveloper] JBoss Developer production builds down over holiday period Message-ID: All, Given that most of us are away for the next two weeks, we thought it best not to rebuild+publish the JBoss Developer production site every 6 hours, like we currently do. Should something go wrong it is unlikely that we would notice, plus I don?t really want to be on-call to fix it ;-) I?ll re-enable on January the 5th. Paul. -- Paul Robinson JBoss Developer Team Lead (www.jboss.org) Free/busy info: https://www.google.com/calendar/embed?src=probinso%40redhat.com&ctz=Europe/London JBoss, a Division of Red Hat Registered in England and Wales under Company Registration No. 03798903 Directors:Michael Cunningham (US), Charles Peters (US), Matt Parson (US), Paul Hickey (Ireland) -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20141219/1a4b003c/attachment-0001.html From benevides at redhat.com Mon Dec 29 09:17:56 2014 From: benevides at redhat.com (Rafael Benevides) Date: Mon, 29 Dec 2014 12:17:56 -0200 Subject: [jbossdeveloper] New year gift! QSTools 1.5.0.Final released Message-ID: <54A16294.5040500@redhat.com> We will begin 2015 with QSTools 1.5.0.Final. Since 1.4.1.Final release we started a long running path to 1.5.0 and here are the changes/new features: - Updated all references from JDF to "JBoss Developer Materials" - Allow ArtifactIdNameChecker to be ignored - Make MavenCentralRepositoryChecker to be ignored as default - JDF-690 - Changed artifactId from maven-qstools-plugin to qstools - JDF-762 - Implemented a new goal: qstools:repositories that allows maintenance in pom.xml files - JDF-786 - QSTools shows detailed information about its version in report - JDF-788 - Check Readme metadata value lenght More details about setup "approved repositories" can see at http://jboss-developer.github.io/maven-qstools-plugin/#setup-jboss-maven-approved-repositories Happy new year! - -- *Rafael Benevides | Senior Software Engineer* JBoss Developer M: +55-61-9269-6576 Red Hat Better technology. Faster innovation. Powered by community collaboration. See how it works at www.redhat.com LinkedIn Youtube -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20141229/8a69a22c/attachment.html -------------- next part -------------- A non-text attachment was scrubbed... Name: {a8aabf3a-4467-4e37-9bc5-48b1d7b494a2}_LATAM_RedHat.jpg Type: image/jpeg Size: 4815 bytes Desc: not available Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20141229/8a69a22c/attachment.jpg -------------- next part -------------- A non-text attachment was scrubbed... Name: linkedin.png Type: image/png Size: 597 bytes Desc: not available Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20141229/8a69a22c/attachment.png -------------- next part -------------- A non-text attachment was scrubbed... Name: youtube.png Type: image/png Size: 616 bytes Desc: not available Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20141229/8a69a22c/attachment-0001.png From benevides at redhat.com Mon Dec 29 12:56:06 2014 From: benevides at redhat.com (Rafael Benevides) Date: Mon, 29 Dec 2014 15:56:06 -0200 Subject: [jbossdeveloper] Update JBoss Developer Materials to Java EE 7 - JAX-RS Client API In-Reply-To: References: <53FB2B23.6090802@redhat.com> <540DF5BC.3020103@redhat.com> <540EF853.9080405@redhat.com> Message-ID: <54A195B6.3020504@redhat.com> Hi all, I'm pleased to announce that we have now the second Java EE 7 feature shown as a JBoss Developer Quickstart: JDF-769 - Create a JAX-RS Client API Quickstart - https://github.com/jboss-developer/jboss-sandbox-quickstarts/tree/master/jaxrs-client I believe that we will need to update the existing Java EE 6 "jax-rs-client" quickstart (EAP and Wildfly) to a name that makes more sense like jaxrs-resteasyclient. Thanks On 9/9/14 10:07, Arun Gupta wrote: > Thanks, now watching! > > On Tue, Sep 9, 2014 at 3:53 PM, Rafael Benevides > wrote: > > I create a ticket for each one of them in case some of you want to > follow the progress. > > - WebSocket server endpoint - https://issues.jboss.org/browse/JDF-765 > - Chunk style batch processing - > https://issues.jboss.org/browse/JDF-766 > - Object-based JSON generation and Stream-based JSON consuming - > https://issues.jboss.org/browse/JDF-767 > - ManagedExecutorService - https://issues.jboss.org/browse/JDF-768 > - JAX-RS Client API - https://issues.jboss.org/browse/JDF-769 > > > Em 9/9/14, 1:29, Arun Gupta escreveu: >> Hi Rafael, >> >> If you are looking for the top 5 features that should be >> highlighted in Java EE 7, then they would be: >> >> - WebSocket server endpoint >> - Chunk style batch processing >> - Object-based JSON generation and Stream-based JSON consuming >> - ManagedExecutorService >> - JAX-RS Client API >> >> There are samples for each one of these at: >> >> https://github.com/javaee-samples/javaee7-samples >> >> I had some basic discussions with Vineet last week on where some >> of these usecases can be incorporated in Ticket Monster. Please >> keep me involved in the design of how TiMo is going to evolve for >> Java EE 7 support. Some of the documents that would be very >> useful from that process are: >> >> - How to migrate an existing Java EE 6 application to EE 7 ? This >> would be very useful to our customers as well. >> - Compare LOC/deployment descriptors between the EE 6 and 7 >> versions. These would make nice graphs. >> - Before/after code fragment for different pieces that were migrated. >> - What proprietary technologies were replaced with >> standards-based when using EE 7 >> >> Cheers >> Arun >> >> On Mon, Sep 8, 2014 at 9:30 PM, Rafael Benevides >> > wrote: >> >> Returning the discussion about JBoss Developer Material for >> Java EE 7, >> >> Arun, >> >> Do you have the list of the 5 features/use cases/quickstarts >> that we want to show, right? Can you share it? >> >> Thanks >> >> Em 8/25/14, 9:25, Rafael Benevides escreveu: >>> Hi All, >>> >>> We're about to start the update process of JBoss Developer >>> Materials to Java EE 7. But before put the hands on it I >>> talked with Pete and we decided that it's better to bring >>> this $subject to discussion with everyone on this list. >>> >>> Ticket Monster already started to be updated >>> https://issues.jboss.org/browse/JDF-754 >>> >>> Actually our jboss-eap-quickstarts have been updated to Java >>> EE 7.0 on https://github.com/wildfly/quickstart. Anyway we >>> still miss some Java EE 7 specific features/use cases on >>> these quickstarts. >>> >>> It seems that Arun Gupta has a list of about 5 features/use >>> cases/quickstarts that we want to show. The idea is to have >>> these Java EE 7 specific quickstarts to be available at >>> www.jboss.org >>> >>> The main point that we should discuss are: >>> >>> - What are those quickstarts/features? >>> - Where will we host those Java EE 7 quickstarts? >>> https://github.com/jboss-developer/jboss-sandbox-quickstarts ? >>> - Paul Robinson, >>> >>> Considering that the jboss-sandbox-quickstarts github >>> structure, do you think that it could have any issues with >>> it? Can we choose just specific quickstarts to be present at >>> www.jboss.org >>> >>> Well, >>> >>> This is just a starting point, so we can discuss about this >>> update process until we have a detailed plan. >>> >>> The Google docs with the plan is available at: >>> https://docs.google.com/document/d/1n0uVG2rhDf1eSp0b4MhggdIxNa3cthnuWaj2OjBpxoY/edit >>> >>> >>> -- >>> >>> *Rafael Benevides | Senior Software Engineer* >>> JBoss Developer >>> M: +55-61-9269-6576 >>> >>> Red Hat >>> >>> Better technology. Faster innovation. Powered by community >>> collaboration. >>> See how it works at www.redhat.com >>> >>> LinkedIn Youtube >>> >>> >>> >>> _______________________________________________ >>> jbossdeveloper mailing list >>> jbossdeveloper at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper >> >> >> _______________________________________________ >> jbossdeveloper mailing list >> jbossdeveloper at lists.jboss.org >> >> https://lists.jboss.org/mailman/listinfo/jbossdeveloper >> >> >> >> >> -- >> http://blog.arungupta.me >> http://twitter.com/arungupta > > > > > -- > http://blog.arungupta.me > http://twitter.com/arungupta -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20141229/85f082f0/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 4815 bytes Desc: not available Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20141229/85f082f0/attachment-0001.jpe -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 597 bytes Desc: not available Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20141229/85f082f0/attachment-0002.png -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 616 bytes Desc: not available Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20141229/85f082f0/attachment-0003.png