Hi,
Nicolas, thanks for the clarification.
Matthias, could you try copying all the java files to a new folder?
For convenience, here is a bash script that would copy all files preserving the folder
structure:
for file in $(find . -name '*.java'); do mkdir -p NEWFOLDER/$(dirname $file); cp
$file NEWFOLDER/$(dirname $file); done
Cheers,
Doru
On 27 Apr 2011, at 23:49, Nicolas Anquetil wrote:
-----
Mail original -----
De: "Tudor Girba"
<tudor.girba(a)gmail.com>
À: "Moose-related development" <moose-dev(a)iam.unibe.ch>
Envoyé: Mercredi 27 Avril 2011 09:46:15
Objet: [Moose-dev] Re: VerveineJ problem
Hi,
I had a similar problem before with the new inFusion which is also
based on JDT. In that case, the problem was due to inFusion relying
on
an Eclipse project and it got confused because of the .project file
from the root folder.
Nicolas, would VerveineJ not be affected by a .project?
You mean a .project that would not reference all the source that are
in the path?
I am just asking whether VerveineJ takes .project into account, or if
it always traverses deep all the sources starting from the root
folder. If it does consider a possible .project, it could be that the
problem stems from this.
Cheers,
Doru
No it dsoes not use .project afaik.
It looks for all the java files in the directory(ies) it is given
nicolas
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.tudorgirba.com
"When people care, great things can happen."