On Tuesday 01 July 2008 Michael McCallum wrote:
On Tue, Jul 1, 2008 at 2:58 PM, Martin Höller [EMAIL PROTECTED] wrote:
I think I found one BIG problem with your workaround: it only works
if you already have (the latest version of) your WAR's pom.xml file
in the repository, otherwise
Hi Arnaud!
I think I found one BIG problem with your workaround: it only works if you
already have (the latest version of) your WAR's pom.xml file in the
repository, otherwise maven 2.0.9 reports a missing dependency.
So this approach is not useable with the maven-release-plugin :-(
I made up
My workaround is more a hack that something else.
It's not really logical to have in a project to dependencies to a pom and a
war of a same artifact.
This is certainly a bug in the core of maven which doesn't support it :-(
I'm trying to see how I can change the ear plugin to fix this issue.
On Tue, Jul 1, 2008 at 2:58 PM, Martin Höller [EMAIL PROTECTED] wrote:
I think I found one BIG problem with your workaround: it only works if
you already have (the latest version of) your WAR's pom.xml file in the
repository, otherwise maven 2.0.9 reports a missing dependency.
So this
Maybe I'm missing something but I thought the purpose of a skinny war was
to consolidate shared dependencies between several wars and some ejb jars.
If the new feature will build a jar in the same project as the war and that
jar contains dependencies there has to be some other feature that takes
Hello,
looks interesting. Are there any comments or recommendations from the Maven
Team?
Thanks for sharing.
Kuno
-Ursprüngliche Nachricht-
Von: Arnaud HERITIER [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 3. Juni 2008 19:31
An: Maven Users List
Betreff: Tip about Skinny Wars
Hi all
i'm wondering if the solution would render the war-path plugin
obsolete? it's causing trouble in embedded use.
http://issues.appfuse.org/browse/APF-645
Milos
On 6/3/08, Arnaud HERITIER [EMAIL PROTECTED] wrote:
Hi all,
I would like to share with you a workaround I found for the problem of
, 4.6.2008:
Von: Milos Kleint [EMAIL PROTECTED]
Betreff: Re: Tip about Skinny Wars
An: Maven Users List users@maven.apache.org
Datum: Mittwoch, 4. Juni 2008, 11:17
i'm wondering if the solution would render the war-path
plugin
obsolete? it's causing trouble in embedded use.
http
Not totally.
It can fix : Automatically inherit transitive dependencies from the war
artifact (the default Maven behaviour is not to inherit transitively from
war dependencies).
But not : Develop with classes included in the war artifact /WEB-INF/classes
directory by including them in the project
FWIW, I used a slightly different approach in the cargo uberwar plugin
(which generates a War-of-Wars). I made it look at the WAR
dependencies, and create a 'phantom' pom projects in the repository,
which can then be passed to the normal maven dependency
reconciliation framework to work out what
I made additional tests and I found that it is another side effect of the
usage of the enforcer plugin (build from trunk rev 651824).
:-(
I will have a look at its code to see if this bug of the enforcer plugin can
become a feature in the war plugin ;-)
Arnaud
On Tue, Jun 3, 2008 at 7:31 PM,
with the maven-ear-plugin.
LieGrü,
strub
--- Arnaud HERITIER [EMAIL PROTECTED] schrieb am Mi, 4.6.2008:
Von: Arnaud HERITIER [EMAIL PROTECTED]
Betreff: Re: Tip about Skinny Wars - is an enforcer plugin's bug side effect
:-(
An: Maven Users List users@maven.apache.org
CC: Maven Developers List [EMAIL
: Tip about Skinny Wars - is an enforcer plugin's bug side
effect :-(
An: Maven Users List users@maven.apache.org
CC: Maven Developers List [EMAIL PROTECTED]
Datum: Mittwoch, 4. Juni 2008, 15:28
I made additional tests and I found that it is another side
effect of the
usage of the enforcer
Hi Arnaud,
Arnaud HERITIER wrote:
I think it is not the same problem.
MWAR-131 is about to reuse classes defined in a war.
attachClasses will generate a secondary artifact that we'll be able
to reuse as dependency in another project.
Yes, this other project might be the ear ...
The problem
ok I didn't think about that.
It can be a usable workaround.
Thx
Arnaud
On Wed, Jun 4, 2008 at 6:08 PM, Jörg Schaible
[EMAIL PROTECTED] wrote:
Hi Arnaud,
Arnaud HERITIER wrote:
I think it is not the same problem.
MWAR-131 is about to reuse classes defined in a war.
attachClasses will
Hi all,
I would like to share with you a workaround I found for the problem of
transitive dependencies in skinny wars.
In the documentation it is said that :
Now the painful part. Your EAR's pom.xml needs to list every
dependency that the WAR has.
This is because Maven assumes fat WARs and
16 matches
Mail list logo
