I made the dependency optional, so that it works if aries application and blueprint is not present, but it's still used if available, so we can't remove the dependencies. I uploaded a snapshot after my changes at
http://repository.apache.org/content/groups/snapshots/org/apache/aries/subsystem/org.apache.aries.subsystem.core/1.0.1-SNAPSHOT/ 2014-04-25 21:41 GMT+02:00 Cristiano Gavião <[email protected]>: > Guillaume, > > you removed the need of blueprint so seems to be safe to remove all > related maven dependencies from org.apache.aries.subsystem bundle pom, > don't you think ? they are still there... > > regards, > > Cristiano > > > On 15-04-2014 08:08, Guillaume Nodet wrote: > > The refactoring is done. > http://svn.apache.org/viewvc?view=revision&revision=1587513 > Subsystem is now completely independent of applications and blueprint > (though it will still be leveraged if present). > > > 2014-04-14 21:35 GMT+02:00 Holly Cummins <[email protected]>: > >> If applications aren't using blueprint this analysis of blueprint >> files won't be providing any useful information, so we should be able to >> make something in that chain optional without loss of function. Of course, >> doing that refactoring may not meet anyone's definition of 'easy'. :) >> >> >> On Monday, April 14, 2014, Guillaume Nodet <[email protected]> wrote: >> >>> Actually, the Aries Application Modeller really needs Aries Blueprint as >>> it analyses blueprint files to find provided services, so this dependency >>> can't be easily removed. >>> >>> Guillaume Nodet >>> >>> >>> 2014-04-14 17:19 GMT+02:00 Guillaume Nodet <[email protected]>: >>> >>>> Yes, it would be nice to have subsystems being independent of blueprint >>>> imho. >>>> >>>> >>>> 2014-04-14 16:37 GMT+02:00 Cristiano Gavião <[email protected]>: >>>> >>>> Hi Mark. >>>>> >>>>> Well, last time I tried, the subsystems service (zero) wasn't >>>>> registered without blueprint bundles in active state. >>>>> Seems that a dependency of subsystem, application-modeller, has a >>>>> direct dependency to blueprint: >>>>> https://github.com/apache/aries/tree/trunk/application/application-modeller/src/main/resources/OSGI-INF/blueprint >>>>> >>>>> regards, >>>>> >>>>> Cristiano >>>>> >>>>> >>>>> On 11-04-2014 11:45, Mark Nuttall wrote: >>>>> >>>>> Hello, >>>>> I've looked over the code and can only see a dependency on blueprint >>>>> in the subsystem-itests pom. So there's a dependency on blueprint to run >>>>> the itests, but I cannot see a runtime dependency from subsystem-core on >>>>> blueprint, Have I missed something? >>>>> >>>>> Regards, >>>>> Mark >>>>> >>>>> >>>>> On 10 April 2014 14:13, Cristiano Gavião <[email protected]> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> I had a system that was developed using only Declarative Services. We >>>>>> are studying to use Subsystem to help with an isolation issue. >>>>>> >>>>>> The first problem for us is that it depends on Blueprint and we don't >>>>>> like the idea to add this overhead in this environment just to be able to >>>>>> use Subsystems. >>>>>> >>>>>> Could someone explain me this dependency? are beans being injected or >>>>>> just services? >>>>>> >>>>>> would be possible to use DS instead of Blueprint in case no bean >>>>>> being injected ? >>>>>> >>>>>> thanks >>>>>> >>>>>> Cristiano >>>>>> >>>>> >>>>> >>>>> >>>> >>> > >
