Currently I am debugging an annoying maven situation in which a simple
mvn dependency:tree
complains
The POM for com.bitplan.java:com.bitplan.bobase:jar:${bobase.version} is missing, no dependency information available
So it looks like a property is not defined somewhere. But the relevant parent pom clearly has:
<properties>
<bobase.version>0.0.2</bobase.version>
</properties>
What is more interesting is that I am not even referencing any relevant file with such a declaration directly.
In the process of this mishap in the local repository a directory:
./com/bitplan/java/com.bitplan.bobase/${bobase.version}
shows up. So I got curious and looked if there were more of these:
cd $HOME/.m2/repository
find . -type d | grep "\\$"
gives me some 27 results at this time e.g.
./net/sourceforge/htmlcleaner/htmlcleaner/${htmlcleaner.version}
./junit/junit/${junit.version}
./junit/junit/${junit4.version}
./org/hamcrest/hamcrest-all/${hamcrestall.version}
./org/apache/commons/commons-lang3/${commons.version}
./commons-io/commons-io/${commons-io.version}
./commons-io/commons-io/${commons.io.version}
./args4j/args4j/${args4j.version}
I only understand one of the cases - the commons.io.version one - that was a typo and I fixed it. All other variables should be dereferencing ok and there should not be any such directories.
What causes this maven behavior and how can it be avoided?
I only found one releated question:
Check for unresolved properties in Maven Resources
but that gave me no useful hint
debugging
find . -type d -name "*\$*" -exec echo -n {} \; -exec stat -f %Sm -t " "%Y-%m-%d {} \;
shows the last modification time of the directories. E.g.
./junit/junit/${junit.version} 2018-08-22
./junit/junit/${junit4.version} 2017-05-28
so in my case the issue seems to happen every once in a while.
mvn deploy
of the parent pom is necessary if the version of the pom has not been upgraded.
mvn install
is not sufficient. The resolution of variables will be done on the "old" settings from the repository.
Related
I'm aware of artifactory (which is planned in the future), but it's requested to package the artifacts on our releases.
We currently do on a script:
printf "\nCopying artifacts...\n"
for artifact_dir in "$HOME"/.m2/repository/com/foo/{*-ear,*-ui,*-tool}; do
highest_version=$(find "${artifact_dir}"/* -maxdepth 1 -type d -printf "%f\n" | sort -V | tail -1)
artifact_name=$(basename "${artifact_dir}")
mkdir --parent "${artifacts_out}/com/foo/${artifact_name}/${highest_version}"
cp --archive "${artifact_dir}/${highest_version}"/* \
"${artifacts_out}/com/foo/${artifact_name}/${highest_version}"
done
But as you can see it's not very neat, p.e we can not create a release with older artifacts because the script always takes the newest one.
Is there a maven plugin or something that permits to archive specific artifacts ?
If you want to create bundles of artifacts, run the Maven assembly plugin during the build. It can be used to gather artifacts, zip them and deploy the result to Artifactory/Nexus.
When this(selenium-chrome-driver) dependency can be use ?
<!-- https://mvnrepository.com/artifact/org.seleniumhq.selenium/selenium-chrome-driver -->
<dependency>
<groupId>org.seleniumhq.selenium</groupId>
<artifactId>selenium-chrome-driver</artifactId>
<version>3.14.0</version>
</dependency>
On many answers I have read, It need to use with Chrome binary definition. By using only chrome binary we are able to execute script on Chrome Browser. Thus, driver calling is subject with Binary definition.
Question: So what is the use of this dependency, without chrome binary file ?
I have referred below answers and tried, without using binary declaration. Which says to use WebDriverManager dependency:
How to work with chrome driver in Maven
selenium 2 chrome driver
https://stackoverflow.com/a/39809773/9405154
https://github.com/bonigarcia/webdrivermanager
This is Resolved,
Error: Failure to transfer
org.apache.commons:commons-compress:jar:1.14 from
https://repo.maven.apache.org/maven2 was cached in the local
repository, resolution will not be reattempted until the update
interval of central has elapsed or updates are forced. Original error:
Could not transfer artifact
org.apache.commons:commons-compress:jar:1.14 from/to central
(https://repo.maven.apache.org/maven2): The operation was cancelled.
Selenium is a multi-module project. One of the modules is selenium-chrome-driver. It contains logic related to running chrome with selenium. You can add this dependency to your project and somehow modify/extend its original behavior. It will not run the actual chrome browser without having a binary though - that's just how it works. You will have to build executable file by yourself then. You can check how projects use this dependency here
Long story short if you don't want to bother managing binaries use WebDriverManager because it works like a charm.
Based on the error text from your question, you can try the following solution:
Remove all your failed downloads:
find ~/.m2 -name "*.lastUpdated" -exec grep -q "Could not transfer" {} \; -print -exec rm {} \;
For windows:
cd %userprofile%\.m2\repository
for /r %i in (*.lastUpdated) do del %i
Then rightclick on your project in eclipse and choose Maven->"Update Project ...", make sure "Update Dependencies" is checked in the resulting dialog and click OK.
copied from here: Link
I assume your automation project is a maven-project. So when you build your project, the dependencies in pom will be downloaded locally to execute. But a binary file needs to be set using SystemProperty and passing the parameter as the path to that webdriver, which will allow the webdriver instance to communicate with the browser instance on that machine. So, we do not need this dependency in all. Same goes for other browser too I guess.
Also if you are doing CI using jenkins, you should prefer using docker. That way you don't have to manage the binary instances, the docker will handle that for you.
As the header says I wonder if there is such an opportunity in Maven to know the jar a class file gets loaded in a module. Just like dependency:tree, but I would like to see jars with a specific class file. Thanks!
As far as I know, there is no specific Maven plugin (3.0+) that will search dependencies for class declarations. However, I believe I understand your need and offer the following solutions:
Finding duplicate declarations
mvn dependency:analyze-duplicate -DcheckDuplicateClasses
Find containing JAR within Eclipse
Use CTRL+SHIFT+T to bring up the Open Type dialog. Entering part or the whole class name presents a list of containing JARs on the build classpath.
Find containing JAR without IDE
If more programatic control is required for checking on systems without an IDE, say a CI server, the following snippets can be used to list JAR files containing a specific class or even a specific name pattern. This approach uses Maven's dependency plugin to collect all dependencies in a temporary directory such that they may be easily searched.
For Unix or Git Bash systems
mvn clean dependency:copy-dependencies -DoutputDirectory=target/temp
for j in target/temp/*.jar; do jar -tf $j | grep SomeClass && echo $j; done
For Windows via cmd shell
mvn clean dependency:copy-dependencies -DoutputDirectory=target/temp
for /R %G in (target\temp\*.jar) do #jar -tf "%G" | find "SomeClass" && echo %G
In either case, a matching entry's full package and class name will be displayed followed by the containing JAR file name. grep and find search parameters can be further refined to restrict matches as needed, such as SomeClass.class.
Hope this helps.
I have an Eclipse setup with m2eclipse and subversive. I have imported a maven2 project from svn. But I get the error message that a whole bunch of artifacts are missing (for instance: Missing artifact org.springframework:spring-test:jar:3.0.1.RELEASE:test).
If I look in my repository I see the jar files there but they have an extra extension .lastUpdated. Why is maven appending .lastUpdated to the jars? And more importantly: how can I fix this?
There is no mention of the type lastUpdated in my POMs.
These files indicate to Maven that it attempted to obtain the archive by download, but was unsuccessful. In order to save bandwidth it will not attempt this again until a certain time period encoded in the file has elapsed. The command line switch -U force maven to perform the update before the retry period. This may be necessary if you attempted to build while disconnected from the network.
The method of removing the files works with most versions of maven, but since the files are internal mementos to maven, I would not recommend this method. There is no guarantee that this information is not referenced or held elsewhere and such manipulation can damage the system.
As rperez said, I use to delete all those .lastUpdated files. In Linux I have created a little script to keep it simple:
find -name \*.lastUpdated -exec rm -fv {} +
Just create a file with the previous content and put it on your local Maven repository. Usually it will be ~/.m2/repository.
I installed Maven2 and ran mvn compile from the command line. This seems to have resolved the problem
you might have a problem with some of the artifacts to be retrieved from the repository. for example spring framework has its own repository. this xtension is appended when the artifact cannot fully downloaded. add the spring framework repository to your pom or settings.xml, delete the folder that include the broken jars and start again
If you hit this problem and you're using Nexus, it might be the case that you have a routing rule defined, which is incorrect. I hit this myself and the files it was downloading were correctly named, at the proper URL-s it was looking at, but they were all with the .lastUpdated extension and an error message as contents.
Open your terminal, navigate to your Eclipse's project directory and run:
mvn install
If mvn install doesn't update your dependencies, then call it with a switch to force update:
mvn install -U
This is a much safer approach compared to tampering with maven files as you delete ".lastUpdated".
Use this command inside the .m2/repository dir to rename all files:
for file in `find . -iname *.lastUpdated`; do renamed=$(echo $file | rev | cut -c13- | rev); echo renaming: $file to $renamed; mv $file $renamed; done
This is usefull to not download all sources again.
This not work... The .jar is lost. :(
What I do when I encounter this issue:
Make sure you have the version of the latest 'maven-source-plugin' plugin:
https://maven.apache.org/plugins/maven-source-plugin/usage.html
$ mvn source:jar install
Now if the file *.lastUpdate exist in your local ~/.m2/repositories/your-lib/0.0.1/ directory you can just remove it then run the command above again.
This is a side-effect of a failure to successfully extract from the repository. To get the actual content you want into your repository, check for correct paths to the repository/repositories within your pom file, and resolve certificate/security issues, if any. It is almost invariably one or the other of these issues.
There is no need to delete the .lastUpdated entries, and doing so won't solve your problem.
In our project, Maven build generates artifacts for different modules i.e. jar, console, car etc in corresponding folder structure.
Everytime we check in the code, the build genarates full new artifacts even if there is only change in "console" module.
Is there any Maven plugin or a way to generate only the artifacts which were changed since last successful build?
For instance, if I have changed the code for "console" module, then the artifact generated should only have console file in its corresponding folder.
If you are on command line you can use
mvn -pl moduleToBuild
which can be combined with:
mvn -pl moduleToBuild -am
which will also build the dependencies of moduleToBuild.
If you are in a CI solution like jenkins there is a check box to activate this behaviour. This can be found under the Maven configuration part Incremental build - only build changed modules.
You have to start the maven call on the root of your multi-module build.
You may want to look at using maven reactor plugin's reactor:make-scm-changes goal. This link has example on how to use this.
I was looking for something that would check what files I have changed compared to the "upstream" version, and build all Maven modules which contain the files, and all depending on them.
Since reactor:make-scm-changes doesn't seem to do that, one way to do it (Linux Bash way) is to
list the changed files, using (git diff --name-only master...),
find the nearest pom.xml for all,
deduplicate (... | sort | uniq),
provide it to Maven as a list using --project-list, with --also-make.
The rest is joining it together using pipes and functions.
Of course this assumes that all sources are within the folder with pom.xml, which typically is true.
Here's an example of the approach mentioned by Ondra Žižka, using mvn clean install and bash.
Note, it ignores pom packaging modules (as those are typically roots of subtrees and would usually cause additional, unnecessary modules to be built. It also looks for pom.xml files 3 levels deep (for speed), assuming they're all part of the same reactor, but this can be adjusted to your project.
find . -maxdepth 3 -name pom.xml | xargs -I{} grep -iL -F "<packaging>pom</packaging>" {} | xargs dirname | grep -v target | sed -e 's/^.[/]*//g' | grep . > /tmp/mvn-modules.txt && git diff --name-only #{u}...HEAD | grep -o -F -f /tmp/mvn-modules.txt | xargs | tr ' ' ',' | xargs -I{} mvn clean install -U -pl {} -amd
In the example #{u}...HEAD references changes in current branch compared to upstream, but this can be swapped for another diff (example <branchname> master) if this is more suitable.