You can manually download the required files and install them, or copy the files to the local maven repository ~/.m2/repository/ (I'm not sure of the path in windows, but you can look for It easily)
The local maven repository can be configured in the maven_install_dir/conf/settings.xml if you want to change the location of the local m2 repository on your file system.
I'm not sure if you have some network shares/mounts available, but you could perform your builds on a machine that does have access to the public repositories. I assume that the webconsole is not the only thing you will need to install?
Another option is to set a Nexus server url in the /etc/org.ops4j.pax.url.mvn.cfg file in the org.ops4j.pax.url.mvn.repositories property at the bottom.
In that case your system is still closed, the nexus server is on your local network and it is the nexus server that access the public repositories, instead of your closed system.
We don't want Maven binaries or repositories existing on or accessible by the machine we install Fuse ESB on.
We wish to have a self contained distribution of Fuse ESB with all immediate dependencies and optional dependencies (as defined by uninstalled features), custom components, and configuration modifications already included.
Is there a folder in the Fuse ESB distribution we can dump these dependencies? Maybe that is what the \system folder is for? __shrug__
We do have our dev env setup very similar to what you propose, but our customers will not.
I know this probably mucks around a bit with fundamental concepts/behavior/principals, but thought I'd inquire anyway..
Yeah, put the artifacts into $SMX_HOME/system folder should be fine.