Skip to content

Instantly share code, notes, and snippets.

@magnuspalmer
Created December 16, 2015 16:29
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save magnuspalmer/1f257cb011a4d5728a66 to your computer and use it in GitHub Desktop.
Save magnuspalmer/1f257cb011a4d5728a66 to your computer and use it in GitHub Desktop.
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<parent>
<groupId>org.mule.tools.devkit</groupId>
<artifactId>mule-devkit-parent</artifactId>
<version>3.7.2</version>
</parent>
<modelVersion>4.0.0</modelVersion>
<groupId>org.mule.modules</groupId>
<artifactId>mule-module-hue</artifactId>
<version>1.0-SNAPSHOT</version>
<packaging>mule-module</packaging>
<name>Philips Hue Connector</name>
<description>Connects to the Philips Hue smart lighting system. This connector
does not cover the full API rather the more common things that a developer
would automate from Mule.</description>
<profiles>
<profile>
<!-- Integration tests profile
Basically don't run these unless you have access to a Hue light bridge
-->
<id>it</id>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-failsafe-plugin</artifactId>
<version>2.14.1</version>
<executions>
<execution>
<goals>
<goal>integration-test</goal>
<goal>verify</goal>
</goals>
</execution>
</executions>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-enforcer-plugin</artifactId>
<version>1.3</version>
<executions>
<execution>
<id>enforce-files-exist</id>
<goals>
<goal>enforce</goal>
</goals>
<configuration>
<rules>
<requireFilesExist>
<!-- this is picked up by the integration tests grab API keys and other private information -->
<files>
<file>${user.home}/.mule-test.properties</file>
</files>
<message>Set up a .mule-test.properties in your home directory where you can
store API keys used from running tests for this module</message>
</requireFilesExist>
</rules>
<fail>true</fail>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
</profile>
</profiles>
<dependencies>
<!-- Rest API client -->
<dependency>
<groupId>com.sun.jersey</groupId>
<artifactId>jersey-client</artifactId>
<version>1.12</version>
</dependency>
<dependency>
<groupId>org.mule.modules</groupId>
<artifactId>mule-module-json</artifactId>
<version>${mule.version}</version>
</dependency>
</dependencies>
<repositories>
<repository>
<releases>
<enabled>true</enabled>
</releases>
<snapshots>
<enabled>false</enabled>
</snapshots>
<id>mule-public</id>
<name>Mule public releases</name>
<url>https://repository.mulesoft.org/nexus/content/repositories/releases</url>
<layout>default</layout>
</repository>
</repositories>
</project>
@magnuspalmer
Copy link
Author

Ross probably have a settings.xml pointing out the mule repository that is why it doesn't work out of the box when cloning and building.
Updated to dev-kit 3.7.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment