| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Update the Version to include the version and build time | antelder | 2010-01-27 | 1 | -0/+3 |
| | | | | | 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 ↵ | antelder | 2010-01-26 | 1 | -0/+33 |
| | | | | | | | 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 | ||||
| * | Moving 2.x trunk | lresende | 2009-11-20 | 1 | -0/+207 |
| git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@882795 13f79535-47bb-0310-9956-ffa450edef68 | |||||
 |
index : apache-tuscany | |
| apache tuscany | lookshe |
| summaryrefslogtreecommitdiffstats |