[jitsi-dev] Jitsi official JNLP address?


#1

The RTC client launcher JAR knows the following address (unless overridden):

     https://jitsi.org/webstart/latest/client.jnlp

     https://jitsi.org/webstart/stable/client.jnlp

and it just tries the first one by default.

Would it be possible to automatically publish the latest builds of the
webstart branch at that URL or could somebody tell me another URL to put
in the launcher JAR as a default?


#2

The RTC client launcher JAR knows the following address (unless

overridden):

     https://jitsi.org/webstart/latest/client.jnlp
     
     https://jitsi.org/webstart/stable/client.jnlp
and it just tries the first one by default.

Would it be possible to automatically publish the latest builds of the
webstart branch at that URL or could somebody tell me another URL to put
in the launcher JAR as a default?

I lost track of the current status with all your pull requests :slight_smile:
Did you solve the problem with repacking BouncyCastle?

I guess we could setup another build and publish it, not so much of an issue
as it is a pure java build and an upload. The more important question is: do
we want that? I for once don't have the resources to actively maintain it,
and I think even less so the other developers. Can you give some kind of a
commitment to keep the branch (or then probably merged to master) up to date
with the ever evolving and changing JWS requirements?

Emil?

Ingo

···

On 2014-08-13 17:50, Daniel Pocock wrote:


#3

The RTC client launcher JAR knows the following address (unless

overridden):

     https://jitsi.org/webstart/latest/client.jnlp
     
     https://jitsi.org/webstart/stable/client.jnlp
and it just tries the first one by default.

Would it be possible to automatically publish the latest builds of the
webstart branch at that URL or could somebody tell me another URL to put
in the launcher JAR as a default?

I lost track of the current status with all your pull requests :slight_smile:
Did you solve the problem with repacking BouncyCastle?

Only by manually stripping the old signatures from the JAR and resigning it

I guess we could setup another build and publish it, not so much of an issue
as it is a pure java build and an upload. The more important question is: do
we want that? I for once don't have the resources to actively maintain it,
and I think even less so the other developers. Can you give some kind of a
commitment to keep the branch (or then probably merged to master) up to date

Whatever we decide, I feel it will need to be merged into master to make
it easier to support.

Continuous integration (e.g. Jenkins) should be able to build and
publish a daily update to the webstart

with the ever evolving and changing JWS requirements?

Just making it work for current JVMs will be enough for some users.

If it is successful then hopefully webstart users will start providing
feedback (and maybe even pull requests) as the JVM security requirements
continue to evolve.

···

On 13/08/14 13:10, Ingo Bauersachs wrote:

On 2014-08-13 17:50, Daniel Pocock wrote:

Emil?

Ingo

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev