Common project dependency

[adrian.brock]

I've fixed the dependency on jboss-common-core to be 2.2.1-SNAPSHOT
instead of 2.0.3.GA from the jboss-vfs dependency.

Similar to this problem:
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077827#4077827

This fixes the failing tests where the container tests couldn't find the javabean schema.

[alesj]

Similar to this problem:
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077827#4077827

I still get this problem:
- from Hudson: http://dev45.qa.atl.jboss.com:8585/hudson/job/Microcontainer/org.jboss.microcontainer$jboss-container/367/console

It's the same locally and on my TeamCity:

# /opt/buildAgent/work/Server/JBoss_Microcontainer/container/src/main/org/jboss/beans/info/plugins/AbstractBeanInfoFactory.java:[147,38] type org.jboss.util.collection.WeakValueHashMap does not take parameters

The 2.0.4.GA is pulled in from somewhere - and appears in classpath before 2.2.1.
I saw some pom.xml changes from PaulG, thought this is what he was aiming at - info from linked post.

btw: I saw there is new jbossxb 2.0.4.GA in repo - under org.jboss groupId. Should I move MC to use that?

[adrian.brock]

"alesj" wrote:

The 2.0.4.GA is pulled in from somewhere - and appears in classpath before 2.2.1.
I saw some pom.xml changes from PaulG, thought this is what he was aiming at - info from linked post.

It works fine for me, so this is obviously non-deterministic and needs fixing
in Maven itself. I don't see how we can do a release when two people get
different dependencies from a build?

btw: I saw there is new jbossxb 2.0.4.GA in repo - under org.jboss groupId. Should I move MC to use that?

We're supposed to be doing the beta4 release sometime over the next week
so we don't really want to be changing things unnecessarily at this late stage.

However, it passes the testsuite then I'm ok with it.

[alesj]

We're supposed to be doing the beta4 release sometime over the next week
so we don't really want to be changing things unnecessarily at this late stage.

However, it passes the testsuite then I'm ok with it.

I'll check this once the Maven issue is resolved.
And if it's OK, I'll do the change.

btw: I saw there are some Managed tests failing as well, for some time now. Is this also the consequence of Maven issue?

[pgier]

I added an exclusion that should fix this.
See this thread: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=116996

[adrian.brock]

"alesj" wrote:

btw: I saw there are some Managed tests failing as well, for some time now. Is this also the consequence of Maven issue?

I don't think so. Scott broke some of these tests, I fixed them, then Scott broke some
other ones. It's basically a WIP so I wouldn't worry about it until Scott says it is finished. :-)

[pgier]

I made a couple of changes to the container pom to clean up the dependency warnings.
I noticed there are a couple of transitive deps on logging-spi 2.0.4. But the direct dependency is on 2.0.3. Should all of mc be updated to use 2.0.4?

[starksm64]

I have fixed the current managed failures. Right now I'm validating use of the managed object changes in my jboss5 workspace by updating the jca layer with the management annotations to get the ProfileServiceUnitTestCase running.

[adrian.brock]

"pgier" wrote:
I made a couple of changes to the container pom to clean up the dependency warnings.
I noticed there are a couple of transitive deps on logging-spi 2.0.4. But the direct dependency is on 2.0.3. Should all of mc be updated to use 2.0.4?

I think this change broke the build? I had to add an explicit dependency
on jboss-vfs to make the deployers-vfs-spi project compile.

What's the difference between 2.0.4 and 2.0.3?