The build for the jetspeed-api is broken as result of adding the new o.a.j.layout.JetspeedPowerToolFactory interface.
It depends on the jetspeedPowerTool interface which still is defined in the jetspeed-portal component.
Although moving that interface to the jetspeed-api would seem easy enough the do, there is a caveat: it exposes the commons-configuration Configuration class.
And because the jetspeed-api needs to be deployed in the shared/lib context, it would pull in the commons-configuration there too, which we definitely don't want (not even can).
So, this solution more or less isn't going to work out and we need to think of some workaround for it.
Changing the JetspeedPowerTool interface to not expose commons-configuration might be a way to do it, but I'm not sure that's feasible.
I've scanned the (Java) code for usage of the specific method: Configuration getTypeConfiguration(String type, String name, String location), and have found none, but maybe there are extensions out there which might use it?
If not, we could opt for changing the interface and return a Properties object instead.