Community
Participate
Working Groups
Build Identifier: M20110210-1200 I'm aware that's not the proper wizard to import an EJB project, but I consider this case is worth to investigate. Reproducible: Always Steps to Reproduce: 1. File -> Import -> General -> Archive File 2. Browse for the file "ConverterEJB3.jar" (Attached here) 3. Click Open
Created attachment 199446 [details] jar that causes the error
Created attachment 199447 [details] Stack trace of the error
A Stackoverflow is not nice.
Created attachment 199470 [details] Fix
Could also add a test case to ImportArchiveOperationTest.
Eric, OK for 3.7.1?
Looks safe enough... Committed in >20110809. Applied the patch. Dani, could you do the VERIFY ?
(In reply to comment #7) > Looks safe enough... > > Committed in >20110809. Applied the patch. Do we need a separate bug for tracking this in 3.8 and 4.2?
> Do we need a separate bug for tracking this in 3.8 and 4.2? And 4.1.1. Yes, I think Platform UI does it like this. In JDT we only use a single bug and set the lowest target as it is our common practice to also put the fix in all newer streams. >Dani, could you do the VERIFY ? Will do.
Dani, I've only made the changes in the R7_maintenance stream...are you going to do 3.8 ? Apparently we also have to explicitly get the change into the R4_development stream as well...I think I need a lesson in 'cherry picking' (that's GIT talk for moving a commit from one branch to another).
(In reply to comment #10) > Dani, I've only made the changes in the R7_maintenance stream...are you going > to do 3.8 ? It would be great if you could do it, as I'm not yet set-up with Git. We should do it now so that all streams are in sync.
Verified for 3.7.1. in M20110810-0800. I'm reopening this bug until we either have separate bugs for 3.8, 4.1.1 and 4.2 or we have comments in this bug confirming the commit into those branches.
(In reply to comment #12) > I'm reopening this bug until we either have separate bugs for 3.8, 4.1.1 and > 4.2 or we have comments in this bug confirming the commit into those branches. I've opened bug 354487 to track the one for 3.8 and bug 354489 for 4.x. We haven't split 4.1.1 and 4.2...yet.
(In reply to comment #12) > Verified for 3.7.1. in M20110810-0800. Resetting to VERIFIED. Thanks for verifying the fix, Dani.