[
https://issues.apache.org/jira/browse/SOLR-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12533951
]
Robert Clark commented on SOLR-19:
----------------------------------
+1 from me, I found these poms very useful for us in helping to provide jar and
war files from our development trunk.
In our local branch of solr-dev we brought everything up to date (all the jars
from lib are on public maven repsitories, except for the apache-commons-csv
snapshot) and we now have clean jars and wars being provided.
Specific issues encountered around Maven were:
- testing didn't work (i will continue looking at why) as configuring base
directories, sys properties, doesn't appear to be "out of the box" compatible
with maven/eclipse (nothing some digging around can't solve)
- some test sources had to be moved to test source folders from main
- executing "mvn release:deploy" didn't work as the modules "solr-core" and
"solr-abstract-war" weren't able to check out the source they operate on into
their target directories. So we ended up with jar's and war's with nothing in
them. The solution to this is a somewhat hacky subversion External pointing
"src" beneath each of these to the project "src" root.
To make things more maven compatible there would ideally be one artifact per
project, so a movement towards that would be good. To support both ant users
and maven users we thought that the project structure could be refactored to
align with single-artifact sub-structures, whilst keeping build.xml aware of
all the new locations.
There would be several sub "projects", perhaps:
solr-core ( solr-embedded ??)
solr-common
solr-solrj
solr-war
solr-example
A top level build.xml would preserve all current behaviour against these.
Once we're rolling with development it would be quite easy for us to provide
patches to make these changes for anyone interested.
> pom.xml to support maven2
> -------------------------
>
> Key: SOLR-19
> URL: https://issues.apache.org/jira/browse/SOLR-19
> Project: Solr
> Issue Type: New Feature
> Environment: all
> Reporter: Darren Erik Vengroff
> Priority: Minor
> Attachments: pom.xml, solr-maven2.zip
>
>
> I created a preliminary pom.xml to support building solr with maven2.
> Currently it compiles all the core solr code into a jar and runs the junit
> tests.
> Dropping this pom.xml into the root dir, in parallel with build.xml, will let
> those who wish to build with maven2.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
