maven-jar-plugin

New <updateManifestEntries> entries of webstart-maven-plugin breaks the application

别等时光非礼了梦想. 提交于 2019-12-01 16:27:14
As my JDK version upgraded to u45 now I get warnings about missing security information. So I used following security updates as part of webstart signing using webstart-maven-plugin <plugin> <groupId> org.codehaus.mojo</groupId> <artifactId>webstart-maven-plugin</artifactId> <version>1.0-beta-4</version> <executions> <execution> <phase>package</phase> <goals> <goal>jnlp-inline</goal> <!-- use jnlp, jnlp-inline or jnlp-single as appropriate --> </goals> </execution> </executions> <configuration> <!--outputDirectory></outputDirectory --> <!-- not required?? --> <!-- Set to true to exclude all

Why is the Maven JAR plugin not including some resources?

爷,独闯天下 提交于 2019-12-01 15:51:57
问题 I have an enterprise application which I am in the process of converting from an Ant build to Maven. It's almost completely converted; this is the very last thing I need to fix. The application is packaged as an EAR file which contains two WARs and has a JAR module which provides all of the core functionality of the application. I'm using the Freemarker templating library to generate, among other things, message bodies for automatic emails sent by the application. Freemarker needs its *.ftl

New <updateManifestEntries> entries of webstart-maven-plugin breaks the application

泪湿孤枕 提交于 2019-12-01 15:06:20
问题 As my JDK version upgraded to u45 now I get warnings about missing security information. So I used following security updates as part of webstart signing using webstart-maven-plugin <plugin> <groupId> org.codehaus.mojo</groupId> <artifactId>webstart-maven-plugin</artifactId> <version>1.0-beta-4</version> <executions> <execution> <phase>package</phase> <goals> <goal>jnlp-inline</goal> <!-- use jnlp, jnlp-inline or jnlp-single as appropriate --> </goals> </execution> </executions>

How do you create a standalone application with dependencies intact using Maven?

[亡魂溺海] 提交于 2019-11-30 14:58:15
问题 I have a desktop Java application built using Maven 2 (but I could upgrade to Maven 3 if that helps) with a number of open source dependencies. I'm now trying to package it up as a standalone to make it available to end users without them needing to install maven or anything else. I've successfully used maven-assembly-plugin to build a single jar containing all dependencies but this is not really what I want because when using LGPL libraries you are meant to redistribute the libraries you are

Maven JAR Plugin 3.0.2 Error: You have to use a classifier to attach supplemental artifacts to the project instead of replacing them

生来就可爱ヽ(ⅴ<●) 提交于 2019-11-28 22:54:42
Maven JAR plugin (version 3.0.2) keeps throwing the following error, even for a single invocation of the jar goal : [ERROR] Failed to execute goal org.apache.maven.plugins:maven-jar-plugin:3.0.2:jar (default) on project test: You have to use a classifier to attach supplemental artifacts to the project instead of replacing them. -> [Help 1] Here's a (minimal?) pom.xml which demonstrates the problem: <project xmlns="http://maven.apache.org/POM/4.0.0"> <modelVersion>4.0.0</modelVersion> <groupId>test</groupId> <artifactId>test</artifactId> <version>1.0.0-SNAPSHOT</version> <build> <plugins>

How to include test classes in Jar created by maven-shade-plugin?

橙三吉。 提交于 2019-11-28 06:17:54
I'm trying to package my test classes in to an executable jar with dependencies using Maven, but I'm struggling to get this right. This is my pom.xml so far: <project> <modelVersion>4.0.0</modelVersion> <groupId>com.c0deattack</groupId> <artifactId>executable-tests</artifactId> <version>1.0</version> <packaging>jar</packaging> <name>executable-tests</name> <dependencies> <dependency> <groupId>info.cukes</groupId> <artifactId>cucumber-java</artifactId> <version>1.0.0</version> </dependency> <dependency> <groupId>info.cukes</groupId> <artifactId>cucumber-junit</artifactId> <version>1.0.0<

Maven: The packaging for this project did not assign a file to the build artifact

依然范特西╮ 提交于 2019-11-28 02:54:37
I'm using Maven 3.0.3 on Mac 10.6.6. I have a JAR project and when I run the command "mvn clean install:install", I'm getting the error, [ERROR] Failed to execute goal org.apache.maven.plugins:maven-install-plugin:2.3.1:install (default-cli) on project StarTeamCollisionUtil: The packaging for this project did not assign a file to the build artifact -> [Help 1] What does this mean and how can I fix it? Below is my pom.xml. Let me know what other info would be helpful and I'll edit this post. Thanks, - Dave <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001

disable the execution: default-jar

放肆的年华 提交于 2019-11-27 09:13:33
i am using maven assembly plugin to pack a jar file. But when i run mvn package , maven always trigger the [jar:jar {execution: default-jar}] to create a default jar file. So i will have 2 jar files (one created by assembly plugin and one created by maven jar which i dont want to be created). How can i turn off the execution: default-jar. in my pom.xml, i am using : <packaging>jar</packaging> . i dont want to change it to <packaging>pom</packaging> . (...) So i will have 2 jar files (one created by assembly plugin and one created by maven jar which i dont want to be created). Looks like you're

How can I include test classes into Maven jar and execute them?

扶醉桌前 提交于 2019-11-27 04:04:43
In a Maven project, I have test classes and source classes in the same package, but in different physical locations. .../src/main/java/package/** <-- application code .../src/test/java/package/** <-- test code It's no problem to access the source classes in the test classes, but I would like to run a test runner in the main method and access the AllTest.class so that I can create jar and execute my tests. public static void main(String[] args) { // AllTest not found Result result = JUnitCore.runClasses(AllTest.class); for (Failure failure : result.getFailures()) { System.out.println(failure

Maven JAR Plugin 3.0.2 Error: You have to use a classifier to attach supplemental artifacts to the project instead of replacing them

Deadly 提交于 2019-11-27 02:06:17
问题 Maven JAR plugin (version 3.0.2) keeps throwing the following error, even for a single invocation of the jar goal : [ERROR] Failed to execute goal org.apache.maven.plugins:maven-jar-plugin:3.0.2:jar (default) on project test: You have to use a classifier to attach supplemental artifacts to the project instead of replacing them. -> [Help 1] Here's a (minimal?) pom.xml which demonstrates the problem: <project xmlns="http://maven.apache.org/POM/4.0.0"> <modelVersion>4.0.0</modelVersion> <groupId