jcabi / jcabi-mysql-maven-plugin

MySQL Maven Plugin: starts MySQL server on pre-integration phase and shuts it down on post-integration phase

Home Page:https://mysql.jcabi.com

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

mysql-dist classifier is wrong for 32-bit Linux

peterjanes opened this issue · comments

os.arch is i386 in Java on 32-bit Linux platforms, so jcabi-mysql-maven-plugin:classify sets ${mysql.classifier} to i386. com.jcabi:mysql-dist versions are deployed with a classifier of linux-x86, which means that artifact downloads using the variable fail.

(The workaround of setting mysql.classifier directly in a Linux/i386-specific profile causes jcabi-mysql-maven-plugin:classify to fail; that makes it necessary for each target platform to have its own profile and the :classify execution to be removed from the POM.)

oops, thanks for reporting. I'll make a fix soon

@rultor release, tag is 0.8.2

@rultor release, tag is 0.8.2

@yegor256 OK, I will release it now. Please check the progress here

@rultor release, tag is 0.8.2

@yegor256 Oops, I failed. You can see the full log here (spent 3min)

@rultor release, tag is 0.8.2

@rultor release, tag is 0.8.2

@yegor256 OK, I will release it now. Please check the progress here

@rultor release, tag is 0.8.2

@yegor256 Oops, I failed. You can see the full log here (spent 6min)

Hello jcabi team :)

We are hit by this issue as well. Is there any known w/a for the time before this is resolved?

@sarxos this issue slipped through my fingers. I'll try to resolve it this weekend and release a new fixed version on Sunday.

Hi @yegor256,

There is no rush. I managed to w/a this problem by deploying mysql-dist with modified classifier into my private repository.

<repository>
  <id>sarxos-repo</id>
  <url>http://repo.sarxos.pl/maven2</url>
</repository>

This w/a is for version 5.6.14 only.

<dependency>
  <groupId>com.jcabi</groupId>
  <artifactId>mysql-dist</artifactId>
  <version>5.6.14</version>
</dependency>

Anyone who would like to use my repo to w/a this problem can feel free and do that, but please note that I will most likely remove it while the nearest cleanup after the issue is fixed by the @jcabi team.

@rultor release, tag is 0.8.2

@rultor release, tag is 0.8.2

@yegor256 OK, I will release it now. Please check the progress here

@rultor release, tag is 0.8.2

@yegor256 Done! FYI, the full log is here (took me 30min)

@peterjanes please check version 0.8.2 (in Maven Central), it should fix the issue. If it works fine, please close the issue

Looks good to me.