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

derek commented on KAFKA-139:
-----------------------------

Thanks for looking into it! For what it's worth, my comment on this being a 
complicated patch was meant to convey my understanding that I'm probably doing 
some things here well outside the norm for submitted patches, not a complaint 
about the process :)

For #3 do you mean that changes in code don't result in a newly built JAR for 
certain subprojects? If that's the case I'm probably missing a dependency 
setting on those subprojects. For #4, this is a change in the behavior of SBT 
for 0.10+. Now, SBT uses Ivy, so none of the downloaded deps will be in the 
project dir. Rather, they will be in the user's Ivy home (~/.ivy2/cache by 
default). In the case of packaging, this is something that may (and I stress 
*may*) be simpler within SBT, as in the Release.scala I had originally, or by 
using the sbt-assembly plugin (https://github.com/sbt/sbt-assembly/) to bundle 
all JARs together into one. Please let me know if I can help with that. If 
you'd like me to take a look at it, would it be possible to check in what you 
*do* have working on a branch so that I can simply point git-svn at it and work 
on your exact codebase?

Thanks,

Derek
                
> cross-compile multiple Scala versions
> -------------------------------------
>
>                 Key: KAFKA-139
>                 URL: https://issues.apache.org/jira/browse/KAFKA-139
>             Project: Kafka
>          Issue Type: Improvement
>          Components: packaging
>    Affects Versions: 0.8
>            Reporter: Chris Burroughs
>              Labels: build
>             Fix For: 0.8
>
>         Attachments: kafka-sbt0-11-3-0.8.patch, kafka-sbt0-11-3-0.8-v2.patch, 
> kafka-sbt0-11-3-0.8-v3.patch, kafka-sbt0-11-3-0.8-v4.patch, 
> kafka-sbt0-11-3.patch
>
>
> Since scala does not maintain binary compatibly between versions, 
> organizations tend to have to move all of there code at the same time.  It 
> would thus be very helpful if we could cross build multiple scala versions.
> http://code.google.com/p/simple-build-tool/wiki/CrossBuild
> Unclear if this would require KAFKA-134 or just work.

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

        

Reply via email to