search

yuchen931201 / maven-android-plugin

Automatically exported from code.google.com/p/maven-android-plugin
0 stars 0 forks source link

can't do mvn release easily #18

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Try releasing everything with maven.
2.
3.

What is the expected output? What do you see instead?
It should just work.
The samples can't be released at the same time as the plugin, because they
require it to be built first. Having the plugin and samples directories in
the same git repo (but still subdirectories, and no root pom) doesn't work
either.

What is the output of "mvn -version" on your machine?
Maven version: 2.0.10
Java version: 1.6.0_13
OS name: "linux" version: "2.6.28-11-generic" arch: "i386" Family: "unix"

Please use labels and text to provide additional information.

Original issue reported on code.google.com by hugo.josefson.old@gmail.com on 11 Jun 2009 at 12:57

GoogleCodeExporter commented 9 years ago 
Implementation note:
Perhaps split up maven-android-plugin directory and samples directory into 
different
git repos. Then each one has its pom.xml in the root directory of their git 
repo.

Original comment by hugo.josefson.old@gmail.com on 11 Jun 2009 at 12:58

GoogleCodeExporter commented 9 years ago

Original comment by hugo.josefson.old@gmail.com on 11 Jun 2009 at 12:58

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
I split up the git repo locally into one for maven-android-plugin, and one for
samples. Each have their respective pom.xml in the root of their git repo, and 
YES!
That worked. It is now much easier to perform a release.

Will just have to repeat the same procedure on github now...

For future reference, here's the basic release procedure:
* Run this command first in maven-android-plugin, then in 
maven-android-plugin-samples:

mvn clean && mvn install && mvn release:prepare release:perform

Original comment by hugo.josefson.old@gmail.com on 11 Jun 2009 at 5:04

GoogleCodeExporter commented 9 years ago 
note to self: also remember to document that it's appropriate to update the 
samples
poms to use the newly released version of the plugin before releasing the 
samples.

Original comment by hugo.josefson.old@gmail.com on 11 Jun 2009 at 5:23

GoogleCodeExporter commented 9 years ago 
Done.
Samples are now in their own git repo, and released as its own artifact.

Original comment by hugo.josefson.old@gmail.com on 11 Jun 2009 at 9:37

GoogleCodeExporter commented 9 years ago 
It worked well.

Original comment by hugo.josefson.old@gmail.com on 12 Jun 2009 at 8:46