Hi, Am Dienstag, den 08.01.2008, 09:51 +0100 schrieb Carsten Ziegeler: > Felix Meschberger wrote: > > Hi, > > > > I am at unease with both solutions ;-) > :) > > > > > But I think clearing the URL and not doing anything if the url is > > missing is probably the better solution. Otherwise we would have the > > strange situation - when calling the install or deploy goal from the > > command line - that we would say "call the goal AND don't skip it"... > > > > The question is, why you want to configure the Sling plugin into the > > project: If it is for the assembly and/or war goals, we would probably > > be better off to split these goals into one or two separate plugins. > > > I want to use the install feature into a local app during development. I > tried
Ah ! I always call the plugin from the command line like this: $ mvn clean package org.apache.sling:maven-sling-plugin:install and thanks to bash I just can reuse the command line ... Regards Felix > defining a "develop" profile in the parent pom, so I could do a > "mvn -P develop install" at runtime for a sling bundle. But > unfortunately profiles are not inherited, so either I define the profile > in each bundle or I can convince everyone to change the default :) > > Carsten > >
