We can't really fix this issue as we have no way to change an artifact that has been already released. I think we should update the servicemix 3.2 branch to use the latest xbean version and that would work around the problem.
On Thu, Aug 21, 2008 at 5:04 AM, Ramon Buckland <[EMAIL PROTECTED]> wrote: > > Hi Ryan, > > You problem is caused by an invalid Xbean 3.3 POM. I have detailed the issue > here. > > https://issues.apache.org/jira/browse/XBEAN-110 > > Until they fix it (Guillaume, can you fix that one ?) you can do the > following. > > Rerun the archtetype:create maven goal again.. > > Edit ~/.m2/repository/org/apache/xbean/xbean/3.3/xbean-3.3.pom > (Windows: C:\Documents and > Settings\USER\.m2\repository\org\apache\xbean\xbean\3.3\xbean-3.3.pom ) > > and change line 61 from > <version>3.3-SNAPSHOT</version> > to > <version>3.3</version> > > You can note the comment above which describes that it should have been done > as part of the xbean release, but it was missed. We (they) are only human > :-) > > Hope that helps > Regards > Ramon > > > -- > View this message in context: > http://www.nabble.com/Another-Maven2-dependency-problem-for-Servicemix-3.2.2-tp19020478p19081709.html > Sent from the ServiceMix - User mailing list archive at Nabble.com. > > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/
