Re: How to make CVS Import ignore the ignore list

You should need just nbbuild and javacvs. The build script for the 
library is in javacvs/libmodule. Do not use javacvs/build.xml, this 
would build the old javacvs module, which is likely not compilable any 
more. We should probably remove these sources (which are under javacvs/src).

I'll send you the library offline...

It's necessary to pass -source 1.4 to the compiler to handle asserts. 
It's strange that you've encountered this. Did you checkout nbbuild 
module? There is nbbuild/templates/projectized.xml file, which is 
imported by the vcscore/build.xml.

-Martin

Andrew wrote:

> Well, I'm trying to build the 4.0 cvslib and i'm having a bit of a 
> problem.  For a library that is independant of netbeans, you sure need 
> a lot of netbeans to compile it...
>
> I have checked out:
> javacvs
> vcscore
> vcscvs
> vcsgeneric
> openide
> lib
>
> and then then I try to do an
> ant compile_independant (after commenting out the MakeNBM taskdefs at 
> the top...) and I get:
>
> Buildfile: build.xml
>
> compile_independant:
>    [javac] Compiling 16 source files to 
> E:\dev\abserff\testcvsworking\vcscore\src
>    [javac] 
> E:\dev\abserff\testcvsworking\vcscore\src\org\netbeans\modules\vcscore\cache\CacheDir.java:837: 
> warning: as of release 1.4, assert is a ke
> yword, and may not be used as an identifier
>    [javac]         assert (cacheDirNames = (String[]) 
> childDirs.keySet().toArray(new String[0])) != null;
>    [javac]         ^
>    [javac] 
> E:\dev\abserff\testcvsworking\vcscore\src\org\netbeans\modules\vcscore\cache\CacheDir.java:837: 
> not a statement
>    [javac]         assert (cacheDirNames = (String[]) 
> childDirs.keySet().toArray(new String[0])) != null;
>    
> [javac]                                                                                       
> ^
>    [javac] 
> E:\dev\abserff\testcvsworking\vcscore\src\org\netbeans\modules\vcscore\cache\CacheDir.java:838: 
> warning: as of release 1.4, assert is a ke
> yword, and may not be used as an identifier
>    [javac]         assert (fsDirNames = dirFile.list(DIR_FILTER)) != 
> null : "Probably is not directory " + dirFile;
>    [javac]         ^
>    [javac] 
> E:\dev\abserff\testcvsworking\vcscore\src\org\netbeans\modules\vcscore\cache\CacheDir.java:838: 
> not a statement
>    [javac]         assert (fsDirNames = dirFile.list(DIR_FILTER)) != 
> null : "Probably is not directory " + dirFile;
>    [javac]                                                        ^
>    [javac] 
> E:\dev\abserff\testcvsworking\vcscore\src\org\netbeans\modules\vcscore\cache\CacheDir.java:838: 
> ';' expected
>    [javac]         assert (fsDirNames = dirFile.list(DIR_FILTER)) != 
> null : "Probably is not directory " + dirFile;
>    
> [javac]                                                                ^
>    [javac] 
> E:\dev\abserff\testcvsworking\vcscore\src\org\netbeans\modules\vcscore\cache\CacheDir.java:839: 
> warning: as of release 1.4, assert is a ke
> yword, and may not be used as an identifier
>    [javac]         assert cacheDirNames.length == fsDirNames.length :
>    [javac]         ^
>    [javac] 
> E:\dev\abserff\testcvsworking\vcscore\src\org\netbeans\modules\vcscore\cache\CacheDir.java:839: 
> ';' expected
>    [javac]         assert cacheDirNames.length == fsDirNames.length :
>    [javac]                             ^
>    [javac] 4 errors
>    [javac] 3 warnings
>
> BUILD FAILED
>
> Does VCScore not build under 1.4?  I can't imagine that.
> Is there anyway someone could just build the 4.0 javacvs.jar and send 
> it to me?  Let me know if you can help.  Thanks
>
> Andrew
>
>
> Andrew wrote:
>
>> Is the 4.0 libary still in beta with the rest of netbeans?  Or are 
>> you at a stable point right now?  If I want to get the 4.0 library, 
>> do I just check out the head from /cvs/javacvs?  I couldn't find the 
>> instruction for CVS checkout on the javacvs homepage.
>>
>> Also, using netbeans 3.6, if you right click on a file->CVS->Import...
>> There is an option in the GUI for "File to ignore" Is that not 
>> implemented?  Or do that work?  If so, can you tell me how they are 
>> doing it from there?  I don't know where the code for that GUI is.
>> Thanks for your help!
>> Andrew
>>
>> Martin Entlicher wrote:
>>
>>> Andrew wrote:
>>>
>>>> What version is ImportCommand.addIgnoredFile in?  I'm using the 3.6 
>>>> build and that method doesn't exist.  So that doesn't help me...
>>>
>>>
>>>
>>>
>>>
>>> It's in 4.0. It was added as a fix of issue #47054.
>>> The original developer did not implement all options, so there is 
>>> probably no way to do it in 3.6. You would have to patch the 
>>> library. It should be O.K. to grab the ImportCommand class from 
>>> trunk, compile it and replace it in the library jar.
>>>
>>> Regards,
>>> Martin
>>>
>>>>
>>>> Andrew
>>>> Martin Entlicher wrote:
>>>>
>>>>> Hi Andrew,
>>>>>
>>>>> .so files are ignored by default as described at 
>>>>> https://www.cvshome.org/docs/manual/cvs-1.11.18/cvs_18.html#SEC178.
>>>>> There does not seem to be any direct API for "!", but from the 
>>>>> code it looks that ImportCommand.addIgnoredFile("!") should work.
>>>>>
>>>>> Regards,
>>>>> Martin
>>>>>
>>>>> Andrew wrote:
>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> I've just found a bug in my code that is using javacvs and I 
>>>>>> can't fid out how to fix it.  I am exporting code from one 
>>>>>> repository and importing it into another.  When I do this, 
>>>>>> everything (code, jar files, scripts, etc) but some .so's I have 
>>>>>> get imported.  The .so's get ignored.  I have no .cvsrc in my 
>>>>>> environment, so I don't know why it is ignoring them.  Does the 
>>>>>> CVS server ignore binary files by default?
>>>>>> In anycase, I want to get able to tell the import command to 
>>>>>> ignore the ignore list.  i.e. do a cvs import -I! module
>>>>>> How can I do this with the javacvs Import command?
>>>>>>
>>>>>> Thanks!
>>>>>> Andrew
>>>>>>
>>>>>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>