[jira] Created: (MECLIPSE-552) Autodiscovery of projects dependencies in the workspace should be deactivated by default
Autodiscovery of projects dependencies in the workspace should be deactivated by default Key: MECLIPSE-552 URL: http://jira.codehaus.org/browse/MECLIPSE-552 Project: Maven 2.x Eclipse Plugin Issue Type: Bug Components: Core : Dependencies resolution and build path (.classpath) Affects Versions: 2.6 Reporter: Stephen Duncan Jr Autodiscovery of project dependencies in the workspace doesn't work well enough to be turned on by default, and it creates surprising breakages compared to the prior behavior of the maven-eclipse-plugin. See http://www.nabble.com/maven-eclipse-plugin-2.6-project-references-td23025400.html for more details. -- 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-1884) Upload Tagsoup 1.2
Upload Tagsoup 1.2 -- Key: MAVENUPLOAD-1884 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1884 Project: maven-upload-requests Issue Type: Task Reporter: Stephen Duncan Jr I uploaded the previous version: http://jira.codehaus.org/browse/MAVENUPLOAD-1593 -- 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-1593) Upload Tagsoup 1.1.3
Upload Tagsoup 1.1.3 Key: MAVENUPLOAD-1593 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1593 Project: maven-upload-requests Issue Type: Task Reporter: Stephen Duncan Jr I uploaded the previous version: http://jira.codehaus.org/browse/MAVENUPLOAD-1127 -- 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-2934) Cannot Deploy Using Webdav due to DependencyManagement
[ http://jira.codehaus.org/browse/MNG-2934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_97379 ] Stephen Duncan Jr commented on MNG-2934: Further testing shows the problem only occurs when specifying the version in dependencyManagement; a direct dependency on the newer commons-httpclient (without dependencyManagement) does not seem to effect the wagon-webdav being loaded as an extension. > Cannot Deploy Using Webdav due to DependencyManagement > -- > > Key: MNG-2934 > URL: http://jira.codehaus.org/browse/MNG-2934 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies, Deployment >Affects Versions: 2.0.6 >Reporter: Stephen Duncan Jr > Fix For: 2.0.7 > > Attachments: pom.xml > > > The webdav wagon requires commons-httpclient-2.0.2.jar. If I have a > dependencyManagement section that specifies commons-httpclient 3.0.1, then > deployment fails. > The resulting output is: > [EMAIL PROTECTED] webdavtest]$ mvn deploy > [INFO] Scanning for projects... > [INFO] artifact org.apache.maven.wagon:wagon-webdav: checking for updates > from ce-releases > - > this realm = app0.child-container[extensions] > urls[0] = > file:/home/duncans/.m2/repository/de/zeigermann/xml/xml-im-exporter/1.1/xml-im-exporter-1.1.jar > urls[1] = file:/home/duncans/.m2/repository/jdom/jdom/1.0/jdom-1.0.jar > urls[2] = > file:/home/duncans/.m2/repository/org/apache/maven/wagon/wagon-webdav/1.0-beta-2/wagon-webdav-1.0-beta-2.jar > urls[3] = > file:/home/duncans/.m2/repository/commons-codec/commons-codec/1.2/commons-codec-1.2.jar > urls[4] = > file:/home/duncans/.m2/repository/slide/slide-webdavlib/2.1/slide-webdavlib-2.1.jar > urls[5] = > file:/home/duncans/.m2/repository/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar > urls[6] = > file:/home/duncans/.m2/repository/commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.jar > urls[7] = > file:/home/duncans/.m2/repository/commons-httpclient/commons-httpclient/3.0.1/commons-httpclient-3.0.1.jar > urls[8] = file:/home/duncans/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar > Number of imports: 0 > this realm = plexus.core > urls[0] = file:/home/duncans/apps/maven/lib/maven-core-2.0.6-uber.jar > Number of imports: 0 > - > [INFO] > > [INFO] Building Unnamed - test:webdavtest:pom:1.0-SNAPSHOT > [INFO]task-segment: [deploy] > [INFO] > > [INFO] [site:attach-descriptor] > [INFO] [install:install] > [INFO] Installing /home/duncans/tmp/webdavtest/pom.xml to > /home/duncans/.m2/repository/test/webdavtest/1.0-SNAPSHOT/webdavtest-1.0-SNAPSHOT.pom > [INFO] [deploy:deploy] > altDeploymentRepository = null > [INFO] Retrieving previous build number from snapshots > [WARNING] repository metadata for: 'snapshot test:webdavtest:1.0-SNAPSHOT' > could not be retrieved from repository: snapshots due to an error: > Unsupported Protocol: 'dav': Cannot find wagon which supports the requested > protocol: dav > [INFO] Repository 'snapshots' will be blacklisted > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Error deploying artifact: Unsupported Protocol: 'dav': Cannot find > wagon which supports the requested protocol: dav > Component descriptor cannot be found in the component repository: > org.apache.maven.wagon.Wagondav. > [INFO] > > [INFO] For more information, run Maven with the -e switch > [INFO] > > [INFO] Total time: 2 seconds > [INFO] Finished at: Thu Apr 05 13:49:52 EDT 2007 > [INFO] Final Memory: 6M/10M > [INFO] > -- 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-2934) Cannot Deploy Using Webdav due to DependencyManagement
[ http://jira.codehaus.org/browse/MNG-2934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_97324 ] Stephen Duncan Jr commented on MNG-2934: Jason, I don't understand the relevancy of your comment. I have a parent POM that specifies a newer version of commons-httpclient in dependencyManagement. In any project using this parent POM, the webdav wagon does not work because that newer version is used, instead of the correct dependency of the webdav wagon. Whether I have specified an actual dependency on commons-httpclient doesn't have any effect. The problem here is that some change between Maven 2.0.5 and 2.0.6 caused the extension's dependencies and/or classloader to be affected by the project's dependency resolution. Extensions should be able to load their dependencies in an isolated fashion, so that the webdav wagon can work on a project that requires the newer commons-httpclient. > Cannot Deploy Using Webdav due to DependencyManagement > -- > > Key: MNG-2934 > URL: http://jira.codehaus.org/browse/MNG-2934 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies, Deployment >Affects Versions: 2.0.6 >Reporter: Stephen Duncan Jr > Fix For: 2.0.7 > > Attachments: pom.xml > > > The webdav wagon requires commons-httpclient-2.0.2.jar. If I have a > dependencyManagement section that specifies commons-httpclient 3.0.1, then > deployment fails. > The resulting output is: > [EMAIL PROTECTED] webdavtest]$ mvn deploy > [INFO] Scanning for projects... > [INFO] artifact org.apache.maven.wagon:wagon-webdav: checking for updates > from ce-releases > - > this realm = app0.child-container[extensions] > urls[0] = > file:/home/duncans/.m2/repository/de/zeigermann/xml/xml-im-exporter/1.1/xml-im-exporter-1.1.jar > urls[1] = file:/home/duncans/.m2/repository/jdom/jdom/1.0/jdom-1.0.jar > urls[2] = > file:/home/duncans/.m2/repository/org/apache/maven/wagon/wagon-webdav/1.0-beta-2/wagon-webdav-1.0-beta-2.jar > urls[3] = > file:/home/duncans/.m2/repository/commons-codec/commons-codec/1.2/commons-codec-1.2.jar > urls[4] = > file:/home/duncans/.m2/repository/slide/slide-webdavlib/2.1/slide-webdavlib-2.1.jar > urls[5] = > file:/home/duncans/.m2/repository/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar > urls[6] = > file:/home/duncans/.m2/repository/commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.jar > urls[7] = > file:/home/duncans/.m2/repository/commons-httpclient/commons-httpclient/3.0.1/commons-httpclient-3.0.1.jar > urls[8] = file:/home/duncans/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar > Number of imports: 0 > this realm = plexus.core > urls[0] = file:/home/duncans/apps/maven/lib/maven-core-2.0.6-uber.jar > Number of imports: 0 > - > [INFO] > > [INFO] Building Unnamed - test:webdavtest:pom:1.0-SNAPSHOT > [INFO]task-segment: [deploy] > [INFO] > > [INFO] [site:attach-descriptor] > [INFO] [install:install] > [INFO] Installing /home/duncans/tmp/webdavtest/pom.xml to > /home/duncans/.m2/repository/test/webdavtest/1.0-SNAPSHOT/webdavtest-1.0-SNAPSHOT.pom > [INFO] [deploy:deploy] > altDeploymentRepository = null > [INFO] Retrieving previous build number from snapshots > [WARNING] repository metadata for: 'snapshot test:webdavtest:1.0-SNAPSHOT' > could not be retrieved from repository: snapshots due to an error: > Unsupported Protocol: 'dav': Cannot find wagon which supports the requested > protocol: dav > [INFO] Repository 'snapshots' will be blacklisted > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Error deploying artifact: Unsupported Protocol: 'dav': Cannot find > wagon which supports the requested protocol: dav > Component descriptor cannot be found in the component repository: > org.apache.maven.wagon.Wagondav. > [INFO] > > [INFO] For more information, run Maven with the -e switch > [INFO] > > [INFO] Total time: 2 seconds > [INFO] Finished at: Thu Apr 05 13:49:52 EDT 2007 > [INFO] Final Memory: 6M/10M > [INFO] > -- 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 informati
[jira] Created: (MAVENUPLOAD-1485) Upload EasyMock-PropertyUtils-1.1
Upload EasyMock-PropertyUtils-1.1 - Key: MAVENUPLOAD-1485 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1485 Project: maven-upload-requests Issue Type: Task Reporter: Stephen Duncan Jr Code hosted site: http://code.google.com/p/jrduncans/ -- 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-2934) Cannot Deploy Using Webdav due to DependencyManagement
[ http://jira.codehaus.org/browse/MNG-2934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_92263 ] Stephen Duncan Jr commented on MNG-2934: Notes: This only happens with Maven 2.0.6, not with 2.0.5. Also, is not only dependencyManagement that seems to break the extension, but also a direct dependency, or anything that causes the wrong version of commons-httpclient to be resolved. Dependency resolution within the project should no affect extension dependency resolution. > Cannot Deploy Using Webdav due to DependencyManagement > -- > > Key: MNG-2934 > URL: http://jira.codehaus.org/browse/MNG-2934 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies, Deployment >Affects Versions: 2.0.6 >Reporter: Stephen Duncan Jr > Attachments: pom.xml > > > The webdav wagon requires commons-httpclient-2.0.2.jar. If I have a > dependencyManagement section that specifies commons-httpclient 3.0.1, then > deployment fails. > The resulting output is: > [EMAIL PROTECTED] webdavtest]$ mvn deploy > [INFO] Scanning for projects... > [INFO] artifact org.apache.maven.wagon:wagon-webdav: checking for updates > from ce-releases > - > this realm = app0.child-container[extensions] > urls[0] = > file:/home/duncans/.m2/repository/de/zeigermann/xml/xml-im-exporter/1.1/xml-im-exporter-1.1.jar > urls[1] = file:/home/duncans/.m2/repository/jdom/jdom/1.0/jdom-1.0.jar > urls[2] = > file:/home/duncans/.m2/repository/org/apache/maven/wagon/wagon-webdav/1.0-beta-2/wagon-webdav-1.0-beta-2.jar > urls[3] = > file:/home/duncans/.m2/repository/commons-codec/commons-codec/1.2/commons-codec-1.2.jar > urls[4] = > file:/home/duncans/.m2/repository/slide/slide-webdavlib/2.1/slide-webdavlib-2.1.jar > urls[5] = > file:/home/duncans/.m2/repository/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar > urls[6] = > file:/home/duncans/.m2/repository/commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.jar > urls[7] = > file:/home/duncans/.m2/repository/commons-httpclient/commons-httpclient/3.0.1/commons-httpclient-3.0.1.jar > urls[8] = file:/home/duncans/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar > Number of imports: 0 > this realm = plexus.core > urls[0] = file:/home/duncans/apps/maven/lib/maven-core-2.0.6-uber.jar > Number of imports: 0 > - > [INFO] > > [INFO] Building Unnamed - test:webdavtest:pom:1.0-SNAPSHOT > [INFO]task-segment: [deploy] > [INFO] > > [INFO] [site:attach-descriptor] > [INFO] [install:install] > [INFO] Installing /home/duncans/tmp/webdavtest/pom.xml to > /home/duncans/.m2/repository/test/webdavtest/1.0-SNAPSHOT/webdavtest-1.0-SNAPSHOT.pom > [INFO] [deploy:deploy] > altDeploymentRepository = null > [INFO] Retrieving previous build number from snapshots > [WARNING] repository metadata for: 'snapshot test:webdavtest:1.0-SNAPSHOT' > could not be retrieved from repository: snapshots due to an error: > Unsupported Protocol: 'dav': Cannot find wagon which supports the requested > protocol: dav > [INFO] Repository 'snapshots' will be blacklisted > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Error deploying artifact: Unsupported Protocol: 'dav': Cannot find > wagon which supports the requested protocol: dav > Component descriptor cannot be found in the component repository: > org.apache.maven.wagon.Wagondav. > [INFO] > > [INFO] For more information, run Maven with the -e switch > [INFO] > > [INFO] Total time: 2 seconds > [INFO] Finished at: Thu Apr 05 13:49:52 EDT 2007 > [INFO] Final Memory: 6M/10M > [INFO] > -- 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-2934) Cannot Deploy Using Webdav due to DependencyManagement
Cannot Deploy Using Webdav due to DependencyManagement -- Key: MNG-2934 URL: http://jira.codehaus.org/browse/MNG-2934 Project: Maven 2 Issue Type: Bug Components: Dependencies, Deployment Affects Versions: 2.0.6 Reporter: Stephen Duncan Jr Attachments: pom.xml The webdav wagon requires commons-httpclient-2.0.2.jar. If I have a dependencyManagement section that specifies commons-httpclient 3.0.1, then deployment fails. The resulting output is: [EMAIL PROTECTED] webdavtest]$ mvn deploy [INFO] Scanning for projects... [INFO] artifact org.apache.maven.wagon:wagon-webdav: checking for updates from ce-releases - this realm = app0.child-container[extensions] urls[0] = file:/home/duncans/.m2/repository/de/zeigermann/xml/xml-im-exporter/1.1/xml-im-exporter-1.1.jar urls[1] = file:/home/duncans/.m2/repository/jdom/jdom/1.0/jdom-1.0.jar urls[2] = file:/home/duncans/.m2/repository/org/apache/maven/wagon/wagon-webdav/1.0-beta-2/wagon-webdav-1.0-beta-2.jar urls[3] = file:/home/duncans/.m2/repository/commons-codec/commons-codec/1.2/commons-codec-1.2.jar urls[4] = file:/home/duncans/.m2/repository/slide/slide-webdavlib/2.1/slide-webdavlib-2.1.jar urls[5] = file:/home/duncans/.m2/repository/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar urls[6] = file:/home/duncans/.m2/repository/commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.jar urls[7] = file:/home/duncans/.m2/repository/commons-httpclient/commons-httpclient/3.0.1/commons-httpclient-3.0.1.jar urls[8] = file:/home/duncans/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar Number of imports: 0 this realm = plexus.core urls[0] = file:/home/duncans/apps/maven/lib/maven-core-2.0.6-uber.jar Number of imports: 0 - [INFO] [INFO] Building Unnamed - test:webdavtest:pom:1.0-SNAPSHOT [INFO]task-segment: [deploy] [INFO] [INFO] [site:attach-descriptor] [INFO] [install:install] [INFO] Installing /home/duncans/tmp/webdavtest/pom.xml to /home/duncans/.m2/repository/test/webdavtest/1.0-SNAPSHOT/webdavtest-1.0-SNAPSHOT.pom [INFO] [deploy:deploy] altDeploymentRepository = null [INFO] Retrieving previous build number from snapshots [WARNING] repository metadata for: 'snapshot test:webdavtest:1.0-SNAPSHOT' could not be retrieved from repository: snapshots due to an error: Unsupported Protocol: 'dav': Cannot find wagon which supports the requested protocol: dav [INFO] Repository 'snapshots' will be blacklisted [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error deploying artifact: Unsupported Protocol: 'dav': Cannot find wagon which supports the requested protocol: dav Component descriptor cannot be found in the component repository: org.apache.maven.wagon.Wagondav. [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 2 seconds [INFO] Finished at: Thu Apr 05 13:49:52 EDT 2007 [INFO] Final Memory: 6M/10M [INFO] -- 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: (SUREFIRE-314) NullPointerException When No Test Framework Is Provided
NullPointerException When No Test Framework Is Provided --- Key: SUREFIRE-314 URL: http://jira.codehaus.org/browse/SUREFIRE-314 Project: Maven Surefire Issue Type: Bug Components: plugin Affects Versions: 2.3 Reporter: Stephen Duncan Jr When I have test sources, but neither JUnit nor TestNG defined as a dependency, instead of a warning (which I believe was previous behavior), the following error is given: [INFO] [surefire:test] [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [INFO] Trace java.lang.NullPointerException at org.apache.maven.plugin.surefire.SurefirePlugin.constructSurefireBooter(SurefirePlugin.java:594) at org.apache.maven.plugin.surefire.SurefirePlugin.execute(SurefirePlugin.java:391) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:420) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java: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:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) [INFO] -- 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-1200) Password Characters Not Supported in SCM Checkout
[ http://jira.codehaus.org/browse/CONTINUUM-1200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89131 ] Stephen Duncan Jr commented on CONTINUUM-1200: -- In the scenario being used, no password info is in the scm url. The password was provided when authenticating to download the POM from subversion. > Password Characters Not Supported in SCM Checkout > - > > Key: CONTINUUM-1200 > URL: http://jira.codehaus.org/browse/CONTINUUM-1200 > Project: Continuum > Issue Type: Bug >Reporter: Stephen Duncan Jr > > Certain characters are not supported for the password for an SCM checkout. > For instance if a ')' is the first character, then the command fails. This > is because the password is provided as a CLI parameter, and is not surrounded > by quotes. Obviously, adding quotes might break other passwords, so it would > be best to pass the password along some other way. -- 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-1200) Password Characters Not Supported in SCM Checkout
Password Characters Not Supported in SCM Checkout - Key: CONTINUUM-1200 URL: http://jira.codehaus.org/browse/CONTINUUM-1200 Project: Continuum Issue Type: Bug Reporter: Stephen Duncan Jr Certain characters are not supported for the password for an SCM checkout. For instance if a ')' is the first character, then the command fails. This is because the password is provided as a CLI parameter, and is not surrounded by quotes. Obviously, adding quotes might break other passwords, so it would be best to pass the password along some other way. -- 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-1199) Password Characters Not Supported in HTTP Authentication
Password Characters Not Supported in HTTP Authentication Key: CONTINUUM-1199 URL: http://jira.codehaus.org/browse/CONTINUUM-1199 Project: Continuum Issue Type: Bug Affects Versions: 1.1 Reporter: Stephen Duncan Jr When entering a url +username + password to download a pom to configure a project, certain password characters will cause it to fail. This is because the password is inserted into the url, so url special characters (@,?, etc) will not work. The password should be provided in response to the challenge, rather than as part of the url. -- 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: (MCHECKSTYLE-54) checkstyle:check does not see provided scope dependencies
[ http://jira.codehaus.org/browse/MCHECKSTYLE-54?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89040 ] Stephen Duncan Jr commented on MCHECKSTYLE-54: -- Indeed, I reported this against Maven 2.0.4; the version meant version 2.1 of the checkstyle plugin. > checkstyle:check does not see provided scope dependencies > - > > Key: MCHECKSTYLE-54 > URL: http://jira.codehaus.org/browse/MCHECKSTYLE-54 > Project: Maven 2.x Checkstyle Plugin > Issue Type: Bug >Affects Versions: 2.1 >Reporter: Stephen Duncan Jr >Priority: Critical > > Running checkstyle:check against a project that uses Exceptions from > dependencies that are provided scope causes checktyle errors such as the > following: > name="/share/duncans/workspace/eclipse/cdcie-webapp-feedreader/src/main/java/mil/jfcom/cie/portal/feedreader/converter/ConverterImpl.java"> > > These errors go away when the scope is changed to compile. This does not > happen for checkstyle:checkstyle; the report correct indicates no checkstyle > errors. This is preventing us from using the checkstyle plugin to enforce > checkstyle rules. -- 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-2821) Extensions for Ant target dependency stopped working in Maven 2.0.5 Candidate build
[
http://jira.codehaus.org/browse/MNG-2821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_87442
]
Stephen Duncan Jr commented on MNG-2821:
After thinking about, I realized I was looking forward to this behavior in the
case of my wagon-webdav extension, where I don't want it to pollute the
classpath. I recommend this as a wontfix, just make sure that the change in
behavior is prominently mentioned in the release notes & that any applicable
documentation is updated.
> Extensions for Ant target dependency stopped working in Maven 2.0.5 Candidate
> build
> ---
>
> Key: MNG-2821
> URL: http://jira.codehaus.org/browse/MNG-2821
> Project: Maven 2
> Issue Type: Bug
> Components: Ant tasks, Dependencies, POM
>Affects Versions: 2.0.5
>Reporter: Stephen Duncan Jr
>
> I have a POM where I configure the XFire ws-gen Ant task, and I have
> specified the xfire jar containing that Ant task as a build extension. In
> Maven 2.0.4 this worked, it does not in the latest build of Maven 2.0.5. the
> following error occurs:
> [INFO] [antrun:run {execution: default}]
> [INFO] Executing tasks
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Error executing ant tasks
> Embedded error: taskdef class org.codehaus.xfire.gen.WsGenTask cannot be found
> [INFO]
>
> The extensions section is:
>
>
> org.codehaus.xfire
> xfire-generator
> 1.2.4
>
>
> And the Antrun plugin configuration:
>
> maven-antrun-plugin
>
>
>
> generate-sources
>
> run
>
>
>
> ${project.build.directory}/generated-sources/java
>
> name="wsgen" classname="org.codehaus.xfire.gen.WsGenTask"
> classpathref="maven.test.classpath"/>
>
> ...
> I'm not sure if this was 'supposed' to work before or if I was choosing the
> wrong mechanism, but it does break one of my builds when switching from Maven
> 2.0.4 to 2.0.5
--
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-2821) Extensions for Ant target dependency stopped working in Maven 2.0.5 Candidate build
Extensions for Ant target dependency stopped working in Maven 2.0.5 Candidate
build
---
Key: MNG-2821
URL: http://jira.codehaus.org/browse/MNG-2821
Project: Maven 2
Issue Type: Bug
Components: Ant tasks, Dependencies, POM
Affects Versions: 2.0.5
Reporter: Stephen Duncan Jr
I have a POM where I configure the XFire ws-gen Ant task, and I have specified
the xfire jar containing that Ant task as a build extension. In Maven 2.0.4
this worked, it does not in the latest build of Maven 2.0.5. the following
error occurs:
[INFO] [antrun:run {execution: default}]
[INFO] Executing tasks
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error executing ant tasks
Embedded error: taskdef class org.codehaus.xfire.gen.WsGenTask cannot be found
[INFO]
The extensions section is:
org.codehaus.xfire
xfire-generator
1.2.4
And the Antrun plugin configuration:
maven-antrun-plugin
generate-sources
run
${project.build.directory}/generated-sources/java
...
I'm not sure if this was 'supposed' to work before or if I was choosing the
wrong mechanism, but it does break one of my builds when switching from Maven
2.0.4 to 2.0.5
--
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-1054) IllegalStateException stack adding pom
[ http://jira.codehaus.org/browse/CONTINUUM-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_86340 ] Stephen Duncan Jr commented on CONTINUUM-1054: -- I'm seeing the same error attempting to load from web location (Authenticated + SSL), and it is NOT working. > IllegalStateException stack adding pom > -- > > Key: CONTINUUM-1054 > URL: http://jira.codehaus.org/browse/CONTINUUM-1054 > Project: Continuum > Issue Type: Bug > Components: Web interface >Affects Versions: 1.1 >Reporter: Carlos Sanchez > Fix For: 1.1 > > > Adding a m2 pom from a web location causes this stack trace, although seems > to work fine > 2006-12-13 10:46:07,109 [SocketListener0-1] INFO DispatcherUtils >- Unable to find 'webwork.multipart.saveDir' property setting. Defaulting > to javax.servlet.context.tempdir > 2006-12-13 10:46:07,156 [SocketListener0-1] WARN MultiPartRequest >- Item is a file upload of 0 size, ignoring > 2006-12-13 10:46:07,156 [SocketListener0-1] ERROR DispatcherUtils >- Error setting character encoding to 'UTF-8' - ignoring. > java.lang.IllegalStateException: getReader() or getInputStream() called > at > org.mortbay.jetty.servlet.ServletHttpRequest.setCharacterEncoding(ServletHttpRequest.java:602) > at > javax.servlet.ServletRequestWrapper.setCharacterEncoding(ServletRequestWrapper.java:112) > at > com.opensymphony.webwork.dispatcher.DispatcherUtils.prepare(DispatcherUtils.java:392) > at > com.opensymphony.webwork.dispatcher.FilterDispatcher.doFilter(FilterDispatcher.java:160) > at > org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821) > at > com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:118) > at > com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:52) > at > org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821) > at > com.opensymphony.webwork.dispatcher.ActionContextCleanUp.doFilter(ActionContextCleanUp.java:88) > at > org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821) > at > org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:471) > at > org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:568) > at org.mortbay.http.HttpContext.handle(HttpContext.java:1530) > at > org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:633) > at org.mortbay.http.HttpContext.handle(HttpContext.java:1482) > at org.mortbay.http.HttpServer.service(HttpServer.java:909) > at org.mortbay.http.HttpConnection.service(HttpConnection.java:816) > at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:982) > at org.mortbay.http.HttpConnection.handle(HttpConnection.java:833) > at > org.mortbay.http.SocketListener.handleConnection(SocketListener.java:244) > at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357) > at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534) -- 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-1227) Upload EasyMock-PropertyUtils-1.0
Upload EasyMock-PropertyUtils-1.0 - Key: MAVENUPLOAD-1227 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1227 Project: maven-upload-requests Issue Type: Task Reporter: Stephen Duncan Jr Code hosted site: http://code.google.com/p/jrduncans/ -- 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: (MECLIPSE-58) Links should not be created when current directory = target directory (eclipse.workspace=***)
[ http://jira.codehaus.org/browse/MECLIPSE-58?page=comments#action_76866 ]
Stephen Duncan Jr commented on MECLIPSE-58:
---
Based on Eclipse 3.2's support for nested projects, I no longer have interest
in the -Declipse.workspace= features. Won't fix is fine with me.
> Links should not be created when current directory = target directory
> (eclipse.workspace=***)
> -
>
> Key: MECLIPSE-58
> URL: http://jira.codehaus.org/browse/MECLIPSE-58
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Improvement
>Reporter: Stephen Duncan Jr
>
> To avoid typing the location to my eclipse workspace, and to flatten
> multi-projects, I have a property in my setting.xml that specifies
> eclipse.workspace property. However, when running eclipse:eclipse on a
> simple project that is already in the Eclipse workspace directory, I get
> links to my folders created, and the classpath uses the links instead of the
> actual directory. This behaviour also occurs when I have a multi-project in
> the eclipse workspace directory where the directory name matches the
> artifactId of the parent project, the pom.xml file is linked over the top of
> the actual file.
> The linking behavior of eclipse:eclipse when eclipse.workspace is set should
> only be turned on when the target project directory
> (${eclipse.workspace}/${project.artifactId} does not match the current
> directory. In that case, the normal eclipse:eclipse behavior should apply.
--
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: (DOXIA-47) APT - local named anchors in apt text are not created properly.
[ http://jira.codehaus.org/browse/DOXIA-47?page=comments#action_75701 ] Stephen Duncan Jr commented on DOXIA-47: Indeed. Shouldn't Maven's implementation match this implementations output as far as possible: http://www.xmlmind.com/aptconvert.html ? In that case I think b) would have been the right answer. Links should be assumed to be to local anchors (and should error out if the named anchor does not exist) unless they start with something that indicates they are an external anchor: Text beginning with http:/, https:/, ftp:/, file:/, mailto:, ../, ./ (..\ and .\ on Windows) according to the documentation. > APT - local named anchors in apt text are not created properly. > --- > > Key: DOXIA-47 > URL: http://jira.codehaus.org/browse/DOXIA-47 > Project: doxia > Issue Type: Bug >Affects Versions: 1.0-alpha-6 > Environment: osx 10.4.4, java 1.4.2_09 >Reporter: Julian Wood >Priority: Minor > Fix For: 1.0 > > Attachments: DOXIA-47-doxia-core.patch > > > Named anchors don't work in APT text. It seems that the anchor part is OK, > but the link is not. -- 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: (MSITE-181) Provide Syntax Highlighting Capability
Provide Syntax Highlighting Capability -- Key: MSITE-181 URL: http://jira.codehaus.org/browse/MSITE-181 Project: Maven 2.x Site Plugin Issue Type: New Feature Reporter: Stephen Duncan Jr Provide some mechanism for syntax highlighting of source within documentation. Use something like jhighlight: https://jhighlight.dev.java.net/ The more formats it's available from the better (APT, XDOC, FML). Note: this appears to be implemented for the muse format in this plugin: http://www.oqube.com/projects/muse-java/ -- 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: (MECLIPSE-5) When using output directory (-Declipse.workspace=), links to non-source folders and files to be created
[ http://jira.codehaus.org/browse/MECLIPSE-5?page=comments#action_74924 ] Stephen Duncan Jr commented on MECLIPSE-5: -- Wouldn't it be possible to loop through all the directories in src/main, and if they weren't linked as source folders, link them as simple folders? Or, if it's not too hard to detect an overlap, you should be able to make sure everything is linked by starting at the top, and working downwards through the tree, adding a folder or file as a link if there's not already an overlapping link created. Note: With Eclipse 3.2 and the ability to have nested projects, this issue is no longer important to me. I do not use the linked project feature. > When using output directory (-Declipse.workspace=), links to non-source > folders and files to be created > --- > > Key: MECLIPSE-5 > URL: http://jira.codehaus.org/browse/MECLIPSE-5 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug >Affects Versions: 2.0 >Reporter: Stephen Duncan Jr > > When running mvn -Declipse.workspace=/home/user/workspace, my webapp module > did not get a link created to src/main/webapp. At a minimum, well known > maven folders should be checked for and links added. -- 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-2563) Checksums For http://ibiblio.org/maven2/org/apache/maven/plugins/maven-war-plugin/maven-metadata.xml does not match
Checksums For http://ibiblio.org/maven2/org/apache/maven/plugins/maven-war-plugin/maven-metadata.xml does not match --- Key: MNG-2563 URL: http://jira.codehaus.org/browse/MNG-2563 Project: Maven 2 Issue Type: Bug Reporter: Stephen Duncan Jr The checksum for the maven-metadata file does not match the file, causing checksum errors (including Maven Archiva proxy not downloading 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
[jira] Created: (MAVENUPLOAD-1127) Upload Tagsoup 1.0.1
Upload Tagsoup 1.0.1 Key: MAVENUPLOAD-1127 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1127 Project: maven-upload-requests Issue Type: Task Reporter: Stephen Duncan Jr Notes: Tagsoup 0.9.7 was already provided: http://www.ibiblio.org/maven2/org/ccil/cowan/tagsoup/tagsoup/ Tagsoup developer requested that I provide the upload bundle: http://tech.groups.yahoo.com/group/tagsoup-friends/message/551 -- 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: (MCHECKSTYLE-54) checkstyle:check does not see provided scope dependencies
checkstyle:check does not see provided scope dependencies - Key: MCHECKSTYLE-54 URL: http://jira.codehaus.org/browse/MCHECKSTYLE-54 Project: Maven 2.x Checkstyle Plugin Issue Type: Bug Affects Versions: 2.1 Reporter: Stephen Duncan Jr Priority: Critical Running checkstyle:check against a project that uses Exceptions from dependencies that are provided scope causes checktyle errors such as the following: These errors go away when the scope is changed to compile. This does not happen for checkstyle:checkstyle; the report correct indicates no checkstyle errors. This is preventing us from using the checkstyle plugin to enforce checkstyle rules. -- 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-1577) dependencyManagent does not work for transient dependencies
[ http://jira.codehaus.org/browse/MNG-1577?page=comments#action_70016 ] Stephen Duncan Jr commented on MNG-1577: Can someone change the description of this bug to say "transitive" instead of "transient"? That should make it easier to find... > dependencyManagent does not work for transient dependencies > --- > > Key: MNG-1577 > URL: http://jira.codehaus.org/browse/MNG-1577 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.0 >Reporter: Joerg Schaible > Fix For: 2.1 > > > The dependencyManagement does not work for transient dependencies. The > specified version is ignored. > Use case: > Main POM defines commons-digester-1.6 and commons-beanutils-1.7.0, A-SNAPSHOT > and B-SNAPSHOT > Project A is child of Main and depends directly on commons-beanutils (version > inherited from Main) > Project B is child of Main and depends directly on commons-digester (version > inherited from Main) > Project C is child of Main and depends directly on A & B (versions inherited > from Main) > A is compiled and tests are run using commons-beanutils-1.7.0 > B is compiled and tests are run using commons-digester-1.6 and > commons-beanutils-1.6, since digester is dependend on this > C is compiled and tests are run using commons-beanutils-1.7.0 > Integration tests of B did not verify, that B is behaving as expected in this > scenario. B might fail with 1.7.0 and it is not even recognized. > If I add beanutils also as direct dependency to B, it works fine, but then > are transitive dependency useless. It should be possible to define at least > in the dependencyManagement, that the versions of transient dependencies also > defined in the dependencyManagement have priority. > - Jörg -- 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: (MECLIPSE-94) Allow eclipse:eclipse to work on pom (and other) projects
[ http://jira.codehaus.org/browse/MECLIPSE-94?page=comments#action_69128 ] Stephen Duncan Jr commented on MECLIPSE-94: --- Well, I generally have a POM project in eclipse to use for interacting with CVS or SVN for the top-level pom project. However, I generally check-out through Eclipse also, which creates the .project file for me. So this is no longer a major concern for me. However, the original request seems to have to do with using "pom" packaging for an integration-test project. I can't really speak to that use case. > Allow eclipse:eclipse to work on pom (and other) projects > - > > Key: MECLIPSE-94 > URL: http://jira.codehaus.org/browse/MECLIPSE-94 > Project: Maven 2.x Eclipse Plugin > Type: Improvement > Versions: 2.1 > Reporter: Felipe Leme > > > I'm creating a Java EE project based on the m2book (which I was reviewing; > it's not available yet...) and one of the projects is a pom-packaging project > used for integration tests. According to Vincent, currently this project must > be a pom (in fact, I tried to set it as jar, but then the test phase would be > run anyway, which would cause the tests to fail), as it doesn't produces a > jar. But as it has java files (on the src/main/it/java directory), I tried to > call eclipse:eclipse but it fails, saying that "Not running eclipse plugin > goal for pom project". > For these scenarios, I think a propery would be enough. At first I thought > something about a 'force' or 'forceGeneration' property, would enough, which > the code change being from: > if ( "pom".equals( packaging ) && eclipseProjectDir == null ) > to: > if ( "pom".equals( packaging ) && eclipseProjectDir == null && > !forceGeneration ) > Then I realized there is other place where the pom nature is checked: > if ( "pom".equals( packaging ) && eclipseProjectDir == null && > !forceGeneration ) > So, I think a better name for the property would be 'javaProject' and the > change would be: > final boolean isJavaProjectProperty = // read property; defaults to false... > if ( "pom".equals( packaging ) && eclipseProjectDir == null && > !isJavaProjectProperty ) > isJavaProject = isJavaProjectProperty || !"ear".equals( packaging ) && > !"pom".equals( packaging ); > If nobody objects and someone is willing to apply the changes, I can provide > such patch (with the proper test cases). > -- Felipe > PS: I'm assigning it to Vincent for now, as he 'dreamed' that such features > already existed :-) -- 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: (MNG-2115) Anchors Broken on Getting Started Guide
[ http://jira.codehaus.org/browse/MNG-2115?page=all ] Stephen Duncan Jr closed MNG-2115: -- Resolution: Fixed This problem no longer appears on the site. > Anchors Broken on Getting Started Guide > --- > > Key: MNG-2115 > URL: http://jira.codehaus.org/browse/MNG-2115 > Project: Maven 2 > Type: Bug > Components: Documentation: Guides > Versions: documentation > Reporter: Stephen Duncan Jr > Priority: Minor > > > On the Maven Getting Started Guide: > http://maven.apache.org/guides/getting-started/index.html the links don't > link to the sections properly. The anchors for the section have an extra "#" > character. -- 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-2340) Incorrect dependency version downloaded
[ http://jira.codehaus.org/browse/MNG-2340?page=comments#action_66503 ]
Stephen Duncan Jr commented on MNG-2340:
It appears that while "mvn package" uses the correct dependency, the
dependencies report when running "mvn site" also uses the incorrect version
from dependencyManagement.
> Incorrect dependency version downloaded
> ---
>
> Key: MNG-2340
> URL: http://jira.codehaus.org/browse/MNG-2340
> Project: Maven 2
> Type: Bug
> Components: Embedding
> Versions: 2.0.4
> Reporter: Adrian
> Assignee: Jason van Zyl
> Priority: Critical
> Attachments: MNGECLIPSE-131.zip
>
>
> I have a parent pom with a dependency management section specifying the
> version of an artifact to use. In the child project, I override this version.
> The maven plugin ignores the overriding version and downloads the version
> specified by the parent pom.
> For example, in the parent pom
> {code}
>
> lucene
> lucene
> 1.4.3
>
> {code}
> in the project pom, inheriting the parent pom
> {code}
>
> lucene
> lucene
> 2.0
>
> {code}
> The maven eclipse plugin downloads version 1.4.3 for my 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: (MECLIPSE-107) Dependency Version Incorrectly Taken from DependencyManagement
[ http://jira.codehaus.org/browse/MECLIPSE-107?page=comments#action_66501 ] Stephen Duncan Jr commented on MECLIPSE-107: I've verified that this also affects the Netbeans plugin. And overriding the version (or scope) in dependencyManagement in the child pom fixes the problem. Assumably, just a dependencyManagement section is required to reproduce this, even in a single project. What shared component might be responsible? Can/should this issue be moved, or should I try to create a new issue for Maven overall? > Dependency Version Incorrectly Taken from DependencyManagement > -- > > Key: MECLIPSE-107 > URL: http://jira.codehaus.org/browse/MECLIPSE-107 > Project: Maven 2.x Eclipse Plugin > Type: Bug > Versions: 2.2 > Reporter: Stephen Duncan Jr > Priority: Critical > Attachments: dmtest.zip > > > The version used when generating .classpath is taken from > dependencyManagement even though the child pom sets the dependency version, > which should override what is in dependencyManagement. This is a regression > from the correct behaviour in 2.1. > The attached project demonstrates the problem. The .classpath file generated > for the "child" project should specify log4j-1.2.13, but instead specifies > 1.28. -- 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: (MEV-277) More Spring Dependencies Should be Optional
[ http://jira.codehaus.org/browse/MEV-277?page=all ] Stephen Duncan Jr closed MEV-277: - Resolution: Fixed Fixed in 1.2.7 poms. > More Spring Dependencies Should be Optional > --- > > Key: MEV-277 > URL: http://jira.codehaus.org/browse/MEV-277 > Project: Maven Evangelism > Type: Improvement > Components: Dependencies > Reporter: Stephen Duncan Jr > Assignee: Carlos Sanchez > > > I appreciate all the work that has been done on getting Springs dependencies > optional. However, I still have a global parent POM defining > dependencyManagement dependencies for my spring jars that contain the > following exclusions. I may be wrong on a couple, but I think most of them > should be optional, as I've had no problems excluding them. > For spring-aop, I exclude aopalliance:aopalliance, and oro:oro > For spring-web, I exclude javax.servlet:jsp-api, javax.servlet:jstl, and > taglibs:standard > For spring-dao, I exclude javax.transaction:jta > For spring-orm, I exclude org.springframework:spring-webmvc -- 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-107) Dependency Version Incorrectly Taken from DependencyManagement
Dependency Version Incorrectly Taken from DependencyManagement -- Key: MECLIPSE-107 URL: http://jira.codehaus.org/browse/MECLIPSE-107 Project: Maven 2.x Eclipse Plugin Type: Bug Versions: 2.2 Reporter: Stephen Duncan Jr Priority: Critical Attachments: dmtest.zip The version used when generating .classpath is taken from dependencyManagement even though the child pom sets the dependency version, which should override what is in dependencyManagement. This is a regression from the correct behaviour in 2.1. The attached project demonstrates the problem. The .classpath file generated for the "child" project should specify log4j-1.2.13, but instead specifies 1.28. -- 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: (MEV-363) Spring 1.2.7 POMs Missing
[ http://jira.codehaus.org/browse/MEV-363?page=comments#action_64616 ] Stephen Duncan Jr commented on MEV-363: --- Well, I put in an issue at the c3p0 site to do the upload: http://sourceforge.net/tracker/index.php?func=detail&aid=1480831&group_id=25357&atid=383691 > Spring 1.2.7 POMs Missing > - > > Key: MEV-363 > URL: http://jira.codehaus.org/browse/MEV-363 > Project: Maven Evangelism > Type: Bug > Components: Missing POM > Reporter: Stephen Duncan Jr > Attachments: spring-poms-1.2.7.zip, spring-poms-1.2.7.zip > > > All Spring 1.2.7 jars need POMs added. POMs should be duplicates of Spring > 1.2.6 but with the following other MEV issues taken into account: > http://jira.codehaus.org/browse/MEV-316 and > http://jira.codehaus.org/browse/MEV-277 -- 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: (MEV-363) Spring 1.2.7 POMs Missing
[ http://jira.codehaus.org/browse/MEV-363?page=comments#action_64595 ] Stephen Duncan Jr commented on MEV-363: --- Note that it should be (without the the 't' in the version #): "easymock:easymock" change from "1.2_RC2_Java1.3" to "1.2_Java1.3" > Spring 1.2.7 POMs Missing > - > > Key: MEV-363 > URL: http://jira.codehaus.org/browse/MEV-363 > Project: Maven Evangelism > Type: Bug > Components: Missing POM > Reporter: Stephen Duncan Jr > Attachments: spring-poms-1.2.7.zip > > > All Spring 1.2.7 jars need POMs added. POMs should be duplicates of Spring > 1.2.6 but with the following other MEV issues taken into account: > http://jira.codehaus.org/browse/MEV-316 and > http://jira.codehaus.org/browse/MEV-277 -- 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: (MEV-363) Spring 1.2.7 POMs Missing
[ http://jira.codehaus.org/browse/MEV-363?page=comments#action_64593 ] Stephen Duncan Jr commented on MEV-363: --- Changes to make, all in spring-parent, all version changes: C3P0 0.9.0.4 is not available in the Maven repo. I'd recommend to leave it at C3P0 0.9.0.2 Carlos? "easymock:easymock" change from "1.2_RC2_Java1.3" to "1.2_Java1.3t" "ibatis:ibatis2-sqlmap" change from "2.1.5.582" to "2.1.7.597" "commons-httpclient:commons-httpclient" change from "3.0-rc4" to "3.0" "log4j:log4j" change from "1.2.9" to "1.2.13" "ojb:db-ojb" change from "1.0.3" to "1.0.4" "struts:struts" change from "1.2.7" to "1.2.8" (though 1.2.9 appears to the latest release) "velocity-tools:velocity-tools-view" change from "1.1" to "1.2" "velocity-tools:velocity-tools-generic" change from "1.1" to "1.2" > Spring 1.2.7 POMs Missing > - > > Key: MEV-363 > URL: http://jira.codehaus.org/browse/MEV-363 > Project: Maven Evangelism > Type: Bug > Components: Missing POM > Reporter: Stephen Duncan Jr > Attachments: spring-poms-1.2.7.zip > > > All Spring 1.2.7 jars need POMs added. POMs should be duplicates of Spring > 1.2.6 but with the following other MEV issues taken into account: > http://jira.codehaus.org/browse/MEV-316 and > http://jira.codehaus.org/browse/MEV-277 -- 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: (MEV-363) Spring 1.2.7 POMs Missing
[ http://jira.codehaus.org/browse/MEV-363?page=comments#action_64592 ] Stephen Duncan Jr commented on MEV-363: --- Jared, you still need to take into account updates to version numbers based on Carlos's link. If you tell me how to generate the md5&sha1 files, I can go through and do it, or I can tell you exactly which POMs need to change (after I search through and figure it out!), or you can figure those out too. Let me know. Thanks for your help so far! > Spring 1.2.7 POMs Missing > - > > Key: MEV-363 > URL: http://jira.codehaus.org/browse/MEV-363 > Project: Maven Evangelism > Type: Bug > Components: Missing POM > Reporter: Stephen Duncan Jr > Attachments: spring-poms-1.2.7.zip > > > All Spring 1.2.7 jars need POMs added. POMs should be duplicates of Spring > 1.2.6 but with the following other MEV issues taken into account: > http://jira.codehaus.org/browse/MEV-316 and > http://jira.codehaus.org/browse/MEV-277 -- 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: (MEV-363) Spring 1.2.7 POMs Missing
[ http://jira.codehaus.org/browse/MEV-363?page=comments#action_64099 ] Stephen Duncan Jr commented on MEV-363: --- I know it'd be advantageous to have the Spring folks manage the spring jars, etc., but considering the lack of movement on this issue, can't this be resolved without them as prior versions have? > Spring 1.2.7 POMs Missing > - > > Key: MEV-363 > URL: http://jira.codehaus.org/browse/MEV-363 > Project: Maven Evangelism > Type: Bug > Components: Missing POM > Reporter: Stephen Duncan Jr > > > All Spring 1.2.7 jars need POMs added. POMs should be duplicates of Spring > 1.2.6 but with the following other MEV issues taken into account: > http://jira.codehaus.org/browse/MEV-316 and > http://jira.codehaus.org/browse/MEV-277 -- 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-2221) Multiple Executions of Plugin at Difference Inhertiance levels causes plugin executions to run multiple times
[ http://jira.codehaus.org/browse/MNG-2221?page=comments#action_63311 ] Stephen Duncan Jr commented on MNG-2221: More details on how to run the test. cd repeat-parent-test mvn install cd ../repeat-child-test mvn package You will see 2 executions of each antrun. > Multiple Executions of Plugin at Difference Inhertiance levels causes plugin > executions to run multiple times > - > > Key: MNG-2221 > URL: http://jira.codehaus.org/browse/MNG-2221 > Project: Maven 2 > Type: Bug > Components: Inheritence and Interpolation > Versions: 2.0.4 > Reporter: Stephen Duncan Jr > Priority: Critical > Attachments: repeat-test.zip > > > Can occur in a variety of ways, but the attached test case shows a parent pom > defining an antrun-execution, and then a child specifying another execution > with a different id. Both executions run twice when running from the child. > I believe this is the same as Kenney Westerhof's comment: > http://jira.codehaus.org/browse/MNG-2054#action_62477 -- 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-2054) Multiple Inheritence causes plugin executions to run multiple times (Test Case Attached)
[ http://jira.codehaus.org/browse/MNG-2054?page=comments#action_63310 ]
Stephen Duncan Jr commented on MNG-2054:
I've filed http://jira.codehaus.org/browse/MNG-2221 which I think is the same
as Kenney's.
> Multiple Inheritence causes plugin executions to run multiple times (Test
> Case Attached)
>
>
> Key: MNG-2054
> URL: http://jira.codehaus.org/browse/MNG-2054
> Project: Maven 2
> Type: Bug
> Components: Inheritence and Interpolation
> Versions: 2.0.2
> Environment: WinXp
> Reporter: Brian Fox
> Assignee: Brett Porter
> Priority: Critical
> Fix For: 2.0.4
> Attachments: antrun2.tgz, sample-regression.zip, sample.zip
>
>
> See the attached sample. If a plugin execution is set in a parent of a
> parent, when the child is built from either aggregator, the plugin execution
> runs multiple times. In my sample, I set the sources to be generated, but
> when run, see that the sources are generated and installed 2x.
> [INFO] Building jar:
> E:\STC\sample\sample-parent2\sample-jar\target\sample-jar-SNAPSHOT-tests.jar
> [INFO] [install:install]
> [INFO] Installing
> E:\STC\sample\sample-parent2\sample-jar\target\sample-jar-SNAPSHOT.jar to
> f:\mavenRepo\sampl
> e-project\sample-jar\SNAPSHOT\sample-jar-SNAPSHOT.jar
> [INFO] Installing
> E:\STC\sample\sample-parent2\sample-jar\target\sample-jar-SNAPSHOT-sources.jar
> to f:\mavenRe
> po\sample-project\sample-jar\SNAPSHOT\sample-jar-SNAPSHOT-sources.jar
> [INFO] Installing
> E:\STC\sample\sample-parent2\sample-jar\target\sample-jar-SNAPSHOT-sources.jar
> to f:\mavenRe
> po\sample-project\sample-jar\SNAPSHOT\sample-jar-SNAPSHOT-sources.jar
> [INFO] Installing
> E:\STC\sample\sample-parent2\sample-jar\target\sample-jar-SNAPSHOT-tests.jar
> to f:\mavenRepo
> \sample-project\sample-jar\SNAPSHOT\sample-jar-SNAPSHOT-tests.jar
> [INFO]
> If run directly from the child build, the sources are only built 1x:
> [INFO] [jar:jar]
> [INFO] Building jar:
> E:\STC\sample\sample-parent2\sample-jar\target\sample-jar-SNAPSHOT.jar
> [INFO] [source:jar {execution: attach-source}]
> [INFO] Building jar:
> E:\STC\sample\sample-parent2\sample-jar\target\sample-jar-SNAPSHOT-sources.jar
> [INFO] [jar:test-jar {execution: default}]
> [INFO] Building jar:
> E:\STC\sample\sample-parent2\sample-jar\target\sample-jar-SNAPSHOT-tests.jar
> [INFO] [install:install]
> [INFO] Installing
> E:\STC\sample\sample-parent2\sample-jar\target\sample-jar-SNAPSHOT.jar to
> f:\mavenRepo\sampl
> e-project\sample-jar\SNAPSHOT\sample-jar-SNAPSHOT.jar
> [INFO] Installing
> E:\STC\sample\sample-parent2\sample-jar\target\sample-jar-SNAPSHOT-sources.jar
> to f:\mavenRe
> po\sample-project\sample-jar\SNAPSHOT\sample-jar-SNAPSHOT-sources.jar
> [INFO] Installing
> E:\STC\sample\sample-parent2\sample-jar\target\sample-jar-SNAPSHOT-tests.jar
> to f:\mavenRepo
> \sample-project\sample-jar\SNAPSHOT\sample-jar-SNAPSHOT-tests.jar
--
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-2221) Multiple Executions of Plugin at Difference Inhertiance levels causes plugin executions to run multiple times
Multiple Executions of Plugin at Difference Inhertiance levels causes plugin executions to run multiple times - Key: MNG-2221 URL: http://jira.codehaus.org/browse/MNG-2221 Project: Maven 2 Type: Bug Components: Inheritence and Interpolation Versions: 2.0.4 Reporter: Stephen Duncan Jr Priority: Critical Attachments: repeat-test.zip Can occur in a variety of ways, but the attached test case shows a parent pom defining an antrun-execution, and then a child specifying another execution with a different id. Both executions run twice when running from the child. I believe this is the same as Kenney Westerhof's comment: http://jira.codehaus.org/browse/MNG-2054#action_62477 -- 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: (MECLIPSE-94) Allow eclipse:eclipse to work on pom (and other) projects
[ http://jira.codehaus.org/browse/MECLIPSE-94?page=comments#action_62802 ] Stephen Duncan Jr commented on MECLIPSE-94: --- As http://jira.codehaus.org/browse/MECLIPSE-19 was marked as a duplicate of this, I'll flesh out some details here. 1) My request about JAR projects is apparently incorrect, and the addition of the wtpversion attribute solves the real issue which was a desire not to have WTP builders for jar projects 2) For POM projects, there are two current behaviors. a) When simply running eclipse:eclipse for a POM project, the project is skipped. I think this is incorrect behavior, and should instead create a .project file for an Eclipse "Simple Project" with no builders, etc. This is somewhat in contrast to the request here, as it sounds like Felipe wants to generate a Java Project. That could still be effectively done with specifying builders or something, but it may be that a more convenient mechanism is needed. b) when running eclipse:eclipse -Declipse.workspace=/path/to/workspace, a project for the POM packaged artifact IS created, and it IS a java project. Again, in that case, I would like it to be changed to be a Simple Project (no builders or natures). That was what my original request was about. Feel free to separate this back out into separate requests or re-open MECLIPSE-19 if this clarification indicates that they are not really duplicates... > Allow eclipse:eclipse to work on pom (and other) projects > - > > Key: MECLIPSE-94 > URL: http://jira.codehaus.org/browse/MECLIPSE-94 > Project: Maven 2.x Eclipse Plugin > Type: Improvement > Versions: 2.1 > Reporter: Felipe Leme > > > I'm creating a Java EE project based on the m2book (which I was reviewing; > it's not available yet...) and one of the projects is a pom-packaging project > used for integration tests. According to Vincent, currently this project must > be a pom (in fact, I tried to set it as jar, but then the test phase would be > run anyway, which would cause the tests to fail), as it doesn't produces a > jar. But as it has java files (on the src/main/it/java directory), I tried to > call eclipse:eclipse but it fails, saying that "Not running eclipse plugin > goal for pom project". > For these scenarios, I think a propery would be enough. At first I thought > something about a 'force' or 'forceGeneration' property, would enough, which > the code change being from: > if ( "pom".equals( packaging ) && eclipseProjectDir == null ) > to: > if ( "pom".equals( packaging ) && eclipseProjectDir == null && > !forceGeneration ) > Then I realized there is other place where the pom nature is checked: > if ( "pom".equals( packaging ) && eclipseProjectDir == null && > !forceGeneration ) > So, I think a better name for the property would be 'javaProject' and the > change would be: > final boolean isJavaProjectProperty = // read property; defaults to false... > if ( "pom".equals( packaging ) && eclipseProjectDir == null && > !isJavaProjectProperty ) > isJavaProject = isJavaProjectProperty || !"ear".equals( packaging ) && > !"pom".equals( packaging ); > If nobody objects and someone is willing to apply the changes, I can provide > such patch (with the proper test cases). > -- Felipe > PS: I'm assigning it to Vincent for now, as he 'dreamed' that such features > already existed :-) -- 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-48) mvan.plugin.classpath does not include configured dependencies
[ http://jira.codehaus.org/browse/MANTRUN-48?page=comments#action_62513 ] Stephen Duncan Jr commented on MANTRUN-48: -- I apologize. I can't reproduce this issue. Please close. > mvan.plugin.classpath does not include configured dependencies > -- > > Key: MANTRUN-48 > URL: http://jira.codehaus.org/browse/MANTRUN-48 > Project: Maven 2.x Antrun Plugin > Type: Improvement > Reporter: Stephen Duncan Jr > > > If I declare additional dependencies in inside plugin configuration in the > POM, I can't find any way to access these with the existing classpath > elements. They should be added to maven.plugin.classpath. -- 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-48) mvan.plugin.classpath does not include configured dependencies
[ http://jira.codehaus.org/browse/MANTRUN-48?page=comments#action_61937 ] Stephen Duncan Jr commented on MANTRUN-48: -- Did you try it? I guess I should work on a limited test case when I get some time, but I tested this, and they were NOT included in m.p.c. > mvan.plugin.classpath does not include configured dependencies > -- > > Key: MANTRUN-48 > URL: http://jira.codehaus.org/browse/MANTRUN-48 > Project: Maven 2.x Antrun Plugin > Type: Improvement > Reporter: Stephen Duncan Jr > > > If I declare additional dependencies in inside plugin configuration in the > POM, I can't find any way to access these with the existing classpath > elements. They should be added to maven.plugin.classpath. -- 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: (MANTRUN-48) mvan.plugin.classpath does not include configured dependencies
mvan.plugin.classpath does not include configured dependencies -- Key: MANTRUN-48 URL: http://jira.codehaus.org/browse/MANTRUN-48 Project: Maven 2.x Antrun Plugin Type: Improvement Reporter: Stephen Duncan Jr If I declare additional dependencies in inside plugin configuration in the POM, I can't find any way to access these with the existing classpath elements. They should be added to maven.plugin.classpath. -- 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: (MEV-363) Spring 1.2.7 POMs Missing
[ http://jira.codehaus.org/browse/MEV-363?page=comments#action_61748 ] Stephen Duncan Jr commented on MEV-363: --- Added http://opensource2.atlassian.com/projects/spring/browse/SPR-1810 in Spring JIRA. > Spring 1.2.7 POMs Missing > - > > Key: MEV-363 > URL: http://jira.codehaus.org/browse/MEV-363 > Project: Maven Evangelism > Type: Bug > Components: Missing POM > Reporter: Stephen Duncan Jr > > > All Spring 1.2.7 jars need POMs added. POMs should be duplicates of Spring > 1.2.6 but with the following other MEV issues taken into account: > http://jira.codehaus.org/browse/MEV-316 and > http://jira.codehaus.org/browse/MEV-277 -- 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: (MEV-363) Spring 1.2.7 POMs Missing
Spring 1.2.7 POMs Missing - Key: MEV-363 URL: http://jira.codehaus.org/browse/MEV-363 Project: Maven Evangelism Type: Bug Components: Missing POM Reporter: Stephen Duncan Jr All Spring 1.2.7 jars need POMs added. POMs should be duplicates of Spring 1.2.6 but with the following other MEV issues taken into account: http://jira.codehaus.org/browse/MEV-316 and http://jira.codehaus.org/browse/MEV-277 -- 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: (MPLUGIN-13) Provide Automated Documentation for a Plugin That Provides a Report
Provide Automated Documentation for a Plugin That Provides a Report --- Key: MPLUGIN-13 URL: http://jira.codehaus.org/browse/MPLUGIN-13 Project: Maven 2.x Plugin Plugin Type: Improvement Reporter: Stephen Duncan Jr Provide some automated, consistent indication and documentation that a plugin can be used 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] Created: (WAGONSSH-43) SFTP as used by site-deploy, causes mkdir command to be executed
SFTP as used by site-deploy, causes mkdir command to be executed Key: WAGONSSH-43 URL: http://jira.codehaus.org/browse/WAGONSSH-43 Project: wagon-ssh Type: Improvement Versions: 1.0-alpha-6 Reporter: Stephen Duncan Jr Priority: Critical I'm trying to run mvn site-deploy with an sftp:// url. The remote system provided a limited shell for my user account that allows cvs & sftp. This works for mvn deploy to deploy jars, etc., even when it needs to create a directory to copy the file up. The site plugin, however, must call a different wagon method that causes the following command to be executed: Executing command: mkdir -p /var/www/sites/cdcie-parent-core/cdcie-parent-webapp/cdcie-webapp-troubletickets/. To be able to deploy my site, I need an sftp:// url to strictly use only sftp as is done by mvn deploy. -- 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
