Re: [jdf-dev] Seam 2 -> Java EE 6 migration
by Pete Muir
How about Friday next week? Hanelli?
On 5 Dec 2012, at 18:08, Cody Lerum wrote:
> Sure just send out some times and I can help out.
>
> I can make 7AM US-Mountain until 11PM
>
>
> On Wed, Dec 5, 2012 at 11:05 AM, Pete Muir <pmuir(a)bleepbleep.org.uk> wrote:
> Not sure if Cody and Hanelli are here.
>
> Maybe we could do a google hangout next week to start some brainstorming, both around ideas and how to get it done...
>
> On 5 Dec 2012, at 18:01, Jason Porter wrote:
>
> > Cody and probably Hanneli have some more information. The trick I think is getting them to write it.
> >
> > ----- Original Message -----
> >> From: "Pete Muir" <pmuir(a)bleepbleep.org.uk>
> >> To: "jdf-dev" <jdf-dev(a)lists.jboss.org>
> >> Sent: Wednesday, December 5, 2012 9:05:02 AM
> >> Subject: [jdf-dev] Seam 2 -> Java EE 6 migration
> >>
> >> Guys
> >>
> >> we need to get more content in around this topic. Anybody got some
> >> interesting ideas around this? How to present it, how to collect it
> >> etc.?
> >>
> >> Pete
> >> _______________________________________________
> >> jdf-dev mailing list
> >> jdf-dev(a)lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/jdf-dev
> >>
> > _______________________________________________
> > jdf-dev mailing list
> > jdf-dev(a)lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/jdf-dev
>
>
11 years, 11 months
URGENT Check and Update to archetypes needed
by Pete Muir
RichFaces/Aerogear teams,
Due to a mixup [1] the archetypes didn't get properly checked for EAP 6.0.1. As a result they are still using versions of the BOM which aren't in the EAP 6.0.1 Maven repo.
Please can you update src/main/resources/META-INF/maven/archetype-resources.xml and make sure that the jboss-bom-enterprise-version property is set to the 1.0.2.Final-redhat-1:
<requiredProperty key="jboss-bom-enterprise-version">
<defaultValue>1.0.2.Final-redhat-1</defaultValue>
</requiredProperty>
We'll then need you to do a release, and send a pull to stacks.yaml with the new version of your archetype.
Thanks!
Pete
[1] The EAP team weren't checking the archetypes were working, it only got picked up by JBDS QE. We've asked the EAP team to start testing the archetypes as part of the acceptance tests, and notify the JDF team (me and Rafael) of any issues, so that we can go ahead and fix the problems.
11 years, 11 months
Re: [jdf-dev] URGENT Check and Update to archetypes needed
by Jay Balunas
Pete - thanks for letting us know about the issue. Given the holidays we're not going to get to this until after the new years.
On Dec 24, 2012, at 3:13 PM, Douglas Campos <dcampos(a)redhat.com> wrote:
> no, I'm trying to understand how urgent is this (new guy at red hat ;))
>
> -- qmx (mobile)
>
> On 24/12/2012, at 17:42, Pete Muir <pmuir(a)bleepbleep.org.uk> wrote:
>
>> Up to you. We can push incremental changes out, so you arent blocking other peoples fixes.
>>
>> On 24 Dec 2012 17:35, "Douglas Campos" <dcampos(a)redhat.com> wrote:
>>> can this wait until the end of the holiday break?
>>>
>>> -- qmx (mobile)
>>>
>>> On 24/12/2012, at 12:33, Pete Muir <pmuir(a)bleepbleep.org.uk> wrote:
>>>
>>> > RichFaces/Aerogear teams,
>>> >
>>> > Due to a mixup [1] the archetypes didn't get properly checked for EAP 6.0.1. As a result they are still using versions of the BOM which aren't in the EAP 6.0.1 Maven repo.
>>> >
>>> > Please can you update src/main/resources/META-INF/maven/archetype-resources.xml and make sure that the jboss-bom-enterprise-version property is set to the 1.0.2.Final-redhat-1:
>>> >
>>> > <requiredProperty key="jboss-bom-enterprise-version">
>>> > <defaultValue>1.0.2.Final-redhat-1</defaultValue>
>>> > </requiredProperty>
>>> >
>>> > We'll then need you to do a release, and send a pull to stacks.yaml with the new version of your archetype.
>>> >
>>> > Thanks!
>>> >
>>> > Pete
>>> >
>>> > [1] The EAP team weren't checking the archetypes were working, it only got picked up by JBDS QE. We've asked the EAP team to start testing the archetypes as part of the acceptance tests, and notify the JDF team (me and Rafael) of any issues, so that we can go ahead and fix the problems.
11 years, 12 months
Re: [jdf-dev] URGENT Check and Update to archetypes needed
by Pete Muir
Up to you. We can push incremental changes out, so you arent blocking other
peoples fixes.
On 24 Dec 2012 17:35, "Douglas Campos" <dcampos(a)redhat.com> wrote:
> can this wait until the end of the holiday break?
>
> -- qmx (mobile)
>
> On 24/12/2012, at 12:33, Pete Muir <pmuir(a)bleepbleep.org.uk> wrote:
>
> > RichFaces/Aerogear teams,
> >
> > Due to a mixup [1] the archetypes didn't get properly checked for EAP
> 6.0.1. As a result they are still using versions of the BOM which aren't in
> the EAP 6.0.1 Maven repo.
> >
> > Please can you update
> src/main/resources/META-INF/maven/archetype-resources.xml and make sure
> that the jboss-bom-enterprise-version property is set to the
> 1.0.2.Final-redhat-1:
> >
> > <requiredProperty key="jboss-bom-enterprise-version">
> > <defaultValue>1.0.2.Final-redhat-1</defaultValue>
> > </requiredProperty>
> >
> > We'll then need you to do a release, and send a pull to stacks.yaml with
> the new version of your archetype.
> >
> > Thanks!
> >
> > Pete
> >
> > [1] The EAP team weren't checking the archetypes were working, it only
> got picked up by JBDS QE. We've asked the EAP team to start testing the
> archetypes as part of the acceptance tests, and notify the JDF team (me and
> Rafael) of any issues, so that we can go ahead and fix the problems.
>
11 years, 12 months
Looking for volunteers for new quickstarts
by Sande Gilda
Hi everyone,
As you know, the quickstarts have received a lot of attention and seem
to be a big hit. If you thought you missed your opportunity to help out,
you are wrong. We have a growing list of new quickstarts that would be
extremely useful to our customers. If you choose to contribute, not only
do you get the satisfaction of knowing you are making JBoss developers'
lives easier, but you get celebrity status as author of the quickstart!
The following list of JIRAs describe the quickstarts we need. If you see
one that looks interesting, please feel free to grab the JIRA. If you
don't have access, send me an email and I will grab it for you.
JDF-37 Provide a JAAS quickstart
JDF-46 Clustered JMS quickstart
JDF-131 Provide a MBean quickstart
JDF-137 Add OSGi war quickstart
JDF-138 Create a quickstart demonstrating a custom CDI context and scope
JDF-140 Create a quickstart demonstrating CDI alternatives
JDF-141 Create a quickstart demonstrating CDI Stereotypes
JDF-142 Create a quickstart demonstrating CDI Decorators
JDF-143 Create a quickstart demonstrating CDI Interceptors
JDF-144 Create a quick start using the deltaspike property configuration
JDF-145 Create a quickstart using deltaspike's exception handling
JDF-146 Add Deltaspike version of kitchensink that shows how to use
@Transactional
JDF-147 Upgrade i8ln quickstarts to use DeltaSpike i8ln
JDF-148 Add a quickstart showing how to create new beans using DS
utilities
JDF-149 Add a quickstart that shows how to use DeltaSpike
BeanManagerProvider to access CDI in a EntityListener
JDF-150 Add a quickstart that shows how to use @TransactionScoped
If none in the list above appeals to you, we also have an existing
'helloword-mdb' example that currently demonstrates JMS Queues. It would
be great to enhance it to demonstrate JMS Topics as well.
Information about the current quickstarts can be found here:
http://site-jdf.rhcloud.com/quickstarts/get-started/
The source code for the current quickstarts is here:
https://github.com/jboss-jdf/jboss-as-quickstart/
Information about contributing a quickstart is here:
http://site-jdf.rhcloud.com/about/contributing/
Please let me know if you need any more information or have any questions.
Thanks,
Sande
12 years
Fwd: JUDCOn Brazil 2013 Call4papers open
by Jason Porter
Do we have some presentations we'd like to submit?
----- Forwarded Message -----
From: "Ricardo Martinelli de Oliveira" <rmartine(a)redhat.com>
To: "thecore(a)redhat.com The Core" <thecore(a)redhat.com>
Sent: Monday, December 17, 2012 1:58:41 PM
Subject: JUDCOn Brazil 2013 Call4papers open
Hello all,
JUDCon is coming to Brazil! The event will be in April 19-20 and I'm honoured to announce that the call 4 papers is now open.
Portuguese version: http://www.jboss.org/pt_BR/events/JUDCon/2013/brazil
English version: http://www.jboss.org/events/JUDCon/2013/brazil
Regards,
Ricardo Martinelli de Oliveira I JBoss Senior Technical Support Engineer
Red Hat Brazil
+55 11 35296125
Supporting success. Exceeding expectations.
Red Hat Customer Portal
Red Hat Support Twitter
Red Hat Support Facebook
Red Hat Support Google+
Red Hat LinkedIn
12 years
Creating a track for framework integrators
by Pete Muir
Hi all
We need to create a track (tutorial, like TicketMonster, or the one for the quickstarts) for framework and library writers, who want to integrate with CDI and Java EE. The quickstarts we're building for CDI and DeltaSpike will form the backbone of this, but we need to build the guide around it.
Anyone want to take this on?
12 years
[JBoss JIRA] (JDF-172) Update TicketMonster tutorial to use JBDS for OpenShift deployment
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JDF-172?page=com.atlassian.jira.plugin.sy... ]
Andre Dietisheim edited comment on JDF-172 at 12/17/12 5:18 AM:
----------------------------------------------------------------
Btw. there's the "skip_maven_build" to prevent source from being built. IMHO that's the better option than to remove the pom.
We actually exactly do the same as you: The openshift git repo (with the starter app) is imported into 1 workspace project, the ticket-monster repo is in another workspace project. Drag and dropping the ticket-monster project to the OpenShift project does what you achieve by building the war and copying it into the OpenShift clone. We add the "skip_maven_build" to achieve what you do by killing the pom.
I agree on saying that we could offer some UI to point out, facilitate and offer a better user experience. Nevertheless I'm not convinced that this is all solved with checkboxes. I'll have a chat with Max, collecting ideas after my PTO.
was (Author: adietish):
Btw. there's the "skip_maven_build" to prevent source from being built. IMHO that's the better option than to remove the pom.
We actually exactly the same as you: The openshift git repo (with the starter app) is imported into 1 workspace project, the ticket-monster repo is in a different workspace project. Drag and dropping the ticket-monster project to the OpenShift project does what you achieve by building the war and copying it into the OpenShift clone. We add the "skip_maven_build" to achieve what you do by killing the pom.
I agree on saying that we could offer some UI to point out, facilitate and offer a better user experience. Nevertheless I'm not convinced that this is all solved with checkboxes. I'll have a chat with Max, collecting ideas after my PTO.
> Update TicketMonster tutorial to use JBDS for OpenShift deployment
> ------------------------------------------------------------------
>
> Key: JDF-172
> URL: https://issues.jboss.org/browse/JDF-172
> Project: JBoss Developer Framework
> Issue Type: Task
> Components: ticket-monster
> Affects Versions: 2.0.0.Final
> Reporter: Stefan Bunciak
> Assignee: Marius Bogoevici
> Attachments: ticket-monster.png
>
>
> We should guide users to use JBDS for OpenShift deployment, but first we need to find out the proper/working way:
> * Source deployment needs medium sized gear on OpenShift (which normal user don't have, but should work either way): JBIDE-13295
> * Binary deployment works, but there's no way to deploy it to application root: JBIDE-13296
> Once above jira issues are resolved, the TicketMonster tutorial should be updated.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (JDF-172) Update TicketMonster tutorial to use JBDS for OpenShift deployment
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JDF-172?page=com.atlassian.jira.plugin.sy... ]
Andre Dietisheim commented on JDF-172:
--------------------------------------
Btw. there's the "skip_maven_build" to prevent source from being built. IMHO that's the better option than to remove the pom.
We actually exactly the same as you: The openshift git repo (with the starter app) is imported into 1 workspace project, the ticket-monster repo is in a different workspace project. Drag and dropping the ticket-monster project to the OpenShift project does what you achieve by building the war and copying it into the OpenShift clone. We add the "skip_maven_build" to achieve what you do by killing the pom.
I agree on saying that we could offer some UI to point out, facilitate and offer a better user experience. Nevertheless I'm not convinced that this is all solved with checkboxes. I'll have a chat with Max, collecting ideas after my PTO.
> Update TicketMonster tutorial to use JBDS for OpenShift deployment
> ------------------------------------------------------------------
>
> Key: JDF-172
> URL: https://issues.jboss.org/browse/JDF-172
> Project: JBoss Developer Framework
> Issue Type: Task
> Components: ticket-monster
> Affects Versions: 2.0.0.Final
> Reporter: Stefan Bunciak
> Assignee: Marius Bogoevici
> Attachments: ticket-monster.png
>
>
> We should guide users to use JBDS for OpenShift deployment, but first we need to find out the proper/working way:
> * Source deployment needs medium sized gear on OpenShift (which normal user don't have, but should work either way): JBIDE-13295
> * Binary deployment works, but there's no way to deploy it to application root: JBIDE-13296
> Once above jira issues are resolved, the TicketMonster tutorial should be updated.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
