? If scope import is not what you want, I am curious why you
are using a dependency of type pom.
Regards,
Curtis
On Thu, Oct 11, 2012 at 3:53 AM, Stefan Rademacher rademac...@hhla.dewrote:
Sorry, I didn't notice, that my original posting wasn't attached to my
last email.
Here is again, what I asked
in the tracker, maybe you stumbled accross
http://jira.codehaus.org/browse/MASSEMBLY-609?
2012/10/8 Stefan Rademacher rademac...@hhla.de
Hi,
is there nobody, who can confirm, if this is a known issue?
Thanks,
Stefan
Hi,
is there nobody, who can confirm, if this is a known issue?
Thanks,
Stefan
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Hi all,
I want to create an assembly, using a moduleSet. With the following
(simplified) example, I select a certain artifact, define the output directory
and provide a naming pattern.
assembly
iddistribution/id
formats
formatzip/format
/formats
moduleSets
moduleSet
Hello,
sorry, I forgot to mention, that I work with Maven 2.0.2.
I'm still searching for the reason of the issue with the surefire
plugin. I use the latest version of the plugin and checked, that the
configuration in the projects pom is really recognized (by using
skiptrue/skip I saw, that the
Hello,
I solved the problem. As far as I know, in the latest version the
surefire plugin has forking as a default setting. In my pom I still
configured the plugin explicitly, as mentioned below.
For some reason, the explicit setting of forkModeonce/forkMode
leads to an error, during the test
Hello,
I have some JUnit tests, that fail with a LinkageError: loader
constraints violated when linking org/xml/sax/Parser class.
As described in the documentation and other threads in the mailing
list, I set forking to once, in order to run the tests in a separate
JVM. Here is the plugin
Hello,
I have an ejb-project (hhla.smd.bl) and an ear-project
(hhla.smd.application) which has a dependency to this ejb-project.
Installing the ejb-project to my local repository works fine, but when I
execute mvn package on the ear-project, the POM of the ejb-project
cannot be validated (Due to
Hello,
I found the origin of the problem, described below, am I right, that
it's a bug in the maven-ear-plugin?
The ejb-project has dependencies, e.g. to log4j and to a weblogic.jar
in my local repository, without version- and scope-element. Version and
scope are defined in the pom of the parent
Hello,
I have a problem, when I try creating an EAR file, that includes two
EJB modules. Nobody else seems to have this issue, so there might be an
easy solution...
I have a project with packaging=ear and two projects with
packaging=ejb. When I package the ejb projects separately, there are no
no answer for your question unfortunately. However I would
like to ask you for source of your ejb POM's (from ejb modules) - it
would help me much.
Thanks,
Pawel
Od: Stefan Rademacher [EMAIL PROTECTED]
Do: users@maven.apache.org
Data: Mon, 16 Jan 2006 13:31:27 +0100
Temat: [M2] Problem with maven-ear
Hello,
I still have no idea, what the error described below is about. Is there
anyone with any suggestions?
Thank you,
Stefan
[EMAIL PROTECTED] 09.01.2006 15:58:31
Hello *,
when running the JUnit tests of my project with maven, I get the
following error (JUnit tests within Eclipse work
Hello *,
when running the JUnit tests of my project with maven, I get the
following error (JUnit tests within Eclipse work fine):
loader constraints violated when linking org/xml/sax/InputSource
class
On the internet I found some solutions (without detailed explanation)
for maven 1, but I don't
.
Thanks,
-allan
Stefan Rademacher wrote:
Hello,
thank you. I already had this code in my POM but the packaging was
set
to jar. Now I changed it to ejb and it works fine. Now there is
one
more problem. The maven-ejb-plugin doesn't find the deployment
descriptors. It searches in target/classes
Hello,
Could anyone provide me with a working example of a project, which uses
the maven-ejb-plugin to generate jar files for the ejb-module and for
the ejb-client?
(I use the xdoclet-maven-plugin to generate the ejb artifacts to the
folder 'targets/generated-sources/xdoclet')
I'm quite new to
...
plugins
...
/build
...
/project
-Original Message-
From: Stefan Rademacher [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 05, 2006 03:14
To: Maven Users List
Subject: How can I create ejb-jar and ejb-client-jar
withmaven-ejb-plugin in Maven 2?
Hello,
Could anyone provide
] 19.12.2005 19:56
Hi,
AFAIK this variable (project.build.outputDirectory) comes from pom.xml as
follows:
project
...
build
outputDirectorytarget/classes/outputDirectory
/build
...
/project
Hope this helps.
Dário
-Original Message-
From: Stefan Rademacher
Hello,
on the page for the xdoclet-maven-plugin there is an example, which
contains a variable ${project.build.outputDirectory}.
Where can I find out generally, which variables are available in a
pom.xml? And another question is: Can I define my own variables
somwhere?
Would be great, if anyone
Hello,
I am trying to get the xdoclet-maven-plugin 1.0-alpha-1 working. But a
mvn package ends up with the following error messages:
-
...
[INFO] Building hhla.smd.bl
Hello,
thank you, Jochen. I solved the first issue. After changing the depency
of the xdoclet-maven-plugin to the servlet-api in its pom-file, the
warning disappeared.
Best regards,
Stefan
[EMAIL PROTECTED] 16.12.2005 11:14
On 12/16/05, Stefan Rademacher [EMAIL PROTECTED] wrote
Hello,
I found a workaround for the AbstractMethodError on
http://www.nabble.com/xdoclet-maven-plugin-%3E-maven2-t432992.html#a1186055
If anyone knows, if this is a better way to get the plugin to work, pls
let me know.
Regards,
Stefan
[EMAIL PROTECTED] 16.12.2005 11:14
On 12/16/05, Stefan
21 matches
Mail list logo
