Hi,
i have a large project which contains multiple modules and sub-modules.
Base (packaging: POM)
+--- M1 (parent: Base)
+--- M2 (parent: Base)
+--- M3 (packaging: POM; parent: Base)
+--- M3.1 (parent: M3)
+--- M3.2 (parent: M3)
+--- M4(packaging: POM; parent: Ba
Hi there,
i have a little problem with the release:prepare running in Maven.
I have a mutli module setup which seemed to be ok
parent
+--- Module A (depends on C) (result in tar.gz)
+--- Module B
+--- Module C
+--- Module WAR
+--- Module D (Tomcat with .war from Module WAR as a .ta
2009/3/24 Karl Heinz Marbaise
> Hi,
>
> i have a large project which contains multiple modules and sub-modules.
>
>
> Base (packaging: POM)
> +--- M1 (parent: Base)
> +--- M2 (parent: Base)
> +--- M3 (packaging: POM; parent: Base)
> +--- M3.1 (parent: M3)
> +--- M3.2 (paren
Hi Stephen,
If you are doing that you'd be better omitting the version entirely as it
will be inherited from the parent...
Yeah i changed that and it worked...great...
foo
bar
1.0-SNAPSHOT
manchu
is exactly equivalent to
foo
bar
1.0-SNAPSHOT
${proj
2009/3/24 Karl Heinz Marbaise
> Hi Stephen,
>
> If you are doing that you'd be better omitting the version entirely as it
>> will be inherited from the parent...
>>
> Yeah i changed that and it worked...great...
>
>
>>
>>foo
>>bar
>>1.0-SNAPSHOT
>>
>> manchu
>>
>>
>> is exact
Hi Karl Heinz!
On 29 Sep 2008, Karl Heinz Marbaise wrote:
> i have a little problem with the release:prepare running in Maven.
>
> I have a mutli module setup which seemed to be ok
>
> parent
> +--- Module A (depends on C) (result in tar.gz)
> +--- Module B
> +--- Module C
> +--- Mo
Hi Martin,
first thanks for your answer,
> We are having the same problem here with EARs and skinny WARs. It's been
> a while since I last looked what the problem is but our problem is
> definitely related to the skinny WAR problem [0] and your's might be too.
> The workaround we are using is to
On Wednesday 01 October 2008 Karl Heinz Marbaise wrote:
> > We are having the same problem here with EARs and skinny WARs. It's
> > been a while since I last looked what the problem is but our problem is
> > definitely related to the skinny WAR problem [0] and your's might be
> > too. The workaroun
Hi,
I am facing a problem with correctly setting up shading in a multi module
maven project. Currently all the original code is removed / filtered out
from the user-jar even though.
http://stackoverflow.com/questions/43873608/maven-shade-in-multi-project-setup-filtering-too-much
Looking forward t
Hello there,
I am fairly new to using Maven having mostly done it through IDE or using
Ant.
We are using Spring Boot, and their 1.4.x update changed the structure of
their FAT jar mechanism such that many libraries that also scan for classes
broke. There is a work around, basically it requires se
Hi Maven gurus,
I would like to know what is the best recommended way of definining maven
multi-module projects?
Is it the hierarchical ?
parent/pom.xml
parent/childA/pom.xml
parent/childB/pom.xml
or flat-structure ?
parent/pom.xml
childA/pom.xml
childB/pom.xml
I'm using eclipseIDE w
I have been looking at
http://mojo.codehaus.org/jalopy-maven-plugin/multimodule.html
And I really don't understand the build-tools module concept. Can someone
please help?
How does the jalopy.xml in build-tools get used on the other modules?
--
---
Thanks,
Mick Knutson
http://www.baselogic.com
Hello Guillaume,
I must say I've tried both with almost equal success, the one positive
advantage of the hierarchical option is that it allows the option of having
multiple depths of hierarchy without the quick growth of the number of
folders on a level. It also helps organize the structure when th
laume
From: Walid "jo" Gedeon [mailto:[EMAIL PROTECTED]
Sent: Fri 21/11/2008 7:14 PM
To: Maven Users List
Subject: Re: Maven multi-module setup hierarchical or flat folder hierarchy
Hello Guillaume,
I must say I've tried both with almost equal succe
On 7/11/07, Mick Knutson <[EMAIL PROTECTED]> wrote:
I have been looking at
http://mojo.codehaus.org/jalopy-maven-plugin/multimodule.html
And I really don't understand the build-tools module concept. Can someone
please help?
How does the jalopy.xml in build-tools get used on the other modules?
Can you describe this:
gt2/jalopy.xml
Is the jar called gt2?
On 7/11/07, Wendy Smoak <[EMAIL PROTECTED]> wrote:
On 7/11/07, Mick Knutson <[EMAIL PROTECTED]> wrote:
> I have been looking at
> http://mojo.codehaus.org/jalopy-maven-plugin/multimodule.html
>
> And I really don't understand the
And why should I not use:
http://mirrors.ibiblio.org/pub/mirrors/maven2/maven/maven-jalopy-plugin/1.5.1/
On 7/11/07, Wendy Smoak <[EMAIL PROTECTED]> wrote:
On 7/11/07, Mick Knutson <[EMAIL PROTECTED]> wrote:
> I have been looking at
> http://mojo.codehaus.org/jalopy-maven-plugin/multimodule
On 7/11/07, Mick Knutson <[EMAIL PROTECTED]> wrote:
Can you describe this:
gt2/jalopy.xml
Is the jar called gt2?
My guess is that the jar contains a directory called gt2. Adding the
build-config jar as a dependency will put its contents on the
classpath, where the files can be read by the pl
Hi,
I'm trying to use Maven2 for a new project I'm working on and so far
I'm very impressed with it, but I have found a couple of problems. Problems
that are probably down to user error and mis-configuration.
First of these problems is that with the project setup in a
multi-mod
Warning: This method may not be a long term solution but works today for me.
To get rid of the slow-down when there is no POM in your local repository I
did the following.
1) Create a default/do-nothing POM for the jars. Here is the one for my
Websphere 6.0.0 j2ee.jar.
4.0.0
com.ibm.websphe
List
Cc: [EMAIL PROTECTED]
Subject: Re: M2: Build error when building an individual module in a
multi-module setup
Warning: This method may not be a long term solution but works today for me.
To get rid of the slow-down when there is no POM in your local repository I
did the following.
1) Create
21 matches
Mail list logo
