When working just on my JSP files, I always find it much faster to just copy my JSP files to the webapps folder, as compared to building the entire project, so that's where this task comes from. you'll see that I also created a task just to deploy my JSP files. In the meantime, here is a sample Ant build.xml file that demonstrates the use of the Ant WAR task, and can be used to create a war file. Advertisements By default the Ant editor only has an association with build.xml named files.You are free to use other file names or save the build file in some other location. #MUCOMMANDER ANT BUILD FILE MANUAL#When you create a new Ant buildfile project builder, the default target is set to be run for After a Clean and Manual Build and the remaining two kinds Auto Build and During a Clean are set to not be. Targets can have dependencies on other targets. However there is no restriction on the file name or its location. A target is a collection of tasks that you want to run as one unit. I'm not going to provide any explanation of any of this right now, but if I have time in the future I'll come back here and add a few comments about how this build script works. Ant’s build file, called build.xml should reside in the base directory of the project. The ivysettings.xml file This is where you define things like: - resolvers: The repositories from which to resolve artifacta - publications: Which artifacts to publish (deploy) to. You'll probably have to know a little bit about Java, Ant, and build files for this sample build.xml file to be any use to you, but if you're looking for a sample Ant build script that can be used to create a war file, or one that simple uses a war task, this example might work for you. The build.xml file This is the Ant build script which compiles the code, produces a jar artifact and publishes (deploys) it to the Strongbox artifact repository.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |