[jira] [Commented] (MCHECKSTYLE-302) Using inline configuration does not work with Maven 2.2.1
[ https://issues.apache.org/jira/browse/MCHECKSTYLE-302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14900247#comment-14900247 ] Michael Osipov commented on MCHECKSTYLE-302: Is that still true for Maven 3? I am cofused why we need to document a behavior which is not present in Maven 3. > Using inline configuration does not work with Maven 2.2.1 > - > > Key: MCHECKSTYLE-302 > URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-302 > Project: Maven Checkstyle Plugin > Issue Type: Bug >Affects Versions: 2.15 >Reporter: Dennis Lundberg > > A test project is already checked in, as part of the IT for MCHECKSTYLE-295. > That IT will fail with Maven 2.2.1 complaining that the attribute "name" is > missing from element "module". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (SUREFIRE-1178) Upgrade maven-shared-utils to Version 0.9
[ https://issues.apache.org/jira/browse/SUREFIRE-1178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana closed SUREFIRE-1178. -- Resolution: Fixed commit 257f59e63fa2dca66e42e19715ab7be04884e12f > Upgrade maven-shared-utils to Version 0.9 > - > > Key: SUREFIRE-1178 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1178 > Project: Maven Surefire > Issue Type: Improvement > Components: Maven Failsafe Plugin, Maven Surefire Plugin >Reporter: Tibor Digana >Assignee: Tibor Digana > Fix For: 2.19 > > > New Surefire feature SUREFIRE-524 requires bug fix MSHARED-434. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (MCHECKSTYLE-302) Using inline configuration does not work with Maven 2.2.1
[ https://issues.apache.org/jira/browse/MCHECKSTYLE-302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg reopened MCHECKSTYLE-302: - I don't expect us to make this work for Maven 2, but we should at least document the currently behavior. > Using inline configuration does not work with Maven 2.2.1 > - > > Key: MCHECKSTYLE-302 > URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-302 > Project: Maven Checkstyle Plugin > Issue Type: Bug >Affects Versions: 2.15 >Reporter: Dennis Lundberg > > A test project is already checked in, as part of the IT for MCHECKSTYLE-295. > That IT will fail with Maven 2.2.1 complaining that the attribute "name" is > missing from element "module". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MCHECKSTYLE-275) remove old deprecated parameters from report
[ https://issues.apache.org/jira/browse/MCHECKSTYLE-275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14900056#comment-14900056 ] Hervé Boutemy commented on MCHECKSTYLE-275: --- don't hesitate to do it: I have much to do on other topics thanks > remove old deprecated parameters from report > > > Key: MCHECKSTYLE-275 > URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-275 > Project: Maven Checkstyle Plugin > Issue Type: Task > Components: checkstyle:checkstyle >Affects Versions: 2.13 >Reporter: Hervé Boutemy >Priority: Minor > > there are a bunch of parameters that are deprecated since 2005 (I don't even > tried to find the version form the plugin: it was before 2.0): > - format: Use configLocation instead > - propertiesFile: Use propertiesLocation instead > - propertiesURL: Use propertiesLocation instead > - headerFile: Use headerLocation instead > - suppressionsFile: Use suppressionsLocation instead > - packageNamesFile: Use packageNamesLocation instead > removing these will clean up source code > in fact, we should have a general policy for parameter deprecation: > 1. add a warning when detecting deprecated parameter usage exactly at the > same time as deprecating the parameter, > 2. a few versions later (no hurry), change warning to failure > 3. then a few versions later remove the code > for this case, I intend to go to step 3 directly if nobody is against it -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MCHECKSTYLE-275) remove old deprecated parameters from report
[ https://issues.apache.org/jira/browse/MCHECKSTYLE-275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14900054#comment-14900054 ] Michael Osipov commented on MCHECKSTYLE-275: [~hboutemy], eight months have passed. Why don't you go ahead and fix this issue? No objections received. > remove old deprecated parameters from report > > > Key: MCHECKSTYLE-275 > URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-275 > Project: Maven Checkstyle Plugin > Issue Type: Task > Components: checkstyle:checkstyle >Affects Versions: 2.13 >Reporter: Hervé Boutemy >Priority: Minor > > there are a bunch of parameters that are deprecated since 2005 (I don't even > tried to find the version form the plugin: it was before 2.0): > - format: Use configLocation instead > - propertiesFile: Use propertiesLocation instead > - propertiesURL: Use propertiesLocation instead > - headerFile: Use headerLocation instead > - suppressionsFile: Use suppressionsLocation instead > - packageNamesFile: Use packageNamesLocation instead > removing these will clean up source code > in fact, we should have a general policy for parameter deprecation: > 1. add a warning when detecting deprecated parameter usage exactly at the > same time as deprecating the parameter, > 2. a few versions later (no hurry), change warning to failure > 3. then a few versions later remove the code > for this case, I intend to go to step 3 directly if nobody is against it -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (MCHECKSTYLE-302) Using inline configuration does not work with Maven 2.2.1
[ https://issues.apache.org/jira/browse/MCHECKSTYLE-302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov resolved MCHECKSTYLE-302. Resolution: Won't Fix Maven 2.2.1 is retired. So closing as won't fix. > Using inline configuration does not work with Maven 2.2.1 > - > > Key: MCHECKSTYLE-302 > URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-302 > Project: Maven Checkstyle Plugin > Issue Type: Bug >Affects Versions: 2.15 >Reporter: Dennis Lundberg > > A test project is already checked in, as part of the IT for MCHECKSTYLE-295. > That IT will fail with Maven 2.2.1 complaining that the attribute "name" is > missing from element "module". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MPOM-88) yyy-LATEST deployment URL breaks site parent reference menu
[ https://issues.apache.org/jira/browse/MPOM-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MPOM-88: -- Summary: yyy-LATEST deployment URL breaks site parent reference menu (was: yyy-LATEST deployment URL breaks site parent reference manu) > yyy-LATEST deployment URL breaks site parent reference menu > --- > > Key: MPOM-88 > URL: https://issues.apache.org/jira/browse/MPOM-88 > Project: Maven POMs > Issue Type: Bug > Components: maven-plugins, maven-shared-components, maven-skins >Reporter: Karl Heinz Marbaise >Assignee: Hervé Boutemy >Priority: Minor > Fix For: MAVEN-SKINS-11, MAVEN-SHARED-22, MAVEN-PLUGINS-28 > > > On the page of the http://maven.apache.org/shared/maven-reporting-exec/ the > link to the "Parent Project" Apache Maven Shared Components shows the > following: > http://maven.apache.org/shared/maven-shared-components-LATEST/index.html > which is wrong. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MPOM-88) yyy-LATEST deployment URL breaks site parent reference manu
[ https://issues.apache.org/jira/browse/MPOM-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy closed MPOM-88. - Resolution: Fixed Assignee: Hervé Boutemy Fix Version/s: MAVEN-PLUGINS-28 MAVEN-SHARED-22 MAVEN-SKINS-11 fixed in [r1704181|http://svn.apache.org/r1704181] for shared components, [r1704183|http://svn.apache.org/r1704183] for plugins and [r1704185|http://svn.apache.org/r1704185] > yyy-LATEST deployment URL breaks site parent reference manu > --- > > Key: MPOM-88 > URL: https://issues.apache.org/jira/browse/MPOM-88 > Project: Maven POMs > Issue Type: Bug > Components: maven-plugins, maven-shared-components, maven-skins >Reporter: Karl Heinz Marbaise >Assignee: Hervé Boutemy >Priority: Minor > Fix For: MAVEN-SKINS-11, MAVEN-SHARED-22, MAVEN-PLUGINS-28 > > > On the page of the http://maven.apache.org/shared/maven-reporting-exec/ the > link to the "Parent Project" Apache Maven Shared Components shows the > following: > http://maven.apache.org/shared/maven-shared-components-LATEST/index.html > which is wrong. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MCHECKSTYLE-307) Upgrade to Checkstyle 6.11
[
https://issues.apache.org/jira/browse/MCHECKSTYLE-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MCHECKSTYLE-307:
---
Fix Version/s: 2.17
> Upgrade to Checkstyle 6.11
> --
>
> Key: MCHECKSTYLE-307
> URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-307
> Project: Maven Checkstyle Plugin
> Issue Type: Task
>Affects Versions: 2.16
>Reporter: Michael Osipov
>Assignee: Michael Osipov
> Fix For: 2.17
>
>
> Hi folks,
> I have upraded Checkstyle locally and almost all ITs pass except for the
> issues [~denn...@apache.org] already has described:
> {quote}
> Changes in Checkstyle 6.3 that impact this plugin:
> * The IT MCHECKSTYLE-214-basedir-resource fails after upgrade to Checkstyle
> 6.3 with NPE - I have not found a solution for this yet
> Changes in Checkstyle 6.6 that impact this plugin:
> * DefaultLogger( OutputStream, boolean ) now throws
> UnsupportedEncodingException - this is easy to fix
> {quote}
> The first issue is caused because the default checkfiles apply to specific
> file extensions now, so IT for MCHECKSTYLE-214. [~rfscholte], what do you
> think about it. We can invert the test or add a custom {{sun_checks.xml}}.
> The second one can be fixed with the linked GH issue.
> I am willing to promote a release if I get some help to resolve the issues
> above.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MCHECKSTYLE-307) Upgrade to Checkstyle 6.11
[
https://issues.apache.org/jira/browse/MCHECKSTYLE-307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14900051#comment-14900051
]
Michael Osipov commented on MCHECKSTYLE-307:
No, not really. One IT will be fixed/changed as soon as 6.11 will be available.
The rest passes. If no one complains, I intend to release as-is.
> Upgrade to Checkstyle 6.11
> --
>
> Key: MCHECKSTYLE-307
> URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-307
> Project: Maven Checkstyle Plugin
> Issue Type: Task
>Affects Versions: 2.16
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>
> Hi folks,
> I have upraded Checkstyle locally and almost all ITs pass except for the
> issues [~denn...@apache.org] already has described:
> {quote}
> Changes in Checkstyle 6.3 that impact this plugin:
> * The IT MCHECKSTYLE-214-basedir-resource fails after upgrade to Checkstyle
> 6.3 with NPE - I have not found a solution for this yet
> Changes in Checkstyle 6.6 that impact this plugin:
> * DefaultLogger( OutputStream, boolean ) now throws
> UnsupportedEncodingException - this is easy to fix
> {quote}
> The first issue is caused because the default checkfiles apply to specific
> file extensions now, so IT for MCHECKSTYLE-214. [~rfscholte], what do you
> think about it. We can invert the test or add a custom {{sun_checks.xml}}.
> The second one can be fixed with the linked GH issue.
> I am willing to promote a release if I get some help to resolve the issues
> above.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Moved] (MPOM-88) yyy-LATEST deployment URL breaks site parent reference manu
[ https://issues.apache.org/jira/browse/MPOM-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy moved DOXIATOOLS-50 to MPOM-88: - Component/s: (was: Doxia Integration Tools) maven-skins maven-shared-components maven-plugins Issue Type: Bug (was: Question) Key: MPOM-88 (was: DOXIATOOLS-50) Project: Maven POMs (was: Maven Doxia Tools) > yyy-LATEST deployment URL breaks site parent reference manu > --- > > Key: MPOM-88 > URL: https://issues.apache.org/jira/browse/MPOM-88 > Project: Maven POMs > Issue Type: Bug > Components: maven-plugins, maven-shared-components, maven-skins >Reporter: Karl Heinz Marbaise >Priority: Minor > > On the page of the http://maven.apache.org/shared/maven-reporting-exec/ the > link to the "Parent Project" Apache Maven Shared Components shows the > following: > http://maven.apache.org/shared/maven-shared-components-LATEST/index.html > which is wrong. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MCHECKSTYLE-307) Upgrade to Checkstyle 6.11
[
https://issues.apache.org/jira/browse/MCHECKSTYLE-307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14900044#comment-14900044
]
Ruslan Diachenko commented on MCHECKSTYLE-307:
--
[~michael-o] Another Checkstyle's issue was fixed:
https://github.com/checkstyle/checkstyle/issues/2193. Does anything else in
Checkstyle block your development?
> Upgrade to Checkstyle 6.11
> --
>
> Key: MCHECKSTYLE-307
> URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-307
> Project: Maven Checkstyle Plugin
> Issue Type: Task
>Affects Versions: 2.16
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>
> Hi folks,
> I have upraded Checkstyle locally and almost all ITs pass except for the
> issues [~denn...@apache.org] already has described:
> {quote}
> Changes in Checkstyle 6.3 that impact this plugin:
> * The IT MCHECKSTYLE-214-basedir-resource fails after upgrade to Checkstyle
> 6.3 with NPE - I have not found a solution for this yet
> Changes in Checkstyle 6.6 that impact this plugin:
> * DefaultLogger( OutputStream, boolean ) now throws
> UnsupportedEncodingException - this is easy to fix
> {quote}
> The first issue is caused because the default checkfiles apply to specific
> file extensions now, so IT for MCHECKSTYLE-214. [~rfscholte], what do you
> think about it. We can invert the test or add a custom {{sun_checks.xml}}.
> The second one can be fixed with the linked GH issue.
> I am willing to promote a release if I get some help to resolve the issues
> above.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1177) TestNG "suitethreadpoolsize" parameter can not be set by Maven Surefire
[
https://issues.apache.org/jira/browse/SUREFIRE-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1493#comment-1493
]
ASF GitHub Bot commented on SUREFIRE-1177:
--
Github user Tibor17 commented on the pull request:
https://github.com/apache/maven-surefire/pull/105#issuecomment-141812040
Agreed, we can improve later on.
Then the TestNG project should be informed that we continue using old
configuration method.
I have to ask you guys to publish documentation in
maven-surefire-plugin project src/main/site/**/*.apt.vm with both
examples for "-suitethreadpoolsize" and "-dataproviderthreadcount".
I will commit the fix as soon as you introduce integration tests for
all configurations.
Please make sure that we hit more than 10 concurrent threads.
Make sure that sanity check throws TestSetFailedException with
meaningful message that "-suitethreadpoolsize" or
"-dataproviderthreadcount" should be positive integer.
On 9/19/15, Julien Herr wrote:
> Are we agree that the current PR is more about parameters than threading?
>
> Before the fix: "-suitethreadpoolsize" and "-dataproviderthreadcount" were
> sent without conversion to TestNG, but TestNG need `Integer`.
> After the fix: "-suitethreadpoolsize" and "-dataproviderthreadcount" are
> sent with conversion to TestNG, what it supposed to be done.
>
> @dundacek already made [a fix](https://github.com/cbeust/testng/pull/798)
> into TestNG for "-suitethreadpoolsize" but not for
> "-dataproviderthreadcount". And I think we are all agree that TestNG is
not
> the good place for that.
>
> What I propose is to merge my fix because it has no risk
> ("-suitethreadpoolsize" and "-dataproviderthreadcount" are `Integer` since
> the begginning) and it will help users, then we can try to improve
parallel
> and/or use the "new" TestNG method.
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/apache/maven-surefire/pull/105#issuecomment-141709744
--
Cheers
Tibor
> TestNG "suitethreadpoolsize" parameter can not be set by Maven Surefire
> ---
>
> Key: SUREFIRE-1177
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1177
> Project: Maven Surefire
> Issue Type: Bug
> Components: TestNG support
>Affects Versions: 2.18.1
>Reporter: Jan Dundáček
>
> Because of Surefire is using deprecated TestNG.configure(Map) method,
> parameter "suitethreadpoolsize" value is not read by TestNG. And so test
> suites can not be run in parallel. This parameter is read only in
> TestNG.configure(CommandLineArgs) method.
> /**
>* This method is invoked by Maven's Surefire to configure the runner,
>* do not remove unless you know for sure that Surefire has been updated
>* to use the new configure(CommandLineArgs) method.
>*
>* @deprecated use new configure(CommandLineArgs) method
>*/
> @Deprecated
> public void configure(Map cmdLineArgs) {
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (DOXIATOOLS-50) yyy-LATEST deployment URL breaks site parent reference manu
[ https://issues.apache.org/jira/browse/DOXIATOOLS-50?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14899962#comment-14899962 ] Hervé Boutemy commented on DOXIATOOLS-50: - moved to DoxiaTools as a question, since I don't think there is any bug in any plugin or tool: this is a problem with our configuration of poms I don't know if we can add a feature in the tools, or change our convention in pom.xml but here is the code that calculates parent reference: http://maven.apache.org/doxia/doxia-tools/doxia-integration-tools/xref/org/apache/maven/doxia/tools/DefaultSiteTool.html#L638 > yyy-LATEST deployment URL breaks site parent reference manu > --- > > Key: DOXIATOOLS-50 > URL: https://issues.apache.org/jira/browse/DOXIATOOLS-50 > Project: Maven Doxia Tools > Issue Type: Question > Components: Doxia Integration Tools >Reporter: Karl Heinz Marbaise >Priority: Minor > > On the page of the http://maven.apache.org/shared/maven-reporting-exec/ the > link to the "Parent Project" Apache Maven Shared Components shows the > following: > http://maven.apache.org/shared/maven-shared-components-LATEST/index.html > which is wrong. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (DOXIATOOLS-50) yyy-LATEST deployment URL breaks site parent reference manu
[ https://issues.apache.org/jira/browse/DOXIATOOLS-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated DOXIATOOLS-50: Component/s: Doxia Integration Tools > yyy-LATEST deployment URL breaks site parent reference manu > --- > > Key: DOXIATOOLS-50 > URL: https://issues.apache.org/jira/browse/DOXIATOOLS-50 > Project: Maven Doxia Tools > Issue Type: Question > Components: Doxia Integration Tools >Reporter: Karl Heinz Marbaise >Priority: Minor > > On the page of the http://maven.apache.org/shared/maven-reporting-exec/ the > link to the "Parent Project" Apache Maven Shared Components shows the > following: > http://maven.apache.org/shared/maven-shared-components-LATEST/index.html > which is wrong. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Moved] (DOXIATOOLS-50) yyy-LATEST deployment URL breaks site parent reference manu
[ https://issues.apache.org/jira/browse/DOXIATOOLS-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy moved MSCMPUB-17 to DOXIATOOLS-50: Issue Type: Question (was: Bug) Key: DOXIATOOLS-50 (was: MSCMPUB-17) Project: Maven Doxia Tools (was: Maven SCM Publish Plugin) > yyy-LATEST deployment URL breaks site parent reference manu > --- > > Key: DOXIATOOLS-50 > URL: https://issues.apache.org/jira/browse/DOXIATOOLS-50 > Project: Maven Doxia Tools > Issue Type: Question >Reporter: Karl Heinz Marbaise >Priority: Minor > > On the page of the http://maven.apache.org/shared/maven-reporting-exec/ the > link to the "Parent Project" Apache Maven Shared Components shows the > following: > http://maven.apache.org/shared/maven-shared-components-LATEST/index.html > which is wrong. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MSCMPUB-17) yyy-LATEST deployment URL breaks site parent reference manu
[ https://issues.apache.org/jira/browse/MSCMPUB-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MSCMPUB-17: - Description: On the page of the http://maven.apache.org/shared/maven-reporting-exec/ the link to the "Parent Project" Apache Maven Shared Components shows the following: http://maven.apache.org/shared/maven-shared-components-LATEST/index.html which is wrong. was: On the page of the http://maven.apache.org/shared/maven-reporting-exec/ the link to the maven shared components shows the following: http://maven.apache.org/shared/maven-shared-components-LATEST/index.html which is wrong. > yyy-LATEST deployment URL breaks site parent reference manu > --- > > Key: MSCMPUB-17 > URL: https://issues.apache.org/jira/browse/MSCMPUB-17 > Project: Maven SCM Publish Plugin > Issue Type: Bug >Reporter: Karl Heinz Marbaise >Priority: Minor > > On the page of the http://maven.apache.org/shared/maven-reporting-exec/ the > link to the "Parent Project" Apache Maven Shared Components shows the > following: > http://maven.apache.org/shared/maven-shared-components-LATEST/index.html > which is wrong. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MSCMPUB-19) Plugin fails to publish to SCMs whose working copies don't have any kind of private storage
[
https://issues.apache.org/jira/browse/MSCMPUB-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy closed MSCMPUB-19.
Resolution: Fixed
Assignee: Hervé Boutemy
Fix Version/s: 1.2
patch applied in [r1704147|http://svn.apache.org/r1704147]
thank you for the patch (and for your patience...)
> Plugin fails to publish to SCMs whose working copies don't have any kind of
> private storage
> ---
>
> Key: MSCMPUB-19
> URL: https://issues.apache.org/jira/browse/MSCMPUB-19
> Project: Maven SCM Publish Plugin
> Issue Type: Bug
>Affects Versions: 1.1
>Reporter: Roman Korpachyov
>Assignee: Hervé Boutemy
> Fix For: 1.2
>
>
> I've discovered this problem when tried to use the plugin to check files in
> to StarTeam server. Running {{scm-publish:publish-scm}} goal resulted in
> following message:
> {code:title=mvn scm-publish:publish-scm}
> ...
> [INFO] --- maven-scm-publish-plugin:1.1:publish-scm (default-cli) @
> starteam-checkin ---
> [WARNING] No output encoding, defaulting to UTF-8.
> [INFO] Checking out the pub tree from scm:starteam::://
> into ${basedir}\target\scmpublish-checkout
> [INFO] Working directory: ${basedir}\target\scmpublish-checkout
> [INFO] Command line: cmd.exe /X /C "stcmd co -x -nologo -stop -p
> "@://" -fp ${basedir}/target/scmpublish-checkout
> -is -eol on"
> [INFO] Checked out: ./dummy.txt
> [INFO] Updating checkout directory with actual content in ${basedir}\dist
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-scm-publish-plugin:1.1:publish-scm
> (default-cli) on project starteam-checkin: Execution default-cli of goal
> org.apache.maven.plugins:maven-scm-publish-plugin:1.1:publish-scm failed: The
> wildcard must not be null -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-scm-publish-plugin:1.1
> :publish-scm (default-cli) on project starteam-checkin: Execution default-cli
> of goal org.apache.maven.plugins:maven-scm-publish-plugin:1.1:publish-scm
> failed: The wildcard must not be null
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> default-cli of goal
> org.apache.maven.plugins:maven-scm-publish-plugin:1.1:publish-scm failed: The
> wildcard must not be null
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:143)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> ... 19 more
> Caused by: java.lang.IllegalArgumentException: The wildcard must not be null
> at
> org.apache.commons.io.filefilter.NameFileFilter.(NameFileFilter.java:75)
> at
> org.apache.commons.io.filefilter.NameFileFilter.(NameFileFilter.java:63)
> at
> org.apache.maven.plugins.scmpublish.ScmPublishPublishScmMojo.update(ScmPublishPublishScmMojo.java:92)
> at
> org.apache.ma
[jira] [Commented] (DOXIA-531) improve MacroRequest API with parser and sourceContent parameters requirements
[ https://issues.apache.org/jira/browse/DOXIA-531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14877460#comment-14877460 ] Hervé Boutemy commented on DOXIA-531: - done for Xhtml format in [r1704107|http://svn.apache.org/r1704107] after macro support was added in DOXIA-529 > improve MacroRequest API with parser and sourceContent parameters requirements > -- > > Key: DOXIA-531 > URL: https://issues.apache.org/jira/browse/DOXIA-531 > Project: Maven Doxia > Issue Type: Task > Components: Core >Affects Versions: 1.6 >Reporter: Hervé Boutemy >Assignee: Hervé Boutemy > Fix For: 1.7 > > > there is a convention that every parser that creates macro request provide > "sourceContent" and "parser" in the parameters map, to let toc macro work > this requirement would be better understood/documented if it was part of the > constructor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (DOXIA-529) Add macro support to XHTML
[ https://issues.apache.org/jira/browse/DOXIA-529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy closed DOXIA-529. --- Resolution: Fixed Assignee: Hervé Boutemy Fix Version/s: 1.7 patch applied in [r1704102|http://svn.apache.org/r1704102] thank you for your contribution and patience > Add macro support to XHTML > --- > > Key: DOXIA-529 > URL: https://issues.apache.org/jira/browse/DOXIA-529 > Project: Maven Doxia > Issue Type: Improvement > Components: Module - Xhtml >Reporter: Masatake Iwasaki >Assignee: Hervé Boutemy > Fix For: 1.7 > > Attachments: DOXIA-529.001.patch > > > Adding macro support to XhtmlParser. It could be used by MarkdownParser which > uses XHTML as intermediate format for conversion. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
