Hi,
Interesting plugin. I'm looking for an alternative to default ivy deployer to deploy to webdav repositories.
How to override "publish" task with this plugin by default?
Thanks
Damien
--
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.
> I will see if its possible to convince aether to make this work as
> well, but for now this is the one caveat.
Arf, so I will have to wait, I need it to deploy a sbt-plugin.
Anyway, good work.
Thanks
Damien
Looking into this now. Should be easy enough to add.
--
--
The sbt binary version is encoded as an extra attribute, as well as the Scala binary version. Aether can *encode* the value but not use it. So it cannot distinguish between cross published versions. That means the "addSbtPlugin" functions don't work.
I've also dabbled in whether + sbt. Given the way sbt does some components/plugins you're never going to be able to replace ivy with aether. It's unfortunate since ivy caching is terrible.
However for publishing it's a fine idea. I'd just recommend against supporting plugins.
Just watch out for optional components and artifacts where pom/artifact don't match. Aether had a terrible time resolving without writing your own resolver.
Awesome, I'll take a look shortly.
I see. You're adding custom support for sbt-isms. If this has no negative effect on caching and resolution, I'm more than willing to jump in and help. Resolving is where I gave up.