What I currently set up is that it only rebuilds the wicket-ajax when appropriate profile is enabled. You will run into a problem only if you need to modify the wicket-ajax. If you really have to do that and you are in such hostile environment as you describe then you can always use your local node to build the ts. The wicket ajax itself doesn't have any exe files in deps so far.
On Tue, 7 May 2019 at 22:22, Sven Meier <s...@meiers.net> wrote: > > > Hi Martin, > > > > every company I've worked for uses its internal Nexus as a pull-through > cache. > > > > First thing the frontend plugin is doing? Downloading an exe file from the > webz :( > > > > Sven > > > > > > > > > > > > > On 07.05.2019 at 12:12, <Martin Grigorov> wrote: > > > > > > On Mon, May 6, 2019 at 12:54 PM Sven Meier wrote: > > > Sure, but > often enough a corporate web proxy/virus scanner will make this > a real > pain :( > Isn't the same valid for Maven dependencies? If you cannot > reach Maven Central then you won't be able to build the Java classes. > > > > > Sven > > > > > > > > > > > > > On > 05.05.2019 at 20:02, wrote: > > > > > > On vrijdag 3 mei 2019 > 17:16:02 CEST Sven Meier wrote: > JS Tests are > not built each time, > so npm is not a requirement to build > Wicket. I'd > like to keep it > that way. With the frontend-maven-plugin it isn't required > to have it > installed on your system. The plugin will download node and npm > as part > of the build. It works on all operating systems. The only problem I > > have with npm is the package- lock.json that keeps changing. Emond > > > > > > >
