From benevides at redhat.com Thu Feb 12 13:49:27 2015 From: benevides at redhat.com (Rafael Benevides) Date: Thu, 12 Feb 2015 13:49:27 -0500 Subject: [jbossdeveloper] Update JBoss Developer Materials to Java EE 7 In-Reply-To: References: <53FB2B23.6090802@redhat.com> <540DF5BC.3020103@redhat.com> <540EF853.9080405@redhat.com> Message-ID: <54DCF5B7.70108@redhat.com> Another Java EE 7 Quickstart just got out of the oven. - https://issues.jboss.org/browse/JDF-768 - Create a ManagedExecutorService Quickstart - https://github.com/jboss-developer/jboss-sandbox-quickstarts/tree/master/managedexecutorservice More 2 to go: - https://issues.jboss.org/browse/JDF-766 - Chunk style batch processing - https://issues.jboss.org/browse/JDF-767 - Object-based JSON generation and Stream-based JSON consuming Feel free to test it and give me any feedback. Thanks On 9/9/14 09: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/20150212/eeebf04b/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/20150212/eeebf04b/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/20150212/eeebf04b/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/20150212/eeebf04b/attachment-0003.png From manderse at redhat.com Thu Feb 12 18:28:55 2015 From: manderse at redhat.com (Max Rydahl Andersen) Date: Fri, 13 Feb 2015 00:28:55 +0100 Subject: [jbossdeveloper] Update JBoss Developer Materials to Java EE 7 In-Reply-To: <54DCF5B7.70108@redhat.com> References: <53FB2B23.6090802@redhat.com> <540DF5BC.3020103@redhat.com> <540EF853.9080405@redhat.com> <54DCF5B7.70108@redhat.com> Message-ID: Cool. > Another Java EE 7 Quickstart just got out of the oven. > > - https://issues.jboss.org/browse/JDF-768 - Create a > ManagedExecutorService Quickstart - > https://github.com/jboss-developer/jboss-sandbox-quickstarts/tree/master/managedexecutorservice Any issues found while testing these in JBoss Tools/Developer Studio ? > More 2 to go: > - https://issues.jboss.org/browse/JDF-766 - Chunk style batch > processing We are adding Batch support which would be interesting to use with work around JDF-766. https://issues.jboss.org/browse/JBIDE-18859 first version will be available in our upcoming Alpha1 (next week) If you find issues using JavaEE 7 please let us know in https://issues.jboss.org/browse/JBDS-2847# or link to it. thanks, /max > - https://issues.jboss.org/browse/JDF-767 - Object-based JSON > generation and Stream-based JSON consuming > > Feel free to test it and give me any feedback. > > Thanks > > On 9/9/14 09: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 > > _______________________________________________ > jbossdeveloper mailing list > jbossdeveloper at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbossdeveloper /max http://about.me/maxandersen From benevides at redhat.com Fri Feb 13 10:38:16 2015 From: benevides at redhat.com (Rafael Benevides) Date: Fri, 13 Feb 2015 10:38:16 -0500 Subject: [jbossdeveloper] Update JBoss Developer Materials to Java EE 7 In-Reply-To: References: <53FB2B23.6090802@redhat.com> <540DF5BC.3020103@redhat.com> <540EF853.9080405@redhat.com> <54DCF5B7.70108@redhat.com> Message-ID: <54DE1A68.1060003@redhat.com> On 2/12/15 18:28, Max Rydahl Andersen wrote: > Cool. > > > >> Another Java EE 7 Quickstart just got out of the oven. >> >> - https://issues.jboss.org/browse/JDF-768 - Create a >> ManagedExecutorService Quickstart - >> https://github.com/jboss-developer/jboss-sandbox-quickstarts/tree/master/managedexecutorservice > > Any issues found while testing these in JBoss Tools/Developer Studio ? I didn't find any. > >> More 2 to go: >> - https://issues.jboss.org/browse/JDF-766 - Chunk style batch processing > > We are adding Batch support which would be interesting to use with > work around JDF-766. > > https://issues.jboss.org/browse/JBIDE-18859 > > first version will be available in our upcoming Alpha1 (next week) > > If you find issues using JavaEE 7 please let us know in > https://issues.jboss.org/browse/JBDS-2847# or link to it. That's for sure, Max! Thanks for letting me know about it. > > thanks, > /max > >> - https://issues.jboss.org/browse/JDF-767 - Object-based JSON >> generation and Stream-based JSON consuming >> >> Feel free to test it and give me any feedback. >> >> Thanks >> >> On 9/9/14 09: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 >> >> _______________________________________________ >> jbossdeveloper mailing list >> jbossdeveloper at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbossdeveloper > > > /max > http://about.me/maxandersen From manderse at redhat.com Mon Feb 16 03:30:48 2015 From: manderse at redhat.com (Max Rydahl Andersen) Date: Mon, 16 Feb 2015 09:30:48 +0100 Subject: [jbossdeveloper] Update JBoss Developer Materials to Java EE 7 In-Reply-To: <54DE1A68.1060003@redhat.com> References: <53FB2B23.6090802@redhat.com> <540DF5BC.3020103@redhat.com> <540EF853.9080405@redhat.com> <54DCF5B7.70108@redhat.com> <54DE1A68.1060003@redhat.com> Message-ID: <18FDCAE9-4B83-48AE-9C6D-4EAB0D9B5413@redhat.com> On 13 Feb 2015, at 16:38, Rafael Benevides wrote: > On 2/12/15 18:28, Max Rydahl Andersen wrote: >> Cool. >> >> >> >>> Another Java EE 7 Quickstart just got out of the oven. >>> >>> - https://issues.jboss.org/browse/JDF-768 - Create a >>> ManagedExecutorService Quickstart - >>> https://github.com/jboss-developer/jboss-sandbox-quickstarts/tree/master/managedexecutorservice >> >> Any issues found while testing these in JBoss Tools/Developer Studio >> ? > I didn't find any. Great, that means we catch the most obvious Java EE 7 ones for JBDS 8 or that we don't even enable the Java EE 7 tooling (i.e. the proper versioned facets) in the examples - I hope its the first one :) Thanks, /max >>> More 2 to go: >>> - https://issues.jboss.org/browse/JDF-766 - Chunk style batch >>> processing >> >> We are adding Batch support which would be interesting to use with >> work around JDF-766. >> >> https://issues.jboss.org/browse/JBIDE-18859 >> >> first version will be available in our upcoming Alpha1 (next week) >> >> If you find issues using JavaEE 7 please let us know in >> https://issues.jboss.org/browse/JBDS-2847# or link to it. > That's for sure, Max! > > Thanks for letting me know about it. >> >> thanks, >> /max >> >>> - https://issues.jboss.org/browse/JDF-767 - Object-based JSON >>> generation and Stream-based JSON consuming >>> >>> Feel free to test it and give me any feedback. >>> >>> Thanks >>> >>> On 9/9/14 09: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 >>> >>> _______________________________________________ >>> jbossdeveloper mailing list >>> jbossdeveloper at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper >> >> >> /max >> http://about.me/maxandersen /max http://about.me/maxandersen From paul.robinson at redhat.com Tue Feb 17 13:37:25 2015 From: paul.robinson at redhat.com (Paul Robinson) Date: Tue, 17 Feb 2015 18:37:25 +0000 Subject: [jbossdeveloper] JBoss Developer builds failing Message-ID: All, Production and pull request builds are currently broken for JBoss Developer. I?m on PTO tomorrow, so it?s unlikely I?ll get this fixed by Thursday. The impact is: 1) Changes to things that we index (e.g connectors, events, videos etc) will not be reflected on the site. 2) If you raise a PR or update an existing one, you won?t get a preview build. The live site is not impacted, other than from the lack of updates. I?ll report back when this is fixed. 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/20150217/e79753cd/attachment-0001.html From vpereira at redhat.com Tue Feb 17 15:18:48 2015 From: vpereira at redhat.com (Vineet Reynolds Pereira) Date: Tue, 17 Feb 2015 15:18:48 -0500 (EST) Subject: [jbossdeveloper] File uploads to filemgmt.jboss.org In-Reply-To: <1242073953.18679426.1424204314210.JavaMail.zimbra@redhat.com> Message-ID: <1011096138.18682132.1424204328511.JavaMail.zimbra@redhat.com> Can anyone else upload files using the jbossdeveloper account: jbossdeveloper at filemgmt.jboss.org ? Vineet From meisele at redhat.com Wed Feb 18 05:55:58 2015 From: meisele at redhat.com (Markus Eisele) Date: Wed, 18 Feb 2015 11:55:58 +0100 Subject: [jbossdeveloper] SEO for Developers Message-ID: <018101d04b69$7b247320$716d5960$@redhat.com> Hi all, Just a heads-up for a free webcast from O'Reilly which might be worth a look. http://www.oreilly.com/pub/e/3324 Cheers, M ___ http://blog.eisele.net http://twitter.com/myfear From meisele at redhat.com Wed Feb 18 05:57:12 2015 From: meisele at redhat.com (Markus Eisele) Date: Wed, 18 Feb 2015 11:57:12 +0100 Subject: [jbossdeveloper] Workaround for Google API Limit? Message-ID: <018301d04b69$a70eaaf0$f52c00d0$@redhat.com> Hi All, I am trying to get the local JBoss.org site setup to contribute some pages. Can't do a rake clean preview because I always run into the Google User Rate Limit. >While processing file >An error occurred: User Rate Limit Exceeded. Please sign up How are you guys locally previewing your changes? Is there a workaround? This is not exactly a particular feature of the site I am interested. Can I just skip this step somehow? Thanks for your help! Cheers, M ___ http://blog.eisele.net http://twitter.com/myfear From meisele at redhat.com Wed Feb 18 03:33:46 2015 From: meisele at redhat.com (Markus Eisele) Date: Wed, 18 Feb 2015 09:33:46 +0100 Subject: [jbossdeveloper] Workaround for Google API Limit? Message-ID: <012701d04b55$9d7c0b40$d87421c0$@redhat.com> Hi All, I am trying to get the local JBoss.org site setup to contribute some pages. Can't do a rake clean preview because I always run into the Google User Rate Limit. >While processing file >An error occurred: User Rate Limit Exceeded. Please sign up How are you guys locally previewing your changes? Is there a workaround? This is not exactly a particular feature of the site I am interested. Can I just skip this step somehow? Thanks for your help! Cheers, M ___ http://blog.eisele.net http://twitter.com/myfear From benevides at redhat.com Wed Feb 18 10:00:05 2015 From: benevides at redhat.com (Rafael Benevides) Date: Wed, 18 Feb 2015 10:00:05 -0500 Subject: [jbossdeveloper] SEO for Developers In-Reply-To: <018101d04b69$7b247320$716d5960$@redhat.com> References: <018101d04b69$7b247320$716d5960$@redhat.com> Message-ID: <54E4A8F5.1010609@redhat.com> Thanks Markus, I enrolled for it. On 2/18/15 05:55, Markus Eisele wrote: > Hi all, > > Just a heads-up for a free webcast from O'Reilly which might be worth a > look. > > http://www.oreilly.com/pub/e/3324 > > Cheers, > M > > ___ > http://blog.eisele.net > http://twitter.com/myfear > > > _______________________________________________ > jbossdeveloper mailing list > jbossdeveloper at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbossdeveloper From benevides at redhat.com Wed Feb 18 10:09:18 2015 From: benevides at redhat.com (Rafael Benevides) Date: Wed, 18 Feb 2015 10:09:18 -0500 Subject: [jbossdeveloper] Workaround for Google API Limit? In-Reply-To: <012701d04b55$9d7c0b40$d87421c0$@redhat.com> References: <012701d04b55$9d7c0b40$d87421c0$@redhat.com> Message-ID: <54E4AB1E.4010004@redhat.com> Markus, Coincidentally I've faced the same issue yesterday. Look what Paul Robinson said me: "Set authenticate_google_books_api: true in the developemtn profile in _config/site.yml. Don?t leave it like that though. The problem is that with that enabled, you?ll be using requests from the quota we use for building staging and production. Because it?s a single account we have with Googel Books api but you only get 1000 reqs per day. DEVELOPER-1203 should fix this. We are currently doing book API requests on every build. so the quota is getting eaten up quickly" Source: http://transcripts.jboss.org/channel/irc.freenode.org/%23jboss-developer/2015/%23jboss-developer.2015-02-16.log.html#t2015-02-16T20:25:25 On 2/18/15 03:33, Markus Eisele wrote: > Hi All, > > I am trying to get the local JBoss.org site setup to contribute some pages. > Can't do a rake clean preview because I always run into the Google User Rate > Limit. > >> While processing file >> An error occurred: User Rate Limit Exceeded. Please sign up > How are you guys locally previewing your changes? Is there a workaround? > This is not exactly a particular feature of the site I am interested. Can I > just skip this step somehow? > > Thanks for your help! > > Cheers, > M > > ___ > http://blog.eisele.net > http://twitter.com/myfear > > > _______________________________________________ > 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/20150218/6c3654c3/attachment.html From pmuir at redhat.com Wed Feb 18 10:13:50 2015 From: pmuir at redhat.com (Pete Muir) Date: Wed, 18 Feb 2015 15:13:50 +0000 Subject: [jbossdeveloper] Workaround for Google API Limit? In-Reply-To: <018301d04b69$a70eaaf0$f52c00d0$@redhat.com> References: <018301d04b69$a70eaaf0$f52c00d0$@redhat.com> Message-ID: <00562549-048E-4DE1-84D7-EADCF2C3A3CC@redhat.com> I?ll let Paul or Jason respond in detail, but in general we do have a problem here with local builds. If you have a gpg key, I can add you to our password vault, and you can use our account to increase the rate limit. Pete > On 18 Feb 2015, at 10:57, Markus Eisele wrote: > > Hi All, > > I am trying to get the local JBoss.org site setup to contribute some pages. > Can't do a rake clean preview because I always run into the Google User > Rate > Limit. > >> While processing file >> An error occurred: User Rate Limit Exceeded. Please sign up > > How are you guys locally previewing your changes? Is there a workaround? > This is not exactly a particular feature of the site I am interested. Can I > just > skip this step somehow? > > Thanks for your help! > > Cheers, > M > > ___ > http://blog.eisele.net > http://twitter.com/myfear > > > _______________________________________________ > jbossdeveloper mailing list > jbossdeveloper at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbossdeveloper From benevides at redhat.com Wed Feb 18 10:19:56 2015 From: benevides at redhat.com (Rafael Benevides) Date: Wed, 18 Feb 2015 10:19:56 -0500 Subject: [jbossdeveloper] Workaround for Google API Limit? In-Reply-To: <00562549-048E-4DE1-84D7-EADCF2C3A3CC@redhat.com> References: <018301d04b69$a70eaaf0$f52c00d0$@redhat.com> <00562549-048E-4DE1-84D7-EADCF2C3A3CC@redhat.com> Message-ID: <54E4AD9C.60100@redhat.com> Markus, That should be preferable. Pete, I'll send you also my gpg key. On 2/18/15 10:13, Pete Muir wrote: > I?ll let Paul or Jason respond in detail, but in general we do have a problem here with local builds. > > If you have a gpg key, I can add you to our password vault, and you can use our account to increase the rate limit. > > Pete > >> On 18 Feb 2015, at 10:57, Markus Eisele wrote: >> >> Hi All, >> >> I am trying to get the local JBoss.org site setup to contribute some pages. >> Can't do a rake clean preview because I always run into the Google User >> Rate >> Limit. >> >>> While processing file >>> An error occurred: User Rate Limit Exceeded. Please sign up >> How are you guys locally previewing your changes? Is there a workaround? >> This is not exactly a particular feature of the site I am interested. Can I >> just >> skip this step somehow? >> >> Thanks for your help! >> >> Cheers, >> M >> >> ___ >> http://blog.eisele.net >> http://twitter.com/myfear >> >> >> _______________________________________________ >> 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 jporter at redhat.com Wed Feb 18 11:27:29 2015 From: jporter at redhat.com (Jason Porter) Date: Wed, 18 Feb 2015 11:27:29 -0500 (EST) Subject: [jbossdeveloper] Workaround for Google API Limit? In-Reply-To: <00562549-048E-4DE1-84D7-EADCF2C3A3CC@redhat.com> References: <018301d04b69$a70eaaf0$f52c00d0$@redhat.com> <00562549-048E-4DE1-84D7-EADCF2C3A3CC@redhat.com> Message-ID: <530393960.15311110.1424276849774.JavaMail.zimbra@redhat.com> ----- Pete Muir wrote: > I?ll let Paul or Jason respond in detail, but in general we do have a problem here with local builds. > > If you have a gpg key, I can add you to our password vault, and you can use our account to increase the rate limit. > > Pete > > > On 18 Feb 2015, at 10:57, Markus Eisele wrote: > > > > Hi All, > > > > I am trying to get the local JBoss.org site setup to contribute some pages. > > Can't do a rake clean preview because I always run into the Google User > > Rate > > Limit. > > > >> While processing file > >> An error occurred: User Rate Limit Exceeded. Please sign up > > > > How are you guys locally previewing your changes? Is there a workaround? > > This is not exactly a particular feature of the site I am interested. Can I > > just > > skip this step somehow? > > > > Thanks for your help! > > > > Cheers, > > M > > > > ___ > > http://blog.eisele.net > > http://twitter.com/myfear > > > > > > _______________________________________________ > > 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 pmuir at redhat.com Wed Feb 18 11:32:26 2015 From: pmuir at redhat.com (Pete Muir) Date: Wed, 18 Feb 2015 16:32:26 +0000 Subject: [jbossdeveloper] Workaround for Google API Limit? In-Reply-To: <530393960.15311110.1424276849774.JavaMail.zimbra@redhat.com> References: <018301d04b69$a70eaaf0$f52c00d0$@redhat.com> <00562549-048E-4DE1-84D7-EADCF2C3A3CC@redhat.com> <530393960.15311110.1424276849774.JavaMail.zimbra@redhat.com> Message-ID: Markus and Rafael are both in the file. Now you can edit https://github.com/jboss-developer/www.jboss.org/blob/master/_config/site.yml#L52 and change that line to true. > On 18 Feb 2015, at 16:27, Jason Porter wrote: > > > ----- Pete Muir wrote: >> I?ll let Paul or Jason respond in detail, but in general we do have a problem here with local builds. >> >> If you have a gpg key, I can add you to our password vault, and you can use our account to increase the rate limit. >> >> Pete >> >>> On 18 Feb 2015, at 10:57, Markus Eisele wrote: >>> >>> Hi All, >>> >>> I am trying to get the local JBoss.org site setup to contribute some pages. >>> Can't do a rake clean preview because I always run into the Google User >>> Rate >>> Limit. >>> >>>> While processing file >>>> An error occurred: User Rate Limit Exceeded. Please sign up >>> >>> How are you guys locally previewing your changes? Is there a workaround? >>> This is not exactly a particular feature of the site I am interested. Can I >>> just >>> skip this step somehow? >>> >>> Thanks for your help! >>> >>> Cheers, >>> M >>> >>> ___ >>> http://blog.eisele.net >>> http://twitter.com/myfear >>> >>> >>> _______________________________________________ >>> 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/20150218/280f18e4/attachment-0001.html From jporter at redhat.com Wed Feb 18 12:29:23 2015 From: jporter at redhat.com (Jason Porter) Date: Wed, 18 Feb 2015 10:29:23 -0700 Subject: [jbossdeveloper] Workaround for Google API Limit? In-Reply-To: <530393960.15311110.1424276849774.JavaMail.zimbra@redhat.com> References: <018301d04b69$a70eaaf0$f52c00d0$@redhat.com> <00562549-048E-4DE1-84D7-EADCF2C3A3CC@redhat.com> <530393960.15311110.1424276849774.JavaMail.zimbra@redhat.com> Message-ID: <20150218172923.GA8310@localhost.localdomain> I doubt you'll have need to do this, but at times I've had to use my Google API key if I was working on things that required a clean book cache. ? 2015-02-18 Wed 09:27, Jason Porter : > > ----- Pete Muir wrote: > > I?ll let Paul or Jason respond in detail, but in general we do have a problem here with local builds. > > > > If you have a gpg key, I can add you to our password vault, and you can use our account to increase the rate limit. > > > > Pete > > > > > On 18 Feb 2015, at 10:57, Markus Eisele wrote: > > > > > > Hi All, > > > > > > I am trying to get the local JBoss.org site setup to contribute some pages. > > > Can't do a rake clean preview because I always run into the Google User > > > Rate > > > Limit. > > > > > >> While processing file > > >> An error occurred: User Rate Limit Exceeded. Please sign up > > > > > > How are you guys locally previewing your changes? Is there a workaround? > > > This is not exactly a particular feature of the site I am interested. Can I > > > just > > > skip this step somehow? > > > > > > Thanks for your help! > > > > > > Cheers, > > > M > > > > > > ___ > > > http://blog.eisele.net > > > http://twitter.com/myfear > > > > > > > > > _______________________________________________ > > > 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 -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: not available Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150218/a099dbb1/attachment.bin From meisele at redhat.com Wed Feb 18 13:34:08 2015 From: meisele at redhat.com (Markus Eisele) Date: Wed, 18 Feb 2015 13:34:08 -0500 (EST) Subject: [jbossdeveloper] Workaround for Google API Limit? In-Reply-To: <20150218172923.GA8310@localhost.localdomain> References: <018301d04b69$a70eaaf0$f52c00d0$@redhat.com> <00562549-048E-4DE1-84D7-EADCF2C3A3CC@redhat.com> <530393960.15311110.1424276849774.JavaMail.zimbra@redhat.com> <20150218172923.GA8310@localhost.localdomain> Message-ID: Paul responded to me directly, he's on pto today.?Looks like there's an issue with the ip address / network you're using the api key from.?Starting the build while not being on VPN solved it.? Still, ?seems to be a good idea to have a lightweight prototyping area where I can just build some slim pages and go ahead with a PR.? @jason: where do I put in my own api key?? Thanks for the help so far,?M _______http://blog.eisele.net?@myfear -------- Original message -------- From: Jason Porter Date: 18/02/2015 18:29 (GMT+01:00) To: Pete Muir , Markus Eisele , jbossdeveloper at lists.jboss.org Subject: Re: [jbossdeveloper] Workaround for Google API Limit? I doubt you'll have need to do this, but at times I've had to use my Google API key if I was working on things that required a clean book cache. ? 2015-02-18 Wed 09:27, Jason Porter : > > ----- Pete Muir wrote: > > I?ll let Paul or Jason respond in detail, but in general we do have a problem here with local builds. > > > > If you have a gpg key, I can add you to our password vault, and you can use our account to increase the rate limit. > > > > Pete > > > > > On 18 Feb 2015, at 10:57, Markus Eisele wrote: > > > > > > Hi All, > > > > > > I am trying to get the local JBoss.org site setup to contribute some pages. > > > Can't do a rake clean preview because I always run into the Google User > > > Rate > > > Limit. > > > > > >> While processing file > > >> An error occurred: User Rate Limit Exceeded. Please sign up > > > > > > How are you guys locally previewing your changes? Is there a workaround? > > > This is not exactly a particular feature of the site I am interested. Can I > > > just > > > skip this step somehow? > > > > > > Thanks for your help! > > > > > > Cheers, > > > M > > > > > > ___ > > > http://blog.eisele.net > > > http://twitter.com/myfear > > > > > > > > > _______________________________________________ > > > 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/20150218/f15acecb/attachment.html -------------- next part -------------- I doubt you'll have need to do this, but at times I've had to use my Google API key if I was working on things that required a clean book cache. ? 2015-02-18 Wed 09:27, Jason Porter : > > ----- Pete Muir wrote: > > I?ll let Paul or Jason respond in detail, but in general we do have a problem here with local builds. > > > > If you have a gpg key, I can add you to our password vault, and you can use our account to increase the rate limit. > > > > Pete > > > > > On 18 Feb 2015, at 10:57, Markus Eisele wrote: > > > > > > Hi All, > > > > > > I am trying to get the local JBoss.org site setup to contribute some pages. > > > Can't do a rake clean preview because I always run into the Google User > > > Rate > > > Limit. > > > > > >> While processing file > > >> An error occurred: User Rate Limit Exceeded. Please sign up > > > > > > How are you guys locally previewing your changes? Is there a workaround? > > > This is not exactly a particular feature of the site I am interested. Can I > > > just > > > skip this step somehow? > > > > > > Thanks for your help! > > > > > > Cheers, > > > M > > > > > > ___ > > > http://blog.eisele.net > > > http://twitter.com/myfear > > > > > > > > > _______________________________________________ > > > 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 jporter at redhat.com Wed Feb 18 16:42:49 2015 From: jporter at redhat.com (Jason Porter) Date: Wed, 18 Feb 2015 14:42:49 -0700 Subject: [jbossdeveloper] Workaround for Google API Limit? In-Reply-To: References: <018301d04b69$a70eaaf0$f52c00d0$@redhat.com> <00562549-048E-4DE1-84D7-EADCF2C3A3CC@redhat.com> <530393960.15311110.1424276849774.JavaMail.zimbra@redhat.com> <20150218172923.GA8310@localhost.localdomain> Message-ID: <20150218214249.GB8310@localhost.localdomain> You'd edit the _config/secrets.yaml.gpg file, but DO NOT COMMIT IT :) ? 2015-02-18 Wed 11:34, Markus Eisele : > > > Paul responded to me directly, he's on pto today.?Looks like there's an issue with the ip address / network you're using the api key from.?Starting the build while not being on VPN solved it.? > Still, ?seems to be a good idea to have a lightweight prototyping area where I can just build some slim pages and go ahead with a PR.? > @jason: where do I put in my own api key?? > Thanks for the help so far,?M > > > _______http://blog.eisele.net?@myfear > > > -------- Original message -------- > From: Jason Porter > Date: 18/02/2015 18:29 (GMT+01:00) > To: Pete Muir , Markus Eisele , jbossdeveloper at lists.jboss.org > Subject: Re: [jbossdeveloper] Workaround for Google API Limit? > > I doubt you'll have need to do this, but at times I've had to use my Google API key if I was working on things that required a clean book cache. > ? 2015-02-18 Wed 09:27, Jason Porter : > > > > ----- Pete Muir wrote: > > > I?ll let Paul or Jason respond in detail, but in general we do have a problem here with local builds. > > > > > > If you have a gpg key, I can add you to our password vault, and you can use our account to increase the rate limit. > > > > > > Pete > > > > > > > On 18 Feb 2015, at 10:57, Markus Eisele wrote: > > > > > > > > Hi All, > > > > > > > > I am trying to get the local JBoss.org site setup to contribute some pages. > > > > Can't do a rake clean preview because I always run into the Google User > > > > Rate > > > > Limit. > > > > > > > >> While processing file > > > >> An error occurred: User Rate Limit Exceeded. Please sign up > > > > > > > > How are you guys locally previewing your changes? Is there a workaround? > > > > This is not exactly a particular feature of the site I am interested. Can I > > > > just > > > > skip this step somehow? > > > > > > > > Thanks for your help! > > > > > > > > Cheers, > > > > M > > > > > > > > ___ > > > > http://blog.eisele.net > > > > http://twitter.com/myfear > > > > > > > > > > > > _______________________________________________ > > > > 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 -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: not available Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150218/77244295/attachment.bin From paul.robinson at redhat.com Thu Feb 19 04:18:43 2015 From: paul.robinson at redhat.com (Paul Robinson) Date: Thu, 19 Feb 2015 09:18:43 +0000 Subject: [jbossdeveloper] JBoss Developer builds failing In-Reply-To: References: Message-ID: <1E9B437F-8EFD-4FEF-9C62-5D180DBCFB50@redhat.com> All, Staging and production builds are working again. I don't yet know what caused the failures on Tuesday but we are going to investigate. In general, it's a high priority to protect the build from failures in third-party services and something that I hope we can improve significantly over the next few months. Paul. > On 17 Feb 2015, at 18:37, Paul Robinson wrote: > > All, > > Production and pull request builds are currently broken for JBoss Developer. I?m on PTO tomorrow, so it?s unlikely I?ll get this fixed by Thursday. > > The impact is: > > 1) Changes to things that we index (e.g connectors, events, videos etc) will not be reflected on the site. > 2) If you raise a PR or update an existing one, you won?t get a preview build. > > The live site is not impacted, other than from the lack of updates. > > I?ll report back when this is fixed. > > 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) > 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/20150219/03277d94/attachment-0001.html From paul.robinson at redhat.com Thu Feb 19 04:38:20 2015 From: paul.robinson at redhat.com (Paul Robinson) Date: Thu, 19 Feb 2015 09:38:20 +0000 Subject: [jbossdeveloper] Workaround for Google API Limit? In-Reply-To: <20150218214249.GB8310@localhost.localdomain> References: <018301d04b69$a70eaaf0$f52c00d0$@redhat.com> <00562549-048E-4DE1-84D7-EADCF2C3A3CC@redhat.com> <530393960.15311110.1424276849774.JavaMail.zimbra@redhat.com> <20150218172923.GA8310@localhost.localdomain> <20150218214249.GB8310@localhost.localdomain> Message-ID: <522D6987-1ACF-455A-BEAD-C933A971DB75@redhat.com> It sounds like you have a workaround now. But here's some more info on the problem... The problem is that Google books API provides a very small quota for both anonymous and authenticated clients. We can't share the same key for development and CI builds as the quota will not be high enough. Therefore the plan was for CI to use the API key and for developers to be anonymous. In theory each developer would have their own quota. However, due to the way Google rate-limits anonymous users, it seems to detect all developers on the Red Hat VPN as being the same user, and thus using a single quota. None of this should be a problem as development and staging builds cache requests to the google books API. So as a developer, you should never need to make a Google Books API call again, after doing a successful build (unless you clear the cache, of course). However, there was an issue with this approach, which I though we fixed on Tuesday. However, I'm still seeing API calls coming from my dev box with a primed cache. I'll report back once we've investigated further. Paul. > On 18 Feb 2015, at 21:42, Jason Porter wrote: > > You'd edit the _config/secrets.yaml.gpg file, but DO NOT COMMIT IT :) > ? 2015-02-18 Wed 11:34, Markus Eisele : >> >> >> Paul responded to me directly, he's on pto today. Looks like there's an issue with the ip address / network you're using the api key from. Starting the build while not being on VPN solved it. >> Still, seems to be a good idea to have a lightweight prototyping area where I can just build some slim pages and go ahead with a PR. >> @jason: where do I put in my own api key? >> Thanks for the help so far, M >> >> >> _______http://blog.eisele.net @myfear >> >> >> -------- Original message -------- >> From: Jason Porter >> Date: 18/02/2015 18:29 (GMT+01:00) >> To: Pete Muir , Markus Eisele , jbossdeveloper at lists.jboss.org >> Subject: Re: [jbossdeveloper] Workaround for Google API Limit? >> >> I doubt you'll have need to do this, but at times I've had to use my Google API key if I was working on things that required a clean book cache. >> ? 2015-02-18 Wed 09:27, Jason Porter : >>> >>> ----- Pete Muir wrote: >>>> I?ll let Paul or Jason respond in detail, but in general we do have a problem here with local builds. >>>> >>>> If you have a gpg key, I can add you to our password vault, and you can use our account to increase the rate limit. >>>> >>>> Pete >>>> >>>>> On 18 Feb 2015, at 10:57, Markus Eisele wrote: >>>>> >>>>> Hi All, >>>>> >>>>> I am trying to get the local JBoss.org site setup to contribute some pages. >>>>> Can't do a rake clean preview because I always run into the Google User >>>>> Rate >>>>> Limit. >>>>> >>>>>> While processing file >>>>>> An error occurred: User Rate Limit Exceeded. Please sign up >>>>> >>>>> How are you guys locally previewing your changes? Is there a workaround? >>>>> This is not exactly a particular feature of the site I am interested. Can I >>>>> just >>>>> skip this step somehow? >>>>> >>>>> Thanks for your help! >>>>> >>>>> Cheers, >>>>> M >>>>> >>>>> ___ >>>>> http://blog.eisele.net >>>>> http://twitter.com/myfear >>>>> >>>>> >>>>> _______________________________________________ >>>>> 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 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/20150219/a7572825/attachment.html From paul.robinson at redhat.com Thu Feb 19 05:33:40 2015 From: paul.robinson at redhat.com (Paul Robinson) Date: Thu, 19 Feb 2015 10:33:40 +0000 Subject: [jbossdeveloper] Fix for: "User Rate Limit Exceeded. Please sign up" when building JBoss Developer Message-ID: All, We've now got a fix for the "User Rate Limit Exceeded. Please sign up" error. The problem was that the build was making calls to the API even with a primed cache. You need to do the following in your dev environment: 0. Update your checkout of the code and ensure you have this commit: https://github.com/jboss-developer/www.jboss.org/commit/d274ae23898214eb76e3792e5b78bfc27dc6e33b 1. Clear the cache using: rm -rf _tmp 2. Build the site as normal using: rake clean preview 3. If you hit the "User Rate Limit Exceeded. Please sign up" error, then try: 3.1 Disconnect from the VPN and rebuild 3.2 Set the following line to true: https://github.com/jboss-developer/www.jboss.org/blob/master/_config/site.yml#L52 and build the site again. Remember to set back to false after the site builds. 4. Once the site builds successfully, you will have a primed cache, and subsequent builds won't make any Google Book API calls. Going forward, you should be able to clear your cache when required. It's unlikely that we'll exceed the API limits now that the build isn't making excessive calls. 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/20150219/a85200f6/attachment.html From paul.robinson at redhat.com Thu Feb 19 12:49:17 2015 From: paul.robinson at redhat.com (Paul Robinson) Date: Thu, 19 Feb 2015 17:49:17 +0000 Subject: [jbossdeveloper] Tracking Intermittent CI Failures Message-ID: <56ED2644-BC5C-46F3-8102-2E67D323B771@redhat.com> All, You may have noticed that intermittent failure of PR and production builds is getting much worse. It's really costing us, so we need to do something about it. I've set up a process for tracking intermittent CI failures. It's the same process we used on the transactions team to significantly improve the stability of the build. Dan will carry out this process and as an output we will get a JIRA issue for every failure along with a tally of how many times each failure is occurring. This will help us target the hotspots. Here's the steps that Dan will follow: https://github.com/jboss-developer/www.jboss.org/blob/master/README.md#tracking-ci-intermittent-failures Dan will update this report weekly by Tues COB: https://docs.google.com/a/redhat.com/spreadsheets/d/1KrHGJ7_eKzSy-3S6ZXqVFPNC1obEBjSSpSR9XkqLlow/edit#gid=0 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/20150219/f4bffe7a/attachment-0001.html From ozizka at redhat.com Thu Feb 19 18:40:25 2015 From: ozizka at redhat.com (Ondrej Zizka) Date: Fri, 20 Feb 2015 00:40:25 +0100 Subject: [jbossdeveloper] Tracking Intermittent CI Failures In-Reply-To: <56ED2644-BC5C-46F3-8102-2E67D323B771@redhat.com> References: <56ED2644-BC5C-46F3-8102-2E67D323B771@redhat.com> Message-ID: <54E67469.4000107@redhat.com> Hi, this might be useful: https://code.google.com/p/junitdiff/ Ondra On 19.2.2015 18:49, Paul Robinson wrote: > All, > > You may have noticed that intermittent failure of PR and production > builds is getting much worse. It's really costing us, so we need to do > something about it. > > I've set up a process for tracking intermittent CI failures. It's the > same process we used on the transactions team to significantly improve > the stability of the build. Dan will carry out this process and as an > output we will get a JIRA issue for every failure along with a tally > of how many times each failure is occurring. This will help us target > the hotspots. > > Here's the steps that Dan will follow: > > https://github.com/jboss-developer/www.jboss.org/blob/master/README.md#tracking-ci-intermittent-failures > > Dan will update this report weekly by Tues COB: > https://docs.google.com/a/redhat.com/spreadsheets/d/1KrHGJ7_eKzSy-3S6ZXqVFPNC1obEBjSSpSR9XkqLlow/edit#gid=0 > > 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/20150220/b23fc52b/attachment.html From paul.robinson at redhat.com Fri Feb 20 04:36:48 2015 From: paul.robinson at redhat.com (Paul Robinson) Date: Fri, 20 Feb 2015 09:36:48 +0000 Subject: [jbossdeveloper] Tracking Intermittent CI Failures In-Reply-To: <54E67469.4000107@redhat.com> References: <56ED2644-BC5C-46F3-8102-2E67D323B771@redhat.com> <54E67469.4000107@redhat.com> Message-ID: Thanks Ondra, I don't think it will be of use to us, as we are not using JUnit. The issues we get are during the execution of a Rake build :-( However, it might be of use to the Transactions team as I know they use JUnit and the intermittent failures they experience are test failures. I'll pass it on. Paul. > On 19 Feb 2015, at 23:40, Ondrej Zizka wrote: > > Hi, > > this might be useful: > https://code.google.com/p/junitdiff/ > > Ondra > > > On 19.2.2015 18:49, Paul Robinson wrote: >> All, >> >> You may have noticed that intermittent failure of PR and production builds is getting much worse. It's really costing us, so we need to do something about it. >> >> I've set up a process for tracking intermittent CI failures. It's the same process we used on the transactions team to significantly improve the stability of the build. Dan will carry out this process and as an output we will get a JIRA issue for every failure along with a tally of how many times each failure is occurring. This will help us target the hotspots. >> >> Here's the steps that Dan will follow: >> >> https://github.com/jboss-developer/www.jboss.org/blob/master/README.md#tracking-ci-intermittent-failures >> >> Dan will update this report weekly by Tues COB: https://docs.google.com/a/redhat.com/spreadsheets/d/1KrHGJ7_eKzSy-3S6ZXqVFPNC1obEBjSSpSR9XkqLlow/edit#gid=0 >> >> 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/20150220/065818cf/attachment.html From benevides at redhat.com Fri Feb 27 09:46:29 2015 From: benevides at redhat.com (Rafael Benevides) Date: Fri, 27 Feb 2015 09:46:29 -0500 Subject: [jbossdeveloper] Ticket Monster session replication Message-ID: <54F08345.2030506@redhat.com> Hi all, I'm preparing a presentation demo using Ticket Monster and I'd like to demonstrate a failover cluster. Is TM capable of session replication ? I mean: Did someone already tested if enabling it through element would be sufficient for TM without any other source code modification ? -- *Rafael Benevides | Senior Software Engineer* JBoss Developer M: +1-919-592-6255 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/20150227/0b30e203/attachment-0001.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/20150227/0b30e203/attachment-0001.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/20150227/0b30e203/attachment-0002.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/20150227/0b30e203/attachment-0003.png From vpereira at redhat.com Fri Feb 27 10:54:22 2015 From: vpereira at redhat.com (Vineet Reynolds Pereira) Date: Fri, 27 Feb 2015 10:54:22 -0500 (EST) Subject: [jbossdeveloper] Ticket Monster session replication In-Reply-To: <54F08345.2030506@redhat.com> References: <54F08345.2030506@redhat.com> Message-ID: <1678747618.27723382.1425052462169.JavaMail.zimbra@redhat.com> Hi Rafael, I believe it should be, when you use MySQL or PostgreSQL as the database. Avoid H2 (the default DB) since each DB instance would not be shared across EAP instances. I'll verify whether the proposed config works flawlessly over the weekend, as I am working on demonstrating scaling of TicketMonster using a Kubernetes+WildFly+(MySQL/Postgres)+HAProxy. Vineet ----- Original Message ----- > From: "Rafael Benevides" > To: "Vineet Reynolds Pereira" , jbossdeveloper at lists.jboss.org > Sent: Friday, February 27, 2015 8:16:29 PM > Subject: Ticket Monster session replication > > Hi all, > > I'm preparing a presentation demo using Ticket Monster and I'd like to > demonstrate a failover cluster. > > Is TM capable of session replication ? I mean: Did someone already > tested if enabling it through element would be > sufficient for TM without any other source code modification ? > > -- > > *Rafael Benevides | Senior Software Engineer* > JBoss Developer > M: +1-919-592-6255 > > Red Hat > > Better technology. Faster innovation. Powered by community collaboration. > See how it works at www.redhat.com > > LinkedIn Youtube > > From benevides at redhat.com Fri Feb 27 10:56:59 2015 From: benevides at redhat.com (Rafael Benevides) Date: Fri, 27 Feb 2015 10:56:59 -0500 Subject: [jbossdeveloper] Ticket Monster session replication In-Reply-To: <1678747618.27723382.1425052462169.JavaMail.zimbra@redhat.com> References: <54F08345.2030506@redhat.com> <1678747618.27723382.1425052462169.JavaMail.zimbra@redhat.com> Message-ID: <54F093CB.3000209@redhat.com> " I am working on demonstrating scaling of TicketMonster using a Kubernetes+WildFly+(MySQL/Postgres)+HAProxy" Me too :) Let's chat about this when you have a chance. On 2/27/15 10:54, Vineet Reynolds Pereira wrote: > Hi Rafael, > > I believe it should be, when you use MySQL or PostgreSQL as the database. Avoid H2 (the default DB) since each DB instance would not be shared across EAP instances. I'll verify whether the proposed config works flawlessly over the weekend, as I am working on demonstrating scaling of TicketMonster using a Kubernetes+WildFly+(MySQL/Postgres)+HAProxy. > > Vineet > > > ----- Original Message ----- >> From: "Rafael Benevides" >> To: "Vineet Reynolds Pereira" , jbossdeveloper at lists.jboss.org >> Sent: Friday, February 27, 2015 8:16:29 PM >> Subject: Ticket Monster session replication >> >> Hi all, >> >> I'm preparing a presentation demo using Ticket Monster and I'd like to >> demonstrate a failover cluster. >> >> Is TM capable of session replication ? I mean: Did someone already >> tested if enabling it through element would be >> sufficient for TM without any other source code modification ? >> >> -- >> >> *Rafael Benevides | Senior Software Engineer* >> JBoss Developer >> M: +1-919-592-6255 >> >> Red Hat >> >> Better technology. Faster innovation. Powered by community collaboration. >> See how it works at www.redhat.com >> >> LinkedIn Youtube >> >>