Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [paho-dev] mqtt-client 0.4.0 appears to be missing from repo.eclipse.org

Hi mqtt devs,

This is a very serious issue for the Spark project because a lot of Spark users build from source. We are going to upgrade mqtt version for future releases, but this breaks all current/past releases. In case you are not familiar with Spark, it is now the most actively developed Big Data open source project: in the past year alone, there are close to 400 people that have contributed code to the project. Many applications are being built on top of this and this can potentially break all of them. I'd also imagine this breaks other non-Spark projects that depend on mqtt as well.

A released artifact in a repository should be immutable. Spark depends on it, other applications depend on it, and applications that depend on Spark can depend on it. The transitive closure is pretty large.

Again, we are going to upgrade the mqtt dependency in Spark, but I urge you to add the 0.4.0 artifact back. Otherwise we would have to be extra cautious in the future with respect to any dependency on mqtt, e.g. removing it from the dependency or the default build profile, which would cause inconvenience for our users also. 


On Wed, Nov 26, 2014 at 11:56 AM, Jeff Prestes <jeffprestes@xxxxxxxxx> wrote:
Hi All,

I agree with Brian. Of course work with lastest version is best way, however it could break some legacy code where you can't change fast for any reasons (who works for Enterprise companies knows this bad situation). 

IMHO, remove the old version from Repository maybe is not the best approach to improve the innovation. The idea in general is good but maybe we could find another way.

Best,

-Jeff Prestes



2014-11-26 17:26 GMT-02:00 Brian Cantoni <brian.cantoni@xxxxxxxxxxxx>:

I've been talking with Reynold from the Spark team (copied) about the possibility of updating to a newer version. In addition I really think we should restore that old build to keep existing builds working. 

Brian

On Nov 26, 2014, at 2:16 AM, Ian Craggs <icraggs@xxxxxxxxxxxxxxxxxxxxxxx> wrote:

Brian,

that approach sounds like exactly what we have now, and which I was hoping to avoid.  In addition to other factors, the 0.4 version was not an official release.

I'm trying to get a 1.0.1 service release out (while on vacation), so I'm having to get a crash course in Maven/Nexus.  Maybe I'll figure out a better or correct way to move people onto the later versions. 

Can't we get Apache Spark to update their dependency?

Ian

On 25/11/14 10:42, Brian Cantoni wrote:
Ian,

I agree on the issues around supporting those older versions.

In our case we are doing a build which relies on another project (Apache Spark) which is explicitly building with that older version of the mqtt-client (https://github.com/apache/spark/blob/master/external/mqtt/pom.xml#L44-L48). Removing the 0.4.0 artifacts means that builds expecting a specific version (even if older, not the latest, etc.) will break.

My suggestion would be to restore the older builds, then if/when users encounter or report bugs, have the first response be "first, upgrade to the latest".

Brian


On Mon, Nov 24, 2014 at 1:27 AM, Ian Craggs <icraggs@xxxxxxxxxxxxxxxxxxxxxxx> wrote:

Brian,

apologies, but we have kept getting questions and bug reports about the older versions of the Java client.  It seemed that the repo structure had led people to find the 0.4 version sometimes in preference to the 1.0 version or later.  I thought that deleting the 0.4 version would help minimize people encountering bugs which had already been fixed - which is a waste of everyone's time, user and developer.

If anyone has any other suggestions for how we should manage this, I would be happy to hear them.

Ian



On 21/11/14 20:04, Brian Cantoni wrote:
What happened to the 0.4.0 version? We are bringing this in as a dependency of another package we are using and need to get that exact version.

Brian


On Thu, Nov 20, 2014 at 6:07 PM, Bin BJ Zhang <zhbinbj@xxxxxxxxxx> wrote:

Please use a newer version:  https://repo.eclipse.org/content/repositories/paho-releases/org/eclipse/paho/org.eclipse.paho.client.mqttv3/1.0.1/

Best Regards,
Bin Zhang(张斌)
--------------------------------------------------------------------------------------------
WebSphere MQ, IBM China Software Development Lab
Notes:   Bin BJ Zhang/China/IBM
E-Mail:  zhbinbj@xxxxxxxxxx
Address: Ring Building 3F, ZhongGuanCun Software Park,
DongBeiWang West Road No.8, Haidian District, Beijing, 100193, China
-------------------------------------------------------------------------------------------

<mime-attachment.gif>Brian Cantoni ---11/21/2014 04:11:50 AM---We recently noticed a working build which started having a problem pulling in the .jar files for mqt


From: Brian Cantoni <brian.cantoni@xxxxxxxxxxxx>
To: paho-dev@xxxxxxxxxxx
Date: 11/21/2014 04:11 AM
Subject: [paho-dev] mqtt-client 0.4.0 appears to be missing from repo.eclipse.org
Sent by: paho-dev-bounces@xxxxxxxxxxx




We recently noticed a working build which started having a problem pulling in the .jar files for mqtt-client v0.4.0.

It looks like this repo dir is empty:
https://repo.eclipse.org/content/repositories/paho-releases/org/eclipse/paho/mqtt-client/0.4.0/

If I go up one level, it shows the 0.4.0 dir as last modified on Wed Nov 19 09:46:54 EST 2014.

Is it possible that the files were removed accidentally, or are we pointing to the wrong place?

thanks,
Brian Cantoni_______________________________________________
paho-dev mailing list
paho-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/paho-dev

_______________________________________________
paho-dev mailing list
paho-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/paho-dev



_______________________________________________
paho-dev mailing list
paho-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/paho-dev


_______________________________________________
paho-dev mailing list
paho-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/paho-dev



_______________________________________________
paho-dev mailing list
paho-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/paho-dev

_______________________________________________
paho-dev mailing list
paho-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/paho-dev

_______________________________________________
paho-dev mailing list
paho-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/paho-dev


Back to the top