You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by Guillaume Nodet <gn...@gmail.com> on 2008/09/25 15:35:08 UTC
[DISCUSS] Releasing components
I think we can start releasing a first run of all components now.
In order to do so, we need to release the components-pom first, but
the current svn tree set up is done so that all components are under
components-pom using svn:externals.
I think it would make things easier if we create another svn tree in
https://svn.apache.org/repos/asf/servicemix/components/all/
which would contain a root pom with svn externals for ease of build.
This would allow removing those from the components-pom/trunk, and
they would then not appear in the tags and make releasing the
components-pom easier (no need to hack / remove all the modules from
the pom before releasing).
Anyway, feedback is welcome on both topics.
Btw, in order to release the CXF components, we'll need to use a non
snapshot dependency. Any problems reverting to the latest release of
Apache CXF ? Also, I haven't grepped the whole tree atm but if you
are aware of any other snapshot dependencies ... we'll have to remove
those before releasing.
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://open.iona.com
Re: [DISCUSS] Releasing components
Posted by Edell Nolan <ed...@gmail.com>.
+1.
It would be good to get a release of the maven plugins.
On Fri, Sep 26, 2008 at 1:07 PM, Gert Vanthienen
<ge...@skynet.be>wrote:
> Guillaume Nodet wrote:
>
>> I think we can start releasing a first run of all components now.
>> In order to do so, we need to release the components-pom first, but
>> the current svn tree set up is done so that all components are under
>> components-pom using svn:externals.
>> I think it would make things easier if we create another svn tree in
>> https://svn.apache.org/repos/asf/servicemix/components/all/
>> which would contain a root pom with svn externals for ease of build.
>> This would allow removing those from the components-pom/trunk, and
>> they would then not appear in the tags and make releasing the
>> components-pom easier (no need to hack / remove all the modules from
>> the pom before releasing).
>> Anyway, feedback is welcome on both topics.
>>
>>
> +1, we probably want to do the same thing for the maven-plugins btw...
>
>> Btw, in order to release the CXF components, we'll need to use a non
>> snapshot dependency. Any problems reverting to the latest release of
>> Apache CXF ? Also, I haven't grepped the whole tree atm but if you
>> are aware of any other snapshot dependencies ... we'll have to remove
>> those before releasing
>>
>
> I'd say we try to release all the components asap, downgrading to CXF 2.1.2
> to do the release now and do another servicemix-cxf-bc/se release once CXF
> 2.1.3 is out
>
>
> Regards,
>
> Gert
>
Re: [DISCUSS] Releasing components
Posted by Freeman Fang <fr...@gmail.com>.
Gert Vanthienen wrote:
> Guillaume Nodet wrote:
>> I think we can start releasing a first run of all components now.
>> In order to do so, we need to release the components-pom first, but
>> the current svn tree set up is done so that all components are under
>> components-pom using svn:externals.
>> I think it would make things easier if we create another svn tree in
>> https://svn.apache.org/repos/asf/servicemix/components/all/
>> which would contain a root pom with svn externals for ease of build.
>> This would allow removing those from the components-pom/trunk, and
>> they would then not appear in the tags and make releasing the
>> components-pom easier (no need to hack / remove all the modules from
>> the pom before releasing).
>> Anyway, feedback is welcome on both topics.
>>
> +1, we probably want to do the same thing for the maven-plugins btw...
>> Btw, in order to release the CXF components, we'll need to use a non
>> snapshot dependency. Any problems reverting to the latest release of
>> Apache CXF ? Also, I haven't grepped the whole tree atm but if you
>> are aware of any other snapshot dependencies ... we'll have to remove
>> those before releasing
>
> I'd say we try to release all the components asap, downgrading to CXF
> 2.1.2 to do the release now and do another servicemix-cxf-bc/se
> release once CXF 2.1.3 is out
Already downgrade to cxf 2.1.2, so cxf component is also ready to go. :-)
>
>
> Regards,
>
> Gert
>
Re: [DISCUSS] Releasing components
Posted by Gert Vanthienen <ge...@skynet.be>.
Guillaume Nodet wrote:
> I think we can start releasing a first run of all components now.
> In order to do so, we need to release the components-pom first, but
> the current svn tree set up is done so that all components are under
> components-pom using svn:externals.
> I think it would make things easier if we create another svn tree in
> https://svn.apache.org/repos/asf/servicemix/components/all/
> which would contain a root pom with svn externals for ease of build.
> This would allow removing those from the components-pom/trunk, and
> they would then not appear in the tags and make releasing the
> components-pom easier (no need to hack / remove all the modules from
> the pom before releasing).
> Anyway, feedback is welcome on both topics.
>
+1, we probably want to do the same thing for the maven-plugins btw...
> Btw, in order to release the CXF components, we'll need to use a non
> snapshot dependency. Any problems reverting to the latest release of
> Apache CXF ? Also, I haven't grepped the whole tree atm but if you
> are aware of any other snapshot dependencies ... we'll have to remove
> those before releasing
I'd say we try to release all the components asap, downgrading to CXF
2.1.2 to do the release now and do another servicemix-cxf-bc/se release
once CXF 2.1.3 is out
Regards,
Gert
Re: [DISCUSS] Releasing components
Posted by Freeman Fang <fr...@gmail.com>.
Hi Willem,
But cxf 2.1.3 is not released, right?
We need some fixes which check in after cxf 2.1.2 release.
Regards
Freeman
Willem Jiang wrote:
> Hi Freeman,
>
> I think the CXF version should be 2.1.3, since 2.1.2 has been released
> for a while :)
>
> Willem
>
>
> Freeman Fang wrote:
>>
>> Guillaume Nodet wrote:
>>> I think we can start releasing a first run of all components now.
>>> In order to do so, we need to release the components-pom first, but
>>> the current svn tree set up is done so that all components are under
>>> components-pom using svn:externals.
>>> I think it would make things easier if we create another svn tree in
>>> https://svn.apache.org/repos/asf/servicemix/components/all/
>>> which would contain a root pom with svn externals for ease of build.
>>> This would allow removing those from the components-pom/trunk, and
>>> they would then not appear in the tags and make releasing the
>>> components-pom easier (no need to hack / remove all the modules from
>>> the pom before releasing).
>>> Anyway, feedback is welcome on both topics.
>>>
>> +1 for this.
>>
>>> Btw, in order to release the CXF components, we'll need to use a non
>>> snapshot dependency. Any problems reverting to the latest release of
>>> Apache CXF ? Also, I haven't grepped the whole tree atm but if you
>>> are aware of any other snapshot dependencies ... we'll have to remove
>>> those before releasing.
>>>
>> The latest cxf release 2.1.2 is not enough, we need CXF-1755/CXF-1760
>> to fix SM-1508 and CXF-1779 to fix SM-1526, those issue get fixed
>> after cxf2.1.2 release
>>
>> Regards
>> Freeman
>>
>>
>
>
Re: [DISCUSS] Releasing components
Posted by Freeman Fang <fr...@gmail.com>.
Hi Guillaume,
Downgrade to 2.1.2 should be fine if I comment out two test case, which
means SM-1508 and SM-1526 won't be fixed by this bundle of releases.
That's good for me to do another cxf component release when cxf 2.1.3 is
ready.
I will revert it soon
Regards
Freeman
Guillaume Nodet wrote:
> Yes, it's currently 2.1.3-SNAPSHOT.
>
> What about downgrading to 2.1.2, release all the components, and
> revert to 2.1.3-SNAPSHOT. Then, when CXF 2.1.3 is released, we can
> release new versions of the CXF based components.
> One of the goal when splitting the components was to be able to
> release them independandly, so that one snapshot dependency does not
> hold everything. This will also allow releasing components more
> regularly when we fix bugs in those.
>
> On Fri, Sep 26, 2008 at 10:09 AM, Willem Jiang <wi...@gmail.com> wrote:
>
>> Hi Freeman,
>>
>> I think the CXF version should be 2.1.3, since 2.1.2 has been released for a
>> while :)
>>
>> Willem
>>
>>
>> Freeman Fang wrote:
>>
>>> Guillaume Nodet wrote:
>>>
>>>> I think we can start releasing a first run of all components now.
>>>> In order to do so, we need to release the components-pom first, but
>>>> the current svn tree set up is done so that all components are under
>>>> components-pom using svn:externals.
>>>> I think it would make things easier if we create another svn tree in
>>>> https://svn.apache.org/repos/asf/servicemix/components/all/
>>>> which would contain a root pom with svn externals for ease of build.
>>>> This would allow removing those from the components-pom/trunk, and
>>>> they would then not appear in the tags and make releasing the
>>>> components-pom easier (no need to hack / remove all the modules from
>>>> the pom before releasing).
>>>> Anyway, feedback is welcome on both topics.
>>>>
>>>>
>>> +1 for this.
>>>
>>>
>>>> Btw, in order to release the CXF components, we'll need to use a non
>>>> snapshot dependency. Any problems reverting to the latest release of
>>>> Apache CXF ? Also, I haven't grepped the whole tree atm but if you
>>>> are aware of any other snapshot dependencies ... we'll have to remove
>>>> those before releasing.
>>>>
>>>>
>>> The latest cxf release 2.1.2 is not enough, we need CXF-1755/CXF-1760 to
>>> fix SM-1508 and CXF-1779 to fix SM-1526, those issue get fixed after
>>> cxf2.1.2 release
>>>
>>> Regards
>>> Freeman
>>>
>>>
>>>
>>
>
>
>
>
Re: [DISCUSS] Releasing components
Posted by Guillaume Nodet <gn...@gmail.com>.
Yes, it's currently 2.1.3-SNAPSHOT.
What about downgrading to 2.1.2, release all the components, and
revert to 2.1.3-SNAPSHOT. Then, when CXF 2.1.3 is released, we can
release new versions of the CXF based components.
One of the goal when splitting the components was to be able to
release them independandly, so that one snapshot dependency does not
hold everything. This will also allow releasing components more
regularly when we fix bugs in those.
On Fri, Sep 26, 2008 at 10:09 AM, Willem Jiang <wi...@gmail.com> wrote:
> Hi Freeman,
>
> I think the CXF version should be 2.1.3, since 2.1.2 has been released for a
> while :)
>
> Willem
>
>
> Freeman Fang wrote:
>>
>> Guillaume Nodet wrote:
>>>
>>> I think we can start releasing a first run of all components now.
>>> In order to do so, we need to release the components-pom first, but
>>> the current svn tree set up is done so that all components are under
>>> components-pom using svn:externals.
>>> I think it would make things easier if we create another svn tree in
>>> https://svn.apache.org/repos/asf/servicemix/components/all/
>>> which would contain a root pom with svn externals for ease of build.
>>> This would allow removing those from the components-pom/trunk, and
>>> they would then not appear in the tags and make releasing the
>>> components-pom easier (no need to hack / remove all the modules from
>>> the pom before releasing).
>>> Anyway, feedback is welcome on both topics.
>>>
>>
>> +1 for this.
>>
>>> Btw, in order to release the CXF components, we'll need to use a non
>>> snapshot dependency. Any problems reverting to the latest release of
>>> Apache CXF ? Also, I haven't grepped the whole tree atm but if you
>>> are aware of any other snapshot dependencies ... we'll have to remove
>>> those before releasing.
>>>
>>
>> The latest cxf release 2.1.2 is not enough, we need CXF-1755/CXF-1760 to
>> fix SM-1508 and CXF-1779 to fix SM-1526, those issue get fixed after
>> cxf2.1.2 release
>>
>> Regards
>> Freeman
>>
>>
>
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://open.iona.com
Re: [DISCUSS] Releasing components
Posted by Willem Jiang <wi...@gmail.com>.
Hi Freeman,
I think the CXF version should be 2.1.3, since 2.1.2 has been released
for a while :)
Willem
Freeman Fang wrote:
>
> Guillaume Nodet wrote:
>> I think we can start releasing a first run of all components now.
>> In order to do so, we need to release the components-pom first, but
>> the current svn tree set up is done so that all components are under
>> components-pom using svn:externals.
>> I think it would make things easier if we create another svn tree in
>> https://svn.apache.org/repos/asf/servicemix/components/all/
>> which would contain a root pom with svn externals for ease of build.
>> This would allow removing those from the components-pom/trunk, and
>> they would then not appear in the tags and make releasing the
>> components-pom easier (no need to hack / remove all the modules from
>> the pom before releasing).
>> Anyway, feedback is welcome on both topics.
>>
> +1 for this.
>
>> Btw, in order to release the CXF components, we'll need to use a non
>> snapshot dependency. Any problems reverting to the latest release of
>> Apache CXF ? Also, I haven't grepped the whole tree atm but if you
>> are aware of any other snapshot dependencies ... we'll have to remove
>> those before releasing.
>>
> The latest cxf release 2.1.2 is not enough, we need CXF-1755/CXF-1760
> to fix SM-1508 and CXF-1779 to fix SM-1526, those issue get fixed
> after cxf2.1.2 release
>
> Regards
> Freeman
>
>
Re: [DISCUSS] Releasing components
Posted by Freeman Fang <fr...@gmail.com>.
Guillaume Nodet wrote:
> I think we can start releasing a first run of all components now.
> In order to do so, we need to release the components-pom first, but
> the current svn tree set up is done so that all components are under
> components-pom using svn:externals.
> I think it would make things easier if we create another svn tree in
> https://svn.apache.org/repos/asf/servicemix/components/all/
> which would contain a root pom with svn externals for ease of build.
> This would allow removing those from the components-pom/trunk, and
> they would then not appear in the tags and make releasing the
> components-pom easier (no need to hack / remove all the modules from
> the pom before releasing).
> Anyway, feedback is welcome on both topics.
>
+1 for this.
> Btw, in order to release the CXF components, we'll need to use a non
> snapshot dependency. Any problems reverting to the latest release of
> Apache CXF ? Also, I haven't grepped the whole tree atm but if you
> are aware of any other snapshot dependencies ... we'll have to remove
> those before releasing.
>
The latest cxf release 2.1.2 is not enough, we need CXF-1755/CXF-1760 to
fix SM-1508 and CXF-1779 to fix SM-1526, those issue get fixed after
cxf2.1.2 release
Regards
Freeman
Re: [DISCUSS] Releasing components
Posted by Lars Heinemann <la...@compart.net>.
Am Donnerstag 25 September 2008 15:35:08 schrieb Guillaume Nodet:
> I think we can start releasing a first run of all components now.
> In order to do so, we need to release the components-pom first, but
> the current svn tree set up is done so that all components are under
> components-pom using svn:externals.
> I think it would make things easier if we create another svn tree in
> https://svn.apache.org/repos/asf/servicemix/components/all/
> which would contain a root pom with svn externals for ease of build.
> This would allow removing those from the components-pom/trunk, and
> they would then not appear in the tags and make releasing the
> components-pom easier (no need to hack / remove all the modules from
> the pom before releasing).
> Anyway, feedback is welcome on both topics.
>
+1
> Btw, in order to release the CXF components, we'll need to use a non
> snapshot dependency. Any problems reverting to the latest release of
> Apache CXF ? Also, I haven't grepped the whole tree atm but if you
> are aware of any other snapshot dependencies ... we'll have to remove
> those before releasing.
>
No idea here but having a non-snapshot versions of deps is mandatory I think
(as far as possible).