[aerogear-dev] Help! (was: Re: Cordova Push - 1.0.3 release (was: Re: Push plugin for Cordova))

Matthias Wessendorf matzew at apache.org
Tue Jul 14 11:01:44 EDT 2015


I need help :-)

a few 'problems'

* there is already a 1.0.3 TAG - but was not published (not a big deal - we
will just do 1.0.4 instead)
* I can not publish the 1.0.4 stuff - this is a real problem/blocker :-(

here is my
> plugman publish .

I am getting this error:
<error>
attempting to publish plugin to registry
npm ERR! publish Failed PUT response undefined
Error Code: undefined
login error
</error>

Unfortunately the current published 1.0.2 is broken and does not work...,
another pity is the 'old' registry (where our 1.0.x stuff is located) is
read-only by tomorrow:
http://cordova.apache.org/announcements/2015/04/21/plugins-release-and-move-to-npm.html

So... we can only update it today :-)


If one of you, that did push some plugins in the past (Erik in on
vacation), could help out here and push the 1.0.4 TAG to the registry? It's
highly appreciated.

thanks,
Matthias



On Tue, Jul 14, 2015 at 2:30 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hi,
>
> now that we merged the PR from Martin, and the given fact that the old
> plugin registry is read-only, starting tomorrow, I'd like to push a release
> of the 1.0.3 version, using this branch:
>
> https://github.com/aerogear/aerogear-cordova-push/tree/1.0.x
>
> Any thoughts?
>
> On Tue, Jul 14, 2015 at 1:35 PM, Martin Murphy <mmurphy at redhat.com> wrote:
>
>>
>> On 14 Jul 2015, at 12:16, Matthias Wessendorf <matzew at apache.org> wrote:
>>
>>
>>
>> On Tue, Jul 14, 2015 at 1:11 PM, Martin Murphy <mmurphy at redhat.com>
>> wrote:
>>
>>> Hi Matthias,
>>> That would do, however I was think more of this way:
>>>
>>> https://github.com/mmurphy/aerogear-cordova-push/commit/73198edf6364c93ca77f6f32d7f0925c19bb1477
>>> to avoid the risk of pointing at a changing repo.
>>>
>>
>> sounds good!
>>
>>
>>>
>>> Can use the one you mentioned, or a combination of them?
>>>
>>> I can certainly do the PR.
>>>
>>
>> that would be awesome
>>
>>
>> Is this sufficient?
>> https://github.com/aerogear/aerogear-cordova-push/pull/74
>>
>>
>>
>>>
>>>
>>> Best Regards,
>>> Martin Murphy.
>>>
>>>
>>> On 14 Jul 2015, at 11:59, Matthias Wessendorf <matzew at apache.org> wrote:
>>>
>>> Hi Martin,
>>>
>>> so - it's basically porting this commit over to the 1.0x branch:
>>>
>>> https://github.com/aerogear/aerogear-cordova-push/commit/ac1bcc624db98d5a0123d092a1d2231911a7c2c3
>>>
>>> right ?
>>>
>>> Mind sending a PR ?
>>>
>>> On Mon, Jul 13, 2015 at 5:59 PM, Martin Murphy <mmurphy at redhat.com>
>>> wrote:
>>>
>>>> Hi folks,
>>>> we have a Cordova application that’s using Codrova 3.3.
>>>> The application uses org.jboss.aerogear.cordova.push 1.0.2
>>>>
>>>> When preparing for an android build, there seems to be an problem
>>>> installing one of the dependencies of the aurora plugin
>>>> An id has been updated: com.vladstirbu.cordova.promise, now has a
>>>> different id: es6-promise-plugin.
>>>>
>>>> The newer plugin 2.0.2 is in the npm registry.
>>>>
>>>> Is it possible to add a fix and deploy to the old cordova registry so
>>>> that it’s usable in 3.x
>>>> Is the newer plugin 2.0.2 backward compatible with 1.0.2
>>>>
>>>> I understand that the ideal approach would be to use a more up-to-date
>>>> version of Cordova, and use the latest aurora plugin, however it will take
>>>> some time before I will be able to do that.
>>>> I’m open to other suggestions also.
>>>>
>>>> Best Regards,
>>>> Martin Murphy.
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> 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
>>>
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> 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
>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> 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
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150714/6d4540de/attachment.html 


More information about the aerogear-dev mailing list