Readonly file ProjectRef #120

Merged
merged 1 commit into from Jul 24, 2011

3 participants

@duboisf

This allows using a project reference that points to a readonly
directory.

The use case for this is having sbt plugin projects on a network
share (readonly) that you can just point to. The plugin projects
get copied and built automatically, just like a git project
reference gets cloned and built.

This will ease plugin imcompatibilies between minor sbt versions,
avoiding to have to cross build plugins against all compatible sbt
versions.

@harrah
sbt member

Use git rebase upstream/0.10 to clean up the history so that only your commit shows up. Otherwise, it looks fine.

@duboisf duboisf Support for readonly file ProjectRef
This allows using a project reference that points to a readonly
directory.

The use case for this is having sbt plugin projects on a network
share (readonly) that you can just point to. The plugin projects
get copied and built automatically, just like a git project
reference gets cloned and built.

This will ease plugin imcompatibilies between minor sbt versions,
avoiding to have to cross build plugins against all compatible sbt
versions.
4ffe240
@duboisf

Thanks, I was wondering why there were more then 1 commit. From now on I'll rebase upstream instead of merging.

@harrah harrah merged commit 671053c into sbt:0.10 Jul 24, 2011
@harrah
sbt member

Great, thanks!

@jakajancar

@duboisf 4 year laters, this is causing some problems for me :) Can you let me know what your thoughts are on #2202?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment