Hi Brent,
You can place a *copy* of the castorbuilder.properties in your working
directory (the directory in which you will be executing your compile
command) and Castor will use that copy instead of the one in the jar. So
you don't need to unpack/repack the jar file.
This is also true for the castor.properties file. Castor checks the
working directory before it checks the classpath.
--Keith
Brent Hale wrote:
>
> Hi,
>
> I'm new to Castor but have found that it will work nicely. Thanks,
>
> I'm using Castor to generate my classes from with Maven (which I would
> suggest to Castor since the current build - although easy - is rather
> unstandard..needing to use the batch file rather than Ant directly for
> instance). I need to be able to specify the superclass for my generated
> file. I've done this in the castorbuilder.properties file and then
> repackaged the jar. The build process packages the
> castorbuilder.properties file into it which I find less than useful.
> Ideally I want to download Castor standard jar file and be able to
> modify behavior external to it. Since the properties file is embedded
> into the standard jar file I don't know of a way to override it without
> re-jarring. If there is a way please tell me.
>
> I'm wondering if all of the options available via the
> castorbuilder.properties file could easily be made available via command
> line arguments. This would make it so an external process could use the
> standard jar file and modify its behaviour at will without having to rejar.
>
> Thanks
>
> --
> Brent Hale
> Fishbowl Inventory
> www.fishbowlinventory.com
>
> -----------------------------------------------------------
> If you wish to unsubscribe from this mailing, send mail to
> [EMAIL PROTECTED] with a subject of:
> unsubscribe castor-dev
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
