Re: JavaCVS client library

"Jonah, Jim" wrote:
> 
> Hi,
> 
> I'm in the process of enabling one of our products (built on netbeans) to
> utilize the javacvs library.
> 
> A message from a month ago or so implied that the core of the javacvs
> library would be merged with (moved into?) the vcsgeneric/profile code base.
> Has the timing of this migration been decided? Shall I assume the "projects
> builds" is part of NB4.0 not NB3.5?

Well, the javacvs library didn't move, it will stay where it is
(javacvs/libsrc). What has changed is that javacvs module as such will not be a
part of the projects build (projects builds are most probably future NB 4.0, NB
3.5 is already released and no changes are planned there). Only the cvs library
will be a part of the projects build. For this reason a separate manifest and
build script was created for the library (located at javacvs/libmodule).

Thus in NetBeans projects builds anyone can setup a dependency on the cvs
library module. The vcsgeneric/profiles/cvsprofile will do that and reuse most
of the javacvs filesystem functionality. For other users of the cvs library
that use it outside of NetBeans nothing will change. The library will be still
maintained at javacvs/libsrc.

> 
> Also, I've seen it stated somewhere that non-NetBeans tools have utilized
> the library part of javacvs. Now that I've been working with the javacvs
> code I'd like to understand how the core library can be utilized for
> standalone tools. Where can I look to find sample code that utilizes the
> library in a non-netbeans fashion?

http://javacvs.netbeans.org/library/GettingStarted.html and
http://javacvs.netbeans.org/library/DesignOverview.html

> 
> Finally, would I be correct in assuming that
> (javacvs/libsrc/)org.netbeans.lib.cvsclient.* is the library that's referred
> to as being not dependent upon running inside netbeans?

Exactly.

Regards,
Martin

> 
> Thanks!
> 
> Jim
> 
> -----Original Message-----
> From: Martin Entlicher [mailto:[email protected]]
> Sent: Thursday, June 19, 2003 12:21 PM
> To: 'javacvs-dev'
> Subject: [javacvs-dev] JavaCVS client library
> 
> Hi all,
> 
> Issue #33692 is resolved - the cvs client library is built as an autoload
> module and it is a part of the projects build. Any module can now have a
> dependency on the library.
> 
> All issues that are submitted for the library have now "library"
> subcomponent.
> These issues will most likely be resolved in NB 4.0, the library will be
> actively used by the cvs profile under vcsgeneric module.
> 
> The rest of the module (javacvs/src) will likely not be maintained much and
> it
> will not work in the projects builds due to incompatible changes there
> (mainly
> UI and architectural changes).
> 
> The changelog sub-module will hopefully be rewritten to plug into the cvs
> profile (issue #34499).
> 
> Regards,
> Martin
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 
> The contents of this e-mail are intended for the named addressee only. It
> contains information that may be confidential. Unless you are the named
> addressee or an authorized designee, you may not copy or use it, or disclose
> it to anyone else. If you received it in error please notify us immediately
> and then destroy it.
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]