[jira] (MEAR-158) Elements library-directory and env-entry out of sequence in application.xml for JEE 6
[ https://jira.codehaus.org/browse/MEAR-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MEAR-158. --- Resolution: Fixed Assignee: Robert Scholte Patch of [~fbricon] applied, thanks! Fixed in [r1540462|http://svn.apache.org/r1540462] > Elements library-directory and env-entry out of sequence in application.xml > for JEE 6 > - > > Key: MEAR-158 > URL: https://jira.codehaus.org/browse/MEAR-158 > Project: Maven Ear Plugin > Issue Type: Bug >Affects Versions: 2.8 >Reporter: Marty Phelan >Assignee: Robert Scholte > Fix For: 2.8.1 > > Attachments: application.xml, pom.xml, pom.xml, pom.xml > > > When the pom.xml for an JEE 6 EAR project contains plugin configuration > entries for both defaultLibBundleDir and env-entries, the resulting elements > in application.xml are out-of-sequence per specification. The generated order > is env-entry - library-directory. This should be reversed. > Attached are two files: the sample pom.xml and resulting application.xml. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MEAR-160) Performance regression while copying artifacts into ear
[ https://jira.codehaus.org/browse/MEAR-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=335504#comment-335504 ] Robert Scholte commented on MEAR-160: - I guess this issue can be closed as fixed, right? @[~olamy], what has been changed? I can't find any related issue or commit here. > Performance regression while copying artifacts into ear > --- > > Key: MEAR-160 > URL: https://jira.codehaus.org/browse/MEAR-160 > Project: Maven Ear Plugin > Issue Type: Bug >Affects Versions: 2.8 > Environment: Intel Core i3 : Arch Linux 64-bit : Kernel 3.6.2 : ext4 > filesystem : JDK 7u9 >Reporter: Joseph Freeman >Assignee: Olivier Lamy > Fix For: 2.9 > > Attachments: test.zip > > > Just upgraded the maven ear plugin from 2.7 to 2.8 and it's now taking double > the time to build my project. The time increase happens when my jars and war > are being copied into the ear as unpacked artifacts. Packed artifacts are > still just as fast as before > Time Comparisons: > v2.7: > * unpacked => 24 seconds > * packed => 21 seconds > v2.8: > * unpacked => 49 seconds > * packed => 20 seconds -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MEAR-174) generate-application-xml does not support the definition of an application id
[ https://jira.codehaus.org/browse/MEAR-174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte reassigned MEAR-174: --- Assignee: Robert Scholte > generate-application-xml does not support the definition of an application id > - > > Key: MEAR-174 > URL: https://jira.codehaus.org/browse/MEAR-174 > Project: Maven Ear Plugin > Issue Type: Improvement >Affects Versions: 2.8 > Environment: all environments >Reporter: Andreas Schufft >Assignee: Robert Scholte > Fix For: 2.9 > > Attachments: maven-ear-plugin-trunk.patch > > > The schema/dtd's for EAR deployment descriptors define an id attribute for > the application element. Some container specific deployment descriptors (or > deployment descriptor extensions) reference the id as follows: > > The simple patch provides the as config for the > generate-application-xml mojo and adds the id to the generated > application.xml. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCHECKSTYLE-203) Exclusions fail to exclude property file
[ https://jira.codehaus.org/browse/MCHECKSTYLE-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies updated MCHECKSTYLE-203: - Summary: Exclusions fail to exclude property file (was: Exclusions fail to exclusde property file) > Exclusions fail to exclude property file > > > Key: MCHECKSTYLE-203 > URL: https://jira.codehaus.org/browse/MCHECKSTYLE-203 > Project: Maven Checkstyle Plugin > Issue Type: Bug >Affects Versions: 2.10 >Reporter: Benson Margulies > > I cannot find a way to make the plugin stay away from .property files, or the > src/main/resources directory, in general. > I am not going to attach a full repro and test case here, because I plan to > work on this problem right away and document my findings and repairs with > this JIRA. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCHECKSTYLE-203) Exclusions fail to exclusde property file
Benson Margulies created MCHECKSTYLE-203: Summary: Exclusions fail to exclusde property file Key: MCHECKSTYLE-203 URL: https://jira.codehaus.org/browse/MCHECKSTYLE-203 Project: Maven Checkstyle Plugin Issue Type: Bug Affects Versions: 2.10 Reporter: Benson Margulies I cannot find a way to make the plugin stay away from .property files, or the src/main/resources directory, in general. I am not going to attach a full repro and test case here, because I plan to work on this problem right away and document my findings and repairs with this JIRA. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCHECKSTYLE-203) Exclusions fail to exclude property file
[ https://jira.codehaus.org/browse/MCHECKSTYLE-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies reassigned MCHECKSTYLE-203: Assignee: Benson Margulies > Exclusions fail to exclude property file > > > Key: MCHECKSTYLE-203 > URL: https://jira.codehaus.org/browse/MCHECKSTYLE-203 > Project: Maven Checkstyle Plugin > Issue Type: Bug >Affects Versions: 2.10 >Reporter: Benson Margulies >Assignee: Benson Margulies > > I cannot find a way to make the plugin stay away from .property files, or the > src/main/resources directory, in general. > I am not going to attach a full repro and test case here, because I plan to > work on this problem right away and document my findings and repairs with > this JIRA. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCHECKSTYLE-137) Checkstyle plugin rejects Unicode single character constants.
[
https://jira.codehaus.org/browse/MCHECKSTYLE-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies closed MCHECKSTYLE-137.
Resolution: Fixed
Fix Version/s: 2.10
Assignee: Benson Margulies
> Checkstyle plugin rejects Unicode single character constants.
> -
>
> Key: MCHECKSTYLE-137
> URL: https://jira.codehaus.org/browse/MCHECKSTYLE-137
> Project: Maven Checkstyle Plugin
> Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Benson Margulies
>Assignee: Benson Margulies
> Fix For: 2.10
>
>
> Even with the encoding set to UTF-8 in the plugin configuration, the
> following is rejected, claiming that it found an invalid character while
> looking for a single quote.
> if (script != ISO15924.Hira || c == 'の') {
> break;
> }
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCHECKSTYLE-203) Exclusions fail to exclude property file
[ https://jira.codehaus.org/browse/MCHECKSTYLE-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies closed MCHECKSTYLE-203. Resolution: Duplicate > Exclusions fail to exclude property file > > > Key: MCHECKSTYLE-203 > URL: https://jira.codehaus.org/browse/MCHECKSTYLE-203 > Project: Maven Checkstyle Plugin > Issue Type: Bug >Affects Versions: 2.10 >Reporter: Benson Margulies >Assignee: Benson Margulies > > I cannot find a way to make the plugin stay away from .property files, or the > src/main/resources directory, in general. > I am not going to attach a full repro and test case here, because I plan to > work on this problem right away and document my findings and repairs with > this JIRA. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCHECKSTYLE-193) Resource files get included regardless of explicit sourceDirectory / includes / excludes configuration
[ https://jira.codehaus.org/browse/MCHECKSTYLE-193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies reassigned MCHECKSTYLE-193: Assignee: Benson Margulies > Resource files get included regardless of explicit sourceDirectory / includes > / excludes configuration > -- > > Key: MCHECKSTYLE-193 > URL: https://jira.codehaus.org/browse/MCHECKSTYLE-193 > Project: Maven Checkstyle Plugin > Issue Type: Bug >Affects Versions: 2.10 >Reporter: Oleg Kalnichevski >Assignee: Benson Margulies > > Resource files get included into checkstyle audit regardless of explicit > sourceDirectory / includes / excludes configuration, which seems wrong to me. > I found no way of forcing version 2.10 to revert to the behavior of version > 2.9.1 with regards to project resources. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCHECKSTYLE-199) Make resource file processing configurable
[ https://jira.codehaus.org/browse/MCHECKSTYLE-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies reassigned MCHECKSTYLE-199: Assignee: Benson Margulies > Make resource file processing configurable > -- > > Key: MCHECKSTYLE-199 > URL: https://jira.codehaus.org/browse/MCHECKSTYLE-199 > Project: Maven Checkstyle Plugin > Issue Type: Improvement >Affects Versions: 2.10 >Reporter: Dennis Lundberg >Assignee: Benson Margulies > > In MCHECKSTYLE-184 processing of resource files was added. This is currently > hard coded, which leads to problems under certain conditions. See comments in > MCHECKSTYLE-184. Add configuration parameters for this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCHECKSTYLE-193) Resource files get included regardless of explicit sourceDirectory / includes / excludes configuration
[ https://jira.codehaus.org/browse/MCHECKSTYLE-193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies closed MCHECKSTYLE-193. Resolution: Fixed Fix Version/s: 2.11 > Resource files get included regardless of explicit sourceDirectory / includes > / excludes configuration > -- > > Key: MCHECKSTYLE-193 > URL: https://jira.codehaus.org/browse/MCHECKSTYLE-193 > Project: Maven Checkstyle Plugin > Issue Type: Bug >Affects Versions: 2.10 >Reporter: Oleg Kalnichevski >Assignee: Benson Margulies > Fix For: 2.11 > > > Resource files get included into checkstyle audit regardless of explicit > sourceDirectory / includes / excludes configuration, which seems wrong to me. > I found no way of forcing version 2.10 to revert to the behavior of version > 2.9.1 with regards to project resources. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCHECKSTYLE-193) Resource files get included regardless of explicit sourceDirectory / includes / excludes configuration
[ https://jira.codehaus.org/browse/MCHECKSTYLE-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=335525#comment-335525 ] Benson Margulies commented on MCHECKSTYLE-193: -- I've just committed a set of options: includeResources includeTestResources resourceIncludes resourceExcludes Since 2.10 has been out there with the default of checking resources for some time now, I did not change the defaults. > Resource files get included regardless of explicit sourceDirectory / includes > / excludes configuration > -- > > Key: MCHECKSTYLE-193 > URL: https://jira.codehaus.org/browse/MCHECKSTYLE-193 > Project: Maven Checkstyle Plugin > Issue Type: Bug >Affects Versions: 2.10 >Reporter: Oleg Kalnichevski >Assignee: Benson Margulies > > Resource files get included into checkstyle audit regardless of explicit > sourceDirectory / includes / excludes configuration, which seems wrong to me. > I found no way of forcing version 2.10 to revert to the behavior of version > 2.9.1 with regards to project resources. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCHECKSTYLE-199) Make resource file processing configurable
[ https://jira.codehaus.org/browse/MCHECKSTYLE-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies closed MCHECKSTYLE-199. Resolution: Fixed Fix Version/s: 2.11 Fixed as part of MCHECKSTYLE-193. > Make resource file processing configurable > -- > > Key: MCHECKSTYLE-199 > URL: https://jira.codehaus.org/browse/MCHECKSTYLE-199 > Project: Maven Checkstyle Plugin > Issue Type: Improvement >Affects Versions: 2.10 >Reporter: Dennis Lundberg >Assignee: Benson Margulies > Fix For: 2.11 > > > In MCHECKSTYLE-184 processing of resource files was added. This is currently > hard coded, which leads to problems under certain conditions. See comments in > MCHECKSTYLE-184. Add configuration parameters for this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCHECKSTYLE-197) Documentation: Check goal is incorrectly described
[
https://jira.codehaus.org/browse/MCHECKSTYLE-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies reassigned MCHECKSTYLE-197:
Assignee: Benson Margulies
> Documentation: Check goal is incorrectly described
> --
>
> Key: MCHECKSTYLE-197
> URL: https://jira.codehaus.org/browse/MCHECKSTYLE-197
> Project: Maven Checkstyle Plugin
> Issue Type: Bug
>Affects Versions: 2.10
>Reporter: Stephen Colebourne
>Assignee: Benson Margulies
>
> The website describes the check goal as
> {panel}
> checkstyle:check performs a violation check against the last Checkstyle run
> to see if there are any violations. It reads the Checkstyle output file,
> counts the number of violations found and displays it on the console.{panel}
> This is incorrect. The check goal will, by default, run the actual checkstyle
> analysis before printing the messages.
> The following text would be better on the home page:
> http://maven.apache.org/plugins/maven-checkstyle-plugin/index.html
> {panel}
> * checkstyle:checkstyle - a reporting task that performs Checkstyle analysis
> and generates an HTML report on violations.
> * checkstyle:checkstyle-aggregate - a reporting task that performs Checkstyle
> analysis and generates an aggregate HTML report on violations in a
> multi-module reactor build.
> * checkstyle:check - performs Checkstyle analysis and outputs violations to
> the console, potentially failing the build. It can also be configured to
> re-use an earlier analysis.
> {panel}
> The description on the check-mojo page should also be fixed similarly:
> http://maven.apache.org/plugins/maven-checkstyle-plugin/check-mojo.html
> An example or FAQ should be added to emphasise the difference between the
> checkstyle and check goals.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCHECKSTYLE-202) The link on Usage page to 'Maven 3.x Compatibility Notes' is not correct
[ https://jira.codehaus.org/browse/MCHECKSTYLE-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies closed MCHECKSTYLE-202. Resolution: Fixed Fix Version/s: 2.11 Fixed in 1540563. > The link on Usage page to 'Maven 3.x Compatibility Notes' is not correct > > > Key: MCHECKSTYLE-202 > URL: https://jira.codehaus.org/browse/MCHECKSTYLE-202 > Project: Maven Checkstyle Plugin > Issue Type: Bug >Affects Versions: 2.10 > Environment: web-site > http://maven.apache.org/plugins/maven-checkstyle-plugin >Reporter: Tjeerd Verhagen >Assignee: Benson Margulies >Priority: Trivial > Fix For: 2.11 > > > The link on Usage page to 'Maven 3.x Compatibility Notes' is not correct. > URL of Usage page: > http://maven.apache.org/plugins/maven-checkstyle-plugin/usage.html > Current href: > https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html > Should become: > https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility+Notes -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCHECKSTYLE-202) The link on Usage page to 'Maven 3.x Compatibility Notes' is not correct
[ https://jira.codehaus.org/browse/MCHECKSTYLE-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies reassigned MCHECKSTYLE-202: Assignee: Benson Margulies > The link on Usage page to 'Maven 3.x Compatibility Notes' is not correct > > > Key: MCHECKSTYLE-202 > URL: https://jira.codehaus.org/browse/MCHECKSTYLE-202 > Project: Maven Checkstyle Plugin > Issue Type: Bug >Affects Versions: 2.10 > Environment: web-site > http://maven.apache.org/plugins/maven-checkstyle-plugin >Reporter: Tjeerd Verhagen >Assignee: Benson Margulies >Priority: Trivial > > The link on Usage page to 'Maven 3.x Compatibility Notes' is not correct. > URL of Usage page: > http://maven.apache.org/plugins/maven-checkstyle-plugin/usage.html > Current href: > https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html > Should become: > https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility+Notes -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCHECKSTYLE-197) Documentation: Check goal is incorrectly described
[
https://jira.codehaus.org/browse/MCHECKSTYLE-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies closed MCHECKSTYLE-197.
Resolution: Fixed
Fix Version/s: 2.11
Fixed in 1540563.
> Documentation: Check goal is incorrectly described
> --
>
> Key: MCHECKSTYLE-197
> URL: https://jira.codehaus.org/browse/MCHECKSTYLE-197
> Project: Maven Checkstyle Plugin
> Issue Type: Bug
>Affects Versions: 2.10
>Reporter: Stephen Colebourne
>Assignee: Benson Margulies
> Fix For: 2.11
>
>
> The website describes the check goal as
> {panel}
> checkstyle:check performs a violation check against the last Checkstyle run
> to see if there are any violations. It reads the Checkstyle output file,
> counts the number of violations found and displays it on the console.{panel}
> This is incorrect. The check goal will, by default, run the actual checkstyle
> analysis before printing the messages.
> The following text would be better on the home page:
> http://maven.apache.org/plugins/maven-checkstyle-plugin/index.html
> {panel}
> * checkstyle:checkstyle - a reporting task that performs Checkstyle analysis
> and generates an HTML report on violations.
> * checkstyle:checkstyle-aggregate - a reporting task that performs Checkstyle
> analysis and generates an aggregate HTML report on violations in a
> multi-module reactor build.
> * checkstyle:check - performs Checkstyle analysis and outputs violations to
> the console, potentially failing the build. It can also be configured to
> re-use an earlier analysis.
> {panel}
> The description on the check-mojo page should also be fixed similarly:
> http://maven.apache.org/plugins/maven-checkstyle-plugin/check-mojo.html
> An example or FAQ should be added to emphasise the difference between the
> checkstyle and check goals.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCHECKSTYLE-199) Make resource file processing configurable
[ https://jira.codehaus.org/browse/MCHECKSTYLE-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=335530#comment-335530 ] Benson Margulies commented on MCHECKSTYLE-199: -- fixed in 1540550. > Make resource file processing configurable > -- > > Key: MCHECKSTYLE-199 > URL: https://jira.codehaus.org/browse/MCHECKSTYLE-199 > Project: Maven Checkstyle Plugin > Issue Type: Improvement >Affects Versions: 2.10 >Reporter: Dennis Lundberg >Assignee: Benson Margulies > Fix For: 2.11 > > > In MCHECKSTYLE-184 processing of resource files was added. This is currently > hard coded, which leads to problems under certain conditions. See comments in > MCHECKSTYLE-184. Add configuration parameters for this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCHECKSTYLE-193) Resource files get included regardless of explicit sourceDirectory / includes / excludes configuration
[ https://jira.codehaus.org/browse/MCHECKSTYLE-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=335531#comment-335531 ] Benson Margulies commented on MCHECKSTYLE-193: -- Fixed in 1540550. > Resource files get included regardless of explicit sourceDirectory / includes > / excludes configuration > -- > > Key: MCHECKSTYLE-193 > URL: https://jira.codehaus.org/browse/MCHECKSTYLE-193 > Project: Maven Checkstyle Plugin > Issue Type: Bug >Affects Versions: 2.10 >Reporter: Oleg Kalnichevski >Assignee: Benson Margulies > Fix For: 2.11 > > > Resource files get included into checkstyle audit regardless of explicit > sourceDirectory / includes / excludes configuration, which seems wrong to me. > I found no way of forcing version 2.10 to revert to the behavior of version > 2.9.1 with regards to project resources. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCHECKSTYLE-166) Drop @requiresDependencyResolution test
[
https://jira.codehaus.org/browse/MCHECKSTYLE-166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=335532#comment-335532
]
Benson Margulies commented on MCHECKSTYLE-166:
--
Well, how about a patch with an integration test?
> Drop @requiresDependencyResolution test
> ---
>
> Key: MCHECKSTYLE-166
> URL: https://jira.codehaus.org/browse/MCHECKSTYLE-166
> Project: Maven Checkstyle Plugin
> Issue Type: Bug
>Affects Versions: 2.8
> Environment: N/A
>Reporter: Ernst de Haan
>Priority: Minor
>
> Currently, the
> [{{CheckstyleViolationCheckMojo}}|http://svn.apache.org/viewvc/maven/plugins/tags/maven-checkstyle-plugin-2.8/src/main/java/org/apache/maven/plugin/checkstyle/CheckstyleViolationCheckMojo.java?revision=1188083&view=markup]
> class declares:{code}@requiresDependencyResolution test{code}However, that
> should not be necessary. Checkstyle works on source files, not on bytecode.
> If this declaration would be removed, then this Checkstyle plugin should
> still work perfectly fine (I would expect without any further code changes).
> The advantage would be that in our Continuous Integration pipeline I can skip
> the _compile_ stage and immediately trigger the _checkstyle_ stage. That
> would save us multiple minutes on the feedback roundtrip.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MEAR-160) Performance regression while copying artifacts into ear
[ https://jira.codehaus.org/browse/MEAR-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=335533#comment-335533 ] Olivier Lamy commented on MEAR-160: --- see MEAR-164 > Performance regression while copying artifacts into ear > --- > > Key: MEAR-160 > URL: https://jira.codehaus.org/browse/MEAR-160 > Project: Maven Ear Plugin > Issue Type: Bug >Affects Versions: 2.8 > Environment: Intel Core i3 : Arch Linux 64-bit : Kernel 3.6.2 : ext4 > filesystem : JDK 7u9 >Reporter: Joseph Freeman >Assignee: Olivier Lamy > Fix For: 2.9 > > Attachments: test.zip > > > Just upgraded the maven ear plugin from 2.7 to 2.8 and it's now taking double > the time to build my project. The time increase happens when my jars and war > are being copied into the ear as unpacked artifacts. Packed artifacts are > still just as fast as before > Time Comparisons: > v2.7: > * unpacked => 24 seconds > * packed => 21 seconds > v2.8: > * unpacked => 49 seconds > * packed => 20 seconds -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPLUGINTESTING-27) ClassDefNotFound exception
[
https://jira.codehaus.org/browse/MPLUGINTESTING-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=335539#comment-335539
]
Baron Roberts commented on MPLUGINTESTING-27:
-
The folks at [Simpligility have created a
fork|https://github.com/simpligility/maven-plugin-testing] of the
maven-plugin-testing-harness that fixes the incompatibility with 3.1.x.
> ClassDefNotFound exception
> --
>
> Key: MPLUGINTESTING-27
> URL: https://jira.codehaus.org/browse/MPLUGINTESTING-27
> Project: Maven Plugin Testing
> Issue Type: Bug
> Components: plugin-testing-harness
>Affects Versions: 2.1
> Environment: Maven 3.0.4, JDK 1.7, MacOSx
>Reporter: Artur Keska
>
> I'm trying to extend an existing project using p.-t.-hatness.
> So I added to my project dependency:
>
> org.apache.maven.plugin-testing
> maven-plugin-testing-harness
> 2.1
> test
>
> And extended the test class follow the quick start guide.
> On the first run I have following exception:
> rg.apache.maven.surefire.util.SurefireReflectionException:
> java.lang.reflect.InvocationTargetException; nested exception is
> java.lang.reflect.InvocationTargetException: null
> java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at
> org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164)
> at
> org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110)
> at
> org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175)
> at
> org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcessWhenForked(SurefireStarter.java:107)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:68)
> Caused by: java.lang.NoClassDefFoundError:
> org/sonatype/aether/RepositorySystemSession
> at java.lang.Class.getDeclaredMethods0(Native Method)
> at java.lang.Class.privateGetDeclaredMethods(Class.java:2442)
> at java.lang.Class.getMethod0(Class.java:2685)
> at java.lang.Class.getMethod(Class.java:1620)
> at
> org.apache.maven.surefire.common.junit3.JUnit3Reflector.createInstanceFromSuiteMethod(JUnit3Reflector.java:152)
> at
> org.apache.maven.surefire.common.junit3.JUnit3Reflector.constructTestObject(JUnit3Reflector.java:121)
> at
> org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:71)
> at
> org.apache.maven.surefire.junit.JUnit3Provider.executeTestSet(JUnit3Provider.java:117)
> at
> org.apache.maven.surefire.junit.JUnit3Provider.invoke(JUnit3Provider.java:94)
> ... 9 more
> Caused by: java.lang.ClassNotFoundException:
> org.sonatype.aether.RepositorySystemSession
> at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:423)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
> ... 18 more
> It loks like the Aether classes are not found. So I simply added dependency:
>
> com.rempl
> rempl-cli
> 1.1.3
> bin
> test
>
> And now I have exception:
> Caused by: java.lang.ClassNotFoundException:
> org.apache.maven.execution.MavenExecutionRequest
> That's funny because MavenExecutionRequest is a part of the Maven core and
> should be just available. Anyway I checked what's happend if I will add
> maven-core manually. When adding dependency:
>
> org.apache.maven
> maven-core
> ${maven-version}
> test
>
> I have another error:
> Caused by: java.lang.ClassNotFoundException:
> org.apache.maven.execution.MavenExecutionResult
> Hmmm... This is also a part of maven-core. This brings me to the conclusion,
> that trying to add dependencies manually was was a bad idea and there must be
> another solution.
> I will appreciative for any idea what can I do.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
