Re: Trouble with 2.0.1 main pom and building anything a G dependency

2007-09-03 Thread Jason Dillon
IMO, we need to ween ourselves off of the local repository module completely... and avoid future use of any such local repository. When I (er we) did the main Maven 2 conversion I added some of these local modules as short-term work arounds to problems... there was no intention of leaving

Re: Trouble with 2.0.1 main pom and building anything a G dependency

2007-09-03 Thread Vamsavardhana Reddy
On 9/3/07, Jason Dillon [EMAIL PROTECTED] wrote: IMO, we need to ween ourselves off of the local repository module completely... and avoid future use of any such local repository. +1 When I (er we) did the main Maven 2 conversion I added some of these local modules as short-term work

Re: Trouble with 2.0.1 main pom and building anything a G dependency

2007-09-02 Thread Vamsavardhana Reddy
I thought I would initiate this discussion on the dependency issue I have run into with projects dependent on G 2.0.1. But, then I had to go offline for a few days. Now that someone else has run into the same problem, I guess it needs to be addressed for good. On 8/31/07, Jeff Genender [EMAIL

Re: Trouble with 2.0.1 main pom and building anything a G dependency

2007-09-01 Thread David Jencks
On Aug 31, 2007, at 8:28 PM, Tim McConnell wrote: Hi Jeff, I'm getting a similar problem when building the Eclipse plugin with a clean repo, except mine is axis2-jaxws-api... 1) org.apache.axis2:axis2-jaxws-api:jar:1.3-r562247 Where is this special repository I should use so that maven can

Re: Trouble with 2.0.1 main pom and building anything a G dependency

2007-09-01 Thread Tim McConnell
Hi David, thanks for the information. I can easily do that for myself and certainly don't mind doing so. However, this does bring to mind yet another question. The Geronimo Eclipse plugin will not build from a clean M2 repo without some of the artifacts in this repo, and I've been striving to

Re: Trouble with 2.0.1 main pom and building anything a G dependency

2007-08-31 Thread Matt Hogstrom
+1 ... Also, I think we'll be in better shape in the future but will always have this issue. Unfortunately, everyone was working at different paces to get to Java EE 5. Of course, the same problem will resurface on Java EE 6 ;-P On Aug 30, 2007, at 10:47 PM, Paul McMahan wrote: On Aug

Re: Trouble with 2.0.1 main pom and building anything a G dependency

2007-08-31 Thread Tim McConnell
Hi Jeff, I'm getting a similar problem when building the Eclipse plugin with a clean repo, except mine is axis2-jaxws-api... 1) org.apache.axis2:axis2-jaxws-api:jar:1.3-r562247 Where is this special repository I should use so that maven can find and download this ?? Thanks Jeff Genender

Re: Trouble with 2.0.1 main pom and building anything a G dependency

2007-08-30 Thread Kevan Miller
On Aug 30, 2007, at 6:05 PM, Jeff Genender wrote: Hi, I was building a 3rd party application with a dependency on the Geronimo specs (jee)...and I could not get it to build because it was looking for axis-saaj-1.3-r562247 For the life of me, I thought I had that usual maven corrupt

Re: Trouble with 2.0.1 main pom and building anything a G dependency

2007-08-30 Thread Paul McMahan
On Aug 30, 2007, at 6:05 PM, Jeff Genender wrote: D) Rename our special versions to g-axis-saaj-1.3-r562247 and house those under our own control (org.apache.geronimo...) in central on our next build (2.0.2). (The easy and quick, and very temprary fix!) This option seems most reasonable to