Had a discussion with Kishanthan on this. We will face some issues if we do this.
1) We will have to repeat maven plugin version in all the orbit pom.xml 2) We will have to repeat distribution repositories, maven plugin repositories in all the orbit pom.xml The best solution is to upload the common parent pom.xml and used it every where. I've seen many projects have followed this pattern. Thanks, Sameera. On Thu, Jun 26, 2014 at 5:18 PM, Kasun Gajasinghe <[email protected]> wrote: > Hi, > > Is there a need to have a parent pom file for orbit bundles in git? [1] > AFAIK, the orbit bundles should be self-contained. If so, shall we get rid > of it? > > [1] https://github.com/wso2/orbit/blob/master/pom.xml > > Thanks, > KasunG > > -- > > *Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc. > email: kasung AT spamfree wso2.com > linked-in: http://lk.linkedin.com/in/gajasinghe > blog: http://kasunbg.org > > > -- Sameera Jayasoma, Software Architect, WSO2, Inc. (http://wso2.com) email: [email protected] blog: http://sameera.adahas.org twitter: https://twitter.com/sameerajayasoma flickr: http://www.flickr.com/photos/sameera-jayasoma/collections Mobile: 0094776364456 Lean . Enterprise . Middleware
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
