Prepopulate .m2 and .grapes for most used Fuse versions

[apupier]

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?

• pre-building an offline repository and installing it (I know that fuse is providing some https://access.redhat.com/documentation/en-us/red_hat_jboss_fuse/6.3/html/integration_guide/transtools)
• calling a kind of mvn on a basic Fuse example?

What do you think?

[tsedmik]

👍

[dgolovin]

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

• Add maven into list of installable components under Java channel with detection;
• download maven repo for Fuse from developers.redhat.com download manager service (not access.redhat.com) as part of fuse installer or as separate one;
• configure repo to be used by maven.

[dgolovin]

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

[apupier]

@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]

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]

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]

That is possible. I did implement something similar in past as an experiment, but have not finished that yet (see #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.