Concerned: uberJar is deprecated, and will be removed in a future version

890 views
Skip to first unread message

David Hoffer

unread,
Mar 16, 2021, 3:41:12 PM3/16/21
to Quarkus Development mailing list
After upgrading to 1.12.2.Final I see the following in the build logs.

[INFO] --- quarkus-maven-plugin:1.12.2.Final:build (quarkus-maven-plugin-build) @ accountmgt-quarkus ---
[WARNING] The parameter uberJar is deprecated, and will be removed in a future version. To build an uber-jar set the config property quarkus.package.type=uber-jar. For more info see https://quarkus.io/guides/maven-tooling#uber-jar-maven

I do understand that fastJar is the new default but we prefer the simplicity of the uberJar.  Our concern is why would you ever remove support for uberJar?  We prefer that you keep this packaging as one of the available options.

Thanks,
-Dave


Georgios Andrianakis

unread,
Mar 16, 2021, 3:45:25 PM3/16/21
to David Hoffer, Quarkus Development mailing list
The parameter has been deprecated, not the uber-jar itself.

The proper way to set uber-jar as the desired package is now: quarkus.package.typer=uber-jar

--
You received this message because you are subscribed to the Google Groups "Quarkus Development mailing list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to quarkus-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/quarkus-dev/5a074fbf-e2d2-4122-b88e-a57fc85cb118n%40googlegroups.com.

George Gastaldi

unread,
Mar 16, 2021, 3:45:51 PM3/16/21
to David Hoffer, Quarkus Development mailing list
It's not the support for uberJar that will be removed, it's the parameter "uberJar"  in the maven plugin that will be removed. 

As the message says: To build an uber-jar set the config property quarkus.package.type=uber-jar

David Hoffer

unread,
Mar 16, 2021, 7:34:59 PM3/16/21
to Quarkus Development mailing list
Related to this...when using the latest maven-install-plugin we get the following error.  I assume it's because the Maven build doesn't really know what is being generated for the primary artifact?  We do use the maven-assembly-plugin to generate some additional packaging artifacts.  They are all created but then fails at install.  We have to revert to <version>2.5.2</version> (it has warning but it does work).  

<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-install-plugin</artifactId>
<version>3.0.0-M1</version>
</plugin>

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-install-plugin:3.0.0-M1:install (default-install) on project dataadmin-quarkus: NoFileAssignedException: The packaging plugin for this project did not assign a main file to the project but it has attachments. Change packaging to 'pom'. -> [Help 1]

With 2.5.2...
[INFO] --- maven-install-plugin:2.5.2:install (default-install) @ dataadmin-quarkus ---
[INFO] No primary artifact to install, installing attached artifacts instead.

-Dave

George Gastaldi

unread,
Mar 16, 2021, 7:42:13 PM3/16/21
to David Hoffer, Quarkus Development mailing list
If you could please open an issue with a small reproducer that would help a lot.

Thanks!

Reply all
Reply to author
Forward
0 new messages