Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.0-Alpha3
-
Component/s: ICE-Components
-
Labels:None
-
Environment:All
Description
When running the dist target on the generator ant script, it compiles the sparkle components' Meta classes, and then packages those .class files into the generator jar. Perhaps we should just have the generator ant script only compile the generator. The component ant script could compile the Meta classes, leaving them out of the generator jar.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Solved ICE-5677 and ICE-5712 together, by mapping out the complete sequence of the sparkle generator and components builds, then reordering the sequence of target building to match dependencies, moved generated files into separate locations to facilitate resequenced build, and reorganising which ant scripts were responsible for which targets.
Ran into technical difficulties having code generation ran from component ant script, so created component ant target that passed through to generator ant target for generation.
Subversion 21415
Show
Mark Collette
added a comment - Solved ICE-5677 and ICE-5712 together, by mapping out the complete sequence of the sparkle generator and components builds, then reordering the sequence of target building to match dependencies, moved generated files into separate locations to facilitate resequenced build, and reorganising which ant scripts were responsible for which targets.
Ran into technical difficulties having code generation ran from component ant script, so created component ant target that passed through to generator ant target for generation.
Subversion 21415
Adnan, please review this issue and comment as to whether there is a technical reason that the meta classes are compiled with the generator itself, etc.