RE: [mojo-user] Unable to use the weblogic-8.1 plugin to deploy a simple ejb jar
When I manually change the name of the artifact like so mv dsc-ear-1.0.ear dsc-ear.ear Now I get this. [EMAIL PROTECTED]:target]$ cd .. [EMAIL PROTECTED]:ear]$ mvn weblogic:deploy [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'weblogic'. [INFO] [INFO] Building DSC:: Enterprise Application [INFO]task-segment: [weblogic:deploy] [INFO] [INFO] Preparing weblogic:deploy [INFO] [ear:generate-application-xml] [INFO] Generating application.xml [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [ear:ear] [INFO] Copying artifact[jar:net.myco.dsc:dsc-ejb:1.0] to[dsc-ejb-1.0.jar] [INFO] Could not find manifest file: /opt/app/devtp/username/builds/dsc/vobs/opus_dev/earpackaging/ear/src/ma in/application/META-INF/MANIFEST.MF - Generating one [INFO] Building jar: /opt/app/devtp/username/builds/dsc/vobs/opus_dev/earpackaging/ear/target /dsc-ear-1.0.ear Downloading: http://corprepo.edc.myco.net:4321/repository/weblogic/webservices/8.1/we bservices-8.1.pom [WARNING] Unable to get resource from repository central (http://repo1.maven.org/maven2) [INFO] [weblogic:deploy] [INFO] Weblogic Deployment beginning weblogic.management.DeploymentException: Error while loading descriptors: Error processing file 'META-INF/application.xml'. weblogic.xml.process.XMLProcessingException: XML document does not appear to contain a properly formed DOCTYPE header - with nested exception: [weblogic.xml.process.ProcessorFactoryException: XML document does not appear to contain a properly formed DOCTYPE header] - with nested exception: [weblogic.xml.process.ProcessorFactoryException: XML document does not appear to contain a properly formed DOCTYPE header] weblogic.management.ApplicationException: weblogic.management.DeploymentException: Error while loading descriptors: Error processing file 'META-INF/application.xml'. weblogic.xml.process.XMLProcessingException: XML document does not appear to contain a properly formed DOCTYPE header - with nested exception: [weblogic.xml.process.ProcessorFactoryException: XML document does not appear to contain a properly formed DOCTYPE header] - with nested exception: [weblogic.xml.process.ProcessorFactoryException: XML document does not appear to contain a properly formed DOCTYPE header] I think Weblogic is not happy with the application descriptor being generated by mvn because there is no DOCTYPE header. How can I instruct maven to add a DOCTYPE Header to the application.xml? Can I create or modify the application.xml manually? [EMAIL PROTECTED]:target]$ cat application.xml ?xml version=1.0 encoding=UTF-8? application xmlns=http://java.sun.com/xml/ns/j2ee; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/application_1_4.xsd; version=1.4 descriptionDSC/description display-nameDSC Enterprise Application/display-name module javadsc-ejb-1.0.jar/java /module /application -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 26, 2006 11:13 AM To: user@mojo.codehaus.org Subject: Re: [mojo-user] Unable to use the weblogic-8.1 plugin to deploy a simple ejb jar I actually don't use Weblogic much these days, just trying to help Bryan out. ;-) Bryan, let us know how it goes... Wayne On 7/26/06, Scott Ryan [EMAIL PROTECTED] wrote: Yes that will work to change the object that is being sought. you can also use the same structure for deploying the ejb.jar target/dsc-ejb-1.0.jar. I am really trying to get the defaults to work for you guys but in the mean time the overrides will work for you. Scott Ryan Chief Technology Officer Soaring Eagle L.L.C. [EMAIL PROTECTED] www.soaringeagleco.com (303) 263-3044 -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 26, 2006 12:31 AM To: user@mojo.codehaus.org Subject: Re: [mojo-user] Unable to use the weblogic-8.1 plugin to deploy a simple ejb jar Give this a try, it might work (??)... Obviously I'm not positive of all the details, but I think you can figure it out. build plugins plugin groupIdo.a.m.p artifactIdweblogic... configuration objectPathtarget/dsc-ear-1.0.ear/objectPath /configuration ... Wayne - To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [mojo-user] Unable to use the weblogic-8.1 plugin to deploy a simple ejb jar
According to the weblogic documentation.. http://e-docs.bea.com/wls/docs81/programming/app_xml.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [mojo-user] Unable to use the weblogic-8.1 plugin to deploy a simple ejb jar
The only place I specify ejb is in the packagingejb/packaging element of the projects pom. I can not change this and get maven 2.0.4 to generate the ejb-client jars. Why would the weblogic deployer assume a .ejb extension unless maven was somehow passing this to the deployer? -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Friday, July 21, 2006 4:32 PM To: user@mojo.codehaus.org Subject: Re: [mojo-user] Unable to use the weblogic-8.1 plugin to deploy a simple ejb jar If you grok the entire log, you'll find: [INFO] Building ejb dsc-ejb-1.0 [INFO] Building jar: /opt/app/devbox/username/builds/myapp_ssk_dsc_1.0.1/vobs/pos_dev/dsc-pro file-services/target/dsc-ejb-1.0.jar ... [INFO] Building ejb client dsc-ejb-1.0-client [INFO] Building jar: /opt/app/devbox/username/builds/myapp_ssk_dsc_1.0.1/vobs/pos_dev/dsc-pro file-services/target/dsc-ejb-1.0-client.jar ... [INFO] Weblogic Deployment parameters [-deploy, -adminurl, http://devbox.wdc.myco.net:32030, -username, guido, -password, something, -name, dsc-ejb, -targets, myapp-frontend-server, -remote, -nostage, -sourcerootforupload, /opt/app/devbox/username/builds/myapp_ssk_dsc_1.0.1/vobs/pos_dev/dsc-pro file-services/target/dsc-ejb.ejb] weblogic.Deployer$DeployerException: The source file /opt/app/devbox/username/builds/myapp_ssk_dsc_1.0.1/vobs/pos_dev/dsc-pro file-services/target/dsc-ejb.ejb does not exist and cannot be deployed. So basically you are building a .jar file and then the Weblogic deployer is looking for a .ejb file. Change one or the other and its bound to work, I'd expect. Wayne On 7/21/06, Pauquette, Bryan [EMAIL PROTECTED] wrote: To: 'user@mojo.codehaus.org' Trying to deploy a simple ejb-jar using the weblogic 8.1 plugin. I think I followed all of the instructions correctly but alas I am getting the following. (Sensitive information has been changed in the post). It seems the name of the artifact is not correctly updated to .jar a .ejb extension is being used. I already posted on the maven users list regarding a similar issue a few days ago. Is this a bug? Thanks mvn -e -X weblogic:deploy + Error stacktraces are turned on. Maven version: 2.0.4 [DEBUG] Building Maven user-level plugin registry from: '/opt/app/devbox/username/.m2/plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: '/opt/app/devbox/myappbuild/.gnu/maven-2.0.4/conf/plugin-registry.xml' [INFO] Scanning for projects... [DEBUG] Searching for parent-POM: net.myco.dsc:dsc::1.0 of project: null:dsc-ejb:ejb:null in relative path: ../pom.xml [DEBUG] Parent-POM: net.myco.dsc:dsc::1.0 not found in relative path: ../pom.xml [DEBUG] Retrieving parent-POM: net.myco.dsc:dsc::1.0 for project: null:dsc-ejb:ejb:null from the repository. [INFO] Searching repository for plugin with prefix: 'weblogic'. [DEBUG] Skipping disabled repository Maven Snapshots [DEBUG] Skipping disabled repository Maven Snapshots [DEBUG] Skipping disabled repository Maven Snapshots [DEBUG] maven-ejb-plugin: resolved to version 2.0 from repository central [DEBUG] Retrieving parent-POM: org.apache.maven.plugins:maven-plugin-parent::2.0 for project: null:maven-ejb-plugin:maven-plugin:2.0 from the repository. [DEBUG] Skipping disabled repository central [DEBUG] Skipping disabled repository central [DEBUG] weblogic-maven-plugin: resolved to version 2.8.0-20060304.202223-1 from repository Maven Snapshots [DEBUG] Retrieving parent-POM: org.codehaus.mojo:mojo-sandbox::2-SNAPSHOT for project: null:weblogic-maven-plugin:maven-plugin:2.8.0-20060304.202223-1 from the repository. [DEBUG] Skipping disabled repository central [DEBUG] Skipping disabled repository central [DEBUG] mojo-sandbox: resolved to version 2-20060213.034901-2 from repository Maven Snapshots [DEBUG] Retrieving parent-POM: org.codehaus.mojo:mojo::7 for project: null:mojo-sandbox:pom:2-SNAPSHOT from the repository. [DEBUG] weblogic-maven-plugin: resolved to version 2.8.0-20060304.202223-1 from repository Maven Snapshots [DEBUG] Retrieving parent-POM: org.codehaus.cargo:cargo-extensions::0.8 for project: null:cargo-maven2-plugin:maven-plugin:0.2 from the repository. [DEBUG] Retrieving parent-POM: org.codehaus.cargo:cargo::0.8 for project: null:cargo-extensions:pom:null from the repository. [DEBUG] weblogic-maven-plugin: resolved to version 2.8.0-20060304.202223-1 from repository Maven Snapshots [DEBUG] Retrieving parent-POM: org.codehaus.mojo:mojo-sandbox::2-SNAPSHOT for project: null:weblogic-maven-plugin:maven-plugin:2.8.0-20060304.202223-1 from the repository. [DEBUG] mojo-sandbox: resolved to version 2-20060213.034901-2 from repository Maven Snapshots [DEBUG] Retrieving parent-POM: org.codehaus.mojo:mojo::7 for project: null:mojo-sandbox:pom:2-SNAPSHOT from the repository. [DEBUG] weblogic-maven-plugin: resolved to version 2.8.0-20060304.202223-1 from repository Maven Snapshots [INFO
Weblogic Deployment
I have a maven 2.0.4 build creating an ear file that I would like to
deploy to a weblogic 8.1.x container via a mvn command line.
Where do I start?
I have tried getting the maven-weblogic-plugin installed but this
doesn't seem to be working for me. I have tried the following...
mvn install:install-file -Dfile=maven-weblogic-plugin-2.8.0.jar
-DgroupId=org.codehaus.mojo -DartifactId=maven-weblogic-plugin
-Dversion=2.8.0 -Dpackaging=plugin
mvn install:install-file -Dfile=maven-weblogic-plugin-2.8.0.jar
-DgroupId=org.codehaus.mojo -DartifactId=maven-weblogic-plugin
-Dversion=2.8.0 -Dpackaging=jar
These both succeed in that I get the message Build Successful
however
When I attempt to use the plugin via adding the plugin into the ear
pom.xml
Like so
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdmaven-weblogic-plugin/artifactId
configuration
adminServerHostNamemyhostname/adminServerHostName
adminServerPort8081/adminServerPort
userIdweblogic/userId
objectPath${project.build.outputDirectory}/../${project.artifactId}.${
project.packaging}/objectPath
passwordweblogic/password
name${project.artifactId}/name
stagingnostage/staging
targetNames
targetNameopus-frontend-server/targetName
/targetNames
/configuration
/plugin
I get the following
What am I doing wrong?
[EMAIL PROTECTED]:ear]$ mvn -e -X deploy
+ Error stacktraces are turned on.
Maven version: 2.0.4
[DEBUG] Building Maven user-level plugin registry from:
'/opt/app/devtp/bp6048/.m2/plugin-registry.xml'
[DEBUG] Building Maven global-level plugin registry from:
'/opt/app/devtp/opusbuild/.gnu/maven-2.0.4/conf/plugin-registry.xml'
[INFO] Scanning for projects...
[DEBUG] Searching for parent-POM: net.cingular.dsc:dsc::1.0 of project:
null:dsc-ear:ear:null in relative path: ../pom.xml
[DEBUG] Using parent-POM from the project hierarchy at: '../pom.xml' for
project: null:dsc-ear:ear:null
[INFO]
[INFO] Building Device Support Center:: Enterprise Application
[INFO]task-segment: [deploy]
[INFO]
[DEBUG] maven-ear-plugin: resolved to version 2.0 from repository
central
[DEBUG] Retrieving parent-POM:
org.apache.maven.plugins:maven-plugin-parent::2.0 for project:
null:maven-ear-plugin:maven-plugin:2.0 from the repository.
[DEBUG] maven-resources-plugin: resolved to version 2.1 from repository
central
[DEBUG] Retrieving parent-POM:
org.apache.maven.plugins:maven-plugin-parent::2.0 for project:
null:maven-resources-plugin:maven-plugin:2.1 from the repository.
[DEBUG] maven-install-plugin: resolved to version 2.0 from repository
central
[DEBUG] Retrieving parent-POM:
org.apache.maven.plugins:maven-plugin-parent::2.0 for project:
null:maven-install-plugin:maven-plugin:2.0 from the repository.
[DEBUG] maven-deploy-plugin: resolved to version 2.0 from repository
central
[DEBUG] Retrieving parent-POM:
org.apache.maven.plugins:maven-plugin-parent::2.0 for project:
null:maven-deploy-plugin:maven-plugin:2.0 from the repository.
[DEBUG] maven-weblogic-plugin: using locally installed snapshot
[DEBUG] Artifact not found - using stub model: Unable to determine the
latest version
org.codehaus.mojo:maven-weblogic-plugin:pom:LATEST
[DEBUG] Using defaults for missing POM
org.codehaus.mojo:maven-weblogic-plugin:pom:LATEST
[DEBUG] maven-weblogic-plugin: using locally installed snapshot
[DEBUG] Artifact not found - using stub model: Unable to determine the
release version
org.codehaus.mojo:maven-weblogic-plugin:pom:RELEASE
[DEBUG] Using defaults for missing POM
org.codehaus.mojo:maven-weblogic-plugin:pom:RELEASE
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] The plugin 'org.codehaus.mojo:maven-weblogic-plugin' does not
exist or no valid version could be found
[INFO]
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: The plugin
'org.codehaus.mojo:maven-weblogic-plugin' does not exist or no valid
version could be found
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(Default
LifecycleExecutor.java:1281)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindPluginToLifecycl
e(DefaultLifecycleExecutor.java:1216)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMa
ppings(DefaultLifecycleExecutor.java:982)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL
ifecycleExecutor.java:453)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle
Failures(DefaultLifecycleExecutor.java:306)
at
application.xml generation.
When I attempt to deploy my mvn 2.04 generated ear into a weblogic container the container throws a deployment exception due to a missing DOCTYPE header in the application.xml that was generated by maven. weblogic.management.DeploymentException: Error while loading descriptors: Error processing file 'META-INF/application.xml'. weblogic.xml.process.XMLProcessingException: XML document does not appear to contain a properly formed DOCTYPE header - with nested exception: [weblogic.xml.process.ProcessorFactoryException: XML document does not appear to contain a properly formed DOCTYPE header] - with nested exception: [weblogic.xml.process.ProcessorFactoryException: XML document does not appear to contain a properly formed DOCTYPE header] What could be causing this problem? Here is the application.xml generated by maven 2. ?xml version=1.0 encoding=UTF-8? application xmlns=http://java.sun.com/xml/ns/j2ee; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/application_1_4.xsd; version=1.4 descriptionDevice Support Center/description display-nameDevice Support Center Enterprise Application/display-name module web web-uridsc-web-1.0.war/web-uri context-root/web/context-root /web /module module web web-uridsc-kiosk-1.0.war/web-uri context-root/kiosk/context-root /web /module module ejbdsc-ejb-1.0.jar/ejb /module - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Issue with maven 2.0.3, cargo and weblogic 8.x
I am running into an issue with maven2.0.4 and cargo and deploying an ejb-jar to weblogic8x. Has anyone seen a similar issue? It looks like the name of the artifact is being incorrectly ascertained. The extension is not being updated to .jar (instead it uses .ejb) I think the relevant code is here http://svn.cargo.codehaus.org/browse/~raw,r=1061/cargo/cargo/trunk/exten sions/maven2/src/main/java/org/codehaus/cargo/maven2/Deployable.java Is this a bug or am I doing something wrong? Thanks mvn -X -e cargo:start + Error stacktraces are turned on. Maven version: 2.0.4 [DEBUG] Building Maven user-level plugin registry from: '/opt/app/devtp/bp6048/.m2/plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: '/opt/app/devtp/opusbuild/.gnu/maven-2.0.4/conf/plugin-registry.xml' [INFO] Scanning for projects... [DEBUG] Searching for parent-POM: net.mycompany.dsc:dsc::1.0 of project: null:dsc-ejb:ejb:null in relative path: ../pom.xml [DEBUG] Using parent-POM from the project hierarchy at: '../pom.xml' for project: null:dsc-ejb:ejb:null [INFO] Searching repository for plugin with prefix: 'cargo'. [DEBUG] maven-ejb-plugin: resolved to version 2.0 from repository central [DEBUG] Retrieving parent-POM: org.apache.maven.plugins:maven-plugin-parent::2.0 for project: null:maven-ejb-plugin:maven-plugin:2.0 from the repository. [DEBUG] cargo-maven2-plugin: resolved to version 0.1 from repository central [DEBUG] Retrieving parent-POM: org.codehaus.cargo:cargo-extensions::0.7 for project: null:cargo-maven2-plugin:maven-plugin:0.1 from the repository. [DEBUG] Retrieving parent-POM: org.codehaus.cargo:cargo::0.7 for project: null:cargo-extensions:pom:null from the repository. [INFO] [INFO] Building Device Support Center:: EJB Modules [INFO]task-segment: [cargo:start] [INFO] [DEBUG] net.mycompany.dsc:dsc-ejb:ejb:1.0 (selected for null) [DEBUG] commons-logging:commons-logging:jar:1.0.3:provided (selected for provided) [DEBUG] junit:junit:jar:3.7:provided (selected for provided) [DEBUG] logkit:logkit:jar:1.0.1:provided (selected for provided) [DEBUG] log4j:log4j:jar:1.2.6:provided (selected for provided) [DEBUG] org.apache.geronimo.specs:geronimo-j2ee_1.4_spec:jar:1.0:provided (selected for provided) [DEBUG] org.codehaus.cargo:cargo-maven2-plugin:maven-plugin:0.1:runtime (selected for runtime) [DEBUG] javax.servlet:jsp-api:jar:2.0:runtime (selected for runtime) [DEBUG] javax.servlet:servlet-api:jar:2.4:runtime (selected for runtime) [DEBUG] Retrieving parent-POM: org.codehaus.cargo:cargo-core-containers::0.7 for project: null:cargo-core-container-weblogic:jar:0.7 from the repository. [DEBUG] Retrieving parent-POM: org.codehaus.cargo:cargo-core::0.7 for project: null:cargo-core-containers:pom:null from the repository. [DEBUG] Retrieving parent-POM: org.codehaus.cargo:cargo::0.7 for project: null:cargo-core:pom:null from the repository. [DEBUG] org.codehaus.cargo:cargo-core-container-weblogic:jar:0.7:runtime (selected for runtime) [DEBUG] Retrieving parent-POM: org.codehaus.cargo:cargo-core-api::0.7 for project: null:cargo-core-api-container:jar:0.7 from the repository. [DEBUG] Retrieving parent-POM: org.codehaus.cargo:cargo-core::0.7 for project: null:cargo-core-api:pom:null from the repository. [DEBUG] Retrieving parent-POM: org.codehaus.cargo:cargo::0.7 for project: null:cargo-core:pom:null from the repository. [DEBUG] org.codehaus.cargo:cargo-core-api-container:jar:0.7:runtime (selected for runtime) [DEBUG] ant:ant:jar:1.5.4:runtime (selected for runtime) [DEBUG] Retrieving parent-POM: org.codehaus.cargo:cargo-core-api::0.7 for project: null:cargo-core-api-module:jar:0.7 from the repository. [DEBUG] Retrieving parent-POM: org.codehaus.cargo:cargo-core::0.7 for project: null:cargo-core-api:pom:null from the repository. [DEBUG] Retrieving parent-POM: org.codehaus.cargo:cargo::0.7 for project: null:cargo-core:pom:null from the repository. [DEBUG] org.codehaus.cargo:cargo-core-api-module:jar:0.7:runtime (selected for runtime) [DEBUG] xml-apis:xml-apis:jar:1.3.02:runtime (selected for runtime) [DEBUG] Retrieving parent-POM: org.codehaus.cargo:cargo-core-api::0.7 for project: null:cargo-core-api-util:jar:0.7 from the repository. [DEBUG] Retrieving parent-POM: org.codehaus.cargo:cargo-core::0.7 for project: null:cargo-core-api:pom:null from the repository. [DEBUG] Retrieving parent-POM: org.codehaus.cargo:cargo::0.7 for project: null:cargo-core:pom:null from the repository. [DEBUG] org.codehaus.cargo:cargo-core-api-util:jar:0.7:runtime (selected for runtime) [DEBUG] xerces:xercesImpl:jar:2.6.2:runtime (selected for runtime) [DEBUG] geronimo-spec:geronimo-spec-j2ee-deployment:jar:1.1-rc4:runtime (selected for runtime) [DEBUG] javax.servlet:servlet-api:jar:2.4:runtime (selected for
More information on wrapping jelly scripts.
I have several jelly scripts that I need convert to Mojos. I am attempting to migrate from maven 1.0.2 to at least maven 1.1b3 with the eventual goal of getting to maven 2.0+. I looked through the documentation at the maven web site and I found this statement. Replace scripts with Mojos The new plugin architecture does not specify a specific language implementation, so Jelly scripts and other such artifacts should be re-usable with wrappers. It is recommended that you look into moving to Mojos. I have written a very simple Mojo in the past. Does anyone have any experience with doing something similar? Are there any articles on how to do this? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Free book on maven 2.0
There is a free 294 page book on maven 2.0 at the following website I have no affiliation with this organization other than a friend who got hired by this company. He told me about the book. It has been useful to me so I thought I would pass it on. You have to register to get the book. http://www.mergere.com/m2book_download.jsp - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Multiproject Site
What version of maven are you using? -Original Message- From: Aaron Freeman [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 30, 2006 10:59 AM To: Maven Subject: Multiproject Site I have a multi-module project that I am trying to deploy the site for. When I run the site-deploy command it generates all the project sites and looks like it is copying all the sites out the the web server, but it actually only copies the parent project site and none of the sub-project sites. It there some other command I need to run to get it to do this? - 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: Multiproject Site
If its not 2.0 then the command is maven multiproject:site -Original Message- From: Pauquette, Bryan Sent: Tuesday, May 30, 2006 11:15 AM To: Maven Users List Subject: RE: Multiproject Site What version of maven are you using? -Original Message- From: Aaron Freeman [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 30, 2006 10:59 AM To: Maven Subject: Multiproject Site I have a multi-module project that I am trying to deploy the site for. When I run the site-deploy command it generates all the project sites and looks like it is copying all the sites out the the web server, but it actually only copies the parent project site and none of the sub-project sites. It there some other command I need to run to get it to do this? - 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]
junit-report:report plugin
Has anyone had any experience with running integration tests and publishing the results using the junit-report:report plugin? Here is my situation. I have a set of approximately 100 junit tests that are not really unit tests at all because these tests interact with a legacy system that I need to keep a close eye on. We have our build set up to run at 2:00 am in the morning and unfortunately the legacy system is not available at that time so our junit report shows that a lot of the tests have failed. I have collected all of the tests that I want to run in a test suite and I want to run it at 10:00 am in the morning so I can publish it on a daily basis. I don't want to run these tests with the rest of the nightly 2:00 am build. I am somewhat new to maven and struggle with a lot of the concepts involved so I could use an experienced guide. Does any one have any best practices advice on how to achieve something like this? Thanks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
