maven-makepkgs-plugin versions 0.4 and 0.5 do not work at all if remote
repository URL value (i.e. one starting with "http://" ) is specified in plugin
configuration. Plugin execution fails because in this particular scenario plugin
always attempts to invoke makepkgs with -t option, but without -d option and
this combination is (understandably) not accepted.
Looking at the latest maven-makepkgs-plugin mojo class code, it is obvious that
the attempt to preserve backward compatibility backfired. -t option is always
set as the result of the fact that plugin sets the default value for packageFile
parameter. On the other hand, -d option is not set if plugin determines that
repourl parameter points to remote repository (as it needs to in GF build).
IMO, if repourl points to remote repository, plugin should take that to mean
that it should not bother with the creation of local package image, i.e. values
of packageFile, destFile, localRepository and attach parameters should be
disregarded. Even sacrificing some of backward compatibility is more acceptable
than the current state...
I am filing this as P2 since major functionality is broken without obvious
workaround. On the other hand, it is not a stopper for GF v3 release since we
dropped AIX support so there is no urgent need to move to 0.5.