[jira] [Created] (DOXIA-671) Double quotes contained in markdown page are removed in html output
Friederich Christophe created DOXIA-671: --- Summary: Double quotes contained in markdown page are removed in html output Key: DOXIA-671 URL: https://issues.apache.org/jira/browse/DOXIA-671 Project: Maven Doxia Issue Type: Bug Components: Module - Markdown Affects Versions: 2.0.0-M3 Reporter: Friederich Christophe When execute site generation, the double quotes contained in markdown page are removed in html output. After investigation, in MarkdownParser class, the flexmark renderer uses TypographicExtension and by default flexmark replaces double quotes with “ and ”, but theses entities are not recognized by XmlPullParser. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] (ARCHETYPE-406) Support of velocity expressions for user-defined properties
[
https://jira.codehaus.org/browse/ARCHETYPE-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=297509#comment-297509
]
Bue Pierre-Christophe edited comment on ARCHETYPE-406 at 4/30/12 5:06 AM:
--
I can bring more precision.
I have attached an example of the issue. When user-defined propertes are
specified, only the first is correctly evaluated (i think it is, but i'm not
quite sure ...).
In the example, i ask for two properties : propA and propB. i capitalize these
two properties, and use it in two ways : inner use (on text filtering, with
$propA for example), and file name filtering. On both, capitalizePropA is
correctly evaluated, but capitalizePropB is neither evaluated as propA with
capitalizePropA.
Here is the interesting part of the archetype generation log :
Define value for property 'capitalizePropA':
${propA.substring(0,1).toUpperCase()}${propA.substring(1)}: :
Define value for property 'capitalizePropB':
${propB.substring(0,1).toUpperCase()}${propB.substring(1)}: :
Define value for property 'propA': : valA
Define value for property 'propB': : valB
Confirm properties configuration:
groupId: group
artifactId: art
version: 1.0.0-SNAPSHOT
package: group
capitalizePropA: ${propA.substring(0,1).toUpperCase()}${propA.substring(1)}
capitalizePropB: ${propB.substring(0,1).toUpperCase()}${propB.substring(1)}
propA: valA
propB: valB
For the moment, all is ok. But velocity complains on the resolution of
capitalizePropB on effective generation :
[INFO]
[INFO] Using following parameters for creating project from Archetype: test:1
[INFO]
[INFO] Parameter: groupId, Value: group
[INFO] Parameter: artifactId, Value: art
[INFO] Parameter: version, Value: 1.0.0-SNAPSHOT
[INFO] Parameter: package, Value: group
[INFO] Parameter: packageInPathFormat, Value: group
[INFO] Parameter: propA, Value: valA
30 avr. 2012 12:03:34 org.apache.velocity.runtime.log.JdkLogChute log
INFO: FileResourceLoader : adding path '.'
30 avr. 2012 12:03:34 org.apache.velocity.runtime.log.JdkLogChute log
INFO: Null reference [template 'capitalizePropB', line 1, column 1] :
${propB.substring(0,1).toUpperCase()} cannot be resolved.
30 avr. 2012 12:03:34 org.apache.velocity.runtime.log.JdkLogChute log
INFO: Null reference [template 'capitalizePropB', line 1, column 38] :
${propB.substring(1)} cannot be resolved.
[INFO] Parameter: capitalizePropB, Value:
${propB.substring(0,1).toUpperCase()}${propB.substring(1)}
[INFO] Parameter: capitalizePropA, Value: ValA
[INFO] Parameter: package, Value: group
[INFO] Parameter: version, Value: 1.0.0-SNAPSHOT
[INFO] Parameter: groupId, Value: group
[INFO] Parameter: propB, Value: valB
[INFO] Parameter: artifactId, Value: art
[INFO] project created from Archetype in dir: /home/pcbue/test/plop/art
[INFO]
[INFO] BUILD SUCCESS
was (Author: pcbue):
I can bring more precision.
I have attached an example of the issue. When user-defined propertes are
specified, only the first is correctly evaluated (i think it is, but i'm not
quite sure ...).
> Support of velocity expressions for user-defined properties
> ---
>
> Key: ARCHETYPE-406
> URL: https://jira.codehaus.org/browse/ARCHETYPE-406
> Project: Maven Archetype
> Issue Type: Bug
> Components: Plugin
>Affects Versions: 2.x
>Reporter: Bue Pierre-Christophe
> Attachments: sample-archetype406.tar.gz
>
>
> Standard properties (artifactId, groupId, ...) are supported in Velocity
> expressiosn, but still does not work with user defined properties. For
> example:
>
> ${artifactId}.substring(0,1).toUpperCase()
>
> with artifactId=toto will give a=T, but
>
>
> ${b}.substring(0,1).toUpperCase()
>
> with b=toto will give a=${b}.substring(0,1).toUpperCase()
--
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
[jira] (ARCHETYPE-406) Support of velocity expressions for user-defined properties
[
https://jira.codehaus.org/browse/ARCHETYPE-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=297509#comment-297509
]
Bue Pierre-Christophe edited comment on ARCHETYPE-406 at 4/30/12 4:58 AM:
--
I can bring more precision.
I have attached an example of the issue. When user-defined propertes are
specified, only the first is correctly evaluated (i think it is, but i'm not
quite sure ...).
was (Author: pcbue):
Archetype example
> Support of velocity expressions for user-defined properties
> ---
>
> Key: ARCHETYPE-406
> URL: https://jira.codehaus.org/browse/ARCHETYPE-406
> Project: Maven Archetype
> Issue Type: Bug
> Components: Plugin
>Affects Versions: 2.x
>Reporter: Bue Pierre-Christophe
> Attachments: sample-archetype406.tar.gz
>
>
> Standard properties (artifactId, groupId, ...) are supported in Velocity
> expressiosn, but still does not work with user defined properties. For
> example:
>
> ${artifactId}.substring(0,1).toUpperCase()
>
> with artifactId=toto will give a=T, but
>
>
> ${b}.substring(0,1).toUpperCase()
>
> with b=toto will give a=${b}.substring(0,1).toUpperCase()
--
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
[jira] (ARCHETYPE-406) Support of velocity expressions for user-defined properties
[
https://jira.codehaus.org/browse/ARCHETYPE-406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bue Pierre-Christophe updated ARCHETYPE-406:
Attachment: sample-archetype406.tar.gz
Archetype example
> Support of velocity expressions for user-defined properties
> ---
>
> Key: ARCHETYPE-406
> URL: https://jira.codehaus.org/browse/ARCHETYPE-406
> Project: Maven Archetype
> Issue Type: Bug
> Components: Plugin
>Affects Versions: 2.x
>Reporter: Bue Pierre-Christophe
> Attachments: sample-archetype406.tar.gz
>
>
> Standard properties (artifactId, groupId, ...) are supported in Velocity
> expressiosn, but still does not work with user defined properties. For
> example:
>
> ${artifactId}.substring(0,1).toUpperCase()
>
> with artifactId=toto will give a=T, but
>
>
> ${b}.substring(0,1).toUpperCase()
>
> with b=toto will give a=${b}.substring(0,1).toUpperCase()
--
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
[jira] (ARCHETYPE-406) Support of velocity expressions for user-defined properties
[
https://jira.codehaus.org/browse/ARCHETYPE-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=297172#comment-297172
]
Bue Pierre-Christophe commented on ARCHETYPE-406:
-
Not exactly.
ACRHETYPE-397 deals with a problem in the display on the use of standard
properties, such as artifactId.substring, and so on, but they are correctly
evaluate by Velocity in the generation step of the archetype.
This bug wants to manage correctly the use of user-defined properties in the
same way standard properties are, such as the description of this bug
spotlights.
> Support of velocity expressions for user-defined properties
> ---
>
> Key: ARCHETYPE-406
> URL: https://jira.codehaus.org/browse/ARCHETYPE-406
> Project: Maven Archetype
> Issue Type: Bug
> Components: Plugin
>Affects Versions: 2.x
>Reporter: Bue Pierre-Christophe
>
> Standard properties (artifactId, groupId, ...) are supported in Velocity
> expressiosn, but still does not work with user defined properties. For
> example:
>
> ${artifactId}.substring(0,1).toUpperCase()
>
> with artifactId=toto will give a=T, but
>
>
> ${b}.substring(0,1).toUpperCase()
>
> with b=toto will give a=${b}.substring(0,1).toUpperCase()
--
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
[jira] (ARCHETYPE-383) Use velocity expressions in descriptor properties
[
https://jira.codehaus.org/browse/ARCHETYPE-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=296689#comment-296689
]
Bue Pierre-Christophe commented on ARCHETYPE-383:
-
done with [ARCHETYPE-406|https://jira.codehaus.org/browse/ARCHETYPE-406]
> Use velocity expressions in descriptor properties
> -
>
> Key: ARCHETYPE-383
> URL: https://jira.codehaus.org/browse/ARCHETYPE-383
> Project: Maven Archetype
> Issue Type: New Feature
> Components: Plugin
>Affects Versions: 2.1
>Reporter: Emmanuel Hugonnet
>Assignee: Olivier Lamy
> Fix For: 2.2
>
> Attachments: patch_jira_383.patch
>
>
> The descriptor can use velocity expressions for value and defaultValue, thus
> enabling the creation of velocity global properties for an archetype.
> For example :
>
>
> ${rootArtifactId.substring(0,1).toUpperCase()}${rootArtifactId.substring(1)}
>
--
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
[jira] (ARCHETYPE-406) Support of velocity expressions for user-defined properties
Bue Pierre-Christophe created ARCHETYPE-406:
---
Summary: Support of velocity expressions for user-defined
properties
Key: ARCHETYPE-406
URL: https://jira.codehaus.org/browse/ARCHETYPE-406
Project: Maven Archetype
Issue Type: Bug
Components: Plugin
Affects Versions: 2.x
Reporter: Bue Pierre-Christophe
Standard properties (artifactId, groupId, ...) are supported in Velocity
expressiosn, but still does not work with user defined properties. For example:
${artifactId}.substring(0,1).toUpperCase()
with artifactId=toto will give a=T, but
${b}.substring(0,1).toUpperCase()
with b=toto will give a=${b}.substring(0,1).toUpperCase()
--
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
[jira] (ARCHETYPE-383) Use velocity expressions in descriptor properties
[
https://jira.codehaus.org/browse/ARCHETYPE-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=296310#comment-296310
]
Bue Pierre-Christophe commented on ARCHETYPE-383:
-
the bug fiw worked fine for standard properties (artifactId, groupId, ...), but
still does not work with user defined properties. For example:
${artifactId}.substring(0,1).toUpperCase()
with artifactId=toto will give a=T, but
${b}.substring(0,1).toUpperCase()
with b=toto will give a=${b}.substring(0,1).toUpperCase()
> Use velocity expressions in descriptor properties
> -
>
> Key: ARCHETYPE-383
> URL: https://jira.codehaus.org/browse/ARCHETYPE-383
> Project: Maven Archetype
> Issue Type: New Feature
> Components: Plugin
>Affects Versions: 2.1
>Reporter: Emmanuel Hugonnet
>Assignee: Olivier Lamy
> Fix For: 2.2
>
> Attachments: patch_jira_383.patch
>
>
> The descriptor can use velocity expressions for value and defaultValue, thus
> enabling the creation of velocity global properties for an archetype.
> For example :
>
>
> ${rootArtifactId.substring(0,1).toUpperCase()}${rootArtifactId.substring(1)}
>
--
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
[jira] Commented: (MECLIPSE-132) "Class not found" when run/debug JUnit tests
[ http://jira.codehaus.org/browse/MECLIPSE-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=182954#action_182954 ] Christophe commented on MECLIPSE-132: - Still no luck for me. Running on STS 2.1 / Eclipse 3.4, I still get a classnotfound when running src/test/java/com/xxx/ActionTest.java which uses src/main/java/com/xxx/Action.java class. I tried to enble Marven Dependencies Management, update project configuration, still no luck. I disabled Dependencies Management, try again, no luck. Tried to put marven dependencies before JRE System Library. No luck again. I don't understand the problem. I have an other project that I receive from a training class, which work, but nothing seems to be different. I analyzed all parameters of the project, no huge difference Does anyone as another idea? > "Class not found" when run/debug JUnit tests > > > Key: MECLIPSE-132 > URL: http://jira.codehaus.org/browse/MECLIPSE-132 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: Core : Dependencies resolution and build path > (.classpath), M2Eclipse support > Environment: gentoo linux 2006, kernel 2.6, sun-jdk-1.5.0.06, maven > 2.0.4, eclipse sdk 3.2, myeclipse 5 m2 >Reporter: Diego Ballve > Attachments: maven-sample.zip > > > This is for the behavior described in > http://www.nabble.com/Keep-getting-%22Class-not-found%22-when-running-debugging-JUnit-tests-tf1851758.html#a5442440 > You get "Class not found" when running/debuging JUnit tests. > For me it happened when I was importing another project and its dependencies > (both m2 projects). > Clean compile works fine, problem is with run. > The workaround to get it working is: > In the project containing your tests, edit Java Build Path | Order and > Export: Make sure M2 Dependencies appears BEFORE JRE System Library. > Thanks, > Diego -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCHECKSTYLE-76) don't check the test code
[
http://jira.codehaus.org/browse/MCHECKSTYLE-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_104984
]
kerboriou christophe commented on MCHECKSTYLE-76:
-
{code}
org.apache.maven.plugins
maven-checkstyle-plugin
xml
true
http://///checkstyle_config.xml
{code}
> don't check the test code
> -
>
> Key: MCHECKSTYLE-76
> URL: http://jira.codehaus.org/browse/MCHECKSTYLE-76
> Project: Maven 2.x Checkstyle Plugin
> Issue Type: Bug
>Affects Versions: 2.1
> Environment: windos, standar conf projet (juste parent pom)
>Reporter: kerboriou christophe
>Priority: Critical
> Fix For: 2.2
>
>
> the parm for excute checkstyle on test code was at true. and i have this log
> {panel} [DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-checkstyle-plugin:2.1:checkstyle' -->
> [DEBUG] (f) cacheFile =
> D:\workspaces\workspace\{sous-projet}\target/checkstyle-cachefile
> [DEBUG] (f) configLocation = http://///checkstyle_config.xml
> [DEBUG] (f) consoleOutput = false
> [DEBUG] (f) enableFilesSummary = true
> [DEBUG] (f) enableRSS = true
> [DEBUG] (f) enableRulesSummary = true
> [DEBUG] (f) enableSeveritySummary = true
> [DEBUG] (f) failsOnError = false
> [DEBUG] (f) format = sun
> [DEBUG] (f) headerFile = D:\workspaces\workspace\{sous-projet}\LICENSE.txt
> [DEBUG] (f) headerLocation = LICENSE.txt
> [DEBUG] (f) includes = **/*.java
> [DEBUG] (f) linkXRef = true
> [DEBUG] (f) outputDirectory =
> D:\workspaces\workspace\{sous-projet}\target\site
> [DEBUG] (f) outputFile =
> D:\workspaces\workspace\{sous-projet}\target\checkstyle-result.xml
> [DEBUG] (f) outputFileFormat = xml
> [DEBUG] (f) project = [EMAIL PROTECTED]
> [DEBUG] {color:red} *(f) sourceDirectory =
> D:\workspaces\workspace\{sous-projet}\src\main\java*{color}
> [DEBUG] (f) xrefLocation =
> D:\workspaces\workspace\{sous-projet}\target\site\xref
> [DEBUG] -- end configuration --
> [INFO] [checkstyle:checkstyle]
> [DEBUG] resolveLocation(http://///checkstyle_config.xml,
> checkstyle-checker.xml)
> [DEBUG] Potential URL: http://///checkstyle_config.xml
> [DEBUG] resolveLocation(null, checkstyle-checker.properties)
> [DEBUG] resolveLocation(LICENSE.txt, checkstyle-header.txt)
> [DEBUG] Location is not a URL.
> [DEBUG] Location is not a File.
> [DEBUG] Potential Resource:
> jar:file:/C:/dev/maven/bin/../lib/jsch-0.1.24.jar!/LICENSE.txt
> [DEBUG] resolveLocation(null, checkstyle-packages.xml)
> [DEBUG] resolveLocation(null, checkstyle-suppressions.xml)
> [DEBUG] File D:\workspaces\workspace\{sous-projet}\target\site/checkstyle.rss
> created...{panel}
> the src/test/java wasn't use.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MCHECKSTYLE-76) don't check the test code
don't check the test code
-
Key: MCHECKSTYLE-76
URL: http://jira.codehaus.org/browse/MCHECKSTYLE-76
Project: Maven 2.x Checkstyle Plugin
Issue Type: Bug
Affects Versions: 2.1
Environment: windos, standar conf projet (juste parent pom)
Reporter: kerboriou christophe
Priority: Critical
Fix For: 2.2
the parm for excute checkstyle on test code was at true. and i have this log
{panel} [DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-checkstyle-plugin:2.1:checkstyle' -->
[DEBUG] (f) cacheFile =
D:\workspaces\workspace\{sous-projet}\target/checkstyle-cachefile
[DEBUG] (f) configLocation = http://///checkstyle_config.xml
[DEBUG] (f) consoleOutput = false
[DEBUG] (f) enableFilesSummary = true
[DEBUG] (f) enableRSS = true
[DEBUG] (f) enableRulesSummary = true
[DEBUG] (f) enableSeveritySummary = true
[DEBUG] (f) failsOnError = false
[DEBUG] (f) format = sun
[DEBUG] (f) headerFile = D:\workspaces\workspace\{sous-projet}\LICENSE.txt
[DEBUG] (f) headerLocation = LICENSE.txt
[DEBUG] (f) includes = **/*.java
[DEBUG] (f) linkXRef = true
[DEBUG] (f) outputDirectory =
D:\workspaces\workspace\{sous-projet}\target\site
[DEBUG] (f) outputFile =
D:\workspaces\workspace\{sous-projet}\target\checkstyle-result.xml
[DEBUG] (f) outputFileFormat = xml
[DEBUG] (f) project = [EMAIL PROTECTED]
[DEBUG] {color:red} *(f) sourceDirectory =
D:\workspaces\workspace\{sous-projet}\src\main\java*{color}
[DEBUG] (f) xrefLocation =
D:\workspaces\workspace\{sous-projet}\target\site\xref
[DEBUG] -- end configuration --
[INFO] [checkstyle:checkstyle]
[DEBUG] resolveLocation(http://///checkstyle_config.xml,
checkstyle-checker.xml)
[DEBUG] Potential URL: http://///checkstyle_config.xml
[DEBUG] resolveLocation(null, checkstyle-checker.properties)
[DEBUG] resolveLocation(LICENSE.txt, checkstyle-header.txt)
[DEBUG] Location is not a URL.
[DEBUG] Location is not a File.
[DEBUG] Potential Resource:
jar:file:/C:/dev/maven/bin/../lib/jsch-0.1.24.jar!/LICENSE.txt
[DEBUG] resolveLocation(null, checkstyle-packages.xml)
[DEBUG] resolveLocation(null, checkstyle-suppressions.xml)
[DEBUG] File D:\workspaces\workspace\{sous-projet}\target\site/checkstyle.rss
created...{panel}
the src/test/java wasn't use.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
