I suspect this is related to the following. As Jenkins/jetty/maven starts up I get a message:
INFO: ignoring .... because .... already installed
where ... is a long path to my plugin.
Running mvn clean in the plugin directory most certainly does not fix this. Running it in the top level probably doesn't (I didn't look as exhaustively by the time this occurred to me ).
2) On a possibly related note, can someone confirm the behavior of logging/ printing to standard error in this test environment:
I would expect that at least one of the things in the following code generates output somewhere, however, at least in the project directory, it does not happen.
Its unclear if logs go somewhere else, or I am doing something wrong.
:
BuildWrapper ....
public Environment setUp(AbstractBuild build, Launcher launcher, BuildListener listener) throws IOException, InterruptedException {
VirtualBoxMachine machine = VirtualBoxPlugin.getVirtualBoxMachine(getHostName(), getVirtualMachineName());
listener.getLogger().println(Messages.VirtualBoxLauncher_startVM(machine));
listener.getLogger().println("hello world break break break ");
System.out.println("test test test ");
System.err.println("test dfsdfas sdfasdf as");
...
Any help would be appreciated . Also apologizes if this is a blindingly stupid error on my part, I have next to zero experience with maven or java webframeworks.
Ian