Adam Murdoch wrote:
In the vein of give me an inch and I'll take a mile, I'm wondering if
it would be a good idea to have an option that somehow combines the
buildScript dependency with the apply as separate in option (3) above.
Something like:
apply module:'groupId:artifact:version'
...with a default plug-in loaded or even spec'ed on the apply.
It combines the convenience of deployment style (1) with the
versioning and caching of (3).
Just a thought.
It's a good thought.
I like to separate how the plugin is packaged (ie in a script, or
classes in a jar, or as source in a directory, or scripts in jar) from
where the plugin is packaged (ie at a URL, in a repository, somewhere in
buildSrc) so that you can mix and match. That is, you should be able to
apply a plugin from a repository, whether it is packaged in a jar or as
a script. You should be able to apply a plugin from a URL, whether it is
packaged in a jar or as a script. And so on, for plugins in buildSrc, etc.
Any thoughts on how this would work?
I'm just trying to think of a way to easily publish something like my
website plug-in (that may itself contain resources and other
dependencies) in a way that is as simple as the apply url:'' form but
that is versioned and cached like any other build script dependency.
It will be interesting to see how this develops. It's already 1000x
easier to write simple plug-ins in 0.9 as it is.
-Paul
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
