I am under corporate constraints. There is no standard build mechanism here, no continuous integration, etc. But what we do have is a very restrictive set of rules governing the deployment of programs into production.
We are currently just using eclipse to do the builds for us - it is simple, it works, it is consistent, and doesn't require a bunch of extra effort. When we use eclipse to export to a runnable JAR, we have an option for dependent libraries to go into a separate folder. Is there some way (other than messing with
Ant scripts) to get eclipse to put dependent
property files into a separate folder?
If property files are included in the JAR, then you must touch the jar to modify a property. Where I work it can take an hour to get permission to modify a production property file, but several days if you want to touch a jar file that is in production (even if you are just touching it to modify a property file). So, it is to our advantage to keep our property files separate from the JAR file. It would be more consistent if there was a standard automated approach for us to use.
It seems like this should be a fairly common requirement ... I'm hoping that maybe someone did an extension of the default export wizard that meets our needs. If not, is there someone on here with experience creating plugins and/or extending existing wizards that could throw me a bone?
