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

Create dynamic library without specifying main jar #64

Open
jonvnieu opened this issue Nov 25, 2017 · 2 comments
Open

Create dynamic library without specifying main jar #64

jonvnieu opened this issue Nov 25, 2017 · 2 comments

Comments

@jonvnieu
Copy link

Hi,

I would like to be able to create a dynamic library that does not contain any source code of its own ( i.e. there is no main jar artifact), but it just bundles several dependencies together. At the moment I can't do this easily, because the plugin expects a main jar to specified.

There are workarounds (e.g. using the maven-assembly-plugin to first create a jar-with-dependencies and then ignoring the project dependencies). But the solution would be more elegant if we could somehow specify that we are building a DLL that's purely based on libraries.

@pjBooms
Copy link
Contributor

pjBooms commented Nov 27, 2017

Would you like to you use <packaging>pom</packaging> for such a case?
If you use <packaging>jar</packaging>, Maven creates an empty jar if there is no sources (just dependencies) and jet plugin compiles that empty jar with all the dependencies into a DLL (that can be considered as another workaround).

@jonvnieu
Copy link
Author

jonvnieu commented Nov 27, 2017

Yes, I was thinking about a scenario where <packaging>pom</packaging> is used.
For the time being I was already using the jar-packaging as a workaround (which works just fine).

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