Re: [m2] aspectj
Hi Kaare, I haven't noticed before that it's possible to switch to @AJ sintax and working with AspectJ without a special compiler, thank you for the tip! But it's still needed to do aspect weaving, how do you make it with maven 2, or even with maven 1? 2005/11/7, Kaare Nilsen [EMAIL PROTECTED]: You should not rely on the number of people that asks for priority. The persons that asks are the one who already have a motivation of using maven, the wast majority i would suspect checks if maven have a plugin for it, if not they would use something else. I for sure would not use maven if i was not on a java 1.5 project due to the fact of the missing aspectJ plugin. But luckily using aspectJ 5 and java 1.5 i don't need a special compiler. With all that said. Maven2 really has made my building way more easy, and if you could use java 1.5 and aspectJ 5 that is a working combination /Kaare Nilsen On 07/11/05, Brett Porter [EMAIL PROTECTED] wrote: I don't believe this is currently working. You're probably the 3rd person that has asked all year - so that probably justifies the priority :) That's possibly just a matter of it not being there though - I'm sure if it was started more would come out of the woodwork. There has been some discussion on this list in the past about possible ways to implement it - if you are interested in searching for that, revieweing, and reviving the discussion, we'd really appreciate anything you are able to contribute. For myself, I'm not an aspectj user. Cheers, Brett On 11/5/05, Eduardo Rocha [EMAIL PROTECTED] wrote: I have seen in Maven Plugin Matrix that AspectJ Plugin for Maven 2 is considered Low Priority (!) and it is yet to be done. However, I was googling around and found some Maven2 compilers besides javac (eclipse, aspectj), called plexus-SOMENAME-compiler. I saw in this mail list as well someone trying to use csharp compiler as well. Does anyone already has AspectJ + Maven 2 working? Does anyone know how to properly use these plexus compilers? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Custom Global Repository Out of Memory Error
Hi Michael Owen! Have you lost interest in football after leaving Real Madrid or are you sharing your time developing and playing in Newcastle United? PS.: sorry the off topic :) 2005/11/10, Michael Owen [EMAIL PROTECTED]: Hi, I'm using Maven 1.1 beta 2, and have a custom global repository on Tomcat 5.5.4. For Tomcat to publish the global repository files it uses a symbolic link. I'm finding that when I use the custom global repository to download dependencies, a lot of the time I get out of memory errors. I've increased the amount of memory given to Tomcat by specifying JAVA_OPTS to be -Xmn64m -Xms256m -Xmx1024m in catalina.sh. On the server I also have AntHill Pro running. The errors are connected when downloading repository files by Maven due to keeping tracks on things and not having problems when only AntHill Pro is installed. Not sure if it is a Maven downloading problem or Tomcat problem. Anybody got an idea what a solution could be, be it a Maven or Tomcat problem? :) Cheers Mike - 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: How to make self contained database dependant unit tests in maven 2?
Testing with another DB than the production one has its disadvantages too. There is a nice discussion about it here: http://www.theserverside.com/tss?service=direct/0/NewsThread/threadViewer.markNoisy.linksp=l33215sp=l165443 2005/11/9, Brian E. Fox [EMAIL PROTECTED]: Funny you should mention that. I just stumbled upon this myself. Do you need to execute anything before hand to setup the hsqldb or do you just point the jdbc connection at it? -Original Message- From: Chris Richardson [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 09, 2005 2:06 PM To: Maven Users List Subject: Re: How to make self contained database dependant unit tests in maven 2? I use HSQL DB (http://hsqldb.org/) for testing with both Kodo JDO and Hibernate. It works well and is very fast. This is what I have in my pom.xml dependency groupIdhsqldb/groupId artifactIdhsqldb/artifactId version1.7.2.2 http://1.7.2.2/version scopetest/scope /dependency Chris -- Enterprise POJO consulting - http://www.chrisrichardson.net Author, POJOs in Action - http://www.manning.com/crichardson Enterprise POJOs blog - http://chris-richardson.blog-city.com On 11/9/05, Brian E. Fox [EMAIL PROTECTED] wrote: We currently have a system that uses JDO (Kodo implementation) for our persistence layer. In order to test these persistent classes, I need to have a JDBC driver and compliant database running. I would really like to make the process completely self contained like the Maven Wagon builds. ie download a jar from somewhere that gives me an ultra light db implementation and jdbc driver and run my tests on it. Does anyone know if such a thing exists and where I might find it? Alternatively, does anyone know of any decent file based jdbc drivers that are open source? Thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Surefire report plugin exception
Hi Wim, It is a known bug, it was already reported and fixed: http://jira.codehaus.org/browse/MOJO-100?page=all []'s Eduardo 2005/11/8, Wim Deblauwe [EMAIL PROTECTED]: Hi, after running mvn -U clean site:site site:deploy I go the following error: [INFO] Generate Maven Surefire Report report. java.lang.NumberFormatException: For input string: 0,157 at sun.misc.FloatingDecimal.readJavaFormatString(FloatingDecimal.java:1224) at java.lang.Float.parseFloat(Float.java:394) at org.codehaus.mojo.surefire.ReportTestSuite.startElement( ReportTestSuite.java:78) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement (AbstractSAXParser.java:533) at com.sun.org.apache.xerces.internal.impl.dtd.XMLDTDValidator.startElement( XMLDTDValidator.java:798) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement (XMLDocumentFragmentScannerImpl.java:878) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$ContentDispatcher.scanRootElementHook (XMLDocumentScannerImpl.java:1157) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch (XMLDocumentFragmentScannerImpl.java:1794) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument (XMLDocumentFragmentScannerImpl.java:368) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse( XML11Configuration.java:834) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse( XML11Configuration.java:764) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java :148) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse( AbstractSAXParser.java:1242) at javax.xml.parsers.SAXParser.parse(SAXParser.java:375) at javax.xml.parsers.SAXParser.parse(SAXParser.java:311) at org.codehaus.mojo.surefire.ReportTestSuite.init(ReportTestSuite.java :59) at org.codehaus.mojo.surefire.SurefireReportParser.parseXMLReportFiles( SurefireReportParser.java:42) at org.codehaus.mojo.surefire.SurefireReportGenerator.doGenerateReport( SurefireReportGenerator.java:44) at org.codehaus.mojo.surefire.SurefireReportMojo.executeReport( SurefireReportMojo.java:77) at org.apache.maven.reporting.AbstractMavenReport.generate( AbstractMavenReport.java:117) at org.apache.maven.plugins.site.SiteMojo.generateReportsPages(SiteMojo.java :802) at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:301) at org.apache.maven.plugin.DefaultPluginManager.executeMojo( DefaultPluginManager.java:399) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals( DefaultLifecycleExecutor.java:519) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal (DefaultLifecycleExecutor.java:482) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal( DefaultLifecycleExecutor.java:452) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures (DefaultLifecycleExecutor.java:301) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( DefaultLifecycleExecutor.java:268) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute( DefaultLifecycleExecutor.java:137) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:113) at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java :39) at sun.reflect.DelegatingMethodAccessorImpl.invoke( DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) java.lang.NullPointerException at org.codehaus.mojo.surefire.SurefireReportGenerator.constructTestCasesSection (SurefireReportGenerator.java:344) at org.codehaus.mojo.surefire.SurefireReportGenerator.doGenerateReport( SurefireReportGenerator.java:60) at org.codehaus.mojo.surefire.SurefireReportMojo.executeReport( SurefireReportMojo.java:77) at org.apache.maven.reporting.AbstractMavenReport.generate( AbstractMavenReport.java:117) at org.apache.maven.plugins.site.SiteMojo.generateReportsPages(SiteMojo.java :802) at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:301) at org.apache.maven.plugin.DefaultPluginManager.executeMojo( DefaultPluginManager.java:399) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals( DefaultLifecycleExecutor.java:519) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal (DefaultLifecycleExecutor.java:482) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
Re: [m2] Surefire report plugin exception
You can checkout HEAD on CVS and build Maven as indicated in site :) 2005/11/8, Wim Deblauwe [EMAIL PROTECTED]: ah, ok. Hopefully a new version containing this fix will be released soon, because now I can't generate any site using Maven 2. I would like to be able to continue my conversion from M1 to M2 as soon as possible. thanks, Wim 2005/11/8, Eduardo Rocha [EMAIL PROTECTED]: Hi Wim, It is a known bug, it was already reported and fixed: http://jira.codehaus.org/browse/MOJO-100?page=all []'s Eduardo 2005/11/8, Wim Deblauwe [EMAIL PROTECTED]: Hi, after running mvn -U clean site:site site:deploy I go the following error: [INFO] Generate Maven Surefire Report report. java.lang.NumberFormatException: For input string: 0,157 at sun.misc.FloatingDecimal.readJavaFormatString(FloatingDecimal.java :1224) at java.lang.Float.parseFloat(Float.java:394) at org.codehaus.mojo.surefire.ReportTestSuite.startElement( ReportTestSuite.java:78) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement (AbstractSAXParser.java:533) at com.sun.org.apache.xerces.internal.impl.dtd.XMLDTDValidator.startElement( XMLDTDValidator.java:798) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement (XMLDocumentFragmentScannerImpl.java:878) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$ContentDispatcher.scanRootElementHook (XMLDocumentScannerImpl.java:1157) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch (XMLDocumentFragmentScannerImpl.java:1794) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument (XMLDocumentFragmentScannerImpl.java:368) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse( XML11Configuration.java:834) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse( XML11Configuration.java:764) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse( XMLParser.java :148) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse( AbstractSAXParser.java:1242) at javax.xml.parsers.SAXParser.parse(SAXParser.java:375) at javax.xml.parsers.SAXParser.parse(SAXParser.java:311) at org.codehaus.mojo.surefire.ReportTestSuite.init( ReportTestSuite.java :59) at org.codehaus.mojo.surefire.SurefireReportParser.parseXMLReportFiles( SurefireReportParser.java:42) at org.codehaus.mojo.surefire.SurefireReportGenerator.doGenerateReport( SurefireReportGenerator.java:44) at org.codehaus.mojo.surefire.SurefireReportMojo.executeReport( SurefireReportMojo.java:77) at org.apache.maven.reporting.AbstractMavenReport.generate( AbstractMavenReport.java:117) at org.apache.maven.plugins.site.SiteMojo.generateReportsPages( SiteMojo.java :802) at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:301) at org.apache.maven.plugin.DefaultPluginManager.executeMojo( DefaultPluginManager.java:399) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals( DefaultLifecycleExecutor.java:519) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal (DefaultLifecycleExecutor.java:482) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal( DefaultLifecycleExecutor.java:452) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures (DefaultLifecycleExecutor.java:301) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( DefaultLifecycleExecutor.java:268) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute( DefaultLifecycleExecutor.java:137) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:113) at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke( NativeMethodAccessorImpl.java :39) at sun.reflect.DelegatingMethodAccessorImpl.invoke( DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) java.lang.NullPointerException at org.codehaus.mojo.surefire.SurefireReportGenerator.constructTestCasesSection (SurefireReportGenerator.java:344) at org.codehaus.mojo.surefire.SurefireReportGenerator.doGenerateReport( SurefireReportGenerator.java:60) at org.codehaus.mojo.surefire.SurefireReportMojo.executeReport( SurefireReportMojo.java:77
[m2] aspectj
I have seen in Maven Plugin Matrix that AspectJ Plugin for Maven 2 is considered Low Priority (!) and it is yet to be done. However, I was googling around and found some Maven2 compilers besides javac (eclipse, aspectj), called plexus-SOMENAME-compiler. I saw in this mail list as well someone trying to use csharp compiler as well. Does anyone already has AspectJ + Maven 2 working? Does anyone know how to properly use these plexus compilers? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
MNG-1216 - Project Report Locale Bug
Are you sure bug MNG-1216 is fixed? I am having the same problem with maven 2.0 final: java.util.MissingResourceException: Can't find bundle for base name project-info-report, locale pt_BR
Re: [m2] Optional Transient Dependecies
Nice idea. 2005/10/24, Tomislav Stojcevich [EMAIL PROTECTED]: If I am correct, maven2 includes all optional transient dependencies by default and you have to specify an exclude for each optional transient dependency you do not want. This could potentially lead to many excludes. It would be nice to have a flag to to turn off all optional transient dependencies from being included by default for a specific dependency (something like excludeOptionalDependencies) and then specify what you want included rather than specify what you want excluded. IMO the optional transient dependencies you want included would be easier to determine because you usually know what optional dependencies you use, and if you don't your compile or test cases will tell you. --tom
Site archetype should not need archetypeVersion parameter
I am struggling with the following command, found in maven 2's Getting Started Guide: mvn archetype:create -DgroupId=com.mycompany.app -DartifactId=my-app -DarchetypeGroupId=org.apache.maven.archetypes -DarchetypeArtifactId=maven-archetype-site The error is: [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. GroupId: org.apache.maven.archetypes ArtifactId: maven-archetype-site Version: RELEASE Reason: Unable to determine the release version org.apache.maven.archetypes:maven-archetype-site:RELEASE:jar Currently I am using -DarchetypeVersion=1.0-alpha-2 to make it work, but I think this is only because there is no maven-metadata.xml in folder /maven2/org/apache/maven/archetypes/maven-archetype-site at www.ibiblio.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
