[
https://issues.apache.org/jira/browse/LUCENE-622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Busch updated LUCENE-622:
---------------------------------
Attachment: LUCENE-622_NEW.patch
This new patch combines the pom.xml files from Sami and Karl with some
modifications
to make them consistent, as well as Hoss' recommendations regarding the maven
ant
tasks.
Details:
- We now have pom.xml files for all contribs except javascript (which has no
build.xml) and gdata.
- I added the following four poms to the root directory:
"lucene-contrib-pom.xml",
"lucene-core-pom.xml", "lucene-demos-pom.xml" and "lucene-parent-pom.xml".
Each contrib directory contains a file "pom.xml".
- Added the "m2-deploy" macro to common-build.xml. It now uses the maven ant
tasks
to deploy the pom and jar files to a local repository located in dist/maven.
- Added a new target "dist-maven" to contrib-build.xml that is only executed if
a pom.xml is present in the contrib dir.
- Added the target "generate-maven-artifacts" to build.xml which calls
"m2-deploy"
for the parent, core, demos, and contrib poms. Then it does a contrib crawl
with target "dist-maven".
This works quite well. However there are probably some things that can be
simplified or improved:
- I copy the pom.xml to the build dir first so that I can replace the @version@
placeholder with the actual value. There's probably a way to do this with
the maven ant tasks without having to copy the file first.
- This might be a hack but I couldn't figure out a way to do this differently
yet: In the "dist-maven" target I read the parent, core and contrib pom.xml
using the <artifact:pom> task. I don't actually need to load those poms
but if I don't do it the build fails, because the contrib artifacts have the
"lucene-contrib" artifact as parent. Even if I specify the local repository
where those artifacts are located or if I add them as dependencies it doesn't
work. A hint here is appreciated.
- The new lucene-checksum macro is not used yet for md5 computation of the
artifact files.
I will spend more time on this patch during the next days for testing. Some
feedback
and help with testing is highly appreciated. It would also be helpful if the
contrib
owners could take a look at the particular pom.xml files.
For testing purposes I uploaded the artifacts generated by this patch to
http://people.apache.org/~buschmi/staging_area/lucene
> Provide More of Lucene For Maven
> --------------------------------
>
> Key: LUCENE-622
> URL: https://issues.apache.org/jira/browse/LUCENE-622
> Project: Lucene - Java
> Issue Type: Task
> Affects Versions: 2.0.0
> Reporter: Stephen Duncan Jr
> Assignee: Michael Busch
> Fix For: 2.2
>
> Attachments: lucene-622.txt, LUCENE-622_NEW.patch, lucene-core.pom,
> lucene-highlighter-2.0.0.pom, lucene-maven.patch, lucene-maven.tar.bz2,
> test-project.tar.gz
>
>
> Please provide javadoc & source jars for lucene-core. Also, please provide
> the rest of lucene (the jars inside of "contrib" in the download bundle) if
> possible.
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
