Community
Participate
Working Groups
+++ This bug was initially created as a clone of Bug #226471 +++ See bug 226471 for some of the history, but the short story is for expediency, we worked around a PDE build limitation (when there are cycles in the build dependencies) by "force" ... removing some "import-package javax.mail* " from the javax.activation bundle (since the mail bundle has import packages from javax.activation). If/when bug 208011 get's fixed, we should consider putting back in the import packages into javax.activation bundle to make sure no runtime behavior is broken.
BIRT and MYLIN Teams, can you please can you peek at bug 273060? I'm confusing myself, and wondering if it was the "commons.logging" and "javax.naming" packages that were causing you before during your builds? Do you recall?
I don't recall any problems with our build related to javax.activation. We currently neither depend directly on javax.activation or javax.mail. We do use org.apache.axis 1.4 but we get that as a pre-compiled bundle from Orbit.
Doing a mass "reset to default assignee" of 21 bugs to help make clear it will (very likely) not be me working on things I had previously planned to work on. I hope this will help prevent the bugs from "getting lost" in other people's queries. Feel free to "take" a bug if appropriate.