Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
AW: [jwt-dev] Documentation and build updates

Hi Mickael,

nicely written. I'm wondering whether we should stay on this page with the
division of "What we did" and "What we have". I don't think that the first
paragraphs (What we did) are still necessary. Otherwise it should be much
more elaborated, since we (especially you!) did much more things than only
download CVS, PDE and start Java... But I would leave the distinction
between "What we have" and "How to use it". That's really helpful!
Do you agree?

Best regards,

Florian

-----Ursprüngliche Nachricht-----
Von: jwt-dev-bounces@xxxxxxxxxxx [mailto:jwt-dev-bounces@xxxxxxxxxxx] Im
Auftrag von Mickael Istria
Gesendet: 08 January 2009 10:37
An: Java Workflow Toolbox
Betreff: [jwt-dev] Documentation and build updates

Hello,

I've made some improvements on the build process and related documentations

Build process update:
* Releng folder was refactored
* Used a new base for building (see
http://wiki.eclipse.org/JWT_Automatic_Build#JWT_build_minimal_Eclipse_base )
* build scripts now runs tests  BUT
** running tests on Eclipse server requires you to have an Xserver on your
local machine (see http://wiki.eclipse.org/JWT_Automatic_Build#Requirements
)
** Build now takes around 10 minutes
** Still the permission problems reported by Florian on bug 259578
<https://bugs.eclipse.org/bugs/show_bug.cgi?id=259578>
* The build scripts creates a clone of the build base and adds to it newly
built JWT features and plugins, then runs the test scripts
(org.eclipse.jwt/releng/jwt-tests-plugin/test.xml)
* A test report is published on the update site (see
http://download.eclipse.org/technology/jwt/integration-update-site/ )

Documentation about build:
The page
http://wiki.eclipse.org/JWT_Automatic_Build#Adding_new_plugins_to_the_JWT_re
lease
explains how to include new plugins into the build process

Documentation about Bug fixing:
I writed a little checklist of things that should be done in order to solve
a bug. Since the build now handles automated testing, this strategy
encourages Test Driven Development to ensure that we'll get more and more
non-regression tests.
http://wiki.eclipse.org/JWT_DeveloperFAQ#How_to_nicely_fix_a_bug.3F


If you have any correction or precision to give to this documentation, do
not hesitate to edit it.

Regards,
Mickael
_______________________________________________
jwt-dev mailing list
jwt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jwt-dev



Back to the top