summaryrefslogtreecommitdiffstats
path: root/sca-java-2.x/trunk/modules/core-spi/pom.xml (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Allow the spring component to receive parent application context from the ↵rfeng2011-03-211-2/+2
| | | | | | composite context git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@1083938 13f79535-47bb-0310-9956-ffa450edef68
* Put back the build number plugin so that the version in the SPI is correctly ↵antelder2011-03-171-2/+3
| | | | | | populated (was this commented out in error?) git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@1082436 13f79535-47bb-0310-9956-ffa450edef68
* Fix lots of depricated maven variable warnings for Maven v3antelder2011-02-051-1/+1
| | | | git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@1067440 13f79535-47bb-0310-9956-ffa450edef68
* Remove dependencies now included in base Javaantelder2010-12-111-13/+0
| | | | git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@1044577 13f79535-47bb-0310-9956-ffa450edef68
* Move to wstx-as version 3.2.6 consistently. Having two versions in the ↵slaws2010-09-241-3/+3
| | | | | | distro is causing OSGi wiring conflicts git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@1000968 13f79535-47bb-0310-9956-ffa450edef68
* Reenable the version spi with the buildnumber-maven-pluginantelder2010-07-041-2/+0
| | | | git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@960329 13f79535-47bb-0310-9956-ffa450edef68
* Temporarily take out the build number plugin to see if that fixes the Hudson ↵antelder2010-04-081-0/+2
| | | | | | build git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@931839 13f79535-47bb-0310-9956-ffa450edef68
* Start to clean up the node-api (remove Node.destroy())rfeng2010-02-091-1/+1
| | | | git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@908233 13f79535-47bb-0310-9956-ffa450edef68
* Making fallback revision a number to avoid test case issueslresende2010-02-041-1/+1
| | | | git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@906700 13f79535-47bb-0310-9956-ffa450edef68
* Making harvesting of revision number optional, to avoid issues when running ↵lresende2010-01-291-0/+1
| | | | | | on GIT copy of the svn repo git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@904595 13f79535-47bb-0310-9956-ffa450edef68
* Update the Version to include the version and build timeantelder2010-01-271-1/+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 ↵antelder2010-01-261-0/+44
| | | | | | 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 trunklresende2009-11-201-0/+71
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@882795 13f79535-47bb-0310-9956-ffa450edef68