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

Bug 29073

Summary:

site.xml update.jar builder builds wrong order

Product:

[Eclipse Project] PDE

Reporter:

Gunnar Wagenknecht <gunnar>

Component:

Build

Assignee:

PDE-Core-Inbox <pde-core-inbox>

Status:

RESOLVED DUPLICATE

QA Contact:

Severity:

critical

Priority:

Version:

2.1

Target Milestone:

---

Hardware:

OS:

Windows 2000

Whiteboard:

Attachments:

Description	Flags
sitebuild build.log	none

Description Gunnar Wagenknecht

2003-01-07 05:59:16 EST

The update-site project is a greate improvement but the build process of the 
update jars that starts after clicking on "Build Now" has to be improved.

I assume it builds using the order the features are defined in the xml source. 
At least this have to be documented and the user has to be warned about that.

THE solution should be to analyze the features and compute a suitable build 
order.

How I discovered this?

I have 2 features. 

org.harbour.ide
org.harbour.ide.win32

I don't know why - may be I added the win32 feature first - but the win32 is 
defined in code before the base feature. Thus it is build first. The build went 
wrong because some classes couldn't be found. This happens because the base 
feature provides these classes.

BUT it was to difficult to recognize the errors because no error message was 
presented to me. I look through the "Build Log" that is accessible through the 
provided link next to the "Build Now" button and didn't discovered the error 
first. Please see attached sitebuild build.log and you will recognize that 
important messages can easily be missed because of the lot build messages.

And even if you found the message you will read that you should look into the 
compiler log. But how can I get this? It is deleted after build because it is 
generated during build into the temp directory, which is deleted after build. I 
have no chance to get the compiler logs.

Comment 1 Gunnar Wagenknecht

2003-01-07 06:01:03 EST

Created attachment 2905 [details]
sitebuild build.log

Comment 2 Gunnar Wagenknecht

2003-01-07 06:08:40 EST

It seems NOT to be a problem of the build order. It must have another cause. 
Because after changing the order in site.xml it still builds with compile 
errors.

I can't see what these compile errors are because the site build tool deletes 
the log files but I know they are because of missing classes. I noticed this 
because the generated plugins won't run in Eclipse because of inconsistent type 
hierarchies and other errors.

If I build the features manually in the right order (right click on feature.xml 
and "Create Feature JAR" I don't get compile errors. The created plugins runs 
smothly.

Comment 3 DJ Houghton

2003-02-19 16:05:29 EST

Classpath ordering has been fixes in the latest builds.
Please re-open if you are still experiencing this problem with the new build.

*** This bug has been marked as a duplicate of 27136 ***