L.S., That would be one option. On the infra@ list, there also was another suggestion: instead of creating the full assembly with everything in there, we could create an offline-system.zip file that contains the bits that are missing from the default assembly. That way, the offline repository could just be extracted on top of a default installation.
Wdyt? Gert Vanthienen On Tue, Jul 16, 2013 at 12:45 PM, Geaaru <[email protected]> wrote: > Hi Gert, > About problem of size could be a valid solution create a script (ant,bash > or other) that permit download to users of all system directory of the > release without include it directly to bundle? > > My cent > Geaaru > Il giorno 16/lug/2013 10:48, "Gert Vanthienen" <[email protected]> > ha scritto: > >> L.S., >> >> >> I think we are ready to restart the 4.5.2 release. It looks like we >> removed as many of the duplicate bundles as possible and the upgrade >> to Camel 2.10.6 and CXF 2.6.8 was done for both the NMR and Features >> build. >> >> We've just heard back from infra@ on the larger assemblies (with the >> new 200 MB limit, only the -full assembly is problematic, really) but >> we're still working on a solution. Even if we don't have a solution >> (yet) for this assembly, it probably makes sense to go ahead with the >> release build anyway and only publish the other assemblies for now. >> >> I'll start the release builds later today unless anyone objects. >> >> >> Regards, >> >> Gert Vanthienen >>
