You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by Bruce Atherton <br...@callenish.com> on 2010/06/19 20:38:54 UTC

[VOTE] Remove commercial tasks from Ant

Ant supplies several tasks that require commercial software in order to 
run. This is a problem because the Ant developers do not typically have 
access to the commercial products required to test, maintain, and 
enhance the tasks. It also means that users downloading the binary 
edition of Ant end up with a lot of tasks that they cannot use.

In order to rectify this situation, I'm calling a vote on how to deal 
with these unsupportable tasks. The vote is composed of two parts: 
should we drop support for each of these tasks from the Ant release, and 
should we establish the commercial tasks that have been dropped as 
Antlibs in the sandbox.

1. Should the following commercial tasks be dropped from being 
distributed with the Ant release?

[  ]  Continuous/Synergy tasks:  CCMCheckin, CCMCheckout, 
CCMCheckinTask, CCMReconfigure, CCMCreateTask
[  ]  Clearcase tasks: CCCheckin, CCCheckout, CCUnCheckout, CCUpdate, 
CCMklbtype, CCMklabel, CCRmtype, CCLock, CCUnlock, CCMkbl, CCMkattr, 
CCMkdir, CCMkelem
[  ]  Perforce Tasks: P4Sync, P4Change, P4Edit, P4Submit, P4Have, 
P4Label, P4Labelsync, P4Counter, P4Reopen, P4Revert, P4Add, P4Delete, 
P4Integrate, P4Resolve, P4Fstat
[  ]  PVCS
[  ]  ServerDeploy, but only for the jonas and weblogic nested elements, 
generic can stay where it is.
[  ]  Source Offsite: sosget, soslabel, soscheckin, soscheckout
[  ]  Microsoft Visual SourceSafe (already an Antlib)

2. Should the commercial tasks that are voted for dropping from Ant core 
above be established in their own Antlibs in the sandbox?

[  ]  +1 = Yes, establish one new Antlib in the sandbox for each task 
dropped
       -1 = No, just drop the commercial tasks altogether from Ant

Note that question 1 is a  vote for code modification, so any -1 vote on 
question 1 is considered a veto. Question 2 is just for guidance from 
the community about whether there is a desire to keep the commercial 
tasks around in Antlibs. Since any committer can create a sandbox Antlib 
at any time, the vote is non-binding and any -1 vote just indicates that 
the voter does not think that this is a good idea rather than being a veto.

Three or more +1 votes with no -1 votes are required for dropping any of 
the commercial tasks. The vote will end in one week.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Re: [VOTE] Remove commercial tasks from Ant

Posted by Gilles Scokart <gs...@gmail.com>.
On 19 June 2010 20:38, Bruce Atherton <br...@callenish.com> wrote:
>
> 1. Should the following commercial tasks be dropped from being distributed
> with the Ant release?
>
> [  ]  Continuous/Synergy tasks:  CCMCheckin, CCMCheckout, CCMCheckinTask,
> CCMReconfigure, CCMCreateTask
> [  ]  Clearcase tasks: CCCheckin, CCCheckout, CCUnCheckout, CCUpdate,
> CCMklbtype, CCMklabel, CCRmtype, CCLock, CCUnlock, CCMkbl, CCMkattr,
> CCMkdir, CCMkelem
> [  ]  Perforce Tasks: P4Sync, P4Change, P4Edit, P4Submit, P4Have, P4Label,
> P4Labelsync, P4Counter, P4Reopen, P4Revert, P4Add, P4Delete, P4Integrate,
> P4Resolve, P4Fstat
> [  ]  PVCS
> [  ]  ServerDeploy, but only for the jonas and weblogic nested elements,
> generic can stay where it is.
> [  ]  Source Offsite: sosget, soslabel, soscheckin, soscheckout
> [  ]  Microsoft Visual SourceSafe (already an Antlib)
>

+0 For ServerDeploy.  Putting each nested elements in a separate
antlib would give very small antlibs, and if you put all together into
a signle antlib It seems we should rather put the generic part into
this antlib also.

+1 for all others

> 2. Should the commercial tasks that are voted for dropping from Ant core
> above be established in their own Antlibs in the sandbox?
>
> [  ]  +1 = Yes, establish one new Antlib in the sandbox for each task
> dropped
>      -1 = No, just drop the commercial tasks altogether from Ant
>

+1

Gilles

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Re: [VOTE] Remove commercial tasks from Ant

Posted by Maarten Coene <ma...@yahoo.com>.
+1 to drop all listed commercial tasks from Ant distributions
+1 to create antlib in sandbox for each dropped task

Maarten




----- Original Message ----
From: Bruce Atherton <br...@callenish.com>
To: Ant Developers List <de...@ant.apache.org>
Sent: Sat, June 19, 2010 8:38:54 PM
Subject: [VOTE] Remove commercial tasks from Ant

Ant supplies several tasks that require commercial software in order to run. This is a problem because the Ant developers do not typically have access to the commercial products required to test, maintain, and enhance the tasks. It also means that users downloading the binary edition of Ant end up with a lot of tasks that they cannot use.

In order to rectify this situation, I'm calling a vote on how to deal with these unsupportable tasks. The vote is composed of two parts: should we drop support for each of these tasks from the Ant release, and should we establish the commercial tasks that have been dropped as Antlibs in the sandbox.

1. Should the following commercial tasks be dropped from being distributed with the Ant release?

[  ]  Continuous/Synergy tasks:  CCMCheckin, CCMCheckout, CCMCheckinTask, CCMReconfigure, CCMCreateTask
[  ]  Clearcase tasks: CCCheckin, CCCheckout, CCUnCheckout, CCUpdate, CCMklbtype, CCMklabel, CCRmtype, CCLock, CCUnlock, CCMkbl, CCMkattr, CCMkdir, CCMkelem
[  ]  Perforce Tasks: P4Sync, P4Change, P4Edit, P4Submit, P4Have, P4Label, P4Labelsync, P4Counter, P4Reopen, P4Revert, P4Add, P4Delete, P4Integrate, P4Resolve, P4Fstat
[  ]  PVCS
[  ]  ServerDeploy, but only for the jonas and weblogic nested elements, generic can stay where it is.
[  ]  Source Offsite: sosget, soslabel, soscheckin, soscheckout
[  ]  Microsoft Visual SourceSafe (already an Antlib)

2. Should the commercial tasks that are voted for dropping from Ant core above be established in their own Antlibs in the sandbox?

[  ]  +1 = Yes, establish one new Antlib in the sandbox for each task dropped
      -1 = No, just drop the commercial tasks altogether from Ant

Note that question 1 is a  vote for code modification, so any -1 vote on question 1 is considered a veto. Question 2 is just for guidance from the community about whether there is a desire to keep the commercial tasks around in Antlibs. Since any committer can create a sandbox Antlib at any time, the vote is non-binding and any -1 vote just indicates that the voter does not think that this is a good idea rather than being a veto.

Three or more +1 votes with no -1 votes are required for dropping any of the commercial tasks. The vote will end in one week.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


      

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Re: [VOTE] Remove commercial tasks from Ant

Posted by Peter Reilly <pe...@gmail.com>.
On Fri, Jun 25, 2010 at 6:14 AM, Bruce Atherton <br...@callenish.com> wrote:
> On 19/06/2010 11:38 AM, Bruce Atherton wrote:
>>
>> 1. Should the following commercial tasks be dropped from being distributed
>> with the Ant release?
>>
>> [  ]  Continuous/Synergy tasks:  CCMCheckin, CCMCheckout, CCMCheckinTask,
>> CCMReconfigure, CCMCreateTask
>> [  ]  Clearcase tasks: CCCheckin, CCCheckout, CCUnCheckout, CCUpdate,
>> CCMklbtype, CCMklabel, CCRmtype, CCLock, CCUnlock, CCMkbl, CCMkattr,
>> CCMkdir, CCMkelem
>> [  ]  Perforce Tasks: P4Sync, P4Change, P4Edit, P4Submit, P4Have, P4Label,
>> P4Labelsync, P4Counter, P4Reopen, P4Revert, P4Add, P4Delete, P4Integrate,
>> P4Resolve, P4Fstat
>> [  ]  PVCS
>> [  ]  ServerDeploy, but only for the jonas and weblogic nested elements,
>> generic can stay where it is.
>> [  ]  Source Offsite: sosget, soslabel, soscheckin, soscheckout
>> [  ]  Microsoft Visual SourceSafe (already an Antlib)
>
> +1 to all
+ 1 to all
>
>>
>> 2. Should the commercial tasks that are voted for dropping from Ant core
>> above be established in their own Antlibs in the sandbox?
>>
>> [  ]  +1 = Yes, establish one new Antlib in the sandbox for each task
>> dropped
>>      -1 = No, just drop the commercial tasks altogether from Ant
>
> +1
+1

Peter
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Re: [VOTE] Remove commercial tasks from Ant

Posted by Bruce Atherton <br...@callenish.com>.
On 19/06/2010 11:38 AM, Bruce Atherton wrote:
> 1. Should the following commercial tasks be dropped from being 
> distributed with the Ant release?
>
> [  ]  Continuous/Synergy tasks:  CCMCheckin, CCMCheckout, 
> CCMCheckinTask, CCMReconfigure, CCMCreateTask
> [  ]  Clearcase tasks: CCCheckin, CCCheckout, CCUnCheckout, CCUpdate, 
> CCMklbtype, CCMklabel, CCRmtype, CCLock, CCUnlock, CCMkbl, CCMkattr, 
> CCMkdir, CCMkelem
> [  ]  Perforce Tasks: P4Sync, P4Change, P4Edit, P4Submit, P4Have, 
> P4Label, P4Labelsync, P4Counter, P4Reopen, P4Revert, P4Add, P4Delete, 
> P4Integrate, P4Resolve, P4Fstat
> [  ]  PVCS
> [  ]  ServerDeploy, but only for the jonas and weblogic nested 
> elements, generic can stay where it is.
> [  ]  Source Offsite: sosget, soslabel, soscheckin, soscheckout
> [  ]  Microsoft Visual SourceSafe (already an Antlib)

+1 to all

>
> 2. Should the commercial tasks that are voted for dropping from Ant 
> core above be established in their own Antlibs in the sandbox?
>
> [  ]  +1 = Yes, establish one new Antlib in the sandbox for each task 
> dropped
>       -1 = No, just drop the commercial tasks altogether from Ant

+1


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Re: [VOTE] Remove commercial tasks from Ant

Posted by Jesse Glick <je...@oracle.com>.
On 06/19/2010 02:38 PM, Bruce Atherton wrote:
> 1. Should the following commercial tasks be dropped from being
> distributed with the Ant release?

+1 for all.

> 2. Should the commercial tasks that are voted for dropping from Ant core
> above be established in their own Antlibs in the sandbox?
>
> [ ] +1 = Yes, establish one new Antlib in the sandbox for each task dropped
> -1 = No, just drop the commercial tasks altogether from Ant

+0 - it might be helpful to have an official spot where the last known good versions of these tasks could be hosted. In some cases I would hope the company producing the 
commercial software would maintain their own Ant integrations.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Re: [VOTE] Remove commercial tasks from Ant

Posted by Dominique Devienne <dd...@gmail.com>.
On Sat, Jun 19, 2010 at 1:38 PM, Bruce Atherton <br...@callenish.com> wrote:
>
> 1. Should the following commercial tasks be dropped from being distributed
> with the Ant release?

+1 to all.

> 2. Should the commercial tasks that are voted for dropping from Ant core
> above be established in their own Antlibs in the sandbox?

+1.

--DD

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Re: Contacting vendors

Posted by Bruce Atherton <br...@callenish.com>.
On 06/07/2010 1:57 AM, Kevin Jackson wrote:
> How about adding that of course the customers can continue to use the
> current version of Ant as is with the tasks integrated and that it
> will only affect people that use the latest versions (ok my wording is
> crappy, but to let them know that we're not dropping support from the
> current version, just for future development)
>    

Good point. I'll add that.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Re: Contacting vendors

Posted by Kevin Jackson <fo...@gmail.com>.
Hi,

>> Sure. How about this as a first attempt. Feedback and suggestions
>> appreciated.
>

How about adding that of course the customers can continue to use the
current version of Ant as is with the tasks integrated and that it
will only affect people that use the latest versions (ok my wording is
crappy, but to let them know that we're not dropping support from the
current version, just for future development)

Kev

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Re: Contacting vendors

Posted by Stefan Bodewig <bo...@apache.org>.
On 2010-07-01, Bruce Atherton wrote:

> On 30/06/2010 4:43 AM, Jan Matèrne wrote:
>> Could you provide a mail 'template' we could use?
>> I could try to contact the Synergy-people at IBM.

> Sure. How about this as a first attempt. Feedback and suggestions
> appreciated.

"I am not a native speaker" disclaimer - looks good to me.

Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Contacting vendors (was [RESULT][VOTE] Remove commercial tasks from Ant)

Posted by Bruce Atherton <br...@callenish.com>.
On 30/06/2010 4:43 AM, Jan Matèrne wrote:
> Could you provide a mail 'template' we could use?
> I could try to contact the Synergy-people at IBM.
>    

Sure. How about this as a first attempt. Feedback and suggestions 
appreciated.

--

On behalf of the Apache Ant Project, I am writing to let you know that 
the Ant development team has recently voted to remove all commercial 
software tasks from future Ant releases, including tasks which support 
your product []. This decision was made because the developers have 
found it impossible to develop and maintain the tasks when they lack 
access to the software that the tasks are designed to interact with.

We recognize that dropping these tasks will have a negative impact on 
your customers. We therefore suggest that your organization take over 
development, maintenance, and release of the code for these tasks. If 
you do so we will provide a pointer on the Ant site indicating where 
people can find these tasks on your web site, thereby easing the 
transition for your customers.

If you are unable or unwilling to take over responsibility for these 
tasks, we will try to move them into an unsupported Ant Library. How 
long this will take is unknown, and the results are unlikely to work 
correctly since we lack the ability to test them. It will be left to 
your customers to try to figure out how to make the library work.

We plan to remove the tasks September 1st. Please let us know what your 
intentions are prior to that date so that we can plan accordingly.

Thank you.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


AW: [RESULT][VOTE] Remove commercial tasks from Ant

Posted by Jan Matèrne <ap...@materne.de>.
> The next step I'd like to take is to contact all the companies that make
> the commercial software whose tasks we are removing. With any luck some
> of them will take over responsibility for the tasks. It will take me a
> while to do this, though (I've just recently changed cities so my life
> is in a bit of upheaval) so if anyone wants to help out, particularly
> if they have connections in some of the organizations involved, please let
> me know and we can coordinate things.

Could you provide a mail 'template' we could use?
I could try to contact the Synergy-people at IBM.



> Once we have alerted the parties involved about the change, we can start
> removing the tasks and creating new Antlibs in the sandbox. Are there
> targets available anywhere to facilitate the creation of standard new
> Antlibs?

It seems that the buildfile of the Antlib-root [1] could help.
Not sure if it is uptodate ...


Jan


[1] http://svn.apache.org/repos/asf/ant/sandbox/antlibs/build.xml


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


[RESULT][VOTE] Remove commercial tasks from Ant

Posted by Bruce Atherton <br...@callenish.com>.
The results of the vote are in. Both motions passed.

The motion to drop the commercial tasks from the binary release of Ant 
had 13 +1 votes for almost all the commercial tasks, and no -1 votes. 
The one exception was the Server Deploy subtasks, which Gilles voted +0 
on, resulting in 12 +1 votes and 1 +0 vote. Stefan also expressed some 
concern about the complexity of moving them to Antlibs. We should 
probably discuss how to move these separately now that their removal has 
been approved.

The motion to move the tasks into their own Antlibs had 10 +1 votes and 
3 +0 votes with no -1 votes. This motion also passes.

Votes came from Stefan, Gilles, Jesse, Jan, Kevin, Dominique, Antoine, 
Matt, Conor, myself, Peter, Martijn, and Maarten,

The next step I'd like to take is to contact all the companies that make 
the commercial software whose tasks we are removing. With any luck some 
of them will take over responsibility for the tasks. It will take me a 
while to do this, though (I've just recently changed cities so my life 
is in a bit of upheaval) so if anyone wants to help out, particularly if 
they have connections in some of the organizations involved, please let 
me know and we can coordinate things.

Once we have alerted the parties involved about the change, we can start 
removing the tasks and creating new Antlibs in the sandbox. Are there 
targets available anywhere to facilitate the creation of standard new 
Antlibs?


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Re: [VOTE] Remove commercial tasks from Ant

Posted by Antoine Levy-Lambert <an...@gmx.de>.
On 6/19/2010 2:38 PM, Bruce Atherton wrote:
>
> 1. Should the following commercial tasks be dropped from being 
> distributed with the Ant release?
>
> +1 for all
>
> 2. Should the commercial tasks that are voted for dropping from Ant 
> core above be established in their own Antlibs in the sandbox?
>
> +1 for all

Regards,

Antoine

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Re: [VOTE] Remove commercial tasks from Ant

Posted by Kevin Jackson <fo...@gmail.com>.
Hi,

Sorry a little late to the party...

> 1. Should the following commercial tasks be dropped from being distributed
> with the Ant release?
>
> [  ]  Continuous/Synergy tasks:  CCMCheckin, CCMCheckout, CCMCheckinTask,
> CCMReconfigure, CCMCreateTask
> [  ]  Clearcase tasks: CCCheckin, CCCheckout, CCUnCheckout, CCUpdate,
> CCMklbtype, CCMklabel, CCRmtype, CCLock, CCUnlock, CCMkbl, CCMkattr,
> CCMkdir, CCMkelem
> [  ]  Perforce Tasks: P4Sync, P4Change, P4Edit, P4Submit, P4Have, P4Label,
> P4Labelsync, P4Counter, P4Reopen, P4Revert, P4Add, P4Delete, P4Integrate,
> P4Resolve, P4Fstat
> [  ]  PVCS
> [  ]  ServerDeploy, but only for the jonas and weblogic nested elements,
> generic can stay where it is.
> [  ]  Source Offsite: sosget, soslabel, soscheckin, soscheckout
> [  ]  Microsoft Visual SourceSafe (already an Antlib)

Absolutely +1

> 2. Should the commercial tasks that are voted for dropping from Ant core
> above be established in their own Antlibs in the sandbox?
>
> [  ]  +1 = Yes, establish one new Antlib in the sandbox for each task
> dropped

+1 move to antlibs for each group of tasks

>      -1 = No, just drop the commercial tasks altogether from Ant

Thanks,
Kev

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Re: [VOTE] Remove commercial tasks from Ant

Posted by Matt Benson <gu...@gmail.com>.
On Jun 19, 2010, at 1:38 PM, Bruce Atherton wrote:

> Ant supplies several tasks that require commercial software in order to run. This is a problem because the Ant developers do not typically have access to the commercial products required to test, maintain, and enhance the tasks. It also means that users downloading the binary edition of Ant end up with a lot of tasks that they cannot use.
> 
> In order to rectify this situation, I'm calling a vote on how to deal with these unsupportable tasks. The vote is composed of two parts: should we drop support for each of these tasks from the Ant release, and should we establish the commercial tasks that have been dropped as Antlibs in the sandbox.
> 
> 1. Should the following commercial tasks be dropped from being distributed with the Ant release?
> 
> [  ]  Continuous/Synergy tasks:  CCMCheckin, CCMCheckout, CCMCheckinTask, CCMReconfigure, CCMCreateTask
> [  ]  Clearcase tasks: CCCheckin, CCCheckout, CCUnCheckout, CCUpdate, CCMklbtype, CCMklabel, CCRmtype, CCLock, CCUnlock, CCMkbl, CCMkattr, CCMkdir, CCMkelem
> [  ]  Perforce Tasks: P4Sync, P4Change, P4Edit, P4Submit, P4Have, P4Label, P4Labelsync, P4Counter, P4Reopen, P4Revert, P4Add, P4Delete, P4Integrate, P4Resolve, P4Fstat
> [  ]  PVCS
> [  ]  ServerDeploy, but only for the jonas and weblogic nested elements, generic can stay where it is.
> [  ]  Source Offsite: sosget, soslabel, soscheckin, soscheckout
> [  ]  Microsoft Visual SourceSafe (already an Antlib)
> 

+1 to all

> 2. Should the commercial tasks that are voted for dropping from Ant core above be established in their own Antlibs in the sandbox?
> 
> [  ]  +1 = Yes, establish one new Antlib in the sandbox for each task dropped
>      -1 = No, just drop the commercial tasks altogether from Ant
> 

+0

-Matt

> Note that question 1 is a  vote for code modification, so any -1 vote on question 1 is considered a veto. Question 2 is just for guidance from the community about whether there is a desire to keep the commercial tasks around in Antlibs. Since any committer can create a sandbox Antlib at any time, the vote is non-binding and any -1 vote just indicates that the voter does not think that this is a good idea rather than being a veto.
> 
> Three or more +1 votes with no -1 votes are required for dropping any of the commercial tasks. The vote will end in one week.
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Re: [VOTE] Remove commercial tasks from Ant

Posted by Stefan Bodewig <bo...@apache.org>.
On 2010-06-19, Bruce Atherton wrote:

> 1. Should the following commercial tasks be dropped from being
> distributed with the Ant release?

> [  ]  Continuous/Synergy tasks:  CCMCheckin, CCMCheckout,
>       CCMCheckinTask, CCMReconfigure, CCMCreateTask
> [  ]  Clearcase tasks: CCCheckin, CCCheckout, CCUnCheckout, CCUpdate,
>       CCMklbtype, CCMklabel, CCRmtype, CCLock, CCUnlock, CCMkbl, CCMkattr,
>       CCMkdir, CCMkelem
> [  ]  Perforce Tasks: P4Sync, P4Change, P4Edit, P4Submit, P4Have,
>       P4Label, P4Labelsync, P4Counter, P4Reopen, P4Revert, P4Add, P4Delete,
>       P4Integrate, P4Resolve, P4Fstat
> [  ]  PVCS
> [  ]  Source Offsite: sosget, soslabel, soscheckin, soscheckout
> [  ]  Microsoft Visual SourceSafe (already an Antlib)

+1 to all of them

> [  ]  ServerDeploy, but only for the jonas and weblogic nested
>       elements, generic can stay where it is.

Does the current Antlib mechanism allow us to distribute the nested
elements separately?  Probably if we type/componentdef them, but it may
require some modifications to the serverdeploy task itself, I guess.

+1 to the intent and I'm willing to help making the move possible.

> 2. Should the commercial tasks that are voted for dropping from Ant
> core above be established in their own Antlibs in the sandbox?

> [  ]  +1 = Yes, establish one new Antlib in the sandbox for each task
>            dropped
>       -1 = No, just drop the commercial tasks altogether from Ant

+1

Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Re: [VOTE] Remove commercial tasks from Ant

Posted by Martijn Kruithof <jk...@apache.org>.
On 19-6-2010 20:38, Bruce Atherton wrote:
> Ant supplies several tasks that require commercial software in order 
> to run. This is a problem because the Ant developers do not typically 
> have access to the commercial products required to test, maintain, and 
> enhance the tasks. It also means that users downloading the binary 
> edition of Ant end up with a lot of tasks that they cannot use.
>
> In order to rectify this situation, I'm calling a vote on how to deal 
> with these unsupportable tasks. The vote is composed of two parts: 
> should we drop support for each of these tasks from the Ant release, 
> and should we establish the commercial tasks that have been dropped as 
> Antlibs in the sandbox.
>
> 1. Should the following commercial tasks be dropped from being 
> distributed with the Ant release?
>
> [  ]  Continuous/Synergy tasks:  CCMCheckin, CCMCheckout, 
> CCMCheckinTask, CCMReconfigure, CCMCreateTask
> [  ]  Clearcase tasks: CCCheckin, CCCheckout, CCUnCheckout, CCUpdate, 
> CCMklbtype, CCMklabel, CCRmtype, CCLock, CCUnlock, CCMkbl, CCMkattr, 
> CCMkdir, CCMkelem
> [  ]  Perforce Tasks: P4Sync, P4Change, P4Edit, P4Submit, P4Have, 
> P4Label, P4Labelsync, P4Counter, P4Reopen, P4Revert, P4Add, P4Delete, 
> P4Integrate, P4Resolve, P4Fstat
> [  ]  PVCS
> [  ]  ServerDeploy, but only for the jonas and weblogic nested 
> elements, generic can stay where it is.
> [  ]  Source Offsite: sosget, soslabel, soscheckin, soscheckout
> [  ]  Microsoft Visual SourceSafe (already an Antlib)
>

+1

> 2. Should the commercial tasks that are voted for dropping from Ant 
> core above be established in their own Antlibs in the sandbox?
>
> [  ]  +1 = Yes, establish one new Antlib in the sandbox for each task 
> dropped
>       -1 = No, just drop the commercial tasks altogether from Ant
>
> Note that question 1 is a  vote for code modification, so any -1 vote 
> on question 1 is considered a veto. Question 2 is just for guidance 
> from the community about whether there is a desire to keep the 
> commercial tasks around in Antlibs. Since any committer can create a 
> sandbox Antlib at any time, the vote is non-binding and any -1 vote 
> just indicates that the voter does not think that this is a good idea 
> rather than being a veto.
+1

>
> Three or more +1 votes with no -1 votes are required for dropping any 
> of the commercial tasks. The vote will end in one week.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


AW: [VOTE] Remove commercial tasks from Ant

Posted by Ja...@rzf.fin-nrw.de.
>1. Should the following commercial tasks be dropped from being 
>distributed with the Ant release?

+1 for all


>2. Should the commercial tasks that are voted for dropping from Ant
core 
>above be established in their own Antlibs in the sandbox?
>
>[  ]  +1 = Yes, establish one new Antlib in the sandbox for each task 
>dropped
>       -1 = No, just drop the commercial tasks altogether from Ant


+1 one antlib per task-family


Jan

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Re: [VOTE] Remove commercial tasks from Ant

Posted by Conor MacNeill <co...@apache.org>.
On Sun, Jun 20, 2010 at 04:38, Bruce Atherton <br...@callenish.com> wrote:
>
> 1. Should the following commercial tasks be dropped from being distributed
> with the Ant release?
>
> [  ]  Continuous/Synergy tasks:  CCMCheckin, CCMCheckout, CCMCheckinTask,
> CCMReconfigure, CCMCreateTask
> [  ]  Clearcase tasks: CCCheckin, CCCheckout, CCUnCheckout, CCUpdate,
> CCMklbtype, CCMklabel, CCRmtype, CCLock, CCUnlock, CCMkbl, CCMkattr,
> CCMkdir, CCMkelem
> [  ]  Perforce Tasks: P4Sync, P4Change, P4Edit, P4Submit, P4Have, P4Label,
> P4Labelsync, P4Counter, P4Reopen, P4Revert, P4Add, P4Delete, P4Integrate,
> P4Resolve, P4Fstat
> [  ]  PVCS
> [  ]  ServerDeploy, but only for the jonas and weblogic nested elements,
> generic can stay where it is.
> [  ]  Source Offsite: sosget, soslabel, soscheckin, soscheckout
> [  ]  Microsoft Visual SourceSafe (already an Antlib)
>

+1 to all.

> 2. Should the commercial tasks that are voted for dropping from Ant core
> above be established in their own Antlibs in the sandbox?
>
> [  ]  +1 = Yes, establish one new Antlib in the sandbox for each task
> dropped
>      -1 = No, just drop the commercial tasks altogether from Ant
>

+0

Conor

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org