Re: Testing maven java web projects?
Would like to test Web based maven java project and use Maven 2.0 with stubs llibs open source like Junits and etc. Any advices? thanks, dt ww.ejinz.com search tools - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [logging] commons-logging Makes My POM So Ugly
Hi Wayne, Thanks a lot for your tip. I tried that and now my pom looks much better now :) And now I also see why it's better to use specific spring-xxx.jar(s) sub-component, instead of the monolithic spring.jar, that is, to avoid excluding spring-xxx.jar(s) multi times in case other dependencies also depend on them. Thanks On 11/25/07, Wayne Fay <[EMAIL PROTECTED]> wrote: > Could you try declaring a dependency on commons-logging directly, and > setting its scope to provided? Then you can remove all of those > exclusions, and it won't get bundled with your app. (At least, that's > the theory...) > > Wayne > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Translation for Chinese Users
Sounds great, and you have good timing. Dennis L. just sent an email requesting translation assistance. Wayne On 11/22/07, Juven Xu <[EMAIL PROTECTED]> wrote: > Hi, guys: > > I'm a maven user from China and I do the build work for my company which > is in Shanghai. > Now I find that I've already been attracted by this powerful project > management tool and I really want to do something to contribute. > So, how about letting me do some translation work for Chinese users? > Anyone agree with me? > Thanks. > > Juven > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
The Maven team needs help from translators
Hi all We are preparing the next release of the maven-project-info-reports-plugin. The current localizations are lacking translations for lots of resources. We need your help improving this. Have a look at this report, and see if you are skilled in any of the listed languages: http://people.apache.org/~dennisl/maven-project-info-reports-plugin/l10n-status.html If so please create a patch and attach it to this issue in JIRA: http://jira.codehaus.org/browse/MPIR-34 Make sure you use unicode escape sequences for non-ascii characters. You can see how this is done in the current localizations. For more info on internationalization/localization in Maven plugins, see this page: http://maven.apache.org/plugins/maven-site-plugin/i18n.html If you have any questions about this, please don't hesitate to ask here on the list. "Thanks for your cooperation" -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [logging] commons-logging Makes My POM So Ugly
Could you try declaring a dependency on commons-logging directly, and setting its scope to provided? Then you can remove all of those exclusions, and it won't get bundled with your app. (At least, that's the theory...) Wayne On 11/24/07, Roger Ye <[EMAIL PROTECTED]> wrote: > Here is my attempt to do logging only with log4j, no commons-logging > or jdk-logging. > > So, the original intent is to drop commons-logging away, but now it's > everywhere in my pom.xml... > > and, what's interesting, to do "mvn tomcat:run", I have to explicitly > include the 1.1 version of JCL to make the problematic JCL 1.0.3 > version go away. BTW. maybe this is not the most appropriate way? if > so, please tell me. > > then I still have the error > > Console output > [INFO] [tomcat:run] > [INFO] Using existing Tomcat server configuration at C:\work\prj\target/tomcat > [INFO] Starting tomcat server > [INFO] Starting Servlet Engine: Apache Tomcat/5.5.15 > [INFO] XML validation disabled > log4j:ERROR A "org.apache.log4j.ConsoleAppender" object is not > assignable to a "org.apache.log4j.Appender" variable. > log4j:ERROR The class "org.apache.log4j.Appender" was loaded by > log4j:ERROR [EMAIL PROTECTED] > whereas object of type > log4j:ERROR "org.apache.log4j.ConsoleAppender" was loaded by > [WebappClassLoader > delegate: false > repositories: > --> Parent Classloader: > [EMAIL PROTECTED] > ]. > log4j:ERROR Could not instantiate appender named "stdout". > 2007-11-24 18:23:04,732 WARN > org.apache.struts2.config.Settings.getLocale(Settings.java:143) >Settings: Could not parse struts.locale setting, substituting > default VM locale > > [INFO] Initializing Coyote HTTP/1.1 on http-8080 > [INFO] Starting Coyote HTTP/1.1 on http-8080 > > > > > == POM == > > > http://maven.apache.org/POM/4.0.0"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; >xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 > http://maven.apache.org/xsd/maven-4.0.0.xsd";> > >4.0.0 >pkg >prj >war >PRJ >1.0-M1 >... > > >prj > > > >com.sun.tools.xjc.maven2 >maven-jaxb-plugin >1.1 > > > com.ws.schema >-wsdl > > > **/*.wsdl > > > /target/generated/xjc/java > > > > >generate > > > > > >maven-compiler-plugin > >UTF-8 >1.5 >1.5 >true >128m >512m > > > >org.codehaus.mojo >tomcat-maven-plugin >1.0-alpha-1 > >/ > > > > > commons-logging > > commons-logging >1.1 > > > > >org.codehaus.mojo > > hibernate3-maven-plugin >2.0-alpha-2 > > > >hbm2java > > /target/generated/hbn/java > > >hbm2ddl > > /target/generated/hbn >
RE: Code Coverage Plugins with Maven 2
I've created an issue for this in MOJO's JIRA. If this is the wrong location, please let me know. http://jira.codehaus.org/browse/MOJO-954 Matt mraible wrote: > > This didn't work. AFAICT, the Cobertura and AspectJ plugin can't be > activated at the same time if you want Cobertura reports to work. > > Matt > > > mraible wrote: >> >> It looks like this is a known issue in the aspectj-maven-plugin. >> >> http://jira.codehaus.org/browse/MOJO-456 >> >> Looks like we're using the latest version, so I guess I need to add a new >> execution with a configuration to do weaveMainSourceFolder=false. >> >> Matt >> >> >> mraible wrote: >>> >>> Hmmm, it looks like the aspectj-maven-plugin is causing the problem. If >>> I remove the following from my pom.xml, everything works fine: >>> >>> >>> org.codehaus.mojo >>> aspectj-maven-plugin >>> 1.0-beta-2 >>> >>> 1.5 >>> true >>> 1.5 >>> true >>> >>> >>> org.springframework >>> spring-aspects >>> >>> >>> >>> >>> >>> >>> compile >>> >>> >>> >>> >>> >>> Any ideas how to make the two play nicely together? >>> >>> Matt >>> >>> mraible wrote: This is what I'm using. However, it reports 0% coverage. Maybe this is caused by another plugin? Matt Iker Almandoz wrote: > > Matt, > Cobertura 2.0 works ok for me... > > My pom.xml has: > > > > > org.codehaus.mojo > cobertura-maven-plugin > 2.0 > > > > That sets the cobertura version to 2.0 as the latest did not seem to > work... > > > > > >org.codehaus.mojo >cobertura-maven-plugin > > > > Regards, > Iker > > -Original Message- > From: mraible [mailto:[EMAIL PROTECTED] > Sent: Monday, September 24, 2007 9:57 AM > To: users@maven.apache.org > Subject: Code Coverage Plugins with Maven 2 > > > AFAICT, the cobertura-maven-plugin (versions 2.0 and 2.1) doesn't work > and > neither does the emma-maven-plugin in Mojo's sandbox. Has anyone had > any > luck with either of these plugins? Is there an open source > code-coverage > plugin that works with Maven 2? I know about Clover, but that's not > open > source. > > Using Emma and Cobertura with Ant seem to work great. > > Thanks, > > Matt > -- > View this message in context: > http://www.nabble.com/Code-Coverage-Plugins-with-Maven-2-tf4510331s177.html# > a12863761 > 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/Code-Coverage-Plugins-with-Maven-2-tf4510331s177.html#a13926228 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[logging] commons-logging Makes My POM So Ugly
Here is my attempt to do logging only with log4j, no commons-logging or jdk-logging. So, the original intent is to drop commons-logging away, but now it's everywhere in my pom.xml... and, what's interesting, to do "mvn tomcat:run", I have to explicitly include the 1.1 version of JCL to make the problematic JCL 1.0.3 version go away. BTW. maybe this is not the most appropriate way? if so, please tell me. then I still have the error Console output [INFO] [tomcat:run] [INFO] Using existing Tomcat server configuration at C:\work\prj\target/tomcat [INFO] Starting tomcat server [INFO] Starting Servlet Engine: Apache Tomcat/5.5.15 [INFO] XML validation disabled log4j:ERROR A "org.apache.log4j.ConsoleAppender" object is not assignable to a "org.apache.log4j.Appender" variable. log4j:ERROR The class "org.apache.log4j.Appender" was loaded by log4j:ERROR [EMAIL PROTECTED] whereas object of type log4j:ERROR "org.apache.log4j.ConsoleAppender" was loaded by [WebappClassLoader delegate: false repositories: --> Parent Classloader: [EMAIL PROTECTED] ]. log4j:ERROR Could not instantiate appender named "stdout". 2007-11-24 18:23:04,732 WARN org.apache.struts2.config.Settings.getLocale(Settings.java:143) Settings: Could not parse struts.locale setting, substituting default VM locale [INFO] Initializing Coyote HTTP/1.1 on http-8080 [INFO] Starting Coyote HTTP/1.1 on http-8080 == POM == http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd";> 4.0.0 pkg prj war PRJ 1.0-M1 ... prj com.sun.tools.xjc.maven2 maven-jaxb-plugin 1.1 com.ws.schema -wsdl **/*.wsdl /target/generated/xjc/java generate maven-compiler-plugin UTF-8 1.5 1.5 true 128m 512m org.codehaus.mojo tomcat-maven-plugin 1.0-alpha-1 / commons-logging commons-logging 1.1 org.codehaus.mojo hibernate3-maven-plugin 2.0-alpha-2 hbm2java /target/generated/hbn/java hbm2ddl /target/generated/hbn /src/main/resources/hibernate.cfg.xml true schema.sql false
