[jira] [Closed] (SCM-819) Integrity blame command fixes.
[ https://issues.apache.org/jira/browse/SCM-819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy (*$^¨%`£) closed SCM-819. -- Resolution: Fixed pr merged. > Integrity blame command fixes. > -- > > Key: SCM-819 > URL: https://issues.apache.org/jira/browse/SCM-819 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-integrity >Affects Versions: 1.9.4 >Reporter: Olivier Lamy (*$^¨%`£) >Assignee: Olivier Lamy (*$^¨%`£) > Fix For: 1.9.5 > > > pr https://github.com/apache/maven-scm/pull/9 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SCM-819) Integrity blame command fixes.
Olivier Lamy (*$^¨%`£) created SCM-819: -- Summary: Integrity blame command fixes. Key: SCM-819 URL: https://issues.apache.org/jira/browse/SCM-819 Project: Maven SCM Issue Type: Bug Components: maven-scm-provider-integrity Affects Versions: 1.9.4 Reporter: Olivier Lamy (*$^¨%`£) Assignee: Olivier Lamy (*$^¨%`£) Fix For: 1.9.5 pr https://github.com/apache/maven-scm/pull/9 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (MSITE-722) align display info on executed reports
[
https://issues.apache.org/jira/browse/MSITE-722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated MSITE-722:
Comment: was deleted
(was: UNSTABLE: Integrated in maven-plugins #5586 (See
[https://builds.apache.org/job/maven-plugins/5586/])
[MSITE-722] added updated decoration xsd info (hboutemy:
[http://svn.apache.org/viewvc/?view=rev&rev=1737709])
* maven-site-plugin/src/site/apt/migrate.apt
)
> align display info on executed reports
> --
>
> Key: MSITE-722
> URL: https://issues.apache.org/jira/browse/MSITE-722
> Project: Maven Site Plugin
> Issue Type: Improvement
>Affects Versions: 3.3
>Reporter: Hervé Boutemy
>Assignee: Hervé Boutemy
>Priority: Minor
> Fix For: 3.4
>
>
> currently, there is fixed space between text and report info:
> {noformat}[INFO] Generating "Continuous Integration" report---
> maven-project-info-reports-plugin:2.7:cim
> [INFO] Generating "Mailing Lists" report---
> maven-project-info-reports-plugin:2.7:mailing-list
> [INFO] Generating "Project License" report---
> maven-project-info-reports-plugin:2.7:license
> [INFO] Generating "Project Team" report---
> maven-project-info-reports-plugin:2.7:project-team
> [INFO] Generating "Project Summary" report---
> maven-project-info-reports-plugin:2.7:summary
> [INFO] Generating "Dependency Information" report---
> maven-project-info-reports-plugin:2.7:dependency-info
> [INFO] Generating "Issue Tracking" report---
> maven-project-info-reports-plugin:2.7:issue-tracking{noformat}
> it would be more readable (cost less space) if there were some alignment,
> with less psace when the text is large:
> {noformat}[INFO] Generating "Continuous Integration" report ---
> maven-project-info-reports-plugin:2.7:cim
> [INFO] Generating "Mailing Lists" report---
> maven-project-info-reports-plugin:2.7:mailing-list
> [INFO] Generating "Project License" report ---
> maven-project-info-reports-plugin:2.7:license
> [INFO] Generating "Project Team" report ---
> maven-project-info-reports-plugin:2.7:project-team
> [INFO] Generating "Project Summary" report ---
> maven-project-info-reports-plugin:2.7:summary
> [INFO] Generating "Dependency Information" report ---
> maven-project-info-reports-plugin:2.7:dependency-info
> [INFO] Generating "Issue Tracking" report ---
> maven-project-info-reports-plugin:2.7:issue-tracking{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MSITE-772) Any element in causes site to fail
[
https://issues.apache.org/jira/browse/MSITE-772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15225120#comment-15225120
]
Hervé Boutemy commented on MSITE-772:
-
UNSTABLE: Integrated in maven-plugins #5586 (See
[https://builds.apache.org/job/maven-plugins/5586/])
[MSITE-722] added updated decoration xsd info (hboutemy:
[http://svn.apache.org/viewvc/?view=rev&rev=1737709])
* maven-site-plugin/src/site/apt/migrate.apt
> Any element in causes site to fail
> -
>
> Key: MSITE-772
> URL: https://issues.apache.org/jira/browse/MSITE-772
> Project: Maven Site Plugin
> Issue Type: Bug
> Components: site descriptor
>Affects Versions: 3.5
>Reporter: Gordon Pettey
>Assignee: Hervé Boutemy
> Attachments: m-site-p-3.5-exception.txt
>
>
> Any site descriptor containing elements in causes the site plugin to
> fail with
> {quote}[ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.5:site (default-cli) on project
> common-parent: SiteToolException: Error parsing site descriptor: TEXT must be
> immediately followed by END_TAG and not START_TAG (position: START_TAG seen
> ...\n... @74:26) -> [Help 1]{quote}
> The error happened initially with a {{}} element added per the DOAP
> plugin.
> The error occurs after all "configuring plugin..." log lines, but before any
> "Generating XYZ report..." lines.
> The relevant portion of site_en.xml is
> {code:xml}
>
>
> href="${project.url}/doap_${project.artifactId}.rdf"
> type="application/rdf+xml"/>
>
>
>
>
> {code}
> This worked in m-site-p:3.4, so is a regression in 3.5.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (MNG-4099) Password encryption CLI switches should prompt for password if missing
[ https://issues.apache.org/jira/browse/MNG-4099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15224874#comment-15224874 ] Karl Heinz Marbaise edited comment on MNG-4099 at 4/4/16 7:29 PM: -- Ok published production site http://maven.apache.org/guides/mini/guide-encryption.html takes a few minutes to synchronize. Thanks for your help and feedback... was (Author: khmarbaise): Ok published production site...takes a few minutes...Thanks for your help and feedback... > Password encryption CLI switches should prompt for password if missing > -- > > Key: MNG-4099 > URL: https://issues.apache.org/jira/browse/MNG-4099 > Project: Maven > Issue Type: Improvement > Components: Command Line >Affects Versions: 2.1.0 >Reporter: Mark Hobson >Assignee: Robert Scholte >Priority: Trivial > Fix For: 3.2.1 > > > The -emp and -ep CLI switches should prompt for a password if the user omits > it. This would help to avoid having to escape shell characters in strong > passwords. > Note that the docs mention that these switches prompt for a password when > they do not: > http://maven.apache.org/guides/mini/guide-encryption.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNG-4099) Password encryption CLI switches should prompt for password if missing
[ https://issues.apache.org/jira/browse/MNG-4099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15224874#comment-15224874 ] Karl Heinz Marbaise commented on MNG-4099: -- Ok published production site...takes a few minutes...Thanks for your help and feedback... > Password encryption CLI switches should prompt for password if missing > -- > > Key: MNG-4099 > URL: https://issues.apache.org/jira/browse/MNG-4099 > Project: Maven > Issue Type: Improvement > Components: Command Line >Affects Versions: 2.1.0 >Reporter: Mark Hobson >Assignee: Robert Scholte >Priority: Trivial > Fix For: 3.2.1 > > > The -emp and -ep CLI switches should prompt for a password if the user omits > it. This would help to avoid having to escape shell characters in strong > passwords. > Note that the docs mention that these switches prompt for a password when > they do not: > http://maven.apache.org/guides/mini/guide-encryption.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNG-4099) Password encryption CLI switches should prompt for password if missing
[ https://issues.apache.org/jira/browse/MNG-4099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15224867#comment-15224867 ] Konrad Windszus commented on MNG-4099: -- Looks good now. Thanks a lot. > Password encryption CLI switches should prompt for password if missing > -- > > Key: MNG-4099 > URL: https://issues.apache.org/jira/browse/MNG-4099 > Project: Maven > Issue Type: Improvement > Components: Command Line >Affects Versions: 2.1.0 >Reporter: Mark Hobson >Assignee: Robert Scholte >Priority: Trivial > Fix For: 3.2.1 > > > The -emp and -ep CLI switches should prompt for a password if the user omits > it. This would help to avoid having to escape shell characters in strong > passwords. > Note that the docs mention that these switches prompt for a password when > they do not: > http://maven.apache.org/guides/mini/guide-encryption.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MJAR-210) Remove useDefaultManifestFile parameter
[
https://issues.apache.org/jira/browse/MJAR-210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15224829#comment-15224829
]
Karl Heinz Marbaise commented on MJAR-210:
--
In general a very good idea (should have been done with the latest 2.X release
which was not the case) but in this case i think it would be ok...cause we make
a major version update...but i will add a note to the docs about that to make
it more clear...
> Remove useDefaultManifestFile parameter
> ---
>
> Key: MJAR-210
> URL: https://issues.apache.org/jira/browse/MJAR-210
> Project: Maven JAR Plugin
> Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
> Fix For: 3.0.0
>
>
> The following:
> {code}
> @Parameter( property = "maven.jar.useDefaultManifestFile", defaultValue =
> "false" )
> private boolean useDefaultManifestFile;
> {code}
> does not make sense in general, cause it can be handled via
> [MavenArchiver|http://maven.apache.org/shared/maven-archiver/index.html]
> configuration. So this should be completely removed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MJAR-210) Remove useDefaultManifestFile parameter
[
https://issues.apache.org/jira/browse/MJAR-210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15224819#comment-15224819
]
Hudson commented on MJAR-210:
-
UNSTABLE: Integrated in maven-plugins #5587 (See
[https://builds.apache.org/job/maven-plugins/5587/])
[MJAR-210] Remove useDefaultManifestFile parameter
o Removed the parameter useDefaultManifestFile,
defaultManifestFile and removed the docs about that.
Everything can be handled by MavenArchiveConfiguration. (khmarbaise:
[http://svn.apache.org/viewvc/?view=rev&rev=1737724])
* maven-jar-plugin/src/it/mjar-71-01/pom.xml
*
maven-jar-plugin/src/main/java/org/apache/maven/plugins/jar/AbstractJarMojo.java
* maven-jar-plugin/src/site/apt/examples/default-manifest-file.apt.vm
* maven-jar-plugin/src/site/apt/examples/manifest-customization.apt.vm
* maven-jar-plugin/src/site/apt/index.apt.vm
* maven-jar-plugin/src/site/site.xml
> Remove useDefaultManifestFile parameter
> ---
>
> Key: MJAR-210
> URL: https://issues.apache.org/jira/browse/MJAR-210
> Project: Maven JAR Plugin
> Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
> Fix For: 3.0.0
>
>
> The following:
> {code}
> @Parameter( property = "maven.jar.useDefaultManifestFile", defaultValue =
> "false" )
> private boolean useDefaultManifestFile;
> {code}
> does not make sense in general, cause it can be handled via
> [MavenArchiver|http://maven.apache.org/shared/maven-archiver/index.html]
> configuration. So this should be completely removed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MJAR-210) Remove useDefaultManifestFile parameter
[
https://issues.apache.org/jira/browse/MJAR-210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15224801#comment-15224801
]
Anders Hammar commented on MJAR-210:
Just an idea, should we keep params that we want to remove but mark them as
deprecated and have them issue an exception with a good error message? To
simplify for people upgrading and catch these breaking changes.
> Remove useDefaultManifestFile parameter
> ---
>
> Key: MJAR-210
> URL: https://issues.apache.org/jira/browse/MJAR-210
> Project: Maven JAR Plugin
> Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
> Fix For: 3.0.0
>
>
> The following:
> {code}
> @Parameter( property = "maven.jar.useDefaultManifestFile", defaultValue =
> "false" )
> private boolean useDefaultManifestFile;
> {code}
> does not make sense in general, cause it can be handled via
> [MavenArchiver|http://maven.apache.org/shared/maven-archiver/index.html]
> configuration. So this should be completely removed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (MJAR-210) Remove useDefaultManifestFile parameter
[
https://issues.apache.org/jira/browse/MJAR-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise closed MJAR-210.
Resolution: Fixed
Fixed in [r1737724|http://svn.apache.org/r1737724]
> Remove useDefaultManifestFile parameter
> ---
>
> Key: MJAR-210
> URL: https://issues.apache.org/jira/browse/MJAR-210
> Project: Maven JAR Plugin
> Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
> Fix For: 3.0.0
>
>
> The following:
> {code}
> @Parameter( property = "maven.jar.useDefaultManifestFile", defaultValue =
> "false" )
> private boolean useDefaultManifestFile;
> {code}
> does not make sense in general, cause it can be handled via
> [MavenArchiver|http://maven.apache.org/shared/maven-archiver/index.html]
> configuration. So this should be completely removed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (MNG-4099) Password encryption CLI switches should prompt for password if missing
[ https://issues.apache.org/jira/browse/MNG-4099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15224715#comment-15224715 ] Karl Heinz Marbaise edited comment on MNG-4099 at 4/4/16 6:33 PM: -- Done so..please check...if you give feedback i can publish the staging site to production... was (Author: khmarbaise): Done so..please check... > Password encryption CLI switches should prompt for password if missing > -- > > Key: MNG-4099 > URL: https://issues.apache.org/jira/browse/MNG-4099 > Project: Maven > Issue Type: Improvement > Components: Command Line >Affects Versions: 2.1.0 >Reporter: Mark Hobson >Assignee: Robert Scholte >Priority: Trivial > Fix For: 3.2.1 > > > The -emp and -ep CLI switches should prompt for a password if the user omits > it. This would help to avoid having to escape shell characters in strong > passwords. > Note that the docs mention that these switches prompt for a password when > they do not: > http://maven.apache.org/guides/mini/guide-encryption.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MJAR-210) Remove useDefaultManifestFile parameter
[
https://issues.apache.org/jira/browse/MJAR-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise reassigned MJAR-210:
Assignee: Karl Heinz Marbaise
> Remove useDefaultManifestFile parameter
> ---
>
> Key: MJAR-210
> URL: https://issues.apache.org/jira/browse/MJAR-210
> Project: Maven JAR Plugin
> Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
> Fix For: 3.0.0
>
>
> The following:
> {code}
> @Parameter( property = "maven.jar.useDefaultManifestFile", defaultValue =
> "false" )
> private boolean useDefaultManifestFile;
> {code}
> does not make sense in general, cause it can be handled via
> [MavenArchiver|http://maven.apache.org/shared/maven-archiver/index.html]
> configuration. So this should be completely removed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MNG-4099) Password encryption CLI switches should prompt for password if missing
[ https://issues.apache.org/jira/browse/MNG-4099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15224715#comment-15224715 ] Karl Heinz Marbaise commented on MNG-4099: -- Done so..please check... > Password encryption CLI switches should prompt for password if missing > -- > > Key: MNG-4099 > URL: https://issues.apache.org/jira/browse/MNG-4099 > Project: Maven > Issue Type: Improvement > Components: Command Line >Affects Versions: 2.1.0 >Reporter: Mark Hobson >Assignee: Robert Scholte >Priority: Trivial > Fix For: 3.2.1 > > > The -emp and -ep CLI switches should prompt for a password if the user omits > it. This would help to avoid having to escape shell characters in strong > passwords. > Note that the docs mention that these switches prompt for a password when > they do not: > http://maven.apache.org/guides/mini/guide-encryption.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNG-4099) Password encryption CLI switches should prompt for password if missing
[
https://issues.apache.org/jira/browse/MNG-4099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15224688#comment-15224688
]
Konrad Windszus commented on MNG-4099:
--
Minor improvement for the tips section
Instead of
{quote}
Prompting for Password
In Maven before version 3.2.1 you have to give the password on command line
which means you might need to escape your password etc. and might cause
problems related to the history funcitonality of your command line processor.
Starting with Maven 3.2.1 the password is an optional argument which means if
you omit the password you will be prompted for the password which can prevent
many problems with escaping the password and history issues as well.
So we strongly recomment to use Maven 3.2.1 and above to prevent problems with
escaping special characters and of course security issues related to bash
history or environment issues in relationship with the password.
{quote}
I would rather say
{quote}
Prompting for Password
In Maven before version 3.2.1 you have to give the password on command line as
argument which means you might need to escape your password. In addition
usually the shell stores the full history of commands you have entered,
therefore anyone with access to your computer could restore the password from
the shell`s history.
Starting with Maven 3.2.1 the password is an optional argument which means if
you omit the password you will be prompted for it which prevents all the issues
mentioned above.
Therefore we strongly recommend to use Maven 3.2.1 and above to prevent
problems with escaping special characters and of course security issues related
to bash history or environment issues in relationship with the password.
{quote}
> Password encryption CLI switches should prompt for password if missing
> --
>
> Key: MNG-4099
> URL: https://issues.apache.org/jira/browse/MNG-4099
> Project: Maven
> Issue Type: Improvement
> Components: Command Line
>Affects Versions: 2.1.0
>Reporter: Mark Hobson
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.2.1
>
>
> The -emp and -ep CLI switches should prompt for a password if the user omits
> it. This would help to avoid having to escape shell characters in strong
> passwords.
> Note that the docs mention that these switches prompt for a password when
> they do not:
> http://maven.apache.org/guides/mini/guide-encryption.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MNG-4099) Password encryption CLI switches should prompt for password if missing
[
https://issues.apache.org/jira/browse/MNG-4099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15224671#comment-15224671
]
Konrad Windszus commented on MNG-4099:
--
Looks much better, thanks a lot. One minor improvement though would be to link
the additional tip in both How-Tos (where this 3.2.1 feature is mentioned).
So this:
{quote}
Since Maven 3.2.1 the password is an optional argument. If not provided, Maven
will prompt for the password. Earlier versions of Maven will not prompt for a
password, so it must be typed on the command-line in plaintext. See Tips below
for more information.
{quote}
should become
{quote}
Since Maven 3.2.1 the password argument should no longer be used (see Tips
below for more information). Maven will prompt for the password. Earlier
versions of Maven will not prompt for a password, so it must be typed on the
command-line in plaintext.
{quote}
and this
{quote}
Just like --encrypt-master-password the password argument is optional since
Maven 3.2.1.
{quote}
should become
{quote}
Just like --encrypt-master-password the password argument should no longer be
used since Maven 3.2.1 (see Tips below for more information).
{quote}
> Password encryption CLI switches should prompt for password if missing
> --
>
> Key: MNG-4099
> URL: https://issues.apache.org/jira/browse/MNG-4099
> Project: Maven
> Issue Type: Improvement
> Components: Command Line
>Affects Versions: 2.1.0
>Reporter: Mark Hobson
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 3.2.1
>
>
> The -emp and -ep CLI switches should prompt for a password if the user omits
> it. This would help to avoid having to escape shell characters in strong
> passwords.
> Note that the docs mention that these switches prompt for a password when
> they do not:
> http://maven.apache.org/guides/mini/guide-encryption.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MNG-4099) Password encryption CLI switches should prompt for password if missing
[ https://issues.apache.org/jira/browse/MNG-4099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15224637#comment-15224637 ] Karl Heinz Marbaise commented on MNG-4099: -- Can you check this site: http://maven.staging.apache.org/guides/mini/guide-encryption.html and tell me what you think? Better ? Suggestions for improvements? > Password encryption CLI switches should prompt for password if missing > -- > > Key: MNG-4099 > URL: https://issues.apache.org/jira/browse/MNG-4099 > Project: Maven > Issue Type: Improvement > Components: Command Line >Affects Versions: 2.1.0 >Reporter: Mark Hobson >Assignee: Robert Scholte >Priority: Trivial > Fix For: 3.2.1 > > > The -emp and -ep CLI switches should prompt for a password if the user omits > it. This would help to avoid having to escape shell characters in strong > passwords. > Note that the docs mention that these switches prompt for a password when > they do not: > http://maven.apache.org/guides/mini/guide-encryption.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MSITE-722) align display info on executed reports
[
https://issues.apache.org/jira/browse/MSITE-722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15224635#comment-15224635
]
Hudson commented on MSITE-722:
--
UNSTABLE: Integrated in maven-plugins #5586 (See
[https://builds.apache.org/job/maven-plugins/5586/])
[MSITE-722] added updated decoration xsd info (hboutemy:
[http://svn.apache.org/viewvc/?view=rev&rev=1737709])
* maven-site-plugin/src/site/apt/migrate.apt
> align display info on executed reports
> --
>
> Key: MSITE-722
> URL: https://issues.apache.org/jira/browse/MSITE-722
> Project: Maven Site Plugin
> Issue Type: Improvement
>Affects Versions: 3.3
>Reporter: Hervé Boutemy
>Assignee: Hervé Boutemy
>Priority: Minor
> Fix For: 3.4
>
>
> currently, there is fixed space between text and report info:
> {noformat}[INFO] Generating "Continuous Integration" report---
> maven-project-info-reports-plugin:2.7:cim
> [INFO] Generating "Mailing Lists" report---
> maven-project-info-reports-plugin:2.7:mailing-list
> [INFO] Generating "Project License" report---
> maven-project-info-reports-plugin:2.7:license
> [INFO] Generating "Project Team" report---
> maven-project-info-reports-plugin:2.7:project-team
> [INFO] Generating "Project Summary" report---
> maven-project-info-reports-plugin:2.7:summary
> [INFO] Generating "Dependency Information" report---
> maven-project-info-reports-plugin:2.7:dependency-info
> [INFO] Generating "Issue Tracking" report---
> maven-project-info-reports-plugin:2.7:issue-tracking{noformat}
> it would be more readable (cost less space) if there were some alignment,
> with less psace when the text is large:
> {noformat}[INFO] Generating "Continuous Integration" report ---
> maven-project-info-reports-plugin:2.7:cim
> [INFO] Generating "Mailing Lists" report---
> maven-project-info-reports-plugin:2.7:mailing-list
> [INFO] Generating "Project License" report ---
> maven-project-info-reports-plugin:2.7:license
> [INFO] Generating "Project Team" report ---
> maven-project-info-reports-plugin:2.7:project-team
> [INFO] Generating "Project Summary" report ---
> maven-project-info-reports-plugin:2.7:summary
> [INFO] Generating "Dependency Information" report ---
> maven-project-info-reports-plugin:2.7:dependency-info
> [INFO] Generating "Issue Tracking" report ---
> maven-project-info-reports-plugin:2.7:issue-tracking{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MSITE-772) Any element in causes site to fail
[
https://issues.apache.org/jira/browse/MSITE-772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15224570#comment-15224570
]
Hervé Boutemy commented on MSITE-772:
-
good catch: I'll update for the future (soon) 3.5.1
> Any element in causes site to fail
> -
>
> Key: MSITE-772
> URL: https://issues.apache.org/jira/browse/MSITE-772
> Project: Maven Site Plugin
> Issue Type: Bug
> Components: site descriptor
>Affects Versions: 3.5
>Reporter: Gordon Pettey
>Assignee: Hervé Boutemy
> Attachments: m-site-p-3.5-exception.txt
>
>
> Any site descriptor containing elements in causes the site plugin to
> fail with
> {quote}[ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.5:site (default-cli) on project
> common-parent: SiteToolException: Error parsing site descriptor: TEXT must be
> immediately followed by END_TAG and not START_TAG (position: START_TAG seen
> ...\n... @74:26) -> [Help 1]{quote}
> The error happened initially with a {{}} element added per the DOAP
> plugin.
> The error occurs after all "configuring plugin..." log lines, but before any
> "Generating XYZ report..." lines.
> The relevant portion of site_en.xml is
> {code:xml}
>
>
> href="${project.url}/doap_${project.artifactId}.rdf"
> type="application/rdf+xml"/>
>
>
>
>
> {code}
> This worked in m-site-p:3.4, so is a regression in 3.5.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (MNG-4099) Password encryption CLI switches should prompt for password if missing
[ https://issues.apache.org/jira/browse/MNG-4099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15224500#comment-15224500 ] Konrad Windszus edited comment on MNG-4099 at 4/4/16 4:58 PM: -- Can you add stronger hint on this in http://maven.apache.org/guides/mini/guide-encryption.html? Currently it just says: Since Maven 3.2.1 the password is an optional argument. This should be strong recommendation like: Since Maven 3.2.1 the password should no longer be provided as argument to prevent issues with the bash history and the decoding of special characters. At least in the tips section this should be explicitly mention, but preferably also in the How-Tos it should be clarified. was (Author: kwin): Can you add a hint on this in http://maven.apache.org/guides/mini/guide-encryption.html? At least in the tips section but preferably also in the How-Tos (with a hint that this is only supported since Maven 3.2.1)? > Password encryption CLI switches should prompt for password if missing > -- > > Key: MNG-4099 > URL: https://issues.apache.org/jira/browse/MNG-4099 > Project: Maven > Issue Type: Improvement > Components: Command Line >Affects Versions: 2.1.0 >Reporter: Mark Hobson >Assignee: Robert Scholte >Priority: Trivial > Fix For: 3.2.1 > > > The -emp and -ep CLI switches should prompt for a password if the user omits > it. This would help to avoid having to escape shell characters in strong > passwords. > Note that the docs mention that these switches prompt for a password when > they do not: > http://maven.apache.org/guides/mini/guide-encryption.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNG-4099) Password encryption CLI switches should prompt for password if missing
[ https://issues.apache.org/jira/browse/MNG-4099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15224500#comment-15224500 ] Konrad Windszus commented on MNG-4099: -- Can you add a hint on this in http://maven.apache.org/guides/mini/guide-encryption.html? At least in the tips section but preferably also in the How-Tos (with a hint that this is only supported since Maven 3.2.1)? > Password encryption CLI switches should prompt for password if missing > -- > > Key: MNG-4099 > URL: https://issues.apache.org/jira/browse/MNG-4099 > Project: Maven > Issue Type: Improvement > Components: Command Line >Affects Versions: 2.1.0 >Reporter: Mark Hobson >Assignee: Robert Scholte >Priority: Trivial > Fix For: 3.2.1 > > > The -emp and -ep CLI switches should prompt for a password if the user omits > it. This would help to avoid having to escape shell characters in strong > passwords. > Note that the docs mention that these switches prompt for a password when > they do not: > http://maven.apache.org/guides/mini/guide-encryption.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNG-5900) early interpolation: support ${this.*} as expression
[
https://issues.apache.org/jira/browse/MNG-5900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15224400#comment-15224400
]
Paul Benedict commented on MNG-5900:
I'd like further background on the ticket's requirement: "So it is not possible
that parent poms can lock values, ie avoid child poms override". Can you please
give an example why something like this is necessary? Why is the child POM so
problematic for your use case?
> early interpolation: support ${this.*} as expression
>
>
> Key: MNG-5900
> URL: https://issues.apache.org/jira/browse/MNG-5900
> Project: Maven
> Issue Type: New Feature
> Components: Inheritance and Interpolation
>Reporter: Robert Scholte
> Fix For: Issues to be reviewed for 4.x
>
>
> Right now we have $\{project.\*} which always interpolates values based on
> the final project: "classical" interpolation is "late" interpolation. So it
> is not possible that parent poms can lock values, ie avoid child poms
> override. By adding $\{this} for "early" interpolation, it will be possible
> to have intermediate interpolation.
> If a pomfile depends on a parent, that parent will first resolve all
> $\{this.\*} values for itself. Once the fully inherited pom is there, all
> $\{project.\*} will be resolved.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (MSITE-772) Any element in causes site to fail
[
https://issues.apache.org/jira/browse/MSITE-772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15224368#comment-15224368
]
Gordon Pettey edited comment on MSITE-772 at 4/4/16 3:51 PM:
-
If m-site-p-3.5 wants users to use decoration-1.7.0.xsd to validate, it should
be using 1.7.0 itself and in documentation, rather than 1.6.0.
was (Author: gpettey):
If m-site-p-3.5 wants users to use decoration-1.7.0.xsd to validate, it should
be using 1.7.0 itself and in documentation.
> Any element in causes site to fail
> -
>
> Key: MSITE-772
> URL: https://issues.apache.org/jira/browse/MSITE-772
> Project: Maven Site Plugin
> Issue Type: Bug
> Components: site descriptor
>Affects Versions: 3.5
>Reporter: Gordon Pettey
>Assignee: Hervé Boutemy
> Attachments: m-site-p-3.5-exception.txt
>
>
> Any site descriptor containing elements in causes the site plugin to
> fail with
> {quote}[ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.5:site (default-cli) on project
> common-parent: SiteToolException: Error parsing site descriptor: TEXT must be
> immediately followed by END_TAG and not START_TAG (position: START_TAG seen
> ...\n... @74:26) -> [Help 1]{quote}
> The error happened initially with a {{}} element added per the DOAP
> plugin.
> The error occurs after all "configuring plugin..." log lines, but before any
> "Generating XYZ report..." lines.
> The relevant portion of site_en.xml is
> {code:xml}
>
>
> href="${project.url}/doap_${project.artifactId}.rdf"
> type="application/rdf+xml"/>
>
>
>
>
> {code}
> This worked in m-site-p:3.4, so is a regression in 3.5.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MSITE-772) Any element in causes site to fail
[
https://issues.apache.org/jira/browse/MSITE-772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15224368#comment-15224368
]
Gordon Pettey commented on MSITE-772:
-
If m-site-p-3.5 wants users to use decoration-1.7.0.xsd to validate, it should
be using 1.7.0 itself and in documentation.
> Any element in causes site to fail
> -
>
> Key: MSITE-772
> URL: https://issues.apache.org/jira/browse/MSITE-772
> Project: Maven Site Plugin
> Issue Type: Bug
> Components: site descriptor
>Affects Versions: 3.5
>Reporter: Gordon Pettey
>Assignee: Hervé Boutemy
> Attachments: m-site-p-3.5-exception.txt
>
>
> Any site descriptor containing elements in causes the site plugin to
> fail with
> {quote}[ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.5:site (default-cli) on project
> common-parent: SiteToolException: Error parsing site descriptor: TEXT must be
> immediately followed by END_TAG and not START_TAG (position: START_TAG seen
> ...\n... @74:26) -> [Help 1]{quote}
> The error happened initially with a {{}} element added per the DOAP
> plugin.
> The error occurs after all "configuring plugin..." log lines, but before any
> "Generating XYZ report..." lines.
> The relevant portion of site_en.xml is
> {code:xml}
>
>
> href="${project.url}/doap_${project.artifactId}.rdf"
> type="application/rdf+xml"/>
>
>
>
>
> {code}
> This worked in m-site-p:3.4, so is a regression in 3.5.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MNG-5994) add explicit ordering support for plugins
Romain Manni-Bucau created MNG-5994: --- Summary: add explicit ordering support for plugins Key: MNG-5994 URL: https://issues.apache.org/jira/browse/MNG-5994 Project: Maven Issue Type: New Feature Affects Versions: 3.3.9 Reporter: Romain Manni-Bucau Hi On one side maven doesn't really support plugin ordering in a deterministic manner (on some doc the merging mecanism states it follows the pom ordering but with some exceptions making a pom rarely deterministic and user friendly or at a very very high cost when pom hierarchy + profile are there). On another side it is more and more common to need to add some custom processing (another plugin, a main through mvn-exec or a groovy script) between 2 plugins. Very common use cases are frontend optimizations, documentation generation etc... That's why I'd like maven to support an explicit ordering. It can be as easy as adding to plugin a before/after tag(s) referring execution id of another plugin. This would allow end users to explicitly control their whole build chain without having to hack maven with either meta-tasks, custom mojo or worse custom lifecycle. This would also finally allows users to remove workaround using wrong phases to ensure of the ordering for instance. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SCM-775) Add workItem and changeset associate support for scm deliver
[
https://issues.apache.org/jira/browse/SCM-775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15224129#comment-15224129
]
Rafael Odon de Alencar commented on SCM-775:
I'm really interested in this pull-request. Not being able to associate
workItem is definetely a huge obstacle to the maven release plugin in my
current project. Is it possible to already start using it by referencing some
snapshot version of the plugin on my pom.xml?
> Add workItem and changeset associate support for scm deliver
>
>
> Key: SCM-775
> URL: https://issues.apache.org/jira/browse/SCM-775
> Project: Maven SCM
> Issue Type: Improvement
> Components: maven-scm-provider-jazz
>Affects Versions: 1.9.1
>Reporter: AShit Shah
>Assignee: Chris Graham
> Fix For: 1.9.5
>
>
> Maven {{release:prepare}} command is failing with below error while
> delivering updated pom.xml to the stream due to Preconditions configured in
> RTC to have comments and associated work item with every delivery.
> {noformat}
> [ERROR] Name: Deliver
> [ERROR] Participant Reports:
> [ERROR] Name: Require Work items and Comments
> [ERROR] A work item must be associated with the change set.`
> [ERROR] At least one of the associated work items must specify that the work
> is planned for the current iteration.
> [ERROR] At least one of the associated work items must be assigned to you.
> [ERROR] Problem running 'deliver':
> [ERROR] 'Deliver' failed. Preconditions have not been met: A work item must
> be associated with the change set.
> [ERROR] -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-release-plugin:2.5:prepare (default-cli)
> on project junit-ext: Unable to commit files
> Provider message:
> Error code for Jazz SCM deliver command - 17
> {noformat}
> I can not find any optional parameters on
> http://maven.apache.org/maven-release/maven-release-plugin/prepare-mojo.html
> for release:prepare command which I can use and pass the RTC workitem number
> on command line.
> Suggestion:
> It will be great if you can provide optional parameters like "workItem" which
> I can use and pass RTC workitem number with release:prepare at command line.
> Example: {{mvn -PmyProfile release:prepare -DworkItem=123456}}
> So build process should associate change sets created by {{release:prepare}}
> with work item 123456 and deliver change sets to the stream.
> As of now I have to use "{{-DpushChanges=false}}" parameter to block delivery
> process and I have to manually find the change sets, associate them with work
> item and deliver them before I run {{release:perform}}.
> Thanks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MEAR-229) Change default value for version parameter
Anders Hammar created MEAR-229: -- Summary: Change default value for version parameter Key: MEAR-229 URL: https://issues.apache.org/jira/browse/MEAR-229 Project: Maven Ear Plugin Issue Type: Improvement Affects Versions: 2.10.1 Environment: n/a Reporter: Anders Hammar Fix For: 3.0.0 The default value for the version parameter (version in application.xml) is currently 1.3. We should probably change that to 6 or maybe even 7. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MEAR-229) Change default value for version parameter
[ https://issues.apache.org/jira/browse/MEAR-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anders Hammar updated MEAR-229: --- Priority: Minor (was: Major) > Change default value for version parameter > -- > > Key: MEAR-229 > URL: https://issues.apache.org/jira/browse/MEAR-229 > Project: Maven Ear Plugin > Issue Type: Improvement >Affects Versions: 2.10.1 > Environment: n/a >Reporter: Anders Hammar >Priority: Minor > Fix For: 3.0.0 > > > The default value for the version parameter (version in application.xml) is > currently 1.3. We should probably change that to 6 or maybe even 7. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MEAR-228) Remove manifestFile parameter
[ https://issues.apache.org/jira/browse/MEAR-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anders Hammar updated MEAR-228: --- Fix Version/s: 3.0.0 > Remove manifestFile parameter > - > > Key: MEAR-228 > URL: https://issues.apache.org/jira/browse/MEAR-228 > Project: Maven Ear Plugin > Issue Type: Improvement > Environment: n/a >Reporter: Anders Hammar >Priority: Minor > Fix For: 3.0.0 > > > Specifying a manifest file to use can be used via [archiver > configuration|https://maven.apache.org/shared/maven-archiver/examples/manifestFile.html], > so the manifetsFile parameter should be removed to align configuration for > all packaging maven plugins. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MEAR-228) Remove manifestFile parameter
Anders Hammar created MEAR-228: -- Summary: Remove manifestFile parameter Key: MEAR-228 URL: https://issues.apache.org/jira/browse/MEAR-228 Project: Maven Ear Plugin Issue Type: Improvement Environment: n/a Reporter: Anders Hammar Priority: Minor Specifying a manifest file to use can be used via [archiver configuration|https://maven.apache.org/shared/maven-archiver/examples/manifestFile.html], so the manifetsFile parameter should be removed to align configuration for all packaging maven plugins. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (MJAR-210) Remove useDefaultManifestFile parameter
[
https://issues.apache.org/jira/browse/MJAR-210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15223749#comment-15223749
]
Anders Hammar edited comment on MJAR-210 at 4/4/16 7:08 AM:
This parameter was added in v2.2 so I wonder what the use case is/was? There is
a doc page for it:
https://maven.apache.org/plugins/maven-jar-plugin/examples/default-manifest-file.html
Archiver config to achieve the same:
https://maven.apache.org/shared/maven-archiver/examples/manifestFile.html
Also, I think that the "default" part of the parameter name is completely
wrong. I view the generated manifest file as the default, not a manifest file
included in the source tree.
was (Author: afloom):
This parameter was added in v2.2 so I wonder what the use case is/was? There is
a doc page for it:
https://maven.apache.org/plugins/maven-jar-plugin/examples/default-manifest-file.html
Archiver config to achieve the same:
https://maven.apache.org/shared/maven-archiver/examples/manifestFile.html
Also, I think that the name "default" part of the parameter name is completely
wrong. I view the generated manifest file as the default, not a manifest file
included in the source tree.
> Remove useDefaultManifestFile parameter
> ---
>
> Key: MJAR-210
> URL: https://issues.apache.org/jira/browse/MJAR-210
> Project: Maven JAR Plugin
> Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: Karl Heinz Marbaise
> Fix For: 3.0.0
>
>
> The following:
> {code}
> @Parameter( property = "maven.jar.useDefaultManifestFile", defaultValue =
> "false" )
> private boolean useDefaultManifestFile;
> {code}
> does not make sense in general, cause it can be handled via
> [MavenArchiver|http://maven.apache.org/shared/maven-archiver/index.html]
> configuration. So this should be completely removed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Issue Comment Deleted] (MJAR-209) Remove param properties that doesn't make sense for CLI usage
[ https://issues.apache.org/jira/browse/MJAR-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anders Hammar updated MJAR-209: --- Comment: was deleted (was: Please handle removal of that param as a separate ticket. I assume removing it could break backwards compatibility.) > Remove param properties that doesn't make sense for CLI usage > - > > Key: MJAR-209 > URL: https://issues.apache.org/jira/browse/MJAR-209 > Project: Maven JAR Plugin > Issue Type: Improvement > Environment: n/a >Reporter: Anders Hammar > > Currently the plugin supports configuring several of the parameters via CLI > properties. This doesn't make sense in many cases and encourages bad Maven > usage (builds should be reproducable). Remove the properties for those > parameters. The v3.0.0 release is a good time to do this. > First of all we need to identify candidates for removal. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MJAR-210) Remove useDefaultManifestFile parameter
[
https://issues.apache.org/jira/browse/MJAR-210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15223749#comment-15223749
]
Anders Hammar commented on MJAR-210:
This parameter was added in v2.2 so I wonder what the use case is/was? There is
a doc page for it:
https://maven.apache.org/plugins/maven-jar-plugin/examples/default-manifest-file.html
Archiver config to achieve the same:
https://maven.apache.org/shared/maven-archiver/examples/manifestFile.html
Also, I think that the name "default" part of the parameter name is completely
wrong. I view the generated manifest file as the default, not a manifest file
included in the source tree.
> Remove useDefaultManifestFile parameter
> ---
>
> Key: MJAR-210
> URL: https://issues.apache.org/jira/browse/MJAR-210
> Project: Maven JAR Plugin
> Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: Karl Heinz Marbaise
> Fix For: 3.0.0
>
>
> The following:
> {code}
> @Parameter( property = "maven.jar.useDefaultManifestFile", defaultValue =
> "false" )
> private boolean useDefaultManifestFile;
> {code}
> does not make sense in general, cause it can be handled via
> [MavenArchiver|http://maven.apache.org/shared/maven-archiver/index.html]
> configuration. So this should be completely removed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
