Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

maven-jar-plugin update not discovered #1070

Open
THausherr opened this issue Apr 22, 2024 · 2 comments
Open

maven-jar-plugin update not discovered #1070

THausherr opened this issue Apr 22, 2024 · 2 comments

Comments

@THausherr
Copy link

THausherr commented Apr 22, 2024

How to reproduce:

  1. Clone https://github.com/apache/tika
  2. in tika-parent/pom.xml , change <maven.jar.version>3.4.1</maven.jar.version> to <maven.jar.version>3.3.0</maven.jar.version>
  3. run mvn org.codehaus.mojo:versions-maven-plugin:2.16.2:display-dependency-updates org.codehaus.mojo:versions-maven-plugin:2.16.2:display-plugin-updates org.codehaus.mojo:versions-maven-plugin:2.16.2:display-property-updates, while using maven 3.9.6.

expected: getting output like

${maven.jar.version} ................................... 3.3.0 -> 3.4.1
maven-jar-plugin ................................... 3.3.0 -> 3.4.1

what I got instead: no such thing

Whatever the cause is, it doesn't happen in another project of mine, so I think the jar itself or its metadata isn't to blame. I have read the FAQ.

@slawekjaranowski
Copy link
Member

Hi

maven.jar.version property is not used in tika-parent/pom.xml so property update is not detected.
plase add a pluginManagemnt section in tika-parent/pom.xml

but:

mvn versions:display-plugin-updates -pl tika-eval/tika-eval-core/pom.xml  
...

[INFO] --- versions:2.16.2:display-plugin-updates (default-cli) @ tika-eval-core ---
[INFO] 
[INFO] The following plugin updates are available:
[INFO]   maven-jar-plugin ................................... 3.3.0 -> 3.4.1

looks ok.

@THausherr
Copy link
Author

Thanks, this works, but is unexpected. It would mean that it wouldn't make much sense to use properties. Github dependabot detects it (but has other drawbacks).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants