Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (nike.apache.org: domain of daition@gmail.com designates
 209.85.216.54 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=C7sjbgdL5LS/MmyvikzeislqVYMh4sqJ188QQwF/ii1SYDjt4laxKaP8KMkU4vvIdX
         lRnIpYj6h8JnWClXu4kuIIDzN5m1JlpMWk3F8SWj8kya/o4vB650acEWphUK3HVVH1L8
         T5NHTtf6Cmnt97nQ1TWjvY9syJ8IXXHw40aBw=
MIME-Version: 1.0
Date: Fri, 9 Jul 2010 16:37:50 +0800
Message-ID: <AANLkTilSBLE8rHqC1xAzmcR280v39gsDbEwQPEVb_2Mp@mail.gmail.com>
Subject: [Discussion] Time to release an updated maven-eclipsepde-plugin?
From: Delos <daition@gmail.com>
To: dev@geronimo.apache.org
Content-Type: multipart/alternative; boundary=00c09f9b05ee775024048af05121

--00c09f9b05ee775024048af05121
Content-Type: text/plain; charset=ISO-8859-1

As part of GEP, maven-eclipsepde-plugin helps to convert eclipse plugins to
maven dependencies and add them into artifact dependency list. So without
it, GEP can't be compiled successfully. The plugin is in version 1.0. But
now, some new requirements come out that the plugin didn't take into account
before. I'm afraid we have to update the plugin to accommodate new
requirements.

1) Eclipse on Mac
There are two edition of eclipse on Mac, carbon and cocoa. From Eclipse 3.6,
 only cocoa is supported. But maven-eclipsepde-plugin can only recognize
carbon eclipse on Mac, so we have to fix it to make GEP build successfully
on Mac. You may see details in

2)Optional bundles
There are some optional required bundles in MANIFEST.MF for some extended
functions, such as TPTP and Free Aires Tools. They're not mandatory for GEP
and actually GEP don't need these bundles in build process. They're marked
as "optional" because user may get these extra plugins by themselves for
some advanced functions. So these optional bundles shouldn't block the build
process of GEP. Unfortunately, current maven-eclipsepde-plugin does block
GEP build process because of these optional bundles.

Because of these new requirements, I suggest we release an updated
maven-eclipsepde-plugin with version 1.1. Any objection?

-- 
Best Regards,

Delos

--00c09f9b05ee775024048af05121
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<meta http-equiv=3D"content-type" content=3D"text/html; charset=3Dutf-8">As=
 part of GEP, maven-eclipsepde-plugin helps to convert eclipse plugins to m=
aven dependencies and add them into artifact dependency list. So without it=
, GEP can&#39;t be compiled successfully. The plugin is in version 1.0.=A0B=
ut now, some new requirements come out that the plugin didn&#39;t take into=
 account before. I&#39;m afraid we have to update the plugin to=A0accommoda=
te=A0new requirements.<div>
<br></div><div>1) Eclipse on Mac</div><div>There are two edition of eclipse=
 on Mac, carbon and cocoa. From Eclipse 3.6, =A0only cocoa is supported. Bu=
t maven-eclipsepde-plugin can only recognize carbon eclipse on Mac, so we h=
ave to fix it to make GEP build successfully on Mac. You may see details in=
=A0</div>
<div><br></div><div>2)Optional bundles</div><div>There are some optional re=
quired bundles in MANIFEST.MF for some extended functions, such as TPTP and=
 Free Aires Tools. They&#39;re not=A0mandatory=A0for GEP and actually GEP d=
on&#39;t need these bundles in build process. They&#39;re marked as &quot;o=
ptional&quot; because user may get these extra plugins by themselves for so=
me advanced functions. So these optional bundles shouldn&#39;t block the bu=
ild process of GEP. Unfortunately, current maven-eclipsepde-plugin does blo=
ck GEP build process because of these optional bundles.</div>
<div><br></div><div>Because of these new requirements, I suggest we release=
 an updated maven-eclipsepde-plugin with version 1.1.=A0Any objection?=A0</=
div><br>-- <br>Best Regards,<br><br>Delos<br>

--00c09f9b05ee775024048af05121--