s was reported to SUN it is not yet fixed in JDK :-( Please vote
> for it : http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6843751
>
> Nobody found a workaround ?
>
> Arnaud
>
>
> On Mon, May 25, 2009 at 11:38 AM, j_ri
> wrote:
>
>>
>> Hi,
>>
Hi,
I tried to update our Maven installation to the newest version (2.2.0), but
got problems while trying to generate the site report with "mvn site" (see
stacktrace below).
I didn't find this issue in the issue list, but just tried your mentioned
2.2.1-RC1 version.and it works again;-)
Whe
finally we found the cause of the issue.
javac of 1.6 doesn't ignore the class-path entries in the manifest file of
the JARs in the classpath as 1.5 did.
As all of our jars have configured
.
false
..
There are a lot of dependencies in the "search path for class files" of the
co
> B can use types form A in its public interface. Do we really want to
> force all C's to know which of B's dependencies appear in its public
> interface? Or do all B's document which dependencies they "re-export",
> i.e. which should be considered transitive, and which not?
>
> Actually, that las
Hi,
meanwhile I posted in the Sun Developer Network, since my tests lead to the
conclusion that the problem occures because of a bug in the javac compiler
of Java 6.
see
http://forums.sun.com/thread.jspa?threadID=5386732&tstart=0
http://forums.sun.com/thread.jspa?threadID=5386732&tstart=0
an
this better.
j_ri wrote:
>
>
> I did some mor tests.
>
> First of all I tried with deactivated antivirus software. As expected this
> didn't solve the problem
>
> What I wrote last time. That Maven builds a different classpath for JDK
> 1.5 and
I did some mor tests.
First of all I tried with deactivated antivirus software. As expected this
didn't solve the problem
What I wrote last time. That Maven builds a different classpath for JDK 1.5
and 1.6 is only true for Maven 2.07. Maven 2.1.0 built the same classpath
with both versions
No, our antivirus is configured to trust nothing;-) we didn't configure it to
trust the old java and so the new java isn't configured as trustet either.
But I'll try after I found an admin who does ist for me (I'm working in a
bank.)
Today we noticed while checking the log output of running m
I tried with JDK 6 Update 10 and JDK 6 Update 13(with JDK 5 Update 11
everything was fine)
OS is Windows XP Pro SP2
I tried with Maven 2.0.7 and 2.1.0
--
View this message in context:
http://www.nabble.com/Slow-maven-compile-after-upgrading-JDK-from-1.5-to-1.6-tp23501164p23520344.html
Sent
Hi,
I have problems with the compilation-time of some of our projects using java
6 (update 10 and 13) and maven (I tried with 2.0.7 and 2.1.0).
Compiling 806 source-files takes about 7 seconds using jdk 1.5. When
switching to jdk 1.6 ist takes 59 seconds.
To compare the results I copied the jar
10 matches
Mail list logo
