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

[Pascal Rapicault <Pascal_Rapicault@xxxxxxxxxx>]

The problem is not internal vs public.
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 an we don't
want to do that.

At this point what we need is something
that generates the site.xml from an existing one or a template (something
along the line of what is provided in the UI but made available in a standalone
build).

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

12/02/2005 08:36 AM

Please respond to
"Eclipse PDE Build developers list."

To	pde-build-dev@xxxxxxxxxxx
cc
Subject	[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.

Why not just put it in an internal package?

> We are looking into making it part of PDE and would actually welcome
> any help on that.

What help would you like?

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