summaryrefslogtreecommitdiffstats
path: root/sca-java-2.x/trunk/modules/core-spi/src/main/resources (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Refactor the DomainRegistryFactory to be extensions of ↵rfeng2010-01-291-0/+17
| | | | | | DomainRegistryFactoryExtensionPoint git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@904367 13f79535-47bb-0310-9956-ffa450edef68
* Update the Version to include the version and build timeantelder2010-01-271-0/+2
| | | | git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@903575 13f79535-47bb-0310-9956-ffa450edef68
* First cut at having a programatic way to get the svn revision that a tuscany ↵antelder2010-01-261-0/+28
| | | | | | build is from. This approach seems a little conveluted so if anyone has a better approach please do say, this one uses the Maven buildnumber plugin to set a mvn property with the svn revision, which is then written into a message properties file with the antrun plugin, which is then used initilize a constant in a Version class. Not sure if it even actually works, committing it so i can get a Hudson build and check if it does end up with the correct value git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@903166 13f79535-47bb-0310-9956-ffa450edef68
* Start to split policy builder into two phases: implementation hierarchy and ↵rfeng2009-12-011-19/+0
| | | | | | structural hierarchy git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@885961 13f79535-47bb-0310-9956-ffa450edef68
* Moving 2.x trunklresende2009-11-204-0/+76
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@882795 13f79535-47bb-0310-9956-ffa450edef68