redhat-developer-tooling / developer-platform-install

Single Installer for all Red Hat Development Tools and more. Download it form Red Hat Developers Portal web site - http://developers.redhat.com/products/devsuite/overview/.
Apache License 2.0
25 stars 29 forks source link

Prepopulate .m2 and .grapes for most used Fuse versions #1254

Open apupier opened 6 years ago

apupier commented 6 years ago

When creating the first Fuse project, a lot of time is required mainly downloading artefacts. (can be 15-20 minutes even with reasonable connection speed). I'm wondering if it would be possible to "hide" this time in the installer when installing Fuse Tooling.

Would it be possible?

What do you think?

tsedmik commented 6 years ago

:+1:

dgolovin commented 6 years ago

That would require a little work of course, but it is possible. What would be required is:

dgolovin commented 6 years ago

@apupier What do you mean by "calling a kind of mvn on a basic Fuse example?" ?

apupier commented 6 years ago

@apupier What do you mean by "calling a kind of mvn on a basic Fuse example?" ?

it is an alternative, instead of downloading the offline repo, the idea would be to call maven a one Fuse example which will download and install dependencies in the local .m2 of the user.

apupier commented 6 years ago

Add maven into list of installable components under Java channel with detection;

I'm not even sure that Maven is required. Currently in Fuse Tooling, it is using the embedded Maven Runtime of m2e. In case we need a Maven call, maybe we can provide a specific "eclipse application" to call Maven from inside JBoss Tools. In case just the repo is copied/installed, Maven might not be required. (seems to be the easiest solution but is it safe?)

apupier commented 6 years ago

as the release cycle of Fuse on one side and Fuse Tooling/DevStudio on the other side are different. It would be nice to be able to change the offline repositories used during installation.

dgolovin commented 6 years ago

That is possible. I did implement something similar in past as an experiment, but have not finished that yet (see https://github.com/redhat-developer-tooling/developer-platform-install/pull/811). Implemented approach would require to publish 'requirement.json' for download on developer portal under devsuite when we want to force installer to download new releases without full installer rebuild.