On 12-05-07 10:42 AM, Mck wrote:
On Mon, 2012-05-07 at 09:55 -0400, Nicolas LE BAS wrote:
No, it doesn't help with tiles-request-* depending on
tiles-autotag-core-runtime and tiles-autotag-* depending on
tiles-request-api :-(
I'm not sure I understand your point. BTW, in order to be inclusive,
tiles-* depends on those two artifacts, too.
You can't build the tiles-request-1.0 project without
tiles-autotag-core-runtime-1.0
And you can't build the tiles-autotag-1.0 project without
tiles-request-api-1.0
In the case where you are developing both projects forward things get
difficult. Normally this won't be the case though.
Actually the dependency is currently very thin, even if maven doesn't
show it: tiles-autotag only needs the interface
org.apache.tiles.request.Request to be there. It doesn't even calls its
methods directly, it just passes the request along to the appropriate
tag model. So as long as we don't remove Request, we should be able to
evolve tiles-request without impacting autotag. Sounds rather safe :)
So in the case we want to develop both projects forward, we have to
start with tiles-autotag-core-runtime.
Just being curious: do you currently have plans to develop the autotag SPI?
Nick.
