[jira] [Created] (DOXIA-538) Tag used for monospaced is not a valid html5 tag
Ievgen Degtiarenko created DOXIA-538: Summary: Tag used for monospaced is not a valid html5 tag Key: DOXIA-538 URL: https://issues.apache.org/jira/browse/DOXIA-538 Project: Maven Doxia Issue Type: Bug Components: Core, Module - Xdoc, Module - Xhtml Affects Versions: 1.6 Reporter: Ievgen Degtiarenko -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (DOXIA-538) Tag used for monospaced is not a valid html5 tag
[ https://issues.apache.org/jira/browse/DOXIA-538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ievgen Degtiarenko updated DOXIA-538: - Attachment: monospaced_for_doxia.patch > Tag used for monospaced is not a valid html5 tag > -- > > Key: DOXIA-538 > URL: https://issues.apache.org/jira/browse/DOXIA-538 > Project: Maven Doxia > Issue Type: Bug > Components: Core, Module - Xdoc, Module - Xhtml >Affects Versions: 1.6 >Reporter: Ievgen Degtiarenko > Attachments: monospaced_for_doxia.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (DOXIA-538) Tag used for monospaced is not a valid html5 tag
[ https://issues.apache.org/jira/browse/DOXIA-538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ievgen Degtiarenko updated DOXIA-538: - Description: https://maven.apache.org/doxia/references/apt-format.html <<>> is converted into Monospaced that is not valid tag in html5 Attached patch replaces tag with that is the most common tag that is displayed as monospaced text in modern browsers. > Tag used for monospaced is not a valid html5 tag > -- > > Key: DOXIA-538 > URL: https://issues.apache.org/jira/browse/DOXIA-538 > Project: Maven Doxia > Issue Type: Bug > Components: Core, Module - Xdoc, Module - Xhtml >Affects Versions: 1.6 >Reporter: Ievgen Degtiarenko > Attachments: monospaced_for_doxia.patch > > > https://maven.apache.org/doxia/references/apt-format.html > <<>> is converted into Monospaced that is not valid tag > in html5 > Attached patch replaces tag with that is the most common tag that > is displayed as monospaced text in modern browsers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DOXIA-538) Tag used for monospaced is not a valid html5 tag
[
https://issues.apache.org/jira/browse/DOXIA-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15107049#comment-15107049
]
Christian Schulte commented on DOXIA-538:
-
{code:xml}
http://www.w3.org/1999/xhtml"; xml:lang="en" lang="en">
{code}
Doxia currently does not produce HTML5.
{code}
{code}
would be a better replacement for
{code}
{code}
IMHO.
> Tag used for monospaced is not a valid html5 tag
> --
>
> Key: DOXIA-538
> URL: https://issues.apache.org/jira/browse/DOXIA-538
> Project: Maven Doxia
> Issue Type: Bug
> Components: Core, Module - Xdoc, Module - Xhtml
>Affects Versions: 1.6
>Reporter: Ievgen Degtiarenko
> Attachments: monospaced_for_doxia.patch
>
>
> https://maven.apache.org/doxia/references/apt-format.html
> <<>> is converted into Monospaced that is not valid tag
> in html5
> Attached patch replaces tag with that is the most common tag that
> is displayed as monospaced text in modern browsers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (MNG-5934) String handling issues identified by PMD
[ https://issues.apache.org/jira/browse/MNG-5934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulte closed MNG-5934. -- Resolution: Fixed Assignee: Christian Schulte (was: Michael Osipov) Fix Version/s: 3.4.0 > String handling issues identified by PMD > > > Key: MNG-5934 > URL: https://issues.apache.org/jira/browse/MNG-5934 > Project: Maven > Issue Type: Improvement >Affects Versions: 3.3.9 >Reporter: Alex Henrie >Assignee: Christian Schulte >Priority: Minor > Labels: easyfix, newbie, patch, performance > Fix For: 3.4.0 > > Attachments: > 0001-Prefer-StringBuilder.append-char-to-StringBuilder.ap.patch, > 0002-Prefer-String.indexOf-char-to-String.indexOf-String.patch, > 0003-Combine-string-literals-instead-of-calling-String.ap.patch, > 0004-Construct-StringBuffers-with-enough-space-to-begin-w.patch > > > The code linting tool [PMD|http://pmd.sourceforge.net/pmd-5.2.0/] identified > numerous places where Maven's string handling is inefficient. I've prepared a > set of patches that should help speed things up. > The command I used was `pmd -d . -R java-strings` -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNG-5934) String handling issues identified by PMD
[ https://issues.apache.org/jira/browse/MNG-5934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15107544#comment-15107544 ] Hudson commented on MNG-5934: - SUCCESS: Integrated in maven-3.x #1195 (See [https://builds.apache.org/job/maven-3.x/1195/]) [MNG-5934] String handling issues identified by PMD Submitted by: Alex (schulte: rev 2d3b5811566190b52840e27cd04eb26bd02bb1b4) * maven-embedder/src/main/java/org/apache/maven/cli/MavenCli.java * maven-compat/src/main/java/org/apache/maven/repository/metadata/MetadataGraphVertex.java * maven-core/src/main/java/org/apache/maven/project/MavenProject.java * maven-compat/src/main/java/org/apache/maven/repository/metadata/MetadataGraph.java * maven-artifact/src/main/java/org/apache/maven/artifact/repository/ArtifactRepositoryPolicy.java * maven-compat/src/test/java/org/apache/maven/project/LegacyLocalRepositoryManager.java * maven-compat/src/main/java/org/apache/maven/artifact/versioning/ManagedVersionMap.java * maven-builder-support/src/main/java/org/apache/maven/building/DefaultProblem.java * maven-artifact/src/main/java/org/apache/maven/artifact/versioning/Restriction.java * maven-core/src/main/java/org/apache/maven/artifact/repository/MavenArtifactRepository.java * maven-core/src/main/java/org/apache/maven/lifecycle/LifecycleExecutionException.java * maven-core/src/main/java/org/apache/maven/plugin/PluginParameterExpressionEvaluator.java * maven-core/src/main/java/org/apache/maven/artifact/repository/metadata/AbstractRepositoryMetadata.java * maven-embedder/src/main/java/org/apache/maven/cli/logging/impl/UnsupportedSlf4jBindingConfiguration.java * maven-core/src/main/java/org/apache/maven/repository/ArtifactTransferEvent.java * maven-artifact/src/main/java/org/apache/maven/artifact/versioning/DefaultArtifactVersion.java * maven-embedder/src/test/java/org/apache/maven/cli/CLIManagerDocumentationTest.java * maven-plugin-api/src/main/java/org/apache/maven/plugin/MojoNotFoundException.java * maven-artifact/src/main/java/org/apache/maven/artifact/versioning/VersionRange.java * maven-model-builder/src/main/java/org/apache/maven/model/building/ModelProblemUtils.java * maven-core/src/test/java/org/apache/maven/project/LegacyLocalRepositoryManager.java * maven-compat/src/main/java/org/apache/maven/project/validation/ModelValidationResult.java * maven-core/src/main/java/org/apache/maven/repository/legacy/metadata/AbstractArtifactMetadata.java * maven-compat/src/main/java/org/apache/maven/artifact/repository/DefaultArtifactRepository.java * maven-embedder/src/main/java/org/apache/maven/cli/CLIReportingUtils.java * maven-artifact/src/main/java/org/apache/maven/artifact/resolver/AbstractArtifactResolutionException.java * maven-core/src/main/java/org/apache/maven/artifact/resolver/ArtifactResolutionResult.java * maven-compat/src/test/java/org/apache/maven/project/inheritance/AbstractProjectInheritanceTestCase.java * maven-embedder/src/main/java/org/apache/maven/cli/event/ExecutionEventLogger.java * maven-settings-builder/src/main/java/org/apache/maven/settings/building/DefaultSettingsProblem.java * maven-model-builder/src/main/java/org/apache/maven/model/building/DefaultModelProblem.java * maven-core/src/main/java/org/apache/maven/plugin/MojoExecution.java * maven-artifact/src/main/java/org/apache/maven/artifact/DefaultArtifact.java * maven-core/src/main/java/org/apache/maven/project/DefaultProjectDependenciesResolver.java * maven-compat/src/main/java/org/apache/maven/repository/MetadataResolutionResult.java * maven-model-builder/src/main/java/org/apache/maven/model/building/DefaultModelBuilder.java * maven-core/src/main/java/org/apache/maven/lifecycle/mapping/LifecyclePhase.java * maven-artifact/src/main/java/org/apache/maven/artifact/resolver/MultipleArtifactsNotFoundException.java * maven-core/src/main/java/org/apache/maven/plugin/PluginParameterException.java > String handling issues identified by PMD > > > Key: MNG-5934 > URL: https://issues.apache.org/jira/browse/MNG-5934 > Project: Maven > Issue Type: Improvement >Affects Versions: 3.3.9 >Reporter: Alex Henrie >Assignee: Christian Schulte >Priority: Minor > Labels: easyfix, newbie, patch, performance > Fix For: 3.4.0 > > Attachments: > 0001-Prefer-StringBuilder.append-char-to-StringBuilder.ap.patch, > 0002-Prefer-String.indexOf-char-to-String.indexOf-String.patch, > 0003-Combine-string-literals-instead-of-calling-String.ap.patch, > 0004-Construct-StringBuffers-with-enough-space-to-begin-w.patch > > > The code linting tool [PMD|http://pmd.sourceforge.net/pmd-5.2.0/] identified > numerous places where Maven's string handling is inefficient. I've prepared a > set of patches that should help speed things up. > The command I used was `pmd -d .
[jira] [Commented] (MRESOURCES-212) maven resource plugin does not preserve symlinks
[ https://issues.apache.org/jira/browse/MRESOURCES-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15107562#comment-15107562 ] Sachin Ramchandra Kothe commented on MRESOURCES-212: Is there any plan of upgrade in release 2.8? > maven resource plugin does not preserve symlinks > > > Key: MRESOURCES-212 > URL: https://issues.apache.org/jira/browse/MRESOURCES-212 > Project: Maven Resources Plugin > Issue Type: Bug > Components: copy >Affects Versions: 2.7 >Reporter: Sachin Ramchandra Kothe >Priority: Minor > > If we have a symlinks under src/main/resources. Maven resources plugin does > not preserve the symlinks and just copies the files. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MRESOURCES-212) maven resource plugin does not preserve symlinks
[
https://issues.apache.org/jira/browse/MRESOURCES-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15107586#comment-15107586
]
Karl Heinz Marbaise commented on MRESOURCES-212:
One question about the use case here. What kind of links you have under
{{/src/main/resources}} ? Apart from that the next planned release will be
3.0.0 which will be lifted to Java 1.6...but we might think about using
reflection...
> maven resource plugin does not preserve symlinks
>
>
> Key: MRESOURCES-212
> URL: https://issues.apache.org/jira/browse/MRESOURCES-212
> Project: Maven Resources Plugin
> Issue Type: Bug
> Components: copy
>Affects Versions: 2.7
>Reporter: Sachin Ramchandra Kothe
>Priority: Minor
>
> If we have a symlinks under src/main/resources. Maven resources plugin does
> not preserve the symlinks and just copies the files.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MRESOURCES-212) maven resource plugin does not preserve symlinks
[ https://issues.apache.org/jira/browse/MRESOURCES-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15107676#comment-15107676 ] Sachin Ramchandra Kothe commented on MRESOURCES-212: We are keeping project templates(Apache velocity) under resources. Our application parses these templates and generates the project for user to start building with. As part of the template we have few symlinks which are helpful for co designing the generated project. > maven resource plugin does not preserve symlinks > > > Key: MRESOURCES-212 > URL: https://issues.apache.org/jira/browse/MRESOURCES-212 > Project: Maven Resources Plugin > Issue Type: Bug > Components: copy >Affects Versions: 2.7 >Reporter: Sachin Ramchandra Kothe >Priority: Minor > > If we have a symlinks under src/main/resources. Maven resources plugin does > not preserve the symlinks and just copies the files. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MRELEASE-938) Need better support for staging release candidates with git and Nexus
Christopher Tubbs created MRELEASE-938:
--
Summary: Need better support for staging release candidates with
git and Nexus
Key: MRELEASE-938
URL: https://issues.apache.org/jira/browse/MRELEASE-938
Project: Maven Release Plugin
Issue Type: Improvement
Reporter: Christopher Tubbs
Use case:
An ASF project creates git tags which are GPG-signed named "rel/"
after a release is voted on. If the release passes, the contents of the pom.xml
files should refer to this final tag, and not any intermediate release
candidate tag name.
To avoid pushing the release prior to building a release candidate and
publishing it to the staging maven repository, the configuration sets
{{false}} and
{{true}}, and the tag name is created with
{{rel/@\{project.version\}}}.
There is still a risk of a release manager accidentally pushing the tag created
by the maven-release-plugin, which has the final name, but is not GPG signed,
and should not be pushed, because it cannot (and should not) change once it is.
What might be useful here is an alternate, intermediate name,
{{@\{project.version\}}} which can be used as the checkout tag for the perform
step.
Alternatively, no tag actually has to be created in this case (a GPG-signed tag
is manually created later). Unless {{suppressCommitBeforeTag}} is set, the
perform step can check out from {{HEAD~1}}, instead. An option to skip tag
creation entirely could work under these circumstances.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
