You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is use case when 3rd party jar depends on open-source components, so we added dependency within pom.xml
Then however looking at pom.xml file deployed to local maven repository, it is clear that the composed pom.xml is deployed, that has <packaging>non-maven-jar</packaging>
That means we will need this plugin to bring as well if we just want to use non-maven-jar in other project.
I think it would be better to produce pom.xml more like it should be, if created by jar authors.
The text was updated successfully, but these errors were encountered:
There is use case when 3rd party jar depends on open-source components, so we added dependency within pom.xml
Then however looking at pom.xml file deployed to local maven repository, it is clear that the composed pom.xml is deployed, that has
<packaging>non-maven-jar</packaging>
That means we will need this plugin to bring as well if we just want to use non-maven-jar in other project.
I think it would be better to produce pom.xml more like it should be, if created by jar authors.
The text was updated successfully, but these errors were encountered: