Hi all, In the approach described in previous mail information related to JARS In product packs are stored in repository as 'Modules' and 'Artifacts'. But there are jars generated using 'ant'. 'Artifacts' and 'Modules' of C5 governance solution are intended to store information of maven projects and dependencies. Therefor, it's not possible to store information of jars generated using ant through an 'Artifact' or 'Module'.
Please provide your suggestions on how to handle such jars when storing information and generating LICENSE.txt. A tentative approach would be, - Having another RXT called 'Other Dependencies'(with contains file name, license type) - Recored information of non maven dependency jars using it when executing 'licfill' goal - And, fetch information from the repository when executing 'licgen' or else, We cant store information of such jars in another data store(e.g. my sql) and fetch information from there when generating the file. Thanks *,Sajith Ravindra* Senior Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware mobile: +94 77 2273550 blog: http://sajithr.blogspot.com/ <http://lk.linkedin.com/pub/shani-ranasinghe/34/111/ab> On Thu, Apr 3, 2014 at 11:23 PM, Sajith Ravindra <[email protected]> wrote: > Hi all, > > For $subject for a product pack the following approach will be taken, > > Following 3 fields will be added to the 'Artifact' and 'Module' asset types > - JAR Name - Name of the .jar file generated for maven project or the .jar > file of the dependency > - License type > - Packaging type - Can be jar,bundle or jarinbundle > > Two goals will be added to the governance maven plugin. These goals must > be executed against the root pom.xml of the product. > - licfill - Feed the license information to the GReg. > - licgen - Generate LICENSE.txt. > > The purpose of having two swperate goals is to allow generation of > LICENSE.txt files without requiring to updating license information every > time when generating the file. > > To feed license information to the GReg, the plugin will scan through the > pack to locate jars and to read their pom.xml files .'Artifacts/Modules' > are mapped to jars using information read from the pom.xmls of jars. In > this process,If there is an 'Artifact/Module' for a given jar in repository > it will be updated with license information. Otherwise, an 'Artifact' will > be created to represent the jar(dependency). To retrieve license > information of jars [1] will be used. > > When generating LICENSE.txt, plugin will scan through the pack to locate > pom.xmls of jars inside the pack. Then it will read > groupid:artifactid:version from pom.xml and use that information as key to > get license information from Greg of each jar. > > Please provide your feedback/suggestions on this approach. > > [1] - http://mojo.codehaus.org/license-maven-plugin/ > > > Thanks > *,Sajith Ravindra* > Senior Software Engineer > WSO2 Inc.; http://wso2.com > lean.enterprise.middleware > > mobile: +94 77 2273550 > blog: http://sajithr.blogspot.com/ > <http://lk.linkedin.com/pub/shani-ranasinghe/34/111/ab> > > > On Mon, Mar 31, 2014 at 5:18 PM, Sajith Ravindra <[email protected]> wrote: > >> Hi all, >> >> Under C5 development governance project we are planing to facilitate the >> generation of LICENSE.txt. >> >> Up to now, we have implemented support for generating LICENSE.txt for a >> single JAR(Carbon Feature) or a carbon component by looking at all its >> listed dependencies in pom.xml files >> >> Now we are trying to implement support for generating LICENSE.txt for a >> product pack. Because a product pack contains jars that are not are not >> related to dependencies in pom.xml files of the product, it's required to >> scan through the pack to identify the jars. After identifying the jars, the >> jars must be mapped to Modules/Artifacts[*] stored in a Greg instance we >> maintain in C5 development governance solution. >> >> The problem we are trying to solve is, how the mapping between jar file >> names and Artifact/Module[*] can be done properly? >> >> Please suggest on a proper way you can think of to do this mapping. >> >> [*] - In C5 development governance solution we use two types of RXT >> artifacts to capture dependency information of a maven project. it contains >> information such as group id, artifact id and version of a dependency >> (1) Module - refers to an internal maven project >> (2) Artifact - refers to an external 3rd party dependency. >> >> Thanks >> *,Sajith Ravindra* >> Senior Software Engineer >> WSO2 Inc.; http://wso2.com >> lean.enterprise.middleware >> >> mobile: +94 77 2273550 >> blog: http://sajithr.blogspot.com/ >> <http://lk.linkedin.com/pub/shani-ranasinghe/34/111/ab> >> > >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
