[jira] (MPIR-329) French translation in project-info-report_fr.properties
[ https://jira.codehaus.org/browse/MPIR-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=361233#comment-361233 ] Michael Osipov commented on MPIR-329: - Have you added the narrow no-breaking space and checked what the browsers have spit out? If that is not an option, you can emply the alternative space char and add a comment at the top of the file explaning the problem. > French translation in project-info-report_fr.properties > --- > > Key: MPIR-329 > URL: https://jira.codehaus.org/browse/MPIR-329 > Project: Maven Project Info Reports Plugin > Issue Type: Improvement >Reporter: Olivier Maury >Priority: Minor > Attachments: project-info-report_fr.properties, > project-info-report_fr.properties.patch > > > Some corrections on typography and term. > File from > http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-project-info-reports-plugin/src/main/resources/project-info-report_fr.properties -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNGSITE-221) Broken link in maven site
[ https://jira.codehaus.org/browse/MNGSITE-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=361259#comment-361259 ] Michael Osipov commented on MNGSITE-221: Where does this link exist. > Broken link in maven site > - > > Key: MNGSITE-221 > URL: https://jira.codehaus.org/browse/MNGSITE-221 > Project: Maven Project Web Site > Issue Type: Improvement >Reporter: Venkatachalam Muthusamy >Priority: Minor > > I could not able to access the below link. Please check > http://maven.apache.org/benefits-of-using-maven.html -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNGSITE-221) Broken link in maven site
[ https://jira.codehaus.org/browse/MNGSITE-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=361259#comment-361259 ] Michael Osipov edited comment on MNGSITE-221 at 1/15/15 8:45 AM: - Where does this link come from? was (Author: michael-o): Where does this link exist. > Broken link in maven site > - > > Key: MNGSITE-221 > URL: https://jira.codehaus.org/browse/MNGSITE-221 > Project: Maven Project Web Site > Issue Type: Improvement >Reporter: Venkatachalam Muthusamy >Priority: Minor > > I could not able to access the below link. Please check > http://maven.apache.org/benefits-of-using-maven.html -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SCM-780) Duplicate connection url's properties
[
https://jira.codehaus.org/browse/SCM-780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=361261#comment-361261
]
Karl-Heinz Marbaise commented on SCM-780:
-
I have my doubts on that. I would suggest to simply make it correct. You might
add an alias with the accidently wrong name...just to be sure.
> Duplicate connection url's properties
> -
>
> Key: SCM-780
> URL: https://jira.codehaus.org/browse/SCM-780
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-plugin
>Affects Versions: 1.9.1
>Reporter: Dan Tran
>Assignee: Dan Tran
> Fix For: 1.9.3
>
>
> at AbstractScmMojo
> /**
> * The SCM connection URL.
> */
> @Parameter( property = "connectionUrl", defaultValue =
> "${project.scm.connection}" )
> private String connectionUrl;
> /**
> * The SCM connection URL for developers.
> */
> @Parameter( property = "connectionUrl", defaultValue =
> "${project.scm.developerConnection}" )
> private String developerConnectionUrl;
> the property "connectionUrl" is used by both connectionUrl and
> developerConnectionUrl
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNGSITE-221) Broken link in maven site
[ https://jira.codehaus.org/browse/MNGSITE-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=361267#comment-361267 ] Venkatachalam Muthusamy commented on MNGSITE-221: - Go to -> http://maven.apache.org/guides/getting-started/index.html Look for "The Benefits of Using Maven" hyperlink in that page. > Broken link in maven site > - > > Key: MNGSITE-221 > URL: https://jira.codehaus.org/browse/MNGSITE-221 > Project: Maven Project Web Site > Issue Type: Improvement >Reporter: Venkatachalam Muthusamy >Priority: Minor > > I could not able to access the below link. Please check > http://maven.apache.org/benefits-of-using-maven.html -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCOMPILER-223) Move to a non-ancient maven-toolchain dependency
[ https://jira.codehaus.org/browse/MCOMPILER-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated MCOMPILER-223: -- Fix Version/s: 3.3 > Move to a non-ancient maven-toolchain dependency > > > Key: MCOMPILER-223 > URL: https://jira.codehaus.org/browse/MCOMPILER-223 > Project: Maven Compiler Plugin > Issue Type: Bug >Reporter: Noa Resare >Priority: Minor > Fix For: 3.3 > > > It turns out that the maven-toolchain-1.0.jar available form maven central > has some serious issues resulting in it not being extractable by the oracle > provided jar tool (the toplevel directories in the archives are empty files > and not directories, which breaks extraction) > Some tools (IntelliJ in my case) expect to be able to extract jarfiles to be > able to see the contents. > Looking into the maven-toolchain artifact it seems like it has moved into > maven-core for 3.x versions, but for 2.x versions it kind of tracks the maven > release. > Because of this, I propose that we use $mavenVersion for the maven-toolchain > dependency (2.0.9 in our case) which seems to do the right thing and works > around my broken-jar-problem nicely. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCOMPILER-223) Move to a non-ancient maven-toolchain dependency
[ https://jira.codehaus.org/browse/MCOMPILER-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise closed MCOMPILER-223. - Resolution: Fixed Assignee: Karl-Heinz Marbaise Fixed in [r1652303|http://svn.apache.org/r1652303] > Move to a non-ancient maven-toolchain dependency > > > Key: MCOMPILER-223 > URL: https://jira.codehaus.org/browse/MCOMPILER-223 > Project: Maven Compiler Plugin > Issue Type: Bug >Reporter: Noa Resare >Assignee: Karl-Heinz Marbaise >Priority: Minor > Fix For: 3.3 > > > It turns out that the maven-toolchain-1.0.jar available form maven central > has some serious issues resulting in it not being extractable by the oracle > provided jar tool (the toplevel directories in the archives are empty files > and not directories, which breaks extraction) > Some tools (IntelliJ in my case) expect to be able to extract jarfiles to be > able to see the contents. > Looking into the maven-toolchain artifact it seems like it has moved into > maven-core for 3.x versions, but for 2.x versions it kind of tracks the maven > release. > Because of this, I propose that we use $mavenVersion for the maven-toolchain > dependency (2.0.9 in our case) which seems to do the right thing and works > around my broken-jar-problem nicely. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5753) Allow plugin implementors to choose how they want the configuration created for a particular MojoExecution
[ https://jira.codehaus.org/browse/MNG-5753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl closed MNG-5753. -- Resolution: Fixed > Allow plugin implementors to choose how they want the configuration created > for a particular MojoExecution > -- > > Key: MNG-5753 > URL: https://jira.codehaus.org/browse/MNG-5753 > Project: Maven > Issue Type: New Feature >Reporter: Jason van Zyl >Assignee: Jason van Zyl >Priority: Minor > Fix For: 3.2.6 > > > Provide finer grained control over how a is processed before > handing a final mojo configuration over the Configurator which takes the > configuration and applies it to the Mojo. My specific use case is that I want > to allow many mojos to be configured clearly by scoping the configuration for > a Mojo by Mojo name. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5753) Allow plugin implementors to choose how they want the configuration created for a particular MojoExecution
[ https://jira.codehaus.org/browse/MNG-5753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=361275#comment-361275 ] Jason van Zyl commented on MNG-5753: Implemented on 36d491a64856e4ffcb16175753783b0ef991870b > Allow plugin implementors to choose how they want the configuration created > for a particular MojoExecution > -- > > Key: MNG-5753 > URL: https://jira.codehaus.org/browse/MNG-5753 > Project: Maven > Issue Type: New Feature >Reporter: Jason van Zyl >Assignee: Jason van Zyl >Priority: Minor > Fix For: 3.2.6 > > > Provide finer grained control over how a is processed before > handing a final mojo configuration over the Configurator which takes the > configuration and applies it to the Mojo. My specific use case is that I want > to allow many mojos to be configured clearly by scoping the configuration for > a Mojo by Mojo name. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCHECKSTYLE-268) Add flag/option to use built-in Google style
[ https://jira.codehaus.org/browse/MCHECKSTYLE-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=361276#comment-361276 ] Henning Schmiedehausen commented on MCHECKSTYLE-268: I would keep config/sun_checks.xml for one release to allow for reasonable deprecation and then remove it in the next release afterwards. > Add flag/option to use built-in Google style > > > Key: MCHECKSTYLE-268 > URL: https://jira.codehaus.org/browse/MCHECKSTYLE-268 > Project: Maven Checkstyle Plugin > Issue Type: Wish >Reporter: Christopher Tubbs > > Checkstyle 6 adds a style which implements the [Google Style > Guide|https://code.google.com/p/google-styleguide/], called > [google_chekcs.xml|https://github.com/checkstyle/checkstyle/blob/master/google_checks.xml]. > It would be nice to expose this style with a flag, providing it with the > plugin, rather than requiring a user to specify the style file directly. This > would make it easier for multi-module projects to easily adopt and configure > a standard style, provided by the upstream Checkstyle project. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCHECKSTYLE-272) Upgrade to Checkstyle 6.2
[ https://jira.codehaus.org/browse/MCHECKSTYLE-272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=361278#comment-361278 ] Henning Schmiedehausen commented on MCHECKSTYLE-272: Fix is at https://github.com/apache/maven-plugins/pull/42 (and on the MCHECKSTYLE-272 branch in subversion) > Upgrade to Checkstyle 6.2 > - > > Key: MCHECKSTYLE-272 > URL: https://jira.codehaus.org/browse/MCHECKSTYLE-272 > Project: Maven Checkstyle Plugin > Issue Type: Improvement >Reporter: Dennis Lundberg > Fix For: 2.16 > > > This version of Checkstyle requires Java 7. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MGPG-27) Allow option to create none ascii output
[ https://jira.codehaus.org/browse/MGPG-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran closed MGPG-27. Resolution: Won't Fix Withdraw this request since I no longer have a need for this ehancement > Allow option to create none ascii output > > > Key: MGPG-27 > URL: https://jira.codehaus.org/browse/MGPG-27 > Project: Maven GPG Plugin > Issue Type: New Feature >Affects Versions: 1.1 > Environment: all >Reporter: Dan Tran > Labels: scrub-review-started > > Please add new option "armor" with default value "true" to keep the default > behavior. > The motivation is i am currently have a sh script using gpg and expect the > produce a binary gpg file. It would be nice for me to use maven-gpg-plugin > intead -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCHECKSTYLE-253) Upgrade to checkstyle 5.9 for Java 8 compatibility
[ https://jira.codehaus.org/browse/MCHECKSTYLE-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MCHECKSTYLE-253: Fix Version/s: (was: 2.14) > Upgrade to checkstyle 5.9 for Java 8 compatibility > -- > > Key: MCHECKSTYLE-253 > URL: https://jira.codehaus.org/browse/MCHECKSTYLE-253 > Project: Maven Checkstyle Plugin > Issue Type: New Feature >Reporter: Zlika >Assignee: Dennis Lundberg > > Checkstyle 5.9 has just been released and adds support for Java 8. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCHECKSTYLE-253) Upgrade to checkstyle 5.9 for Java 8 compatibility
[ https://jira.codehaus.org/browse/MCHECKSTYLE-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg reopened MCHECKSTYLE-253: - Assignee: Dennis Lundberg (was: Mirko Friedenhagen) This will be reverted in favor of MCHECKSTYLE-261. > Upgrade to checkstyle 5.9 for Java 8 compatibility > -- > > Key: MCHECKSTYLE-253 > URL: https://jira.codehaus.org/browse/MCHECKSTYLE-253 > Project: Maven Checkstyle Plugin > Issue Type: New Feature >Reporter: Zlika >Assignee: Dennis Lundberg > > Checkstyle 5.9 has just been released and adds support for Java 8. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCHECKSTYLE-261) Upgrade to Checkstyle 6.1.1
[ https://jira.codehaus.org/browse/MCHECKSTYLE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg reassigned MCHECKSTYLE-261: --- Assignee: Dennis Lundberg > Upgrade to Checkstyle 6.1.1 > --- > > Key: MCHECKSTYLE-261 > URL: https://jira.codehaus.org/browse/MCHECKSTYLE-261 > Project: Maven Checkstyle Plugin > Issue Type: Improvement >Affects Versions: 2.14 >Reporter: Dennis Lundberg >Assignee: Dennis Lundberg > Fix For: 2.15 > > > Upgrade to the latest 6.x version of Checkstyle, which at the time of writing > is 6.1. > Note that this upgrade will make the Checkstyle plugin require Java 6, > because Checkstyle requires Java 6 since version 5.9. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
