Most sub project have these parameters defined all over again in their own project.properties.
My standing on this is that there should be only one place (J2/project.properties) defining those. Because the subproject all inherit from the root project.xml this should be no problem.
I did remove all the definitions from the sub projects and could still run allBuild (still with HSQLDB) without any problem. I didn't check standalone testing for each subproject though so there may still be some issues.
Another point where the a HSQLDB dependency is hard coded is in the repository_database.xml for the platform attribute. That file is further more also defined on multiple locations so its not clear to me which should be considered the master file. Anyway, the platform attribute really should be derived from J2/project.properties I think.
Regards,
Ate
Ate Douma wrote:
I've created Blocking issue JS2-18 last night after a long frustrated day trying to get J2 ready to use Oracle as db.
In that issue I identified (at least) 5 major problems I like to ask attention to.
Although JIRA is fine for issue tracking I think the mailing list is more interactive to discuss these issues.
Therefore I created this mail as a wrapper for the several problems which I will describe separately as reply to this mail.
I am very dependent on Oracle for running J2 as it is required for my client. Furthermore, in our project we will start developing portlets based on J2 any time now (I know its kind of early for that but we need some result before the summer and hopefully our development will provide lots of feedback to J2 to help it get out of the door sooner).
Regards, Ate
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
