Should #2061 be able to import projects from 4.0?
I just imported a project I am using in IDEA 4.0 into build #2061 and
it's behaving weirdly. I have Log4J included as a project library, the
path is correct, the jar is there and yet IDEA doesn't recognize the
imports for the library, nor does org.apache.* appear if I try to edit
imports.
I couldn't find anything in the tracker, is this a known problem?
Regards,
Matt
p.s. What are the rules for using the tracker?
Please sign in to leave a comment.
Em Mon, 31 May 2004 14:28:34 +0100, Matt Mower escreveu:
You're probably on linux, using kernel 2.6 and experiencing the
-Didea.jars.nocopy problem. Search the forum form a description and a
solution for this problem.
--
Marcus Brito <pazu@animegaiden.com.br>
Marcus Brito wrote:
>>I just imported a project I am using in IDEA 4.0 into build #2061 and it's
>>behaving weirdly. I have Log4J included as a project library, the path is
>>correct, the jar is there and yet IDEA doesn't recognize the imports for
>>the library, nor does org.apache.* appear if I try to edit imports.
As the matter of fact kernel 2.6 problem should not be the cause since it is already fixed for several builds.
--
Maxim Shafirov
IntelliJ Labs / JetBrains Inc.
http://www.intellij.com
"Develop with pleasure!"
Marcus Brito wrote:
>>I just imported a project I am using in IDEA 4.0 into build #2061 and it's
>>behaving weirdly. I have Log4J included as a project library, the path is
>>correct, the jar is there and yet IDEA doesn't recognize the imports for
>>the library, nor does org.apache.* appear if I try to edit imports.
Sorry, I forgot to add spec to my previous message.
Windows XP-SP1
Fresh install of #2061 (not installed over a previous version, no
imported settings)
JDK 1.5beta2
Regards,
Matt
Matt, that's precisely what I've seen since build 2057 (see post "red
errors shown..." in this forum. I assumed it was the -Didea.jars.nocopy
thing until I saw your post. You're on Win32 so that changes things...
I also notice that the jars do not expand in the "libraries" folder in
the Project/Packages window. Something is weird here...
Nick.
Matt Mower wrote:
>> Em Mon, 31 May 2004 14:28:34 +0100, Matt Mower escreveu:
>>
>>
>>> I just imported a project I am using in IDEA 4.0 into build #2061 and
>>> it's
>>> behaving weirdly. I have Log4J included as a project library, the
>>> path is
>>> correct, the jar is there and yet IDEA doesn't recognize the imports for
>>> the library, nor does org.apache.* appear if I try to edit imports.
>>
>>
>>
>> You're probably on linux, using kernel 2.6 and experiencing the
>> -Didea.jars.nocopy problem. Search the forum form a description and a
>> solution for this problem.
>>
Maxim Shafirov (JetBrains) wrote:
Do you happen to know what is wrong with Linux kernel 2.6 and JDK
combination. Is this a kernel or JDK bug? Has it already been submitted to
SUN bug parade? Is it dangerous to run Java on Linux 2.6?
Peter
Peter Levart wrote:
The JDK uses a specific kernel function to do fast file copies. This
function doesn't work for all types of sources/targets. In the past, if
specific types of sources/targets didn't support this fast file copy,
the kernel would use a slower, fallback method. This fallback behaviour
was removed, and the function now returns an error for unsupported
sources/targets.
The problem is (was?) that the JDK relies on fallback-behaviour in the
kernel. AFAIK this has not yet been fixed in the JDK
> Has it already been submitted to SUN bug parade?
Yes - there are several bugs filed on this in the bugparade - search for
"FileChannel" bugs.
No - just this annoyance. I'm sure it will be fixed, but in the mean
time you can work around it, as JetBrains has.
CU,
Edwin