[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [wtp-dev] Project Metadata changes for 1.5
- From: "Fabrizio Giustina" <fgiust@xxxxxxxxxx>
- Date: Wed, 26 Apr 2006 17:23:39 +0200
- Delivered-to: firstname.lastname@example.org
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=c74J/mPjNPBxaEw315RkUqlX6Sl97SML1dx3rStdpOTdtZuGe0UO3wXHRZGzaYcwVAlMNjIpNyn9YuJzQdNubOiyECAVbS2xBrWe23iLJR7ISJgxaBiOGmcYD+T50Fw1Gq2rlSMeN/AVjHFkpdsJYAxHoKAdezKFlZU7zkwRCj0=
On 4/26/06, Chuck Bridgham <cbridgha@xxxxxxxxxx> wrote:
> Normally when metadata file changes occur, announcements are not required,
> but because the ".component" file doesn't have a complete tooling story yet,
> end users may need to be aware of its existence for advanced scenarios.
Thanks for communicating this, Chuck.
> Normally when metadata file changes occur, announcements are not required
I will take care of fixing the Maven eclipse plugin (it generates WTP
metadata files for projects built using maven): in the past it has
always been hard to find out if wtp descriptor were requiring a
modification, glad to see that you are trying to improve this ;)