[jira] [Commented] (MNG-5799) Incorrect execution order of plugins in the same phase
[
https://issues.apache.org/jira/browse/MNG-5799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15173347#comment-15173347
]
Gerhard Poul commented on MNG-5799:
---
The introduction at
https://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html#A_Build_Phase_is_Made_Up_of_Plugin_Goals
states: "In Maven 2.0.5 and above, multiple goals bound to a phase are
executed in the same order as they are declared in the POM, however multiple
instances of the same plugin are not supported."
> Incorrect execution order of plugins in the same phase
> --
>
> Key: MNG-5799
> URL: https://issues.apache.org/jira/browse/MNG-5799
> Project: Maven
> Issue Type: Bug
> Components: Plugins and Lifecycle
>Affects Versions: 3.2.5
> Environment: Apache Maven 3.2.5
> (12a6b3acb947671f09b81f49094c53f426d8cea1; 2014-12-14T18:29:23+01:00)
>Reporter: Gerhard Poul
>Assignee: Christian Schulte
>
> When multiple plugins are used and assigned to the same phase they are not
> executed in the order they're listed in the POM.
> Repro case: https://github.com/gpoul/arquillian-container-was/tree/MNG-5799
> Repro steps: Execute {{mvn test}} in folder {{wlp-managed-8.5}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MNG-5799) Incorrect execution order of plugins in the same phase
[
https://issues.apache.org/jira/browse/MNG-5799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15172973#comment-15172973
]
Christian Schulte commented on MNG-5799:
Did you read about the order of declaration having a meaning somewhere? It
would be great if you could provide pointers to that here. A quick peek at the
Maven website does not show that is documented anywhere. Does not mean that
information is not provided somewhere. Whatever this issue leads to, it will
need to be documented to stop people from relying on some implementation detail
documented/specified nowhere.
> Incorrect execution order of plugins in the same phase
> --
>
> Key: MNG-5799
> URL: https://issues.apache.org/jira/browse/MNG-5799
> Project: Maven
> Issue Type: Bug
> Components: Plugins and Lifecycle
>Affects Versions: 3.2.5
> Environment: Apache Maven 3.2.5
> (12a6b3acb947671f09b81f49094c53f426d8cea1; 2014-12-14T18:29:23+01:00)
>Reporter: Gerhard Poul
>Assignee: Christian Schulte
>
> When multiple plugins are used and assigned to the same phase they are not
> executed in the order they're listed in the POM.
> Repro case: https://github.com/gpoul/arquillian-container-was/tree/MNG-5799
> Repro steps: Execute {{mvn test}} in folder {{wlp-managed-8.5}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MJAVADOC-441) javadoc plugin fails with recent jdk9-ea builds
[
https://issues.apache.org/jira/browse/MJAVADOC-441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15172743#comment-15172743
]
Pether Sörling commented on MJAVADOC-441:
-
org.codehaus.plexus
plexus-archiver
3.0.3
Is released now, resolved the above problem for me both in this plugin and
maven-war-plugin by changed dependencies for the plugins.
> javadoc plugin fails with recent jdk9-ea builds
> ---
>
> Key: MJAVADOC-441
> URL: https://issues.apache.org/jira/browse/MJAVADOC-441
> Project: Maven Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.10.3
> Environment: Windows7 64bit, java-9 ea, build 99 (
> https://jdk9.java.net/download/ )
> C:\Program Files\Java\jdk-9\bin>java -version
> java version "9-ea"
> Java(TM) SE Runtime Environment (build
> 9-ea+99-2015-12-23-183325.javare.4146.nc)
> Java HotSpot(TM) 64-Bit Server VM (build
> 9-ea+99-2015-12-23-183325.javare.4146.nc, mixed mode)
>Reporter: Tagir Valeev
>
> Steps to reproduce:
> 1. Create simple POM:
> {code:xml}
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd";>
> 4.0.0
> one.sample
> test
> 0.0.1-SNAPSHOT
> jar
> Test
>
>
>
> org.apache.maven.plugins
> maven-javadoc-plugin
> 2.10.3
>
>
>
>
> {code}
> 2. Run mvn javadoc:jar (using java-9)
> Expected behavior: successful build.
> Actual behavior: exception:
> {noformat}
> [INFO] --- maven-javadoc-plugin:2.10.3:jar (default-cli) @ test ---
> [WARNING] Error injecting: org.codehaus.plexus.archiver.jar.JarArchiver
> java.lang.ExceptionInInitializerError
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:426)
> at
> com.google.inject.internal.DefaultConstructionProxyFactory$1.newInstance(DefaultConstructionProxyFactory.java:86)
> at
> com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:109)
> at
> com.google.inject.internal.ConstructorInjector.access$000(ConstructorInjector.java:32)
> at
> com.google.inject.internal.ConstructorInjector$1.call(ConstructorInjector.java:92)
> at
> com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:100)
> at
> com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:116)
> at
> com.google.inject.internal.ProvisionListenerStackCallback.provision(ProvisionListenerStackCallback.java:55)
> at
> com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:90)
> at
> com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:269)
> at
> com.google.inject.internal.InjectorImpl$2$1.call(InjectorImpl.java:997)
> at
> com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1054)
> at com.google.inject.internal.InjectorImpl$2.get(InjectorImpl.java:993)
> at
> com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1032)
> at
> org.eclipse.sisu.space.AbstractDeferredClass.get(AbstractDeferredClass.java:48)
> at
> com.google.inject.internal.ProviderInternalFactory.provision(ProviderInternalFactory.java:86)
> at
> com.google.inject.internal.InternalFactoryToInitializableAdapter.provision(InternalFactoryToInitializableAdapter.java:55)
> at
> com.google.inject.internal.ProviderInternalFactory$1.call(ProviderInternalFactory.java:70)
> at
> com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:100)
> at
> com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:116)
> at
> com.google.inject.internal.ProvisionListenerStackCallback.provision(ProvisionListenerStackCallback.java:55)
> at
> com.google.inject.internal.ProviderInternalFactory.circularGet(ProviderInternalFactory.java:68)
> at
> com.google.inject.internal.InternalFactoryToInitializableAdapter.get(InternalFactoryToInitializableAdapter.java:47)
> at
> com.google.inject.internal.InjectorImpl$2$1.call(InjectorImpl.java:997)
> at
> com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1054)
> at com.google.inject.internal.InjectorImpl$2.
[jira] [Comment Edited] (MSITE-768) maven-site-plugin 3.5 breaks Velocity
[
https://issues.apache.org/jira/browse/MSITE-768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15172680#comment-15172680
]
Michael Osipov edited comment on MSITE-768 at 2/29/16 10:15 PM:
I have tested your sample project and am able to confirm that this is not a bug
in MSITE. There are two issues with Doxia Sitetools and Plexus Velocity
component.
1. The configured Site Renderer Component misses to pass the following property
to the Velocity engine:
{code}
eventhandler.include.class
org.apache.velocity.app.event.implement.IncludeRelativePath
{code}
2. All custom resource loaders, whether from Sitetools or Plexus Velocity, are
crap. The do not stick to the contract from the abstract {{ResourceLoader}}
class.
Ultimately, due to the first issue, your {{include.vm}} is not make absolute to
{{index.md.vm}} and second throws an NPE because the first loader does not find
your included template in the classpath. No one checks for a {{null}} after
{{getResourceAsStream}}. It should actually throw {{ResourceNotFoundException}}.
Please open for both appropriate issues, I will close this one and process the
others. As far as I can see, the resource loaders provided by Velocity should
do it in most cases.
was (Author: michael-o):
I have tested your sample project and am able to confirm that this is not a bug
in MSITE. There are two issues with Doxia Sitetools and Plexus Velocity
component.
1. The configured Site Renderer Component misses to pass the following property
to the Velocity engine:
{code}
eventhandler.include.class
org.apache.velocity.app.event.implement.IncludeRelativePath
{code}
2. All custom resource loaders, whether from Sitetools or Plexus Velocity, are
crap. The do not stick to the contract from the abstract {{ResourceLoader}}
class.
Ultimately, due to the first issue, your {{include.vm}} is not make absolute to
{{index.md.vm}} and second throws an NPE because the first loader does not find
your included template in the classpath. No one checks for a {{null}} after
{{getResourceAsStream}}.
Please open for both appropriate issues, I will close this one and process the
others. As far as I can see, the resource loaders provided by Velocity should
do it in most cases.
> maven-site-plugin 3.5 breaks Velocity
> -
>
> Key: MSITE-768
> URL: https://issues.apache.org/jira/browse/MSITE-768
> Project: Maven Site Plugin
> Issue Type: Bug
>Affects Versions: 3.5
> Environment: $ mvn --version
> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
> 2015-11-10T17:41:47+01:00)
> Maven home: /usr/local/Cellar/maven/3.3.9/libexec
> Java version: 1.8.0_74, vendor: Oracle Corporation
> Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_74.jdk/Contents/Home/jre
> Default locale: de_DE, platform encoding: UTF-8
> OS name: "mac os x", version: "10.11.3", arch: "x86_64", family: "mac"
>Reporter: Christian Schlichtherle
>Priority: Blocker
> Attachments: msite-768.zip
>
>
> It seem like since version 3.5, I cannot use {{#parse}} or {{#include}} in
> Velocity filtered templates anymore. See attached test project.
> Please note that it doesn't matter what the name of the file to parse is. You
> can even change it to a non-existent file (e.g. "foo") and it all still abort
> unnecessary recursion.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MSOURCES-94) Heap space OOM
[
https://issues.apache.org/jira/browse/MSOURCES-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15172716#comment-15172716
]
Jeff commented on MSOURCES-94:
--
we have this exact same issue as well even with small single module projects.
After reverting to 2.4 it runs fine.
> Heap space OOM
> --
>
> Key: MSOURCES-94
> URL: https://issues.apache.org/jira/browse/MSOURCES-94
> Project: Maven Source Plugin
> Issue Type: Bug
>Affects Versions: 3.0.0
> Environment: Apache Maven 3.3.9
> (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00)
> Java version: 1.8.0_74, vendor: Oracle Corporation
> OS name: "linux", version: "3.19.0-32-generic", arch: "amd64", family: "unix"
>Reporter: Stephan Schroevers
>
> After upgrading from version 2.4 to 3.0.0 our aggregate build (comprising 52
> jar/war modules) started failing when run on Travis CI:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-source-plugin:3.0.0:jar-no-fork
> (generate-source-jar) on project etl-executor-impl: Error creating source
> archive: Problem creating jar: Execution exception: Java heap space -> [Help
> 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-source-plugin:3.0.0:jar-no-fork
> (generate-source-jar) on project etl-executor-impl: Error creating source
> archive: Problem creating jar: Execution exception
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
> 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.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:188)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:184)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error creating
> source archive: Problem creating jar: Execution exception
> at
> org.apache.maven.plugins.source.AbstractSourceJarMojo.packageSources(AbstractSourceJarMojo.java:311)
> at
> org.apache.maven.plugins.source.AbstractSourceJarMojo.packageSources(AbstractSourceJarMojo.java:253)
> at
> org.apache.maven.plugins.source.AbstractSourceJarMojo.execute(AbstractSourceJarMojo.java:216)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> ... 11 more
> Caused by: org.codehaus.plexus.archiver.ArchiverException: Problem creating
> jar: Execution exception
> at
> org.codehaus.plexus.archiver.AbstractArchiver.createArchive(AbstractArchiver.java:982)
> at
> org.apache.maven.archiver.MavenArchiver.createArchive(MavenArchiver.java:650)
> at
> org.apache.maven.plugins.source.AbstractSourceJarMojo.packageSources(AbstractSourceJarMojo.java:303)
> ... 15 more
> Caused by: java.io.IOException: Execution exception
> at
> org.codehaus.plexus.archiver.zip.AbstractZipArchiver.close(AbstractZipArchiver.java:807)
> at
> org.codehaus.plexus.archiver.AbstractArchiver.createArchive(AbstractArchiver.java:969)
> ... 17 more
> Caused by: java.lang.OutOfMemoryError: Java heap space
> at
> org.codehaus.plexus.archiver.zip.ByteArrayOutputStream.needNewBuffer(ByteArrayOutputStream.java:121)
> at
> org.codehaus.plexus.archiver.zip.ByteArrayOutputStream.(ByteArrayOutputStream.java:90)
> at
> org.codehaus.plexus.archiver.zip.OffloadingOutputStream.(OffloadingOutputStream.java:109)
> at
> org.codehaus.plexus.archiver.zip.OffloadingOutputStream.(OffloadingOutputStream.java:89)
> at
> org.codehaus.plexus.archiver.zip.DeferredScatterOutputStream.(DeferredScatterOutputStream.java:28)
> at
> org.codehaus.plexus.archiver.zip.ConcurrentJarCreator$DeferredSupplier.get(ConcurrentJarCreator.java:47)
> at
> org.apache.commons.compress.archivers.zip.ParallelScatterZipCreator.createDeferred(ParallelScatterZipCreator.java:75)
> at
> org.apache.commons.compress.archivers.zip.ParallelScatterZipCreator.access$100(ParallelScatte
[jira] [Comment Edited] (MSITE-768) maven-site-plugin 3.5 breaks Velocity
[
https://issues.apache.org/jira/browse/MSITE-768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15172680#comment-15172680
]
Michael Osipov edited comment on MSITE-768 at 2/29/16 10:05 PM:
I have tested your sample project and am able to confirm that this is not a bug
in MSITE. There are two issues with Doxia Sitetools and Plexus Velocity
component.
1. The configured Site Renderer Component misses to pass the following property
to the Velocity engine:
{code}
eventhandler.include.class
org.apache.velocity.app.event.implement.IncludeRelativePath
{code}
2. All custom resource loaders, whether from Sitetools or Plexus Velocity, are
crap. The do not stick to the contract from the abstract {{ResourceLoader}}
class.
Ultimately, due to the first issue, your {{include.vm}} is not make absolute to
{{index.md.vm}} and second throws an NPE because the first loader does not find
your included template in the classpath. No one checks for a {{null}} after
{{getResourceAsStream}}.
Please open for both appropriate issues, I will close this one and process the
others. As far as I can see, the resource loaders provided by Velocity should
do it in most cases.
was (Author: michael-o):
I have tested your sample project and am able to confirm that this is not a bug
in MSITE. There are two issues with Doxia Sitetools and Plexus Velocity
component.
1. The configured Site Renderer Component misses to pass the following property
to the Velocity engine:
{code}
eventhandler.include.class
org.apache.velocity.app.event.implement.IncludeRelativePath
{code}
2. All custom resource loaders, whether from Sitetools or Plexus Velocity, are
crap. The do not stick to the contract from the abstract {{ResourceLoader}}
class.
Ultimately, due to the first issue, your {{include.vm}} is not make absolute to
{{index.md.vm}} and second throws an NPE because the first loader does not find
your included template in the classpath. No one checks for a {{null}} after
{{getResourceAsStream}}.
Please open for both appropriate issues, I will close this one and process the
others.
> maven-site-plugin 3.5 breaks Velocity
> -
>
> Key: MSITE-768
> URL: https://issues.apache.org/jira/browse/MSITE-768
> Project: Maven Site Plugin
> Issue Type: Bug
>Affects Versions: 3.5
> Environment: $ mvn --version
> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
> 2015-11-10T17:41:47+01:00)
> Maven home: /usr/local/Cellar/maven/3.3.9/libexec
> Java version: 1.8.0_74, vendor: Oracle Corporation
> Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_74.jdk/Contents/Home/jre
> Default locale: de_DE, platform encoding: UTF-8
> OS name: "mac os x", version: "10.11.3", arch: "x86_64", family: "mac"
>Reporter: Christian Schlichtherle
>Priority: Blocker
> Attachments: msite-768.zip
>
>
> It seem like since version 3.5, I cannot use {{#parse}} or {{#include}} in
> Velocity filtered templates anymore. See attached test project.
> Please note that it doesn't matter what the name of the file to parse is. You
> can even change it to a non-existent file (e.g. "foo") and it all still abort
> unnecessary recursion.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (MSITE-768) maven-site-plugin 3.5 breaks Velocity
[
https://issues.apache.org/jira/browse/MSITE-768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15172680#comment-15172680
]
Michael Osipov edited comment on MSITE-768 at 2/29/16 9:52 PM:
---
I have tested your sample project and am able to confirm that this is not a bug
in MSITE. There are two issues with Doxia Sitetools and Plexus Velocity
component.
1. The configured Site Renderer Component misses to pass the following property
to the Velocity engine:
{code}
eventhandler.include.class
org.apache.velocity.app.event.implement.IncludeRelativePath
{code}
2. All custom resource loaders, whether from Sitetools or Plexus Velocity, are
crap. The do not stick to the contract from the abstract {{ResourceLoader}}
class.
Ultimately, due to the first issue, your {{include.vm}} is not make absolute to
{{index.md.vm}} and second throws an NPE because the first loader does not find
your included template in the classpath. No one checks for a {{null}} after
{{getResourceAsStream}}.
Please open for both appropriate issues, I will close this one and process the
others.
was (Author: michael-o):
I have tested your sample project and am able to confirm that this is not a bug
in MSITE. There are two issues with Doxia Sitetools and Plexus Velocity
component.
1. The configured Site Renderer Component misses to pass the following property
to the Velocity engine:
{format}
eventhandler.include.class
org.apache.velocity.app.event.implement.IncludeRelativePath
{format}
2. All custom resource loaders, whether from Sitetools or Plexus Velocity, are
crap. The do not stick to the contract from the abstract {{ResourceLoader}}
class.
Ultimately, due to the first issue, your {{include.vm}} is not make absolute to
{{index.md.vm}} and second throws an NPE because the first loader does not find
your included template in the classpath. No one checks for a {{null}} after
{{getResourceAsStream}}.
Please open for both appropriate issues, I will close this one and process the
others.
> maven-site-plugin 3.5 breaks Velocity
> -
>
> Key: MSITE-768
> URL: https://issues.apache.org/jira/browse/MSITE-768
> Project: Maven Site Plugin
> Issue Type: Bug
>Affects Versions: 3.5
> Environment: $ mvn --version
> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
> 2015-11-10T17:41:47+01:00)
> Maven home: /usr/local/Cellar/maven/3.3.9/libexec
> Java version: 1.8.0_74, vendor: Oracle Corporation
> Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_74.jdk/Contents/Home/jre
> Default locale: de_DE, platform encoding: UTF-8
> OS name: "mac os x", version: "10.11.3", arch: "x86_64", family: "mac"
>Reporter: Christian Schlichtherle
>Priority: Blocker
> Attachments: msite-768.zip
>
>
> It seem like since version 3.5, I cannot use {{#parse}} or {{#include}} in
> Velocity filtered templates anymore. See attached test project.
> Please note that it doesn't matter what the name of the file to parse is. You
> can even change it to a non-existent file (e.g. "foo") and it all still abort
> unnecessary recursion.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MSITE-768) maven-site-plugin 3.5 breaks Velocity
[
https://issues.apache.org/jira/browse/MSITE-768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15172680#comment-15172680
]
Michael Osipov commented on MSITE-768:
--
I have tested your sample project and am able to confirm that this is not a bug
in MSITE. There are two issues with Doxia Sitetools and Plexus Velocity
component.
1. The configured Site Renderer Component misses to pass the following property
to the Velocity engine:
{format}
eventhandler.include.class
org.apache.velocity.app.event.implement.IncludeRelativePath
{format}
2. All custom resource loaders, whether from Sitetools or Plexus Velocity, are
crap. The do not stick to the contract from the abstract {{ResourceLoader}}
class.
Ultimately, due to the first issue, your {{include.vm}} is not make absolute to
{{index.md.vm}} and second throws an NPE because the first loader does not find
your included template in the classpath. No one checks for a {{null}} after
{{getResourceAsStream}}.
Please open for both appropriate issues, I will close this one and process the
others.
> maven-site-plugin 3.5 breaks Velocity
> -
>
> Key: MSITE-768
> URL: https://issues.apache.org/jira/browse/MSITE-768
> Project: Maven Site Plugin
> Issue Type: Bug
>Affects Versions: 3.5
> Environment: $ mvn --version
> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
> 2015-11-10T17:41:47+01:00)
> Maven home: /usr/local/Cellar/maven/3.3.9/libexec
> Java version: 1.8.0_74, vendor: Oracle Corporation
> Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_74.jdk/Contents/Home/jre
> Default locale: de_DE, platform encoding: UTF-8
> OS name: "mac os x", version: "10.11.3", arch: "x86_64", family: "mac"
>Reporter: Christian Schlichtherle
>Priority: Blocker
> Attachments: msite-768.zip
>
>
> It seem like since version 3.5, I cannot use {{#parse}} or {{#include}} in
> Velocity filtered templates anymore. See attached test project.
> Please note that it doesn't matter what the name of the file to parse is. You
> can even change it to a non-existent file (e.g. "foo") and it all still abort
> unnecessary recursion.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MPDF-78) Compatibility with doxia-module-docbook-simple 1.7
[
https://issues.apache.org/jira/browse/MPDF-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15172181#comment-15172181
]
Hervé Boutemy commented on MPDF-78:
---
ok, I just had a look: I didn't commit the Doxia 1.7 upgrade
I'll do it this WE (not at home currently...) and I'll report for you to check
> Compatibility with doxia-module-docbook-simple 1.7
> --
>
> Key: MPDF-78
> URL: https://issues.apache.org/jira/browse/MPDF-78
> Project: Maven PDF Plugin
> Issue Type: Improvement
>Affects Versions: 1.3
>Reporter: Denis Braud
>
> maven-pdf-plugin 1.3 became incompatible with doxia-module-docbook-simple
> last version (1.7).
> [ERROR] 1) Error in custom provider, java.lang.TypeNotPresentException: Type
> org.apache.maven.doxia.module.docbook.DocBookSiteModule not present
> DocBookSiteModule has been removed in 1.7 :
> see https://issues.apache.org/jira/browse/DOXIA-511 : remove deprecated
> o.a.m.doxia.module.site package (- DocBookSiteModule)
> pom Configuration :
> {code:xml}
> maven-pdf-plugin
> 1.3
>
>
> org.apache.maven.doxia
> doxia-module-docbook-simple
> 1.7
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MPDF-78) Compatibility with doxia-module-docbook-simple 1.7
[
https://issues.apache.org/jira/browse/MPDF-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15172165#comment-15172165
]
Denis Braud commented on MPDF-78:
-
Same error with trunk (maven-pdf-plugin 1.4-SNAPSHOT).
> Compatibility with doxia-module-docbook-simple 1.7
> --
>
> Key: MPDF-78
> URL: https://issues.apache.org/jira/browse/MPDF-78
> Project: Maven PDF Plugin
> Issue Type: Improvement
>Affects Versions: 1.3
>Reporter: Denis Braud
>
> maven-pdf-plugin 1.3 became incompatible with doxia-module-docbook-simple
> last version (1.7).
> [ERROR] 1) Error in custom provider, java.lang.TypeNotPresentException: Type
> org.apache.maven.doxia.module.docbook.DocBookSiteModule not present
> DocBookSiteModule has been removed in 1.7 :
> see https://issues.apache.org/jira/browse/DOXIA-511 : remove deprecated
> o.a.m.doxia.module.site package (- DocBookSiteModule)
> pom Configuration :
> {code:xml}
> maven-pdf-plugin
> 1.3
>
>
> org.apache.maven.doxia
> doxia-module-docbook-simple
> 1.7
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MSITE-769) Can't use property in breadcrumbs items in child module site descriptor
[
https://issues.apache.org/jira/browse/MSITE-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15172082#comment-15172082
]
Hervé Boutemy commented on MSITE-769:
-
we knew that there were some cleanups that could cause such local issues: then
we did the immediate breaking changes in the same row
now, let's fix the subtle "expected unexpected" breaks :)
> Can't use property in breadcrumbs items in child module site descriptor
> ---
>
> Key: MSITE-769
> URL: https://issues.apache.org/jira/browse/MSITE-769
> Project: Maven Site Plugin
> Issue Type: Bug
> Components: inheritance, site descriptor
>Affects Versions: 3.5
>Reporter: Tony Chemit
>Priority: Critical
> Attachments: MSITE-769.zip
>
>
> In a multi-module project, I have this in pom module site descriptor
> {noformat}
>
>
>href="${project.url}/v/${siteDeployClassifier}/en/index.html"/>
>
> {noformat}
> While running mvn site, the build fail with this error :
> {noformat}
> Caused by: java.lang.IllegalArgumentException: Illegal character in path at
> index 1: ${project.url}/index.html
> at java.net.URI.create(URI.java:852)
> at
> org.apache.maven.doxia.site.decoration.inheritance.URIPathDescriptor.(URIPathDescriptor.java:69)
> at
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler$URLContainer.rebaseLink(DefaultDecorationModelInheritanceAssembler.java:453)
> at
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.rebaseLinkItemPaths(DefaultDecorationModelInheritanceAssembler.java:300)
> at
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.mergeLinkItemLists(DefaultDecorationModelInheritanceAssembler.java:326)
> at
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.assembleBodyInheritance(DefaultDecorationModelInheritanceAssembler.java:228)
> at
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.assembleModelInheritance(DefaultDecorationModelInheritanceAssembler.java:109)
> at
> org.apache.maven.doxia.tools.DefaultSiteTool.getDecorationModel(DefaultSiteTool.java:1171)
> at
> org.apache.maven.doxia.tools.DefaultSiteTool.getDecorationModel(DefaultSiteTool.java:423)
> at
> org.apache.maven.plugins.site.descriptor.AbstractSiteDescriptorMojo.prepareDecorationModel(AbstractSiteDescriptorMojo.java:86)
> at
> org.apache.maven.plugins.site.render.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:279)
> at
> org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.java:151)
> at
> org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:135)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> ... 21 more
> Caused by: java.net.URISyntaxException: Illegal character in path at index 1:
> ${project.url}/index.html
> at java.net.URI$Parser.fail(URI.java:2848)
> at java.net.URI$Parser.checkChars(URI.java:3021)
> at java.net.URI$Parser.parseHierarchical(URI.java:3105)
> at java.net.URI$Parser.parse(URI.java:3063)
> at java.net.URI.(URI.java:588)
> at java.net.URI.create(URI.java:850)
> ... 34 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MSITE-769) Can't use property in breadcrumbs items in child module site descriptor
[
https://issues.apache.org/jira/browse/MSITE-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15172076#comment-15172076
]
Tony Chemit commented on MSITE-769:
---
Ok, so 3.5 is a breaking version arf :( Not a good news to me. Let me know if I
can help. thanks for the short notice reply [~michael-o] and [~hboutemy]
> Can't use property in breadcrumbs items in child module site descriptor
> ---
>
> Key: MSITE-769
> URL: https://issues.apache.org/jira/browse/MSITE-769
> Project: Maven Site Plugin
> Issue Type: Bug
> Components: inheritance, site descriptor
>Affects Versions: 3.5
>Reporter: Tony Chemit
>Priority: Critical
> Attachments: MSITE-769.zip
>
>
> In a multi-module project, I have this in pom module site descriptor
> {noformat}
>
>
>href="${project.url}/v/${siteDeployClassifier}/en/index.html"/>
>
> {noformat}
> While running mvn site, the build fail with this error :
> {noformat}
> Caused by: java.lang.IllegalArgumentException: Illegal character in path at
> index 1: ${project.url}/index.html
> at java.net.URI.create(URI.java:852)
> at
> org.apache.maven.doxia.site.decoration.inheritance.URIPathDescriptor.(URIPathDescriptor.java:69)
> at
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler$URLContainer.rebaseLink(DefaultDecorationModelInheritanceAssembler.java:453)
> at
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.rebaseLinkItemPaths(DefaultDecorationModelInheritanceAssembler.java:300)
> at
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.mergeLinkItemLists(DefaultDecorationModelInheritanceAssembler.java:326)
> at
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.assembleBodyInheritance(DefaultDecorationModelInheritanceAssembler.java:228)
> at
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.assembleModelInheritance(DefaultDecorationModelInheritanceAssembler.java:109)
> at
> org.apache.maven.doxia.tools.DefaultSiteTool.getDecorationModel(DefaultSiteTool.java:1171)
> at
> org.apache.maven.doxia.tools.DefaultSiteTool.getDecorationModel(DefaultSiteTool.java:423)
> at
> org.apache.maven.plugins.site.descriptor.AbstractSiteDescriptorMojo.prepareDecorationModel(AbstractSiteDescriptorMojo.java:86)
> at
> org.apache.maven.plugins.site.render.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:279)
> at
> org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.java:151)
> at
> org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:135)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> ... 21 more
> Caused by: java.net.URISyntaxException: Illegal character in path at index 1:
> ${project.url}/index.html
> at java.net.URI$Parser.fail(URI.java:2848)
> at java.net.URI$Parser.checkChars(URI.java:3021)
> at java.net.URI$Parser.parseHierarchical(URI.java:3105)
> at java.net.URI$Parser.parse(URI.java:3063)
> at java.net.URI.(URI.java:588)
> at java.net.URI.create(URI.java:850)
> ... 34 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MPDF-78) Compatibility with doxia-module-docbook-simple 1.7
[
https://issues.apache.org/jira/browse/MPDF-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15172073#comment-15172073
]
Hervé Boutemy commented on MPDF-78:
---
yes, this was expected: we need to do a new release
did you try to use trunk and compile it for yourself, to confirm that it works
for you as expected?
I think I updated code when doing the changes, but I'm not sure integration
tests are very good: then having a real world check would be a good feedback
> Compatibility with doxia-module-docbook-simple 1.7
> --
>
> Key: MPDF-78
> URL: https://issues.apache.org/jira/browse/MPDF-78
> Project: Maven PDF Plugin
> Issue Type: Improvement
>Affects Versions: 1.3
>Reporter: Denis Braud
>
> maven-pdf-plugin 1.3 became incompatible with doxia-module-docbook-simple
> last version (1.7).
> [ERROR] 1) Error in custom provider, java.lang.TypeNotPresentException: Type
> org.apache.maven.doxia.module.docbook.DocBookSiteModule not present
> DocBookSiteModule has been removed in 1.7 :
> see https://issues.apache.org/jira/browse/DOXIA-511 : remove deprecated
> o.a.m.doxia.module.site package (- DocBookSiteModule)
> pom Configuration :
> {code:xml}
> maven-pdf-plugin
> 1.3
>
>
> org.apache.maven.doxia
> doxia-module-docbook-simple
> 1.7
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MPDF-78) Compatibility with doxia-module-docbook-simple 1.7
[
https://issues.apache.org/jira/browse/MPDF-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated MPDF-78:
--
Description:
maven-pdf-plugin 1.3 became incompatible with doxia-module-docbook-simple last
version (1.7).
[ERROR] 1) Error in custom provider, java.lang.TypeNotPresentException: Type
org.apache.maven.doxia.module.docbook.DocBookSiteModule not present
DocBookSiteModule has been removed in 1.7 :
see https://issues.apache.org/jira/browse/DOXIA-511 : remove deprecated
o.a.m.doxia.module.site package (- DocBookSiteModule)
pom Configuration :
{code:xml}
maven-pdf-plugin
1.3
org.apache.maven.doxia
doxia-module-docbook-simple
1.7
{code}
was:
maven-pdf-plugin 1.3 became incompatible with doxia-module-docbook-simple last
version (1.7).
[ERROR] 1) Error in custom provider, java.lang.TypeNotPresentException: Type
org.apache.maven.doxia.module.docbook.DocBookSiteModule not present
DocBookSiteModule has been removed in 1.7 :
see https://issues.apache.org/jira/browse/DOXIA-511 : remove deprecated
o.a.m.doxia.module.site package (- DocBookSiteModule)
pom Configuration :
maven-pdf-plugin
1.3
org.apache.maven.doxia
doxia-module-docbook-simple
1.7
> Compatibility with doxia-module-docbook-simple 1.7
> --
>
> Key: MPDF-78
> URL: https://issues.apache.org/jira/browse/MPDF-78
> Project: Maven PDF Plugin
> Issue Type: Improvement
>Affects Versions: 1.3
>Reporter: Denis Braud
>
> maven-pdf-plugin 1.3 became incompatible with doxia-module-docbook-simple
> last version (1.7).
> [ERROR] 1) Error in custom provider, java.lang.TypeNotPresentException: Type
> org.apache.maven.doxia.module.docbook.DocBookSiteModule not present
> DocBookSiteModule has been removed in 1.7 :
> see https://issues.apache.org/jira/browse/DOXIA-511 : remove deprecated
> o.a.m.doxia.module.site package (- DocBookSiteModule)
> pom Configuration :
> {code:xml}
> maven-pdf-plugin
> 1.3
>
>
> org.apache.maven.doxia
> doxia-module-docbook-simple
> 1.7
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MSITE-769) Can't use property in breadcrumbs items in child module site descriptor
[
https://issues.apache.org/jira/browse/MSITE-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15172065#comment-15172065
]
Hervé Boutemy commented on MSITE-769:
-
I suppose this is related to MSITE-135: values are interpolated later in the
effective model calculation
the issue with relative urls calculations on inermediate (now non-interpolated)
value is an unexpected side effect
when working on all this, I found at least 2 or 3 ways of calculating relative
paths, each with its own algorithm: I didn't take time to really detect which
were the limitations for each case (there was for example the case for Maven
pseudo urls like {{dav:https://...}})
it seems we'll have to take time to work on one super-well tested
implementation, supporting not only special protocols like {{dav}}, but also
content with non-interpolated properties
> Can't use property in breadcrumbs items in child module site descriptor
> ---
>
> Key: MSITE-769
> URL: https://issues.apache.org/jira/browse/MSITE-769
> Project: Maven Site Plugin
> Issue Type: Bug
> Components: inheritance, site descriptor
>Affects Versions: 3.5
>Reporter: Tony Chemit
>Priority: Critical
> Attachments: MSITE-769.zip
>
>
> In a multi-module project, I have this in pom module site descriptor
> {noformat}
>
>
>href="${project.url}/v/${siteDeployClassifier}/en/index.html"/>
>
> {noformat}
> While running mvn site, the build fail with this error :
> {noformat}
> Caused by: java.lang.IllegalArgumentException: Illegal character in path at
> index 1: ${project.url}/index.html
> at java.net.URI.create(URI.java:852)
> at
> org.apache.maven.doxia.site.decoration.inheritance.URIPathDescriptor.(URIPathDescriptor.java:69)
> at
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler$URLContainer.rebaseLink(DefaultDecorationModelInheritanceAssembler.java:453)
> at
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.rebaseLinkItemPaths(DefaultDecorationModelInheritanceAssembler.java:300)
> at
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.mergeLinkItemLists(DefaultDecorationModelInheritanceAssembler.java:326)
> at
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.assembleBodyInheritance(DefaultDecorationModelInheritanceAssembler.java:228)
> at
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.assembleModelInheritance(DefaultDecorationModelInheritanceAssembler.java:109)
> at
> org.apache.maven.doxia.tools.DefaultSiteTool.getDecorationModel(DefaultSiteTool.java:1171)
> at
> org.apache.maven.doxia.tools.DefaultSiteTool.getDecorationModel(DefaultSiteTool.java:423)
> at
> org.apache.maven.plugins.site.descriptor.AbstractSiteDescriptorMojo.prepareDecorationModel(AbstractSiteDescriptorMojo.java:86)
> at
> org.apache.maven.plugins.site.render.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:279)
> at
> org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.java:151)
> at
> org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:135)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> ... 21 more
> Caused by: java.net.URISyntaxException: Illegal character in path at index 1:
> ${project.url}/index.html
> at java.net.URI$Parser.fail(URI.java:2848)
> at java.net.URI$Parser.checkChars(URI.java:3021)
> at java.net.URI$Parser.parseHierarchical(URI.java:3105)
> at java.net.URI$Parser.parse(URI.java:3063)
> at java.net.URI.(URI.java:588)
> at java.net.URI.create(URI.java:850)
> ... 34 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MSITE-769) Can't use property in breadcrumbs items in child module site descriptor
[
https://issues.apache.org/jira/browse/MSITE-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15172063#comment-15172063
]
Michael Osipov commented on MSITE-769:
--
Maybe a regression from MSITE-135?
> Can't use property in breadcrumbs items in child module site descriptor
> ---
>
> Key: MSITE-769
> URL: https://issues.apache.org/jira/browse/MSITE-769
> Project: Maven Site Plugin
> Issue Type: Bug
> Components: inheritance, site descriptor
>Affects Versions: 3.5
>Reporter: Tony Chemit
>Priority: Critical
> Attachments: MSITE-769.zip
>
>
> In a multi-module project, I have this in pom module site descriptor
> {noformat}
>
>
>href="${project.url}/v/${siteDeployClassifier}/en/index.html"/>
>
> {noformat}
> While running mvn site, the build fail with this error :
> {noformat}
> Caused by: java.lang.IllegalArgumentException: Illegal character in path at
> index 1: ${project.url}/index.html
> at java.net.URI.create(URI.java:852)
> at
> org.apache.maven.doxia.site.decoration.inheritance.URIPathDescriptor.(URIPathDescriptor.java:69)
> at
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler$URLContainer.rebaseLink(DefaultDecorationModelInheritanceAssembler.java:453)
> at
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.rebaseLinkItemPaths(DefaultDecorationModelInheritanceAssembler.java:300)
> at
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.mergeLinkItemLists(DefaultDecorationModelInheritanceAssembler.java:326)
> at
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.assembleBodyInheritance(DefaultDecorationModelInheritanceAssembler.java:228)
> at
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.assembleModelInheritance(DefaultDecorationModelInheritanceAssembler.java:109)
> at
> org.apache.maven.doxia.tools.DefaultSiteTool.getDecorationModel(DefaultSiteTool.java:1171)
> at
> org.apache.maven.doxia.tools.DefaultSiteTool.getDecorationModel(DefaultSiteTool.java:423)
> at
> org.apache.maven.plugins.site.descriptor.AbstractSiteDescriptorMojo.prepareDecorationModel(AbstractSiteDescriptorMojo.java:86)
> at
> org.apache.maven.plugins.site.render.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:279)
> at
> org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.java:151)
> at
> org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:135)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> ... 21 more
> Caused by: java.net.URISyntaxException: Illegal character in path at index 1:
> ${project.url}/index.html
> at java.net.URI$Parser.fail(URI.java:2848)
> at java.net.URI$Parser.checkChars(URI.java:3021)
> at java.net.URI$Parser.parseHierarchical(URI.java:3105)
> at java.net.URI$Parser.parse(URI.java:3063)
> at java.net.URI.(URI.java:588)
> at java.net.URI.create(URI.java:850)
> ... 34 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MSITE-769) Can't use property in breadcrumbs items in child module site descriptor
[
https://issues.apache.org/jira/browse/MSITE-769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tony Chemit updated MSITE-769:
--
Attachment: MSITE-769.zip
> Can't use property in breadcrumbs items in child module site descriptor
> ---
>
> Key: MSITE-769
> URL: https://issues.apache.org/jira/browse/MSITE-769
> Project: Maven Site Plugin
> Issue Type: Bug
> Components: inheritance, site descriptor
>Affects Versions: 3.5
>Reporter: Tony Chemit
>Priority: Critical
> Attachments: MSITE-769.zip
>
>
> In a multi-module project, I have this in pom module site descriptor
> {noformat}
>
>
>href="${project.url}/v/${siteDeployClassifier}/en/index.html"/>
>
> {noformat}
> While running mvn site, the build fail with this error :
> {noformat}
> Caused by: java.lang.IllegalArgumentException: Illegal character in path at
> index 1: ${project.url}/index.html
> at java.net.URI.create(URI.java:852)
> at
> org.apache.maven.doxia.site.decoration.inheritance.URIPathDescriptor.(URIPathDescriptor.java:69)
> at
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler$URLContainer.rebaseLink(DefaultDecorationModelInheritanceAssembler.java:453)
> at
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.rebaseLinkItemPaths(DefaultDecorationModelInheritanceAssembler.java:300)
> at
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.mergeLinkItemLists(DefaultDecorationModelInheritanceAssembler.java:326)
> at
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.assembleBodyInheritance(DefaultDecorationModelInheritanceAssembler.java:228)
> at
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.assembleModelInheritance(DefaultDecorationModelInheritanceAssembler.java:109)
> at
> org.apache.maven.doxia.tools.DefaultSiteTool.getDecorationModel(DefaultSiteTool.java:1171)
> at
> org.apache.maven.doxia.tools.DefaultSiteTool.getDecorationModel(DefaultSiteTool.java:423)
> at
> org.apache.maven.plugins.site.descriptor.AbstractSiteDescriptorMojo.prepareDecorationModel(AbstractSiteDescriptorMojo.java:86)
> at
> org.apache.maven.plugins.site.render.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:279)
> at
> org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.java:151)
> at
> org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:135)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> ... 21 more
> Caused by: java.net.URISyntaxException: Illegal character in path at index 1:
> ${project.url}/index.html
> at java.net.URI$Parser.fail(URI.java:2848)
> at java.net.URI$Parser.checkChars(URI.java:3021)
> at java.net.URI$Parser.parseHierarchical(URI.java:3105)
> at java.net.URI$Parser.parse(URI.java:3063)
> at java.net.URI.(URI.java:588)
> at java.net.URI.create(URI.java:850)
> ... 34 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MSITE-769) Can't use property in breadcrumbs items in child module site descriptor
[
https://issues.apache.org/jira/browse/MSITE-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15171942#comment-15171942
]
Tony Chemit commented on MSITE-769:
---
The problem only occurs when I use a site descriptor coming from a parent
module.
In the example I give to you if you comment the parent in the pom.xml
everything is ok.
What I suspect is that if a site descriptor attribute coming from a parent does
not resolv variables in it.
In the example I give to you, you can see in the parent site descriptor I put
{noformat}
http://docutils.sourceforge.net/rst.html"; name="ReStructuredText"
img="${someUrl}/images/logos/restructuredtext-logo.png"/>
{noformat}
which is well rendered, but in the child module I got this error
{noformat}
Caused by: java.lang.IllegalArgumentException: Illegal character in path at
index 1: ${someUrl}/images/logos/restructuredtext-logo.png
at java.net.URI.create(URI.java:852)
at
org.apache.maven.doxia.site.decoration.inheritance.URIPathDescriptor.(URIPathDescriptor.java:69)
at
org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler$URLContainer.rebaseLink(DefaultDecorationModelInheritanceAssembler.java:453)
at
org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.rebaseLogoPaths(DefaultDecorationModelInheritanceAssembler.java:311)
at
org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.mergePoweredByLists(DefaultDecorationModelInheritanceAssembler.java:361)
at
org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.assembleModelInheritance(DefaultDecorationModelInheritanceAssembler.java:87)
at
org.apache.maven.doxia.tools.DefaultSiteTool.getDecorationModel(DefaultSiteTool.java:1171)
at
org.apache.maven.doxia.tools.DefaultSiteTool.getDecorationModel(DefaultSiteTool.java:423)
at
org.apache.maven.plugins.site.descriptor.AbstractSiteDescriptorMojo.prepareDecorationModel(AbstractSiteDescriptorMojo.java:86)
at
org.apache.maven.plugins.site.render.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:279)
at
org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.java:151)
at
org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:135)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
{noformat}
> Can't use property in breadcrumbs items in child module site descriptor
> ---
>
> Key: MSITE-769
> URL: https://issues.apache.org/jira/browse/MSITE-769
> Project: Maven Site Plugin
> Issue Type: Bug
> Components: inheritance, site descriptor
>Affects Versions: 3.5
>Reporter: Tony Chemit
>Priority: Critical
>
> In a multi-module project, I have this in pom module site descriptor
> {noformat}
>
>
>href="${project.url}/v/${siteDeployClassifier}/en/index.html"/>
>
> {noformat}
> While running mvn site, the build fail with this error :
> {noformat}
> Caused by: java.lang.IllegalArgumentException: Illegal character in path at
> index 1: ${project.url}/index.html
> at java.net.URI.create(URI.java:852)
> at
> org.apache.maven.doxia.site.decoration.inheritance.URIPathDescriptor.(URIPathDescriptor.java:69)
> at
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler$URLContainer.rebaseLink(DefaultDecorationModelInheritanceAssembler.java:453)
> at
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.rebaseLinkItemPaths(DefaultDecorationModelInheritanceAssembler.java:300)
> at
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.mergeLinkItemLists(DefaultDecorationModelInheritanceAssembler.java:326)
> at
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.assembleBodyInheritance(DefaultDecorationModelInheritanceAssembler.java:228)
> at
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.assembleModelInheritance(DefaultDecorationModelInheritanceAssembler.java:109)
> at
> org.apache.maven.doxia.tools.DefaultSiteTool.getDecorationModel(DefaultSiteTool.java:1171)
> at
> org.apache.maven.doxia.tools.DefaultSiteTool.getDecorationModel(DefaultSiteTool.java:423)
> at
> org.apache.maven.plugins.site.descriptor.AbstractSiteDescriptorMojo.prepareDecorationModel(AbstractSiteDescriptorMojo.java:86)
> at
> org.apache.maven.plugins.site.render.AbstractSiteRenderingMojo.createSiteRenderingContext
[jira] [Comment Edited] (MENFORCER-248) Upgrading maven-enforcer-plugin to 1.4.1 breaks maven-assembly-plugin
[
https://issues.apache.org/jira/browse/MENFORCER-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15171821#comment-15171821
]
Blazej Checinski edited comment on MENFORCER-248 at 2/29/16 12:42 PM:
--
I had a look into the logs.
Basing on the previous error: {noformat}MENFORCER-42 is an important
improvement, it seems to have a side-effect: even though dependencies are now
calculated instead of gathered, the artifact is still marked as resolved
afterwards.
The assembly-plugin checks if the artifacts is resolved, otherwise i'll search
the local and remote repositories for the files. ( The NPE is caused by the
artifact.getFile() ).{noformat}
https://issues.apache.org/jira/browse/MENFORCER-156?focusedCommentId=14436085&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14436085
What should I upgrade? There is the same issue with assembly 2.6 and enforcer
1.4.1 - which are up to date.
was (Author: hakamairi):
I had a look into the logs.
Basing on the previous error: {noformat}MENFORCER-42 is an important
improvement, it seems to have a side-effect: even though dependencies are now
calculated instead of gathered, the artifact is still marked as resolved
afterwards. The assembly-plugin checks if the artifacts is resolved, otherwise
i'll search the local and remote repositories for the files. ( The NPE is
caused by the artifact.getFile() ).{noformat}
https://issues.apache.org/jira/browse/MENFORCER-156?focusedCommentId=14436085&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14436085
What should I upgrade? There is the same issue with assembly 2.6 and enforcer
1.4.1 - which are up to date.
> Upgrading maven-enforcer-plugin to 1.4.1 breaks maven-assembly-plugin
> -
>
> Key: MENFORCER-248
> URL: https://issues.apache.org/jira/browse/MENFORCER-248
> Project: Maven Enforcer Plugin
> Issue Type: Bug
> Components: Plugin
>Reporter: Blazej Checinski
>Assignee: Karl Heinz Marbaise
> Fix For: 1.4.1
>
> Attachments: extjars.xml, pom.xml
>
>
> After upgrading m-e-p from 1.4 to 1.4.1 the maven-assembly-plugin generates
> the following error:
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-assembly-plugin:2.4:single (assemble) on
> project extjars: Execution assemble of goal
> org.apache.maven.plugins:maven-assembly-plugin:2.4:single failed.
> NullPointerException -> [Help 1]
> Downgrading to m-e-p 1.4 makes the assembly work again.
> Sample pom & assembly that expose the error attached.
> When called via:
> mvn -Dplugins.maven-enforcer-plugin.version=1.4
> a zip file is generated as expected, when called via
> mvn -Dplugins.maven-enforcer-plugin.version=1.4.1
> (or without argument) you will get the NPE.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MENFORCER-248) Upgrading maven-enforcer-plugin to 1.4.1 breaks maven-assembly-plugin
[
https://issues.apache.org/jira/browse/MENFORCER-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15171821#comment-15171821
]
Blazej Checinski commented on MENFORCER-248:
I had a look into the logs.
Basing on the previous error: {noformat}MENFORCER-42 is an important
improvement, it seems to have a side-effect: even though dependencies are now
calculated instead of gathered, the artifact is still marked as resolved
afterwards. The assembly-plugin checks if the artifacts is resolved, otherwise
i'll search the local and remote repositories for the files. ( The NPE is
caused by the artifact.getFile() ).{noformat}
https://issues.apache.org/jira/browse/MENFORCER-156?focusedCommentId=14436085&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14436085
What should I upgrade? There is the same issue with assembly 2.6 and enforcer
1.4.1 - which are up to date.
> Upgrading maven-enforcer-plugin to 1.4.1 breaks maven-assembly-plugin
> -
>
> Key: MENFORCER-248
> URL: https://issues.apache.org/jira/browse/MENFORCER-248
> Project: Maven Enforcer Plugin
> Issue Type: Bug
> Components: Plugin
>Reporter: Blazej Checinski
>Assignee: Karl Heinz Marbaise
> Fix For: 1.4.1
>
> Attachments: extjars.xml, pom.xml
>
>
> After upgrading m-e-p from 1.4 to 1.4.1 the maven-assembly-plugin generates
> the following error:
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-assembly-plugin:2.4:single (assemble) on
> project extjars: Execution assemble of goal
> org.apache.maven.plugins:maven-assembly-plugin:2.4:single failed.
> NullPointerException -> [Help 1]
> Downgrading to m-e-p 1.4 makes the assembly work again.
> Sample pom & assembly that expose the error attached.
> When called via:
> mvn -Dplugins.maven-enforcer-plugin.version=1.4
> a zip file is generated as expected, when called via
> mvn -Dplugins.maven-enforcer-plugin.version=1.4.1
> (or without argument) you will get the NPE.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MSITE-769) Can't use property in breadcrumbs items in child module site descriptor
[
https://issues.apache.org/jira/browse/MSITE-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15171716#comment-15171716
]
Michael Osipov commented on MSITE-769:
--
Sample project?
> Can't use property in breadcrumbs items in child module site descriptor
> ---
>
> Key: MSITE-769
> URL: https://issues.apache.org/jira/browse/MSITE-769
> Project: Maven Site Plugin
> Issue Type: Bug
> Components: inheritance, site descriptor
>Affects Versions: 3.5
>Reporter: Tony Chemit
>Priority: Critical
>
> In a multi-module project, I have this in pom module site descriptor
> {noformat}
>
>
>href="${project.url}/v/${siteDeployClassifier}/en/index.html"/>
>
> {noformat}
> While running mvn site, the build fail with this error :
> {noformat}
> Caused by: java.lang.IllegalArgumentException: Illegal character in path at
> index 1: ${project.url}/index.html
> at java.net.URI.create(URI.java:852)
> at
> org.apache.maven.doxia.site.decoration.inheritance.URIPathDescriptor.(URIPathDescriptor.java:69)
> at
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler$URLContainer.rebaseLink(DefaultDecorationModelInheritanceAssembler.java:453)
> at
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.rebaseLinkItemPaths(DefaultDecorationModelInheritanceAssembler.java:300)
> at
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.mergeLinkItemLists(DefaultDecorationModelInheritanceAssembler.java:326)
> at
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.assembleBodyInheritance(DefaultDecorationModelInheritanceAssembler.java:228)
> at
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.assembleModelInheritance(DefaultDecorationModelInheritanceAssembler.java:109)
> at
> org.apache.maven.doxia.tools.DefaultSiteTool.getDecorationModel(DefaultSiteTool.java:1171)
> at
> org.apache.maven.doxia.tools.DefaultSiteTool.getDecorationModel(DefaultSiteTool.java:423)
> at
> org.apache.maven.plugins.site.descriptor.AbstractSiteDescriptorMojo.prepareDecorationModel(AbstractSiteDescriptorMojo.java:86)
> at
> org.apache.maven.plugins.site.render.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:279)
> at
> org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.java:151)
> at
> org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:135)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> ... 21 more
> Caused by: java.net.URISyntaxException: Illegal character in path at index 1:
> ${project.url}/index.html
> at java.net.URI$Parser.fail(URI.java:2848)
> at java.net.URI$Parser.checkChars(URI.java:3021)
> at java.net.URI$Parser.parseHierarchical(URI.java:3105)
> at java.net.URI$Parser.parse(URI.java:3063)
> at java.net.URI.(URI.java:588)
> at java.net.URI.create(URI.java:850)
> ... 34 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MSITE-769) Can't use property in breadcrumbs items in child module site descriptor
[
https://issues.apache.org/jira/browse/MSITE-769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MSITE-769:
-
Fix Version/s: (was: 3.6)
> Can't use property in breadcrumbs items in child module site descriptor
> ---
>
> Key: MSITE-769
> URL: https://issues.apache.org/jira/browse/MSITE-769
> Project: Maven Site Plugin
> Issue Type: Bug
> Components: inheritance, site descriptor
>Affects Versions: 3.5
>Reporter: Tony Chemit
>Priority: Critical
>
> In a multi-module project, I have this in pom module site descriptor
> {noformat}
>
>
>href="${project.url}/v/${siteDeployClassifier}/en/index.html"/>
>
> {noformat}
> While running mvn site, the build fail with this error :
> {noformat}
> Caused by: java.lang.IllegalArgumentException: Illegal character in path at
> index 1: ${project.url}/index.html
> at java.net.URI.create(URI.java:852)
> at
> org.apache.maven.doxia.site.decoration.inheritance.URIPathDescriptor.(URIPathDescriptor.java:69)
> at
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler$URLContainer.rebaseLink(DefaultDecorationModelInheritanceAssembler.java:453)
> at
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.rebaseLinkItemPaths(DefaultDecorationModelInheritanceAssembler.java:300)
> at
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.mergeLinkItemLists(DefaultDecorationModelInheritanceAssembler.java:326)
> at
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.assembleBodyInheritance(DefaultDecorationModelInheritanceAssembler.java:228)
> at
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.assembleModelInheritance(DefaultDecorationModelInheritanceAssembler.java:109)
> at
> org.apache.maven.doxia.tools.DefaultSiteTool.getDecorationModel(DefaultSiteTool.java:1171)
> at
> org.apache.maven.doxia.tools.DefaultSiteTool.getDecorationModel(DefaultSiteTool.java:423)
> at
> org.apache.maven.plugins.site.descriptor.AbstractSiteDescriptorMojo.prepareDecorationModel(AbstractSiteDescriptorMojo.java:86)
> at
> org.apache.maven.plugins.site.render.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:279)
> at
> org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.java:151)
> at
> org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:135)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> ... 21 more
> Caused by: java.net.URISyntaxException: Illegal character in path at index 1:
> ${project.url}/index.html
> at java.net.URI$Parser.fail(URI.java:2848)
> at java.net.URI$Parser.checkChars(URI.java:3021)
> at java.net.URI$Parser.parseHierarchical(URI.java:3105)
> at java.net.URI$Parser.parse(URI.java:3063)
> at java.net.URI.(URI.java:588)
> at java.net.URI.create(URI.java:850)
> ... 34 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MSITE-769) Can't use property in breadcrumbs items in child module site descriptor
Tony Chemit created MSITE-769:
-
Summary: Can't use property in breadcrumbs items in child module
site descriptor
Key: MSITE-769
URL: https://issues.apache.org/jira/browse/MSITE-769
Project: Maven Site Plugin
Issue Type: Bug
Components: inheritance, site descriptor
Affects Versions: 3.5
Reporter: Tony Chemit
Priority: Critical
Fix For: 3.6
In a multi-module project, I have this in pom module site descriptor
{noformat}
{noformat}
While running mvn site, the build fail with this error :
{noformat}
Caused by: java.lang.IllegalArgumentException: Illegal character in path at
index 1: ${project.url}/index.html
at java.net.URI.create(URI.java:852)
at
org.apache.maven.doxia.site.decoration.inheritance.URIPathDescriptor.(URIPathDescriptor.java:69)
at
org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler$URLContainer.rebaseLink(DefaultDecorationModelInheritanceAssembler.java:453)
at
org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.rebaseLinkItemPaths(DefaultDecorationModelInheritanceAssembler.java:300)
at
org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.mergeLinkItemLists(DefaultDecorationModelInheritanceAssembler.java:326)
at
org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.assembleBodyInheritance(DefaultDecorationModelInheritanceAssembler.java:228)
at
org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.assembleModelInheritance(DefaultDecorationModelInheritanceAssembler.java:109)
at
org.apache.maven.doxia.tools.DefaultSiteTool.getDecorationModel(DefaultSiteTool.java:1171)
at
org.apache.maven.doxia.tools.DefaultSiteTool.getDecorationModel(DefaultSiteTool.java:423)
at
org.apache.maven.plugins.site.descriptor.AbstractSiteDescriptorMojo.prepareDecorationModel(AbstractSiteDescriptorMojo.java:86)
at
org.apache.maven.plugins.site.render.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:279)
at
org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.java:151)
at
org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:135)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
... 21 more
Caused by: java.net.URISyntaxException: Illegal character in path at index 1:
${project.url}/index.html
at java.net.URI$Parser.fail(URI.java:2848)
at java.net.URI$Parser.checkChars(URI.java:3021)
at java.net.URI$Parser.parseHierarchical(URI.java:3105)
at java.net.URI$Parser.parse(URI.java:3063)
at java.net.URI.(URI.java:588)
at java.net.URI.create(URI.java:850)
... 34 more
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MPDF-78) Compatibility with doxia-module-docbook-simple 1.7
Denis Braud created MPDF-78: --- Summary: Compatibility with doxia-module-docbook-simple 1.7 Key: MPDF-78 URL: https://issues.apache.org/jira/browse/MPDF-78 Project: Maven PDF Plugin Issue Type: Improvement Affects Versions: 1.3 Reporter: Denis Braud maven-pdf-plugin 1.3 became incompatible with doxia-module-docbook-simple last version (1.7). [ERROR] 1) Error in custom provider, java.lang.TypeNotPresentException: Type org.apache.maven.doxia.module.docbook.DocBookSiteModule not present DocBookSiteModule has been removed in 1.7 : see https://issues.apache.org/jira/browse/DOXIA-511 : remove deprecated o.a.m.doxia.module.site package (- DocBookSiteModule) pom Configuration : maven-pdf-plugin 1.3 org.apache.maven.doxia doxia-module-docbook-simple 1.7 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
