Well, the use case is that we perform an integration test of an Apache Oozie workflow and one step in this test is to verify that some hive databases have been deleted. Since the tests are not run locally but on a cluster, we need to execute some commands on that cluster over ssh.
An obvious follow-up question is, is there any recommended maven plugin for executing ssh commands? But on a more philosophical level I am also interested in why the Wagon code looks like it does. Best Regards Thomas On Tue, Jul 29, 2014 at 3:49 PM, Benson Margulies <[email protected]> wrote: > In my experience, trying to use the wagon-maven-plugin to do anything > except move Maven artifacts around is a really exciting experience. If > you describe your entire use case perhaps someone can offer another > approach? > > On Tue, Jul 29, 2014 at 9:47 AM, Thomas Larsson > <[email protected]> wrote: > > Hello all, > > > > I am wondering why it is that > > org.apache.maven.wagon.providers.ssh.jsch.AbstractJschWagon is not > looking > > at non-zero exit codes instead of non-null error streams to determine > > whether a command has succeeded or not? > > > > We have a case where we execute an Apache Hive query over ssh using the > > maven wagon plugin, with a command looking something like "hive -e 'show > > databases'". > > When doing this, hive outputs parts of the result over stderr (which is > > very weird I grant) but the command exits with exit code 0, i.e. no > error. > > However, since wagon (and in extension the wagon-plugin) sees stderr > > content, it considers this a failed step. > > > > I found some TODOs in the code surrounding this but no JIRA Issue. > > So I am wondering what the concrete reason is for doing it in this > slightly > > weird way. > > > > Best Regards > > Thomas > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
