Re: [jdf-dev] JBDS in the Getting Started Developing Applications Guide
by Pete Muir
Max, what about the original question? Should we be using JBDS as our "source" for quickstarts, rather than asking people to download them?
On 31 Jul 2012, at 13:12, Max Rydahl Andersen wrote:
>
> On 25 Jul 2012, at 17:52, Jonathan Fuerth <jfuerth(a)redhat.com> wrote:
>
>> Yes, this does make sense.
>>
>> Is there an automatic process available for updating our archetypes in JBDS and JBT? As I recall, the process we've been using is to file a JIRA for each archetype update we'd like.
>
> Not yet, thats the stack.yml efforts.
>
>> We've been incrementally automating our release procedure, and if we have to file a bunch of JIRAs every time we release Errai,
>
> It's one jira, not a bunch if i'm correct ;)
>
> And its not *everytime* you do a release afaik, its when you have a release that you feel is compatible and tested enough to work with AS 7.1/EAP 6.0 to be put front and center in JBT and/or JBDS.
>
>>> Fred/Max, I know what appears in the list is controlled centrally. Can you point us at it, so that we can understand where we are at, today?
>
> Fred is on vacation/honeymoon right now (got married saturday) - but he sent around this https://community.jboss.org/wiki/TestArchetypesInJBossCentral
> a while ago which describes how to test/setup archetype info.
>
> There is also https://community.jboss.org/wiki/MavenArchetypeCreationGuidelines stating the guidelines for the archetypes.
>
> The actual files are at http://download.jboss.org/jbosstools/examples/
>
> I believe the JBT 3.3 is http://download.jboss.org/jbosstools/examples/project-examples-maven-3.3.xml
> and JBDS 5.0 is at http://download.jboss.org/jbosstools/examples/project-examples-jbds50.xml
>
> /max
14 years
Re: [jdf-dev] JBDS in the Getting Started Developing Applications Guide
by Pete Muir
On 31 Jul 2012, at 13:12, Max Rydahl Andersen wrote:
>
> On 25 Jul 2012, at 17:52, Jonathan Fuerth <jfuerth(a)redhat.com> wrote:
>
>> Yes, this does make sense.
>>
>> Is there an automatic process available for updating our archetypes in JBDS and JBT? As I recall, the process we've been using is to file a JIRA for each archetype update we'd like.
>
> Not yet, thats the stack.yml efforts.
>
>> We've been incrementally automating our release procedure, and if we have to file a bunch of JIRAs every time we release Errai,
>
> It's one jira, not a bunch if i'm correct ;)
>
> And its not *everytime* you do a release afaik, its when you have a release that you feel is compatible and tested enough to work with AS 7.1/EAP 6.0 to be put front and center in JBT and/or JBDS.
>
>>> Fred/Max, I know what appears in the list is controlled centrally. Can you point us at it, so that we can understand where we are at, today?
>
> Fred is on vacation/honeymoon right now (got married saturday) - but he sent around this https://community.jboss.org/wiki/TestArchetypesInJBossCentral
> a while ago which describes how to test/setup archetype info.
>
> There is also https://community.jboss.org/wiki/MavenArchetypeCreationGuidelines stating the guidelines for the archetypes.
>
> The actual files are at http://download.jboss.org/jbosstools/examples/
>
> I believe the JBT 3.3 is http://download.jboss.org/jbosstools/examples/project-examples-maven-3.3.xml
It looks like http://download.jboss.org/jbosstools/examples/project-examples-shared-3.3... is more relevant
> and JBDS 5.0 is at http://download.jboss.org/jbosstools/examples/project-examples-jbds50.xml
>
> /max
14 years
JBDS in the Getting Started Developing Applications Guide
by Pete Muir
All
ATM the guide discusses using Maven from the command line to work with the quickstarts, and then presents JBDS as an option, suggesting people import the quickstart via m2e. Since I originally wrote this guide JBoss Central has been added to JBDS, and incorporates many of the quickstarts that the guide discusses in the "Project Examples".
I propose that I rework the guide to present using the Project Examples first and foremost, and present the command line, with the quickstarts download, as an option.
This does mean we're going to have push the quickstarts to JBDS more actively, and decide on what should be included.
Fred/Max, I know what appears in the list is controlled centrally. Can you point us at it, so that we can understand where we are at, today?
Pete
14 years
JBoss Stacks site update
by Rafael Benevides
Hi ALL
After digging the awestruct/ruby/haml world I update the JDF site to
read the jboss-stack yaml file
So I created a new section named JBoss Stacks that's what we have been
calling it.
This new section contains:
- The JBoss boms (from yaml file -
https://github.com/jboss-jdf/jdf-stack/blob/Beta2/stacks.yaml)
- The Runtime matrix (Major Releases, Minor Releases and some
Runtime data - also read from yaml file)
- A page about JDF plugin (from README.md)
- PLANED: Archetypes data
This new section is at http://site-jdf.rhcloud.com/stack/boms/ - *I'll
thank for any review* and just to know: My designer skill is terrible :p
P.S: Pete Muir heard something about "JBoss Stacks" is an overloaded
name. I don't think that we should change it but if someone have any
name idea, it will be welcome.
--
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
14 years
Re: [jdf-dev] Beta EAP6, JBDS5, WFK2 Training/Demo
by Pete Muir
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.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>
14 years
Re: [jdf-dev] Beta EAP6, JBDS5, WFK2 Training/Demo
by Pete Muir
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.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>
14 years
Re: [jdf-dev] Full set of Java EE APIs in JBoss spec
by Pete Muir
Less proliferation of APIs. Good example of sharing and community involvement.
On 24 Jul 2012, at 14:51, Shelly McGowan wrote:
>
>
> Really? Why do you think working with Geronimo is a good idea?
>
> Shelly
>
>
>
> ----- Original Message -----
> From: "Pete Muir" <pmuir(a)redhat.com>
> To: "Paul Gier" <pgier(a)redhat.com>
> Cc: "Jason Porter" <jporter(a)redhat.com>, jdf-dev(a)lists.jboss.org, "Shelly McGowan" <smcgowan(a)redhat.com>
> Sent: Tuesday, July 24, 2012 7:15:05 AM
> Subject: Re: [jdf-dev] Full set of Java EE APIs in JBoss spec
>
> Working with Geronimo sounds like a good option to me
>
> On 23 Jul 2012, at 19:52, Paul Gier wrote:
>
>> At this point I guess we just have to decide how much resources we want
>> to spend on the JBoss specs project. We found some questionable
>> licensing issues earlier this year which caused us to change the
>> licenses of the specs project. So one of the priorities for the JBoss
>> specs project is to do a more thorough code and license review. And it
>> may be necessary to re-write some of the projects from scratch if we
>> want to own the copyright.
>>
>> Another option would be for us to move away from the JBoss specs project
>> and work more closely with the Geronimo team, eventually just using
>> their set of specs in JBoss AS. Possibly with our own forked builds of
>> their jars in case we need to fix something quickly.
>>
>> With either of these options we also have the issue of some JBoss
>> projects which control their own spec APIs and would likely not give up
>> this control. I'm thinking of Hibernate with JPA and Resteasy with JAX-RS.
>>
>> On 07/23/2012 08:23 AM, Jason Porter wrote:
>>> There's no problem AFAIK, however, the Fedora Java guys are looking to package things up in Fedora (and that will probably make its way to RHEL) and they're much better off to use all jars from a single source. Right now that single source looks to be Geromino instead of JBoss.
>>>
>>> ----- Paul Gier <pgier(a)redhat.com> wrote:
>>>> Hi Pete,
>>>>
>>>> By missing, do you mean APIs jars that come from thirdparty? I believe
>>>> our BOM has all the APIs, there is just a split between the jars built
>>>> as part of the JBoss specs project vs. built by thirdparties.
>>>>
>>>> You can see the split in the specs BOM here:
>>>> http://repo1.maven.org/maven2/org/jboss/spec/jboss-javaee-6.0/3.0.1.Final...
>>>>
>>>> I'm not sure if we'll have time to re-create the remaining thirdparty
>>>> ones, it's pretty low priority. What's the problem that they cause
>>>> currently?
>>>>
>>>> On 07/09/2012 05:17 PM, Pete Muir wrote:
>>>>> Hey Shelly, Paul,
>>>>>
>>>>> I know we are missing a few of these, and for consistency/one less FAQ, it would be nice to have a complete set.
>>>>>
>>>>> WDYT? Do you guys have time to "finish this off" over the next month or two?
>>>>>
>>>>> Pete
>>>>>
>>>>
>>>> _______________________________________________
>>>> jdf-dev mailing list
>>>> jdf-dev(a)lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jdf-dev
>>>
>>
>
14 years
