[ANN] Apache Maven Resources Plugin 3.2.0 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Resources Plugin, version 3.2.0 The Resources Plugin handles the copying of project resources to the output directory. https://maven.apache.org/plugins/maven-resources-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-resources-plugin 3.2.0 You can download the appropriate sources etc. from the download page: https://maven.apache.org/plugins/maven-resources-plugin/download.cgi Release Notes - Maven Resources Plugin - Version 3.2.0 ** Bug * [MRESOURCES-171] - ISO8859-1 properties files get changed into UTF-8 when filtered * [MRESOURCES-210] - copy-resources erases file permissions * [MRESOURCES-236] - Copying of files with permissions broken * [MRESOURCES-257] - property from list element in pom model ** Improvement * [MRESOURCES-251] - Upgrade plexus-interpolation 1.26 * [MRESOURCES-252] - Add m2e lifecycle Metadata to plugin * [MRESOURCES-256] - make build Reproducible * [MRESOURCES-258] - Only overwrite filtered resources when contents differ ** Dependency upgrade * [MRESOURCES-249] - Upgrade maven-plugins parent to version 32 * [MRESOURCES-255] - Upgrade plexus-utils 3.3.0 * [MRESOURCES-261] - Make Maven 3.1.0 the minimum version * [MRESOURCES-263] - Update to maven-filtering 3.2.0 Enjoy, -The Apache Maven team
[ANN] Apache Maven Filtering 3.2.0 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Filtering, version 3.2.0 This is a shared component for all plugins that need to filter resources. https://maven.apache.org/shared/maven-filtering/ You should specify the version in your project's plugin configuration: org.apache.maven.shared maven-filtering 3.2.0 You can download the appropriate sources etc. from the download page: https://maven.apache.org/shared/maven-filtering/download.cgi Release Notes - Maven Filtering - Version 3.2.0 ** Bug * [MSHARED-417] - Infinite loop when loading self-referencing properties * [MSHARED-599] - Escaping the escape string produces incorrect output. * [MSHARED-829] - MavenResourcesExecution.copyOf() returns new instance without properties set ** New Feature * [MSHARED-934] - Allow using a different encoding when filtering properties files ** Improvement * [MSHARED-646] - Removed prerequisites for none maven-plugin project * [MSHARED-664] - Add ico files to default non-filtered extensions * [MSHARED-830] - Require Java 7 * [MSHARED-879] - make build Reproducible * [MSHARED-884] - Only overwrite filtered resources when contents differ * [MSHARED-946] - Update to maven-shared-utils 3.3.3 ** Dependency upgrade * [MSHARED-575] - Upgrade maven-shared-utils to 3.1.0 * [MSHARED-600] - Upgrade of plexus-interpolation to 1.24. * [MSHARED-645] - Upgrade to maven-shared-utils 3.2.0 * [MSHARED-667] - plexus-utils 3.0.24 to 3.1.0 * [MSHARED-711] - Upgrade parent to 31 * [MSHARED-712] - Upgrade maven-surefire/failsafe-plugin 2.21.0 for JDK 10 * [MSHARED-755] - Upgrade parent to version 32. * [MSHARED-756] - Upgrade plexus-interpolation to 1.25 * [MSHARED-757] - Upgrade maven-shared-utils to 3.2.1 * [MSHARED-758] - Upgrade JUnit to 4.12 * [MSHARED-789] - Upgrade maven-shared-components parent to 33 * [MSHARED-790] - Upgrade plexus-utils 3.1.1 * [MSHARED-809] - Upgrade plexus-utils 3.2.0 Enjoy, -The Apache Maven team
[ANN] Apache Maven Shared Utils 3.3.3 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Shared Utils, version 3.3.3 This project aims to be a functional replacement for plexus-utils in Maven. https://maven.apache.org/shared/maven-shared-utils/ You should specify the version in your project's configuration: org.apache.maven.shared maven-shared-utils 3.3.3 You can download the appropriate sources etc. from the download page: https://maven.apache.org/plugins/maven-shared-utils/download.cgi Release Notes - Maven Shared Components - Version maven-shared-utils-3.3.3 ** Bug * [MSHARED-297] - Commandline class shell injection vulnerabilities * [MSHARED-416] - Odd number of quotes in command-line fails * [MSHARED-431] - # (Hash-Sign) should trigger quoting in BourneShell.java * [MSHARED-681] - Maven-Shared: Java7Support silently fails overwriting symlinks * [MSHARED-749] - Commandline does not thrown CommandLineException when uneven number of quotation marks used * [MSHARED-750] - Unbalanced quotes in command with escaped double quotation mark ** Improvement * [MSHARED-684] - Upgrade parent to 31 * [MSHARED-748] - Upgrade maven-shared-parent to 32 * [MSHARED-826] - Require Java 7 * [MSHARED-879] - make build Reproducible * [MSHARED-881] - try with resources in FileUtils Enjoy, -The Apache Maven team
Re: Maven Versions Plugin scans whole Maven repository
Hi, This is most likely due to a dependency on something from Spring Boot. I have seen this as well. In many of the Spring Boot POMs they declare a ton of dependencies in dependency management, to make sure all their components use the same versions. The versions-maven-plugin might go through all of them, because they are transitive dependencies of Spring Boot, depending on how the dependency on Spring Boot artifact is declared and which Spring Boot artifact it is. -- Dennis Lundberg Den lör 11 juli 2020 kl 08:39 skrev Lukáš Satin : > Hi, > > Maven Versions Plugin scans whole Maven repository. > > It takes about 1 hour and scans everything from com.google.* and > org.springframework.* plus other packages while they are nowhere in the > pom.xml! There is only org.springbootframework.boot, org.apache.commons, > com.oracle! > > I read all articles, FAQ. > > Why is this behavior? How to make it update only actual dependencies > present in pom.xml and not some transitive stuff? > > [INFO] artifact com.google.api.grpc:proto-google-cloud-bigtable-v2: > checking for updates from snapshots > [INFO] artifact com.google.api.grpc:proto-google-cloud-billing-v1: checking > for updates from central > [INFO] artifact com.google.api.grpc:proto-google-cloud-billing-v1: checking > for updates from snapshots > [INFO] artifact com.google.api.grpc:grpc-google-cloud-billing-v1: checking > for updates from central > [INFO] artifact com.google.api.grpc:grpc-google-cloud-billing-v1: checking > for updates from snapshots > [INFO] artifact com.google.cloud:google-cloud-billing: checking for updates > from central > [INFO] artifact com.google.cloud:google-cloud-billing: checking for updates > from snapshots > [INFO] artifact > com.google.api.grpc:grpc-google-cloud-billingbudgets-v1beta1: checking for > updates from central > [INFO] artifact > com.google.api.grpc:grpc-google-cloud-billingbudgets-v1beta1: checking for > updates from snapshots > [INFO] artifact > com.google.api.grpc:proto-google-cloud-billingbudgets-v1beta1: checking for > updates from central > [INFO] artifact > com.google.api.grpc:proto-google-cloud-billingbudgets-v1beta1: checking for > updates from snapshots > [INFO] artifact com.google.cloud:google-cloud-billingbudgets: checking for > updates from central > [INFO] artifact com.google.cloud:google-cloud-billingbudgets: checking for > updates from snapshots > [INFO] artifact com.google.api.grpc:grpc-google-cloud-build-v1: checking > for updates from central > [INFO] artifact com.google.api.grpc:grpc-google-cloud-build-v1: checking > for updates from snapshots > [INFO] artifact com.google.api.grpc:proto-google-cloud-build-v1: checking > for updates from central > [INFO] artifact com.google.api.grpc:proto-google-cloud-build-v1: checking > for updates from snapshots > [INFO] artifact com.google.cloud:google-cloud-build: checking for updates > from central >
Re: [VOTE] Retire Maven Application Skin, Maven Classic Skin, Maven Stylus Skin
+1 from me 2015-12-24 23:34 GMT+01:00 Michael Osipov <1983-01...@gmx.net>: > Hi, > > as previously suggested, it makes sense to retire those skins because > they haven't been updated for a long time and we don't have the resources > to maintain them properly [1]. > > Last releases: > Maven Application Skin: 2012-01-18 > Maven Classic Skin: 2012-01-18 > Maven Stylus Skin: 2012-07-30 > > I therefore propose that we retire these skins. > > If this vote is successful I will make one final release of the skin, making > it clear on the skin site that it has been retired. After that the source code > will be moved into the "retired" area in our Subversion repository. > > The process for retiring a skin is described here: > http://maven.apache.org/developers/retirement-plan-plugins.html > (Though these aren't plugins, the process is universal) > > The vote is open for 72 hours. > > [ ] +1 Yes, it's about time > [ ] -1 No, because... > > I would ask kindly those who have already cast their vote to revote to make it > "official". > > [1] > http://mail-archives.apache.org/mod_mbox/maven-dev/201512.mbox/%3Ctrinity-8ab6577c-ab69-4f9f-86e6-533e0b309a94-1450902628141%403capp-gmx-bs54%3E > > Michael > > ----- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven PMD Plugin 3.6 Released
The Maven team is pleased to announce the release of the Apache Maven PMD Plugin, version 3.6 A Maven plugin for the PMD toolkit, that produces a report on both code rule violations and detected copy and paste fragments, as well as being able to fail the build based on these metrics. http://maven.apache.org/plugins/maven-pmd-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-pmd-plugin 3.6 Release Notes - Apache Maven PMD Plugin - Version 3.6 Bug * [MPMD-218] Update to PMD 5.3.5 * [MPMD-217] False positive UselessParentheses * [MPMD-215] FieldDeclarationsShouldBeAtStartOfClass false positive * [MPMD-186] Class names with slash are omitted from exclusions on pmd:check Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Checkstyle Plugin 2.16 Released
The Maven team is pleased to announce the release of the Apache Maven Checkstyle Plugin, version 2.16 Generates a report on violations of code style and optionally fails the build if violations are detected. http://maven.apache.org/plugins/maven-checkstyle-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-checkstyle-plugin 2.16 Release Notes - Apache Maven Checkstyle Plugin - Version 2.16 Bug * [MCHECKSTYLE-295] Test resources are not included * [MCHECKSTYLE-271] checkstyle plugin fails with default ruleset and checkstyle 6.2 Improvement * [MCHECKSTYLE-290] add a history table to show which version of Chesktyle is used by default in which version of m-checkstyle-p * [MCHECKSTYLE-284] Remove config/sun_checks.xml and use the one built into Checkstyle 6.2+ * [MCHECKSTYLE-272] Upgrade to Checkstyle 6.2 Task * [MCHECKSTYLE-285] Remove config/maven_checks.xml by removing the dependency on maven-shared-resources:2 * [MCHECKSTYLE-278] Require Java 7 * [MCHECKSTYLE-268] Add flag/option to use built-in Google style Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven PMD Plugin 3.5 Released
The Maven team is pleased to announce the release of the Apache Maven PMD Plugin, version 3.5 A Maven plugin for the PMD toolkit, that produces a report on both code rule violations and detected copy and paste fragments, as well as being able to fail the build based on these metrics. http://maven.apache.org/plugins/maven-pmd-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-pmd-plugin 3.5 Release Notes - Apache Maven PMD Plugin - Version 3.5 Bug * [MPMD-208] Warning about deprecated Rule name when using rulesets/maven.xml * [MPMD-205] Javascript violations won't fail the build Improvement * [MPMD-211] Upgrade plexus-resources from 1.0-alpha-7 to 1.1 * [MPMD-209] Upgrade to PMD 5.3.2 * [MPMD-206] Make the sourceDirectories configurable New Feature * [MPMD-207] Support Javascript and JSP for CPD Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Exec Maven Plugin 1.4.0 Released
Hi, The Mojo team is pleased to announce the release of the Exec Maven Plugin version 1.4.0. The plugin helps with execution of system and Java programs. http://mojo.codehaus.org/exec-maven-plugin/ To get this update, simply specify the version in your project's plugin configuration: org.codehaus.mojo exec-maven-plugin 1.4.0 Release Notes ** Bug * [MEXEC-150] - Plugin warns that "killAfter is now deprecated" for no obvious reason ** Improvement * [MEXEC-143] - Rename skip property to exec.skip * [MEXEC-147] - Update of mojo parent to version 34 * [MEXEC-148] - Upgrade plexus-utils to 3.0.20 * [MEXEC-149] - Upgrade plexus-interpolation to 1.21 ** Task * [MEXEC-127] - Remove added parameters after commons-exec is fixed * [MEXEC-152] - Update to commons-exec:1.3 Enjoy, The Mojo team. -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Checkstyle Plugin 2.15 Released
The Maven team is pleased to announce the release of the Apache Maven Checkstyle Plugin, version 2.15 Generates a report on violations of code style and optionally fails the build if violations are detected. http://maven.apache.org/plugins/maven-checkstyle-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-checkstyle-plugin 2.15 Release Notes - Apache Maven Checkstyle Plugin - Version 2.15 Bug * [MCHECKSTYLE-288] NullPointerException during building a multi-module project * [MCHECKSTYLE-250] NPE on tying to load LICENSE.txt resource from non-jar plugin dependencies Improvement * [MCHECKSTYLE-286] Add info on ruleset used in console output * [MCHECKSTYLE-261] Upgrade to Checkstyle 6.1.1 Task * [MCHECKSTYLE-277] Require Java 6 * [MCHECKSTYLE-273] Remove Turbine configuration since it is not used any more Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Cobertura Maven Plugin 2.7 Released
Hi, The Mojo team is pleased to announce the release of the Cobertura Maven Plugin version 2.7. This plugin provides the features of Cobertura within the Maven 2 & 3 environment. http://mojo.codehaus.org/cobertura-maven-plugin/ To get this update, simply specify the version in your project's plugin configuration: org.codehaus.mojo cobertura-maven-plugin 2.7 Release Notes ** Bug * [MCOBERTURA-86] - no coverage reported for integration-test * [MCOBERTURA-161] - cobertura report appear a lot of error : JavaNCSS got an error while parsing the java file * [MCOBERTURA-180] - Cobertura does not seem to work on OSX * [MCOBERTURA-189] - Code coverage is not working with Java 8 sources * [MCOBERTURA-190] - com.ibm.icu:icu:2.6.1 dependency makes maven-enforcer-plugin checkSignatureRule to fail ** Improvement * [MCOBERTURA-183] - Update Main class finding algorithm to handle Cobertura releases after 2.0.3 ** Task * [MCOBERTURA-187] - Upgrade to Cobertura 2.1.1 * [MCOBERTURA-192] - Require Java 6 Enjoy, The Mojo team. -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Source Release Assembly Descriptor 1.0.5 Released
The Apache Source Release Assembly Descriptor team is pleased to announce the apache-source-release-assembly-descriptor-1.0.5 release! This jar contains a customized source assembly descriptor to produce Apache compliant source bundles. http://maven.apache.org/apache-resource-bundles/ Changes in this version include: o Add pre-defined descriptor in apache-source-release-assembly-descriptor for tarball-only Issue: MASFRES-9. Have fun! -Apache Source Release Assembly Descriptor team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [ANN] Apache Maven Checkstyle Plugin 2.14 Released
James, Yes, there are lenghy discussions on this topic in JIRA. Have look at MCHECKSTYLE-251 for example. Version 2.15-SNAPSHOT is already using Checkstyle 6.1.1 and 2.16 will be using version Checkstyle 6.2. -- Dennis Lundberg Den 9 feb 2015 16:35 skrev "James Green" : > Dennis, > > Thanks for that - any reason why the maven plugin does not track the > Checkstyle releases then? That's the cause for the questioning in the first > place. > > James > > On 7 February 2015 at 10:31, Dennis Lundberg wrote: > > > Hi James > > > > Upgrading *should* work but, since we cannot predict what changes will > > be made to Checkstyle in the future, we cannot give any guarantees. If > > it works - great, if it doesn't then please file an issue telling us > > to update the plugin to a specific newer version of Checkstyle. Please > > check first that someone else hasn't already reported it. There are > > already issue for Checkstyle 6.1.1 (MCHECKSTYLE-261) and 6.2 > > (MCHECKSTYLE-272). > > > > On Fri, Feb 6, 2015 at 3:08 PM, James Green > > wrote: > > > The plugin page "Upgrading at runtime" mentions 5.8 is the default but > > that > > > upgrading to the latest should be possible. Does this take into account > > the > > > 6.x releases? > > > > > > Either way may be prudent to add a declaration to this page to avoid > > others > > > wondering the same question. > > > > > > Thanks, > > > > > > James > > > > > > On 5 February 2015 at 20:46, Dennis Lundberg > wrote: > > > > > >> The Maven team is pleased to announce the release of the Apache Maven > > >> Checkstyle Plugin, version 2.14 > > >> > > >> Generates a report on violations of code style and optionally fails > the > > >> build if violations are detected. > > >> > > >> http://maven.apache.org/plugins/maven-checkstyle-plugin/ > > >> > > >> You should specify the version in your project's plugin configuration: > > >> > > >> > > >> org.apache.maven.plugins > > >> maven-checkstyle-plugin > > >> 2.14 > > >> > > >> > > >> > > >> Release Notes - Apache Maven Checkstyle Plugin - Version 2.14 > > >> > > >> Bug > > >> * [MCHECKSTYLE-255] First checkstyle error is not printed in the > console > > >> ouput > > >> * [MCHECKSTYLE-254] Update plexus-interpolation to avoid thread safety > > >> issues > > >> * [MCHECKSTYLE-249] ITs failing when building on Windows from > > distribution > > >> prepared on Unix > > >> > > >> Improvement > > >> * [MCHECKSTYLE-283] Move maven_checks.xml and maven-header.txt away > from > > >> the plugin > > >> * [MCHECKSTYLE-282] add info on ruleset used in report intro > > >> * [MCHECKSTYLE-263] Removed dependency > > >> plexus-container-default:1.0-alpha-9-stable-1 > > >> * [MCHECKSTYLE-262] Upgrade to maven-plugins parent version 27 > > >> * [MCHECKSTYLE-257] display content/documentation of Checkstyle > > >> configurations predefined by maven-checkstyle-plugin in plugin's > > >> documentation site > > >> * [MCHECKSTYLE-256] add Java package information to output, instead of > > >> class name only > > >> * [MCHECKSTYLE-251] Upgrade to Checkstyle 5.8 > > >> > > >> Task > > >> * [MCHECKSTYLE-281] fail if deprecated parameters are used and display > > >> update instructions > > >> * [MCHECKSTYLE-280] add documentation on upgrading Checkstyle at > runtime > > >> * [MCHECKSTYLE-276] remove RedundantThrows rule from default configs > > >> * [MCHECKSTYLE-274] remove Avalon configuration since the Avalon > project > > >> is retired > > >> > > >> > > >> Enjoy, > > >> > > >> -The Maven team > > >> > > >> - > > >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > >> For additional commands, e-mail: users-h...@maven.apache.org > > >> > > >> > > > > > > > > -- > > Dennis Lundberg > > > > - > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org > > > > >
Re: [ANN] Apache Maven Checkstyle Plugin 2.14 Released
Hi James Upgrading *should* work but, since we cannot predict what changes will be made to Checkstyle in the future, we cannot give any guarantees. If it works - great, if it doesn't then please file an issue telling us to update the plugin to a specific newer version of Checkstyle. Please check first that someone else hasn't already reported it. There are already issue for Checkstyle 6.1.1 (MCHECKSTYLE-261) and 6.2 (MCHECKSTYLE-272). On Fri, Feb 6, 2015 at 3:08 PM, James Green wrote: > The plugin page "Upgrading at runtime" mentions 5.8 is the default but that > upgrading to the latest should be possible. Does this take into account the > 6.x releases? > > Either way may be prudent to add a declaration to this page to avoid others > wondering the same question. > > Thanks, > > James > > On 5 February 2015 at 20:46, Dennis Lundberg wrote: > >> The Maven team is pleased to announce the release of the Apache Maven >> Checkstyle Plugin, version 2.14 >> >> Generates a report on violations of code style and optionally fails the >> build if violations are detected. >> >> http://maven.apache.org/plugins/maven-checkstyle-plugin/ >> >> You should specify the version in your project's plugin configuration: >> >> >> org.apache.maven.plugins >> maven-checkstyle-plugin >> 2.14 >> >> >> >> Release Notes - Apache Maven Checkstyle Plugin - Version 2.14 >> >> Bug >> * [MCHECKSTYLE-255] First checkstyle error is not printed in the console >> ouput >> * [MCHECKSTYLE-254] Update plexus-interpolation to avoid thread safety >> issues >> * [MCHECKSTYLE-249] ITs failing when building on Windows from distribution >> prepared on Unix >> >> Improvement >> * [MCHECKSTYLE-283] Move maven_checks.xml and maven-header.txt away from >> the plugin >> * [MCHECKSTYLE-282] add info on ruleset used in report intro >> * [MCHECKSTYLE-263] Removed dependency >> plexus-container-default:1.0-alpha-9-stable-1 >> * [MCHECKSTYLE-262] Upgrade to maven-plugins parent version 27 >> * [MCHECKSTYLE-257] display content/documentation of Checkstyle >> configurations predefined by maven-checkstyle-plugin in plugin's >> documentation site >> * [MCHECKSTYLE-256] add Java package information to output, instead of >> class name only >> * [MCHECKSTYLE-251] Upgrade to Checkstyle 5.8 >> >> Task >> * [MCHECKSTYLE-281] fail if deprecated parameters are used and display >> update instructions >> * [MCHECKSTYLE-280] add documentation on upgrading Checkstyle at runtime >> * [MCHECKSTYLE-276] remove RedundantThrows rule from default configs >> * [MCHECKSTYLE-274] remove Avalon configuration since the Avalon project >> is retired >> >> >> Enjoy, >> >> -The Maven team >> >> - >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> >> -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Checkstyle Plugin 2.14 Released
The Maven team is pleased to announce the release of the Apache Maven Checkstyle Plugin, version 2.14 Generates a report on violations of code style and optionally fails the build if violations are detected. http://maven.apache.org/plugins/maven-checkstyle-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-checkstyle-plugin 2.14 Release Notes - Apache Maven Checkstyle Plugin - Version 2.14 Bug * [MCHECKSTYLE-255] First checkstyle error is not printed in the console ouput * [MCHECKSTYLE-254] Update plexus-interpolation to avoid thread safety issues * [MCHECKSTYLE-249] ITs failing when building on Windows from distribution prepared on Unix Improvement * [MCHECKSTYLE-283] Move maven_checks.xml and maven-header.txt away from the plugin * [MCHECKSTYLE-282] add info on ruleset used in report intro * [MCHECKSTYLE-263] Removed dependency plexus-container-default:1.0-alpha-9-stable-1 * [MCHECKSTYLE-262] Upgrade to maven-plugins parent version 27 * [MCHECKSTYLE-257] display content/documentation of Checkstyle configurations predefined by maven-checkstyle-plugin in plugin's documentation site * [MCHECKSTYLE-256] add Java package information to output, instead of class name only * [MCHECKSTYLE-251] Upgrade to Checkstyle 5.8 Task * [MCHECKSTYLE-281] fail if deprecated parameters are used and display update instructions * [MCHECKSTYLE-280] add documentation on upgrading Checkstyle at runtime * [MCHECKSTYLE-276] remove RedundantThrows rule from default configs * [MCHECKSTYLE-274] remove Avalon configuration since the Avalon project is retired Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Javadoc Plugin 2.10 Released
The Maven team is pleased to announce the release of the Apache Maven Javadoc Plugin, version 2.10. This release is focused on Java 8 compatibility. The Apache Maven Javadoc Plugin is a plugin that uses the javadoc tool for generating javadocs for the specified project. http://maven.apache.org/plugins/maven-javadoc-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-javadoc-plugin 2.10 Release Notes - Apache Maven Javadoc Plugin - Version 2.10 Task * [MJAVADOC-403] MavenProject/MavenSession Injection as a parameter instead as a component. * [MJAVADOC-398] Classes from build output directory can cause failure * [MJAVADOC-395] Add JDK8 support to maven-javadoc-plugin * [MJAVADOC-394] javadoc is not found properly by default under Oracle's JDK 7+ on Mac OSX * [MJAVADOC-386] Documentation links to oracle web site are broken * [MJAVADOC-380] Add Maven version used to Created-By entry in manifest * [MJAVADOC-376] please add property 'maven.javadoc.classifier' * [MJAVADOC-372] Index page should refer to Apache Maven for at least the first mention * [MJAVADOC-371] Goals missing from overview page * [MJAVADOC-369] New goals javadoc-no-fork and test-javadoc-no-fork which will not invoke generate-*-sources * [MJAVADOC-351] Javadoc:fix fixTags parameter doesn't support 'return' value Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven PMD Plugin 3.2 Released
The Maven team is pleased to announce the release of the Apache Maven PMD Plugin, version 3.2 A Maven plugin for the PMD toolkit, that produces a report on both code rule violations and detected copy and paste fragments, as well as being able to fail the build based on these metrics. http://maven.apache.org/plugins/maven-pmd-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-pmd-plugin 3.2 Release Notes - Apache Maven PMD Plugin - Version 3.2 Task * [MPMD-188] Require Java 6 * [MPMD-182] Upgrade to PMD 5.1.2 Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: cannot initialize module TreeWalker - Unable to instantiate SuppressWarningsHolder
Hi, That feature was added in Checkstyle 5.7, so you need maven-checkstyle-plugin 2.12 or newer. On Tue, Jul 29, 2014 at 8:11 AM, ecthelion wrote: > I have maven-checkstyle-plugin(v2.5) and maven-eclipse-plugin(v2.8) > configured. > > Everything worked as expected but as soon as I introduced, > > *AND/OR* name="SuppressWarningsFilter"/> to my checkstyle-config.xml, I started to > have problems building the project. > > Here is what I get: > > [ERROR] BUILD ERROR > 1> [INFO] > > 1> [INFO] Failed during checkstyle configuration > 1> > 1>EXEC : Embedded error : cannot initialize module TreeWalker - Unable to > instantiate SuppressWarningsHolder > 1> Unable to instantiate SuppressWarningsHolderCheck > > > If I remove SuppressWarningsHolderCheck, I get the same error for > SuppressWarningsFilter. > > Any ideas? > > Thanks > > > > -- > View this message in context: > http://maven.40175.n5.nabble.com/cannot-initialize-module-TreeWalker-Unable-to-instantiate-SuppressWarningsHolder-tp5801306.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Checkstyle Plugin 2.12.1 Released
The Maven team is pleased to announce the release of the Apache Maven Checkstyle Plugin, version 2.12.1 Generates a report on violations of code style and optionally fails the build if violations are detected. http://maven.apache.org/plugins/maven-checkstyle-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-checkstyle-plugin 2.12.1 Release Notes - Apache Maven Checkstyle Plugin - Version 2.12.1 Bug * [MCHECKSTYLE-227] Avalon and turbine checks are broken * [MCHECKSTYLE-225] headerLocation no longer sets checkstyle.header.file * [MCHECKSTYLE-224] Warning about missing XRef for module with no files to check Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Changes Plugin 2.10 Released
The Maven team is pleased to announce the release of the Apache Maven Changes Plugin, version 2.10 Creates a release history for inclusion into the site and assists in generating an announcement mail. http://maven.apache.org/plugins/maven-changes-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-changes-plugin 2.10 Release Notes - Apache Maven Changes Plugin - Version 2.10 Bug * [MCHANGES-329] RestJiraDownloader does not handle components, type, updated or version * [MCHANGES-326] announcement-mail does not respect templateEncoding * [MCHANGES-324] Plugin logs into JIRA, but doesn't seem to make the status request with the session * [MCHANGES-323] Incompatible Jira Issue Management URL suggested in documentation * [MCHANGES-280] announcement-mail broken when using the announcementFile parameter * [MCHANGES-266] It is not possible to disable the reports in submodules Improvement * [MCHANGES-328] Allow setting useJql parameter from the command line * [MCHANGES-303] Add an option to enable tls * [MCHANGES-282] New parameter releaseDateLocale in changes-check goal New Feature * [MCHANGES-292] announcement-generate goal doesn't respect useJql parameter Task * [MCHANGES-332] Update to maven-reporting-impl 2.2 * [MCHANGES-331] Update to Doxia 1.4 and Doxia Sitetools 1.4 Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Checkstyle Plugin 2.12 Released
The Maven team is pleased to announce the release of the Apache Maven Checkstyle Plugin, version 2.12 Generates a report on violations of code style and optionally fails the build if violations are detected. http://maven.apache.org/plugins/maven-checkstyle-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-checkstyle-plugin 2.12 Release Notes - Apache Maven Checkstyle Plugin - Version 2.12 Bug * [MCHECKSTYLE-222] Resource-only project is not checked * [MCHECKSTYLE-221] ResourceIncludes default value is wrong * [MCHECKSTYLE-219] When no license is specified, ALv2 from maven-checkstyle-plugin is used * [MCHECKSTYLE-210] Resource bundles have wrong file encoding * [MCHECKSTYLE-208] Plugin generates reports incompatible with the 'maven-jxr-plugin' version 2.4 * [MCHECKSTYLE-207] file handle leak - leading to failed builds * [MCHECKSTYLE-205] NPE in CheckstyleReportGenerator.doFilesSummary:654 version 2.11 regression * [MCHECKSTYLE-190] Add user property for checkstyle:consoleOutput * [MCHECKSTYLE-169] Suppressions property is incorrectly set if suppressions file is on classpath Improvement * [MCHECKSTYLE-218] Put file anchor directly on the h2 tag * [MCHECKSTYLE-212] Upgrade to Checkstyle 5.7 * [MCHECKSTYLE-209] Correct grammar, make icons and text consistent in the report * [MCHECKSTYLE-182] Use Maven log levels when logging to console New Feature * [MCHECKSTYLE-211] allow inline configuration for checkstyle plugin Task * [MCHECKSTYLE-213] Upgrade Doxia dependencies Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven PMD Plugin 3.1 Released
The Maven team is pleased to announce the release of the Apache Maven PMD Plugin, version 3.1 A Maven plugin for the PMD toolkit, that produces a report on both code rule violations and detected copy and paste fragments, as well as being able to fail the build based on these metrics. http://maven.apache.org/plugins/maven-pmd-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-pmd-plugin 3.1 Release Notes - Apache Maven PMD Plugin - Version 3.1 Bug * [MPMD-179] Plugin generates reports incompatible with the 'maven-jxr-plugin' version 2.4 * [MPMD-176] upgrade to last 5.0.5 * [MPMD-172] Warning about missing XRef for module with no source * [MPMD-168] Skip report generation if results are empty * [MPMD-167] CPD performance issues * [MPMD-166] Plugin fails when switching from 2.7.1 to 3.0.1 Improvement * [MPMD-180] Remove redundant "Report" word on report name labels * [MPMD-175] Work around PMD bug #1155 which crashes the plugin with an empty ruleset element. * [MPMD-169] Support multi-threaded mode of PMD 5 New Feature * [MPMD-181] Add flag to capture Benchmark information Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Checkstyle Plugin 2.12 Released
The Maven team is pleased to announce the release of the Apache Maven Checkstyle Plugin, version 2.12 Generates a report on violations of code style and optionally fails the build if violations are detected. http://maven.apache.org/plugins/maven-checkstyle-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-checkstyle-plugin 2.12 Release Notes - Apache Maven Checkstyle Plugin - Version 2.12 Task * [MCHECKSTYLE-222] Resource-only project is not checked * [MCHECKSTYLE-221] ResourceIncludes default value is wrong * [MCHECKSTYLE-219] When no license is specified, ALv2 from maven-checkstyle-plugin is used * [MCHECKSTYLE-218] Put file anchor directly on the h2 tag * [MCHECKSTYLE-213] Upgrade Doxia dependencies * [MCHECKSTYLE-212] Upgrade to Checkstyle 5.7 * [MCHECKSTYLE-211] allow inline configuration for checkstyle plugin * [MCHECKSTYLE-210] Resource bundles have wrong file encoding * [MCHECKSTYLE-209] Correct grammar, make icons and text consistent in the report * [MCHECKSTYLE-208] Plugin generates reports incompatible with the 'maven-jxr-plugin' version 2.4 * [MCHECKSTYLE-207] file handle leak - leading to failed builds * [MCHECKSTYLE-205] NPE in CheckstyleReportGenerator.doFilesSummary:654 version 2.11 regression * [MCHECKSTYLE-190] Add user property for checkstyle:consoleOutput * [MCHECKSTYLE-182] Use Maven log levels when logging to console * [MCHECKSTYLE-169] Suppressions property is incorrectly set if suppressions file is on classpath Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Help configuring checkstyle Maven plugin
Hi Andrew, Which tutorial is out of date? If you give me your working config, I can update the tutorials if needed. On Thu, Sep 26, 2013 at 4:33 PM, Andrew Pennebaker wrote: > Ah, the tutorials for this are out of date. For version 2.10 of this > plugin, the stuff should go inside ``, not ``. > > > On Tue, Sep 24, 2013 at 3:00 PM, Andrew Pennebaker > wrote: > >> Could someone help me tweak my checkstyle plugin in my pom? >> >> I would like `mvn checkstyle:check` to output the checkstyle results >> directly to the console, but setting true >> has no effect; it all goes to target/checkstyle-results.xml. >> -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Application Assembler Maven Plugin 1.5 Released
Hi, The Mojo team is pleased to announce the release of the Application Assembler Maven Plugin version 1.5. The Application Assembler Plugin is a Maven plugin for generating scripts for starting java applications. All dependencies and the artifact of the project itself are placed in a generated Maven repository in a defined assemble directory. All artifacts (dependencies + the artifact from the project) are added to the classpath in the generated bin scripts. http://mojo.codehaus.org/appassembler/appassembler-maven-plugin/ To get this update, simply specify the version in your project's plugin configuration: org.codehaus.mojo appassembler-maven-plugin 1.5 Release Notes ** Bug * [MAPPASM-96] - Deployment fails when used in combination with version 2.5 of the maven-deploy-plugin * [MAPPASM-152] - repositoryName can not be used in generate-daemons to give a separate location for the repository (JSW) * [MAPPASM-190] - invalid JAVA_HOME on mountain lion * [MAPPASM-194] - licenseHeaderFile ignored when generating booter daemons ** Improvement * [MAPPASM-93] - generate-daemon should support setting config dir and repos dir ** New Feature * [MAPPASM-71] - Support Repo's File Name Mapping Enjoy, The Mojo team. -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Mapping 1.0 Released
The Maven team is pleased to announce the release of the Apache Maven Mapping, version 1.0 A shared component to assist in interpolating file names using properties from a Maven project. http://maven.apache.org/shared/maven-mapping/ You should specify the version in your project's dependency configuration: org.apache.maven.shared maven-mapping 1.0 Release Notes - Apache Maven Mapping - Version 1.0 Task * [MSHARED-291] Copy code for file name mapping from Maven WAR Plugin Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven One Plugin 1.3 Released
The Maven team is pleased to announce the release of the Apache Maven One Plugin (RETIRED), version 1.3 As you can see in the release notes below, this plugin has now been retired. There will be no more releases of this plugin. Eases the migration from Maven 1.x to Maven 2.x by providing a POM converter etc. http://maven.apache.org/plugins/maven-one-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-one-plugin 1.3 Release Notes - Apache Maven One Plugin (RETIRED) - Version 1.3 Task * [MONE-33] Retire this plugin * [MONE-27] Upgrade to maven-model-converter 2.3 * [MONE-24] one:convert puts javadoc-plugin in build/plugins vs reporting/plugins * [MONE-23] one:convert kept a,b,c vs making abc * [MONE-6] The install goal should not assume that the "pom" packaging is only only one that does not have a primary artifact Enjoy, -The Maven team -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Model Converter 2.3 Released
The Maven team is pleased to announce the release of the Apache Maven Model Converter, version 2.3 As you can see in the release notes below, this shared component is now retired. Most likely it will be transferred to the Apache Archiva project. Converts between version 3.0.0 and version 4.0.0 models. http://maven.apache.org/shared/maven-model-converter/ You should specify the version in your project's dependency configuration: org.apache.maven.shared maven-model-converter 2.3 Release Notes - Apache Maven Model Converter (RETIRED) - Version 2.3 Task * [MSHARED-289] Retire this shared component * [MSHARED-71] Exclude some default files from the Site Plugin * [MSHARED-70] Allow the conversion of report plugins to specify reportSets * [MSHARED-69] Improve pretty printing the POM when it gets written to a file * [MSHARED-49] Add support for Castor plugin * [MSHARED-48] Add support for Jalopy plugin Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Model Converter 2.3 Released
The Maven team is pleased to announce the release of the Apache Maven Model Converter, version 2.3 As you can see in the release notes below, this shared component is now retired. Most likely it will be transferred to the Apache Archiva project. Converts between version 3.0.0 and version 4.0.0 models. http://maven.apache.org/shared/maven-model-converter/ You should specify the version in your project's dependency configuration: org.apache.maven.shared maven-model-converter 2.3 Release Notes - Apache Maven Model Converter (RETIRED) - Version 2.3 Task * [MSHARED-289] Retire this shared component * [MSHARED-71] Exclude some default files from the Site Plugin * [MSHARED-70] Allow the conversion of report plugins to specify reportSets * [MSHARED-69] Improve pretty printing the POM when it gets written to a file * [MSHARED-49] Add support for Castor plugin * [MSHARED-48] Add support for Jalopy plugin Enjoy, -The Maven team -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven IDEA Plugin 2.2.1 Released
The Maven team is pleased to announce the release of the Apache Maven IDEA Plugin, version 2.2.1. As you can see in the release notes below, this plugin has now been retired. There will be no more releases of this plugin. Generates project files for usage with IntelliJ IDEA from the POM. http://maven.apache.org/plugins/maven-idea-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-idea-plugin 2.2.1 Release Notes - Apache Maven IDEA Plugin (RETIRED) - Version 2.2.1 Task * [MIDEA-128] Retire this plugin Enjoy, -The Maven team -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[RESULT] [VOTE] Retire Maven One Plugin
Hi, The vote has passed with the following result: +1 (binding): Olivier Lamy, Robert Scholte, Arnaud Héritier, Hervé Boutemy, Wayne Fay, Stephen Connolly, Ralph Goers, Brett Porter, Stephane Nicoll, Dennis Lundberg +1 (non binding): Anders Hammar, Lennart Jörelid, Baptiste Mathus I will continue with the steps required to retire this plugin. On Sat, Jul 20, 2013 at 11:13 AM, Dennis Lundberg wrote: > Hi, > > Now that we have Maven 1 at End-Of-Life, I think it's time to retire > Maven One Plugin as well. It has been almost six years since the last > release. I therefor propose that we retire maven-one-plugin. > > http://maven.apache.org/plugins/maven-one-plugin/ > > If this vote is successful I will make one final release of the > plugin, making it clear on the plugin site that it has been retired. > After that the source code will be moved into the "retired" area in > Subversion. > > The process for retiring a plugin is described here, and is being improved: > http://maven.apache.org/developers/retirement-plan-plugins.html > > The vote is open for 72 hours. > > [ ] +1 Yes, it's about time > [ ] -1 No, because... > > -- > Dennis Lundberg -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[RESULT] [VOTE] Retire Maven Model Converter
Hi, The vote has passed with the following result: +1 (binding): Arnaud Héritier, Hervé Boutemy, Wayne Fay, Stephen Connolly, Ralph Goers, Brett Porter, Dennis Lundberg +1 (non binding): Lennart Jörelid, Baptiste Mathus I will continue with the steps required to retire this shared component. On Sat, Jul 20, 2013 at 7:26 PM, Dennis Lundberg wrote: > Hi, > > The only consumer of Maven Model Converter we have left at the Apache > Maven project is Maven One Plugin. If the vote for the retirement of > Maven One Plugin succeeds we should also retire Maven Model Converter. > The last release was made almost six years ago. Last time I checked > Maven Model Converter was also used by the Apache Archiva project. The > retirement plan is to move the component to the Apache Archiva > project, if they want it. > > http://maven.apache.org/shared/maven-model-converter/ > > I therefor propose that we retire maven-model-converter. > > If this vote is successful I will make one final release of the > component (there are some issues that have been fixed) making it clear > on the component site that it has been retired. After that the source > code will be moved to the Apache Archiva project in Subversion, or if > they do not want it to the "retired" area in Subversion. > > The process for retiring a plugin is described here: > http://maven.apache.org/developers/retirement-plan-plugins.html > > The vote is open for 72 hours. > > [ ] +1 Yes, it's about time > [ ] -1 No, because... > > -- > Dennis Lundberg -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[RESULT] [VOTE] Retire maven-idea-plugin
Hi, The vote has passed with the following result: +1 (binding): Arnaud Héritier, Robert Scholte, Stéphane Nicoll, Ralph Goers, Stephen Connolly, Olivier Lamy, Kristian Rosenvold, Wayne Fay, Brett Porter, Dennis Lundberg +1 (non binding): Lennart Jörelid, Anders Hammar, Baptiste Mathus, Chris Graham I will continue with the steps required to retire this plugin. On Fri, Jul 19, 2013 at 7:01 PM, Dennis Lundberg wrote: > Hi > > It has been almost five years since I made the last release of > maven-idea-plugin. The features in IDEA to integrate Maven has been greatly > improved since then, making our own plugin obsolete. I therefor propose that > we retire maven-idea-plugin. > > If this vote is successful I will make one final release of the plugin, > making it clear on the plugin site that it has been retired. After that the > source code will be moved into the "retired" area in Subversion. > > This is AFAIK the first vote to follow our process for retiring a plugin. > For those interested, the process is described here: > http://maven.apache.org/developers/retirement-plan-plugins.html > > > [ ] +1 Yes, it's about time > [ ] -1 No, because... > > -- > Dennis Lundberg -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[VOTE] Retire Maven Model Converter
Hi, The only consumer of Maven Model Converter we have left at the Apache Maven project is Maven One Plugin. If the vote for the retirement of Maven One Plugin succeeds we should also retire Maven Model Converter. The last release was made almost six years ago. Last time I checked Maven Model Converter was also used by the Apache Archiva project. The retirement plan is to move the component to the Apache Archiva project, if they want it. http://maven.apache.org/shared/maven-model-converter/ I therefor propose that we retire maven-model-converter. If this vote is successful I will make one final release of the component (there are some issues that have been fixed) making it clear on the component site that it has been retired. After that the source code will be moved to the Apache Archiva project in Subversion, or if they do not want it to the "retired" area in Subversion. The process for retiring a plugin is described here: http://maven.apache.org/developers/retirement-plan-plugins.html The vote is open for 72 hours. [ ] +1 Yes, it's about time [ ] -1 No, because... -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[VOTE] Retire Maven One Plugin
Hi, Now that we have Maven 1 at End-Of-Life, I think it's time to retire Maven One Plugin as well. It has been almost six years since the last release. I therefor propose that we retire maven-one-plugin. http://maven.apache.org/plugins/maven-one-plugin/ If this vote is successful I will make one final release of the plugin, making it clear on the plugin site that it has been retired. After that the source code will be moved into the "retired" area in Subversion. The process for retiring a plugin is described here, and is being improved: http://maven.apache.org/developers/retirement-plan-plugins.html The vote is open for 72 hours. [ ] +1 Yes, it's about time [ ] -1 No, because... -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: mvn test can't find the resource but mvn exec:exec running is ok
Hi
Where in your source tree is the file config.properties located?
Also, it looks like you are feeding exec-maven-plugin an empty classpath in
.
On Wed, Jun 19, 2013 at 10:14 AM, Inred wrote:
> my pom.xml
>
>org.codehaus.mojo
>exec-maven-plugin
>1.2.1
>
> java
>
> -classpath
>
>
> helper.BaseCheckerTest
>
>
>
>
>
>
>org.codehaus.mojo
>exec-maven-plugin
>1.2.1
>
>
> process-test-classes
>
> java
>
>
>
>
> helper.BaseCheckerTest
> runtime
>
>
> -classpath
>
>
>
>
>
>
>
>
>
> it's ok when
> c:\>mvn exec:exec
>
> but it report that can't find the resouce file config.properties when i do
> c:\>mvn test
>
> Class BaseCheckerTest{
> static {
> try {
> prop = new Properties();
> prop.load(ClassLoader.class.getResourceAsStream("/config.properties"));
> } catch (Exception e) {
> // TODO Auto-generated catch block
> e.printStackTrace();
> }
> }
> }
>
>
>
> c:\>mvn --version
> Apache Maven 3.0.4 (r1232337; 2012-01-17 16:44:56+0800)
> Maven home: C:\Downloads\apache-maven-3.0.4\bin\..
> Java version: 1.6.0_24, vendor: Sun Microsystems Inc.
> Java home: C:\Program Files (x86)\Java\jdk1.6.0_24\jre
>
> --
> Dennis Lundberg
Re: Maven script for connecting svn and checking out code
Hi
If I understand you correctly, you need to split your project into (at
least) 6 modules. One module for each "folder" as you call them. Please
read this:
http://maven.apache.org/guides/mini/guide-multiple-modules.html
When you say you want to "connect to a dependent folder", in the Maven
world what you do is that you add a dependency.
On Tue, Jul 2, 2013 at 8:36 AM, Keerthana wrote:
> Hi,
>
> I am new to Maven and i need a help. I have a pom.xml file which is
> connecting to SVN and checking out the code. There are totally 6 folders in
> the checked out code. Out of which one folder is independent and all the
> other 5 are dependent on the other. Now i need to compile the checked out
> code separately and create jar and connect to the dependent folders and
> finally create war for the 6th folder. Please can anyone help me to do
> this.
>
> Below is my pom.xml file which is connecting to svn and checking out and
> creating war file of the same project.
>
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
> 4.0.0
> com.sample.webapp
> HellojBossApp
> war
> 0.0.1-SNAPSHOT
> HellojBossApp Maven Webapp
> http://maven.apache.org
>
>
> scm:svn:http://d-113017553/svn/PRONTO/trunk/dev
>
> scm:svn:http://d-113017553/svn/PRONTO/trunk/dev
>
> http://d-113017553/svn/PRONTO/trunk/dev
>
>
>
> junit
> junit
> 3.8.1
> test
>
>
>
> HellojBossApp
>
>
> org.apache.maven.plugins
> maven-scm-plugin
> 1.8.1
>
> connection
> keerthana
> keerthana
>
> ${project.basedir}/co/src
>
> ${project.basedir}/co/src
>
>
>
>
>
> maven-release-plugin
> 2.2.2
>
>
> release
> scm:checkout
>
>
>
> org.apache.maven.plugins
> maven-war-plugin
> 2.1.1
>
> HellojBossApp
>
>
> D:\Keerthana\jboss-as-7.1.1.Final\standalone\deployments
>
>
>
>
>
>
>
>
>
> --
> View this message in context:
> http://maven.40175.n5.nabble.com/Maven-script-for-connecting-svn-and-checking-out-code-tp5761624.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
> --
> Dennis Lundberg
Re: maven-changelog-plugin not working...
> > [ERROR] Failed to execute goal > > org.apache.maven.plugins:maven-changelog-plugin:2.1:changelog > (default-cli) > > on project uCMDB-PatternDev: An error has occurred in Change Log report > > generation. NullPointerException -> [Help 1] > > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > > goal org.apache.maven.plugins:maven-changelog-plugin:2.1:changelog > > (default-cli) on project uCMDB-PatternDev: An error has occurred in > Change > > Log report generation. > > at > > > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217) > > at > > > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > > at > > > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > > at > > > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) > > at > > > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) > > at > > > org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) > > at > > > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) > > at > > org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) > > at > > org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) > > at > org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) > > at > org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) > > at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) > > 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.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) > > at > > > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) > > at > > > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) > > at > > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) > > Caused by: org.apache.maven.plugin.MojoExecutionException: An error has > > occurred in Change Log report generation. > > at > > > org.apache.maven.reporting.AbstractMavenReport.execute(AbstractMavenReport.java:79) > > at > > > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) > > at > > > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) > > ... 19 more > > Caused by: java.lang.NullPointerException > > at > > > org.apache.maven.plugin.changelog.ChangeLogReport$1.compare(ChangeLogReport.java:1046) > > at > > java.util.TimSort.countRunAndMakeAscending(TimSort.java:324) > > at java.util.TimSort.sort(TimSort.java:203) > > at java.util.TimSort.sort(TimSort.java:173) > > at java.util.Arrays.sort(Arrays.java:659) > > at java.util.Collections.sort(Collections.java:217) > > at > > > org.apache.maven.plugin.changelog.ChangeLogReport.doChangedSetTable(ChangeLogReport.java:1040) > > at > > > org.apache.maven.plugin.changelog.ChangeLogReport.doChangedSet(ChangeLogReport.java:889) > > at > > > org.apache.maven.plugin.changelog.ChangeLogReport.doGenerateReport(ChangeLogReport.java:847) > > at > > > org.apache.maven.plugin.changelog.ChangeLogReport.executeReport(ChangeLogReport.java:340) > > at > > > org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:98) > > at > > > org.apache.maven.reporting.AbstractMavenReport.execute(AbstractMavenReport.java:73) > > ... 21 more > > > > - > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org > > > > > > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > -- > Dennis Lundberg
Re: Checkstyle crashes with NullPointerException in DefaultCheckstyleRssGenerator.generateRSS in Maven 3
Hi For Maven 3 compatibility you need to use maven-checkstyle-plugin 2.5 or newer. On Thu, Jun 20, 2013 at 1:25 AM, Adam Crume wrote: > Checkstyle crashes when I run it with Maven 3.0.4, but works with Maven > 2.2.1. > > I'm afraid I don't know enough about Maven to create a smaller test case > than this: > > 1. Set JAVA_HOME to a 1.6 JDK > 2. Clone http://github.com/nasa/mct > 3. Follow the steps in README.md, using Maven 3 > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-checkstyle-plugin:2.4:checkstyle > (published-api-checks) on project mct-platform: Execution > published-api-checks of goal > org.apache.maven.plugins:maven-checkstyle-plugin:2.4:checkstyle failed. > NullPointerException -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal org.apache.maven.plugins:maven-checkstyle-plugin:2.4:checkstyle > (published-api-checks) on project mct-platform: Execution > published-api-checks of goal > org.apache.maven.plugins:maven-checkstyle-plugin:2.4:checkstyle failed. > at > > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:225) > at > > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at > > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at > > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) > at > > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) > at > > org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) > at > > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at > > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) > at > > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) > at > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) > Caused by: org.apache.maven.plugin.PluginExecutionException: Execution > published-api-checks of goal > org.apache.maven.plugins:maven-checkstyle-plugin:2.4:checkstyle failed. > at > > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:110) > at > > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) > ... 19 more > Caused by: java.lang.NullPointerException > at > > org.apache.maven.plugin.checkstyle.rss.DefaultCheckstyleRssGenerator.generateRSS(DefaultCheckstyleRssGenerator.java:72) > at > > org.apache.maven.plugin.checkstyle.CheckstyleReport.executeReport(CheckstyleReport.java:639) > at > > org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:131) > at > > org.apache.maven.reporting.AbstractMavenReport.execute(AbstractMavenReport.java:76) > at > > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) > ... 20 more > > Adam > > -- > Dennis Lundberg
[VOTE] Retire maven-idea-plugin
Hi It has been almost five years since I made the last release of maven-idea-plugin. The features in IDEA to integrate Maven has been greatly improved since then, making our own plugin obsolete. I therefor propose that we retire maven-idea-plugin. If this vote is successful I will make one final release of the plugin, making it clear on the plugin site that it has been retired. After that the source code will be moved into the "retired" area in Subversion. This is AFAIK the first vote to follow our process for retiring a plugin. For those interested, the process is described here: http://maven.apache.org/developers/retirement-plan-plugins.html [ ] +1 Yes, it's about time [ ] -1 No, because... -- Dennis Lundberg
[ANN] Maven Checkstyle Plugin 2.10 Released
The Maven team is pleased to announce the release of the Maven Checkstyle Plugin, version 2.10 Generates a report on violations of code style and optionally fails the build if violations are detected. http://maven.apache.org/plugins/maven-checkstyle-plugin You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-checkstyle-plugin 2.10 Release Notes - Maven Checkstyle Plugin - Version 2.10 Bug * [MCHECKSTYLE-181] Upgrade to Checkstyle 5.6 * [MCHECKSTYLE-172] Checkstyle Plugin 2.8+ generates an additional aggregate report * [MCHECKSTYLE-167] Unconfigured checkstyle plugin duplicates entries in aggregated report * [MCHECKSTYLE-144] If 'src/main/java' does not exist in a project then checkstyle skips the other source folders of the project Improvement * [MCHECKSTYLE-175] Upgrade usage.htm to make it clear how configuration is done New Feature * [MCHECKSTYLE-184] Allow src/main/resources to be searched by Checkstyle Task * [MCHECKSTYLE-179] use plexus java 5 annotations instead of old-style javadoc annotations * [MCHECKSTYLE-178] use maven-plugin-tools' java 5 annotations Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: assembly plugin logging anomaly
Hi Steve, I can't remember what notation system it uses, but its a different one than what is usually seen for unix like permissions. It comes from a component that the plugin uses to perform these operations. On 2013-01-07 21:49, Steve Cohen wrote: > Using the assembly plugin I have a file set defined with > 644 > 755 > > This works correctly - the archive generated has the desired permissions. > > But the logging says > [DEBUG] FileSet[outputDir/] dir perms 4 file perms 10 > > What notation system is this and why does the plugin report it this way > in the log. > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Optional dependency not overlaid
Hi Daniel, The 2.0 version of Maven WAR Plugin is over 6 years old. The first thing I'd do is try a later version to see if it solves your problem. The latest version is 2.3. On 2012-12-08 02:32, Winsor, Daniel wrote: > Hi, > > I have declared an optional dependency, but it is not being overlaid with > maven-war-plugin v 2.0 > > //parent-of-everything/pom.xml > > > > org.apache.maven.plugins > > maven-war-plugin > > > > > > > > to-be-overlaid > > > > ** > > > > > > > > > > > > > > > > > > > > //some-webapp-war/pom.xml > > > > > > to-be-overlaid > > true > > war > > > > > > > When optional is set to false, then > > [INFO] Assembling webapp some-webapp-war in /target/some-webapp-war > > [INFO] Expanding: /.m2/repository/to-be-overlaid.war into > /target/to-be-overlaid > > [INFO] Overlaying 1 war(s). > > > When optional is set to true, then no such overlaying happens. > > However, according to optional dependencies, if some-webapp-war optionally > depends on to-be-overlaid, well it should show up in this first level > dependency, just like normal. What is going on here? And how can I best > overlay a war to certain other wars while leaving them out of most wars using > parent-of-everything (I am currently using a property in the skip parameter > in maven-war-plugin)? > > Thank you, > Daniel Winsor > Associate, IT Architecture > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Neater way to include/exclude DAO tests?
Hi No, we use a very old version (8.something) of Oracle that doesn't handle NULLs at all for CHAR or VARCHAR fields. If you insert null into them it is magically transformed into an empty string '', thus solving the sorting issue. On 2012-11-24 08:38, Stephane-3 wrote: > Hi Dennis, > > Thanks for the feedback. I'm impressed by the fact that you succeeded in not > using any different sql syntax for the different database servers out there. > I'm faced with the ordering by "nulls first on MySql" vs "nulls last on > Oracle" issue on resorted to a specific DAO method for Oracle with a native > sql statement containing the "nulls first" clause. Haven't you been bitten > by this one ? :-) > > I posted on the Hibernate forum as it is more a Hibernate issue than a Maven > one. > > https://forum.hibernate.org/viewtopic.php?f=1&t=1024833 > > Kind Regards, > > > > > -- > View this message in context: > http://maven.40175.n5.nabble.com/Neater-way-to-include-exclude-DAO-tests-tp110827p5732802.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Neater way to include/exclude DAO tests?
On 2012-11-23 06:44, Stephane-3 wrote: > Hello Dennis, Hi Stephane > I'm interested in how you set up your multi database servers with syntax > specifics project. > > Could you elaborate on that ? As I explained in an earlier post, we have a couple of different .ddl scripts that helps us set up a database from scratch for running tests. These handle the differences in syntax between database vendors when it comes to setting up the database. Our current setup is: - Derby for automatic unit testing - MySQL for integration testing using an external test database on another server. It is activated by a profile in the POM that redirects all tests to that database instead of the embedded Derby one. - MySQL or Oracle in production, depending on product > I have a MySql based project and am now trying to port it on Oracle but some > sql statements need specific syntax. We do not use different SQL syntax for different databases in our Java code - we use the same DAO implementations for all databases. > It would be nice to inject some Oracle specific DAOs in the Spring context > when the sql syntax requires iit. Sorry, can't be of any help when it comes to Spring... > Thanks for any direction tips ! > > > > > -- > View this message in context: > http://maven.40175.n5.nabble.com/Neater-way-to-include-exclude-DAO-tests-tp110827p5732575.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Assembly Plugin 2.4 Released
The Maven team is pleased to announce the release of the Maven Assembly Plugin, version 2.4 A Maven plugin to create archives of your project's sources, classes, dependencies etc. from flexible assembly descriptors. http://maven.apache.org/plugins/maven-assembly-plugin You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-assembly-plugin 2.4 Release Notes - Maven Assembly Plugin - Version 2.4 Bug * [MASSEMBLY-636] Directory permissions still not correct for dirs created by dependencySet * [MASSEMBLY-633] Misspelled expression/property for parameter updateOnly * [MASSEMBLY-629] Explanation of default value for useAllReactorProjects is at best confusing, possibly wrong * [MASSEMBLY-626] NullPointerException in PlexusIoURLResource.getContents * [MASSEMBLY-621] directoryMode not enforced * [MASSEMBLY-620] The dependencySet/includes/include format is documented incorrectly * [MASSEMBLY-608] Missing XML tag in example documentation * [MASSEMBLY-604] Please document dir * [MASSEMBLY-602] Multiple Assemblies Causes Infinite Loop\Recursion * [MASSEMBLY-599] Mistake in javadoc for dependencySet/includes * [MASSEMBLY-591] Empty classifier in dependency causes extra dash * [MASSEMBLY-567] Version wildcard in dependencySet include does not work * [MASSEMBLY-553] Assembly plugin does not inherit configuration/execution from parent * [MASSEMBLY-549] StackOverflowError while creating assembly * [MASSEMBLY-449] Permissions on directories in a zipped archive incorrect * [MASSEMBLY-422] Generated directories have wrong file attributes * [MASSEMBLY-371] Converting line endings corrupts ISO-8859-1 files when platform encoding is UTF-8 * [MASSEMBLY-96] using fileSet -> lineEnding will always put the selected lineEnding at the end of the file, even if the original file does not end in one Improvement * [MASSEMBLY-634] Add Maven version used to Created-By entry in manifest * [MASSEMBLY-631] "Using Component Descriptors" page uses deprecated assembly goal * [MASSEMBLY-627] use last plexus-utils 3.0.7 which is faster on copying files. * [MASSEMBLY-623] Assembly documentation does not list all supported formats * [MASSEMBLY-611] Documentation unclear in Usage > Configuration (part 2) * [MASSEMBLY-610] Documentation unclear in the Usage > Configuration section * [MASSEMBLY-546] Cannot supply escapeString for filtering * [MASSEMBLY-532] Documentation has parts reversed for full include/exclude patterns in dependencySet New Feature * [MASSEMBLY-630] Add recompressZippedFiles support to assembly Task * [MASSEMBLY-635] Update to maven-filtering:1.1 * [MASSEMBLY-618] use maven-plugin-tools' java 5 annotations Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven site can not find parent
tMaven.execute(DefaultMaven.java:156)at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)atsun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)atsun.reflect.Deleg atingMet hodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)at java.lang.reflect.Method.invoke(Method.java:616)atorg.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)atorg.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)atorg.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)atorg.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)Caused by: org.apache.maven.plugin.MojoExecutionException:SiteToolException: Unable to read local module-POMatorg.apache.maven.plugins.site.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:300)atorg.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:154)at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:138)atorg.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)atorg.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)... 19 moreCaus ed by: org.apache.maven.doxia.tools.SiteToolException: Unable toread local module-POMatorg.apache.maven.doxia.tools.DefaultSiteTool.populateModulesMenu(DefaultSiteTool.java:892)atorg.apache.maven.doxia.tools.DefaultSiteTool.getDecorationModel(DefaultSiteTool.java:488)atorg.apache.maven.plugins.site.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:293)... 23 moreCaused by: org.apache.maven.project.InvalidProjectModelException: 1problem was encountered while building the effective model forgroupId:moduleA:1.1.5-SNAPSHOT[FATAL] Non-resolvable parent POM forgroupId:projectName:1.1.5-SNAPSHOT: Could not find artifactgroupId:parent:pom:1.0.3 in central(http://repo1.maven.org/maven2) @groupId:projectName:1.1.5-SNAPSHOT, /home/agomes/workspace/projectName/pom.xml,line 9, column 10for project groupId:moduleA:1.1.5-SNAPSHOTat /home/agomes/workspace/projectName/moduleA/pom.xml for projectgroupId:moduleA:1.1.5-SNAPSHOTat /home/agomes/workspace/projectNa me/modul eA/pom.xmlatorg.apache.maven.project.DefaultMavenProjectBuilder.transformError(DefaultMavenProjectBuilder.java:194)atorg.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:211)atorg.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:223)atorg.apache.maven.doxia.tools.DefaultSiteTool.populateModulesMenu(DefaultSiteTool.java:888)... 25 more > > > > > -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] ASF Parent 12 Released
The Maven team is pleased to announce the release of the Apache Software Foundation Parent POM version 12. This project consists of a POM that contains settings that are likely to be useful to any Apache project that is building and releasing code with Maven 2/3. By using this project as a parent, a project gets these settings. http://maven.apache.org/pom/asf/ For details about the changes that went into this release, see the "History" at the bottom of the front page of the site. Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Should maven-war-plugin accept null includes?
Hi Daniel,
Could you please try the latest version, 2.3, of Maven WAR Plugin and
see if it has the same behavior?
If it work the same way, then please file an issue in JIRA at
https://jira.codehaus.org/browse/MWAR
On 2012-11-02 22:16, Winsor, Daniel wrote:
> Hi,
>
> I ran into the use case where I'd like to have an overlay that will either
> include a file or not, depending on a property. EG
>
> file1
> file2
>
> ${some.property}
>
>
>
> Where
>
>
>
>
>
> Unfortunately this results in an exception being thrown during the build,
> since the file is null -> Failed to execute goal
> org.apache.maven.plugins:maven-war-plugin:2.1.1:war (default-war) on
> project neo-widgets: Execution default-war of goal
> org.apache.maven.plugins:maven-war-plugin:2.1.1:war failed.
> NullPointerException
>
> Interestingly, the packageExcludes parameter of the same plugin does
> accept null. So although I made a workaround by setting the property to
> "dummy_value_cant_be_null", should this plugin be made to accept null
> include parameters?
>
>
>
> Thank you,
> Daniel Winsor
> Associate, IT Architecture
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
--
Dennis Lundberg
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Remote Resources Plugin 1.4 Released
The Maven team is pleased to announce the release of the Maven Remote Resources
Plugin, version 1.4
Process resources packaged in JARs that have been deployed to
a remote repository. The primary use case being satisfied is the consistent
inclusion of common resources in a large set of projects. Maven projects at
Apache use this plug-in to satisfy licensing requirements at Apache where
each project must include license and notice files for each release.
http://maven.apache.org/plugins/maven-remote-resources-plugin
You should specify the version in your project's plugin configuration:
org.apache.maven.plugins
maven-remote-resources-plugin
1.4
Release Notes - Maven Remote Resources Plugin - Version 1.4
Bug
* [MRRESOURCES-64] Mojo: process uses deprecated expression
project.build.resources
* [MRRESOURCES-56] The maven-remote-resources-plugin (1.2.1) fails to create a
usable Resource Bundle if the outputDirectory configuration parameter is
specified and does not explicitly contain ${project.build.outputDirectory}
Task
* [MRRESOURCES-66] Update to Maven Filtering 1.1
* [MRRESOURCES-63] use maven-plugin-tools' java 5 annotations
Enjoy,
-The Maven team
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: pdf problem
Hi Have a look at the PDF Plugin: https://maven.apache.org/plugins/maven-pdf-plugin/ On 2012-10-23 22:32, Loay Mohammed wrote: > Dear All > > I have mvn install in my windows 7 and it is working fine, i have documents > in xml make by mvn, how can i make it to be in PDF. > > > Thanks > -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Site Plugin 3 3.2 Released
The Maven team is pleased to announce the release of the Maven Site Plugin 3, version 3.2 The Maven Site Plugin is a plugin that generates a site for the current project. http://maven.apache.org/plugins/maven-site-plugin You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-site-plugin 3.2 Release Notes - Maven Site Plugin 3 - Version 3.2 Bug * [MSITE-652] site not staging when skipDeploy=true * [MSITE-649] The staged site is still deployed to a wrong place * [MSITE-645] Menu no longer accepts "href" attribute * [MSITE-644] NullPointerException when site URL is not defined in distributionManagement Improvement * [MSITE-647] reduce visibility of the new reportPlugins format documentation waiting for better support Task * [MSITE-643] use maven-plugin-tools' java 5 annotations Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven WAR Plugin 2.3 Released
The Maven team is pleased to announce the release of the Maven WAR Plugin, version 2.3 Builds a Web Application Archive (WAR) file from the project output and its dependencies. http://maven.apache.org/plugins/maven-war-plugin You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-war-plugin 2.3 Release Notes - Maven WAR Plugin - Version 2.3 Bug * [MWAR-275] An incomplete fix for the NPE bugs in WebappStructure.java * [MWAR-246] NullPointerException Processing Web Resources * [MWAR-241] Overlay and an empty classifier Improvement * [MWAR-287] use last plexus-utils 3.0.7 which is faster on copying files. * [MWAR-164] Support for specifying which encoding to use when filtering resources New Feature * [MWAR-292] Add flag for recompressZippedFiles Task * [MWAR-291] Update skinny war documentation to reference instead of Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [PATCH provided] How to generate an announcement from GitHub with Changes plugin?
Thank you! I'll review the patch. It might take a little while before I get to it, but I promise that I will. On 2012-09-30 13:40, Markku Saarela wrote: > Hi > > Created issue MCHANGES-290 > <http://jira.codehaus.org/browse/MCHANGES-290> and patch is applied. > > Markku > > On 09/30/2012 08:43 AM, Markku Saarela wrote: >> Hi, >> >> Thanks, i'll look those. >> >> Markku >> >> On 09/30/2012 12:06 AM, Dennis Lundberg wrote: >>> Hi >>> >>> Support for a report based on issues at GitHub was added in the latest >>> version. There is no support for announcements yet. It should be >>> relatively easy to do though, now that the code to fetch issues from the >>> GitHub issue tracker is in place. >>> >>> Patches are welcome. Have a look in AnnouncementMojo how it has been >>> implemented for JIRA and Trac. >>> >>> On 2012-09-29 10:22, Markku Saarela wrote: >>>> Hi, >>>> >>>> Is it possible somehow to generate an announcement from GitHub with >>>> Changes plugin. >>>> >>>> Or is there an other way? >>>> >>>> Rgds, Markku >>>> >>>> - >>>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >>>> For additional commands, e-mail: users-h...@maven.apache.org >>>> >>> >> >> >> - >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> > > -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to generate an announcement from GitHub with Changes plugin?
Hi Support for a report based on issues at GitHub was added in the latest version. There is no support for announcements yet. It should be relatively easy to do though, now that the code to fetch issues from the GitHub issue tracker is in place. Patches are welcome. Have a look in AnnouncementMojo how it has been implemented for JIRA and Trac. On 2012-09-29 10:22, Markku Saarela wrote: > Hi, > > Is it possible somehow to generate an announcement from GitHub with > Changes plugin. > > Or is there an other way? > > Rgds, Markku > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Doxia Integration Tools 1.5 Released
The Maven team is pleased to announce the release of the Maven Doxia Integration Tools, version 1.5 This shared component has some utilities that are useful when integrating Doxia in Maven, mainly for site generation and report creation. The main entry point is the SiteTool Plexus component. http://maven.apache.org/doxia/doxia-tools/doxia-integration-tools/ You should specify the version in your project's plugin configuration: org.apache.maven.doxia doxia-integration-tools 1.5 Release Notes - Maven Doxia Tools 1.5 ** Bug * [DOXIATOOLS-16] - NullPointerException when site URL is being generated ** Improvement * [DOXIATOOLS-35] - [PATCH] Migration from obsolete plexus-maven-plugin to plexus-containers-component-metadata ** Task * [DOXIATOOLS-37] - use plexus java 5 annotations instead of old-style javadoc annotations * [DOXIATOOLS-41] - Update to Doxia base 1.3 * [DOXIATOOLS-42] - Upgrade to doxia-sitetools-1.3 Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Changes Report Plugin 2.8 Released
The Maven team is pleased to announce the release of the Maven Changes Report Plugin, version 2.8 Creates a release history for inclusion into the site and assists in generating an announcement mail. http://maven.apache.org/plugins/maven-changes-plugin You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-changes-plugin 2.8 Release Notes - Maven Changes Report Plugin - Version 2.8 Bug * [MCHANGES-285] SAXException parsing JIRA XML from JIRA 5.1 Improvement * [MCHANGES-268] Create an issue link template for Sourceforge 2.0 * [MCHANGES-267] Add ability to skip JIRA report creation * [MCHANGES-176] Make ConversionTool available in the VelocityContext New Feature * [MCHANGES-283] Add GitHub reporter Task * [MCHANGES-284] use maven-plugin-tools' java 5 annotations Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Any ETA for a m-project-info-report-p 2.5.1 release?
On 2012-08-23 10:16, myron0...@gmx.net wrote: > Hi, > > just wanted to know, if and when there's a release planned. It is currently being voted on. > Tested the 2.6-SN and it worked fine so far. > Really want the working new DependencyInfo report :) > Or is there anything from the unscheduled items we should wait for? > > TIA > Myron > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Is install always required before compile?
On 2012-08-12 18:34, Lewis John Mcgibbney wrote: > Hi, Hi > I am currently working on a project which has required us to branch > [0] Gora trunk and begin some slight APi refactoring to accommodate > the added functionality we intend to implement. > > I have one question though. If I do a clean checkout of the code then > run mvn clean compile I get a failure due to the new refactoring. If > however I do mvn clean install, then mvn clean compile everything is > OK. > > Is this normal behavior? No. My gut feeling is that you have something wrong in your dependency tree regarding your internal modules. Looking at the parent pom.xml you seem to be using test jars in two different ways. Either type=test-jar or classifier=tests. The first one has had problems depending on which version of Maven you use, see http://jira.codehaus.org/browse/MNG-2045 Can you share with us the error you get? > Kind Regards and thank you in advance for any suggestion or help. > > Lewis > > [0] http://svn.apache.org/repos/asf/gora/branches/goraamazon/ > -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: problem: Maven creates the second plugin classloader during parallel build and uses two classloader hierachies simultaneously
On 2012-07-11 11:42, Oleg Estekhin wrote: > Hi, > > I am trying to solve the mystery behind > http://code.google.com/p/maven-svn-revision-number-plugin/issues/detail?id=16 > with the help of the reporter of the original issue and the developer of > SqlJet library. > > So far we have found that at some point there appears second > classloader, which initializes some singleton classes second time, and > after that the parallel build continues with two separate singletons. > One set of build tasks still uses the first singleton, other set of > build tasks uses the second singleton, and that, just as expected, > causes a lot of pain later. > > What is worse, I can't reproduce this behavior on my system (Windows 7, > Maven 3.0.4, JDK 1.7u5) with a test project, but it is reliably > reproduced on the system of one of the plugin' users (OpenSUSE 11.1, > maven 3.0.4, JDK 1.7u4) with his own project, by my test project builds > just fine there too. Means I am missing something in the test project, > but so far I do not know what I am missing. > > Questions, questions: > What could cause the Maven to create the second classloader during the > parallel build while the first classloader and singleton are definitely > still in use? > What kind of even more logging could be added to the plugin or to the > SqlJet library that can provide some additional insight of what is going > on? > What kind of debugging could be used on Maven parallel build? > What should I have asked besides the questions above? > > Best regards, > Oleg. > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org test -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven and parallel execution: fundamentally borked, right?
Hi Parallel execution works fine, but you need to update the version of maven-compiler-plugin to the latest version 2.5.1. You are being bitten by a bug in that plugin: http://jira.codehaus.org/browse/MCOMPILER-170 On 2012-07-20 22:43, Laird Nelson wrote: > I have never gotten the -T option to Maven to work. > > On a simple jar project that gets scheduled, periodically the compiler will > say things like this: > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-compiler-plugin:2.4:compile > (default-compile) on project com-foobar-api: Compilation failure: > Compilation failure: > [ERROR] > /Users/ljnelson/Projects/foobar/com-foobar-api/src/main/java/com/foobar/api/FrobnicationManager.java:[1,0] > class, interface, or enum expected > [ERROR] > /Users/ljnelson/Projects/foobar/com-foobar-api/src/main/java/com/foobar/api/FrobnicationManager.java:[5,0] > class, interface, or enum expected > [ERROR] -> [Help 1] > > ...even though in serial mode this class compiles fine (and indeed is > syntactically valid). > > In other cases it will complain about how it cannot load, e.g., > java.util.LinkedHashMap, even though--again--in serial mode this class is > loaded just fine. > > I am using Maven 3.0.3 on a Mac with four cores with -T 2 as my parallel > option in a large multi-module project. > > I assume that the parallel feature of Maven is in a pre-alpha state? Just > trying to see what the status is. > > Best, > Laird > -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: problem in installing/running maven
Hi Please run the command SET in a command window and paste the relevant parts here, i.e. M2_HOME, M2, JAVA_HOME and PATH. On 2012-07-17 22:01, rahul bhalla wrote: > hi > I new to maven project and first time i to runand install maven > I followed the following steps which instruct by apache maven > >1. Add the M2_HOME environment variable by opening up the system >properties (WinKey + Pause), selecting the "Advanced" tab, and the >"Environment Variables" button, then adding the M2_HOME variable in the >user variables with the value *C:\Program Files\apache-maven-3.0.4* >2. In the same dialog, add the M2 environment variable in the user >variables with the value %M2_HOME%\bin. >3. In the same dialog, update/create the Path environment variable in >the user variables and prepend the value %M2% to add Maven available in >the command line. >4. In the same dialog, make JAVA_HOME in user variables with the > value C:\Program >Files\Java\jdk1.6.0_21 and that %JAVA_HOME%\bin is in your Path environment >variable. >5. Open a *new* command prompt (Winkey + R then type cmd) and run mvn >--version to verify that it is correctly installed. > > *C:\Users\sahil>mvn --version* > 'mvn' is not recognized as an internal or external command, > operable program or batch file > > if the directory is changes to* C:\Program Files\apache-maven-3.0.4\bin>* > then it runs . > > now please tell me what is problem when i try to issue a command from * > C:\Users\sahil>* directory > -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: war overlays file merging
On 2012-06-28 21:06, chad.da...@emc.com wrote: > >>> Is it possible to have a merge of files that exist in both wars? >> >> I'm not quite sure how that would work. You'd have to write pretty >> smart code to handle the various types of files and merges which are >> possible. >> > > How do people manage source files that are additive between overlay wars > then? For instance, I'm doing an overlay of a struts application. They both > have a struts.properties file. It seems that if I change something in the > base war's properties file, I'll have to remember to move it up to the second > one too . . . It seems that it would be nice for these to be additive . . . > but maybe I'm not thinking of this correctly. Maybe there's no good solution > here, or maybe I'm misusing overlays. Hi, Unfortunately that is the way it currently works. There is an open issue for merging web.xml files for overlays here: http://jira.codehaus.org/browse/MWAR-100 -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Site Plugin 3 3.1 Released
The Maven team is pleased to announce the release of the Maven Site Plugin 3,
version 3.1
The Maven Site Plugin is a plugin that generates a site for the current project.
http://maven.apache.org/plugins/maven-site-plugin
You should specify the version in your project's plugin configuration:
org.apache.maven.plugins
maven-site-plugin
3.1
Release Notes - Maven Site Plugin 3 - Version 3.1
Bug
* [MSITE-638] site.xml parameter and template variables not documented
* [MSITE-633] Doco: reference to ${currentVersion} should be
${currentStableVersion} in creating-content.html#Filtering
* [MSITE-624] Usage page has incorrect information on the id used by
site:stage-deploy
* [MSITE-621] empty outputDirectory causes mvn clean to delete whole tree
* [MSITE-620] Fix documentation of attach-descriptor according to Maven3
Compatibility Notes
* [MSITE-610] No doc for reportPlugins in main goal docs
* [MSITE-609] site:deploy is broken
* [MSITE-607] no documentation for breadcrumbs in the doc of site.xml
* [MSITE-603] ClassNotFoundException on site:site when validating XML input
documents
* [MSITE-602] The staged site is deployed to the wrong place
* [MSITE-600] site plugin 3.0 does not permit a child to fully override parent
site deployment URL
* [MSITE-549] Not possible to easily customise footer
* [MSITE-402] Execution order of report plugins is arbitrary if inheritance is
involved
New Feature
* [MSITE-582] Make it possible to remove breadcrumbs in child projects again
Task
* [MSITE-641] Require Maven 2.2.1
* [MSITE-637] Upgrade to doxia-sitetools-1.3
* [MSITE-636] Upgrade to doxia-1.3
* [MSITE-627] Upgrade to reporting-exec 1.0.2
* [MSITE-625] Please add an 'archive' parameter to the 'jar' goal of the
'maven-site-plugin'.
Enjoy,
-The Maven team
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Site Plugin 2 2.4 Released
The Maven team is pleased to announce the release of the Maven Site Plugin 2, version 2.4 The Maven Site Plugin is a plugin that generates a site for the current project. http://maven.apache.org/plugins/maven-site-plugin-2.4 You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-site-plugin 2.4 Release Notes - Maven Site Plugin 2 - Version 2.4 Bug * [MSITE-600] site plugin 3.0 does not permit a child to fully override parent site deployment URL * [MSITE-593] Correction in the french localization * [MSITE-589] Invalid image assignation in html * [MSITE-585] site-deploy: empty deploy protocol when properties are used Improvement * [MSITE-541] add "skip" option for site:deploy New Feature * [MSITE-582] Make it possible to remove breadcrumbs in child projects again * [MSITE-367] add skip parameter for multimodule project Task * [MSITE-637] Upgrade to doxia-sitetools-1.3 * [MSITE-636] Upgrade to doxia-1.3 Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to add additional info to the MANIFEST.MF
cedeploy.zip > [INFO] > [INFO] <<< servicedeploy-plugin:0.0.1-SNAPSHOT:run (run-servicedeploy) @ > CDIPubSubMgmtMed <<< > [INFO] > [INFO] --- servicedeploy-plugin:0.0.1-SNAPSHOT:run (run-servicedeploy) @ > CDIPubSubMgmtMed --- > > initialize: > > serviceDeploy: > [echo] *** Running serviceDeploy... *** > [mkdir] Created dir: > C:\Workspace\WID\build\target\CDIPubSubMgmtMed\servicedeploy > [exec] The workbench is starting in > C:\Workspace\WID\build\target\CDIPubSubMgmtMed\servicedeploy\136e57e327a. > [exec] The workspace is initializing. > [exec] CDIPubSubMgmtMed-servicedeploy.zip was successfully imported > into the workspace. > [exec] The CDIPubSubMgmtMedApp project is being created. > [exec] The CDIPubSubMgmtMedWeb project is being created. > [exec] The CDIPubSubMgmtMed project is building. > [exec] CDIPubSubMgmtMed is being validated. > [exec] > [exec] The following 3 warning messages were reported during > deployment: > [exec] > [exec] Severity: [warning] > [exec] Description: CWSCA8095W: Unable to find class > com.ibm.ws.sib.api.jmsra.JmsJcaManagedConnectionFactory, please make sure > the classpath is properly set up. > [exec] Resource: ClientInfoEventPublishImport.import > [exec] Location: > [exec] > [exec] Severity: [warning] > [exec] Description: XSD: There is no xmlns declaration for namespace > 'http://www.nbfg.ca/ClientServices/InitiatePublishEvent' > [exec] Resource: MemberEventNotification.xsd > [exec] Location: 1 > [exec] > [exec] Severity: [warning] > [exec] Description: CWZMU0044E: The fail terminal of the > manageIndividualEvent : CDIServicePartner callout response primitive is not > connected. > [exec] Resource: CDIPubSubMgmtMed.medflow > [exec] Location: > [exec] > [exec] > [exec] The > C:\Workspace\WID\CDIPubSubMgmtMed\..\build\target\CDIPubSubMgmtMed\CDIPubSubMgmtMed-0.0.1-SNAPSHOT.ear > application is being exported. > [exec] Deployment has completed. > [INFO] > [INFO] --- maven-install-plugin:2.3.1:install (default-install) @ > CDIPubSubMgmtMed --- > [INFO] Installing > C:\Workspace\WID\CDIPubSubMgmtMed\..\build\target\CDIPubSubMgmtMed\CDIPubSubMgmtMed.jar > to > C:\Users\Administrator\.m2\repository\com\nbfg\max\wesb\CDIPubSubMgmtMed\0.0.1-SNAPSHOT\CDIPubSubMgmtMed-0.0.1-SNAPSHOT.jar > [INFO] Installing C:\Workspace\WID\CDIPubSubMgmtMed\pom.xml to > C:\Users\Administrator\.m2\repository\com\nbfg\max\wesb\CDIPubSubMgmtMed\0.0.1-SNAPSHOT\CDIPubSubMgmtMed-0.0.1-SNAPSHOT.pom > [INFO] Installing > C:\Workspace\WID\CDIPubSubMgmtMed\..\build\target\CDIPubSubMgmtMed\CDIPubSubMgmtMed-0.0.1-SNAPSHOT.ear > to > C:\Users\Administrator\.m2\repository\com\nbfg\max\wesb\CDIPubSubMgmtMed\0.0.1-SNAPSHOT\CDIPubSubMgmtMed-0.0.1-SNAPSHOT-App.ear > [INFO] > > [INFO] BUILD SUCCESS > [INFO] > > [INFO] Total time: 37.667s > [INFO] Finished at: Tue Apr 24 13:55:47 EDT 2012 > [INFO] Final Memory: 43M/512M > [INFO] > > > > > > -- > View this message in context: > http://maven.40175.n5.nabble.com/How-to-add-additional-info-to-the-MANIFEST-MF-tp5662221p5662830.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Incorrectly generated URLs in pom's using maven release plugin
On 2012-04-23 16:48, Lewis John Mcgibbney wrote: > Hi, Hi Lewis > When pushing out a release candidate for a VOTE, it was brought to my > attention that all generated module pom's contain incorrect URLs. I've > attached a brief description of what is wrong below with the link to the > staged repos here [0]. The release plugin is version 2.2.2 > > There are some wrong urls in the pom.xml files, namely in the scm section. > (I am not sure what impact of this is). It is about: > -the pom.xml in the project root --> seems incorrect. Not sure what happened to this one... > -the sources-dist/pom.xml --> like above, plus: url, connection and > developerConnection have 'trunk' postfixed. > -the subprojects (store implementations) pom.xml --> like above. This is because the SCM URLs that you have in your subprojects in trunk are wrong. They are currently pointing to http://svn.apache.org/viewvc/gora/trunk/ when they should be pointing to http://svn.apache.org/viewvc/gora/trunk// > My cmd's to create the staged tag was > > mvn release:clean release:prepare -P apache -DautoVersionSubmodules=true > > mvn release:perform -P apache > > 1) WIll these characteristics have any relative effect on the atrifacts? > 2) Is there any mechanism I can use to prevent this happening? If it is > trivial then I will more than likely spin another RC. > > Thank you in advance for any help. > > Lewis > > [0] https://repository.apache.org/content/repositories/orgapachegora-074/ > -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Doxia Sitetools 1.3 Released
The Doxia Sitetools team is pleased to announce the doxia-sitetools-1.3 release! Doxia Sitetools generates sites, consisting of static and dynamic content that was generated by Doxia. http://maven.apache.org/doxia/doxia-sitetools/ Release Notes - Maven Doxia Sitetools - Version 1.3 ** Bug * [DOXIASITETOOLS-54] - site.xml should also have attribute for all elements that have attributes * [DOXIASITETOOLS-59] - Using a relative path to an image in a generates a wrong "src" value for HTML tag * [DOXIASITETOOLS-65] - footer declared in the site.xml is not inherited in multi-module sites * [DOXIASITETOOLS-70] - Html title of generated pages does not include project name ** Improvement * [DOXIASITETOOLS-60] - Useless error message "error in opening zip file" in DefaultSiteRenderer.createContextForSkin() * [DOXIASITETOOLS-62] - improve breadcrumbs inheritance: if child defines an item already in parent, remove every breadcrumb item from parent after it * [DOXIASITETOOLS-63] - Make publish date configurable * [DOXIASITETOOLS-64] - Change style for menuitems to recognize the ones with a long name * [DOXIASITETOOLS-66] - Add Velocity Toolmanager support ** New Feature * [DOXIASITETOOLS-71] - Add the version of doxia-site-renderer that is used to the generated site * [DOXIASITETOOLS-72] - Allow declaring Google AdSense in site.xml ** Task * [DOXIASITETOOLS-73] - Update to Doxia base 1.3 Have fun! -Doxia Sitetools team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Doxia base 1.3 Released
The Maven team is pleased to announce the release of the Maven Doxia base, version 1.3 Doxia is a content generation framework that provides powerful techniques for generating static and dynamic content, supporting a variety of markup languages. http://maven.apache.org/doxia/doxia/ Release Notes - Maven Doxia - Version 1.3 ** Bug * [DOXIA-430] - FO: empty lines are not preserved in verbatim text * [DOXIA-433] - Regression: Unicode characters not rendered in table cells * [DOXIA-437] - SWF macro generates HTML tags for params without closing sign * [DOXIA-444] - Doc for doxia docbook doesn't warn user that it's not in the site plugin by default * [DOXIA-446] - XhtmlBaseSink: problems with xdoc source attributes * [DOXIA-448] - Div class attribute replicated to nested h2 element ** Improvement * [DOXIA-451] - Tweak Doxia Markdown module HTML to better match ** New Feature * [DOXIA-387] - Add RandomAccessSink * [DOXIA-426] - Markdown module ** Task * [DOXIA-465] - Move doxia-book and doxia-maven-plugin to Doxia Tools Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Need to pass munge directives to 'mvn site:site'
On 2012-04-14 02:08, Eugene Koontz wrote: > Hi, > I'm trying to debug an error in running 'mvn site:site' within the > Apache Giraph project's top-level directory. The pom.xml is here: > > https://github.com/apache/giraph/blob/trunk/pom.xml > > Note that there is a default profile, hadoop_0.20.203. This profile has > the munge symbols HADOOP_NON_SASL_RPC,HADOOP_NON_INTERVERSIONED_RPC > which are used control conditional compilation. This works fine for some > goals, like "mvn test" and "mvn verify". However, when I try to do "mvn > site:site" it fails due to a Java compile error: > > [ERROR] COMPILATION ERROR : > [INFO] - > [ERROR] > /home/ec2-user/giraph/src/main/java/org/apache/giraph/comm/BasicRPCCommunications.java:[66,28] > cannot find symbol > symbol : class ProtocolSignature > location: package org.apache.hadoop.ipc > > This compile error would be avoided if the munge symbols mentioned above > were employed (as they are with "test" and "verify"). So the problem > seems to be to get "mvn site:site" to use munge. > > What I need to do to the pom.xml to make this happen? Please also help > me understand what the difference is between "mvn compile" and "mvn > compiler:compile" - the former succeeds, the latter fails due to the > same compilation error. mvn compile invokes a lifecycle phase mvn compiler:compile invokes a goal in the compiler plugin > Perhaps "mvn site:site" is having a problem because it is invoking "mvn > compiler:compile" rather than "mvn compile"? (mvn -X site:site seems to > suggest so). mvn site:site invokes a goal on the site plugin mvn site invokes a lifecycle phase Try the latter and see if it works for you. Read more about phases and goals here: http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html > -Eugene > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Reporting Executor 1.0.2 Released
The Maven team is pleased to announce the release of the Maven Reporting Executor, version 1.0.2 Classes to manage report plugin executions with Maven 3. http://maven.apache.org/shared/maven-reporting-exec You should specify the version in your project's dependency configuration: org.apache.maven.shared maven-reporting-exec 1.0.2 Release Notes - Maven Reporting Executor - Version 1.0.2 Bug * [MSHARED-219] Maven3 LinkageError in maven report Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Issue with maven-plugin-plugin: For two artifacts which have the same groupId, goalPrefix is not resolved correctly.
Hi First try the latest version of maven-plugin-plugin, which is 2.9, to see if that solves your issue. On 2012-03-12 22:56, Dhawan Gayash wrote: > Hi, > > I am trying to write two plugins with the same groupId and goal but > different artifactId. For example. > > com.foo.bar.myOne-maven-plugin & com.foo.bar.myTwo-maven-plugin > > In both these plugins I would like to configure goalPrefixes as "myone" > and "mytwo". I am using maven-plugin-plugin for doing this with version 2.3 > > When I use mvn myone:<> it works fine. However when I use mvn > mytwo:<> it still executes the myone plugin. > > When I checked the depot location for how these plugins have been > provisioned I find the maven-metadata-local.xml file to have these configs. > > > |$/> cd /usr/local/.m2/repositories/3.0/com/foo/bar/ > $/> cat maven-metadata-local.xml > > > > > > My First Plugin > myone > myOne-maven-plugin > > > My Second Plugin > mytwo > myOne-maven-plugin > > > | > > This is a bug in maven-plugin-plugin version 2.3. Has this issue been > resolved or should I file this bug in JIRA. > > Steps to reproduce the bug: > > 1.) Take two artifacts with same groupId. > 2.) Configure goalPrefix by using maven-plugin-plugin. For both the plugins > > > > maven-plugin-plugin > 2.3 > > myone > > > > > 3.) Provision these plugins into your local repo. > 4.) Execute the plugins using goalPrefix. And for further investigation > please check the maven-metadata-local.xml > > > Thanks, > Dhawan > > -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Clirr Maven Plugin 2.4 Released
The Mojo team is pleased to announce the clirr-maven-plugin-2.4 release! Clirr is a tool that checks Java libraries for binary and source compatibility with older releases. Basically you give it two sets of jar files and Clirr dumps out a list of changes in the public API. The clirr-maven-plugin can be configured to break the build, if it detects incompatible api changes. In a continuous integration process, the clirr-maven-plugin can automatically prevent accidental introduction of binary or source compatibility problems. Additionally, the plugin can generate a report as part of the generated site. http://mojo.codehaus.org/clirr-maven-plugin/ To get this update, simply specify the version in your project's plugin configuration: org.codehaus.mojo clirr-maven-plugin 2.4 Release Notes Fixed Bugs: o Plugin does not support "maven-plugin" packaging/type Issue: MCLIRR-39. o ClirrReport throws java.lang.NegativeArraySizeException Issue: MCLIRR-37. o AbstractClirrMojo.reportDiffs crashes with ArrayIndexOutOfBoundsException while handling CheckerException Issue: MCLIRR-36. o Invalid xref link generated for added inner class Issue: MCLIRR-18. Changes: o provide german resource bundle Issue: MCLIRR-45. o Add Swedish resource bundle Issue: MCLIRR-44. o Add russian resource bundle Issue: MCLIRR-43. o Add dutch resource bundle Issue: MCLIRR-42. Have fun! -The Mojo team -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: The "perfect" reporting tool?
seem to get developed any >>> more. And there is not way to support Emma in it either. >> What does your pom look like? And what version of Maven, site/findbugs/... >> plugins do you use? >> >> On my system I'm using a corporate parent pom containing a couple of >> profiles that, when activated, add Findbugs, Checkstyle and/or PMD reports >> to the generated website. Works pretty fine. >> >> >> Regards >> >> Thorsten > > -- > Oracle <http://www.oracle.com> > Lucas Persson | Principal Member of Technical Staff > Phone: +4684773644 | | | Mobile: +46730946656 > > Oracle Communications Platform > ORACLE Sweden | Söder Mälarstrand 29, 6 tr | 118 25 Stockholm > > Oracle Svenska AB, Kronborgsgränd 17, S-164 28 KISTA, reg.no. 556254-6746 > Green Oracle <http://www.oracle.com/commitment> Oracle is committed to > developing practices and products that help protect the environment -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Checkstyle Plugin 2.9.1 Released
The Maven team is pleased to announce the release of the Maven Checkstyle Plugin, version 2.9.1 Generates a report on violations of code style and optionally fails the build if violations are detected. http://maven.apache.org/plugins/maven-checkstyle-plugin You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-checkstyle-plugin 2.9.1 Release Notes - Maven Checkstyle Plugin - Version 2.9.1 Bug * [MCHECKSTYLE-173] Embedded error: Cannot set property 'charset' in module Checker to 'UTF-8,UTF-8': UTF-8,UTF-8 Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: how to copy resources? how to create a zip file with the app jar, the dependent jars and the resources?
Hi You might also want to take a look at appassembler-maven-plugin http://mojo.codehaus.org/appassembler/appassembler-maven-plugin/ On Thu, Feb 23, 2012 at 7:40 PM, Maria Cristina wrote: > Sorry for the duplicate post. I am new to Maven and need some help. This > what I currently have: > > 1. > my project's src/main/resources contains two packages: > the default package contains two files jndi.properties and log4j.properties > another package named company.it.app.i18n contains one file called > MessageResourceBundle.properties > > 2. > my pom includes: > > > > org.apache.maven.plugins > maven-jar-plugin > 2.4 > > > > true > company.it.app.MyApp > > > config/ > > > > > > > > > 3. > my class references the resource bundle as follows: > private static final String BUNDLE_NAME = > "company.it.app.i18n.MessageResourceBundle"; > > 4. > inside the generated executable jar file app-1.0.jar contains: > > (i) > in the manifest the following class path and main class: > Class-Path: config/ log4j-1.2.7.jar (and other dependent jars) > Main-Class: company.it.app.MyApp > > (ii) > config/jndi.properties > config/log4j.properties > > (iii) > company\it\app\i18n\MessageResourceBundle.properties > > my IDE results is successful: > clean and build works and the JUnit tests run successfully > > then I do several manual steps > copy app-1.0.jar to a my destination folder named testapp > remove jndi.properties and log4j.properties from app-1.0.jar and copy to a > folder named config in folder testapp > copy log4j-1.2.7.jar (and other dependent jars) to the folder testapp > > my command line result is successful: > java -jar app-1.0.jar > > I'd like to make some changes to achieve the following: > > because I'd like to automate my manual steps, I'd like to use Maven to > automate the creation of a zip file containing: > > app-1.0.jar > lib/log4j-1.2.7.jar (and other dependent jars) > config/jndi.properties > config/log4j.properties > > I've been trying and I don't know how to copy the resources to the config > folder without breaking the JUnit tests. Is it possible, if so how? How > would I create the zip with the structure? > > Thanks in advance. -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven PMD Plugin 2.7.1 Released
The Maven team is pleased to announce the release of the Maven PMD Plugin, version 2.7.1 A Maven plugin for the PMD toolkit, that produces a report on both code rule violations and detected copy and paste fragments, as well as being able to fail the build based on these metrics. http://maven.apache.org/plugins/maven-pmd-plugin You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-pmd-plugin 2.7.1 Release Notes - Maven PMD Plugin - Version 2.7.1 Bug * [MPMD-142] PMD Report for maven site fails with ClassCastException Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Reporting Implementation 2.2 Released
The Maven team is pleased to announce the release of the Maven Reporting Implementation, version 2.2 Abstract classes to manage report generation. http://maven.apache.org/shared/maven-reporting-impl You should specify the version in your project's dependency configuration: org.apache.maven.shared maven-reporting-impl 2.2 Release Notes - Maven Reporting Implementation - Version 2.2 Bug * [MSHARED-105] StringIndexOutOfBoundsException in AbstractMavenReportRenderer.applyPattern Improvement * [MSHARED-222] Update the dependency on commons-validator * [MSHARED-204] AbstractMavenReport should check isExternalReport() before trying to output a Doxia document Task * [MSHARED-159] remove [WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink instance and no SinkFactory available. Please update this plugin. Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Checkstyle Plugin 2.9 Released
The Maven team is pleased to announce the release of the Maven Checkstyle Plugin, version 2.9 Generates a report on violations of code style and optionally fails the build if violations are detected. http://maven.apache.org/plugins/maven-checkstyle-plugin You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-checkstyle-plugin 2.9 Release Notes - Maven Checkstyle Plugin - Version 2.9 Bug * [MCHECKSTYLE-170] Test errors and failures on Windows * [MCHECKSTYLE-168] checkstyle-aggregate give a wrong file count * [MCHECKSTYLE-167] Unconfigured checkstyle plugin duplicates entries in aggregated report * [MCHECKSTYLE-164] Multimodule Configuration example does not show how to configure build-tools pom * [MCHECKSTYLE-152] encoding property in maven plugin is never set correctly to charset property of the checkstyle itself. * [MCHECKSTYLE-146] mvn checkstyle:checkstyle KO, Unable to find the mojo, org/apache/maven/doxia/logging/Log * [MCHECKSTYLE-145] maven-checkstyle-plugin 2.6 SinkFactory WARNING Improvement * [MCHECKSTYLE-165] Upgrade to checkstyle 5.5 Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to turn off project assembly generation
Hi Tim Maven does not produce such assemblies by default. Somewhere in your project's POM hierarchy you should find a configuration for maven-assembly-plugin. To find it you can use this command: mvn help:effective-pom On 2012-02-10 20:07, Tim Pizey wrote: > Hi, > > I have seen that the default (in maven 2.2) is now to generate a series of > -project.zip, -project.tar.bz2, -project.tar.gz files. > > I have read the site but cannot figure out how to configure my pom to > only produce the > .jar outputs. > > thanks in advance > Tim > > -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven PMD Plugin 2.7 Released
The Maven team is pleased to announce the release of the Maven PMD Plugin, version 2.7 A Maven plugin for the PMD toolkit, that produces a report on both code rule violations and detected copy and paste fragments, as well as being able to fail the build based on these metrics. http://maven.apache.org/plugins/maven-pmd-plugin You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-pmd-plugin 2.7 Release Notes - Maven PMD Plugin - Version 2.7 Improvement * [MPMD-141] Add Italian Resource Bundle * [MPMD-138] Use modello to generate models to read pmd and cpd files * [MPMD-135] Update to use and require Java 5 * [MPMD-122] Add @threadSafe support for maven3 New Feature * [MPMD-137] Add French translation for CPD * [MPMD-136] Add Dutch translation Task * [MPMD-140] Require Maven 2.2.1 * [MPMD-134] Update to PMD 4.3 -- allow target to java 7 Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: MVN Site doesn't bring Project Modules structure properly
That'd be the Javadoc Plugin: http://maven.apache.org/plugins/maven-javadoc-plugin/ On 2012-01-16 22:36, Daivish Shah wrote: > Thanks Dennis for your quick reply on this... > > > And how to associate JAVADOC with this MVN submodule project ? As all > submodules has JAVADOC and i want to associate those with MVN SITE, How can > i do that ? > > Thanks. > > On Mon, Jan 16, 2012 at 12:18 PM, Dennis Lundberg wrote: > >> >> http://maven.apache.org/plugins/maven-site-plugin/faq.html#Why_dont_the_links_between_parent_and_child_modules_work_when_I_run_mvn_site >> >> On 2012-01-16 21:04, Daivish Shah wrote: >>> I have project like this. >>> >>> MainProject >>> >>> SubProject1 >>> >>> --- SubProject2 >>> >>> SubProject3 >>> >>> >>> And i am trying to execute MVN SITE command. I am able to setup all other >>> section in Project Information Section. >>> >>> All sub module's POM.XML have SubProject1 entry for this, that's why i am >>> able to see that module name in Project Modules Section. >>> >>> But when i am trying to click the submodule link it's looking for HTML >> file >>> under PARENT PROJECT so something like this. >>> >>> MainProject/target/site/SubModule1/index.html >>> >>> Actually that location i don't find anything. So what is the correct >>> approach for MultiModule structure SITE creating ? >>> Looking for some good multi module(SITE) material or website to read on >>> this and which can fix my issue. Or if you have guys have any POM.XML to >>> use it please post it here. >>> >> >> >> -- >> Dennis Lundberg >> >> - >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> >> > -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven EAR Plugin 2.7 Released
The Maven team is pleased to announce the release of the Maven EAR Plugin, version 2.7 The most noteworthy in this release is the support for skinny WAR files. It is one of the most voted on issues in our JIRA with 50 votes. We would love to hear your feedback on this new feature. The plugin generates a J2EE Enterprise Archive (EAR) file. http://maven.apache.org/plugins/maven-ear-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-ear-plugin 2.7 Release Notes - Maven EAR Plugin - Version 2.7 Improvement * [MEAR-60] Improve support for skinny WAR files New Feature * [MEAR-87] Allow exclusion of artifacts when building the ear file. Task * [MEAR-140] HTML Anchors on page "EAR Modules" defect * [MEAR-48] Remove the deprecated resourcesDir parameter Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: MVN Site doesn't bring Project Modules structure properly
http://maven.apache.org/plugins/maven-site-plugin/faq.html#Why_dont_the_links_between_parent_and_child_modules_work_when_I_run_mvn_site On 2012-01-16 21:04, Daivish Shah wrote: > I have project like this. > > MainProject > > SubProject1 > > --- SubProject2 > > SubProject3 > > > And i am trying to execute MVN SITE command. I am able to setup all other > section in Project Information Section. > > All sub module's POM.XML have SubProject1 entry for this, that's why i am > able to see that module name in Project Modules Section. > > But when i am trying to click the submodule link it's looking for HTML file > under PARENT PROJECT so something like this. > > MainProject/target/site/SubModule1/index.html > > Actually that location i don't find anything. So what is the correct > approach for MultiModule structure SITE creating ? > Looking for some good multi module(SITE) material or website to read on > this and which can fix my issue. Or if you have guys have any POM.XML to > use it please post it here. > -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: mavem-war-plugin packagingExcludes regex not working
On 2012-01-12 14:57, mschipperheyn wrote: > Hi, > > I'm trying to exclude javascript source files from war packaging process and > include minified files that end with -min.js > > files are named as such > /msa-network/msa-network.js > /msa-network/msa-network-min.js > > etc > > On regex planet, http://www.regexplanet.com/, this regular expression does > the trick: > (? > However, in the maven-war-plugin I use this in packagingExcludes and it > doesn't work. The files are still included > > <packagingExcludes> > > I've tried other variations. Nothing works, although I did confirm that > regular expressions work in packagingExcludes. > I'm using maven-war-plugin 2.2-SNAPSHOT > > Any suggestions? > > Marc > > > -- > View this message in context: > http://maven.40175.n5.nabble.com/mavem-war-plugin-packagingExcludes-regex-not-working-tp5139981p5139981.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Error in POM.XML
Hi If you need a proxy to access the internet, check that it is properly configured in the new version of STS. On 2011-12-26 12:48, zed420 wrote: > Hi All > I'm seeing this error in my POM.XML file since I've updated my STS 2.7.1 to > 2.8.1. Has anyone experienced this error ??? Anyone know the solution ??? > > Failure to transfer com.thoughtworks.xstream:xstream:jar:1.3.1 from > http://repo1.maven.org/maven2 was cached in the local repository, resolution > will not be reattempted until the update interval of central has elapsed or > updates are forced. Original error: Could not transfer artifact > com.thoughtworks.xstream:xstream:jar:1.3.1 from/to central > (http://repo1.maven.org/maven2): No response received after 6 > > Many thanks > Zed420 > > -- > View this message in context: > http://maven.40175.n5.nabble.com/Error-in-POM-XML-tp5101426p5101426.html > Sent from the Maven - Users mailing list archive at Nabble.com. -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Solve my exception for mvn installtion
Hi You need to use Java 5 or newer to run the latest versions of Maven. On 2011-12-15 09:04, ashishmemod wrote: > > Hi friends, > > i found these types of error or exceptions. > > please help me ro solve it. > > > C:\Users\Ashish>mvn install > Exception in thread "main" java.lang.UnsupportedClassVersionError: > org/apache/ma > ven/cli/MavenCli (Unsupported major.minor version 49.0) > at java.lang.ClassLoader.defineClass0(Native Method) > at java.lang.ClassLoader.defineClass(ClassLoader.java:539) > at > java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123) > at java.net.URLClassLoader.defineClass(URLClassLoader.java:251) > at java.net.URLClassLoader.access$100(URLClassLoader.java:55) > at java.net.URLClassLoader$1.run(URLClassLoader.java:194) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:187) > at > org.codehaus.plexus.classworlds.realm.ClassRealm.loadClassFromSelf(ClassRealm.java:386) > at > org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:42) > at > org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:244) > at > org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:230) > at > org.codehaus.plexus.classworlds.launcher.Launcher.getMainClass(Launcher.java:145) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:267) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) > at > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) > at > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) > > > -- > View this message in context: > http://maven.40175.n5.nabble.com/Solve-my-exception-for-mvn-installtion-tp5076811p5076811.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > ----- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: newbie issue in preparing release: svn tag dies with "Unable to open an ra_local session to URL"
Hi The developerConnection should point to the svn server - not the svn checkout. On Monday, November 7, 2011, revengeofthepencil < revengeofthepen...@gmail.com> wrote: > Hello all, > > I'm a little new to cutting a release with Maven and I'm having a terrible > time getting it to work. Everything looks good until I get to the svn tag > step, at which point it always fails. Here's the error: > > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 17.274s > [INFO] Finished at: Mon Nov 07 10:57:30 PST 2011 > [INFO] Final Memory: 5M/81M > [INFO] > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-release-plugin:2.0-beta-9:prepare > (default-cli) on project testproject: Unable to tag SCM > [ERROR] Provider message: > [ERROR] The svn tag command failed. > [ERROR] Command output: > [ERROR] svn: Unable to open an ra_local session to URL > [ERROR] svn: Unable to open repository > 'file:///Users/ignatiusjreilly/release/testproject' > [ERROR] -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal org.apache.maven.plugins:maven-release-plugin:2.0-beta-9:prepare > (default-cli) on project testproject: Unable to tag SCM > Provider message: > The svn tag command failed. > Command output: > svn: Unable to open an ra_local session to URL > svn: Unable to open repository > 'file:///Users/ignatiusjreilly/release/testproject' > >at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213) >at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) >at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) >at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) >at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) >at > org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) >at > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) >at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) >at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) >at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) >at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) >at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) >at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) >at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >at java.lang.reflect.Method.invoke(Method.java:597) >at > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) >at > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) >at > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) >at > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) > Caused by: org.apache.maven.plugin.MojoFailureException: Unable to tag SCM > Provider message: > The svn tag command failed. > Command output: > svn: Unable to open an ra_local session to URL > svn: Unable to open repository > 'file:///Users/ignatiusjreilly/release/testproject' > > > I am certain that the path /Users/ignatiusjreilly/release/testproject is > valid and is part of an svn checkout. Here are the relevant portions of my > pom: > > > > > scm:svn:file:Users/ignatiusjreilly/release/testproject/trunk > > > > >org.apache.maven.plugins >maven-release-plugin >2.0-beta-9 > > > file:Users/ignatiusjreilly/release/testproject/tags > > > > Anyone who can spot what I'm doing wrong here will have my eternal > gratitude. > > Thanks, > Alex > > > -- > View this message in context: http://maven.40175.n5.nabble.com/newbie-issue-in-preparing-release-svn-tag-dies-with-Unable-to-open-an-ra-local-session-to-URL-tp4972156p4972156.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > -- Dennis Lundberg
Re: Unclear documentation "filter the deployment descriptor"
You can read more about filtering here: http://maven.apache.org/guides/getting-started/index.html#How_do_I_filter_resource_files I'll add a link to that page from the page you reference below. On 2011-10-12 19:43, Steve Cohen wrote: > This is one of the most useless bits of documentation I've ever seen. > > http://maven.apache.org/plugins/maven-ejb-plugin/examples/filter-deployment-descriptor.html > > > HOW would one "inject values into it during the build"? > WHEN in the build process would one do so? > WHY would one need to do so? > > An example is sorely needed. > > I am sorry for my tone but I have been beating my head against the wall > for a week trying to build something that sounds so simple until you try > it. This is only about the 1000th such issue I've stubbed my toe on. > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven archetype
Hi
Did you try this variant?
On 2011-10-03 17:59, Nalini Chavala wrote:
>
> Hi,
>
> I am trying to create a maven archetype and followed the link
>
> http://maven.apache.org/archetype/maven-archetype-plugin/
>
> http://code.google.com/p/jianwikis/wiki/HowToCreateMavenArchetypeFromProject
>
>
> I was able to create an archetype with default structure but I like to create
> a template with the artifact Id.
> Eg:
>Templeate-java
>Templeate-ejb
>
>
> I need to have a template with like
>
> Eg:
> Artificatid-java
> Artifactid-ejb
>
>
> I have specified the archetype-metadata.xml with "__artifactId__Client"
>
>
>
>name="${artifactId}-Client">
>
>
> src/main/java/sf/iasc
>
> **/*.java
> **/*.xml
>
>
>
> src/test/java
>
> **/*.xml
> **/*.java
>
>
>
>
>
>
>
>
>
>
> Please let me know how to resolve the issue.
>
> Thanks
>
>
--
Dennis Lundberg
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Insert a timestamp into an archetype?
Hi Bram
Thanks for your suggestion. My current approach is to use filtering to
insert the timestamp into the .java file.
The problem I am having is actually getting hold of the appropriate
value of a timestamp. It should reflect the point in time when my
archetype is used to generate a new project.
On 2011-09-30 22:03, Bram Patelski wrote:
> You could use filtering?
>
> On Fri, Sep 30, 2011 at 22:01, Dennis Lundberg wrote:
>
>> Hi
>>
>> I'm creating an archetype, with a bunch of files. In the .java files I
>> want to insert a timestamp. When I use the archetype to generate a new
>> project, the .java files should show when they were generated.
>>
>> Is this possible?
>>
>> I have tried inserting ${maven.build.timestamp} as the default value in
>> my archetype-metadata.xml file, but it doesn't seem to work.
>>
>> --
>> Dennis Lundberg
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>>
>
--
Dennis Lundberg
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Insert a timestamp into an archetype?
Hi
I'm creating an archetype, with a bunch of files. In the .java files I
want to insert a timestamp. When I use the archetype to generate a new
project, the .java files should show when they were generated.
Is this possible?
I have tried inserting ${maven.build.timestamp} as the default value in
my archetype-metadata.xml file, but it doesn't seem to work.
--
Dennis Lundberg
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: correct section for plugins-definitons
On 2011-09-28 18:18, codingplayer wrote:
> Hi everybody,
>
> I'm currently reworking my master pom to use the section
> as proposed.
>
> For me it is still unclear which parts of a plugin-definition need to be
> placed in which section? (pluginManagment, plugins, reporting)
>
> As i would interpret, the default config for a plugin should be placed into
> the section, for example with the maven-javadoc-plugin:
>
> 1. i would place this under :
>
>
> org.apache.maven.plugins
> maven-javadoc-plugin
> ${javadoc.plugin.version}
>
> ${java.source.version}
>
>
>
> deploy
>
> jar
>
>
>
>
>
> in order to automatically create a -javadoc.jar everytime the deploy phase
> is executed.
>
> 2. in the section, i would only place this:
>
>
> org.apache.maven.plugins
> maven-javadoc-plugin
>
>
> to enable the javadoc plugin for my project (the version and configuration
> would be taken from the section above).
>
> 3. also in the section, i would place:
>
>
> org.apache.maven.plugins
> maven-javadoc-plugin
>
> ${java.source.version}
> 128m
> 512m
> true
>
>
>
> for the site generation.
>
> Is this right?
That's exactly right!
> I also wonder, if those plugins only needed for the site generation, should
> be configured in the section as well?
>
> for example: the maven-jxr-plugin
>
> org.apache.maven.plugins
> maven-jxr-plugin
> ${jxr.plugin.version}
>
> true
>
>
>
It would have been good if this worked in the same way as for build
plugins. Unfortunately it doesn't. See
http://jira.codehaus.org/browse/MSITE-443 for more info on this.
>
> i would appreciate any help, or a link to the corresponding maven
> documentation, since everything i could find was not that helpful.
>
> br
> Roman
>
> --
> View this message in context:
> http://maven.40175.n5.nabble.com/correct-section-for-plugins-definitons-tp4849832p4849832.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
--
Dennis Lundberg
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Question about SCM and maven-release-plugin
On 2011-09-26 20:58, Laird Nelson wrote: > What should the scm element contain so that the maven-release-plugin will > work properly? > > I have seen people's projects have scm stanzas like this: > > > scm:svn:https://whatever.com/whatever/trunk > scm:svn:https://whatever.com/whatever/trunk > > > > ...and I've seen the same without the trunk: > > > scm:svn:https://whatever.com/whatever > scm:svn:https://whatever.com/whatever > > > > If one is using Subversion, should one append the branch/trunk name to the > scm element, or should one only specify the repository root? You should add trunk or branch + branch-name. > Thanks, > Laird > -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: mvn dependency tree not working
Hello again I'll try to explain it one more time. The dependency that you have specified in your POM does not exist. I'm not sure which dependency it is that you want. If it is "ehcache" you want, then your dependency should look like this: org.hibernate hibernate-ehcache 3.3.1.GA If it is "hibernate-core" you want, then your dependency should look like this: org.hibernate hibernate-core 3.3.1.GA You can browse the available Hibernate artifacts in the Central repository at this URL: http://repo1.maven.org/maven2/org/hibernate/ The reason that Maven Dependency Plugin cannot do it's job, and present the tree, is because the tree is broken. On 2011-09-21 18:38, kapila wrote: > Thanks but I have tried to see that with debug option X and U . Nothing I > could infer. But don't understand why I can't get dependency tree print. > > Pls help. > Sent from BlackBerry® on Airtel > > -Original Message- > From: Jörg Schaible [via Maven] > Date: Wed, 21 Sep 2011 09:32:21 > To: kapila > Subject: Re: mvn dependency tree not working > > > > kapilanarang wrote: > >> Thanks Dennis for reply. >> path in central is correct & in specific pom - its mentioned correctly. >> >> org.hibernate.ehcache >> ehcache >> 3.3.1.GA >> >> >> whereas its calling for path- >> org.hibernate.ehcache:hibernate-core:jar:3.3.1.GA >> what i feel is some1 (internal) has wrongly mentioned the path in one of >> the dependent jar's. I need to dig which jar is causing this issue. but >> unable to find the dependency jars' >> >> pls advice to find that? > > Start with -X option > > - Jörg > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > > > ___ > If you reply to this email, your message will be added to the discussion > below: > http://maven.40175.n5.nabble.com/mvn-dependency-tree-not-working-tp4822352p4827004.html > > To unsubscribe from mvn dependency tree not working, visit > http://maven.40175.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4822352&code=a2FwaWxhLmtvaGxpQGdtYWlsLmNvbXw0ODIyMzUyfDk2MjU3ODY3Ng== > > > -- > View this message in context: > http://maven.40175.n5.nabble.com/mvn-dependency-tree-not-working-tp4822352p4827017.html > Sent from the Maven - Users mailing list archive at Nabble.com. -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: mvn dependency tree not working
Hi No, it is not correct in your POM. You should have this org.hibernate On Wednesday, September 21, 2011, kapilanarang wrote: > Thanks Dennis for reply. > path in central is correct & in specific pom - its mentioned correctly. > >org.hibernate.ehcache >ehcache >3.3.1.GA > > > whereas its calling for path- > org.hibernate.ehcache:hibernate-core:jar:3.3.1.GA > what i feel is some1 (internal) has wrongly mentioned the path in one of the > dependent jar's. I need to dig which jar is causing this issue. but unable > to find the dependency jars' > > pls advice to find that? > > -- > View this message in context: http://maven.40175.n5.nabble.com/mvn-dependency-tree-not-working-tp4822352p4825431.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > -- Dennis Lundberg
Re: Not a valid plugin file: maven-taglib-plugin-1.4.2.jar
On 2011-09-20 21:31, Wayne Fay wrote: >> It is a Maven 1.0 build and supposedly has been working for >> quite some time. >> >> Does anyone recall this issue when working with Maven 1.0? > > No, but I haven't touched M1 in a very long time. You should seriously > just spend an hour +/- converting it to work with Maven2 or M3 rather > than debugging/fixing this old M1 build, IMO. I agree. You can get a jump start by using the convert goal of Maven One Plugin. It will convert most of your Maven 1 project.xml into a Maven 2 pom.xml. http://maven.apache.org/plugins/maven-one-plugin/ > > Wayne > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: mvn dependency tree not working
Hi On 2011-09-20 14:30, kapila wrote: > While building a sub-project where I am trying to find the jar dependency > showing up in compliation which i am not able to locate in code/pom. > Tried command ;- mvn dependency:tree > this doesnt show up the dependency tree > > this jar doesnt exist on nexus even, so i wanna see where is this defined in > pom or dependency jar is calling it. > > error is > > Downloaded: > http://IP:8081/nexus/content/groups/public-snapshots/abc/abc-web-utils/1.1-SNAPSHOT/maven-metadata.xml > (351 B at 6.0 KB/sec) > Downloading: > http://IP:8081/nexus/content/groups/public/org/hibernate/ehcache/hibernate-core/3.3.1.GA/hibernate-core-3.3.1.GA.pom > > [WARNING] The POM for org.hibernate.ehcache:hibernate-core:jar:3.3.1.GA is > missing, no dependency information available The message above says that it cannot find org.hibernate.ehcache:hibernate-core:3.3.1.GA in your Nexus repository. Looking at what is available in the Central repository it looks like you have used the wrong groupId in your POM. It should be "org.hibernate". The dependency can't do it's job if it cannot find all the dependencies for a given project. > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 6.065s > [INFO] Finished at: Tue Sep 20 16:29:32 IST 2011 > [INFO] Final Memory: 8M/1009M > [INFO] > > [ERROR] Failed to execute goal on project com.abc.data.web: Could not > resolve dependencies for project com.abc:com.abc.data.web:war:3.0.0.M1: > Could not find artifact org.hibernate.ehcache:hibernate-core:jar:3.3.1.GA in > abc (http://IP:8081/nexus/content/groups/public) -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException > > [kapila.narang@svn data-web]$ pwd > /home/kapilacvs/data-3.0/data-web/data-web > > have made entry in pom also - > > org.apache.maven.plugins > > maven-dependency-plugin > 2.3 > > > maven version i am using is /usr/local/apache-maven-3.0/bin/mvn > > i have tried to run same command- mvn dependency:analyze-only on its parent > pom its runs fine for other sub-projects. but give issue in this specific > project. Doesn't give any dependency graph at all build gives build failure. > > was trying to understand what harm can these make expect cleaner code- > > [WARNING] Used undeclared dependencies found: > [WARNING] Unused declared dependencies found: > > -- > View this message in context: > http://maven.40175.n5.nabble.com/mvn-dependency-tree-not-working-tp4822352p4822352.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] AspectJ Maven Plugin 1.4 Released
Hi, The Mojo team is pleased to announce the release of the AspectJ Maven Plugin version 1.4. Handles AspectJ usage within Maven. Functionality provided is: weaving of aspects (or existing aspects from libraries) with the test and/or main classes, weaving of pre-existing jars and ajdoc reporting. http://mojo.codehaus.org/aspectj-maven-plugin/ To get this update, simply specify the version in your project's plugin configuration: org.codehaus.mojo aspectj-maven-plugin 1.4 Release Notes ** Bug * [MASPECTJ-102] - NullPointerException when running under m2e 1.0 * [MASPECTJ-103] - Empty in cause error ** Improvement * [MASPECTJ-91] - Mark aspectj plugin as @threadSafe if possible * [MASPECTJ-95] - sourceDirectory and testSourceDirectory params are required * [MASPECTJ-96] - configurable option to skip execution * [MASPECTJ-100] - Add support resource bundles for the report ** New Feature * [MASPECTJ-9] - Add support for weaving classes in folders instead of jars ** Task * [MASPECTJ-104] - Update to AspectJ 1.6.11 * [MASPECTJ-105] - Upgrade minimum required Maven version to 2.2.0 Enjoy, The Mojo team. -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-site-plugin 3.0 deploy not working
repository/javax/servlet/servlet-api/2.5/servlet-api-2.5.jar > urls[20] = > file:/d:/chrism_iii/mavenrepository/org/apache/maven/doxia/doxia-decoration-model/1.2/doxia-decoration-model-1.2.jar > urls[21] = > file:/d:/chrism_iii/mavenrepository/org/apache/maven/doxia/doxia-site-renderer/1.2/doxia-site-renderer-1.2.jar > urls[22] = > file:/d:/chrism_iii/mavenrepository/org/codehaus/plexus/plexus-i18n/1.0-beta-7/plexus-i18n-1.0-beta-7.jar > urls[23] = > file:/d:/chrism_iii/mavenrepository/org/codehaus/plexus/plexus-velocity/1.1.8/plexus-velocity-1.1.8.jar > urls[24] = > file:/d:/chrism_iii/mavenrepository/org/apache/maven/shared/maven-doxia-tools/1.4/maven-doxia-tools-1.4.jar > urls[25] = > file:/d:/chrism_iii/mavenrepository/commons-io/commons-io/1.4/commons-io-1.4.jar > urls[26] = > file:/d:/chrism_iii/mavenrepository/org/codehaus/plexus/plexus-archiver/1.0/plexus-archiver-1.0.jar > urls[27] = > file:/d:/chrism_iii/mavenrepository/org/codehaus/plexus/plexus-io/1.0/plexus-io-1.0.jar > urls[28] = > file:/d:/chrism_iii/mavenrepository/org/mortbay/jetty/jetty/6.1.25/jetty-6.1.25.jar > urls[29] = > file:/d:/chrism_iii/mavenrepository/org/mortbay/jetty/jetty-util/6.1.25/jetty-util-6.1.25.jar > urls[30] = > file:/d:/chrism_iii/mavenrepository/org/mortbay/jetty/servlet-api/2.5-20081211/servlet-api-2.5-20081211.jar > [FATAL ERROR] Container realm = plexus.core > urls[0] = file:/c:/apache/maven-2.2.1/bin/../lib/maven-2.2.1-uber.jar > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] > org.codehaus.plexus.PlexusContainer.getContainerRealm()Lorg/codehaus/plexus/classworlds/realm/ClassRealm; > [INFO] > > [INFO] Trace > java.lang.NoSuchMethodError: > org.codehaus.plexus.PlexusContainer.getContainerRealm()Lorg/codehaus/plexus/classworlds/realm/ClassRealm; > at > org.apache.maven.plugins.site.AbstractDeployMojo.configureWagon(AbstractDeployMojo.java:687) > at > org.apache.maven.plugins.site.AbstractDeployMojo.deploy(AbstractDeployMojo.java:268) > at > org.apache.maven.plugins.site.AbstractDeployMojo.deployTo(AbstractDeployMojo.java:257) > at > org.apache.maven.plugins.site.AbstractDeployMojo.execute(AbstractDeployMojo.java:165) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) > at > org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > [INFO] > -------- > [INFO] Total time: 3 seconds > [INFO] Finished at: Tue Aug 09 12:28:36 CEST 2011 > [INFO] Final Memory: 14M/34M > [INFO] > > > For better readability I attach the xmls and output as textfile, I > hope this comes through the list. > > thanks in advance and best regards, > christian > > > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
