Re: maven antrun plugin 1.7 ignores second execution
mvn integration-test. Wait. I think I got it. Will try Monday at work. Cheers, Kai 2012/2/25 Wayne Fay > > that matches the target of the first execution. However the second > > execution never appears in the log nor is a file created for it. What am > I > ... > > 5. > > 6. Starting Apache > > 7. pre-integration-test > ... > > 21. > > 22. Stopping Apache > > 23. post-integration-test > > What command are you executing? "mvn ..." > > PS Here's a hint into why this probably isn't working... review the > lifecycle: > > http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html > > Wayne >
maven antrun plugin 1.7 ignores second execution
Hello, I have problems getting my second antrun target to run. Below is the plugin configuration I use. Its purpose is to start an Apache httpd server before integration tests and kill it later. The executables and folders are set profile and os specific. The first execution I can see in the maven log, and in target/antrun there is a build-main.xml created that matches the target of the first execution. However the second execution never appears in the log nor is a file created for it. What am I missing here? Cheers, Kai http://pastebin.com/JhpA0vaY 1. 2. maven-antrun-plugin 3. 1.7 4. 5. 6. Starting Apache 7. pre-integration-test 8. 9. run 10. 11. 12. 13. Starting Apache httpd: 14. 15. 16. 17. 18. 19. 20. 21. 22. Stopping Apache 23. post-integration-test 24. 25. run 26. 27. 28. 29. Stopping Apache httpd: 30. 31. 32. 33. 34. 35. 36. 37. 38. 39. * *
Deployment in Repository without version in file name?
Hello, I was asked if it is possible to deploy a file into the repository without the version suffix added to it? In this case a war file should be retrieved from the Nexus repository into a Tomcat wepapps folder using wget, and they are looking for a way where the file doesn't need to be renamed. Cheers, Kai
Re: Maven 3.0 jar assembly: classpath in runnable jar manifest is missing
Me neither, but because maven resisted to resolve the plugin dependency
maven-filtering-1.0-SNAPSHOT
2011/2/8 Dennis Lundberg
> On 2011-02-07 22:41, Stevo Slavić wrote:
> > Doesn't work for me with
> >
> https://repository.apache.org/content/groups/snapshots/org/apache/maven/plugins/maven-assembly-plugin/2.2.1-SNAPSHOT/maven-assembly-plugin-2.2.1-20110203.204308-1.jar
> > - classpath still nowhere to be seen. Checking out
> > maven-assembly-plugin trunk (r1068108), installing it, and making use
> > of it didn't help as well.
>
> OK, thanks for testing.
>
> >
> > Regards,
> > Stevo.
> >
> > On Mon, Feb 7, 2011 at 8:28 PM, Dennis Lundberg
> wrote:
> >> On 2011-02-07 00:27, Kai Hackemesser wrote:
> >>> Hi there,
> >>>
> >>> We try to migrate to Maven 3.0 here but one assembly causes us
> headache.
> >>>
> >>> In the project we try to build a runnable jar that depends on libraries
> that
> >>> are assembled into a lib folder. Under Maven 2(.2.1) we have no problem
> with
> >>> that, the runnable jar works as designed. The same project build under
> Maven
> >>> 3.0.2 currently builds the project without complaints, but in our
> resulting
> >>> jar's MANIFEST.MF file the Class-Path entry is missing completely.
> >>>
> >>> Is this a known bug, is there a workaround known if so? Or do I need to
> >>> modify something in the assembly for this?
> >>
> >> Can you please try with the latest 2.2.1-SNAPSHOT version of the
> >> Assembly Plugin?
> >>
> >>> here's our plugin configuration:
> >>>
> >>> maven-assembly-plugin
> >>> 2.2
> >>>
> >>>
> >>> deploy-assembly
> >>> package
> >>>
> >>> single
> >>>
> >>>
> >>> false
> >>>
> >>>
> >>> src/main/assembly/executable-assembly.xml
> >>>
> >>>
> >>>
> >>>
> >>> true
> >>>
> com.energyintellect.ecg.Application
> >>> *true*
> >>> false
> >>>
> >>>
> >>> eig-${project.version}
> >>>
> >>>
> >>>
> >>>
> >>> and the assembly descriptor:
> >>>
> >>> http://maven.apache.org/xsd/assembly-1.1.0";
> xmlns:xsi="
> >>> http://www.w3.org/2001/XMLSchema-instance";
> >>> xsi:schemaLocation="http://maven.apache.org/xsd/assembly-1.1.0
> >>> http://maven.apache.org/xsd/assembly-1.1.0-SNAPSHOT.xsd";>
> >>> bin
> >>>
> >>> jar
> >>>
> >>> false
> >>>
> >>>
> >>> false
> >>> true
> >>> runtime
> >>>
> >>> com.[...]
> >>> com.[...]
> >>> com.[...]
> >>> com.[...]
> >>> com.smardec:license4j
> >>> net.wimpi:modbus
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> target/classes
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> Cheers,
> >>> Kai
> >>>
> >>
> >>
> >> --
> >> Dennis Lundberg
> >>
> >> -
> >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> >> For additional commands, e-mail: users-h...@maven.apache.org
> >>
> >>
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> >
> >
>
>
> --
> Dennis Lundberg
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
Maven 3.0 jar assembly: classpath in runnable jar manifest is missing
Hi there,
We try to migrate to Maven 3.0 here but one assembly causes us headache.
In the project we try to build a runnable jar that depends on libraries that
are assembled into a lib folder. Under Maven 2(.2.1) we have no problem with
that, the runnable jar works as designed. The same project build under Maven
3.0.2 currently builds the project without complaints, but in our resulting
jar's MANIFEST.MF file the Class-Path entry is missing completely.
Is this a known bug, is there a workaround known if so? Or do I need to
modify something in the assembly for this?
here's our plugin configuration:
maven-assembly-plugin
2.2
deploy-assembly
package
single
false
src/main/assembly/executable-assembly.xml
true
com.energyintellect.ecg.Application
*true*
false
eig-${project.version}
and the assembly descriptor:
http://maven.apache.org/xsd/assembly-1.1.0"; xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/xsd/assembly-1.1.0
http://maven.apache.org/xsd/assembly-1.1.0-SNAPSHOT.xsd";>
bin
jar
false
false
true
runtime
com.[...]
com.[...]
com.[...]
com.[...]
com.smardec:license4j
net.wimpi:modbus
target/classes
Cheers,
Kai
Re: Override 'provided' dependency in maven assembly?
We tried it in the pom we want to build, but no success. The setting in the parent pom should stay untouched. 2010/9/22 Wayne Fay > > we have the case that we have a managed dependency to jug:jug.jar > :provided > > in our managed dependency pom. Now one of our applications should include > > that jar as it gets deployed to a place where jug is not provided. When > we > > Did you try just setting it to "compile"? And explicitly mentioning it > in the proper pom, of course. > > Wayne > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Override 'provided' dependency in maven assembly?
Hi there, we have the case that we have a managed dependency to jug:jug.jar :provided in our managed dependency pom. Now one of our applications should include that jar as it gets deployed to a place where jug is not provided. When we set the scope in the pom in question to 'runtime' the maven assembly is still not deploying the jar into the deployment zip. We tried to force it using an include tag in the dependencySet tag, but this only let to a message that the string didn't match. Even more strange - this worked well while the pom was in SNAPSHOT mode. What do I miss here? Cheers, Kai
Writing a plugin, intercepting resource plugin...
Hello, I am thinking about a plugin, that when present in a maven pom plugins set should automatically adds some special source and target folder to the resources plugin, so that some special resources are copied without having to configure them in the resources plugin itself. How do I do that ? Cheers, Kai - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Plugin Development: how to make a multi value parameter available via command line args
Hi there, Does anybody know an example of how to annotate / evaluate a multivalue parameter exposed via command line and plugin configuration? I haven't found a general syntax for that. Cheers, Kai
Re: Begginer's question: How can I use an other Mojo in my own plugin?
I found a way to get my plugin dependencies from outside:
@SuppressWarnings("unchecked")
List pluginArtifacts =
pluginManager.getPluginDescriptorForPrefix("myPrefix").getArtifacts();
Artifact plugin = null;
for(Artifact artifact: pluginArtifacts){
if(artifact.getArtifactId().equals("theArtifactImLookingFor")){
plugin = artifact;
break;
}
}
Cheers,
Kai
2010/2/23 Stephen Connolly
> ahh you want the dependencies of your plugin... as distinct from the
> dependencies of the project your plugin is running in... I can't remember
> exactly what you need to inject... somebody (Benjamin maybe) might have it
> on the tip of their tongue... otherwise you'll have to wait while I look it
> up
>
> Sent from my [rhymes with tryPod] ;-)
>
>
> On 23 Feb 2010, at 00:50, Kai Hackemesser
> wrote:
>
> Ok, I can try that. How can I get the dependencies of the current plugin?
>> I
>> tried to get them with
>> pluginManager.getPluginDefinitionForPrefix("myprefix", session,
>> project).getDependencies() but that returned only an empty list.
>>
>> Cheers,
>> Kai
>>
>> 2010/2/23 Stephen Connolly
>>
>> depending on another maven plugin is a bad plan. Due to issues with how
>>> Maven 2 loads plugins, the first version of a plugin loaded in a
>>> multi-module build is the only version that is loaded.
>>>
>>> Maven 3 will fix this somewhat, but in essence your build will be
>>> completely
>>> unpredictable if you try to depend on another plugin.
>>>
>>> IIRC getting the resolved dependencies is actually quite easy from within
>>> maven (just annotate the mojo with @requiresDependencyResolution scope
>>> where
>>> scope is the scope you require and then I think annotate a field with
>>> @parameter expression="${project.artifacts}" or something similar...
>>> you're
>>> making your life more complex by trying to depend on a separate plugin
>>>
>>> -Stephen
>>>
>>> On 22 February 2010 21:59, Kai Hackemesser >>
>>>> wrote:
>>>>
>>>
>>> Hi, James,
>>>>
>>>> that tip is almost good! But this one executes the mojo, and I want to
>>>>
>>> have
>>>
>>>> the mojo object accessible, as I want to access a field. In more
>>>> details,
>>>>
>>> I
>>>
>>>> want to call the getResults() method on ResolveDependenciesMojo to get
>>>>
>>> hold
>>>
>>>> of the dependencies.
>>>> The actual scenario: I want to build a classpath string containing some
>>>> dependencies of the plugin and the dependencies of the current project.
>>>>
>>> Or
>>>
>>>> I
>>>> need a list of resolved jar files for the same set of dependencies.
>>>>
>>>> Cheers,
>>>> Kai
>>>>
>>>
>>>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
Re: Begginer's question: How can I use an other Mojo in my own plugin?
Ok, I can try that. How can I get the dependencies of the current plugin? I
tried to get them with
pluginManager.getPluginDefinitionForPrefix("myprefix", session,
project).getDependencies() but that returned only an empty list.
Cheers,
Kai
2010/2/23 Stephen Connolly
> depending on another maven plugin is a bad plan. Due to issues with how
> Maven 2 loads plugins, the first version of a plugin loaded in a
> multi-module build is the only version that is loaded.
>
> Maven 3 will fix this somewhat, but in essence your build will be
> completely
> unpredictable if you try to depend on another plugin.
>
> IIRC getting the resolved dependencies is actually quite easy from within
> maven (just annotate the mojo with @requiresDependencyResolution scope
> where
> scope is the scope you require and then I think annotate a field with
> @parameter expression="${project.artifacts}" or something similar... you're
> making your life more complex by trying to depend on a separate plugin
>
> -Stephen
>
> On 22 February 2010 21:59, Kai Hackemesser >wrote:
>
> > Hi, James,
> >
> > that tip is almost good! But this one executes the mojo, and I want to
> have
> > the mojo object accessible, as I want to access a field. In more details,
> I
> > want to call the getResults() method on ResolveDependenciesMojo to get
> hold
> > of the dependencies.
> > The actual scenario: I want to build a classpath string containing some
> > dependencies of the plugin and the dependencies of the current project.
> Or
> > I
> > need a list of resolved jar files for the same set of dependencies.
> >
> > Cheers,
> > Kai
>
Re: Begginer's question: How can I use an other Mojo in my own plugin?
Hi, James, that tip is almost good! But this one executes the mojo, and I want to have the mojo object accessible, as I want to access a field. In more details, I want to call the getResults() method on ResolveDependenciesMojo to get hold of the dependencies. The actual scenario: I want to build a classpath string containing some dependencies of the plugin and the dependencies of the current project. Or I need a list of resolved jar files for the same set of dependencies. Cheers, Kai 2010/2/22 James William Dumay > Hey Kai, > You might want to checkout the Mojo Executor project :) > > http://code.google.com/p/mojo-executor/ > > James > > > Kai Hackemesser wrote: > >> Hi, >> >> I would like to execute another Mojo (the ResolveDependenciesMojo) from >> inside my own Mojo. I wasn't yet successful in adding it with the >> @component >> annotation. What is a proper way to do that? >> >> Cheers, >> Kai >> >> >> > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Begginer's question: How can I use an other Mojo in my own plugin?
Hi, I would like to execute another Mojo (the ResolveDependenciesMojo) from inside my own Mojo. I wasn't yet successful in adding it with the @component annotation. What is a proper way to do that? Cheers, Kai
learning about dependencies of a plugin
Hi there, I'm writing my first plugin. My plugin will have a dependency to another library/artifact that needs to be added to the classpath when the plugin executes its work. How can I find the artifact that the plugin is depending to, when the plugin is running? The maven-dependency-plugin resolves the dependencies of the current project, not of the current plugin. Or am I wrong here? Cheers, Kai
M2Eclipse 0.9.9.200909092308 - Maven Project builder is running endless
Hi, Do you know how to stop M2Ecklipse Project builder from running in all the time? As soon as it reaches the end it starts from begin with info: Maven Builder: AUTO_BUILD requireFullBuild I get each time this warning 29/09/09 12:50:27 PM: [WARN] 'reporting.plugins.plugin.version' is missing for org.apache.maven.plugins:maven-javadoc-plugin @ ... which seems to come from Maven 3.0 snaphot used from the builder (I want it to use Maven 2.0 as long as this isn't fixed - or how do I fix it?) Cheers, Kai
Re: Problems with latest m2eclipse
Just found it. the setting for the Maven runtime in the builder configuration dialog was hidden because the configuration window was a little too small. Looks like an eclipse issue.
Problems with latest m2eclipse
Hello, I just updated my eclipse configuration today, and it is complaining now about things that aren't absolutely understandable to me. The plugins mentioned in the output below aren't defined by my project and should be use whatever is default. The project has an extra m2 builder defined to cal war:exploded after saving stuff in Eclipse. I have found after my update that Eclipse has updated the Maven runtime to 3.0 snapshot, but I have defined my own configuration for 2.0.10 that should be used. I haven't found a way to configure m2 builder to use anything instead the default maven config. How do I solve that issue? [INFO] Scanning for projects... [WARNING] [WARNING] Some problems were encountered while building the effective model for com.en[...]war:2.0.0-SNAPSHOT [WARNING] [WARNING] 'reporting.plugins.plugin.version' is missing for org.apache.maven.plugins:maven-javadoc-plugin @ com.en[...]:2.0.0-SNAPSHOT (C:\workspace\suite-4.0-SNAPSHOT\project\pom.xml) [WARNING] 'reporting.plugins.plugin.version' is missing for org.codehaus.mojo:taglist-maven-plugin @ com.en[...]:2.0.0-SNAPSHOT (C:\workspace\suite-4.0-SNAPSHOT\project\pom.xml) [WARNING] 'reporting.plugins.plugin.version' is missing for org.apache.maven.plugins:maven-jxr-plugin @ com.en[...]:2.0.0-SNAPSHOT (C:\workspace\suite-4.0-SNAPSHOT\project\pom.xml) [WARNING] 'reporting.plugins.plugin.version' is missing for org.apache.maven.plugins:maven-surefire-report-plugin @ com.en[...]:2.0.0-SNAPSHOT (C:\workspace\suite-4.0-SNAPSHOT\project\pom.xml) [WARNING] 'reporting.plugins.plugin.version' is missing for org.apache.maven.plugins:maven-checkstyle-plugin @ com.en[...]:2.0.0-SNAPSHOT (C:\workspace\suite-4.0-SNAPSHOT\project\pom.xml) [WARNING] [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build. [WARNING] [WARNING] For this reason, future Maven versions might no longer support building such malformed projects. [WARNING] [INFO] [INFO] [INFO] Building clariti 2.0.0-SNAPSHOT [INFO] [INFO] [INFO] --- maven-war-plugin:2.1-alpha-2:exploded (default-cli) @ project --- [INFO] Exploding webapp [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 3.359s [INFO] Finished at: Mon Sep 28 16:35:55 NZDT 2009 [INFO] Final Memory: 4M/8M [INFO] [ERROR] modelEncoding : modelEncoding Debugging information message : modelEncoding : modelEncoding cause-exception : com.thoughtworks.xstream.mapper.CannotResolveClassException cause-message : modelEncoding : modelEncoding class : org.apache.maven.plugin.war.util.WebappStructure required-type : org.apache.maven.model.Dependency path: /webapp-structure/dependenciesInfo/org.apache.maven.plugin.war.util.DependencyInfo/dependency/modelEncoding line number : 2039 ---
How to use subversion in an ant task in maven?
Hi, can anyone show me an example how to use an svn ant task in maven? where can I get the svnant library in a repository? Cheers, Kai
Re: Using two 'central' repository mirrors?
Hi, Wayne, Yes, there is: I'm not in position to suggest that. They seem to want having it isolated. They only mirror the open source packages they require for their product, as example FOP and some apache commons. They don't want the developers to add uncontrolled software. I'm just an external, and I'm just trying to get around that because I have a problem after upgrading to Maven 2.0.7 (see earlier post today '(2.0.7) LinkageError: Class org/xml/sax/XMLReader violates loader constraints') Ciao! Kai Wayne Fay schrieb: This is an unnecessarily complex setup. I would suggest consolidating things to a single mirror, ideally by simply setting up the existing "local central repo mirror" to proxy to the "real" Central. Is there a reason you can't set this up? Wayne On 7/19/07, Kai Hackemesser <[EMAIL PROTECTED]> wrote: Hi there, The company I'm currently working at has its own local 'central' repository mirror, which doesn't proxy to any outer repository. They have deployed their local code there. How should I set up my settings to access a real outer mirror for update first and if this fails lookup (because it's a private jar) the private 'mirror'? Ciao! Kai - 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: (2.0.7) LinkageError: Class org/xml/sax/XMLReader violates loader constraints
I see. Do you know which library caused that? In that thread you mentioned someone told to upgrade to surefire-2.3 - I already have that before. Any other suggestion? Ciao! Kai Lukas Theussl schrieb: I had a similar problem recently in a doxia build [1], running 'mvn -U' solved it... HTH, -Lukas [1] http://mail-archives.apache.org/mod_mbox/maven-doxia-dev/200706.mbox/browser Kai Hackemesser wrote: hi there! Since I upgraded to Maven 2.0.7 my maven surefire tests fail with exceptions like this: java.lang.LinkageError: Class org/xml/sax/XMLReader violates loader constraints at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:539) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123) at java.net.URLClassLoader.defineClass(URLClassLoader.java:251) at java.net.URLClassLoader.access$100(URLClassLoader.java:55) at java.net.URLClassLoader$1.run(URLClassLoader.java:194) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:187) at org.codehaus.surefire.IsolatedClassLoader.loadClass(IsolatedClassLoader.java:61) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302) at org.apache.avalon.framework.configuration.DefaultConfigurationBuilder.getHandler(DefaultConfigurationBuilder.java:145) at org.apache.avalon.framework.configuration.DefaultConfigurationBuilder.setParser(DefaultConfigurationBuilder.java:131) at org.apache.avalon.framework.configuration.DefaultConfigurationBuilder.(DefaultConfigurationBuilder.java:107) at org.apache.avalon.framework.configuration.DefaultConfigurationBuilder.(DefaultConfigurationBuilder.java:82) at org.apache.fop.apps.FopFactory.setUserConfig(FopFactory.java:514) ... 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:324) at junit.framework.TestCase.runTest(TestCase.java:154) at junit.framework.TestCase.runBare(TestCase.java:127) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:118) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) 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:324) at org.codehaus.surefire.battery.JUnitBattery.executeJUnit(JUnitBattery.java:246) at org.codehaus.surefire.battery.JUnitBattery.execute(JUnitBattery.java:220) at org.codehaus.surefire.Surefire.executeBattery(Surefire.java:204) at org.codehaus.surefire.Surefire.run(Surefire.java:153) at org.codehaus.surefire.Surefire.run(Surefire.java:77) 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:324) at org.codehaus.surefire.SurefireBooter.run(SurefireBooter.java:104) at org.apache.maven.test.SurefirePlugin.execute(SurefirePlugin.java:303) 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:280) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25
Using two 'central' repository mirrors?
Hi there, The company I'm currently working at has its own local 'central' repository mirror, which doesn't proxy to any outer repository. They have deployed their local code there. How should I set up my settings to access a real outer mirror for update first and if this fails lookup (because it's a private jar) the private 'mirror'? Ciao! Kai - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
(2.0.7) LinkageError: Class org/xml/sax/XMLReader violates loader constraints
hi there! Since I upgraded to Maven 2.0.7 my maven surefire tests fail with exceptions like this: java.lang.LinkageError: Class org/xml/sax/XMLReader violates loader constraints at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:539) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123) at java.net.URLClassLoader.defineClass(URLClassLoader.java:251) at java.net.URLClassLoader.access$100(URLClassLoader.java:55) at java.net.URLClassLoader$1.run(URLClassLoader.java:194) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:187) at org.codehaus.surefire.IsolatedClassLoader.loadClass(IsolatedClassLoader.java:61) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302) at org.apache.avalon.framework.configuration.DefaultConfigurationBuilder.getHandler(DefaultConfigurationBuilder.java:145) at org.apache.avalon.framework.configuration.DefaultConfigurationBuilder.setParser(DefaultConfigurationBuilder.java:131) at org.apache.avalon.framework.configuration.DefaultConfigurationBuilder.(DefaultConfigurationBuilder.java:107) at org.apache.avalon.framework.configuration.DefaultConfigurationBuilder.(DefaultConfigurationBuilder.java:82) at org.apache.fop.apps.FopFactory.setUserConfig(FopFactory.java:514) ... 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:324) at junit.framework.TestCase.runTest(TestCase.java:154) at junit.framework.TestCase.runBare(TestCase.java:127) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:118) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) 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:324) at org.codehaus.surefire.battery.JUnitBattery.executeJUnit(JUnitBattery.java:246) at org.codehaus.surefire.battery.JUnitBattery.execute(JUnitBattery.java:220) at org.codehaus.surefire.Surefire.executeBattery(Surefire.java:204) at org.codehaus.surefire.Surefire.run(Surefire.java:153) at org.codehaus.surefire.Surefire.run(Surefire.java:77) 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:324) at org.codehaus.surefire.SurefireBooter.run(SurefireBooter.java:104) at org.apache.maven.test.SurefirePlugin.execute(SurefirePlugin.java:303) 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: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: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) I've googled a while and the only thing I found is that comparable exceptions seem to appear since 2.0.6 - I haven't found a solution in net. Is t
