[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [rap-dev] WAR Product Export
- From: Ralf Sternberg <rsternberg@xxxxxxxxxxxxxxxxx>
- Date: Thu, 17 May 2012 21:49:29 +0200
- Delivered-to: firstname.lastname@example.org
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eclipsesource.com; s=eclipsesource; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding; bh=QrKyPJo1BcP3pB3BZExpJQVVgkrwJLS8Kq2iCovDdyM=; b=LPVjyoGdqjGU1sLsWSK4s7CdzhpxVGoWDC1P4MeBFFVtBLojRBYgfPi4P6XzFaBGZu InR1difyuUFdq+W6CaXAPQPsv2ctOwJe2KCC8C+/+9Z86xqBXj+4/gMSPP9mCujJHoQs XqPBMLtmBe6X3IdZssCc2RHMO5QVnLCSv7Wwk=
I'm not convinced that including the war products is worth marking the
whole package as "incubation".
1) The package is used by RCP developers as well and downloaded quite
often, the incubation warning might scare more users away than would
actually benefit from the war products. Last year, there was the same
discussion about including EGit, it had been rejected because of its
2) The war products feature is very easy to install from the Juno
repository that is already configured in the IDE.
3) Including the war products would not make this feature easier to
find. Without reading the documentation, you wouldn't know that
it's there, neither how to use it.
However, it's a trade-off. If you have a strong feeling towards
including it, you should open a bug against EPP.
Apart from this, we should check with the Libra guys about their
plans. If they can provide a release version next year, it will surely
be included. With RC1 already built, it's too late for Juno anyway, I
On Tue, May 15, 2012 at 10:36 PM, Frank Gerhardt <fg@xxxxxxxxxxxxxxxxx> wrote:
> On Tue 15 May 2012 06:48:38 PM CEST, Frank Appel wrote:
>> RÃdiger told me so yesterday too, Âwhich brings me back to my original
>> Opinion.. :-)
> I'd also rather include it. A colleague used it for a few months
> already and I learned about it only last week. Why not make the UX
> rap-dev mailing list