Stop releasing as SNAPSHOT about dagger HOT 13 CLOSED

+1

from dagger.

+1

from dagger.

👎 Dagger 2 is not ready for non SNAPSHOT release, as we all can see because of issues like #108 mentioned by @mgrzechocinski which are breaking the API.

I agree, that Dagger team can release snapshot with versioning according to Semantic Versioning v2.0.0 , it will be great.

If you want stability from SNAPSHOT — download jars from mavenCentral and put them into your projects, don't let your build system to change things on the fly.

from dagger.

+1 Had an issue with the latest push to snapshot - still trying to boil it down into a simple example for an issue request...

from dagger.

No. If you don't want a snapshot version to break your code then don't depend on it. There's plenty of other safe, hermetic ways to get Dagger 2 into your app. This is a terrible request to make.

from dagger.

What are the "other safe and hermetic ways to get Dagger2 into your app"? Hope you won't ask us to keep Dagger2 jar within source code like in old 90ies...

I'm not against developing software under SNAPSHOT in overall. It's extremely useful in some situations, especially when working on multi-module apps. I also know, that depending on a SNAPSHOT might break my code, I'm aware of it.

I just think that Dagger2, as feature completed library is no longer a SNAPSHOT and should be released with fixed versions, so that real projects (=not simple examples) which can give you a real feedback won't break after ones push new version. Alpha, Beta, RC, there are plenty of classifiers to use until releasing as final v2.0.

from dagger.

Why do you think it's feature complete? Features are landing in every sync from Google's internal repo.

from dagger.

I pointed to Gregory's presentation when opening this request and also trying to be up to date with the latest commits.

from dagger.

I'll tell the next pull request to watch the presentation. Deploy a jar to your internal artifact repository or check it in temporarily. These types of issues is what makes people burn out on open source and should be closed with extreme prejudice.

from dagger.

I watched it and because I used Dagger1 a lot, I decided to switch to v2.

Frankly, what makes me personally burnt out on OS is trying to help by giving feedback from a real project and failing it under random&unclear circumstances just because you can't use 0.x, Alpha, Beta or any other versioning rule, saying "don't depend on it".

I'll check-in previous JAR version, feeling like in ANT times. EOT for me.

from dagger.

Who said "don't depend on it"? If you depend on a snapshot, you have explicitly opted in to breaking changes without notice. Stop blaming others and just fix your build.

from dagger.

@mgrzechocinski How about using timestamped snapshots [1] with a repository manager (to make sure it's not pruned from the repository; you set your own strategy rather than relying on the Sonatype OSS one)
Or you can “fork” and release/deploy non-snapshots you can rely on (or snapshots under your own coordinates; the idea being that you choose when you update).

[1] Maven has mvn versions:lock-snapshots, there might be equivalent plugins for Gradle (maybe nebula.dependency-lock would do it)

from dagger.

We will be releasing a stable 2.0 shortly.

from dagger.