lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Male (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LUCENE-3930) nuke jars from source tree and use ivy
Date Thu, 29 Mar 2012 10:32:27 GMT

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

Chris Male commented on LUCENE-3930:
------------------------------------

{quote}
For the unreleased jars, can we just include their source in our source? This would work for
commons-csv and noggit which are the only two in solr/lib. They're both very small jars with
only a handful of java files.
{quote}

Any opinions on this? Do I need to change the packages for anything that we put into our source?

{quote}
Ouch, i didn't notice they changed over to git... The git repository they have just doesn't
correspond
to any meaningful rev numbers (die git die), but still has the history from svn. We are going
to 
have to do a git checkout i think?
{quote}

A checkout of head and upgrade to use that? or do a checkout of an older revision? We're going
to have to checkout the jsonic source as well.

{quote}
We likely also won't have any of the IDE configurations working unless someone has the time
to jump into that, and I have no idea if the maven build will break by us not having jars
in the source tree. These are all things I will ignore without hesitation because they don't
need to block a release. If anyone wants to fix this stuff, just start committing to the branch,
i need your help... its just that simple
{quote}

I think both IDE support and Maven will be fine.  The idea and eclipse targets will need to
invoke resolve to ensure the libs are downloaded.  Once they're in the same place as they
were before, the IDE configurations should march along fine.  Any libs we've changed the name
of or dropped, we can just update the configs for.  For Maven all this work is actually going
to simplify the poms.  We just need to bring the dependencies inline with the libs we have.
 Both wont be big deals.

 
                
> 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-solr-example.patch, LUCENE-3930-solr-example.patch,
LUCENE-3930.patch, LUCENE-3930.patch, LUCENE-3930.patch, ant_-verbose_clean_test.out.txt,
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