Install phase isn't all that necessary. Iirc it's the last one in the
process. So you can use either verify (which is the integration test phase)
or package (which is jar generation phase and runs after unit tests)
On Tue, Oct 31, 2023, 19:04 Peter Carlson wrote:
> This works well, except I dont
This works well, except I dont want this:
[INFO] Installing /home/peter/workspace/SDCP/target/sdcp.jar to
/home/peter/.m2/repository/com/howudodat/sdcp/1.0-SNAPSHOT/sdcp-1.0-SNAPSHOT.jar
[INFO] Installing /home/peter/workspace/SDCP/pom.xml to
/home/peter/.m2/repository/com/howudodat/sdcp/1.0-SN
For me best solution is assembly plugin :
https://maven.apache.org/plugins/maven-assembly-plugin/
You can chose dir format if you don't want zip or equivalent
Arnaud
Le mar. 31 oct. 2023, 17:01, Delany a écrit :
> Hi Peter,
>
> Firstly, compile and package are part of the same lifecycle (the d
Hi Peter,
Firstly, compile and package are part of the same lifecycle (the default
lifecycle), so its not necessary to specify both.
Then you can add this profile to your pom so you don't have to run the
dependency plugin separately.
dispatch
${project.artifactId}
I currently use the below commands to prepare my java application:
mvn clean compile package dependency:copy-dependencies
Then I manually copy the files with:
cp target/myapp-1.0-SNAPSHOT.jar /mnt/remote_app/myapp.jar
cp target/dependency/* /mnt/remote_app/libs/
I'm wondering:
