Written before Stefano's response - sorry for the duplication if any. No time to edit now...
Berin Loritsch wrote:
It appears the dust has settled, and it looks like ANT has been decided upon
as the way to go. That's OK with me. The questions I now have are in regards
to the things that I perceived Maven would help with.
I didn't think it was quite that settled, but this is a good part of the discussion either way.
1) Dependency resolution. Let's face it, blocks will depend on other blocks.
That's OK, they're supposed to. The question is for the third party block
developer. How are they going to find the dependencies that they need, or
publish them?
As I understand it, this is a matter of block librarian implementation, and isn't a build consideration. Blocks depend on other blocks only through declared component resolution and pipeline based resource exposure. So, compiling a block (and therefore its build) doesn't need these other implementations to be resolved. Only the deploy step needs them present and that's the domain of the block librarian and block deploy tool isn't it?
If block A defines a component with a method getBlah, and block B has a component that uses that method, how do you compile block B without having the source for block A available? Surely there is _some_ compile time consideration to be made?
<rest-snipped/>
Upayavira
