JBoss Stacks Echosystem going Final
by Rafael Benevides
Hi all,
I want a feedback from JBoss Stacks Echosystem (stacks.yaml format /
stacks-client / jdf-forge-plugin).
We are on 1.0.0.CR2 format to stacks.yaml and I want to know if do you
have any other issue on this? So I can move all of them to .Final and we
can release JDF 2.0.0.Final next week.
Thanks
--
Rafael Benevides | Senior Software Engineer
Red Hat Brazil
+55-61-9269-6576
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
12 years, 2 months
REST QS - @JsonIgnore ?
by Ondřej Žižka
Hi Pete,
this is in the JAX-RS QS:
@XmlTransient
// JSON: uncomment to include json support (note json is not part of
the JAX-RS standard)
//@JsonIgnore
public User getOwner() {
return owner;
}
I didn't find JsonIgnore anywhere else than Jackson. It's not in
Quickstart's deps.
I've checked public API (wow, it's actually useful! :) and it's not
there.
So - does @JsonIgnore even belong there?
Thanks,
Ondra
12 years, 3 months
Re: [jdf-dev] Beta EAP6, JBDS5, WFK2 Training/Demo
by Pete Muir
Ok, great!
Rafael, can you do a .Final release of the archetypes?
Fred, can you file an issue in JDF for the imports?
On 2 Oct 2012, at 09:44, Fred Bricon wrote:
> Sorry, I totally missed that thread. We've been toying with the CR1 archetypes in Central for a while now, they do the job.
> Although you might want to organize imports on the java classes, in order to avoid some warning in Eclipse (unused imports).
>
> Try creating the java ee projects in JBT/JBDS to see these warnings.
>
> Le mardi 2 octobre 2012 18:31:05, Max Rydahl Andersen a écrit :
>> I must have missed something - .CR1 of what ?
>>
>> Sorry if I'm dense but which archetypes ? we got about 6 currently and they all come from different gitrepos/locations/mailinglists so
>> could you point out (github/maven/something like) what you want tested ?
>>
>> /max
>>
>>> No, I never got an ack from the JBDS team that the .CR1 was good to go.
>>>
>>> On 1 Oct 2012, at 22:02, Vimal Kansal wrote:
>>>
>>>> Hi Pete,
>>>>
>>>> I still see only CR1. Did you update it to Final?
>>>>
>>>> Thx
>>>>
>>>> Vimal
>>>>
>>>> On 25/07/2012 10:00 PM, Pete Muir wrote:
>>>>> Fred, do you want to do any JBDS testing? Or should I release .Final?
>>>>>
>>>>> On 25 Jul 2012, at 12:56, Vimal Kansal wrote:
>>>>>
>>>>>> Hi Pete,
>>>>>>
>>>>>> Just tested both the archetypes and they work perfectly.
>>>>>>
>>>>>> Thanks a lot
>>>>>>
>>>>>> Vimal
>>>>>>
>>>>>> On 25/07/2012 2:01 AM, Pete Muir wrote:
>>>>>>> Hi Vimal
>>>>>>>
>>>>>>> I've just released 7.1.1.CR1 of the archetypes (will sync to central in the next 24hrs). I tested them against the released EAP 6 Maven repo, and it looked like it was working.
>>>>>>>
>>>>>>> If you can double check, I can release the .Final and ask Fred to update JBDS.
>>>>>>>
>>>>>>> On 10 Jul 2012, at 00:16, Vimal Kansal wrote:
>>>>>>>
>>>>>>>> Yup, I used from maven central, but when I enable the EAP6 flag, I get the exceptions which I mentioned below.
>>>>>>>>
>>>>>>>> On 10/07/2012 9:45 AM, Pete Muir wrote:
>>>>>>>>> This should be delivered via Maven central. I will check on the status, it looks like a release may not have been promoted.
>>>>>>>>>
>>>>>>>>> On 9 Jul 2012, at 22:35, Vimal Kansal wrote:
>>>>>>>>>
>>>>>>>>>> Hi Pete,
>>>>>>>>>>
>>>>>>>>>> Can you confirm whether the archetypes to generate "blank" web app and ear app were productized or not?
>>>>>>>>>>
>>>>>>>>>> Thx
>>>>>>>>>>
>>>>>>>>>> Vimal
>>>>>>>>>>
>>>>>>>>>> On 24/06/2012 3:58 AM, Vimal Kansal wrote:
>>>>>>>>>>> Hi Guys,
>>>>>>>>>>>
>>>>>>>>>>> Any update on this. I am using GA of EAP 6, EAP 6 repository and JBDS 5.0, but still the same behaviour ?
>>>>>>>>>>>
>>>>>>>>>>> Thx
>>>>>>>>>>>
>>>>>>>>>>> Vimal
>>>>>>>>>>>
>>>>>>>>>>> On 11/04/2012 9:31 PM, Pete Muir wrote:
>>>>>>>>>>>> Ah yes, this is to be expected. We are still working out how to productize those top two artifacts… Shelly or Paul know more.
>>>>>>>>>>>>
>>>>>>>>>>>> On 11 Apr 2012, at 02:49, Vimal Kansal wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Hi Pete,
>>>>>>>>>>>>>
>>>>>>>>>>>>> Sorry for being late. I set up the whole thing again i.e EAP 6.0 Beta1, EAP 6.0 Maven Repo, JBDS 5.0 Beta 1 and used "New --> Maven -> Project" to use the new archetype. In the generated project, pom throws up following errors (with enterprise option set to true) :
>>>>>>>>>>>>>
>>>>>>>>>>>>> Project build error: Non-resolvable import POM: Failure to find org.jboss.bom:jboss-javaee-6.0-with-hibernate:pom:1.0.0.M6-redhat-1 in file:///home/vimal/jboss-eap-6.0.0.ER3-maven-repository was cached in the local repository, resolution will not be reattempted until the update interval of jboss-eap has elapsed or updates are forced
>>>>>>>>>>>>>
>>>>>>>>>>>>> Project build error: Non-resolvable import POM: Failure to find org.jboss.bom:jboss-javaee-6.0-with-tools:pom:1.0.0.M6-redhat-1 in file:///home/vimal/jboss-eap-6.0.0.ER3-maven-repository was cached in the local repository, resolution will not be reattempted until the update interval of jboss-eap has elapsed or updates are forced
>>>>>>>>>>>>>
>>>>>>>>>>>>> Project build error: 'dependencies.dependency.version' for org.jboss.spec.javax.annotation:jboss-annotations-api_1.1_spec:jar is missing.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Project build error: 'dependencies.dependency.version' for javax.enterprise:cdi-api:jar is missing.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Project build error: 'dependencies.dependency.version' for org.jboss.arquillian.protocol:arquillian-protocol-servlet:jar is missing.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Project build error: 'dependencies.dependency.version' for org.jboss.arquillian.junit:arquillian-junit-container:jar is missing.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Project build error: 'dependencies.dependency.version' for junit:junit:jar is missing.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Project build error: 'dependencies.dependency.version' for org.hibernate:hibernate-validator-annotation-processor:jar is missing.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Project build error: 'dependencies.dependency.version' for org.hibernate:hibernate-jpamodelgen:jar is missing.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Project build error: 'dependencies.dependency.version' for org.jboss.spec.javax.faces:jboss-jsf-api_2.0_spec:jar is missing.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Project build error: 'dependencies.dependency.version' for org.hibernate:hibernate-validator:jar is missing.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Project build error: 'dependencies.dependency.version' for org.hibernate.javax.persistence:hibernate-jpa-2.0-api:jar is missing.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Project build error: 'dependencies.dependency.version' for org.jboss.spec.javax.ws.rs:jboss-jaxrs-api_1.1_spec:jar is missing.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thx
>>>>>>>>>>>>>
>>>>>>>>>>>>> Vimal
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On 5/04/2012 10:02 PM, Pete Muir wrote:
>>>>>>>>>>>>>> Many thanks!
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On 4 Apr 2012, at 21:37, Vimal Kansal wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Hi Pete,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I am on customer site in Sydney and today I fly back to Melbourne. I will do a test again tomorrow and will get back to you.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thx
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Vimal
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On 5/04/2012 2:31 AM, Pete Muir wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Any details vimal?
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On 2 Apr 2012, at 13:57, Vimal Kansal wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Hi Pete,
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> The archetypes are working but when I set enterprise = true, they don't.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Thx
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Vimal
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On 2/04/2012 6:45 PM, Pete Muir wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Vimal, do you have time to test them quickly, before we push them live to JBoss Central?
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On 31 Mar 2012, at 01:19, Fred Bricon wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Pete, if they need to be included in JBoss Central, please open a JIRA with the GAV you want to see updated
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Le 30/03/2012 15:29, Pete Muir a écrit :
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Hi guys, 7.1.1.Beta1 of the archetypes are released. This includes the rebrand.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Please test for me.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Jay needs to merge some updates from Aerogear and then we can go Final. Hopefully this is it for EAP 6 now.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> On 20 Mar 2012, at 09:05, Vimal Kansal wrote:
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> So, I checked the repository downloaded from customer support portal and it does not have the archetypes, and hence it goes to maven central. When these archetypes were being developed, a requirement was raised that we needed to have archetypes that could generate blank web application and a blank ear application. As a result of which, following archetypes were developed :
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> • org.jboss.spec.archetypes:boss-javaee6-webapp-archetype-blank
>>>>>>>>>>>>>>>>>>>>> • org.jboss.spec.archetypes:jboss-javaee6-webapp-ear-archetype-blank
>>>>>>>>>>>>>>>>>>>>> Subsequently, on my request, these were renamed as :
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> • org.jboss.spec.archetypes:boss-javaee6-webapp-blank-archetype
>>>>>>>>>>>>>>>>>>>>> • org.jboss.spec.archetypes:jboss-javaee6-webapp-ear-blank-archetype
>>>>>>>>>>>>>>>>>>>>> Please note the position of "blank" - I made this recommendation just to bring a standardisation to archetype naming convention i.e "archetype" be the last word in the name. This recommendation was accepted by Pete and subsequently all bug fixes and features were added to the second set of archetypes. These archetypes are hosted at :
>>>>>>>>>>>>>>>>>>>>> https://repository.jboss.org/nexus/content/groups/public/org/jboss/spec/a...
>>>>>>>>>>>>>>>>>>>>> (Actually this location continues to have both sets) The second set is not available in maven central, which is where JBDS 5.0/maven are fetching . Please note that the first set of archetypes above do not generate the correct project structure. So here is what I am not sure :
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> • Why are we not packaging the maven archetypes with the the maven repository that we download from Customer Support Portal?
>>>>>>>>>>>>>>>>>>>>> • Can we resolve the correct archetypes for blank project generation.
>>>>>>>>>>>>>>>>>>>>> Thx
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Vimal
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> On 20/03/2012 8:50 PM, Vimal Kansal wrote:
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> And here is my settings.xml file(please see attached)
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> On 20/03/2012 8:46 PM, Vimal Kansal wrote:
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Hi Burr,
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> I am kind of confused , before I ask my question, here is how I have setup the EAP 6 and JBDS 5.0 and maven (So far my dev environment had involved working with AS 7.1.1, eclipse 3.7 + JBoss Tools 3.3) :
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> • I deployed my EAP 6 by unzipping it.
>>>>>>>>>>>>>>>>>>>>>>> • I also deployed JBDS 5.0
>>>>>>>>>>>>>>>>>>>>>>> • I added EAP 6.0 to JBDS 5.0
>>>>>>>>>>>>>>>>>>>>>>> • A installed maven separately i.e separate to JBDS .
>>>>>>>>>>>>>>>>>>>>>>> • Withing my JBDS, I updated maven plugin to refer to my externally installed maven :
>>>>>>>>>>>>>>>>>>>>>>> • /home/vimal/Apps/apache-maven-3.0.4/conf/settings.xml
>>>>>>>>>>>>>>>>>>>>>>> • I updated my settings file to refer to maven repository that I downloaded from the Customer Support Portal
>>>>>>>>>>>>>>>>>>>>>>> • Now withing JBDS, from JBoss Central when I create a web app, it still goes to get the archetypes etc from maven central repository.
>>>>>>>>>>>>>>>>>>>>>>> My question is : doesn't the downloaded repository already include archetypes for web app generation?
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Thx
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Vimal
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> On 17/03/2012 7:59 AM, Burr Sutter wrote:
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> The Elluminate recording is now available
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> https://sas.elluminate.com/p.jnlp?psid=2012-03-16.0739.M.D93C90BA9FE03944...
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> My camtasia-based recording did not work as expected - user error :-(
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> I will make another attempt at getting a "vimeo" available version.
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>
>>>
>>>
>>> _______________________________________________
>>> jdf-dev mailing list
>>> jdf-dev(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jdf-dev
>>
>
>
12 years, 3 months
Re: [jdf-dev] Beta EAP6, JBDS5, WFK2 Training/Demo
by Pete Muir
No, I never got an ack from the JBDS team that the .CR1 was good to go.
On 1 Oct 2012, at 22:02, Vimal Kansal wrote:
> Hi Pete,
>
> I still see only CR1. Did you update it to Final?
>
> Thx
>
> Vimal
>
> On 25/07/2012 10:00 PM, Pete Muir wrote:
>> Fred, do you want to do any JBDS testing? Or should I release .Final?
>>
>> On 25 Jul 2012, at 12:56, Vimal Kansal wrote:
>>
>>> Hi Pete,
>>>
>>> Just tested both the archetypes and they work perfectly.
>>>
>>> Thanks a lot
>>>
>>> Vimal
>>>
>>> On 25/07/2012 2:01 AM, Pete Muir wrote:
>>>> Hi Vimal
>>>>
>>>> I've just released 7.1.1.CR1 of the archetypes (will sync to central in the next 24hrs). I tested them against the released EAP 6 Maven repo, and it looked like it was working.
>>>>
>>>> If you can double check, I can release the .Final and ask Fred to update JBDS.
>>>>
>>>> On 10 Jul 2012, at 00:16, Vimal Kansal wrote:
>>>>
>>>>> Yup, I used from maven central, but when I enable the EAP6 flag, I get the exceptions which I mentioned below.
>>>>>
>>>>> On 10/07/2012 9:45 AM, Pete Muir wrote:
>>>>>> This should be delivered via Maven central. I will check on the status, it looks like a release may not have been promoted.
>>>>>>
>>>>>> On 9 Jul 2012, at 22:35, Vimal Kansal wrote:
>>>>>>
>>>>>>> Hi Pete,
>>>>>>>
>>>>>>> Can you confirm whether the archetypes to generate "blank" web app and ear app were productized or not?
>>>>>>>
>>>>>>> Thx
>>>>>>>
>>>>>>> Vimal
>>>>>>>
>>>>>>> On 24/06/2012 3:58 AM, Vimal Kansal wrote:
>>>>>>>> Hi Guys,
>>>>>>>>
>>>>>>>> Any update on this. I am using GA of EAP 6, EAP 6 repository and JBDS 5.0, but still the same behaviour ?
>>>>>>>>
>>>>>>>> Thx
>>>>>>>>
>>>>>>>> Vimal
>>>>>>>>
>>>>>>>> On 11/04/2012 9:31 PM, Pete Muir wrote:
>>>>>>>>> Ah yes, this is to be expected. We are still working out how to productize those top two artifacts… Shelly or Paul know more.
>>>>>>>>>
>>>>>>>>> On 11 Apr 2012, at 02:49, Vimal Kansal wrote:
>>>>>>>>>
>>>>>>>>>> Hi Pete,
>>>>>>>>>>
>>>>>>>>>> Sorry for being late. I set up the whole thing again i.e EAP 6.0 Beta1, EAP 6.0 Maven Repo, JBDS 5.0 Beta 1 and used "New --> Maven -> Project" to use the new archetype. In the generated project, pom throws up following errors (with enterprise option set to true) :
>>>>>>>>>>
>>>>>>>>>> Project build error: Non-resolvable import POM: Failure to find org.jboss.bom:jboss-javaee-6.0-with-hibernate:pom:1.0.0.M6-redhat-1 in file:///home/vimal/jboss-eap-6.0.0.ER3-maven-repository was cached in the local repository, resolution will not be reattempted until the update interval of jboss-eap has elapsed or updates are forced
>>>>>>>>>>
>>>>>>>>>> Project build error: Non-resolvable import POM: Failure to find org.jboss.bom:jboss-javaee-6.0-with-tools:pom:1.0.0.M6-redhat-1 in file:///home/vimal/jboss-eap-6.0.0.ER3-maven-repository was cached in the local repository, resolution will not be reattempted until the update interval of jboss-eap has elapsed or updates are forced
>>>>>>>>>>
>>>>>>>>>> Project build error: 'dependencies.dependency.version' for org.jboss.spec.javax.annotation:jboss-annotations-api_1.1_spec:jar is missing.
>>>>>>>>>>
>>>>>>>>>> Project build error: 'dependencies.dependency.version' for javax.enterprise:cdi-api:jar is missing.
>>>>>>>>>>
>>>>>>>>>> Project build error: 'dependencies.dependency.version' for org.jboss.arquillian.protocol:arquillian-protocol-servlet:jar is missing.
>>>>>>>>>>
>>>>>>>>>> Project build error: 'dependencies.dependency.version' for org.jboss.arquillian.junit:arquillian-junit-container:jar is missing.
>>>>>>>>>>
>>>>>>>>>> Project build error: 'dependencies.dependency.version' for junit:junit:jar is missing.
>>>>>>>>>>
>>>>>>>>>> Project build error: 'dependencies.dependency.version' for org.hibernate:hibernate-validator-annotation-processor:jar is missing.
>>>>>>>>>>
>>>>>>>>>> Project build error: 'dependencies.dependency.version' for org.hibernate:hibernate-jpamodelgen:jar is missing.
>>>>>>>>>>
>>>>>>>>>> Project build error: 'dependencies.dependency.version' for org.jboss.spec.javax.faces:jboss-jsf-api_2.0_spec:jar is missing.
>>>>>>>>>>
>>>>>>>>>> Project build error: 'dependencies.dependency.version' for org.hibernate:hibernate-validator:jar is missing.
>>>>>>>>>>
>>>>>>>>>> Project build error: 'dependencies.dependency.version' for org.hibernate.javax.persistence:hibernate-jpa-2.0-api:jar is missing.
>>>>>>>>>>
>>>>>>>>>> Project build error: 'dependencies.dependency.version' for org.jboss.spec.javax.ws.rs:jboss-jaxrs-api_1.1_spec:jar is missing.
>>>>>>>>>>
>>>>>>>>>> Thx
>>>>>>>>>>
>>>>>>>>>> Vimal
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On 5/04/2012 10:02 PM, Pete Muir wrote:
>>>>>>>>>>> Many thanks!
>>>>>>>>>>>
>>>>>>>>>>> On 4 Apr 2012, at 21:37, Vimal Kansal wrote:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> Hi Pete,
>>>>>>>>>>>>
>>>>>>>>>>>> I am on customer site in Sydney and today I fly back to Melbourne. I will do a test again tomorrow and will get back to you.
>>>>>>>>>>>>
>>>>>>>>>>>> Thx
>>>>>>>>>>>>
>>>>>>>>>>>> Vimal
>>>>>>>>>>>>
>>>>>>>>>>>> On 5/04/2012 2:31 AM, Pete Muir wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Any details vimal?
>>>>>>>>>>>>>
>>>>>>>>>>>>> On 2 Apr 2012, at 13:57, Vimal Kansal wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hi Pete,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> The archetypes are working but when I set enterprise = true, they don't.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thx
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Vimal
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On 2/04/2012 6:45 PM, Pete Muir wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Vimal, do you have time to test them quickly, before we push them live to JBoss Central?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On 31 Mar 2012, at 01:19, Fred Bricon wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Pete, if they need to be included in JBoss Central, please open a JIRA with the GAV you want to see updated
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Le 30/03/2012 15:29, Pete Muir a écrit :
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Hi guys, 7.1.1.Beta1 of the archetypes are released. This includes the rebrand.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Please test for me.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Jay needs to merge some updates from Aerogear and then we can go Final. Hopefully this is it for EAP 6 now.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On 20 Mar 2012, at 09:05, Vimal Kansal wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> So, I checked the repository downloaded from customer support portal and it does not have the archetypes, and hence it goes to maven central. When these archetypes were being developed, a requirement was raised that we needed to have archetypes that could generate blank web application and a blank ear application. As a result of which, following archetypes were developed :
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> • org.jboss.spec.archetypes:boss-javaee6-webapp-archetype-blank
>>>>>>>>>>>>>>>>>> • org.jboss.spec.archetypes:jboss-javaee6-webapp-ear-archetype-blank
>>>>>>>>>>>>>>>>>> Subsequently, on my request, these were renamed as :
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> • org.jboss.spec.archetypes:boss-javaee6-webapp-blank-archetype
>>>>>>>>>>>>>>>>>> • org.jboss.spec.archetypes:jboss-javaee6-webapp-ear-blank-archetype
>>>>>>>>>>>>>>>>>> Please note the position of "blank" - I made this recommendation just to bring a standardisation to archetype naming convention i.e "archetype" be the last word in the name. This recommendation was accepted by Pete and subsequently all bug fixes and features were added to the second set of archetypes. These archetypes are hosted at :
>>>>>>>>>>>>>>>>>> https://repository.jboss.org/nexus/content/groups/public/org/jboss/spec/a...
>>>>>>>>>>>>>>>>>> (Actually this location continues to have both sets) The second set is not available in maven central, which is where JBDS 5.0/maven are fetching . Please note that the first set of archetypes above do not generate the correct project structure. So here is what I am not sure :
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> • Why are we not packaging the maven archetypes with the the maven repository that we download from Customer Support Portal?
>>>>>>>>>>>>>>>>>> • Can we resolve the correct archetypes for blank project generation.
>>>>>>>>>>>>>>>>>> Thx
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Vimal
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On 20/03/2012 8:50 PM, Vimal Kansal wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> And here is my settings.xml file(please see attached)
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> On 20/03/2012 8:46 PM, Vimal Kansal wrote:
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Hi Burr,
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> I am kind of confused , before I ask my question, here is how I have setup the EAP 6 and JBDS 5.0 and maven (So far my dev environment had involved working with AS 7.1.1, eclipse 3.7 + JBoss Tools 3.3) :
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> • I deployed my EAP 6 by unzipping it.
>>>>>>>>>>>>>>>>>>>> • I also deployed JBDS 5.0
>>>>>>>>>>>>>>>>>>>> • I added EAP 6.0 to JBDS 5.0
>>>>>>>>>>>>>>>>>>>> • A installed maven separately i.e separate to JBDS .
>>>>>>>>>>>>>>>>>>>> • Withing my JBDS, I updated maven plugin to refer to my externally installed maven :
>>>>>>>>>>>>>>>>>>>> • /home/vimal/Apps/apache-maven-3.0.4/conf/settings.xml
>>>>>>>>>>>>>>>>>>>> • I updated my settings file to refer to maven repository that I downloaded from the Customer Support Portal
>>>>>>>>>>>>>>>>>>>> • Now withing JBDS, from JBoss Central when I create a web app, it still goes to get the archetypes etc from maven central repository.
>>>>>>>>>>>>>>>>>>>> My question is : doesn't the downloaded repository already include archetypes for web app generation?
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Thx
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Vimal
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> On 17/03/2012 7:59 AM, Burr Sutter wrote:
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> The Elluminate recording is now available
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> https://sas.elluminate.com/p.jnlp?psid=2012-03-16.0739.M.D93C90BA9FE03944...
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> My camtasia-based recording did not work as expected - user error :-(
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> I will make another attempt at getting a "vimeo" available version.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>
12 years, 3 months
Re: [jdf-dev] JBoss Stacks Echosystem going Final
by Rafael Benevides
JBoss Stacks CR2 just adds JDF-112 from CR1
Thanks :)
Em 02-10-2012 13:45, Fred Bricon escreveu:
> I haven't tested the CR2 version yet (will do tomorrow morning).
> Looking at the changes (JDF-112), I'm pretty confident we should be ok
> for now.
>
> Fred.
>
> Le 02/10/2012 17:13, Rafael Benevides a écrit :
>> Hi all,
>>
>> I want a feedback from JBoss Stacks Echosystem (stacks.yaml format /
>> stacks-client / jdf-forge-plugin).
>>
>> We are on 1.0.0.CR2 format to stacks.yaml and I want to know if do
>> you have any other issue on this? So I can move all of them to .Final
>> and we can release JDF 2.0.0.Final next week.
>>
>>
>> Thanks
>>
>
12 years, 3 months
Fwd: [wfk] TicketMonster JDG delayed
by Pete Muir
FYI
Begin forwarded message:
> From: Marius Bogoevici <mbogoevi(a)redhat.com>
> Subject: [wfk] TicketMonster JDG delayed
> Date: 1 October 2012 15:42:54 PDT
> To: wfk-pm-list <wfk-pm-list(a)redhat.com>
>
> All,
>
> Unfortunately, the JDG integration with TicketMonster is delayed, mainly by the failure of completing the work before Java One. I plan to release it on the week of October 8, most likely mid-to late in the week.
>
> Sorry for the delay as well as the delayed notice.
>
> Sent from my iPhone
>
12 years, 3 months
JDF 2.0 Candidate Release 1 - 10/02/2012
by Rafael Benevides
This e-mail is just to remember the component owners that 2.0.0.CR1 will be published tomorrow (10/02/2012) and if you want to include your component in this release, you need to:
* release your component
* update the submodule in site to point to the release branch (used to render the updated guide)
* update the guide_metadata in the site to point to the right version number (used to point to the right stuff for download)
Thanks
--
Rafael Benevides | Senior Software Engineer
Red Hat Brazil
+55-61-9269-6576
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
12 years, 3 months
[JBoss JIRA] (JDF-40) Augment my application with RichFaces
by Rafael Benevides (JIRA)
[ https://issues.jboss.org/browse/JDF-40?page=com.atlassian.jira.plugin.sys... ]
Rafael Benevides updated JDF-40:
--------------------------------
Fix Version/s: 2.0.0.Final
(was: 2.0.0.CR1)
> Augment my application with RichFaces
> -------------------------------------
>
> Key: JDF-40
> URL: https://issues.jboss.org/browse/JDF-40
> Project: JBoss Developer Framework
> Issue Type: Feature Request
> Components: how_do_i
> Reporter: Burr Sutter
> Assignee: Pete Muir
> Fix For: 2.0.0.Final
>
>
> One of the key use case scenarios that I have personally run in to is...what happens when I wish to add RichFaces to an existing Java EE application.
> For instance, lets say that I have started using the Java EE Web Project in JBoss Central (JBDS) or the Blank archetype at Maven Central, how do I achieve the following:
> 1) update my pom.xml to include the additional dependencies
> 2) make sure any needed JBDS/Eclipse facets are enabled
> 3) update my .xhtml to include RichFaces libraries
--
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, 3 months
