Bugzilla – Full Text Bug Listing
| Summary: | Building SWT package fails on target replace64 with java.lang.StringIndexOutOfBoundsException: start > length() | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Missing name Mising name <turbors> |
| Component: | SWT | Assignee: | Felipe Heidrich <eclipse.felipe> |
| Status: | CLOSED WONTFIX | QA Contact: | Scott Kovatch <skovatch> |
| Severity: | normal | ||
| Priority: | P3 | CC: | eclipse.felipe, skovatch, turbors |
| Version: | 3.6 | ||
| Target Milestone: | --- | ||
| Hardware: | Macintosh | ||
| OS: | Mac OS X | ||
| See Also: | https://bugs.eclipse.org/bugs/show_bug.cgi?id=312597 | ||
| Whiteboard: | stalebug | ||
|
Description
Missing name Mising name
This is how I do it: check out org.eclipse.swt and org.eclipse.swt.cocoa.macosx.x86_64 select org.eclipse.swt.cocoa.macosx.x86_64 run menu bar > File > Export choose Deployable plugin and fragments Does that work for you ? Hello Felipe, Maybe you misunderstood me. I didn't want to export the packages / plug-ins but I wanted to build them after checking them out within Eclipse. During build I got the errors I described above. If I'm exporting the selected package you mentioned what else should I do to let them build? Cheers Ralf Eclipse runs the correct build script before exporting the packages, so it will include any code changes you did to the jar file. Felipe, Doing the Export you described succeeded. I got a plugin.jar, as destination I used a directory. But does this solve the problem I described? Cheers, Ralf (In reply to comment #4) > But does this solve the problem I described? I'm not sure the if regular build process is expected to work for SWT. We always had a special build process to handle different platforms and native code. Over to Felipe. Please triage or close. Looking at the initial description I would expect the steps you followed to work.
The only part that is not clear to me is:
>and the coupled ant version 1.7.1.
What do you mean by that ? Are you using some other Ant rather than the one that comes with Eclipse ?
Does it work if you use the regular Eclipse Ant (starting from a fresh workspace) ?
No, with coupled ant version 1.7.1 I mean that ant version that was shipped with the Helios Eclipse Release. Sorry if I did not express this clearly enough. It's that in my eclipse/plugins directory: org.apache.ant_1.7.1.v20100518-1145 So I only used this ant version where I got the failures I described above. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. If the bug is still relevant, please remove the "stalebug" whiteboard tag. |