Re: site-deploy not copying Java Docs
site:stage gets processed first. I got the problem though. I now do a 'site-deploy' and all the links are working fine. There was a jira issue filed which said that the top most pom should have a url tag in it or else the modules links wont work good. franz see wrote: Good day to you, Dmystery, In the build output, what gets processed first, javadoc or site:stage? Thanks, Franz Dmystery wrote: I've a multi-module project for which i'm generating a site. I'm doing a mvn site:stage -DstagingDirectory=somedirectory. This works fine and the modules are linked properly too. However, the Java doc generated are not copied to the staging directory. Only the index.html is copied, the rest remains in the project build directory. My parent pom looks like, . . distributionManagement site idmy-site/id namemy-site/name urlfile:///url /site /distributionManagement reporting plugins plugin artifactIdmaven-javadoc-plugin/artifactId /plugin plugin groupIdorg.codehaus.mojo/groupId artifactIdjxr-maven-plugin/artifactId /plugin /plugins /reporting . . Interestingly, instead of the above command, if i use 'mvn site-deploy' with site idmy-site/id namemy-site/name urlfile://c:/somedirectory/url /site in my pom, the apidocs are copied but the module and apidocs links do not exists. Is there a clean way of deploying a site on to the local machine?? -- View this message in context: http://www.nabble.com/site-deploy-not-copying-Java-Docs-tf2628872s177.html#a7375485 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Execute phase in weblogic:appc
I've doubts in weblogic-maven-plugin's appc mojo. The executePhase in the plugin.xml is 'package' which means that it will bounded to the pom along with other goals with 'package' phase. According to the write up at http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html, when the appc mojo will execute the tasks already executed in the package phase and the preceding phases will rerun. I've appc in an pom with 'ear' packaging. The ear plugin has the following life-cycle, http://cvs.peopleware.be/training/maven/maven2/buildLifecyclePhases.html#ear So when appc is executed it will again generate the application.xml and the ear . Also i've a antrun plugin defined to in the 'package' phase that generates webservices using the generated ear. The whole life cycle executing twice is adding a considerable amount of time to the build process. Is there a way to avoid this? Moving the appc to install phase will install the ear to the repository first and run appc on the ear in the build directory. Which is not desirable. Any thoughts??? -- View this message in context: http://www.nabble.com/Execute-phase-in-weblogic%3Aappc-tf2642288s177.html#a7375755 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: Execute phase in weblogic:appc
That was my belief too that appc should add on the additional goals. But it is certainly the goals in packaging twice. As i said, i'm using appc in a pom with 'ear' packaging which runs ear:ear in the package phase. When the packaging is over appc prepares itself and run ear:ear again. See http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html 'Forking a parallel life cycle' May be if you can try using appc in a ear pom and do a 'mvn install' Scott Ryan-2 wrote: It certainly should not run twice. It should run all the goals in the packaging mojo and then add on the additional goals after packaging but not run them again. I am not seeing that behavour so i will have to investigate the scenario you are describing. I have a number of mojos that run during the packaging phase and i am not seeing it run multple times. I will try to look into it but if you have suggestions i am more than happy to make changes to the mojo. 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 16, 2006 4:13 AM To: users@maven.apache.org Subject: Execute phase in weblogic:appc I've doubts in weblogic-maven-plugin's appc mojo. The executePhase in the plugin.xml is 'package' which means that it will bounded to the pom along with other goals with 'package' phase. According to the write up at http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.ht ml, when the appc mojo will execute the tasks already executed in the package phase and the preceding phases will rerun. I've appc in an pom with 'ear' packaging. The ear plugin has the following life-cycle, http://cvs.peopleware.be/training/maven/maven2/buildLifecyclePhases.html#ear So when appc is executed it will again generate the application.xml and the ear . Also i've a antrun plugin defined to in the 'package' phase that generates webservices using the generated ear. The whole life cycle executing twice is adding a considerable amount of time to the build process. Is there a way to avoid this? Moving the appc to install phase will install the ear to the repository first and run appc on the ear in the build directory. Which is not desirable. Any thoughts??? -- View this message in context: http://www.nabble.com/Execute-phase-in-weblogic%3Aappc-tf2642288s177.html#a7 375755 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/Execute-phase-in-weblogic%3Aappc-tf2642288s177.html#a7394684 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: weblogic-maven-plugin:using properties file
Scott,
Can you let me know the correct way to do this? I'm not able to substitute
the plugin config values using the properties file. I think this is quite
trivial.
Dmystery wrote:
I did somthing like -
profile
iddeploy/id
activation
property
namedeploy/name
valuetrue/value
/property
/activation
build
plugins
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdweblogic-maven-plugin/artifactId
version2.8.0-SNAPSHOT/version
configuration
objectPath${project.build.directory}/${project.artifactId}-${project.version}.ear/objectPath
verbosetrue/verbose
debuggingtrue/debugging
nowarningsfalse/nowarnings
lineNumberstrue/lineNumbers
adminServerHostName${host}/adminServerHostName
adminServerPort${port}/adminServerPort
adminServerProtocolt3/adminServerProtocol
userId${user}/userId
password${password}/password
uploadfalse/upload
remotefalse/remote
verbosefalse/verbose
debugfalse/debug
targetNames${server.name}/targetNames
/configuration
executions
execution
phasepackage/phase
goals
goaldeploy/goal
/goals
/execution
/executions
/plugin
/plugins
filters
filter../../env/${env}.properties/filter //The configuration
values marked bold are in this file
/filters
/build
/profile
When i do 'mvn install -Ddeploy=true -Denv=dev', the above profile is
executed but it fails to pick up the porperties from the dev.properties
file. It tries to use the default porperties as of a localhost. Is it the
case that the filter will only work for resources? I'm using the same
filter for compiling the resources.
Scott Ryan-2 wrote:
You just need to configure the plugin in your different profiles. You
can
have a different set of configurations in each profile definition.
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 08, 2006 4:35 AM
To: users@maven.apache.org
Subject: weblogic-maven-plugin:using properties file
How can i use a properties file in weblogic-maven-plugin. I've to deploy
an
ear on different enviroments and the
adminServerHostName,adminServerPort
etc will hold values based on the environment. At the pom level i can
access
the appropriate properties file using profiles, but the same properties
are
not available in the plugin.
Any solution???
--
View this message in context:
http://www.nabble.com/weblogic-maven-plugin%3Ausing-properties-file-tf259470
5s177.html#a7236919
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/weblogic-maven-plugin%3Ausing-properties-file-tf2594705s177.html#a7334793
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: site-deploy not copying Java Docs
I dont think it adresses the issue here. I changed it to the lastest plugin though :) dennisl-2 wrote: Dmystery wrote: I've a multi-module project for which i'm generating a site. I'm doing a mvn site:stage -DstagingDirectory=somedirectory. This works fine and the modules are linked properly too. However, the Java doc generated are not copied to the staging directory. Only the index.html is copied, the rest remains in the project build directory. My parent pom looks like, . . distributionManagement site idmy-site/id namemy-site/name urlfile:///url /site /distributionManagement reporting plugins plugin artifactIdmaven-javadoc-plugin/artifactId /plugin plugin groupIdorg.codehaus.mojo/groupId artifactIdjxr-maven-plugin/artifactId /plugin /plugins /reporting . . Interestingly, instead of the above command, if i use 'mvn site-deploy' with site idmy-site/id namemy-site/name urlfile://c:/somedirectory/url /site in my pom, the apidocs are copied but the module and apidocs links do not exists. Is there a clean way of deploying a site on to the local machine?? You might want to replace the old org.codehaus.mojo:jxr-maven-plugin with the newer org.apache.maven.plugins:maven-jxr-plugin. -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/site-deploy-not-copying-Java-Docs-tf2628872s177.html#a7352031 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: Example POM for WebLogic servicegen needed
What i have right now is a ejb-project, war-project and an ear-project. In the ejb-project i use appc to compile the generated artifact so when i do an install the 'compiled artifact' gets installed in the repository. The war-project uses the compiled ejb artifact. Same for the ear-project, it generates the ear (with compiled ejb and the war), generates Webservices using servicegen, runs appc and then gets installed in the repository. So, i have a fully compiled and webservice ready ear in the repository. If one is to use seperate projects for servicegen and appc, then what should be the 'packaging' of that project? Also doing so will generate services using the ear in the local project build folders, so how to install the ear again in the repository? This is important for a multi-module project where an 'mvn install' will build all the modules populate the repositiry. I guess the appc should be in an ear or ejb project and the sericegen in the ear project. But my original question still remains - appc in package phase still executes the build twice :( Thanks. Jeff Bailey wrote: Thanks for the example. That saved me a lot of time! Re: phase for appc, I'm trying to take the approach having one project create the ejb-jar and a separate project create the web services using servicegen. Currently I run appc in the package phase. I thought it might be better to decompose things that way instead of trying to do to much in one project. In fact, I'm starting look into actually having a another project to create the ear. In a nutshell I'd have the following projects: EJB Project - contains my session beans. WebService Project - uses servicegen to create webservices for my sessions beans Web Project - contains my web app EAR Project - Packages the artifacts of the other three packages into the ear for my application. My goal is to separate out the assembly of the EAR and to keep each project relatively simple. I have a few challenges that I need to overcome: 1) servicegen needs to reference the ejb jar as a parameter. I currently have a relative path hardcoded to my ejb project, but what I'd really like to do is reference the ejb artifact. I'm sure this can be done but I need to dig into how to refernce it. Maybe declare the ejb jar as a dependency and somehow reference that in the servicegen call? 2) The WebService project uses servicegen to generate an EAR. I'm really only interested in the war file that's generated by servicegen so it can be packaged into the EAR by my EAR project. I have servicegen configured to generate an exploded ear, but I need to figure out how to make the war that servicegen generates the artifact of my WebService project so that it will be installed in the repository and can be picked up by my EAR project. Hopefully this makes sense. I'd be curious to know if others think by breakdown of maven projects is good pattern or an anti-pattern and if you have any suggestions on how to solve the remaining issues. Thanks, Jeff Dmystery wrote: On a different note, what execution phase are you executing the weblogic:appc? I'm doing it in a pom which first generate sources using XMLbeans, compiles some aspects, create ejb-jar, ejb-client-jar and then run weblogic:appc which is in the package phase. The problem is, when appc is started, it does the whole thing again, XMLBeans to ejb-client-jar. Just wanna know what phase you have weblogic:appc? Thanks. -- View this message in context: http://www.nabble.com/Example-POM-for-WebLogic-servicegen-needed-tf2604105s177.html#a7312860 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: Not set groupId and version?
The parent of this pom might be using pluginManagement. To know more http://maven.apache.org/pom.html#Plugin%20Management jiangshachina wrote: Hi guys, I have saw some guides like the following, http://maven.apache.org/guides/mini/guide-assemblies.html plugin artifactIdmaven-assembly-plugin/artifactId configuration descriptorsrc/main/assembly/dep.xml/descriptor /configuration /plugin Why can not set groupId and artifactId? Then how do Maven to deal with the plugin? Mave would search the whole local repository, then find it(the artifactId is unique), and use the last version? If the artifactId is duplicted, what would happen? a cup of Java, cheers! Sha Jiang -- View this message in context: http://www.nabble.com/Not-set-groupId-and-version--tf2620955s177.html#a7313626 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: Example POM for Weblogic servicegen needed
Thanks for the replies guys. Even i first thought of having a seperate project for servicegen and appc, but didn't build on the thought. Looks like i should try it out. As of now i've appc defined in an execution and in the package phase. I hope the servicegen mojo in the plugin will solve a lot of problems :) Scott Ryan-2 wrote: Thanks for pointing out the issue with the basicClientJar. I fixed the code this morning along with the forceGeneration and lineNumbers flags. I pushed a new snapshot up to the codehaus repository as well. Let me know if you have any other issues. Scott Ryan Chief Technology Officer Soaring Eagle L.L.C. [EMAIL PROTECTED] www.soaringeagleco.com (303) 263-3044 -Original Message- From: Jeff Bailey [mailto:[EMAIL PROTECTED] Sent: Saturday, November 11, 2006 5:08 PM To: users@maven.apache.org Subject: RE: Example POM for WebLogic servicegen needed That would be great to have servicegen available in the plugin! BTW, I'm using the 2.8 version since I'm stuck on WebLogic 8.1.4. I noticed that version currently accepts the -basicClientJar flag to appc but doesn't actually pass it into the appc command. Thanks! Jeff Scott Ryan-2 wrote: That is actually the way we build all of our projects and it makes it easier for development, unit testing and our SCM processes. We really don't need the ear for dev and unit testing but it is our required packaging to get through audit and SCM process. WE actually check them into our source code control in a consolidated project and use the master pom of the project to control the versions so that all the artifacts within that group use the same versions of related artifacts and the resolution within the project is consistent. I hope to have the servicegen mojo done this weekend and will push up the snapshot of both plugins once it is ready providing the snow does not call me out skiing. The servicegen mojo will construct the classpath from the depenency path of the pom.xml so you will only have to include the ejb artifact in order for servicegen to find it. Scott Ryan Chief Technology Officer Soaring Eagle L.L.C. [EMAIL PROTECTED] www.soaringeagleco.com (303) 263-3044 -Original Message- From: Jeff Bailey [mailto:[EMAIL PROTECTED] Sent: Friday, November 10, 2006 6:43 PM To: users@maven.apache.org Subject: Re: Example POM for WebLogic servicegen needed Thanks for the example. That saved me a lot of time! Re: phase for appc, I'm trying to take the approach having one project create the ejb-jar and a separate project create the web services using servicegen. Currently I run appc in the package phase. I thought it might be better to decompose things that way instead of trying to do to much in one project. In fact, I'm starting look into actually having a another project to create the ear. In a nutshell I'd have the following projects: EJB Project - contains my session beans. WebService Project - uses servicegen to create webservices for my sessions beans Web Project - contains my web app EAR Project - Packages the artifacts of the other three packages into the ear for my application. My goal is to separate out the assembly of the EAR and to keep each project relatively simple. I have a few challenges that I need to overcome: 1) servicegen needs to reference the ejb jar as a parameter. I currently have a relative path hardcoded to my ejb project, but what I'd really like to do is reference the ejb artifact. I'm sure this can be done but I need to dig into how to refernce it. Maybe declare the ejb jar as a dependency and somehow reference that in the servicegen call? 2) The WebService project uses servicegen to generate an EAR. I'm really only interested in the war file that's generated by servicegen so it can be packaged into the EAR by my EAR project. I have servicegen configured to generate an exploded ear, but I need to figure out how to make the war that servicegen generates the artifact of my WebService project so that it will be installed in the repository and can be picked up by my EAR project. Hopefully this makes sense. I'd be curious to know if others think by breakdown of maven projects is good pattern or an anti-pattern and if you have any suggestions on how to solve the remaining issues. Thanks, Jeff Dmystery wrote: On a different note, what execution phase are you executing the weblogic:appc? I'm doing it in a pom which first generate sources using XMLbeans, compiles some aspects, create ejb-jar, ejb-client-jar and then run weblogic:appc which is in the package phase. The problem is, when appc is started, it does the whole thing again, XMLBeans to ejb-client-jar. Just wanna know what phase you have weblogic:appc? Thanks. -- View this message in context: http://www.nabble.com/Example-POM-for-WebLogic-servicegen-needed-tf2604105s1 77.html#a7288485 Sent from
RE: EJB JAR Manifest
There is nothing new on mvn -X console when the big pause happens. Its just the normal debug statements like [DEBUG] adding some-file ... Big Pause here -- The last file to be added is are the pom.xml file [DEBUG] preparing weblogic:appc Sebastien Brunot wrote: On my side, I did not observe substantial timing differences adding classpath entries (automatically regarding the dependencies or manualy providing my own manifest.mf file) to the EJB jar. Perhaps you could send the output of mvn -X package to the list as an attached file ? Sebastien -Original Message- From: Dmystery [mailto:[EMAIL PROTECTED] Sent: Friday, November 10, 2006 6:13 AM To: users@maven.apache.org Subject: RE: EJB JAR Manifest Sebastein, Is it taking too long to add the classpath entry in the manifest? Since i made the ejb plugin to add the classpath entry, it is taking almost 1 min more to complete the ejb goal. Is it working normally for you? Thanks Sebastien Brunot wrote: Thanks for your help Jörg. Sebastien -Original Message- From: Jörg Schaible [mailto:[EMAIL PROTECTED] Sent: Thursday, November 09, 2006 2:20 PM To: Maven Users List Subject: RE: EJB JAR Manifest Sebastien Brunot wrote on Thursday, November 09, 2006 1:59 PM: Hi all, how can one specify a Class-Path: entry in the manifest of an EJB jar ? You have to configure it: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-ejb-plugin/artifactId configuration generateClienttrue/generateClient archive manifest addClasspathtrue/addClasspath /manifest /archive /configuration /plugin - Jörg - 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/EJB-JAR-Manifest-tf2601563s177.html#a7271531 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/EJB-JAR-Manifest-tf2601563s177.html#a7274113 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: Example POM for WebLogic servicegen needed
plugin
artifactIdmaven-antrun-plugin/artifactId
version1.0/version
executions
execution
phasepackage/phase
configuration
tasks
taskdef name=servicegen
classname=weblogic.ant.taskdefs.webservices.servicegen.ServiceGenTask
classpath refid=maven.dependency.classpath /
/taskdef
servicegen
destEar=${project.build.directory}/${project.artifactId}-${project.version}.ear
warName=castle-server-web-${project.parent.version}.war
contextURI=castle
mergeWithExistingWS=True
classpath refid=maven.dependency.classpath /
service targetNamespace=http://my.company.com;
ejbJar=${basedir}/path-to-ejb-jar/your-ejb.jar
includeEJBs=service name serviceName=service name
serviceURI=/jndi/name generateTypes=True
style=documentwrapped expandMethods=True
typeMappingFile=auto-types mapping file
/service
/servicegen
/tasks
/configuration
goals
goalrun/goal
/goals
/execution
/executions
dependencies
dependency
groupIdsun.jdk/groupId
artifactIdtools/artifactId
version1.5.1/version
scopesystem/scope
systemPath${java.home}/../lib/tools.jar/systemPath
/dependency
/dependencies
/plugin
Jeff Bailey wrote:
I need to create a WebService from a session bean using the WebLogic 8.1.4
servicegen ant task. Can anyone provide me a good example of a clean way
to accomplish this in the POM?
I'm successfully using the weblogic-maven-plugin to run appc, but the
plugin does not yet support servicegen.
Thanks,
Jeff
--
View this message in context:
http://www.nabble.com/Example-POM-for-WebLogic-servicegen-needed-tf2604105s177.html#a7274315
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: Example POM for WebLogic servicegen needed
On a different note, what execution phase are you executing the
weblogic:appc? I'm doing it in a pom which first generate sources using
XMLbeans, compiles some aspects, create ejb-jar, ejb-client-jar and then run
weblogic:appc which is in the package phase. The problem is, when appc is
started, it does the whole thing again, XMLBeans to ejb-client-jar. Just
wanna know what phase you have weblogic:appc?
Thanks.
Dmystery wrote:
Hope this helps,
plugin
artifactIdmaven-antrun-plugin/artifactId
version1.0/version
executions
execution
phasepackage/phase
configuration
tasks
taskdef name=servicegen
classname=weblogic.ant.taskdefs.webservices.servicegen.ServiceGenTask
classpath refid=maven.dependency.classpath /
/taskdef
servicegen
destEar=${project.build.directory}/${project.artifactId}-${project.version}.ear
warName=castle-server-web-${project.parent.version}.war
contextURI=castle
mergeWithExistingWS=True
classpath refid=maven.dependency.classpath /
service targetNamespace=http://my.company.com;
ejbJar=${basedir}/path-to-ejb-jar/your-ejb.jar
includeEJBs=service name serviceName=service name
serviceURI=/jndi/name generateTypes=True
style=documentwrapped expandMethods=True
typeMappingFile=auto-types mapping file
/service
/servicegen
/tasks
/configuration
goals
goalrun/goal
/goals
/execution
/executions
dependencies
dependency
groupIdsun.jdk/groupId
artifactIdtools/artifactId
version1.5.1/version
scopesystem/scope
systemPath${java.home}/../lib/tools.jar/systemPath
/dependency
/dependencies
/plugin
Jeff Bailey wrote:
I need to create a WebService from a session bean using the WebLogic
8.1.4 servicegen ant task. Can anyone provide me a good example of a
clean way to accomplish this in the POM?
I'm successfully using the weblogic-maven-plugin to run appc, but the
plugin does not yet support servicegen.
Thanks,
Jeff
--
View this message in context:
http://www.nabble.com/Example-POM-for-WebLogic-servicegen-needed-tf2604105s177.html#a7274411
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
maven-ejb-plugin : take too long
The maven-ejb-plugin when asked to addclasspath takes abnormal long time to complete. plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-ejb-plugin/artifactId version2.1-SNAPSHOT/version configuration !-- This takes a lot of time -- archive indextrue/index manifest addClasspathtrue/addClasspath /manifest /archive generateClienttrue/generateClient clientExcludes clientExclude**/*.xml/clientExclude clientExclude**/*.properties/clientExclude /clientExcludes /configuration /plugin Has anyone faced the same problem? It seems it takes around 1 min more for the goal to complete. -- View this message in context: http://www.nabble.com/maven-ejb-plugin-%3A-take-too-long-tf2600393s177.html#a7254356 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: maven-ejb-plugin : take too long
Nothing that i see in particular. [DEBUG] adding entry META-INF/maven/proj/proj-server-ejb/pom.xml [DEBUG] adding entry META-INF/maven/proj/proj-server-ejb/pom.properties Big pause ( 1) [DEBUG] adding entry META-INF/INDEX.LIST [INFO] Preparing weblogic:appc [DEBUG] maven-ejb-plugin: using locally installed snapshot [DEBUG] maven-ejb-plugin: using locally installed snapshot [DEBUG] weblogic-maven-plugin: using locally installed snapshot [WARNING] Removing: appc from forked lifecycle, to prevent recursive invocation. Wayne Fay wrote: Run mvn -X -e ... and perhaps you'll see what's going on differently in the console when you add the addClasspath setting. Wayne On 11/9/06, Dmystery [EMAIL PROTECTED] wrote: The maven-ejb-plugin when asked to addclasspath takes abnormal long time to complete. plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-ejb-plugin/artifactId version2.1-SNAPSHOT/version configuration !-- This takes a lot of time -- archive indextrue/index manifest addClasspathtrue/addClasspath /manifest /archive generateClienttrue/generateClient clientExcludes clientExclude**/*.xml/clientExclude clientExclude**/*.properties/clientExclude /clientExcludes /configuration /plugin Has anyone faced the same problem? It seems it takes around 1 min more for the goal to complete. -- View this message in context: http://www.nabble.com/maven-ejb-plugin-%3A-take-too-long-tf2600393s177.html#a7254356 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/maven-ejb-plugin-%3A-take-too-long-tf2600393s177.html#a7254646 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: Aspectj compilation?
Not sure about that, but i'm using the 'aspectj-maven-plugin'. plugin groupIdorg.codehaus.mojo/groupId artifactIdaspectj-maven-plugin/artifactId configuration ajdtBuildDefFileajbuild.properties/ajdtBuildDefFile aspectLibraries aspectLibrary groupId/groupId artifactId/artifactId//aspects to use. /aspectLibrary /aspectLibraries weaveDependencies weaveDependency groupId/groupId artifactId/artifactId //jar for aspects to weave into. /weaveDependency /weaveDependencies /configuration executions execution goals goalcompile/goal /goals /execution /executions /plugin Wim Deblauwe wrote: Hi, Looking at http://maven.apache.org/plugins/maven-compiler-plugin/non-javac-compilers.html, it mentions an plexus-compiler-aspectj. Is this a replacement for the aspectj plugin? regards, Wim -- View this message in context: http://www.nabble.com/Aspectj-compilation--tf2600117s177.html#a7255429 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: EJB JAR Manifest
Sebastein, Is it taking too long to add the classpath entry in the manifest? Since i made the ejb plugin to add the classpath entry, it is taking almost 1 min more to complete the ejb goal. Is it working normally for you? Thanks Sebastien Brunot wrote: Thanks for your help Jörg. Sebastien -Original Message- From: Jörg Schaible [mailto:[EMAIL PROTECTED] Sent: Thursday, November 09, 2006 2:20 PM To: Maven Users List Subject: RE: EJB JAR Manifest Sebastien Brunot wrote on Thursday, November 09, 2006 1:59 PM: Hi all, how can one specify a Class-Path: entry in the manifest of an EJB jar ? You have to configure it: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-ejb-plugin/artifactId configuration generateClienttrue/generateClient archive manifest addClasspathtrue/addClasspath /manifest /archive /configuration /plugin - Jörg - 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/EJB-JAR-Manifest-tf2601563s177.html#a7271531 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: weblogic-maven-plugin:using properties file
Any solutions to this one??
Dmystery wrote:
I did somthing like -
profile
iddeploy/id
activation
property
namedeploy/name
valuetrue/value
/property
/activation
build
plugins
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdweblogic-maven-plugin/artifactId
version2.8.0-SNAPSHOT/version
configuration
objectPath${project.build.directory}/${project.artifactId}-${project.version}.ear/objectPath
verbosetrue/verbose
debuggingtrue/debugging
nowarningsfalse/nowarnings
lineNumberstrue/lineNumbers
adminServerHostName${host}/adminServerHostName
adminServerPort${port}/adminServerPort
adminServerProtocolt3/adminServerProtocol
userId${user}/userId
password${password}/password
uploadfalse/upload
remotefalse/remote
verbosefalse/verbose
debugfalse/debug
targetNames${server.name}/targetNames
/configuration
executions
execution
phasepackage/phase
goals
goaldeploy/goal
/goals
/execution
/executions
/plugin
/plugins
filters
filter../../env/${env}.properties/filter //The configuration
values marked bold are in this file
/filters
/build
/profile
When i do 'mvn install -Ddeploy=true -Denv=dev', the above profile is
executed but it fails to pick up the porperties from the dev.properties
file. It tries to use the default porperties as of a localhost. Is it the
case that the filter will only work for resources? I'm using the same
filter for compiling the resources.
Scott Ryan-2 wrote:
You just need to configure the plugin in your different profiles. You
can
have a different set of configurations in each profile definition.
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 08, 2006 4:35 AM
To: users@maven.apache.org
Subject: weblogic-maven-plugin:using properties file
How can i use a properties file in weblogic-maven-plugin. I've to deploy
an
ear on different enviroments and the
adminServerHostName,adminServerPort
etc will hold values based on the environment. At the pom level i can
access
the appropriate properties file using profiles, but the same properties
are
not available in the plugin.
Any solution???
--
View this message in context:
http://www.nabble.com/weblogic-maven-plugin%3Ausing-properties-file-tf259470
5s177.html#a7236919
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/weblogic-maven-plugin%3Ausing-properties-file-tf2594705s177.html#a7271741
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
weblogic-maven-plugin:using properties file
How can i use a properties file in weblogic-maven-plugin. I've to deploy an ear on different enviroments and the adminServerHostName,adminServerPort etc will hold values based on the environment. At the pom level i can access the appropriate properties file using profiles, but the same properties are not available in the plugin. Any solution??? -- View this message in context: http://www.nabble.com/weblogic-maven-plugin%3Ausing-properties-file-tf2594705s177.html#a7236919 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
EAR: goal executed twice
My pom.xml has a packaging of ear and i'm using it to generate an ear, create
webservices using antrun plugin, and compile the ear using weblogic:appc.
project
parent
parent pom info---
/parent
modelVersion4.0.0/modelVersion
artifactIdapp-web/artifactId
packagingear/packaging
nameApp Ear/name
dependencies
..dependencies.
/dependencies
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-ear-plugin/artifactId
configuration
--ear
/configuration
/plugin
plugin
artifactIdmaven-antrun-plugin/artifactId
version1.0/version
executions
execution
phasepackage/phase
configuration
tasks
Tasks to generate webservice using servicegen-
/tasks
/configuration
goals
goalrun/goal
/goals
/execution
/executions
dependencies
plugin dependency-
/dependencies
/plugin
!-- Plugin to compile ear.--
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdweblogic-maven-plugin/artifactId
version2.8.0-SNAPSHOT/version
configuration
objectPath${project.build.directory}/${project.artifactId}-${project.version}.ear/objectPath
verbosetrue/verbose
debuggingtrue/debugging
nowarningsfalse/nowarnings
lineNumberstrue/lineNumbers
/configuration
executions
execution
phasepackage/phase
goals
goalappc/goal
/goals
/execution
/executions
dependencies
dependency
groupIdsun.jdk/groupId
artifactIdtools/artifactId
version1.5.1/version
scopesystem/scope
systemPath${java.home}/../lib/tools.jar/systemPath
/dependency
/dependencies
/plugin
/plugins
/build
/project
When i do 'mvn install', first the ear is generated, the task in antrun
plugin are executed, and then instead of weblogic:appc goal, the ear is
again generated followed by the antrun plugin tasks and then finally the
weblogic:appc is executed.
Both the antrun plugin and weblogic-maven-plugin have 'package' as the
execution phase. Even if i put antrun to 'compile' phase the build is
executed twice.
Is there some problem with the weblogic-maven-plugin?? (Scott ?? same thing
happens when i do a weblogic:deploy) or am i putting the plugins in wrong
phases??
--
View this message in context:
http://www.nabble.com/EAR%3A-goal-executed-twice-tf2599687s177.html#a7252399
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: weblogic-maven-plugin:using properties file
I did somthing like -
profile
iddeploy/id
activation
property
namedeploy/name
valuetrue/value
/property
/activation
build
plugins
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdweblogic-maven-plugin/artifactId
version2.8.0-SNAPSHOT/version
configuration
objectPath${project.build.directory}/${project.artifactId}-${project.version}.ear/objectPath
verbosetrue/verbose
debuggingtrue/debugging
nowarningsfalse/nowarnings
lineNumberstrue/lineNumbers
adminServerHostName${host}/adminServerHostName
adminServerPort${port}/adminServerPort
adminServerProtocolt3/adminServerProtocol
userId${user}/userId
password${password}/password
uploadfalse/upload
remotefalse/remote
verbosefalse/verbose
debugfalse/debug
targetNames${server.name}/targetNames
/configuration
executions
execution
phasepackage/phase
goals
goaldeploy/goal
/goals
/execution
/executions
/plugin
/plugins
filters
filter../../env/${env}.properties/filter
/filters
/build
/profile
When i do 'mvn install -Ddeploy=true -Denv=dev', the above profile is
executed but it fails to pick up the porperties from the dev.properties
file. It tries to use the default porperties as of a localhost. Is it the
case that the filter will only work for resources? I'm using the same filter
for compiling the resources.
Scott Ryan-2 wrote:
You just need to configure the plugin in your different profiles. You can
have a different set of configurations in each profile definition.
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 08, 2006 4:35 AM
To: users@maven.apache.org
Subject: weblogic-maven-plugin:using properties file
How can i use a properties file in weblogic-maven-plugin. I've to deploy
an
ear on different enviroments and the
adminServerHostName,adminServerPort
etc will hold values based on the environment. At the pom level i can
access
the appropriate properties file using profiles, but the same properties
are
not available in the plugin.
Any solution???
--
View this message in context:
http://www.nabble.com/weblogic-maven-plugin%3Ausing-properties-file-tf259470
5s177.html#a7236919
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/weblogic-maven-plugin%3Ausing-properties-file-tf2594705s177.html#a7252764
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
EAR: build executed twice.
My pom.xml has a packaging of ear and i'm using it to generate an ear, create
webservices using antrun plugin, and compile the ear using weblogic:appc.
project
parent
parent pom info---
/parent
modelVersion4.0.0/modelVersion
artifactIdapp-web/artifactId
packagingear/packaging
nameApp Ear/name
dependencies
..dependencies.
/dependencies
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-ear-plugin/artifactId
configuration
--ear
/configuration
/plugin
plugin
artifactIdmaven-antrun-plugin/artifactId
version1.0/version
executions
execution
phasepackage/phase
configuration
tasks
Tasks to generate webservice using servicegen-
/tasks
/configuration
goals
goalrun/goal
/goals
/execution
/executions
dependencies
plugin dependency-
/dependencies
/plugin
!-- Plugin to compile ear.--
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdweblogic-maven-plugin/artifactId
version2.8.0-SNAPSHOT/version
configuration
objectPath${project.build.directory}/${project.artifactId}-${project.version}.ear/objectPath
verbosetrue/verbose
debuggingtrue/debugging
nowarningsfalse/nowarnings
lineNumberstrue/lineNumbers
/configuration
executions
execution
phasepackage/phase
goals
goalappc/goal
/goals
/execution
/executions
dependencies
dependency
groupIdsun.jdk/groupId
artifactIdtools/artifactId
version1.5.1/version
scopesystem/scope
systemPath${java.home}/../lib/tools.jar/systemPath
/dependency
/dependencies
/plugin
/plugins
/build
/project
When i do 'mvn install', first the ear is generated, the task in antrun
plugin are executed, and then instead of weblogic:appc goal, the ear is
again generated followed by the antrun plugin tasks and then finally the
weblogic:appc is executed.
Both the antrun plugin and weblogic-maven-plugin have 'package' as the
execution phase. Even if i put antrun to 'compile' phase the build is
executed twice.
Is there some problem with the weblogic-maven-plugin?? (Scott ?? same thing
happens when i do a weblogic:deploy) or am i putting the plugins in wrong
phases??
--
View this message in context:
http://www.nabble.com/EAR%3A-build-executed-twice.-tf2593630s177.html#a7233745
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Profile problem
I've a parent pom say pom.xml and two child poms say pomA.xml and pomB.xml. I'm declaring a profile in both the child pom like, profile iddev/id activation property nameenv/name valuedev/value /property /activation build filters filtersrc/main/env/dev.properties/filter /filters /build /profile This is used to create artifacts for different environment. So there is a profile for each environment. Now the problem is, i have to put the same set of environment files in src/main/env/ of each childs and also have to write the profile declarations in both the child poms. Is there a way that profiles can be declared in the top most parent pom and there is a single 'environment' directory at the parent pom level that holds all the environment files? the childs can then just filter a particular file from that directory instead of having them in their resources directory. I've a lot of child projects and each needs to build based on a particular environment file. Can this be done? Does profile inheritance work? I've not found better answers yet on the forum. -- View this message in context: http://www.nabble.com/Profile-problem-tf2580392s177.html#a7193233 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
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: Too many jars added to lib?
Use maven-war-plugin. Due to transitive dependencies in M2, you need to remove them using the warSourceExcludes tag in the plugin as below. build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-war-plugin/artifactId version2.0.1/version configuration warSourceExcludes WEB-INF/lib/jar1,WEB-INF/lib/jar2, /warSourceExcludes /configuration /plugin /plugins /build Checkout : http://maven.apache.org/plugins/maven-war-plugin/index.html jiangshachina wrote: I have another question. In Web application project, generally, class files would be located at WEB-INF/classes. But now, I want they to be archived, and locate at WEB-INF/lib. And I want the jars could be put into different sub-directory under WEB-INF/lib? maven-jar-plugin or maven-war-plugin can help me? How can I do? jiangshachina wrote: Hello, My web projects needs Apache commons-configuration. I added commons-configuration to my dependency. After run mvn package, too many jar files were added into WEB-INF/lib directory. But I found many jars(e.g. xalan-2.7.0.jar) out of the list, which lists commons-configuration's runtime dependencies, shown at home of commons-collections. In commons-configuration-1.2.pom, so many dependencies are added. How to cancel the trouble? a cup of Java, cheers! Sha Jiang -- View this message in context: http://www.nabble.com/Too-many-jars-added-to-lib--tf2558368s177.html#a7129610 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: Too many jars added to lib?
This should definitely remove all the unwanted dependencies. Even if they are dependencies of a dependency. I'm doing the same thing to remove all the unwanted files. Can you post your pom.xml? jiangshachina wrote: Hi Dmystery, Thanks for your help. I'm sorry that I cannot success with your instructions. And I also read the guide on maven-war-plugin, especially at http://maven.apache.org/plugins/maven-war-plugin/examples/adding-filtering-webresources.html Unfortunately, I don't find the answer. The guide is on how to add or filter resources from standard/customized resource paths. But it's not on how to filter resources from the dependencies of dependencies. a cup of Java, cheers! Sha Jiang Dmystery wrote: Use maven-war-plugin. Due to transitive dependencies in M2, you need to remove them using the warSourceExcludes tag in the plugin as below. build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-war-plugin/artifactId version2.0.1/version configuration warSourceExcludes WEB-INF/lib/jar1,WEB-INF/lib/jar2, /warSourceExcludes /configuration /plugin /plugins /build Checkout : http://maven.apache.org/plugins/maven-war-plugin/index.html jiangshachina wrote: I have another question. In Web application project, generally, class files would be located at WEB-INF/classes. But now, I want they to be archived, and locate at WEB-INF/lib. And I want the jars could be put into different sub-directory under WEB-INF/lib? maven-jar-plugin or maven-war-plugin can help me? How can I do? jiangshachina wrote: Hello, My web projects needs Apache commons-configuration. I added commons-configuration to my dependency. After run mvn package, too many jar files were added into WEB-INF/lib directory. But I found many jars(e.g. xalan-2.7.0.jar) out of the list, which lists commons-configuration's runtime dependencies, shown at home of commons-collections. In commons-configuration-1.2.pom, so many dependencies are added. How to cancel the trouble? a cup of Java, cheers! Sha Jiang -- View this message in context: http://www.nabble.com/Too-many-jars-added-to-lib--tf2558368s177.html#a7131903 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
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: Too many jars added to lib?
I'm not sure how you are using the plugin, but your pom.xml should read like,
project
parent
groupIdce.demo/groupId
artifactIddemo/artifactId
version1.0-SNAPSHOT/version
/parent
modelVersion4.0.0/modelVersion
groupIdce.demo/groupId
artifactIdwebapp/artifactId
packagingwar/packaging
nameWeb Application Project/name
dependencies
dependency
groupIdce.demo/groupId
artifactIdapp/artifactId
version${project.version}/version
/dependency
dependency
groupIdjavax.servlet/groupId
artifactIdservlet-api/artifactId
version2.4/version
/dependency
dependency
groupIdcommons-configuration/groupId
artifactIdcommons-configuration/artifactId
version1.2/version
exclusions
exclusion
groupIddom4j/groupId
artifactIddom4j/artifactId
/exclusion
/exclusions
/dependency
/dependencies
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-war-plugin/artifactId
version2.0.1/version
configuration
warSourceExcludes
/warSourceExcludes
/configuration
/plugin
/plugins
/build
/project
Do note that the plugin version is 2.0.1
jiangshachina wrote:
Hi,
I used the following scripts(for example, I didn't want dom4j-1.4.jar),
and had a success.
dependency
dependency
groupIdcommons-configuration/groupId
artifactIdcommons-configuration/artifactId
version1.2/version
exclusions
exclusion
groupIddom4j/groupId
artifactIddom4j/artifactId
/exclusion
/exclusions
/dependency
/dependency
but didn't get same result with following scripts,
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-war-plugin/artifactId
version2.0.1/version
configuration
warSourceExcludes
WEB-INF/lib/dom4j-1.4.jar
/warSourceExcludes
/configuration
/plugin
/plugins
/build
And I don't find parameter warSourceExcludes at maven-war-plugin doc
http://maven.apache.org/plugins/maven-war-plugin/war-mojo.html
I also don't find warSourceExcludes at link
http://maven.apache.org/plugins/maven-war-plugin/examples/adding-filtering-webresources.html
Dmystery, you said all is ok in your project.
Can you show your case briefly?
My pom.xml is very simple, following is the all
project
parent
groupIdce.demo/groupId
artifactIddemo/artifactId
version1.0-SNAPSHOT/version
/parent
modelVersion4.0.0/modelVersion
groupIdce.demo/groupId
artifactIdwebapp/artifactId
packagingwar/packaging
nameWeb Application Project/name
dependencies
dependency
groupIdce.demo/groupId
artifactIdapp/artifactId
version${project.version}/version
/dependency
dependency
groupIdjavax.servlet/groupId
artifactIdservlet-api/artifactId
version2.4/version
/dependency
dependency
groupIdcommons-configuration/groupId
artifactIdcommons-configuration/artifactId
version1.2/version
exclusions
exclusion
groupIddom4j/groupId
artifactIddom4j/artifactId
/exclusion
/exclusions
/dependency
/dependencies
/project
a cup of Java, cheers!
Sha Jiang
struberg wrote:
there is a syntax to exclude some transitive
dependencies from the dependency-list:
a small sample:
dependency
groupIdavalon-framework/groupId
artifactIdavalon-framework-api/artifactId
version4.3/version
exclusions
exclusion
groupIdavalon-logkit/groupId
artifactIdavalon-logkit/artifactId
/exclusion
/exclusions
/dependency
I guess this may solve your problems.
best regards,
strub
--- Dmystery [EMAIL PROTECTED] schrieb:
This should definitely remove all the unwanted
dependencies. Even if they are
dependencies of a dependency. I'm doing the same
thing to remove all the
unwanted files.
Can you post your pom.xml?
jiangshachina wrote:
Hi Dmystery,
Thanks for your help.
I'm sorry that I cannot success with your
instructions.
And I also read the guide on maven-war-plugin
Re: Too many jars added to lib?
This sounds strange. Is dom4j jar in your
target/webapp-1.0-SNAPSHOT/WEB-INF/lib ? if its a parent dependency then, it
should be in this folder. warSourceExcludes will exclude whatever jar you
specify from this folder when the plugin creates the war file, but those jar
will continue to exist in that folder.
jiangshachina wrote:
Dear Dmystery,
The following is new pom.xml with your instructions,
project
parent
groupIdce.demo/groupId
artifactIddemo/artifactId
version1.0-SNAPSHOT/version
/parent
modelVersion4.0.0/modelVersion
groupIdce.demo/groupId
artifactIdwebapp/artifactId
packagingwar/packaging
nameWeb Application Project/name
dependencies
dependency
groupIdce.demo/groupId
artifactIdapp/artifactId
/dependency
dependency
groupIdjavax.servlet/groupId
artifactIdservlet-api/artifactId
version2.4/version
/dependency
dependency
groupIdcommons-configuration/groupId
artifactIdcommons-configuration/artifactId
version2.4/version
/dependency
/dependencies
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-war-plugin/artifactId
version2.0.1/version
configuration
warSourceExcludesdom4j-1.4.jar/warSourceExcludes
/configuration
/plugin
/plugins
/build
/project
But can't get result I expect.
If change warSourceExcludesdom4j-1.4.jar/warSourceExcludes to
warSourceExcludesWEB-INF/lib/dom4j-1.4.jar/warSourceExcludes, the
result still is that.
Dmystery wrote:
I'm not sure how you are using the plugin, but your pom.xml should read
like,
project
parent
groupIdce.demo/groupId
artifactIddemo/artifactId
version1.0-SNAPSHOT/version
/parent
modelVersion4.0.0/modelVersion
groupIdce.demo/groupId
artifactIdwebapp/artifactId
packagingwar/packaging
nameWeb Application Project/name
dependencies
dependency
groupIdce.demo/groupId
artifactIdapp/artifactId
version${project.version}/version
/dependency
dependency
groupIdjavax.servlet/groupId
artifactIdservlet-api/artifactId
version2.4/version
/dependency
dependency
groupIdcommons-configuration/groupId
artifactIdcommons-configuration/artifactId
version1.2/version
exclusions
exclusion
groupIddom4j/groupId
artifactIddom4j/artifactId
/exclusion
/exclusions
/dependency
/dependencies
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-war-plugin/artifactId
version2.0.1/version
configuration
warSourceExcludes
/warSourceExcludes
/configuration
/plugin
/plugins
/build
/project
Do note that the plugin version is 2.0.1
jiangshachina wrote:
Hi,
I used the following scripts(for example, I didn't want dom4j-1.4.jar),
and had a success.
dependency
dependency
groupIdcommons-configuration/groupId
artifactIdcommons-configuration/artifactId
version1.2/version
exclusions
exclusion
groupIddom4j/groupId
artifactIddom4j/artifactId
/exclusion
/exclusions
/dependency
/dependency
but didn't get same result with following scripts,
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-war-plugin/artifactId
version2.0.1/version
configuration
warSourceExcludes
WEB-INF/lib/dom4j-1.4.jar
/warSourceExcludes
/configuration
/plugin
/plugins
/build
And I don't find parameter warSourceExcludes at maven-war-plugin doc
http://maven.apache.org/plugins/maven-war-plugin/war-mojo.html
I also don't find warSourceExcludes at link
http://maven.apache.org/plugins/maven-war-plugin/examples/adding-filtering-webresources.html
Dmystery, you said all is ok in your project.
Can you show your case briefly?
My pom.xml is very simple, following is the all
project
parent
groupIdce.demo/groupId
artifactIddemo/artifactId
version1.0-SNAPSHOT/version
/parent
modelVersion4.0.0
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
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
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(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(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
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]
[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]
[m2] jspaces
Where can i find jspaces.jar? I'm not able to find it at http://repo1.maven.org -- View this message in context: http://www.nabble.com/-m2--jspaces-tf2459964.html#a6856501 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] jspaces
Yeah it is Gigaspaces. If i remember right, there used to be a groupIdcom.j_spacesgroupId artifactIdjspaces/artifactId version5.0/version artifact in maven central repo. Wayne Fay wrote: I'm not positive what's inside YOUR jspaces.jar... But Google says jspaces.jar is most likely Gigaspaces... If that's in fact what you're looking for, I can agree that I'm unable to find it in the Maven2 repo myself. Please ask the Gigaspaces guys to make a Maven bundle and upload it via JIRA. Wayne On 10/17/06, Dmystery [EMAIL PROTECTED] wrote: Where can i find jspaces.jar? I'm not able to find it at http://repo1.maven.org -- View this message in context: http://www.nabble.com/-m2--jspaces-tf2459964.html#a6856501 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--jspaces-tf2459964.html#a6859350 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Transitive dependencies in war-plugin.
IS there a way to turn off transitive dependencies while packaging a war file? I want my ejb-client in the war-packaging but it brings along all the ejb-client dependencies. I've searched enough on this forum but cant find a solution. My webapp pom has a dependency as follows.. dependencies dependency groupIdcom-server/groupId artifactIdcom-server-ejb/artifactId version1/version typeejb-client/type /dependency /dependencies Has anyone solved this isssue? -- View this message in context: http://www.nabble.com/Transitive-dependencies-in-war-plugin.-tf2452739.html#a6835918 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: Transitive dependencies in war-plugin.
Thanks! I was not aware of the warSourceExcludes
But, wont it be great to just turn-off the t-dependency by a
transitive/transitive element.
dependency
groupIdcom-server/groupId
artifactIdcom-server-ejb/artifactId
version1/version
typeejb-client/type
transitivefalse/transitive
/dependency
Zarar Siddiqi wrote:
If you are using the maven-war-plugin, you can use the
warSourceExcludes elements to exclude jars from your war. They will
still appear in the work directory (where the war is assembled) but once
your war is bundled up, they won't be there. You should also look at
dependentWarExcludes.
http://maven.apache.org/plugins/maven-war-plugin/examples/war-overlay.html
Here's some usage:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-war-plugin/artifactId
version2.0.1/version
configuration
warSourceExcludes
WEB-INF/lib/antlr-2*,WEB-INF/lib/avalon*/warSourceExcludes
warName${app.name}/warName
containerConfigXML${war.dir}/context.xml/containerConfigXML
webXml${war.dir}/WEB-INF/web.xml/webXml
/configuration
/plugin
Zarar
Dmystery wrote:
IS there a way to turn off transitive dependencies while packaging a war
file?
I want my ejb-client in the war-packaging but it brings along all the
ejb-client dependencies. I've searched enough on this forum but cant find
a solution.
My webapp pom has a dependency as follows..
dependencies
dependency
groupIdcom-server/groupId
artifactIdcom-server-ejb/artifactId
version1/version
typeejb-client/type
/dependency
/dependencies
Has anyone solved this isssue?
--
View this message in context:
http://www.nabble.com/Transitive-dependencies-in-war-plugin.-tf2452739.html#a6848538
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Missing Javax jars
The javax.transaction and javax.security jars are missing in http://repo1.maven.org. I'm using hibernate for compilation and i dont know why it wants these javax jars. I can set up a local hibernate repository but i want maven to download everything from the central. Is there a work around. Thanks -- View this message in context: http://www.nabble.com/Missing-Javax-jars-tf2441945.html#a6809041 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
