[jira] (MSKINS-95) Doxia 1.6 puts a line break between div and pre, pretty print is broken

2014-12-28 Thread Rautureau (JIRA) 

[ 
https://jira.codehaus.org/browse/MSKINS-95?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=359842#comment-359842
 ] 

Rautureau commented on MSKINS-95:
-

thanks

 Doxia 1.6 puts a line break between div and pre, pretty print is broken
 ---

 Key: MSKINS-95
 URL: https://jira.codehaus.org/browse/MSKINS-95
 Project: Maven Skins
  Issue Type: Bug
  Components: Fluido Skin
Affects Versions: fluido-1.3.1
 Environment: Maven v3.0.5
Reporter: Rautureau
 Attachments: 3.2.png, 3.3.png, maven-site-example.zip


 Hi,
 you will find in attachment a maven project that shows the issue.
 When you run the command {{mvn site}} you get:
 !3.2.png!
 When you run the command {{mvn site -Dmaven.site.plugin.version=3.3}} you get 
 !3.3.png!
 By comparing html produce by maven-site-plugin:
 * With 3.2, all snippets are in tag pre class=prettyprint linenumssome 
 code/pre
 * With 3.3, all snippets are in tag presome code/pre
 This is why the fluido skin .js don't activate color syntax nor line 
 numbering.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

[jira] (MSITE-696) site:deploy try to deploy the site of a sub module even if the property maven.site.skip is set to true

2013-09-12 Thread Rautureau (JIRA) 
Rautureau created MSITE-696:
---

 Summary: site:deploy try to deploy the site of a sub module even 
if the property maven.site.skip is set to true
 Key: MSITE-696
 URL: https://jira.codehaus.org/browse/MSITE-696
 Project: Maven Site Plugin
  Issue Type: Bug
  Components: multi module, site:deploy
Affects Versions: 3.2
 Environment: Maven 3.0.5
Reporter: Rautureau


Hi,

when deploying a site of a multi module project (using {{mvn site-deploy}}),  
the deploy goal tell me that the site cannot be deployed because it has no been 
generated:
{code}
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-site-plugin:3.2:deploy (default-deploy) on 
project um-cgum: The site does not exist, please run site:site first - [Help 1]
{code}
It's true because I set in the submodule {{um-cgum}} the property 
{{maven.site.skip}} to true.
When I set the property {{maven.site.deploy.skip}} to true, the deploy goal 
skip the deployment, which is fine.
Why not skipping deployment if the site generation is skipped?

thanks 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] (MSITE-692) The maven-site-plugin v3.3 does not render snippets as in v3.2 (Syntax highlighting and line numbers)

2013-07-04 Thread Rautureau (JIRA) 
Rautureau created MSITE-692:
---

 Summary: The maven-site-plugin v3.3 does not render snippets as in 
v3.2 (Syntax highlighting and line numbers)
 Key: MSITE-692
 URL: https://jira.codehaus.org/browse/MSITE-692
 Project: Maven 2.x and 3.x Site Plugin
  Issue Type: Bug
  Components: doxia integration
Affects Versions: 3.3
 Environment: Maven v3.0.5
Reporter: Rautureau
 Attachments: 3.2.png, 3.3.png, maven-site-example.zip

Hi,

you will find in attachment a maven project that shows the issue.
When you run the command {{mvn site}} you get:
!3.2.png

When you run the command {{mvn site -Dmaven.site.plugin.version=3.3}} you get 
!3.3.png!

By comparing html produce by maven-site-plugin:
* With 3.2, all snippets are in tag pre class=prettyprint linenumssome 
code/pre
* With 3.3, all snippets are in tag presome code/pre

This is why the fluido skin .js don't activate color syntax nor line numbering.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] (MRELEASE-555) update versions does not update intermodule dependencies

2012-04-16 Thread Rautureau (JIRA) 

[ 
https://jira.codehaus.org/browse/MRELEASE-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=296558#comment-296558
 ] 

Rautureau commented on MRELEASE-555:


The problem still there with version 2.2.1 and 2.2.2 of the plugin

 update versions does not update intermodule dependencies
 

 Key: MRELEASE-555
 URL: https://jira.codehaus.org/browse/MRELEASE-555
 Project: Maven 2.x Release Plugin
  Issue Type: Bug
  Components: update-versions
Affects Versions: 2.0
 Environment: Maven 2.2.1, JDK 6, XP SP3
Reporter: Michael Osipov

 I recently tried the update-versions goal which is really nice and worked 
 well. I cleaned my local repo today and reran mvn package on a multi-module 
 project. It failed due tue a depenceny error.
 My project was previously on version 2.6.1-SNAPSHOT. Module war depends on 
 module jar with the same version. When doing a release:prepare, the plugin  
 perfectly bumps this intermodule dependency. The release:update-versions 
 missed that dep spot. My build process failed.
 The goal should crawl for those deps too and update them if 
 autoVersionSubmodules is on. (Same behavior as the prepare goal)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira