On Thu, 2010-07-08 at 13:01 +1000, Adam Murdoch wrote: [ . . . ] > DefaultPublishArtifact is considered an internal class, and so it's not > included in the API docs. But then, given that the only way to add > custom artifacts is to use this class, it's not really an internal class > after all. Perhaps we should include it in the API. Or fix the original > problem, which is probably a better option. [ . . . ]
Difficult choice. If all concrete PublishArtifact types should be opaque then the DSL ought to be fixed for 0.9 rather than for 0.10 or beyond, so as to avoid people promulgating this "hack". However, this disrupts the plan for getting 0.9 out of the door and so is probably too disruptive. Of course actually publishing the existence of the class then totally destroys the opaqueness even if the presence is rescinded later. So this is not really a viable route. Basically there seems no good solution :-( In the interim I will use the source code as documentation and put a big comment in by build.gradle file saying "this is a hideous hack that shouldn't be and won't be very soon now". Then people will realize that things will get changed for the better as soon as viable. The danger of Google is that it stores code fragments in the index the people can find and treat as idioms for the next 40 years. :-(( Thanks. -- Russel. ============================================================================= Dr Russel Winder t: +44 20 7585 2200 voip: sip:[email protected] 41 Buckmaster Road m: +44 7770 465 077 xmpp: [email protected] London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder
signature.asc
Description: This is a digitally signed message part
