| Summary: | "dropins" folder not identified by Orion server | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Pradyut Sarma <pradyutksarma> |
| Component: | Server | Assignee: | Project Inbox <orion.server-inbox> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P4 | CC: | john.arthorne, ken_walker, kitlo, malgorzata.tomczyk, simon_kaegi, Szymon.Brandys |
| Version: | 0.3 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 374414 | ||
|
Description
Pradyut Sarma
The same story with language packs. We have to modify bundles.info to add them. We should address it in .5. (In reply to comment #1) > The same story with language packs. We have to modify bundles.info to add them. > We should address it in .5. I just got off from ST with Kit Lo (from globalization), he said that we should have a simpler scenario for installing language packs. I have to say that at first we'll be translated to 14 languages, having 4 bundles each, gives 56 bundles to be added to bundle.info, if administrator wants to add all of them. I talked to Simon about dropins folder and p2 support. It seems that for Orion a better way would be a mechanism that configures Orion packs on download time. It could work like this: - the user opens the download page - sets what he wants in the Orion pack (ssl, supported OpenID providers etc.) - the download site prepares the pack for him - the user downloads it and does not have to configure anything else It would be like our Eclipse SDK download site where we already have packs for EE, Java Dev or C Dev. The idea for Orion is to make this mechanism more dynamic. So if the user chooses to have Polish support, this mechanism would prepare and publish an Orion pack with Polish language packs and bundles.info updated. We changed the installation of language pack plugins to client-site. In this case "dropins" folder is no longer critical for the globalization. It is however still needed for the other mentioned use cases. I'm incredibly reluctant to support dropins in a server environment for the out of the box Orion server however a custom implementation is free to do what it likes. |