| new b3 version checked in - guice added and one more test green [message #606988] |
Thu, 13 May 2010 02:10 |
 Henrik Lindberg
Messages: 2509
Registered: July 2009 |
Senior Member |
|
|
Hi,
I just checked in a new version of b3 (non aggregator) which has the
repository stuff almost done. The failing "fruitsallad" test now works
again - so after you get this new version should expect 2 of the b3
JUnit tests to be failing.
I will come back with a more elaborate post on how the repository
support now works, but here is a brief explanation:
When editing:
- the editor will allow any type of repository to be used, but will show
warnings for anything it does not "understand"
- if the repository type is known, the editor will show errors if the
declaration does not comply with the rules set up for the repository type.
- A repository type is made known to the environment via an extension
point where a 'repository validator' class is associated with the
repository type. This validator validates the possible options for a
particular repository type.
At runtime:
- Google Guice is used to bind interfaces to implementation
- A request for a particular repository type is thus configurable.
- All unknown (and known repositories without specific binding), are
bound to a repository handler that just keeps track of the evaluated data.
This means:
- A specific engine (like one using buckminster to build) can use the
default (descriptive repository implementations) and use this to
instantiate specific implementations.
- A testing engine can verify that the evaluated information and options
are there
- A testing engine can use a repository type that is known to serve
particular build units (without actually testing a particular repository
technology).
- etc. etc.
Regards
- henrik
|
|
|
Powered by
FUDForum. Page generated in 0.03995 seconds
] 
Search
Help
Register
Login
Home
