[JBoss-dev] RE: microcontainer-head-testsuite Build Failed
This is complaining about not seeing the test profileservice from the container module: _default:compile-classes: [mkdir] Created dir: /services/cruisecontrol/work/checkout/microcontainer-head-testsuite/kernel/output/classes-tests [javac] Compiling 167 source files to /services/cruisecontrol/work/checkout/microcontainer-head-testsuite/kernel/output/classes-tests [javac] /services/cruisecontrol/work/checkout/microcontainer-head-testsuite/kernel/src/tests/org/jboss/test/profileservice/support/Simple1PSBootstrap.java:34: package org.jboss.test.profileservice.simple1 does not exist [javac] import org.jboss.test.profileservice.simple1.ProfileServiceImpl; Looking at the kernel/built-test.xml classpath its only pulling in the jboss-container.jar and this contains no test classes. The issue is that the profileservice test impl should be testable from the container module as this has no dependency on the kernel bootstrap classes that are failing to compile. The container module has no dependency on the kernel module. It seem like a jboss-container-test.jar is needed. Also, what allows eclipse to see these container test classes from the kernel project, just the reference to the container project in the Java Build Path/Projects tab? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 30, 2006 4:37 AMTo: jboss-development@lists.sourceforge.net; QA; Scott M StarkSubject: microcontainer-head-testsuite Build FailedImportance: High View results here - http://cruisecontrol.jboss.com/cc/buildresults/microcontainer-head-testsuite?log=log20060530070401 BUILD FAILED Ant Error Message:/services/cruisecontrol/work/scripts/build-microcontainer-head-testsuite.xml:84: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-microcontainer-head-testsuite.xml:142: See tests.log in Build Artifacts for details. Date of build:05/30/2006 07:04:01 Time to build:30 minutes 46 seconds Last changed:05/26/2006 13:17:34 Last log entry:Add profile service test jars Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (first 50 of 34) 1.13 modified starksm /build-test.xml Add profile service test jars 1.1 added starksm src/tests/org/jboss/test/profileservice/support/ProfileServiceBootstrap.java First pass at kernel bootstrap with profileservice test 1.1 added starksm src/tests/org/jboss/test/profileservice/support/SecurityActions.java First pass at kernel bootstrap with profileservice test 1.1 added starksm src/tests/org/jboss/test/profileservice/support/Simple1PSBootstrap.java First pass at kernel bootstrap with profileservice test 1.1 added starksm src/tests/org/jboss/test/profileservice/test/SimplePSTestCase.java First pass at kernel bootstrap with profileservice test 1.1 added starksm src/tests/org/jboss/test/profileservice/test/SimplePSTestCase.properties First pass at kernel bootstrap with profileservice test 1.1 added starksm src/tests/org/jboss/test/profileservice/profiles/p0/beans/DataSourceThing.java First pass at kernel bootstrap with profileservice test 1.1 added starksm src/tests/org/jboss/test/profileservice/profiles/p0/beans/DataSourceView.java First pass at kernel bootstrap with profileservice test 1.1 added starksm src/tests/org/jboss/test/profileservice/profiles/p0/beans/JCAMgr.java First pass at kernel bootstrap with profileservice test 1.1 added starksm src/tests/org/jboss/test/profileservice/profiles/p0/beans/NamingService.java First pass at kernel bootstrap with profileservice test 1.1 added starksm src/tests/org/jboss/test/profileservice/profiles/p0/beans/PoolView.java First pass at kernel bootstrap with profileservice test 1.1 added starksm src/tests/org/jboss/test/profileservice/profiles/p0/beans/TxMgr.java First pass at kernel bootstrap with profileservice test 1.1 added starksm src/tests/org/jboss/test/profileservice/profiles/p0/ifaces/IJCAMgr.java First pass at kernel bootstrap with profileservice test 1.1 added starksm src/tests/org/jboss/test/profileservice/profiles/p0/ifaces/INamingService.java First pass at
[JBoss-dev] RE: microcontainer-head-testsuite Build Failed
On Tue, 2006-05-30 at 09:49 -0500, Scott M Stark wrote: This is complaining about not seeing the test profileservice from the container module: _default:compile-classes: [mkdir] Created dir: /services/cruisecontrol/work/checkout/microcontainer-head-testsuite/kernel/output/classes-tests [javac] Compiling 167 source files to /services/cruisecontrol/work/checkout/microcontainer-head-testsuite/kernel/output/classes-tests [javac] /services/cruisecontrol/work/checkout/microcontainer-head-testsuite/kernel/src/tests/org/jboss/test/profileservice/support/Simple1PSBootstrap.java:34: package org.jboss.test.profileservice.simple1 does not exist [javac] import org.jboss.test.profileservice.simple1.ProfileServiceImpl; Looking at the kernel/built-test.xml classpath its only pulling in the jboss-container.jar and this contains no test classes. The issue is that the profileservice test impl should be testable from the container module as this has no dependency on the kernel bootstrap classes that are failing to compile. The container module has no dependency on the kernel module. It seem like a jboss-container-test.jar is needed. I'm not sure what the question is here? If you need the jboss-container-test.jar in the MC testsuite, you'll need to include it in the classpath in kernel/build-test.xml Also, what allows eclipse to see these container test classes from the kernel project, just the reference to the container project in the Java Build Path/Projects tab? It depends how you configure the project. The default is to include the whole project. -- Adrian Brock Chief Scientist JBoss Inc. --- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnkkid=107521bid=248729dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] RE: microcontainer-head-testsuite Build Failed
It seem like a jboss-container-test.jar is needed. I'm not sure what the question is here? If you need the jboss-container-test.jar in the MC testsuite, you'll need to include it in the classpath in kernel/build-test.xml The question is wether a jboss-container-test.jar is what we want to add to allow container test impls to be accessible to the kernel tests. I did see how the kernel/build-test.xml is pulling in the container classes. Also, what allows eclipse to see these container test classes from the kernel project, just the reference to the container project in the Java Build Path/Projects tab? It depends how you configure the project. The default is to include the whole project. I'm using the existing module .project files. --- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnkkid7521bid$8729dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] RE: microcontainer-head-testsuite Build Failed
On Tue, 2006-05-30 at 10:08 -0500, Scott M Stark wrote: It seem like a jboss-container-test.jar is needed. I'm not sure what the question is here? If you need the jboss-container-test.jar in the MC testsuite, you'll need to include it in the classpath in kernel/build-test.xml The question is wether a jboss-container-test.jar is what we want to add to allow container test impls to be accessible to the kernel tests. I did see how the kernel/build-test.xml is pulling in the container classes. I generally duplicate test support classes rather than having one test depend upon something from another test. Let alone dependencies across projects. ;-) -- Adrian Brock Chief Scientist JBoss Inc. --- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnkkid=107521bid=248729dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] RE: microcontainer-head-testsuite Build Failed
For now I'm going to move these prototype test classes into the kernel test source tree as there is not much point to testing them without a kernel. I generally duplicate test support classes rather than having one test depend upon something from another test. Let alone dependencies across projects. ;-) -- Adrian Brock Chief Scientist JBoss Inc. --- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnkkid7521bid$8729dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] RE: microcontainer-head-testsuite Build Failed
Not anymore they don't. :-) On Wed, 2006-05-03 at 10:41 -0500, Rajesh Rajasekaran wrote: The kernel aop-mc-int build.xml still uses jboss.container.classpath. http://cruisecontrol.jboss.com/cc/artifacts/microcontainer-head-testsuite/20060502220252/compile.log Buildfile: ../checkout/microcontainer-head-testsuite/kernel/build.xml BUILD FAILED /services/cruisecontrol/work/checkout/microcontainer-head-testsuite/tools/etc/buildmagic/buildmagic.ent:456: Reference jboss.container.classpath not found. __ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 02, 2006 9:29 PM To: Adrian Brock; Bill Burke; jboss-development@lists.sourceforge.net; QA; Scott M Stark; Thomas Diesler Subject: microcontainer-head-testsuite Build Failed Importance: High View results here - http://cruisecontrol.jboss.com/cc/buildresults/microcontainer-head-testsuite?log=log20060502220252 BUILD FAILED Ant Error Message: /services/cruisecontrol/work/scripts/build-microcontainer-head-testsuite.xml:72: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-microcontainer-head-testsuite.xml:119: See compile.log in Build Artifacts for details. Date of build: 05/02/2006 22:02:52 Time to build: 25 minutes 22 seconds Last changed: 05/02/2006 16:18:48 Last log entry: Temporary fix for optional compilation with JDK1.4 Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (first 50 of 43) 1.25 modified adrian
[JBoss-dev] RE: microcontainer-head-testsuite Build Failed
The next iteration of the profile service is in progress based on a day I spent with Charles going over the admin usecases in more detail. To finish a real prototype the vdf/vfs/classloader need to exist in some form. -Original Message- From: Adrian Brock Sent: Friday, April 28, 2006 6:19 AM To: QA Cc: Bill Burke; jboss-development@lists.sourceforge.net Subject: Re: microcontainer-head-testsuite Build Failed Did I miss the discussion, roadmap, JIRA tasks on this deployer prototype? How does this relate to what we've already agreed for the aspectized deployers? i.e. The VDF. The aspectized deployers will be in a separate project *NOT* the Microcontainer which is an IOC container or more accurately a dependency state machine. Even the current microcontainer xml deployer will move to that project. In fact, I've already started my own prototype of an embedded container that will based on the: profile service +aspectized deployers +microcontainer +integration abstractions +optional features like aop integration, alternate classloaders, etc. But, it is currently fifth on the list of my priorities: 1) MC/AOP integration 2) JMX/MC integration in jboss-head 3) Aspectized deployers in jboss-head 4) Profile service (currently being prototyped by Scott) 5) Embedded Mind you, these priorties change every couple of months. :-) Remember Tripoli or POJOServer? --- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid0709bid3057dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Re: microcontainer-head-testsuite Build Failed
Did I miss the discussion, roadmap, JIRA tasks on this deployer prototype? How does this relate to what we've already agreed for the aspectized deployers? i.e. The VDF. The aspectized deployers will be in a separate project *NOT* the Microcontainer which is an IOC container or more accurately a dependency state machine. Even the current microcontainer xml deployer will move to that project. In fact, I've already started my own prototype of an embedded container that will based on the: profile service +aspectized deployers +microcontainer +integration abstractions +optional features like aop integration, alternate classloaders, etc. But, it is currently fifth on the list of my priorities: 1) MC/AOP integration 2) JMX/MC integration in jboss-head 3) Aspectized deployers in jboss-head 4) Profile service (currently being prototyped by Scott) 5) Embedded Mind you, these priorties change every couple of months. :-) Remember Tripoli or POJOServer? On Fri, 2006-04-28 at 06:51 -0400, [EMAIL PROTECTED] wrote: View results here - http://cruisecontrol.jboss.com/cc/buildresults/microcontainer-head-testsuite?log=log20060428062444 BUILD FAILED Ant Error Message: /services/cruisecontrol/work/scripts/build-microcontainer-head-testsuite.xml:41: Exit code: 1 See compilejbosshead.log in Build Artifacts for details. Date of build: 04/28/2006 06:24:44 Time to build: 25 minutes 34 seconds Last changed: 04/27/2006 19:45:34 Last log entry: Deployer prototype Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (first 50 of 12) 1.10 modified bill /build-test.xml Deployer prototype 1.24 modified bill /build.xml Deployer prototype 1.1 added bill src/main/org/jboss/deployment/DeploymentImpl.java Deployer prototype 1.1 added bill src/main/org/jboss/deployment/KernelErrorsLogger.java Deployer prototype 1.1 added bill src/main/org/jboss/deployment/MainDeployerImpl.java Deployer prototype 1.3 modified bill src/main/org/jboss/vfs/spi/VirtualFile.java deployer prototype. added stuff to VFS to:1) allow you to get all children recursively from any VirtualFile2) Fix some bugs here and there. 1.1 added bill src/main/org/jboss/vfs/spi/VirtualFileFilter.java deployer prototype. added stuff to VFS to:1) allow you to get all children recursively from any VirtualFile2) Fix some bugs here and there. 1.4 modified bill src/main/org/jboss/vfs/file/FileImpl.java deployer prototype. added stuff to VFS to:1)
