В рейтинге участвует:

групп:

каналов:

Виртуальный сервер на SSD - недорого!

Аренда выделенных и виртуальных серверов (VDS/VPS), хостинг, аренда IP-адресов, администрирование, круглосуточная поддержка

qwarta.ru подробнее

Резервное копирование с проверкой на вирусы!!!

Удобный сервис создания резервных копий на любой сервер сети интернет. Отслеживайте изменения, проверяйте на вирусы. Надежно защитите свой бизнес!

go.backupland.com

Выбираете сервер? Любая конфигурация на заказ!

Аренда физических серверов любых конфигураций под любые запросы - 1С бухгалтерия, игровые сервера, нагруженные проекты, интернет-магазины!

qwarta.ru подробнее

Size: a a a

Чат подкаста «Разбор Полётов»

909 membersпожаловаться на группу
2020 June 09

D

Dima in Чат подкаста «Разбор Полётов»
Alexey Abashev
сколько народу герпесом заражается?
просто выглядело так, что сняли спецом перед поправками
источник
23:01пожаловаться#1

AA

Anton Arhipov in Чат подкаста «Разбор Полётов»
Было? https://spring.io/blog/2020/06/08/migrating-spring-boot-s-build-to-gradle
spring.io
Migrating Spring Boot's Build to Gradle
We made a fairly significant change to Spring Boot in 2.3.0.M1. It was the first release of the project to be built with Gradle rather than Maven. A <a href="https://twitter.com/phillip_webb/status/1222943872205983744">thread on Twitter about the migration had a number of people asking why we switched and the benefits, if any, that we’d seen. This blog post aims to answer those questions.
Each project in the Spring portfolio is run in a fairly autonomous manner. We strive for consistency where our users will see it most – API design, for example – but choose the tools that best meet the needs of the project for things that are less visible. One example of this is the build system. A change to the build system affects those that contribute to the project but, if we get things right, it has no effect on users. This has led to a mixture of Maven- and Gradle-based builds. For example, Spring Framework has been built with Gradle since 3.2.0.M1 in 2012, whereas Spring Boot began a year later and Spring Cloud shortly…
источник
23:52пожаловаться#2

AA

Anton Arhipov in Чат подкаста «Разбор Полётов»
Чтоб чатик совсем в говно политоты не скатился, приходится сюда приносить годноту самому
источник
23:52пожаловаться#3

D

Dima in Чат подкаста «Разбор Полётов»
Anton Arhipov
Было? https://spring.io/blog/2020/06/08/migrating-spring-boot-s-build-to-gradle
spring.io
Migrating Spring Boot's Build to Gradle
We made a fairly significant change to Spring Boot in 2.3.0.M1. It was the first release of the project to be built with Gradle rather than Maven. A <a href="https://twitter.com/phillip_webb/status/1222943872205983744">thread on Twitter about the migration had a number of people asking why we switched and the benefits, if any, that we’d seen. This blog post aims to answer those questions.
Each project in the Spring portfolio is run in a fairly autonomous manner. We strive for consistency where our users will see it most – API design, for example – but choose the tools that best meet the needs of the project for things that are less visible. One example of this is the build system. A change to the build system affects those that contribute to the project but, if we get things right, it has no effect on users. This has led to a mixture of Maven- and Gradle-based builds. For example, Spring Framework has been built with Gradle since 3.2.0.M1 in 2012, whereas Spring Boot began a year later and Spring Cloud shortly…
что-то новенькое
источник
23:54пожаловаться#4

J🎩

JBáruch 🎩 in Чат подкаста «Разбор Полётов»
Anton Arhipov
Было? https://spring.io/blog/2020/06/08/migrating-spring-boot-s-build-to-gradle
spring.io
Migrating Spring Boot's Build to Gradle
We made a fairly significant change to Spring Boot in 2.3.0.M1. It was the first release of the project to be built with Gradle rather than Maven. A <a href="https://twitter.com/phillip_webb/status/1222943872205983744">thread on Twitter about the migration had a number of people asking why we switched and the benefits, if any, that we’d seen. This blog post aims to answer those questions.
Each project in the Spring portfolio is run in a fairly autonomous manner. We strive for consistency where our users will see it most – API design, for example – but choose the tools that best meet the needs of the project for things that are less visible. One example of this is the build system. A change to the build system affects those that contribute to the project but, if we get things right, it has no effect on users. This has led to a mixture of Maven- and Gradle-based builds. For example, Spring Framework has been built with Gradle since 3.2.0.M1 in 2012, whereas Spring Boot began a year later and Spring Cloud shortly…
эт очень смешно. Если поискать, можно найти анонс первого Спринг Бута на SpringOne2GS и услышать как Dave Syer говорит “только Мавен, никакого Грейдла, через мой труп”.
источник
23:57пожаловаться#5

D

Dima in Чат подкаста «Разбор Полётов»
грэдл намного лаконичнее для спринг бута
источник
23:58пожаловаться#6
2020 June 10

D

Dima in Чат подкаста «Разбор Полётов»
Anton Arhipov
Было? https://spring.io/blog/2020/06/08/migrating-spring-boot-s-build-to-gradle
spring.io
Migrating Spring Boot's Build to Gradle
We made a fairly significant change to Spring Boot in 2.3.0.M1. It was the first release of the project to be built with Gradle rather than Maven. A <a href="https://twitter.com/phillip_webb/status/1222943872205983744">thread on Twitter about the migration had a number of people asking why we switched and the benefits, if any, that we’d seen. This blog post aims to answer those questions.
Each project in the Spring portfolio is run in a fairly autonomous manner. We strive for consistency where our users will see it most – API design, for example – but choose the tools that best meet the needs of the project for things that are less visible. One example of this is the build system. A change to the build system affects those that contribute to the project but, if we get things right, it has no effect on users. This has led to a mixture of Maven- and Gradle-based builds. For example, Spring Framework has been built with Gradle since 3.2.0.M1 in 2012, whereas Spring Boot began a year later and Spring Cloud shortly…
но от поддержки самого мэйвена в фрэймворке они наверно еще много лет не откажутся
источник
00:00пожаловаться#7

AA

Anton Arhipov in Чат подкаста «Разбор Полётов»
Dima
но от поддержки самого мэйвена в фрэймворке они наверно еще много лет не откажутся
Всмысле, бом-ы?
источник
00:00пожаловаться#8

AA

Anton Arhipov in Чат подкаста «Разбор Полётов»
Конечно не откажутся. Это хлеб
источник
00:00пожаловаться#9

D

Dima in Чат подкаста «Разбор Полётов»
Anton Arhipov
Всмысле, бом-ы?
бомы, мэйвен-плагины специфичные и тд и тп
источник
00:00пожаловаться#10

D

Dima in Чат подкаста «Разбор Полётов»
но пример хороший и аргумент сильный
источник
00:01пожаловаться#11

J🎩

JBáruch 🎩 in Чат подкаста «Разбор Полётов»
ну понятно, что не откажутся, поддержка и грейдла была с первого дня
источник
00:05пожаловаться#12

J🎩

JBáruch 🎩 in Чат подкаста «Разбор Полётов»
мы про билд говорим
источник
00:05пожаловаться#13

OG

Old Grog in Чат подкаста «Разбор Полётов»
Dima
было 1500 сутки
И неплохо было бы учитывать количество проводимых тестов
источник
00:14пожаловаться#14

NK

ID:0 in Чат подкаста «Разбор Полётов»
Переслано от Anton Arhipov
Было? https://spring.io/blog/2020/06/08/migrating-spring-boot-s-build-to-gradle
spring.io
Migrating Spring Boot's Build to Gradle
We made a fairly significant change to Spring Boot in 2.3.0.M1. It was the first release of the project to be built with Gradle rather than Maven. A <a href="https://twitter.com/phillip_webb/status/1222943872205983744">thread on Twitter about the migration had a number of people asking why we switched and the benefits, if any, that we’d seen. This blog post aims to answer those questions.
Each project in the Spring portfolio is run in a fairly autonomous manner. We strive for consistency where our users will see it most – API design, for example – but choose the tools that best meet the needs of the project for things that are less visible. One example of this is the build system. A change to the build system affects those that contribute to the project but, if we get things right, it has no effect on users. This has led to a mixture of Maven- and Gradle-based builds. For example, Spring Framework has been built with Gradle since 3.2.0.M1 in 2012, whereas Spring Boot began a year later and Spring Cloud shortly…
источник
00:27пожаловаться#15

LI

Leonid Igolnik in Чат подкаста «Разбор Полётов»
Фарит Фаттахов
Неожиданно было, сам оттуда:)
Ха !!! Я правда оттуда уехал В 1984-м году но мы родственники попозже. Дядя когда-то заведовал ферасплавным заводом
источник
00:30пожаловаться#16

OK

Oleg Kovalov in Чат подкаста «Разбор Полётов»
https://twitter.com/AmandiOnAir/status/1270361553968205827
Twitter
Fernand R. Amandi
A tale of two Presidential intern pics.
источник
00:52пожаловаться#17

J🎩

JBáruch 🎩 in Чат подкаста «Разбор Полётов»
Oleg Kovalov
https://twitter.com/AmandiOnAir/status/1270361553968205827
Twitter
Fernand R. Amandi
A tale of two Presidential intern pics.
тут есть тема расы самого Президента. Вопрос, была ли, у Клинтона например, картинка отличная от Трампа
источник
00:59пожаловаться#18

DP

Denis Pavlyuchenko in Чат подкаста «Разбор Полётов»
Anton Arhipov
Было? https://spring.io/blog/2020/06/08/migrating-spring-boot-s-build-to-gradle
spring.io
Migrating Spring Boot's Build to Gradle
We made a fairly significant change to Spring Boot in 2.3.0.M1. It was the first release of the project to be built with Gradle rather than Maven. A <a href="https://twitter.com/phillip_webb/status/1222943872205983744">thread on Twitter about the migration had a number of people asking why we switched and the benefits, if any, that we’d seen. This blog post aims to answer those questions.
Each project in the Spring portfolio is run in a fairly autonomous manner. We strive for consistency where our users will see it most – API design, for example – but choose the tools that best meet the needs of the project for things that are less visible. One example of this is the build system. A change to the build system affects those that contribute to the project but, if we get things right, it has no effect on users. This has led to a mixture of Maven- and Gradle-based builds. For example, Spring Framework has been built with Gradle since 3.2.0.M1 in 2012, whereas Spring Boot began a year later and Spring Cloud shortly…
кроме статьи, еще коммент от Andy интересен- "Our team uses a mixture of Eclipse and IntelliJ IDEA", вот чего лично я точно не ожидал)
источник
01:20пожаловаться#19

AA

Anton Arhipov in Чат подкаста «Разбор Полётов»
Denis Pavlyuchenko
кроме статьи, еще коммент от Andy интересен- "Our team uses a mixture of Eclipse and IntelliJ IDEA", вот чего лично я точно не ожидал)
ты думал что STS используют?
источник
01:27пожаловаться#20