Hi,
Am Dienstag, den 08.01.2008, 10:40 +0100 schrieb Bertrand Delacretaz:
> On Jan 8, 2008 10:28 AM, Felix Meschberger <[EMAIL PROTECTED]> wrote:
>
> > ... * If the sling plugin IS configured in the project, the installation
> > happens in the "install" phase - and of course fails if there is
> > no local install....
>
> Here's my failure scenario:
>
> -Beginner runs some Sling example app, on the default port as Beginners do.
ACK
>
> -Beginner plays around with other modules, tries to build them ("mvn
> install" - that's the default for Maven Beginners) while studying the
> example app.
ACK
>
> -Modules which have the Sling plugin configured get their bundles
> installed. That's almost invisible - there are way too many messages
> in the build cycle for Beginner anyway.
ACK. BUT: There should be none in Sling, AFAIK.
>
> -Confused Beginner is left with a "patched" Mystery Example App which
> behaves in weird ways due to the added bundles. And *we* have to
> explain Beginner what's going on...
>
> Don't we all hate <insert large software company name here> for
> installing "upgrades" automatically behind people's backs?
Agreed, but I am not sure, whether this is the same case here ...
>
> I really think we should turn off these automatic installs, by default.
Still, I am against changing the defaults.
What I could agree to, and this would make the uses very obvious, is to
separate the install and deploy goals into separate plugins. If then
someone configures the - say - maven-slinginstall-plugin, the users must
live with the result.
Regards
Felix
