I like this too, perhaps deploy:deploy and deploy:deploy-file could
check the dependencies for existence.
Regards,
Marcel
--- David Sag <[EMAIL PROTECTED]> wrote:
> I think that is actually an excellent solution - i am going through
> similar pain right now - our build of maven2 does what we want on a
> few
> test projects of increasing complexity, but we've written a bunch of
> patches (submitted via jira) and plugins to get where we are and it's
>
> still not exactly a no brainer for someone to move to maven 2. a big
> part
> of that is the overall veracity of the ibiblio libs themselves. some
> tool
> needs to be written that checks every upload to ibiblio and rejects
> that
> upload if the dependencies cannot be downloaded.
>
> Kind regards,
> Dave Sag
>
>
>
>
>
>
> Bengt-Erik Fröberg <[EMAIL PROTECTED]> wrote on 27-12-2005
> 17:13:48:
>
> > Wrote an issue to maven-repository-plugin-JIRA.
> > I don't think you should be allowed to publish to repository if
> dependencies
> > of the stuff you're publishing does not exist.
> >
> > Regards,
> >
> >
> >
> >
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
>
__________________________________
Yahoo! for Good - Make a difference this year.
http://brand.yahoo.com/cybergivingweek2005/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
