Hi,

On Tue, Aug 23, 2011 at 3:43 PM, Afkham Azeez <[email protected]> wrote:
> The rationale is to have a single repository, and the product profiles to
> point to that repository. This will drastically reduce the size of
> distributions such as Stratos. What is the plan to make this work?

It should work. I mean it is possible with the new maven plugin goals.
I will come up with a sample-setup (maybe with two products) after i'm
finished with feature manager.

thanks,
--Pradeep


>
> On Tue, Aug 23, 2011 at 3:39 PM, Pradeep Fernando <[email protected]> wrote:
>>
>> Hi,
>>
>> On Tue, Aug 23, 2011 at 2:53 PM, Afkham Azeez <[email protected]> wrote:
>> > Sameera/Pradeep,
>> > What is the status of this?
>>
>>  We never started such work. At least the title is different. ;) You
>> are referring to the equinox migration I'm doing right now. While
>> doing the migration,
>> we decided to generate product profiles from the scratch. (right now
>> we are provisioning to a already available profile - kind of hard
>> coded).
>>
>> I was able to migrate carbon to new equinox-3.7. In the process I
>> wrote some maven plugins to create profiles based on eclipse .product
>> files.
>>
>> Heres what happens right now - my local version.
>>
>> 1. publish feartures/bundles to p2-repo
>> 2. publish product definition (.product file) to p2-repo
>> 3. materialize the product.
>>
>>
>> This brings two advantages :
>>
>> 1. future equinox migrations will be trivial  ( since equinox libs
>> itself is bundled as a feature)
>> 2. we can create products using new maven plugins. (we can say: create
>> the p2 aware product Appserver with the profileName wso2.appserver and
>> use the /target/bundlePool as the bundle location).  - *so several
>> products can share the same bundle location*.
>>
>>
>> My status :
>>
>> 1. during the process I had to get rid of the p2-agent (which was used
>> as the minimal p2-runtime as well as the initial carbon profile). I
>> used some of the tycho libs as the p2-runtime and hence had to migrate
>> carbon to maven3 build system. I did that upto feature level.
>>
>> 2. Equinox migration is finished.
>> 3. things like touchpoints are working.
>>
>> 4. Right now I'm doing the feature manager upgrade. Ideally old
>> p2-libs should work with new equinox. But we are using p2-libs with
>> some provisional APIs. almost all the APIs have changed in p2 after
>> that.
>>
>>
>>
>>
>> thanks,
>> --Pradeep
>
>
>
> --
> Afkham Azeez
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
>
> email: [email protected] cell: +94 77 3320919
> blog: http://blog.afkham.org
> twitter: http://twitter.com/afkham_azeez
> linked-in: http://lk.linkedin.com/in/afkhamazeez
>
> Lean . Enterprise . Middleware
>



-- 
Pradeep Fernando
Software Engineer
WSO2 Inc; http://wso2.com/

blog: http://pradeepfernando.blogspot.com/
m: +94776603662
_______________________________________________
Carbon-dev mailing list
[email protected]
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Reply via email to