Hi Matthias,
Of course, not sure if it's the correct but in my flow I only push it to
repo, after release it, so, we can revert it or add something like this[1]
without dirtying the repository
I have 2 questions
1) Should I push it when I stage a version?
2) Should I add this[1] in 0.2.8 version?
[1]
https://github.com/aerogear/aerogear-parent/pull/28
-- Passos
On Thu, Oct 16, 2014 at 4:52 AM, Matthias Wessendorf <matzew(a)apache.org>
wrote:
looks like the pom on the actual git repo is still 0.2.8-SNAPSHOT,
but we
do have a 0.2.8 tag
https://github.com/aerogear/aerogear-parent/blob/master/pom.xml
Noticed when I wanted to merge
https://github.com/aerogear/aerogear-parent/pull/28
You mind pushing the master changes, from the release plugin ?
On Tue, Oct 14, 2014 at 4:36 PM, Daniel Passos <daniel(a)passos.me> wrote:
> Hi,
>
> I’d like to run a new release of our parent/bom.
>
> Here is some changes related to newer versions:
>
> - AEROGEAR-1526 - Update Android Support library version
> <
https://issues.jboss.org/browse/AEROGEAR-1526>
> - AEROGEAR-1525 - Remove unnecessary dependencies
> <
https://issues.jboss.org/browse/AEROGEAR-1525>
> - AEROGEAR-1524 - Change Android Maven Central stub to real Android
> library from Maven SDK deploy
> <
https://issues.jboss.org/browse/AEROGEAR-1524>
> - AEROGEAR-1527 - Move gcm server and json simple from android bom to
> bom <
https://issues.jboss.org/browse/AEROGEAR-1527>
>
> Feel free to test it. I have plan to release it next thursday.
>
> The staging repo is here:
>
>
https://repository.jboss.org/nexus/content/repositories/jboss_releases_st...
>
> — Passos
>