Paul Merlin a écrit :
Niclas Hedhman a écrit :
If the release specification is changed to;
def satisfied = ( codebase == 'none'&& docs == 'complete'&&
tests != 'complete' )
satisfied |= ( codebase != 'early'&& docs == 'good'&& tests ==
'good' )
satisfied |= ( codebase != 'beta'&& docs == 'brief'&& tests ==
'some' )
satisfied |= ( codebase == 'stable' )
satisfied |= ( codebase == 'mature' )
A much more reasonable subset of modules are included. It makes it
heavy on the 'codebase' side, but for 2.0-RCx releases I think this
makes a lot of sense.
It seems to be a clever move.
What are the resulting releasable modules then?
Nevermind, I can see that in the build output.
This produces some odities. Here is an example:
org.qi4j.extension.entitystore-neo4j(true) -> stable, none, some
org.qi4j.library.neo4j(false) -> early, none, none
But we can't release entitystore-neo4j without the neo4j library.
I think that at some point we'll have to review all dev-status.xml files
as the neo4j library should be quite stable for example.
/Paul
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
