There are outstanding issues that exist with Maven itself. Until Maven resolves these issues we will likely not be using it. We are monitoring these issues and can see that they are all marked to be fixed in Maven. In the immediate we will continue to use Ant for our build because it works great. We will manually push builds to Maven repos for Maven users. When/if Maven fixes it's issues we will move ahead with the build.
In regards to Spring not resolving. I suspect they are looking for the jar in the wrong place. That would be an issue they need to resolve. Brandon On 5/16/07, Daigo Kobayashi <[EMAIL PROTECTED]> wrote:
Thank you for replying. Any progress about agreement? This issue stay in open status for a long time. And I think other product can't resolve dependency about iBatis 2.3. (For example spring 2.0.2 and later can't resolve iBatis dependency correctly.) So early resolution is necessary. > See the last comment: > > "iBATIS 2.3.0 has been pushed to iBiblio for Maven 2. I'm going to leave > this issue open until we get a plan of action in place that we all agree > on for getting this to ibiblio when we release." ~ Brandon Goodin > > Clinton > > On 5/15/07, *Daigo Kobayashi* < [EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > I found jira about maven. > http://issues.apache.org/jira/browse/IBATIS-122 > > iBatis 2.3 is already uploaded to maven central repository. > However IBATIS-122 is not closed yet. Which status of this > issue is correct? > >
