felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Richard S. Hall" <he...@ungoverned.org>
Subject Re: Dumb question
Date Tue, 02 May 2006 19:20:51 GMT
I would like to see some reorganization of the repo, but I don't know 
enough about it to do it myself. If someone wants to step up and do some 
organizing, I think that would be great. I would love to see all bundles 
being dropped into a common "bundle" directory.

-> richard

Francesco Furfari wrote:
> Hi all,
> I'm going to commit the rest of UPnP examples, this thread seems me be 
> concluded about the  "Apache Felix " prefix, but what about  the  
> re-organization proposed by Marcel?
> I assume we are postponing any changes to the repo structure so far ....
>
> Regards
> Francesco
>
> Dennis Geurts wrote:
>> On Wed, 2006-04-05 at 17:17 +0200, Marcel Offermans wrote:
>>
>>  
>>> Furthermore, we might want to categorize the subprojects:
>>>  - framework;
>>>  - bundles;
>>>  - examples.
>>>
>>> I can imagine you might want to build just the framework, or the 
>>> bundles, for example. Is that something that's possible and fits in 
>>> the "maven way of working"?
>>>
>>> Greetings, Marcel
>>>
>>>     
>>
>> Marcel,
>>
>> What you suggest is possible in mvn (if that infers it is a maven way of
>> doing, I don't know)
>>
>>
>> Consider the following set-up: (bear with me)
>>
>> /pom.xml                               <--packaging == pom, no parent
>> /framework/pom.xml                     <--packaging == pom, parent
>> == /pom.xml
>> /framework/framework-main/pom.xml      <--packaging == any, parent
>> == /framework/pom.xml
>> /framework/framework-util/pom.xml      <--packaging == any, parent
>> == /framework/pom.xml
>> /framework/framework-optional/pom.xml  <--packaging == any, parent
>> == /framework/pom.xml
>>
>> /bundles/pom.xml             <--packaging == pom, parent == /pom.xml
>> /bundles/bundle1/pom.xml     <--packaging == osgi-bundle, parent
>> == /bundle/pom.xml
>> /bundles/bundle2/pom.xml     <--packaging == osgi-bundle, parent
>> == /bundle/pom.xml
>> /bundles/bundle3/pom.xml     <--packaging == osgi-bundle, parent
>> == /bundle/pom.xml
>> /bundles/bundle4/pom.xml     <--packaging == osgi-bundle, parent
>> == /bundle/pom.xml
>>
>> /examples/pom.xml            <--packaging == pom, parent == /pom.xml
>> /examples/example1/pom.xml   <--packaging == any, parent
>> == /examples/pom.xml
>> /examples/example2/pom.xml   <--packaging == any, parent
>> == /examples/pom.xml
>> /examples/example3/pom.xml   <--packaging == any, parent
>> == /examples/pom.xml
>>
>> furthermore:
>> /pom.xml has modules: -framework
>> -bundles
>> -examples
>>
>> /framework/pom.xml has modules:
>> -framework-main
>> -framework-util
>> -framework-optional
>>
>> /bundles/pom.xml has modules
>> -bundle1
>> -bundle2
>> -bundle3
>> -bundle4
>>
>> idem for examples
>>
>>
>> to build ALL targets, navigate to '/' and do mvn 'install' (or any other
>> goal)
>>
>> to build all 'framework' targets, navigate to '/framework' and do 'mvn
>> install'  (or any other goal)
>>
>>
>>
>>
>> Greetings, Dennis
>>
>>
>>
>>
>>
>>
>>
>>   
>
>

Mime
View raw message