Hi
I see this as well in our corporate aggregator POM that builds everything.
This 124 module build succeeds with Maven 3.0.5, but fails with
java.lang.OutOfMemoryError: PermGen space
after 108 modules when using Maven 3.1.0-alpha-1.
Sorry but I can't share the project.
Are there any free tools
It may be Maven or one of the plugins that changed as a result of updating the
default plugins. I have a several very large builds and performance seems the
same. I will set up the performance framework for the core[1], and I have a
profiler for plugins that I will cleanup. I think it best to
Hi Jason,
Jason van Zyl wrote:
Doesn't see to be a whole lot of activity around the 3.1.0-alpha-1 so I
plan to cut the 3.1.0-beta-1 this weekend if there are no objections.
Apart from the reported bogus build with snapshots (MNG-5207) it seems M31
has a major problem with PermGen space
Are you able to provide standalone example project that demonstrates the
problem?
--
Regards,
Igor
On 2013-06-26 4:23 PM, Jörg Schaible wrote:
Hi Jason,
Jason van Zyl wrote:
Doesn't see to be a whole lot of activity around the 3.1.0-alpha-1 so I
plan to cut the 3.1.0-beta-1 this weekend if
Funny in a sort of ironic way, permgen is noticeably better in 3.1 for
my usecases :)
The simplest way to get (my) attention to this issue is to create 2
heap dumps of your maven process, one after some time and the other
just before it runs out of permgen.
(some time is supposed to be well into
Oops. It appears the standard heap dump toosl don't really dump
permgen, so that's not going to get us anywhere.
I usually do this in jprofiler, maybe someone else has a suggestion :)
Kristian
2013/6/26 Kristian Rosenvold kristian.rosenv...@gmail.com:
Funny in a sort of ironic way, permgen
I will resurrect the performance framework that Igor build long ago. I should
be running it when major changes are made. I'll report back later this week. I
need to find an old, crappy machine to run them on to gauge the difference
accurately.
On Jun 26, 2013, at 8:23 AM, Jörg Schaible
Hi Jason,
did you had a chance to take a second look, following my instructions in my
first reply?
Thanks,
Jörg
Jason van Zyl wrote:
I unpacked your example and ran your preparation script and it fails in
2.2.1 as well:
https://gist.github.com/jvanzyl/5824206
What's the overall
Developers List
Subject: Re: Maven 3.1.0-beta-1
I'm just going to cut the 3.1.0. Almost zero people have given feedback and I
don't think anyone is going to look at this until it's released and then I
think all sort of issues are going to surface and I will prepare to fix those.
I believe
: Re: Maven 3.1.0-beta-1
I'm just going to cut the 3.1.0. Almost zero people have given feedback
and I don't think anyone is going to look at this until it's released and
then I think all sort of issues are going to surface and I will prepare to
fix those. I believe there will be many issues
I'm just going to cut the 3.1.0. Almost zero people have given feedback and I
don't think anyone is going to look at this until it's released and then I
think all sort of issues are going to surface and I will prepare to fix those.
I believe there will be many issues but this process isn't
Hi Jason
I've installed 3.1.0-alpha-1 into my local Jenkins 1.512 instance running
on Windows. After that I tried a simple build and ran into an exception
that others apparently had also seen:
https://issues.jenkins-ci.org/browse/JENKINS-15935
Is that a problem in the Maven Integration plugin
The Jenkins and Hudson integration require changes with anything related to
event spies that use Sisu or Aether specific classes. Existing versions of
Hudson don't work either because of the event spy implementation requiring bits
of Sisu in the sonatype space.
This is expected. It's a major
Actually the error in JENKINS-15935 is because MavenLoggerManager was removed
in:
https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=a23f7cfd10c04da702c7efb299cce6b3499c18ab
and the Jenkins maven-plugin depends on that class, hence the NCDFE.
Regarding event spy
Yes, just pointing out the current sisu/aether issues. All to be expected given
the significant movement of projects to different organizations and the
commensurate package changes. In Aether's case, significant API changes as well.
jvz
On 2013-06-23, at 11:38 AM, Stuart McCulloch
Hello,
I have a question about the alpha-1 release. I see that Aether has
been updated to 0.9.0 M2.
Does it implies that issue MNG-2802 (Concurrent-safe access to local
Maven repository) is now implemented ?
If this is the case, then IMHO this should be mentioned, even
highlighted in the release
On Jun 21, 2013, at 11:48 PM, Vincent Latombe vincent.lato...@gmail.com wrote:
Hello,
I have a question about the alpha-1 release. I see that Aether has
been updated to 0.9.0 M2.
Does it implies that issue MNG-2802 (Concurrent-safe access to local
Maven repository) is now implemented ?
OK, thanks for the clarification.
Vincent
2013/6/22 Jason van Zyl ja...@tesla.io:
On Jun 21, 2013, at 11:48 PM, Vincent Latombe vincent.lato...@gmail.com
wrote:
Hello,
I have a question about the alpha-1 release. I see that Aether has
been updated to 0.9.0 M2.
Does it implies that
Hi Jason,
first, thanks that you actually take your time to look into it!
Jason van Zyl wrote:
I unpacked your example and ran your preparation script and it fails in
2.2.1 as well:
https://gist.github.com/jvanzyl/5824206
The submodules are independent projects, you have to run clean
Hi Jason,
Jason van Zyl wrote:
Doesn't see to be a whole lot of activity around the 3.1.0-alpha-1 so I
plan to cut the 3.1.0-beta-1 this weekend if there are no objections.
Since all versions of M30x fail in their core competence to make reliable
builds because it uses stale snapshots, it
I unpacked your example and ran your preparation script and it fails in 2.2.1
as well:
https://gist.github.com/jvanzyl/5824206
What's the overall usecase? You have a build with snapshots and you find you
need to go back to a release so you lock down to a previous release and want to
use that?
Doesn't see to be a whole lot of activity around the 3.1.0-alpha-1 so I plan to
cut the 3.1.0-beta-1 this weekend if there are no objections.
Thanks,
Jason
--
Jason van Zyl
Founder CTO, Sonatype
Founder, Apache Maven
Is there an expert about the // build who could have a look at the last
comment provided by Dimitri :
http://jira.codehaus.org/browse/MNG-4996?focusedCommentId=326816page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-326816
I know him, he'll be happy to help us more to
yes, there doesn't seem to be much people reporting any issues.
Do we have any meaning of measuring the use of this new version?
I'm missing time at the moment to work on code.
But I'd like to work on little POM schema additions, like encoding
configuration: the precise list of additions that
Jason van Zyl wrote:
Doesn't see to be a whole lot of activity around the 3.1.0-alpha-1 so I plan to
cut the 3.1.0-beta-1 this weekend if there are no objections.
+1 - have been using it all week with no issues.
One thing I would love to see ( and I should really raise a JIRA for
this ),
25 matches
Mail list logo
