We have alot buildpas's that are broken right in the build. this stems from the api changes that occured. what i want to do is condense them in a couple of files rather than the 10 we have. so when new api changes occur(possibly when we move to OTrunk), its not such a job to update them all.
i just checked in BuildPasQti, this has notes, and student assmt, and will have CQ. archana, u can add the code to create a cq question in this one. i will have BuildPasJaxbQti for the tree of jaxb'ed qti objects that i am working on. other one like BuildPasMisc can be for other steps like applet, etc....... thoughts? Tony --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SAIL-Dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/SAIL-Dev?hl=en -~----------~----~----~----~------~----~------~--~---
