On Jun 7, 2010, at 3:22 PM, Justin Edelson wrote:
If you don't do release:perform, how does the release artifact get
created?
The release artifacts for my project (a stand-alone Java desktop app)
are created using the osxappbundle and launch4j plugins. So my release
process is:
1. Tag the current trunk
2. Check out and build the tagged release
3. Run "mvn osxappbundle:bundle" to create the Mac release artifact
4. Run "mvn launch4j:launch4j" to create the Windows release artifact
5. Grab the resulting .dmg and .exe files from /target and email them
to the client
There's no formal deploy process because I'm just one guy working on a
little desktop app. Setting up a repository would seem like overkill.
Does it make sense to skip release:perform in this context?
Perhaps another option (instead of simply skipping release:perform) is
to configure the deploy:deploy goal with skip=true.
Trevor
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
