Hey Daz, Thanks. Is the DSL for “ivy-publish” about to change as well (it’s @Incubating, just like Binary!), or is it just the classes and interfaces like SoftwareComponent?
-- Lóránt On Wednesday 23 July 2014 at 23:03, Daz DeBoer wrote: > Hey > Nope, this is not future-proof and is likely to change substantially in the > coming months. There's a lot of work going on in order to allow custom > component models, which will feed into both dependency resolution and > publishing. But for now, only use this if you're prepared to keep updated > with the changes. > Daz > > > > On Wed, Jul 23, 2014 at 2:58 PM, Lóránt Pintér <lorant.pin...@prezi.com > (mailto:lorant.pin...@prezi.com)> wrote: > > Hi, > > > > Is it future-proof to create my own SoftwareComponents to be published via > > “ivy-publishing”? Does anyone do this already except for the Java and War > > plugins? > > > > I’m asking this because SoftwareComponent is in an internal package, and > > I’ve had some bad experiences with non-stable APIs changing in Gradle 2.0 > > (I’m looking at you, Binary). :) > > > > Thanks. > > > > -- > > > > Lóránt Pintér > > > > > > Developer at Prezi (http://prezi.com) > > > > > > > > > > > > > > -- > Darrell (Daz) DeBoer > http://www.gradleware.com (http://www.gradleware.com/)
