Hello everybody,
I have a problem with inheritance of dependencies from the parent pom. I
have a multi-module project. The situation is that I need 2 jdbc drivers: an
older version (9.xxx) and a newer version (10.xxx). I declared these
dependencies in the parent pom like this:
com.or
Well, we are migrating a very old project from ant to maven. It is a multi
module project (ca. 17 modules). We can already compile and use the whole
project, so we are sure that our new maven "multi-module-structure" works
right. The next target is that the project should be delivered as a set of
d
What are you trying to build?
Unless you are building something that is really off-beat, you should
just be able to follow best practices.
Most people do not need to do what you are doing.
You seem to heading down a bizarre development path that is likely not
needed and going to set up a comp
I need not only dependenciesSets, but also fileSets...
2011/4/28 Anders Hammar
> You should not traverse the file structure but rely on dependencies! It
> should work building when just checking out this specific module from scm.
>
> /Anders
>
> On Thu, Apr 28, 2011 at 18:01, Dmitriy Neretin <
>
You should not traverse the file structure but rely on dependencies! It
should work building when just checking out this specific module from scm.
/Anders
On Thu, Apr 28, 2011 at 18:01, Dmitriy Neretin <
dmitriy.nere...@googlemail.com> wrote:
> Holy sh... :)) Of cource it works :) But it is not
Holy sh... :)) Of cource it works :) But it is not really that what I wanted
but it's not important now :) Thank you very much. But I still don't
understand why the moduleSet didn't work... Strange (How old is the maven
documentation). With this variable ${project.parent.basedir} I can get
acce
No, you should not use moduleSet but dependencySet (or similar, I'm not at
my computer and cannot check syntax).
/Anders (mobile)
Den 28 apr 2011 17.14 skrev "Dmitriy Neretin" <
dmitriy.nere...@googlemail.com>:
> Well I just removed the assembly declaration from the parent POM. I just
> left there
Well I just removed the assembly declaration from the parent POM. I just
left there the new distribution module. When I change to the distribution
folder and execute mvn assembly:single or mvn clean package I get this:
[INFO] Reading assembly descriptor: config/assembly.xml
[WARNING] The following
Ok, the log output indicates that the assembly is executed twice (there is a
warning about the same id used twice).
Start by removing any assembly configuration from your parent, to keep
things simple. Just add it yo your module. When you get that to work you
could start by doing advanced stuff.
/
Thanks for the reply!
2011/4/28 Anders Hammar
> The "declaration" in your parent, is that a binding? Or is it in
> pluginManagement?
>
Well I don't really understand what do you mean with binding :) The assembly
plugin is declared between the tags:
Assembly declaration
>
> Why are confi
The "declaration" in your parent, is that a binding? Or is it in
pluginManagement?
Why are configuring the descriptor in the parent? Are you trying to make an
assembly in the parent as well as in the child?
/Anders
On Thu, Apr 28, 2011 at 15:03, Dmitriy Neretin <
dmitriy.nere...@googlemail.com> w
Hello everybody,
I have a problem with the assembly plugin. I used the following
documentation:
http://maven.apache.org/plugins/maven-assembly-plugin/examples/multimodule/module-binary-inclusion-simple.html
I created the additional module to keep my assembly in the parent POM:
...
A
B
C
dis
rsion}
Thanks,
mohan kr
-Original Message-
From: Alexander Vaysberg [mailto:w...@vaisberg.de]
Sent: Wednesday, July 01, 2009 2:42 AM
To: Maven Users List
Subject: maven assembly plugin problem.
Hi,
I have a problem with assembly plugin. I have a standalone application
and I make for this
-
From: Alexander Vaysberg [mailto:w...@vaisberg.de]
Sent: Wednesday, July 01, 2009 2:42 AM
To: Maven Users List
Subject: maven assembly plugin problem.
Hi,
I have a problem with assembly plugin. I have a standalone application
and I make for this app a jar with manifest. In manifest set I a
Hi,
I have a problem with assembly plugin. I have a standalone application
and I make for this app a jar with manifest. In manifest set I a
Main-Class and all dependencies for this app with jar plugin. That work
fine. Than, I create with assembly the zip and get the all dependencies
in lib.
On 7/5/06, Arnaud Bailly <[EMAIL PROTECTED]> wrote:
nazim chakik <[EMAIL PROTECTED]> writes:
May be the following assembly descriptor can help you:
bin
tar.gz
zip
false
pom.xml
src/
true
I've never used module sets.
I
nazim chakik <[EMAIL PROTECTED]> writes:
May be the following assembly descriptor can help you:
bin
tar.gz
zip
false
pom.xml
src/
true
regards,
--
OQube < software engineering \ génie logiciel >
Arnaud Bailly, Dr.
\web>
descripteur.xml
bin
jar
false
..
../ife-asp/target
lib
*.jar
true
..
*
Hi,
indeed i want all dependency jars in a 'lib' directory in the assembly.
here my poms and my descriptor:
ROOT POM*
...
../ife-asp
../ife-aspstruts
..
...
${basedir}/src/java
${basedir}/
Hi,
it would help if you could post your pom.xml with the assembly plugin configuration and
your assembly descriptor. Also you should describe how you expect the final assembly to
look like. Do you want to create just one jar file that contains your classes + the
classes of the dependencies (y
Should help you :
http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html
On 6/30/06, nazim chakik <[EMAIL PROTECTED]> wrote:
Hello,
I use the maven's assembly plugin and I have the following problem: I have
several projects which are modules of one main project containing
Hello,
I use the maven's assembly plugin and I have the following problem: I have
several projects which are modules of one main project containing the pom
root. Each module has its own dependencies ,
When I run the command: (mvn assembly:assembly) on the root pom, I recover
the su
22 matches
Mail list logo