You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by Gert Vanthienen <ge...@gmail.com> on 2013/07/16 10:47:32 UTC
Ready for 4.5.2 release?
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
Re: Ready for 4.5.2 release?
Posted by Gert Vanthienen <ge...@gmail.com>.
L.S.,
You're right, off course, that this would solve the problem for the
long run, but from a users' point-of-view it might not be the best
option. It would mean that people would have to download Apache
ServiceMix on their local workstation (or on a machine that has a
working internet connection), extract it there, run the command to add
the extra artifacts and then zip it backup again or transfer it to the
target machine in some way.
Perhaps we could also do both: raise an enhancement JIRA at Karaf to
add support for adding bundles to the system repository through some
command (a kind of feature:go-offline command perhaps?) and ship the
offline-repo.zip as a separate artifact for now?
Regards,
Gert Vanthienen
On Tue, Jul 16, 2013 at 3:50 PM, Ge@@ru <ge...@gmail.com> wrote:
> Yes, it is a solution.
> But in the future yet offline-system.zip file could be arrive to upload
> limit and so a solution with a script for prepare an offline-system.zip
> file directly from user permit to resolve this problem for ever or until
> an asteroid destroy the Earth :)
>
> Bye
>
> On Tue, 2013-07-16 at 14:18 +0200, Gert Vanthienen wrote:
>> 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 <ge...@gmail.com> 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" <ge...@gmail.com>
>> > 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
>> >>
>
>
Re: Ready for 4.5.2 release?
Posted by "Ge@@ru" <ge...@gmail.com>.
Yes, it is a solution.
But in the future yet offline-system.zip file could be arrive to upload
limit and so a solution with a script for prepare an offline-system.zip
file directly from user permit to resolve this problem for ever or until
an asteroid destroy the Earth :)
Bye
On Tue, 2013-07-16 at 14:18 +0200, Gert Vanthienen wrote:
> 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 <ge...@gmail.com> 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" <ge...@gmail.com>
> > 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
> >>
Re: Ready for 4.5.2 release?
Posted by Gert Vanthienen <ge...@gmail.com>.
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 <ge...@gmail.com> 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" <ge...@gmail.com>
> 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
>>
Re: Ready for 4.5.2 release?
Posted by Geaaru <ge...@gmail.com>.
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" <ge...@gmail.com>
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
>