jar index?
Hi folks! Are there any indexes available for the repository content - so that I could search for contents of jar-files? It would be could to be able to search for, say, TestCase, and get junit artifacts listed. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Planning for 2.0.10
Brian E. Fox skrev: Now that 2.0.9 is essentially behind us, I think the focus for the next release needs to continue on preventing new regressions and stomping out the old ones. This should take precedence over new features and other "nice to haves" as we still have a significant user base stuck on [snip] All this is important (killing of regressions). But I also want to bring focus to another really killer-issue which seems to have been dormant for a long time - and which is a wagon problem - and which probably is a real PITA for enterprise users - which is probably a large userbase: http://jira.codehaus.org/browse/WAGON-80 It has 19 votes and 20 watchers - and is a year old. It essentially renders maven useless behind a corporate firewall because proxying is applied globally in maven - and nonProxyHosts are not taken into account. Even by using a local mirror with proximity or archiva - there is still a need for proxy-support to reach external resources like findbugs rules etc - or the other way - to access local LAN resources - without going through the corporate proxy. WDYT? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Serious regression in 2.0.8
I don't know if anybody have noticed this one - but it seems like a real
ugly regression bug.
See http://jira.codehaus.org/browse/MNG-3316.
If an attribute in the configuration section of a plugin containes an
attribute with name *encoding - it will result in the folling stack trace:
[INFO] Trace
org.apache.maven.reactor.MavenExecutionException: Failed to build model
from file 'C:\TEMP\pom.xml'.
Error: '${ENCODING.DEFAULT}' for project unknown
at
org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:376)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:289)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)
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:597)
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)
Caused by: org.apache.maven.project.ProjectBuildingException: Failed to
build model from file 'C:\TEMP\pom.xml'.
Error: '${ENCODING.DEFAULT}' for project unknown
at
org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1386)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.j
va:474)
at
org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:197)
at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:548)
at
org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:458)
at
org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:362)
... 11 more
Caused by: java.io.UnsupportedEncodingException: ${ENCODING.DEFAULT}
at
sun.nio.cs.StreamDecoder.forInputStreamReader(StreamDecoder.java:52)
at java.io.InputStreamReader.(InputStreamReader.java:83)
at
hidden.org.codehaus.plexus.util.xml.XmlReader.prepareReader(XmlReader.java:479)
at
hidden.org.codehaus.plexus.util.xml.XmlReader.doRawStream(XmlReader.java:462)
at
hidden.org.codehaus.plexus.util.xml.XmlReader.(XmlReader.java:179)
at
hidden.org.codehaus.plexus.util.xml.XmlReader.(XmlReader.java:142)
at
hidden.org.codehaus.plexus.util.xml.XmlReader.(XmlReader.java:123)
at
hidden.org.codehaus.plexus.util.xml.XmlStreamReader.(XmlStreamReader.java:67)
at
hidden.org.codehaus.plexus.util.ReaderFactory.newXmlReader(ReaderFactory.java:113)
at
org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1376)
... 16 more
[INFO]
[INFO] Total time: < 1 second
[INFO] Finished at: Tue Jan 08 14:10:08 CET 2008
[INFO] Final Memory: 1M/4M
[INFO]
So it seems maven2.0.8 are parsing attributes named *encoding terribly
wrong.
David
David J. M. Karlsen - +47 90 68 22 43
http://www.davidkarlsen.com
http://mp3.davidkarlsen.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Maven Surefire 2.3.1
Mauro Talevi wrote: Hi all, I'd like to release Maven Surefire 2.3.1 Yihaa! That would solve a lot of my problems (http://jira.codehaus.org/browse/SUREFIRE-326 , http://jira.codehaus.org/browse/SUREFIRE-297 and http://jira.codehaus.org/browse/SUREFIRE-388 are all biting us in several projects I work on). A big, awaiting, non-binding +1 :-D -- David J. M. Karlsen - +47 90 68 22 43 http://www.davidkarlsen.com http://mp3.davidkarlsen.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Getting hold of compile classpath in an Ant task
Hi! I've followed the guide at: http://maven.apache.org/guides/plugin/guide-ant-plugin-development.html Unfortunately this guide does not show how to get hold of the compile-classpath defined by the maven project model. After some surfing i stumbled upon maven-ant-tasks which is supposed to be capable of this. Adding this dependency ends up in: [ERROR] FATAL ERROR [INFO] [INFO] org.apache.maven.script.ant.AntMojoComponentFactory cannot be cast to org.codehaus.plexus.component.factory.Compo nentFactory [INFO] [INFO] Trace java.lang.ClassCastException: org.apache.maven.script.ant.AntMojoComponentFactory cannot be cast to org.codehaus.plexus. component.factory.ComponentFactory at org.codehaus.plexus.component.factory.DefaultComponentFactoryManager.findComponentFactory(DefaultComponentFac toryManager.java:68) at org.codehaus.plexus.DefaultPlexusContainer.createComponentInstance(DefaultPlexusContainer.java:1457) at org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManag er.java:93) at org.codehaus.plexus.component.manager.PerLookupComponentManager.getComponent(PerLookupComponentManager.java:4 8) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:331) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:440) at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:562) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:421) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:48 0) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.jav a:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) 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:597) 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) [INFO] [INFO] Total time: 4 seconds [INFO] Finished at: Mon Nov 12 18:47:24 CET 2007 [INFO] Final Memory: 12M/22M [INFO] My questions are: 1) Is maven-plugin-plugin + maven-plugin-tools-ant still the preferred way to develop ant-based maven plugins? 2) How can I reference the compile classpath as defined by maven in my ant-tasks? 3) If 2 is by using maven-ant-tasks - how? (As it fails as described above). -- David J. M. Karlsen - +47 90 68 22 43 http://www.davidkarlsen.com http://mp3.davidkarlsen.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Developing a maven-script-ant with a taget fail with
Oliver Stauss wrote: Hello, I try to develop a maven-script-ant plugin. The idea is to migrate my project from an existing ant into a maven2 (2.0.4). So my first step was to generalize my exising ANT targets and create Seperate Maven2 plugins. I do this reading the Guide: http://maven.apache.org/guides/plugin/guide-ant-plugin-development.html But then the Problem started with the following ANT-TARGET: I need to call a java runtime from the ant file with classpath... A call to the call result in : [INFO] [INFO] [rexx:edit] edit-target: [java] java.lang.NoClassDefFoundError: de/mytools/Editor [java] Exception in thread "main" [java] Java Result: 1 [INFO] Thanks in advance Regards Oliver Stauss mytools.build.xml: = = Mytools.mojos.xml: = edit edit-target Start the Editor = Any pointers for this one? I'm facing the same problem (a year after the original post). Also - if I add org.apache.maven maven-ant-tasks 2.0.7 I'll get a classcast: [INFO] [ERROR] FATAL ERROR [INFO] [INFO] org.apache.maven.script.ant.AntMojoComponentFactory cannot be cast to org.codehaus.plexus.component.factory.Compo nentFactory [INFO] [DEBUG] Trace java.lang.ClassCastException: org.apache.maven.script.ant.AntMojoComponentFactory cannot be cast to org.codehaus.plexus. component.factory.ComponentFactory at org.codehaus.plexus.component.factory.DefaultComponentFactoryManager.findComponentFactory(DefaultComponentFac toryManager.java:68) at org.codehaus.plexus.DefaultPlexusContainer.createComponentInstance(DefaultPlexusContainer.java:1457) at org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManag er.java:93) at org.codehaus.plexus.component.manager.PerLookupComponentManager.getComponent(PerLookupComponentManager.java:4 8) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:331) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:440) at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:562) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:421) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:48 0) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.jav a:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) 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:597) 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) -- David J. M. Karlsen - +47 90 68 22 43 http://www.davidkarlsen.com http://mp3.davidkarlsen.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Preflight check for 2.0.7
Jason van Zyl wrote: I have built a snapshot for 2.0.7 and put it here: http://people.apache.org/~jvanzyl/ I figure are going to try and squeeze in more issues so what I plan is let people state their case and I'll slot those into 2.0.8 and push back whatever I can into 2.0.7 but I would like to call for vote on Wednesday let people mess around and release it on Monday. Works on a fairly large multiproject (~10-12 artifacts)! Same problems with the xdoclet plugin as before - adding ant 1.6.5 as a dep to it fixes the problem. -- David J. M. Karlsen - +47 90 68 22 43 http://www.davidkarlsen.com http://mp3.davidkarlsen.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: M206 Regression: Build is broken
Jörg Schaible wrote: Hi folks, after some hours testing M206 and looking for solutions, I am quite helpless with our build that is broken if I run a multi-project build. Part of this build is the creation of an ejb-client jar and another artifact that is dependend on it. Unfortunately the dependent artifact cannot be compiled, because the classes from the ejb-client are misssing. Culprit seems to be indicated by the line from the resources:resources goal, where the ejb-client is listed with a scope of "null": [DEBUG] ip.evtmon:ip-evtmon-ejb:ejb-client:client:2.2.2-SNAPSHOT (selected for null) and therefore it seems consequently omitted compiling the classes, since it is not part of the classpath anymore. If I build the module locally there's no problem, the scope is "compile", but not when running in a multi-project build. I already tried to introduce a dependencyManagment section in the local POM where I declare this artifacts again with explicit scope "compile". Any idea what might cause this? - Jörg Hi - I expirience the same - but only when running a multiproject: parent -ejb-project (generating ejb and ejb-client) -client-project (using ejb-client) If I try a multibuild it fails, if I cd into client-project and do mvn clean install it succeeds. -- David J. M. Karlsen - +47 90 68 22 43 http://www.davidkarlsen.com http://mp3.davidkarlsen.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Adding extra dirs for surefire classpath
Jason Dillon skrev: Whats the easiest way to add an extra directory to the classpath which surefire will use when running tests? http://jira.codehaus.org/browse/SUREFIRE-180 Also - you could try defining system scoped dependencies - or define them as testResource's - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: 2.0.6 Pre flight check
David J. M. Karlsen skrev: Jason van Zyl wrote: Hi, Before I staged the release I just wanted to get some people to a build first: http://idisk.maven.org/jvanzyl/Public/maven/ Brian, Jason Dillon, and Dan Kulp have tried their builds and I just wanted to get a little more feedback. I'm getting another issue on another project. It builds fine on maven 2.0.5, with the snapshot I get a problem with xdoclet - see the attached log. this realm = app0.child-container[org.codehaus.mojo:xdoclet-maven-plugin] urls[0] = file:/heim/ab62939/.m2/repository/org/codehaus/mojo/xdoclet-maven-plugin/1.0-beta-1-SNAPSHOT/xdoclet-maven-plugin-1.0-beta-1-SNAPSHOT.jar urls[1] = file:/heim/ab62939/.m2/repository/xdoclet/xdoclet-wsee-module/1.2.3/xdoclet-wsee-module-1.2.3.jar urls[2] = file:/heim/ab62939/.m2/repository/xdoclet/xdoclet-jboss-module/1.2.3/xdoclet-jboss-module-1.2.3.jar urls[3] = file:/heim/ab62939/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar urls[4] = file:/heim/ab62939/.m2/repository/xdoclet/xdoclet-orion-module/1.2.3/xdoclet-orion-module-1.2.3.jar urls[5] = file:/heim/ab62939/.m2/repository/xdoclet/xdoclet-xdoclet-module/1.2.3/xdoclet-xdoclet-module-1.2.3.jar urls[6] = file:/heim/ab62939/.m2/repository/xdoclet/xdoclet-jmx-module/1.2.3/xdoclet-jmx-module-1.2.3.jar urls[7] = file:/heim/ab62939/.m2/repository/xdoclet/xdoclet-ibm-module/1.2.3/xdoclet-ibm-module-1.2.3.jar urls[8] = file:/heim/ab62939/.m2/repository/commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.jar urls[9] = file:/heim/ab62939/.m2/repository/commons-collections/commons-collections/2.1/commons-collections-2.1.jar urls[10] = file:/heim/ab62939/.m2/repository/ant/ant/1.5.2/ant-1.5.2.jar urls[11] = file:/heim/ab62939/.m2/repository/xdoclet/xdoclet-apache-module/1.2.3/xdoclet-apache-module-1.2.3.jar urls[12] = file:/heim/ab62939/.m2/repository/xdoclet/xdoclet-fr_FR-locale/1.2.3/xdoclet-fr_FR-locale-1.2.3.jar urls[13] = file:/heim/ab62939/.m2/repository/ant/ant-launcher/1.6.5/ant-launcher-1.6.5.jar urls[14] = file:/heim/ab62939/.m2/repository/xdoclet/xdoclet-objectweb-module/1.2.3/xdoclet-objectweb-module-1.2.3.jar urls[15] = file:/heim/ab62939/.m2/repository/org/apache/maven/plugins/maven-antrun-plugin/1.0/maven-antrun-plugin-1.0.jar urls[16] = file:/heim/ab62939/.m2/repository/xdoclet/xdoclet-java-module/1.2.3/xdoclet-java-module-1.2.3.jar urls[17] = file:/heim/ab62939/.m2/repository/xdoclet/xdoclet-exolab-module/1.2.3/xdoclet-exolab-module-1.2.3.jar urls[18] = file:/heim/ab62939/.m2/repository/xdoclet/xdoclet-bea-module/1.2.3/xdoclet-bea-module-1.2.3.jar urls[19] = file:/heim/ab62939/.m2/repository/xdoclet/xdoclet-mvcsoft-module/1.2.3/xdoclet-mvcsoft-module-1.2.3.jar urls[20] = file:/heim/ab62939/.m2/repository/xdoclet/xdoclet-sun-module/1.2.3/xdoclet-sun-module-1.2.3.jar urls[21] = file:/heim/ab62939/.m2/repository/xdoclet/xdoclet-spring-module/1.2.3/xdoclet-spring-module-1.2.3.jar urls[22] = file:/heim/ab62939/.m2/repository/xdoclet/xdoclet-de-locale/1.2.3/xdoclet-de-locale-1.2.3.jar urls[23] = file:/heim/ab62939/.m2/repository/jboss/jboss-j2ee/3.2.1/jboss-j2ee-3.2.1.jar urls[24] = file:/heim/ab62939/.m2/repository/xdoclet/xdoclet-caucho-module/1.2.3/xdoclet-caucho-module-1.2.3.jar urls[25] = file:/heim/ab62939/.m2/repository/xdoclet/xdoclet-web-module/1.2.3/xdoclet-web-module-1.2.3.jar urls[26] = file:/heim/ab62939/.m2/repository/javax/servlet/servlet-api/2.3/servlet-api-2.3.jar urls[27] = file:/heim/ab62939/.m2/repository/xdoclet/xdoclet-jdo-module/1.2.3/xdoclet-jdo-module-1.2.3.jar urls[28] = file:/heim/ab62939/.m2/repository/xdoclet/xdoclet-tjdo-module/1.2.3/xdoclet-tjdo-module-1.2.3.jar urls[29] = file:/heim/ab62939/.m2/repository/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar urls[30] = file:/heim/ab62939/.m2/repository/xdoclet/xdoclet-openejb-module/1.2.3/xdoclet-openejb-module-1.2.3.jar urls[31] = file:/heim/ab62939/.m2/repository/xdoclet/xdoclet-oracle-module/1.2.3/xdoclet-oracle-module-1.2.3.jar urls[32] = file:/heim/ab62939/.m2/repository/xdoclet/xdoclet-hp-module/1.2.3/xdoclet-hp-module-1.2.3.jar urls[33] = file:/heim/ab62939/.m2/repository/xdoclet/xdoclet-webwork-module/1.2.3/xdoclet-webwork-module-1.2.3.jar urls[34] = file:/heim/ab62939/.m2/repository/xdoclet/xdoclet-mx4j-module/1.2.3/xdoclet-mx4j-module-1.2.3.jar urls[35] = file:/heim/ab62939/.m2/repository/xdoclet/xdoclet-solarmetric-module/1.2.3/xdoclet-solarmetric-module-1.2.3.jar urls[36] = file:/heim/ab62939/.m2/repository/xdoclet/xdoclet/1.2.3/xdoclet-1.2.3.jar urls[37] = file:/heim/ab62939/.m2/repository/xdoclet/xdoclet-jsf-module/1.2.3/xdoclet-jsf-module-1.2.3.jar urls[38] = file:/heim/ab62939/.m2/repository/xdoclet/xdoclet-pramati-module/1.2.3/xdoclet-pramati-module-1.2.3.jar urls[39] = file:/heim/ab62939/.m2/repository/xdoclet/xdoclet-pt_BR-locale/1.2.3/xdoclet-pt_BR-locale-1.2.3.jar urls[40] = file:/heim/ab62939/.m2/repository/xdoclet/xdoclet-ejb-module/1.2.3/xdoclet-ejb-module-1.2.3.jar
Re: 2.0.6 Pre flight check
David J. M. Karlsen wrote: Jason van Zyl wrote: Hi, Before I staged the release I just wanted to get some people to a build first: http://idisk.maven.org/jvanzyl/Public/maven/ Brian, Jason Dillon, and Dan Kulp have tried their builds and I just wanted to get a little more feedback. Fails on surefire reports: [snip] but succeeded on the 2nd run. -- David J. M. Karlsen - +47 90 68 22 43 http://www.davidkarlsen.com http://mp3.davidkarlsen.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: 2.0.6 Pre flight check
Jason van Zyl wrote: Hi, Before I staged the release I just wanted to get some people to a build first: http://idisk.maven.org/jvanzyl/Public/maven/ Brian, Jason Dillon, and Dan Kulp have tried their builds and I just wanted to get a little more feedback. Fails on surefire reports: [INFO] [site:site] [INFO] [ERROR] FATAL ERROR [INFO] [INFO] org/apache/maven/artifact/Artifact [INFO] [INFO] Trace java.lang.NoClassDefFoundError: org/apache/maven/artifact/Artifact at org.apache.maven.plugins.surefire.report.SurefireReportMojo.canGenerateReport(SurefireReportMojo.java:196) at org.apache.maven.plugins.site.AbstractSiteRenderingMojo.filterReports(AbstractSiteRenderingMojo.java:387) at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:73) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:272) 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) [INFO] [INFO] Total time: 2 minutes 44 seconds [INFO] Finished at: Tue Mar 27 18:10:19 MEST 2007 [INFO] Final Memory: 39M/223M [INFO] -- David J. M. Karlsen - +47 90 68 22 43 http://www.davidkarlsen.com http://mp3.davidkarlsen.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Releasing Maven 2.0.5
Mark Hobson wrote: +1, more frequent releases the better. Absolutely - and more frequent releases of plugins too. It's becoming increasingly hard to "sell in" the maven idea to projects due to long-lasting outstanding bugs (or outstanding releases). I think this would be a lot easier if releases were more often cut off. -- David J. M. Karlsen - +47 90 68 22 43 http://www.davidkarlsen.com http://mp3.davidkarlsen.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
maven-dependency-report not reliable
Hi list! I have commons-configuration 1.3 declared in my parent-pom in the dependencyManagement section along with another inhouse artifact which depdends on commons-configuration 1.0rc2. I then have another artifact which depends on commons-configuration 1.3 - all well. But 1.0rc2 end up in my ear along with the other artifacts - no surprise as MNG-1577 is well known. dependency:copy-dependencies also resolves to 1.0rc2 (as it is "nearer"). BUT - running the maven-dependency-report plugin - it states 1.3 as the transitive dependency!? What? Does dependency-report resolve dependecies another way than the rest of maven? Thats dangerous - beacuse it could tell you lies (like this one) - which renders dependency-report totally useless. What's the explaination for this? -- David J. M. Karlsen - +47 90 68 22 43 http://www.davidkarlsen.com http://mp3.davidkarlsen.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
people.apache.org on track?
How is the move of people.apache.org going? I received a few ping answers this night, but it's been non-responsive today - the maintaince-period was scheduled to be over on monday? -- David J. M. Karlsen - +47 90 68 22 43 http://www.davidkarlsen.com http://mp3.davidkarlsen.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [RANT] Maven is both heaven and hell
Alexandre Poitras wrote: I think this is the issue I was referring too. I just know that I can't use a snapshot dependency that has a timestamp in its filename or I won't get the last version. I remember Brett couple of months ago saying this feature wasn't implemented yet. I'll try to find the JIRA issue. This is definitely a showstopper when you don't know about it. Did you set up the repo as a enabled one? On 9/17/06, Wendy Smoak <[EMAIL PROTECTED]> wrote: On 9/17/06, Alexandre Poitras <[EMAIL PROTECTED]> wrote: > Another thing I would like to see fixed is the snapshot apache > repository. Nighlty builds are still deployed using a unique version > identifier. This feature doesn't work and this is why a lot of people > have trouble when it's come to snapshot dependencies. Do you mean *without* a unique version identifier here? This is the 'Maven 2.0.4 will not download a x.x-SNAPSHOT.jar if one is already present in the local repository' problem, correct? It would be nice if it would deploy both a uniquely named version _and_ the x.x.x-SNAPSHOT.jar. The projects I'm involved with have uniqueVersion set to false for that reason. -- Wendy - 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] -- David J. M. Karlsen - +47 90 68 22 43 http://www.davidkarlsen.com http://mp3.davidkarlsen.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] commons attributes plugin
Does there exist an commons attributes plugin for maven2? (Parinsg && compiling). David -- David J. M. Karlsen - +47 90 68 22 43 http://www.davidkarlsen.com http://mp3.davidkarlsen.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] xdoclet plugin - problem binding to phase
Hi!
I've declared the folling in my pom:
org.codehaus.mojo
xdoclet-maven-plugin
generate-sources
xdoclet
destDir="${project.build.outputDirectory}/META-INF" ejbSpec="2.0"
verbose="true" addedTags="@xdoclet-generated">
includes="**/*MDB.java" />
But still I can see xdoclet being called several times:
[INFO] [clean:clean]
...
[INFO] [xdoclet:xdoclet {execution: default}]
[INFO] Initializing DocletTasks!!!
[INFO] Executing tasks
Generating EJB deployment descriptor (ejb-jar.xml).
[INFO] Executed tasks
[INFO] [resources:resources]
[INFO] [compiler:compile]
[INFO] [xdoclet:xdoclet {execution: default}]
[INFO] Initializing DocletTasks!!!
[INFO] Executing tasks
[INFO] Executed tasks
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [surefire:test]
[INFO] Tests are skipped.
[INFO] [ejb:ejb]
Seems like xdoclet is "resetting" the execution of phases?
I would expect it to execute once, and only once at generate-sources,
and then the normal resource, compile, package phases.
The last version of the xdoclet plugin I can find is:
http://www.ibiblio.org/maven2/org/codehaus/mojo/xdoclet-maven-plugin/1.0-alpha-2/
(nov 2005). There are quite som bugs in this plugin - has the project
stalled? Could somebody build a snapshot so that I can test a later version?
--
David J. M. Karlsen - +47 90 68 22 43
http://www.davidkarlsen.com
http://mp3.davidkarlsen.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [discussion/idea] resource scoping
Brett Porter wrote:
I'm sorry ,maybe its just because I'm pre-coffee, but I don't really
understand what you are referring to.
Sorry - I'll try to elaborate a little more:
process-[test-]resources copies with targetPath to
target/[test-]classes, which is added to the classpath. So it should
all be correct.
That's fine - but all this stuff will be added to the test-jar (I'm
using attached tests - so that I can reuse the same tests later - see
http://maven.apache.org/guides/mini/guide-attached-tests.html).
When I run the test phase with surefire in the my main artifact I need
some spring-config, log4j-config etc available on the classpath - but I
do *not* want these to end up in my tests which are jar'ed together for
reuse in other artifacts.
So, what I want to achieve is:
target/test-classes (only .class files - to be added to
--tests.jar
target/some-test-resources (only available on classpath during execution
of tests).
(The same would hold for the main artifact and resources).
I assume you are talking about modifying the manifest Class-Path:
entry in the JAR plugin, which you can do either by:
a) filtering the manifest (this is already possible using normal
filters, it has nothing to do with the JAR plugin)
b) using ${project.*} variables or others in the manifest elements on
the jar plugin configuration.
The clue is to avoid these resources to end up in the archive - but
still have them available on the classpath while executing the tests.
--
David J. M. Karlsen - +47 90 68 22 43
http://www.davidkarlsen.com
http://mp3.davidkarlsen.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[discussion/idea] resource scoping
Hi list! We have resource scoping today with the //build/resources and //build/testresources elements - this is OK for stuff that's supposed to end up in the archived artifact. (yes - I am aware that a different targetPath may be specified - but these directories won't be added to the surefire classpath when executing the tests). Very often one wants to have some other resources (typically configuration) added to the classpath when running tests / execution in a procution environment. What do you guys think is the most appropiate approach to this? 1. automatically add [test]resources with a targetPath element to the surefire classpath? 2. add filtering to the jar plugin? 3. Add ability to append to surefire's classpath manually (See http://jira.codehaus.org/browse/MSUREFIRE-153). It could also be solved by adding the targetPaths to the manifest's classpath entries - but solving it this way will require the resource/config directory to have the same name in all environments. WDYT? Regards, David -- David J. M. Karlsen - +47 90 68 22 43 http://www.davidkarlsen.com http://mp3.davidkarlsen.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Developed a RAD6 extention of maven-eclipse-plugin
Richard van Nieuwenhoven wrote: It supports J2EE projects with the websphere development envorment, supported are - EJB projects - Web projects - EAR- projects all these projects are recognized by rad-6 as what they are and use of the development enviorment including hot-deployment features. i wrote writers for: - the ".j2ee" files - the "application.xml" and the "modulemaps" file - copying the extrenal libs in the ear project root - adapting the MANIFEST.MF of the projects - the ".websettings" file - the ".websiteconfig" file - the ".project" (only alternative project natures/builders) regards, Ritchie Cool - this should probably be merged with the eclipse plugin (maybe we can add a flag true/false. I've registered a related issue: http://jira.codehaus.org/browse/MECLIPSE-136 (for the normal eclipse natures). which could be extended with the stuff you provide. Very nice indeed! -- David J. M. Karlsen - +47 90 68 22 43 http://www.davidkarlsen.com http://mp3.davidkarlsen.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] maven-war-plugin broken again
David J. M. Karlsen wrote: Hi! i was able to add depdendencies to the classpath in the manifest for the generated war, but excluding them from the actual .war archive (as they will be included in the .ear anyway) before ( around version 2.0?). This was possible earlier by adding the depdendencies with scope=provded and or adding **/*.jar clause. This seems to be broken with the current (2.0.1) version. Does anybody know an approach that's known to work with this version? Sorry about this - i deleted the maven-war-plugin and plexus-stuff from my repo (forcing a new download), and added **/*.jar to the configuration, and left the dependencies with compile scope - and this fixed it. David -- David J. M. Karlsen - +47 90 68 22 43 http://www.davidkarlsen.com http://mp3.davidkarlsen.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] maven-war-plugin broken again
Hi! i was able to add depdendencies to the classpath in the manifest for the generated war, but excluding them from the actual .war archive (as they will be included in the .ear anyway) before ( around version 2.0?). This was possible earlier by adding the depdendencies with scope=provded and or adding **/*.jar clause. This seems to be broken with the current (2.0.1) version. Does anybody know an approach that's known to work with this version? -- David J. M. Karlsen - +47 90 68 22 43 http://www.davidkarlsen.com http://mp3.davidkarlsen.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] Jira for maven-war-plugin?
http://maven.apache.org/plugins/maven-war-plugin/issue-tracking.html states that http://jira.codehaus.org/browse/MPA is the url for issue tracking - but this doesn't seem correct. What is the correct url? -- David J. M. Karlsen - +47 90 68 22 43 http://www.davidkarlsen.com http://mp3.davidkarlsen.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] which repo for snapshots?
Hi! Which repository is used for snapshots? I've seen http://people.apache.org/maven-snapshot-repository as well as http://cvs.apache.org/maven-snapshot-repository both? -- David J. M. Karlsen - +47 90 68 22 43 http://www.davidkarlsen.com http://mp3.davidkarlsen.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] release maven-archetype-j2ee-simple
Jesse McConnell wrote: Please vote on releasing maven-archetype-j2ee-simple This archetype is being used by a number of folks on the user list and I have seen a number of requests for it as of late. It was formally known as maven-archetype-j2ee but after discussion on the mailing list and on irc with jdcasey and jason we decided to rename to j2ee-simple and most likely release a number of variations on the j2ee project layout. I know vmassol has other thoughts on a more industrial scale layout which can be released along side this simple one. I'll keep open for 72hrs and then sum up +1 jesse -- jesse mcconnell jesseDOTmcconnellATgmailDOTcom jmcconnellATapacheDOTorg Where can the project be found? What does the plugin do? -- David J. M. Karlsen - +47 90 68 22 43 http://www.davidkarlsen.com http://mp3.davidkarlsen.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
plexus
Hi! I'm using org.codehaus.plexus.util.cli.Commandline to execute shell commands. Does anybody know if it's possible to configure it to use another shell? (e.g. 4dos instead of CMD.EXE) ? -- David J. M. Karlsen - +47 90 68 22 43 http://www.davidkarlsen.com http://mp3.davidkarlsen.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
