[ 
https://issues.apache.org/jira/browse/LUCENE-2657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12913350#action_12913350
 ] 

Chris Male commented on LUCENE-2657:
------------------------------------

I'm wondering whether generating poms is just going to make them more 
mysterious.  While they are templates I can at least see them and they can be 
validated by XML validators (including IDEs).  Suddenly they are created 
through a more complex process which we also have to maintain.  

Assuming we have well-structured poms in the first place (huge assumption, 
different issue), are developers unprepared to add the appropriate dependency 
to the necessary pom? It doesn't seem like it'll happen very often, most of our 
artifacts have very few dependencies and we resist increasing them.  We can 
document the process, make it very clear exactly what needs to be added and 
where.

Also, I'm not sure all jars are going to have the appropriate manifest.  If the 
pom is generated (like Artifactory can do btw), I'm not sure it is packaged in 
the jar?

I think Robert was onto the right idea with this original proposal: If we 
consider our modules section and if we add a pom at the modules level and then 
one for each module, running a build from the modules level will recursively 
build each module.  If there is something wrong with the poms themselves, maven 
will fail.  If a dependency is omitted meaning the code cannot be built, maven 
will fail.  If any of these 2 issues occur, then the build would fail and an 
issue can be created for those more comfortable with maven to fix.

> Auto-generate POM templates from Ant builds
> -------------------------------------------
>
>                 Key: LUCENE-2657
>                 URL: https://issues.apache.org/jira/browse/LUCENE-2657
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Build
>            Reporter: Steven Rowe
>            Priority: Minor
>             Fix For: 3.1, 4.0
>
>
> Lucene and Solr modules' POM templates are manually maintained, and so are 
> not always in sync with the dependencies used by the Ant build. 
> It should be possible to auto-generate POM templates using build tools 
> extending Ant's 
> [BuildListener|http://api.dpml.net/ant/1.6.5/org/apache/tools/ant/BuildListener.html]
>  interface, similarly to how the 
> [ant2ide|http://gleamynode.net/articles/2234/] project generates eclipse 
> project files.

-- 
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]

Reply via email to