Hi,
I like the idea. As allways, please add a feature request for it.
http://objectstyle.org/jira/
A mail to the list does not count as a feature request.
Ulrich
Am 21.12.2003 um 07:27 schrieb Christian Edward Gruber:
> Hi guys,
>
> I don't know if anyone has already suggested something like this.
> I
> was thinking about an <eomodel> task that would be a nested task in a
> woframework or woapplication task. It would look something like this:
>
> <eomodel file="${resources.dir}/${project.name}.eomodeld"> (maybe
> support multiples with filesets?)
> <connection>
> <url>jdbc:oracle:thin..oo.bar.com:1521:MY_SID</url>
> <username>${eomodel.user}</username>
> <password>${eomodel.password}</password>
> <driver></driver>
> <plugin></plugin>
> </connection>
> </eomodel>
>
> This way when the build happens, the build can hot-swap various
> fields in the connection-dictionary (or maybe other relevant parts)
> that
> need to be different for, say, developer vs. QA vs. production builds.
> I included the <connection> wrapper only for grouping, in case anyone
> could find other groups of things that would be useful to transform.
> Probably, it could just be:
>
> <eomodel file="${resources.dir}/${project.name}.eomodeld"> (maybe
> support multiples with filesets?)
> <url>jdbc:oracle:thin..oo.bar.com:1521:MY_SID</url>
> <username>${eomodel.user}</username>
> <password>${eomodel.password}</password>
> <driver></driver>
> <plugin></plugin>
> </eomodel>
>
> and would most often be:
>
> <eomodel file="${resources.dir}/${project.name}.eomodeld"> (maybe
> support multiples with filesets?)
>
> <url>jdbc:oracle:thin..{eomodel.address}:1521:${eomodel.SID}</url>
> <username>${eomodel.user}</username>
> <password>${eomodel.password}</password>
> </eomodel>
>
> ... since that seems most likely to be the important things to
> alter
> between various build target-environments.
>
> Regards,
> Christian.
>
This archive was generated by hypermail 2.0.0 : Mon Dec 22 2003 - 07:05:21 EST