And it looks like the upgrade from wadi 2.0m1 to 2.0m2-SNAPSHOT is
non-trivial. I see a ton of "org.codehaus.wadi.gridstate" related
symbols missing and a bunch of things like missing "ProxiedLocation"
and "InvocationContext".
I think someone who knows all this wadi muck is going to need to look
at this.
We need to get this resolved so we don't ship different versions of
activemq/activeio/activecluster junk with G.
--jason
On Oct 25, 2006, at 6:11 PM, Jason Dillon wrote:
Blah... wadi needs to be upgraded as well :-(
--jason
On Oct 25, 2006, at 5:27 PM, Dain Sundstrom wrote:
Submit a patch.
-dain
On Oct 25, 2006, at 5:21 PM, Jason Dillon wrote:
Looks like openejb2 is still using old ActiveMQ jars.
Can we get those deps upgraded plz?
--jason
On Oct 25, 2006, at 5:11 PM, Jason Dillon wrote:
Anyone know why we are still seeing old activemq and
activecluster bits?
<snip>
[WARNING] POM for 'activecluster:activecluster:pom:1.1-
SNAPSHOT:compile' is invalid. It will be ignored for artifact
resolution. Reason: Not a v4.0.0 POM.
[WARNING] POM for 'activemq:activemq:pom:3.2.4-SNAPSHOT:compile'
is invalid. It will be ignored for artifact resolution. Reason:
Not a v4.0.0 POM.
</snip>
--jason
