On Aug 19, 2008, at 4:15 PM, Shalin Shekhar Mangar (JIRA) wrote:
[ https://issues.apache.org/jira/browse/SOLR-586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12623780
#action_12623780 ]
Shalin Shekhar Mangar commented on SOLR-586:
--------------------------------------------
The uniqueVersion="false" forces maven to use the same version each
time overwriting the artifacts. No need to create a separate
snapshot artifact each time -- it will just clog the repository.
Yep, was just commenting that it didn't work w/ an older version of
the Maven Ant tasks.
bq. Can we close this?
I've kept it open just to make sure we remember to start publishing
snapshot artifacts before 1.3 and of course released artifact when
1.3 goes out. Some one with enough karma should take a look at
lucene's way of doing this and make the changes on hudson.
I'll take a look.
Maven - Solr Artifact Publishing
--------------------------------
Key: SOLR-586
URL: https://issues.apache.org/jira/browse/SOLR-586
Project: Solr
Issue Type: New Feature
Components: clients - java, contrib - DataImportHandler
Affects Versions: 1.3
Reporter: Spencer Crissman
Assignee: Shalin Shekhar Mangar
Priority: Minor
Fix For: 1.3
Attachments: SOLR-586-20080811-craigmcc.zip, SOLR-586-
nits.patch, SOLR-586.patch, SOLR-586.patch, SOLR-586.patch, solr-
common.pom.xml, solr-dih.pom.xml, solr-server.pom.xml, solr2mvn.sh,
solrj.pom.xml
I know there is an issue open (SOLR-19) for getting a solr build
going under Maven. This issue differs from that in that it does
not concern the build process of the solr project, but rather
simple dependency management for maven projects that depend on the
solr artifacts. I've outlined a way to easily incorporate solrj +
dependencies into your own maven projects, in hopes that others
doing this find it useful.
This issue's purpose is twofold:
1) Let others know the process.
2) Open the idea of whether this can be streamlined/incorporated
into the standard build in some manner.
Depending on Solrj in a Maven Project
1) Build a 1.3 snapshot.
1.1) Check out the code from http://svn.apache.org/repos/asf/lucene/solr/
1.2) Build using "ant dist"
2) Install the artifacts into your maven repo, using the included
pom files.
2.1) Move to your dist/apache-solr-1.3-dev/dist directory.
2.2) Copy the attached pom files into this directory.
2.3) Install solr-common into your repo.
ex) mvn install:install-file -Dfile=apache-solr-common-1.3-
dev.jar -DpomFile=solr-common.pom.xml
2.4) Install solrj into your repo.
ex) mvn install:install-file -Dfile=apache-solr-solrj-1.3-
dev.jar -DpomFile=solrj.pom.xml
3) Use Solrj in your existing Maven projects by including it as a
dependency in your own pom.xml
<dependency>
<groupId>org.apache.lucene.solr</groupId>
<artifactId>solrj</artifactId>
<version>1.3-SNAPSHOT</version>
</dependency>
So given the above process, it seems like it would be relatively
simple to standardize this process by:
1) Including the solr-common and solrj pom files w/ the dist.
2) Automating the periodic installation of the artifacts to a
central repo, such as the ibiblio repo.
If those steps were performed, then creating a (maven) project
based on solrj would be super simple: just #3 from above. Since
most custom developments are probably for the clients, it seems
like simplifying this would be a nice step to take.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
--------------------------
Grant Ingersoll
http://www.lucidimagination.com
Lucene Helpful Hints:
http://wiki.apache.org/lucene-java/BasicsOfPerformance
http://wiki.apache.org/lucene-java/LuceneFAQ
