[jira] Commented: (MNG-2190) -Dkey=value parameters cannot include spaces in the value
[ http://jira.codehaus.org/browse/MNG-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108054 ] Heinrich Nirschl commented on MNG-2190: --- The approach taken in maven 2.0.7 still does not work as this example shows (with bash on Linux): $ mvn help:effective-settings -Dfoo="ba\" bu" [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'help'. [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Invalid task 'bu': you must specify a valid lifecycle phase, or a goal in the format plugin:goal or pluginGroupId:pluginArtifactId:pluginVersion:goal [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: < 1 second [INFO] Finished at: Sun Sep 23 08:47:21 CEST 2007 [INFO] Final Memory: 1M/66M [INFO] I think it's the responsibility of the shell wrapper to correctly pass the parameters to the java process. Workarounds in Java are just a mess. > -Dkey=value parameters cannot include spaces in the value > - > > Key: MNG-2190 > URL: http://jira.codehaus.org/browse/MNG-2190 > Project: Maven 2 > Issue Type: Bug > Components: Command Line >Affects Versions: 2.0.2 > Environment: Darwin >Reporter: Gordon Henriksen >Assignee: Brett Porter > Fix For: 2.0.x > > Attachments: MNG-2190.patch > > > Even if I properly escape spaces in a path at the shell level, Maven seems to > re-split the command parameters. For instance, on Unix, the following should > all run the compile goal with a property foo="bar baz": > $ mvn compile "-Dfoo=bar baz" > $ mvn compile -Dfoo="bar baz" > $ mvn compile -Dfoo=bar\ baz > But in fact, Maven fails, complaining that "baz" is an invalid task: > [INFO] Scanning for projects... > [INFO] > > [ERROR] BUILD FAILURE > [INFO] > > [INFO] Invalid task 'baz': you must specify a valid lifecycle phase, or a > goal in the format plugin:goal or > pluginGroupId:pluginArtifactId:pluginVersion:goal > [INFO] > > [INFO] For more information, run Maven with the -e switch > [INFO] > > [INFO] Total time: < 1 second > [INFO] Finished at: Wed Mar 29 15:21:01 EST 2006 > [INFO] Final Memory: 1M/2M > [INFO] > > Is this intended behavior? Seems as if Maven is unnecessarily splitting the > string, when the OS already does as much. > I was merely trying to run: > mvn deploy:deploy-file "-Dfile=/Users/me/Desktop/Bellicose > SDK/lib/Bellicose.jar" ... > In my case, it's practical to work around by renaming the Bellicose SDK > folder, but it seems as if Windows users stuck with "C:\Documents and > Settings\..." might have a harder time of it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MECLIPSE-326) m2eclipse goal does not respect additionalBuildcommands and additionalProjectnatures defined in pom
m2eclipse goal does not respect additionalBuildcommands and additionalProjectnatures defined in pom --- Key: MECLIPSE-326 URL: http://jira.codehaus.org/browse/MECLIPSE-326 Project: Maven 2.x Eclipse Plugin Issue Type: Bug Affects Versions: 2.4 Environment: win xp, jre/jdk 1.6, maven 2.0.7, maven-eclipse-plugin 2.4 Reporter: Tom Pasierb Attachments: m2eclipseMojoPatch.patch I have defined additional buildCommand and projectNature in my pom.xml After running eclipse:m2eclipse on my project, the produced eclipse project descriptors contain neither of the above. >From what I saw in the source code the m2eclipseMojo uses the >setAdditionalBuildcommands and setAdditionalProjectnatures methods not >considering that the collections may already contain some entries. I'm attaching a patch that solves this issue, however I have no experience in developing mojos so I'm not sure if I'm doing it the right way. Should it be acceptable please apply the patch. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-1731) ACEGI-JSF Component Library
ACEGI-JSF Component Library --- Key: MAVENUPLOAD-1731 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1731 Project: maven-upload-requests Issue Type: New Feature Reporter: Cagatay Civici ACEGI-JSF Integration library contains the reimplementation of ACEGI's JSP tags as JSF components. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-1323) Plugin extensions (dependencies) not resolved in reactor build
[ http://jira.codehaus.org/browse/MNG-1323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108069 ] Jason van Zyl commented on MNG-1323: I have reverted this change: svn merge -r575987:575986 https://svn.apache.org/repos/asf/maven/components/trunk . As it was breaking trunk horribly. My theory is that I had everything locally required to make it work. Piotr, you'll have to look at you get a PluginDescriptor not found error for tons of plugins which isn't right. > Plugin extensions (dependencies) not resolved in reactor build > -- > > Key: MNG-1323 > URL: http://jira.codehaus.org/browse/MNG-1323 > Project: Maven 2 > Issue Type: Bug > Components: Plugins and Lifecycle >Affects Versions: 2.0 >Reporter: Kenney Westerhof > Fix For: 2.0.x > > Attachments: MNG-1323-components-2.0.x.diff, > MNG-1323-core-integration-testing-2.diff, > MNG-1323-core-integration-testing.diff, > MNG-1323-core-integration-tests-3.diff, MNG-1323-core-integration-tests.diff, > MNG1323-maven-core-2.1.diff > > > I've added a dependency on an Ant Task in > project/build/plugins/plugin[artifactId='maven-antrun-plugin']/dependencies/ > and run that anttask using the antrun plugin. > When run from the project dir itself it runs fine. > When running from the root of the project tree (reactor build, project one > level below root), > antrun bails out because the taskdef can't be found (not on classpath). > It looks like the dependency isn't resolved, or not added to the plugins' > classrealm. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (CONTINUUM-1331) create new page: show current build queue with project name, next build time
[ http://jira.codehaus.org/browse/CONTINUUM-1331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated CONTINUUM-1331: Fix Version/s: (was: Future) 1.1-beta-4 > create new page: show current build queue with project name, next build time > > > Key: CONTINUUM-1331 > URL: http://jira.codehaus.org/browse/CONTINUUM-1331 > Project: Continuum > Issue Type: New Feature > Components: Web interface >Affects Versions: 1.1-alpha-2 >Reporter: tony nys >Assignee: Olivier Lamy > Fix For: 1.1-beta-4 > > > show current build queue with project name, next build time -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (CONTINUUM-583) Show the build queue on the web/xmlrpc interface
[ http://jira.codehaus.org/browse/CONTINUUM-583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated CONTINUUM-583: --- Assignee: Olivier Lamy Fix Version/s: (was: Future) 1.1-beta-4 > Show the build queue on the web/xmlrpc interface > > > Key: CONTINUUM-583 > URL: http://jira.codehaus.org/browse/CONTINUUM-583 > Project: Continuum > Issue Type: New Feature > Components: Web interface, XMLRPC Interface >Reporter: Henri Yandell >Assignee: Olivier Lamy > Fix For: 1.1-beta-4 > > > It would be very nice to be able to see the build queue on the web interface. > The current interface shows whether things are in progress, or in queue; but > not what the order is. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (CONTINUUM-1287) editable build queue
[ http://jira.codehaus.org/browse/CONTINUUM-1287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated CONTINUUM-1287: Fix Version/s: (was: Future) 1.1-beta-4 > editable build queue > > > Key: CONTINUUM-1287 > URL: http://jira.codehaus.org/browse/CONTINUUM-1287 > Project: Continuum > Issue Type: New Feature >Affects Versions: 1.1-alpha-1 >Reporter: Eirik Maus >Assignee: Olivier Lamy > Fix For: 1.1-beta-4 > > > It should be possible to interact with the build queue. > - to see the order of the modules in queue > - to remove entries if you want to cancel the build. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (CONTINUUM-1452) Show a summary total of the Projects and Build Status columns on the Project Groups page
[ http://jira.codehaus.org/browse/CONTINUUM-1452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated CONTINUUM-1452: Patch Submitted: [Yes] > Show a summary total of the Projects and Build Status columns on the Project > Groups page > > > Key: CONTINUUM-1452 > URL: http://jira.codehaus.org/browse/CONTINUUM-1452 > Project: Continuum > Issue Type: Wish > Components: Web - UI >Affects Versions: 1.1-beta-2 >Reporter: Tomislav Stojcevich >Assignee: Olivier Lamy >Priority: Minor > Fix For: 1.1-beta-4 > > Attachments: CONTINUUM-1452-continuum-webapp.patch, Project Group > with totals.jpg > > > It would be nice to see a summary total of all of the projects and the status > displayed at the bottom of the the Projects and Build Status columns on the > Project Groups page. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MRM-511) Maven IT 94 fails when using Archiva as a proxy
Maven IT 94 fails when using Archiva as a proxy --- Key: MRM-511 URL: http://jira.codehaus.org/browse/MRM-511 Project: Archiva Issue Type: Bug Components: remote proxy Affects Versions: 1.0-beta-2 Reporter: Brett Porter looks like a metadata bug - it fails to resolve log4j with version [1.2.9,] - the same thing works when I stop using it as a proxy. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MRM-512) Unable to convert null repository config to archiva repository.
Unable to convert null repository config to archiva repository. --- Key: MRM-512 URL: http://jira.codehaus.org/browse/MRM-512 Project: Archiva Issue Type: Bug Affects Versions: 1.0-beta-2 Reporter: James William Dumay Attachments: wrapper.20070924.log Unable to convert null repository config to archiva repository. I just deleted the default repositories and got a whole bunch of exceptions. There also seems to be some first start schema exceptions in the logs also. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MRM-512) Unable to convert null repository config to archiva repository.
[ http://jira.codehaus.org/browse/MRM-512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James William Dumay updated MRM-512: Attachment: proxy connector removal.log Same occurs for the removal of proxy connectors. See log. > Unable to convert null repository config to archiva repository. > --- > > Key: MRM-512 > URL: http://jira.codehaus.org/browse/MRM-512 > Project: Archiva > Issue Type: Bug >Affects Versions: 1.0-beta-2 >Reporter: James William Dumay > Attachments: proxy connector removal.log, wrapper.20070924.log > > > Unable to convert null repository config to archiva repository. > I just deleted the default repositories and got a whole bunch of exceptions. > There also seems to be some first start schema exceptions in the logs also. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3008) Multiple executions of embedder reuse the ProjectBuildCache
[ http://jira.codehaus.org/browse/MNG-3008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108080 ] Carlos Sanchez commented on MNG-3008: - the memory problem described in last comment happens when calling MavenEmbedder.readProjectWithDependencies( MavenExecutionRequest ) repeatedly. > Multiple executions of embedder reuse the ProjectBuildCache > --- > > Key: MNG-3008 > URL: http://jira.codehaus.org/browse/MNG-3008 > Project: Maven 2 > Issue Type: Bug > Components: Embedding >Affects Versions: 2.1-alpha-1 >Reporter: Carlos Sanchez > Fix For: 2.1 > > > In DefaultModelLineageBuilder.resumeBuildingModelLineage( ModelLineage > lineage, ArtifactRepository localRepository, ProfileManager profileManager ) > there's a call to resolveParentPom passing the projectBuildCache > This test breaks > /trunk/pom.xml (a:b:1.0-SNAPSHOT) > /trunk/child/pom.xml (has a:b:1.0-SNAPSHOT as parent) > when running a goal in /trunk/child/pom.xml it will cache that > a:b:1.0-SNAPSHOT is in /trunk/pom.xml > now if it's moved or copied to /trunk2 or any other place and the embedder is > called again it will use the parent in /trunk/pom.xml instead of > /trunk2/pom.xml as it's in the cache > If it doesn't exist it will throw a FileNotFoundException -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCLOVER-82) Selection of unclovered ear based upon timestamp is too restrictive
[ http://jira.codehaus.org/browse/MCLOVER-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108082 ] Tom Davies commented on MCLOVER-82: --- Window increased to 2 seconds in 3.0-beta-4 > Selection of unclovered ear based upon timestamp is too restrictive > --- > > Key: MCLOVER-82 > URL: http://jira.codehaus.org/browse/MCLOVER-82 > Project: Maven 2.x Clover Plugin > Issue Type: Bug >Affects Versions: 2.4 > Environment: windows/jdk1.5/maven 2. 0.7 >Reporter: Martin Franklin > Fix For: 2.5 > > Attachments: cloverlag.diff > > > When clover plugin is run on a jar artifact using the install lifecycle step, > the unclovered jar file is also created and installed. In certain > circumstances (which appear to be timing related) the unclovered artifact is > installed _after_ the clovered artifact. > The clover plugin, when creating an ear will then use the unclovered artifact > in preference to the unclovered artifact. The patch provided widens the > window and so long as the clovered artifact is no more than 100ms older than > the unclovered artifact, the clovered artifact will be used. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MRM-512) Unable to convert null repository config to archiva repository.
[ http://jira.codehaus.org/browse/MRM-512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-512: - Attachment: update-repository-consumers.log This also occurred when I updated the consumers in Repository Scanning. Please see corresponding log file. > Unable to convert null repository config to archiva repository. > --- > > Key: MRM-512 > URL: http://jira.codehaus.org/browse/MRM-512 > Project: Archiva > Issue Type: Bug >Affects Versions: 1.0-beta-2 >Reporter: James William Dumay > Fix For: 1.0-beta-3 > > Attachments: proxy connector removal.log, > update-repository-consumers.log, wrapper.20070924.log > > > Unable to convert null repository config to archiva repository. > I just deleted the default repositories and got a whole bunch of exceptions. > There also seems to be some first start schema exceptions in the logs also. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MRM-512) Unable to convert null repository config to archiva repository.
[ http://jira.codehaus.org/browse/MRM-512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-512: - Fix Version/s: 1.0-beta-3 > Unable to convert null repository config to archiva repository. > --- > > Key: MRM-512 > URL: http://jira.codehaus.org/browse/MRM-512 > Project: Archiva > Issue Type: Bug >Affects Versions: 1.0-beta-2 >Reporter: James William Dumay > Fix For: 1.0-beta-3 > > Attachments: proxy connector removal.log, > update-repository-consumers.log, wrapper.20070924.log > > > Unable to convert null repository config to archiva repository. > I just deleted the default repositories and got a whole bunch of exceptions. > There also seems to be some first start schema exceptions in the logs also. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRM-512) Unable to convert null repository config to archiva repository.
[ http://jira.codehaus.org/browse/MRM-512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108084 ] Maria Odea Ching commented on MRM-512: -- Same error when saving a Network Proxy.. > Unable to convert null repository config to archiva repository. > --- > > Key: MRM-512 > URL: http://jira.codehaus.org/browse/MRM-512 > Project: Archiva > Issue Type: Bug >Affects Versions: 1.0-beta-2 >Reporter: James William Dumay > Fix For: 1.0-beta-3 > > Attachments: proxy connector removal.log, > update-repository-consumers.log, wrapper.20070924.log > > > Unable to convert null repository config to archiva repository. > I just deleted the default repositories and got a whole bunch of exceptions. > There also seems to be some first start schema exceptions in the logs also. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-3219) Create a CLIRR/JarDiff setup for 2.0.x and 2.1.x
Create a CLIRR/JarDiff setup for 2.0.x and 2.1.x Key: MNG-3219 URL: http://jira.codehaus.org/browse/MNG-3219 Project: Maven 2 Issue Type: New Feature Affects Versions: 2.1 Reporter: Jason van Zyl It may not only be for the core but also the plugin tools that have been separated. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3008) Multiple executions of embedder reuse the ProjectBuildCache
[ http://jira.codehaus.org/browse/MNG-3008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108086 ] Carlos Sanchez commented on MNG-3008: - Discussion http://www.nabble.com/Caching-in-Maven-core-tf4506840s177.html > Multiple executions of embedder reuse the ProjectBuildCache > --- > > Key: MNG-3008 > URL: http://jira.codehaus.org/browse/MNG-3008 > Project: Maven 2 > Issue Type: Bug > Components: Embedding >Affects Versions: 2.1-alpha-1 >Reporter: Carlos Sanchez > Fix For: 2.1 > > > In DefaultModelLineageBuilder.resumeBuildingModelLineage( ModelLineage > lineage, ArtifactRepository localRepository, ProfileManager profileManager ) > there's a call to resolveParentPom passing the projectBuildCache > This test breaks > /trunk/pom.xml (a:b:1.0-SNAPSHOT) > /trunk/child/pom.xml (has a:b:1.0-SNAPSHOT as parent) > when running a goal in /trunk/child/pom.xml it will cache that > a:b:1.0-SNAPSHOT is in /trunk/pom.xml > now if it's moved or copied to /trunk2 or any other place and the embedder is > called again it will use the parent in /trunk/pom.xml instead of > /trunk2/pom.xml as it's in the cache > If it doesn't exist it will throw a FileNotFoundException -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-1732) upload xSocket V2.0-alpha-1
upload xSocket V2.0-alpha-1 --- Key: MAVENUPLOAD-1732 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1732 Project: maven-upload-requests Issue Type: New Feature Reporter: greg xSocket is a easy to use NIO-based library to build high performance, high scalable network applications. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MRM-513) Support remote repositories with passwords
Support remote repositories with passwords -- Key: MRM-513 URL: http://jira.codehaus.org/browse/MRM-513 Project: Archiva Issue Type: Wish Affects Versions: 1.0-beta-1, 1.0-beta-2 Reporter: James William Dumay Support remote repositories with passwords. Currently archiva cannot authenticate to other http auth protected repositories. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCLOVER-71) Cannot resolve license file
[ http://jira.codehaus.org/browse/MCLOVER-71?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108087 ] Tom Davies commented on MCLOVER-71: --- This is fixed in 3.0-beta-4 -- see http://confluence.atlassian.com/x/K4CDBQ for details of this version. > Cannot resolve license file > --- > > Key: MCLOVER-71 > URL: http://jira.codehaus.org/browse/MCLOVER-71 > Project: Maven 2.x Clover Plugin > Issue Type: Bug >Affects Versions: 2.4 >Reporter: Bryan Madsen > Attachments: MavenLoader_24.diff, MCLOVER-71.diff, MCLOVER-71.diff > > > The license file cannot be found when the license location is a URL. This > works with version 2.3. > [INFO] [clover:instrumentInternal] > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Failed to load license file > [http://scm.apparch.cerner.corp/svn/apparch/licenses/clover.license] > Embedded error: Could not find resource > 'http://scm.apparch.cerner.corp/svn/apparch/licenses/clover.license'. > [INFO] > > [INFO] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to load > license file > [http://scm.apparch.cerner.corp/svn/apparch/licenses/clover.license] > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:896) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:739) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:510) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463) > 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:330) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:123) > 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) > Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to load > license file > [http://scm.apparch.cerner.corp/svn/apparch/licenses/clover.license] > at > org.apache.maven.plugin.clover.internal.AbstractCloverMojo.registerLicenseFile(AbstractCloverMojo.java:164) > at > org.apache.maven.plugin.clover.internal.AbstractCloverMojo.registerLicenseFile(AbstractCloverMojo.java:134) > at > org.apache.maven.plugin.clover.internal.AbstractCloverMojo.execute(AbstractCloverMojo.java:119) > at > org.apache.maven.plugin.clover.CloverInstrumentInternalMojo.execute(CloverInstrumentInternalMojo.java:132) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:420) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) > ... 20 more > Caused by: org.codehaus.plexus.resource.loader.ResourceNotFoundException: > Could not find resource > 'http://scm.apparch.cerner.corp/svn/apparch/licenses/clover.license'. > at > org.codehaus.plexus.resource.DefaultResourceManager.getResourceAsInputStream(DefaultResourceManager.java:91) > at > org.codehaus.plexus.resource.DefaultResourceManager.getResourceAsFile(DefaultResourceManager.java:117) > at > org.codehaus.plexus.resource.DefaultResourceManager.getResourceAsFile(DefaultResourceManager.java:100) > at > org.apache.maven.plugin.clover.internal
