Closed sisao closed 10 years ago
The plugin is not hard coded related to Maven. The plugin just monitors the maven target folders from the eclipse workspace. If for example a .war or .ear file was created or updated in the target folder of your project the plugin starts the redeploy/hotdeploy process.
What you can do is to configure a custom 'run configuration' with your prefered maven goals and then you can choose - by selecting the option 'refresh workspace' - if the manik-plugin should be triggered.
Another consideration from me is to transform the whole Manik plugin from an Eclipse plugin directly into a Maven plugin. I think that would be even cooler. But in the moment I have not the time for that migration.
Thx, I forgot the 'refresh workspace' options... now it works.
Hi, your plugin looks very useful and interesting :-)
is it possible to start the autodeploy from other maven targets? Because I didn't want to have run "mvn test" before every redeploy..
Or where is it specified that it should redeploy after "maven install"? I searched in your code but didn't find the right spot... Maybe I could fork it...
thx, Stefan