| No, this project is not dead [message #2707] |
Tue, 23 June 2009 20:56  |
 Konstantin Komissarchik
Messages: 1077
Registered: July 2009 |
Senior Member |
|
|
... just hibernating until Galileo activity calmed down and I had cycles
to pay attention to longer-term items.
With Galileo out of the way, I have spent several days on getting the
project bootstrapped. I forked the relevant code from WTP, repackaged it
according to this project's naming convention and got everything into CVS.
If you look in CVS now (at /cvsroot/technology), you will see the
structure outlined later in this message. There is quite a bit of code and
content in there. Team project set files can be found at
/org.eclipse.fproj/releng/psfs/.
Everything in CVS HEAD currently builds (against Galileo) and runs. The
existing unit tests that were brought over from WTP are all passing as
well.
We actually even have a working build system now, courtesy of Athena
common build infrastructure and Hudson. I will post instructions later for
how to run the build locally, but anyone can now access build results on
Hudson via the following URL:
https://build.eclipse.org/hudson/job/cbi-fproj-0.1-Galileo/
This job is configured to always build latest from HEAD. I am not a big
fan of map files, tagging and only building what's been "released".
About plans. There are going to be a series of milestones over the next
few months as progress is made towards 1.0.
As a review item, the major goals for the 1.0 release are as follows:
1. Get setup as an independent project.
2. API refactoring and cleanup.
3. Backwards compatibility layer for WTP.
4. Join Helios release train.
So, the first milestone (dubbed 0.1) will take an incremental step towards
the above goals:
1. Code forked from WTP and repackaged into the new namespace... done.
2. Build system implemented and running on Hudson... done.
3. Existing unit tests passing... done.
4. Builds publishing to the download server.
5. Deprecated code removed and other mechanical cleanup items.
My current estimate is that 0.1 will be ready by end of July. After that,
its on to deeper API refactoring and backwards compatibility layer for
WTP. This would be an excellent time for anyone who wants to be involved
with this project (in whatever capacity) to get involved. We have an
opportunity that doesnt happen very often in framework code to make deep
changes in API, but once 1.0 ships next summer, we will have a new API
contract to maintain and will be much more limited in the type of changes
that can be done. So, if you are an existing user of this framework in
WTP, get involved and make your opinions heard. Are there parts of API
that you dislike or are giving you particular problems? Post questions and
feedback on fproj-dev@eclipse.org or the newsgroup
( http://www.eclipse.org/newsportal/thread.php?group=eclipse.f proj). You
can also open bugs and enhancements against this project
( https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Faceted% 20Project%2
0Framework).
CVS Layout of Faceted Project Framework
=======================================
org.eclipse.fproj
core
docs
org.eclipse.fproj.doc.api
features
org.eclipse.fproj-feature
org.eclipse.fproj.sdk-feature
plugins
org.eclipse.fproj
org.eclipse.fproj.sdk
org.eclipse.fproj.ui
tests
features
org.eclipse.fproj.tests-feature
plugins
org.eclipse.fproj.tests
enablement-jdt
docs
org.eclipse.fproj.enablement.jdt.samples
org.eclipse.fproj.enablement.jdt.samples.rand.lib-1.0
org.eclipse.fproj.enablement.jdt.samples.rand.lib-2.0
features
org.eclipse.fproj.enablement.jdt-feature
org.eclipse.fproj.enablement.jdt.sdk-feature
plugins
org.eclipse.fproj.enablement.jdt
org.eclipse.fproj.enablement.jdt.sdk
org.eclipse.fproj.enablement.jdt.ui
releng
releng-features
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03912 seconds
] 
Search
Help
Register
Login
Home
