lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LUCENE-3930) nuke jars from source tree and use ivy
Date Sat, 31 Mar 2012 19:44:25 GMT

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

Hoss Man commented on LUCENE-3930:
----------------------------------

I did some testing of the "packages" built using trunk (circa r1307608)...

* we don't ship solr's build.xml (or any of the sub-build.xml files) in the "binary" artifacts,
and with these changes most of the new ivy.xml files are also excluded -- but for some reason
these newly added files are showing up, we should probably figure out why and exclude them
as well since they aren't usable and could easily people...
** ./example/example-DIH/ivy.xml
** ./example/example-DIH/build.xml
** ./example/ivy.xml
** ./example/build.xml
* the lib's for test-framework (ant, ant-junit, and junit) aren't being included in the lucene
"binary" artifacts ... for the ant jars this might (test-framework doesn't actually have any
run-time deps on anything in ant does it?) but it seems like hte junit jar should be included
since including lucene-test-framework.jar in your classpath is useless w/o also including
junit
* "ant ivy-bootstrap" followed by "ant test" using the lucene "source" package (lucene-4.0-SNAPSHOT-src.tgz)
produces a build failure -- but this may have been a problem even before ivy (note the working
dir and the final error)...

{noformat}
hossman@bester:~/tmp/ivy-pck-testing/lu/src/lucene-4.0-SNAPSHOT$ ant test
...
    [junit] Testsuite: org.apache.lucene.util.junitcompat.TestReproduceMessage
    [junit] Tests run: 12, Failures: 0, Errors: 0, Time elapsed: 0.114 sec
    [junit] 

test:

compile-lucene-core:

jflex-uptodate-check:

jflex-notice:

javacc-uptodate-check:

javacc-notice:

ivy-availability-check:

ivy-fail:

resolve:
[ivy:retrieve] :: loading settings :: url = jar:file:/home/hossman/.ant/lib/ivy-2.2.0.jar!/org/apache/ivy/core/settings/ivysettings.xml

init:

clover.setup:

clover.info:
     [echo] 
     [echo]       Clover not found. Code coverage reports disabled.
     [echo]   	

clover:

common.compile-core:
    [javac] Compiling 1 source file to /home/hossman/tmp/ivy-pck-testing/lu/src/lucene-4.0-SNAPSHOT/build/core/classes/java

compile-core:

compile-test-framework:

ivy-availability-check:

ivy-fail:

resolve:
[ivy:retrieve] :: loading settings :: url = jar:file:/home/hossman/.ant/lib/ivy-2.2.0.jar!/org/apache/ivy/core/settings/ivysettings.xml

init:

compile-lucene-core:

compile-core:

compile-test:
     [echo] Building demo...

ivy-availability-check:

ivy-fail:

resolve:
[ivy:retrieve] :: loading settings :: url = jar:file:/home/hossman/.ant/lib/ivy-2.2.0.jar!/org/apache/ivy/core/settings/ivysettings.xml

common.init:

compile-lucene-core:

contrib-build.init:

check-lucene-core-uptodate:

jar-lucene-core:

jflex-uptodate-check:

jflex-notice:

javacc-uptodate-check:

javacc-notice:

ivy-availability-check:

ivy-fail:

resolve:
[ivy:retrieve] :: loading settings :: url = jar:file:/home/hossman/.ant/lib/ivy-2.2.0.jar!/org/apache/ivy/core/settings/ivysettings.xml

init:

clover.setup:

clover.info:
     [echo] 
     [echo]       Clover not found. Code coverage reports disabled.
     [echo]   	

clover:

common.compile-core:
    [javac] Compiling 1 source file to /home/hossman/tmp/ivy-pck-testing/lu/src/lucene-4.0-SNAPSHOT/build/core/classes/java

compile-core:

jar-core:
      [jar] Building jar: /home/hossman/tmp/ivy-pck-testing/lu/src/lucene-4.0-SNAPSHOT/build/core/lucene-core-4.0-SNAPSHOT.jar

init:

compile-test:
     [echo] Building demo...

check-analyzers-common-uptodate:

jar-analyzers-common:

BUILD FAILED
/home/hossman/tmp/ivy-pck-testing/lu/src/lucene-4.0-SNAPSHOT/build.xml:487: The following
error occurred while executing this line:
/home/hossman/tmp/ivy-pck-testing/lu/src/lucene-4.0-SNAPSHOT/common-build.xml:1026: The following
error occurred while executing this line:
/home/hossman/tmp/ivy-pck-testing/lu/src/lucene-4.0-SNAPSHOT/contrib/contrib-build.xml:58:
The following error occurred while executing this line:
/home/hossman/tmp/ivy-pck-testing/lu/src/lucene-4.0-SNAPSHOT/common-build.xml:551: Basedir
/home/hossman/tmp/ivy-pck-testing/lu/src/modules/analysis/common does not exist

Total time: 5 minutes 10 seconds
{noformat}

...it's trying to reach back up out of the working directory into "../modules"
                
> nuke jars from source tree and use ivy
> --------------------------------------
>
>                 Key: LUCENE-3930
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3930
>             Project: Lucene - Java
>          Issue Type: Task
>          Components: general/build
>            Reporter: Robert Muir
>            Assignee: Robert Muir
>            Priority: Blocker
>             Fix For: 3.6
>
>         Attachments: LUCENE-3930-skip-sources-javadoc.patch, LUCENE-3930-solr-example.patch,
LUCENE-3930-solr-example.patch, LUCENE-3930.patch, LUCENE-3930.patch, LUCENE-3930.patch, LUCENE-3930__ivy_bootstrap_target.patch,
ant_-verbose_clean_test.out.txt, noggit-commons-csv.patch, patch-jetty-build.patch
>
>
> As mentioned on the ML thread: "switch jars to ivy mechanism?".

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


Mime
View raw message