[jira] Created: (MAVENUPLOAD-2001) JasperReports 2.0.5 upload
JasperReports 2.0.5 upload -- Key: MAVENUPLOAD-2001 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2001 Project: maven-upload-requests Issue Type: Task Reporter: Teodor Danciu http://jasperreports.sf.net/maven/jasperreports-2.0.5-bundle.jar http://sourceforge.net/projects/jasperreports http://sourceforge.net/project/memberlist.php?group_id=36382 Open Source Reporting Engine -- 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-416) Build failures (EclipsePluginTest failures and errors)
[ http://jira.codehaus.org/browse/MECLIPSE-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=129666#action_129666 ] Richard van Nieuwenhoven commented on MECLIPSE-416: --- the requireMavenVersion also applies to the runtime, but 2.0.8 is just required for the testing during the build. As far as i know not for the runtime. We use the plugin in a lot of projects that are locked to maven 2.0.7. So please limit it only for the build time. > Build failures (EclipsePluginTest failures and errors) > -- > > Key: MECLIPSE-416 > URL: http://jira.codehaus.org/browse/MECLIPSE-416 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Environment: $ uname -a > Linux expresso2 2.6.24-12-generic #1 SMP Wed Mar 12 23:01:54 UTC 2008 i686 > GNU/Linux > $ java -version > java version "1.5.0_11" > Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03) > Java HotSpot(TM) Server VM (build 1.5.0_11-b03, mixed mode) >Reporter: Jerome Lacoste >Assignee: Arnaud Heritier > Fix For: 2.5.2 > > Attachments: MECLIPSE-416.diff, > org.apache.maven.plugin.eclipse.EclipsePluginTest.txt > > > Trunk build fails (r642941). > Results : > Failed tests: > testProject33(org.apache.maven.plugin.eclipse.EclipsePluginTest) > Tests in error: > testProject16(org.apache.maven.plugin.eclipse.EclipsePluginTest) > testProject17(org.apache.maven.plugin.eclipse.EclipsePluginTest) > testMECLIPSE_56_encoding(org.apache.maven.plugin.eclipse.EclipsePluginTest) > Tests run: 91, Failures: 1, Errors: 3, Skipped: 0 > [INFO] > > [ERROR] BUILD FAILURE > [INFO] > > [INFO] There are test failures. > $ svn info > Path: . > URL: http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-eclipse-plugin > Repository Root: http://svn.apache.org/repos/asf > Repository UUID: 13f79535-47bb-0310-9956-ffa450edef68 > Revision: 642941 > Node Kind: directory > Schedule: normal > Last Changed Author: aheritier > Last Changed Rev: 642029 > Last Changed Date: 2008-03-28 00:43:44 +0100 (Fri, 28 Mar 2008) > This probably encompass various failures. -- 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-416) Build failures (EclipsePluginTest failures and errors)
[ http://jira.codehaus.org/browse/MECLIPSE-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=129668#action_129668 ] Jerome Lacoste commented on MECLIPSE-416: - Good point. Disregard my patch then. > Build failures (EclipsePluginTest failures and errors) > -- > > Key: MECLIPSE-416 > URL: http://jira.codehaus.org/browse/MECLIPSE-416 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Environment: $ uname -a > Linux expresso2 2.6.24-12-generic #1 SMP Wed Mar 12 23:01:54 UTC 2008 i686 > GNU/Linux > $ java -version > java version "1.5.0_11" > Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03) > Java HotSpot(TM) Server VM (build 1.5.0_11-b03, mixed mode) >Reporter: Jerome Lacoste >Assignee: Arnaud Heritier > Fix For: 2.5.2 > > Attachments: MECLIPSE-416.diff, > org.apache.maven.plugin.eclipse.EclipsePluginTest.txt > > > Trunk build fails (r642941). > Results : > Failed tests: > testProject33(org.apache.maven.plugin.eclipse.EclipsePluginTest) > Tests in error: > testProject16(org.apache.maven.plugin.eclipse.EclipsePluginTest) > testProject17(org.apache.maven.plugin.eclipse.EclipsePluginTest) > testMECLIPSE_56_encoding(org.apache.maven.plugin.eclipse.EclipsePluginTest) > Tests run: 91, Failures: 1, Errors: 3, Skipped: 0 > [INFO] > > [ERROR] BUILD FAILURE > [INFO] > > [INFO] There are test failures. > $ svn info > Path: . > URL: http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-eclipse-plugin > Repository Root: http://svn.apache.org/repos/asf > Repository UUID: 13f79535-47bb-0310-9956-ffa450edef68 > Revision: 642941 > Node Kind: directory > Schedule: normal > Last Changed Author: aheritier > Last Changed Rev: 642029 > Last Changed Date: 2008-03-28 00:43:44 +0100 (Fri, 28 Mar 2008) > This probably encompass various failures. -- 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: (MEAR-75) Incorrect file name in class path (in manifest) if specifying different bundleFileName for module
[
http://jira.codehaus.org/browse/MEAR-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=129667#action_129667
]
B. Garvelink commented on MEAR-75:
--
If anything is done about {{}} and manifest class-paths, the
{{}} element should be taken into account as well.
> Incorrect file name in class path (in manifest) if specifying different
> bundleFileName for module
> -
>
> Key: MEAR-75
> URL: http://jira.codehaus.org/browse/MEAR-75
> Project: Maven 2.x Ear Plugin
> Issue Type: Bug
>Affects Versions: 2.3.1
> Environment: Windows XP SP2, Maven 2.0.7, JDK 1.5.0_12
>Reporter: Anders Hammar
>Priority: Minor
> Attachments: jbossaop-poc.zip
>
>
> The file name included in the class path in the generated Manifest.mf file is
> incorrect if a different bundle file name is defined in the configuration for
> the ear plugin. The file name used in the class path is the original file
> name, not the defined bundle file name (which is the actual file name in the
> created ear).
> In my POM I have:
> {code:title=pom.xml|borderStyle=solid}
> ...
>
>
> jbossaop-poc
> aop
> jar
>
> ...
>
>
>
>
> maven-ear-plugin
>
>
>
>
> true
>
>
>
>
>
> jbossaop-poc
>
> aop
>
> aop-${pom.version}.aop
>
> true
>
>
>
>
>
>
> {code}
> In the resulting ear file, the included artifact 'aop-1.0-SNAPSHOT.jar' has
> been renamed to 'aop-1.0-SNAPSHOT.aop'. However, in the Manifest.mf (in the
> ear) the class path incorrectly specifies:
> Class-Path: aop-1.0-SNAPSHOT.jar
> Attached is a multi-module project that should reproduce this.
--
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: (MPIR-93) MPIR ignores reports set declared in child modules
MPIR ignores reports set declared in child modules -- Key: MPIR-93 URL: http://jira.codehaus.org/browse/MPIR-93 Project: Maven 2.x Project Info Reports Plugin Issue Type: Bug Affects Versions: 2.0.1 Reporter: Michael Osipov I have declared my parent POM to produce selective reports only, see [here|http://dev.fckeditor.net/browser/FCKeditor.Java/branches/2.4/pom.xml#L114]. Then I reclared the child modules to produces less reports but they still produce the same reports as the parent pom. See [here|http://dev.fckeditor.net/browser/FCKeditor.Java/branches/2.4/fckeditor-java/pom.xml#L127] and [there|http://dev.fckeditor.net/browser/FCKeditor.Java/branches/2.4/fckeditor-java-demo/pom.xml#L105]. this is a bug to me, breaking inheritance override. You may [checkout|http://svn.fckeditor.net/FCKeditor.Java/branches/2.4/] my project and try yourself. -- 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: (WAGONFTP-7) site:deploy (deploying with FTP) Wagon protocol 'ftp' doesn't support directory copying
[ http://jira.codehaus.org/browse/WAGONFTP-7?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=129699#action_129699 ] Matthieu Leclercq commented on WAGONFTP-7: -- After more that a year, it seems that no new released has been deployed that fixes this issue. What is the procedure to obtain a working stable release ? > site:deploy (deploying with FTP) Wagon protocol 'ftp' doesn't support > directory copying > > > Key: WAGONFTP-7 > URL: http://jira.codehaus.org/browse/WAGONFTP-7 > Project: wagon-ftp > Issue Type: Improvement >Affects Versions: 1.0-alpha-4 > Environment: windows >Reporter: pinghe >Assignee: Carlos Sanchez > Fix For: 1.0 > > Attachments: putDirectory-impl.patch, putDirectory-impl.patch > > > Wagon protocol 'ftp' doesn't support directory copying -- 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: (MECLIPSE-364) incorrect dependencies with different projectNameTemplates in submodules
[ http://jira.codehaus.org/browse/MECLIPSE-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todor Todorov updated MECLIPSE-364: --- Attachment: maven-eclipse-plugin.test.patch I modified *project-34* a bit, so the *multymodule-1* has a custom prefix in its eclipse project name. Since +testProject34+ does not make any check, I moved it from +EclipsePluginTest.java+ to a new created +EclipsePluginMultimoduleTest.java+ file and modified it to check the expected files for all processed multi-modules. Hope this test helps to release the previously attached patch with version 2.5.2. > incorrect dependencies with different projectNameTemplates in submodules > - > > Key: MECLIPSE-364 > URL: http://jira.codehaus.org/browse/MECLIPSE-364 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: Core : Dependencies resolution and build path, Core : > Multi-projects >Affects Versions: 2.4 > Environment: MacOSX, mvn 2.0.6 >Reporter: Frank Stolle >Assignee: Arnaud Heritier > Fix For: 2.5.2 > > Attachments: maven-eclipse-plugin.patch, > maven-eclipse-plugin.test.patch, patch.txt > > > If you have a project with different submodules and you use different > projectNameTemplate-Settings in some modules, the resulting .project and > .classpath -Files contains wrong project-names, because the wrong > template-name will be applied. > Example: > A > +---B (with projectNameTemplate "b-[artifactId]") > +---C (with projectNameTemplate "c-[artifactId]") > And C depends on B. In C the dependency will result in project c-B and not > b-B, as suspected. > A testcase is currently not submitted, because I don't know how to check > files in sub-projects. Only the expected-directory of the main-project will > be checked. -- 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-3498) StringIndexOutOfBounds -1 during path translation while reading pom.xml
StringIndexOutOfBounds -1 during path translation while reading pom.xml
---
Key: MNG-3498
URL: http://jira.codehaus.org/browse/MNG-3498
Project: Maven 2
Issue Type: Bug
Components: Inheritance and Interpolation
Affects Versions: 2.0.9, 2.1-alpha-1
Reporter: John Casey
${basedir} expresses this. The problem is that the
DefaultPathTranslator expects there to be more than the simple basedir
expression, and chokes if it encounters that expression as the only part of the
value.
--
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: (MCHECKSTYLE-75) Checkstyle plugin doesn't work with Maven 2.1
[
http://jira.codehaus.org/browse/MCHECKSTYLE-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Massol updated MCHECKSTYLE-75:
--
Attachment: checkstyle21error.txt
Logs of executing mvn clean install -X on 2.1-SNAPSHOT.
Note that the exact same module is working fine in 2.0.8 and 2.0.9.
> Checkstyle plugin doesn't work with Maven 2.1
> -
>
> Key: MCHECKSTYLE-75
> URL: http://jira.codehaus.org/browse/MCHECKSTYLE-75
> Project: Maven 2.x Checkstyle Plugin
> Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Vincent Massol
> Attachments: checkstyle21error.txt
>
>
> Running "mvn clean install" with the following configuration fails:
> {code}
>
>
> ...
>
>
> org.apache.maven.plugins
> maven-checkstyle-plugin
>
>
> com.xpn.xwiki.platform
> xwiki-build-verifications
> 1.1
>
>
>
>
> **/Api.java,
> **/xmlrpc/ConfluenceRpcInterface,
> **/xmlrpc/Attachment.java,
> **/xmlrpc/SpaceSummary.java,
> **/ViewAction.java,
> **/ZipExplorer*.java,
> **/FileUpload*.java,
> **/PluginApi.java,
> **/content/**/*.java,
> **/XWikiMessageTool.java,
> **/XWikiListFilter.java,
> **/MyPersistentLoginManager.java
>
>
> **/RenamePageReplaceLinkHandler.java
>
>
>
>
>
> {code}
> I have the following in the top level pom:
> {code}
>
>
>
>
>
> org.apache.maven.plugins
> maven-checkstyle-plugin
>
>
> com.xpn.xwiki.platform
> xwiki-build-verifications
>
>
>
> true
> checkstyle.xml
> checkstyle.license
>
>
>
>
> check
>
>
>
>
> ...
> {code}
> The error I get:
> {noformat}
> ...
> [DEBUG] Mojo: check has config:
>
>
> **/Api.java,
> **/xmlrpc/ConfluenceRpcInterface,
> **/xmlrpc/Attachment.java,
> **/xmlrpc/SpaceSummary.java,
> **/ViewAction.java,
> **/ZipExplorer*.java,
> **/FileUpload*.java,
> **/PluginApi.java,
> **/content/**/*.java,
> **/XWikiMessageTool.java,
> **/XWikiListFilter.java,
> **/MyPersistentLoginManager.java
> **/RenamePageReplaceLinkHandler.java
> true
> checkstyle.xml
> checkstyle.license
>
> [DEBUG] In verifyVersionedPlugin for:
> org.apache.maven.plugins:maven-checkstyle-plugin
> [DEBUG] maven-checkstyle-plugin: using locally installed snapshot
> [DEBUG]
> org.apache.maven.plugins:maven-checkstyle-plugin:maven-plugin:2.2-SNAPSHOT:runtime
> (selected for runtime)
> ...
> [DEBUG] Looking up mojo
> org.apache.maven.plugins:maven-checkstyle-plugin:2.2-SNAPSHOT:check in realm
> org.apache.maven.plugins:maven-checkstyle-plugin -
> descRealmId=org.apache.maven.plugins:maven-checkstyle-plugin
> [DEBUG] Looked up - [EMAIL PROTECTED] -
> ClassRealm[org.apache.maven.plugins:maven-checkstyle-plugin, parent:
> ClassRealm[plexus.core, parent: null]]
> [DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-checkstyle-plugin:2.2-SNAPSHOT:check' -->
> [DEBUG] (f) failOnViolation = true
> [DEBUG] (f) outputFile =
> /Users/vmassol/dev/xwiki/trunks-devs/xwiki-platform-core/target/checkstyle-result.xml
> [DEBUG] (f) outputFileFormat = xml
> [DEBUG] (f) skip = false
> [DEBUG] -- end configuration --
> [INFO] [checkstyle:check]
> [INFO] Unable to perform checkstyle:check, unable to find
> checkstyle:checkstyle outputFile.
> ...
> {noformat}
> The strange thing is that if I run "mvn checkstyle:checkstyle" or "mvn
> checkstyle:check", it works fine...
> Thanks
--
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-761) Exception when trying to retrieve a Maven 1 artifact of type zip
[ http://jira.codehaus.org/browse/MRM-761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=129715#action_129715 ] Ivan POPOV commented on MRM-761: It is a maven 1 repository legacy > Exception when trying to retrieve a Maven 1 artifact of type zip > > > Key: MRM-761 > URL: http://jira.codehaus.org/browse/MRM-761 > Project: Archiva > Issue Type: Bug >Affects Versions: 1.0.1 >Reporter: Ivan POPOV >Assignee: Brett Porter > Fix For: 1.0.x > > > Through my browser, I try to access my artifact : > the url is > http://localhost:8080/archiva/repository/maven1/jdk/zips/jre-1.0.zip > and the exception is > Error 404 Not Found > The following resource does not exist: > http://localhost:8080/repository/jdk/distributions/jre-1.0.zip > org.apache.maven.archiva.repository.layout.LayoutException: Invalid path to > Artifact: mismatch on extension [zip] and layout specified type > [distributions] (which maps to extension: [distribution]) on path > [jdk/distributions/jre-1.0.zip] > at > org.apache.maven.archiva.repository.content.LegacyPathParser.toArtifactReference(LegacyPathParser.java:190) > at > org.apache.maven.archiva.repository.content.RepositoryRequest.toArtifactReference(RepositoryRequest.java:135) > at > org.apache.maven.archiva.repository.content.RepositoryRequest.toNativePath(RepositoryRequest.java:281) > at > org.apache.maven.archiva.web.repository.ProxiedDavServer.process(ProxiedDavServer.java:193) > at > org.codehaus.plexus.webdav.servlet.multiplexed.MultiplexedWebDavServlet.service(MultiplexedWebDavServlet.java:119) > at > org.apache.maven.archiva.web.repository.RepositoryServlet.service(RepositoryServlet.java:155) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) > at > org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:428) > at > org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:830) > at > com.opensymphony.webwork.dispatcher.FilterDispatcher.doFilter(FilterDispatcher.java:189) > at > org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821) > at > com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:39) > 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) > The artifact has been correctly deployed on archiva and what is strange is > that it tries to access > jdk/distributions/jre-1.0.zip instead of jdk/zips/jre-1.0.zip > If I install my artifact under le directory jdk/distributions, this don't > solve the problem and > if I try to retrieve the artifact with maven it fails too. -- 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-75) Checkstyle plugin doesn't work with Maven 2.1
[
http://jira.codehaus.org/browse/MCHECKSTYLE-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=129717#action_129717
]
Vincent Massol commented on MCHECKSTYLE-75:
---
To reproduce:
* svn co
https://svn.xwiki.org/svnroot/xwiki/xwiki-platform/core/trunk/xwiki-core
* mvn clean install
> Checkstyle plugin doesn't work with Maven 2.1
> -
>
> Key: MCHECKSTYLE-75
> URL: http://jira.codehaus.org/browse/MCHECKSTYLE-75
> Project: Maven 2.x Checkstyle Plugin
> Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Vincent Massol
> Attachments: checkstyle21error.txt
>
>
> Running "mvn clean install" with the following configuration fails:
> {code}
>
>
> ...
>
>
> org.apache.maven.plugins
> maven-checkstyle-plugin
>
>
> com.xpn.xwiki.platform
> xwiki-build-verifications
> 1.1
>
>
>
>
> **/Api.java,
> **/xmlrpc/ConfluenceRpcInterface,
> **/xmlrpc/Attachment.java,
> **/xmlrpc/SpaceSummary.java,
> **/ViewAction.java,
> **/ZipExplorer*.java,
> **/FileUpload*.java,
> **/PluginApi.java,
> **/content/**/*.java,
> **/XWikiMessageTool.java,
> **/XWikiListFilter.java,
> **/MyPersistentLoginManager.java
>
>
> **/RenamePageReplaceLinkHandler.java
>
>
>
>
>
> {code}
> I have the following in the top level pom:
> {code}
>
>
>
>
>
> org.apache.maven.plugins
> maven-checkstyle-plugin
>
>
> com.xpn.xwiki.platform
> xwiki-build-verifications
>
>
>
> true
> checkstyle.xml
> checkstyle.license
>
>
>
>
> check
>
>
>
>
> ...
> {code}
> The error I get:
> {noformat}
> ...
> [DEBUG] Mojo: check has config:
>
>
> **/Api.java,
> **/xmlrpc/ConfluenceRpcInterface,
> **/xmlrpc/Attachment.java,
> **/xmlrpc/SpaceSummary.java,
> **/ViewAction.java,
> **/ZipExplorer*.java,
> **/FileUpload*.java,
> **/PluginApi.java,
> **/content/**/*.java,
> **/XWikiMessageTool.java,
> **/XWikiListFilter.java,
> **/MyPersistentLoginManager.java
> **/RenamePageReplaceLinkHandler.java
> true
> checkstyle.xml
> checkstyle.license
>
> [DEBUG] In verifyVersionedPlugin for:
> org.apache.maven.plugins:maven-checkstyle-plugin
> [DEBUG] maven-checkstyle-plugin: using locally installed snapshot
> [DEBUG]
> org.apache.maven.plugins:maven-checkstyle-plugin:maven-plugin:2.2-SNAPSHOT:runtime
> (selected for runtime)
> ...
> [DEBUG] Looking up mojo
> org.apache.maven.plugins:maven-checkstyle-plugin:2.2-SNAPSHOT:check in realm
> org.apache.maven.plugins:maven-checkstyle-plugin -
> descRealmId=org.apache.maven.plugins:maven-checkstyle-plugin
> [DEBUG] Looked up - [EMAIL PROTECTED] -
> ClassRealm[org.apache.maven.plugins:maven-checkstyle-plugin, parent:
> ClassRealm[plexus.core, parent: null]]
> [DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-checkstyle-plugin:2.2-SNAPSHOT:check' -->
> [DEBUG] (f) failOnViolation = true
> [DEBUG] (f) outputFile =
> /Users/vmassol/dev/xwiki/trunks-devs/xwiki-platform-core/target/checkstyle-result.xml
> [DEBUG] (f) outputFileFormat = xml
> [DEBUG] (f) skip = false
> [DEBUG] -- end configuration --
> [INFO] [checkstyle:check]
> [INFO] Unable to perform checkstyle:check, unable to find
> checkstyle:checkstyle outputFile.
> ...
> {noformat}
> The strange thing is that if I run "mvn checkstyle:checkstyle" or "mvn
> checkstyle:check", it works fine...
> Thanks
--
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: (MCHECKSTYLE-75) Checkstyle plugin doesn't work with Maven 2.1
[
http://jira.codehaus.org/browse/MCHECKSTYLE-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Massol updated MCHECKSTYLE-75:
--
Attachment: checkstyle21error.txt
Full debug logs
> Checkstyle plugin doesn't work with Maven 2.1
> -
>
> Key: MCHECKSTYLE-75
> URL: http://jira.codehaus.org/browse/MCHECKSTYLE-75
> Project: Maven 2.x Checkstyle Plugin
> Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Vincent Massol
> Attachments: checkstyle21error.txt, checkstyle21error.txt
>
>
> Running "mvn clean install" with the following configuration fails:
> {code}
>
>
> ...
>
>
> org.apache.maven.plugins
> maven-checkstyle-plugin
>
>
> com.xpn.xwiki.platform
> xwiki-build-verifications
> 1.1
>
>
>
>
> **/Api.java,
> **/xmlrpc/ConfluenceRpcInterface,
> **/xmlrpc/Attachment.java,
> **/xmlrpc/SpaceSummary.java,
> **/ViewAction.java,
> **/ZipExplorer*.java,
> **/FileUpload*.java,
> **/PluginApi.java,
> **/content/**/*.java,
> **/XWikiMessageTool.java,
> **/XWikiListFilter.java,
> **/MyPersistentLoginManager.java
>
>
> **/RenamePageReplaceLinkHandler.java
>
>
>
>
>
> {code}
> I have the following in the top level pom:
> {code}
>
>
>
>
>
> org.apache.maven.plugins
> maven-checkstyle-plugin
>
>
> com.xpn.xwiki.platform
> xwiki-build-verifications
>
>
>
> true
> checkstyle.xml
> checkstyle.license
>
>
>
>
> check
>
>
>
>
> ...
> {code}
> The error I get:
> {noformat}
> ...
> [DEBUG] Mojo: check has config:
>
>
> **/Api.java,
> **/xmlrpc/ConfluenceRpcInterface,
> **/xmlrpc/Attachment.java,
> **/xmlrpc/SpaceSummary.java,
> **/ViewAction.java,
> **/ZipExplorer*.java,
> **/FileUpload*.java,
> **/PluginApi.java,
> **/content/**/*.java,
> **/XWikiMessageTool.java,
> **/XWikiListFilter.java,
> **/MyPersistentLoginManager.java
> **/RenamePageReplaceLinkHandler.java
> true
> checkstyle.xml
> checkstyle.license
>
> [DEBUG] In verifyVersionedPlugin for:
> org.apache.maven.plugins:maven-checkstyle-plugin
> [DEBUG] maven-checkstyle-plugin: using locally installed snapshot
> [DEBUG]
> org.apache.maven.plugins:maven-checkstyle-plugin:maven-plugin:2.2-SNAPSHOT:runtime
> (selected for runtime)
> ...
> [DEBUG] Looking up mojo
> org.apache.maven.plugins:maven-checkstyle-plugin:2.2-SNAPSHOT:check in realm
> org.apache.maven.plugins:maven-checkstyle-plugin -
> descRealmId=org.apache.maven.plugins:maven-checkstyle-plugin
> [DEBUG] Looked up - [EMAIL PROTECTED] -
> ClassRealm[org.apache.maven.plugins:maven-checkstyle-plugin, parent:
> ClassRealm[plexus.core, parent: null]]
> [DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-checkstyle-plugin:2.2-SNAPSHOT:check' -->
> [DEBUG] (f) failOnViolation = true
> [DEBUG] (f) outputFile =
> /Users/vmassol/dev/xwiki/trunks-devs/xwiki-platform-core/target/checkstyle-result.xml
> [DEBUG] (f) outputFileFormat = xml
> [DEBUG] (f) skip = false
> [DEBUG] -- end configuration --
> [INFO] [checkstyle:check]
> [INFO] Unable to perform checkstyle:check, unable to find
> checkstyle:checkstyle outputFile.
> ...
> {noformat}
> The strange thing is that if I run "mvn checkstyle:checkstyle" or "mvn
> checkstyle:check", it works fine...
> Thanks
--
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] Moved: (MNG-3499) Checkstyle plugin doesn't work with Maven 2.1
[
http://jira.codehaus.org/browse/MNG-3499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Casey moved MCHECKSTYLE-75 to MNG-3499:
Affects Version/s: (was: 2.1)
2.1-alpha-1
Complexity: Expert
Key: MNG-3499 (was: MCHECKSTYLE-75)
Project: Maven 2 (was: Maven 2.x Checkstyle Plugin)
> Checkstyle plugin doesn't work with Maven 2.1
> -
>
> Key: MNG-3499
> URL: http://jira.codehaus.org/browse/MNG-3499
> Project: Maven 2
> Issue Type: Bug
>Affects Versions: 2.1-alpha-1
>Reporter: Vincent Massol
> Attachments: checkstyle21error.txt, checkstyle21error.txt
>
>
> Running "mvn clean install" with the following configuration fails:
> {code}
>
>
> ...
>
>
> org.apache.maven.plugins
> maven-checkstyle-plugin
>
>
> com.xpn.xwiki.platform
> xwiki-build-verifications
> 1.1
>
>
>
>
> **/Api.java,
> **/xmlrpc/ConfluenceRpcInterface,
> **/xmlrpc/Attachment.java,
> **/xmlrpc/SpaceSummary.java,
> **/ViewAction.java,
> **/ZipExplorer*.java,
> **/FileUpload*.java,
> **/PluginApi.java,
> **/content/**/*.java,
> **/XWikiMessageTool.java,
> **/XWikiListFilter.java,
> **/MyPersistentLoginManager.java
>
>
> **/RenamePageReplaceLinkHandler.java
>
>
>
>
>
> {code}
> I have the following in the top level pom:
> {code}
>
>
>
>
>
> org.apache.maven.plugins
> maven-checkstyle-plugin
>
>
> com.xpn.xwiki.platform
> xwiki-build-verifications
>
>
>
> true
> checkstyle.xml
> checkstyle.license
>
>
>
>
> check
>
>
>
>
> ...
> {code}
> The error I get:
> {noformat}
> ...
> [DEBUG] Mojo: check has config:
>
>
> **/Api.java,
> **/xmlrpc/ConfluenceRpcInterface,
> **/xmlrpc/Attachment.java,
> **/xmlrpc/SpaceSummary.java,
> **/ViewAction.java,
> **/ZipExplorer*.java,
> **/FileUpload*.java,
> **/PluginApi.java,
> **/content/**/*.java,
> **/XWikiMessageTool.java,
> **/XWikiListFilter.java,
> **/MyPersistentLoginManager.java
> **/RenamePageReplaceLinkHandler.java
> true
> checkstyle.xml
> checkstyle.license
>
> [DEBUG] In verifyVersionedPlugin for:
> org.apache.maven.plugins:maven-checkstyle-plugin
> [DEBUG] maven-checkstyle-plugin: using locally installed snapshot
> [DEBUG]
> org.apache.maven.plugins:maven-checkstyle-plugin:maven-plugin:2.2-SNAPSHOT:runtime
> (selected for runtime)
> ...
> [DEBUG] Looking up mojo
> org.apache.maven.plugins:maven-checkstyle-plugin:2.2-SNAPSHOT:check in realm
> org.apache.maven.plugins:maven-checkstyle-plugin -
> descRealmId=org.apache.maven.plugins:maven-checkstyle-plugin
> [DEBUG] Looked up - [EMAIL PROTECTED] -
> ClassRealm[org.apache.maven.plugins:maven-checkstyle-plugin, parent:
> ClassRealm[plexus.core, parent: null]]
> [DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-checkstyle-plugin:2.2-SNAPSHOT:check' -->
> [DEBUG] (f) failOnViolation = true
> [DEBUG] (f) outputFile =
> /Users/vmassol/dev/xwiki/trunks-devs/xwiki-platform-core/target/checkstyle-result.xml
> [DEBUG] (f) outputFileFormat = xml
> [DEBUG] (f) skip = false
> [DEBUG] -- end configuration --
> [INFO] [checkstyle:check]
> [INFO] Unable to perform checkstyle:check, unable to find
> checkstyle:checkstyle outputFile.
> ...
> {noformat}
> The strange thing is that if I run "mvn checkstyle:checkstyle" or "mvn
> checkstyle:check", it works fine...
> Thanks
--
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-3499) Checkstyle plugin doesn't work with Maven 2.1
[
http://jira.codehaus.org/browse/MNG-3499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=129719#action_129719
]
John Casey commented on MNG-3499:
-
It appears that the DefaultBuildPlanner component isn't processing @execute
goal="checkstyle" correctly. I'll put together an integration/unit test to help
guard against this in the future.
> Checkstyle plugin doesn't work with Maven 2.1
> -
>
> Key: MNG-3499
> URL: http://jira.codehaus.org/browse/MNG-3499
> Project: Maven 2
> Issue Type: Bug
>Affects Versions: 2.1-alpha-1
>Reporter: Vincent Massol
> Attachments: checkstyle21error.txt, checkstyle21error.txt
>
>
> Running "mvn clean install" with the following configuration fails:
> {code}
>
>
> ...
>
>
> org.apache.maven.plugins
> maven-checkstyle-plugin
>
>
> com.xpn.xwiki.platform
> xwiki-build-verifications
> 1.1
>
>
>
>
> **/Api.java,
> **/xmlrpc/ConfluenceRpcInterface,
> **/xmlrpc/Attachment.java,
> **/xmlrpc/SpaceSummary.java,
> **/ViewAction.java,
> **/ZipExplorer*.java,
> **/FileUpload*.java,
> **/PluginApi.java,
> **/content/**/*.java,
> **/XWikiMessageTool.java,
> **/XWikiListFilter.java,
> **/MyPersistentLoginManager.java
>
>
> **/RenamePageReplaceLinkHandler.java
>
>
>
>
>
> {code}
> I have the following in the top level pom:
> {code}
>
>
>
>
>
> org.apache.maven.plugins
> maven-checkstyle-plugin
>
>
> com.xpn.xwiki.platform
> xwiki-build-verifications
>
>
>
> true
> checkstyle.xml
> checkstyle.license
>
>
>
>
> check
>
>
>
>
> ...
> {code}
> The error I get:
> {noformat}
> ...
> [DEBUG] Mojo: check has config:
>
>
> **/Api.java,
> **/xmlrpc/ConfluenceRpcInterface,
> **/xmlrpc/Attachment.java,
> **/xmlrpc/SpaceSummary.java,
> **/ViewAction.java,
> **/ZipExplorer*.java,
> **/FileUpload*.java,
> **/PluginApi.java,
> **/content/**/*.java,
> **/XWikiMessageTool.java,
> **/XWikiListFilter.java,
> **/MyPersistentLoginManager.java
> **/RenamePageReplaceLinkHandler.java
> true
> checkstyle.xml
> checkstyle.license
>
> [DEBUG] In verifyVersionedPlugin for:
> org.apache.maven.plugins:maven-checkstyle-plugin
> [DEBUG] maven-checkstyle-plugin: using locally installed snapshot
> [DEBUG]
> org.apache.maven.plugins:maven-checkstyle-plugin:maven-plugin:2.2-SNAPSHOT:runtime
> (selected for runtime)
> ...
> [DEBUG] Looking up mojo
> org.apache.maven.plugins:maven-checkstyle-plugin:2.2-SNAPSHOT:check in realm
> org.apache.maven.plugins:maven-checkstyle-plugin -
> descRealmId=org.apache.maven.plugins:maven-checkstyle-plugin
> [DEBUG] Looked up - [EMAIL PROTECTED] -
> ClassRealm[org.apache.maven.plugins:maven-checkstyle-plugin, parent:
> ClassRealm[plexus.core, parent: null]]
> [DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-checkstyle-plugin:2.2-SNAPSHOT:check' -->
> [DEBUG] (f) failOnViolation = true
> [DEBUG] (f) outputFile =
> /Users/vmassol/dev/xwiki/trunks-devs/xwiki-platform-core/target/checkstyle-result.xml
> [DEBUG] (f) outputFileFormat = xml
> [DEBUG] (f) skip = false
> [DEBUG] -- end configuration --
> [INFO] [checkstyle:check]
> [INFO] Unable to perform checkstyle:check, unable to find
> checkstyle:checkstyle outputFile.
> ...
> {noformat}
> The strange thing is that if I run "mvn checkstyle:checkstyle" or "mvn
> checkstyle:check", it works fine...
> Thanks
--
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-3497) rar, par and ejb3 archives should not be added to classpath
[
http://jira.codehaus.org/browse/MNG-3497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=129723#action_129723
]
Herve Boutemy commented on MNG-3497:
fixed in trunk r644434
waiting for 2.0.9 release before merging change in 2.0.x branch
> rar, par and ejb3 archives should not be added to classpath
> ---
>
> Key: MNG-3497
> URL: http://jira.codehaus.org/browse/MNG-3497
> Project: Maven 2
> Issue Type: Bug
> Components: Artifacts and Repositories
>Affects Versions: 2.0.9
>Reporter: Herve Boutemy
>
> like war files, should be declared in {{components.xml}} as
> {code:xml}true
> java
> false{code}
--
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-3487) The POM model should support not only but also
[ http://jira.codehaus.org/browse/MNG-3487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=129729#action_129729 ] Eduardo Martins commented on MNG-3487: -- Please note that this feature implies that the install phase must put a POM with the properties injected in the M2 repo, otherwise the POM is broken. > The POM model should support not only but also > -- > > Key: MNG-3487 > URL: http://jira.codehaus.org/browse/MNG-3487 > Project: Maven 2 > Issue Type: New Feature > Components: POM >Reporter: Eduardo Martins > > Currently there is no support for properties files in the POM, users often > need this feature and use plugins to achieve that, but plugins can't touch > elements in the POM which use a property to define some value, simply because > that is defined before any phase is done. > I recommend adding a new element, , which can have > childs. Maven will load all properties in this file (no xml, > usual format of property.name=property.value) the same way if they were > defined inside . -- 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-3499) Checkstyle plugin doesn't work with Maven 2.1
[
http://jira.codehaus.org/browse/MNG-3499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=129741#action_129741
]
John Casey commented on MNG-3499:
-
Not sure when you last build your maven 2.1 copy, but I've added a new
integration test to core-integration-testing that mocks up the @execute
goal="" behavior, and it seems to work well here.
Can you let me know how old your maven copy is, and we can go from there?
> Checkstyle plugin doesn't work with Maven 2.1
> -
>
> Key: MNG-3499
> URL: http://jira.codehaus.org/browse/MNG-3499
> Project: Maven 2
> Issue Type: Bug
>Affects Versions: 2.1-alpha-1
>Reporter: Vincent Massol
>Assignee: John Casey
> Attachments: checkstyle21error.txt, checkstyle21error.txt
>
>
> Running "mvn clean install" with the following configuration fails:
> {code}
>
>
> ...
>
>
> org.apache.maven.plugins
> maven-checkstyle-plugin
>
>
> com.xpn.xwiki.platform
> xwiki-build-verifications
> 1.1
>
>
>
>
> **/Api.java,
> **/xmlrpc/ConfluenceRpcInterface,
> **/xmlrpc/Attachment.java,
> **/xmlrpc/SpaceSummary.java,
> **/ViewAction.java,
> **/ZipExplorer*.java,
> **/FileUpload*.java,
> **/PluginApi.java,
> **/content/**/*.java,
> **/XWikiMessageTool.java,
> **/XWikiListFilter.java,
> **/MyPersistentLoginManager.java
>
>
> **/RenamePageReplaceLinkHandler.java
>
>
>
>
>
> {code}
> I have the following in the top level pom:
> {code}
>
>
>
>
>
> org.apache.maven.plugins
> maven-checkstyle-plugin
>
>
> com.xpn.xwiki.platform
> xwiki-build-verifications
>
>
>
> true
> checkstyle.xml
> checkstyle.license
>
>
>
>
> check
>
>
>
>
> ...
> {code}
> The error I get:
> {noformat}
> ...
> [DEBUG] Mojo: check has config:
>
>
> **/Api.java,
> **/xmlrpc/ConfluenceRpcInterface,
> **/xmlrpc/Attachment.java,
> **/xmlrpc/SpaceSummary.java,
> **/ViewAction.java,
> **/ZipExplorer*.java,
> **/FileUpload*.java,
> **/PluginApi.java,
> **/content/**/*.java,
> **/XWikiMessageTool.java,
> **/XWikiListFilter.java,
> **/MyPersistentLoginManager.java
> **/RenamePageReplaceLinkHandler.java
> true
> checkstyle.xml
> checkstyle.license
>
> [DEBUG] In verifyVersionedPlugin for:
> org.apache.maven.plugins:maven-checkstyle-plugin
> [DEBUG] maven-checkstyle-plugin: using locally installed snapshot
> [DEBUG]
> org.apache.maven.plugins:maven-checkstyle-plugin:maven-plugin:2.2-SNAPSHOT:runtime
> (selected for runtime)
> ...
> [DEBUG] Looking up mojo
> org.apache.maven.plugins:maven-checkstyle-plugin:2.2-SNAPSHOT:check in realm
> org.apache.maven.plugins:maven-checkstyle-plugin -
> descRealmId=org.apache.maven.plugins:maven-checkstyle-plugin
> [DEBUG] Looked up - [EMAIL PROTECTED] -
> ClassRealm[org.apache.maven.plugins:maven-checkstyle-plugin, parent:
> ClassRealm[plexus.core, parent: null]]
> [DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-checkstyle-plugin:2.2-SNAPSHOT:check' -->
> [DEBUG] (f) failOnViolation = true
> [DEBUG] (f) outputFile =
> /Users/vmassol/dev/xwiki/trunks-devs/xwiki-platform-core/target/checkstyle-result.xml
> [DEBUG] (f) outputFileFormat = xml
> [DEBUG] (f) skip = false
> [DEBUG] -- end configuration --
> [INFO] [checkstyle:check]
> [INFO] Unable to perform checkstyle:check, unable to find
> checkstyle:checkstyle outputFile.
> ...
> {noformat}
> The strange thing is that if I run "mvn checkstyle:checkstyle" or "mvn
> checkstyle:check", it works fine...
> Thanks
--
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-3499) Checkstyle plugin doesn't work with Maven 2.1
[
http://jira.codehaus.org/browse/MNG-3499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Massol closed MNG-3499.
---
Resolution: Won't Fix
My snapshot was dating back to end of January - Mid February (not sure when,
would be nice if mvn --help would provide the date).
I've just rebuilt 2.1-SNAPSHOT from sources and it's now working fine.
Sorry for the trouble and thanks again.
-Vincent
> Checkstyle plugin doesn't work with Maven 2.1
> -
>
> Key: MNG-3499
> URL: http://jira.codehaus.org/browse/MNG-3499
> Project: Maven 2
> Issue Type: Bug
>Affects Versions: 2.1-alpha-1
>Reporter: Vincent Massol
>Assignee: John Casey
> Attachments: checkstyle21error.txt, checkstyle21error.txt
>
>
> Running "mvn clean install" with the following configuration fails:
> {code}
>
>
> ...
>
>
> org.apache.maven.plugins
> maven-checkstyle-plugin
>
>
> com.xpn.xwiki.platform
> xwiki-build-verifications
> 1.1
>
>
>
>
> **/Api.java,
> **/xmlrpc/ConfluenceRpcInterface,
> **/xmlrpc/Attachment.java,
> **/xmlrpc/SpaceSummary.java,
> **/ViewAction.java,
> **/ZipExplorer*.java,
> **/FileUpload*.java,
> **/PluginApi.java,
> **/content/**/*.java,
> **/XWikiMessageTool.java,
> **/XWikiListFilter.java,
> **/MyPersistentLoginManager.java
>
>
> **/RenamePageReplaceLinkHandler.java
>
>
>
>
>
> {code}
> I have the following in the top level pom:
> {code}
>
>
>
>
>
> org.apache.maven.plugins
> maven-checkstyle-plugin
>
>
> com.xpn.xwiki.platform
> xwiki-build-verifications
>
>
>
> true
> checkstyle.xml
> checkstyle.license
>
>
>
>
> check
>
>
>
>
> ...
> {code}
> The error I get:
> {noformat}
> ...
> [DEBUG] Mojo: check has config:
>
>
> **/Api.java,
> **/xmlrpc/ConfluenceRpcInterface,
> **/xmlrpc/Attachment.java,
> **/xmlrpc/SpaceSummary.java,
> **/ViewAction.java,
> **/ZipExplorer*.java,
> **/FileUpload*.java,
> **/PluginApi.java,
> **/content/**/*.java,
> **/XWikiMessageTool.java,
> **/XWikiListFilter.java,
> **/MyPersistentLoginManager.java
> **/RenamePageReplaceLinkHandler.java
> true
> checkstyle.xml
> checkstyle.license
>
> [DEBUG] In verifyVersionedPlugin for:
> org.apache.maven.plugins:maven-checkstyle-plugin
> [DEBUG] maven-checkstyle-plugin: using locally installed snapshot
> [DEBUG]
> org.apache.maven.plugins:maven-checkstyle-plugin:maven-plugin:2.2-SNAPSHOT:runtime
> (selected for runtime)
> ...
> [DEBUG] Looking up mojo
> org.apache.maven.plugins:maven-checkstyle-plugin:2.2-SNAPSHOT:check in realm
> org.apache.maven.plugins:maven-checkstyle-plugin -
> descRealmId=org.apache.maven.plugins:maven-checkstyle-plugin
> [DEBUG] Looked up - [EMAIL PROTECTED] -
> ClassRealm[org.apache.maven.plugins:maven-checkstyle-plugin, parent:
> ClassRealm[plexus.core, parent: null]]
> [DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-checkstyle-plugin:2.2-SNAPSHOT:check' -->
> [DEBUG] (f) failOnViolation = true
> [DEBUG] (f) outputFile =
> /Users/vmassol/dev/xwiki/trunks-devs/xwiki-platform-core/target/checkstyle-result.xml
> [DEBUG] (f) outputFileFormat = xml
> [DEBUG] (f) skip = false
> [DEBUG] -- end configuration --
> [INFO] [checkstyle:check]
> [INFO] Unable to perform checkstyle:check, unable to find
> checkstyle:checkstyle outputFile.
> ...
> {noformat}
> The strange thing is that if I run "mvn checkstyle:checkstyle" or "mvn
> checkstyle:check", it works fine...
> Thanks
--
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-313) Use proper file encoding when storing site descriptor in local repo
Use proper file encoding when storing site descriptor in local repo
---
Key: MSITE-313
URL: http://jira.codehaus.org/browse/MSITE-313
Project: Maven 2.x Site Plugin
Issue Type: Bug
Components: encoding
Affects Versions: 2.0-beta-6
Reporter: Benjamin Bentmann
{{SiteDescriptorArtifactMetadata}} is currently using {{FileWriter}} to save
the decoration model into the local repository, potentially messing up
Non-ASCII characters, see also [Common
Bugs|http://www.nabble.com/Common-Bugs-to14783703s177.html#a15919795].
--
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: (MSITE-313) Use proper file encoding when storing site descriptor in local repo
[
http://jira.codehaus.org/browse/MSITE-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MSITE-313.
---
Assignee: Benjamin Bentmann
Resolution: Fixed
Fix Version/s: 2.0-beta-7
Fixed in [r644528|http://svn.apache.org/viewvc?view=rev&revision=644528].
> Use proper file encoding when storing site descriptor in local repo
> ---
>
> Key: MSITE-313
> URL: http://jira.codehaus.org/browse/MSITE-313
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Components: encoding
>Affects Versions: 2.0-beta-6
>Reporter: Benjamin Bentmann
>Assignee: Benjamin Bentmann
> Fix For: 2.0-beta-7
>
>
> {{SiteDescriptorArtifactMetadata}} is currently using {{FileWriter}} to save
> the decoration model into the local repository, potentially messing up
> Non-ASCII characters, see also [Common
> Bugs|http://www.nabble.com/Common-Bugs-to14783703s177.html#a15919795].
--
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-2002) Please upload JCROM 1.2
Please upload JCROM 1.2 --- Key: MAVENUPLOAD-2002 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2002 Project: maven-upload-requests Issue Type: Wish Reporter: Olafur Gauti Gudmundsson http://jcrom.googlecode.com/files/jcrom-1.2-bundle.jar http://jcrom.org (forwards to the google-code page for JCROM) http://code.google.com/u/oli.gauti/ I am the project owner, please upload. -- 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: (MPLUGINTESTING-1) Add convenience methods to MavenProjectStub to easily populate model from test resource
Add convenience methods to MavenProjectStub to easily populate model from test
resource
---
Key: MPLUGINTESTING-1
URL: http://jira.codehaus.org/browse/MPLUGINTESTING-1
Project: Maven 2.x Plugin Testing
Issue Type: Improvement
Components: plugin-testing-harness
Affects Versions: 1.1
Reporter: Benjamin Bentmann
Priority: Minor
The following code snippet
{code:java}
MavenXpp3Reader pomReader = new MavenXpp3Reader();
Model model = null;
try
{
File pomFile = new File( getBasedir(), "some-pom.xml" );
model = pomReader.read( ReaderFactory.newXmlReader( pomFile ) );
setModel( model );
}
catch ( Exception e )
{
throw new RuntimeException( e );
}
{code}
is both tiresome and error-prone (encoding). Moving this functionality into the
{{MavenProjectStub}} would make life easier.
--
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: (MPLUGINTESTING-1) Add convenience methods to MavenProjectStub to easily populate model from test resource
[
http://jira.codehaus.org/browse/MPLUGINTESTING-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MPLUGINTESTING-1.
--
Assignee: Benjamin Bentmann
Resolution: Fixed
Fix Version/s: 1.2
Added in [r644546|http://svn.apache.org/viewvc?view=rev&revision=644546].
> Add convenience methods to MavenProjectStub to easily populate model from
> test resource
> ---
>
> Key: MPLUGINTESTING-1
> URL: http://jira.codehaus.org/browse/MPLUGINTESTING-1
> Project: Maven 2.x Plugin Testing
> Issue Type: Improvement
> Components: plugin-testing-harness
>Affects Versions: 1.1
>Reporter: Benjamin Bentmann
>Assignee: Benjamin Bentmann
>Priority: Minor
> Fix For: 1.2
>
>
> The following code snippet
> {code:java}
> MavenXpp3Reader pomReader = new MavenXpp3Reader();
> Model model = null;
> try
> {
> File pomFile = new File( getBasedir(), "some-pom.xml" );
> model = pomReader.read( ReaderFactory.newXmlReader( pomFile ) );
> setModel( model );
> }
> catch ( Exception e )
> {
> throw new RuntimeException( e );
> }
> {code}
> is both tiresome and error-prone (encoding). Moving this functionality into
> the {{MavenProjectStub}} would make life easier.
--
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: (SCM-334) Faulty svn commandline is generated for passwords containing special chars
[
http://jira.codehaus.org/browse/SCM-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=129761#action_129761
]
Rahul Thakur commented on SCM-334:
--
I haven't tried this but shouldn't this be escaped with a {{backslash}} '\'
character rather than using single quotes.
What happens if the password itself contains a single quote?
> Faulty svn commandline is generated for passwords containing special chars
> --
>
> Key: SCM-334
> URL: http://jira.codehaus.org/browse/SCM-334
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-svn
>Affects Versions: 1.0
> Environment: All
>Reporter: Jan Lisse
>Priority: Critical
> Attachments: patch.txt
>
>
> If i use a svn password containing a semicolon with the
> maven-scm-provider-svnexe, the commandline generated by SvnCommandlineUtils
> is faulty, because
> the password is not quoted. Passwords containing other special chars might
> cause problems too.
> Solution: Enclosing the password for the commandline in single quotes solves
> this problem.
> I have attached a patch for SvnCommandlineUtils that fixes this issue.
--
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: (NMAVEN-107) Missing packaging paramter in bootstrap-build.bat
Missing packaging paramter in bootstrap-build.bat - Key: NMAVEN-107 URL: http://jira.codehaus.org/browse/NMAVEN-107 Project: NMaven Issue Type: Bug Reporter: Maria Catherine Tan Priority: Minor this applies for https://svn.apache.org/repos/asf/incubator/nmaven/tags/STABLE-2007-12-16/ -- 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: (NMAVEN-108) NMaven test compilation occurs in the compile phase
NMaven test compilation occurs in the compile phase --- Key: NMAVEN-108 URL: http://jira.codehaus.org/browse/NMAVEN-108 Project: NMaven Issue Type: Bug Reporter: John Michael Luy Using the STABLE-2007-12-16 tag, NMaven test compilation occurs in the compile phase. It should be on the test-compile phase. -- 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: (NMAVEN-108) NMaven test compilation occurs in the compile phase
[ http://jira.codehaus.org/browse/NMAVEN-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Michael Luy updated NMAVEN-108: Attachment: NMAVEN-108.patch > NMaven test compilation occurs in the compile phase > --- > > Key: NMAVEN-108 > URL: http://jira.codehaus.org/browse/NMAVEN-108 > Project: NMaven > Issue Type: Bug >Reporter: John Michael Luy > Attachments: NMAVEN-108.patch > > > Using the STABLE-2007-12-16 tag, NMaven test compilation occurs in the > compile phase. It should be on the test-compile phase. -- 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: (MWAR-9) WAR plugin should support minimal WARs for inclusion within an EAR
[ http://jira.codehaus.org/browse/MWAR-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=129770#action_129770 ] Barend Garvelink commented on MWAR-9: - This comment adds the words "skinny war" to this issue, because that's the name used in http://maven.apache.org/plugins/maven-war-plugin/examples/skinny-wars.html and therefore a likely search key. (I overlooked this one yesterday) > WAR plugin should support minimal WARs for inclusion within an EAR > -- > > Key: MWAR-9 > URL: http://jira.codehaus.org/browse/MWAR-9 > Project: Maven 2.x War Plugin > Issue Type: Improvement >Reporter: Mike Perham >Assignee: Stephane Nicoll > Fix For: 2.1 > > Attachments: AbstractWarMojo.patch > > > I noticed that when I build a WAR, I get a gigantic WEB-INF/lib with all my > deps. This is fine for a default but maven should also support "skeleton" > WARs which will be packaged within an EAR. We have EARs which package 3-4 > WARs each and to have the deps duplicated within each WAR means we cannot > have shared data (since the classes are loaded within each WAR's classloader, > rather than by the parent EAR's classloader). It also means 80MB EARs! :-) > It seems like two things need to happen: > 1) Add a "skeleton" flag which prevents copying any dependencies to > WEB-INF/lib. > 2) Instead generate a META-INF/MANIFEST.MF which has a Class-Path entry which > lists the relative locations of the dependencies within the parent EAR. > Fabrice has basically the same idea written down here. Starting with "- for > a War..." : > http://marc.theaimsgroup.com/?l=turbine-maven-user&m=112737860024530&w=2 -- 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: (NMAVEN-109) The text '${file.separator}' sometimes appear in directory names
The text '${file.separator}' sometimes appear in directory names
Key: NMAVEN-109
URL: http://jira.codehaus.org/browse/NMAVEN-109
Project: NMaven
Issue Type: Bug
Reporter: John Michael Luy
Using the STABLE-2007-12-16 tag, the text '${file.separator}' sometimes appear
in directory names for tests.
--
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: (NMAVEN-107) Missing packaging paramter in bootstrap-build.bat
[ http://jira.codehaus.org/browse/NMAVEN-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Catherine Tan updated NMAVEN-107: --- Attachment: fix-xmlschema-install.patch Attached patch to fix this issue > Missing packaging paramter in bootstrap-build.bat > - > > Key: NMAVEN-107 > URL: http://jira.codehaus.org/browse/NMAVEN-107 > Project: NMaven > Issue Type: Bug >Reporter: Maria Catherine Tan >Priority: Minor > Attachments: fix-xmlschema-install.patch > > > this applies for > https://svn.apache.org/repos/asf/incubator/nmaven/tags/STABLE-2007-12-16/ -- 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: (NMAVEN-109) The text '${file.separator}' sometimes appear in directory names
[
http://jira.codehaus.org/browse/NMAVEN-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Michael Luy updated NMAVEN-109:
Attachment: NMAVEN-109.patch
attached patch to fix issue.
> The text '${file.separator}' sometimes appear in directory names
>
>
> Key: NMAVEN-109
> URL: http://jira.codehaus.org/browse/NMAVEN-109
> Project: NMaven
> Issue Type: Bug
>Reporter: John Michael Luy
> Attachments: NMAVEN-109.patch
>
>
> Using the STABLE-2007-12-16 tag, the text '${file.separator}' sometimes
> appear in directory names for tests.
--
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-3067) Getting arbitrary depth=2 dependencies when using optional=true
[ http://jira.codehaus.org/browse/MNG-3067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=129773#action_129773 ] Barend Garvelink commented on MNG-3067: --- Is this related to MNG-3269 ? > Getting arbitrary depth=2 dependencies when using optional=true > --- > > Key: MNG-3067 > URL: http://jira.codehaus.org/browse/MNG-3067 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies >Affects Versions: 2.0.6 >Reporter: Jason Melnick > Fix For: 2.1 > > > When using a dependency section like this in a WAR (just an excerpt - these > are not the culprit to my knowledge): > > xmlbeans > xbean > true > > > xmlbeans > xbean_xpath > true > > > xml-apis > xml-apis > true > > > xml-resolver > xml-resolver > true > > I am getting artifacts with a depth of 2 - when nothing should resolve. Only > depth 1 (non-optional deps, plus their deps, etc) should be resolving. i.e. > [INFO] mq: 2 > [INFO] mqjms: 2 > [INFO] spring-orm: 2 > [INFO] struts: 1 > [INFO] child: commons-beanutils:commons-beanutils:jar:1.6.1:compile > (2; disabled) > [INFO] child: commons-collections:commons-collections:jar:3.1:compile > (2; disabled) > [INFO] child: struts:struts-legacy:jar:1.1:compile (2; enabled) > [INFO] child: commons-digester:commons-digester:jar:1.6:compile (2; > disabled) > [INFO] child: commons-fileupload:commons-fileupload:jar:1.0:compile > (2; enabled) > [INFO] child: commons-lang:commons-lang:jar:2.1:compile (2; disabled) > [INFO] child: commons-logging:commons-logging:jar:1.0:compile (2; > disabled) > [INFO] child: commons-validator:commons-validator:jar:1.1.4:compile > (2; disabled) > [INFO] child: oro:oro:jar:2.0.7:compile (2; disabled) > [INFO] child: javax.sql:jdbc-stdext:jar:2.0:compile (2; enabled) > [INFO] commons-logging: 1 > [INFO] child: log4j:log4j:jar:1.2.6:compile (2; enabled) > [INFO] child: logkit:logkit:jar:1.0.1:compile (2; enabled) > [INFO] child: avalon-framework:avalon-framework:jar:4.1.3:compile (2; > enabled) > [INFO] distribution-service-client-jar: 2 > [INFO] jdbc-stdext: 2 > [INFO] struts-bean: 1 > [INFO] cmf-nol-submit-jar: 2 > [INFO] mqiiop: 2 > [INFO] distribution-service-ejb: 2 > [INFO] jaxen: 2 > [INFO] spring-dao: 2 > [INFO] struts-tiles: 1 > [INFO] cmf-final-jar: 2 > [INFO] struts-legacy: 2 > [INFO] standard: 1 > [INFO] saxpath: 2 > [INFO] jstl: 1 > [INFO] nw-exception: 1 > [INFO] relaxngDatatype: 2 > [INFO] mqbind: 2 > [INFO] struts-logic: 1 > [INFO] commons-fileupload: 2 > [INFO] isorelax: 2 > [INFO] spring-core: 2 > [INFO] log4j: 1 > [INFO] msv: 2 > [INFO] struts-nested: 1 > [INFO] nw-struts: 1 > [INFO] child: struts:struts:jar:1.1:compile (2; disabled) > [INFO] struts-html: 1 > [INFO] authorization-tag-jar: 1 > [INFO] child: commons-logging:commons-logging:jar:1.0.4:compile (2; > disabled) > [INFO] child: log4j:log4j:jar:1.2.7:compile (2; disabled) > [INFO] child: com.nationwide.common:nw-exception:jar:1.2.0:compile > (2; disabled) > [INFO] child: > com.nationwide.pc.claims.horizon:simple-security-client-jar:jar:2.0.0:compile > (2; disabled) -- 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: (NMAVEN-110) Ability to generate .vbproj files
Ability to generate .vbproj files - Key: NMAVEN-110 URL: http://jira.codehaus.org/browse/NMAVEN-110 Project: NMaven Issue Type: New Feature Reporter: Maria Catherine Tan this applies to https://svn.apache.org/repos/asf/incubator/nmaven/tags/STABLE-2007-12-16/ -- 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: (NMAVEN-110) Ability to generate .vbproj files
[ http://jira.codehaus.org/browse/NMAVEN-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=129775#action_129775 ] Maria Catherine Tan commented on NMAVEN-110: It should be possible to generate the Visual Studio config files (.vbproj, etc.) for a VB .NET project. > Ability to generate .vbproj files > - > > Key: NMAVEN-110 > URL: http://jira.codehaus.org/browse/NMAVEN-110 > Project: NMaven > Issue Type: New Feature >Reporter: Maria Catherine Tan > > this applies to > https://svn.apache.org/repos/asf/incubator/nmaven/tags/STABLE-2007-12-16/ -- 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
