See my reply below the quote...
Fri, 22 Mar 2024, /Debraj Manna/:
[...]
I tried the below
org.springframework.boot
spring-boot-maven-plugin
true
org.apache.maven.plugins
maven-jar-plugin
I think the "simple" solution is to use 2 maven modules, then you don't
need to do anything special. The layout does not make sense to me so I must
be missing something. If the common code is needed for both main and test,
then it should be in main. You can put that common code in its own package
I most frequently use tree and analyze, but have used others like the copy* and
unpack* goals, too.
I do miss an equivalent to tree for plugin dependencies.
--
Alexander Kriegisch
https://scrum-master.de
Tamás Cservenák schrieb am 21.03.2024 17:04 (GMT +01:00):
> I'd would be interested in
I have a Maven module named synapse.
main
java
package1
A.java
test
java
common
C.java
package1
ATest.java
Can someone let me know if in Maven I can create a non-executable jar
containing all non-test code (main/) and another test-jar containing only
the code