Saminda Wijeratne wrote:
> Hi Ruwan,
>
> Yes there need to have dependency bundles defined as dependencies at 
> some point. My theory is try to have those from a parent pom on the 
> hirarchy as much as possible so that we wont be redeclaring such 
> dependencies. The idea was to have a single place where the version is 
> defined.
It is OK to define the version at a parent, but you must define all 
dependencies at the feature pom itself, otherwise the aggregated build 
will not work properly.

Thanks,
Ruwan
>
> Saminda
>
> On Sun, Jan 31, 2010 at 11:11 AM, Sameera Jayasoma <same...@wso2.com 
> <mailto:same...@wso2.com>> wrote:
>
>
>
>     On Sun, Jan 31, 2010 at 11:03 AM, Ruwan Linton <ru...@wso2.com
>     <mailto:ru...@wso2.com>> wrote:
>
>         Sameera Jayasoma wrote:
>         >
>         >
>         > On Sun, Jan 31, 2010 at 10:17 AM, Ruwan Linton
>         <ru...@wso2.com <mailto:ru...@wso2.com>
>         > <mailto:ru...@wso2.com <mailto:ru...@wso2.com>>> wrote:
>         >
>         >     Folks,
>         >
>         >     In p2 feature pom files there are no dependencies, there
>         for maven
>         >     fails
>         >     to order the build properly, when aggregated into one
>         build. Can we
>         >     please add dependencies to all the feature poms.
>         >
>         >     I will start on this, but need everyones help.\
>         >
>         >
>         > We are planning to have hackthon session this tuesday. The
>         purpose is
>         > to update all the features in trunk. We can discuss about
>         this and do
>         > the necessary things during that event. WDYT?
>         >
>         >
>         >
>         >     Sameera/Saminda, one question, we can treat features as
>         jar files as
>         >     well and take a dependency on them right, they are
>         available on the
>         >     maven repositories as well, right? It has to be other
>         wise the whole
>         >     maven build concept will fail.
>         >
>         >
>         > Outcome of a feature build is a zip file which is created
>         according
>         > the Eclipse feature format. Theoretically, during the build
>         time, a
>         > features does not need to depend on another feature(maven
>         dependency).
>         > You only need to mention the dependencies on other features
>         in the
>         > feature.xml. During the installation, P2 will handle
>         dependencies..
>         OK, but it is different for bundles right? when you try to
>         create a
>         feature from bundle, it tries to read it, right?? So we need
>         the bundle
>         dependencies for features, but not feature dependencies? Am I
>         correct?
>
>
>     Yes. Bundles need to be there before building features. Required
>     bundles get copied the feature zip file.
>
>     Sameera
>
>
>         Thanks,
>         Ruwan
>         >
>         > Thanks
>         > Sameera
>         >
>         >
>         >
>         >     On a side note, we are proceeding very well with the one
>         build
>         >     aspect on
>         >     top of one checkout. I was able to build till the
>         jar-services
>         >     feature,
>         >     with ESB product profile, which excludes Ode and Openjpa
>         and also
>         >     skipping tests with -Dmaven.test.skip=true. (Andreas did
>         a fix on
>         >     axis2
>         >     trunk to get rid of the jaxws-integration issue) since
>         jar-services
>         >     feature do not have a dependency on jar services bundle
>         maven tried to
>         >     build jar services feature before the bundle :-(
>         >
>         >     Thanks,
>         >     Ruwan
>         >
>         >     _______________________________________________
>         >     Carbon-dev mailing list
>         >     Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org>
>         <mailto:Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org>>
>         >     https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>         >
>         >
>         >
>         
> ------------------------------------------------------------------------
>         >
>         > _______________________________________________
>         > Carbon-dev mailing list
>         > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org>
>         > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>         >
>
>
>         _______________________________________________
>         Carbon-dev mailing list
>         Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org>
>         https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
>
>     _______________________________________________
>     Carbon-dev mailing list
>     Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org>
>     https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>   


_______________________________________________
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Reply via email to