This repository has been archived by the owner on Jan 19, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2
/
pom.xml
157 lines (151 loc) · 6.77 KB
/
pom.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
<?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">
<modelVersion>4.0.0</modelVersion>
<!-- test org ID -->
<groupId>26d53683-6746-4040-ad07-f671f8e2b27e</groupId>
<artifactId>apikit-badrequest-extractor</artifactId>
<version>1.0.0</version>
<packaging>mule-module</packaging>
<name>Mule APIKit BadRequest Extractor</name>
<parent>
<groupId>org.mule.tools.devkit</groupId>
<artifactId>mule-devkit-parent</artifactId>
<version>3.9.0</version>
</parent>
<distributionManagement>
<repository>
<id>mule-exchange</id>
<name>Mule Exchange Repository</name>
<url>https://maven.anypoint.mulesoft.com/api/v1/organizations/${project.groupId}/maven</url>
<layout>default</layout>
</repository>
</distributionManagement>
<build>
<plugins>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>xml-maven-plugin</artifactId>
<version>1.0.1</version>
<executions>
<!-- Want a default operation for this -->
<execution>
<id>fix-editors-xml</id>
<phase>compile</phase>
<goals>
<goal>transform</goal>
</goals>
<configuration>
<!-- If we don't force this, it doesn't work properly in the package phase
even though it works fine in the compile phase -->
<forceCreation>true</forceCreation>
<transformationSets>
<transformationSet>
<dir>${project.build.directory}/generated-sources/mule/apikit-badrequest-extractor</dir>
<includes>editors.xml</includes>
<stylesheet>${basedir}/fixes/editors.xsl</stylesheet>
<outputDir>${project.build.directory}/classes/apikit-badrequest-extractor</outputDir>
</transformationSet>
</transformationSets>
</configuration>
</execution>
</executions>
</plugin>
<plugin>
<artifactId>maven-compiler-plugin</artifactId>
<version>3.1</version>
<configuration>
<compilerId>groovy-eclipse-compiler</compilerId>
</configuration>
<dependencies>
<dependency>
<groupId>org.codehaus.groovy</groupId>
<artifactId>groovy-eclipse-compiler</artifactId>
<version>2.9.2-01</version>
</dependency>
<dependency>
<groupId>org.codehaus.groovy</groupId>
<artifactId>groovy-eclipse-batch</artifactId>
<version>2.4.3-01</version>
</dependency>
</dependencies>
<executions>
<!-- Mule devkit Maven plugin does code generation in the default-generate-sources phase
and will try and compile our connector+config class. it doesn't know Groovy so we force
compilation of Groovy early on -->
<execution>
<id>groovy-classes</id>
<goals>
<goal>compile</goal>
</goals>
<phase>generate-sources</phase>
<configuration>
<source>1.8</source>
<target>1.8</target>
<includes>
<include>**/*.groovy</include>
</includes>
</configuration>
</execution>
</executions>
</plugin>
<plugin>
<!-- AnyPoint connector devkit uses this to generate the .classpath and Eclipse .project files
for Studio. See below why we have this here -->
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-eclipse-plugin</artifactId>
<version>2.10</version>
<configuration>
<sourceIncludes>
<!-- We're using Groovy in this project. If we don't add this in here, then Groovy files are
not compiled by Eclipse. This doesn't impact building the connector since Maven does that.
What it does prevent is running the unit tests in Studio/Eclipse. By adding this in here,
Eclipse will include groovy files in its compilation and unit tests can be run in the Eclipse
JUnit runner -->
<param>**/*.groovy</param>
</sourceIncludes>
</configuration>
</plugin>
</plugins>
</build>
<dependencies>
<dependency>
<groupId>org.codehaus.groovy</groupId>
<artifactId>groovy-all</artifactId>
<version>2.4.4</version>
<!-- Doesn't need to be deployed in ZIP, engine already has this -->
<scope>provided</scope>
</dependency>
<dependency>
<groupId>org.hamcrest</groupId>
<artifactId>hamcrest-library</artifactId>
<version>1.3</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.mule.modules</groupId>
<artifactId>mule-module-apikit</artifactId>
<version>3.8.3</version>
</dependency>
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>4.12</version>
<scope>test</scope>
</dependency>
</dependencies>
<properties>
<category>Community</category>
<licensePath>LICENSE.md</licensePath>
<devkit.studio.package.skip>false</devkit.studio.package.skip>
<type>connector</type>
</properties>
<repositories>
<repository>
<id>mulesoft-releases</id>
<name>MuleSoft Releases Repository</name>
<url>http://repository.mulesoft.org/releases/</url>
<layout>default</layout>
</repository>
</repositories>
</project>