I've pushed out a 7.0.0.Beta1-prerelease tag and updated upstream for Beta2 development. Later this week Jason will be setting the release "code name" and uploading the binary artifacts to be made available for downloading and taking care of all that business. Big thanks to everyone who put in extra effort to get this tag done. I expect that the official release announcement will be happening later this week. -- - DML _______________________________________________ jboss-as7-dev mailing list jboss-as7-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

"Ides of March" is now live: http://www.jboss.org/jbossas/downloads I'll do a proper announcement soon. On Mar 15, 2011, at 6:54 PM, Bruno Georges<bgeorges(a)redhat.com> wrote: > David, All > > Thank you for your incredible efforts! > This is another great milestone for JBoss AS7! > Again delivered according to plan. > Many of you worked around the clock to make this happen, it is greatly appreciated. > > We will be looking forward to get community feedback! > The Beta releases cadence is starting and more will be coming at regular intervals. > > AS7 Rocks! > > B. > On 16 Mar 2011, at 09:14, David M. Lloyd wrote: > >> I've pushed out a 7.0.0.Beta1-prerelease tag and updated upstream for >> Beta2 development. Later this week Jason will be setting the release >> "code name" and uploading the binary artifacts to be made available for >> downloading and taking care of all that business. >> >> Big thanks to everyone who put in extra effort to get this tag done. I >> expect that the official release announcement will be happening later >> this week. >> >> -- >> - DML >> _______________________________________________ >> jboss-as7-dev mailing list >> jboss-as7-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev > > > _______________________________________________ > jboss-as7-dev mailing list > jboss-as7-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-as7-dev _______________________________________________ jboss-as7-dev mailing list jboss-as7-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

Great news ! 1st start: JBoss AS 7.0.0.Beta1 "Ides of March" started in 3495ms 2nd start: JBoss AS 7.0.0.Beta1 "Ides of March" started in 2422ms Good to see :) Congrats to the team ! On 03/16/2011 07:25 AM, Jason Greene wrote: > "Ides of March" is now live: > http://www.jboss.org/jbossas/downloads > > I'll do a proper announcement soon. > > On Mar 15, 2011, at 6:54 PM, Bruno Georges<bgeorges(a)redhat.com> wrote: > >> David, All >> >> Thank you for your incredible efforts! >> This is another great milestone for JBoss AS7! >> Again delivered according to plan. >> Many of you worked around the clock to make this happen, it is greatly appreciated. >> >> We will be looking forward to get community feedback! >> The Beta releases cadence is starting and more will be coming at regular intervals. >> >> AS7 Rocks! >> >> B. >> On 16 Mar 2011, at 09:14, David M. Lloyd wrote: >> >>> I've pushed out a 7.0.0.Beta1-prerelease tag and updated upstream for >>> Beta2 development. Later this week Jason will be setting the release >>> "code name" and uploading the binary artifacts to be made available for >>> downloading and taking care of all that business. >>> >>> Big thanks to everyone who put in extra effort to get this tag done. I >>> expect that the official release announcement will be happening later >>> this week. >>> >>> -- >>> - DML >>> _______________________________________________ >>> jboss-as7-dev mailing list >>> jboss-as7-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev >> >> _______________________________________________ >> jboss-as7-dev mailing list >> jboss-as7-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev > _______________________________________________ > jboss-as7-dev mailing list > jboss-as7-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-as7-dev _______________________________________________ jboss-as7-dev mailing list jboss-as7-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

Alpha1: 19MB Beta1: 52MB ...what the heck happened ;) /max > Great news ! > > 1st start: JBoss AS 7.0.0.Beta1 "Ides of March" started in 3495ms > 2nd start: JBoss AS 7.0.0.Beta1 "Ides of March" started in 2422ms > > Good to see :) > > Congrats to the team ! > > > On 03/16/2011 07:25 AM, Jason Greene wrote: >> "Ides of March" is now live: >> http://www.jboss.org/jbossas/downloads >> >> I'll do a proper announcement soon. >> >> On Mar 15, 2011, at 6:54 PM, Bruno Georges<bgeorges(a)redhat.com> wrote: >> >>> David, All >>> >>> Thank you for your incredible efforts! >>> This is another great milestone for JBoss AS7! >>> Again delivered according to plan. >>> Many of you worked around the clock to make this happen, it is greatly appreciated. >>> >>> We will be looking forward to get community feedback! >>> The Beta releases cadence is starting and more will be coming at regular intervals. >>> >>> AS7 Rocks! >>> >>> B. >>> On 16 Mar 2011, at 09:14, David M. Lloyd wrote: >>> >>>> I've pushed out a 7.0.0.Beta1-prerelease tag and updated upstream for >>>> Beta2 development. Later this week Jason will be setting the release >>>> "code name" and uploading the binary artifacts to be made available for >>>> downloading and taking care of all that business. >>>> >>>> Big thanks to everyone who put in extra effort to get this tag done. I >>>> expect that the official release announcement will be happening later >>>> this week. >>>> >>>> -- >>>> - DML >>>> _______________________________________________ >>>> jboss-as7-dev mailing list >>>> jboss-as7-dev(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev >>> >>> _______________________________________________ >>> jboss-as7-dev mailing list >>> jboss-as7-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev >> _______________________________________________ >> jboss-as7-dev mailing list >> jboss-as7-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev > > _______________________________________________ > jboss-as7-dev mailing list > jboss-as7-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-as7-dev /max http://about.me/maxandersen _______________________________________________ jboss-as7-dev mailing list jboss-as7-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

> You get more stuff for the same $$$, it's good for you :-) > > (of course, it's just more libs included) Yeah, I know :) Was just dreaming of having a really small EE compliant server...

/max > On 16/03/2011 13:14, Max Rydahl Andersen wrote: >> >> Alpha1: 19MB >> Beta1: 52MB >> >> ...what the heck happened ;) >> >> /max >> >>> Great news ! >>> >>> 1st start: JBoss AS 7.0.0.Beta1 "Ides of March" started in 3495ms >>> 2nd start: JBoss AS 7.0.0.Beta1 "Ides of March" started in 2422ms >>> >>> Good to see :) >>> >>> Congrats to the team ! >>> >>> >>> On 03/16/2011 07:25 AM, Jason Greene wrote: >>>> "Ides of March" is now live: >>>> http://www.jboss.org/jbossas/downloads >>>> >>>> I'll do a proper announcement soon. >>>> >>>> On Mar 15, 2011, at 6:54 PM, Bruno Georges<bgeorges(a)redhat.com> wrote: >>>> >>>>> David, All >>>>> >>>>> Thank you for your incredible efforts! >>>>> This is another great milestone for JBoss AS7! >>>>> Again delivered according to plan. >>>>> Many of you worked around the clock to make this happen, it is greatly appreciated. >>>>> >>>>> We will be looking forward to get community feedback! >>>>> The Beta releases cadence is starting and more will be coming at regular intervals. >>>>> >>>>> AS7 Rocks! >>>>> >>>>> B. >>>>> On 16 Mar 2011, at 09:14, David M. Lloyd wrote: >>>>> >>>>>> I've pushed out a 7.0.0.Beta1-prerelease tag and updated upstream for >>>>>> Beta2 development. Later this week Jason will be setting the release >>>>>> "code name" and uploading the binary artifacts to be made available for >>>>>> downloading and taking care of all that business. >>>>>> >>>>>> Big thanks to everyone who put in extra effort to get this tag done. I >>>>>> expect that the official release announcement will be happening later >>>>>> this week. >>>>>> >>>>>> -- >>>>>> - DML >>>>>> _______________________________________________ >>>>>> jboss-as7-dev mailing list >>>>>> jboss-as7-dev(a)lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev >>>>> _______________________________________________ >>>>> jboss-as7-dev mailing list >>>>> jboss-as7-dev(a)lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev >>>> _______________________________________________ >>>> jboss-as7-dev mailing list >>>> jboss-as7-dev(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev >>> _______________________________________________ >>> jboss-as7-dev mailing list >>> jboss-as7-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev >> /max >> http://about.me/maxandersen >> >> >> >> >> _______________________________________________ >> jboss-as7-dev mailing list >> jboss-as7-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev > -- > xxxxxxxxxxxxxxxxxxxxxxxxxxxx > Dimitris Andreadis > Software Engineering Manager > JBoss Application Server > by Red Hat > xxxxxxxxxxxxxxxxxxxxxxxxxxxx > > http://dandreadis.blogspot.com/ > _______________________________________________ > jboss-as7-dev mailing list > jboss-as7-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-as7-dev /max http://about.me/maxandersen _______________________________________________ jboss-as7-dev mailing list jboss-as7-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

Alpha1: 19MB Beta1: 52MB ...what the heck happened ;) /max > Great news ! > > 1st start: JBoss AS 7.0.0.Beta1 "Ides of March" started in 3495ms > 2nd start: JBoss AS 7.0.0.Beta1 "Ides of March" started in 2422ms > > Good to see :) > > Congrats to the team ! > > > On 03/16/2011 07:25 AM, Jason Greene wrote: >> "Ides of March" is now live: >> http://www.jboss.org/jbossas/downloads >> >> I'll do a proper announcement soon. >> >> On Mar 15, 2011, at 6:54 PM, Bruno Georges<bgeorges(a)redhat.com> wrote: >> >>> David, All >>> >>> Thank you for your incredible efforts! >>> This is another great milestone for JBoss AS7! >>> Again delivered according to plan. >>> Many of you worked around the clock to make this happen, it is greatly appreciated. >>> >>> We will be looking forward to get community feedback! >>> The Beta releases cadence is starting and more will be coming at regular intervals. >>> >>> AS7 Rocks! >>> >>> B. >>> On 16 Mar 2011, at 09:14, David M. Lloyd wrote: >>> >>>> I've pushed out a 7.0.0.Beta1-prerelease tag and updated upstream for >>>> Beta2 development. Later this week Jason will be setting the release >>>> "code name" and uploading the binary artifacts to be made available for >>>> downloading and taking care of all that business. >>>> >>>> Big thanks to everyone who put in extra effort to get this tag done. I >>>> expect that the official release announcement will be happening later >>>> this week. >>>> >>>> -- >>>> - DML >>>> _______________________________________________ >>>> jboss-as7-dev mailing list >>>> jboss-as7-dev(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev >>> >>> _______________________________________________ >>> jboss-as7-dev mailing list >>> jboss-as7-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev >> _______________________________________________ >> jboss-as7-dev mailing list >> jboss-as7-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev > > _______________________________________________ > jboss-as7-dev mailing list > jboss-as7-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-as7-dev /max http://about.me/maxandersen _______________________________________________ jboss-as7-dev mailing list jboss-as7-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

Since it's all modularized now. What about if we ship really small, and allow for things to be pulled / downloaded later?

By default we would still pack all bins, or you could download pre-configred lazy module-pull AS. And setup some jboss.org JBoss Modules custom repo, to simplify lookup, almost the same way we do it now locally.

On Mar 16, 2011, at 2:36 PM, David M. Lloyd wrote: > This brings up an important point that I think we need to address during > the Beta series. A few modules are including their Maven dependencies > directly within their module - even if that Maven dependency already > exists elsewhere - and also, we have a lot of extra dependencies for > things which are either redundant or are only in use for a few classes. > This defeats the gains we get from modules, in addition to introducing > potential CCE problems. > > In the interests of fast boot time and low mem. footprint, I will be > opening JIRAs for each of these occurrences to be fixed for Beta2 or > perhaps Beta3. > > In terms of raw memory usage, more "stuff" is loaded and cached to be > sure, if the memory is available - however you'll find that if you limit > the maximum heap -Xmx16m for example it should boot just fine. A couple > weeks ago I got it to boot with -Xmx9m. > > On 03/16/2011 06:14 AM, Max Rydahl Andersen wrote: >> >> >> Alpha1: 19MB >> Beta1: 52MB >> >> ...what the heck happened ;) >> >> /max >> >>> Great news ! >>> >>> 1st start: JBoss AS 7.0.0.Beta1 "Ides of March" started in 3495ms >>> 2nd start: JBoss AS 7.0.0.Beta1 "Ides of March" started in 2422ms >>> >>> Good to see :) >>> >>> Congrats to the team ! >>> >>> >>> On 03/16/2011 07:25 AM, Jason Greene wrote: >>>> "Ides of March" is now live: >>>> http://www.jboss.org/jbossas/downloads >>>> >>>> I'll do a proper announcement soon. >>>> >>>> On Mar 15, 2011, at 6:54 PM, Bruno Georges<bgeorges(a)redhat.com> wrote: >>>> >>>>> David, All >>>>> >>>>> Thank you for your incredible efforts! >>>>> This is another great milestone for JBoss AS7! >>>>> Again delivered according to plan. >>>>> Many of you worked around the clock to make this happen, it is greatly appreciated. >>>>> >>>>> We will be looking forward to get community feedback! >>>>> The Beta releases cadence is starting and more will be coming at regular intervals. >>>>> >>>>> AS7 Rocks! >>>>> >>>>> B. >>>>> On 16 Mar 2011, at 09:14, David M. Lloyd wrote: >>>>> >>>>>> I've pushed out a 7.0.0.Beta1-prerelease tag and updated upstream for >>>>>> Beta2 development. Later this week Jason will be setting the release >>>>>> "code name" and uploading the binary artifacts to be made available for >>>>>> downloading and taking care of all that business. >>>>>> >>>>>> Big thanks to everyone who put in extra effort to get this tag done. I >>>>>> expect that the official release announcement will be happening later >>>>>> this week. >>>>>> >>>>>> -- >>>>>> - DML >>>>>> _______________________________________________ >>>>>> jboss-as7-dev mailing list >>>>>> jboss-as7-dev(a)lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev >>>>> >>>>> _______________________________________________ >>>>> jboss-as7-dev mailing list >>>>> jboss-as7-dev(a)lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev >>>> _______________________________________________ >>>> jboss-as7-dev mailing list >>>> jboss-as7-dev(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev >>> >>> _______________________________________________ >>> jboss-as7-dev mailing list >>> jboss-as7-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev >> >> /max >> http://about.me/maxandersen >> >> >> >> >> _______________________________________________ >> jboss-as7-dev mailing list >> jboss-as7-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev > > > -- > - DML > _______________________________________________ > jboss-as7-dev mailing list > jboss-as7-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-as7-dev _______________________________________________ jboss-as7-dev mailing list jboss-as7-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

Since it's all modularized now. What about if we ship really small, and allow for things to be pulled / downloaded later? It could be experimental to start with, and if it proves to be "popular", we could make it default. By default we would still pack all bins, or you could download pre-configred lazy module-pull AS. And setup some jboss.org JBoss Modules custom repo, to simplify lookup, almost the same way we do it now locally. On Mar 16, 2011, at 2:36 PM, David M. Lloyd wrote: > This brings up an important point that I think we need to address during > the Beta series. A few modules are including their Maven dependencies > directly within their module - even if that Maven dependency already > exists elsewhere - and also, we have a lot of extra dependencies for > things which are either redundant or are only in use for a few classes. > This defeats the gains we get from modules, in addition to introducing > potential CCE problems. > > In the interests of fast boot time and low mem. footprint, I will be > opening JIRAs for each of these occurrences to be fixed for Beta2 or > perhaps Beta3. > > In terms of raw memory usage, more "stuff" is loaded and cached to be > sure, if the memory is available - however you'll find that if you limit > the maximum heap -Xmx16m for example it should boot just fine. A couple > weeks ago I got it to boot with -Xmx9m. > > On 03/16/2011 06:14 AM, Max Rydahl Andersen wrote: >> >> >> Alpha1: 19MB >> Beta1: 52MB >> >> ...what the heck happened ;) >> >> /max >> >>> Great news ! >>> >>> 1st start: JBoss AS 7.0.0.Beta1 "Ides of March" started in 3495ms >>> 2nd start: JBoss AS 7.0.0.Beta1 "Ides of March" started in 2422ms >>> >>> Good to see :) >>> >>> Congrats to the team ! >>> >>> >>> On 03/16/2011 07:25 AM, Jason Greene wrote: >>>> "Ides of March" is now live: >>>> http://www.jboss.org/jbossas/downloads >>>> >>>> I'll do a proper announcement soon. >>>> >>>> On Mar 15, 2011, at 6:54 PM, Bruno Georges<bgeorges(a)redhat.com> wrote: >>>> >>>>> David, All >>>>> >>>>> Thank you for your incredible efforts! >>>>> This is another great milestone for JBoss AS7! >>>>> Again delivered according to plan. >>>>> Many of you worked around the clock to make this happen, it is greatly appreciated. >>>>> >>>>> We will be looking forward to get community feedback! >>>>> The Beta releases cadence is starting and more will be coming at regular intervals. >>>>> >>>>> AS7 Rocks! >>>>> >>>>> B. >>>>> On 16 Mar 2011, at 09:14, David M. Lloyd wrote: >>>>> >>>>>> I've pushed out a 7.0.0.Beta1-prerelease tag and updated upstream for >>>>>> Beta2 development. Later this week Jason will be setting the release >>>>>> "code name" and uploading the binary artifacts to be made available for >>>>>> downloading and taking care of all that business. >>>>>> >>>>>> Big thanks to everyone who put in extra effort to get this tag done. I >>>>>> expect that the official release announcement will be happening later >>>>>> this week. >>>>>> >>>>>> -- >>>>>> - DML >>>>>> _______________________________________________ >>>>>> jboss-as7-dev mailing list >>>>>> jboss-as7-dev(a)lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev >>>>> >>>>> _______________________________________________ >>>>> jboss-as7-dev mailing list >>>>> jboss-as7-dev(a)lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev >>>> _______________________________________________ >>>> jboss-as7-dev mailing list >>>> jboss-as7-dev(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev >>> >>> _______________________________________________ >>> jboss-as7-dev mailing list >>> jboss-as7-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev >> >> /max >> http://about.me/maxandersen >> >> >> >> >> _______________________________________________ >> jboss-as7-dev mailing list >> jboss-as7-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev > > > -- > - DML > _______________________________________________ > jboss-as7-dev mailing list > jboss-as7-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-as7-dev _______________________________________________ jboss-as7-dev mailing list jboss-as7-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

Sure, long term I think we should definitely come up with something like this. However actually doing this is more complex than you'd think. For now we need to keep our eye on the prize and get a feature-complete AS7 GA out the door. On 03/16/2011 09:00 AM, Ales Justin wrote: > Since it's all modularized now. > What about if we ship really small, > and allow for things to be pulled / downloaded later? > > It could be experimental to start with, > and if it proves to be "popular", we could make it default. > > By default we would still pack all bins, > or you could download pre-configred lazy module-pull AS. > And setup some jboss.org JBoss Modules custom repo, > to simplify lookup, almost the same way we do it now locally.

Yesterday, we replaced "jaas" with "security-domains". Pull upstream. On 03/17/2011 11:40 AM, Ales Justin wrote: > OK, couldn't resist playing with this last night, > so I hacked a simple "remote" ModuleLoader. > > * https://github.com/alesj/jboss-modules/blob/f1debb42023bc720708c53dd1801b... > > It gets me pretty far. > Initial issue is to have logging module already locally, dunno really why. > > Then it all fails with configuration scanning. > Any idea why? > > > 17:17:07,601 ERROR [org.jboss.msc.service.fail] MSC00001: Failed to start service jboss.as.server-controller: org.jboss.msc.service.StartException in service jboss.as.server-controller: org.jboss.as.controller.persistence.ConfigurationPersistenceException: Failed to parse configuration > at org.jboss.as.server.ServerControllerService.start(ServerControllerService.java:146) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1344) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_22] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_22] > at java.lang.Thread.run(Thread.java:680) [:1.6.0_22] > Caused by: org.jboss.as.controller.persistence.ConfigurationPersistenceException: Failed to parse configuration > at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:120) > at org.jboss.as.server.ServerControllerService.start(ServerControllerService.java:144) > ... 4 more > Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[143,19] > Message: Unexpected element '{urn:jboss:domain:security:1.0}jaas' encountered > at org.jboss.as.controller.parsing.ParseUtils.unexpectedElement(ParseUtils.java:65) > at org.jboss.as.security.SecuritySubsystemParser.readElement(SecuritySubsystemParser.java:118) > at org.jboss.as.security.SecuritySubsystemParser.readElement(SecuritySubsystemParser.java:73) > at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:100) > at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:69) > at org.jboss.as.controller.parsing.StandaloneXml.parseServerProfile(StandaloneXml.java:390) > at org.jboss.as.controller.parsing.StandaloneXml.readServerElement(StandaloneXml.java:159) > at org.jboss.as.controller.parsing.StandaloneXml.readElement(StandaloneXml.java:92) > at org.jboss.as.controller.parsing.StandaloneXml.readElement(StandaloneXml.java:80) > at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:100) > at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:59) > at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:112) > ... 5 more > > 17:17:07,607 ERROR [stderr] java.util.concurrent.ExecutionException: Operation failed > 17:17:07,607 ERROR [org.jboss.as] JBoss AS 7.0.0.Beta2 "(TBD)" started (with errors) in 118502ms - Started 16 of 17 services (1 services failed or missing dependencies, 0 services are passive or on-demand) > 17:17:07,607 ERROR [stderr] at org.jboss.threads.AsyncFutureTask.operationFailed(AsyncFutureTask.java:74) > 17:17:07,607 ERROR [stderr] at org.jboss.threads.AsyncFutureTask.get(AsyncFutureTask.java:268) > 17:17:07,607 ERROR [stderr] at org.jboss.as.server.Main.main(Main.java:83) > 17:17:07,607 ERROR [stderr] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > 17:17:07,607 ERROR [stderr] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > 17:17:07,607 ERROR [stderr] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > 17:17:07,608 ERROR [stderr] at java.lang.reflect.Method.invoke(Method.java:597) > 17:17:07,608 ERROR [stderr] at org.jboss.modules.Module.run(Module.java:261) > 17:17:07,608 ERROR [stderr] at org.jboss.modules.Main.main(Main.java:236) > 17:17:07,608 ERROR [stderr] Caused by: org.jboss.msc.service.StartException in service jboss.as.server-controller: org.jboss.as.controller.persistence.ConfigurationPersistenceException: Failed to parse configuration > 17:17:07,608 ERROR [stderr] at org.jboss.as.server.ServerControllerService.start(ServerControllerService.java:146) > 17:17:07,608 ERROR [stderr] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1344) > 17:17:07,608 ERROR [stderr] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > 17:17:07,608 ERROR [stderr] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > 17:17:07,609 ERROR [stderr] at java.lang.Thread.run(Thread.java:680) > 17:17:07,609 ERROR [stderr] Caused by: org.jboss.as.controller.persistence.ConfigurationPersistenceException: Failed to parse configuration > 17:17:07,609 ERROR [stderr] at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:120) > 17:17:07,609 ERROR [stderr] at org.jboss.as.server.ServerControllerService.start(ServerControllerService.java:144) > 17:17:07,609 ERROR [stderr] ... 4 more > 17:17:07,609 ERROR [stderr] Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[143,19] > 17:17:07,609 ERROR [stderr] Message: Unexpected element '{urn:jboss:domain:security:1.0}jaas' encountered > 17:17:07,609 ERROR [stderr] at org.jboss.as.controller.parsing.ParseUtils.unexpectedElement(ParseUtils.java:65) > 17:17:07,610 ERROR [stderr] at org.jboss.as.security.SecuritySubsystemParser.readElement(SecuritySubsystemParser.java:118) > 17:17:07,610 ERROR [stderr] at org.jboss.as.security.SecuritySubsystemParser.readElement(SecuritySubsystemParser.java:73) > 17:17:07,610 ERROR [stderr] at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:100) > 17:17:07,610 ERROR [stderr] at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:69) > 17:17:07,611 ERROR [stderr] at org.jboss.as.controller.parsing.StandaloneXml.parseServerProfile(StandaloneXml.java:390) > 17:17:07,611 ERROR [stderr] at org.jboss.as.controller.parsing.StandaloneXml.readServerElement(StandaloneXml.java:159) > 17:17:07,611 ERROR [stderr] at org.jboss.as.controller.parsing.StandaloneXml.readElement(StandaloneXml.java:92) > 17:17:07,611 ERROR [stderr] at org.jboss.as.controller.parsing.StandaloneXml.readElement(StandaloneXml.java:80) > 17:17:07,611 ERROR [stderr] at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:100) > 17:17:07,611 ERROR [stderr] at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:59) > 17:17:07,611 ERROR [stderr] at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:112) > 17:17:07,611 ERROR [stderr] ... 5 more > > On Mar 16, 2011, at 3:08 PM, David M. Lloyd wrote: > >> Sure, long term I think we should definitely come up with something like >> this. However actually doing this is more complex than you'd think. >> For now we need to keep our eye on the prize and get a feature-complete >> AS7 GA out the door. >> >> On 03/16/2011 09:00 AM, Ales Justin wrote: >>> Since it's all modularized now. >>> What about if we ship really small, >>> and allow for things to be pulled / downloaded later? >>> >>> It could be experimental to start with, >>> and if it proves to be "popular", we could make it default. >>> >>> By default we would still pack all bins, >>> or you could download pre-configred lazy module-pull AS. >>> And setup some jboss.org JBoss Modules custom repo, >>> to simplify lookup, almost the same way we do it now locally. > _______________________________________________ jboss-as7-dev mailing list jboss-as7-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

Ah, you were right Anil. :-) My "remote" repo had the latest version, while I had old locally. It takes a while to boot the first time, but it works. :-) * 1st -- 18:29:34,386 INFO [org.jboss.as] (MSC service thread 1-2) JBoss AS 7.0.0.Beta2 "(TBD)" started in 228356ms - Started 88 of 112 services (24 services are passive or on-demand) * 2nd -- 18:30:03,713 INFO [org.jboss.as] (MSC service thread 1-4) JBoss AS 7.0.0.Beta2 "(TBD)" started in 2081ms - Started 88 of 112 services (24 services are passive or on-demand) Still dunno why I need logmanager locally to start with ... > Hmm, it works with default (non RemoteModuleLoader) usage. > I'll try the rebase, but I doubt it will change anything. > > On Mar 17, 2011, at 5:49 PM, Anil Saldhana wrote: > >> Yesterday, we replaced "jaas" with "security-domains". Pull upstream. >> >> On 03/17/2011 11:40 AM, Ales Justin wrote: >>> OK, couldn't resist playing with this last night, >>> so I hacked a simple "remote" ModuleLoader. >>> >>> * https://github.com/alesj/jboss-modules/blob/f1debb42023bc720708c53dd1801b... _______________________________________________ jboss-as7-dev mailing list jboss-as7-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

I've pushed out a 7.0.0.Beta1-prerelease tag and updated upstream for Beta2 development. Later this week Jason will be setting the release "code name" and uploading the binary artifacts to be made available for downloading and taking care of all that business. Big thanks to everyone who put in extra effort to get this tag done. I expect that the official release announcement will be happening later this week.

Thomas I think ultimately we need a comprehensive in-AS test suite. This is the only way we're going to be able to catch problems on an ongoing basis. I don't think we can afford to externally validate only once per release - I can absolutely guarantee that this will cause unexpected release delays. On 03/16/2011 04:27 AM, Thomas Diesler wrote: > Hi David, > > do we have a process that allows subsystem providers to verify a > potential AS7 release before it gets tagged? I have an extensive OSGi > testsuite that runs on a nightly basis against AS7 master. I noticed > this morning that this commit > > https://github.com/jbossas/jboss-as/commit/fd5696596545d9d9c2e4eb4c499bf3... > > > broke OSGi webapp support again. The related issue, which I now > reopened, is https://issues.jboss.org/browse/JBAS-8940 > > Can we perhaps resolve this issue before Beta1 becomes generally available? > To move forward I'll improve OSGi test coverage to a level were it > covers everything that is expected to work. > > cheers > -thomas > > On 03/16/2011 02:14 AM, David M. Lloyd wrote: >> I've pushed out a 7.0.0.Beta1-prerelease tag and updated upstream for >> Beta2 development. Later this week Jason will be setting the release >> "code name" and uploading the binary artifacts to be made available for >> downloading and taking care of all that business. >> >> Big thanks to everyone who put in extra effort to get this tag done. I >> expect that the official release announcement will be happening later >> this week. >> > -- - DML _______________________________________________ jboss-as7-dev mailing list jboss-as7-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

David, the AS test suite needs to be comprehensive - no doubt. However, we have a release cycle that is different from AS and continuously test a large set of OSGi functionality against AS7 trunk one a nightly basis. Following your suggested approach, I would need to duplicate every OSGi example and functional test in the AS7 code base. Alternatively, I'm suggesting to have a known "Code Freeze" date and give every subsystem that has an external test suite a chance to verify/veto the intended release code base. 1.0.0.Beta1 was broken for OSGi webapps because of last minute changes - I'm looking for ways to possibly fix Beta1 and have a reasonable process that avoids this to happen in the future. cheers -thomas On 03/16/2011 02:30 PM, David M. Lloyd wrote: > Thomas I think ultimately we need a comprehensive in-AS test suite. > This is the only way we're going to be able to catch problems on an > ongoing basis. I don't think we can afford to externally validate > only once per release - I can absolutely guarantee that this will > cause unexpected release delays. > > On 03/16/2011 04:27 AM, Thomas Diesler wrote: >> Hi David, >> >> do we have a process that allows subsystem providers to verify a >> potential AS7 release before it gets tagged? I have an extensive OSGi >> testsuite that runs on a nightly basis against AS7 master. I noticed >> this morning that this commit >> >> https://github.com/jbossas/jboss-as/commit/fd5696596545d9d9c2e4eb4c499bf3... >> >> >> >> broke OSGi webapp support again. The related issue, which I now >> reopened, is https://issues.jboss.org/browse/JBAS-8940 >> >> Can we perhaps resolve this issue before Beta1 becomes generally >> available? >> To move forward I'll improve OSGi test coverage to a level were it >> covers everything that is expected to work. >> >> cheers >> -thomas >> >> On 03/16/2011 02:14 AM, David M. Lloyd wrote: >>> I've pushed out a 7.0.0.Beta1-prerelease tag and updated upstream for >>> Beta2 development. Later this week Jason will be setting the release >>> "code name" and uploading the binary artifacts to be made available for >>> downloading and taking care of all that business. >>> >>> Big thanks to everyone who put in extra effort to get this tag done. I >>> expect that the official release announcement will be happening later >>> this week. >>> >

I don't have any really good solution to this problem... On 03/17/2011 05:23 AM, Thomas Diesler wrote: > David, the AS test suite needs to be comprehensive - no doubt. However, > we have a release cycle that is different from AS and continuously test > a large set of OSGi functionality against AS7 trunk one a nightly basis. > > Following your suggested approach, I would need to duplicate every OSGi > example and functional test in the AS7 code base. Alternatively, I'm > suggesting to have a known "Code Freeze" date and give every subsystem > that has an external test suite a chance to verify/veto the intended > release code base. > > 1.0.0.Beta1 was broken for OSGi webapps because of last minute changes - > I'm looking for ways to possibly fix Beta1 and have a reasonable process > that avoids this to happen in the future. > > cheers > -thomas > > On 03/16/2011 02:30 PM, David M. Lloyd wrote: >> Thomas I think ultimately we need a comprehensive in-AS test suite. >> This is the only way we're going to be able to catch problems on an >> ongoing basis. I don't think we can afford to externally validate only >> once per release - I can absolutely guarantee that this will cause >> unexpected release delays. >> >> On 03/16/2011 04:27 AM, Thomas Diesler wrote: >>> Hi David, >>> >>> do we have a process that allows subsystem providers to verify a >>> potential AS7 release before it gets tagged? I have an extensive OSGi >>> testsuite that runs on a nightly basis against AS7 master. I noticed >>> this morning that this commit >>> >>> https://github.com/jbossas/jboss-as/commit/fd5696596545d9d9c2e4eb4c499bf3... >>> >>> >>> >>> broke OSGi webapp support again. The related issue, which I now >>> reopened, is https://issues.jboss.org/browse/JBAS-8940 >>> >>> Can we perhaps resolve this issue before Beta1 becomes generally >>> available? >>> To move forward I'll improve OSGi test coverage to a level were it >>> covers everything that is expected to work. >>> >>> cheers >>> -thomas >>> >>> On 03/16/2011 02:14 AM, David M. Lloyd wrote: >>>> I've pushed out a 7.0.0.Beta1-prerelease tag and updated upstream for >>>> Beta2 development. Later this week Jason will be setting the release >>>> "code name" and uploading the binary artifacts to be made available for >>>> downloading and taking care of all that business. >>>> >>>> Big thanks to everyone who put in extra effort to get this tag done. I >>>> expect that the official release announcement will be happening later >>>> this week. >>>> >>

The thing that needs to be solved is automating it. For beta releases, it can't be a mode of "do a code freeze, tag something and then poll project leads for acceptance." CRs and GA can be more time consuming, but in order to support weekly or bi-weekly beta releases there needs to be something where we can tag/branch, run some job and then get a green light. On 3/17/11 10:23 AM, Thomas Diesler wrote: > How about creating a branch after code freeze. Any change to the branch > must have a "very good reason" and would trigger a new test cycle. This > would include external test suites that we know about. In practise WS, > OSGi and possibly others would have to produce a stable hudson run on > the latest code freeze branch. > > On 03/17/2011 03:56 PM, David M. Lloyd wrote: >> I don't have any really good solution to this problem... >> >> On 03/17/2011 05:23 AM, Thomas Diesler wrote: >>> David, the AS test suite needs to be comprehensive - no doubt. However, >>> we have a release cycle that is different from AS and continuously test >>> a large set of OSGi functionality against AS7 trunk one a nightly basis. >>> >>> Following your suggested approach, I would need to duplicate every OSGi >>> example and functional test in the AS7 code base. Alternatively, I'm >>> suggesting to have a known "Code Freeze" date and give every subsystem >>> that has an external test suite a chance to verify/veto the intended >>> release code base. >>> >>> 1.0.0.Beta1 was broken for OSGi webapps because of last minute changes - >>> I'm looking for ways to possibly fix Beta1 and have a reasonable process >>> that avoids this to happen in the future. >>> >>> cheers >>> -thomas >>> >>> On 03/16/2011 02:30 PM, David M. Lloyd wrote: >>>> Thomas I think ultimately we need a comprehensive in-AS test suite. >>>> This is the only way we're going to be able to catch problems on an >>>> ongoing basis. I don't think we can afford to externally validate only >>>> once per release - I can absolutely guarantee that this will cause >>>> unexpected release delays. >>>> >>>> On 03/16/2011 04:27 AM, Thomas Diesler wrote: >>>>> Hi David, >>>>> >>>>> do we have a process that allows subsystem providers to verify a >>>>> potential AS7 release before it gets tagged? I have an extensive OSGi >>>>> testsuite that runs on a nightly basis against AS7 master. I noticed >>>>> this morning that this commit >>>>> >>>>> https://github.com/jbossas/jboss-as/commit/fd5696596545d9d9c2e4eb4c499bf3... >>>>> >>>>> >>>>> >>>>> broke OSGi webapp support again. The related issue, which I now >>>>> reopened, is https://issues.jboss.org/browse/JBAS-8940 >>>>> >>>>> Can we perhaps resolve this issue before Beta1 becomes generally >>>>> available? >>>>> To move forward I'll improve OSGi test coverage to a level were it >>>>> covers everything that is expected to work. >>>>> >>>>> cheers >>>>> -thomas >>>>> >>>>> On 03/16/2011 02:14 AM, David M. Lloyd wrote: >>>>>> I've pushed out a 7.0.0.Beta1-prerelease tag and updated upstream for >>>>>> Beta2 development. Later this week Jason will be setting the release >>>>>> "code name" and uploading the binary artifacts to be made available for >>>>>> downloading and taking care of all that business. >>>>>> >>>>>> Big thanks to everyone who put in extra effort to get this tag done. I >>>>>> expect that the official release announcement will be happening later >>>>>> this week. >>>>>> >>>> >> > -- Brian Stansberry Principal Software Engineer JBoss by Red Hat _______________________________________________ jboss-as7-dev mailing list jboss-as7-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

The osgi (or any other component) test suite can be easily be added as a downstream project to the AS 7 build. This afternoon I created two JBoss AS 7 testsuite jobs - one running with Sun JDK 1.6 and the other with OpenJDK 1.6: http://hudson.jboss.org/hudson/job/JBoss-AS-7.0.x-testSuite-sun16/ http://hudson.jboss.org/hudson/job/JBoss-AS-7.0.x-testSuite-openjdk/ The JBoss-AS-7.0.x-testSuite-openjdk is not yet published as it fails due to a compilation error ( http://pastebin.com/T3EH108H ). I've had the OpenJDK version upgraded to the latest and another job is queued. The JBoss-AS-7.0.x-testSuite-sun16 is not completing as it is hanging running the demos. I'm seeing similar issues with the latest JBoss AS 7 build which Aborts due to time out as it is hanging as well: http://hudson.jboss.org/hudson/job/JBoss-AS-7.0.x/

I'll look into it. Rajesh offered to test and upload the community releases starting with the CR1. For the AS 6 release, they followed this check list: http://community.jboss.org/wiki/JBossAS6xReleaseChecklist I created wiki to start identifying what needs to be done for an AS 7 release. You can start filling in the blanks here: http://community.jboss.org/wiki/JBossAS7xReleaseChecklist Shelly McGowan JBoss, by Red Hat ----- Original Message ----- From: "Jason Greene" <jgreene(a)redhat.com&gt; To: "Brian Stansberry" <brian.stansberry(a)redhat.com&gt; Cc: jboss-as7-dev(a)lists.jboss.org Sent: Thursday, March 17, 2011 6:01:51 PM Subject: Re: [jboss-as7-dev] JBoss AS 7.0.0.Beta1 tagged... Exactly. We need a Hudson run that is current upstream with the osgi testsuite. A two week cycle doesn't allow for a freeze plus days of testing. IMO we should just fix the osgi issue in beta2 which is a little over a week away. Sent from my iPhone On Mar 17, 2011, at 9:35 AM, Brian Stansberry <brian.stansberry(a)redhat.com&gt; wrote: > The thing that needs to be solved is automating it. For beta releases, > it can't be a mode of "do a code freeze, tag something and then poll > project leads for acceptance." CRs and GA can be more time consuming, > but in order to support weekly or bi-weekly beta releases there needs to > be something where we can tag/branch, run some job and then get a green > light. > > On 3/17/11 10:23 AM, Thomas Diesler wrote: >> How about creating a branch after code freeze. Any change to the branch >> must have a "very good reason" and would trigger a new test cycle. This >> would include external test suites that we know about. In practise WS, >> OSGi and possibly others would have to produce a stable hudson run on >> the latest code freeze branch. >> >> On 03/17/2011 03:56 PM, David M. Lloyd wrote: >>> I don't have any really good solution to this problem... >>> >>> On 03/17/2011 05:23 AM, Thomas Diesler wrote: >>>> David, the AS test suite needs to be comprehensive - no doubt. However, >>>> we have a release cycle that is different from AS and continuously test >>>> a large set of OSGi functionality against AS7 trunk one a nightly basis. >>>> >>>> Following your suggested approach, I would need to duplicate every OSGi >>>> example and functional test in the AS7 code base. Alternatively, I'm >>>> suggesting to have a known "Code Freeze" date and give every subsystem >>>> that has an external test suite a chance to verify/veto the intended >>>> release code base. >>>> >>>> 1.0.0.Beta1 was broken for OSGi webapps because of last minute changes - >>>> I'm looking for ways to possibly fix Beta1 and have a reasonable process >>>> that avoids this to happen in the future. >>>> >>>> cheers >>>> -thomas >>>> >>>> On 03/16/2011 02:30 PM, David M. Lloyd wrote: >>>>> Thomas I think ultimately we need a comprehensive in-AS test suite. >>>>> This is the only way we're going to be able to catch problems on an >>>>> ongoing basis. I don't think we can afford to externally validate only >>>>> once per release - I can absolutely guarantee that this will cause >>>>> unexpected release delays. >>>>> >>>>> On 03/16/2011 04:27 AM, Thomas Diesler wrote: >>>>>> Hi David, >>>>>> >>>>>> do we have a process that allows subsystem providers to verify a >>>>>> potential AS7 release before it gets tagged? I have an extensive OSGi >>>>>> testsuite that runs on a nightly basis against AS7 master. I noticed >>>>>> this morning that this commit >>>>>> >>>>>> https://github.com/jbossas/jboss-as/commit/fd5696596545d9d9c2e4eb4c499bf3... >>>>>> >>>>>> >>>>>> >>>>>> broke OSGi webapp support again. The related issue, which I now >>>>>> reopened, is https://issues.jboss.org/browse/JBAS-8940 >>>>>> >>>>>> Can we perhaps resolve this issue before Beta1 becomes generally >>>>>> available? >>>>>> To move forward I'll improve OSGi test coverage to a level were it >>>>>> covers everything that is expected to work. >>>>>> >>>>>> cheers >>>>>> -thomas >>>>>> >>>>>> On 03/16/2011 02:14 AM, David M. Lloyd wrote: >>>>>>> I've pushed out a 7.0.0.Beta1-prerelease tag and updated upstream for >>>>>>> Beta2 development. Later this week Jason will be setting the release >>>>>>> "code name" and uploading the binary artifacts to be made available for >>>>>>> downloading and taking care of all that business. >>>>>>> >>>>>>> Big thanks to everyone who put in extra effort to get this tag done. I >>>>>>> expect that the official release announcement will be happening later >>>>>>> this week. >>>>>>> >>>>> >>> >> > > > -- > Brian Stansberry > Principal Software Engineer > JBoss by Red Hat > _______________________________________________ > jboss-as7-dev mailing list > jboss-as7-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-as7-dev _______________________________________________ jboss-as7-dev mailing list jboss-as7-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev _______________________________________________ jboss-as7-dev mailing list jboss-as7-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

The osgi (or any other component) test suite can be easily be added as a downstream project to the AS 7 build. This afternoon I created two JBoss AS 7 testsuite jobs - one running with Sun JDK 1.6 and the other with OpenJDK 1.6: http://hudson.jboss.org/hudson/job/JBoss-AS-7.0.x-testSuite-sun16/ http://hudson.jboss.org/hudson/job/JBoss-AS-7.0.x-testSuite-openjdk/ The JBoss-AS-7.0.x-testSuite-openjdk is not yet published as it fails due to a compilation error ( http://pastebin.com/T3EH108H ). I've had the OpenJDK version upgraded to the latest and another job is queued. The JBoss-AS-7.0.x-testSuite-sun16 is not completing as it is hanging running the demos. I'm seeing similar issues with the latest JBoss AS 7 build which Aborts due to time out as it is hanging as well: http://hudson.jboss.org/hudson/job/JBoss-AS-7.0.x/ I'll look into it. Rajesh offered to test and upload the community releases starting with the CR1. For the AS 6 release, they followed this check list: http://community.jboss.org/wiki/JBossAS6xReleaseChecklist I created wiki to start identifying what needs to be done for an AS 7 release. You can start filling in the blanks here: http://community.jboss.org/wiki/JBossAS7xReleaseChecklist Shelly McGowan JBoss, by Red Hat ----- Original Message ----- From: "Jason Greene" <jgreene(a)redhat.com&gt; To: "Brian Stansberry" <brian.stansberry(a)redhat.com&gt; Cc: jboss-as7-dev(a)lists.jboss.org Sent: Thursday, March 17, 2011 6:01:51 PM Subject: Re: [jboss-as7-dev] JBoss AS 7.0.0.Beta1 tagged... Exactly. We need a Hudson run that is current upstream with the osgi testsuite. A two week cycle doesn't allow for a freeze plus days of testing. IMO we should just fix the osgi issue in beta2 which is a little over a week away. Sent from my iPhone On Mar 17, 2011, at 9:35 AM, Brian Stansberry <brian.stansberry(a)redhat.com&gt; wrote: > The thing that needs to be solved is automating it. For beta releases, > it can't be a mode of "do a code freeze, tag something and then poll > project leads for acceptance." CRs and GA can be more time consuming, > but in order to support weekly or bi-weekly beta releases there needs to > be something where we can tag/branch, run some job and then get a green > light. > > On 3/17/11 10:23 AM, Thomas Diesler wrote: >> How about creating a branch after code freeze. Any change to the branch >> must have a "very good reason" and would trigger a new test cycle. This >> would include external test suites that we know about. In practise WS, >> OSGi and possibly others would have to produce a stable hudson run on >> the latest code freeze branch. >> >> On 03/17/2011 03:56 PM, David M. Lloyd wrote: >>> I don't have any really good solution to this problem... >>> >>> On 03/17/2011 05:23 AM, Thomas Diesler wrote: >>>> David, the AS test suite needs to be comprehensive - no doubt. However, >>>> we have a release cycle that is different from AS and continuously test >>>> a large set of OSGi functionality against AS7 trunk one a nightly basis. >>>> >>>> Following your suggested approach, I would need to duplicate every OSGi >>>> example and functional test in the AS7 code base. Alternatively, I'm >>>> suggesting to have a known "Code Freeze" date and give every subsystem >>>> that has an external test suite a chance to verify/veto the intended >>>> release code base. >>>> >>>> 1.0.0.Beta1 was broken for OSGi webapps because of last minute changes - >>>> I'm looking for ways to possibly fix Beta1 and have a reasonable process >>>> that avoids this to happen in the future. >>>> >>>> cheers >>>> -thomas >>>> >>>> On 03/16/2011 02:30 PM, David M. Lloyd wrote: >>>>> Thomas I think ultimately we need a comprehensive in-AS test suite. >>>>> This is the only way we're going to be able to catch problems on an >>>>> ongoing basis. I don't think we can afford to externally validate only >>>>> once per release - I can absolutely guarantee that this will cause >>>>> unexpected release delays. >>>>> >>>>> On 03/16/2011 04:27 AM, Thomas Diesler wrote: >>>>>> Hi David, >>>>>> >>>>>> do we have a process that allows subsystem providers to verify a >>>>>> potential AS7 release before it gets tagged? I have an extensive OSGi >>>>>> testsuite that runs on a nightly basis against AS7 master. I noticed >>>>>> this morning that this commit >>>>>> >>>>>> https://github.com/jbossas/jboss-as/commit/fd5696596545d9d9c2e4eb4c499bf3... >>>>>> >>>>>> >>>>>> >>>>>> broke OSGi webapp support again. The related issue, which I now >>>>>> reopened, is https://issues.jboss.org/browse/JBAS-8940 >>>>>> >>>>>> Can we perhaps resolve this issue before Beta1 becomes generally >>>>>> available? >>>>>> To move forward I'll improve OSGi test coverage to a level were it >>>>>> covers everything that is expected to work. >>>>>> >>>>>> cheers >>>>>> -thomas >>>>>> >>>>>> On 03/16/2011 02:14 AM, David M. Lloyd wrote: >>>>>>> I've pushed out a 7.0.0.Beta1-prerelease tag and updated upstream for >>>>>>> Beta2 development. Later this week Jason will be setting the release >>>>>>> "code name" and uploading the binary artifacts to be made available for >>>>>>> downloading and taking care of all that business. >>>>>>> >>>>>>> Big thanks to everyone who put in extra effort to get this tag done. I >>>>>>> expect that the official release announcement will be happening later >>>>>>> this week. >>>>>>> >>>>> >>> >> > > > -- > Brian Stansberry > Principal Software Engineer > JBoss by Red Hat > _______________________________________________ > jboss-as7-dev mailing list > jboss-as7-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-as7-dev _______________________________________________ jboss-as7-dev mailing list jboss-as7-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev _______________________________________________ jboss-as7-dev mailing list jboss-as7-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev