The problem is that you must compile the subprojects separately and then import the jar files into your local maven repository by hand.
As for feedback, I posted instructions on how to do all this in the interim until the pom.xml file gets fixed. The maven version problem is not a big deal. I upgraded my environment. Thanks.. On Sat, Mar 29, 2008 at 9:46 AM, Niklas Gustavsson <[EMAIL PROTECTED]> wrote: > Hi > > > On Fri, Mar 28, 2008 at 1:37 PM, Mark Webb <[EMAIL PROTECTED]> wrote: > > While I agree that this is an option, none of the other MINA > > subprojects require this. For consistency, they should all be the > > same. > > Not sure what issue we talk about here, could you please describe it > in some more detail? > > > > I am sorry if I am nitpicking and I apologize if I am upsetting > > anyone, but as this program grows and evolves we should try to make > > things easier for the users in order to gain more users and continued > > satisfaction for the program. > > All feedback is very welcome :-) > > > > Another question I have, the pom.xml requires that maven 2.0.5 or > > 2.0.7 are used. OS X comes with 2.0.6 and this causes a problem. Is > > there a reason why 2.0.6 cannot be used? > > Yeah, there was a bug in 2.0.6 that made the build failed. Reported > somewhere in the Maven JIRA but I can't seem to find it now. Since > quite a few users reported issues with this we decided after some > discussion to disable the use of 2.0.6 (the same was true for Maven > versions before 2.0.5). Anyways, it might well have been related to a > plugin that has since been fixed. If you can build with 2.0.6 I would > happily remove the restriction. > > /niklas > -- -------------------------------- Talent hits a target no one else can hit; Genius hits a target no one else can see.
