For example, on the server The steps required to deploy content on the above. It is usually build, then scp, and finally some remote setup scripts:
> mvn package
> scp target/foobar.jar server:
> ssh server install-foobar
> ssh server’./bin/foobar restart’
In this case, I tend to write a small Makefile that looks like
deploy:
mvn package
scp target/foobar.jar server:
ssh server install-foobar
ssh server'./bin/foobar restart '
How do you automate your workflow?
Is Ant the tool of choice? What are the advantages/disadvantages?
< p>Pros:
>Good documentation,
>Good IDE integration
>A large number of third-party extensions and tools
Disadvantages:
>A bit lengthy (well, it’s still Another XML format)
>Some things that should be simple are not (such as any type of loop)
I don’t have any experience with makefiles, so I can’t say how they compare. Maybe you should be simple Use something more experienced by developers.
Whenever I notice that something in my workflow is a repetitive task, I try to automate it.
For example, the steps required to deploy content on the server. It is usually build, then scp, and finally some remote setup scripts:
> mvn package
> scp target / foobar.jar server:
> ssh server install-foobar
> ssh server’./bin/foobar restart’
In this case, I tend to write A small Makefile that looks like
deploy:
mvn package
scp target/foobar.jar server:
ssh server install- foobar
ssh server'./bin/foobar restart'
How do you automate your workflow?
Is Ant the tool of choice? What are the advantages/disadvantages?
For Java development, I would say that Ant is the default choice.
Pros:
>Good documentation,< br>>Good IDE integration
>Lots of third-party extensions and tools
Disadvantages:
>A bit verbose (well, it’s another XML format)
>Some should Simple things are not (such as any type of loop)
I don’t have any experience with makefiles, so I can’t say how they compare. Maybe you should simply use something that the developer is more experienced.
p>