lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicolas Lalevée (JIRA) <>
Subject [jira] Created: (LUCENE-816) Manage dependencies in the build with ivy
Date Mon, 26 Feb 2007 10:01:13 GMT
Manage dependencies in the build with ivy

                 Key: LUCENE-816
             Project: Lucene - Java
          Issue Type: New Feature
          Components: Analysis
    Affects Versions: 2.1
            Reporter: Nicolas Lalevée
         Attachments: common-build.tar.gz

There were issues about making the 2.1 release :
Then the discussion started to talk about maven, and also about ivy.
I propose here a draft, a proof of concept of an ant + ivy build. I made this build parallel
to the actual one, so people can evaluate it.
Note that I have only ivy-ified the core, the demo and the contrib/benchmark. The other contrib
projects can be ivy-ified quite easily.

The build system is in the common-build directory. In this directory we have :
* common-build.xml : the main common build which handle dependencies with ivy
* common-build-project.xml : build a java project, core, demo, or a contrib one
* common-build-webapp.xml : extend common-build-project and have some tasks about building
a war
* common-build-modules.xml : allow to build sevral projects, just using some subant task
* common-build-gcj.xml : build with gcj. It work once, need to be fixed
* ivyconf.xml, : ivy configuration
* build.xml : a little task to generate the ivyconf.xml to use with the eclipse ivy plugin
* eclipse directory : contains some XSL/XML to generate .classpath and .project

To test it and see how ivy is cool :
cd contrib/benchmark
ant -f build-ivy.xml buildeep

and look at the new local-libs directory at the root of the lucene directory !

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

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

View raw message