clean up some distribution project pom diffs
diff --git a/distribution/pom.xml b/distribution/pom.xml
index a2936f0..29b6bea 100644
--- a/distribution/pom.xml
+++ b/distribution/pom.xml
@@ -70,8 +70,8 @@
<dependencies>
<!-- The general strategy here is to only declare "top-level"
- Edgent artifacts, like an Edgent application pom would,
- and let those artifacts pull in their dependent
+ Edgent artifacts, like an Edgent application pom would,
+ and let those artifacts pull in their dependent
Edgent artifacts, etc.
So declare Providers, Analytics, Utils, Connectors.
-->
diff --git a/platforms/android/distribution/pom.xml b/platforms/android/distribution/pom.xml
index 2d16f40..9283b3d 100644
--- a/platforms/android/distribution/pom.xml
+++ b/platforms/android/distribution/pom.xml
@@ -77,6 +77,11 @@
-->
<!-- Providers -->
+ <!-- Not on android <dependency>
+ <groupId>${edgent.runtime.groupId}</groupId>
+ <artifactId>edgent-providers-development</artifactId>
+ <version>1.2.0-SNAPSHOT</version>
+ </dependency-->
<dependency>
<groupId>${edgent.runtime.groupId}</groupId>
<artifactId>edgent-providers-direct</artifactId>
@@ -195,6 +200,19 @@
<artifactId>edgent-connectors-websocket-jetty</artifactId>
<version>1.2.0-SNAPSHOT</version>
</dependency>
+
+ <!-- Include console-servlets.war to enable a user to run
+ it in their own Servlets engine.
+ It's bundled in the edgent-console-server.jar.
+ Note, edgent-console-server is pulled in as a dependency
+ of the development provider.
+ -->
+ <!-- Not on android <dependency>
+ <groupId>${edgent.runtime.groupId}</groupId>
+ <artifactId>edgent-console-servlets</artifactId>
+ <version>1.2.0-SNAPSHOT</version>
+ <type>war</type>
+ </dependency-->
</dependencies>
</project>
diff --git a/platforms/java7/distribution/pom.xml b/platforms/java7/distribution/pom.xml
index 3726245..f443e58 100644
--- a/platforms/java7/distribution/pom.xml
+++ b/platforms/java7/distribution/pom.xml
@@ -66,36 +66,6 @@
</executions>
</plugin>
</plugins>
- <pluginManagement>
- <plugins>
- <!--This plugin's configuration is used to store Eclipse m2e settings only. It has no influence on the Maven build itself.-->
- <plugin>
- <groupId>org.eclipse.m2e</groupId>
- <artifactId>lifecycle-mapping</artifactId>
- <version>1.0.0</version>
- <configuration>
- <lifecycleMappingMetadata>
- <pluginExecutions>
- <pluginExecution>
- <pluginExecutionFilter>
- <groupId>net.orfjackal.retrolambda</groupId>
- <artifactId>retrolambda-maven-plugin</artifactId>
- <versionRange>[2.5.1,)</versionRange>
- <goals>
- <goal>process-main</goal>
- <goal>process-test</goal>
- </goals>
- </pluginExecutionFilter>
- <action>
- <ignore/>
- </action>
- </pluginExecution>
- </pluginExecutions>
- </lifecycleMappingMetadata>
- </configuration>
- </plugin>
- </plugins>
- </pluginManagement>
</build>
<dependencies>
