|
That's it, I'am afraid. The '$' (at least, in
folder names) are not supported by default.
I don't know if there's a work around for that, by
configuring something, or they cannot be used. Hopefully, Rob or any other user
will be able to help you better with it. Can't you live without those dollar
signs?
Btw, won't it be easier for you to develop if the
.class files are not in SJ? Its an annoyance to keep on checking them in &
out, as what is important is the source code (you'll get the same .class if you
compile the code).And if you want to keep release versioning, it's more usual to
just keep the jar files. This is just a suggestion, although independent of
the software you use as versioning tool.
Cheers,
Albert.
----- Original Message -----
Sent: Wednesday, June 22, 2005 10:12
AM
Subject: Re: [SourceJammer-users] Error
INVALID_CHARACTER_ERR: An invalid or illegal XML character is specified
No Sweat.
The only unusual ones are '$' , multiple '.'s
(even in dir names) and long names: examples:
org.eclipse.jdt.launching.localJavaApplication.SHARED_INFO.launch
in
C:\1Eclipse\GtgDiff\.metadata\.plugins\org.eclipse.debug.core\.launches
org.eclipse.jdt.launching.prefs
in
C:\1Eclipse\GtgDiff\.metadata\.plugins\org.eclipse.core.runtime\.settings
state.dat
in
C:\1Eclipse\GtgDiff\.metadata\.plugins\org.eclipse.core.resources\.projects\GtgDiff01\org.eclipse.jdt.core
DirectoryCompareDialog$1.class
in C:\1Eclipse\GtgDiff\GtgDiff01\classes\diffgui (note not under .metadata,
and "works" in the client)
1077868989.index in
C:\1Eclipse\GtgDiff\.metadata\.plugins\org.eclipse.jdt.core
A
thought - is the problem not in the .xml files? Or does the "." in the
.metadata dir cause a problem?
Another thought - one possible way to
trouble shoot this could be if you could position an archive
(sourcejammer-server-2.1.0.0) on the internet and iI could add my files this
evening (+10 hours) using my client
(sourcejammer-client-2.1.2.0.beta.1)?
On 6/22/05, Albert
Moliner <[EMAIL PROTECTED]> wrote:
Yes, SJ can manage binary files.
Sorry, I should have specified that those
characters can provoke problems if they are in the file/folder name. Inside
a file, binary chars may generate errors only if the file has been uploaded
as text, not as binary.
So, any file with some suspectful character in
its name?
Albert.
|
