search

angelozerr / tern.java

Use tern.js in Java context
http://ternjs.net/
Other
249 stars 52 forks source link

Build all maven projects at once #271

Open paulvi opened 9 years ago

paulvi commented 9 years ago

It is possible to create new Maven project and put all main Eclipse project (angularjs-Eclipse, tern.java, eclipse-wtp-resources and later eclipse-wtp-json) as modules.

This way there will a build to build all at once and if to keep version the same (please continue to) then update version in all project at once.

It is possible also then to have one solid p2 repository (also as zip archive) for all included. But that will require to have one more place where all features to be included are listed.

@pascalleclercq please comment

Des commentaires sont les bienvenus!

I can do that when agreed.

angelozerr commented 9 years ago

@paulvi I would like to keep a github project per technologies angular, tern, jsbuild-eclipse, etc because I would like to avoid having one wiki which merges those several technologies.

@pascalleclercq will study if it's possible to create a new main github project which references angular, tern.java project (git submodule?) to create an Update site like you wish. We don't know if it's possible to do that.

paulvi commented 9 years ago

@angelozerr

The proposal was not understood. Nothing needs to be changed, but only new project in new repository, that should be cloned into the same folder as angular, tern, jsbuild-eclipse, etc

Then in this super-build all project can be referenced as modules 

<module>../tern.java</module>

Or alternatively those project can be inside this new super-build as git modules, but let's don't do that for now, as git modules are good for non-changing repos. There is some alternative, but that is other issue.

piotrtomiak commented 9 years ago

@paulvi @angelozerr

I think that submodules are very good in this case, even when projects are rapidly changing. Nightly builds would happen per each repo separately anyway. When you would want to do a release/common build, than you would check out appropriate commits for each of the sub-modules repos in the super repo and you would push it to GitHub. The automated process will be able to create a build from that. You can also correctly tag such state.