Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » IAM (Eclipse Integration for Apache Maven) » Release candidate 0.9.0 at Q4E
Release candidate 0.9.0 at Q4E [message #17493] Mon, 20 April 2009 18:51 Go to next message
Carlos Sanchez is currently offline Carlos SanchezFriend
Messages: 114
Registered: July 2009
Senior Member
I have prepared a release candidate of 0.9.0 at the old Q4E site (due to
the IP process we can't release at Eclipse yet)

Instructions to update from Q4E are at
http://code.google.com/p/q4e/wiki/UpgradingToEclipseIAM

Please test and provide feedback.

Thanks
Re: Release candidate 0.9.0 at Q4E [message #18637 is a reply to message #17493] Wed, 29 April 2009 01:01 Go to previous messageGo to next message
Carlos Sanchez is currently offline Carlos SanchezFriend
Messages: 114
Registered: July 2009
Senior Member
A new build has been published with a fix (when reopening a project,
other projects' classpath might not be updated) and the ability to
detect dependencies in the workspace when using version ranges.


On 4/20/09 11:51 AM, Carlos Sanchez wrote:
> I have prepared a release candidate of 0.9.0 at the old Q4E site (due to
> the IP process we can't release at Eclipse yet)
>
> Instructions to update from Q4E are at
> http://code.google.com/p/q4e/wiki/UpgradingToEclipseIAM
>
> Please test and provide feedback.
>
> Thanks
Re: Release candidate 0.9.0 at Q4E [message #18658 is a reply to message #18637] Wed, 29 April 2009 13:28 Go to previous messageGo to next message
Marek Romanowski is currently offline Marek RomanowskiFriend
Messages: 8
Registered: July 2009
Junior Member
I've installed q4e 0.9.0 at April 28 (before your update) and have some
comments:
1. Adding maven nature works a lot faster. I have >100 projects under
eclipse&maven and with previous version "updating classpath" worked so
slow, I couldn't take it as a development environment.
2. Unfortunatelly eclipse run out of memory while adding ~50 projects. I
have -Xmx1g arg in my eclipse.ini, so i don't think it's too small. I was
planning to dump memory and analyze it, but 3. happened.
3. After a few out of memory errors something strange occured:
- I could open file (.java for example)
- I could edit it (adding some text)
- I couldn't(!) save it, because save operation was blocked until some
other operation finish.
In Progres view I saw only sleeping "Synchronizing task list" and my save
operation. Restarts (some with -clean option) did not help - situation was
the same. I had do uninstall IAM and that helped.

I was thinking that some information could be written in plugin
configuration. Then after restart, because of this info, some process
started but did not report to Progress View. I'm not able to describe
situation more accuratelly.

Sorry for lack of details, I don't know how to give you more description.
If you have some questions, possible solution or could describe where to
find any logs from IAM work i would try to reproduce situation and post
results.

Cheers!
Marek.
Re: Release candidate 0.9.0 at Q4E [message #18681 is a reply to message #18658] Wed, 29 April 2009 17:20 Go to previous messageGo to next message
Abel Mui is currently offline Abel MuiFriend
Messages: 247
Registered: July 2009
Senior Member
Hello Marek,

Thanks for your report... see below for some comments.

Marek Romanowski wrote:

> 3. After a few out of memory errors something strange occured:
> - I could open file (.java for example)
> - I could edit it (adding some text)
> - I couldn't(!) save it, because save operation was blocked until some
> other operation finish.
> In Progres view I saw only sleeping "Synchronizing task list" and my save
> operation. Restarts (some with -clean option) did not help - situation was
> the same. I had do uninstall IAM and that helped.
[...]
> Sorry for lack of details, I don't know how to give you more description.
> If you have some questions, possible solution or could describe where to
> find any logs from IAM work i would try to reproduce situation and post
> results.

IAM writes to the eclipse log, so that's the first place where you could
look for possible errors.

If you are able to test again, please:
- open the Events view, so you can see any messages by maven. Remember to
change the filter to "debug" level so you can see all output
- I have to verify this, but it is possible that the first maven run
after importing a project is locking the project and not showing on the
progress view. With 50+ projects, it might take some time for maven to
run, specially in online mode (the default).

Regaring the out of memory exceptions, maybe you could workaround them by
importing progects in smaller groups?

--
Abel Muiño
Re: Release candidate 0.9.0 at Q4E [message #18702 is a reply to message #18681] Wed, 29 April 2009 19:17 Go to previous messageGo to next message
Marek Romanowski is currently offline Marek RomanowskiFriend
Messages: 8
Registered: July 2009
Junior Member
I've dumped JVM memory on OutOfMemoryError and started to analyze it with
Eclipse Memory Analyzer. I think there is some problem with MavenLog
class. One of instances points to a String 275MB big... Connections go
like this:

MavenEventStore -> CircularFifoBuffer -> Object -> MavenLog ->
String -> char[137022158]

So it looks like MavenEventStore stores logs in CircularFifoBuffer. CFB
has got array of logs (array size: 10000). Array holds reference to a
MavenLog which references enormous String (137022158 characters). This
String starts with: " (f) classpathElements = [" - after this goes
classpath elements from my project; two first chars are whitespaces.

I think this take place only while plugin enables maven dependency
management. Maybe when I'm enabling it for 50+ projects at one operation,
this log is concatenated between all of them?


I hope this will help you,
Marek.
Re: Release candidate 0.9.0 at Q4E [message #18725 is a reply to message #18702] Wed, 29 April 2009 20:24 Go to previous messageGo to next message
Abel Mui is currently offline Abel MuiFriend
Messages: 247
Registered: July 2009
Senior Member
Unless there is a bug (which, by the size of the string, is quite
possible), each MavenLog is an object representing a log message from
maven (along with other formatting information).

It looks like maven is generating this gigantic string for your build.

Could you try one more thing?
Run a command line build with debug output enabled and look for the
string in the output:
mvn -X process-test-resources > build.log

This will not be 100% accurate (since IAM uses a non-released version of
maven) but with some luck it might help us to determine if maven is
creating this string or is something in IAM.

Marek Romanowski wrote:

> I've dumped JVM memory on OutOfMemoryError and started to analyze it with
> Eclipse Memory Analyzer. I think there is some problem with MavenLog
> class. One of instances points to a String 275MB big... Connections go
> like this:

> MavenEventStore -> CircularFifoBuffer -> Object -> MavenLog ->
> String -> char[137022158]

> So it looks like MavenEventStore stores logs in CircularFifoBuffer. CFB
> has got array of logs (array size: 10000). Array holds reference to a
> MavenLog which references enormous String (137022158 characters). This
> String starts with: " (f) classpathElements = [" - after this goes
> classpath elements from my project; two first chars are whitespaces.

> I think this take place only while plugin enables maven dependency
> management. Maybe when I'm enabling it for 50+ projects at one operation,
> this log is concatenated between all of them?


> I hope this will help you,
> Marek.
Re: Release candidate 0.9.0 at Q4E [message #18747 is a reply to message #18725] Thu, 30 April 2009 11:28 Go to previous messageGo to next message
Marek Romanowski is currently offline Marek RomanowskiFriend
Messages: 8
Registered: July 2009
Junior Member
mvn -X process-test-resources > build.log

I'm using Maven 2.1.0 and for all projects I've enabled with IAM build.log
is 1407565 bytes big.

More huge log details: there is 1701146 classpath elements in it, but only
326 unique. Log severity is debug. As you said it could be problem with
specific version of maven used in IAM. Is it possible to change it to
default maven distribution installed on system?
Re: Release candidate 0.9.0 at Q4E [message #18770 is a reply to message #18637] Tue, 05 May 2009 19:24 Go to previous messageGo to next message
Marek Romanowski is currently offline Marek RomanowskiFriend
Messages: 8
Registered: July 2009
Junior Member
Is it possible that this version of IAM changes pom.xml files by sorting
elements (to standard maven way) and removing namespace declarations from
<project> element? I'm not sure is it a problem with IAM, but from short
time my pom's are modified in this manner without prompt.
Re: Release candidate 0.9.0 at Q4E [message #18790 is a reply to message #18770] Tue, 05 May 2009 20:25 Go to previous message
Abel Mui is currently offline Abel MuiFriend
Messages: 247
Registered: July 2009
Senior Member
Marek Romanowski wrote:

> Is it possible that this version of IAM changes pom.xml files by sorting
> elements (to standard maven way) and removing namespace declarations from
> <project> element? I'm not sure is it a problem with IAM, but from short
> time my pom's are modified in this manner without prompt.

I have never seen this, but it is possible that things like that could
happen if you use any of the actions which modify the pom programatically
(adding/removing dependencies and many controls in the visual pom editor
can alter collections of pom elements).

If you are not using another tool to edit your pom, then it probably is
IAM (although I doubt it is specific to this new version).

It would be most useful if you could find a test case of this behaviour!

Thanks!
--
Abel Muiño
Re: Release candidate 0.9.0 at Q4E [message #568753 is a reply to message #17493] Wed, 29 April 2009 01:01 Go to previous message
Carlos Sanchez is currently offline Carlos SanchezFriend
Messages: 114
Registered: July 2009
Senior Member
A new build has been published with a fix (when reopening a project,
other projects' classpath might not be updated) and the ability to
detect dependencies in the workspace when using version ranges.


On 4/20/09 11:51 AM, Carlos Sanchez wrote:
> I have prepared a release candidate of 0.9.0 at the old Q4E site (due to
> the IP process we can't release at Eclipse yet)
>
> Instructions to update from Q4E are at
> http://code.google.com/p/q4e/wiki/UpgradingToEclipseIAM
>
> Please test and provide feedback.
>
> Thanks
Re: Release candidate 0.9.0 at Q4E [message #568772 is a reply to message #18637] Wed, 29 April 2009 13:28 Go to previous message
Marek Romanowski is currently offline Marek RomanowskiFriend
Messages: 8
Registered: July 2009
Junior Member
I've installed q4e 0.9.0 at April 28 (before your update) and have some
comments:
1. Adding maven nature works a lot faster. I have >100 projects under
eclipse&maven and with previous version "updating classpath" worked so
slow, I couldn't take it as a development environment.
2. Unfortunatelly eclipse run out of memory while adding ~50 projects. I
have -Xmx1g arg in my eclipse.ini, so i don't think it's too small. I was
planning to dump memory and analyze it, but 3. happened.
3. After a few out of memory errors something strange occured:
- I could open file (.java for example)
- I could edit it (adding some text)
- I couldn't(!) save it, because save operation was blocked until some
other operation finish.
In Progres view I saw only sleeping "Synchronizing task list" and my save
operation. Restarts (some with -clean option) did not help - situation was
the same. I had do uninstall IAM and that helped.

I was thinking that some information could be written in plugin
configuration. Then after restart, because of this info, some process
started but did not report to Progress View. I'm not able to describe
situation more accuratelly.

Sorry for lack of details, I don't know how to give you more description.
If you have some questions, possible solution or could describe where to
find any logs from IAM work i would try to reproduce situation and post
results.

Cheers!
Marek.
Re: Release candidate 0.9.0 at Q4E [message #568786 is a reply to message #18658] Wed, 29 April 2009 17:20 Go to previous message
Abel Mui is currently offline Abel MuiFriend
Messages: 247
Registered: July 2009
Senior Member
Hello Marek,

Thanks for your report... see below for some comments.

Marek Romanowski wrote:

> 3. After a few out of memory errors something strange occured:
> - I could open file (.java for example)
> - I could edit it (adding some text)
> - I couldn't(!) save it, because save operation was blocked until some
> other operation finish.
> In Progres view I saw only sleeping "Synchronizing task list" and my save
> operation. Restarts (some with -clean option) did not help - situation was
> the same. I had do uninstall IAM and that helped.
[...]
> Sorry for lack of details, I don't know how to give you more description.
> If you have some questions, possible solution or could describe where to
> find any logs from IAM work i would try to reproduce situation and post
> results.

IAM writes to the eclipse log, so that's the first place where you could
look for possible errors.

If you are able to test again, please:
- open the Events view, so you can see any messages by maven. Remember to
change the filter to "debug" level so you can see all output
- I have to verify this, but it is possible that the first maven run
after importing a project is locking the project and not showing on the
progress view. With 50+ projects, it might take some time for maven to
run, specially in online mode (the default).

Regaring the out of memory exceptions, maybe you could workaround them by
importing progects in smaller groups?

--
Abel Muiño
Re: Release candidate 0.9.0 at Q4E [message #568809 is a reply to message #18681] Wed, 29 April 2009 19:17 Go to previous message
Marek Romanowski is currently offline Marek RomanowskiFriend
Messages: 8
Registered: July 2009
Junior Member
I've dumped JVM memory on OutOfMemoryError and started to analyze it with
Eclipse Memory Analyzer. I think there is some problem with MavenLog
class. One of instances points to a String 275MB big... Connections go
like this:

MavenEventStore -> CircularFifoBuffer -> Object -> MavenLog ->
String -> char[137022158]

So it looks like MavenEventStore stores logs in CircularFifoBuffer. CFB
has got array of logs (array size: 10000). Array holds reference to a
MavenLog which references enormous String (137022158 characters). This
String starts with: " (f) classpathElements = [" - after this goes
classpath elements from my project; two first chars are whitespaces.

I think this take place only while plugin enables maven dependency
management. Maybe when I'm enabling it for 50+ projects at one operation,
this log is concatenated between all of them?


I hope this will help you,
Marek.
Re: Release candidate 0.9.0 at Q4E [message #568826 is a reply to message #18702] Wed, 29 April 2009 20:24 Go to previous message
Abel Mui is currently offline Abel MuiFriend
Messages: 247
Registered: July 2009
Senior Member
Unless there is a bug (which, by the size of the string, is quite
possible), each MavenLog is an object representing a log message from
maven (along with other formatting information).

It looks like maven is generating this gigantic string for your build.

Could you try one more thing?
Run a command line build with debug output enabled and look for the
string in the output:
mvn -X process-test-resources > build.log

This will not be 100% accurate (since IAM uses a non-released version of
maven) but with some luck it might help us to determine if maven is
creating this string or is something in IAM.

Marek Romanowski wrote:

> I've dumped JVM memory on OutOfMemoryError and started to analyze it with
> Eclipse Memory Analyzer. I think there is some problem with MavenLog
> class. One of instances points to a String 275MB big... Connections go
> like this:

> MavenEventStore -> CircularFifoBuffer -> Object -> MavenLog ->
> String -> char[137022158]

> So it looks like MavenEventStore stores logs in CircularFifoBuffer. CFB
> has got array of logs (array size: 10000). Array holds reference to a
> MavenLog which references enormous String (137022158 characters). This
> String starts with: " (f) classpathElements = [" - after this goes
> classpath elements from my project; two first chars are whitespaces.

> I think this take place only while plugin enables maven dependency
> management. Maybe when I'm enabling it for 50+ projects at one operation,
> this log is concatenated between all of them?


> I hope this will help you,
> Marek.
Re: Release candidate 0.9.0 at Q4E [message #568854 is a reply to message #18725] Thu, 30 April 2009 11:28 Go to previous message
Marek Romanowski is currently offline Marek RomanowskiFriend
Messages: 8
Registered: July 2009
Junior Member
mvn -X process-test-resources > build.log

I'm using Maven 2.1.0 and for all projects I've enabled with IAM build.log
is 1407565 bytes big.

More huge log details: there is 1701146 classpath elements in it, but only
326 unique. Log severity is debug. As you said it could be problem with
specific version of maven used in IAM. Is it possible to change it to
default maven distribution installed on system?
Re: Release candidate 0.9.0 at Q4E [message #568886 is a reply to message #18637] Tue, 05 May 2009 19:24 Go to previous message
Marek Romanowski is currently offline Marek RomanowskiFriend
Messages: 8
Registered: July 2009
Junior Member
Is it possible that this version of IAM changes pom.xml files by sorting
elements (to standard maven way) and removing namespace declarations from
<project> element? I'm not sure is it a problem with IAM, but from short
time my pom's are modified in this manner without prompt.
Re: Release candidate 0.9.0 at Q4E [message #568916 is a reply to message #18770] Tue, 05 May 2009 20:25 Go to previous message
Abel Mui is currently offline Abel MuiFriend
Messages: 247
Registered: July 2009
Senior Member
Marek Romanowski wrote:

> Is it possible that this version of IAM changes pom.xml files by sorting
> elements (to standard maven way) and removing namespace declarations from
> <project> element? I'm not sure is it a problem with IAM, but from short
> time my pom's are modified in this manner without prompt.

I have never seen this, but it is possible that things like that could
happen if you use any of the actions which modify the pom programatically
(adding/removing dependencies and many controls in the visual pom editor
can alter collections of pom elements).

If you are not using another tool to edit your pom, then it probably is
IAM (although I doubt it is specific to this new version).

It would be most useful if you could find a test case of this behaviour!

Thanks!
--
Abel Muiño
Previous Topic:Release candidate 0.9.0 at Q4E
Next Topic:[ANN] Eclipse IAM 0.9.0 release
Goto Forum:
  


Current Time: Thu Apr 18 15:49:54 GMT 2024

Powered by FUDForum. Page generated in 0.02652 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top