summaryrefslogtreecommitdiffstats
path: root/maven-plugins/trunk/tuscany-bundle-plugin/README
diff options
context:
space:
mode:
authorantelder <antelder@13f79535-47bb-0310-9956-ffa450edef68>2011-06-20 10:01:05 +0000
committerantelder <antelder@13f79535-47bb-0310-9956-ffa450edef68>2011-06-20 10:01:05 +0000
commitc6b254a593dbf474ed0ee7cf786546a7936ffd41 (patch)
tree4b593527238882d58163e9c88ec4467406b1e5e7 /maven-plugins/trunk/tuscany-bundle-plugin/README
parenta3d3bbee3933d6d150f9504159eff6e5f208ee37 (diff)
TUSCANY-3861: Rename bundle plugin to be tuscany-bundle-plugin to conform to Maven naming.
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@1137571 13f79535-47bb-0310-9956-ffa450edef68
Diffstat (limited to 'maven-plugins/trunk/tuscany-bundle-plugin/README')
-rw-r--r--maven-plugins/trunk/tuscany-bundle-plugin/README72
1 files changed, 72 insertions, 0 deletions
diff --git a/maven-plugins/trunk/tuscany-bundle-plugin/README b/maven-plugins/trunk/tuscany-bundle-plugin/README
new file mode 100644
index 0000000000..74b16f3266
--- /dev/null
+++ b/maven-plugins/trunk/tuscany-bundle-plugin/README
@@ -0,0 +1,72 @@
+A Maven plugin used by the Tuscany SCA project that can build an OSGi bundle for a
+project's third-party dependencies, generate a directory containing OSGi bundles
+for all the project's module dependencies, and create Eclipse project files
+(.project, .classpath etc) to configure the Eclipse PDE environment for a project.
+
+To build, from the top maven-bundle-plugin run maven:
+
+mvn
+
+or once all the dependencies have been downloaded and a succesful build run use:
+
+mvn clean install -o
+
+So as to avoid the Tuscany SCA project using SNAPSHOT dependencies any changes
+to this module should be released and the Tuscany SCA project updated to use
+the newly released version.
+
+To release this module:
+
+mvn release:prepare
+
+followed by:
+
+mvn release:perform
+
+That will automatically create an SVN tag from the release, update the version
+numbers in the pom.xml files in the trunk and tag, and deploy the artifacts to the
+staging repository defined by the <deploy.altRepository> in your Maven settings.xml.
+While running it will prompt you for the names for the tag, release version etc.
+
+Note: there seem to be issues with having empty folders in the src tree which causes
+ release:prepare to fail, not sure why but deleting the empty folder fixes the
+ problem. You can do "mvn release:rollback" to undo a failed release.
+
+In your maven settings.xml file you must have a server defined named "apache.releases",
+and a profile named "release". For example:
+
+ <servers>
+ ...
+ <server>
+ <id>apache.releases</id>
+ <username>antelder</username>
+ <privateKey>\ant\id_dsa</privateKey>
+ <passphrase>xxx</passphrase>
+ <directoryPermissions>775</directoryPermissions>
+ <filePermissions>664</filePermissions>
+ </server>
+ </servers>
+
+ <profiles>
+ ...
+ <profile>
+ <id>release</id>
+ <properties>
+ <gpg.passphrase>...</gpg.passphrase>
+ <deploy.altRepository>apache.releases::default::scp://people.apache.org/home/antelder/public_html/tuscany/maven-bundle-plugin-1.0</deploy.altRepository>
+ </properties>
+ </profile>
+ </profiles>
+
+Call a vote to release the module, eg: http://apache.markmail.org/message/6jnlfxbx7uklt5nv
+
+After a successful vote copy the staging artifacts to the live repository, eg:
+
+cp -p -v -R maven-bundle-plugin-1.0/org/apache/tuscany/maven/plugins/ /x1/www/people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/tuscany/maven/plugins
+
+
+
+
+
+
+