[aerogear-dev] aerogear-unified-push-java-client 0.2.0 released

Sebastien Blanc scm.blanc at gmail.com
Wed Aug 7 02:50:55 EDT 2013


Hi,
FYI , it is now on maven central \o/

http://repo1.maven.org/maven2/org/jboss/aerogear/unifiedpush/unified-push-java-client/



On Sun, Aug 4, 2013 at 4:56 PM, Sebastien Blanc <scm.blanc at gmail.com> wrote:

> Ok, old staging repo has been dropped. Did the release again .
> New staging repo is
> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-1416/
> Seb
>
>
>
> On Fri, Aug 2, 2013 at 10:17 PM, Bruno Oliveira <bruno at abstractj.org>wrote:
>
>> Yes, you MUST delete the tag, otherwise maven plugin will grab the old one
>>
>> Yes, repeat the whole process means delete the tag, tag again, push the
>> tag...
>>
>> Remote tag.
>>
>>
>> On Fri, Aug 2, 2013 at 9:10 AM, Sebastien Blanc <scm.blanc at gmail.com>wrote:
>>
>>>
>>>
>>>
>>> On Fri, Aug 2, 2013 at 11:50 AM, Bruno Oliveira <bruno at abstractj.org>wrote:
>>>
>>>> I would drop the staged release, fix it and release again. That wasn't
>>>> released to maven central yet, so doesn't make sense to have a buggy
>>>> release.
>>>>
>>>> Regarding the release process if you are up to revert it
>>>>
>>>> - Revert
>>>>
>>>
>>> And also delete the remote 0.2.0 tag , correct ?
>>>
>>> - Fix the changes and commit
>>>> - Follow the release process
>>>> - Instead of push the changes to master and tag. Just tag the release, I
>>>> already tested and it works with maven plugin
>>>>
>>>
>>> Just double checking : The tag still needs to be pushed ? What does the
>>> maven release use : the local tag or the remote tag ?
>>>
>>>>
>>>> Into this way you will avoid reverted commits on master.
>>>>
>>>> Matthias Wessendorf wrote:
>>>> >
>>>> >
>>>> >
>>>> > On Fri, Aug 2, 2013 at 10:26 AM, Sebastien Blanc <scm.blanc at gmail.com
>>>> > <mailto:scm.blanc at gmail.com>> wrote:
>>>> >
>>>> >     Okay,
>>>> >     So after testing various scenarios, we spotted a critical
>>>> >     bug https://issues.jboss.org/browse/AGPUSH-233
>>>> >     My question is, the release 0.2.0 is currently on staging, what is
>>>> >     the next step ? Cancel it and prepare a 0.2.1 release ?
>>>> >
>>>> >
>>>> > that would be my personal preference.
>>>> >
>>>> > -M
>>>> >
>>>> >
>>>> >     Thx,
>>>> >     Seb
>>>> >
>>>> >
>>>> >
>>>> >     On Wed, Jul 31, 2013 at 2:25 PM, Sebastien Blanc
>>>> >     <scm.blanc at gmail.com <mailto:scm.blanc at gmail.com>> wrote:
>>>> >
>>>> >         Hi Folks,
>>>> >
>>>> >         I'm happy to announce the release of
>>>> >          aerogear-unified-push-java-client 0.2.0.
>>>> >         With this release, thanks to the fluent API it will be even
>>>> >         easier to send messages to the Push Server.
>>>> >
>>>> >         This is the staging repo :
>>>> >
>>>> >
>>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-1382
>>>> >
>>>> >         Here is the changelog :
>>>> >
>>>> >         * added missing descrs and minor formatting
>>>> >          * adding javadoc to the getters
>>>> >          * refactor to have category, deviceType and variants on the
>>>> >         correct level
>>>> >          * javadoc in-sync with the guide
>>>> >          * moved to attributes map instead of fields
>>>> >          * added test case
>>>> >          * missing getter for variants
>>>> >          * be specific on ids
>>>> >          * added missing variants param.
>>>> >          * remove unused param.
>>>> >          * missing throw
>>>> >          * small typo
>>>> >          * renamed the tag name to unified-push-java-client
>>>> >          * rename artifact to unified-push-java-client
>>>> >          * Merge remote-tracking branch 'qmx/release_cleanups'
>>>> >          * fix formatting
>>>> >          * update developer section
>>>> >          * add scm section
>>>> >          * fix javadoc warnings and polish
>>>> >          * add a some javadoc to the buildUrl method
>>>> >          * add a non args constructor + extrac checks for serverURL
>>>> >          * README update,  selective send section should use sendTo
>>>> >          * Merge branch 'parent_pom'
>>>> >          * add aerogear's parent pom
>>>> >          * fix pom formatting
>>>> >          * fixing conflicts
>>>> >          * fixed unit test
>>>> >          * moved Strings to fields, extra test cases, null check
>>>> >          * simple-push auto version fix
>>>> >          * more javadoc polishing
>>>> >          * updated javadoc
>>>> >          * more JavaDoc
>>>> >          * added some Javadoc
>>>> >          * add category, deviceType and rename identifiers to aliases
>>>> >          * change the version and update the readme
>>>> >          * Fixing merge conflicts
>>>> >          * first version of UnifiedMessage Builder
>>>> >          * fixed unit test
>>>> >          * moved Strings to fields, extra test cases, null check
>>>> >          * simple-push auto version fix
>>>> >          * more javadoc polishing
>>>> >          * updated javadoc
>>>> >          * more JavaDoc
>>>> >          * added some Javadoc
>>>> >          * Merge branch 'AGPUSH-135' of
>>>> >         https://github.com/aerogear/aerogear-unified-push-java-client
>>>> >         into AGPUSH-135
>>>> >          * add category, deviceType and rename identifiers to aliases
>>>> >          * first version of UnifiedMessage Builder
>>>> >          * Merge branch 'master' of
>>>> >         https://github.com/aerogear/aerogear-unified-push-java-client
>>>> >          * Polishing the JAva Sender Client
>>>> >          * Merge branch 'readme_update'
>>>> >          * Update Readme example code
>>>> >          * Adding a finally block and a disconnect(), to release
>>>> resources
>>>> >          * change the version and update the readme
>>>> >          * first version of UnifiedMessage Builder
>>>> >          * Keep it simple
>>>> >          * moving to httpurlconnection
>>>> >          * Merge branch 'license_fixes'
>>>> >          * fix license headers
>>>> >          * Merge branch 'formatting'
>>>> >          * fix formatting
>>>> >
>>>> >         Please enjoy, test and report bugs !
>>>> >
>>>> >         Seb
>>>> >
>>>> >
>>>> >
>>>> >     _______________________________________________
>>>> >     aerogear-dev mailing list
>>>> >     aerogear-dev at lists.jboss.org <mailto:aerogear-dev at lists.jboss.org
>>>> >
>>>> >     https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>> >
>>>> >
>>>> >
>>>> >
>>>> > --
>>>> > Matthias Wessendorf
>>>> >
>>>> > blog: http://matthiaswessendorf.wordpress.com/
>>>> > sessions: http://www.slideshare.net/mwessendorf
>>>> > twitter: http://twitter.com/mwessendorf
>>>> >
>>>> > _______________________________________________
>>>> > aerogear-dev mailing list
>>>> > aerogear-dev at lists.jboss.org
>>>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>> --
>>>> abstractj
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>>
>> --
>> "The measure of a man is what he does with power" - Plato
>> -
>> @abstractj
>> -
>> Volenti Nihil Difficile
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20130807/18a4c2b1/attachment-0001.html 


More information about the aerogear-dev mailing list