nice-sbt-settings v0.4.0 release

[laughedelic]

• Upgrades:
  • upgrade to sbt-release 0.8.3
  • upgrade to sbt-s3-resolver 0.11.0
  • upgrade to literator v0.5.1
• New integrations:
  • sbt-taglist: for warnings about TODO and FIXME tags
  • sbt-github-release: for automated release notes and artifacts on Github
  • sbt-updates: for checking, that your deps are up to date (Integrating sbt-updates plugin #10)
  • java docs generation?
• Improvements:

  • Improving release process #12: improve release process

  • adding release notes to the version setting commit message

  • clean task improvement:

    cleanFiles ++= Seq(
      baseDirectory.value / "project/target"
    , baseDirectory.value / "project/project"
    )

[johanandren]

I've merged your fix/change into sbt-taglist and made a new release, 1.3

[laughedelic]

thank you, @johanandren!

[laughedelic]

WARNING: I couldn't catch the error which appears, when you publish an artifact which is already published, so the release process won't stop in this case. I anybody knows how to do that, tell me. @evdokim it's from your ivy-resolver, may be you know

[evdokim]

@laughedelic you mean that you artifacts are can be overridden? are you sure that it is reproducible? it can be related with eventual consistency

[laughedelic]

@evdokim, no the ivy-resolver doesn't allow to overwrite the artifacts, it's fine. It's just that it shows an error about it, but the publishing release step doesn't fail on it.

[evdokim]

I don't know I throw an exception https://github.com/ohnosequences/ivy-s3-resolver/blob/master/src/main/java/ohnosequences/ivy/S3Repository.java#L171

what can I do for it more?

[laughedelic]

I don't know.. It's strange then, that I cannot catch it

[laughedelic]

TODO for myself:

• separate docs generation into a task
• name release steps and print it, so that the user is not lost in the logger flood
• structure the code: separate keys, setting sets, project settings (scala/java) and release steps/process

[laughedelic]

Would be nice to add this fix to the release, instead of using a workaround: sbt/sbt-release#62

[eparejatobes]

@laughedelic I'm trying to set this up in bio4j/bio4j#24 and I get unresolved literator etc. Is everything published??

[laughedelic]

yep, just need more resolvers. sorry, it's not obvious, but it is in the readme of this branch: https://github.com/ohnosequences/nice-sbt-settings/tree/release/v0.4.0#usage

[laughedelic]

resolvers ++= Seq(
  "Era7 maven releases" at "http://releases.era7.com.s3.amazonaws.com"
  "sbt-taglist-releases" at "http://johanandren.github.com/releases/",
  "laughedelic maven releases" at "http://dl.bintray.com/laughedelic/maven",
  Resolver.url("laughedelic sbt-plugins", url("http://dl.bintray.com/laughedelic/sbt-plugins"))(Resolver.ivyStylePatterns)
)

[laughedelic]

TODO:

• separate actions from commits, so that first we do things, generate docs, set version etc. and only in the end commit changes
• remove md docs from cleanFiles; clean them only in release
• structure the code: separate keys, setting sets, project settings (scala/java) and release steps/process
• upgrade to literator v0.5.1

[laughedelic]

• upgrade to sbt-assembly 0.11: http://notes.implicit.ly/post/78421706213/sbt-assembly-0-11-0

[laughedelic]

Released 0.4.0-M3 with a lot of improvements. tested on releasing itself. Tomorrow will use it to release bio4j/bio4j and bio4j/neo4jdb.

[laughedelic]

Released 0.4.0-M4 which makes release process even more flexible, configurable and nice.

• fix bug: something is wrong with tagging, some old commit is tagged and then the final step can't push the right tag.

[laughedelic]

TODO
don't forget to update to the sbt-release 0.8.3 with the fix

[laughedelic]

TODO
just saw an update of sbt-assembly with improvements and bugfixes

[laughedelic]

Finally, it happened! 🚢
We have v0.4.0