Re: [pde-build-dev] update site builder, was: How to properly use config

[Pascal Rapicault <Pascal_Rapicault@xxxxxxxxxx>]

I think you have forgotten to say that
you will contribute and maintain the code.

Thomas L Roche <tlroche@xxxxxxxxxx>
Sent by: pde-build-dev-bounces@xxxxxxxxxxx

12/02/2005 09:36 AM

Please respond to
"Eclipse PDE Build developers list."

To	"Eclipse PDE Build developers list." <pde-build-dev@xxxxxxxxxxx>
cc
Subject	Re: [pde-build-dev] update site builder,        was: How to properly use configs= property

Pascal Rapicault 12/01/2005 11:19:13 PM:
>>>>> In the SDK team we build our update site by first
doing a normal
>>>>> build and then running a little tool that Sonia wrote
but it is
>>>>> not available to the public because we don't want
to have the
>>>>> burden to maintain it.

Tom Roche 12/02/2005 08:36 AM
>>>> Why not just put it in an internal package?

Pascal Rapicault 12/02/2005 09:05:15 AM (rearranged)
>>> The problem is: as soon as it is in, then people will start
using
>>> it, enter bug, complain, etc, etc... and we will then have
to
>>> maintain it

>>> The problem is not internal vs public.

Umm, no:

http://dev.eclipse.org/naming.html
>> ISVs will be told that all packages marked internal are out of
>> bounds. (A simple text search for ".internal." detects
suspicious
>> reference in source files; likewise, "/internal/" is
suspicious in
>> .class files).

Benefit: tool is made available to folks who could use it.

Cost: you hafta "just say no" to bug reports.

Recommendation: create a text file with contents like

> We only support API. Packages marked "internal" are not
API.

Cut and paste, set Status=CLOSED, set Resolution=WONTFIX, hit the
Commit button. How hard it that? One minute of work, max.

_______________________________________________
pde-build-dev mailing list
pde-build-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pde-build-dev