On Tue, Dec 16, 2008 at 4:12 PM, Rickard Öberg <[email protected]> wrote:
> As a result of this we have refactored all API classes so that > Structure101 says it's "clean" (basically fixing all cyclic package > dependencies), and have also moved everything one level from org.qi4j > into org.qi4j.api, so that it's symmetric with org.qi4j.spi and > org.qi4j.runtime. Overall I think the refactoring is pretty good, but > there's a LOT of changes because of it. Everything that is in OPS4J will > be refactored with it, but any custom projects will require some work, > mainly on imports of packages. > > Those are the main changes coming up (AFAICR). Niclas, what did I miss? Not much, I was about to post this; - The whole Qi4j API should be in its own single package, so we are introducing org.qi4j.api - We have broken out pieces from the org.qi4j.composite package and placed them into org.qi4j.api.mixin, org.qi4j.api.concern, org.qi4j.api.sideeffect and others. - We still have a nastiness with the Service Configuration feature, which brings in the ServiceDescriptor to the API (where it doesn't belong) and with it came a few other bits. We have pushed those around a bit, and still there is problems due to this. BUT, since we also want to refactor the entire Service subsystem to better understand the Hosted vs Imported Services (see QI-149), we will attack this problem when that happens. Expect the ServiceDescriptor and other bits to be relegated to Bootstrap where they belong. I am pretty happy with the work so far, and I think it is better to bite the bullet now, than 2 years down the line. Cheers Niclas _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
