Yes, this would be the clean solution and I am refactoring the project
to go there. But first I have to separate integration and component
tests. Therefore I need the classes in the war module also available as
jar for those tests.
Oliver
Am 19.12.15 um 13:28 schrieb Tibor Digana:
@Oliver
Wh
Hi,
I decided to create an additional jar while refactoring the the
buildstructure of an old project not created by me. The integration and
component tests, which I moved to an separated modul, have dependecies
to classes of the war producing module. As I can not add a war to the
classepath I
@Oliver
What is your use case?
I want to know why you want to split classes/resources and web content. Is
not it more clean solution to have multi-module project where jar module
would contain Java files+resources and war module dependent on jar artifact?
On Sat, Dec 19, 2015 at 12:48 PM, Oliver B
Hi Olivier
Why not using standard war plugin for that:
https://maven.apache.org/plugins/maven-war-plugin/war-mojo.html#attachClasses
Le 19 déc. 2015 12:49, "Oliver B. Fischer" a écrit :
> Hi,
>
> my project is build as war but I need also a jar of the classes. Therefore
> I build also a .jar and
Hi,
you can use a configuration option of the maven-war-plugin
(attachClasses) which will produce a separate jar of the classes you
have in your war module:
http://maven.apache.org/plugins/maven-war-plugin/war-mojo.html#attachClasses
This jar is separately installed and can be used by other
Hi,
my project is build as war but I need also a jar of the classes.
Therefore I build also a .jar and use the build-helper-maven-plugin to
attach it to artifacts to be installed. With this configuration the .jar
will be installed as .war and as .jar. The .war itself will be not
installed.
