AeroGear Crypto Java 0.1.2 released
by Bruno Oliveira
Good morning, just to let you know we released today the bits for digital signatures and some bug fixes.
Have a happy new year sweet hearts.
--
abstractj
2 years, 7 months
1.2.0.Final (was: Re: UPS 1.2.0-beta.2 release)
by Matthias Wessendorf
Things are staged here:
https://repository.jboss.org/nexus/content/repositories/jboss_releases_st...
It's basically stable since we did the last beta releases, and requires now
WF10 or later, and Keycloak is required to be separated as well
-M
On Wed, Sep 13, 2017 at 4:33 PM, Matthias Wessendorf <matzew(a)apache.org>
wrote:
> RC2 is available for evaluation:
> https://repository.jboss.org/nexus/content/repositories/
> jboss_releases_staging_profile-12344/
>
> big difference between rc1 and rc2 is just this one JIRA:
> https://issues.jboss.org/browse/AGPUSH-1368
>
> -M
>
> On Mon, Sep 11, 2017 at 2:40 PM, Matthias Wessendorf <matzew(a)apache.org>
> wrote:
>
>> Tomorrow, I will start the 1.2.0.Final release
>>
>> afterwards will update the docker images
>>
>> On Wed, Sep 6, 2017 at 5:14 PM, Matthias Wessendorf <matzew(a)apache.org>
>> wrote:
>>
>>> release candidate 1 is here:
>>>
>>> https://repository.jboss.org/nexus/content/repositories/jbos
>>> s_releases_staging_profile-12288/
>>>
>>> -M
>>>
>>> On Wed, Sep 6, 2017 at 12:57 PM, Matthias Wessendorf <matzew(a)apache.org>
>>> wrote:
>>>
>>>> Ok, clicked the button.
>>>>
>>>> this will be online tomorrow
>>>>
>>>> In a few days, we might see a CR1 - and shortly after that a .Final :-)
>>>>
>>>> Cheers,
>>>> Matthias
>>>>
>>>> On Tue, Sep 5, 2017 at 6:00 PM, Matthias Wessendorf <matzew(a)apache.org>
>>>> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> after some month of time, we are running a new release of the master
>>>>> branch: 1.2.0-beta.2
>>>>>
>>>>> Main fixes did include:
>>>>> * WildFly 11 (CR1) support
>>>>> * Keycloak decoulping
>>>>> * SimplePush/MPNS removal
>>>>> * version updates of the non Java EE dependencies
>>>>>
>>>>> More details can be found here:
>>>>> https://issues.jboss.org/projects/AGPUSH/versions/12335470
>>>>>
>>>>> Staging repo is located here:
>>>>> https://repository.jboss.org/nexus/content/repositories/jbos
>>>>> s_releases_staging_profile-12282/
>>>>>
>>>>> Once the release is out, I will update the docker images and compose
>>>>> file (including a decouple Keycloak)
>>>>>
>>>>> Have fun!
>>>>> -Matthias
>>>>>
>>>>>
>>>>> --
>>>>> Matthias Wessendorf
>>>>>
>>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>>> twitter: http://twitter.com/mwessendorf
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Matthias Wessendorf
>>>>
>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>> twitter: http://twitter.com/mwessendorf
>>>>
>>>
>>>
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> twitter: http://twitter.com/mwessendorf
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> twitter: http://twitter.com/mwessendorf
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> twitter: http://twitter.com/mwessendorf
>
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf
7 years
Upstream Community Documentation
by Paul Wright
Hi AeroGear, FeedHenry
As part of a review of Digger (Build Farm) docs, I created a PR
<https://github.com/aerogear/aerogear.org/pull/687> to attempt to
improve user navigation of:
https://aerogear.org/
Feedback on that PR raised the question of general navigation of this
web site:
* What should be in the Getting Started menu to help me get started with
digger? (I think digger is more than a code snippet or library)
* If I'm interested in digger, should I expect any digger info under
module or platform menu items?
* I sometimes navigate to a page, but can't remember how I navigated to
it, then cannot find the info again.
These issues can be resolved, but will require a lot of effort, but
another question is:
* Will it provide us a platform to build the community we want?
The web site looks great, and I learn a lot from browsing it (eg I
didn't know about https://aerogear.org/sync/ until today), but I wonder
if it is doing the job we want it to do? and how do we keep it
up-to-date? (https://aerogear.org/docs/planning/
<https://aerogear.org/docs/planning/>)
Meanwhile over at:
http://feedhenry.org/docs/
Not much there at the moment, but it will be the location for
mobile.next doc
* Do we want users switching from MCP doc on feedhenry.org
<http://feedhenry.org> over to digger doc on aerogear.org
<http://aerogear.org> and back again for some fh.sync doc?
These are difficult and challenging questions, I don't expect them to be
easy to resolve and I'm happy to agree with whatever the communities
decide to do. All this mail hopes to do is to raise the question of
* How do we communicate the "mobile.next" (i.e. feedhenry mcp and
aerogear digger) message as cleanly as possible?
(The real challenge occurs after that, convincing them to adopt
mobile.next, but users will never adopt if they can't find answers they
hit the first stumbling block)
thanks,
Paul
7 years
SonarQube problem ?
by Matthias Wessendorf
Hi,
running "mvn clean org.jacoco:jacoco-maven-plugin:prepare-agent package
sonar:sonar" locally (and on travis), I get a build failure:
[ERROR] SonarQube server [http://localhost:9000] can not be reached
[ERROR] Failed to execute goal
org.sonarsource.scanner.maven:sonar-maven-plugin:3.3.0.603:sonar
(default-cli) on project unifiedpush-parent: Unable to execute SonarQube:
Fail to get bootstrap index from server: Failed to connect to
localhost/0:0:0:0:0:0:0:1:9000: Connection refused (Connection refused) ->
[Help 1]
I think it used to work - seeing this now locally for the first time ....
any ideas ?
-M
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf
7 years
Re: [aerogear-dev] [feedhenry-dev] Upstream Community Documentation
by Laura Fitzgerald
+1 on merging. From my experience having multiple locations where we are
documenting the same project has created some unnecessary difficulties in
terms of maintaining/managing documentation.
Also Paul and John raised some valid points here in terms of building
community/engagement in use of the product. It's never a fun experience
when the documentation on a project is not good and it doesn't give a good
impression to start.
On Mon, Nov 27, 2017 at 12:17 PM, Wojciech Trocki <wtrocki(a)redhat.com>
wrote:
>
> ---------- Forwarded message ----------
> From: Wei Li <weil(a)redhat.com>
> Date: Thu, Nov 23, 2017 at 2:46 PM
> Subject: Re: [feedhenry-dev] [aerogear-dev] Upstream Community
> Documentation
> To: John Frizelle <jfrizell(a)redhat.com>
> Cc: AeroGear Developer Mailing List <aerogear-dev(a)lists.jboss.org>,
> Matthias Wessendorf <matzew(a)apache.org>, feedhenry-dev(a)redhat.com
>
>
> +1. Maintaining 2 communities with similar objectives are just too
> confusing to a lot of people. I would like to see them merged as well.
>
> On Thu, Nov 23, 2017 at 1:23 PM, John Frizelle <jfrizell(a)redhat.com>
> wrote:
>
>> Hi All,
>>
>> I would like to get people's thoughts on the cost / benefit of continuing
>> to maintain both the feedhenry and aerogear communities (mailing lists, IRC
>> channels, web sites etc...). There seems to be a lot of cross over between
>> the two (the are both mobile focused communities backed primarily by Red
>> Hat) and I struggle to see what benefit we, or our community members, get
>> from having our work spread across these two communities...
>>
>> From my perspective, I would rather see one healthy, vibrant community
>> that we can all get behind instead of the current fractured status where it
>> is unclear what lives where and why.
>>
>> Just my 2 cents...
>>
>> Cheers,
>> John.
>>
>>
>> --
>> John Frizelle
>> Chief Architect, Red Hat Mobile
>> Consulting Engineer
>>
>> mobile: *+353 87 290 1644 <//+353872901644>*
>> twitter:* @johnfriz*
>> skype: *john_frizelle*
>> mail: *jfrizell(a)redhat.com <jfrizell(a)redhat.com>*
>>
>>
>>
>>
>> On 23 November 2017 at 13:09, Ali Ok <aliok(a)redhat.com> wrote:
>>
>>> Hello,
>>>
>>> FYI, once I started this epic to improve and clean up AeroGear.org
>>> website: https://issues.jboss.org/browse/AEROGEAR-1760
>>>
>>> If we would like to do it, we need to find out a group that takes
>>> ownership of the clean up. AeroGear people are now more spread than before.
>>>
>>> Cheers
>>>
>>> On Thu, Nov 23, 2017 at 9:13 AM, Matthias Wessendorf <matzew(a)apache.org>
>>> wrote:
>>>
>>>> Hi Paul,
>>>>
>>>> lot's of content on the AeroGear website is out of date, due to lack of
>>>> work in the past two years (see the planing page).
>>>>
>>>> Note: the sync was a prototype, for real-time sync; based on different
>>>> algorithms and papers in that area, but never went really anywere...
>>>> I guess it's dead now.
>>>>
>>>> Over the past two years we did work a bit on the AeroGear Push server,
>>>> and their libraries (e.g. mobile client-side lib and server-side
>>>> integrations for node/java).
>>>>
>>>> Regarding Digger - it's a standalone project, under the aerogear realm
>>>> - like push. Both bits can be used completely independent.
>>>>
>>>>
>>>> I think some content (e.g. sync) needs to be removed (while we can
>>>> still keep the repos), but we should be perhaps focusing on AeroGear UPS
>>>> and digger, for community offerings.
>>>>
>>>> ag.org/push (like is)
>>>> ag.org/digger (with backgrounds motivations, Laura's videos etc)
>>>>
>>>>
>>>> Regarding feedhenry / mcp , just one comment: it does integrate w/ AG
>>>> features, such as push or digger, and will IMO offer the integration parts
>>>> (e.g. APBs etc)
>>>>
>>>>
>>>> -Matthias
>>>>
>>>>
>>>> On Wed, Nov 22, 2017 at 2:59 PM, Paul Wright <pwright(a)redhat.com>
>>>> wrote:
>>>>
>>>>> Hi AeroGear, FeedHenry
>>>>>
>>>>> As part of a review of Digger (Build Farm) docs, I created a PR
>>>>> <https://github.com/aerogear/aerogear.org/pull/687> to attempt to
>>>>> improve user navigation of:
>>>>>
>>>>> https://aerogear.org/
>>>>>
>>>>> Feedback on that PR raised the question of general navigation of this
>>>>> web site:
>>>>>
>>>>> * What should be in the Getting Started menu to help me get started
>>>>> with digger? (I think digger is more than a code snippet or library)
>>>>>
>>>>> * If I'm interested in digger, should I expect any digger info under
>>>>> module or platform menu items?
>>>>>
>>>>> * I sometimes navigate to a page, but can't remember how I navigated
>>>>> to it, then cannot find the info again.
>>>>>
>>>>> These issues can be resolved, but will require a lot of effort, but
>>>>> another question is:
>>>>>
>>>>> * Will it provide us a platform to build the community we want?
>>>>>
>>>>> The web site looks great, and I learn a lot from browsing it (eg I
>>>>> didn't know about https://aerogear.org/sync/ until today), but I
>>>>> wonder if it is doing the job we want it to do? and how do we keep it
>>>>> up-to-date? (https://aerogear.org/docs/planning/)
>>>>>
>>>>> Meanwhile over at:
>>>>>
>>>>> http://feedhenry.org/docs/
>>>>>
>>>>> Not much there at the moment, but it will be the location for
>>>>> mobile.next doc
>>>>>
>>>>> * Do we want users switching from MCP doc on feedhenry.org over to
>>>>> digger doc on aerogear.org and back again for some fh.sync doc?
>>>>>
>>>>> These are difficult and challenging questions, I don't expect them to
>>>>> be easy to resolve and I'm happy to agree with whatever the communities
>>>>> decide to do. All this mail hopes to do is to raise the question of
>>>>>
>>>>> * How do we communicate the "mobile.next" (i.e. feedhenry mcp and
>>>>> aerogear digger) message as cleanly as possible?
>>>>>
>>>>> (The real challenge occurs after that, convincing them to adopt
>>>>> mobile.next, but users will never adopt if they can't find answers they
>>>>> hit the first stumbling block)
>>>>>
>>>>> thanks,
>>>>>
>>>>> Paul
>>>>>
>>>>> _______________________________________________
>>>>> aerogear-dev mailing list
>>>>> aerogear-dev(a)lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Matthias Wessendorf
>>>>
>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>> twitter: http://twitter.com/mwessendorf
>>>>
>>>> _______________________________________________
>>>> feedhenry-dev mailing list
>>>> feedhenry-dev(a)redhat.com
>>>> https://www.redhat.com/mailman/listinfo/feedhenry-dev
>>>>
>>>>
>>>
>>> _______________________________________________
>>> feedhenry-dev mailing list
>>> feedhenry-dev(a)redhat.com
>>> https://www.redhat.com/mailman/listinfo/feedhenry-dev
>>>
>>>
>>
>> _______________________________________________
>> feedhenry-dev mailing list
>> feedhenry-dev(a)redhat.com
>> https://www.redhat.com/mailman/listinfo/feedhenry-dev
>>
>>
>
>
> --
>
> WEI LI
>
> SENIOR SOFTWARE ENGINEER
>
> Red Hat Mobile <https://www.redhat.com/>
>
> weil(a)redhat.com M: +353862393272
> <https://red.ht/sig>
>
> _______________________________________________
> feedhenry-dev mailing list
> feedhenry-dev(a)redhat.com
> https://www.redhat.com/mailman/listinfo/feedhenry-dev
>
>
>
>
> --
>
> WOJCIECH TROCKI
>
> Red Hat Mobile <https://www.redhat.com/>
>
> IM: wtrocki
> <https://red.ht/sig>
>
--
LAURA FITZGERALD
Red Hat Mobile <https://www.redhat.com/>
Communications House, Cork Road
Waterford City, Ireland X91NY33
lfitzger(a)redhat.com IM: lfitzgerald
<https://red.ht/sig>
7 years
AeroGear Android Offline
by Daniel Passos
A long time ago we try to draft an offline library, we have created an
aerogear-android-offline GH repo, but we did not work too much on it there
and never released it.
Should we delete this repo or only add a notice on the README
--
-- Passos
7 years, 1 month
Digger repository renaming
by Ali Ok
Hi,
We are renaming the Digger Github repositories.
- digger-jenkins ---> aerogear-digger
- digger-java --> aerogear-digger-java-client
- digkins --> aerogear-digger-node-client
- digger-installer --> aerogear-digger-installer
Related JIRA: https://issues.jboss.org/browse/AGDIGGER-203
I will send another email once everything is done.
Cheers,
Ali
7 years, 1 month
