THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- Grab the latest source from SVN
Wiki MarkupCode Block svn co svn+ssh:// https://svn.apache.org/repos/asf/incubator/activemq/camel/trunk cd activemq
- Change the version number: (we so need to make this step automatic) :
project.xml
etc/project.xml
the WireFormat version (if needed.)
Code Block Code Block maven clean default multiproject:deploy dist:deploy
Code Block - Tag the release using your local workspace to a new CAMEL_X_Y label
Code Block svn mkdir svn+ssh://https://svn.apache.org/repos/asf/incubator/activemq/camel/tags/CAMEL_X_Y
-m "Camel X.Y Release"
svn copy ../activemq svn+ssh://https://svn.apache.org/repos/asf/incubator/activemq/camel/tags/CAMEL_X_Y/activemq
-m "Camel X.Y Release"
Code Block - Check that the binaries look fine. h2.
Testing
...
the
...
Camel
...
Release
...
Candidate
...
When
...
folks
...
need
...
to
...
test
...
out
...
a
...
release
...
candidate,
...
the
...
jars
...
will
...
not
...
have
...
been
...
uploaded
...
to
...
the
...
Maven
...
repo.
...
This
...
means
...
that
...
the
...
example
...
programs
...
which
...
use
...
Maven
...
will
...
not
...
automatically
...
work.
...
So
...
whenever
...
running
...
the
...
...
you
...
need
...
to
...
append
...
the
...
following
...
command
...
line
...
argument...
...
| Code Block |
|---|
|
...
mvn camel:run -DremoteRepo=http://people.apache.org/~chirino/apache-camel-1.2.0-RC1/maven2 |
...
|
...
Assuming that the release candidate is deployed to *http://people.apache.org/~chirino/apache-camel-1.2.0-RC1/maven2*.
Announcing the Camel Release
...