This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 164207 - stackoverflow while creating new maven web project in tests
Summary: stackoverflow while creating new maven web project in tests
Status: VERIFIED DUPLICATE of bug 154894
Alias: None
Product: java
Classification: Unclassified
Component: Project (show other bugs)
Version: 6.x
Hardware: Sun All
: P3 blocker (vote)
Assignee: Jan Jancura
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-30 14:09 UTC by Jindrich Sedek
Modified: 2010-02-02 02:09 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
stack (18.42 KB, text/plain)
2009-04-30 14:10 UTC, Jindrich Sedek
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jindrich Sedek 2009-04-30 14:09:51 UTC
I'm having test for web applications, I've started them running also over maven web application and I'm facing 
java.lang.StackOverflowError
The stacktrace doesn't say much, because it contains only the cycle many times, but not the base where is the problem 
comming from:
-------
at java.util.regex.Pattern$GroupTail.match(Pattern.java:4227)
at java.util.regex.Pattern$BranchConn.match(Pattern.java:4078)
at java.util.regex.Pattern$CharProperty.match(Pattern.java:3345)
at java.util.regex.Pattern$Branch.match(Pattern.java:4114)
at java.util.regex.Pattern$GroupHead.match(Pattern.java:4168)
at java.util.regex.Pattern$Loop.match(Pattern.java:4295)
---------
I'll attach possible stacktrace base that seems to be causing the problem. 
(I found it putting break point at java.util.regex.Pattern$Loop.match(Pattern.java:4295) )

To reproduce run MavenWebProjectValidation test in web.kit module

I'm not able to reproduce manually, please avaluate what could be the impact of this problem and set appropriate 
priority
Comment 1 Jindrich Sedek 2009-04-30 14:10:40 UTC
Created attachment 81314 [details]
stack
Comment 2 Jindrich Sedek 2009-04-30 14:13:11 UTC
The problem rised in test on "Apr 25, 2009 12:31:18 AM" for the first time, it could be caused by some last friday 
changes.
Comment 3 Milos Kleint 2009-04-30 14:48:05 UTC
it seems to fail at detection of javadoc/source root. That was indeed added just recently. Can you provide details about
1. dependencies of the tested project
2. content of the local repository for these dependencies
maybe the javadoc/source jar for the dependency is broken, or highlights some issue in the root detection algorithm.
Comment 4 Jindrich Sedek 2009-04-30 15:02:16 UTC
the problem appears for newly created project while finishing wizard, so dependecies are default from maven web app 
template

I've moved .m2 to another dir, to simulate new maven project, libraries were downloaded after the wizard finishing, but 
the SOE was thrown after the fresh libraries download as well. 
Comment 5 Milos Kleint 2009-05-11 12:21:57 UTC
reassigning to java, the code looking for source/javadoc roots is not maven related.

jsedek: can you verify that all jars downloaded by the maven integration (in the local repository) and correct and complete?
Comment 6 Jindrich Sedek 2009-05-11 13:24:14 UTC
please evaluate if issue #164549 is not related
Comment 7 Jindrich Sedek 2009-05-11 13:28:24 UTC
I'm not sure how to recognize the jar correctness, but it seems all files are downloaded and I don't see any error 
anywhere
Comment 8 Jan Lahoda 2009-10-26 08:29:14 UTC
Fixed as issue #154894.

*** This issue has been marked as a duplicate of 154894 ***
Comment 9 Jindrich Sedek 2010-02-02 02:09:56 UTC
v.