lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steven Rowe (JIRA)" <j...@apache.org>
Subject [jira] Commented: (LUCENE-2657) Auto-generate POM templates from Ant builds
Date Wed, 22 Sep 2010 02:46:33 GMT

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

Steven Rowe commented on LUCENE-2657:
-------------------------------------

bq. 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? 

If nothing else, it is abundantly clear that there are more than a couple of Lucene/Solr developers
that don't want to put in *any* effort for Maven's sake.

bq. 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've looked into 10-15 jars, and very few have the required info.  Some even have the wrong
information in the manifest...

I think we can use .jar digest (SHA-1) as identifiers to look up the appropriate Maven info
to automatically set up POM dependencies.  I wrote a script to crawl the central Maven repo
for SHA-1 keyed Maven coordinates (groupId:artifactId:version), and it seems to work, but
at the rate it's progressing, it will take 4 days to finish.  Anyway, it seems like overkill
to gather info on all of the ~250k artifacts in the Maven central repo, just to handle the
~80 .jar files in the Lucene/Solr source tree.  

I found a free service that provides Maven central repo search, including by artifact digest:
http://www.jarvana.com/jarvana/search - it uses Lucene to power the search :).  I plan on
using this as the basis for automatic Maven coordinate lookup for arbitrary .jars.


> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message