| Summary: | Produce jetty-websocket aggregate jar for android use | ||
|---|---|---|---|
| Product: | [RT] Jetty | Reporter: | Joakim Erdfelt <joakim.erdfelt> |
| Component: | websocket | Assignee: | Joakim Erdfelt <joakim.erdfelt> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | jetty-inbox |
| Version: | 7.5.4 | ||
| Target Milestone: | 7.5.x | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Bug Depends on: | 401273 | ||
| Bug Blocks: | |||
|
Description
Joakim Erdfelt
Added maven-shade-plugin configuration (default config, no bytecode manipulation) with classifier 'aggregate' to produce an aggregate jar of the jetty-websocket dependencies. reopening, while the produced artifact is indeed an aggregate, having the pom refer to the existing downstream / transitive dependencies makes using this artifact more noisy.
example:
<dependencies>
<dependency>
<groupId>com.google.android</groupId>
<artifactId>android</artifactId>
<version>${android-version}</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>org.eclipse.jetty</groupId>
<artifactId>jetty-websocket</artifactId>
<version>${jetty-version}</version>
<classifier>aggregate</classifier>
<type>jar</type>
<exclusions>
<exclusion>
<groupId>org.eclipse.jetty</groupId>
<artifactId>jetty-util</artifactId>
</exclusion>
<exclusion>
<groupId>org.eclipse.jetty</groupId>
<artifactId>jetty-io</artifactId>
</exclusion>
<exclusion>
<groupId>org.eclipse.jetty</groupId>
<artifactId>jetty-http</artifactId>
</exclusion>
</exclusions>
</dependency>
</dependencies>
Adding dependency on community/process bug #401273 The new Android Studio 1.0 makes this an irrelevant task. |