Hello Geoffrey, thanks for the speedy and informative reply. I found the issue
similar to what you suggested which I repeat here for posterity: the POM
employs an external assembly (assembly.xml) please see snippet included below.
The <directory></directory> element tag was empty which created the maven
hickup. Putting in the (dot). fixed the issue. Thanks, David.
<resources>
<resource>
<directory>.</directory>
</resource>
</resources>
Geoffrey Wiseman wrote ..
> On Tue, Jul 15, 2008 at 6:22 PM, David Brown <[EMAIL PROTECTED]> wrote:
>
> > Hello maven crowd, I had a POM that was working perfectly and w/o changing
> > anything I unexpectedly got the exception stated in the Subject line. Google
> > found nothing useful. I did not see this in the FAQ. The particulars follow.
> > TIA and please advise, David.
>
>
> Nothing preceded that message? I believe that I've seen that before when I
> have, for instance, failed to put a version identifier in because I thought
> I had covered a dependency in the parent POM's dependency management
> section, but ... whenever that's happened, I got a message about the missing
> version, then later a message about he failed POM.
>
> - Geoffrey
> --
> Geoffrey Wiseman
Yet some, not wise, go to the other side of the globe, to barbarous and
unhealthy regions, and devote ten or twenty years, in that they may live,-that
is, keep comfortably warm,- and die in New England at last.
Henry David Thoreau - Walden - 1845
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
