RE: Classpath issue in custom maven plugin
From: mgai...@hotmail.com
To: users@maven.apache.org
Subject: RE: Classpath issue in custom maven plugin
Date: Mon, 15 Sep 2014 18:49:41 -0400
Date: Mon, 15 Sep 2014 19:06:56 +0530
Subject: Classpath issue in custom maven plugin
From: kavita.gpt1...@gmail.com
To: users@maven.apache.org
CC: shailesh.man...@gmail.com
Hi!
I have created my own custom maven plugin(api-docs) for developing apiary
blueprint. While triggering my custom plugin using m2Eclipse I am getting a
classpath issue that classPath.getresources is fetching resources from plexus
jar, while when I debug the swagger plugin (which I am taking as a reference)
it is picking up the resources from rt.jar. In swagger I am getting
web/target/classes in URLS but in my custom project I am not getting the
web/target/classes in URLS. Code snippet is:
MGas previously mentioned...
If the tests pass on command line with maven 3.0.2 or newer but fail from m2e,
please open a
bugreport in https://bugs.eclipse.org/bugs/enter_bug.cgi?product=m2e
Make sure to attach complete standalone example project and steps to reproduce
the problem.
https://docs.sonatype.org/display/M2ECLIPSE/Runtime+classpath
MG
ClassLoader classLoader =
Thread.currentThread().getContextClassLoader();
System.out.println(classLoader.getResources(com/abc/service/rest/resource));
assert classLoader != null;String path = packageName.replace('.',
'/');EnumerationURL resources = classLoader.getResources(path);
My custom plugin's dependency tree is attached(apidocsTree.txt). I have
integrated it in my other project i.e web. Here is the web pom configuration
for the plugin.
plugin groupIdcom.thed/groupId
artifactIdapi-docs/artifactId version1.0-SNAPSHOT/version
configuration
packageNamecom.thed.service.rest.resource/packageName
vmFileapiary.vm/vmFile
outputFileName${basedir}/target/apiary.apib/outputFileName
/configuration executions execution
phaseprepare-package/phase goals
goalgenerateApiDocs/goal
/goals/execution/executions
/plugin
I am taking swagger-plugin as a reference. Its dependency tree is attached as
swaggerTree.txt. Its configuration in web is:plugin
groupIdcom.github.kongchen/groupId
artifactIdswagger-maven-plugin/artifactId version1.0-SNAPSHOT/version
configurationapiSources apiSource
apiPackagecom.thed.service.rest.resource/apiPackage
apiVersionv1/apiVersion
basePathhttp://localhost:8080/flex/services/rest/latest/basePath
outputTemplate${basedir}/src/site/docs/template/rest/zephyr_html.mustache/outputTemplate
outputPath${basedir}/src/main/webapp/data/rest-doc.html/outputPath
/apiSource /apiSources/configurationexecutions
execution phaseprepare-package/phase
goals goalgenerate/goal /goals
/execution/executions/plugin
Please provide me the input to solve this classpath issue.
--
Thanks, Kavita Gupta Agarwal
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Classpath issue in custom maven plugin
Limitation perhaps comes from OSGi where each bundle has its own class
loader. Did u try to run it from command line?
On Sep 15, 2014 6:36 AM, Kavita Gupta kavita.gpt1...@gmail.com wrote:
Hi!
I have created my own custom maven plugin(api-docs) for developing apiary
blueprint. While triggering my custom plugin using m2Eclipse I am getting a
classpath issue that classPath.getresources is fetching resources from
plexus jar, while when I debug the swagger plugin (which I am taking as a
reference) it is picking up the resources from rt.jar. In swagger I am
getting web/target/classes in URLS but in my custom project I am not
getting the web/target/classes in URLS. Code snippet is:
ClassLoader classLoader =
Thread.currentThread().getContextClassLoader();
System.out.println(classLoader.getResources(com/abc/service/rest/resource));
assert classLoader != null;
String path = packageName.replace('.', '/');
EnumerationURL resources = classLoader.getResources(path);
My custom plugin's dependency tree is attached(apidocsTree.txt). I have
integrated it in my other project i.e web. Here is the web pom
configuration for the plugin.
plugin
groupIdcom.thed/groupId
artifactIdapi-docs/artifactId
version1.0-SNAPSHOT/version
configuration
packageNamecom.thed.service.rest.resource/packageName
vmFileapiary.vm/vmFile
outputFileName${basedir}/target/apiary.apib/outputFileName
/configuration
executions
execution
phaseprepare-package/phase
goals
goalgenerateApiDocs/goal
/goals
/execution
/executions
/plugin
I am taking swagger-plugin as a reference. Its dependency tree is attached
as swaggerTree.txt. Its configuration in web is:
plugin
groupIdcom.github.kongchen/groupId
artifactIdswagger-maven-plugin/artifactId
version1.0-SNAPSHOT/version
configuration
apiSources
apiSource
apiPackagecom.thed.service.rest.resource/apiPackage
apiVersionv1/apiVersion
basePathhttp://localhost:8080/flex/services/rest/latest
/basePath
outputTemplate${basedir}/src/site/docs/template/rest/zephyr_html.mustache/outputTemplate
outputPath${basedir}/src/main/webapp/data/rest-doc.html/outputPath
/apiSource
/apiSources
/configuration
executions
execution
phaseprepare-package/phase
goals
goalgenerate/goal
/goals
/execution
/executions
/plugin
Please provide me the input to solve this classpath issue.
--
Thanks,
Kavita Gupta Agarwal
RE: Classpath issue in custom maven plugin
Date: Mon, 15 Sep 2014 19:06:56 +0530
Subject: Classpath issue in custom maven plugin
From: kavita.gpt1...@gmail.com
To: users@maven.apache.org
CC: shailesh.man...@gmail.com
Hi!
I have created my own custom maven plugin(api-docs) for developing apiary
blueprint. While triggering my custom plugin using m2Eclipse I am getting a
classpath issue that classPath.getresources is fetching resources from plexus
jar, while when I debug the swagger plugin (which I am taking as a reference)
it is picking up the resources from rt.jar. In swagger I am getting
web/target/classes in URLS but in my custom project I am not getting the
web/target/classes in URLS. Code snippet is:MG
ClassLoader classLoader =
Thread.currentThread().getContextClassLoader();
System.out.println(classLoader.getResources(com/abc/service/rest/resource));
assert classLoader != null;String path = packageName.replace('.',
'/');EnumerationURL resources = classLoader.getResources(path);
My custom plugin's dependency tree is attached(apidocsTree.txt). I have
integrated it in my other project i.e web. Here is the web pom configuration
for the plugin.
plugin groupIdcom.thed/groupId
artifactIdapi-docs/artifactId version1.0-SNAPSHOT/version
configuration
packageNamecom.thed.service.rest.resource/packageName
vmFileapiary.vm/vmFile
outputFileName${basedir}/target/apiary.apib/outputFileName
/configuration executions execution
phaseprepare-package/phase goals
goalgenerateApiDocs/goal
/goals/execution/executions
/plugin
I am taking swagger-plugin as a reference. Its dependency tree is attached as
swaggerTree.txt. Its configuration in web is:plugin
groupIdcom.github.kongchen/groupId
artifactIdswagger-maven-plugin/artifactId version1.0-SNAPSHOT/version
configurationapiSources apiSource
apiPackagecom.thed.service.rest.resource/apiPackage
apiVersionv1/apiVersion
basePathhttp://localhost:8080/flex/services/rest/latest/basePath
outputTemplate${basedir}/src/site/docs/template/rest/zephyr_html.mustache/outputTemplate
outputPath${basedir}/src/main/webapp/data/rest-doc.html/outputPath
/apiSource /apiSources/configurationexecutions
execution phaseprepare-package/phase
goals goalgenerate/goal /goals
/execution/executions/plugin
Please provide me the input to solve this classpath issue.
--
Thanks, Kavita Gupta Agarwal
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Re : Re : A classpath issue ?
Sorry for the late answer, I had not seen your question. I now saw it because the exact same issue showed up again a year later when running the build on a new computer. I had forgotten again to install this settings.xml file. So I just copied it again in the .m2/ directory and it now works fine. To be honest, I don't know today what in this file makes the issue go away. Here is the settings.xml file content: ?xml version=1.0 encoding=UTF-8? settings xmlns=http://maven.apache.org/SETTINGS/1.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd; pluginGroups pluginGrouporg.mortbay.jetty/pluginGroup /pluginGroups profiles profile activation activeByDefaulttrue/activeByDefault /activation repositories repository idmaven2/id nameMaven2 repository/name releases enabledtrue/enabled /releases snapshots enabledfalse/enabled /snapshots urlhttp://repo2.maven.org/maven2/url /repository repository idibiblio/id nameibiblio repository/name releases enabledtrue/enabled /releases snapshots enabledfalse/enabled /snapshots urlhttp://www.ibiblio.org/maven/url /repository repository idmaven/id nameMaven repository/name releases enabledtrue/enabled /releases snapshots enabledfalse/enabled /snapshots urlhttp://mvnrepository.com/url /repository /repositories /profile /profiles /settings -- View this message in context: http://maven.40175.n5.nabble.com/A-classpath-issue-tp3300543p5459421.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Re : Re : A classpath issue ?
I just found out what in the settings.xml file prevents this issue. It is the directive: activation activeByDefaulttrue/activeByDefault /activation that makes the issue go away. Removing this directive from the settings.xml file triggers the exception. I wonder why.. -- View this message in context: http://maven.40175.n5.nabble.com/A-classpath-issue-tp3300543p5459429.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
axistools-maven-plugin classpath issue
Hi,
I have a situation where I have to generate wsdd
(web-service-deployment-descriptors) for a couple of projects.
I'm using the axistools-maven-plugin admin goal to accomplish this.
In order to get it to work, I find that I have to include the project
dependencies within the plugin dependencies, i.e.:
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdaxistools-maven-plugin/artifactId
executions
execution
id${project.artifactId}-gen-server-wsdd/id
goalsgoaladmin/goal/goals
configuration
configOutputDirectory${project.build.outputDirectory}/WEB-INF/configOutputDirectory
isServerConfigtrue/isServerConfig
inputFiles
include${SERVER_WSDD}/include
/inputFiles
/configuration
/execution
/executions
dependencies
dependency
groupIdaxis/groupId
artifactIdaxis/artifactId
version1.2.1/version
/dependency
dependency
LOCAL_ARTIFACT_A
/dependency
/dependencies
/plugin
Not sure why the LOCAL_ARTIFACT dependencies have to appear within
the plugin deps, and this may be the source of the problem.
Rest assured that it is not declared there, the plugin does not use
the project dependencies (as I think it should), and so the task
fails with missing class errors.
The above works fine when I build locally.
However, when I add a second use of the plugin in a different pom,
but in the same reactor, the classpath from the first instance is
used and the wsdd generation fails.
As a work-around, I have included both LOCAL_ARTIFACT dependencies in
the plugin declaration, so no matter which one gets called first, it
will have a full classpath that will work for either project. If I
added a third project, I would have to keep doing this.
Not the most desirable situation.
So my question is, is this a maven classloading issue, or a plugin
issue? Has anyone else encountered this sticky classpath issue
with other plugins?
mvn --version
Apache Maven 2.2.1 (r801777; 2009-08-06 12:16:01-0700)
Java version: 1.5.0_24
Java home: /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home
Default locale: en_US, platform encoding: MacRoman
OS name: mac os x version: 10.6.6 arch: i386 Family: unix
tia,
-Russ
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Re : Re : A classpath issue ?
I was using the default install of maven on the iMac and I forgot to copy the settings.xml file I had on Linux. I guess I'm a little bit curious now about the contents of your settings.xml file... Must be a profile that does something with your spring xml file? Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re : Re : A classpath issue ?
Stupid me !! I was using the default install of maven on the iMac and I forgot to copy the settings.xml file I had on Linux. Funny, the default maven install on the iMac had no settings.xml file at all. Did the copy and the build passed. So sorry to bother you smart people with my mistake.. Kind Regards, Stephane De : Wayne Fay [via Maven] ml-node+3301286-284534167-63...@n5.nabble.com À : Stephane-3 mittiprove...@yahoo.se Envoyé le : Sam 11 décembre 2010, 7h 12min 46s Objet : Re: Re : A classpath issue ? And, again on the iMac, if this time I don't specify the integration-test profile on the command line with the specified profile replacing the standard resources directory. Stranges this is happening on this OSX maven.. Run mvn -X help:effective-pom and compare the versions of EVERYTHING. Surely there is a difference that you just haven't noticed in a plugin or something. Once you find the difference, come back and tell us about it. Wayne - To unsubscribe, e-mail: [hidden email] For additional commands, e-mail: [hidden email] View message @ http://maven.40175.n5.nabble.com/A-classpath-issue-tp3300543p3301286.html To unsubscribe from A classpath issue ?, click here. -- View this message in context: http://maven.40175.n5.nabble.com/A-classpath-issue-tp3300543p3301418.html Sent from the Maven - Users mailing list archive at Nabble.com.
A classpath issue ?
that I don't see the resources/ directory in the classpath. -- View this message in context: http://maven.40175.n5.nabble.com/A-classpath-issue-tp3300543p3300543.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: A classpath issue ?
The file does exist in the source directory: stephane:learnintouch$ ll core/src/main/resources/ -rwxr-xr-x 1 stephane staff 607 9 déc 17:34 spring-data-source.xml But it is nowhere to be found in the target directory: stephane:learnintouch$ll core/target/classes/ drwxr-xr-x 3 stephane staff 102 10 déc 17:43 com -rw-r--r-- 1 stephane staff 5359 10 déc 17:43 spring-hibernate-dao.xml -rw-r--r-- 1 stephane staff 2760 10 déc 17:43 spring-hibernate.xml -rw-r--r-- 1 stephane staff 529 10 déc 17:43 spring-service.xml stephane:learnintouch$ll core/target/test-classes/ drwxr-xr-x 3 stephane staff 102 10 déc 17:43 com stephane:learnintouch$ The file has not been copied into the target directory. Strange.. -- View this message in context: http://maven.40175.n5.nabble.com/A-classpath-issue-tp3300543p3300609.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: A classpath issue ?
I'm running the following version of maven: stephane:learnintouch/$ mvn -version Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200) Java version: 1.6.0_22 Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home Default locale: fr_FR, platform encoding: MacRoman OS name: mac os x version: 10.6.5 arch: x86_64 Family: mac -- View this message in context: http://maven.40175.n5.nabble.com/A-classpath-issue-tp3300543p3300635.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: A classpath issue ?
.jar, /Users/stephane/.m2/repository/org/springframework/spring-tx/2.5.6/spring-tx-2.5.6.jar, /Users/stephane/.m2/repository/org/springframework/spring-test/2.5.6/spring-test-2.5.6.jar] The surefire report says: Caused by: org.springframework.beans.factory.BeanDefinitionStoreException: IOException parsing XML document from class path resource [spring-data-source.xml]; nested exception is java.io.FileNotFoundException: class path resource [spring-data-source.xml] cannot be opened because it does not exist It is strange that I don't see the resources/ directory in the classpath. -- View this message in context: http://maven.40175.n5.nabble.com/A-classpath-issue-tp3300543p3300543.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: A classpath issue ?
, /Users/stephane/.m2/repository/org/springframework/spring-beans/2.5.6/spring-beans-2.5.6.jar, /Users/stephane/.m2/repository/org/springframework/spring-core/2.5.6/spring-core-2.5.6.jar, /Users/stephane/.m2/repository/org/springframework/spring-context/2.5.6/spring-context-2.5.6.jar, /Users/stephane/.m2/repository/org/springframework/spring-tx/2.5.6/spring-tx-2.5.6.jar, /Users/stephane/.m2/repository/org/springframework/spring-test/2.5.6/spring-test-2.5.6.jar] The surefire report says: Caused by: org.springframework.beans.factory.BeanDefinitionStoreException: IOException parsing XML document from class path resource [spring-data-source.xml]; nested exception is java.io.FileNotFoundException: class path resource [spring-data-source.xml] cannot be opened because it does not exist It is strange that I don't see the resources/ directory in the classpath. -- View this message in context: http://maven.40175.n5.nabble.com/A-classpath-issue-tp3300543p3300543.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re : A classpath issue ?
I just ran the following command, on the Linux box:
mvn help:effective-pom -Pintegration-test
And it gives the following output:
sourceDirectory/home/stephane/dev/java/project/learnintouch/src/main/java/sourceDirectory^M
scriptSourceDirectorysrc/main/scripts/scriptSourceDirectory^M
testSourceDirectory/home/stephane/dev/java/project/learnintouch/src/integration/java/testSourceDirectory^M
outputDirectory/home/stephane/dev/java/project/learnintouch/target/classes/outputDirectory^M
testOutputDirectory/home/stephane/dev/java/project/learnintouch/target/test-classes/testOutputDirectory^M
resources^M
resource^M
filteringtrue/filtering^M
mergeIdresource-0/mergeId^M
directory/home/stephane/dev/java/project/learnintouch/src/main/resources/directory^M
/resource^M
resource^M
filteringtrue/filtering^M
mergeIdresource-1/mergeId^M
directory/home/stephane/dev/java/project/learnintouch/src/integration/resources/directory^M
/resource^M
/resources^M
testResources^M
testResource^M
mergeIdresource-2/mergeId^M
directory/home/stephane/dev/java/project/learnintouch/src/test/resources/directory^M
/testResource^M
/testResources^M
directory/home/stephane/dev/java/project/learnintouch/target/directory
I shall now run it on the iMac machine.
De : Anders Hammar [via Maven] ml-node+3301035-833614543-63...@n5.nabble.com
À : Stephane-3 mittiprove...@yahoo.se
Envoyé le : Ven 10 décembre 2010, 22h 55min 14s
Objet : Re: A classpath issue ?
Hmm, I now see that you say it works on Linux. Maybe the resources section
outside the profiles isn't being replaced but added to? Check the effective
pom and you'll know for sure.
/Anders
On Fri, Dec 10, 2010 at 22:52, Anders Hammar [hidden email] wrote:
That's because you haven't configured that folder in the profile. This is
what you have configured:
resources
resource
directorysrc/integration/
resources/directory
filteringtrue/filtering
/resource
/resources
This replaces the resources section defined outside the profiles.
Execute this and check the effective pom:
mvn help:effective-pom -P integration-test
/Anders
On Fri, Dec 10, 2010 at 17:16, Stephane-3 [hidden email] wrote:
Hi,
I have a maven build that is doing fine on my old linux box.
Trying now to run it in the new iMac environment, I get an issue with a
spring xml file not being found.
It feels like the classpath is not correctly set.
The pom.xml file is:
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
groupIdcom.thalasoft/groupId
artifactIdlearnintouch/artifactId
packagingpom/packaging
version1.0-SNAPSHOT/version
namelearnintouch/name
urlhttp://www.thalasoft.com/url
modules
modulecore/module
/modules
properties
spring.core.version2.5.6/spring.core.version
hibernate.version3.6.0.Final/hibernate.version
test.source.dirsrc/test/java/test.source.dir
/properties
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
configuration
source1.6/source
target1.6/target
encodingUTF-8/encoding
/configuration
/plugin
/plugins
testSourceDirectory
${test.source.dir}
/testSourceDirectory
/build
profiles
profile
iddefault/id
activation
activeByDefaulttrue/activeByDefault
/activation
properties
/properties
build
filters
filtersrc/main/filters/data-source.properties/filter
/filters
resources
resource
directorysrc/main/resources/directory
filteringtrue/filtering
/resource
/resources
/build
/profile
profile
idintegration-test/id
properties
test.source.dirsrc/integration/java/test.source.dir
/properties
build
filters
filtersrc/integration/filters/data-source.properties/filter
/filters
resources
resource
directorysrc/integration/resources/directory
filteringtrue/filtering
/resource
Re : A classpath issue ?
And the same command on the iMac machine:
sourceDirectory/Users/stephane/dev/java/projects/learnintouch/core/src/main/java/sourceDirectory
scriptSourceDirectorysrc/main/scripts/scriptSourceDirectory
testSourceDirectory/Users/stephane/dev/java/projects/learnintouch/core/src/integration/java/testSourceDirectory
outputDirectory/Users/stephane/dev/java/projects/learnintouch/core/target/classes/outputDirectory
testOutputDirectory/Users/stephane/dev/java/projects/learnintouch/core/target/test-classes/testOutputDirectory
resources
resource
filteringtrue/filtering
mergeIdresource-2/mergeId
directory/Users/stephane/dev/java/projects/learnintouch/core/src/integration/resources/directory
/resource
/resources
testResources
testResource
mergeIdresource-3/mergeId
directory/Users/stephane/dev/java/projects/learnintouch/core/src/test/resources/directory
/testResource
/testResources
directory/Users/stephane/dev/java/projects/learnintouch/core/target/directory
Indeed, the standard resources directory is missing.
De : Anders Hammar [via Maven] ml-node+3301035-833614543-63...@n5.nabble.com
À : Stephane-3 mittiprove...@yahoo.se
Envoyé le : Ven 10 décembre 2010, 22h 55min 14s
Objet : Re: A classpath issue ?
Hmm, I now see that you say it works on Linux. Maybe the resources section
outside the profiles isn't being replaced but added to? Check the effective
pom and you'll know for sure.
/Anders
On Fri, Dec 10, 2010 at 22:52, Anders Hammar [hidden email] wrote:
That's because you haven't configured that folder in the profile. This is
what you have configured:
resources
resource
directorysrc/integration/
resources/directory
filteringtrue/filtering
/resource
/resources
This replaces the resources section defined outside the profiles.
Execute this and check the effective pom:
mvn help:effective-pom -P integration-test
/Anders
On Fri, Dec 10, 2010 at 17:16, Stephane-3 [hidden email] wrote:
Hi,
I have a maven build that is doing fine on my old linux box.
Trying now to run it in the new iMac environment, I get an issue with a
spring xml file not being found.
It feels like the classpath is not correctly set.
The pom.xml file is:
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
groupIdcom.thalasoft/groupId
artifactIdlearnintouch/artifactId
packagingpom/packaging
version1.0-SNAPSHOT/version
namelearnintouch/name
urlhttp://www.thalasoft.com/url
modules
modulecore/module
/modules
properties
spring.core.version2.5.6/spring.core.version
hibernate.version3.6.0.Final/hibernate.version
test.source.dirsrc/test/java/test.source.dir
/properties
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
configuration
source1.6/source
target1.6/target
encodingUTF-8/encoding
/configuration
/plugin
/plugins
testSourceDirectory
${test.source.dir}
/testSourceDirectory
/build
profiles
profile
iddefault/id
activation
activeByDefaulttrue/activeByDefault
/activation
properties
/properties
build
filters
filtersrc/main/filters/data-source.properties/filter
/filters
resources
resource
directorysrc/main/resources/directory
filteringtrue/filtering
/resource
/resources
/build
/profile
profile
idintegration-test/id
properties
test.source.dirsrc/integration/java/test.source.dir
/properties
build
filters
filtersrc/integration/filters/data-source.properties/filter
/filters
resources
resource
directorysrc/integration/resources/directory
filteringtrue/filtering
/resource
/resources
/build
/profile
profile
idmysql-test/id
properties
test.source.dirsrc/integration/java/test.source.dir
/properties
build
filters
filtersrc/main/filters/data-source.properties/filter
Re : A classpath issue ?
And, again on the iMac, if this time I don't specify the integration-test
profile on the command line
mvn help:effective-pom
I get
sourceDirectory/Users/stephane/dev/java/projects/learnintouch/core/src/main/java/sourceDirectory
scriptSourceDirectorysrc/main/scripts/scriptSourceDirectory
testSourceDirectory/Users/stephane/dev/java/projects/learnintouch/core/src/test/java/testSourceDirectory
outputDirectory/Users/stephane/dev/java/projects/learnintouch/core/target/classes/outputDirectory
testOutputDirectory/Users/stephane/dev/java/projects/learnintouch/core/target/test-classes/testOutputDirectory
resources
resource
filteringtrue/filtering
mergeIdresource-2/mergeId
directory/Users/stephane/dev/java/projects/learnintouch/core/src/main/resources/directory
/resource
/resources
testResources
testResource
mergeIdresource-3/mergeId
directory/Users/stephane/dev/java/projects/learnintouch/core/src/test/resources/directory
/testResource
/testResources
directory/Users/stephane/dev/java/projects/learnintouch/core/target/directory
with the specified profile replacing the standard resources directory.
Stranges this is happening on this OSX maven..
De : Anders Hammar [via Maven] ml-node+3301035-833614543-63...@n5.nabble.com
À : Stephane-3 mittiprove...@yahoo.se
Envoyé le : Ven 10 décembre 2010, 22h 55min 14s
Objet : Re: A classpath issue ?
Hmm, I now see that you say it works on Linux. Maybe the resources section
outside the profiles isn't being replaced but added to? Check the effective
pom and you'll know for sure.
/Anders
On Fri, Dec 10, 2010 at 22:52, Anders Hammar [hidden email] wrote:
That's because you haven't configured that folder in the profile. This is
what you have configured:
resources
resource
directorysrc/integration/
resources/directory
filteringtrue/filtering
/resource
/resources
This replaces the resources section defined outside the profiles.
Execute this and check the effective pom:
mvn help:effective-pom -P integration-test
/Anders
On Fri, Dec 10, 2010 at 17:16, Stephane-3 [hidden email] wrote:
Hi,
I have a maven build that is doing fine on my old linux box.
Trying now to run it in the new iMac environment, I get an issue with a
spring xml file not being found.
It feels like the classpath is not correctly set.
The pom.xml file is:
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
groupIdcom.thalasoft/groupId
artifactIdlearnintouch/artifactId
packagingpom/packaging
version1.0-SNAPSHOT/version
namelearnintouch/name
urlhttp://www.thalasoft.com/url
modules
modulecore/module
/modules
properties
spring.core.version2.5.6/spring.core.version
hibernate.version3.6.0.Final/hibernate.version
test.source.dirsrc/test/java/test.source.dir
/properties
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
configuration
source1.6/source
target1.6/target
encodingUTF-8/encoding
/configuration
/plugin
/plugins
testSourceDirectory
${test.source.dir}
/testSourceDirectory
/build
profiles
profile
iddefault/id
activation
activeByDefaulttrue/activeByDefault
/activation
properties
/properties
build
filters
filtersrc/main/filters/data-source.properties/filter
/filters
resources
resource
directorysrc/main/resources/directory
filteringtrue/filtering
/resource
/resources
/build
/profile
profile
idintegration-test/id
properties
test.source.dirsrc/integration/java/test.source.dir
/properties
build
filters
filtersrc/integration/filters/data-source.properties/filter
/filters
resources
resource
directorysrc/integration/resources/directory
filteringtrue/filtering
/resource
/resources
/build
/profile
profile
idmysql-test/id
properties
test.source.dirsrc
Re: Re : A classpath issue ?
And, again on the iMac, if this time I don't specify the integration-test profile on the command line with the specified profile replacing the standard resources directory. Stranges this is happening on this OSX maven.. Run mvn -X help:effective-pom and compare the versions of EVERYTHING. Surely there is a difference that you just haven't noticed in a plugin or something. Once you find the difference, come back and tell us about it. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: classpath issue accessing lib/*.jar in a jar
On Fri, Oct 1, 2010 at 7:27 PM, torsten.reinh...@gi-de.com wrote: Hi, acually I´m working on a SAP Web AS integration, so I need to access some classes from external 3rd party jars. these jars seem to be OSGI bundels, with a MANIFEST.MF containing for example: Require-Bundle: com.tssap.sap.libs.logging Bundle-Vendor: %provider.name Bundle-ClassPath: lib/sap.com~tc~exception~impl.jar Bundle-Version: 2.0.0.091202153157 Bundle-Localization: plugin Bundle-Name: %plugin.name Bundle-ManifestVersion: 2 Bundle-SymbolicName: com.sap.exception;singleton:=true = is there a way to simple deploy these jars and get the classes from lib/*.jar into the classpath ? or do I have to extract the lib/*.jar and deploy it separately ? Have you had a read of the assembly plugin? http://maven.apache.org/plugins/maven-assembly-plugin/usage.html - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Multi-module build and plugin classpath issue
Hi, I am committer for the Castor (http://www.castor.org) project, and I am experiencing 'behaviour' I somehow find hard to understand. We at castor have a multi-module setup, where some of the modules have the maven plugin for Castor configured to generate java code from XML schema. So far, so fine. It now and then happens that we'd like to override the default dependency for the Maven plugin for Castor in one module only (to e.g. integrate some new functionality of the code generator). Whenever we do this (i.e. add a dependency in the plugin configuration of one module only) and execute a 'mvn install' in the project directory, we can see that the new dependency is being picked up but for all modules that use the Maven plugin for Castor - which is not what we want. Questions: Is this expected behaviour ? Or are we missing something in e.g. the plugin configuration to have the isolation we'd like to see ? If I have failed to make myself understandable, let me know Regards Werner - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multi-module build and plugin classpath issue
As far as I understand, currently in Maven there is not isolation between plugins in different projects. If you have a multi-module build, the first use of a plugin in that multi-module build will determine both the version and the dependencies that are loaded into it's classloader for all subsequent plugin invokations during the reactor build. I'm not sure if this is what you wanted to hear, but it is what it is :-( -Stephen 2008/10/2 Werner Guttmann [EMAIL PROTECTED] Hi, I am committer for the Castor (http://www.castor.org) project, and I am experiencing 'behaviour' I somehow find hard to understand. We at castor have a multi-module setup, where some of the modules have the maven plugin for Castor configured to generate java code from XML schema. So far, so fine. It now and then happens that we'd like to override the default dependency for the Maven plugin for Castor in one module only (to e.g. integrate some new functionality of the code generator). Whenever we do this (i.e. add a dependency in the plugin configuration of one module only) and execute a 'mvn install' in the project directory, we can see that the new dependency is being picked up but for all modules that use the Maven plugin for Castor - which is not what we want. Questions: Is this expected behaviour ? Or are we missing something in e.g. the plugin configuration to have the isolation we'd like to see ? If I have failed to make myself understandable, let me know Regards Werner - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multi-module build and plugin classpath issue
Thanks, Stephen, for confirming what we have already been assuming, based upon our builds. And no, I would have very much liked to see a different answer. Let me just ask a few follow-ups: a) Is this by design, or ... b) Is this a current limitation of the reactor ? c) Could this be overcome (in theory, at least), and d) What would it take to see this changed ? Thanks for your time Werner Stephen Connolly wrote: As far as I understand, currently in Maven there is not isolation between plugins in different projects. If you have a multi-module build, the first use of a plugin in that multi-module build will determine both the version and the dependencies that are loaded into it's classloader for all subsequent plugin invokations during the reactor build. I'm not sure if this is what you wanted to hear, but it is what it is :-( -Stephen 2008/10/2 Werner Guttmann [EMAIL PROTECTED] Hi, I am committer for the Castor (http://www.castor.org) project, and I am experiencing 'behaviour' I somehow find hard to understand. We at castor have a multi-module setup, where some of the modules have the maven plugin for Castor configured to generate java code from XML schema. So far, so fine. It now and then happens that we'd like to override the default dependency for the Maven plugin for Castor in one module only (to e.g. integrate some new functionality of the code generator). Whenever we do this (i.e. add a dependency in the plugin configuration of one module only) and execute a 'mvn install' in the project directory, we can see that the new dependency is being picked up but for all modules that use the Maven plugin for Castor - which is not what we want. Questions: Is this expected behaviour ? Or are we missing something in e.g. the plugin configuration to have the isolation we'd like to see ? If I have failed to make myself understandable, let me know Regards Werner - 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]
Re: Multi-module build and plugin classpath issue
my understanding is b and it's being worked on 2008/10/2 Werner Guttmann [EMAIL PROTECTED]: Thanks, Stephen, for confirming what we have already been assuming, based upon our builds. And no, I would have very much liked to see a different answer. Let me just ask a few follow-ups: a) Is this by design, or ... b) Is this a current limitation of the reactor ? c) Could this be overcome (in theory, at least), and d) What would it take to see this changed ? Thanks for your time Werner Stephen Connolly wrote: As far as I understand, currently in Maven there is not isolation between plugins in different projects. If you have a multi-module build, the first use of a plugin in that multi-module build will determine both the version and the dependencies that are loaded into it's classloader for all subsequent plugin invokations during the reactor build. I'm not sure if this is what you wanted to hear, but it is what it is :-( -Stephen 2008/10/2 Werner Guttmann [EMAIL PROTECTED] Hi, I am committer for the Castor (http://www.castor.org) project, and I am experiencing 'behaviour' I somehow find hard to understand. We at castor have a multi-module setup, where some of the modules have the maven plugin for Castor configured to generate java code from XML schema. So far, so fine. It now and then happens that we'd like to override the default dependency for the Maven plugin for Castor in one module only (to e.g. integrate some new functionality of the code generator). Whenever we do this (i.e. add a dependency in the plugin configuration of one module only) and execute a 'mvn install' in the project directory, we can see that the new dependency is being picked up but for all modules that use the Maven plugin for Castor - which is not what we want. Questions: Is this expected behaviour ? Or are we missing something in e.g. the plugin configuration to have the isolation we'd like to see ? If I have failed to make myself understandable, let me know Regards Werner - 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]
Test classpath issue with v2.0.8 and v2.0.9
When trying to access test resources in my unit tests, maven 2.0.8 and above are returning the wrong directory. Here is my basic code to access the folder def file = new JmblXsltDriverTest().getClass().getResource(/)?.file println file On 2.0.7 this would print /workspace/checkout/weather/trunk/jetjwis/jbi/jmbl-xslt/target/test-classes/ On 2.0.8 and 2.0.9 this prints /workspace/checkout/weather/trunk/jetjwis/jbi/jmbl-xslt/target/classes/ To me this is a critical bug that would almost certainly cause every projects unit tests that access test resources to fail. -- View this message in context: http://www.nabble.com/Test-classpath-issue-with-v2.0.8-and-v2.0.9-tp17276386p17276386.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Test classpath issue with v2.0.8 and v2.0.9
jlo_gestalt wrote: When trying to access test resources in my unit tests, maven 2.0.8 and above are returning the wrong directory. Here is my basic code to access the folder def file = new JmblXsltDriverTest().getClass().getResource(/)?.file println file On 2.0.7 this would print /workspace/checkout/weather/trunk/jetjwis/jbi/jmbl-xslt/target/test-classes/ On 2.0.8 and 2.0.9 this prints /workspace/checkout/weather/trunk/jetjwis/jbi/jmbl-xslt/target/classes/ To me this is a critical bug that would almost certainly cause every projects unit tests that access test resources to fail. I'm going to guess you're encountering the bug described here: http://docs.codehaus.org/display/MAVENUSER/Classpath+Ordering+Bugs+in+Maven+Surefire Upgrading Surefire will probably restore you to the correct behavior. -Dan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Test classpath issue with v2.0.8 and v2.0.9
I have a couple of observations... First off I see you're writing you unit tests in Groovy! That's a good thing of course for far too many reasons. It's also an important detail to pay attention to. There are a hole host of other details to look at as well. Secondly it appears you are trying to query for the resource folder using code. This is not a good thing or a necessary thing to do. Maven will put all of your test resources under the test-classes folder unless something else somewhere else tells it not to. Another detail is that your code is asking the wrong question and may have been mistakenly getting at the right answer all along. It asks the location of it's execution folder not the location of the resource folder. I can show you the correct hack to locating the resource folder involving a marker file which you could run and arrive at a more accurate answer. More on that later. Here's the important things to consider. Groovy is interpreted/compiled. Running that same groovy code through a plugin (like the Groovy plugin or Ant run) would place compiled classes in your classes output folder. In one case I'm assuming the code was being copied from the test/resources to the test-classes folder and in another case it is possibly being filtered. I can't tell without looking. Here's some things to look for. Find out where the Groovy code is being run from. Is it being both compiled to target/classes and copied over to target/test-classes as .groovy files? If so then there's some ambiguity worth cleaning up. What is it you are actually trying to do? Do you want to run the scripts or do you want to compile them? If you are compiling them make sure you point the compiler to the correct output folder. I feel like I'm babbling and confusing you more than helping but I'm sure your problem lies in whther you compile to the correct output folder or copy to the correct output folder. Look for filters that may have been added as well. jlo_gestalt wrote: When trying to access test resources in my unit tests, maven 2.0.8 and above are returning the wrong directory. Here is my basic code to access the folder def file = new JmblXsltDriverTest().getClass().getResource(/)?.file println file On 2.0.7 this would print /workspace/checkout/weather/trunk/jetjwis/jbi/jmbl-xslt/target/test-classes/ On 2.0.8 and 2.0.9 this prints /workspace/checkout/weather/trunk/jetjwis/jbi/jmbl-xslt/target/classes/ To me this is a critical bug that would almost certainly cause every projects unit tests that access test resources to fail. -- View this message in context: http://www.nabble.com/Test-classpath-issue-with-v2.0.8-and-v2.0.9-tp17276386p17281319.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Test classpath issue with v2.0.8 and v2.0.9
I disagree with you on accessing the resources my way, but that is for another post. Anyways, I was able to upgrade to maven 2.0.8 and surefire plugin 2.4.3 and things worked as expected. The only unfortunate thing is that now it won't work on maven 2.0.7, but oh well. Clifton wrote: I have a couple of observations... First off I see you're writing you unit tests in Groovy! That's a good thing of course for far too many reasons. It's also an important detail to pay attention to. There are a hole host of other details to look at as well. Secondly it appears you are trying to query for the resource folder using code. This is not a good thing or a necessary thing to do. Maven will put all of your test resources under the test-classes folder unless something else somewhere else tells it not to. Another detail is that your code is asking the wrong question and may have been mistakenly getting at the right answer all along. It asks the location of it's execution folder not the location of the resource folder. I can show you the correct hack to locating the resource folder involving a marker file which you could run and arrive at a more accurate answer. More on that later. Here's the important things to consider. Groovy is interpreted/compiled. Running that same groovy code through a plugin (like the Groovy plugin or Ant run) would place compiled classes in your classes output folder. In one case I'm assuming the code was being copied from the test/resources to the test-classes folder and in another case it is possibly being filtered. I can't tell without looking. Here's some things to look for. Find out where the Groovy code is being run from. Is it being both compiled to target/classes and copied over to target/test-classes as .groovy files? If so then there's some ambiguity worth cleaning up. What is it you are actually trying to do? Do you want to run the scripts or do you want to compile them? If you are compiling them make sure you point the compiler to the correct output folder. I feel like I'm babbling and confusing you more than helping but I'm sure your problem lies in whther you compile to the correct output folder or copy to the correct output folder. Look for filters that may have been added as well. jlo_gestalt wrote: When trying to access test resources in my unit tests, maven 2.0.8 and above are returning the wrong directory. Here is my basic code to access the folder def file = new JmblXsltDriverTest().getClass().getResource(/)?.file println file On 2.0.7 this would print /workspace/checkout/weather/trunk/jetjwis/jbi/jmbl-xslt/target/test-classes/ On 2.0.8 and 2.0.9 this prints /workspace/checkout/weather/trunk/jetjwis/jbi/jmbl-xslt/target/classes/ To me this is a critical bug that would almost certainly cause every projects unit tests that access test resources to fail. -- View this message in context: http://www.nabble.com/Test-classpath-issue-with-v2.0.8-and-v2.0.9-tp17276386p17283178.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
M2 Classpath issue
Hi,
I am adding some Unit tests to a legacy application before I make any changes.
As part of the tests I start the application. When the application
starts it scans all the classes on the classpath. Unfortunately the
only jar on the classpath is the classworlds.jar due to the way maven
handles dependencies. The application will use a system property
called java.class.path if present. So I have configured the surefire
plugin as shown below.
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-surefire-plugin/artifactId
version2.3/version
configuration
workingDirectory${basedir}\target\test-classes/workingDirectory
systemProperties
property
namejava.class.path/name
value${project.testClasspathElements}/value
/property
/systemProperties
includes
includenexusalpha/**/*Tests*/include
/includes
excludes
excludenexusalpha/jaf2/services/webservice/AlertServerWebServiceTests*.java/exclude
/excludes
reportFormatbrief/reportFormat
useFilefalse/useFile
skipfalse/skip
/configuration
/plugin
Unfortunately when i run the tests the application prints that the
value for the system property java.class.path is
${project.testClasspathElements}. So it seems that maven is not
filtering this property correctly.
As a quick test i added ${project.testClasspathElements} to the
workingDirectory element I see that maven complains that the
workingDirectory is not valid and on inspection i see that the
projects dependencies are listed correctly.
Can anyone help me out with this? I'm using maven 2.0.8.
Regards
Ben Short
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: M2 Classpath issue
This has come up several times on this list, as recently as a week
ago, and people have discussed strategies for dealing with it etc. One
thread in particular you will want to read is:
date Mar 5, 2008 5:07 PM
subject java.class.path and the surefire-plugin
For more info, go to Nabble.com and search the list archives for
java.class.path.
Wayne
On 3/13/08, ben short [EMAIL PROTECTED] wrote:
Hi,
I am adding some Unit tests to a legacy application before I make any changes.
As part of the tests I start the application. When the application
starts it scans all the classes on the classpath. Unfortunately the
only jar on the classpath is the classworlds.jar due to the way maven
handles dependencies. The application will use a system property
called java.class.path if present. So I have configured the surefire
plugin as shown below.
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-surefire-plugin/artifactId
version2.3/version
configuration
workingDirectory${basedir}\target\test-classes/workingDirectory
systemProperties
property
namejava.class.path/name
value${project.testClasspathElements}/value
/property
/systemProperties
includes
includenexusalpha/**/*Tests*/include
/includes
excludes
excludenexusalpha/jaf2/services/webservice/AlertServerWebServiceTests*.java/exclude
/excludes
reportFormatbrief/reportFormat
useFilefalse/useFile
skipfalse/skip
/configuration
/plugin
Unfortunately when i run the tests the application prints that the
value for the system property java.class.path is
${project.testClasspathElements}. So it seems that maven is not
filtering this property correctly.
As a quick test i added ${project.testClasspathElements} to the
workingDirectory element I see that maven complains that the
workingDirectory is not valid and on inspection i see that the
projects dependencies are listed correctly.
Can anyone help me out with this? I'm using maven 2.0.8.
Regards
Ben Short
-
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]
Re: M2 Classpath issue
Wayne,
Thanks for pointing this out.
Regards
Ben Short
On Thu, Mar 13, 2008 at 2:39 PM, Wayne Fay [EMAIL PROTECTED] wrote:
This has come up several times on this list, as recently as a week
ago, and people have discussed strategies for dealing with it etc. One
thread in particular you will want to read is:
date Mar 5, 2008 5:07 PM
subject java.class.path and the surefire-plugin
For more info, go to Nabble.com and search the list archives for
java.class.path.
Wayne
On 3/13/08, ben short [EMAIL PROTECTED] wrote:
Hi,
I am adding some Unit tests to a legacy application before I make any
changes.
As part of the tests I start the application. When the application
starts it scans all the classes on the classpath. Unfortunately the
only jar on the classpath is the classworlds.jar due to the way maven
handles dependencies. The application will use a system property
called java.class.path if present. So I have configured the surefire
plugin as shown below.
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-surefire-plugin/artifactId
version2.3/version
configuration
workingDirectory${basedir}\target\test-classes/workingDirectory
systemProperties
property
namejava.class.path/name
value${project.testClasspathElements}/value
/property
/systemProperties
includes
includenexusalpha/**/*Tests*/include
/includes
excludes
excludenexusalpha/jaf2/services/webservice/AlertServerWebServiceTests*.java/exclude
/excludes
reportFormatbrief/reportFormat
useFilefalse/useFile
skipfalse/skip
/configuration
/plugin
Unfortunately when i run the tests the application prints that the
value for the system property java.class.path is
${project.testClasspathElements}. So it seems that maven is not
filtering this property correctly.
As a quick test i added ${project.testClasspathElements} to the
workingDirectory element I see that maven complains that the
workingDirectory is not valid and on inspection i see that the
projects dependencies are listed correctly.
Can anyone help me out with this? I'm using maven 2.0.8.
Regards
Ben Short
-
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]
Surefire-plugin 2.3.1 xml-apis classpath issue
Hi there, Was there any change in surefire-plugin from version 3.2 to 3.2.1 that changes the way xml apis are loaded for tests? With version 3.2, I can add xercesIml in scope:test and use XSD validation. After getting the upgrade to version 2.3.1 I'm getting this error: nested exception is javax.xml.parsers.ParserConfigurationException: Unable to validate using XSD: Your JAXP provider [EMAIL PROTECTED] does not support XML Schema. Are you running on Java 1.4 or below with Apache Crimson? Upgrade to Apache Xerces (or Java 1.5) for full XSD support. Caused by: javax.xml.parsers.ParserConfigurationException: Unable to validate using XSD: Your JAXP provider [EMAIL PROTECTED] does not support XML Schema. Are you running on Java 1.4 or below with Apache Crimson? Upgrade to Apache Xerces (or Java 1.5) for full XSD support. I have xercesImpl as test scope dependency and also have it installed in the jdk/jre. Using 3.2 plugin version XSD validation works fine Any idea if this must be reported as a bug? Thanks Ivan Garcia -- View this message in context: http://www.nabble.com/Surefire-plugin-2.3.1-xml-apis-classpath-issue-tp14707599s177p14707599.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [M2] Classpath issue
No, there is definitely only one version in the classpath, and I'm not sure how that would cause a ClassNotFoundException. This is the root exception: Caused by: java.lang.ClassNotFoundException: org.apache.xerces.parsers.SAXParser at org.xml.sax.helpers.XMLReaderFactory.createXMLReader(XMLReaderFactory.java:1 21) at com.fja.pm.dataaccess.config.Configurator.init(Configurator.java:30) ... 44 more But it only happens in Surefire, runs fine in Eclipse. -Original Message- From: Marcos Silva Pereira [mailto:[EMAIL PROTECTED] Sent: Friday, February 23, 2007 4:44 PM To: Maven Users List Subject: Re: [M2] Classpath issue There is some other version of xerces in your classpath? Kind Regards, On 2/23/07, Siegmann Daniel, NY [EMAIL PROTECTED] wrote: I am trying to convert a project from Maven1 to Maven2. Should be simple, but I am getting a ClassNotFoundException on the following line in my code when running JUnit tests through Maven: XMLReaderFactory.createXMLReader(org.apache.xerces.parsers.SAXParser ) This class is in xerces-2.4.0.jar, I have verified. This is listed as a dependency, and the -X option confirms it should be on the classpath. I built the eclipse files and ran the test, no problem - I had to remove some nested directories listed under resources, but this shouldn't have any effect on class loading. Any ideas what could be causing this problem? I don't even know how to debug this. :( -- Daniel Siegmann FJA-US, Inc. 512 Seventh Ave., New York, NY 10018 (212) 840-2618 ext. 139 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Marcos Silva Pereira recife - pe [EMAIL PROTECTED] skype: marcos.silva.pereira http://blastemica.blogspot.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[M2] Classpath issue
I am trying to convert a project from Maven1 to Maven2. Should be simple, but I am getting a ClassNotFoundException on the following line in my code when running JUnit tests through Maven: XMLReaderFactory.createXMLReader(org.apache.xerces.parsers.SAXParser) This class is in xerces-2.4.0.jar, I have verified. This is listed as a dependency, and the -X option confirms it should be on the classpath. I built the eclipse files and ran the test, no problem - I had to remove some nested directories listed under resources, but this shouldn't have any effect on class loading. Any ideas what could be causing this problem? I don't even know how to debug this. :( -- Daniel Siegmann FJA-US, Inc. 512 Seventh Ave., New York, NY 10018 (212) 840-2618 ext. 139 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M2] Classpath issue
There is some other version of xerces in your classpath? Kind Regards, On 2/23/07, Siegmann Daniel, NY [EMAIL PROTECTED] wrote: I am trying to convert a project from Maven1 to Maven2. Should be simple, but I am getting a ClassNotFoundException on the following line in my code when running JUnit tests through Maven: XMLReaderFactory.createXMLReader(org.apache.xerces.parsers.SAXParser) This class is in xerces-2.4.0.jar, I have verified. This is listed as a dependency, and the -X option confirms it should be on the classpath. I built the eclipse files and ran the test, no problem - I had to remove some nested directories listed under resources, but this shouldn't have any effect on class loading. Any ideas what could be causing this problem? I don't even know how to debug this. :( -- Daniel Siegmann FJA-US, Inc. 512 Seventh Ave., New York, NY 10018 (212) 840-2618 ext. 139 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Marcos Silva Pereira recife - pe [EMAIL PROTECTED] skype: marcos.silva.pereira http://blastemica.blogspot.com
Re: Spring classpath issue
hi, my 2 cents. what's hte scope of your dependency? is it compile? hth marco On 12/9/06, Morgovsky, Alexander (US - Glen Mills) [EMAIL PROTECTED] wrote: I have a Spring .jar which has a Spring properties file. I created a dependency on this .jar file but it did not get picked up during integration-test. Does anyone know why this may be? Thanks. This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message. Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. [v.E.1]
RE: [M2]weblogic:appc classpath issue
I am glad that it is working now. I am anxious to push it up onto the snapshot server. Feel free to let me know what else I can add to help you out. You can enter JIRA tickets in the mojo section so I can track what you need. If you can clarify what you mean by autotypes I will look into that. I hope this weekend to add service gen and jwsc support. Also specify which version of Weblogic you are running. The code it different for 9.0 and 8.1 so that helps me know where to start. Keep the bug reports and feature requests coming and I will work on them as I have time. Scott Ryan Chief Technology Officer Soaring Eagle L.L.C. [EMAIL PROTECTED] www.soaringeagleco.com (303) 263-3044 -Original Message- From: Dmystery [mailto:[EMAIL PROTECTED] Sent: Thursday, November 02, 2006 8:55 PM To: users@maven.apache.org Subject: RE: [M2]weblogic:appc classpath issue I downloaded the code from codehaus SNV and it working fine now. Thanks again! Any plans to include autotypes and servicegen goals in the plugin? :) Currently i'm using maven-antrun-plugin to use weblogic servicegen task. Scott Ryan-2 wrote: I would love to push it but I only have access to SVN at codehaus. I do not have the authority to push up a snapshot any longer and the people who can don't seem to have access to the Weblogic jars required to build the code. I hope I can get this worked out this week. Until then you can just download the code from SVN and run mvn install to place it in your local repository to test. Scott Ryan Chief Technology Officer Soaring Eagle L.L.C. [EMAIL PROTECTED] www.soaringeagleco.com (303) 263-3044 -Original Message- From: Dmystery [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 01, 2006 9:06 PM To: users@maven.apache.org Subject: RE: [M2]weblogic:appc classpath issue Thanks Scott. It would be great if you can push the latest snapshot to the repository now. Scott Ryan-2 wrote: I have refactored the 2.8.0 plugin to fix that problem. I have changed some of the parameters and since the website can only support one version of the plugin I need to add a page to describe the new settings for the 2.8.0 plugin. I will be pushing the latest snapshot up to the repository once I have completed that documentation. This fixes the classpath issue both in appc and the client gen mojos. I have not updated the 2.9.0 version as the 9.2 release broke all the apis I was using so i need to refactor to use the new API's. Let me know if you would prefer I push up the 2.8.0 version now and just post the changes on a note to the user list. Scott Ryan Chief Technology Officer Soaring Eagle L.L.C. [EMAIL PROTECTED] www.soaringeagleco.com (303) 263-3044 -Original Message- From: Manu [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 31, 2006 12:07 PM To: Maven Users List Subject: Re: [M2]weblogic:appc classpath issue Hi, I have the same problem. I need to explicitly set the entire classpath by hand to have it worked. In other words, I'm defining another time all the dependencies that already are in the pom. The plugin does not seem to take into account the dependencies. By the way, i'm using version 2.8.0-SNAPSHOT Thxs Manu 2006/10/31, Dmystery [EMAIL PROTECTED]: Alos, looking at AppcMojo.class file, i dont see any default classpath being set. Here is the stack trace when i try to run the plugin. [INFO] Detailed Appc settings information AppcMojo[basicClientJar = false classpath = null compiler = null debugging = true deprecation = false forceGeneration = false idl = false idlDirectory = null idlFactrories = false idlMethodSignatures = null idlNoAbstractInterfaces = true idlNoValueTypes = true idlOrbix = false idlOverwrite = false idlVerbose = false idlVisiBroker = false iiop = false iiopDirectory = null javaOptions = null keepGenerated = true lineNumbers = true nowarnings = false objectPath = D:\Castle-maven\castle\server\server-ejb\target/castle-server-ejb- 1.0.jar optimization = false outputFile = null verbose = true version = false] [INFO] Argument List for Appc settings [-lineNumbers, -keepgenerated, -g, -verb ose, D:\Castle-maven\castle\server\server-ejb\target/castle-server-ejb-1.0.jar] [appc] Created working directory: C:\DOCUME~1\DEEP_M~1.INF\LOCALS~1\Temp\appcgen [J2EE:160119]Appc is unable to process the file 'D:\Castle-maven\castle\server\s erver-ejb\target\castle-server-ejb-1.0.jar'. The following error occurred: java.lang.NoClassDefFoundError: cadvf2/server/AbstractEJB This is a compile dependency in the POM at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:502) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:12 3) at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(Generic ClassLoader.java:480
RE: [M2]weblogic:appc classpath issue
By autotpes i meant the weblogic.ant.taskdefs.webservices.javaschema.JavaSchema task to generate xml based on Java types. I'm using wls 8.1 sp4. Scott Ryan-2 wrote: I am glad that it is working now. I am anxious to push it up onto the snapshot server. Feel free to let me know what else I can add to help you out. You can enter JIRA tickets in the mojo section so I can track what you need. If you can clarify what you mean by autotypes I will look into that. I hope this weekend to add service gen and jwsc support. Also specify which version of Weblogic you are running. The code it different for 9.0 and 8.1 so that helps me know where to start. Keep the bug reports and feature requests coming and I will work on them as I have time. Scott Ryan Chief Technology Officer Soaring Eagle L.L.C. [EMAIL PROTECTED] www.soaringeagleco.com (303) 263-3044 -Original Message- From: Dmystery [mailto:[EMAIL PROTECTED] Sent: Thursday, November 02, 2006 8:55 PM To: users@maven.apache.org Subject: RE: [M2]weblogic:appc classpath issue I downloaded the code from codehaus SNV and it working fine now. Thanks again! Any plans to include autotypes and servicegen goals in the plugin? :) Currently i'm using maven-antrun-plugin to use weblogic servicegen task. Scott Ryan-2 wrote: I would love to push it but I only have access to SVN at codehaus. I do not have the authority to push up a snapshot any longer and the people who can don't seem to have access to the Weblogic jars required to build the code. I hope I can get this worked out this week. Until then you can just download the code from SVN and run mvn install to place it in your local repository to test. Scott Ryan Chief Technology Officer Soaring Eagle L.L.C. [EMAIL PROTECTED] www.soaringeagleco.com (303) 263-3044 -Original Message- From: Dmystery [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 01, 2006 9:06 PM To: users@maven.apache.org Subject: RE: [M2]weblogic:appc classpath issue Thanks Scott. It would be great if you can push the latest snapshot to the repository now. Scott Ryan-2 wrote: I have refactored the 2.8.0 plugin to fix that problem. I have changed some of the parameters and since the website can only support one version of the plugin I need to add a page to describe the new settings for the 2.8.0 plugin. I will be pushing the latest snapshot up to the repository once I have completed that documentation. This fixes the classpath issue both in appc and the client gen mojos. I have not updated the 2.9.0 version as the 9.2 release broke all the apis I was using so i need to refactor to use the new API's. Let me know if you would prefer I push up the 2.8.0 version now and just post the changes on a note to the user list. Scott Ryan Chief Technology Officer Soaring Eagle L.L.C. [EMAIL PROTECTED] www.soaringeagleco.com (303) 263-3044 -Original Message- From: Manu [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 31, 2006 12:07 PM To: Maven Users List Subject: Re: [M2]weblogic:appc classpath issue Hi, I have the same problem. I need to explicitly set the entire classpath by hand to have it worked. In other words, I'm defining another time all the dependencies that already are in the pom. The plugin does not seem to take into account the dependencies. By the way, i'm using version 2.8.0-SNAPSHOT Thxs Manu 2006/10/31, Dmystery [EMAIL PROTECTED]: Alos, looking at AppcMojo.class file, i dont see any default classpath being set. Here is the stack trace when i try to run the plugin. [INFO] Detailed Appc settings information AppcMojo[basicClientJar = false classpath = null compiler = null debugging = true deprecation = false forceGeneration = false idl = false idlDirectory = null idlFactrories = false idlMethodSignatures = null idlNoAbstractInterfaces = true idlNoValueTypes = true idlOrbix = false idlOverwrite = false idlVerbose = false idlVisiBroker = false iiop = false iiopDirectory = null javaOptions = null keepGenerated = true lineNumbers = true nowarnings = false objectPath = D:\Castle-maven\castle\server\server-ejb\target/castle-server-ejb- 1.0.jar optimization = false outputFile = null verbose = true version = false] [INFO] Argument List for Appc settings [-lineNumbers, -keepgenerated, -g, -verb ose, D:\Castle-maven\castle\server\server-ejb\target/castle-server-ejb-1.0.jar] [appc] Created working directory: C:\DOCUME~1\DEEP_M~1.INF\LOCALS~1\Temp\appcgen [J2EE:160119]Appc is unable to process the file 'D:\Castle-maven\castle\server\s erver-ejb\target\castle-server-ejb-1.0.jar'. The following error occurred: java.lang.NoClassDefFoundError: cadvf2/server/AbstractEJB This is a compile dependency in the POM at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java
Re: [M2]weblogic:appc classpath issue
Can you also tell to WHICH maven repository you will publish it ? Thank you very much for your efforts. 2006/11/2, Dmystery [EMAIL PROTECTED]: Thanks Scott. It would be great if you can push the latest snapshot to the repository now. Scott Ryan-2 wrote: I have refactored the 2.8.0 plugin to fix that problem. I have changed some of the parameters and since the website can only support one version of the plugin I need to add a page to describe the new settings for the 2.8.0 plugin. I will be pushing the latest snapshot up to the repository once I have completed that documentation. This fixes the classpath issue both in appc and the client gen mojos. I have not updated the 2.9.0 version as the 9.2 release broke all the apis I was using so i need to refactor to use the new API's. Let me know if you would prefer I push up the 2.8.0 version now and just post the changes on a note to the user list. Scott Ryan Chief Technology Officer Soaring Eagle L.L.C. [EMAIL PROTECTED] www.soaringeagleco.com (303) 263-3044 -Original Message- From: Manu [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 31, 2006 12:07 PM To: Maven Users List Subject: Re: [M2]weblogic:appc classpath issue Hi, I have the same problem. I need to explicitly set the entire classpath by hand to have it worked. In other words, I'm defining another time all the dependencies that already are in the pom. The plugin does not seem to take into account the dependencies. By the way, i'm using version 2.8.0-SNAPSHOT Thxs Manu 2006/10/31, Dmystery [EMAIL PROTECTED]: Alos, looking at AppcMojo.class file, i dont see any default classpath being set. Here is the stack trace when i try to run the plugin. [INFO] Detailed Appc settings information AppcMojo[basicClientJar = false classpath = null compiler = null debugging = true deprecation = false forceGeneration = false idl = false idlDirectory = null idlFactrories = false idlMethodSignatures = null idlNoAbstractInterfaces = true idlNoValueTypes = true idlOrbix = false idlOverwrite = false idlVerbose = false idlVisiBroker = false iiop = false iiopDirectory = null javaOptions = null keepGenerated = true lineNumbers = true nowarnings = false objectPath = D:\Castle-maven\castle\server\server-ejb\target/castle-server-ejb- 1.0.jar optimization = false outputFile = null verbose = true version = false] [INFO] Argument List for Appc settings [-lineNumbers, -keepgenerated, -g, -verb ose, D:\Castle-maven\castle\server\server-ejb\target/castle- server-ejb-1.0.jar] [appc] Created working directory: C:\DOCUME~1\DEEP_M~1.INF\LOCALS~1\Temp\appcgen [J2EE:160119]Appc is unable to process the file 'D:\Castle-maven\castle\server\s erver-ejb\target\castle-server-ejb-1.0.jar'. The following error occurred: java.lang.NoClassDefFoundError: cadvf2/server/AbstractEJB This is a compile dependency in the POM at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:502) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:12 3) at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(Generic ClassLoader.java:480) at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClass Loader.java:182) at java.lang.ClassLoader.loadClass(ClassLoader.java:299) at java.lang.ClassLoader.loadClass(ClassLoader.java:292) at java.lang.ClassLoader.loadClass(ClassLoader.java:255) at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClass Loader.java:224) at weblogic.ejb20.deployer.BeanInfoImpl.loadClass(BeanInfoImpl.java:343) at weblogic.ejb20.deployer.BeanInfoImpl.init(BeanInfoImpl.java:192) at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.init(ClientDrivenB eanInfoImpl.java:179) at weblogic.ejb20.deployer.SessionBeanInfoImpl.init(SessionBeanInfoImp l.java:74) at weblogic.ejb20.deployer.BeanInfoImpl.createBeanInfoImpl(BeanInfoImpl. java:367) at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(M BeanDeploymentInfoImpl.java:548) at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.init(MBeanDeploymen tInfoImpl.java:232) at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java :155) at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java :415) at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java :387) at weblogic.appc.compileEJB(appc.java:802) at weblogic.appc.compileEJB(appc.java:776) at weblogic.appc.compileInput(appc.java:463) at weblogic.appc.runBody(appc.java:184) at weblogic.utils.compiler.Tool.run(Tool.java:192) at weblogic.utils.compiler.Tool.run(Tool.java:147) at weblogic.appc.main(appc.java:1030
SV: [M2]weblogic:appc classpath issue
Also, you mention the 9.2 release. As we're using WLS 8.1.3 will we miss out on this fix? /jonas -Ursprungligt meddelande- Från: Manu [mailto:[EMAIL PROTECTED] Skickat: den 2 november 2006 10:27 Till: Maven Users List Ämne: Re: [M2]weblogic:appc classpath issue Can you also tell to WHICH maven repository you will publish it ? Thank you very much for your efforts. 2006/11/2, Dmystery [EMAIL PROTECTED]: Thanks Scott. It would be great if you can push the latest snapshot to the repository now. Scott Ryan-2 wrote: I have refactored the 2.8.0 plugin to fix that problem. I have changed some of the parameters and since the website can only support one version of the plugin I need to add a page to describe the new settings for the 2.8.0 plugin. I will be pushing the latest snapshot up to the repository once I have completed that documentation. This fixes the classpath issue both in appc and the client gen mojos. I have not updated the 2.9.0 version as the 9.2 release broke all the apis I was using so i need to refactor to use the new API's. Let me know if you would prefer I push up the 2.8.0 version now and just post the changes on a note to the user list. Scott Ryan Chief Technology Officer Soaring Eagle L.L.C. [EMAIL PROTECTED] www.soaringeagleco.com (303) 263-3044 -Original Message- From: Manu [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 31, 2006 12:07 PM To: Maven Users List Subject: Re: [M2]weblogic:appc classpath issue Hi, I have the same problem. I need to explicitly set the entire classpath by hand to have it worked. In other words, I'm defining another time all the dependencies that already are in the pom. The plugin does not seem to take into account the dependencies. By the way, i'm using version 2.8.0-SNAPSHOT Thxs Manu 2006/10/31, Dmystery [EMAIL PROTECTED]: Alos, looking at AppcMojo.class file, i dont see any default classpath being set. Here is the stack trace when i try to run the plugin. [INFO] Detailed Appc settings information AppcMojo[basicClientJar = false classpath = null compiler = null debugging = true deprecation = false forceGeneration = false idl = false idlDirectory = null idlFactrories = false idlMethodSignatures = null idlNoAbstractInterfaces = true idlNoValueTypes = true idlOrbix = false idlOverwrite = false idlVerbose = false idlVisiBroker = false iiop = false iiopDirectory = null javaOptions = null keepGenerated = true lineNumbers = true nowarnings = false objectPath = D:\Castle-maven\castle\server\server-ejb\target/castle-server-ejb- 1.0.jar optimization = false outputFile = null verbose = true version = false] [INFO] Argument List for Appc settings [-lineNumbers, -keepgenerated, -g, -verb ose, D:\Castle-maven\castle\server\server-ejb\target/castle- server-ejb-1.0.jar] [appc] Created working directory: C:\DOCUME~1\DEEP_M~1.INF\LOCALS~1\Temp\appcgen [J2EE:160119]Appc is unable to process the file 'D:\Castle-maven\castle\server\s erver-ejb\target\castle-server-ejb-1.0.jar'. The following error occurred: java.lang.NoClassDefFoundError: cadvf2/server/AbstractEJB This is a compile dependency in the POM at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:502) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:12 3) at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(Generic ClassLoader.java:480) at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClass Loader.java:182) at java.lang.ClassLoader.loadClass(ClassLoader.java:299) at java.lang.ClassLoader.loadClass(ClassLoader.java:292) at java.lang.ClassLoader.loadClass(ClassLoader.java:255) at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClass Loader.java:224) at weblogic.ejb20.deployer.BeanInfoImpl.loadClass(BeanInfoImpl.java:343) at weblogic.ejb20.deployer.BeanInfoImpl.init(BeanInfoImpl.java:192) at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.init(ClientDrivenB eanInfoImpl.java:179) at weblogic.ejb20.deployer.SessionBeanInfoImpl.init(SessionBeanInfoImp l.java:74) at weblogic.ejb20.deployer.BeanInfoImpl.createBeanInfoImpl(BeanInfoImpl. java:367) at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(M BeanDeploymentInfoImpl.java:548) at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.init(MBeanDeploymen tInfoImpl.java:232) at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java :155) at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java :415) at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java :387
RE: [M2]weblogic:appc classpath issue
I would love to push it but I only have access to SVN at codehaus. I do not have the authority to push up a snapshot any longer and the people who can don't seem to have access to the Weblogic jars required to build the code. I hope I can get this worked out this week. Until then you can just download the code from SVN and run mvn install to place it in your local repository to test. Scott Ryan Chief Technology Officer Soaring Eagle L.L.C. [EMAIL PROTECTED] www.soaringeagleco.com (303) 263-3044 -Original Message- From: Dmystery [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 01, 2006 9:06 PM To: users@maven.apache.org Subject: RE: [M2]weblogic:appc classpath issue Thanks Scott. It would be great if you can push the latest snapshot to the repository now. Scott Ryan-2 wrote: I have refactored the 2.8.0 plugin to fix that problem. I have changed some of the parameters and since the website can only support one version of the plugin I need to add a page to describe the new settings for the 2.8.0 plugin. I will be pushing the latest snapshot up to the repository once I have completed that documentation. This fixes the classpath issue both in appc and the client gen mojos. I have not updated the 2.9.0 version as the 9.2 release broke all the apis I was using so i need to refactor to use the new API's. Let me know if you would prefer I push up the 2.8.0 version now and just post the changes on a note to the user list. Scott Ryan Chief Technology Officer Soaring Eagle L.L.C. [EMAIL PROTECTED] www.soaringeagleco.com (303) 263-3044 -Original Message- From: Manu [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 31, 2006 12:07 PM To: Maven Users List Subject: Re: [M2]weblogic:appc classpath issue Hi, I have the same problem. I need to explicitly set the entire classpath by hand to have it worked. In other words, I'm defining another time all the dependencies that already are in the pom. The plugin does not seem to take into account the dependencies. By the way, i'm using version 2.8.0-SNAPSHOT Thxs Manu 2006/10/31, Dmystery [EMAIL PROTECTED]: Alos, looking at AppcMojo.class file, i dont see any default classpath being set. Here is the stack trace when i try to run the plugin. [INFO] Detailed Appc settings information AppcMojo[basicClientJar = false classpath = null compiler = null debugging = true deprecation = false forceGeneration = false idl = false idlDirectory = null idlFactrories = false idlMethodSignatures = null idlNoAbstractInterfaces = true idlNoValueTypes = true idlOrbix = false idlOverwrite = false idlVerbose = false idlVisiBroker = false iiop = false iiopDirectory = null javaOptions = null keepGenerated = true lineNumbers = true nowarnings = false objectPath = D:\Castle-maven\castle\server\server-ejb\target/castle-server-ejb- 1.0.jar optimization = false outputFile = null verbose = true version = false] [INFO] Argument List for Appc settings [-lineNumbers, -keepgenerated, -g, -verb ose, D:\Castle-maven\castle\server\server-ejb\target/castle-server-ejb-1.0.jar] [appc] Created working directory: C:\DOCUME~1\DEEP_M~1.INF\LOCALS~1\Temp\appcgen [J2EE:160119]Appc is unable to process the file 'D:\Castle-maven\castle\server\s erver-ejb\target\castle-server-ejb-1.0.jar'. The following error occurred: java.lang.NoClassDefFoundError: cadvf2/server/AbstractEJB This is a compile dependency in the POM at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:502) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:12 3) at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(Generic ClassLoader.java:480) at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClass Loader.java:182) at java.lang.ClassLoader.loadClass(ClassLoader.java:299) at java.lang.ClassLoader.loadClass(ClassLoader.java:292) at java.lang.ClassLoader.loadClass(ClassLoader.java:255) at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClass Loader.java:224) at weblogic.ejb20.deployer.BeanInfoImpl.loadClass(BeanInfoImpl.java:343) at weblogic.ejb20.deployer.BeanInfoImpl.init(BeanInfoImpl.java:192) at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.init(ClientDrivenB eanInfoImpl.java:179) at weblogic.ejb20.deployer.SessionBeanInfoImpl.init(SessionBeanInfoImp l.java:74) at weblogic.ejb20.deployer.BeanInfoImpl.createBeanInfoImpl(BeanInfoImpl. java:367) at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(M BeanDeploymentInfoImpl.java:548) at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.init(MBeanDeploymen tInfoImpl.java:232) at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:155) at weblogic.ejb20
RE: [M2]weblogic:appc classpath issue
The 2.8.0 version of the plugin is for 8.1.4 and above. It will work for 8.1.3 and below for all but remote deployments. If you need it I can retro fit the remote deployment back to 8.1.3 2.8.0-SNAPSHOT supports the 8.1 version of Weblogic for all versions except remote deployment which requires sp4 and above 2.9.0-SNAPSHOT supports 9.0 with all patch levels The 2.9.0 code is on the trunk and the 2.8.0 code is on the branch. Let me know if you need more information. Scott Ryan Chief Technology Officer Soaring Eagle L.L.C. [EMAIL PROTECTED] www.soaringeagleco.com (303) 263-3044 -Original Message- From: Jonas Olsson [mailto:[EMAIL PROTECTED] Sent: Thursday, November 02, 2006 2:41 AM To: Maven Users List Subject: SV: [M2]weblogic:appc classpath issue Also, you mention the 9.2 release. As we're using WLS 8.1.3 will we miss out on this fix? /jonas -Ursprungligt meddelande- Från: Manu [mailto:[EMAIL PROTECTED] Skickat: den 2 november 2006 10:27 Till: Maven Users List Ämne: Re: [M2]weblogic:appc classpath issue Can you also tell to WHICH maven repository you will publish it ? Thank you very much for your efforts. 2006/11/2, Dmystery [EMAIL PROTECTED]: Thanks Scott. It would be great if you can push the latest snapshot to the repository now. Scott Ryan-2 wrote: I have refactored the 2.8.0 plugin to fix that problem. I have changed some of the parameters and since the website can only support one version of the plugin I need to add a page to describe the new settings for the 2.8.0 plugin. I will be pushing the latest snapshot up to the repository once I have completed that documentation. This fixes the classpath issue both in appc and the client gen mojos. I have not updated the 2.9.0 version as the 9.2 release broke all the apis I was using so i need to refactor to use the new API's. Let me know if you would prefer I push up the 2.8.0 version now and just post the changes on a note to the user list. Scott Ryan Chief Technology Officer Soaring Eagle L.L.C. [EMAIL PROTECTED] www.soaringeagleco.com (303) 263-3044 -Original Message- From: Manu [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 31, 2006 12:07 PM To: Maven Users List Subject: Re: [M2]weblogic:appc classpath issue Hi, I have the same problem. I need to explicitly set the entire classpath by hand to have it worked. In other words, I'm defining another time all the dependencies that already are in the pom. The plugin does not seem to take into account the dependencies. By the way, i'm using version 2.8.0-SNAPSHOT Thxs Manu 2006/10/31, Dmystery [EMAIL PROTECTED]: Alos, looking at AppcMojo.class file, i dont see any default classpath being set. Here is the stack trace when i try to run the plugin. [INFO] Detailed Appc settings information AppcMojo[basicClientJar = false classpath = null compiler = null debugging = true deprecation = false forceGeneration = false idl = false idlDirectory = null idlFactrories = false idlMethodSignatures = null idlNoAbstractInterfaces = true idlNoValueTypes = true idlOrbix = false idlOverwrite = false idlVerbose = false idlVisiBroker = false iiop = false iiopDirectory = null javaOptions = null keepGenerated = true lineNumbers = true nowarnings = false objectPath = D:\Castle-maven\castle\server\server-ejb\target/castle-server-ejb- 1.0.jar optimization = false outputFile = null verbose = true version = false] [INFO] Argument List for Appc settings [-lineNumbers, -keepgenerated, -g, -verb ose, D:\Castle-maven\castle\server\server-ejb\target/castle- server-ejb-1.0.jar] [appc] Created working directory: C:\DOCUME~1\DEEP_M~1.INF\LOCALS~1\Temp\appcgen [J2EE:160119]Appc is unable to process the file 'D:\Castle-maven\castle\server\s erver-ejb\target\castle-server-ejb-1.0.jar'. The following error occurred: java.lang.NoClassDefFoundError: cadvf2/server/AbstractEJB This is a compile dependency in the POM at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:502) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:12 3) at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(Generic ClassLoader.java:480) at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClass Loader.java:182) at java.lang.ClassLoader.loadClass(ClassLoader.java:299) at java.lang.ClassLoader.loadClass(ClassLoader.java:292) at java.lang.ClassLoader.loadClass(ClassLoader.java:255) at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClass Loader.java:224) at weblogic.ejb20.deployer.BeanInfoImpl.loadClass(BeanInfoImpl.java:343) at weblogic.ejb20.deployer.BeanInfoImpl.init(BeanInfoImpl.java:192
RE: [M2]weblogic:appc classpath issue
I downloaded the code from codehaus SNV and it working fine now. Thanks again! Any plans to include autotypes and servicegen goals in the plugin? :) Currently i'm using maven-antrun-plugin to use weblogic servicegen task. Scott Ryan-2 wrote: I would love to push it but I only have access to SVN at codehaus. I do not have the authority to push up a snapshot any longer and the people who can don't seem to have access to the Weblogic jars required to build the code. I hope I can get this worked out this week. Until then you can just download the code from SVN and run mvn install to place it in your local repository to test. Scott Ryan Chief Technology Officer Soaring Eagle L.L.C. [EMAIL PROTECTED] www.soaringeagleco.com (303) 263-3044 -Original Message- From: Dmystery [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 01, 2006 9:06 PM To: users@maven.apache.org Subject: RE: [M2]weblogic:appc classpath issue Thanks Scott. It would be great if you can push the latest snapshot to the repository now. Scott Ryan-2 wrote: I have refactored the 2.8.0 plugin to fix that problem. I have changed some of the parameters and since the website can only support one version of the plugin I need to add a page to describe the new settings for the 2.8.0 plugin. I will be pushing the latest snapshot up to the repository once I have completed that documentation. This fixes the classpath issue both in appc and the client gen mojos. I have not updated the 2.9.0 version as the 9.2 release broke all the apis I was using so i need to refactor to use the new API's. Let me know if you would prefer I push up the 2.8.0 version now and just post the changes on a note to the user list. Scott Ryan Chief Technology Officer Soaring Eagle L.L.C. [EMAIL PROTECTED] www.soaringeagleco.com (303) 263-3044 -Original Message- From: Manu [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 31, 2006 12:07 PM To: Maven Users List Subject: Re: [M2]weblogic:appc classpath issue Hi, I have the same problem. I need to explicitly set the entire classpath by hand to have it worked. In other words, I'm defining another time all the dependencies that already are in the pom. The plugin does not seem to take into account the dependencies. By the way, i'm using version 2.8.0-SNAPSHOT Thxs Manu 2006/10/31, Dmystery [EMAIL PROTECTED]: Alos, looking at AppcMojo.class file, i dont see any default classpath being set. Here is the stack trace when i try to run the plugin. [INFO] Detailed Appc settings information AppcMojo[basicClientJar = false classpath = null compiler = null debugging = true deprecation = false forceGeneration = false idl = false idlDirectory = null idlFactrories = false idlMethodSignatures = null idlNoAbstractInterfaces = true idlNoValueTypes = true idlOrbix = false idlOverwrite = false idlVerbose = false idlVisiBroker = false iiop = false iiopDirectory = null javaOptions = null keepGenerated = true lineNumbers = true nowarnings = false objectPath = D:\Castle-maven\castle\server\server-ejb\target/castle-server-ejb- 1.0.jar optimization = false outputFile = null verbose = true version = false] [INFO] Argument List for Appc settings [-lineNumbers, -keepgenerated, -g, -verb ose, D:\Castle-maven\castle\server\server-ejb\target/castle-server-ejb-1.0.jar] [appc] Created working directory: C:\DOCUME~1\DEEP_M~1.INF\LOCALS~1\Temp\appcgen [J2EE:160119]Appc is unable to process the file 'D:\Castle-maven\castle\server\s erver-ejb\target\castle-server-ejb-1.0.jar'. The following error occurred: java.lang.NoClassDefFoundError: cadvf2/server/AbstractEJB This is a compile dependency in the POM at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:502) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:12 3) at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(Generic ClassLoader.java:480) at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClass Loader.java:182) at java.lang.ClassLoader.loadClass(ClassLoader.java:299) at java.lang.ClassLoader.loadClass(ClassLoader.java:292) at java.lang.ClassLoader.loadClass(ClassLoader.java:255) at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClass Loader.java:224) at weblogic.ejb20.deployer.BeanInfoImpl.loadClass(BeanInfoImpl.java:343) at weblogic.ejb20.deployer.BeanInfoImpl.init(BeanInfoImpl.java:192) at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.init(ClientDrivenB eanInfoImpl.java:179) at weblogic.ejb20.deployer.SessionBeanInfoImpl.init(SessionBeanInfoImp l.java:74) at weblogic.ejb20.deployer.BeanInfoImpl.createBeanInfoImpl(BeanInfoImpl. java:367) at weblogic.ejb20
RE: [M2]weblogic:appc classpath issue
I have refactored the 2.8.0 plugin to fix that problem. I have changed some of the parameters and since the website can only support one version of the plugin I need to add a page to describe the new settings for the 2.8.0 plugin. I will be pushing the latest snapshot up to the repository once I have completed that documentation. This fixes the classpath issue both in appc and the client gen mojos. I have not updated the 2.9.0 version as the 9.2 release broke all the apis I was using so i need to refactor to use the new API's. Let me know if you would prefer I push up the 2.8.0 version now and just post the changes on a note to the user list. Scott Ryan Chief Technology Officer Soaring Eagle L.L.C. [EMAIL PROTECTED] www.soaringeagleco.com (303) 263-3044 -Original Message- From: Manu [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 31, 2006 12:07 PM To: Maven Users List Subject: Re: [M2]weblogic:appc classpath issue Hi, I have the same problem. I need to explicitly set the entire classpath by hand to have it worked. In other words, I'm defining another time all the dependencies that already are in the pom. The plugin does not seem to take into account the dependencies. By the way, i'm using version 2.8.0-SNAPSHOT Thxs Manu 2006/10/31, Dmystery [EMAIL PROTECTED]: Alos, looking at AppcMojo.class file, i dont see any default classpath being set. Here is the stack trace when i try to run the plugin. [INFO] Detailed Appc settings information AppcMojo[basicClientJar = false classpath = null compiler = null debugging = true deprecation = false forceGeneration = false idl = false idlDirectory = null idlFactrories = false idlMethodSignatures = null idlNoAbstractInterfaces = true idlNoValueTypes = true idlOrbix = false idlOverwrite = false idlVerbose = false idlVisiBroker = false iiop = false iiopDirectory = null javaOptions = null keepGenerated = true lineNumbers = true nowarnings = false objectPath = D:\Castle-maven\castle\server\server-ejb\target/castle-server-ejb- 1.0.jar optimization = false outputFile = null verbose = true version = false] [INFO] Argument List for Appc settings [-lineNumbers, -keepgenerated, -g, -verb ose, D:\Castle-maven\castle\server\server-ejb\target/castle-server-ejb-1.0.jar] [appc] Created working directory: C:\DOCUME~1\DEEP_M~1.INF\LOCALS~1\Temp\appcgen [J2EE:160119]Appc is unable to process the file 'D:\Castle-maven\castle\server\s erver-ejb\target\castle-server-ejb-1.0.jar'. The following error occurred: java.lang.NoClassDefFoundError: cadvf2/server/AbstractEJB This is a compile dependency in the POM at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:502) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:12 3) at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(Generic ClassLoader.java:480) at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClass Loader.java:182) at java.lang.ClassLoader.loadClass(ClassLoader.java:299) at java.lang.ClassLoader.loadClass(ClassLoader.java:292) at java.lang.ClassLoader.loadClass(ClassLoader.java:255) at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClass Loader.java:224) at weblogic.ejb20.deployer.BeanInfoImpl.loadClass(BeanInfoImpl.java:343) at weblogic.ejb20.deployer.BeanInfoImpl.init(BeanInfoImpl.java:192) at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.init(ClientDrivenB eanInfoImpl.java:179) at weblogic.ejb20.deployer.SessionBeanInfoImpl.init(SessionBeanInfoImp l.java:74) at weblogic.ejb20.deployer.BeanInfoImpl.createBeanInfoImpl(BeanInfoImpl. java:367) at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(M BeanDeploymentInfoImpl.java:548) at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.init(MBeanDeploymen tInfoImpl.java:232) at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:155) at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java :415) at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java :387) at weblogic.appc.compileEJB(appc.java:802) at weblogic.appc.compileEJB(appc.java:776) at weblogic.appc.compileInput(appc.java:463) at weblogic.appc.runBody(appc.java:184) at weblogic.utils.compiler.Tool.run(Tool.java:192) at weblogic.utils.compiler.Tool.run(Tool.java:147) at weblogic.appc.main(appc.java:1030) at org.codehaus.mojo.weblogic.AppcMojo.execute(AppcMojo.java:276) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi nManager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:534
RE: [M2]weblogic:appc classpath issue
The fix is in the code on the branch 2.8.0. i am trying to publish the fixes if I can get authorization. You can pull down the code and build it and that should fix your classpath issues. Scott Ryan Chief Technology Officer Soaring Eagle L.L.C. [EMAIL PROTECTED] www.soaringeagleco.com (303) 263-3044 -Original Message- From: Manu [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 31, 2006 12:07 PM To: Maven Users List Subject: Re: [M2]weblogic:appc classpath issue Hi, I have the same problem. I need to explicitly set the entire classpath by hand to have it worked. In other words, I'm defining another time all the dependencies that already are in the pom. The plugin does not seem to take into account the dependencies. By the way, i'm using version 2.8.0-SNAPSHOT Thxs Manu 2006/10/31, Dmystery [EMAIL PROTECTED]: Alos, looking at AppcMojo.class file, i dont see any default classpath being set. Here is the stack trace when i try to run the plugin. [INFO] Detailed Appc settings information AppcMojo[basicClientJar = false classpath = null compiler = null debugging = true deprecation = false forceGeneration = false idl = false idlDirectory = null idlFactrories = false idlMethodSignatures = null idlNoAbstractInterfaces = true idlNoValueTypes = true idlOrbix = false idlOverwrite = false idlVerbose = false idlVisiBroker = false iiop = false iiopDirectory = null javaOptions = null keepGenerated = true lineNumbers = true nowarnings = false objectPath = D:\Castle-maven\castle\server\server-ejb\target/castle-server-ejb- 1.0.jar optimization = false outputFile = null verbose = true version = false] [INFO] Argument List for Appc settings [-lineNumbers, -keepgenerated, -g, -verb ose, D:\Castle-maven\castle\server\server-ejb\target/castle-server-ejb-1.0.jar] [appc] Created working directory: C:\DOCUME~1\DEEP_M~1.INF\LOCALS~1\Temp\appcgen [J2EE:160119]Appc is unable to process the file 'D:\Castle-maven\castle\server\s erver-ejb\target\castle-server-ejb-1.0.jar'. The following error occurred: java.lang.NoClassDefFoundError: cadvf2/server/AbstractEJB This is a compile dependency in the POM at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:502) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:12 3) at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(Generic ClassLoader.java:480) at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClass Loader.java:182) at java.lang.ClassLoader.loadClass(ClassLoader.java:299) at java.lang.ClassLoader.loadClass(ClassLoader.java:292) at java.lang.ClassLoader.loadClass(ClassLoader.java:255) at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClass Loader.java:224) at weblogic.ejb20.deployer.BeanInfoImpl.loadClass(BeanInfoImpl.java:343) at weblogic.ejb20.deployer.BeanInfoImpl.init(BeanInfoImpl.java:192) at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.init(ClientDrivenB eanInfoImpl.java:179) at weblogic.ejb20.deployer.SessionBeanInfoImpl.init(SessionBeanInfoImp l.java:74) at weblogic.ejb20.deployer.BeanInfoImpl.createBeanInfoImpl(BeanInfoImpl. java:367) at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(M BeanDeploymentInfoImpl.java:548) at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.init(MBeanDeploymen tInfoImpl.java:232) at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:155) at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java :415) at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java :387) at weblogic.appc.compileEJB(appc.java:802) at weblogic.appc.compileEJB(appc.java:776) at weblogic.appc.compileInput(appc.java:463) at weblogic.appc.runBody(appc.java:184) at weblogic.utils.compiler.Tool.run(Tool.java:192) at weblogic.utils.compiler.Tool.run(Tool.java:147) at weblogic.appc.main(appc.java:1030) at org.codehaus.mojo.weblogic.AppcMojo.execute(AppcMojo.java:276) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi nManager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:534) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi fecycle(DefaultLifecycleExecutor.java:475) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau ltLifecycleExecutor.java:454) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan dleFailures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen ts(DefaultLifecycleExecutor.java:273
RE: [M2]weblogic:appc classpath issue
The code is checked in to SVN to fix this. I will try to push a new snapshot as soon as i can get authorization Scott Ryan Chief Technology Officer Soaring Eagle L.L.C. [EMAIL PROTECTED] www.soaringeagleco.com (303) 263-3044 -Original Message- From: Dmystery [mailto:[EMAIL PROTECTED] Sent: Monday, October 30, 2006 11:47 PM To: users@maven.apache.org Subject: RE: [M2]weblogic:appc classpath issue Alos, looking at AppcMojo.class file, i dont see any default classpath being set. Here is the stack trace when i try to run the plugin. [INFO] Detailed Appc settings information AppcMojo[basicClientJar = false classpath = null compiler = null debugging = true deprecation = false forceGeneration = false idl = false idlDirectory = null idlFactrories = false idlMethodSignatures = null idlNoAbstractInterfaces = true idlNoValueTypes = true idlOrbix = false idlOverwrite = false idlVerbose = false idlVisiBroker = false iiop = false iiopDirectory = null javaOptions = null keepGenerated = true lineNumbers = true nowarnings = false objectPath = D:\Castle-maven\castle\server\server-ejb\target/castle-server-ejb- 1.0.jar optimization = false outputFile = null verbose = true version = false] [INFO] Argument List for Appc settings [-lineNumbers, -keepgenerated, -g, -verb ose, D:\Castle-maven\castle\server\server-ejb\target/castle-server-ejb-1.0.jar] [appc] Created working directory: C:\DOCUME~1\DEEP_M~1.INF\LOCALS~1\Temp\appcgen [J2EE:160119]Appc is unable to process the file 'D:\Castle-maven\castle\server\s erver-ejb\target\castle-server-ejb-1.0.jar'. The following error occurred: java.lang.NoClassDefFoundError: cadvf2/server/AbstractEJB This is a compile dependency in the POM at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:502) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:12 3) at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(Generic ClassLoader.java:480) at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClass Loader.java:182) at java.lang.ClassLoader.loadClass(ClassLoader.java:299) at java.lang.ClassLoader.loadClass(ClassLoader.java:292) at java.lang.ClassLoader.loadClass(ClassLoader.java:255) at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClass Loader.java:224) at weblogic.ejb20.deployer.BeanInfoImpl.loadClass(BeanInfoImpl.java:343) at weblogic.ejb20.deployer.BeanInfoImpl.init(BeanInfoImpl.java:192) at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.init(ClientDrivenB eanInfoImpl.java:179) at weblogic.ejb20.deployer.SessionBeanInfoImpl.init(SessionBeanInfoImp l.java:74) at weblogic.ejb20.deployer.BeanInfoImpl.createBeanInfoImpl(BeanInfoImpl. java:367) at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(M BeanDeploymentInfoImpl.java:548) at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.init(MBeanDeploymen tInfoImpl.java:232) at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:155) at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:415) at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:387) at weblogic.appc.compileEJB(appc.java:802) at weblogic.appc.compileEJB(appc.java:776) at weblogic.appc.compileInput(appc.java:463) at weblogic.appc.runBody(appc.java:184) at weblogic.utils.compiler.Tool.run(Tool.java:192) at weblogic.utils.compiler.Tool.run(Tool.java:147) at weblogic.appc.main(appc.java:1030) at org.codehaus.mojo.weblogic.AppcMojo.execute(AppcMojo.java:276) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi nManager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:534) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi fecycle(DefaultLifecycleExecutor.java:475) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau ltLifecycleExecutor.java:454) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan dleFailures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen ts(DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi fecycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke
RE: [M2]weblogic:appc classpath issue
Thanks Scott. It would be great if you can push the latest snapshot to the repository now. Scott Ryan-2 wrote: I have refactored the 2.8.0 plugin to fix that problem. I have changed some of the parameters and since the website can only support one version of the plugin I need to add a page to describe the new settings for the 2.8.0 plugin. I will be pushing the latest snapshot up to the repository once I have completed that documentation. This fixes the classpath issue both in appc and the client gen mojos. I have not updated the 2.9.0 version as the 9.2 release broke all the apis I was using so i need to refactor to use the new API's. Let me know if you would prefer I push up the 2.8.0 version now and just post the changes on a note to the user list. Scott Ryan Chief Technology Officer Soaring Eagle L.L.C. [EMAIL PROTECTED] www.soaringeagleco.com (303) 263-3044 -Original Message- From: Manu [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 31, 2006 12:07 PM To: Maven Users List Subject: Re: [M2]weblogic:appc classpath issue Hi, I have the same problem. I need to explicitly set the entire classpath by hand to have it worked. In other words, I'm defining another time all the dependencies that already are in the pom. The plugin does not seem to take into account the dependencies. By the way, i'm using version 2.8.0-SNAPSHOT Thxs Manu 2006/10/31, Dmystery [EMAIL PROTECTED]: Alos, looking at AppcMojo.class file, i dont see any default classpath being set. Here is the stack trace when i try to run the plugin. [INFO] Detailed Appc settings information AppcMojo[basicClientJar = false classpath = null compiler = null debugging = true deprecation = false forceGeneration = false idl = false idlDirectory = null idlFactrories = false idlMethodSignatures = null idlNoAbstractInterfaces = true idlNoValueTypes = true idlOrbix = false idlOverwrite = false idlVerbose = false idlVisiBroker = false iiop = false iiopDirectory = null javaOptions = null keepGenerated = true lineNumbers = true nowarnings = false objectPath = D:\Castle-maven\castle\server\server-ejb\target/castle-server-ejb- 1.0.jar optimization = false outputFile = null verbose = true version = false] [INFO] Argument List for Appc settings [-lineNumbers, -keepgenerated, -g, -verb ose, D:\Castle-maven\castle\server\server-ejb\target/castle-server-ejb-1.0.jar] [appc] Created working directory: C:\DOCUME~1\DEEP_M~1.INF\LOCALS~1\Temp\appcgen [J2EE:160119]Appc is unable to process the file 'D:\Castle-maven\castle\server\s erver-ejb\target\castle-server-ejb-1.0.jar'. The following error occurred: java.lang.NoClassDefFoundError: cadvf2/server/AbstractEJB This is a compile dependency in the POM at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:502) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:12 3) at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(Generic ClassLoader.java:480) at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClass Loader.java:182) at java.lang.ClassLoader.loadClass(ClassLoader.java:299) at java.lang.ClassLoader.loadClass(ClassLoader.java:292) at java.lang.ClassLoader.loadClass(ClassLoader.java:255) at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClass Loader.java:224) at weblogic.ejb20.deployer.BeanInfoImpl.loadClass(BeanInfoImpl.java:343) at weblogic.ejb20.deployer.BeanInfoImpl.init(BeanInfoImpl.java:192) at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.init(ClientDrivenB eanInfoImpl.java:179) at weblogic.ejb20.deployer.SessionBeanInfoImpl.init(SessionBeanInfoImp l.java:74) at weblogic.ejb20.deployer.BeanInfoImpl.createBeanInfoImpl(BeanInfoImpl. java:367) at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(M BeanDeploymentInfoImpl.java:548) at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.init(MBeanDeploymen tInfoImpl.java:232) at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:155) at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java :415) at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java :387) at weblogic.appc.compileEJB(appc.java:802) at weblogic.appc.compileEJB(appc.java:776) at weblogic.appc.compileInput(appc.java:463) at weblogic.appc.runBody(appc.java:184) at weblogic.utils.compiler.Tool.run(Tool.java:192) at weblogic.utils.compiler.Tool.run(Tool.java:147) at weblogic.appc.main(appc.java:1030) at org.codehaus.mojo.weblogic.AppcMojo.execute(AppcMojo.java:276) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi nManager.java:412
Re: [M2]weblogic:appc classpath issue
(Method.java:324)
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)
Dmystery wrote:
I still have issue in compiling the ejb jar file. It simply fails to
find
all the dependencies in the classpath.
Here is the plugin definition again.
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdweblogic-maven-plugin/artifactId
version2.8.0-SNAPSHOT/version
configuration
objectPath${project.build.directory}/${project.artifactId}-${
project.version}.jar/objectPath
verbosetrue/verbose
debuggingtrue/debugging
nowarningsfalse/nowarnings
lineNumberstrue/lineNumbers
keepGeneratedtrue/keepGenerated
/configuration
executions
execution
phasepackage/phase
goals
goalappc/goal
/goals
/execution
/executions
/plugin
All the required jars for appc are defined as 'compile' dependecies in
the
pom. Still it gives me a NoClassDefFoundError for the required class
files.
Scott Ryan-2 wrote:
How did you make out with the appc mojo? I am updating the plugin to
simplify it this weekend and will update the code with some code that
was
posted in JIRA. Let me know your status and I will send out a note on
the
weekend when the new code is available.
Scott Ryan
Chief Technology Officer
Soaring Eagle L.L.C.
[EMAIL PROTECTED]
www.soaringeagleco.com
(303) 263-3044
-Original Message-
From: Dmystery [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 18, 2006 2:39 AM
To: users@maven.apache.org
Subject: [M2]weblogic:appc classpath issue
I'm using weblogic-maven-plugin to compile my ejb.jar. Here is the
plugin
definition.
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdweblogic-maven-plugin/artifactId
version2.8.0-SNAPSHOT/version
configuration
objectPath${project.build.directory}/${project.artifactId}-${
project.versi
on}.jar/objectPath
verbosetrue/verbose
debuggingtrue/debugging
nowarningsfalse/nowarnings
lineNumberstrue/lineNumbers
keepGeneratedtrue/keepGenerated
classpath${project.runtimeClasspathElements}/classpath
/configuration
executions
execution
phasepackage/phase
goals
goalappc/goal
/goals
/execution
/executions
/plugin
The ${project.runtimeClasspathElements} is a string like [somedir\jar1,
somedir\jar2]. Because of this the plugin throws a
org.codehaus.plexus.component.configurator.ComponentConfigurationException
:
Invalid parameter supplied while setting '[somedir\jar1, somedir\jar2]'
Are we supposed to provide classpath/classpath in the first place?
or
will it consider ${project.runtimeClasspathElements} as the default
classpath? (I guess not).
If i remove the classpath/classpath from the plugin definition (as
it
is
optional), it fails to find some of the classes that it needs to
compile
the
ejb.jar even though they are defined as dependencies in the project.
Let me know if i'm doing something wrong.
--
View this message in context:
http://www.nabble.com/-M2-weblogic%3Aappc-classpath-issue-tf2465090.html#a68
71847
Sent from the Maven - Users mailing list archive at Nabble.com.
-
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]
--
View this message in context:
http://www.nabble.com/-M2-weblogic%3Aappc-classpath-issue-tf2465090s177.html#a7089129
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Manu (:-Þ)
RE: [M2]weblogic:appc classpath issue
I still have issue in compiling the ejb jar file. It simply fails to find all
the dependencies in the classpath.
Here is the plugin definition again.
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdweblogic-maven-plugin/artifactId
version2.8.0-SNAPSHOT/version
configuration
objectPath${project.build.directory}/${project.artifactId}-${project.version}.jar/objectPath
verbosetrue/verbose
debuggingtrue/debugging
nowarningsfalse/nowarnings
lineNumberstrue/lineNumbers
keepGeneratedtrue/keepGenerated
/configuration
executions
execution
phasepackage/phase
goals
goalappc/goal
/goals
/execution
/executions
/plugin
All the required jars for appc are defined as 'compile' dependecies in the
pom. Still it gives me a NoClassDefFoundError for the required class files.
Scott Ryan-2 wrote:
How did you make out with the appc mojo? I am updating the plugin to
simplify it this weekend and will update the code with some code that was
posted in JIRA. Let me know your status and I will send out a note on the
weekend when the new code is available.
Scott Ryan
Chief Technology Officer
Soaring Eagle L.L.C.
[EMAIL PROTECTED]
www.soaringeagleco.com
(303) 263-3044
-Original Message-
From: Dmystery [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 18, 2006 2:39 AM
To: users@maven.apache.org
Subject: [M2]weblogic:appc classpath issue
I'm using weblogic-maven-plugin to compile my ejb.jar. Here is the plugin
definition.
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdweblogic-maven-plugin/artifactId
version2.8.0-SNAPSHOT/version
configuration
objectPath${project.build.directory}/${project.artifactId}-${project.versi
on}.jar/objectPath
verbosetrue/verbose
debuggingtrue/debugging
nowarningsfalse/nowarnings
lineNumberstrue/lineNumbers
keepGeneratedtrue/keepGenerated
classpath${project.runtimeClasspathElements}/classpath
/configuration
executions
execution
phasepackage/phase
goals
goalappc/goal
/goals
/execution
/executions
/plugin
The ${project.runtimeClasspathElements} is a string like [somedir\jar1,
somedir\jar2]. Because of this the plugin throws a
org.codehaus.plexus.component.configurator.ComponentConfigurationException
:
Invalid parameter supplied while setting '[somedir\jar1, somedir\jar2]'
Are we supposed to provide classpath/classpath in the first place? or
will it consider ${project.runtimeClasspathElements} as the default
classpath? (I guess not).
If i remove the classpath/classpath from the plugin definition (as it
is
optional), it fails to find some of the classes that it needs to compile
the
ejb.jar even though they are defined as dependencies in the project.
Let me know if i'm doing something wrong.
--
View this message in context:
http://www.nabble.com/-M2-weblogic%3Aappc-classpath-issue-tf2465090.html#a68
71847
Sent from the Maven - Users mailing list archive at Nabble.com.
-
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]
--
View this message in context:
http://www.nabble.com/-M2-weblogic%3Aappc-classpath-issue-tf2465090s177.html#a7088731
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: [M2]weblogic:appc classpath issue
still have issue in compiling the ejb jar file. It simply fails to find
all the dependencies in the classpath.
Here is the plugin definition again.
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdweblogic-maven-plugin/artifactId
version2.8.0-SNAPSHOT/version
configuration
objectPath${project.build.directory}/${project.artifactId}-${project.version}.jar/objectPath
verbosetrue/verbose
debuggingtrue/debugging
nowarningsfalse/nowarnings
lineNumberstrue/lineNumbers
keepGeneratedtrue/keepGenerated
/configuration
executions
execution
phasepackage/phase
goals
goalappc/goal
/goals
/execution
/executions
/plugin
All the required jars for appc are defined as 'compile' dependecies in the
pom. Still it gives me a NoClassDefFoundError for the required class
files.
Scott Ryan-2 wrote:
How did you make out with the appc mojo? I am updating the plugin to
simplify it this weekend and will update the code with some code that was
posted in JIRA. Let me know your status and I will send out a note on
the
weekend when the new code is available.
Scott Ryan
Chief Technology Officer
Soaring Eagle L.L.C.
[EMAIL PROTECTED]
www.soaringeagleco.com
(303) 263-3044
-Original Message-
From: Dmystery [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 18, 2006 2:39 AM
To: users@maven.apache.org
Subject: [M2]weblogic:appc classpath issue
I'm using weblogic-maven-plugin to compile my ejb.jar. Here is the plugin
definition.
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdweblogic-maven-plugin/artifactId
version2.8.0-SNAPSHOT/version
configuration
objectPath${project.build.directory}/${project.artifactId}-${project.versi
on}.jar/objectPath
verbosetrue/verbose
debuggingtrue/debugging
nowarningsfalse/nowarnings
lineNumberstrue/lineNumbers
keepGeneratedtrue/keepGenerated
classpath${project.runtimeClasspathElements}/classpath
/configuration
executions
execution
phasepackage/phase
goals
goalappc/goal
/goals
/execution
/executions
/plugin
The ${project.runtimeClasspathElements} is a string like [somedir\jar1,
somedir\jar2]. Because of this the plugin throws a
org.codehaus.plexus.component.configurator.ComponentConfigurationException
:
Invalid parameter supplied while setting '[somedir\jar1, somedir\jar2]'
Are we supposed to provide classpath/classpath in the first place? or
will it consider ${project.runtimeClasspathElements} as the default
classpath? (I guess not).
If i remove the classpath/classpath from the plugin definition (as it
is
optional), it fails to find some of the classes that it needs to compile
the
ejb.jar even though they are defined as dependencies in the project.
Let me know if i'm doing something wrong.
--
View this message in context:
http://www.nabble.com/-M2-weblogic%3Aappc-classpath-issue-tf2465090.html#a68
71847
Sent from the Maven - Users mailing list archive at Nabble.com.
-
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]
--
View this message in context:
http://www.nabble.com/-M2-weblogic%3Aappc-classpath-issue-tf2465090s177.html#a7089129
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: [M2]weblogic:appc classpath issue
That is what i thought. I should not a classpath. Most of my dependencies
are with compile scope and yes i have an ejb jar file that i'm trying to
compile. i cannot send u the exact snippet as i'm on a vacation :). Will get
in touch next week.
thanks.
Scott Ryan-2 wrote:
You should not need a classpath as that is included for the clientgen part
of the plugin. The mojo should recognize the proper classpath from the
plugin dependencies. Are all your dependencies set to the default scope
or
are some set to some other scope like provided etc? Let me try the latest
plugin against my test suite tonight and give you some more feedback.
Just
to clarify you have an ejb jar file you are trying to appc? I have had
success with that. if you could send me a snippet of the issues you see
when you try with out the classpath that would help a lot. i will try to
get you an answer back this evening unless someone else on the list has an
answer before that.
Scott Ryan
Chief Technology Officer
Soaring Eagle L.L.C.
[EMAIL PROTECTED]
www.soaringeagleco.com
(303) 263-3044
-Original Message-
From: Dmystery [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 18, 2006 2:39 AM
To: users@maven.apache.org
Subject: [M2]weblogic:appc classpath issue
I'm using weblogic-maven-plugin to compile my ejb.jar. Here is the plugin
definition.
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdweblogic-maven-plugin/artifactId
version2.8.0-SNAPSHOT/version
configuration
objectPath${project.build.directory}/${project.artifactId}-${project.versi
on}.jar/objectPath
verbosetrue/verbose
debuggingtrue/debugging
nowarningsfalse/nowarnings
lineNumberstrue/lineNumbers
keepGeneratedtrue/keepGenerated
classpath${project.runtimeClasspathElements}/classpath
/configuration
executions
execution
phasepackage/phase
goals
goalappc/goal
/goals
/execution
/executions
/plugin
The ${project.runtimeClasspathElements} is a string like [somedir\jar1,
somedir\jar2]. Because of this the plugin throws a
org.codehaus.plexus.component.configurator.ComponentConfigurationException
:
Invalid parameter supplied while setting '[somedir\jar1, somedir\jar2]'
Are we supposed to provide classpath/classpath in the first place? or
will it consider ${project.runtimeClasspathElements} as the default
classpath? (I guess not).
If i remove the classpath/classpath from the plugin definition (as it
is
optional), it fails to find some of the classes that it needs to compile
the
ejb.jar even though they are defined as dependencies in the project.
Let me know if i'm doing something wrong.
--
View this message in context:
http://www.nabble.com/-M2-weblogic%3Aappc-classpath-issue-tf2465090.html#a68
71847
Sent from the Maven - Users mailing list archive at Nabble.com.
-
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]
--
View this message in context:
http://www.nabble.com/-M2-weblogic%3Aappc-classpath-issue-tf2465090.html#a6929932
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: [M2]weblogic:appc classpath issue
How did you make out with the appc mojo? I am updating the plugin to
simplify it this weekend and will update the code with some code that was
posted in JIRA. Let me know your status and I will send out a note on the
weekend when the new code is available.
Scott Ryan
Chief Technology Officer
Soaring Eagle L.L.C.
[EMAIL PROTECTED]
www.soaringeagleco.com
(303) 263-3044
-Original Message-
From: Dmystery [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 18, 2006 2:39 AM
To: users@maven.apache.org
Subject: [M2]weblogic:appc classpath issue
I'm using weblogic-maven-plugin to compile my ejb.jar. Here is the plugin
definition.
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdweblogic-maven-plugin/artifactId
version2.8.0-SNAPSHOT/version
configuration
objectPath${project.build.directory}/${project.artifactId}-${project.versi
on}.jar/objectPath
verbosetrue/verbose
debuggingtrue/debugging
nowarningsfalse/nowarnings
lineNumberstrue/lineNumbers
keepGeneratedtrue/keepGenerated
classpath${project.runtimeClasspathElements}/classpath
/configuration
executions
execution
phasepackage/phase
goals
goalappc/goal
/goals
/execution
/executions
/plugin
The ${project.runtimeClasspathElements} is a string like [somedir\jar1,
somedir\jar2]. Because of this the plugin throws a
org.codehaus.plexus.component.configurator.ComponentConfigurationException :
Invalid parameter supplied while setting '[somedir\jar1, somedir\jar2]'
Are we supposed to provide classpath/classpath in the first place? or
will it consider ${project.runtimeClasspathElements} as the default
classpath? (I guess not).
If i remove the classpath/classpath from the plugin definition (as it is
optional), it fails to find some of the classes that it needs to compile the
ejb.jar even though they are defined as dependencies in the project.
Let me know if i'm doing something wrong.
--
View this message in context:
http://www.nabble.com/-M2-weblogic%3Aappc-classpath-issue-tf2465090.html#a68
71847
Sent from the Maven - Users mailing list archive at Nabble.com.
-
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]
[M2]weblogic:appc classpath issue
I'm using weblogic-maven-plugin to compile my ejb.jar. Here is the plugin
definition.
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdweblogic-maven-plugin/artifactId
version2.8.0-SNAPSHOT/version
configuration
objectPath${project.build.directory}/${project.artifactId}-${project.version}.jar/objectPath
verbosetrue/verbose
debuggingtrue/debugging
nowarningsfalse/nowarnings
lineNumberstrue/lineNumbers
keepGeneratedtrue/keepGenerated
classpath${project.runtimeClasspathElements}/classpath
/configuration
executions
execution
phasepackage/phase
goals
goalappc/goal
/goals
/execution
/executions
/plugin
The ${project.runtimeClasspathElements} is a string like [somedir\jar1,
somedir\jar2]. Because of this the plugin throws a
org.codehaus.plexus.component.configurator.ComponentConfigurationException :
Invalid parameter supplied while setting '[somedir\jar1, somedir\jar2]'
Are we supposed to provide classpath/classpath in the first place? or
will it consider ${project.runtimeClasspathElements} as the default
classpath? (I guess not).
If i remove the classpath/classpath from the plugin definition (as it is
optional), it fails to find some of the classes that it needs to compile the
ejb.jar even though they are defined as dependencies in the project.
Let me know if i'm doing something wrong.
--
View this message in context:
http://www.nabble.com/-M2-weblogic%3Aappc-classpath-issue-tf2465090.html#a6871847
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: [M2]weblogic:appc classpath issue
You should not need a classpath as that is included for the clientgen part
of the plugin. The mojo should recognize the proper classpath from the
plugin dependencies. Are all your dependencies set to the default scope or
are some set to some other scope like provided etc? Let me try the latest
plugin against my test suite tonight and give you some more feedback. Just
to clarify you have an ejb jar file you are trying to appc? I have had
success with that. if you could send me a snippet of the issues you see
when you try with out the classpath that would help a lot. i will try to
get you an answer back this evening unless someone else on the list has an
answer before that.
Scott Ryan
Chief Technology Officer
Soaring Eagle L.L.C.
[EMAIL PROTECTED]
www.soaringeagleco.com
(303) 263-3044
-Original Message-
From: Dmystery [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 18, 2006 2:39 AM
To: users@maven.apache.org
Subject: [M2]weblogic:appc classpath issue
I'm using weblogic-maven-plugin to compile my ejb.jar. Here is the plugin
definition.
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdweblogic-maven-plugin/artifactId
version2.8.0-SNAPSHOT/version
configuration
objectPath${project.build.directory}/${project.artifactId}-${project.versi
on}.jar/objectPath
verbosetrue/verbose
debuggingtrue/debugging
nowarningsfalse/nowarnings
lineNumberstrue/lineNumbers
keepGeneratedtrue/keepGenerated
classpath${project.runtimeClasspathElements}/classpath
/configuration
executions
execution
phasepackage/phase
goals
goalappc/goal
/goals
/execution
/executions
/plugin
The ${project.runtimeClasspathElements} is a string like [somedir\jar1,
somedir\jar2]. Because of this the plugin throws a
org.codehaus.plexus.component.configurator.ComponentConfigurationException :
Invalid parameter supplied while setting '[somedir\jar1, somedir\jar2]'
Are we supposed to provide classpath/classpath in the first place? or
will it consider ${project.runtimeClasspathElements} as the default
classpath? (I guess not).
If i remove the classpath/classpath from the plugin definition (as it is
optional), it fails to find some of the classes that it needs to compile the
ejb.jar even though they are defined as dependencies in the project.
Let me know if i'm doing something wrong.
--
View this message in context:
http://www.nabble.com/-M2-weblogic%3Aappc-classpath-issue-tf2465090.html#a68
71847
Sent from the Maven - Users mailing list archive at Nabble.com.
-
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]
Plugin classpath issue
Hi, I'm working on a plugin that I'd like to have invoked from the CLI, much like the jetty plugin. I'm having difficulty in getting the classpath to work out the way I'd like though. I have a dependency listed and can use classes from that dependency, but transitive dependencies don't seem to be working. So, while I can use classes in my own dependency list, they can't use anything from their subsequent dependencies. I've tried using @requiresDependencyResolution, but that didn't help. Any advice would be much appreciated. Thanks, Kevin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Plugin classpath issue
On 9/30/06, Kevin Menard [EMAIL PROTECTED] wrote:
Hi,
I'm working on a plugin that I'd like to have invoked from the CLI, much
like the jetty plugin. I'm having difficulty in getting the classpath
to work out the way I'd like though. I have a dependency listed and can
use classes from that dependency, but transitive dependencies don't seem
to be working. So, while I can use classes in my own dependency list,
they can't use anything from their subsequent dependencies. I've tried
using @requiresDependencyResolution, but that didn't help.
Try using @requiresDependencyResolution runtime. Then ${project.artifacts}
should give you all the dependencies I believe.
--
Cheers,
Kristian
[m2] Weblogic classpath issue with Maven-Antlib
I can run wlcompile just fine when I don't use the setWLSenv.cmd from
Weblogic. However, I can't deploy using WLDeploy unless I run setWLSenv.cmd.
The problem is that after I run setWLSenv.cmd and then try to complie I get
a NullPointerException. This error only occurs when I try to referenence
the POM file on the classpath as follows:
artifact:dependencies pathId=dependency.classpath verbose=false
pom refid=maven.project /
/artifact:dependencies
wlcompile srcdir=${src.dir} destdir=${dest.dir}
classpath
path refid=dependency.classpath/
/classpath
javac debug=true/
/wlcompile
If I remvove the refid to a Maven POM it will compile just fine, but without
the dependent files of course. I'm certain it's a classpath conflict of
some sort. Has anyone else had a similar issue?
--
View this message in context:
http://www.nabble.com/-m2--Weblogic-classpath-issue-with-Maven-Antlib-t1826705.html#a4982840
Sent from the Maven - Users forum at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Maven-Surfire classpath issue
When i run surfire 2.2 with TestNG 4.7, the classpath will be set to surefire-api-2.0.jar + plexus-utils-1.1.jar + surefire-booter-2.0.jar The problem is that it does not include relevant dependencies like target/classes. Currently i override the classpath with System#setProperty inside my unit-test as simple workaround. Whats the trick to get surefire to set up the correct classpath? In my mind the cp would consist of all dependency jars + target/classes + target/test-classes. thx Bernhard Neuhauser - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
unit test classpath issue / java.lang.LinkageError
Hello, I'm new to maven and Java 5 and I just started a project using Maven 2. So far everything has been great except for the following issue. I'm currently having a problem getting a particular unit test to run successfully. I'm using java 1.5.0_04 and was trying to validate some XML against a schema. I'm compiling the schema. My code looks like this: final SAXParserFactory spf = SAXParserFactory.newInstance(); System.out.println(spf.getClass().getName()); spf.setSchema(schema); final SAXParser saxParser = spf.newSAXParser(); saxParser.parse(new InputSource(new StringReader(xml)), new FailingHandler(xml)); I got this error: java.lang.UnsupportedOperationException: This parser does not support specification null version null at javax.xml.parsers.SAXParserFactory.setSchema(SAXParserFactory.java:361) on the spf.setSchema(schema); line It seems to be because when maven runs the unit test, it picks up the SAXParserFactory org.apache.xerces.jaxp.SAXParserFactoryImpl; when run from eclipse it picks up com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl which is coming from the Java5 libraries. Running maven with the -X option, I can see there are numerous Xerces libraries being put in the classpath, for example: [DEBUG] /home/tim/.m2/repository/xerces/xercesImpl/2.6.2/xercesImpl-2.6.2.jar [DEBUG] /home/tim/.m2/repository/xerces/xmlParserAPIs/2.6.2/xmlParserAPIs-2.6.2.jar [DEBUG] /home/tim/.m2/repository/xml-apis/xml-apis/1.0.b2/xml-apis-1.0.b2.jar [DEBUG] /home/tim/.m2/repository/xerces/xerces/2.0.2/xerces-2.0.2.jar So I added forkModeonce/forkMode to the surefire plugin. However, this caused my unit tests to fail earlier with the following exception: java.lang.LinkageError: Class javax/xml/transform/Source violates loader constraints at javax.xml.validation.SchemaFactory.newSchema(SchemaFactory.java:489) Does anyone have any suggestions on how to resolve this issue? Is forking the unit test the correct thing to do? Do I need to add the Java5 libraries to the classpath ahead of the others? Update: So I found a workaround when forkMode is not set - by manually telling jaxp which parser factory to use: System.setProperty(javax.xml.parsers.SAXParserFactory, com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl); This seems like a bit of a kludge though - I don't like specifying internal Java classes. However, things still fail when I use the Cobertura plugin to do code coverage, since that seems to force a fork. So I guess I still need to figure out how to get my unit tests to run with forkModeonce/forkMode. Info: echo $JAVA_HOME /opt/apps/jdk1.5.0_04 java -version java version 1.5.0_04 mvn -version Maven version: 2.0.1 Any help would be greatly appreciated, Thanks, Tim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 2 and Ant classpath issue
NB: Replaying message, as the mail client messed-up the xml extract of the
previous message
Hi Chris
Had my first go at the lists, but hasn't been very lucky there :(
I first tried this:
ant antfile=build/ant-build.xml dir=${basedir} inheritRefs=true
target name=generate-sources/
/ant
It didn't work, so now I'm directly embedding my ant script inside the
pom.xml. Which is:
tasks
scriptdef name=lc language=javascript
attribute name=property/
attribute name=value/
project.setNewProperty(attributes.get(property),
attributes.get(value).toLowerCase());
/scriptdef
basename property=gw.name file=${basedir}/
lc property=gw.name.lc value=${gw.name}/
echogw.name=${gw.name}/echo
echogw.name.lc=${gw.name.lc}/echo
echofiltering.../echo
fileset dir=${basedir}/
filterset
filter token=CLIENT_NAME value=${gw.name}/
filter token=client_name value=${gw.name.lc}/
filter token=basedir value=${basedir}/
filter token=env value=${env}/
/filterset
mapper type=regexp from=(.*)_GW(.*)\.(.*)
to=\1${gw.name}_GW\2.\3/
echofiletering complete./echo
/tasks
The ant script is tested and works well standalone.
Much appreciate your help.
Hassan
[EMAIL PROTECTED]
10/01/2006 16:34
Please respond to Maven Users List
To: Maven Users List users@maven.apache.org
cc:
Subject:Re: Maven 2 and Ant classpath issue
Hi Chris
Had my first go at the lists, but hasn't been very lucky there :(
I first tried this:
ant antfile=build/ant-build.xml dir=${basedir} inheritRefs=true
target name=generate-sources/
/ant
It didn't work, so now I'm directly embedding my ant script inside the
pom.xml. Which is:
tasks
scriptdef
name=lc language=javascript
attribute name=property/
attribute name=value/
.setNewProperty(attributes.get(property),
.get(value).toLowerCase());
/scriptdef
basename
property=gw.name file=${basedir}/
lc
property=gw.name.lc value=${gw.name}/
echogw.name=${gw.name}/echo
echogw.name.lc=${gw.name.lc}/echo
echofiltering.../echo
fileset
dir=${basedir}/
filterset
filter token=CLIENT_NAME value=${gw.name}/
filter token=client_name value=${gw.name.lc}/
filter token=basedir value=${basedir}/
filter token=env value=${env}/
/filterset
mapper
type=regexp from=(.*)_GW(.*)\.(.*) to=\1${gw.name}_GW\2.\3/
echofiletering complete./echo
/tasks
The ant script is tested and works well standalone.
Much appreciate your help.
Hassan
Chris Berry [EMAIL PROTECTED]
10/01/2006 15:37
Please respond to Maven Users List
To: Maven Users List users@maven.apache.org
cc:
Subject:Re: Maven 2 and Ant classpath issue
Hassan,
Please search the list archives -- this has been covered many times
recently.
If that doesn't answer your question, then please post the POM snippet
that
shows the ant call. (You may have forgotten inheritRefs=true)
Cheers,
-- Chris
On 1/10/06, [EMAIL PROTECTED] [EMAIL PROTECTED]
wrote:
Hi
I'm using Maven 2.0.1 and trying to use a non-standard Ant task
(scriptdef), in my pom.xml. It's giving me
this error:
Embedded error: Could not create task or type of type: scriptdef.
Looks like the Maven classpath is not being used by Ant...
Just to confirm, I have the required dependency jar in my pom.xml:
dependency
groupIdbsf/groupId
artifactIdbsf/artifactId
version2.3.0/version
/dependency
Your help is highly highly appreciated.
Thanks
Haz
Re: Maven 2 and Ant classpath issue
http://maven.apache.org/plugins/maven-antrun-plugin/classpaths.html
On 1/11/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
NB: Replaying message, as the mail client messed-up the xml extract of the
previous message
Hi Chris
Had my first go at the lists, but hasn't been very lucky there :(
I first tried this:
ant antfile=build/ant-build.xml dir=${basedir} inheritRefs=true
target name=generate-sources/
/ant
It didn't work, so now I'm directly embedding my ant script inside the
pom.xml. Which is:
tasks
scriptdef name=lc language=javascript
attribute name=property/
attribute name=value/
project.setNewProperty(attributes.get(property),
attributes.get(value).toLowerCase());
/scriptdef
basename property=gw.name file=${basedir}/
lc property=gw.name.lc value=${gw.name}/
echogw.name=${gw.name}/echo
echogw.name.lc=${gw.name.lc}/echo
echofiltering.../echo
fileset dir=${basedir}/
filterset
filter token=CLIENT_NAME value=${gw.name}/
filter token=client_name value=${gw.name.lc}/
filter token=basedir value=${basedir}/
filter token=env value=${env}/
/filterset
mapper type=regexp from=(.*)_GW(.*)\.(.*)
to=\1${gw.name}_GW\2.\3/
echofiletering complete./echo
/tasks
The ant script is tested and works well standalone.
Much appreciate your help.
Hassan
[EMAIL PROTECTED]
10/01/2006 16:34
Please respond to Maven Users List
To: Maven Users List users@maven.apache.org
cc:
Subject:Re: Maven 2 and Ant classpath issue
Hi Chris
Had my first go at the lists, but hasn't been very lucky there :(
I first tried this:
ant antfile=build/ant-build.xml dir=${basedir} inheritRefs=true
target name=generate-sources/
/ant
It didn't work, so now I'm directly embedding my ant script inside the
pom.xml. Which is:
tasks
scriptdef
name=lc language=javascript
attribute name=property/
attribute name=value/
.setNewProperty(attributes.get(property),
.get(value).toLowerCase());
/scriptdef
basename
property=gw.name file=${basedir}/
lc
property=gw.name.lc value=${gw.name}/
echogw.name=${gw.name}/echo
echogw.name.lc=${gw.name.lc}/echo
echofiltering.../echo
fileset
dir=${basedir}/
filterset
filter token=CLIENT_NAME value=${gw.name}/
filter token=client_name value=${gw.name.lc}/
filter token=basedir value=${basedir}/
filter token=env value=${env}/
/filterset
mapper
type=regexp from=(.*)_GW(.*)\.(.*) to=\1${gw.name}_GW\2.\3/
echofiletering complete./echo
/tasks
The ant script is tested and works well standalone.
Much appreciate your help.
Hassan
Chris Berry [EMAIL PROTECTED]
10/01/2006 15:37
Please respond to Maven Users List
To: Maven Users List users@maven.apache.org
cc:
Subject:Re: Maven 2 and Ant classpath issue
Hassan,
Please search the list archives -- this has been covered many times
recently.
If that doesn't answer your question, then please post the POM snippet
that
shows the ant call. (You may have forgotten inheritRefs=true)
Cheers,
-- Chris
On 1/10/06, [EMAIL PROTECTED] [EMAIL PROTECTED]
wrote:
Hi
I'm using Maven 2.0.1 and trying to use a non-standard Ant task
(scriptdef), in my pom.xml. It's giving me
this error:
Embedded error: Could not create task or type of type: scriptdef.
Looks like the Maven classpath is not being used by Ant...
Just to confirm, I have the required dependency jar in my pom.xml:
dependency
groupIdbsf/groupId
artifactIdbsf/artifactId
version2.3.0/version
/dependency
Your help is highly highly appreciated.
Thanks
Haz
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Maven 2 and Ant classpath issue
Hi I'm using Maven 2.0.1 and trying to use a non-standard Ant task (scriptdef), in my pom.xml. It's giving me this error: Embedded error: Could not create task or type of type: scriptdef. Looks like the Maven classpath is not being used by Ant... Just to confirm, I have the required dependency jar in my pom.xml: dependency groupIdbsf/groupId artifactIdbsf/artifactId version2.3.0/version /dependency Your help is highly highly appreciated. Thanks Haz
Re: Maven 2 and Ant classpath issue
Hassan, Please search the list archives -- this has been covered many times recently. If that doesn't answer your question, then please post the POM snippet that shows the ant call. (You may have forgotten inheritRefs=true) Cheers, -- Chris On 1/10/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi I'm using Maven 2.0.1 and trying to use a non-standard Ant task (scriptdef), in my pom.xml. It's giving me this error: Embedded error: Could not create task or type of type: scriptdef. Looks like the Maven classpath is not being used by Ant... Just to confirm, I have the required dependency jar in my pom.xml: dependency groupIdbsf/groupId artifactIdbsf/artifactId version2.3.0/version /dependency Your help is highly highly appreciated. Thanks Haz
Re: Maven 2 and Ant classpath issue
Hi Chris
Had my first go at the lists, but hasn't been very lucky there :(
I first tried this:
ant antfile=build/ant-build.xml dir=${basedir} inheritRefs=true
target name=generate-sources/
/ant
It didn't work, so now I'm directly embedding my ant script inside the
pom.xml. Which is:
tasks
scriptdef
name=lc language=javascript
attribute name=property/
attribute name=value/
.setNewProperty(attributes.get(property),
.get(value).toLowerCase());
/scriptdef
basename
property=gw.name file=${basedir}/
lc
property=gw.name.lc value=${gw.name}/
echogw.name=${gw.name}/echo
echogw.name.lc=${gw.name.lc}/echo
echofiltering.../echo
fileset
dir=${basedir}/
filterset
filter
token=CLIENT_NAME value=${gw.name}/
filter
token=client_name value=${gw.name.lc}/
filter
token=basedir value=${basedir}/
filter
token=env value=${env}/
/filterset
mapper
type=regexp from=(.*)_GW(.*)\.(.*) to=\1${gw.name}_GW\2.\3/
echofiletering complete./echo
/tasks
The ant script is tested and works well standalone.
Much appreciate your help.
Hassan
Chris Berry [EMAIL PROTECTED]
10/01/2006 15:37
Please respond to Maven Users List
To: Maven Users List users@maven.apache.org
cc:
Subject:Re: Maven 2 and Ant classpath issue
Hassan,
Please search the list archives -- this has been covered many times
recently.
If that doesn't answer your question, then please post the POM snippet
that
shows the ant call. (You may have forgotten inheritRefs=true)
Cheers,
-- Chris
On 1/10/06, [EMAIL PROTECTED] [EMAIL PROTECTED]
wrote:
Hi
I'm using Maven 2.0.1 and trying to use a non-standard Ant task
(scriptdef), in my pom.xml. It's giving me
this error:
Embedded error: Could not create task or type of type: scriptdef.
Looks like the Maven classpath is not being used by Ant...
Just to confirm, I have the required dependency jar in my pom.xml:
dependency
groupIdbsf/groupId
artifactIdbsf/artifactId
version2.3.0/version
/dependency
Your help is highly highly appreciated.
Thanks
Haz
test:test classpath issue
I have a JUnit test which works fine from an Ant task, but when I run
maven test:test it fails due to a ClassNotFoundException. Can someone
inform me of how to get Maven to add my classes to its classpath? My
project.xml contains the following:
unitTestSourceDirectorysrc/test/unitTestSourceDirectory
unitTest
resources
resource
directory${basedir}/src/test/directory
includes
include**/*Test.java/include
/includes
/resource
/resources
/unitTest
Derek Greer
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: test:test classpath issue
Why do you want your test code (ie .java files) copied to your classpath?
On Fri, 10 Sep 2004 18:46:57 -0600, Derek Greer [EMAIL PROTECTED] wrote:
I have a JUnit test which works fine from an Ant task, but when I run
maven test:test it fails due to a ClassNotFoundException. Can someone
inform me of how to get Maven to add my classes to its classpath? My
project.xml contains the following:
unitTestSourceDirectorysrc/test/unitTestSourceDirectory
unitTest
resources
resource
directory${basedir}/src/test/directory
includes
include**/*Test.java/include
/includes
/resource
/resources
/unitTest
Derek Greer
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
http://www.multitask.com.au/people/dion/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: test:test classpath issue
Never mind. I had my package prefixed with test. I'm guessing the norm
is to store unittest cases under src/test but not actually designate
test as part of the package name?
Derek
Derek Greer wrote:
I have a JUnit test which works fine from an Ant task, but when I run
maven test:test it fails due to a ClassNotFoundException. Can someone
inform me of how to get Maven to add my classes to its classpath? My
project.xml contains the following:
unitTestSourceDirectorysrc/test/unitTestSourceDirectory
unitTest
resources
resource
directory${basedir}/src/test/directory
includes
include**/*Test.java/include
/includes
/resource
/resources
/unitTest
Derek Greer
-
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]
SV: classpath issue with calling ant:java
Try this instead:
ant:echo${pom.dependencyClasspath}/ant:echo
Harald.
_
Harald Ommang, Delfi Data AS
-Opprinnelig melding-
Fra: Parsons, David [mailto:[EMAIL PROTECTED]
Sendt: 26. august 2004 01:48
Til: Maven Users List
Emne: RE: classpath issue with calling ant:java
Any other ideas?
I think I had the syntax wrong.
maven.dependency.classpath is not a variable, it's a path. So
printing it out won't show anything.
try this:
path refid=maven.dependency.classpath/
Tried both that and ant:path refid=maven.dependency.classpath/, to
no avail (NoClassDefFoundError).
Thanks for pointing out that maven.dependency.classpath is a path. Is
there any way to view its value at runtime?
David
-
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]
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
This email with attachments is solely for the use of the individual or
entity to whom it is addressed. Please also be aware that the DnB NOR Group
cannot accept any payment orders or other legally binding correspondence with
customers as a part of an email.
This email message has been virus checked by the virus programs used
in the DnB NOR Group.
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: classpath issue with calling ant:java
Parsons, David wrote:
I need to write a goal to invoke the main() method of a class in my
Maven project. Following suggestions in a recent thread on this
list,
I am attempting this with the ant:java/ tag. The problem I am
having is with the classpath, which needs to include the project's
dependencies. First I tried to use ${maven.dependency.classpath},
like
so:
goal name=perfmon:run
echomaven.dependency.classpath=${maven.dependency.classpath}/echo
ant:java jar=${basedir}/target/perfmon-0.1.jar
fork=true
ant:classpath
ant:path path=${maven.dependency.classpath}/
/ant:classpath
/ant:java
/goal
...which fails because apparently maven.dependency.classpath is not
set (according to the echo/ tag). My second attempt was to
hardcode
the necessary dependencies, but this fails for a different reason:
matthew.hawthorne wrote:
Try it like this:
ant:path path=maven.dependency.classpath/
Tried that, and it makes no difference. maven.dependency.classpath is
not defined, and the classpath that gets passed to the java command line
is empty according to maven -X:
[java] [DEBUG] Execute:Java13CommandLauncher: Executing 'java.exe'
with arguments:
'-jar'
'C:\p4\dev\ims\test\perfmon\target\perfmon-0.1.jar'
Any other ideas?
Thanks - David
-
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]
Re: classpath issue with calling ant:java
Thanks for pointing out that maven.dependency.classpath is a path. Is there any way to view its value at runtime? I also just had another flashback -- I think that maven.dependency.classpath is only available in certain contexts. Try making your custom goal depend on java:compile and see if that makes a difference. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: classpath issue with calling ant:java
Thanks, that really helped. That variable has the right value for the
classpath, and with
ant:classpath
ant:path path=${pom.dependencyClasspath}/
/ant:classpath
...java.exe appears to get the correct -classpath argument (according to
'maven -X').
However: I'm still seeing NoClassDefFoundError. Is it possible the
spaces in my classpath elements might cause this (i.e. the usual
Micro$oft C:\Documents and Settings\ thing)?
David
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 25, 2004 10:20 PM
To: [EMAIL PROTECTED]
Cc: Parsons, David
Subject: SV: classpath issue with calling ant:java
Try this instead:
ant:echo${pom.dependencyClasspath}/ant:echo
Harald.
_
Harald Ommang, Delfi Data AS
-Opprinnelig melding-
Fra: Parsons, David [mailto:[EMAIL PROTECTED]
Sendt: 26. august 2004 01:48
Til: Maven Users List
Emne: RE: classpath issue with calling ant:java
Any other ideas?
I think I had the syntax wrong.
maven.dependency.classpath is not a variable, it's a path. So
printing it out won't show anything.
try this:
path refid=maven.dependency.classpath/
Tried both that and ant:path refid=maven.dependency.classpath/, to
no avail (NoClassDefFoundError).
Thanks for pointing out that maven.dependency.classpath is a path. Is
there any way to view its value at runtime?
David
-
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]
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* *
This email with attachments is solely for the use of the individual or
entity to whom it is addressed. Please also be aware that the DnB NOR
Group cannot accept any payment orders or other legally binding
correspondence with customers as a part of an email.
This email message has been virus checked by the virus programs used in
the DnB NOR Group.
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* *
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Classpath issue - Want to use jars from my directory and not from maven repository
Tapan, We use a multiproject maven setup and extend the base project.xml file with a sub-project specific project.xml. The snippet below downloads everything from a repository local or remote, that can be setup by using a build.properties file. It builds a common-1.0.jar file that is put into a local personal repository.. project extend../../project.xml/extend idcommon/id currentVersion0.1/currentVersion shortDescriptionTicketing Common/shortDescription descriptionDescription/description dependencies dependency groupIdcommons-logging/groupId artifactIdcommons-logging/artifactId version1.0.3/version /dependency dependency groupIdcommons-lang/groupId artifactIdcommons-lang/artifactId version2.0/version /dependency /dependencies /project Why not put your library files into a local maven repositorie.. Works fine! Marco -Original Message- From: Tapan Nanawati [mailto:[EMAIL PROTECTED] Sent: vrijdag 9 januari 2004 13:02 To: Maven List (E-mail) Subject: Classpath issue - Want to use jars from my directory and not from maven repository Hi all We have a specified lib folder where we have our library files. We want to use that for compiling the source and not download from the repository. Please tell me how to do that. I struggled with setting up various parameters in dependencies but could not succeed. If some one can give a sample dependency element, it would be a great help. Thanks very much. Regards Tapan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Classpath issue - Want to use jars from my directory and not from maven repository
The best way: Maven works only with repositories (local and remote), but you can define a remote repository with the file protocol. maven.remote.repo = http://www.ibiblio.org/maven,file:///your_directory/ If you use the file protocol, you must respect the repository structure in your directory. The bad way: You can write a maven.xml, and add all you jars present in your lib directory to the maven classpath with addpath tag. Emmanuel - Original Message - From: Tapan Nanawati [EMAIL PROTECTED] To: Maven List (E-mail) [EMAIL PROTECTED] Sent: Friday, January 09, 2004 1:01 PM Subject: Classpath issue - Want to use jars from my directory and not from maven repository Hi all We have a specified lib folder where we have our library files. We want to use that for compiling the source and not download from the repository. Please tell me how to do that. I struggled with setting up various parameters in dependencies but could not succeed. If some one can give a sample dependency element, it would be a great help. Thanks very much. Regards Tapan - 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]
RE: Classpath issue - Want to use jars from my directory and not from maven repository
Hi Emmanuel, Please correct If I did not understood correctly :- 1) I will need to create directory structure like a repository for my library files something like this :- lib-| | xerces | | jars +xerces-1.0.2.jar Is my structure right? 2) Then I need to add this line to build.properties (Is this correct?) at the same path as project.xml maven.remote.repo = http://www.ibiblio.org/maven,file:///c:/project/libraries/lib (lib is the path to my lib folder) Then for the second (bad) option :- Could you please tell me the syntax for addpath tag. I guess we might have to use this option since our libraries are coming from CVS and it would be difficult porting them to differnt directory structure (that will need some discussion). Thanks for inputs. Regards Tapan -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Friday, January 09, 2004 5:38 PM To: Maven Users List Subject: Re: Classpath issue - Want to use jars from my directory and not from maven repository The best way: Maven works only with repositories (local and remote), but you can define a remote repository with the file protocol. maven.remote.repo = http://www.ibiblio.org/maven,file:///your_directory/ If you use the file protocol, you must respect the repository structure in your directory. The bad way: You can write a maven.xml, and add all you jars present in your lib directory to the maven classpath with addpath tag. Emmanuel - Original Message - From: Tapan Nanawati [EMAIL PROTECTED] To: Maven List (E-mail) [EMAIL PROTECTED] Sent: Friday, January 09, 2004 1:01 PM Subject: Classpath issue - Want to use jars from my directory and not from maven repository Hi all We have a specified lib folder where we have our library files. We want to use that for compiling the source and not download from the repository. Please tell me how to do that. I struggled with setting up various parameters in dependencies but could not succeed. If some one can give a sample dependency element, it would be a great help. Thanks very much. Regards Tapan - 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]
RE: Classpath issue - Want to use jars from my directory and not from maven repository
Before doing anything I would suggest you to read some documenation (at maven web site) how maven works and what are key concepts. What you are trying to do is rather off stream and maybe maven is just not for your team (specially if your ant based build system works fine). To use Maven you will have to a) adapt Maven to your project b) adapt your project to Maven. If you are not ready for b) Maven has probably nothing to offer to you, as only a + b gives you an access to all powerful features of maven. Michal -Original Message- From: Tapan Nanawati [mailto:[EMAIL PROTECTED] Sent: Friday, January 09, 2004 1:33 PM To: 'Maven Users List' Subject: RE: Classpath issue - Want to use jars from my directory and not from maven repository Hi Emmanuel, Please correct If I did not understood correctly :- 1) I will need to create directory structure like a repository for my library files something like this :- lib-| | xerces | | jars +xerces-1.0.2.jar Is my structure right? 2) Then I need to add this line to build.properties (Is this correct?) at the same path as project.xml maven.remote.repo = http://www.ibiblio.org/maven,file:///c:/project/libraries/lib (lib is the path to my lib folder) Then for the second (bad) option :- Could you please tell me the syntax for addpath tag. I guess we might have to use this option since our libraries are coming from CVS and it would be difficult porting them to differnt directory structure (that will need some discussion). Thanks for inputs. Regards Tapan -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Friday, January 09, 2004 5:38 PM To: Maven Users List Subject: Re: Classpath issue - Want to use jars from my directory and not from maven repository The best way: Maven works only with repositories (local and remote), but you can define a remote repository with the file protocol. maven.remote.repo = http://www.ibiblio.org/maven,file:///your_directory/ If you use the file protocol, you must respect the repository structure in your directory. The bad way: You can write a maven.xml, and add all you jars present in your lib directory to the maven classpath with addpath tag. Emmanuel - Original Message - From: Tapan Nanawati [EMAIL PROTECTED] To: Maven List (E-mail) [EMAIL PROTECTED] Sent: Friday, January 09, 2004 1:01 PM Subject: Classpath issue - Want to use jars from my directory and not from maven repository Hi all We have a specified lib folder where we have our library files. We want to use that for compiling the source and not download from the repository. Please tell me how to do that. I struggled with setting up various parameters in dependencies but could not succeed. If some one can give a sample dependency element, it would be a great help. Thanks very much. Regards Tapan - 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]
Re: Classpath issue - Want to use jars from my directory and not from maven repository
I'm totally agree with Michal. - Original Message - From: Maczka Michal [EMAIL PROTECTED] To: 'Maven Users List' [EMAIL PROTECTED] Sent: Friday, January 09, 2004 1:35 PM Subject: RE: Classpath issue - Want to use jars from my directory and not from maven repository Before doing anything I would suggest you to read some documenation (at maven web site) how maven works and what are key concepts. What you are trying to do is rather off stream and maybe maven is just not for your team (specially if your ant based build system works fine). To use Maven you will have to a) adapt Maven to your project b) adapt your project to Maven. If you are not ready for b) Maven has probably nothing to offer to you, as only a + b gives you an access to all powerful features of maven. Michal -Original Message- From: Tapan Nanawati [mailto:[EMAIL PROTECTED] Sent: Friday, January 09, 2004 1:33 PM To: 'Maven Users List' Subject: RE: Classpath issue - Want to use jars from my directory and not from maven repository Hi Emmanuel, Please correct If I did not understood correctly :- 1) I will need to create directory structure like a repository for my library files something like this :- lib-| | xerces | | jars +xerces-1.0.2.jar Is my structure right? 2) Then I need to add this line to build.properties (Is this correct?) at the same path as project.xml maven.remote.repo = http://www.ibiblio.org/maven,file:///c:/project/libraries/lib (lib is the path to my lib folder) Then for the second (bad) option :- Could you please tell me the syntax for addpath tag. I guess we might have to use this option since our libraries are coming from CVS and it would be difficult porting them to differnt directory structure (that will need some discussion). Thanks for inputs. Regards Tapan -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Friday, January 09, 2004 5:38 PM To: Maven Users List Subject: Re: Classpath issue - Want to use jars from my directory and not from maven repository The best way: Maven works only with repositories (local and remote), but you can define a remote repository with the file protocol. maven.remote.repo = http://www.ibiblio.org/maven,file:///your_directory/ If you use the file protocol, you must respect the repository structure in your directory. The bad way: You can write a maven.xml, and add all you jars present in your lib directory to the maven classpath with addpath tag. Emmanuel - Original Message - From: Tapan Nanawati [EMAIL PROTECTED] To: Maven List (E-mail) [EMAIL PROTECTED] Sent: Friday, January 09, 2004 1:01 PM Subject: Classpath issue - Want to use jars from my directory and not from maven repository Hi all We have a specified lib folder where we have our library files. We want to use that for compiling the source and not download from the repository. Please tell me how to do that. I struggled with setting up various parameters in dependencies but could not succeed. If some one can give a sample dependency element, it would be a great help. Thanks very much. Regards Tapan - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Classpath issue - Want to use jars from my directory and not from maven repository
The best way: Maven works only with repositories (local and remote), but you can define a remote repository with the file protocol. maven.remote.repo = http://www.ibiblio.org/maven,file:/// your_directory/ If you use the file protocol, you must respect the repository structure in your directory. The bad way: You can write a maven.xml, and add all you jars present in your lib directory to the maven classpath with addpath tag. You can also specify maven.jar.override = on in your project.properties file and then explicity declare the location of each dependency you want to override. http://maven.apache.org/reference/user-guide.html#Overriding%20Stated%20Depe ndencies Emmanuel - Original Message - From: Tapan Nanawati [EMAIL PROTECTED] To: Maven List (E-mail) [EMAIL PROTECTED] Sent: Friday, January 09, 2004 1:01 PM Subject: Classpath issue - Want to use jars from my directory and not from maven repository Hi all We have a specified lib folder where we have our library files. We want to use that for compiling the source and not download from the repository. Please tell me how to do that. I struggled with setting up various parameters in dependencies but could not succeed. If some one can give a sample dependency element, it would be a great help. Thanks very much. Regards Tapan - 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]
checkstyle classpath issue
Hi all,
I thought to share a solution to a minor problem I had with the
checkstyle
report: I'm using the checkstyle plugin 2.0 and the report being
generated
pointed to many Unable to get class information errors.
I figured out that the checkstyle task supports classpaths and added the
dependency classpath of the project and the maven.build.dest property to
it.
As a result, the class information can be resolved and the report is not
overloaded with these error messages.
ant:checkstyle
config=${checkstyleProperties}
failOnViolation=${maven.checkstyle.fail.on.violation}
classpath
pathelement location=${maven.build.dest} /
path refid=maven.dependency.classpath /
/classpath
...
/ant:checkstyle
Dominik
+-+
_/_/_/_/_/ _/_/_/ __/_/_/_/ Dominik Dahlem
_/ _/_/ _/ _/ M.Sc. student, Computer Science
_/ _/_/ _/ Trinity College Dublin
_/ _/_/ _/tel : +353 (0)1 608
_/ _/_/ _/ _/ email: [EMAIL PROTECTED]
_/ _/_/_/ __/_/_/_/ www : http://www.cs.tcd.ie/~dahlemd
+-+
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
