[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
AW: [jwt-dev] Project Tree Organisation
|
Hi Mickael,
I agree that the current CVS structure is already getting confusing again
:-/ The tree structure that you suggested sounds good to me: /releng as a
main folder with everything that is related to automatic build/tests and
besides that the three main components WE, WAM and Transformations.
I also agree with Chris that under WE we should have a clear structure what
is necessary at least, what are the additional plugins, what are
aspect-related things, samples, etc.
Since the aspect samples are already in jwt-we-plugins, I guess we can
remove the jwt-we-sample-* under /we? The only reason why I didn't do that
already was that probably the aspect code on the branch is removed in
parallel to that. But since the aspect feature is now nearly finished I
guess this should not be a problem, am I right?
Concerning the aspects: now jwt-we is dependent on jwt-we-conf-model and
jwt-we-conf-model.edit as I have read? So probably those should stay in the
/we directory as well in order for newby's to find all plugins? Maybe we
should also have a reference somewhere how and where to download org.jdom,
since one of my students struggled with that before christmas...
When we remove jwt-we-feature from /we then we can probably also remove
jwt-we-update-site from there, since this will be generated automatically in
the future, am I right?
NB: We mustn't forget to update the information on the wiki concerning the
CVS, so that every newcomer can understand all these changes. Perhaps we
might upload a README.txt in org.eclipse.jwt-root with a link to that wiki
page?
Best regards,
Florian
PS @Mickael: Have you seen all the bugs that Anne Jacko has raised
concerning our yearly release, e.g. participate in a UI Best practices
Working Group UI walkthrough (as the STP Policy editor did in December)? We
probably need to work on this in the future as well...
-----Ursprüngliche Nachricht-----
Von: jwt-dev-bounces@xxxxxxxxxxx [mailto:jwt-dev-bounces@xxxxxxxxxxx] Im
Auftrag von Mickael Istria
Gesendet: 07 January 2009 11:24
An: Java Workflow Toolbox
Betreff: [jwt-dev] Project Tree Organisation
Hi all,
I'm thinking on how to improve the JWT project tree organisation, and I
suggest that JWT feature should be part of releng. CVS would look like that:
NB: names of folders are not real name, I changed them by laziness, I do not
suggest anything about naming, only tree structure
/releng
/ builder (current releng)
/ tester (testing utils and ant scrips)
/ feature (defines the set of plugins to be included in the release)
/ test feature (the test feature is necessary to have test run
automatically at each build, it includes all test plugins related to the
plugins that are in the feature, only useful for automated testing, not
intended to be published)
/ jwt-master-test-plugin (the test plugin defines a test suite that runs
all tests, it is the entry point for the automated testing framework) /we
/ jwt-we
/ jwt-we-test
/ jwt-plugins
/ jwt-plugin-1
/ jwt-plugin-1-test
/ jwt-plugin-2
/ jwt-plugin-2-test
/ ...
/ jwt-aspects
/ jwt-conf-model
/ ...
/ wam
/ transformation
/ jwt-transformation-base
/ jwt-transformation-base-test
/ jwt-transformation-xpdl
/ jwt-transformation-xpdl-test
/ ...
I think that this organization would better separate development, testing
and release engineering part of JWT, and also encourage testing and
facilitate release engineering.
What do you think about that?
Mickael
_______________________________________________
jwt-dev mailing list
jwt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jwt-dev
