Alasdair Nottingham
On 28 Jun 2011, at 22:46, Oliver Lietz <apa...@oliverlietz.de> wrote: > Am Tuesday 28 June 2011 schrieb Alasdair Nottingham: >> Alasdair Nottingham >> >> On 28 Jun 2011, at 22:06, Oliver Lietz <apa...@oliverlietz.de> wrote: >>> Am Monday 27 June 2011 schrieb Alasdair Nottingham: >>>> Hi, >>> >>> hey, >>> >>>> I don't think there are any "plans". In the past releases have been more >>>> "on demand". >>>> >>>> After the 0.3 release we decided to move to a pre-bundle release process >>>> so their wont be a big 0.4 release like there were previously. Some >>>> bundles might be at 0.4 and some at 0.3.1. >>>> >>>> Do you need a release? >>> >>> a release with fixed dependencies would be nice. Instead of just >>> switching from org.apache.aries.blueprint 0.2-incubating to 0.3.1 I had >>> to add several missing dependencies (org.apache.aries.proxy, >>> org.apache.aries.util, org.objectweb.asm, org.objectweb.asm.commons, >>> org.objectweb.asm.tree). >> >> I'm not sure I follow what you mean. I know 0.3 required more externals, >> this was a deliberate decision. > > Looks like the manifest of blueprint is broken as it imports > org.apache.aries.proxy and org.apache.aries.util but the scope for > org.apache.aries.proxy in pom.xml is "test". It isn't broken. The org.apache.aries.proxy import is for a package. The pom depends on modules or bundles. The org.apache.aries.proxy bundle contains the implementation of the proxy package and is only required to rub tests, not to compile the code. > >> We aren't going to bundle dependencies >> into the bundles in the future. If you mean you want a zip that contains >> everything you need for blueprint or jpa > > No, I just want a newer version of blueprint in my OSGi integration tests > (https://src.springframework.org/svn/se-db4o/trunk/org.springextensions.db4o- > it-osgi/pom.xml). > >> we have discussed this and have >> support, we just haven't done a distribution release yet. >> >>> O. >
