Community
Participate
Working Groups
20020515 * start with clean install * unzip SDK REV1 into the install tree before start (from local site, will post tomorrow AM) ... actually I did not unzip - the features/ plugins were left over from the unsuccessful ArrayStoreException install. All the xml files were OK so the failure happened after the commit() pass * the net effect of the above is that I am starting with 2 versions of the SDK in the tree, one nested (REV1) and the other not (base) .... although I do not think this is relevant * when I start, all seems well .... configuration contains the later (nested) version of the feature * however, I noticed that the computed plugin path contains both versions of all fragments (plugins are OK), the exclude list does not contain the fragments. I think this is related to the e-mail I sent with the warn log (IOExceptions on fragment.jar) Attaching relevant files from this test run
Created attachment 840 [details] trace log (std out)
Created attachment 841 [details] .log (see IOExceptions)
Created attachment 842 [details] platform.cfg (fragments not on exclude list)
Fixed fragment issue in HEAD (20020515) SiteFileFactory$PluginIdentifier was returning a bad fragment identifer, thus when adding the map (id,url) to the site, the id was not the one specified in the spec Fixed in HEAD 20050515 (core+ui) verify with next build