+1 Specially for enforcing best practices and avoid propagating malpractices.
On Sun, Dec 18, 2011 at 12:16 PM, Thilina Buddhika <thili...@wso2.com>wrote: > Hi Folks, > > Since we have a lot of developers(both internal and external) writing > Carbon components and features, how about the $subject? We can create a > Maven archetypes for Carbon components and features. > > Currently people are taking a copy of the existing component and modifying > it. This has certain drawbacks. > > 1. People do not cleanup the pom.xml files by removing > unnecessary dependencies, etc. > > 2. If there is an issue/bad practice in one component, it might > be propagated to other new components. For example, when we cleanup pom > files, we saw the same mistake is done over and over in some pom.xml files, > mainly because they are copied. > > The idea is to give a proper starting point, so that they can start > implementing it quickly. Also this is a way to enforce the Carbon best > practices for a certain extent, for instance, it is possible to generate > the configurations for Maven bundle plugin. > > Any suggestions or objections ? > > Thanks, > Thilina > > -- > Thilina Buddhika > Associate Technical Lead > WSO2 Inc. ; http://wso2.com > lean . enterprise . middleware > > phone : +94 77 44 88 727 > blog : http://blog.thilinamb.com > > _______________________________________________ > Carbon-dev mailing list > Carbon-dev@wso2.org > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > >
_______________________________________________ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
