Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 318150

Summary:

Internal error when building project using AJDT, suspected classpath issues

Product:

[Tools] AJDT

Reporter:

Sean Hodges <seanhodges84>

Component:

Core

Assignee:

AJDT-inbox <AJDT-inbox>

Status:

RESOLVED FIXED

QA Contact:

Severity:

normal

Priority:

CC:

andrew.eisenberg

Version:

2.0.2

Target Milestone:

2.1.0

Hardware:

OS:

Linux

Whiteboard:

Attachments:

Description	Flags
Stacktrace	none

Description Sean Hodges

2010-06-28 05:40:38 EDT

Build Identifier: 20100218-1602

When building my project, Eclipse fails with the error:

"org.eclipse.core.runtime.AssertionFailedException: assertion failed: Marker property value is too long: Building with settings: [...]" (see attachment for full exception)

The stacktrace includes suspicious references to AJDT, so I'm reporting it here. Please advise if this is invalid.

Reproducible: Couldn't Reproduce

Steps to Reproduce:
1. Open project
2. Click Project -> Clean... 
3. Watch error log, project fails to build with exception.

Comment 1 Sean Hodges

2010-06-28 05:40:59 EDT

Created attachment 172877 [details]
Stacktrace

Comment 2 Sean Hodges

2010-06-28 06:41:52 EDT

This bug appears to be similar to #256735 in the JDT product, which includes a patch: https://bugs.eclipse.org/bugs/show_bug.cgi?id=256735

Comment 3 Andrew Eisenberg

2010-06-28 11:59:39 EDT

This problem is happening because the build path for your project is exceptionally long.  You have a maven project that uses aspectj, and long build paths with maven are normal. However, yours appears to be too long for AJDT to handle.  It is over 2^16 characters.

The problem occurs because you have "Show WeaveInfo" checked in you aspectj compiler properties (either locally for the project, or it is the global setting).  A short term fix would be to disable "show WeaveInfo" and your build will probably work.

The solution on my end is to look for classpath sizes that are too large and trim them before trying to display them.

This is a small enough fix that I think I can get it in before 2.1.0 is released.

Comment 4 Sean Hodges

2010-06-28 12:30:11 EDT

Andrew, you have made my day, thank you so much!

Disabling "output weave info" (in addition to the verbose flag) fixed my problem.

I'm in no immediate rush for a permanent solution but would definitely be a nice-have for the future. I'll leave this bug open for the fix, but feel free to mark as resolved as you see fit.

Comment 5 Andrew Eisenberg

2010-06-29 19:25:42 EDT

Now available in the latest 3.6 dev build.  Soon to be in the 3.5 dev build.