If I update "foo" and publish it to my repository, rebuilding "bar"
does not cause the latest "foo" to be retrieved.
After scouring the wiki and looking through the xsbt source, I can't
figure out why the latest version of "foo" is not being retrieved. It
appears that ".*-SNAPSHOT" is set as the changing pattern, so what
could be going wrong? Could this have anything to do with my project
using an external ivy.xml?
http://groups.google.com/group/simple-build-tool/browse_thread/thread/7464cbe97565463b
...and I made sure to set changing="true" on my "foo" dependency.
Still no luck getting sbt to check the repo for a newer version during
build.
libraryDependencies += "mycompany" % "foo" % "1.0-SNAPSHOT"
When I update "foo" in my repo, it is not re-retrieved when compiling
or updating the test project.
On Dec 5, 4:48 pm, James Douglas <jamesdoug...@gmail.com> wrote:
> I read through this thread:
>
> http://groups.google.com/group/simple-build-tool/browse_thread/thread...
sbt will never update the subproject code in the cache if the github
project is updated, unless I do
"rm -rf ~/.sbt/staging".
-Evan
http://groups.google.com/group/simple-build-tool/browse_thread/thread/5b59604bb08114b3#
best, -sciss-
> --
> You received this message because you are subscribed to the Google Groups "simple-build-tool" group.
> To post to this group, send email to simple-b...@googlegroups.com.
> To unsubscribe from this group, send email to simple-build-t...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/simple-build-tool?hl=en.
>
If I perform a `clean`, then upon next compile my snapshot dependency
*is* updated as expected. Is this the workflow I should follow?
I've also had a problem with snapshots not updating as expected. It's good to know that they'll update after a clean!It would be nice if snapshot updates were more predictable. Updating snapshots only after a clean violates the Principle of Least Surprise, IMO.