Eclipse Community Forums: Dirigible » New Repository Structure

Home » Eclipse Projects » Dirigible » New Repository Structure(Restructuring current Repository hierarchy )

New Repository Structure [message #1763315]

Fri, 12 May 2017 10:43

Eclipse User

Hi Team,

For the new release I thing it's time to have some changes in the Repository.

1. Remove '/db/dirigible' root collection, as it doesn't bring any value
2. Remove the mandatory semantic folders (e.g. 'DataStructures', 'ScriptingServices', 'WebContent', ...)
3. The publish process to be simple 'copy/paste' from the Workspace to the Registry
4. Publish updaters will work based on the file extension, as of now, for the whole Repository
5. The Preview of the artifacts will be dependent by the file extension:
5.1 *.html to be rendered
5.2 *.js will be considered to be executed server-side
6. For the runtime access the 'semantic' path will be still needed, as of now
- /js/example/service.js will be executed server-side
- /web/example/app.js will be executed client-side

Regards,
Yordan

Re: New Repository Structure [message #1763323 is a reply to message #1763315]

Fri, 12 May 2017 11:36

Eclipse User

Hi Yordan,

This proposal looks simpler and much more straight forward than what we have now, I like it.
Something which have to be mentioned is that with this structure the project name will be part of the service module e.g. var myModule1 = require("my_project/some_package/my_module1") which is not necessary a bad thing of course.

Regards,
Nedelcho

Re: New Repository Structure [message #1763327 is a reply to message #1763323]

Fri, 12 May 2017 12:19

Eclipse User

Hi Nedelcho,

What about projects migration?
How we will achieve backward compatibility for projects built with the 2.x version, or at least what will be the migration path?

One possible way is during import to look for the semantic folders, ignore them, ignore the project name and import packages as a top level projects. So in this way project with the following stricture [1] will be imported as [2].

[1]
Example/ScriptingService
/module1/test.js
/module2/test2.js

[2]
module1/test.js
module2/test2.js

Note: module1 and module2 are top level projects!

Regards,
Yordan

Re: New Repository Structure [message #1763332 is a reply to message #1763327]

Fri, 12 May 2017 13:18

Eclipse User

We can have issues with the Git sourced projects in this way. Of course, we can revise the Project:Repository 1:1 decision as well

Re: New Repository Structure [message #1763405 is a reply to message #1763332]

Mon, 15 May 2017 07:10

Eclipse User

New Repository structure proposal:


/registry
  /public
    /<project_name>
        /<artefact_name>
  /settings
    /<setting_group>
      /<setting_file>
  /templates
    /<template_name>
      /<template_artefact_name>
/users
  /<user_name>
    /<workspace_name>
      /<project_name>
        /<artefact_name>

Previous Topic:	Remove Semantic Folders
Next Topic:	Vert.x for reactive apps

Goto Forum:

-=] Back to Top [=-

Current Time: Wed Apr 30 15:26:55 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter