I agree, we probably don't want to single jar plug-ins that have third party content in them. However, for the plug-ins that do not have third party content and can be single jarred, we should do it simply because of performance reasons. Although the theme of WTP 1.0 is API, performance is also very high on the priority list. I'll start opening bugs against plug-ins that are not single jarred. Sachin, thanks for the suggestion.
Thanks,
Jeffrey Liu
IBM Rational Software - Performance Analyst
IBM Toronto Lab.
8200 Warden Ave. Markham, Ontario, L6G 1C7
Internal mail: D3/R8V/8200/MKM (D3-268)
T/L: 969 3531
Tel: (905) 413 3531
Fax: (905) 413 4920
[EMAIL PROTECTED]
| Sachin Patel <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED] 08/26/2005 11:10 AM
|
|
Yep :) I was asking this question in hopes of making things easier when
trying to build with Maven. I don't need all plugins as jars, only the
ones I depend on. (As to which, I don't have a generated list yet...
but I will soon.).
So as far as building with Maven, have you or anyone heard success
stories in doing this?
Thanks.
I'm not sure which or how many depenencies are no
Gorkem Ercan wrote:
> Hi Sachin,
> There are some restiriction to jarring plugins for instance eclipse
> platfor did not jar ANT and JUnit plugins. I am not sure about WTP
> plugins but dependencies such as axis and xerces may also cause WTP do
> the same.
> I assume that you are interested in building eclipse plugins using
> Maven. I am not very familiar with the Maven, do you need all the
> plugins as jar or just the ones you have dependency. If it is
> dependency only, I think I can help you with a couple of them :)
>
_______________________________________________
wtp-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/wtp-dev
_______________________________________________ wtp-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/wtp-dev
