Mailing-List: contact sling-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: sling-dev@incubator.apache.org
Message-ID: <47833D47.5070109@apache.org>
Date: Tue, 08 Jan 2008 10:07:19 +0100
From: Carsten Ziegeler <cziegeler@apache.org>
User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031)
MIME-Version: 1.0
To: sling-dev@incubator.apache.org
Subject: Re: Defaults for the Sling Plugin
References: <478332BF.8050506@apache.org>
	 <1199781487.3305.75.camel@bslm-046.corp.day.com>
	 <4783398E.9090701@apache.org>
 <1199782877.3305.94.camel@bslm-046.corp.day.com>
In-Reply-To: <1199782877.3305.94.camel@bslm-046.corp.day.com>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit

Felix Meschberger wrote:
> 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 ...
> 
D'oh - sometimes the solution is too simple :)
Ok, so forget about this thread and thanks!

Carsten
-- 
Carsten Ziegeler
cziegeler@apache.org