As discusses previously, the VFS3 integration in JBoss AS is planned for for Monday, March 1st. At this point we have all the dependent projects released with the necessary VFS3 changes integrated. So we should be all set to start the integration on Monday. There will be a lot of changes to merge in, so I ask that all commits to AS trunk be suspended durning the integration. So if you could please have all outstanding changes committed by 4PM UTC on Monday. The goal is to have changes to the trunk suspended no more than 48 hours. I will send out a notice as soon as it is available, which hopefully will be earlier than planned. Also, I have created a job on the hudson server to run the AS testsuite against the VFS3 integration branch. There are currently around 30 test failures. I will get the job results published to the hudson.jboss.org site so all can see the failures. I have identified the root cause of several of the failures, but I would appreciate it if everyone can take a look and see if anything jumps out. Let me know if you have any questions or concerns. Thanks, -- John Bailey JBoss by Red Hat -- _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development

I can merge the changes into the trunk and we can wait to check in the changes until deployers 2.2.0.Alpha3 is ready. Do you think there is a good chance it will be ready by 4PM UTC?

> I've created a new JIRA release target for Deployers -- 2.2.0.Alpha3. > * https://jira.jboss.org/jira/browse/JBDEPLOY-244 > which includes your declarative structure deployer fix.

> Adrian's JBDEPLOY-226 is also moved there, as he's probably done with changes? > * https://jira.jboss.org/jira/browse/JBDEPLOY-226

The VFS3 integration in AS trunk is complete. I have checked out a fresh copy of the trunk and successfully built the server. The next step is to see the results of the Hudson runs. Please update your local copies to confirm it runs somewhere other than my machine. :) There is an error being logged at shutdown from the Weld integration deployer. I believe it only occurs with there are no JNDI entries bound into the 'app' context. I will be looking into this further. Let me know if anyone runs into any issues. john On Feb 26, 2010, at 3:07 PM, John Bailey wrote: > As discusses previously, the VFS3 integration in JBoss AS is planned for for Monday, March 1st. At this point we have all the dependent projects released with the necessary VFS3 changes integrated. So we should be all set to start the integration on Monday. > > There will be a lot of changes to merge in, so I ask that all commits to AS trunk be suspended durning the integration. So if you could please have all outstanding changes committed by 4PM UTC on Monday. The goal is to have changes to the trunk suspended no more than 48 hours. I will send out a notice as soon as it is available, which hopefully will be earlier than planned. > > Also, I have created a job on the hudson server to run the AS testsuite against the VFS3 integration branch. There are currently around 30 test failures. I will get the job results published to the hudson.jboss.org site so all can see the failures. I have identified the root cause of several of the failures, but I would appreciate it if everyone can take a look and see if anything jumps out. > > Let me know if you have any questions or concerns. > > Thanks, > -- > John Bailey > JBoss by Red Hat > -- > > > > _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development

There is an error being logged at shutdown from the Weld integration deployer. I believe it only occurs with there are no JNDI entries bound into the 'app' context. I will be looking into this further.

The Hudson job has finished running the testsuite. There were 15 failures. I will continue looking at the failures, but any help would be great. http://hudson.qa.jboss.com/hudson/view/JBoss AS/job/JBoss-AS-6.0.x-testSuite-sun16/579 At this time I think it is safe to say we can open the trunk back up for development, but it would be good to try and tackle the test failures right off. Let me know if you have any questions. john On Mar 1, 2010, at 12:58 PM, John Bailey wrote: > The VFS3 integration in AS trunk is complete. I have checked out a fresh copy of the trunk and successfully built the server. The next step is to see the results of the Hudson runs. > > Please update your local copies to confirm it runs somewhere other than my machine. :) > > There is an error being logged at shutdown from the Weld integration deployer. I believe it only occurs with there are no JNDI entries bound into the 'app' context. I will be looking into this further. > > Let me know if anyone runs into any issues. > > john > > On Feb 26, 2010, at 3:07 PM, John Bailey wrote: > >> As discusses previously, the VFS3 integration in JBoss AS is planned for for Monday, March 1st. At this point we have all the dependent projects released with the necessary VFS3 changes integrated. So we should be all set to start the integration on Monday. >> >> There will be a lot of changes to merge in, so I ask that all commits to AS trunk be suspended durning the integration. So if you could please have all outstanding changes committed by 4PM UTC on Monday. The goal is to have changes to the trunk suspended no more than 48 hours. I will send out a notice as soon as it is available, which hopefully will be earlier than planned. >> >> Also, I have created a job on the hudson server to run the AS testsuite against the VFS3 integration branch. There are currently around 30 test failures. I will get the job results published to the hudson.jboss.org site so all can see the failures. I have identified the root cause of several of the failures, but I would appreciate it if everyone can take a look and see if anything jumps out. >> >> Let me know if you have any questions or concerns. >> >> Thanks, >> -- >> John Bailey >> JBoss by Red Hat >> -- >> >> >> >> > > > > -- John Bailey JBoss by Red Hat -- _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development

I *think* the problem here is due to VFSDeploymentClassLoaderPolicyModule. getDynamicClassRoot() returning null when setting up the AOP stuff @Override public URL getDynamicClassRoot() { return getDeploymentUnit().getAttachment("DYNAMIC_CLASS_URL_KEY", URL.class); } In other words the attachment has not been set yet, probably because this is triggered from FilteredAnnotationRepositoryDeployer/ModuleAnnotationScanner which I guess is before DYNAMIC_CLASS_URL_KEY gets set or it is not getting set at all. Does anybody remember where it gets set/used to get set? On 2 Mar 2010, at 16:37, Kabir Khan wrote: > I will look at the 6 aop ones tomorrow. > On 2 Mar 2010, at 00:15, John Bailey wrote: > >> The Hudson job has finished running the testsuite. There were 15 failures. I will continue looking at the failures, but any help would be great. >> >> http://hudson.qa.jboss.com/hudson/view/JBoss AS/job/JBoss-AS-6.0.x-testSuite-sun16/579 >> >> At this time I think it is safe to say we can open the trunk back up for development, but it would be good to try and tackle the test failures right off. >> >> Let me know if you have any questions. >> >> john >> >> >> >> >> On Mar 1, 2010, at 12:58 PM, John Bailey wrote: >> >>> The VFS3 integration in AS trunk is complete. I have checked out a fresh copy of the trunk and successfully built the server. The next step is to see the results of the Hudson runs. >>> >>> Please update your local copies to confirm it runs somewhere other than my machine. :) >>> >>> There is an error being logged at shutdown from the Weld integration deployer. I believe it only occurs with there are no JNDI entries bound into the 'app' context. I will be looking into this further. >>> >>> Let me know if anyone runs into any issues. >>> >>> john >>> >>> On Feb 26, 2010, at 3:07 PM, John Bailey wrote: >>> >>>> As discusses previously, the VFS3 integration in JBoss AS is planned for for Monday, March 1st. At this point we have all the dependent projects released with the necessary VFS3 changes integrated. So we should be all set to start the integration on Monday. >>>> >>>> There will be a lot of changes to merge in, so I ask that all commits to AS trunk be suspended durning the integration. So if you could please have all outstanding changes committed by 4PM UTC on Monday. The goal is to have changes to the trunk suspended no more than 48 hours. I will send out a notice as soon as it is available, which hopefully will be earlier than planned. >>>> >>>> Also, I have created a job on the hudson server to run the AS testsuite against the VFS3 integration branch. There are currently around 30 test failures. I will get the job results published to the hudson.jboss.org site so all can see the failures. I have identified the root cause of several of the failures, but I would appreciate it if everyone can take a look and see if anything jumps out. >>>> >>>> Let me know if you have any questions or concerns. >>>> >>>> Thanks, >>>> -- >>>> John Bailey >>>> JBoss by Red Hat >>>> -- >>>> >>>> >>>> >>>> >>> >>> >>> >>> >> >> -- >> John Bailey >> JBoss by Red Hat >> -- >> >> >> >> >> >> _______________________________________________ >> jboss-development mailing list >> jboss-development(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jboss-development > > > _______________________________________________ > jboss-development mailing list > jboss-development(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-development _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development

This thread contains reference to InMemoryClassesDeployer http://community.jboss.org/message/314960#314960, which I cannot find anywhere. http://fisheye.jboss.org/browse/JBossAS/projects/jboss-deployers/branches... shows that it does not exist in VFS 3. So what do I do?