Disabling some of the specialpurpose components

[Jacopo Cappellato-4]

We have recently discussed the idea of keeping all the specialpurpose components in the trunk, remove them from future release branches (starting with 13.04 that will probably still contain the ecommerce component because a lot unit tests are based on demo data in it and because of some other minor dependencies) but considering them as "optional", meaning that the community may not maintain them updated.
This seems to be a good compromise between the advantage for the community to have a smaller codebase to maintain to a good quality level (taking care of bug fix releases etc...) and the interest in keeping in the official trunk some specialized/experimental code that may be of interest to smaller groups or that could be resurrected over time.
I would like to go ahead with this plan and disable (i.e. remove from the default build/test process and disable as components) the following two components: "crowd" and "birt".
The main reason is that they both require the very old Axis "1" jar files (published in 2006) that are now in the framework/service component and are not used anymore because a few years ago we upgraded the core components to "Axis 2". In short I would like to:
1) remove the old "Axis 1" jars from the framework
2) disable "crowd" and "birt" components so that they are excluded by the compile task by default; all the code will stay in the trunk
If someone is interested in upgrading them then we could re-enable them at a later point (even if there are other disadvantages in both components that we should address).

WDYT?

Jacopo

[Jacques Le Roux]

+1

Jacques

From: "Jacopo Cappellato" <[hidden email]>

> We have recently discussed the idea of keeping all the specialpurpose components in the trunk, remove them from future release branches (starting with 13.04 that will probably still contain the ecommerce component because a lot unit tests are based on demo data in it and because of some other minor dependencies) but considering them as "optional", meaning that the community may not maintain them updated.
> This seems to be a good compromise between the advantage for the community to have a smaller codebase to maintain to a good quality level (taking care of bug fix releases etc...) and the interest in keeping in the official trunk some specialized/experimental code that may be of interest to smaller groups or that could be resurrected over time.
> I would like to go ahead with this plan and disable (i.e. remove from the default build/test process and disable as components) the following two components: "crowd" and "birt".
> The main reason is that they both require the very old Axis "1" jar files (published in 2006) that are now in the framework/service component and are not used anymore because a few years ago we upgraded the core components to "Axis 2". In short I would like to:
> 1) remove the old "Axis 1" jars from the framework
> 2) disable "crowd" and "birt" components so that they are excluded by the compile task by default; all the code will stay in the trunk
> If someone is interested in upgrading them then we could re-enable them at a later point (even if there are other disadvantages in both components that we should address).
>
> WDYT?
>
> Jacopo
>
>

[hans_bakker]

for birt -1

regards,
Hans
On 04/05/2013 09:52 PM, Jacopo Cappellato wrote:

> We have recently discussed the idea of keeping all the specialpurpose components in the trunk, remove them from future release branches (starting with 13.04 that will probably still contain the ecommerce component because a lot unit tests are based on demo data in it and because of some other minor dependencies) but considering them as "optional", meaning that the community may not maintain them updated.
> This seems to be a good compromise between the advantage for the community to have a smaller codebase to maintain to a good quality level (taking care of bug fix releases etc...) and the interest in keeping in the official trunk some specialized/experimental code that may be of interest to smaller groups or that could be resurrected over time.
> I would like to go ahead with this plan and disable (i.e. remove from the default build/test process and disable as components) the following two components: "crowd" and "birt".
> The main reason is that they both require the very old Axis "1" jar files (published in 2006) that are now in the framework/service component and are not used anymore because a few years ago we upgraded the core components to "Axis 2". In short I would like to:
> 1) remove the old "Axis 1" jars from the framework
> 2) disable "crowd" and "birt" components so that they are excluded by the compile task by default; all the code will stay in the trunk
> If someone is interested in upgrading them then we could re-enable them at a later point (even if there are other disadvantages in both components that we should address).
>
> WDYT?
>
> Jacopo
>

[Jacopo Cappellato-4]

In revision 1465250 I have disabled crowd.
Good news Hans: this time it didn't require much of my work and I was able to save the birt component by copying to it the old Axis 1 jars (in rev. 1465252); so we can keep it enabled and it will still compile and run even if the framework is no more using the old Axis.
By the way I would like to mention that sooner or later someone will have to take care of the issues affecting this component and make it shine, keeping it updated and clean or, if the community doesn't maintain it properly, we will have to disable it when it will cause more problems. Please also remember that when you cast -1 votes, in order to be valid they need to come with a motivation and a solution (in this specific example, you could have offered your help to maintain it and upgrade to the new Axis 2)... by the way, everything is good now and no need to further discuss.

Kind regards,

Jacopo

On Apr 6, 2013, at 1:19 PM, Hans Bakker <[hidden email]> wrote:

> for birt -1
>
> regards,
> Hans
> On 04/05/2013 09:52 PM, Jacopo Cappellato wrote:
>> We have recently discussed the idea of keeping all the specialpurpose components in the trunk, remove them from future release branches (starting with 13.04 that will probably still contain the ecommerce component because a lot unit tests are based on demo data in it and because of some other minor dependencies) but considering them as "optional", meaning that the community may not maintain them updated.
>> This seems to be a good compromise between the advantage for the community to have a smaller codebase to maintain to a good quality level (taking care of bug fix releases etc...) and the interest in keeping in the official trunk some specialized/experimental code that may be of interest to smaller groups or that could be resurrected over time.
>> I would like to go ahead with this plan and disable (i.e. remove from the default build/test process and disable as components) the following two components: "crowd" and "birt".
>> The main reason is that they both require the very old Axis "1" jar files (published in 2006) that are now in the framework/service component and are not used anymore because a few years ago we upgraded the core components to "Axis 2". In short I would like to:
>> 1) remove the old "Axis 1" jars from the framework
>> 2) disable "crowd" and "birt" components so that they are excluded by the compile task by default; all the code will stay in the trunk
>> If someone is interested in upgrading them then we could re-enable them at a later point (even if there are other disadvantages in both components that we should address).
>>
>> WDYT?
>>
>> Jacopo
>>
>

[Medhat]

+1

Medhat


On Fri, Apr 5, 2013 at 4:52 PM, Jacopo Cappellato <
[hidden email]> wrote:

> We have recently discussed the idea of keeping all the specialpurpose
> components in the trunk, remove them from future release branches (starting
> with 13.04 that will probably still contain the ecommerce component because
> a lot unit tests are based on demo data in it and because of some other
> minor dependencies) but considering them as "optional", meaning that the
> community may not maintain them updated.
> This seems to be a good compromise between the advantage for the community
> to have a smaller codebase to maintain to a good quality level (taking care
> of bug fix releases etc...) and the interest in keeping in the official
> trunk some specialized/experimental code that may be of interest to smaller
> groups or that could be resurrected over time.
> I would like to go ahead with this plan and disable (i.e. remove from the
> default build/test process and disable as components) the following two
> components: "crowd" and "birt".
> The main reason is that they both require the very old Axis "1" jar files
> (published in 2006) that are now in the framework/service component and are
> not used anymore because a few years ago we upgraded the core components to
> "Axis 2". In short I would like to:
> 1) remove the old "Axis 1" jars from the framework
> 2) disable "crowd" and "birt" components so that they are excluded by the
> compile task by default; all the code will stay in the trunk
> If someone is interested in upgrading them then we could re-enable them at
> a later point (even if there are other disadvantages in both components
> that we should address).
>
> WDYT?
>
> Jacopo
>
>