RE: Re: Converting Perforce to P4Package

That's ok with me.  It was just a thought.  I started thinking about it due
to the gyrations that are in the getWorkingProject.sh script now.  But I did
some script refactoring that I'm delivering to Maciej in a patch sometime
this week for building off a label that should simplify some of it.  It
should also be a little easier to read if we have problems.

Jim Ray
Software Configuration Engineer
Jabber, Inc.

-----Original Message-----
From: Gael Marziou [mailto:[email protected]] 
Sent: Monday, January 13, 2003 2:22 PM
To: anthill-dev-IWHQxnLZ/[email protected]
Subject: [Anthill-dev] Re: Converting Perforce to P4Package

> Has any thought ever been given to using the P4 Java API, P4Package, for 
> the PerforceRepositoryAdapter?

What would be the benefits?

Personally, I find it simpler to use the p4 command line because I
have to know it anyway,  while I don't really want to learn how to use
a new proprietary API.
By reading anthill log file, anyone knowing p4 is able to understand
what's going on.
To me,  it seems that not all users of anthill are java developers.



_______________________________________________
Anthill-dev mailing list
Anthill-dev-IWHQxnLZ/[email protected]
http://lists.urbancode.com/mailman/listinfo/anthill-dev