{"id":32476,"date":"2019-10-31T21:47:17","date_gmt":"2019-10-31T18:47:17","guid":{"rendered":"https:\/\/prohoster.info\/blog\/opyt-ispolzovaniya-flatten-maven-plugin-dlya-uproshheniya-versionirovaniya-v-maven-proektah\/"},"modified":"2019-10-31T21:47:17","modified_gmt":"2019-10-31T18:47:17","slug":"opyt-ispolzovaniya-flatten-maven-plugin-dlya-uproshheniya-versionirovaniya-v-maven-proektah","status":"publish","type":"post","link":"https:\/\/prohoster.info\/pt\/blog\/administrirovanie\/opyt-ispolzovaniya-flatten-maven-plugin-dlya-uproshheniya-versionirovaniya-v-maven-proektah","title":{"rendered":"Experi\u00eancia com flatten-maven-plugin para simplificar versionamento em projetos maven","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Sobre n\u00f3s<\/h4>\n

\nNa 1C, desenvolvemos n\u00e3o apenas a plataforma 1C: Enterprise<\/a><\/noindex> para C++<\/a><\/noindex> e JavaScript<\/a><\/noindex>, mas tamb\u00e9m aplicativos em Java \u2013 em particular, um novo ambiente de desenvolvimento Ferramentas de Desenvolvimento Empresarial<\/a><\/noindex> baseado no Eclipse e um servidor profundamente integrado com a plataforma de mensageiro \u2013 Sistemas de Intera\u00e7\u00e3o<\/a><\/noindex>.<\/p>\n

Introdu\u00e7\u00e3o<\/h4>\n

\nComo sistema de constru\u00e7\u00e3o de aplicativos Java, costumamos usar o maven, e neste pequeno artigo gostar\u00edamos de falar sobre um dos problemas que encontramos durante a organiza\u00e7\u00e3o do desenvolvimento e a abordagem que nos permitiu super\u00e1-lo.
\n<\/a><\/noindex><\/p>\n

Pressupostos e Fluxo de Trabalho<\/h4>\n

\nDevido \u00e0 especificidade do desenvolvimento em nossos projetos maven, usamos um n\u00famero consider\u00e1vel de m\u00f3dulos, depend\u00eancias e projetos filhos. O n\u00famero de arquivos pom em uma \u00e1rvore pode somar dezenas e at\u00e9 centenas.<\/p>\n

\"Experi\u00eancia
\n
\n\u00c0 primeira vista: n\u00e3o h\u00e1 nada de aterrador, criamos uma vez e esquecemos. Se precisar mudar ou adicionar algo em todos os arquivos de uma vez, existem muitas ferramentas convenientes em editores e IDEs. E qual \u00e9 a altera\u00e7\u00e3o mais comum do pom.xml? Acreditamos que seja a mudan\u00e7a das vers\u00f5es dos projetos e das depend\u00eancias. Talvez algu\u00e9m queira discutir isso, mas \u00e9 assim que as coisas est\u00e3o para n\u00f3s. A raz\u00e3o est\u00e1 no fato de que, junto com o n\u00facleo, desenvolvemos paralelamente muitas bibliotecas pr\u00f3prias, e para garantir a reprodutibilidade cont\u00ednua dos resultados de constru\u00e7\u00e3o e teste, o uso de snapshots n\u00e3o \u00e9 um m\u00e9todo conveniente para n\u00f3s. Por essa raz\u00e3o, somos obrigados a aumentar o n\u00famero da vers\u00e3o nos projetos a cada constru\u00e7\u00e3o.<\/p>\n

Al\u00e9m disso, o desenvolvedor de vez em quando precisa compilar seu ramo de alguma biblioteca e testar sua funcionalidade em todas as depend\u00eancias, para isso \u00e9 necess\u00e1rio mudar manualmente a vers\u00e3o em todas elas.<\/p>\n

Solu\u00e7\u00e3o Inicial<\/h4>\n

\nCom tantas mudan\u00e7as frequentes e m\u00faltiplas nas vers\u00f5es, o processo dentro do CI gostaria de simplificar e automatizar. Aqui entra em cena um plugin conhecido e conveniente versions-maven-plugin<\/i> \u2013 o conectamos e executamos <\/p>\n

mvn -N versions:set -DnewVersion=2.0.1 <\/i><\/p>\n

e o maven far\u00e1 tudo certinho: percorrer\u00e1 a hierarquia de cima para baixo, mudar\u00e1 todas as vers\u00f5es \u2013 lindo! Agora s\u00f3 falta levantar um pull request, os colegas revisar\u00e3o as mudan\u00e7as, e podemos rapidamente nos integrar ao trunk. Rapidamente? Como se n\u00e3o fosse assim. Um par ou tr\u00eas centenas pom.xml<\/i> em revis\u00e3o, e isso sem contar o c\u00f3digo. Al\u00e9m disso, ningu\u00e9m est\u00e1 imune a conflitos de merge com um n\u00famero t\u00e3o grande de arquivos alterados. \u00c9 importante notar que, durante o CI, as mudan\u00e7as de vers\u00e3o ocorrem automaticamente junto com a altera\u00e7\u00e3o da funcionalidade, e n\u00e3o de forma separada.<\/p>\n

Novas funcionalidades<\/h4>\n

\nPor um tempo, nos acalmamos e, resignados, vivemos assim, at\u00e9 que os caras do Maven Apache Project<\/a><\/noindex> inclu\u00edram no maven, a partir da vers\u00e3o 3.5.0-beta-1, o suporte para os chamados 'substitutos' de vers\u00f5es (placeholders). A ess\u00eancia desses substitutos \u00e9 que em pom.xml<\/i> vez de uma indica\u00e7\u00e3o espec\u00edfica da vers\u00e3o do projeto, s\u00e3o utilizadas vari\u00e1veis ${revision}<\/i>, ${sha1}<\/i> e ${changelist}<\/i>. Os pr\u00f3prios valores dessas propriedades s\u00e3o definidos either no elemento <properties<\/i>>, ou podem ser definidos atrav\u00e9s da propriedade do sistema<\/p>\n

mvn -Drevision=2.0.0 clean package<\/i><\/p>\n

Os valores das propriedades do sistema t\u00eam prioridade sobre os valores definidos em <properties<\/i>>.<\/p>\n

Pai<\/b>
\n<project>
\n\u00a0\u00a0<modelVersion>4.0.0<\\\/modelVersion>
\n\u00a0\u00a0<parent>
\n\u00a0\u00a0\u00a0\u00a0<groupId>org.apache<\\\/groupId>
\n\u00a0\u00a0\u00a0\u00a0<artifactId>apache<\\\/artifactId>
\n\u00a0\u00a0\u00a0\u00a0<version>18<\\\/version>
\n\u00a0\u00a0<\\\/parent>
\n\u00a0\u00a0<groupId>org.apache.maven.ci<\\\/groupId>
\n\u00a0\u00a0<artifactId>ci-parent<\\\/artifactId>
\n\u00a0\u00a0<name>First\u00a0CI\u00a0Friendly<\\\/name>
\n\u00a0\u00a0<version>${revision}${sha1}${changelist}<\/b><\\\/version>
\n\u00a0\u00a0\u2026
\n\u00a0\u00a0<properties>
\n\u00a0\u00a0\u00a0\u00a0<revision><\/b>1.3.1<\\\/revision><\/b>
\n\u00a0\u00a0\u00a0\u00a0<changelist><\/b>-SNAPSHOT<\\\/changelist><\/b>
\n\u00a0\u00a0\u00a0\u00a0<sha1\\\/><\/b>
\n\u00a0\u00a0<\\\/properties>
\n<\\\/project>
\n<\/i>
\nFilho<\/b>
\n<project>
\n\u00a0\u00a0<modelVersion>4.0.0<\\\/modelVersion>
\n\u00a0\u00a0<parent>
\n\u00a0\u00a0\u00a0\u00a0<groupId>org.apache.maven.ci<\\\/groupId>
\n\u00a0\u00a0\u00a0\u00a0<artifactId>ci-parent<\\\/artifactId>
\n\u00a0\u00a0\u00a0\u00a0<version>${revision}${sha1}${changelist}<\/b><\\\/version>
\n\u00a0\u00a0<\\\/parent>
\n\u00a0\u00a0<groupId>org.apache.maven.ci<\\\/groupId>
\n\u00a0\u00a0<artifactId>ci-child<\\\/artifactId>
\n\u00a0\u00a0\u00a0\u2026
\n<\\\/project>
\n<\/i><\/p>\n

Se quisermos compilar a vers\u00e3o 2.0.0-SNAPSHOT, basta usarmos <\/p>\n

\u00a0\u00a0\u00a0\u00a0mvn -Drevision=2.0.0 clean package<\/i><\/p>\n

Se quisermos fazer um release, simplesmente zeramos o SNAPSHOT <\/p>\n

\u00a0\u00a0\u00a0\u00a0mvn -Dchangelist= clean package<\/i><\/p>\n

*Os exemplos acima s\u00e3o retirados de artigo<\/a><\/noindex> no site do Maven Apache Project<\/p>\n

A dura realidade<\/h4>\n

\nTudo est\u00e1 bem e maravilha, \u00e9 hora de experimentar a satisfa\u00e7\u00e3o, mas n\u00e3o. Aparentemente, para install e deploy, esse m\u00e9todo n\u00e3o funcionar\u00e1, pois nas descri\u00e7\u00f5es dos artefatos publicados no reposit\u00f3rio n\u00e3o ser\u00e1 feita a substitui\u00e7\u00e3o ${revision}<\/i> pelo seu valor e o maven n\u00e3o entender\u00e1 do que se trata.<\/p>\n

<parent>
\n\u00a0\u00a0\u00a0\u00a0<groupId>org.apache<\\\/groupId>
\n\u00a0\u00a0\u00a0\u00a0<artifactId>apache<\\\/artifactId>
\n\u00a0\u00a0\u00a0\u00a0<version>${revision}<\\\/version>
\n<\\\/parent>
\n<\/i><\/p>\n

Luz no fim do t\u00fanel<\/h4>\n

\n\u00c9 preciso procurar uma solu\u00e7\u00e3o para o problema. A situa\u00e7\u00e3o poderia ser salva por flatten-maven-plugin<\/a><\/noindex>Este plugin permite todas as vari\u00e1veis no pom, mas ao mesmo tempo corta uma tonelada de outras informa\u00e7\u00f5es que s\u00f3 s\u00e3o necess\u00e1rias durante a constru\u00e7\u00e3o e n\u00e3o s\u00e3o necess\u00e1rias ao importar artefatos publicados em outros projetos. Al\u00e9m disso, o plugin \"niveliza\" todas as depend\u00eancias parent-child, resultando em poms planos, que incluem tudo o que \u00e9 necess\u00e1rio. O problema era que ele cortava \"demais\", o que n\u00e3o nos agradava. Depois de estudar informa\u00e7\u00f5es sobre o desenvolvimento deste plugin, descobrimos que n\u00e3o \u00e9ramos os \u00fanicos no universo e que j\u00e1 em agosto de 2018, no GitHub, um pull-request foi criado no reposit\u00f3rio do plugin com o desejo de permitir a defini\u00e7\u00e3o de como \"mudar\" o pom.xml. Os desenvolvedores ouviram as vozes dos clamantes, e j\u00e1 em dezembro, com o lan\u00e7amento da nova vers\u00e3o 1.1.0, surgiu um novo modo resolveCiFriendliesOnly no flatten-maven-plugin, que veio a calhar \u2013 ele mant\u00e9m o pom.xml como est\u00e1, exceto pelo elemento <version><\/i> e permite ${revision}<\/i>, ${sha1}<\/i> e ${changelist}<\/i>.<\/p>\n

Adicionar o plugin ao projeto<\/p>\n

<plugins>
\n\u00a0\u00a0<plugin>
\n\u00a0\u00a0\u00a0\u00a0<groupId>org.codehaus.mojo<\/groupId>
\n\u00a0\u00a0\u00a0\u00a0<artifactId>flatten-maven-plugin<\/artifactId>
\n\u00a0\u00a0\u00a0\u00a0<version>1.1.0<\/version>
\n\u00a0\u00a0\u00a0\u00a0<configuration>
\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<updatePomFile>true<\/updatePomFile>
\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<flattenMode>resolveCiFriendliesOnly<\/b><\/flattenMode>
\n\u00a0\u00a0\u00a0\u00a0<\/configuration>
\n\u00a0\u00a0\u00a0\u00a0<executions>
\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<execution>
\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<id>flatten<\/id>
\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<phase>process-resources<\/phase>
\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<goals>
\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<goal>flatten<\/goal>
\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/goals>
\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/execution>
\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<execution>
\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<id>flatten.clean<\/id>
\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<phase>clean<\/phase>
\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<goals>
\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<goal>clean<\/goal>
\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/goals>
\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/execution>
\n\u00a0\u00a0\u00a0\u00a0<\/executions>
\n\u00a0\u00a0<\/plugin>
\n<\/plugins>
\n<\/i><\/p>\n

Pronto!<\/p>\n

Final feliz<\/h4>\n

\nA partir de agora, para mudar a vers\u00e3o de todo o projeto e informar todas as depend\u00eancias, precisamos apenas editar o elemento <revision<\/i>> em apenas um \u00fanico raiz pom.xml<\/i>. Desta forma, ao revisar, n\u00e3o recebemos centenas desses arquivos com a mesma altera\u00e7\u00e3o, mas um s\u00f3. E a necessidade de usar versions-maven-plugin<\/i>.
\n
Fonte: habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"

\u041e \u043d\u0430\u0441 \u0412 1\u0421 \u043c\u044b \u0440\u0430\u0437\u0440\u0430\u0431\u0430\u0442\u044b\u0432\u0430\u0435\u043c \u043d\u0435 \u0442\u043e\u043b\u044c\u043a\u043e \u043f\u043b\u0430\u0442\u0444\u043e\u0440\u043c\u0443 1\u0421: \u041f\u0440\u0435\u0434\u043f\u0440\u0438\u044f\u0442\u0438\u0435 \u043d\u0430 \u0421++ \u0438 JavaScript, \u043d\u043e \u0438 \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u044f \u043d\u0430 Java \u2013 \u0432 \u0447\u0430\u0441\u0442\u043d\u043e\u0441\u0442\u0438 \u043d\u043e\u0432\u0443\u044e \u0441\u0440\u0435\u0434\u0443 \u0440\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u043a\u0438 Enterprise Development Tools \u043d\u0430 \u0431\u0430\u0437\u0435 Eclipse \u0438 \u0441\u0435\u0440\u0432\u0435\u0440 \u0433\u043b\u0443\u0431\u043e\u043a\u043e \u0438\u043d\u0442\u0435\u0433\u0440\u0438\u0440\u043e\u0432\u0430\u043d\u043d\u043e\u0433\u043e \u0441 \u043f\u043b\u0430\u0442\u0444\u043e\u0440\u043c\u043e\u0439 \u043c\u0435\u0441\u0441\u0435\u043d\u0434\u0436\u0435\u0440\u0430 \u2013 \u0421\u0438\u0441\u0442\u0435\u043c\u044b \u0412\u0437\u0430\u0438\u043c\u043e\u0434\u0435\u0439\u0441\u0442\u0432\u0438\u044f. \u0412\u0441\u0442\u0443\u043f\u043b\u0435\u043d\u0438\u0435 \u0412 \u043a\u0430\u0447\u0435\u0441\u0442\u0432\u0435 \u0441\u0438\u0441\u0442\u0435\u043c\u044b \u0441\u0431\u043e\u0440\u043a\u0438 Java-\u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u0439 \u0447\u0430\u0449\u0435 \u0432\u0441\u0435\u0433\u043e \u043c\u044b \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u0443\u0435\u043c maven, \u0438 \u0432 […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":24280,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-32476","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\n","aioseo_head_json":{"title":"\ud83e\udd47Experi\u00eancia no uso do flatten-maven-plugin para simplificar o versionamento em projetos maven | ProHoster","description":"Sobre n\u00f3s Na 1C, n\u00e3o desenvolvemos apenas a plataforma 1C: Enterprise em","canonical_url":"https:\/\/prohoster.info\/pt\/blog\/administrirovanie\/opyt-ispolzovaniya-flatten-maven-plugin-dlya-uproshheniya-versionirovaniya-v-maven-proektah","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"pt_PT","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47\u041e\u043f\u044b\u0442 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u043d\u0438\u044f flatten-maven-plugin \u0434\u043b\u044f \u0443\u043f\u0440\u043e\u0449\u0435\u043d\u0438\u044f \u0432\u0435\u0440\u0441\u0438\u043e\u043d\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u044f \u0432 maven-\u043f\u0440\u043e\u0435\u043a\u0442\u0430\u0445 | ProHoster","og:description":"\u041e \u043d\u0430\u0441 \u0412 1\u0421 \u043c\u044b \u0440\u0430\u0437\u0440\u0430\u0431\u0430\u0442\u044b\u0432\u0430\u0435\u043c \u043d\u0435 \u0442\u043e\u043b\u044c\u043a\u043e \u043f\u043b\u0430\u0442\u0444\u043e\u0440\u043c\u0443 1\u0421: \u041f\u0440\u0435\u0434\u043f\u0440\u0438\u044f\u0442\u0438\u0435 \u043d\u0430","og:url":"https:\/\/prohoster.info\/pt\/blog\/administrirovanie\/opyt-ispolzovaniya-flatten-maven-plugin-dlya-uproshheniya-versionirovaniya-v-maven-proektah","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2019-10-31T18:47:17+00:00","article:modified_time":"2019-10-31T18:47:17+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"32476","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":"2026-01-21 11:03:20","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 02:58:23","updated":"2026-01-21 11:03:20","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/posts\/32476","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/comments?post=32476"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/posts\/32476\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/media\/24280"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/media?parent=32476"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/categories?post=32476"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/tags?post=32476"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}