Re: Windows Installer / MacOS dmg

[Golan, Yaron]

 https://maven.apache.org/plugins/maven-assembly-plugin/usage.html



From: Vivek Suraiya 
Date: Sunday, 16 October 2022 at 11:28
To: users@maven.apache.org 
Subject: Windows Installer / MacOS dmg
I have a Netbeans 15 JavaFX (18.0.2 / JDK 18.0.2) project with several 
dependencies from the Maven repository. I wish to create a Windows installer 
and a MacOS dmg including all dependencies and the JRE. Is this possible to do?

RE: Global setting for --no-transfer-progress

[Golan, Yaron]

My 2 cents:
alias mvn='/usr/bin/mvn -B --no-transfer-progress'


-Original Message-
From: Tomo Suzuki  
Sent: Tuesday, April 7, 2020 5:17 PM
To: Maven Users List 
Subject: Re: Global setting for --no-transfer-progress

I tried MAVEN_OPTS, which did not work (it's not for Java virtual machine):

suztomo-macbookpro44% export MAVEN_OPTS='--no-transfer-progress'
suztomo-macbookpro44% mvn compile
Unrecognized option: --no-transfer-progress
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.


Ugly suggestion: adding that option at the end of "mvn" shell script.




On Tue, Apr 7, 2020 at 7:29 AM Tarakesh Vishwanath 
wrote:

> Hi,
>
> We have started using Maven 3.6.1's new option --no-transfer-progress 
> to reduce the log output. However, it is cumbersome to add this flag 
> to every maven invocation in codebase.
> Just wanted to know if there's any way this setting can be made Global ??
>
> Regards,
> Tarakesh
>


--
Regards,
Tomo

RE: Maven local repo in a common global directory for multiple parallel execution

[Golan, Yaron]

Please remember that you need much bigger disk space as you are duplicating 
binaries.


-Original Message-
From: Debraj Manna  
Sent: Sunday, May 26, 2019 4:49 PM
To: Maven Users List 
Subject: Maven local repo in a common global directory for multiple parallel 
execution

I have a machine in which multiple parallel maven execution happen . Each 
execution executes the below command in a seperate workspace directory

mvn -f main/pom.xml clean package -DskipTests -T 6

Can someone let me know should I use a seperate maven local repo path (
-Dmaven.repo.local=$MAVEN_REPO) for each execution or I can use a common .m2 
directory for all parallel runs? What is the best practice?


   - Maven Version 3.5
   - Java 8

RE: help on installation issue

[Golan, Yaron]

Can you verify that you have a valid JDK and it is in the path, please?

-Original Message-
From: Marco Stocchi  
Sent: Tuesday, October 23, 2018 10:54 PM
To: users@maven.apache.org
Subject: help on installation issue

Hello...
I have donwloaded and copied the files of maven into my pc. I need to use maven 
to build a java project.
when typing "mvn" on the cmd prompt, I get the following error

Error: -classpath requires class path specification

The internet suggests to mess up with the environment variables, I tried all 
the solutions proposed but nothing worked for me.

Does anyone know what does this message mean?

Thanks

RE: Could not resolve dependencies error

[Golan, Yaron]

The reason for the failure is that there is a missing artifact:
nl.confidential.web:confidentialweb-getdataapi-client:jar:1.2.14.0-SNAPSHOT

1. Are you sure you have your repositories configured as needed?
2. Is the 'getdata-client' ever built before?



-Original Message-
From: Guido van Brakel [mailto:guido.vanbra...@outlook.com] 
Sent: Tuesday, August 28, 2018 11:10
To: users@maven.apache.org
Subject: Could not resolve dependencies error

Hi,

We have an issue with Maven not finding a certain dependency, anyone able to 
help this Maven. Keep in mind that I'm quite newbie to Maven, and just try run 
a build

[ERROR] Failed to execute goal on project confidentialservices: Could not 
resolve dependencies for project 
com.digitaslbi.confidential:confidentialservices:war:0.1.0.12: Could not find 
artifact 
nl.confidential.web:confidentialweb-getdataapi-client:jar:1.2.14.0-SNAPSHOT -> 
[Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal 
on project confidentialservices: Could not resolve dependencies for project 
com.digitaslbi.confidential:confidentialservices:war:0.1.0.12: Could not find 
artifact 
nl.confidential.web:confidentialweb-getdataapi-client:jar:1.2.14.0-SNAPSHOT.

See below for the full stack trace:
Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426; 
2017-04-03T21:39:06+02:00) Maven home: 
C:\Users\davanbrg\.m2\wrapper\dists\apache-maven-3.5.0-bin\6ps54u5pnnbbpr6ds9rppcc7iv\apache-maven-3.5.0
Java version: 1.8.0_181, vendor: Oracle Corporation Java home: C:\Program 
Files\Java\jdk1.8.0_181\jre Default locale: en_US, platform encoding: Cp1252 OS 
name: "windows server 2012 r2", version: "6.3", arch: "amd64", family: "windows"
[DEBUG] Created new class realm maven.api [DEBUG] Importing foreign packages 
into class realm maven.api
[DEBUG]   Imported: javax.enterprise.inject.* < plexus.core
[DEBUG]   Imported: javax.enterprise.util.* < plexus.core
[DEBUG]   Imported: javax.inject.* < plexus.core
[DEBUG]   Imported: org.apache.maven.* < plexus.core
[DEBUG]   Imported: org.apache.maven.artifact < plexus.core
[DEBUG]   Imported: org.apache.maven.classrealm < plexus.core
[DEBUG]   Imported: org.apache.maven.cli < plexus.core
[DEBUG]   Imported: org.apache.maven.configuration < plexus.core
[DEBUG]   Imported: org.apache.maven.exception < plexus.core
[DEBUG]   Imported: org.apache.maven.execution < plexus.core
[DEBUG]   Imported: org.apache.maven.execution.scope < plexus.core
[DEBUG]   Imported: org.apache.maven.lifecycle < plexus.core
[DEBUG]   Imported: org.apache.maven.model < plexus.core
[DEBUG]   Imported: org.apache.maven.monitor < plexus.core
[DEBUG]   Imported: org.apache.maven.plugin < plexus.core
[DEBUG]   Imported: org.apache.maven.profiles < plexus.core
[DEBUG]   Imported: org.apache.maven.project < plexus.core
[DEBUG]   Imported: org.apache.maven.reporting < plexus.core
[DEBUG]   Imported: org.apache.maven.repository < plexus.core
[DEBUG]   Imported: org.apache.maven.rtinfo < plexus.core
[DEBUG]   Imported: org.apache.maven.settings < plexus.core
[DEBUG]   Imported: org.apache.maven.toolchain < plexus.core
[DEBUG]   Imported: org.apache.maven.usability < plexus.core
[DEBUG]   Imported: org.apache.maven.wagon.* < plexus.core
[DEBUG]   Imported: org.apache.maven.wagon.authentication < plexus.core
[DEBUG]   Imported: org.apache.maven.wagon.authorization < plexus.core
[DEBUG]   Imported: org.apache.maven.wagon.events < plexus.core
[DEBUG]   Imported: org.apache.maven.wagon.observers < plexus.core
[DEBUG]   Imported: org.apache.maven.wagon.proxy < plexus.core
[DEBUG]   Imported: org.apache.maven.wagon.repository < plexus.core
[DEBUG]   Imported: org.apache.maven.wagon.resource < plexus.core
[DEBUG]   Imported: org.codehaus.classworlds < plexus.core
[DEBUG]   Imported: org.codehaus.plexus.* < plexus.core
[DEBUG]   Imported: org.codehaus.plexus.classworlds < plexus.core
[DEBUG]   Imported: org.codehaus.plexus.component < plexus.core
[DEBUG]   Imported: org.codehaus.plexus.configuration < plexus.core
[DEBUG]   Imported: org.codehaus.plexus.container < plexus.core
[DEBUG]   Imported: org.codehaus.plexus.context < plexus.core
[DEBUG]   Imported: org.codehaus.plexus.lifecycle < plexus.core
[DEBUG]   Imported: org.codehaus.plexus.logging < plexus.core
[DEBUG]   Imported: org.codehaus.plexus.personality < plexus.core
[DEBUG]   Imported: org.codehaus.plexus.util.xml.Xpp3Dom < plexus.core
[DEBUG]   Imported: org.codehaus.plexus.util.xml.pull.XmlPullParser < 
plexus.core
[DEBUG]   Imported: org.codehaus.plexus.util.xml.pull.XmlPullParserException < 
plexus.core
[DEBUG]   Imported: org.codehaus.plexus.util.xml.pull.XmlSerializer < 
plexus.core
[DEBUG]   Imported: org.eclipse.aether.* < plexus.core
[DEBUG]   Imported: org.eclipse.aether.artifact < plexus.core
[DEBUG]   Imported: org.eclipse.aether.collection < plexus.core
[DEBUG]   Imported: org.eclipse.aether.deployment < plexus.core
[DEBUG]   Imported: org.eclipse.aether.graph < plexus.core
[DEBUG]   

RE: .m2 repository migration

[Golan, Yaron]

I would suggest you NOT to copy anything.
Let maven download whatever it needs.

This will be a test for you, verifying that all your pom.xml files are correct 
and your builds are reproducible on any machine.



-Original Message-
From: USHAKOV, Sergey [mailto:s-n-usha...@yandex.ru] 
Sent: Thursday, May 31, 2018 04:40
To: users@maven.apache.org
Subject: Re: .m2 repository migration

Hi Rishikesh,

and do you see any problem with just copying the '.m2' folder from machine to 
machine?

My guess is that the 'settings.xml' file may deserve your inspection if you 
have anything special in it...

Regards,
Sergey


On 30.05.2018 09:31, Rishikesh Gawade wrote:
> Hello. I would like to migrate my central maven repo, i.e. .m2 from 
> one machine to another machine. Is it possible? If YES, then could you 
> please describe the steps and guide me through? Would be grateful.
> Thanks.
> Regards,
> Rishikesh
>


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

RE: mvn deploy is installing localrepo instead of remote repo

[Golan, Yaron]

Hi,
I usually set the URLs in the DistributionManagement part of the pom.xml file.
Can you share the log file from the 'mvn deploy' command you ran, please?



-Original Message-
From: Naveen Swamy [mailto:mnnav...@gmail.com] 
Sent: Wednesday, May 30, 2018 06:24
To: Maven Users List 
Subject: mvn deploy is installing localrepo instead of remote repo

I am running mvn deploy on the package to send it to the staging repo, however 
it seems to install only on the local repo? Any ideas on how to debug and 
resolve this?

I have already set the right staging repos in settings.xml and it seems to 
reading the settings from what i tell from the debug logs.

Appreciate your help

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

RE: Deploy shaded jar with an without classifier simultaneously

[Golan, Yaron]

Not sure if my proposal will fit your needs, but I'd try to run the 
deploy:deploy-file goal right after the default deploy phase.

The default deploy will upload your default jar while the second execution will 
upload the shaded one.
Or the other way (order) around.

Bottom line is that you'll have both jars uploaded to the artifacts repository.



YG





-Original Message-
From: Dagan Sandler [mailto:dagansand...@gmail.com] 
Sent: Sunday, May 13, 2018 13:52
To: Maven Users List 
Subject: Deploy shaded jar with an without classifier simultaneously

Hi all,

I'll start by saying that I'm aware this is not an ideal configuration and I 
only need this as an intermediate solution to a larger problem I'm dealing with 
which is out of the scope of this question.

I'm wondering if there's an easy way to do this with maven-shade-plugin only.

My current situation is that I have an artifact being packaged as a shaded jar 
with all its dependencies, let's call it *my-shaded-module. *This artifact is 
currently being deployed with a single artifact (the shaded
jar) - named my-shaded-module, without any qualifier*.*

My end goal is to have this module deployed with 2 artifacts - a simple
(plain) jar with no classifier, and the shaded jar with a "shaded"
classifier. I know how to do this, but some outside concerns are limiting my 
ability to do this immediately.

What I'd like to achieve for the intermediate solution is to deploy this 
artifact in its shaded form twice for every build, meaning that running mvn 
deploy will result in 2 artifacts being deployed:
1. my-shaded-module.jar
2. my-shaded-module-shaded.jar
Both of which are supposed to be shaded at this point.

I can probably do it using some additional plugins like assembly plugin or 
something but I'm hoping maybe someone has a solution for a simple idea of how 
to do this, maybe with maven-shade-plugin alone.
Keep in mind that this is a temporary solution, hence why I'm trying to avoid 
introducing additional plugins to the build.

Hope this was clear enough

Thanks,
Dagan.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

RE: Maven Installation Troubleshooting

[Golan, Yaron]

Your JAVA_HOME should point to the folder where you’ve installed the Java *SDK* 
(not JRE)
e.g. (as taken from my PC):
*C:\Java\jdk1.8.0_121*

This folder should have the following folders:
bin
db
include
jre
lib
release

Hope this helps…

From: Hanna Prince [mailto:hannaprin...@gmail.com]
Sent: Friday, April 20, 2018 16:09
To: users@maven.apache.org
Cc: jdegr...@nicholsschool.org
Subject: Maven Installation Troubleshooting

Hi,

I'm try to install Maven to use OpenIMAJ for a high school programming project, 
but I don't have much experience with using terminal and I'm having problems 
installing it.

Here's a screenshot of my terminal with following the OpenIMAJ and Maven 
instructions to check if I have Maven installed correctly.  Based on what I've 
found, I think there's a problem with where I have JAVA_HOME. Is that correct?  
How do I fix this?

Thank you,
Hanna Prince

RE: A maven plugin to add dynamically a repository at build time

[Golan, Yaron]

Hi,

Here is my proposal...

Inside your main/parent pom.xml, set the following:


...

foo
boo




${repo.name}
${repo.url}


...



And your maven command should like:
mvn  -Drepo.name=some.repo.name -Drepo.url=relevant.url


What do you say?

YG




-Original Message-
From: Nicolas Brasey [mailto:nicolas.bra...@gmail.com] 
Sent: Monday, April 09, 2018 20:41
To: users@maven.apache.org
Subject: A maven plugin to add dynamically a repository at build time

Hi,

In my continuous integration solution, I need to have a maven repository which 
is calculated based on the git branch name. For example, I have a naming 
convention which is used to calculate the maven repo URL, something similar to 
this:

Branch name -> Git Repo URL:
--- -
develop -> 
https://urldefense.proofpoint.com/v2/url?u=http-3A__archiva_repositories_snapshot=DwIBaQ=LFYZ-o9_HUMeMTSQicvjIg=GYb_8qONFTPgVpTfZRT53aEptjaOm6sDrruaOwiowLQ=wYKDMhCmuL6gf7KPllHND78qrm6EwCIeSTQMt6cv268=YFvvW16iOsJQtkao0hwVmS33Rh07ba1sfucC1yHSwFI=
 
feature/xxx -> 
https://urldefense.proofpoint.com/v2/url?u=http-3A__archiva_repositories_feature-2Dxxx=DwIBaQ=LFYZ-o9_HUMeMTSQicvjIg=GYb_8qONFTPgVpTfZRT53aEptjaOm6sDrruaOwiowLQ=wYKDMhCmuL6gf7KPllHND78qrm6EwCIeSTQMt6cv268=tUqew2vcZMbgd3HbH8wWGoTp_v94pBrDATIHUCug8jw=
 
staging/xxx -> 
https://urldefense.proofpoint.com/v2/url?u=http-3A__archiva_repositories_staging-2Dxxx=DwIBaQ=LFYZ-o9_HUMeMTSQicvjIg=GYb_8qONFTPgVpTfZRT53aEptjaOm6sDrruaOwiowLQ=wYKDMhCmuL6gf7KPllHND78qrm6EwCIeSTQMt6cv268=KXqHxpLtHwoU86yY9ySm1QrSBtaoN7lsraCeF6DW9dw=
 


I wrote a maven plugin that adds dynamically a repository in my project but 
unfortunately, my plugin is not invoked before maven performs the dependency 
resolution.

I googled it and tried some workaround proposed (like putting my plugin in the 
pre-clean phase), but it still executes after the dependency resolution.

You guys ever tried this?

Thanks,
Nicolas

RE: Installation issue

[Golan, Yaron]

What is the output of:
ls -l /usr/local/apache-maven-3.5.3/bin

if it is OK, try to open a new terminal or, alternatively, run 'source 
.bash_profile'



-Original Message-
From: Romanos Sklavenitis Pistofidis [mailto:r...@broadinstitute.org] 
Sent: Wednesday, March 28, 2018 16:51
To: users@maven.apache.org
Subject: Installation issue

Hi all, 

I am trying to get started with Maven, but I am having trouble installing it. 
 
I have edited my ~/.bash_profile and added /usr/local/apache-maven-3.5.3/bin to 
the $PATH variable and set $JAVA_HOME to 
/Library/Java/JavaVirtualMachines/jdk-9.0.4.jdk/Contents/Home, but when I call 
mvn, command is not found. 

Any suggestions?

Thanks a lot!

~Romanos

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

RE: old version of dependencies getting included into project

[Golan, Yaron]

Hi Jon,
This scenario is very strange.

Are you absolutely sure that the mvn dependency:tree didn't print it out?



-Original Message-
From: Jonathan Yom-Tov [mailto:jon.yom...@huha-analytics.com] 
Sent: Wednesday, March 14, 2018 21:40
To: users@maven.apache.org
Subject: old version of dependencies getting included into project

hi,

I have a fairly large project which compiles to a war file. I've upgraded the 
jackson dependency to 2.7.3 but for some reason 2.4.3 and 2.4.0 jar files are 
included into the war file in addition to the 2.7.3 version. I ran mvn 
dependency:tree to figure out the reason but the old versions don't appear 
there. They also don't appear in the build log. I deleted the old versions from 
my local maven repo. Didn't help. Any ideas on how to figure this out?

thanks,
Jon.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org