August 2006 - jboss-development - Jboss List Archives

jboss-head-testsuite-1.5 Build Failed

by qa＠jboss.com

18 years, 7 months

1
0
0 / 0

ejb3-head-testsuite Build Failed

by qa＠jboss.com

18 years, 7 months

1
0
0 / 0

RE: [JBoss-dev] Microcontainer/Breakout Strategy

by Scott M Stark

I have moved the https://svn.jboss.org/repos/jbossas/trunk/test to https://svn.jboss.org/repos/jbossas/projects/test/trunk/test since it already has a repository binary. This project needs to be converted to maven2 at this point. ________________________________ From: jboss-development-bounces(a)lists.jboss.org [mailto:jboss-development-bounces@lists.jboss.org] On Behalf Of Scott M Stark Sent: Wednesday, August 02, 2006 5:43 PM To: JBoss.org development list Subject: RE: [JBoss-dev] Microcontainer/Breakout Strategy Another question is integration of projects like test. This either needs to be a binary integration, or possibly a svn link. ________________________________ From: jboss-development-bounces(a)lists.jboss.org [mailto:jboss-development-bounces@lists.jboss.org] On Behalf Of Ryan Campbell Sent: Sunday, July 30, 2006 3:22 PM To: JBoss.org development list Subject: [JBoss-dev] Microcontainer/Breakout Strategy Now that we are in SVN, extracting a project out is just a svn move. The question is how do we want to do this? Where do we want microcontainer, and further extracted projects to go? Microcontainer is currently under /archives/trunk, which should be marked as read only. Ruel recommended we have a directory called projects, under which we put extracted projects: https://svn.jboss.org/repos/jbossas/projects/microcontainer <https://svn.jboss.org/repos/jbossas/projects/microcontainer> https://svn.jboss.org/repos/jbossas/projects/aop <https://svn.jboss.org/repos/jbossas/projects/aop> https://svn.jboss.org/repos/jbossas/projects/ejb3 <https://svn.jboss.org/repos/jbossas/projects/ejb3> etc. Thoughts?

18 years, 7 months

1
0
0 / 0

jboss-portal-2.4-testsuite Build Completed With Testsuite Errors

by qa＠jboss.com

18 years, 7 months

1
0
0 / 0

jbossws-head-testsuite-1.5 Build Completed With Testsuite Errors

by qa＠jboss.com

18 years, 7 months

1
0
0 / 0

RE: [JBoss-dev] Re: AOP 2.0 alpha with dependencies

by Scott M Stark

One issue is that the mc projects (container, dependency, kernel) and aop are now read-only in cvs, and the https://svn.jboss.org/repos/jbossas/archives/trunk/ location. These need to be copied from there to a writable location. Its been suggested that such breakouts happen under a https://svn.jboss.org/repos/jbossas/projects root: https://svn.jboss.org/repos/jbossas/projects/microcontainer https://svn.jboss.org/repos/jbossas/projects/aop I need to make some changes to the vfs code in the mc container project so I'm going to setup the https://svn.jboss.org/repos/jbossas/projects/microcontainer. You should do the same for aop Kabir. > -----Original Message----- > From: jboss-development-bounces(a)lists.jboss.org > [mailto:jboss-development-bounces@lists.jboss.org] On Behalf > Of Adrian Brock > Sent: Wednesday, August 02, 2006 6:39 AM > To: Kabir Khan > Cc: 'JBoss.org development list'; 'Shigeru Chiba' > Subject: [JBoss-dev] Re: AOP 2.0 alpha with dependencies > > It should be 2.0.0M1 (really 2.0.0-Beta1 under the new naming > conventions) > > The only problem is the MetaData integration (which also affects AOP). > > i.e. use org.jboss.metadata instead of org.jboss.repository > > If this is not a final release, I can live with 2.0.0-Beta1 > (and aop) using the old meta data repository. > > The only thing is to update the MC documentation with the > changes done in 2.0.0 > > On Tue, 2006-08-01 at 10:40 +0200, Kabir Khan wrote: > > Adrian: > > Do you see any problems with an MC 2.0.alpha1 at this stage? It > > probably doesn't need to be a full-blown release, just something > > tagged in cvs and available in the repository? > > -- > xxxxxxxxxxxxxxxxxxxxxxxxxxx > Adrian Brock > Chief Scientist > JBoss a division of Red Hat > xxxxxxxxxxxxxxxxxxxxxxxxxxx > > _______________________________________________ > jboss-development mailing list > jboss-development(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-development >

18 years, 7 months

1
0
0 / 0

JBoss Portal 2.4.0.CR3 released

by Rali Genova

JBoss Portal 2.4.0.CR3 was released today and is available for download from Sourceforge - http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=8 4509&release_id=415694 This release also includes a clustered distribution of JBoss Portal. Thanks, Rali Genova JBoss QA

18 years, 7 months

1
0
0 / 0

jboss-common.jar from repository was not compiled with javac.debug=on

by Ovidiu Feodorov

FYI

18 years, 7 months

1
0
0 / 0

jboss-remoting-testsuite-1.5 Build Completed With Testsuite Errors

by qa＠jboss.com

18 years, 7 months

1
0
0 / 0

SubversionMigrationGuide/JEE5_TCK branch

by Scott M Stark

I added section to the svn migration guide: http://wiki.jboss.org/wiki/Wiki.jsp?page=SubversionMigrationGuide about while the trunk is being migrated to the MC and VDF framework, it will be unstable. Work on TCK/CTS should be based on the https://svn.jboss.org/repos/jbossas/branches/JEE5_TCK branch with any changes merged to head. If the change is to a deployer that is in flux, create a jira issue with the svn patch set so it can be integrated latter. xxxxxxxxxxxxxxxxxxxxxxxxxxxx Scott Stark VP Architecture & Technology JBoss, a division of Red Hat xxxxxxxxxxxxxxxxxxxxxxxxxxxx

18 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-development August 2006