[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [wtp-dev] Build changes

The "build docs separately" isn't really a problem.  The point Naci was making was that the doc features are defined along with all the other features,
as described in

Once that's done, there can always be a new "packaging build component" (I think that's a "distributable" in Naci's terms),
 defined that includes only the top most one (jst-enterprise-userdocs), all others included
"automatically" and zipped up and ftp'd to wherever. Its expected that one would only run "on demand".
[Technically, this would be true of any of the features in
... that's what is for .. and we just normally don't "distribute" all those mini packages.

In other words, there's no need for special build scripts, or map files, or separate build projects, or directories, that we can tell.

And ... keep in mind  ... while "late in the development cycle" might be true, and there certainly could
be a "maintenance release" that really only included doc changes,
in general, we still need the English version of docs
finished and ready to release when the code is finished and released.

We can chat on who and when creates the "doc featues".
(Anyone can, any time, but I think underscores should be used in project names, instead of the hypens
in the spec).


Lawrence Mandel <lmandel@xxxxxxxxxx>
Sent by: wtp-dev-bounces@xxxxxxxxxxx

09/15/2005 09:33 AM

Please respond to
"General discussion of project-wide or architectural issues."

"General discussion of project-wide or architectural issues." <wtp-dev@xxxxxxxxxxx>
Re: [wtp-dev] Build changes


>docs are not included in the current build.  

Does this mean docs will not be included in M8?

>They will not be built seperately but included with features.  

I think it is a mistake to remove the capability to build docs separately. Docs are typically written late in the development cycle. A separate doc build gives us a way to update the docs after a release without updating all of WTP (or WST, JST, or JSF). In addition, the PMC discussed this on one of their calls (unfortunately I can't find the minutes) where it was agreed that a separate doc build will be beneficial to WTP.

Lawrence Mandel

Software Developer
IBM Rational Software
Phone: 905 - 413 - 3814   Fax: 905 - 413 - 4920

Naci Dai <naci.dai@xxxxxxxxxxxxx>
Sent by: wtp-dev-bounces@xxxxxxxxxxx

09/15/2005 12:58 AM

Please respond to
naci.dai and "General discussion of project-wide or architectural issues."

"General discussion of project-wide or architectural issues." <wtp-dev@xxxxxxxxxxx>
Jeffrey Liu/Toronto/IBM@IBMCA, Lawrence Mandel/Toronto/IBM@IBMCA, David M Williams <david_williams@xxxxxxxxxx>
[wtp-dev] Build changes


In order to improve our builds, there has been some changes.  The old
build releng.builder is now retired. long live the releng.wtpbuilder.  
This will not have a major impact on most committers as releasing and
maps stay the same with a few changes.  You might have noticed that
there are has been some differences.  The work is still in progress so
please bear with us and provide any feedback you have at:


Here is what is different.

  * Builds are continuous, the results are uploaded to a different
    area (http://download.eclipse.org/webtools/committers).  These
    uploads are temporary and will be kept until a build is declared.
    When a build is declared it will be moved to regular builds area
    (http://download.eclipse.org/webtools/downloads).  The home page
    is not active but the but the trial builds can be downloaded using
    the links in notice emails (wtp.releng mail list).
  * wtpbuilder separates build scripts removed api-checks and
    performances tests.  These will be done on declared builds only.
    This is work in progress.
  * wtpbuilder has the concept of a _component _and a
    _distributable_.  A _component _produces a jar from feature
    definitions (such as jst or wst).  A distributable is  a tested
    set of components (ı.e. wst, jst, jst.tests etc.) which have a
    site where these reports can be reviewed and artifacts can be
    downloaded.  Currently, only distributable is wtp.
  * docs are not included in the current build.  They will not be
    built seperately but included with features.  Any component which
    is not top level, must be included in a top-level feature.
    Currently wtp distributable has 8 top level features (wst,
    wst-sdk, wst.tests, wts.perf.tests and jst equivalent of these)
    (Lawrence can we update the features so that docs get included
    with wst and jst)

Naci Dai,
eteration a.s.
Inonu cad. Sumer sok. Zitas D1-15
Kozyatagi, Istanbul 34742
+90 (533) 580 2393 (cell)
+90 (216) 361 5434 (phone)
+90 (216) 361 2034 (fax)

wtp-dev mailing list

wtp-dev mailing list