You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Steven Rowe (Created) (JIRA)" <ji...@apache.org> on 2012/04/04 16:47:24 UTC
[jira] [Created] (LUCENE-3951) generate-maven-artifacts should
depend on ivy resolve, so that maven-ant-tasks jar is available for use by
m2-deploy
generate-maven-artifacts should depend on ivy resolve, so that maven-ant-tasks jar is available for use by m2-deploy
--------------------------------------------------------------------------------------------------------------------
Key: LUCENE-3951
URL: https://issues.apache.org/jira/browse/LUCENE-3951
Project: Lucene - Java
Issue Type: Bug
Components: general/build
Affects Versions: 3.6, 4.0
Reporter: Steven Rowe
Assignee: Steven Rowe
Priority: Blocker
Fix For: 3.6, 4.0
see title
--
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
[jira] [Commented] (LUCENE-3951) get-maven-poms should depend on
ivy resolve, so that non-mavenized jars are available for use by mvn -P
bootstrap install
Posted by "Robert Muir (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-3951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13246401#comment-13246401 ]
Robert Muir commented on LUCENE-3951:
-------------------------------------
on 3.x i think it wants the jetty jars to be there.
but this can be solved by simply adding an <ant dir="solr/example" target="resolve">
to this top-level task only needed by the maven build.
This way it wont interfere with any release tasks.
> get-maven-poms should depend on ivy resolve, so that non-mavenized jars are available for use by mvn -P bootstrap install
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: LUCENE-3951
> URL: https://issues.apache.org/jira/browse/LUCENE-3951
> Project: Lucene - Java
> Issue Type: Bug
> Components: general/build
> Affects Versions: 3.6, 4.0
> Reporter: Steven Rowe
> Assignee: Steven Rowe
> Fix For: 3.6, 4.0
>
>
> see title
--
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
[jira] [Updated] (LUCENE-3951) get-maven-poms should depend on ivy
resolve, so that non-mavenized jars are available for use by mvn -P
bootstrap install
Posted by "Steven Rowe (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-3951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steven Rowe updated LUCENE-3951:
--------------------------------
Attachment: LUCENE-3951-handle-ivy.default.ivy.user.dir.patch
Same patch, with the right issue number in the name this time.
> get-maven-poms should depend on ivy resolve, so that non-mavenized jars are available for use by mvn -P bootstrap install
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: LUCENE-3951
> URL: https://issues.apache.org/jira/browse/LUCENE-3951
> Project: Lucene - Java
> Issue Type: Bug
> Components: general/build
> Affects Versions: 3.6
> Reporter: Steven Rowe
> Assignee: Steven Rowe
> Fix For: 3.6
>
> Attachments: LUCENE-3951-handle-ivy.default.ivy.user.dir.patch, LUCENE-3951.patch, LUCENE-3951.patch
>
>
> see title
--
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
[jira] [Commented] (LUCENE-3951) dist-maven should depend on ivy
resolve, so that maven-ant-tasks jar is available for use by m2-deploy
Posted by "Robert Muir (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-3951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13246325#comment-13246325 ]
Robert Muir commented on LUCENE-3951:
-------------------------------------
But this is really specific to 'the maven build' right?
dist-maven works correctly for releasing.
So this could also be solved in dev-tools/maven, in its executions
it could call whatever ant stuff it needs to work.
> dist-maven should depend on ivy resolve, so that maven-ant-tasks jar is available for use by m2-deploy
> ------------------------------------------------------------------------------------------------------
>
> Key: LUCENE-3951
> URL: https://issues.apache.org/jira/browse/LUCENE-3951
> Project: Lucene - Java
> Issue Type: Bug
> Components: general/build
> Affects Versions: 3.6, 4.0
> Reporter: Steven Rowe
> Assignee: Steven Rowe
> Priority: Blocker
> Fix For: 3.6, 4.0
>
>
> see title
--
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
[jira] [Commented] (LUCENE-3951) get-maven-poms should depend on
ivy resolve, so that non-mavenized jars are available for use by mvn -P
bootstrap install
Posted by "Robert Muir (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-3951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13246420#comment-13246420 ]
Robert Muir commented on LUCENE-3951:
-------------------------------------
And it seems that maven could do this itself in its executions?
see http://search.maven.org/remotecontent?filepath=org/apache/rat/apache-rat-tasks/0.8/apache-rat-tasks-0.8.pom
for an example?
> get-maven-poms should depend on ivy resolve, so that non-mavenized jars are available for use by mvn -P bootstrap install
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: LUCENE-3951
> URL: https://issues.apache.org/jira/browse/LUCENE-3951
> Project: Lucene - Java
> Issue Type: Bug
> Components: general/build
> Affects Versions: 3.6
> Reporter: Steven Rowe
> Assignee: Steven Rowe
> Fix For: 3.6
>
> Attachments: LUCENE-3951.patch
>
>
> see title
--
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
[jira] [Commented] (LUCENE-3951) get-maven-poms should depend on
ivy resolve, so that non-mavenized jars are available for use by mvn -P
bootstrap install
Posted by "Steven Rowe (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-3951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13246413#comment-13246413 ]
Steven Rowe commented on LUCENE-3951:
-------------------------------------
{quote}
on 3.x i think it wants the jetty jars to be there.
but this can be solved by simply adding an <ant dir="solr/example" target="resolve">
to this top-level task only needed by the maven build.
{quote}
Yes, you're right, only on branch_3x, where jetty and jetty-util are still locally-modified non-released test dependencies, 'the maven build' (specifically running tests under Maven) needs these two jars to be in {{solr/example/lib}}. Re-opening...
> get-maven-poms should depend on ivy resolve, so that non-mavenized jars are available for use by mvn -P bootstrap install
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: LUCENE-3951
> URL: https://issues.apache.org/jira/browse/LUCENE-3951
> Project: Lucene - Java
> Issue Type: Bug
> Components: general/build
> Affects Versions: 3.6
> Reporter: Steven Rowe
> Assignee: Steven Rowe
> Fix For: 3.6
>
> Attachments: LUCENE-3951.patch
>
>
> see title
--
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
[jira] [Commented] (LUCENE-3951) get-maven-poms should depend on
ivy resolve, so that non-mavenized jars are available for use by mvn -P
bootstrap install
Posted by "Robert Muir (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-3951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13246399#comment-13246399 ]
Robert Muir commented on LUCENE-3951:
-------------------------------------
ok i see: maven build still requires this task, it just doesnt need the libs resolved...
> get-maven-poms should depend on ivy resolve, so that non-mavenized jars are available for use by mvn -P bootstrap install
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: LUCENE-3951
> URL: https://issues.apache.org/jira/browse/LUCENE-3951
> Project: Lucene - Java
> Issue Type: Bug
> Components: general/build
> Affects Versions: 3.6, 4.0
> Reporter: Steven Rowe
> Assignee: Steven Rowe
> Fix For: 3.6, 4.0
>
>
> see title
--
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
[jira] [Reopened] (LUCENE-3951) get-maven-poms should depend on ivy
resolve, so that non-mavenized jars are available for use by mvn -P
bootstrap install
Posted by "Robert Muir (Reopened) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-3951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Muir reopened LUCENE-3951:
---------------------------------
reopening since i want a maven build before rc for 3.x
> get-maven-poms should depend on ivy resolve, so that non-mavenized jars are available for use by mvn -P bootstrap install
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: LUCENE-3951
> URL: https://issues.apache.org/jira/browse/LUCENE-3951
> Project: Lucene - Java
> Issue Type: Bug
> Components: general/build
> Affects Versions: 3.6
> Reporter: Steven Rowe
> Assignee: Steven Rowe
> Fix For: 3.6
>
>
> see title
--
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
[jira] [Commented] (LUCENE-3951) get-maven-poms should depend on
ivy resolve, so that non-mavenized jars are available for use by mvn -P
bootstrap install
Posted by "Steven Rowe (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-3951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13246392#comment-13246392 ]
Steven Rowe commented on LUCENE-3951:
-------------------------------------
{{dist-maven}} isn't recursive - {{generate-maven-artifacts}} provides {{dist-maven}} recursion.
I'm missing some dots you've connected here - how is it that 'the maven build' not needing {{ant resolve}} to function means that {{generate-maven-artifacts}} is not necessary?
> get-maven-poms should depend on ivy resolve, so that non-mavenized jars are available for use by mvn -P bootstrap install
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: LUCENE-3951
> URL: https://issues.apache.org/jira/browse/LUCENE-3951
> Project: Lucene - Java
> Issue Type: Bug
> Components: general/build
> Affects Versions: 3.6, 4.0
> Reporter: Steven Rowe
> Assignee: Steven Rowe
> Fix For: 3.6, 4.0
>
>
> see title
--
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
[jira] [Commented] (LUCENE-3951) get-maven-poms should depend on
ivy resolve, so that non-mavenized jars are available for use by mvn -P
bootstrap install
Posted by "Steven Rowe (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-3951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13246426#comment-13246426 ]
Steven Rowe commented on LUCENE-3951:
-------------------------------------
{quote}
bq. 'The maven build' doesn't require generate-maven-artifacts, and never has.
well at least hudson needs to call the logic in my patch (somehow) because the maven bootstrap uses:
{noformat}<file>solr/example/lib/jetty-${patched.jetty.version}.jar</file>{noformat}
{quote}
Your patch puts {{ant resolve}} in the wrong place.
{{mvn -P bootstrap install}} is run by the jenkins script before attempting to run {{mvn install}} and {{mvn test}}, but {{ant genenerate-maven-artifacts}} is called by the jenkins script *after* running all of these (to deploy snapshots), so {{ant resolve}} should happen *before* any of the {{mvn ...}} stuff.
{quote}
And it seems that maven could do this itself in its executions?
see http://search.maven.org/remotecontent?filepath=org/apache/rat/apache-rat-tasks/0.8/apache-rat-tasks-0.8.pom for an example?
{quote}
Yes, you're right - the ant build shouldn't have to deal with this at all. I'll make a patch.
> get-maven-poms should depend on ivy resolve, so that non-mavenized jars are available for use by mvn -P bootstrap install
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: LUCENE-3951
> URL: https://issues.apache.org/jira/browse/LUCENE-3951
> Project: Lucene - Java
> Issue Type: Bug
> Components: general/build
> Affects Versions: 3.6
> Reporter: Steven Rowe
> Assignee: Steven Rowe
> Fix For: 3.6
>
> Attachments: LUCENE-3951.patch
>
>
> see title
--
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
[jira] [Updated] (LUCENE-3951) get-maven-poms should depend on ivy
resolve, so that non-mavenized jars are available for use by mvn -P
bootstrap install
Posted by "Steven Rowe (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-3951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steven Rowe updated LUCENE-3951:
--------------------------------
Attachment: LUCENE-3944-handle-ivy.default.ivy.user.dir.patch
The [nightly Jenkins branch_3x Maven job|https://builds.apache.org/job/Lucene-Solr-Maven-3.x/448/console] failed because of {{ivy.default.ivy.user.dir}} sysprop problems (passing through the non-interpolated reference):
{noformat}
[INFO] An Ant BuildException has occured: The following error occurred while executing this line:
/usr/home/hudson/hudson-slave/workspace/Lucene-Solr-Maven-3.x/checkout/solr/example/build.xml:39: java.lang.IllegalArgumentException: ivy.default.ivy.user.dir must be absolute: ${ivy.default.ivy.user.dir}
around Ant part ...<ant inheritall="false" target="resolve" antfile="solr/example/build.xml">... @ 4:77 in /usr/home/hudson/hudson-slave/workspace/Lucene-Solr-Maven-3.x/checkout/lucene/build/lucene-solr-grandparent/antrun/build-main.xml{noformat}
This patch fixes the maven-antrun-plugin setup by defining two executions, one for the case where {{ivy.default.ivy.user.dir}} is set, and another for where it is not.
Committing shortly.
> get-maven-poms should depend on ivy resolve, so that non-mavenized jars are available for use by mvn -P bootstrap install
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: LUCENE-3951
> URL: https://issues.apache.org/jira/browse/LUCENE-3951
> Project: Lucene - Java
> Issue Type: Bug
> Components: general/build
> Affects Versions: 3.6
> Reporter: Steven Rowe
> Assignee: Steven Rowe
> Fix For: 3.6
>
> Attachments: LUCENE-3944-handle-ivy.default.ivy.user.dir.patch, LUCENE-3951.patch, LUCENE-3951.patch
>
>
> see title
--
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
[jira] [Updated] (LUCENE-3951) get-maven-poms should depend on ivy
resolve, so that non-mavenized jars are available for use by mvn -P
bootstrap install
Posted by "Robert Muir (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-3951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Muir updated LUCENE-3951:
--------------------------------
Attachment: LUCENE-3951.patch
patch for 3.x
> get-maven-poms should depend on ivy resolve, so that non-mavenized jars are available for use by mvn -P bootstrap install
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: LUCENE-3951
> URL: https://issues.apache.org/jira/browse/LUCENE-3951
> Project: Lucene - Java
> Issue Type: Bug
> Components: general/build
> Affects Versions: 3.6
> Reporter: Steven Rowe
> Assignee: Steven Rowe
> Fix For: 3.6
>
> Attachments: LUCENE-3951.patch
>
>
> see title
--
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
[jira] [Commented] (LUCENE-3951) get-maven-poms should depend on
ivy resolve, so that non-mavenized jars are available for use by mvn -P
bootstrap install
Posted by "Robert Muir (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-3951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13246429#comment-13246429 ]
Robert Muir commented on LUCENE-3951:
-------------------------------------
ok thanks... i'm admittedly lost in how the maven build uses these tasks,
I just know that packaging works and was trying to think of solutions that
don't mess with that... thanks!
> get-maven-poms should depend on ivy resolve, so that non-mavenized jars are available for use by mvn -P bootstrap install
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: LUCENE-3951
> URL: https://issues.apache.org/jira/browse/LUCENE-3951
> Project: Lucene - Java
> Issue Type: Bug
> Components: general/build
> Affects Versions: 3.6
> Reporter: Steven Rowe
> Assignee: Steven Rowe
> Fix For: 3.6
>
> Attachments: LUCENE-3951.patch
>
>
> see title
--
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
[jira] [Commented] (LUCENE-3951) get-maven-poms should depend on
ivy resolve, so that non-mavenized jars are available for use by mvn -P
bootstrap install
Posted by "Robert Muir (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-3951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13246417#comment-13246417 ]
Robert Muir commented on LUCENE-3951:
-------------------------------------
{quote}
'The maven build' doesn't require generate-maven-artifacts, and never has.
{quote}
well at least hudson needs to call the logic in my patch (somehow) because
the maven bootstrap uses:
{noformat}
<file>solr/example/lib/jetty-${patched.jetty.version}.jar</file>
{noformat}
> get-maven-poms should depend on ivy resolve, so that non-mavenized jars are available for use by mvn -P bootstrap install
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: LUCENE-3951
> URL: https://issues.apache.org/jira/browse/LUCENE-3951
> Project: Lucene - Java
> Issue Type: Bug
> Components: general/build
> Affects Versions: 3.6
> Reporter: Steven Rowe
> Assignee: Steven Rowe
> Fix For: 3.6
>
> Attachments: LUCENE-3951.patch
>
>
> see title
--
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
[jira] [Resolved] (LUCENE-3951) get-maven-poms should depend on ivy
resolve, so that non-mavenized jars are available for use by mvn -P
bootstrap install
Posted by "Steven Rowe (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-3951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steven Rowe resolved LUCENE-3951.
---------------------------------
Resolution: Invalid
There are no longer any non-mavenized jars in the build, so ivy resolve is not a requirement before running the maven build
> get-maven-poms should depend on ivy resolve, so that non-mavenized jars are available for use by mvn -P bootstrap install
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: LUCENE-3951
> URL: https://issues.apache.org/jira/browse/LUCENE-3951
> Project: Lucene - Java
> Issue Type: Bug
> Components: general/build
> Affects Versions: 3.6, 4.0
> Reporter: Steven Rowe
> Assignee: Steven Rowe
> Fix For: 3.6, 4.0
>
>
> see title
--
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
[jira] [Commented] (LUCENE-3951) get-maven-poms should depend on
ivy resolve, so that non-mavenized jars are available for use by mvn -P
bootstrap install
Posted by "Steven Rowe (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-3951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13246359#comment-13246359 ]
Steven Rowe commented on LUCENE-3951:
-------------------------------------
Hmm, JIRA lost a comment I made on this issue before resolving (or I screwed up by editing the issue before submitting a comment I was making) - it was something like:
I confused releasing and enabling 'the maven build', which involves putting the POMs in place via {{ant get-maven-poms}} and installing non-mavenized dependencies into the user's local maven repository via {{mvn -P bootstrap install}}. The source of the non-mavenized dependencies was the {{lib/}} directories, which are empty until ivy resolve is done, so ivy resolve is a prerequisite.
However, since there are no longer any non-mavenized dependencies (see SOLR-3308, LUCENE-3930, and SOLR-3310 - thanks Robert Muir and Chris Male), ivy resolve is no longer a prerequisite for running 'the maven build'. I'll resolve this issue as Invalid.
> get-maven-poms should depend on ivy resolve, so that non-mavenized jars are available for use by mvn -P bootstrap install
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: LUCENE-3951
> URL: https://issues.apache.org/jira/browse/LUCENE-3951
> Project: Lucene - Java
> Issue Type: Bug
> Components: general/build
> Affects Versions: 3.6, 4.0
> Reporter: Steven Rowe
> Assignee: Steven Rowe
> Fix For: 3.6, 4.0
>
>
> see title
--
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
[jira] [Updated] (LUCENE-3951) get-maven-poms should depend on ivy
resolve, so that non-mavenized jars are available for use by mvn -P
bootstrap install
Posted by "Steven Rowe (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-3951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steven Rowe updated LUCENE-3951:
--------------------------------
Attachment: LUCENE-3951.patch
Patch invoking the {{resolve}} target in {{solr/example/build.xml}} via the maven-antrun-plugin from the {{bootstrap}} profile in the Lucene/Solr grandfather POM.
The Ivy jar included on the classpath for the maven-antrun-plugin is from the user's Maven local repository, apparently because maven-antrun-plugin doesn't look in {{~/.ant/lib/}}: [http://maven.apache.org/plugins/maven-antrun-plugin/examples/customTasks.html].
Works for me locally (from the top-level dir):
* {{ant clean clean-jars get-maven-poms}}
* {{mvn -N -P bootstrap install -Divy.default.ivy.user.dir=...}}
* {{mvn -DskipTests install}}
* {{mvn test}}
Committing shortly.
> get-maven-poms should depend on ivy resolve, so that non-mavenized jars are available for use by mvn -P bootstrap install
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: LUCENE-3951
> URL: https://issues.apache.org/jira/browse/LUCENE-3951
> Project: Lucene - Java
> Issue Type: Bug
> Components: general/build
> Affects Versions: 3.6
> Reporter: Steven Rowe
> Assignee: Steven Rowe
> Fix For: 3.6
>
> Attachments: LUCENE-3951.patch, LUCENE-3951.patch
>
>
> see title
--
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
[jira] [Commented] (LUCENE-3951) get-maven-poms should depend on
ivy resolve, so that non-mavenized jars are available for use by mvn -P
bootstrap install
Posted by "Steven Rowe (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-3951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13246406#comment-13246406 ]
Steven Rowe commented on LUCENE-3951:
-------------------------------------
bq. ok i see: maven build still requires this task, it just doesnt need the libs resolved...
'The maven build' doesn't require {{generate-maven-artifacts}}, and never has.
> get-maven-poms should depend on ivy resolve, so that non-mavenized jars are available for use by mvn -P bootstrap install
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: LUCENE-3951
> URL: https://issues.apache.org/jira/browse/LUCENE-3951
> Project: Lucene - Java
> Issue Type: Bug
> Components: general/build
> Affects Versions: 3.6, 4.0
> Reporter: Steven Rowe
> Assignee: Steven Rowe
> Fix For: 3.6, 4.0
>
>
> see title
--
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
[jira] [Resolved] (LUCENE-3951) get-maven-poms should depend on ivy
resolve, so that non-mavenized jars are available for use by mvn -P
bootstrap install
Posted by "Steven Rowe (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-3951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steven Rowe resolved LUCENE-3951.
---------------------------------
Resolution: Fixed
Lucene Fields: New,Patch Available (was: New)
[The most recent Jenkins nightly branch_3x Maven job|https://builds.apache.org/job/Lucene-Solr-Maven-3.x/449/] made it past Ant resolution and compilation, though it had a failure in one of the Solr contribs. That test failure is unrelated to this issue, though, so I'm resolving as fixed.
> get-maven-poms should depend on ivy resolve, so that non-mavenized jars are available for use by mvn -P bootstrap install
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: LUCENE-3951
> URL: https://issues.apache.org/jira/browse/LUCENE-3951
> Project: Lucene - Java
> Issue Type: Bug
> Components: general/build
> Affects Versions: 3.6
> Reporter: Steven Rowe
> Assignee: Steven Rowe
> Fix For: 3.6
>
> Attachments: LUCENE-3951-handle-ivy.default.ivy.user.dir.patch, LUCENE-3951.patch, LUCENE-3951.patch
>
>
> see title
--
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
[jira] [Commented] (LUCENE-3951) get-maven-poms should depend on
ivy resolve, so that non-mavenized jars are available for use by mvn -P
bootstrap install
Posted by "Robert Muir (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-3951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13246388#comment-13246388 ]
Robert Muir commented on LUCENE-3951:
-------------------------------------
so we can remove generate-maven-artifacts task totally?
Then we just have the releasing task: dist-maven
> get-maven-poms should depend on ivy resolve, so that non-mavenized jars are available for use by mvn -P bootstrap install
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: LUCENE-3951
> URL: https://issues.apache.org/jira/browse/LUCENE-3951
> Project: Lucene - Java
> Issue Type: Bug
> Components: general/build
> Affects Versions: 3.6, 4.0
> Reporter: Steven Rowe
> Assignee: Steven Rowe
> Fix For: 3.6, 4.0
>
>
> see title
--
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
[jira] [Updated] (LUCENE-3951) get-maven-poms should depend on ivy
resolve, so that non-mavenized jars are available for use by mvn -P
bootstrap install
Posted by "Steven Rowe (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-3951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steven Rowe updated LUCENE-3951:
--------------------------------
Priority: Major (was: Blocker)
Summary: get-maven-poms should depend on ivy resolve, so that non-mavenized jars are available for use by mvn -P bootstrap install (was: dist-maven should depend on ivy resolve, so that maven-ant-tasks jar is available for use by m2-deploy)
> get-maven-poms should depend on ivy resolve, so that non-mavenized jars are available for use by mvn -P bootstrap install
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: LUCENE-3951
> URL: https://issues.apache.org/jira/browse/LUCENE-3951
> Project: Lucene - Java
> Issue Type: Bug
> Components: general/build
> Affects Versions: 3.6, 4.0
> Reporter: Steven Rowe
> Assignee: Steven Rowe
> Fix For: 3.6, 4.0
>
>
> see title
--
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
[jira] [Updated] (LUCENE-3951) get-maven-poms should depend on ivy
resolve, so that non-mavenized jars are available for use by mvn -P
bootstrap install
Posted by "Steven Rowe (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-3951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steven Rowe updated LUCENE-3951:
--------------------------------
Attachment: (was: LUCENE-3944-handle-ivy.default.ivy.user.dir.patch)
> get-maven-poms should depend on ivy resolve, so that non-mavenized jars are available for use by mvn -P bootstrap install
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: LUCENE-3951
> URL: https://issues.apache.org/jira/browse/LUCENE-3951
> Project: Lucene - Java
> Issue Type: Bug
> Components: general/build
> Affects Versions: 3.6
> Reporter: Steven Rowe
> Assignee: Steven Rowe
> Fix For: 3.6
>
> Attachments: LUCENE-3951-handle-ivy.default.ivy.user.dir.patch, LUCENE-3951.patch, LUCENE-3951.patch
>
>
> see title
--
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
[jira] [Updated] (LUCENE-3951) dist-maven should depend on ivy
resolve, so that maven-ant-tasks jar is available for use by m2-deploy
Posted by "Steven Rowe (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-3951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steven Rowe updated LUCENE-3951:
--------------------------------
Summary: dist-maven should depend on ivy resolve, so that maven-ant-tasks jar is available for use by m2-deploy (was: generate-maven-artifacts should depend on ivy resolve, so that maven-ant-tasks jar is available for use by m2-deploy)
> dist-maven should depend on ivy resolve, so that maven-ant-tasks jar is available for use by m2-deploy
> ------------------------------------------------------------------------------------------------------
>
> Key: LUCENE-3951
> URL: https://issues.apache.org/jira/browse/LUCENE-3951
> Project: Lucene - Java
> Issue Type: Bug
> Components: general/build
> Affects Versions: 3.6, 4.0
> Reporter: Steven Rowe
> Assignee: Steven Rowe
> Priority: Blocker
> Fix For: 3.6, 4.0
>
>
> see title
--
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
[jira] [Updated] (LUCENE-3951) get-maven-poms should depend on ivy
resolve, so that non-mavenized jars are available for use by mvn -P
bootstrap install
Posted by "Robert Muir (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-3951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Muir updated LUCENE-3951:
--------------------------------
Affects Version/s: (was: 4.0)
Fix Version/s: (was: 4.0)
> get-maven-poms should depend on ivy resolve, so that non-mavenized jars are available for use by mvn -P bootstrap install
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: LUCENE-3951
> URL: https://issues.apache.org/jira/browse/LUCENE-3951
> Project: Lucene - Java
> Issue Type: Bug
> Components: general/build
> Affects Versions: 3.6
> Reporter: Steven Rowe
> Assignee: Steven Rowe
> Fix For: 3.6
>
>
> see title
--
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