I have a Java EE 6 project I’m developing in NetBeans. All of the ant configuration was created automatically by NetBeans and I haven’t touched it. Everything builds and deploys using NetBeans with no problem.
Our typical mode of operation with other projects is that the developers will tag a particular build when it’s ready to ship, then our operations support team will run a script to export that build from CVS, create the necessary deployment assets, then copy/deploy those assets to production.
I’m trying to fit into this model with my NetBeans project. How can I build this project (developed on a Windows desktop) using a vanilla jdk/ant/Glassfish installation on a Solaris server? I do not have NetBeans installed on this server, as it is a headless box used to host our integration environment.
I’ve started looking through the ant XML files and it seems to be a tangled mess of dependencies on files that have paths defined for files on my Windows system. Is there some straightforward way to just build this project on another box outside of NetBeans? Failing that, what would be a more typical build/deployment model that falls into a 3-tier support system, where developers are not supposed to be touching production systems?
Thanks,
Steve
IMO the main Ant/Maven/whatever build files should be hand-crafted to do what you actually need, and completely removed from all IDE/directory structure/etc. dependencies.
NetBeans/Eclipse/IntelliJ can all use a properly-configured Ant file, but they can’t necessarily (ever?) use one generated by another IDE, nor can humans/CI servers.
Another option is to create a build script specifically for production/CI/etc. deployment; we’ve done both depending on actual needs/who can touch what/etc.