[
https://issues.apache.org/jira/browse/LUCENE-2657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12917448#action_12917448
]
Steven Rowe commented on LUCENE-2657:
-------------------------------------
bq. Would system scope dependencies be an alternative way?
I thought of that, and it probably makes sense for most of them.
But a jar like tika-parsers-0.8-SNAPSHOT.jar, with 10 or 15 dependencies, would
be even messier to deal with as a system dependency than as a locally installed
artifact. We would have to go look at the POM for it (contained conveniently
within the jar, as it happens), compare the dependencies against the versions
of the local dependencies (which would have previously had to be transferred to
the both the Solr Cell and the DIH Extras POMs) and make changes in both places.
> Replace Maven POM templates with full POMs, and change documentation
> accordingly
> --------------------------------------------------------------------------------
>
> Key: LUCENE-2657
> URL: https://issues.apache.org/jira/browse/LUCENE-2657
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Build
> Affects Versions: 3.1, 4.0
> Reporter: Steven Rowe
> Assignee: Steven Rowe
> Fix For: 3.1, 4.0
>
> Attachments: LUCENE-2657.patch
>
>
> The current Maven POM templates only contain dependency information, the bare
> bones necessary for uploading artifacts to the Maven repository.
> Full Maven POMs will include the information necessary to run a multi-module
> Maven build, in addition to serving the same purpose as the current POM
> templates.
--
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]
