You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Chris Male (Updated) (JIRA)" <ji...@apache.org> on 2012/04/04 13:50:23 UTC
[jira] [Updated] (LUCENE-3948) Experiment with placing poms outside
of src
[ https://issues.apache.org/jira/browse/LUCENE-3948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Male updated LUCENE-3948:
-------------------------------
Attachment: LUCENE-3948.patch
First shot at this. I've added a <module-path> to most poms which connects them to the location of the module.
I also fixed the solr/webapp build path in its pom.xml.template which pointed to solr/build and nuked the whole contents on mvn clean.
I haven't changed get-maven-poms so first you must execute ant filter-pom-templates from lucene/. Then go into build/poms and then you can execute mvn commands.
Everything seems to compile now. Can't see any bad directories being made.
Still TODO:
- Make use of module-directory inside module-path rather than re-specifying that information. Need to check if all tests pass.
- Change get-maven-poms to use filter-pom-templates.
If anybody could give this a whirl to see if it works
> Experiment with placing poms outside of src
> -------------------------------------------
>
> Key: LUCENE-3948
> URL: https://issues.apache.org/jira/browse/LUCENE-3948
> Project: Lucene - Java
> Issue Type: Improvement
> Components: general/build
> Reporter: Chris Male
> Priority: Minor
> Attachments: LUCENE-3948.patch
>
>
> Recent work in LUCENE-3944 has changed how our generated pom.xml files are handled during release preparation, placing them in build/ instead. However get-maven-poms still places the poms inside src/ so you can use them to drive a build. What I think would be ideal is if we could unify the release handling of the poms and the normal building handling, so that the poms can sit outside of src and serve both purposes.
> Some time ago I investigated how the ANT project handles its own Maven integration and it has its poms sitting in their own directory. They then reference the actual src locations inside the poms. This works for ANT but with a warning since some of their tests don't work due to how the Maven surefire plugin works, so they skip their tests.
> I have done some quick testing of my own and this process does seem to work for our poms and tests. I now want to take this to a full scale POC and see if it works fully.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org