| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@908233 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
| |
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@906700 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
|
|
| |
on GIT copy of the svn repo
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@904595 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
| |
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@903575 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
|
|
| |
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
|
|
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@882795 13f79535-47bb-0310-9956-ffa450edef68
|