sikuli-driver team mailing list archive

[Ethan <supercriticalfluid@xxxxxxxxx>]

I'm trying to pull in Sikulixapi for use in a Scala SBT project and I
keep getting failures to grab the dependencies.

I really don't know much at all about Maven or Ivy, and am still very
new at SBT. I'm guessing there must be some difference between how
SBT/Ivy is interacting with the profiles that's throwing things off.

I'll look into it.

In the mean time thanks for the prompt reply. Sikuli is quite
impressive. I got to toy around with it a few years ago using the
Clojure wrapper and I'm just trying to get to the point where I can use
the API again from Scala.

You're doing a great work. In some ways Sikuli has played a part in
getting me into my programming career, so thanks for that as well.

-- 
You received this bug notification because you are a member of Sikuli
Drivers, which is subscribed to Sikuli.
https://bugs.launchpad.net/bugs/1558322

Title:
  pom in sonatype repo seems to not have a place holder being replaced

Status in Sikuli:
  Opinion

Bug description:
  While trying to pull in dependencies for the sikulixapi (in both 1.1.0
  and 1.1.1 as well as in the snapshots) I run into what seems to be the
  same problem across the board. It seems to be related to an issue that
  appears to be in the pom.

  Here's an example from the sonatype repo.

  In the pom file located here

  https://oss.sonatype.org/content/groups/public/com/sikulix/sikulixapi/1.1.0/sikulixapi-1.1.0.pom

  There seem to be some place holder variables that are not being
  resolved when the pom is produced. for example ->

    <dependency>
      <groupId>com.sikulix</groupId>
      <artifactId>${sikulix.libs}</artifactId>
      <version>${project.version}</version>
    </dependency>
  </dependencies>
  <properties>
    <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding></properties>
  <distributionManagement>
    <repository>
      <id>sikulix.deploy</id>
      <url>${sikulix.deploy.target}</url>
    </repository>
  </distributionManagement>

  This isn't the only pom with this problem and it seems to be for these
  same places (the ${sikulix.libs} is what pops up as an error with
  whatever I try to pull down from maven, regardless if I try with
  snapshots or with 1.1.0 or with 1.1.1 or whatever).

To manage notifications about this bug go to:
https://bugs.launchpad.net/sikuli/+bug/1558322/+subscriptions