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/05/29 22:53:41 UTC

[DISCUSS] Commercial Tasks in Ant

There are a number of tasks in Ant that require commercial software in 
order to run. This is problematic in a couple of ways:

         1) The Ant developers usually do not have access to the 
commercial software, and so cannot confirm that existing code or 
submitted patches work correctly.
         2) All users who download the Ant base package are likely to 
get a bunch of tasks that they will never have any use for since they 
don't own the software and cannot easily get a copy to work with.

What I'd like to suggest is that we move all the tasks based on 
commercial software out of the Ant release and into their own Antlibs. 
This has already been done with the Borland Starteam tasks, and The 
Microsoft Visual Sourcesafe package has been moved but not yet released 
(and so older versions of the tasks still live in the Ant release).

Attempts to move a single task or set of tasks has been tried in the 
past, but they failed to get the requisite number of votes because no 
one knew whether the Antlibs could be maintained any more than the 
current tasks. My feeling is that doing nothing (leaving unsupported 
tasks in every Ant release) is worse than making the unsupported task be 
an optional download through Antlibs, and to indicate clearly in the 
Antlib that it is unsupported by the Ant team (if the team lacks access 
to the commercial software).

I'd like to discuss whether to move all of the commercial tasks out of 
Ant core/optional libraries and putting them each into their own 
Antlibs. If people are generally favourable toward this proposition I'll 
call a vote. My current thinking is that the vote should be divided into 
two questions - moving the commercial tasks out of Ant, and opening up 
Antlibs for each of them. Discussion could change that, of course.

We should also try to identify which of the new Antlibs will be 
unsupported versus the ones that Ant developers can support because they 
have access to the commercial software the tasks rely on.

The tasks that I can see that would be affected are as follows. Please 
add or delete items from the list if you don't agree.

     - Continuous/Synergy tasks:  CCMCheckin, CCMCheckout, CCMCheckinTask,
             CCMReconfigure, CCMCreateTask
     - Clearcase tasks: CCCheckin, CCCheckout, CCUnCheckout, CCUpdate, 
CCMklbtype,
             CCMklabel, CCRmtype, CCLock, CCUnlock, CCMkbl, CCMkattr, 
CCMkdir, CCMkelem
     - EJB Tasks: Note that there may no longer be a need for these as 
the servers are very old, we could instead deprecate and eventually get 
rid of.
         * blgenclient    Borland Application Server 4.5 and 5.x
         * ddcreator    Weblogic 4.5.1
         * ejbc    Weblogic 4.5.1
         * iplanet-ejbc    iPlanet Application Server 6.0
         * ejbjar    Nested Elements:
             - borland    Borland Application Server 4.5 and 5.x
             - iPlanet    iPlanet Application Server 6.0
             - jboss    JBoss
             - jonas    JOnAS 2.4.x and 2.5
             - weblogic    Weblogic 5.1 to 7.0
             - websphere    IBM WebSphere 4.0
         * wlrun    Weblogic 4.5.1 to 7.0
         * wlstop    Weblogic 4.5.1 to 7.0
     - 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, just need the 
vote to get it out of Ant core/optional and to get a release.


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


Re: [DISCUSS] Commercial Tasks in Ant

Posted by Antoine Levy-Lambert <an...@gmx.de>.
Stefan Bodewig wrote:
> On 2010-05-29, Bruce Atherton wrote:
>
>   
>> I'd like to discuss whether to move all of the commercial tasks out of
>> Ant core/optional libraries and putting them each into their own
>> Antlibs.
>>     
>
> +1 - I'm not sure we must stop at the commercial task (is there any
> reason to include the CVS tasks with Ant today?), but it will be a
> start.
>
>   
>> The tasks that I can see that would be affected are as follows. Please
>> add or delete items from the list if you don't agree.
>>     
>
> looks complete to me.
>
>   
>>     - EJB Tasks: Note that there may no longer be a need for these as
>>       the servers are very old, we could instead deprecate and eventually
>>       get rid of.
>>     
>
> +1
>
> Stefan
>
>   
+1

Antoine

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


Re: [DISCUSS] Commercial Tasks in Ant

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

> On 01/06/2010 7:51 AM, Stefan Bodewig wrote:

>> +1 - I'm not sure we must stop at the commercial task (is there any
>> reason to include the CVS tasks with Ant today?), but it will be a
>> start.

> I can add CVS to the list if there are no objections. Any other tasks
> to nominate for transfer to an antlib?

While Peter's point applies to all the other tasks as well, he's
probably right that the impact would be too big if we removed the CVS
task.

> One other thing. I think the vote should be to move these to their own
> separate antlibs in the sandbox. That will clearly indicate that they
> are unsupported.

Agreed.

> My only concern is with the difficulty in getting them out of the
> sandbox once we have a volunteer or two to maintain them, as happened
> with VSS. I'm not sure what the answer should be for this problem.

We'll have to find one once the situation comes up.  It looks as if we
were on a way for VSS, but this is just because we now have three
committers with access to the software.

Stefan

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


Re: [DISCUSS] Commercial Tasks in Ant

Posted by Peter Reilly <pe...@gmail.com>.
On Fri, Jun 11, 2010 at 8:29 PM, Bruce Atherton <br...@callenish.com> wrote:
> On 01/06/2010 7:51 AM, Stefan Bodewig wrote:
>>
>> On 2010-05-29, Bruce Atherton wrote:
>>
>>
>>>
>>> I'd like to discuss whether to move all of the commercial tasks out of
>>> Ant core/optional libraries and putting them each into their own
>>> Antlibs.
>>>
>>
>> +1 - I'm not sure we must stop at the commercial task (is there any
>> reason to include the CVS tasks with Ant today?), but it will be a
>> start.
>>
>
> I can add CVS to the list if there are no objections. Any other tasks to
> nominate for transfer to an antlib?

ekk no, I think that a lot of build scripts
in the wild depend on the cvs tasks,
and would be quite expensive to fix



if they are to be moved to an antlib, we should
have an ivy (or similar) based auto loading of
the antlib.

Peter


>
>>>     - EJB Tasks: Note that there may no longer be a need for these as
>>>       the servers are very old, we could instead deprecate and eventually
>>>       get rid of.
>>>
>>
>> +1
>>
>
> So a separate vote for these to be deprecated in the next release and
> removed in the release after that?
>
> One other thing. I think the vote should be to move these to their own
> separate antlibs in the sandbox. That will clearly indicate that they are
> unsupported. My only concern is with the difficulty in getting them out of
> the sandbox once we have a volunteer or two to maintain them, as happened
> with VSS. I'm not sure what the answer should be for this problem.
>
>
> ---------------------------------------------------------------------
> 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: [DISCUSS] Commercial Tasks in Ant

Posted by Bruce Atherton <br...@callenish.com>.
On 01/06/2010 7:51 AM, Stefan Bodewig wrote:
> On 2010-05-29, Bruce Atherton wrote:
>
>    
>> I'd like to discuss whether to move all of the commercial tasks out of
>> Ant core/optional libraries and putting them each into their own
>> Antlibs.
>>      
> +1 - I'm not sure we must stop at the commercial task (is there any
> reason to include the CVS tasks with Ant today?), but it will be a
> start.
>    

I can add CVS to the list if there are no objections. Any other tasks to 
nominate for transfer to an antlib?

>>      - EJB Tasks: Note that there may no longer be a need for these as
>>        the servers are very old, we could instead deprecate and eventually
>>        get rid of.
>>      
> +1
>    

So a separate vote for these to be deprecated in the next release and 
removed in the release after that?

One other thing. I think the vote should be to move these to their own 
separate antlibs in the sandbox. That will clearly indicate that they 
are unsupported. My only concern is with the difficulty in getting them 
out of the sandbox once we have a volunteer or two to maintain them, as 
happened with VSS. I'm not sure what the answer should be for this problem.


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


Re: [DISCUSS] Commercial Tasks in Ant

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

> I'd like to discuss whether to move all of the commercial tasks out of
> Ant core/optional libraries and putting them each into their own
> Antlibs.

+1 - I'm not sure we must stop at the commercial task (is there any
reason to include the CVS tasks with Ant today?), but it will be a
start.

> The tasks that I can see that would be affected are as follows. Please
> add or delete items from the list if you don't agree.

looks complete to me.

>     - EJB Tasks: Note that there may no longer be a need for these as
>       the servers are very old, we could instead deprecate and eventually
>       get rid of.

+1

Stefan

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


Re: Visual SourceSafe Antlib

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

> On 08/06/2010 7:08 AM, Stefan Bodewig wrote:
>> Can the tests depend on cleanup?  Sorry, I haven't actually looked into
>> the build file but thought I might toss out the idea anyway.

> Sure they could, but then you couldn't examine the repository to make
> sure everything is being stored as expected.

If test depends on cleanup you can examine anything you want after
running the tests and things will get cleaned up before you run the next
tests.

Stefan

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


Re: Visual SourceSafe Antlib

Posted by Bruce Atherton <br...@callenish.com>.
On 08/06/2010 7:08 AM, Stefan Bodewig wrote:
> Can the tests depend on cleanup?  Sorry, I haven't actually looked into
> the build file but thought I might toss out the idea anyway.
>    

Sure they could, but then you couldn't examine the repository to make 
sure everything is being stored as expected. Fine for automated tasks, 
but I like having the ability to manually look things over to make sure 
everything is as expected. Eventually the tests could become 
sophisticated enough to do the checking themselves, but for now they are 
pretty basic: Did calling the ss.exe command succeed or return an error 
code? If an error code, then the build fails.



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


Re: Visual SourceSafe Antlib

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

> One downside to the way they are currently laid out is that you have
> to do a test build followed by a cleanup build every time (running Ant
> twice). Separating them out makes sense so that you have time between
> runs to examine the database and make sure everything is as
> expected. The trouble is that if you try to do two tests in a row
> without running cleanup in between, you get a build failure. Any ideas
> about how to fix that?

Can the tests depend on cleanup?  Sorry, I haven't actually looked into
the build file but thought I might toss out the idea anyway.

Stefan

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


Re: Visual SourceSafe Antlib (was [DISCUSS] Commercial Tasks in Ant)

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

> I've got access to Visual SourceSafe now, so between you and me and Stefan
> we could probably get it out of the sandbox.
>
> I've added to the tests in the last couple of days. One downside to the way
> they are currently laid out is that you have to do a test build followed by
> a cleanup build every time (running Ant twice). Separating them out makes
> sense so that you have time between runs to examine the database and make
> sure everything is as expected. The trouble is that if you try to do two
> tests in a row without running cleanup in between, you get a build failure.
> Any ideas about how to fix that?

We could structure it so that the cleanup is done before running the tests.

That way it would still be possible to manually 'eyeball' the
repository after a test run.

I'd have to download vss again as I don't have it right now

Kev

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


Visual SourceSafe Antlib (was [DISCUSS] Commercial Tasks in Ant)

Posted by Bruce Atherton <br...@callenish.com>.
On 02/06/2010 8:14 PM, Kevin Jackson wrote:
>
>>     - Microsoft Visual SourceSafe: already an Antlib, just need the vote to
>> get it out of Ant core/optional and to get a release.
>>
>>      
> I did the work for this, but could never get the requisite number of
> votes for this to be released.
>
>    

I've got access to Visual SourceSafe now, so between you and me and 
Stefan we could probably get it out of the sandbox.

I've added to the tests in the last couple of days. One downside to the 
way they are currently laid out is that you have to do a test build 
followed by a cleanup build every time (running Ant twice). Separating 
them out makes sense so that you have time between runs to examine the 
database and make sure everything is as expected. The trouble is that if 
you try to do two tests in a row without running cleanup in between, you 
get a build failure. Any ideas about how to fix that?


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


Re: [DISCUSS] Commercial Tasks in Ant

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

> What I'd like to suggest is that we move all the tasks based on commercial
> software out of the Ant release and into their own Antlibs. This has already
> been done with the Borland Starteam tasks, and The Microsoft Visual
> Sourcesafe package has been moved but not yet released (and so older
> versions of the tasks still live in the Ant release).

+1 from me - slim down ant core and allow the users to pick the
antlibs they need

>    - Microsoft Visual SourceSafe: already an Antlib, just need the vote to
> get it out of Ant core/optional and to get a release.
>

I did the work for this, but could never get the requisite number of
votes for this to be released.

Kev

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