[jira] (MCHANGES-351) No paging when maxEntries is reached
[
https://jira.codehaus.org/browse/MCHANGES-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Eckenfels updated MCHANGES-351:
-
Description:
I try to generate a JIRA changes report for apache commons VFS. If I set the
maxEntries to 600 it wont work. It looks like the Apache Instance only allows
to search for 100 entries (JIRA On Demand seems to be limited to 1000). In my
case there are 141 bugs in the current fixversion and the query finds 295).
According to the JIRA docu you can query with different offsets, so would it be
possible to query startAt=0-99,100-199,... and so on?
Here is the request and the response:
{code}
Address: https://issues.apache.org/jira/rest/api/2/search
Http-Method: POST
Content-Type: application/json
Headers: {Accept=[application/json], Content-Type=[application/json],
Payload: {"jql":"project = VFS AND status in (5, 6) AND resolution in
(1) AND type in (1, 2, 3, 4, 5, 6) ORDER BY fixversion DESC, type ASC,
key DESC","maxResults":600,"fields":["*all"]...
Response-Code: 200
Encoding: UTF-8
Content-Type: application/json;charset=UTF-8
Headers: \{Cache-Control=[no-cache, no-store, no-transform],
connection=[Keep-Alive], content-type=[application/json;charset=UTF-8],
Date=[Mon, 19 Jan 2015 01:50:37 GMT], Keep-Alive=[timeout=5, max=96],
Server=[Apache-Coyote/1.1],
Set-Cookie=[JSESSIONID=4871902251E72BC474B2D32941521F9A; Path=/jira/; Secure;
HttpOnly], transfer-encoding=[chunked], X-AREQUESTID=[110x29767730x2],
X-ASEN=[SEN-2062203], X-AUSERNAME=[anonymous], X-Content-Type-Options=[nosniff]}
Messages:
Message (saved to tmp file):
Filename:
C:\Users\eckenfel\AppData\Local\Temp\cxf-tmp-435678\cos4903552076318255093tmp
(message truncated to 102400 bytes)
Payload:
{"expand":"schema,names","startAt":0,"maxResults":100,"total":295, ...
{code}
was:
I try to generate a JIRA changes report for apache commons VFS. If I set the
maxEntries to 600 it wont work. It looks like the Apache Instance only allows
to search for 100 entries (JIRA On Demand seems to be limited to 1000). In my
case there are 141 bugs in the current fixversion and the query finds 295).
According to the JIRA docu you can query with different offsets, so would it be
possible to query startAt=0-99,100-199,... and so on?
Here is the request and the response:
{quote}
Address: https://issues.apache.org/jira/rest/api/2/search
Http-Method: POST
Content-Type: application/json
Headers: {Accept=[application/json], Content-Type=[application/json],
Payload: {"jql":"project = VFS AND status in (5, 6) AND resolution in
(1) AND type in (1, 2, 3, 4, 5, 6) ORDER BY fixversion DESC, type ASC,
key DESC","maxResults":600,"fields":["*all"]}
Response-Code: 200
Encoding: UTF-8
Content-Type: application/json;charset=UTF-8
Headers: {Cache-Control=[no-cache, no-store, no-transform],
connection=[Keep-Alive], content-type=[application/json;charset=UTF-8],
Date=[Mon, 19 Jan 2015 01:50:37 GMT], Keep-Alive=[timeout=5, max=96],
Server=[Apache-Coyote/1.1],
Set-Cookie=[JSESSIONID=4871902251E72BC474B2D32941521F9A; Path=/jira/; Secure;
HttpOnly], transfer-encoding=[chunked], X-AREQUESTID=[110x29767730x2],
X-ASEN=[SEN-2062203], X-AUSERNAME=[anonymous], X-Content-Type-Options=[nosniff]}
Messages:
Message (saved to tmp file):
Filename:
C:\Users\eckenfel\AppData\Local\Temp\cxf-tmp-435678\cos4903552076318255093tmp
(message truncated to 102400 bytes)
Payload:
{"expand":"schema,names","startAt":0,"maxResults":100,"total":295, ...
{quote}
> No paging when maxEntries is reached
>
>
> Key: MCHANGES-351
> URL: https://jira.codehaus.org/browse/MCHANGES-351
> Project: Maven Changes Plugin
> Issue Type: Bug
> Components: jira
>Affects Versions: 2.11
> Environment: Maven 3.2.5; Java 1.7.0_72 x64 on win7, german
>Reporter: Bernd Eckenfels
>
> I try to generate a JIRA changes report for apache commons VFS. If I set the
> maxEntries to 600 it wont work. It looks like the Apache Instance only allows
> to search for 100 entries (JIRA On Demand seems to be limited to 1000). In my
> case there are 141 bugs in the current fixversion and the query finds 295).
> According to the JIRA docu you can query with different offsets, so would it
> be possible to query startAt=0-99,100-199,... and so on?
> Here is the request and the response:
> {code}
> Address: https://issues.apache.org/jira/rest/api/2/search
> Http-Method: POST
> Content-Type: application/json
> Headers: {Accept=[application/json], Content-Type=[application/json],
> Payload: {"jql":"project = VFS AND status in (5, 6) AND resolution in
> (1) AND type in (1, 2, 3, 4, 5, 6) ORDER BY fixversion DESC, type ASC,
> key DESC","maxResults":600,"fields":["*all"]...
> Response-Code: 200
> Encoding: UTF-8
> Content-Type: application/json;charset=UTF-8
> Headers: \{Cache-Control=[no-cache, no-store, no-tr
[jira] (MCHANGES-351) No paging when maxEntries is reached
Bernd Eckenfels created MCHANGES-351:
Summary: No paging when maxEntries is reached
Key: MCHANGES-351
URL: https://jira.codehaus.org/browse/MCHANGES-351
Project: Maven Changes Plugin
Issue Type: Bug
Components: jira
Affects Versions: 2.11
Environment: Maven 3.2.5; Java 1.7.0_72 x64 on win7, german
Reporter: Bernd Eckenfels
I try to generate a JIRA changes report for apache commons VFS. If I set the
maxEntries to 600 it wont work. It looks like the Apache Instance only allows
to search for 100 entries (JIRA On Demand seems to be limited to 1000). In my
case there are 141 bugs in the current fixversion and the query finds 295).
According to the JIRA docu you can query with different offsets, so would it be
possible to query startAt=0-99,100-199,... and so on?
Here is the request and the response:
{quote}
Address: https://issues.apache.org/jira/rest/api/2/search
Http-Method: POST
Content-Type: application/json
Headers: {Accept=[application/json], Content-Type=[application/json],
Payload: {"jql":"project = VFS AND status in (5, 6) AND resolution in
(1) AND type in (1, 2, 3, 4, 5, 6) ORDER BY fixversion DESC, type ASC,
key DESC","maxResults":600,"fields":["*all"]}
Response-Code: 200
Encoding: UTF-8
Content-Type: application/json;charset=UTF-8
Headers: {Cache-Control=[no-cache, no-store, no-transform],
connection=[Keep-Alive], content-type=[application/json;charset=UTF-8],
Date=[Mon, 19 Jan 2015 01:50:37 GMT], Keep-Alive=[timeout=5, max=96],
Server=[Apache-Coyote/1.1],
Set-Cookie=[JSESSIONID=4871902251E72BC474B2D32941521F9A; Path=/jira/; Secure;
HttpOnly], transfer-encoding=[chunked], X-AREQUESTID=[110x29767730x2],
X-ASEN=[SEN-2062203], X-AUSERNAME=[anonymous], X-Content-Type-Options=[nosniff]}
Messages:
Message (saved to tmp file):
Filename:
C:\Users\eckenfel\AppData\Local\Temp\cxf-tmp-435678\cos4903552076318255093tmp
(message truncated to 102400 bytes)
Payload:
{"expand":"schema,names","startAt":0,"maxResults":100,"total":295, ...
{quote}
--
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=361354#comment-361354
]
Herve Boutemy commented on MCHECKSTYLE-268:
---
ok for {{config/sun_checks.xml}}: we'll do like MCHECKSTYLE-281
and for runtime upgrade of Checkstyle, see MCHECKSTYLE-280
> 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-249) ITs failing when building on Windows from distribution prepared on Unix
[
https://jira.codehaus.org/browse/MCHECKSTYLE-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy closed MCHECKSTYLE-249.
-
Resolution: Fixed
Assignee: Herve Boutemy
done in [r1652861|http://svn.apache.org/r1652861]
> ITs failing when building on Windows from distribution prepared on Unix
> ---
>
> Key: MCHECKSTYLE-249
> URL: https://jira.codehaus.org/browse/MCHECKSTYLE-249
> Project: Maven Checkstyle Plugin
> Issue Type: Bug
>Affects Versions: 2.13
>Reporter: Herve Boutemy
>Assignee: Herve Boutemy
>Priority: Blocker
> Fix For: 2.14
>
>
> {noformat}[INFO] -
> [INFO] Build Summary:
> [INFO] Passed: 28, Failed: 4, Errors: 0, Skipped: 0
> [INFO] -
> [ERROR] The following builds failed:
> [ERROR] * avalon-checks\pom.xml
> [ERROR] * check-fail\pom.xml
> [ERROR] * MCHECKSTYLE-169\pom.xml
> [ERROR] * turbine-checks\pom.xml
> [INFO] -{noformat}
> They all fail for the same reason:
> NewlineAtEndOfFile: File does not end with a newline.
> The zip file contains Unix newlines, which are not recognized by Checkstyle...
> see
> http://mail-archives.apache.org/mod_mbox/maven-dev/201409.mbox/%3Cop.xmegy1trkdkhrr%40robertscholte.dynamic.ziggo.nl%3E
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MCHECKSTYLE-281) fail if deprecated parameters are used and display update instructions
[ https://jira.codehaus.org/browse/MCHECKSTYLE-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MCHECKSTYLE-281. - Resolution: Fixed Fix Version/s: 2.14 Assignee: Herve Boutemy done in [r1652857|http://svn.apache.org/r1652857] > fail if deprecated parameters are used and display update instructions > -- > > Key: MCHECKSTYLE-281 > URL: https://jira.codehaus.org/browse/MCHECKSTYLE-281 > Project: Maven Checkstyle Plugin > Issue Type: Task > Components: checkstyle:checkstyle >Affects Versions: 2.13 >Reporter: Herve Boutemy >Assignee: Herve Boutemy > Fix For: 2.14 > > > first step before removing in MCHECKSTYLE-275 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCHECKSTYLE-281) fail if deprecated parameters are used and display update instructions
Herve Boutemy created MCHECKSTYLE-281: - Summary: fail if deprecated parameters are used and display update instructions Key: MCHECKSTYLE-281 URL: https://jira.codehaus.org/browse/MCHECKSTYLE-281 Project: Maven Checkstyle Plugin Issue Type: Task Components: checkstyle:checkstyle Affects Versions: 2.13 Reporter: Herve Boutemy first step before removing in MCHECKSTYLE-275 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCHECKSTYLE-249) ITs failing when building on Windows from distribution prepared on Unix
[
https://jira.codehaus.org/browse/MCHECKSTYLE-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=361350#comment-361350
]
Herve Boutemy edited comment on MCHECKSTYLE-249 at 1/18/15 3:28 PM:
no: let's keep the config since it will be used in the report during the
release, but it doesn't fail the build since it is marked in Maven parent pom
as ignore violation
we just need to add the ignore violation in ITs
was (Author: hboutemy):
no: let's keep the config since it will be used in the report during the
release, but it doesn't fail the build since it is marked in Maven parent pom
as ignore violation
> ITs failing when building on Windows from distribution prepared on Unix
> ---
>
> Key: MCHECKSTYLE-249
> URL: https://jira.codehaus.org/browse/MCHECKSTYLE-249
> Project: Maven Checkstyle Plugin
> Issue Type: Bug
>Affects Versions: 2.13
>Reporter: Herve Boutemy
>Priority: Blocker
> Fix For: 2.14
>
>
> {noformat}[INFO] -
> [INFO] Build Summary:
> [INFO] Passed: 28, Failed: 4, Errors: 0, Skipped: 0
> [INFO] -
> [ERROR] The following builds failed:
> [ERROR] * avalon-checks\pom.xml
> [ERROR] * check-fail\pom.xml
> [ERROR] * MCHECKSTYLE-169\pom.xml
> [ERROR] * turbine-checks\pom.xml
> [INFO] -{noformat}
> They all fail for the same reason:
> NewlineAtEndOfFile: File does not end with a newline.
> The zip file contains Unix newlines, which are not recognized by Checkstyle...
> see
> http://mail-archives.apache.org/mod_mbox/maven-dev/201409.mbox/%3Cop.xmegy1trkdkhrr%40robertscholte.dynamic.ziggo.nl%3E
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MCHECKSTYLE-249) ITs failing when building on Windows from distribution prepared on Unix
[
https://jira.codehaus.org/browse/MCHECKSTYLE-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=361350#comment-361350
]
Herve Boutemy commented on MCHECKSTYLE-249:
---
no: let's keep the config since it will be used in the report during the
release, but it doesn't fail the build since it is marked in Maven parent pom
as ignore violation
> ITs failing when building on Windows from distribution prepared on Unix
> ---
>
> Key: MCHECKSTYLE-249
> URL: https://jira.codehaus.org/browse/MCHECKSTYLE-249
> Project: Maven Checkstyle Plugin
> Issue Type: Bug
>Affects Versions: 2.13
>Reporter: Herve Boutemy
>Priority: Blocker
> Fix For: 2.14
>
>
> {noformat}[INFO] -
> [INFO] Build Summary:
> [INFO] Passed: 28, Failed: 4, Errors: 0, Skipped: 0
> [INFO] -
> [ERROR] The following builds failed:
> [ERROR] * avalon-checks\pom.xml
> [ERROR] * check-fail\pom.xml
> [ERROR] * MCHECKSTYLE-169\pom.xml
> [ERROR] * turbine-checks\pom.xml
> [INFO] -{noformat}
> They all fail for the same reason:
> NewlineAtEndOfFile: File does not end with a newline.
> The zip file contains Unix newlines, which are not recognized by Checkstyle...
> see
> http://mail-archives.apache.org/mod_mbox/maven-dev/201409.mbox/%3Cop.xmegy1trkdkhrr%40robertscholte.dynamic.ziggo.nl%3E
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MCHECKSTYLE-249) ITs failing when building on Windows from distribution prepared on Unix
[
https://jira.codehaus.org/browse/MCHECKSTYLE-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=361348#comment-361348
]
Dennis Lundberg commented on MCHECKSTYLE-249:
-
That solution won't be ready until 2.17, since it requires changes to
Checkstyle.
Do we want to disable NewlineAtEndOfFile from the Maven config until then?
> ITs failing when building on Windows from distribution prepared on Unix
> ---
>
> Key: MCHECKSTYLE-249
> URL: https://jira.codehaus.org/browse/MCHECKSTYLE-249
> Project: Maven Checkstyle Plugin
> Issue Type: Bug
>Affects Versions: 2.13
>Reporter: Herve Boutemy
>Priority: Blocker
> Fix For: 2.14
>
>
> {noformat}[INFO] -
> [INFO] Build Summary:
> [INFO] Passed: 28, Failed: 4, Errors: 0, Skipped: 0
> [INFO] -
> [ERROR] The following builds failed:
> [ERROR] * avalon-checks\pom.xml
> [ERROR] * check-fail\pom.xml
> [ERROR] * MCHECKSTYLE-169\pom.xml
> [ERROR] * turbine-checks\pom.xml
> [INFO] -{noformat}
> They all fail for the same reason:
> NewlineAtEndOfFile: File does not end with a newline.
> The zip file contains Unix newlines, which are not recognized by Checkstyle...
> see
> http://mail-archives.apache.org/mod_mbox/maven-dev/201409.mbox/%3Cop.xmegy1trkdkhrr%40robertscholte.dynamic.ziggo.nl%3E
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MCHECKSTYLE-280) add documentation on upgrading Checkstyle at runtime
[ https://jira.codehaus.org/browse/MCHECKSTYLE-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MCHECKSTYLE-280. - Resolution: Fixed Fix Version/s: 2.14 Assignee: Herve Boutemy done in [r1652846|http://svn.apache.org/r1652846] > add documentation on upgrading Checkstyle at runtime > > > Key: MCHECKSTYLE-280 > URL: https://jira.codehaus.org/browse/MCHECKSTYLE-280 > Project: Maven Checkstyle Plugin > Issue Type: Task >Affects Versions: 2.13 >Reporter: Herve Boutemy >Assignee: Herve Boutemy > Fix For: 2.14 > > > we are staying with older Checkstyle versions as plugin's default to keep > minimum java version requirement > But if users have less stric minimum java version requirement, they can > upgrade at runtime: we need to explain it -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCHECKSTYLE-280) add documentation on upgrading Checkstyle at runtime
Herve Boutemy created MCHECKSTYLE-280: - Summary: add documentation on upgrading Checkstyle at runtime Key: MCHECKSTYLE-280 URL: https://jira.codehaus.org/browse/MCHECKSTYLE-280 Project: Maven Checkstyle Plugin Issue Type: Task Affects Versions: 2.13 Reporter: Herve Boutemy we are staying with older Checkstyle versions as plugin's default to keep minimum java version requirement But if users have less stric minimum java version requirement, they can upgrade at runtime: we need to explain it -- 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:all-tabpanel ] Michael Osipov closed MNGSITE-221. -- Resolution: Fixed Fixed with [r1652845|http://svn.apache.org/r1652845]. > Broken link in maven site > - > > Key: MNGSITE-221 > URL: https://jira.codehaus.org/browse/MNGSITE-221 > Project: Maven Project Web Site > Issue Type: Bug >Reporter: Venkatachalam Muthusamy >Assignee: Michael Osipov >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] (MCHECKSTYLE-257) display content/documentation of Checkstyle configurations predefined by maven-checkstyle-plugin in plugin's documentation site
[ https://jira.codehaus.org/browse/MCHECKSTYLE-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MCHECKSTYLE-257. - Resolution: Fixed Assignee: Herve Boutemy done as simple includes in [r1652807|http://svn.apache.org/r1652807] > display content/documentation of Checkstyle configurations predefined by > maven-checkstyle-plugin in plugin's documentation site > --- > > Key: MCHECKSTYLE-257 > URL: https://jira.codehaus.org/browse/MCHECKSTYLE-257 > Project: Maven Checkstyle Plugin > Issue Type: Improvement > Components: predefined ruleset: Maven , predefined ruleset: Sun >Affects Versions: 2.13 >Reporter: Herve Boutemy >Assignee: Herve Boutemy > Fix For: 2.14 > > > since the configuration evolves over plugin versions, we should at least > include a page with configuration inserted as pre > if we have more ambition, we can display a table with each rule and > configuration, like it was done for m-checkstyle-p 2.12 (ie displaying every > configured rules, even if no violation) > perhaps this could be a new report in this plugin: checkstyle configuration > documentation -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCHECKSTYLE-279) mark ParameterNumber, MethodLength and FileLength rules as warning only
Herve Boutemy created MCHECKSTYLE-279: - Summary: mark ParameterNumber, MethodLength and FileLength rules as warning only Key: MCHECKSTYLE-279 URL: https://jira.codehaus.org/browse/MCHECKSTYLE-279 Project: Maven Checkstyle Plugin Issue Type: Task Components: predefined ruleset: Maven Affects Versions: 2.13 Reporter: Herve Boutemy These rules by default cause an error: Maven parent pom marks them as "ignore violation", since we don't really enforce refactoring when limits are hit Perhpas it would be better to just mark these rules as warning: it's the way we use them -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCHECKSTYLE-249) ITs failing when building on Windows from distribution prepared on Unix
[
https://jira.codehaus.org/browse/MCHECKSTYLE-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=361343#comment-361343
]
Herve Boutemy commented on MCHECKSTYLE-249:
---
+1 to "any" option for NewlineAtEndOfFile check: consistency is another
requirement
> ITs failing when building on Windows from distribution prepared on Unix
> ---
>
> Key: MCHECKSTYLE-249
> URL: https://jira.codehaus.org/browse/MCHECKSTYLE-249
> Project: Maven Checkstyle Plugin
> Issue Type: Bug
>Affects Versions: 2.13
>Reporter: Herve Boutemy
>Priority: Blocker
> Fix For: 2.14
>
>
> {noformat}[INFO] -
> [INFO] Build Summary:
> [INFO] Passed: 28, Failed: 4, Errors: 0, Skipped: 0
> [INFO] -
> [ERROR] The following builds failed:
> [ERROR] * avalon-checks\pom.xml
> [ERROR] * check-fail\pom.xml
> [ERROR] * MCHECKSTYLE-169\pom.xml
> [ERROR] * turbine-checks\pom.xml
> [INFO] -{noformat}
> They all fail for the same reason:
> NewlineAtEndOfFile: File does not end with a newline.
> The zip file contains Unix newlines, which are not recognized by Checkstyle...
> see
> http://mail-archives.apache.org/mod_mbox/maven-dev/201409.mbox/%3Cop.xmegy1trkdkhrr%40robertscholte.dynamic.ziggo.nl%3E
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MCHECKSTYLE-249) ITs failing when building on Windows from distribution prepared on Unix
[
https://jira.codehaus.org/browse/MCHECKSTYLE-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=361342#comment-361342
]
Dennis Lundberg commented on MCHECKSTYLE-249:
-
Remember that this check just makes sure that the files ends with a line
separator. It does not check if line separators are consistent inside a file.
The would be the job of another check, and a nice one I think.
> ITs failing when building on Windows from distribution prepared on Unix
> ---
>
> Key: MCHECKSTYLE-249
> URL: https://jira.codehaus.org/browse/MCHECKSTYLE-249
> Project: Maven Checkstyle Plugin
> Issue Type: Bug
>Affects Versions: 2.13
>Reporter: Herve Boutemy
>Priority: Blocker
> Fix For: 2.14
>
>
> {noformat}[INFO] -
> [INFO] Build Summary:
> [INFO] Passed: 28, Failed: 4, Errors: 0, Skipped: 0
> [INFO] -
> [ERROR] The following builds failed:
> [ERROR] * avalon-checks\pom.xml
> [ERROR] * check-fail\pom.xml
> [ERROR] * MCHECKSTYLE-169\pom.xml
> [ERROR] * turbine-checks\pom.xml
> [INFO] -{noformat}
> They all fail for the same reason:
> NewlineAtEndOfFile: File does not end with a newline.
> The zip file contains Unix newlines, which are not recognized by Checkstyle...
> see
> http://mail-archives.apache.org/mod_mbox/maven-dev/201409.mbox/%3Cop.xmegy1trkdkhrr%40robertscholte.dynamic.ziggo.nl%3E
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MCHECKSTYLE-252) Version 2.13 includes non-source files in checks
[
https://jira.codehaus.org/browse/MCHECKSTYLE-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=361341#comment-361341
]
Dennis Lundberg commented on MCHECKSTYLE-252:
-
I've had a look at the attached project and here are my findings on it.
{noformat}
COPYING
COPYING.LESSER
{noformat}
These are included by Checkstyle because they are defined as resources in the
POM.
{code:xml}
${basedir}/src/main/resources
false
META-INF
false
${basedir}
COPYING
COPYING.LESSER
{code}
This is because of the fix for MCHECKSTYLE-70. A work-around for your problem
is available at
http://jira.codehaus.org/browse/MCHECKSTYLE-70?focusedCommentId=353837&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-353837
{noformat}
target/generated-classes/cobertura/cobertura.properties
{noformat}
This file I'm not sure why it is included, but I suspect that Cobertura has
something to to with it, beacause it alters the classpath of the project.
To summarize, Maven Checkstyle Plugin 2.13 does not include non-source files in
the check, but it does include more sources than version 2.12.
> Version 2.13 includes non-source files in checks
>
>
> Key: MCHECKSTYLE-252
> URL: https://jira.codehaus.org/browse/MCHECKSTYLE-252
> Project: Maven Checkstyle Plugin
> Issue Type: Bug
> Components: checkstyle:checkstyle
>Affects Versions: 2.13
>Reporter: Michael Heuer
> Fix For: 2.14
>
> Attachments: mcheckstyle-252.tar.gz
>
>
> Updating maven-checkstyle-plugin to version 2.13 and running
> {noformat}$ mvn site{noformat}
> now includes non-source files in its checks, e.g.
> {noformat}COPYING
> COPYING.LESSER
> target/generated-classes/cobertura/cobertura.properties{noformat}
> While it is rather amusing to have checkstyle complain that COPYING (the text
> of the GNU General Public License) doesn't include a license header, it seems
> that the default source root or one of the other properties new to version
> 2.13 does not have an appropriate default value. The target directory should
> also be excluded by default.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5755) Access toolchains without maven-toolchain-plugin
[ https://jira.codehaus.org/browse/MNG-5755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MNG-5755. --- Resolution: Fixed Fix Version/s: 3.2.6 Fixed in [4b263106db043f5c1d7c314237ab2bc8708c0538|http://git-wip-us.apache.org/repos/asf/maven/commit/4b263106] > Access toolchains without maven-toolchain-plugin > > > Key: MNG-5755 > URL: https://jira.codehaus.org/browse/MNG-5755 > Project: Maven > Issue Type: New Feature > Components: Toolchains >Affects Versions: 3.2.5 >Reporter: Robert Scholte >Assignee: Robert Scholte > Fix For: 3.2.6 > > > The original idea of toolchains was to have the same tool being used by > different plugins within the same project. > This seems like a good approach, but there are several cases where you want > more control over the tool to choose, for instance: > * the maven-compiler-plugin should use the lowest (preferably matching) jdk > version to ensure proper bytecode for the classes > * the maven-surefire-plugin might need a higher version due to requirements > of the testing frameworks > * some code-generators require a more recent JDK compared to the code they're > actually producing. > * the look-and-feel of javadoc has changed per JDK. If you like the latest, > you should be able to use it. > * In case of the maven-invoker-plugin you should be able to test all > combinations of JDK and Maven as runtime environment. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCHECKSTYLE-249) ITs failing when building on Windows from distribution prepared on Unix
[
https://jira.codehaus.org/browse/MCHECKSTYLE-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=361339#comment-361339
]
Robert Scholte commented on MCHECKSTYLE-249:
I think it's more important that the line separator is consistent, not just
any. So the first one you hit should be the one used throughout the project.
> ITs failing when building on Windows from distribution prepared on Unix
> ---
>
> Key: MCHECKSTYLE-249
> URL: https://jira.codehaus.org/browse/MCHECKSTYLE-249
> Project: Maven Checkstyle Plugin
> Issue Type: Bug
>Affects Versions: 2.13
>Reporter: Herve Boutemy
>Priority: Blocker
> Fix For: 2.14
>
>
> {noformat}[INFO] -
> [INFO] Build Summary:
> [INFO] Passed: 28, Failed: 4, Errors: 0, Skipped: 0
> [INFO] -
> [ERROR] The following builds failed:
> [ERROR] * avalon-checks\pom.xml
> [ERROR] * check-fail\pom.xml
> [ERROR] * MCHECKSTYLE-169\pom.xml
> [ERROR] * turbine-checks\pom.xml
> [INFO] -{noformat}
> They all fail for the same reason:
> NewlineAtEndOfFile: File does not end with a newline.
> The zip file contains Unix newlines, which are not recognized by Checkstyle...
> see
> http://mail-archives.apache.org/mod_mbox/maven-dev/201409.mbox/%3Cop.xmegy1trkdkhrr%40robertscholte.dynamic.ziggo.nl%3E
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MCHECKSTYLE-249) ITs failing when building on Windows from distribution prepared on Unix
[
https://jira.codehaus.org/browse/MCHECKSTYLE-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=361338#comment-361338
]
Dennis Lundberg commented on MCHECKSTYLE-249:
-
How do we want to handle this for the 2.14 release?
I've checked the source for Checkstyle and it's doable to add an "any" option
for the NewlineAtEndOfFile check, even though it will probable be a bit slower
than the current options.
> ITs failing when building on Windows from distribution prepared on Unix
> ---
>
> Key: MCHECKSTYLE-249
> URL: https://jira.codehaus.org/browse/MCHECKSTYLE-249
> Project: Maven Checkstyle Plugin
> Issue Type: Bug
>Affects Versions: 2.13
>Reporter: Herve Boutemy
>Priority: Blocker
> Fix For: 2.14
>
>
> {noformat}[INFO] -
> [INFO] Build Summary:
> [INFO] Passed: 28, Failed: 4, Errors: 0, Skipped: 0
> [INFO] -
> [ERROR] The following builds failed:
> [ERROR] * avalon-checks\pom.xml
> [ERROR] * check-fail\pom.xml
> [ERROR] * MCHECKSTYLE-169\pom.xml
> [ERROR] * turbine-checks\pom.xml
> [INFO] -{noformat}
> They all fail for the same reason:
> NewlineAtEndOfFile: File does not end with a newline.
> The zip file contains Unix newlines, which are not recognized by Checkstyle...
> see
> http://mail-archives.apache.org/mod_mbox/maven-dev/201409.mbox/%3Cop.xmegy1trkdkhrr%40robertscholte.dynamic.ziggo.nl%3E
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MCHECKSTYLE-274) remove Avalon configuration since the Avalon project is retired
[ https://jira.codehaus.org/browse/MCHECKSTYLE-274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=361337#comment-361337 ] Dennis Lundberg commented on MCHECKSTYLE-274: - Removed some documentation in [r1652772|http://svn.apache.org/viewvc?view=revision&revision=1652772]. > remove Avalon configuration since the Avalon project is retired > --- > > Key: MCHECKSTYLE-274 > URL: https://jira.codehaus.org/browse/MCHECKSTYLE-274 > Project: Maven Checkstyle Plugin > Issue Type: Task >Affects Versions: 2.13 >Reporter: Herve Boutemy >Assignee: Herve Boutemy >Priority: Trivial > Fix For: 2.14 > > > I don't expect the configuration to be used by anybody else than the Avalon > project (http://avalon.apache.org ) which is retired > removing the configuration should be safe -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MECLIPSE-705) Use Aether (or the shared exposed interface) to ensure correct .classpath ordering of dependencies.
[ https://jira.codehaus.org/browse/MECLIPSE-705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated MECLIPSE-705: - Fix Version/s: (was: 2.10) > Use Aether (or the shared exposed interface) to ensure correct .classpath > ordering of dependencies. > --- > > Key: MECLIPSE-705 > URL: https://jira.codehaus.org/browse/MECLIPSE-705 > Project: Maven Eclipse Plugin > Issue Type: Bug > Components: Core : Dependencies resolution and build path > (.classpath) >Affects Versions: 2.9 >Reporter: Barrie Treloar >Priority: Critical > > The eclipse plugin works out the classpath ordering itself. > It should be re-using whatever is done internally by Maven. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MDOAP-45) Upgrade plexus-i18n to 1.0-beta-10
[ https://jira.codehaus.org/browse/MDOAP-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise closed MDOAP-45. Resolution: Fixed Assignee: Karl-Heinz Marbaise Fixed in [r1652765|http://svn.apache.org/r1652765] > Upgrade plexus-i18n to 1.0-beta-10 > -- > > Key: MDOAP-45 > URL: https://jira.codehaus.org/browse/MDOAP-45 > Project: Maven DOAP Plugin > Issue Type: Improvement >Affects Versions: 1.2 >Reporter: Karl-Heinz Marbaise >Assignee: Karl-Heinz Marbaise >Priority: Minor > Fix For: 1.2 > > -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MDOAP-45) Upgrade plexus-i18n to 1.0-beta-10
Karl-Heinz Marbaise created MDOAP-45: Summary: Upgrade plexus-i18n to 1.0-beta-10 Key: MDOAP-45 URL: https://jira.codehaus.org/browse/MDOAP-45 Project: Maven DOAP Plugin Issue Type: Improvement Affects Versions: 1.2 Reporter: Karl-Heinz Marbaise Priority: Minor -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MDOAP-44) Upgrade plexus-utils to 3.0.20
[ https://jira.codehaus.org/browse/MDOAP-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise closed MDOAP-44. Resolution: Fixed Assignee: Karl-Heinz Marbaise Fixed in [r1652763|http://svn.apache.org/r1652763] > Upgrade plexus-utils to 3.0.20 > -- > > Key: MDOAP-44 > URL: https://jira.codehaus.org/browse/MDOAP-44 > Project: Maven DOAP Plugin > Issue Type: Improvement >Affects Versions: 1.2 >Reporter: Karl-Heinz Marbaise >Assignee: Karl-Heinz Marbaise >Priority: Minor > Fix For: 1.2 > > -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MDOAP-45) Upgrade plexus-i18n to 1.0-beta-10
[ https://jira.codehaus.org/browse/MDOAP-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated MDOAP-45: - Fix Version/s: 1.2 > Upgrade plexus-i18n to 1.0-beta-10 > -- > > Key: MDOAP-45 > URL: https://jira.codehaus.org/browse/MDOAP-45 > Project: Maven DOAP Plugin > Issue Type: Improvement >Affects Versions: 1.2 >Reporter: Karl-Heinz Marbaise >Priority: Minor > Fix For: 1.2 > > -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MDOAP-44) Upgrade plexus-utils to 3.0.20
Karl-Heinz Marbaise created MDOAP-44: Summary: Upgrade plexus-utils to 3.0.20 Key: MDOAP-44 URL: https://jira.codehaus.org/browse/MDOAP-44 Project: Maven DOAP Plugin Issue Type: Improvement Affects Versions: 1.2 Reporter: Karl-Heinz Marbaise Priority: Minor -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MDOAP-44) Upgrade plexus-utils to 3.0.20
[ https://jira.codehaus.org/browse/MDOAP-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated MDOAP-44: - Fix Version/s: 1.2 > Upgrade plexus-utils to 3.0.20 > -- > > Key: MDOAP-44 > URL: https://jira.codehaus.org/browse/MDOAP-44 > Project: Maven DOAP Plugin > Issue Type: Improvement >Affects Versions: 1.2 >Reporter: Karl-Heinz Marbaise >Priority: Minor > Fix For: 1.2 > > -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MDOAP-43) Upgrade to scm 1.9.2
Karl-Heinz Marbaise created MDOAP-43: Summary: Upgrade to scm 1.9.2 Key: MDOAP-43 URL: https://jira.codehaus.org/browse/MDOAP-43 Project: Maven DOAP Plugin Issue Type: Improvement Affects Versions: 1.2 Reporter: Karl-Heinz Marbaise Priority: Minor -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MDOAP-43) Upgrade to scm 1.9.2
[ https://jira.codehaus.org/browse/MDOAP-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated MDOAP-43: - Fix Version/s: 1.2 > Upgrade to scm 1.9.2 > > > Key: MDOAP-43 > URL: https://jira.codehaus.org/browse/MDOAP-43 > Project: Maven DOAP Plugin > Issue Type: Improvement >Affects Versions: 1.2 >Reporter: Karl-Heinz Marbaise >Priority: Minor > Fix For: 1.2 > > -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MDOAP-43) Upgrade to scm 1.9.2
[ https://jira.codehaus.org/browse/MDOAP-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise closed MDOAP-43. Resolution: Fixed Assignee: Karl-Heinz Marbaise Fixed in [r1652762|http://svn.apache.org/r1652762] > Upgrade to scm 1.9.2 > > > Key: MDOAP-43 > URL: https://jira.codehaus.org/browse/MDOAP-43 > Project: Maven DOAP Plugin > Issue Type: Improvement >Affects Versions: 1.2 >Reporter: Karl-Heinz Marbaise >Assignee: Karl-Heinz Marbaise >Priority: Minor > Fix For: 1.2 > > -- 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:all-tabpanel ] Dennis Lundberg reassigned MCHECKSTYLE-272: --- Assignee: Dennis Lundberg > 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 >Assignee: 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] (MCHECKSTYLE-278) Require Java 7
[ https://jira.codehaus.org/browse/MCHECKSTYLE-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MCHECKSTYLE-278: Affects Version/s: (was: 2.14) Fix Version/s: 2.16 Assignee: Dennis Lundberg > Require Java 7 > -- > > Key: MCHECKSTYLE-278 > URL: https://jira.codehaus.org/browse/MCHECKSTYLE-278 > Project: Maven Checkstyle Plugin > Issue Type: Task >Reporter: Dennis Lundberg >Assignee: Dennis Lundberg > Fix For: 2.16 > > > Checkstyle version 6.2+ requires Java 7, so we need to adjust the > requirements in this plugin to reflect that. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCHECKSTYLE-277) Require Java 6
[ https://jira.codehaus.org/browse/MCHECKSTYLE-277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MCHECKSTYLE-277: Fix Version/s: 2.15 Assignee: Dennis Lundberg > Require Java 6 > -- > > Key: MCHECKSTYLE-277 > URL: https://jira.codehaus.org/browse/MCHECKSTYLE-277 > Project: Maven Checkstyle Plugin > Issue Type: Task >Reporter: Dennis Lundberg >Assignee: Dennis Lundberg > Fix For: 2.15 > > > Checkstyle versions 5.9 - 6.1.1 requires Java 6, so we need to adjust the > requirements in this plugin to reflect that. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCHECKSTYLE-278) Require Java 7
Dennis Lundberg created MCHECKSTYLE-278: --- Summary: Require Java 7 Key: MCHECKSTYLE-278 URL: https://jira.codehaus.org/browse/MCHECKSTYLE-278 Project: Maven Checkstyle Plugin Issue Type: Task Affects Versions: 2.14 Reporter: Dennis Lundberg Checkstyle version 6.2+ requires Java 7, so we need to adjust the requirements in this plugin to reflect that. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCHECKSTYLE-277) Require Java 6
Dennis Lundberg created MCHECKSTYLE-277: --- Summary: Require Java 6 Key: MCHECKSTYLE-277 URL: https://jira.codehaus.org/browse/MCHECKSTYLE-277 Project: Maven Checkstyle Plugin Issue Type: Task Reporter: Dennis Lundberg Checkstyle versions 5.9 - 6.1.1 requires Java 6, so we need to adjust the requirements in this plugin to reflect that. -- 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:comment-tabpanel&focusedCommentId=361333#comment-361333 ] Dennis Lundberg commented on MCHECKSTYLE-253: - I reverted the Checkstyle upgrade to 5.9 in [r1652760|http://svn.apache.org/viewvc?view=revision&revision=1652760]. The plugin is now using Checkstyle 5.8. > 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 closed MCHECKSTYLE-253. --- Resolution: Won't Fix > 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] (MNG-5755) Access toolchains without maven-toolchain-plugin
[ https://jira.codehaus.org/browse/MNG-5755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte reassigned MNG-5755: --- Assignee: Robert Scholte > Access toolchains without maven-toolchain-plugin > > > Key: MNG-5755 > URL: https://jira.codehaus.org/browse/MNG-5755 > Project: Maven > Issue Type: New Feature > Components: Toolchains >Affects Versions: 3.2.5 >Reporter: Robert Scholte >Assignee: Robert Scholte > > The original idea of toolchains was to have the same tool being used by > different plugins within the same project. > This seems like a good approach, but there are several cases where you want > more control over the tool to choose, for instance: > * the maven-compiler-plugin should use the lowest (preferably matching) jdk > version to ensure proper bytecode for the classes > * the maven-surefire-plugin might need a higher version due to requirements > of the testing frameworks > * some code-generators require a more recent JDK compared to the code they're > actually producing. > * the look-and-feel of javadoc has changed per JDK. If you like the latest, > you should be able to use it. > * In case of the maven-invoker-plugin you should be able to test all > combinations of JDK and Maven as runtime environment. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5755) Access toolchains without maven-toolchain-plugin
Robert Scholte created MNG-5755: --- Summary: Access toolchains without maven-toolchain-plugin Key: MNG-5755 URL: https://jira.codehaus.org/browse/MNG-5755 Project: Maven Issue Type: New Feature Components: Toolchains Affects Versions: 3.2.5 Reporter: Robert Scholte The original idea of toolchains was to have the same tool being used by different plugins within the same project. This seems like a good approach, but there are several cases where you want more control over the tool to choose, for instance: * the maven-compiler-plugin should use the lowest (preferably matching) jdk version to ensure proper bytecode for the classes * the maven-surefire-plugin might need a higher version due to requirements of the testing frameworks * some code-generators require a more recent JDK compared to the code they're actually producing. * the look-and-feel of javadoc has changed per JDK. If you like the latest, you should be able to use it. * In case of the maven-invoker-plugin you should be able to test all combinations of JDK and Maven as runtime environment. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[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:all-tabpanel ] Michael Osipov reassigned MPIR-329: --- Assignee: Michael Osipov > 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 >Assignee: Michael Osipov >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:all-tabpanel ] Michael Osipov reassigned MNGSITE-221: -- Assignee: Michael Osipov > Broken link in maven site > - > > Key: MNGSITE-221 > URL: https://jira.codehaus.org/browse/MNGSITE-221 > Project: Maven Project Web Site > Issue Type: Bug >Reporter: Venkatachalam Muthusamy >Assignee: Michael Osipov >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-165) Want to become a Maven Mirror Site
[ https://jira.codehaus.org/browse/MNGSITE-165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MNGSITE-165. -- Resolution: Not A Bug > Want to become a Maven Mirror Site > -- > > Key: MNGSITE-165 > URL: https://jira.codehaus.org/browse/MNGSITE-165 > Project: Maven Project Web Site > Issue Type: Task >Reporter: Tony Sandin >Priority: Minor > Labels: close-pending > > We would like to become an official mirror. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MSHARED-398) Removed dependency plexus-container-default:1.0-alpha-9-stable-1
[
https://jira.codehaus.org/browse/MSHARED-398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise closed MSHARED-398.
---
Resolution: Fixed
Assignee: Karl-Heinz Marbaise
Fixed in [r1652713|http://svn.apache.org/r1652713]
> Removed dependency plexus-container-default:1.0-alpha-9-stable-1
>
>
> Key: MSHARED-398
> URL: https://jira.codehaus.org/browse/MSHARED-398
> Project: Maven Shared Components
> Issue Type: Improvement
> Components: maven-jarsigner
>Affects Versions: maven-jarsigner-1.4
>Reporter: Karl-Heinz Marbaise
>Assignee: Karl-Heinz Marbaise
>Priority: Minor
> Fix For: maven-jarsigner-1.4
>
>
> Removing the following dependency:
> {code:xml}
> org.codehaus.plexus
> plexus-container-default
> 1.0-alpha-9-stable-1
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MSHARED-398) Removed dependency plexus-container-default:1.0-alpha-9-stable-1
[
https://jira.codehaus.org/browse/MSHARED-398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise updated MSHARED-398:
Fix Version/s: maven-jarsigner-1.4
> Removed dependency plexus-container-default:1.0-alpha-9-stable-1
>
>
> Key: MSHARED-398
> URL: https://jira.codehaus.org/browse/MSHARED-398
> Project: Maven Shared Components
> Issue Type: Improvement
> Components: maven-jarsigner
>Affects Versions: maven-jarsigner-1.4
>Reporter: Karl-Heinz Marbaise
>Priority: Minor
> Fix For: maven-jarsigner-1.4
>
>
> Removing the following dependency:
> {code:xml}
> org.codehaus.plexus
> plexus-container-default
> 1.0-alpha-9-stable-1
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MSHARED-398) Removed dependency plexus-container-default:1.0-alpha-9-stable-1
Karl-Heinz Marbaise created MSHARED-398:
---
Summary: Removed dependency
plexus-container-default:1.0-alpha-9-stable-1
Key: MSHARED-398
URL: https://jira.codehaus.org/browse/MSHARED-398
Project: Maven Shared Components
Issue Type: Improvement
Components: maven-jarsigner
Affects Versions: maven-jarsigner-1.4
Reporter: Karl-Heinz Marbaise
Priority: Minor
Removing the following dependency:
{code:xml}
org.codehaus.plexus
plexus-container-default
1.0-alpha-9-stable-1
{code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MSHARED-397) Upgrade maven-shared-utils to 0.7
[ https://jira.codehaus.org/browse/MSHARED-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise closed MSHARED-397. --- Resolution: Fixed Assignee: Karl-Heinz Marbaise Fixed in [r1652712|http://svn.apache.org/r1652712] > Upgrade maven-shared-utils to 0.7 > - > > Key: MSHARED-397 > URL: https://jira.codehaus.org/browse/MSHARED-397 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-jarsigner >Affects Versions: maven-jarsigner-1.3.3 >Reporter: Karl-Heinz Marbaise >Assignee: Karl-Heinz Marbaise >Priority: Minor > Fix For: maven-jarsigner-1.4 > > -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MSHARED-397) Upgrade maven-shared-utils to 0.7
[ https://jira.codehaus.org/browse/MSHARED-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated MSHARED-397: Fix Version/s: maven-jarsigner-1.4 > Upgrade maven-shared-utils to 0.7 > - > > Key: MSHARED-397 > URL: https://jira.codehaus.org/browse/MSHARED-397 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-jarsigner >Affects Versions: maven-jarsigner-1.3.3 >Reporter: Karl-Heinz Marbaise >Priority: Minor > Fix For: maven-jarsigner-1.4 > > -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MSHARED-397) Upgrade maven-shared-utils to 0.7
Karl-Heinz Marbaise created MSHARED-397: --- Summary: Upgrade maven-shared-utils to 0.7 Key: MSHARED-397 URL: https://jira.codehaus.org/browse/MSHARED-397 Project: Maven Shared Components Issue Type: Improvement Components: maven-jarsigner Affects Versions: maven-jarsigner-1.3.3 Reporter: Karl-Heinz Marbaise Priority: Minor -- This message was sent by Atlassian JIRA (v6.1.6#6162)
