Antw: Re: Re: Corrupted Assembly, when using a type:pom dependency
Hi Curtis,
yes, that's right. I want do declare a set of dependencies, which always must
be used all or none. That why I encapsulate those dependencies in a
separate pom and reference it with a type=pom dependency.
I didn't know about this scope import before and found your link very
infomative! Thanks!
Unfortunately, the assembly still gets corrupted, as soon as I have a type=pom
dependency in my configuration... with or without scope=import.
Any other suggestions?
Regards,
Stefan
Curtis Rueden ctrue...@wisc.edu 11.10.2012 18:05
Hi Stefan,
dependency
groupIdde.hhla.test/groupId
artifactIdtest.assembly.core/artifactId
version0.0.1-SNAPSHOT/version
typepom/type
/dependency
Personally, I have never used a dependency of type pom. But according to
the Maven docs, the main use case for it is as a shortcut to import a group
of dependencies transitively from that POM project. But in that case, you
would declare that dependency with scope import; see:
http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Importing_Dependencies
Is that what you are trying to do? If you use scope import, does the
problem go away? 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 few weeks ago. Can anyone help me with this?
---
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
useAllReactorProjectstrue/useAllReactorProjects
includes
include${artifact.groupId}:test.assembly.server/include
/includes
binaries
outputDirectory./outputDirectory
unpackfalse/unpack
outputFileNameMapping${module.artifactId}.${module.extension}
/outputFileNameMapping
/binaries
/moduleSet
/moduleSets
/assembly
The module I select in this assembly.xml contains one dependency:
dependency
groupIdde.hhla.test/groupId
artifactIdtest.assembly.core/artifactId
version0.0.1-SNAPSHOT/version
typepom/type
/dependency
The resulting assembly is unusable, as soon as the following two conditions
are
true:
- The module has a dependency with typepom/type
AND
- The outputDirectory of the moduleSet is .
In this case, the resulting assembly (e. g. zip file) looks like this:
ZIP
|
|--
||-- test.assembly.server.jar
|
|-- test.assembly.server.jar
The file test.assembly.server.jar, which is contained in that directory with
an empty name, is not actually a jar, but the POM of the dependency, which I
specified with typepom/type !!! That's totally weird, isn't it?
Extracting this zip structure leads to a corrupted test.assembly.server.jar,
because the first jar in the dir with no name (which actually is an XML file)
overwrites the correct jar at the actual root level of the zip file.
Another hint is this debug output of the assembly plugin:
[DEBUG] Adding file: C:\Dokumente und
Einstellungen\user\.m2\repository\de\hhla\test\test.assembly.core\0.0.1-SNAPSHOT\test.assembly.core-0.0.1-SNAPSHOT.pom
to archive location: TEST_0.0.1-SNAPSHOT//test.assembly.server.jar
(Please notice the two slashes in the destination path.)
Is this already a known issue or should I file a bug?
Thanks and best regards,
Stefan
---
Thanks and best regards
Stefan
tobias maslowski tobiasmaslow...@gmail.com 08.10.2012 11:45
You probably should provide some information about your problem, like what
you tried to do, the setup ...
Anyway there are a few issues 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
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Antw: Re: Corrupted Assembly, when using a type:pom dependency
Sorry, I didn't notice, that my original posting wasn't attached to my last
email.
Here is again, what I asked few weeks ago. Can anyone help me with this?
---
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
useAllReactorProjectstrue/useAllReactorProjects includes
include${artifact.groupId}:test.assembly.server/include /includes
binaries outputDirectory./outputDirectory unpackfalse/unpack
outputFileNameMapping${module.artifactId}.${module.extension}
/outputFileNameMapping /binaries /moduleSet /moduleSets/assembly The
module I select in this assembly.xml contains one dependency:dependency
groupIdde.hhla.test/groupId artifactIdtest.assembly.core/artifactId
version0.0.1-SNAPSHOT/version typepom/type/dependency The resulting
assembly is unusable, as soon as the following two conditions are true: - The
module has a dependency with typepom/typeAND - The outputDirectory of the
moduleSet is . In this case, the resulting assembly (e. g. zip file) looks
like this: ZIP | |-- | |-- test.assembly.server.jar | |--
test.assembly.server.jar The file test.assembly.server.jar, which is
contained in that directory with an empty name, is not actually a jar, but the
POM of the dependency, which I specified with typepom/type !!! That's
totally weird, isn't it? Extracting this zip structure leads to a corrupted
test.assembly.server.jar, because the first jar in the dir with no name
(which actually is an XML file) overwrites the correct jar at the actual root
level of the zip file. Another hint is this debug output of the assembly
plugin: [DEBUG] Adding file: C:\Dokumente und
Einstellungen\user\.m2\repository\de\hhla\test\test.assembly.core\0.0.1-SNAPSHOT\test.assembly.core-0.0.1-SNAPSHOT.pom
to archive location: TEST_0.0.1-SNAPSHOT//test.assembly.server.jar (Please
notice the two slashes in the destination path.) Is this already a known issue
or should I file a bug? Thanks and best regards, Stefan---
Thanks and best regards
Stefan
tobias maslowski tobiasmaslow...@gmail.com 08.10.2012 11:45
You probably should provide some information about your problem, like what
you tried to do, the setup ...
Anyway there are a few issues 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
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Corrupted Assembly, when using a type:pom dependency
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
Corrupted Assembly, when using a type:pom dependency
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
useAllReactorProjectstrue/useAllReactorProjects
includes
include${artifact.groupId}:test.assembly.server/include
/includes
binaries
outputDirectory./outputDirectory
unpackfalse/unpack
outputFileNameMapping${module.artifactId}.${module.extension}
/outputFileNameMapping
/binaries
/moduleSet
/moduleSets
/assembly
The module I select in this assembly.xml contains one dependency:
dependency
groupIdde.hhla.test/groupId
artifactIdtest.assembly.core/artifactId
version0.0.1-SNAPSHOT/version
typepom/type
/dependency
The resulting assembly is unusable, as soon as the following two conditions are
true:
- The module has a dependency with typepom/type
AND
- The outputDirectory of the moduleSet is .
In this case, the resulting assembly (e. g. zip file) looks like this:
ZIP
|
|--
||-- test.assembly.server.jar
|
|-- test.assembly.server.jar
The file test.assembly.server.jar, which is contained in that directory with
an empty name, is not actually a jar, but the POM of the dependency, which I
specified with typepom/type !!! That's totally weird, isn't it?
Extracting this zip structure leads to a corrupted test.assembly.server.jar,
because the first jar in the dir with no name (which actually is an XML file)
overwrites the correct jar at the actual root level of the zip file.
Another hint is this debug output of the assembly plugin:
[DEBUG] Adding file: C:\Dokumente und
Einstellungen\user\.m2\repository\de\hhla\test\test.assembly.core\0.0.1-SNAPSHOT\test.assembly.core-0.0.1-SNAPSHOT.pom
to archive location: TEST_0.0.1-SNAPSHOT//test.assembly.server.jar
(Please notice the two slashes in the destination path.)
Is this already a known issue or should I file a bug?
Thanks and best regards,
Stefan
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Antw: LinkageError in Surefire-Plugin in spite of forking
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 test were really skipped). But still playing with the forkMode and childDelegation options doesn't help to get the tests running. I still get 'java.lang.LinkageError: loader constraints violated when linking org/xml/sax/InputSource class'. Is there anyone, who can help? Thanks, Stefan [EMAIL PROTECTED] 06.02.2006 16:57:29 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 configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-surefire-plugin/artifactId configuration forkModeonce/forkMode /configuration /plugin Unfortunately this doesn't change anything, I still have the same error. Do you have any other suggestions, what the origin of the problem could be? Thanks a lot for your help! regards, Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Antw: LinkageError in Surefire-Plugin in spite of forking
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 execution. Bye, Stefan [EMAIL PROTECTED] 09.02.2006 09:44:19 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 test were really skipped). But still playing with the forkMode and childDelegation options doesn't help to get the tests running. I still get 'java.lang.LinkageError: loader constraints violated when linking org/xml/sax/InputSource class'. Is there anyone, who can help? Thanks, Stefan [EMAIL PROTECTED] 06.02.2006 16:57:29 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 configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-surefire-plugin/artifactId configuration forkModeonce/forkMode /configuration /plugin Unfortunately this doesn't change anything, I still have the same error. Do you have any other suggestions, what the origin of the problem could be? Thanks a lot for your help! regards, Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
LinkageError in Surefire-Plugin in spite of forking
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 configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-surefire-plugin/artifactId configuration forkModeonce/forkMode /configuration /plugin Unfortunately this doesn't change anything, I still have the same error. Do you have any other suggestions, what the origin of the problem could be? Thanks a lot for your help! regards, Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[M2] Failed to validate POM of an ejb-project, when packaging the enclosing ear-project
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 that warning, the dependent libraries of the ejb-project are not included in the ear): [WARNING] POM for: 'de.hhla.smd:hhla.smd.bl:pom:1.0-beta-1-SNAPSHOT' does not appear to be valid. Its will be ignored for artifact resolution. Reason: Failed to validate POM Below you find the complete output of mvn package and the pom of the ejb- and ear-project. What is wrong with the POM of the ejb-project? Thanks a lot for your help! Regards, Stefan __ [INFO] Scanning for projects... [INFO] [INFO] Building Maven Quick Start Archetype [INFO]task-segment: [package] [INFO] [WARNING] POM for: 'de.hhla.smd:hhla.smd.bl:pom:1.0-beta-1-SNAPSHOT' does not appear to be valid. Its will be ignored for artifact resolution. Reason: Failed to validate POM [INFO] [ear:generate-application-xml] [INFO] Generating application.xml [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [WARNING] POM for: 'de.hhla.smd:hhla.smd.bl:pom:1.0-beta-1-SNAPSHOT' does not appear to be valid. Its will be ignored for artifact resolution. Reason: Failed to validate POM [INFO] [ear:ear] [INFO] Copying artifact[ejb:de.hhla.smd:hhla.smd.bl:1.0-beta-1-SNAPSHOT] to[hhla.smd.bl-1.0-beta-1-SNAPSHOT.jar] [INFO] Could not find manifest file: D:\Schiffsmeldedienst\ws_maven\hhla.smd\hhla.smd.application\src\main\application\META-INF\MA NIFEST.MF - Generating one [INFO] Building jar: D:\Schiffsmeldedienst\ws_maven\hhla.smd\hhla.smd.application\target\hhla.smd.application-1.0-SNAPSHOT.ear [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 1 second [INFO] Finished at: Thu Jan 26 11:30:57 CET 2006 [INFO] Final Memory: 3M/6M [INFO] __ project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion parent groupIdde.hhla.smd/groupId artifactIdhhla.smd/artifactId version1.0-beta-1-SNAPSHOT/version /parent groupIdde.hhla.smd/groupId artifactIdhhla.smd.bl/artifactId packagingejb/packaging version1.0-beta-1-SNAPSHOT/version namehhla.smd.bl/name dependencies dependency groupIdweblogic/groupId artifactIdweblogic/artifactId /dependency dependency groupIdjunit/groupId artifactIdjunit/artifactId scopetest/scope /dependency dependency groupIdlog4j/groupId artifactIdlog4j/artifactId /dependency dependency groupIdxstream/groupId artifactIdxstream/artifactId version1.1.2/version /dependency dependency groupIdde.hhla.smd/groupId artifactIdhhla.smd.core/artifactId version1.0-beta-1-SNAPSHOT/version /dependency dependency groupIdde.hhla.smd/groupId artifactIdhhla.smd.dao/artifactId version1.0-beta-1-SNAPSHOT/version /dependency dependency groupIdde.hhla.smd/groupId artifactIdhhla.smd.bwaclient/artifactId version1.0-beta-1-SNAPSHOT/version /dependency dependency groupIdde.hhla.smd/groupId artifactIdhhla.smd.aisclient/artifactId version1.0-beta-1-SNAPSHOT/version /dependency /dependencies build plugins plugin artifactIdxdoclet-maven-plugin/artifactId
Antw: [M2] Failed to validate POM of an ejb-project, when packaging the enclosing ear-project
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 project. Consequently the ejb project can be installed without problems. But when want to package the ear-project, it also looks at the dependencies of the underlying ejb-project, in order to include its dependencies to the ear. Obiously the ear-plugin doesn't consider the ejb-projects' parent pom, where the versions and scopes are defined. So the packaging fails due to incomplete information of the ejb-projects' dependencies. If anyone can confirm, that this is a bug, I would creat a bug report in jira. Or is there anything wrong with my explanation? Thanks and regards, Stefan [EMAIL PROTECTED] 26.01.2006 13:18 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 that warning, the dependent libraries of the ejb-project are not included in the ear): [WARNING] POM for: 'de.hhla.smd:hhla.smd.bl:pom:1.0-beta-1-SNAPSHOT' does not appear to be valid. Its will be ignored for artifact resolution. Reason: Failed to validate POM Below you find the complete output of mvn package and the pom of the ejb- and ear-project. What is wrong with the POM of the ejb-project? Thanks a lot for your help! Regards, Stefan __ [INFO] Scanning for projects... [INFO] [INFO] Building Maven Quick Start Archetype [INFO]task-segment: [package] [INFO] [WARNING] POM for: 'de.hhla.smd:hhla.smd.bl:pom:1.0-beta-1-SNAPSHOT' does not appear to be valid. Its will be ignored for artifact resolution. Reason: Failed to validate POM [INFO] [ear:generate-application-xml] [INFO] Generating application.xml [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [WARNING] POM for: 'de.hhla.smd:hhla.smd.bl:pom:1.0-beta-1-SNAPSHOT' does not appear to be valid. Its will be ignored for artifact resolution. Reason: Failed to validate POM [INFO] [ear:ear] [INFO] Copying artifact[ejb:de.hhla.smd:hhla.smd.bl:1.0-beta-1-SNAPSHOT] to[hhla.smd.bl-1.0-beta-1-SNAPSHOT.jar] [INFO] Could not find manifest file: D:\Schiffsmeldedienst\ws_maven\hhla.smd\hhla.smd.application\src\main\application\META-INF\MA NIFEST.MF - Generating one [INFO] Building jar: D:\Schiffsmeldedienst\ws_maven\hhla.smd\hhla.smd.application\target\hhla.smd.application-1.0-SNAPSHOT.ear [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 1 second [INFO] Finished at: Thu Jan 26 11:30:57 CET 2006 [INFO] Final Memory: 3M/6M [INFO] __ project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion parent groupIdde.hhla.smd/groupId artifactIdhhla.smd/artifactId version1.0-beta-1-SNAPSHOT/version /parent groupIdde.hhla.smd/groupId artifactIdhhla.smd.bl/artifactId packagingejb/packaging version1.0-beta-1-SNAPSHOT/version namehhla.smd.bl/name dependencies dependency groupIdweblogic/groupId artifactIdweblogic/artifactId /dependency dependency groupIdjunit/groupId artifactIdjunit/artifactId scopetest/scope /dependency dependency groupIdlog4j/groupId artifactIdlog4j/artifactId /dependency dependency groupIdxstream/groupId artifactIdxstream/artifactId version1.1.2/version /dependency dependency groupIdde.hhla.smd/groupId artifactIdhhla.smd.core/artifactId version1.0-beta-1-SNAPSHOT/version
[M2] Problem with maven-ear-plugin: Artifact[_:_:ejb] is not a dependency of the project.
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 errors. But when I want to package the ear-project (see pom below), I get the error Artifact[de.hhla.smd:hhla.smd.bwaclient:ejb] is not a dependency of the project. But I added the two ejb projects as dependencies of my ear project. Could anybody tell me, what I'm doing wrong? Thanks a lot for your help! Regards, Stefan POM of the EAR project: project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdde.hhla.smd/groupId artifactIdhhla.smd.provider/artifactId namehhla.smd.provider/name version1.0-beta-1-SNAPSHOT/version packagingear/packaging dependencies dependency groupIdde.hhla.smd/groupId artifactIdhhla.smd.aisclient/artifactId version1.0-beta-1-SNAPSHOT/version /dependency dependency groupIdde.hhla.smd/groupId artifactIdhhla.smd.bwaclient/artifactId version1.0-beta-1-SNAPSHOT/version /dependency /dependencies build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-ear-plugin/artifactId configuration modules ejbModule groupIdde.hhla.smd/groupId artifactIdhhla.smd.bwaclient/artifactId /ejbModule ejbModule groupIdde.hhla.smd/groupId artifactIdhhla.smd.aisclient/artifactId /ejbModule /modules /configuration /plugin /plugins /build /project - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Antw: Re: [M2] Problem with maven-ear-plugin: Artifact[_ :_:ejb] is not a dependency of the project.
Hello,
here is the POM of one of the EJB projects. The other one looks almost
the same.
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
parent
groupIdde.hhla.smd/groupId
artifactIdhhla.smd.provider/artifactId
version1.0-beta-1-SNAPSHOT/version
/parent
groupIdde.hhla.smd/groupId
artifactIdhhla.smd.bwaclient/artifactId
packagingejb/packaging
version1.0-beta-1-SNAPSHOT/version
namehhla.smd.bwaclient/name
dependencies
dependency
groupIdweblogic/groupId
artifactIdweblogic/artifactId
version9.0/version
scopeprovided/scope
/dependency
dependency
groupIdweblogic/groupId
artifactIdwebserviceclient-ssl/artifactId
version9.0/version
scopeprovided/scope
/dependency
dependency
groupIdjunit/groupId
artifactIdjunit/artifactId
version3.8.1/version
scopetest/scope
/dependency
/dependencies
build
plugins
plugin
artifactIdxdoclet-maven-plugin/artifactId
groupIdorg.codehaus.mojo/groupId
version1.0-alpha-2/version
executions
execution
phasegenerate-sources/phase
goals
goalxdoclet/goal
/goals
configuration
tasks
ejbdoclet
destdir=${basedir}/target/generated-sources/xdoclet
addedTags=@xdoclet-generated at ${TODAY},@copyright The XDoclet
Team,@author XDoclet,@version ${version}
excludedTags=@version,@author,@todo verbose=true
fileset
dir=${basedir}/src/main/java includes=**/*SB.java /
entitycmp
destDir=${basedir}/target/generated-sources/xdoclet /
deploymentdescriptor
destDir=${basedir}/target/classes/META-INF /
weblogic
destDir=${basedir}/target/classes/META-INF /
homeinterface
/
localhomeinterface
/
localinterface
/
remoteinterface
/
session
/
utilobject
cacheHomes=true includeGUID=true /
valueobject
/
/ejbdoclet
/tasks
/configuration
/execution
/executions
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-ejb-plugin/artifactId
configuration
generateClienttrue/generateClient
/configuration
/plugin
/plugins
/build
/project
[EMAIL PROTECTED] 16.01.2006 14:02
Hello,
I've got 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-plugin: Artifact[_:_:ejb] is
not a dependency of the project.
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
Antw: [M2] loader constraints violated when linking org/xml/sax/InputSource class
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 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 know what to do in Maven 2. First of all I would like to understand the reason of this error. The dependencies of my project are junit-3.8.1.jar weblogic-9.0.jar (It's the weblogic.jar of WLS 9 from my local repository) webserviceclient-ssl-9.0.jar (also from WLS 9) and I use JDK 1.5_05. The class org.xml.sax.InputSource is in both, the webserviceclient-ssl-9.0-jar and the JRE 1.5. Does it have anything to do with that? Thanks in advance for your help! Regards, Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
loader constraints violated when linking org/xml/sax/InputSource class
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 know what to do in Maven 2. First of all I would like to understand the reason of this error. The dependencies of my project are junit-3.8.1.jar weblogic-9.0.jar (It's the weblogic.jar of WLS 9 from my local repository) webserviceclient-ssl-9.0.jar (also from WLS 9) and I use JDK 1.5_05. The class org.xml.sax.InputSource is in both, the webserviceclient-ssl-9.0-jar and the JRE 1.5. Does it have anything to do with that? Thanks in advance for your help! Regards, Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Antw: RE: How can I create ejb-jar and ejb-client-jar withmaven-ejb-plugin in Maven 2?
Hello Aramirez, I already received a reply on my question. The given solution was to specify the destDir attribute of deploymentdescriptor. This works fine, I just thought there might be a better solution (e.g. generating the deployment descriptors to generated-sources/xdoclet and moving them during compile, along with the generation of the class files). But there doesn't seem to be a need for a jira issue. Thanks, Stefan [EMAIL PROTECTED] 06.01.2006 09:21:10 Hi, Currently, I dont think that we can configure the deployment descriptor path, Please file a jira issue if not yet existing. 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/META-INF but the files are generated by xdoclet-maven-plugin to target/generated-sources/xdoclet/META-INF. What is the right way to make the maven-ejb-plugin find the deployment descriptors? Thanks for your help! Bye, Stefan [EMAIL PROTECTED] 05.01.2006 12:24:48 To generate both jars, you need to tell the plugin that you want both of them as follows: project ... build ... plugins ... plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-ejb-plugin/artifactId configuration generateClienttrue/generateClient /configuration /plugin ... 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 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 maven and don't understand the usage example given on plugins' webpage (http://maven.apache.org/plugins/maven-ejb-plugin/howto.html). When I integrate that XML to my POM, nothing happens. Only calling 'mvn ejb:ejb' manually works, as long as I copy the META-INF-folder from 'target/generated-sources/xdoclet' to 'target/classes' first. How can I integrate this into my build process (mvn package: ejb-jar and ejb-client-jar are generated. mvn install: ejb-jar and ejb-client-jar are copied to my local repository...)? Thanks a lot in advance! Regards, Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How can I create ejb-jar and ejb-client-jar with maven-ejb-plugin in Maven 2?
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 maven and don't understand the usage example given on plugins' webpage (http://maven.apache.org/plugins/maven-ejb-plugin/howto.html). When I integrate that XML to my POM, nothing happens. Only calling 'mvn ejb:ejb' manually works, as long as I copy the META-INF-folder from 'target/generated-sources/xdoclet' to 'target/classes' first. How can I integrate this into my build process (mvn package: ejb-jar and ejb-client-jar are generated. mvn install: ejb-jar and ejb-client-jar are copied to my local repository...)? Thanks a lot in advance! Regards, Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Antw: RE: How can I create ejb-jar and ejb-client-jar withmaven-ejb-plugin in Maven 2?
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/META-INF but the files are generated by xdoclet-maven-plugin to target/generated-sources/xdoclet/META-INF. What is the right way to make the maven-ejb-plugin find the deployment descriptors? Thanks for your help! Bye, Stefan [EMAIL PROTECTED] 05.01.2006 12:24:48 To generate both jars, you need to tell the plugin that you want both of them as follows: project ... build ... plugins ... plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-ejb-plugin/artifactId configuration generateClienttrue/generateClient /configuration /plugin ... 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 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 maven and don't understand the usage example given on plugins' webpage (http://maven.apache.org/plugins/maven-ejb-plugin/howto.html). When I integrate that XML to my POM, nothing happens. Only calling 'mvn ejb:ejb' manually works, as long as I copy the META-INF-folder from 'target/generated-sources/xdoclet' to 'target/classes' first. How can I integrate this into my build process (mvn package: ejb-jar and ejb-client-jar are generated. mvn install: ejb-jar and ejb-client-jar are copied to my local repository...)? Thanks a lot in advance! Regards, Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Antw: RE: Which variables are available, e.g. for thexdoclet-maven-plugin?
Hi,
thanks for your reply. It was already a little helpful. But I have one
further question:
Obviously I can't find out all available variables in this way. For example the
variable ${java.home} (which is used on
http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html)
is available, but is set somwhere else.
Does anybody know, where these variables are initialized and where I can find
them? Additionally I would like to set some variables on my own. I just don't
understand the mechanism behind this.
thanks a lot in advance,
Stefan
[EMAIL PROTECTED] 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 [mailto:[EMAIL PROTECTED]
Sent: segunda-feira, 19 de dezembro de 2005 13:35
To: Maven Users List
Subject: Which variables are available, e.g. for
thexdoclet-maven-plugin?
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 can tell me.
Bye,
Stefan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Which variables are available, e.g. for the xdoclet-maven-plugin?
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 can tell me.
Bye,
Stefan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
XDoclet-Problem: This artifact has been relocated to javax.servlet:servlet-api:2.3
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
[INFO]task-segment: [package]
[INFO]
[INFO] snapshot de.hhla.smd:hhla.smd.provider:1.0-beta-1-SNAPSHOT:
checking for updates from mavenrepo
[WARNING]
This artifact has been relocated to javax.servlet:servlet-api:2.3.
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] null
[INFO]
[INFO] Trace
java.lang.AbstractMethodError
at
org.codehaus.plexus.component.configurator.converters.ComponentValueSetter.configure(ComponentValueSetter.java:247)
at
org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.processConfiguration(ObjectWi
thFieldsConverter.java:137)
at
org.codehaus.plexus.component.configurator.BasicComponentConfigurator.configureComponent(BasicComponentConfigurator.jav
a:56)
at
org.apache.maven.plugin.DefaultPluginManager.populatePluginFields(DefaultPluginManager.java:1038)
at
org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:563)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:377)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:519)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:469)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:448)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:301)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:268)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:137)
at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316)
at
org.apache.maven.DefaultMaven.execute(DefaultMaven.java:113)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
[INFO]
[INFO] Total time: 17 seconds
[INFO] Finished at: Fri Dec 16 09:42:25 CET 2005
[INFO] Final Memory: 5M/10M
[INFO]
---
I already resolved one error, that came up because of a wrong
dependency to the commons-logging.
I don't understand the message This artifact has been relocated to
javax.servlet:servlet-api:2.3.. Where is the origin of this error? Here
is the xml of the xdoclet plugin in my pom:
---
execution
phasegenerate-sources/phase
goals
goalxdoclet/goal
/goals
configuration
tasks
ejbdoclet
destdir=${project.build.outputDirectory}
addedTags=@xdoclet-generated
at ${TODAY},@copyright The XDoclet Team,@author XDoclet,@version
${version}
excludedTags=@version,@author,@todo
verbose=true
fileset
dir=${basedir}/src/main/java
Antw: Re: XDoclet-Problem: This artifact has been relocated to javax.servlet:servlet-api:2.3
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: This artifact has been relocated to javax.servlet:servlet-api:2.3. That's not an error message. That's simply a warning. Most probably you are still using the group ID servletapi, or something like that. Change groupId, artifactId, and version as given in the warning and it will immediately vanish. java.lang.AbstractMethodError That's a completely different beast. Try using the -X flag, if you can find any additional informations. It might be a bug in some plugin. Jochen -- Often it does seem a pity that Noah and his party did not miss the boat. (Mark Twain) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Antw: Re: XDoclet-Problem: This artifact has been relocated to javax.servlet:servlet-api:2.3
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 Rademacher [EMAIL PROTECTED] wrote: This artifact has been relocated to javax.servlet:servlet-api:2.3. That's not an error message. That's simply a warning. Most probably you are still using the group ID servletapi, or something like that. Change groupId, artifactId, and version as given in the warning and it will immediately vanish. java.lang.AbstractMethodError That's a completely different beast. Try using the -X flag, if you can find any additional informations. It might be a bug in some plugin. Jochen -- Often it does seem a pity that Noah and his party did not miss the boat. (Mark Twain) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
