Community
Participate
Working Groups
MTJ currently contains embedded sign components which could be refactored to be more generic in order to be move into TFM (Tools For Mobile) project: * Signing Framework: A generic framework to digitally sign created packages like MIDlets * Certificate Manager: A user friendly UI to create, store and share code signing certificates Those components could be moved from MTJ to the new project, while MTJ would retain the "Mobile Java" specific code, like e.g. a MIDlet signing extension which plugs into the new "generic signing framework". The first action should be requirements definition and then we should evaluate the code we already have(current MTJ impl and MTJ 0.7 signing Framework) in order to reuse at least some part of it. We must start the discussion about the best approach to be followed.
Diego, My and Christian's requirements are below. Mauren Brenner from the TmL team will supply the ones that she has. 1) re-use as much of the existing code as possible (Platform, MTJ, old MTJ) 2) make it as flexible as reasonable possible, cover at least MIDP and Android requirements 3) allow to register new "signing providers" with a Eclipse plug-in mechanism, so that support/customization for specific platform requirements can be added as separate packaged plug-ins. 4) try to anticipate a Symbian signing scenario. No need to develop it, but don't make it impossible to add. 5) Provide hooks in the UI into the Project Navigator (sign package, unsign package) and the main menu. 6) Provide hooks into the build process so that post-build signing can be easily included -E
Thanks Eric. for now, I'll start prototyping on the mtj repository. I'll reuse part of the old implementation from the mtj 0.7 for the "signing providers" and the UI from our latest Releases. The Pre/Pos sign hooks could be similar to the one we have on the build process. I'll also study about Symbian signing to anticipate this scenario. I'll be waiting for Mauren's requirements and I would also like to hear the opinion from Jon about possible requirements. Thanks, Diego
I am lowering the priority of this one. It does not seem that critical... Eric is this someting that is worked as part of sequoyah?
Resolving this one as MTJ has no immediate need to refactor the signing API.. We can use a refactored one if it is provided elsewhere though.
