lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Male (JIRA)" <>
Subject [jira] [Created] (LUCENE-3263) Create Build-A-Module process
Date Thu, 30 Jun 2011 03:53:28 GMT
Create Build-A-Module process

                 Key: LUCENE-3263
             Project: Lucene - Java
          Issue Type: New Feature
          Components: general/build
            Reporter: Chris Male
            Priority: Minor

Over the last few weeks, we've had a number of modules made.  This process seems only likely
to continue with the potential for modules within modules as well.

When creating a module, there is usually a consistent series of steps that need to be done.
 For me these are:

- Create module directory
- Add LICENSE.txt and NOTICE.txt
- Create build.xml with dependencies on other modules (if there are any)
- Update parent build.xml (in case of modules)
- Add java and test directories to dev-tools/eclipse/dot.classpath 
- Create module directory in dev-tools/idea
- Add .iml to dev-tools/idea/path/to/module
- Add module to dev-tools/idea/.idea/modules.xml
- Add module to dev-tools/idea/.idea/workspace.xml
- Create module directory in dev-tools/maven
- Add pom.xml.template to dev-tools/maven/path/to/module

I think we can create a script which provided some basic information, can complete the majority
of the above tasks.  Of course if the module requires some custom build targets or dependencies,
then human involvement will be required afterwards.  But at the very least, it'll reduce the
effort required to make a new module and lower the risk of a step being missed (which I've
done a few times).  

We can also use this as a chance to build in any verification of the configurations, so people
can feel more comfortable using them. 

This message is automatically generated by JIRA.
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message