Ralph
I'm not sure how much this helps since I gather not much can be done
about the osgi jar, or how much maven 2 is better than maven 1 in this,
but the team I work with had similar problems with a bunch of our
framework builds. We solved the circularity problems pretty simply by
splitting up the frameworks into two projects, api and impl. The api
just contains interfaces or very simple classes. We were able to force
the "lower" level implementations to only be dependent on "higher" level
apis. We then used Spring to tie the implementations together at run time.
- Re: Mavenization Alan D. Cabrera
- Re: Mavenization BJ Hargrave
- Re: Mavenization Richard S. Hall
- Re: Mavenization Alan D. Cabrera
- Re: Mavenization Richard S. Hall
- Re: Mavenization Alan D. Cabrera
- Re: Mavenization Richard S. Hall
- Re: **SL-JUNK** Re: Mavenizatio... Alan D. Cabrera
- Re: **SL-JUNK** Re: Mavenizatio... Richard S. Hall
- Re: Mavenization Alan D. Cabrera
- Re: Mavenization Ralph Goers
- Re: Mavenization BJ Hargrave
- Re: Mavenization Niclas Hedhman
- Re: osgi.jar and R4 sources was: Mavenization Brett Porter
- Re: osgi.jar and R4 sources was: Mavenization Richard S. Hall
- Re: osgi.jar and R4 sources was: Mavenizatio... Martijn Dashorst
- Re: osgi.jar and R4 sources was: Maveniz... Richard S. Hall
- Re: osgi.jar and R4 sources was: Mavenizatio... BJ Hargrave
- Re: osgi.jar and R4 sources was: Maveniz... Richard S. Hall
- RE: Mavenization Jeff McAffer
- Re: Mavenization Brett Porter