You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Nicolas Lalevée (JIRA)" <ji...@apache.org> on 2007/02/26 11:13:05 UTC
[jira] Created: (LUCENE-817) Manage dependencies in the build with
ivy
Manage dependencies in the build with ivy
-----------------------------------------
Key: LUCENE-817
URL: https://issues.apache.org/jira/browse/LUCENE-817
Project: Lucene - Java
Issue Type: New Feature
Components: Build
Affects Versions: 2.1
Reporter: Nicolas Lalevée
There were issues about making the 2.1 release : http://www.nabble.com/-VOTE--release-Lucene-2.1-tf3228536.html#a8994721
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, ivyconf.properties : 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: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org
[jira] Resolved: (LUCENE-817) Manage dependencies in the build with
ivy
Posted by "Nicolas Lalevée (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nicolas Lalevée resolved LUCENE-817.
------------------------------------
Resolution: Duplicate
Lucene Fields: [New, Patch Available] (was: [Patch Available, New])
jira not responding, retrying, and then a duplicate issue...
> Manage dependencies in the build with ivy
> -----------------------------------------
>
> Key: LUCENE-817
> URL: https://issues.apache.org/jira/browse/LUCENE-817
> Project: Lucene - Java
> Issue Type: New Feature
> Components: Build
> Affects Versions: 2.1
> Reporter: Nicolas Lalevée
>
> There were issues about making the 2.1 release : http://www.nabble.com/-VOTE--release-Lucene-2.1-tf3228536.html#a8994721
> 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, ivyconf.properties : 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: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org