[jira] Created: (NMAVEN-85) Install plugin fails when parent project is not in parent directory
Install plugin fails when parent project is not in parent directory Key: NMAVEN-85 URL: http://jira.codehaus.org/browse/NMAVEN-85 Project: NMaven Issue Type: Bug Environment: NMaven head (revision 570776). Maven 2.0.6 Windows Vista. Microsoft Visual Studio 2005 version 8.0.50727.867 Reporter: Peter Nilsson I have a fairly big project built with Maven and the parent of a Maven project is not always located in the parent directory. However this seems to cause problems when installing libraries with NMaven. To try it out created two small projects, foo and bar, in sibling directories. The parent project is foo with the following pom: http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";> 4.0.0 nmaventest foo pom 1.0.0.0 org.apache.maven.dotnet.plugins maven-compile-plugin true I install it into local repo with "mvn install". The child project, bar, has this pom: http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";> 4.0.0 nmaventest foo 1.0.0.0 bar library 1.0.0.0 The bar project contains a single C# file in src/main/csharp. Building project bar with "mvn package" works fine and creates bar.dll. However, installing the dll with "mvn install" cause the following error: [INFO] NMAVEN-1001-000: Failed to install artifacts Embedded error: NMAVEN-001-014: Unable to store model: Message = C:\temp\nmaventest\bar\..\pom.xml (The system cannot find the file specified) It seems like the install plugin tries to install the parent pom as well which of course fails as it is not always available (except in local repo). The end of "mvn install -X": [DEBUG] Configuring mojo 'org.apache.maven.dotnet.plugins:maven-install-plugin:0.14-SNAPSHOT:install' --> [DEBUG] (f) isGacInstall = false [DEBUG] (f) localRepository = C:\Users\peterni\.m2\repository [DEBUG] (f) pomFile = C:\temp\nmaventest\bar\pom.xml [DEBUG] (f) profile = GACUTIL [DEBUG] (f) project = [EMAIL PROTECTED] [DEBUG] -- end configuration -- [INFO] [install:install] 2007-aug-29 19:39:53 org.apache.maven.dotnet.registry.ConnectionsRepository lazyLoad INFO: NMAVEN-080-001: Adding data access object: Class Name = org.apache.maven.dotnet.dao.impl.ProjectDaoImpl 2007-aug-29 19:39:53 org.apache.maven.dotnet.registry.ConnectionsRepository lazyLoad INFO: NMAVEN-080-004: Connection Start Up: Time = 67 [INFO] NMAVEN-001-007: Installing file into repository: File = C:\temp\nmaventest\bar\target\bar.dll [INFO] [ERROR] BUILD ERROR [INFO] [INFO] NMAVEN-1001-000: Failed to install artifacts Embedded error: NMAVEN-001-014: Unable to store model: Message = C:\temp\nmaventest\bar\..\pom.xml (The system cannot find the file specified) [INFO] [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: NMAVEN-1001-000: Failed to install artifacts 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.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.co
[jira] Created: (MAVENUPLOAD-1695) CC/PP API jar
CC/PP API jar - Key: MAVENUPLOAD-1695 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1695 Project: maven-upload-requests Issue Type: New Feature Reporter: Torsten Dettborn To enable interoperability between web servers and access mechanisms, and to facilitate development of device independent web applications, this specification will define a set of APIs for processing CC/PP information. This is result from the jsr188. -- 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] Work started: (MRM-392) pressing 'return' in the blacklist/whitelist form field submits whole form and validates, not pressing associated button
[ http://jira.codehaus.org/browse/MRM-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MRM-392 started by Maria Odea Ching. > pressing 'return' in the blacklist/whitelist form field submits whole form > and validates, not pressing associated button > > > Key: MRM-392 > URL: http://jira.codehaus.org/browse/MRM-392 > Project: Archiva > Issue Type: Bug > Components: web application >Affects Versions: 1.0-alpha-1 >Reporter: Brett Porter >Assignee: Maria Odea Ching >Priority: Critical > Fix For: 1.0-beta-2 > > > - add a proxy connector > - don't fill in any fields > - type "foo" into blacklist field > - press return > EXPECTED: add foo to blacklist > ACTUAL: submits form, gives validation errors -- 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: (MDEP-104) Add Analyze HTML Report
[ http://jira.codehaus.org/browse/MDEP-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105987 ] Jeremy Lauture commented on MDEP-104: - We have checked the patch on the branch and there is a little issue with the bundle file ( analyze-report.properties). To solve it just move it form src/main/java/org/apache/maven/plugin/dependency to src/main/resources. In the patch the path seems to be declrared correctly but in the branch it is not placed into the src/main/resources directory. > Add Analyze HTML Report > --- > > Key: MDEP-104 > URL: http://jira.codehaus.org/browse/MDEP-104 > Project: Maven 2.x Dependency Plugin > Issue Type: Improvement >Affects Versions: 2.0-alpha-5 >Reporter: Jeremy Lauture >Assignee: Brian Fox > Attachments: analyze-report-mojo.patch > > > It would be nice to have a HTML analyze report (as same as the CLI analyze > report) when we generate the web site project. > Find in attachment our patch that provides this new feature. > In order to use it, you can add this reporting section in your pom.xml: > > > > org.apache.maven.plugins > maven-dependency-plugin > 2.0-alpha-5-SNAPSHOT > > > > analyze-report > > > > > > -- 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] Closed: (MANT-31) test dependencies are not included
[ http://jira.codehaus.org/browse/MANT-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MANT-31. --- Assignee: Vincent Siveton Resolution: Won't Fix Fix Version/s: 2.0 Should be already fixed in the snapshot > test dependencies are not included > -- > > Key: MANT-31 > URL: http://jira.codehaus.org/browse/MANT-31 > Project: Maven 2.x Ant Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-1 >Reporter: Robert Egglestone >Assignee: Vincent Siveton > Fix For: 2.0 > > > The generated build file should include any dependencies from the pom with a > scope of test on the test classpath, and download them in get-deps. -- 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] Closed: (CONTINUUM-1207) Need to be able to define default build definition used when adding new project
[ http://jira.codehaus.org/browse/CONTINUUM-1207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse closed CONTINUUM-1207. --- Resolution: Fixed Applied. I added default conf for maven1 and Ant projects too > Need to be able to define default build definition used when adding new > project > --- > > Key: CONTINUUM-1207 > URL: http://jira.codehaus.org/browse/CONTINUUM-1207 > Project: Continuum > Issue Type: New Feature >Affects Versions: 1.1-alpha-1 >Reporter: thierry lach >Assignee: Olivier Lamy >Priority: Minor > Fix For: 1.1-beta-3 > > Attachments: CONTINUUM-1207 > > > The default build definition of "clean install --batch-mode --non-recursive" > is hard coded in DefaultContinuum.java, it should be configurable. -- 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: (SCM-337) Unable to checkout or update projects with Continuum-1.1-beta-1
Unable to checkout or update projects with Continuum-1.1-beta-1 --- Key: SCM-337 URL: http://jira.codehaus.org/browse/SCM-337 Project: Maven SCM Issue Type: Bug Components: maven-scm-provider-synergy Affects Versions: 1.0 Environment: Maven 2.0.5 and Continuum-1.1-beta-1 Reporter: David Vicente Priority: Blocker Hi I used Continuum 1.0.3 with Synergy SCM provider(with maven-SCM-api-1.0-beta-4.jar and maven-SCM-provider-synergy-1.0-beta-4.jar in my \ lib) and all works fine. I have just installed continuum-1.1-beta-1 (with 1.0 version of maven-SCM-api and maven-SCM-provider-synergy )and it doesn't work : it does not manage to extract the sources In Continuum.log, I have that 339122 [SocketListener0-0] INFO org.apache.maven.continuum.Continuum:default - Enqueuing 'VignetteOffre' (Build definition id=2). 339169 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - Initializing build 339169 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - Starting build of VignetteOffre 339435 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - Updating working dir 339435 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - Performing action check-working-directory 339435 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - Performing action checkout-project 339638 [pool-1-thread-1] INFO org.apache.maven.continuum.scm.ContinuumScm:default - Checking out project: 'VignetteOffre', id: '1' to 'I:\DONNEES\DATA\continuum-1.1\working-directory\1'. 348091 [pool-1-thread-1] INFO org.apache.maven.scm.manager.ScmManager:default - A working project already exists [Query expression must be specified.]. 354857 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - Merging SCM results 354935 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - Error updating from SCM, not building In my build result page in Continuum : Exception: Cannot checkout sources. Exception while executing SCM command. Commandeline = cmd.exe /X /C '"ccm sync -r -p "Query expression must be specified.""' STDOUT = Project reference requires name and version optionally followed by instance: 'Query expression must be specified.' STDERR = Warning: Unable to identify project. -- 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: (CONTINUUM-1416) Unable to checkout or update projects with SCM Synergy
Unable to checkout or update projects with SCM Synergy -- Key: CONTINUUM-1416 URL: http://jira.codehaus.org/browse/CONTINUUM-1416 Project: Continuum Issue Type: Bug Components: SCM Affects Versions: 1.1-beta-1 Environment: Maven 2.0.5 and Continuum-1.1-beta-1 Reporter: David Vicente Priority: Blocker Hi I used Continuum 1.0.3 with Synergy SCM provider(with maven-SCM-api-1.0-beta-4.jar and maven-SCM-provider-synergy-1.0-beta-4.jar in my \ lib) and all works fine. I have just installed continuum-1.1-beta-1 (with 1.0 version of maven-SCM-api and maven-SCM-provider-synergy )and it doesn't work : it does not manage to extract the sources In Continuum.log, I have that 339122 [SocketListener0-0] INFO org.apache.maven.continuum.Continuum:default - Enqueuing 'VignetteOffre' (Build definition id=2). 339169 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - Initializing build 339169 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - Starting build of VignetteOffre 339435 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - Updating working dir 339435 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - Performing action check-working-directory 339435 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - Performing action checkout-project 339638 [pool-1-thread-1] INFO org.apache.maven.continuum.scm.ContinuumScm:default - Checking out project: 'VignetteOffre', id: '1' to 'I:\DONNEES\DATA\continuum-1.1\working-directory\1'. 348091 [pool-1-thread-1] INFO org.apache.maven.scm.manager.ScmManager:default - A working project already exists [Query expression must be specified.]. 354857 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - Merging SCM results 354935 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - Error updating from SCM, not building In my build result page in Continuum : Exception: Cannot checkout sources. Exception while executing SCM command. Commandeline = cmd.exe /X /C '"ccm sync -r -p "Query expression must be specified.""' STDOUT = Project reference requires name and version optionally followed by instance: 'Query expression must be specified.' STDERR = Warning: Unable to identify project. -- 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: (CONTINUUM-1416) Unable to checkout or update projects with SCM Synergy
[ http://jira.codehaus.org/browse/CONTINUUM-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105994 ] Emmanuel Venisse commented on CONTINUUM-1416: - We don't have CM Synergy so we can't fix this issue. Maybe you can look at Maven SCM code if the problem is in cm synergy provider, we don't have lot of changes between 1.0-beta-4 and 1.0 final of Maven SCM and I don't think the problem is in Continuum or in Maven SCM APIs > Unable to checkout or update projects with SCM Synergy > -- > > Key: CONTINUUM-1416 > URL: http://jira.codehaus.org/browse/CONTINUUM-1416 > Project: Continuum > Issue Type: Bug > Components: SCM >Affects Versions: 1.1-beta-1 > Environment: Maven 2.0.5 and Continuum-1.1-beta-1 >Reporter: David Vicente >Priority: Blocker > > Hi > I used Continuum 1.0.3 with Synergy SCM provider(with > maven-SCM-api-1.0-beta-4.jar and maven-SCM-provider-synergy-1.0-beta-4.jar in > my \ lib) > and all works fine. > I have just installed continuum-1.1-beta-1 (with 1.0 version of maven-SCM-api > and maven-SCM-provider-synergy )and it doesn't work : it does not manage to > extract the sources > In Continuum.log, I have that > 339122 [SocketListener0-0] INFO org.apache.maven.continuum.Continuum:default > - Enqueuing 'VignetteOffre' (Build definition id=2). > 339169 [pool-1-thread-1] INFO > org.apache.maven.continuum.buildcontroller.BuildController:default - > Initializing build > 339169 [pool-1-thread-1] INFO > org.apache.maven.continuum.buildcontroller.BuildController:default - Starting > build of VignetteOffre > 339435 [pool-1-thread-1] INFO > org.apache.maven.continuum.buildcontroller.BuildController:default - Updating > working dir > 339435 [pool-1-thread-1] INFO > org.apache.maven.continuum.buildcontroller.BuildController:default - > Performing action check-working-directory > 339435 [pool-1-thread-1] INFO > org.apache.maven.continuum.buildcontroller.BuildController:default - > Performing action checkout-project > 339638 [pool-1-thread-1] INFO > org.apache.maven.continuum.scm.ContinuumScm:default - Checking out project: > 'VignetteOffre', id: '1' to > 'I:\DONNEES\DATA\continuum-1.1\working-directory\1'. > 348091 [pool-1-thread-1] INFO org.apache.maven.scm.manager.ScmManager:default > - A working project already exists [Query expression must be specified.]. > 354857 [pool-1-thread-1] INFO > org.apache.maven.continuum.buildcontroller.BuildController:default - Merging > SCM results > 354935 [pool-1-thread-1] INFO > org.apache.maven.continuum.buildcontroller.BuildController:default - Error > updating from SCM, not building > In my build result page in Continuum : > Exception: > Cannot checkout sources. > Exception while executing SCM command. > Commandeline = cmd.exe /X /C '"ccm sync -r -p "Query expression must be > specified.""' > STDOUT = Project reference requires name and version optionally followed by > instance: 'Query expression must be specified.' > STDERR = Warning: Unable to identify project. -- 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: (CONTINUUM-1416) Unable to checkout or update projects with SCM Synergy
[ http://jira.codehaus.org/browse/CONTINUUM-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105996 ] David Vicente commented on CONTINUUM-1416: -- Hi Emmanuel, if i check-out the maven-SCM-provider-synergy project from subversion and build it, how can i debug the provider when Continuum is running an update for a project ? > Unable to checkout or update projects with SCM Synergy > -- > > Key: CONTINUUM-1416 > URL: http://jira.codehaus.org/browse/CONTINUUM-1416 > Project: Continuum > Issue Type: Bug > Components: SCM >Affects Versions: 1.1-beta-1 > Environment: Maven 2.0.5 and Continuum-1.1-beta-1 >Reporter: David Vicente >Priority: Blocker > > Hi > I used Continuum 1.0.3 with Synergy SCM provider(with > maven-SCM-api-1.0-beta-4.jar and maven-SCM-provider-synergy-1.0-beta-4.jar in > my \ lib) > and all works fine. > I have just installed continuum-1.1-beta-1 (with 1.0 version of maven-SCM-api > and maven-SCM-provider-synergy )and it doesn't work : it does not manage to > extract the sources > In Continuum.log, I have that > 339122 [SocketListener0-0] INFO org.apache.maven.continuum.Continuum:default > - Enqueuing 'VignetteOffre' (Build definition id=2). > 339169 [pool-1-thread-1] INFO > org.apache.maven.continuum.buildcontroller.BuildController:default - > Initializing build > 339169 [pool-1-thread-1] INFO > org.apache.maven.continuum.buildcontroller.BuildController:default - Starting > build of VignetteOffre > 339435 [pool-1-thread-1] INFO > org.apache.maven.continuum.buildcontroller.BuildController:default - Updating > working dir > 339435 [pool-1-thread-1] INFO > org.apache.maven.continuum.buildcontroller.BuildController:default - > Performing action check-working-directory > 339435 [pool-1-thread-1] INFO > org.apache.maven.continuum.buildcontroller.BuildController:default - > Performing action checkout-project > 339638 [pool-1-thread-1] INFO > org.apache.maven.continuum.scm.ContinuumScm:default - Checking out project: > 'VignetteOffre', id: '1' to > 'I:\DONNEES\DATA\continuum-1.1\working-directory\1'. > 348091 [pool-1-thread-1] INFO org.apache.maven.scm.manager.ScmManager:default > - A working project already exists [Query expression must be specified.]. > 354857 [pool-1-thread-1] INFO > org.apache.maven.continuum.buildcontroller.BuildController:default - Merging > SCM results > 354935 [pool-1-thread-1] INFO > org.apache.maven.continuum.buildcontroller.BuildController:default - Error > updating from SCM, not building > In my build result page in Continuum : > Exception: > Cannot checkout sources. > Exception while executing SCM command. > Commandeline = cmd.exe /X /C '"ccm sync -r -p "Query expression must be > specified.""' > STDOUT = Project reference requires name and version optionally followed by > instance: 'Query expression must be specified.' > STDERR = Warning: Unable to identify project. -- 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: (CONTINUUM-1416) Unable to checkout or update projects with SCM Synergy
[ http://jira.codehaus.org/browse/CONTINUUM-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105997 ] Emmanuel Venisse commented on CONTINUUM-1416: - 1) you need to checkout continuum sources (for example from 1.1-beta-2 tag) and maven-scm-synergy provider 2) you must add debugger parameters in wrapper.conf if you run the standalone version with some lines like: wrapper.java.additional.9=your_parameter_1 wrapper.java.additional.10=your_parameter_2 3) you start continuum 4) you run the remote debug mode in your IDE > Unable to checkout or update projects with SCM Synergy > -- > > Key: CONTINUUM-1416 > URL: http://jira.codehaus.org/browse/CONTINUUM-1416 > Project: Continuum > Issue Type: Bug > Components: SCM >Affects Versions: 1.1-beta-1 > Environment: Maven 2.0.5 and Continuum-1.1-beta-1 >Reporter: David Vicente >Priority: Blocker > > Hi > I used Continuum 1.0.3 with Synergy SCM provider(with > maven-SCM-api-1.0-beta-4.jar and maven-SCM-provider-synergy-1.0-beta-4.jar in > my \ lib) > and all works fine. > I have just installed continuum-1.1-beta-1 (with 1.0 version of maven-SCM-api > and maven-SCM-provider-synergy )and it doesn't work : it does not manage to > extract the sources > In Continuum.log, I have that > 339122 [SocketListener0-0] INFO org.apache.maven.continuum.Continuum:default > - Enqueuing 'VignetteOffre' (Build definition id=2). > 339169 [pool-1-thread-1] INFO > org.apache.maven.continuum.buildcontroller.BuildController:default - > Initializing build > 339169 [pool-1-thread-1] INFO > org.apache.maven.continuum.buildcontroller.BuildController:default - Starting > build of VignetteOffre > 339435 [pool-1-thread-1] INFO > org.apache.maven.continuum.buildcontroller.BuildController:default - Updating > working dir > 339435 [pool-1-thread-1] INFO > org.apache.maven.continuum.buildcontroller.BuildController:default - > Performing action check-working-directory > 339435 [pool-1-thread-1] INFO > org.apache.maven.continuum.buildcontroller.BuildController:default - > Performing action checkout-project > 339638 [pool-1-thread-1] INFO > org.apache.maven.continuum.scm.ContinuumScm:default - Checking out project: > 'VignetteOffre', id: '1' to > 'I:\DONNEES\DATA\continuum-1.1\working-directory\1'. > 348091 [pool-1-thread-1] INFO org.apache.maven.scm.manager.ScmManager:default > - A working project already exists [Query expression must be specified.]. > 354857 [pool-1-thread-1] INFO > org.apache.maven.continuum.buildcontroller.BuildController:default - Merging > SCM results > 354935 [pool-1-thread-1] INFO > org.apache.maven.continuum.buildcontroller.BuildController:default - Error > updating from SCM, not building > In my build result page in Continuum : > Exception: > Cannot checkout sources. > Exception while executing SCM command. > Commandeline = cmd.exe /X /C '"ccm sync -r -p "Query expression must be > specified.""' > STDOUT = Project reference requires name and version optionally followed by > instance: 'Query expression must be specified.' > STDERR = Warning: Unable to identify project. -- 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: (CONTINUUM-1417) continuum group administrator role should imply user + developer too
continuum group administrator role should imply user + developer too Key: CONTINUUM-1417 URL: http://jira.codehaus.org/browse/CONTINUUM-1417 Project: Continuum Issue Type: Bug Components: Security Affects Versions: 1.1-beta-2 Reporter: Brett Porter Priority: Minor currently, these roles appear to be independent. -- 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] Closed: (CONTINUUM-1415) Javascript errors with IE
[ http://jira.codehaus.org/browse/CONTINUUM-1415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse closed CONTINUUM-1415. --- Assignee: Emmanuel Venisse Resolution: Fixed Fix Version/s: 1.1-beta-3 > Javascript errors with IE > - > > Key: CONTINUUM-1415 > URL: http://jira.codehaus.org/browse/CONTINUUM-1415 > Project: Continuum > Issue Type: Bug >Affects Versions: 1.1-beta-2 > Environment: Internet Explorer >Reporter: Wendy Smoak >Assignee: Emmanuel Venisse > Fix For: 1.1-beta-3 > > > Javascript errors with IE reported on irc.codehaus.org #continuum this > morning. > dork541: I just tried 1.1 now and everything is fine :) > jesse: ok good > wsmoak: dork541: good news :) > dork541: It does seem to have java script complaning error in IE when > viewing the page, but with firefox, no issues :) > wsmoak: uh oh. can you please report that issue? > joakim: when reporting, be sure to use the word "infernal" in the summary > line. ;-) > wsmoak: what page has the problem? (JIRA --> > http://jira.codehaus.org/browse/CONTINUUM ) > dork541: mostly the pages from > http://localhost:8080/continuum/groupSummary.action after logged in -- 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-432) Proxy Connectors are unable to download artifacts with alpha numerical version numbers
[ http://jira.codehaus.org/browse/MRM-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106010 ] Elid OR commented on MRM-432: - I have the same problem with : org.jvnet.jaxb1.maven2 maven-jaxb1-plugin 1.0-rc10 It's a very important bug that must correct if somebody have a quick hack > Proxy Connectors are unable to download artifacts with alpha numerical > version numbers > -- > > Key: MRM-432 > URL: http://jira.codehaus.org/browse/MRM-432 > Project: Archiva > Issue Type: Bug > Components: remote proxy >Affects Versions: 1.0-alpha-2 > Environment: Solaris 5.9, java 1.5.0_11, maven 2.0.7 >Reporter: Mathias Arens > Fix For: 1.0-beta-2 > > > Archiva is unable to download this artifact: > > ch.ethz.ganymed > ganymed-ssh2 > build210 > > although it is in the central repository. I can download the artifact if a > switch the central mirror of, just downloading the artifact directly over > maven. I didn't had any problems with all the other artifacts from the > central repository. > I assume that there is a problem with alpha numerical version numbers. But > it's just a guess. -- 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] Closed: (CONTINUUM-1417) continuum group administrator role should imply user + developer too
[ http://jira.codehaus.org/browse/CONTINUUM-1417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse closed CONTINUUM-1417. --- Assignee: Emmanuel Venisse Resolution: Fixed Fix Version/s: 1.1-beta-3 > continuum group administrator role should imply user + developer too > > > Key: CONTINUUM-1417 > URL: http://jira.codehaus.org/browse/CONTINUUM-1417 > Project: Continuum > Issue Type: Bug > Components: Security >Affects Versions: 1.1-beta-2 >Reporter: Brett Porter >Assignee: Emmanuel Venisse >Priority: Minor > Fix For: 1.1-beta-3 > > > currently, these roles appear to be independent. -- 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-1418) Groups Roles aren't added automatically at startup in the available roles list if the users list was deleted
[ http://jira.codehaus.org/browse/CONTINUUM-1418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-1418: Affects Version/s: 1.1-beta-2 Fix Version/s: 1.1-beta-3 > Groups Roles aren't added automatically at startup in the available roles > list if the users list was deleted > > > Key: CONTINUUM-1418 > URL: http://jira.codehaus.org/browse/CONTINUUM-1418 > Project: Continuum > Issue Type: Bug > Components: Security >Affects Versions: 1.1-beta-2 >Reporter: Emmanuel Venisse > Fix For: 1.1-beta-3 > > > As they aren't available, all groups are hidden even for the system > administrator, so projects must be readd to get old groups and project are > duplicated -- 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: (CONTINUUM-1418) Groups Roles aren't added automatically at startup in the available roles list if the users list was deleted
Groups Roles aren't added automatically at startup in the available roles list if the users list was deleted Key: CONTINUUM-1418 URL: http://jira.codehaus.org/browse/CONTINUUM-1418 Project: Continuum Issue Type: Bug Components: Security Reporter: Emmanuel Venisse Fix For: 1.1-beta-3 As they aren't available, all groups are hidden even for the system administrator, so projects must be readd to get old groups and project are duplicated -- 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-432) Proxy Connectors are unable to download artifacts with alpha numerical version numbers
[ http://jira.codehaus.org/browse/MRM-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joakim Erdfelt updated MRM-432: --- Priority: Critical (was: Major) Increasing severity. > Proxy Connectors are unable to download artifacts with alpha numerical > version numbers > -- > > Key: MRM-432 > URL: http://jira.codehaus.org/browse/MRM-432 > Project: Archiva > Issue Type: Bug > Components: remote proxy >Affects Versions: 1.0-alpha-2 > Environment: Solaris 5.9, java 1.5.0_11, maven 2.0.7 >Reporter: Mathias Arens >Assignee: Joakim Erdfelt >Priority: Critical > Fix For: 1.0-beta-2 > > > Archiva is unable to download this artifact: > > ch.ethz.ganymed > ganymed-ssh2 > build210 > > although it is in the central repository. I can download the artifact if a > switch the central mirror of, just downloading the artifact directly over > maven. I didn't had any problems with all the other artifacts from the > central repository. > I assume that there is a problem with alpha numerical version numbers. But > it's just a guess. -- 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-432) Proxy Connectors are unable to download artifacts with alpha numerical version numbers
[ http://jira.codehaus.org/browse/MRM-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106015 ] Joakim Erdfelt commented on MRM-432: I have a feeling this might be a bug in the BidirectionalRepositoryLayout routines. To those of you that have commented / filed this ticket, can I be safe in assuming that you are attempting to download from a repository layout of "default"? > Proxy Connectors are unable to download artifacts with alpha numerical > version numbers > -- > > Key: MRM-432 > URL: http://jira.codehaus.org/browse/MRM-432 > Project: Archiva > Issue Type: Bug > Components: remote proxy >Affects Versions: 1.0-alpha-2 > Environment: Solaris 5.9, java 1.5.0_11, maven 2.0.7 >Reporter: Mathias Arens >Assignee: Joakim Erdfelt >Priority: Critical > Fix For: 1.0-beta-2 > > > Archiva is unable to download this artifact: > > ch.ethz.ganymed > ganymed-ssh2 > build210 > > although it is in the central repository. I can download the artifact if a > switch the central mirror of, just downloading the artifact directly over > maven. I didn't had any problems with all the other artifacts from the > central repository. > I assume that there is a problem with alpha numerical version numbers. But > it's just a guess. -- 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: (CONTINUUM-1402) Syncing with Perforce on Linux/Unix/Bash fails
[
http://jira.codehaus.org/browse/CONTINUUM-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106023
]
Jason Pringle commented on CONTINUUM-1402:
--
This may be related to CONTINUUM-1351.
I see the same error, but do see that the clients exist (check with p4
clients). If I copy/paste the command into a terminal (and escape it) it seems
to work. Also, I haven't seen any changes in the perforceSCM provider in quite
some time, so suspect something within Continuum is causing the issue (probably
something that changed between alpha-2 and beta-1).
> Syncing with Perforce on Linux/Unix/Bash fails
> --
>
> Key: CONTINUUM-1402
> URL: http://jira.codehaus.org/browse/CONTINUUM-1402
> Project: Continuum
> Issue Type: Bug
> Components: Integration - Maven 2, SCM
>Affects Versions: 1.1-beta-2
> Environment: Bash
>Reporter: Sebastian Annies
>Priority: Critical
>
> When a client is created it is named:
> E.g.{{monospaced}}
> sannies-sojus-MavenSCM-\opt\continuum-1.1-beta-3-SNAPSHOT\apps\continuum\webapp\WEB-INF\working-directory\6{{monospaced}}
> that is ok, but now comes the sync command and uses following commandline
> {{monospaced}}
> /bin/bash -c "p4 -d
> /opt/continuum-1.1-beta-3-SNAPSHOT/apps/continuum/webapp/WEB-INF/working-directory/1
>
> -cbackground-sojus-MavenSCM-\opt\continuum-1.1-beta-3-SNAPSHOT\apps\continuum\webapp\WEB-INF\working-directory\1
> sync"
> {{monospaced}}
> The Bash now removes the backslashes in the client name! The result is that
> the client is not existent and perforce returns with an error.
> I think continuum does everything allright but we need the ticket here to be
> reminded to switch to a new plexus-utils or maven-scm if it is fixed there.
> The Problem starts in 'PerforceCheckOutCommand':
> {{monospaced}}
> public static Commandline createCommandLine(
> PerforceScmProviderRepository repo, File workingDirectory,
> ScmVersion version, String
> specname )
> {
> Commandline command = PerforceScmProvider.createP4Command( repo,
> workingDirectory );
> {color:red}
> command.createArgument().setValue( "-c" + specname );
> {color}
> command.createArgument().setValue( "sync" );
> // Use a simple heuristic to determine if we should use the Force flag
> // on sync. Forcing sync is a HUGE performance hit but is required in
> // rare instances where source is somehow deleted. If the target
> // directory is completely empty, assume a force is required. If
> // not empty, we assume a previous checkout was already done and a
> normal
> // sync will suffice.
> // SCM-110
> String[] files = workingDirectory.list();
> if ( files == null || files.length == 0 )
> {
> // We need to force so checkout to an empty directory will work.
> command.createArgument().setValue( "-f" );
> }
> // Not sure what to do here. I'm unclear whether we should be
> // sync'ing each file individually to the label or just sync the
> // entire contents of the workingDir. I'm going to assume the
> // latter until the exact semantics are clearer.
> if ( version != null && StringUtils.isNotEmpty( version.getName() ) )
> {
> command.createArgument().setValue( "@" + version.getName() );
> }
> return command;
> {{monospaced}}
> The {{monospaced}}specname {{monospaced}} contains the backslashes and is
> these are neither escaped nor quoted! Hmm ... Is that a job that the
> CommandLine should handle? I think so!
> The next thing I will do is to file an issue at plexus-utils and link the
> issues.
--
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: (CONTINUUM-1351) Acnnot checkout sources - perforce.
[ http://jira.codehaus.org/browse/CONTINUUM-1351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106024 ] Jason Pringle commented on CONTINUUM-1351: -- This may be related to CONTINUUM-1402. I see the same error, but do see that the clients exist (check with p4 clients). If I copy/paste the command into a terminal (and escape it) it seems to work. Also, I haven't seen any changes in the perforceSCM provider in quite some time, so suspect something within Continuum is causing the issue (probably something that changed between alpha-2 and beta-1). > Acnnot checkout sources - perforce. > --- > > Key: CONTINUUM-1351 > URL: http://jira.codehaus.org/browse/CONTINUUM-1351 > Project: Continuum > Issue Type: Bug >Affects Versions: 1.1-beta-1 > Environment: Linux >Reporter: Duncan McNaught > > The pom files work in 1.1-alpha-2 but after creating a new 1.1-beta-1 release > I get the following build error: > Exception: > Cannot checkout sources. > Index: 0, Size: 0 -- 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-432) Proxy Connectors are unable to download artifacts with alpha numerical version numbers
[ http://jira.codehaus.org/browse/MRM-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106027 ] Mathias Arens commented on MRM-432: --- Yes, in my case that is true. I try to download from a repository in default layout. > Proxy Connectors are unable to download artifacts with alpha numerical > version numbers > -- > > Key: MRM-432 > URL: http://jira.codehaus.org/browse/MRM-432 > Project: Archiva > Issue Type: Bug > Components: remote proxy >Affects Versions: 1.0-alpha-2 > Environment: Solaris 5.9, java 1.5.0_11, maven 2.0.7 >Reporter: Mathias Arens >Assignee: Joakim Erdfelt >Priority: Critical > Fix For: 1.0-beta-2 > > > Archiva is unable to download this artifact: > > ch.ethz.ganymed > ganymed-ssh2 > build210 > > although it is in the central repository. I can download the artifact if a > switch the central mirror of, just downloading the artifact directly over > maven. I didn't had any problems with all the other artifacts from the > central repository. > I assume that there is a problem with alpha numerical version numbers. But > it's just a guess. -- 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-1391) Missing "Download as text " link
[ http://jira.codehaus.org/browse/CONTINUUM-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated CONTINUUM-1391: Assignee: Olivier Lamy Fix Version/s: 1.1-beta-3 Patch Submitted: [Yes] Attachment: CONTINUUM-1391 patch attached. > Missing "Download as text " link > > > Key: CONTINUUM-1391 > URL: http://jira.codehaus.org/browse/CONTINUUM-1391 > Project: Continuum > Issue Type: Bug > Components: Web - UI >Affects Versions: 1.1-beta-1 > Environment: xp >Reporter: Dan Tran >Assignee: Olivier Lamy > Fix For: 1.1-beta-3 > > Attachments: CONTINUUM-1391 > > > Continuum 1.0.3 provides a link to get a build log in full page which I find > it very friendly to view the log. I dont see it in 1.1 -- 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: (CONTINUUM-1419) Continuum does not accept a Linux file URL with a Bazaar repository.
Continuum does not accept a Linux file URL with a Bazaar repository. Key: CONTINUUM-1419 URL: http://jira.codehaus.org/browse/CONTINUUM-1419 Project: Continuum Issue Type: Bug Components: SCM Affects Versions: 1.0.3 Environment: Ubuntu Reporter: James Williams Continuum does not accept a Linux file URL with a Bazaar repository. If you run the exactl text it outputs in the console in another xterm, it executes. But within continuum, it always hangs on bzr check file:/// In the browser, it indicates that the URL is incorrect despite following the wiki pages precisely. -- 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: (CONTINUUM-1351) Acnnot checkout sources - perforce.
[ http://jira.codehaus.org/browse/CONTINUUM-1351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106036 ] Sebastian Annies commented on CONTINUUM-1351: - This issue is not very specific. Could you please give us more info? What SCM? Error Log? etc? by now I can't say whether it is related to CONTINUUM-1402 > Acnnot checkout sources - perforce. > --- > > Key: CONTINUUM-1351 > URL: http://jira.codehaus.org/browse/CONTINUUM-1351 > Project: Continuum > Issue Type: Bug >Affects Versions: 1.1-beta-1 > Environment: Linux >Reporter: Duncan McNaught > > The pom files work in 1.1-alpha-2 but after creating a new 1.1-beta-1 release > I get the following build error: > Exception: > Cannot checkout sources. > Index: 0, Size: 0 -- 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: (SUREFIRE-341) Surefire fails with java.lang.ClassNotFoundException: org.apache.maven.surefire.Surefire
[ http://jira.codehaus.org/browse/SUREFIRE-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106039 ] md commented on SUREFIRE-341: - maven:2.0.6 maven-surefire-plugin: 2.4-SNAPSHOT OS: windows 2k3 SP2 java: 1.5.0_12 my local repository repository was set to D:\java\maven\.m2\repository in my settings.xml I changed it to D:\java\maven\repository ( removed the .m2 folder from the path ) and everything started working. > Surefire fails with java.lang.ClassNotFoundException: > org.apache.maven.surefire.Surefire > > > Key: SUREFIRE-341 > URL: http://jira.codehaus.org/browse/SUREFIRE-341 > Project: Maven Surefire > Issue Type: Bug >Reporter: Pär Wenåker > Fix For: 2.5 > > > Surefire fails with exception: > org.apache.maven.surefire.booter.SurefireExecutionException: Unable to > instantiate and execute Surefire; nested exception is > java.lang.ClassNotFoundException: org.apache.maven.surefire.Surefire > java.lang.ClassNotFoundException: org.apache.maven.surefire.Surefire > at java.net.URLClassLoader$1.run(URLClassLoader.java:200) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:188) > at java.lang.ClassLoader.loadClass(ClassLoader.java:306) > at java.lang.ClassLoader.loadClass(ClassLoader.java:251) > at > org.apache.maven.surefire.booter.IsolatedClassLoader.loadClass(IsolatedClassLoader.java:103) > at > org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:281) > at > org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:818) > This is probably due to the maven repository being located in a director > containing a Swedish letter (C:\Documents and Settings\Pär\.m2\repository). > When I changed the location of the repository the problem disappeared -- 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: (MANTRUN-63) ant classpath resolves incorrectly if project is invoked as part of multi-project builds
[
http://jira.codehaus.org/browse/MANTRUN-63?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106040
]
Joseph Desjardins commented on MANTRUN-63:
--
We had exactly the same problem as Filippos -- mutli-module project with the
parent (A) and a child (B) both defining an antrun plugin but B's defn having
additional dependencies (ant-contrib, etc). When running mvn from A we get a
failure in B.
Workaround : Define all your dependencies that you need in the B pom in the A
pom.
> ant classpath resolves incorrectly if project is invoked as part of
> multi-project builds
>
>
> Key: MANTRUN-63
> URL: http://jira.codehaus.org/browse/MANTRUN-63
> Project: Maven 2.x Antrun Plugin
> Issue Type: Bug
>Affects Versions: 1.1
> Environment: maven-2.0.4, java 5, XP and linux
>Reporter: Binyan
>
> I have the following pom definition:
>
> maven-antrun-plugin
>
>
> package
>
>
>
> MPC: ${mpc}
> target="build-installer"/>
>
>
>
> run
>
>
>
>
>
> ant
> ant-nodeps
> 1.6.5
>
>
>
> with the output being:
> [INFO] Executing tasks
> [echo] MPC: C:\Documents and
> Settings\binyan\.m2\repository\ant\ant-nodeps\1.6.5\ant-nodeps-1.6.5.jar;C:\Documents
> and Settings\binyan\.m2\repository\ant\ant\1.6.5\ant-1.6.5.jar;C:\Documents
> and
> Settings\binyan\.m2\repository\ant\ant-launcher\1.6.5\ant-launcher-1.6.5.jar;E:\maven\lib\maven-project-2.0.4.jar;E:\maven\lib\maven-plugin-api-2.0.4.jar
> ... [ sucessful build performed] ...
> Everything works fine if I build the project standalone, however, if the
> project is part of a maven multi-project build and invoked by the top level
> project then I get the following output:
> [INFO] Executing tasks
> [echo] MPC: C:\Documents and
> Settings\binyan\.m2\repository\ant\ant\1.6.5\ant-1.6.5.jar;C:\Documents and
> Settings\binyan\.m2\repository\ant\ant-launcher\1.6.5\ant-launcher-1.6.5.jar;E:\maven\lib\maven-project-2.0.4.jar;E:\maven\lib\maven-plugin-api-2.0.4.jar
> init:
> [mkdir] Created dir:
> E:\dev\workspace-eclipse\MX\installs\target\installer-staging\mxscripts
> [mkdir] Created dir:
> E:\dev\workspace-eclipse\MX\installs\target\installer-staging\wars
> build-staging:
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Error executing ant tasks
> Embedded error: The following error occurred while executing this line:
> E:\dev\workspace-eclipse\MX\installs\build.xml:23: Could not create type
> regexpmapper due to No supported regular expression matcher found
> [INFO]
>
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Error executing ant
> tasks
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
> 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: Error executing
> ant tasks
> at
> org.apache.ma
[jira] Created: (MNG-3170) DefaultRepositoryMetadataManager caches metadata without eviction policy
DefaultRepositoryMetadataManager caches metadata without eviction policy Key: MNG-3170 URL: http://jira.codehaus.org/browse/MNG-3170 Project: Maven 2 Issue Type: Bug Components: Embedding Affects Versions: 2.1-alpha-1 Reporter: Carlos Sanchez DefaultRepositoryMetadataManager.cachedMetadata ignores changes in the local repo as the metadata is cached forever in an embedded environment -- 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: (MANTTASKS-87) Using a pom.xml for dependencies, in which the pom.xml has a parent pom.xml will cause a "Error downloading parent pom" error
Using a pom.xml for dependencies, in which the pom.xml has a parent pom.xml will cause a "Error downloading parent pom" error - Key: MANTTASKS-87 URL: http://jira.codehaus.org/browse/MANTTASKS-87 Project: Maven 2.x Ant Tasks Issue Type: Bug Components: POM Integration Affects Versions: 2.0.7 Environment: WindowsXP Ant version 1.7.0 Reporter: Jeff Campbell Priority: Blocker Using a pom.xml for dependencies, in which the pom.xml has a parent pom.xml will cause a "Error downloading parent pom" error. This WAS NOT a bug with version 2.0.6 of the maven-ant-tasks (new issue to maven-ant-tasks-2.0.7.jar and still an issue with the latest maven-ant-tasks-2.0.8-SNAPSHOT.jar (as of the writting of this bug)). Just to see if I had done something wrong with the pom.xml file I tried to run a Maven goal against the pom.xml file. I found that if I run "mvn clean" from this same directory (where the build.xml and pom.xml file is located), using Maven-2.0.7, I get a build successfull (it was able to find the parent pom.xml file... so this seems to be isolated to JUST the maven-ant-task not being able to find the parent pom.xml) Sample of the pom.xml file http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";> 4.0.0 intuit.sbconnect sbclogin 1.0.3 SBCLogin mygroup CommonPOM 1.0.2 myothergroup myartifact 1.0 Line in Ant build.xml file that causes the error: Error that occurs when this line is executed in ant: Error downloading parent pom: Missing: -- 1) mygroup:CommonPOM:pom:1.0.2 Path to dependency: 1) unspecified:unspecified:jar:0.0 2) mygroup:CommonPOM:pom:1.0.2 -- 1 required artifact is missing. for artifact: unspecified:unspecified:jar:0.0 from the specified remote repositories: central (http://repo1.maven.org/maven2) -- 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: (MDEP-107) Output the dependencies in a consistent and natural order
Output the dependencies in a consistent and natural order - Key: MDEP-107 URL: http://jira.codehaus.org/browse/MDEP-107 Project: Maven 2.x Dependency Plugin Issue Type: Improvement Affects Versions: 2.0-alpha-5 Reporter: William Ferguson Assignee: Brian Fox As of 2.0-alpha-5-SNAPSHOT 31-AUG-2007 the dependencies when output are in random order as I suspect they come straight form a Set. This makes it really difficult for a human to parse the dependencies. Ordering them using the natural artifact order before output would be a great improvement. In particular dependency:tree is very hard to read when they are not ordered. But if each level were ordered using the natural artifact ordering it would be much easier to read and to work out where the dep problems lay. [INFO] [dependency:tree] [INFO] com.yarris.consol:consol-web:war:1.0-SNAPSHOT [INFO]com.yarris:cielo:jar:1.5:compile [INFO]javax.j2ee:j2ee:jar:1.3.1:compile [INFO]commons-digester:commons-digester:jar:1.7:compile [INFO]opensymphony:sitemesh:jar:2.2.1:compile [INFO]commons-lang:commons-lang:jar:2.1:compile [INFO]com.yarris.consol:consol-ejb:ejb:1.0-SNAPSHOT:compile [INFO] org.apache.axis:axis:jar:1.4:compile [INFO] backport-util-concurrent:backport-util-concurrent:jar:3.0:compile [INFO] commons-discovery:commons-discovery:jar:0.2:compile [INFO] commons-httpclient:commons-httpclient:jar:3.0:compile [INFO] commons-codec:commons-codec:jar:1.3:compile [INFO] commons-javaflow:commons-javaflow:jar:20060411:compile [INFO] commons-pool:commons-pool:jar:1.1:compile [INFO] xerces:xercesImpl:jar:2.0.2:compile [INFO] com.yarris:hubbub-mail:jar:2.1:compile [INFO] jasperreports:jasperreports:jar:1.3.0:compile [INFO] xml-apis:xml-apis:jar:1.0.b2:compile [INFO] eclipse:jdtcore:jar:3.1.0:compile [INFO] org.apache.axis:axis-jaxrpc:jar:1.4:compile [INFO] eclipse:jdt-compiler:jar:3.1.1:compile [INFO] net.sourceforge.jexcelapi:jxl:jar:2.6.3:compile [INFO] com.yarris:kapri:jar:1.0.1:compile [INFO] org.ostermiller:ostermiller-utils:jar:1.04.00:compile [INFO] com.pd4ml:pd4ml:jar:1.2.4:compile [INFO] poi:poi-2.5.1-final:jar:20040804:compile [INFO] javax.xml.soap:saaj-api:jar:1.2:compile [INFO] com.yarris:samurai:jar:1.19:compile [INFO] com.yarris:hubbub-log4j:jar:1.8:compile [INFO] org.acegisecurity:acegi-security:jar:1.0.3:compile [INFO] org.springframework:spring-remoting:jar:1.2.8:compile [INFO]org.springframework:spring-dao:jar:1.2.8:compile [INFO] org.springframework:spring-context:jar:1.2.8:compile [INFO] org.springframework:spring-aop:jar:1.2.8:compile [INFO]org.springframework:spring-webmvc:jar:1.2.8:compile [INFO] org.springframework:spring-web:jar:1.2.8:compile [INFO] org.springframework:spring-jdbc:jar:1.2.8:compile [INFO]org.springframework:spring-beans:jar:1.2.8:compile [INFO] org.springframework:spring-core:jar:1.2.8:compile [INFO] org.springframework:spring-support:jar:1.2.8:runtime [INFO] org.apache.velocity:velocity:jar:1.5:compile [INFO] axis:axis-wsdl4j:jar:1.3:compile [INFO] org.apache.ws:wss4j:jar:1.5.0:compile [INFO] com.yarris:yarris-jms:jar:1.0:compile [INFO] commons-io:commons-io:jar:1.2:compile [INFO] opensymphony:oscache:jar:2.0.2:compile [INFO] com.yarris.consol:consol-interfaces:jar:1.1:compile [INFO] xmlbeans:xbean:jar:2.2.0:compile [INFO]struts:struts-el:jar:1.1:compile [INFO]com.yarris:sopho:jar:1.6:compile [INFO] jdom:jdom:jar:1.0:compile [INFO] log4j:log4j:jar:1.2.14:compile [INFO] velocity:velocity-dep:jar:1.4:compile [INFO]struts:struts:jar:1.1:compile [INFO] struts:struts-legacy:jar:1.1:compile [INFO] commons-validator:commons-validator:jar:1.0.2:compile [INFO] oro:oro:jar:2.0.6:compile [INFO] javax.sql:jdbc-stdext:jar:2.0:compile [INFO]com.yarris:hubbub-web:jar:1.3:compile [INFO]javax.servlet:jstl:jar:1.0.2:compile [INFO]commons-fileupload:commons-fileupload:jar:1.0:compile [INFO]jfree:jfreechart:jar:1.0.2:compile [INFO] jfree:jcommon:jar:1.0.0:compile [INFO] junit:junit:jar:3.7:compile [INFO]taglibs:standard:jar:1.0.4:compile [INFO] xalan:xalan:jar:2.6.0:compile [INFO]displaytag:displaytag:jar:1.1:compile [INFO] com.lowagie:itext:jar:2.0.0:compile [INFO] commons-beanutils:commons-beanutils:jar:1.6:compile [INFO] commons-logging:commons-logging:jar:1.0:compile -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://ji
[jira] Commented: (MEAR-60) Improve support for skinny war files
[ http://jira.codehaus.org/browse/MEAR-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106045 ] Brian Topping commented on MEAR-60: --- A new build I am working on needs the jars available to non-web resources, so a skinny war is needed. Ouch. It seems like state should be able to be stored in the WAR manifest that a skinny WAR is desired, and the EAR plugin looks at the manifest to see if it has that flag. If so, the POM in the WAR is parsed and the dependencies (with transitives) is included. Truly, the 'painful part' of this isn't getting the direct dependencies of the WAR into the ear, it's all the transitives. Suddenly, one of the best things about m2 is broken. I would code this up, but I haven't had much luck getting patches applied before they go stale, resulting in a lot of wasted effort. If someone made a commitment to apply this, I would code it with the test cases. > Improve support for skinny war files > > > Key: MEAR-60 > URL: http://jira.codehaus.org/browse/MEAR-60 > Project: Maven 2.x Ear Plugin > Issue Type: Improvement >Affects Versions: 2.3 > Environment: mvn 2.0.5 >Reporter: Marcel Schutte >Priority: Critical > > Provide a boolean configuration option for webModules to include the war's > transitive dependencies. > As described on > http://maven.apache.org/plugins/maven-war-plugin/examples/skinny-wars.html it > is very common in a J2EE environment to use so called skinny wars. Here the > war's WEB-INF/lib will not contain the dependent jars, but instead they are > packaged inside the EAR. The war references them through its > META-INF/MANIFEST.MF > This option could be used to avoid the 'painful part' mentioned in the above > web page. The war's dependencies wouldn't have to be duplicated alongside the > ear's. > I also found an old issue (MEAR-14) which has asked for the current default > behavior of not including the transitive dependencies. It suggests a property > to include specific dependencies of the war. As far as I can tell this has > never been implemented and this is also not what I am asking for. My proposal > is an all of nothing kind of option for each war module in the ear. > On a side note, for me this is the part where removal of the old maven 1 > style properties per dependency is missed the most. With them it was possible > to decide for each single dependency whether to put it in WEB-INF/lib or > reference it through the manifest classpath. But of course, then we didn't > have the transitive dependencies -- 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: (MNG-3151) Allow plugins that attach artifacts to specify deployment locations
[ http://jira.codehaus.org/browse/MNG-3151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MNG-3151: -- Fix Version/s: (was: 2.0.8) 2.0.x Not applied following objections on [EMAIL PROTECTED] list. If you need this feature, or have a similar use case that could help build a solution - please comment and vote for it. > Allow plugins that attach artifacts to specify deployment locations > --- > > Key: MNG-3151 > URL: http://jira.codehaus.org/browse/MNG-3151 > Project: Maven 2 > Issue Type: Improvement > Components: Artifacts and Repositories, General >Affects Versions: 2.0.8 >Reporter: James William Dumay > Fix For: 2.0.x > > Attachments: MNG-3151-maven-2.0.x.patch, MNG-3151-maven-2.1.x.patch > > > The following patch allows plugins to specify Distribution Management > relating to their attached artifacts. > This is useful in large Java shops where, depending on the type of artifact > (Javadoc, source, assembly, etc)m you may want to deploy these artifacts to > different repositories (eg public and private). -- 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: (MDEPLOY-62) deploy on remote repository with linux
[ http://jira.codehaus.org/browse/MDEPLOY-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kristian meier updated MDEPLOY-62: -- Attachment: settings-publickey.xml > deploy on remote repository with linux > -- > > Key: MDEPLOY-62 > URL: http://jira.codehaus.org/browse/MDEPLOY-62 > Project: Maven 2.x Deploy Plugin > Issue Type: Bug >Affects Versions: 2.2.1 > Environment: first machine > Maven version: 2.0.7 > Java version: 1.5.0_12 > OS name: "linux" version: "2.6.18.8-0.5-default" arch: "i386" > OS Distribution: opensuse10.2 > ssh server/client: OpenSSH_4.4p1, OpenSSL 0.9.8d 28 Sep 2006 > or second machine > Maven version: 2.0.6 > Java version: 1.5.0_08 > OS name: Linux 2.6.19-gentoo-r5 #5 PREEMPT Mon Jul 2 13:23:01 IST 2007 i686 > Mobile AMD Athlon(tm) XP 2600+ AuthenticAMD GNU/Linux > OS Distribution: gentoo > ssh server/client: OpenSSH_4.6p1, OpenSSL 0.9.8e 23 Feb 2007 >Reporter: kristian meier > Attachments: pom.scp.xml, pom.scpexe.xml, settings-login.xml, > settings-publickey.xml > > > after I had again and again problems deploying on remote repositories on > linux and after I colleague of mine also struggled with this, I did some > testing. the tests I made on two machines and both produces the same results. > I used both scp and scpexe as well login and public key authentication. this > gives already quite a matrix. than I discovered that the behaviour is > different if the private key has a passphrase or not. so I also include these > two cases. > the whole test just deploys a pom artifact on localhost in the tmp directory. > so here are the results and some conclusions. the pom.xml and settings.xml I > used are attached. > === > openssh server default config > public-key: no passphrase, removed public-key and authorized_keys for login > tests > === > mvn deploy -f pom.scp.xml -s settings-login.xml > . . . > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Error deploying artifact: Authentication failed: Cannot connect. > Reason: Auth fail > mvn deploy -f pom.scpexe.xml -s settings-login.xml > . . . > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Error deploying artifact: Error executing command for transfer > Exit code 255 - Permission denied (publickey,keyboard-interactive). > mvn deploy -f pom.scp.xml -s settings-publickey.xml > . . . > [INFO] > > [INFO] BUILD SUCCESSFUL > [INFO] > > mvn deploy -f pom.scpexe.xml -s settings-publickey.xml > . . . > [INFO] > > [INFO] BUILD SUCCESSFUL > [INFO] > > === > openssh server with "PasswordAuthentication yes" > public-key: no passphrase, removed public-key and authorized_keys for login > tests > === > mvn deploy -f pom.scp.xml -s settings-login.xml > . . . > [INFO] > > [INFO] BUILD SUCCESSFUL > [INFO] > > mvn deploy -f pom.scpexe.xml -s settings-login.xml > . . . > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Error deploying artifact: Error executing command for transfer > Exit code 255 - Permission denied (publickey,password,keyboard-interactive). > mvn deploy -f pom.scp.xml -s settings-publickey.xml > . . . > [INFO] > > [INFO] BUILD SUCCESSFUL > [INFO] > > mvn deploy -f pom.scpexe.xml -s settings-publickey.xml > . . . > [INFO] > > [INFO] BUILD SUCCESSFUL > [INFO] > > === > openssh server with defaul
[jira] Updated: (MDEPLOY-62) deploy on remote repository with linux
[ http://jira.codehaus.org/browse/MDEPLOY-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kristian meier updated MDEPLOY-62: -- Attachment: settings-login.xml > deploy on remote repository with linux > -- > > Key: MDEPLOY-62 > URL: http://jira.codehaus.org/browse/MDEPLOY-62 > Project: Maven 2.x Deploy Plugin > Issue Type: Bug >Affects Versions: 2.2.1 > Environment: first machine > Maven version: 2.0.7 > Java version: 1.5.0_12 > OS name: "linux" version: "2.6.18.8-0.5-default" arch: "i386" > OS Distribution: opensuse10.2 > ssh server/client: OpenSSH_4.4p1, OpenSSL 0.9.8d 28 Sep 2006 > or second machine > Maven version: 2.0.6 > Java version: 1.5.0_08 > OS name: Linux 2.6.19-gentoo-r5 #5 PREEMPT Mon Jul 2 13:23:01 IST 2007 i686 > Mobile AMD Athlon(tm) XP 2600+ AuthenticAMD GNU/Linux > OS Distribution: gentoo > ssh server/client: OpenSSH_4.6p1, OpenSSL 0.9.8e 23 Feb 2007 >Reporter: kristian meier > Attachments: pom.scp.xml, pom.scpexe.xml, settings-login.xml, > settings-publickey.xml > > > after I had again and again problems deploying on remote repositories on > linux and after I colleague of mine also struggled with this, I did some > testing. the tests I made on two machines and both produces the same results. > I used both scp and scpexe as well login and public key authentication. this > gives already quite a matrix. than I discovered that the behaviour is > different if the private key has a passphrase or not. so I also include these > two cases. > the whole test just deploys a pom artifact on localhost in the tmp directory. > so here are the results and some conclusions. the pom.xml and settings.xml I > used are attached. > === > openssh server default config > public-key: no passphrase, removed public-key and authorized_keys for login > tests > === > mvn deploy -f pom.scp.xml -s settings-login.xml > . . . > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Error deploying artifact: Authentication failed: Cannot connect. > Reason: Auth fail > mvn deploy -f pom.scpexe.xml -s settings-login.xml > . . . > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Error deploying artifact: Error executing command for transfer > Exit code 255 - Permission denied (publickey,keyboard-interactive). > mvn deploy -f pom.scp.xml -s settings-publickey.xml > . . . > [INFO] > > [INFO] BUILD SUCCESSFUL > [INFO] > > mvn deploy -f pom.scpexe.xml -s settings-publickey.xml > . . . > [INFO] > > [INFO] BUILD SUCCESSFUL > [INFO] > > === > openssh server with "PasswordAuthentication yes" > public-key: no passphrase, removed public-key and authorized_keys for login > tests > === > mvn deploy -f pom.scp.xml -s settings-login.xml > . . . > [INFO] > > [INFO] BUILD SUCCESSFUL > [INFO] > > mvn deploy -f pom.scpexe.xml -s settings-login.xml > . . . > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Error deploying artifact: Error executing command for transfer > Exit code 255 - Permission denied (publickey,password,keyboard-interactive). > mvn deploy -f pom.scp.xml -s settings-publickey.xml > . . . > [INFO] > > [INFO] BUILD SUCCESSFUL > [INFO] > > mvn deploy -f pom.scpexe.xml -s settings-publickey.xml > . . . > [INFO] > > [INFO] BUILD SUCCESSFUL > [INFO] > > === > openssh server with default co
[jira] Created: (MDEPLOY-62) deploy on remote repository with linux
deploy on remote repository with linux -- Key: MDEPLOY-62 URL: http://jira.codehaus.org/browse/MDEPLOY-62 Project: Maven 2.x Deploy Plugin Issue Type: Bug Affects Versions: 2.2.1 Environment: first machine Maven version: 2.0.7 Java version: 1.5.0_12 OS name: "linux" version: "2.6.18.8-0.5-default" arch: "i386" OS Distribution: opensuse10.2 ssh server/client: OpenSSH_4.4p1, OpenSSL 0.9.8d 28 Sep 2006 or second machine Maven version: 2.0.6 Java version: 1.5.0_08 OS name: Linux 2.6.19-gentoo-r5 #5 PREEMPT Mon Jul 2 13:23:01 IST 2007 i686 Mobile AMD Athlon(tm) XP 2600+ AuthenticAMD GNU/Linux OS Distribution: gentoo ssh server/client: OpenSSH_4.6p1, OpenSSL 0.9.8e 23 Feb 2007 Reporter: kristian meier Attachments: pom.scp.xml, pom.scpexe.xml, settings-login.xml, settings-publickey.xml after I had again and again problems deploying on remote repositories on linux and after I colleague of mine also struggled with this, I did some testing. the tests I made on two machines and both produces the same results. I used both scp and scpexe as well login and public key authentication. this gives already quite a matrix. than I discovered that the behaviour is different if the private key has a passphrase or not. so I also include these two cases. the whole test just deploys a pom artifact on localhost in the tmp directory. so here are the results and some conclusions. the pom.xml and settings.xml I used are attached. === openssh server default config public-key: no passphrase, removed public-key and authorized_keys for login tests === mvn deploy -f pom.scp.xml -s settings-login.xml . . . [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error deploying artifact: Authentication failed: Cannot connect. Reason: Auth fail mvn deploy -f pom.scpexe.xml -s settings-login.xml . . . [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error deploying artifact: Error executing command for transfer Exit code 255 - Permission denied (publickey,keyboard-interactive). mvn deploy -f pom.scp.xml -s settings-publickey.xml . . . [INFO] [INFO] BUILD SUCCESSFUL [INFO] mvn deploy -f pom.scpexe.xml -s settings-publickey.xml . . . [INFO] [INFO] BUILD SUCCESSFUL [INFO] === openssh server with "PasswordAuthentication yes" public-key: no passphrase, removed public-key and authorized_keys for login tests === mvn deploy -f pom.scp.xml -s settings-login.xml . . . [INFO] [INFO] BUILD SUCCESSFUL [INFO] mvn deploy -f pom.scpexe.xml -s settings-login.xml . . . [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error deploying artifact: Error executing command for transfer Exit code 255 - Permission denied (publickey,password,keyboard-interactive). mvn deploy -f pom.scp.xml -s settings-publickey.xml . . . [INFO] [INFO] BUILD SUCCESSFUL [INFO] mvn deploy -f pom.scpexe.xml -s settings-publickey.xml . . . [INFO] [INFO] BUILD SUCCESSFUL [INFO] === openssh server with default config public-key: with passphrase, removed public-key and authorized_keys for login tests === mvn deploy -f pom.scp.xml -s settings-login.xml . . . [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error deployi
[jira] Updated: (MDEPLOY-62) deploy on remote repository with linux
[ http://jira.codehaus.org/browse/MDEPLOY-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kristian meier updated MDEPLOY-62: -- Attachment: pom.scpexe.xml > deploy on remote repository with linux > -- > > Key: MDEPLOY-62 > URL: http://jira.codehaus.org/browse/MDEPLOY-62 > Project: Maven 2.x Deploy Plugin > Issue Type: Bug >Affects Versions: 2.2.1 > Environment: first machine > Maven version: 2.0.7 > Java version: 1.5.0_12 > OS name: "linux" version: "2.6.18.8-0.5-default" arch: "i386" > OS Distribution: opensuse10.2 > ssh server/client: OpenSSH_4.4p1, OpenSSL 0.9.8d 28 Sep 2006 > or second machine > Maven version: 2.0.6 > Java version: 1.5.0_08 > OS name: Linux 2.6.19-gentoo-r5 #5 PREEMPT Mon Jul 2 13:23:01 IST 2007 i686 > Mobile AMD Athlon(tm) XP 2600+ AuthenticAMD GNU/Linux > OS Distribution: gentoo > ssh server/client: OpenSSH_4.6p1, OpenSSL 0.9.8e 23 Feb 2007 >Reporter: kristian meier > Attachments: pom.scp.xml, pom.scpexe.xml, settings-login.xml, > settings-publickey.xml > > > after I had again and again problems deploying on remote repositories on > linux and after I colleague of mine also struggled with this, I did some > testing. the tests I made on two machines and both produces the same results. > I used both scp and scpexe as well login and public key authentication. this > gives already quite a matrix. than I discovered that the behaviour is > different if the private key has a passphrase or not. so I also include these > two cases. > the whole test just deploys a pom artifact on localhost in the tmp directory. > so here are the results and some conclusions. the pom.xml and settings.xml I > used are attached. > === > openssh server default config > public-key: no passphrase, removed public-key and authorized_keys for login > tests > === > mvn deploy -f pom.scp.xml -s settings-login.xml > . . . > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Error deploying artifact: Authentication failed: Cannot connect. > Reason: Auth fail > mvn deploy -f pom.scpexe.xml -s settings-login.xml > . . . > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Error deploying artifact: Error executing command for transfer > Exit code 255 - Permission denied (publickey,keyboard-interactive). > mvn deploy -f pom.scp.xml -s settings-publickey.xml > . . . > [INFO] > > [INFO] BUILD SUCCESSFUL > [INFO] > > mvn deploy -f pom.scpexe.xml -s settings-publickey.xml > . . . > [INFO] > > [INFO] BUILD SUCCESSFUL > [INFO] > > === > openssh server with "PasswordAuthentication yes" > public-key: no passphrase, removed public-key and authorized_keys for login > tests > === > mvn deploy -f pom.scp.xml -s settings-login.xml > . . . > [INFO] > > [INFO] BUILD SUCCESSFUL > [INFO] > > mvn deploy -f pom.scpexe.xml -s settings-login.xml > . . . > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Error deploying artifact: Error executing command for transfer > Exit code 255 - Permission denied (publickey,password,keyboard-interactive). > mvn deploy -f pom.scp.xml -s settings-publickey.xml > . . . > [INFO] > > [INFO] BUILD SUCCESSFUL > [INFO] > > mvn deploy -f pom.scpexe.xml -s settings-publickey.xml > . . . > [INFO] > > [INFO] BUILD SUCCESSFUL > [INFO] > > === > openssh server with default config
[jira] Commented: (MWAR-104) handle zip dependencies in war plugin
[ http://jira.codehaus.org/browse/MWAR-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106048 ] Tuomas Kiviaho commented on MWAR-104: - Codebase has changed quite dramatically and this patch doesn't apply well anymore. > handle zip dependencies in war plugin > - > > Key: MWAR-104 > URL: http://jira.codehaus.org/browse/MWAR-104 > Project: Maven 2.x War Plugin > Issue Type: Improvement > Environment: all >Reporter: Olivier Lamy > Attachments: foobar.zip, MWAR-104 > > > As MNG-1683 has been applied, the zip artifact must be handled in the war > plugin. -- 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
