Bug 81754 - JCS files not handled correctly
Summary: JCS files not handled correctly
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Pollinate (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Carl McConnell CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-12-21 15:04 EST by Carl McConnell CLA
Modified: 2004-12-21 15:11 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Carl McConnell CLA 2004-12-21 15:04:34 EST 
For a file SequenceControlImpl.jcs (for example), the corresponding 
SequenceControlImplInitializer.java file is not produced by the builder, which 
causes the resulting web app to fail with an error concerning control 
initialization. Note that if a Java suffix is used instead of JCS
(SequenceControlImpl.java, for example), then everything works.
Comment 1 Carl McConnell CLA 2004-12-21 15:11:29 EST 
The builder does copy .jcs files to .java files in the .tmp-src folder, which 
are then fed to APT by the builder, so everything seems kosher in that regard, 
on the face of it anyway. Looking more closely at the APTTask used by the 
Beehive buildWebAppCore.xml build script, I see that it iterates over the 
various special file extensions (jcs, jcx, jws, and so on), which Pollinate 
does not do. Maybe that's where the bug lies?