[
https://issues.apache.org/jira/browse/LUCENE-2657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12912495#action_12912495
]
Steven Rowe commented on LUCENE-2657:
-------------------------------------
bq. How would the BuildListener interface know about dependencies? Does it have
some magic way to know this?
BuildListener has hooks for build task onset and completion events (inter
alia). ant2ide listens for Javac task completion, and captures from it the
source and target directories, as well as the build classpath. You have to
invoke compilation from an Ant build in order for this to work.
Seems kinda magical to me :)
The missing part here is figuring out the maven groupId/artifactId/version, and
I *think* this can be dealt with by looking at the manifest in the jar.
Maven-produced jars also contain their POMs, and pulling from there would be
even simpler.
> 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]
