m2 error: Unable to resolve dependency

2006-07-01 Thread Jason Dillon
Any idea what this is about? snip [INFO] [INFO] Building Geronimo Configs :: Axis Deployer [INFO]task-segment: [install] [INFO]

Re: m2 error: Unable to resolve dependency

2006-07-01 Thread Jacek Laskowski
On 7/1/06, Jason Dillon [EMAIL PROTECTED] wrote: Any idea what this is about? ... Unable to resolve dependency activecluster/activecluster//jar Just a guess (again today), but I saw something alike when I was looking into the m1-based build and the solution was to add dependencies to a

Re: m2 error: Unable to resolve dependency

2006-07-01 Thread Jason Dillon
Seems like other stuff is also missing: Unable to resolve dependency axion/axion//jar Where are these coming from? --jason On Jul 1, 2006, at 3:10 PM, Jacek Laskowski wrote: On 7/1/06, Jason Dillon [EMAIL PROTECTED] wrote: Any idea what this is about? ... Unable to resolve

Re: m2 error: Unable to resolve dependency

2006-07-01 Thread Jason Dillon
Ug I give up. I keep adding a dependency and then find another that is missing... And now it complains about: Unable to resolve dependency geronimo/geronimo-timer/1.2- SNAPSHOT/jar Which looks like an old groupId. Where are these dependencies coming from? Where is this

Re: m2 error: Unable to resolve dependency

2006-07-01 Thread David Jencks
yikes the dependencies need a lot of work axis and axis deployer don't need openejb Anyway I think the problem comes from using m1 built openejb jars that have geronimo-dependency.xml files inside for the m1 groupIds. I think the problem will go away if you build openejb with m2.

Re: m2 error: Unable to resolve dependency

2006-07-01 Thread Jason Dillon
I do not believe that their are m2 builds of openejb to get us the right SNAPSHOT versions we need... so if we need to openejb jars built from m2, then we need to get the CI build up using m2 and deploying so that G can use em. --jason On Jul 1, 2006, at 3:55 PM, David Jencks wrote: