-
15. Re: mc release prep
"adrian@jboss.org" wrote:
"scott.stark@jboss.org" wrote:
The aop 2.0.0.alpha6 and mc 2.0.0.Beta4 release are ready, but there is a temp AspectDeployer that is broken. I assume this is due to the class loading being in flux. I have commented out the JBossScopedClassLoaderHelper usage.
The latest version of AOP contains an updated AspectDeployer in the
asintegration project. The temp version in "system" is then redundant and should
be deleted with the configuration changed in the bootstrap-beans.xml, etc.
I am verifying this at the moment, stay tuned -
16. Re: mc release prep
Why the repository component of that release does not declare any imports ?
http://repository.jboss.com/jboss/microcontainer/2.0.0.Beta4/component-info.xml
It makes MC very difficult to be consumed by other projects."scott.stark@jboss.org" wrote:
The basic mc 2.0.0.Beta4 is released and is now used by jboss5. The aggregate assembly seems broken so I don't know if we are putting out a standalone release as well. -
17. Re: mc release prep
"scott.stark@jboss.org" wrote:
The basic mc 2.0.0.Beta4 is released and is now used by jboss5.
Why did you release 2.0.0.Beta4 without first a snapshot of the latest stuff in jboss-head?
I asked you not to do this. Maybe I should have created a blocker JIRA issue for it?
There are a number of issues I wanted to tidyup (like investigating all those
error messages at undeployment from @JMX) before we did the Beta4 release.
I couldn't do this before, because I wasn't sure of the aop status
so I didn't want to update aop-mc-int.
This will have to wait until RC1 now :-( -
18. Re: mc release prep
I have made the switch to use the AspectDeployer from AOP
http://jira.jboss.com/jira/browse/JBAS-4537 -
19. Re: mc release prep
"adrian@jboss.org" wrote:
Why did you release 2.0.0.Beta4 without first a snapshot of the latest stuff in jboss-head?
This will have to wait until RC1 now :-(
Should we fix those and re-do a new beta ASAP? -
20. Re: mc release prep
"sacha.labourey@jboss.com" wrote:
"adrian@jboss.org" wrote:
Why did you release 2.0.0.Beta4 without first a snapshot of the latest stuff in jboss-head?
This will have to wait until RC1 now :-(
Should we fix those and re-do a new beta ASAP?
Actually, I don't think the problem is really in aop-mc-int anyway.
The issue is that the default aspect from aop-mc-int registers directly
with the MBeanServer.
But the thing that gets registered implements ServiceMBeanSupport
so it "lazily" registers itself with the ServiceController.
This leads to double unregistration.
Inside the appserver, the advice should be replaced with one that
(un)registers with the ServiceController. -
21. Re: mc release prep
"adrian@jboss.org" wrote:
Inside the appserver, the advice should be replaced with one that
(un)registers with the ServiceController.
I've created this task:
http://jira.jboss.com/jira/browse/JBMICROCONT-206
We should be able to just replace the advice for JBoss5-beta3
but it would be better to have this advice be more extensible instead of
repeating code (a task for MC2-RC1). -
22. Re: mc release prep
"adrian@jboss.org" wrote:
"scott.stark@jboss.org" wrote:
Like I said before. The container project (and the classloader project)
shouldn't be in the MC build. They are only there because the MC was initially
the major consumer while we developed them.
If/when this is split out, can we have a separate artifacts from container for metadata etc. for JDK 1.4 like we do for JDK 5? -
23. Re: mc release prep
I created the pom-jdk14.xml in each of the projects for the jdk14 artifacts. When you build with "mvn -f pom-jdk14.xml" it will build the jdk14 stuff, and you can deploy it as
jboss-container-jdk14, jboss-ejb-api-jdk14, etc. -
24. Re: mc release prep
Hmm, the snapshots with the latest mc contents have been in head all week. I guess that was not communicated well enough. We can replace the Beta4 if you want.
-
25. Re: mc release prep
"julien@jboss.com" wrote:
Why the repository component of that release does not declare any imports ?
http://repository.jboss.com/jboss/microcontainer/2.0.0.Beta4/component-info.xml
It makes MC very difficult to be consumed by other projects."scott.stark@jboss.org" wrote:
The basic mc 2.0.0.Beta4 is released and is now used by jboss5. The aggregate assembly seems broken so I don't know if we are putting out a standalone release as well.
I'll update this from the maven pom dependencies today. -
26. Re: mc release prep
"adrian@jboss.org" wrote:
"scott.stark@jboss.org" wrote:
So there is a circular dependencies between mc and aop at least in terms of how the mc is now setup as an assembly type of project. If I try to release jboss-container, it depends on the parent jboss-microcontainer from build/pom.xml and does not have a container/{trunk,tags} structure for an individual release.
aop depends on jboss-container. I can manually release jboss-container, but how should these projects bet setup so that the mvn release process works for such interdependent projects?
Like I said before. The container project (and the classloader project)
shouldn't be in the MC build. They are only there because the MC was initially
the major consumer while we developed them.
ok, a task for that: http://jira.jboss.com/jira/browse/JBMICROCONT-207