On Fri, November 23, 2007 3:35 pm, Jörg Schaible wrote:
I know why my plugin fails, but I don't know why other maven plugins can
handle the situation. I did now a bad hack and will look for the attached
artifact at the same location as the main artifact is located and only if
I cannot find it
On Fri, November 23, 2007 10:30 am, Jörg Schaible wrote:
We use since long ago an own plugin, that accesses a secondary artifact of
a dependency. This worked like charm ... until now. We have now the new
situation, that the secondary artifact is build in the same multi project
build by one
Graham Leggett wrote:
On Fri, November 23, 2007 10:30 am, Jörg Schaible wrote:
We use since long ago an own plugin, that accesses a secondary
artifact of a dependency. This worked like charm ... until now. We
have now the new situation, that the secondary artifact is build in
the same multi
