[VOTE] Final Release of Maven Reactor Plugin 1.1 (RETIRED)
Hi to all, after the vote for the retiring of the plugin has succeeded now the final release of the plugin. The vote is open for 72 hours. [ ] +1 Yes, it's about time [ ] -1 No, because... Kind regards Karl-Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[CANCLE] Re: [VOTE] Final Release of Maven Reactor Plugin 1.1 (RETIRED)
Canceled. Sorry...forget things to mentioned... On 3/30/14 5:05 PM, Karl Heinz Marbaise wrote: Hi to all, after the vote for the retiring of the plugin has succeeded now the final release of the plugin. The vote is open for 72 hours. [ ] +1 Yes, it's about time [ ] -1 No, because... Kind regards Karl-Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[RESULT] [VOTE] Maven Reactor Plugin - Final Release 1.1 (RETIRED) - Take 3
Hi to all, the vote has passed with the following result: +1 (binding): Hervé Boutemy, Stephen Connolly, Oliver Lamy Many thanks for the support. Kind regards Karl-Heinz Marbaise On 3/30/14 6:17 PM, Karl Heinz Marbaise wrote: Hi, We have solved only a single issue (the final retirement issue): http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11831&version=20210 Based on my mistake, the files are already on final ASF repository: http://repository.apache.org/content/groups/public/ http://repository.apache.org/content/groups/public/org/apache/maven/plugins/maven-reactor-plugin/1.1/maven-reactor-plugin-1.1-source-release.zip Source release checksum(s): maven-reactor-plugin-1.1-source-release.zip sha1: a05d38771ae05f1323e474f9562aea0f2dc59898 Staging site: http://maven.apache.org/plugins-archives/maven-reactor-plugin-LATEST/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Kind regards Karl-Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Enforcer plugin
Hi, it would be really nice having a test case which reproduces the wrong behaviour ... Kind regards Karl-Heinz Marbaise On 4/3/14 2:25 AM, Mark Eggers wrote: Folks, I've gotten my classifier artifact to build and install in our local repository. Specifying the classifier gets the appropriate artifact, and removing the classifier gets the [other] appropriate artifact. Now I'm a bit paranoid that the artifact with the classifier will leak out into other releases, so I thought I would write an enforcer rule. I thought that the following would work: org.mdeggers:*:*:*:*:DEBUG based on: http://maven.apache.org/enforcer/enforcer-rules/bannedDependencies.html While this certainly blocked the following dependency: org.mdeggers SampleBuild 1.5 war DEBUG with the message: Found Banned Dependency: org.mdeggers:SampleBuild:war:DEBUG:1.5 It also blocked the following dependency: org.mdeggers SampleBuild 1.5 war with the message: Found Banned Dependency: org.mdeggers:SampleBuild:war:1.5 This I did not expect. The messages are also a bit suspect in that they don't match the pattern given in the documentation. I looked on JIRA and found the following (based on another thread): http://jira.codehaus.org/browse/MENFORCER-74 http://jira.codehaus.org/browse/MENFORCER-75 http://jira.codehaus.org/browse/MENFORCER-72 These are all closed with a 'fixed' designation for release 1.3. I'm using version 1.3.1 However, I briefly looked at the code here: http://svn.apache.org/viewvc/maven/enforcer/tags/enforcer-1.3.1/enforcer-rules/src/main/java/org/apache/maven/plugins/enforcer/BannedDependencies.java?revision=1502671&view=markup and classifier does not seem to have made it in. Have I walked through this correctly? If so, is there a fix (other than not using classifiers, or just hoping that a DEBUG classifier doesn't make it into a release)? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Strange maven central response - do you see the same thing??
Hi, if i try the given URL: > http://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-provider-cvsexe I'm redirected to : http://central.maven.org/maven2/org/apache/maven/scm/maven-scm-provider-cvsexe/ .. Kind regards Karl-Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Strange maven central response - do you see the same thing??
Hi, I guess Karl-Heinz and I are accessing from Germany, so maybe there is some routing problem on your side? You guess is correct Mirko... Kind regards Karl-Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANNOUNCE] Release Mojo's JDepend Maven Plugin version 2.0
Hi, The Mojo team is pleased to announce the release of the JDepend Maven Plugin version 2.0. This plugin produces a nicely formatted metrics report based on your project. http://mojo.codehaus.org/jdepend-maven-plugin/ To get this update, simply specify the version in your project's plugin configuration: org.codehaus.mojo jdepend-maven-plugin 2.0 Release Notes: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=13231&version=20128 Bug [MJDEPEND-8] - Add missing scm entry in pom Improvement [MJDEPEND-6] - Stabilize Plugin IT's by using a setup project [MJDEPEND-9] - Improve Usage page [MJDEPEND-10] - State that plugin uses the JDepend library and include link [MJDEPEND-11] - Change the license text. New Feature [MJDEPEND-1] - Add a -no-fork goal Enjoy, The Mojo team. Karl-Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANNOUNCE] Release Mojo's Exec Maven Plugin version 1.3
Hi, The Mojo team is pleased to announce the release of the Exec Maven Plugin version 1.3. The plugin provides 2 goals to help execute 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.3 Release Notes: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11240&version=17822 Bug [MEXEC-86] - outputFile support for capturing exec not functional [MEXEC-104] - Cannot pass empty argument to exec goal. [MEXEC-105] - %classpath is fragile when used with [MEXEC-108] - NPE at EnvironmentUtils.toStrings() Improvements: [MEXEC-66] - ability to add custom classpath together with %classpath placeholder [MEXEC-73] - add configuration for adding additional directories to project classpath [MEXEC-93] - Exec plugin not marked as @threadSafe [MEXEC-107] - Drop @execute phase="validate" from ExecJavaMojo [MEXEC-119] - At position of argument to "Misconfigured argument, value is null" message [MEXEC-122] - Run integration test only by using the profile run-its [MEXEC-123] - use java 5 plexus annotations [MEXEC-125] - Upgrade Plugin Required Maven Version to 2.2.1 [MEXEC-129] - provided scope for maven-plugin-annotation [MEXEC-130] - @threadSafe [MEXEC-131] - commons-exec upgrade to 1.2 [MEXEC-133] - Upgrade to mojo-parent v:33 Task [MEXEC-101] - Migrate plugin to JDK5 Wish [MEXEC-126] - Bring back Maven 2.0.11 Compatibility Enjoy, The Mojo team. Karl-Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Spring snapshots
Hi, > Hi, I use only spring RELEASE (3.1.4.RELEASE) builds in my pom and I have no repository definitions in the pom. Do you have repository definitions in your settings.xml file ? -- Kind regards Karl-Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [ANN] buildnumber-maven-plugin 1.3 Released
Hi Bruce, > Hi, How does this work? I tried twice but the build number is still the same. What does this mean? What did you tried? Can you show the pom file you used? Can you show the output you've got? Kind regards Karl-Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to override settings for maven module
Hi, the first thing in such situations is to create a separate module which contains the generation code part. In this module you can change the configuration for maven-compiler-plugin via a pluginManagemen block... So looks like this: parent (pom.xml) +-- mod-generated (pom.xml) +-- mod-the-rest (pom.xml) If you follow this suggestions you have clear separation of concern for your modules and you only need to change the configuration for the mod-generated. Kind regards Karl-Heinz Marbaise On 5/9/14 2:59 AM, Niranjan Rao wrote: I have a master POM file which defines common stuff such as common dependencies like junit and compiler settings. The compiler settings are set to treat warning as error using maven-compiler-plugin and Werror as compiler argument. I have a new module which declares the master pom as parent pom, but has generated code which has lot of warnings. I would like to disable treating warnings as errors only for this module or if possible only for generated package or generated source directory. I tried adding compiler plugin entry in module's pom file. But it looks like it overrides from parent. How do I disable warnings for this module only? Regards, Niranjan - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-invoker-plugin: running ITs in parallel?
Hi Baptiste, I'm working often with maven-invoker and have found an issue with parallelThreads option (http://jira.codehaus.org/browse/MINVOKER-147). The local shared repos is also a problem. The should be something like a repo per IT... Kind regards Karl-Heinz Marbaise > *TL;DR: does anyone use the parallelThreads option in maven-invoker-plugin? Do you also have issues with concurrent local repository access? If so, how do you solve them?* I've recently come across the parallelThreads option in maven-invoker-plugin. After having tried to use it a few times, I'm currently stuck. It fails randomly, and not surprisingly it seems like it comes from the fact the local-repo is shared between ITs. While downloading from the MRM, there's always one jars that fails to be written to the disk because of a likely concurrent access. My first thought was to try and have a separate localRepository per IT. But I can't find a property or even a workaround to do that. Because filing an issue to m-invoker-p, I wanted to check here if I was missing something. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to move the of a multi-module project?
Hi, > grandfather | | pom.xml | | father | | pom.xml | | son | | pom.xml If I build that project, I will have these target directories: /home/me/projects/grandfather/target, /home/me/projects/grandfather/father/target and /home/me/projects/grandfather/father/son/target. Is there anyway to modify only 1 pom.xml (it doesn't matter if it is grandfather's or father's or son's) so that the target directories are /tmp/grandfather/target, /tmp/grandfather/father/target and /tmp/grandfather/father/son/target? So my question to this is: Why do want to do this? What's the reason to use a folder outside the modules ? Can you explain your use case and why you need it such that way and can't stuck with the conventions project/target ? Kind regards Karl-Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven EAR Plugin 2.9.1 Released
The Apache Maven team is pleased to announce the release of the Apache Maven EAR Plugin, version 2.9.1 This plugin (insert short description of the plugin's purpose). 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.9.1 Release Notes - Maven EAR Plugin Plugin - Version 2.9.1 Bug * [MEAR-189] - fileNameMapping set to no-version breaks skinnyWars feature Task * [MEAR-185] - Deprecated reference to 'defaultJavaBundleDir' in plugin documentation Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven JAR Plugin 2.5 Released
The Apache Maven team is pleased to announce the release of the Apache Maven JAR Plugin, version 2.5. This plugin provides the capability to build jars. http://maven.apache.org/plugins/maven-jar-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-jar-plugin 2.5 Release Notes - Maven JAR Plugin - Version 2.5 Bugs: [MJAR-157] - forceUpdate documentation is insufficient [MJAR-162] - skipIfEmpty not work for test-jar goal and empty directories [MJAR-167] - skipIfEmpty outputs incorrect logging nessage Improvements: [MJAR-168] - Update to latest plexus-archiver [MJAR-170] - please add property 'maven.jar.classifier' [MJAR-175] - Documentation problem for test-jar [MJAR-176] - Usage page should (only) describe default behavior Tasks: [MJAR-158] - use maven-plugin-tools' java 5 annotations [MJAR-171] - Remove deprecated mojo jar-sign and jar-sign-verify [MJAR-173] - Check correctness of declared deps Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven 3.2.2 breaks maven-invoker-plugin?
Hi,
Created an jira entry http://jira.codehaus.org/browse/MINVOKER-166
for it...
Many thanks for the information...
Kind regards
Karl-Heinz Marbaise
On 6/26/14 4:42 PM, cody.a.fy...@wellsfargo.com wrote:
I just update to 3.2.2 from 3.2.1 and am now getting the error below from the
maven-invoker-plugin. Using Java 1.8.20.
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-invoker-plugin:1.8:run (integration-test) on
project base-pom: Execution integration-test of goal
org.apache.maven.plugins:maven-invoker-plugin:1.8:run failed: An API
incompatibility was encountered while executing
org.apache.maven.plugins:maven-invoker-plugin:1.8:run:
java.lang.NoSuchMethodError:
org.apache.maven.settings.Settings.getRuntimeInfo()Lorg/apache/maven/settings/RuntimeInfo;
Here is the configuration from my pom.xml:
org.apache.maven.plugins
maven-invoker-plugin
1.8
false
pre-integration-test
install
integration-test
run
false
${basedir}/src/test/resources/settings.xml
true
true
${project.build.directory}/it/projects
true
4
${basedir}/src/test/resources/parent
${BUILD_NUMBER}
true
true
${BUILD_NUMBER}
true
${basedir}/src/test/resources/parent/pom.xml
true
true
true
false
install
sonar:sonar
release:prepare
release:perform
something.com
${localRepositoryPath}
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: maven 3.2.2 breaks maven-invoker-plugin?
Hi,
so based on the tests made and the help of Cody the issue is fixed.
> Thanks Karl-Heinz!
You're welcome...
Regards
Karl-Heinz Marbaise
On Jun 26, 2014, at 1:03 PM, Karl Heinz Marbaise mailto:khmarba...@gmx.de>> wrote:
Hi,
Created an jira entry http://jira.codehaus.org/browse/MINVOKER-166
for it...
Many thanks for the information...
Kind regards
Karl-Heinz Marbaise
On 6/26/14 4:42 PM, cody.a.fy...@wellsfargo.com
<mailto:cody.a.fy...@wellsfargo.com> wrote:
I just update to 3.2.2 from 3.2.1 and am now getting the error below
from the maven-invoker-plugin. Using Java 1.8.20.
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-invoker-plugin:1.8:run
(integration-test) on project base-pom: Execution integration-test of
goal org.apache.maven.plugins:maven-invoker-plugin:1.8:run failed: An
API incompatibility was encountered while executing
org.apache.maven.plugins:maven-invoker-plugin:1.8:run:
java.lang.NoSuchMethodError:
org.apache.maven.settings.Settings.getRuntimeInfo()Lorg/apache/maven/settings/RuntimeInfo;
Here is the configuration from my pom.xml:
org.apache.maven.plugins
maven-invoker-plugin
1.8
false
pre-integration-test
install
integration-test
run
false
${basedir}/src/test/resources/settings.xml
true
true
${project.build.directory}/it/projects
true
4
${basedir}/src/test/resources/parent
${BUILD_NUMBER}
true
true
${BUILD_NUMBER}
true
${basedir}/src/test/resources/parent/pom.xml
true
true
true
false
install
sonar:sonar
release:prepare
release:perform
something.com
<http://something.com>
${localRepositoryPath}
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: M2E and Eclipse Luna ?
Hi Jim, first be aware than in Luna the internal Maven is Maven 3.2.1 so i would check if this is the same as you use on command line or in Kepler which is not the case cause in Kepler is was 3.0.4... So it might be caused by that... Have you checked if you get warnings on command at the start of the build ? Kind regards Karl-Heinz Marbaise On 6/27/14 6:49 PM, Jim Garrison wrote: -Original Message- From: Dan Tran Sent: Friday, June 27, 2014 9:42 AM My apology, should have been clearer I installed Eclipse Luna and https://repository.sonatype.org/content/repositories/forge-sites/m2e- extras/0.15.0/N/0.15.0.201206251206 the message at the pom is "Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-plugin- plugin:3.2:descriptor (execution: default-descriptor, phase: process-classes)" I am also seeing weirdness with Luna. My project works under Kepler but in Luna I get MojoFailureException: Artifact[jar:org.mongodb:mongo-java-driver] has 2 candidates, please provide a classifier.pom.xml /etl_app_earline 1 Maven Java EE Configuration Problem But there is no problem in the repository with mongo-java-driver. I can just "delete" this error marker but it reappears every time I do a clean build. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Changelog Plugin 2.3 Released
The Apache Maven team is pleased to announce the release of the
Apache Maven Changelog Plugin, version 2.3.
The Maven Changelog Plugin generates reports regarding the recent changes in
your Software Configuration Management or SCM. These reports include the
changelog report, developer activity report and the file activity report.
http://maven.apache.org/plugins/maven-changelog-plugin/
You should specify the version in your project's plugin configuration:
org.apache.maven.plugins
maven-changelog-plugin
2.3
Release Notes - Maven Changelog Plugin - Version 2.3
Bugs:
* [MCHANGELOG-68] - testReadFile unit test timebased comparisons fail
* [MCHANGELOG-108] - read/write changelog.xml inconsistency
* [MCHANGELOG-129] - use maven-plugin-tools' java 5 annotations
* [MCHANGELOG-130] - NullPointerException when no SCM is defined
* [MCHANGELOG-133] - ChangeLog: allow encoding of file paths for gitblit
* [MCHANGELOG-134] - ChangeLog: added include/exclude support to filter
uninteresting files
Improvements:
* [MCHANGELOG-110] - use ${project.reporting.outputEncoding} as default value
for "outputEncoding" parameter and default to UTF-8
* [MCHANGELOG-114] - add standard skip configuration option
* [MCHANGELOG-123] - Patch with support for SCM provider implementations
(similar to release plugin)
* [MCHANGELOG-126] - Upgrade to Maven SCM 1.8
* [MCHANGELOG-131] - Resource bundle for Spanish Argentina
New Feature:
* [MCHANGELOG-122] - Add pt_BR localization
Task
* [MCHANGELOG-100] - Bump to Doxia 1.1.4
Enjoy,
-The Apache Maven team
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: [Clash Inspector] Release 0.9 and asking for quick feedback
Hi, > Hi guys, some students have created a nice Maven plugin: http://clashinspector.com It analyzes potential problems regarding version clashes between (transient) dependencies. It has a nice HTML view (but can also be used from the console). Just give it a shot: mvn com.clashinspector:clashinspector-maven-plugin:0.9:html for console output: mvn com.clashinspector:clashinspector-maven-plugin:0.9:tree mvn com.clashinspector:clashinspector-maven-plugin:0.9:list Next week they have the possibility to present their results. And it would be great if they had some testimonials from the Maven community. So please feel free to add your feedback: (Even one line will be helpful) First the site does not represent the correct state of your release 0.9 ..the page shows 0.3 (http://clashinspector.com/index.html) and some sub pages show 0.3-SNAPSHOT (http://clashinspector.com/version_clash_details.html) ... It would be helpfull if an up to date documentation is online...in particular if is in Maven central... First this plugin looks good (the output looks really good), but some of the intentions of the plugin do exist already in tasts of the maven-enforcer-plugin (http://maven.apache.org/enforcer/enforcer-rules/dependencyConvergence.html) which exactly checks such dependency convergence problems...and can fail a build in such cases What i don't understand is the html goal which starts Jersey but does not create anything ? The following i got: [INFO] Jun 29, 2014 12:50:29 AM org.glassfish.jersey.server.ApplicationHandler initialize INFO: Initiating Jersey application, version Jersey: 2.8 2014-04-29 01:25:26... [WARNING] Couldn't open File with default-browser. Please open file manually under: /var/folders/22/mdbr7dbx7ln66nz3yhrhph_hgn/T/clashInspector.html [INFO] Local ClashInspector-Server running on port 8090. To stop server press enter. Apart from that above i'm not sure it looks like i've found a little "bug" cause i have started that against one of my plugins...and compared it with the mvn dependency:tree ... In the output of dependency:tree i found an dependency testng which is not listed as an dep in clashinspector output cause testng is defined in scope:test...furthermore junit is listed as a dependency with scope:compile cause testng is defined as scope:test which is not transitive... But this should be inspected very carefully...handling of dependencies in Maven is not a trivial job... Kind regards Karl-Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Invoker Plugin 1.9 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Invoker Plugin, version 1.9. The Invoker Plugin is used to run a set of Maven projects. The plugin can determine whether each project execution is successful, and optionally can verify the output generated from a given project execution. http://maven.apache.org/plugins/maven-invoker-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-invoker-plugin 1.9 Release Notes - Maven Invoker Plugin - Version 1.9 Bugs: * [MINVOKER-162] - IT failure with empty local it-repo * [MINVOKER-166] - Failing in relationship with Maven 3.2.2 Improvement: * [MINVOKER-119] - Allow access to properties in pre- and postBuild scripts New Features: * [MINVOKER-122] - Import information into groovy scripts of the running Maven environment * [MINVOKER-141] - passing own properties to all scripts * [MINVOKER-151] - Add failIfNoProjects Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How do you report a maven bug ?
Hi Tommy, Can you give a little more details what you have done may be you have an example project...? I'm happe to create the jira entry for you if you have doubts to make a registration for jira... Kind regards Karl-Heinz Marbaise On 7/10/14 1:18 PM, Tommy Svensson wrote: Hello, I wonder how you report a bug in maven ? I found the following: http://jira.codehaus.org/browse/MNG But that requires a login and there is no ”sing up”. I get the following when trying to build a maven plugin with version 3.2.2: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-plugin-plugin:3.2:descriptor (default-descriptor) on project markdowndoc-maven-plugin: Execution default-descriptor of goal org.apache.maven.plugins:maven-plugin-plugin:3.2:descriptor failed: 4900 -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-plugin-plugin:3.2:descriptor (default-descriptor) on project markdowndoc-maven-plugin: Execution default-descriptor of goal org.apache.maven.plugins:maven-plugin-plugin:3.2:descriptor failed: 4900 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224) 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:116) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:347) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:154) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213) at org.apache.maven.cli.MavenCli.main(MavenCli.java:157) 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:606) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) Caused by: org.apache.maven.plugin.PluginExecutionException: Execution default-descriptor of goal org.apache.maven.plugins:maven-plugin-plugin:3.2:descriptor failed: 4900 at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:143) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) ... 19 more Caused by: java.lang.ArrayIndexOutOfBoundsException: 4900 at org.objectweb.asm.ClassReader.readClass(Unknown Source) at org.objectweb.asm.ClassReader.accept(Unknown Source) at org.objectweb.asm.ClassReader.accept(Unknown Source) at org.apache.maven.tools.plugin.annotations.scanner.DefaultMojoAnnotationsScanner.scanFile(DefaultMojoAnnotationsScanner.java:139) at org.apache.maven.tools.plugin.annotations.scanner.DefaultMojoAnnotationsScanner.scan(DefaultMojoAnnotationsScanner.java:85) at org.apache.maven.tools.plugin.annotations.JavaAnnotationsMojoDescriptorExtractor.scanAnnotations(JavaAnnotationsMojoDescriptorExtractor.java:125) at org.apache.maven.tools.plugin.annotations.JavaAnnotationsMojoDescriptorExtractor.execute(JavaAnnotationsMojoDescriptorExtractor.java:104) at org.apache.maven.tools.plugin.scanner.DefaultMojoScanner.populatePluginDescriptor(DefaultMojoScanner.java:108) at org.apache.maven.plugin.plugin.AbstractGeneratorMojo.execute(AbstractGeneratorMojo.java:233) at org.apache.maven.plugin.plugin.DescriptorGeneratorMojo.execute(DescriptorGeneratorMojo.java:92) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132) ... 20 more An ArrayIndexOutOfBoundsException looks very much like a bug to me :-). 4900 also looks like a very suspicious number! There is only 261 lines in the plugin code, and a total of 11 annotations. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Source Plugin 2.3 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Source Plugin, version 2.3. The Source Plugin creates a jar archive of the source files of the current project. The jar file is, by default, created in the project's target directory. http://maven.apache.org/plugins/maven-source-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-source-plugin 2.3 Release Notes - Maven Source Plugin - Version 2.3 Bugs: * [MSOURCES-63] - Non-working links on doc site * [MSOURCES-64] - forceCreation=true doesn't create test source package when src/test missing Improvements: * [MSOURCES-68] - Add Maven version used to Created-By entry in manifest * [MSOURCES-69] - Update version of plexus-archiver to 2.4.4 * [MSOURCES-70] - Update of maven-invoker-plugin to 1.9 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven shade/artifact naming help
Hi Eugene, > Hi, I have an existing multi-module project. A module A (i.e. artifactId=A) uses shade plugin to create an uber jar. The shade plug in config doesn't retain the original (slim) jar so the only artifact produced/published from this module is A.jar which is the uber jar. Which is not true, cause you can configure the maven-shade-plugin to produce both artifacts via: true http://maven.apache.org/plugins/maven-shade-plugin/shade-mojo.html Now I need to produce a 'slim' jar (lets call it A-core.jar) which only has the classes from module A. Since this was set up several releases ago I have to keep A.jar as a fat jar to preserve backwards compatibility. (I can easily make shade produce A.jar as the thin jar and A-uber.jar (or any other name) as the fat jar, but this is not acceptable.) Is there some way to make shade plug in do that? Kind regards Karl-Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven shade/artifact naming help
Hi Eugene, First i don't see the need to continue the wrong way...So you should change it... If you really need to go the wrong way i would suggest to use the maven-jar-plugin with a special configuration to create the other jar... But i can't recommend to continue the wrong way... By using the maven-shade-plugin you can't change that wrong way which you have decided to go a time a go... If the way you have already gone is not acceptable.. Kind regards Karl-Heinz Marbaise On 7/14/14 8:55 PM, Eugene Koifman wrote: Thank you for the reply but it doesn't answer my question. "The shade plug in config doesn't retain the original (slim) jar so the only artifact produced/published from this module is A.jar which is the uber jar." - this is a statement about the current pom in the project, not the capabilities of the shade plug in. Adding "shadedArtifactAttached" will create the slim jar called A.jar and an uber jar called A-shaded.jar. Unfortunately, what is needed is an uber jar called A.jar and a slim jar called anything. On Mon, Jul 14, 2014 at 11:48 AM, Karl Heinz Marbaise wrote: Hi Eugene, Hi, I have an existing multi-module project. A module A (i.e. artifactId=A) uses shade plugin to create an uber jar. The shade plug in config doesn't retain the original (slim) jar so the only artifact produced/published from this module is A.jar which is the uber jar. Which is not true, cause you can configure the maven-shade-plugin to produce both artifacts via: true http://maven.apache.org/plugins/maven-shade-plugin/shade-mojo.html Now I need to produce a 'slim' jar (lets call it A-core.jar) which only has the classes from module A. Since this was set up several releases ago I have to keep A.jar as a fat jar to preserve backwards compatibility. (I can easily make shade produce A.jar as the thin jar and A-uber.jar (or any other name) as the fat jar, but this is not acceptable.) - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Release appassembler-maven-plugin Version 1.8.1 - Released
Hi, The Mojo team is pleased to announce the release of the Appassembler Maven Plugin version 1.8.1. 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.8.1 Release Notes: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11780&version=20322 Bugs: * [MAPPASM-121] - Generated script should be set executable (or allow for a umask to be defined). * [MAPPASM-228] - [Daemon *nix template] Params of tr command must be quoted * [MAPPASM-234] - Make unix scripts executable, but not world-writable, i.e. 0755 (on unix) Improvements: * [MAPPASM-230] - Failed to create directory for log/temp files * [MAPPASM-233] - Change integration tests according to maven-invoker-plugin 1.9 (mavenVersion) in verify.groovy Wish: * [MAPPASM-54] - make unix scripts executable (on unix) Enjoy, The Mojo team. Karl-Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: move data from pom to class or class to pom
Hi,
> Move the Java code that should contain the version into an own directory
tree (e.g. src/main/java-templates). Replace the version string with an
expression (e.g. "${project.version}") and use the copy-resources goal of
the resources plugin to filter the file into a target driectory tree (e.g.
target/generated-sources). Bind the goal to the generate-sources phase. Then
use additionally the build-helper plugin to add target/generated-sources as
additional source directory and you're done.
Best solution was already mentoined by Robert Scholte by using the
templating-maven-plugin which exactly supports that scenario without
supplemental addition of target/generated-sources folder by
build-helpr-maven-plugin etc.
Just simply create the template files in src/main/java-templates/ use
the expressions etc. no need for supplemental configuration of
maven-resources-plugin etc.
Best and simple solution...which i wrote longer time a go a blog about
http://blog.soebes.de/blog/2014/01/02/version-information-into-your-appas-with-maven/
Kind regards
Karl-Heinz Marbaise
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: [Announce] Release of SonarQube Maven Plugin 2.4
Hi Cristinano,
for whatever reason the plugin is available in Codehaus Nexus (Staging
Repository)
https://nexus.codehaus.org/content/groups/staging/ but it isn't being
synched to Central
Created a Haus Ticket for it:
http://jira.codehaus.org/browse/HAUS-2391
Thanks for the hint...
Kind regards
Karl-Heinz Marbaise
On 7/17/14 5:29 PM, Cristiano Gavião wrote:
Hi Julien,
I wasn't able to see this version at
http://search.maven.org/#search|ga|1|sonar-maven-plugin
could you check, please?
thanks,
Cristiano
On 15-07-2014 12:08, Julien HENRY wrote:
Hi,
The Mojo team is pleased to announce the release of the SonarQube
Maven Plugin version 2.4.
This plugin aims at running SonarQube analysis for Maven projects.
http://mojo.codehaus.org/sonar-maven-plugin/index.html
To get this update, simply specify the version in your project's
plugin configuration:
org.codehaus.mojo
sonar-maven-plugin
2.4
Release Notes
* [MSONAR-70] - Use every available "sonar.*" property when
running an analysis with Maven
* [MSONAR-75] - Remove unexisting entries from "sonar.sources"
and "sonar.tests" on projects with packaging=pom
* [MSONAR-81] - On "war" modules the directory containing the web
resources ("src/main/webapp" by default) should be automatically added
to "sonar.sources"
* [MSONAR-82] - By default the "pom.xml" file should be part of
"sonar.sources"
* [MSONAR-83] - Populate sonar.libraries
Enjoy,
The Mojo team.
Julien HENRY
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: [Announce] Release of SonarQube Maven Plugin 2.4
Hi Cristiano,
now the artifacts are visible via search.maven.org...so it should work.
Kind regards
Karl-Heinz Marbaise
On 7/17/14 5:38 PM, Karl Heinz Marbaise wrote:
Hi Cristinano,
for whatever reason the plugin is available in Codehaus Nexus (Staging
Repository)
https://nexus.codehaus.org/content/groups/staging/ but it isn't being
synched to Central
Created a Haus Ticket for it:
http://jira.codehaus.org/browse/HAUS-2391
Thanks for the hint...
Kind regards
Karl-Heinz Marbaise
On 7/17/14 5:29 PM, Cristiano Gavião wrote:
Hi Julien,
I wasn't able to see this version at
http://search.maven.org/#search|ga|1|sonar-maven-plugin
could you check, please?
thanks,
Cristiano
On 15-07-2014 12:08, Julien HENRY wrote:
Hi,
The Mojo team is pleased to announce the release of the SonarQube
Maven Plugin version 2.4.
This plugin aims at running SonarQube analysis for Maven projects.
http://mojo.codehaus.org/sonar-maven-plugin/index.html
To get this update, simply specify the version in your project's
plugin configuration:
org.codehaus.mojo
sonar-maven-plugin
2.4
Release Notes
* [MSONAR-70] - Use every available "sonar.*" property when
running an analysis with Maven
* [MSONAR-75] - Remove unexisting entries from "sonar.sources"
and "sonar.tests" on projects with packaging=pom
* [MSONAR-81] - On "war" modules the directory containing the web
resources ("src/main/webapp" by default) should be automatically added
to "sonar.sources"
* [MSONAR-82] - By default the "pom.xml" file should be part of
"sonar.sources"
* [MSONAR-83] - Populate sonar.libraries
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: move data from pom to class or class to pom
Hi Jörg,
>
nice article ;-)
There's one comment I do not understand though:
The main disadvantage of this approach is that you can only use the
Implementation and Specification parts of your MANIFEST.MF file which
might be enough in some situations but not in all.
The comment is related to the implementation in Java which allows only
to extract the implementation and specification part...via
this.getClass().getPackage()
http://docs.oracle.com/javase/7/docs/api/java/lang/Package.html
So can't use that in a very simple way...
You can add all kind of entries to the manifest. You may even overwrite the
defaults. We use typically:
Of course you can so create an appropriate MANIFEST.MF file...
= %< ==
true
true
${parsedVersion.majorVersion}.
${parsedVersion.minorVersion}
${java.version.source}
${java.version.target}
Maven ${maven.version}
${maven.build.timestamp}
${os.name}
= %< ==
With the $parsedVersion and $maven.version variables provided by the build-
helper plugin.
But the above entries can't be read via methods which already exists
like getPackage()
So you need to implement it your own...you have to take care about
classloading issue (classloaders in particular in larger apps etc.)...
so it get more and more complicated...lets talk about apps which
comprise of 150 jar files...
So the simplest Solution is to use the templating-maven-plugin which
solves many of those issues.
Kind regards
Karl-Heinz Marbaise
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-dependency-plugin unpacking aar format?
HI David, > I'm getting the following error trying to unpack some files from an aar. Is this not supported? Is there any way to do this? Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.8:unpack-dependencies (unpack-service) on project service: Unknown archiver type: No such archiver: 'aar'. -> [Help 1] Could you please prepare a example project which reproduces the problem..so i can create a JIRA issue for this... Kind regards Karl-Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-dependency-plugin unpacking aar format?
Hi Robert, > Sorry to interject, but isn¹t the unpack goal of the maven-assembly-plugin deprecated? The documentation actually refers users to the MDP¹s unpack capabilities: https://maven.apache.org/plugins/maven-assembly-plugin/plugin-info.html That page is dated from 2012, so I¹m not sure if something has changed since it was last published. What you mentioned is correct...the unpack goal is marked as deprecated and will be removed... This page is not updated cause on the public available things have not being changed... Apart from that those pages are only updated according with new released which has not been done yet (new release is in preparation 2.4.1 (http://jira.codehaus.org/browse/MASSEMBLY), but it will take some time)... Kind regards Karl-Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: testing-harness plugin: LocalRepositoryManager is not set
Hi,
my assumption is to use the maven-compat artifact in your project apart
from that it would be interesting which kind of plugin do you develop
and which intention it has...
Kind regards
Karl-Heinz Marbaise
On 7/23/14 5:38 PM, Vincent Zurczak wrote:
Hi,
I am not sure this is the right mailing-list.
Maybe I should have posted to the dev list. Anyway...
I have started working on new Maven plug-in last week and I have set up
unit tests using the testing-harness plugin.
I have problems with Maven injected fields, such as the Maven project.
I use the Maven libraries version 3.2.2, and the harness plugin in
version 3.2.0.
My mojo has an injected field...
@Parameter( defaultValue = "${project}", readonly = true )
private MavenProject project;
This field is correctly set when I run the plugin normally.
But it is null when I use the harness plugin. Here is the code in my test.
@Rule
public MojoRule rule = new MojoRule();
@Rule
public TestResources resources = new TestResources();
@Test( expected = MojoFailureException.class )
public void testWithoutAssertions() throws Exception {
File baseDir = this.resources.getBasedir( "project--invalid-app" );
File pom = new File( baseDir, "pom.xml" );
ValidateMojo mojo = (ValidateMojo) this.rule.lookupMojo(
"validate", pom );
mojo.execute();
}
The NPE occurs in the execute method.
The documentation indicates we have (or had) to use a stub. [0]
So, so far, I guess it makes sense (I guess, because unless you read
this page [0], it is not clear on the web site that injected fields will
not work).
The JIRA entry [1] states we can also use
MojoRule#lookupConfiguredMojo() to have a mojo configured with the
default settings.
But when I use it, that is to say...
ValidateMojo mojo = (ValidateMojo) this.rule.lookupConfiguredMojo(
baseDir, "validate" );
mojo.execute();
... I get the following exception.
java.lang.Exception: Unexpected exception,
expected but
was
at
org.junit.internal.runners.statements.ExpectException.evaluate(ExpectException.java:31)
at
org.apache.maven.plugin.testing.MojoRule$2.evaluate(MojoRule.java:308)
at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:47)
at org.junit.rules.RunRules.evaluate(RunRules.java:18)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
at
org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
at
org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192)
*Caused by: java.lang.IllegalArgumentException: Invalid repository
system session: LocalRepositoryManager is not set.*
at
org.eclipse.aether.internal.impl.DefaultRepositorySystem.invalidSession(DefaultRepositorySystem.java:497)
at
org.eclipse.aether.internal.impl.DefaultRepositorySystem.validateSession(DefaultRepositorySystem.java:443)
at
org.eclipse.aether.internal.impl.DefaultRepositorySystem.collectDependencies(DefaultRepositorySystem.java:316)
at
org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:192)
at
org.apache.maven.project.DefaultProjectBuildingHelper.resolveExtensionArtifacts(DefaultProjectBuildingHelper.java:380)
at
org.apache.maven.project.DefaultProjectBuildingHelper.createProjectRealm(DefaultProjectBuildingHelper.java:239)
at
org.apache.maven.project.DefaultModelBuildingListener.buildExtensionsAssembled(DefaultModelBuildingListener.java:110)
at
org.apache.maven.model.building.ModelBuildingEventCatapult$1.fire(ModelBuildingEventCatapult.java:43)
at
org.apache.maven.model.building.DefaultModelBuilder.fireEvent(DefaultModelBuilder.java:1179)
at
org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:415)
at
org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:398)
at
org.apache.maven.model.building.DefaultModel
Re: Upload 3rd party jars retaining original names
Hi David,
> Is it possible to put a bunch of 3rd party jars into a Maven repository
so that they can be accessed by a project using their original names?
What do you mean by original names? As they were in Ant? More or simple
answer to this is no, cause Maven has it's rules how artifacts are
stored in a repository.
I am developing against a 3rd party software package that includes about
a dozen supporting jar files. I am trying to upload these jars into a
Maven repository such that I can put a dependency in my development
project that puts all of the original jars on my classpath. I have
tried:
* insert jars individually (and as a collection) using Nexus console but
the stored jar is named {artifactId}-{version}
This is the rule as artifacts are stored in a repository...
* create jar projects with various source structures but, again, the
stored jar is named {artifactId}-{version}
The sources structure is not related to the naming rules, cause you
should think about how would other consume those artifacts if they do
not follow a naming rule...big example see Maven Central
* create a jar project containing an assembly: I can make the 3rd party
jars visible with their original names but, yet again, they are put into
in a jar named {artifactId}-{version}.
Context is that I'm just beginning to try and replace historical
Ant/Eclipse projects with Maven/Eclipse. I've read through "Maven The
Definitive Guide" and Googled as much as I can but I'm at a stage where
I'm not even sure I'm asking sensible questions. If there's a "how to"
document around (with worked examples rather than isolated XML
fragments) that would be great. If I'm missing the point of Maven and
trying to implement an Ant concept that would be good to know too.
You have to follow the naming rule and change other projects to consume
those artifacts with the appropriate naming rules
Kind regards
Karl-Heinz Marbaise
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven SCM Version 1.9.1 Released
The Apache Maven team is pleased to announce the release of the Apache Maven SCM, version 1.9.1 http://maven.apache.org/scm/ Maven SCM supports Maven 2.x plugins (e.g. maven-release-plugin) and other tools (e.g. Continuum) by providing them with a common API for doing SCM operations. You can look at the list of SCMs for more information on using Maven SCM with your favorite SCM tool. Release Notes - Maven SCM Version 1.9.1 Bugs: * [SCM-740] - Maven Release Plugin releases SNAPSHOT instead of STABLE version * [SCM-750] - TFS-plugin fails in cases of 'TFS policies' is required by TFS upon checkin * [SCM-752] - maven-release-plugin:2.5:prepare fails with 'Error writing POM: (Access is denied)' * [SCM-753] - support TFS checkin-policies * [SCM-757] - bootstrap/checkout/export goals now requires -Dproject.basedir=. set at command line * [SCM-765] - jgit provider commits changes with system user instead of passed username Improvement: * [SCM-741] - scm:validate for svn should offer a way to check the current directory actually matches what's declared in the pom New Feature: * [SCM-747] - [PERFORCE] Support SSL Tasks: * [SCM-754] - Require Tag/Branch Command to return the entire source tree is impractical * [SCM-755] - Inject SecDispatcher into TCK base test case * [SCM-756] - TCK should invoke EditCommand for provider like Perforce before any change * [SCM-760] - remove maven-scm-plugin's RemoveMojoTest due to specific Perforce setup requirement * [SCM-761] - Allow downstream TCK to define its own tag Enjoy, -The Apache Maven team Karl-Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [ANN] FindBugs Maven Plugin version 2.5.5 Released
hi Gary, > I still do not see the release in Maven Central. Thoughts? Gary Created an JIRA for HAUS for it. http://jira.codehaus.org/browse/HAUS-2395 Should be solved in a short time. Thank you for reporting it. Kind regards Karl-Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Assembly Plugin Version 2.4.1 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Assembly Plugin, version 2.4.1 http://maven.apache.org/plugins/maven-assembly-plugin The Assembly Plugin for Maven is primarily intended to allow users to aggregate the project output along with its dependencies, modules, site documentation, and other files into a single distributable archive. Release Notes - Maven Assembly Plugin Version 2.4.1 Bugs: * [MASSEMBLY-637] - fileSet unix strips last newline of file * [MASSEMBLY-651] - REOPEN - OutOfMemory when running maven-assembly-plugin * [MASSEMBLY-652] - Resource filtering does not work if line contains single @ * [MASSEMBLY-696] - Internal Regexp Error with Windows Paths Improvements: * [MASSEMBLY-639] - Change default for recompressZippedFIles back to true * [MASSEMBLY-682] - Make a link to the MavenArchiver documentation * [MASSEMBLY-686] - Update version of maven-filtering to 1.2 * [MASSEMBLY-687] - Change the prefered location for assembly descriptors and filter files * [MASSEMBLY-690] - Think about WARNING for module dependencies * [MASSEMBLY-693] - Update XSD Versions in examples * [MASSEMBLY-694] - Generation of the site does not work with Maven 3.2.1 Enjoy, -The Apache Maven team Karl-Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Use native tar to unpack? good/bad idea?
Hi Kristian, > I know I have a couple of branches that at least convert all the plexus-archiver zip stuff to use commons-compress, which is reasonably simple to plug into plexus-archiver. I have been a bit reluctant to push these changes since I've been mildly concerned about fallout. I think it should be fairly simple to convert the remaining plexus-archiver code to use commons-compress too, including the tar stuff. It would be great to get the commons compress part into...cause it's better maintained etc. Furthermore it would be a path to get rid of plexus-archiver at all...If i understand you would change the plexus-archiver to use commons-compress...so after that we could change the other plugins / components to use commons-compress directly... I am more concerned about the testing aspect of this change, it would require extensive testing and probably some community effort. Is there any interest in this ? Yes it is Of course it needs testing but if we don't go that way we have to stuck all the time plexus-archiver Commons-compress is at least maintained; which is a Good Thing ;) Thumb up... Kind regards Karl-Heinz Marbaise Kristian 2014-06-03 6:20 GMT+02:00 Dan Tran : Looks like it is worth a try to get maven-dependency-plugin having an option to use native tar during unpack. Thanks Jason -Dan On Mon, Jun 2, 2014 at 6:32 PM, Jason van Zyl wrote: I have had many problems with Java-based TAR solutions. I often use this where I can: https://github.com/airlift/airship/blob/master/airship-shared/src/main/java/io/airlift/airship/shared/FileUtils.java On Jun 2, 2014, at 7:15 PM, Dan Tran wrote: BTW, I never have good luck with plexus-archiver, and always ended up to implement my own 'unpack' using native tar to speed up the build and also reserve the softlinks in the archive. So am asking the user list to see if there any interests in this feature to give enough incentive to implement it Thanks -D On Mon, Jun 2, 2014 at 4:08 PM, Dan Tran wrote: Hi Alex, I will find a good sample file for you. Thanks -D On Mon, Jun 2, 2014 at 3:57 PM, Alexander Kriegisch < alexan...@kriegisch.name> wrote: Oh, I see, multiple options. Okay, then yes - maintenance nightmare. I think we should not easily give up Java's idea of platform independence and Maven's whole point: creating standardised, repeatable builds. If your idea is a reaction on your latest tar.gz problems, maybe we can find another solution for it. You have not reacted on my offer to inspect your files and see if I have an idea how to fix that in Java. :-) -- Alexander Kriegisch Am 03.06.2014 um 00:48 schrieb Dan Tran : correct, I would expect user to install tar.exe or cygwin with tar on windows and activate the option. By default, it still uses plexus-archiver to unpack -D On Mon, Jun 2, 2014 at 3:42 PM, Alexander Kriegisch < alexan...@kriegisch.name> wrote: Windows does not have tar by default. You need to install Git (incl. Git Bash), Cygwin, GnuWin32 or similar. I would not expect any user to have tar installed at all or if so then in any predictable location or even reachable via PATH. -- Alexander Kriegisch Am 03.06.2014 um 00:36 schrieb Dan Tran : I am think of enhancing maven-dependency-plugin by adding option to unpack 'tar' like artifact using native tar since it is faster and reserve soft links (?) Thoughts? would it be a maintaining night mare?? Thanks -Dan - 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 Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io - To think is easy. To act is hard. But the hardest thing in the world is to act in accordance with your thinking. -- Johann von Goethe - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Feature for Maven Enforcer Plugin Rule
Hi Basil, > I work for an Indian IT company(1,50,000+ employees) and we use Maven for many of our projects. Recently we used Maven Enforcer Plugin and Dependency Convergence Rule ( http://maven.apache.org/enforcer/enforcer-rules/dependencyConvergence.html). We needed the convergence to be checked for only project specific module dependencies. I wrote a custom rule modifying the existing rule to accept a standard include/exclude list. This is working fine and I think it will be a good feature to be included in the standard Dependency Convergence Rule. Should I raise this in JIRA? I don’t have a JIRA access. Sure it would be great if you create a JIRA account via this: https://xircles.codehaus.org/signup afterwards you can create a JIRA ticket for this purpose and describe what you have changed and of course attach the patch...Apart of that it would be great if you have some tests for the behaviour of your changes... Than i see no objections to integrate your change into maven-enforcer rules... Kind regards Karl-Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: creating custom Maven resource filter
Hi Jose,
can you elaborate a little bit more why you are not using the default
filtering capabilities of maven-resources-plugin etc. ?
Can you explain what exactly you like to achieve?
> Hello,
We have projects with many property and xml files that need resource filtering
per environment.
For example in a property file one might see ${mysqlDbHost}, ${mysqlDbPw}, and ${mysqlDbUser}. There
would also be a system variable called ENVIRONMENT. Based on the ${propertyName} and ENVIRONMENT
value, the resource filter would replace with the correct value. This can be done with a DB (SELECT
value FROM properties WHERE env="env" and name="propertyName") or via a web service
(getPropertyValue?env=env&name=propertyName).
On the Maven side the solution seem to be to create a custom
MavenResourcesFiltering. The custom MavenResourcesFiltering implementation
would do the lookups I mentioned above for each ${propertyName} encountered in
the resource files.
1) Is my assessment that creating a custom MavenResourcesFiltering is the way
to go? Maybe this problem is already solved already, since it does not seem
unique?
2) I have visited multiple Maven articles on this but still have no idea how
to implement it, the sites I visited are listed below. Does anyone know of any
document or can provide feedback on how to implement a custom
MavenResourcesFiltering?
It seems to me that at some point I would need a method that has either gets a
list of all the ${propertyName}'s found in a file and the ability to provide
the value for that property name. Following the links I found I cannot tell
where that method should be implemented and how to get it called from
MyMojo.execute().
1: http://maven.apache.org/shared/maven-filtering/
2: http://maven.apache.org/shared/maven-filtering/usage.html
3: http://maven.apache.org/guides/plugin/guide-java-plugin-development.html
Thank you!
jose
Kind regards
Karl-Heinz Marbaise
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven EJB Plugin Version 2.4 Released
The Apache Maven team is pleased to announce the release of the Apache Maven EJB Plugin, version 2.4 This plugin generates J2EE Enterprise Javabean (EJB) file as well as the associated client jar. http://maven.apache.org/plugins/maven-ejb-plugin org.apache.maven.plugins maven-ejb-plugin 2.4 Release Notes - Apache Maven EJB Version 2.4 Bugs: * [MEJB-28] - outputDirectory is not created before packaging * [MEJB-50] - Empty src/main/java causes ejb plugin to fail * [MEJB-52] - need to update dependency of maven-archiver to 2.5 Improvements: * [MEJB-56] - Add Maven version used to Created-By entry in manifest * [MEJB-58] - Documentation fails to mention where and how the plugin gets ejb-jar.xml from * [MEJB-64] - Upgrade to Maven 2.2.1 compatiblity * [MEJB-65] - Upgrade maven-filtering to 1.2 * [MEJB-66] - Upgrade plexus-archiver to 2.4.4 * [MEJB-68] - MavenProject/MavenSession Injection as a paremeter instead as a component. Tasks: * [MEJB-59] - use maven-plugin-tools' java 5 annotations * [MEJB-62] - "This version of the EJB Plugin uses Maven Archiver 2.4" hardcoded in Javadoc Enjoy, -The Apache Maven team Karl-Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Atomic deploy at end to repo manager like Nexus
Hi Dan, are you using deployAtEnd / installAtEnd options of maven-install-plugin, maven-deploy-plugin ? or do you have any issues with that ? On 8/27/14 10:36 PM, Dan Tran wrote: Hi Per last Maven hangout, Jason and Karl had a discussion and code shared on topic. unzip [1] nexus plugin was mentioned Can you share this knowledge? For my case, I have a multiple module multiple platform builds orchestrated by CI ( jenkins) I like to to delay all the deployments, all the way to the end, zip the up, and deploy to nexus which will correctly unpack and merge to one of the repositories ( ie snapshot or staging ) Kind regards Karl-Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: mvn 3.0.5 timeout during deployment
Hi, > How can I increase the default timeout for this operation? After Googling a lot I tried several server configurations in my settings.xml file but with no success: server.company.com.snapshots xxx xxx 60 60 60 60 Thank you in advance for any help! :-) [ERROR] Failed to execute goal at.company.xyz:xyz-maven-plugin:1.2.14.0:deploy (default-deploy) on project project_core: Unable to execute mojo: Failed to deploy artifacts: Could not transfer artifact at.xyz:project_core:jar:2.0.0.0-20140828.135650-6 from/to server.company.com (https://server.company.com/artifactory/axon-snap shot): No response received after 6 -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal at.company.xyz:xyz-maven-plugin:1.2.14.0:deploy (default-deploy) on project project_core: Unable to execute mojo can you explain what kind of plugin this is: goal at.company.xyz:xyz-maven-plugin:1.2.14.0:deploy (default-deploy) on ? Kind regards Karl-Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Create multi-module archetype with one module only active in a profile
Hi, > I am trying to create an archetype with two modules, one main and one itest. I would like to have the itest module only active when run with a profile. In my original project, the root pom includes a part like this: itest itest However, in the archetype-metadata.xml reference there is nothing mentioned about profiles. First do never create a module which is included by a profile, cause you will get trouble... In particular if you do a release and afterwards doing a build and activate the profile... Take a deeper look here:http://blog.soebes.de/blog/2013/11/09/why-is-it-bad-to-activate-slash-deactive-modules-by-profiles-in-maven/ Kind regards Karl-Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Create multi-module archetype with one module only active in a profile
Hi, a simple solution is to make such a module (sounds like an integration test module) just the profile inside the module so the execution of the integration tests is activated/deactivated by a profile things like maven-failsafe-plugin or whatever... This prevent problems with releases etc. Kind regards Karl-Heinz Marbaise On 8/29/14 9:15 PM, Thomas Larsson wrote: Thanks Karl, This seems like the sensible thing to do, and yes, we have already encountered the headache of keeping the submodules version number in sync after a release :-) Perhaps this should have been obvious. Thanks for the help anyway! /Thomas On Fri, Aug 29, 2014 at 8:28 PM, Karl Heinz Marbaise mailto:khmarba...@gmx.de>> wrote: Hi, > I am trying to create an archetype with two modules, one main and one itest. I would like to have the itest module only active when run with a profile. In my original project, the root pom includes a part like this: itest itest However, in the archetype-metadata.xml reference there is nothing mentioned about profiles. First do never create a module which is included by a profile, cause you will get trouble... In particular if you do a release and afterwards doing a build and activate the profile... Take a deeper look here:http://blog.soebes.de/__blog/2013/11/09/why-is-it-bad-__to-activate-slash-deactive-__modules-by-profiles-in-maven/ <http://blog.soebes.de/blog/2013/11/09/why-is-it-bad-to-activate-slash-deactive-modules-by-profiles-in-maven/> - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Install Plugin Version 2.5.2 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Install Plugin, version 2.5.2 The Install Plugin is used during the install phase to add artifact(s) to the local repository. The Install Plugin uses the information in the POM (groupId, artifactId, version) to determine the proper location for the artifact within the local repository. http://maven.apache.org/plugins/maven-install-plugin org.apache.maven.plugins maven-install-plugin 2.5.2 Release Notes - Apache Maven Install Version 2.5.2 Bugs: * [MINSTALL-100] - Update description for installAtEnd param * [MINSTALL-103] - Concurrency problem with installAtEnd in parallel builds Improvements: * [MINSTALL-106] - MavenProject/MavenSession Injection as a paremeter instead as a component. * [MINSTALL-107] - Upgrade to Maven 2.2.1 compatiblity Enjoy, -The Apache Maven team Karl-Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Deploy Plugin Version 2.8.2 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Deploy Plugin, version 2.8.2 The deploy plugin is primarily used during the deploy phase, to add your artifact(s) to a remote repository for sharing with other developers and projects. This is usually done in an integration or release environment. It can also be used to deploy a particular artifact (e.g. a third party jar like Sun's non redistributable reference implementations). http://maven.apache.org/plugins/maven-deploy-plugin org.apache.maven.plugins maven-deploy-plugin 2.8.2 Release Notes - Apache Maven Deploy Version 2.8.2 Bugs: * [MDEPLOY-172] - Concurrency problem with deployAtEnd in parallel builds * [MDEPLOY-174] - [REGRESSION] url not required anymore, causing a NullPointerException Improvements: * [MDEPLOY-185] - MavenProject/MavenSession Injection as a paremeter instead as a component. * [MDEPLOY-186] - Upgrade to Maven 2.2.1 compatiblity Enjo -The Apache Maven team Karl-Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven ACR Plugin Version 1.1 Released
The Apache Maven team is pleased to announce the release of the Apache Maven ACR Plugin, Version 1.1 This plugin generates J2EE Application Client file. http://maven.apache.org/plugins/maven-acr-plugin org.apache.maven.plugins maven-acr-plugin 1.1 Release Notes - Apache Maven ACR Version 1.1 Bug: * [MACR-5] - Usage page is wrong: Maven 3.0.4 does not include ACR plugin Tasks: * [MACR-6] - use maven-plugin-tools' java 5 annotations * [MACR-7] - Removed warnings during build * [MACR-9] - Upgrade plexus-archiver to 2.4.4 * [MACR-10] - Upgrade maven-filtering to 1.2 * [MACR-11] - Using maven-plugins parent version 25. Enjoy, -The Apache Maven team Karl-Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-javadoc-plugin 2.9.1 does not work with JDK 8, cannot find javax.interceptor.InterceptorBinding
Hi, based on the following issue: http://jira.codehaus.org/browse/MJAVADOC-393 Have you used the most recent version of JDK 8 (8u20?) Kind regards Karl-Heinz Marbaise On 9/10/14 9:58 AM, Rabe, Jens wrote: Hello, this problem was already posted in March, but there were no answers, since I have the same problem, I post it again: When using a source level of 1.8, the maven-javadoc-plugin does not work. My configuration in pom.xml is the following: org.apache.maven.plugins maven-javadoc-plugin attach-javadocs jar -Xdoclint:none This is what I get: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:2.9.1:jar (attach-javadocs) on project myproject: MavenReportException: Error while creating archive: [ERROR] Exit code: 1 - javadoc: error - com.sun.tools.doclets.internal.toolkit.util.DocletAbortException: com.sun.tools.doclets.internal.toolkit.util.DocletAbortException: com.sun.tools.doclets.internal.toolkit.util.DocletAbortException: com.sun.tools.javac.code.Symbol$CompletionFailure: class file for javax.interceptor.InterceptorBinding not found [ERROR] [ERROR] Command line was: /usr/lib/jvm/java-8-oracle/jre/../bin/javadoc @options @packages [ERROR] [ERROR] Refer to the generated Javadoc files in '/somefolder/target/apidocs' dir. [ERROR] -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:2.9.1:jar (attach-javadocs) on project myproject: MavenReportException: Error while creating archive: Exit code: 1 - javadoc: error - com.sun.tools.doclets.internal.toolkit.util.DocletAbortException: com.sun.tools.doclets.internal.toolkit.util.DocletAbortException: com.sun.tools.doclets.internal.toolkit.util.DocletAbortException: com.sun.tools.javac.code.Symbol$CompletionFailure: class file for javax.interceptor.InterceptorBinding not found Command line was: /usr/lib/jvm/java-8-oracle/jre/../bin/javadoc @options @packages Refer to the generated Javadoc files in '/somefolder/target/apidocs' dir. at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216) 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:108) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:76) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:116) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213) at org.apache.maven.cli.MavenCli.main(MavenCli.java:157) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) Caused by: org.apache.maven.plugin.MojoExecutionException: MavenReportException: Error while creating archive: Exit code: 1 - javadoc: error - com.sun.tools.doclets.internal.toolkit.util.DocletAbortException: com.sun.tools.doclets.internal.toolkit.util.DocletAbortException: com.sun.tools.doclets.internal.toolkit.util.DocletAbortException: com.sun.tools.javac.code.Symbol$CompletionFailure: class file for javax.interceptor.InterceptorBinding not found Command line was: /usr/lib/jvm/java-8-oracle/jre/../bin/javadoc @options @packages Refer to the generated Javadoc files in '/somefolder/target/apidocs' dir. at org.apache.maven.plugin.javadoc.AbstractJavadocMojo.failOnError(AbstractJavadocMojo.java:5913) at org.apache.maven.plugin.javadoc.JavadocJar.execute(JavadocJar.java:209) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBui
[ANN] Apache Maven RAR Plugin Version 2.4 Released
The Apache Maven team is pleased to announce the release of the Apache Maven RAR Plugin, Version 2.4 A resource adapter is a system-level software driver that a Java application uses to connect to an enterprise information system (EIS). The RAR plugin has the capability to store these resource adapters to an archive (Resource Adapter Archive or RAR) which can be deployed to a J2EE server. http://maven.apache.org/plugins/maven-rar-plugin org.apache.maven.plugins maven-rar-plugin 2.4 Release Notes - Apache Maven RAR Version 2.4 Improvements: * [MRAR-28] - Add Support for Classifier * [MRAR-35] - MavenProject/MavenSession Injection as a paremeter instead as a component. * [MRAR-37] - Upgrade maven-filtering to 1.2 * [MRAR-38] - Upgrade to Maven 2.2.1 compatiblity New Feature: * [MRAR-34] - provide "skip" parameter for the plugin Enjoy, -The Apache Maven team Karl-Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Releasing Maven Plugins
HI, > I'm currently releasing a new version of Flexmojos. While I sort of found a procedure for releasing > that maven plugin, it's still sort of a PITA. The main problem is that the project contains the plugin as >well as some modules that use the plugin. This is the basic mistake in this scenario. If you build a maven-plugin make a separate project from it and do the release etc. only from the maven-plugin and afterwards you have the release available and can continue with the rest which uses the release... Kind regards Karl-Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: AW: Releasing Maven Plugins
Hi Chris, > But if I create a plugin using the official maven-plugin archetype the setup is almost the same so it can't be that off-track. Which exactly have you used to do the setup... Furhtermore i would separate build tools for the build itself from using them... Apart from that what Anders is saying it is working but on the other hand you seemed to be having some problems so there must be problems in your build... Can you build on command line with a cleaned local repository without an issue just by using: mvn clean package ? Chris ____ Von: Karl Heinz Marbaise Gesendet: Freitag, 12. September 2014 14:46 An: Maven Users List Betreff: Re: Releasing Maven Plugins HI, > I'm currently releasing a new version of Flexmojos. While I sort of found a procedure for releasing > that maven plugin, it's still sort of a PITA. The main problem is that the project contains the plugin as >well as some modules that use the plugin. This is the basic mistake in this scenario. If you build a maven-plugin make a separate project from it and do the release etc. only from the maven-plugin and afterwards you have the release available and can continue with the rest which uses the release... Kind regards - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Shared Component: Maven Dependency Analyzer Version 1.5 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Shared Component: Maven Dependency Analyzer Version 1.5 http://maven.apache.org/shared/maven-dependency-analyzer/ Analyzes the dependencies of a project for undeclared or unused artifacts. org.apache.maven.shared maven-dependency-analyzer 1.5 Bugs: * [MSHARED-285] - Port tests to JUnit 4.11 * [MSHARED-307] - Performance: The implementation of DefaultClassAnalyzer unnecessarily scans jar files bodies * [MSHARED-323] - DefaultProjectDependencyAnalyzer does not correctly transform Files with Spaces to URLs * [MSHARED-327] - maven-dependency-analyzer not compatible with Java 8 Enjoy, -The Maven team Karl-Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven assembly and lifecycle binding
Hi, Do you have a single project or a multi module build? May be you have defined the configuration for maven-assembly-pugin in pluginManagement ? Furthermore you should only configured what is different from the defaults like appendAssemblyId which is by default true...so you can omit that. Kind regards Karl-Heinz Marbaise On 9/17/14 3:48 PM, Luis Villa wrote: Hello all, First of all, I must say I'm new to maven, so I don't have any expertise in the matter. I've made a web application and I'm capable of package it correctly. I have to add a user manual to the packaging, generating a zip that contains the war and the doc file. I've added maven-assembly-plugin to the pom.xml, and a custom packager that allows it. When I do: maven assembly:single The file is created correctly and with the desired content. The problem comes when I want to bind this step to the package phase. Following the examples, I've changed the plugin section in this manner: org.apache.maven.plugins maven-assembly-plugin true src/main/assembly/packager.xml withdocs package single Nevertheless, when I type "mvn package", the file is not created. Only the war is generated. When entering "mvn assembly:single", it keeps working correctly. What am I doing wrong? Thank you all in advance :) - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: lineEnding parameter makes assembly ignore empty directories
Hi, > I'm in front of a bug with the Assembly plugin. When I use the lineEndings property inside an assembly, the plugin start to ignore empty folders. If I remove the lineEnding property, then the plugin include empty folders again. Can you prepare a full working example may be on github which can reproduce the problem... I found that Jira about that bug: https://jira.codehaus.org/browse/MASSEMBLY-578. It seems to be an old ticket (2011) that was created for the version 2.2 of the plugin. I still have this bug with the version 2.4. Have you tried to use 2.4.1 ? Is there someone with a workaround for that bug? May it possible to have that bug resolved soon? What do you mean by soon? Kind regards Karl-Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Shared Component: Maven Dependency Tree Version 2.2 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Shared Component: Maven Dependency Tree Version 2.2 http://maven.apache.org/shared/maven-dependency-tree/ Analyzes the dependencies of a project for undeclared or unused artifacts. org.apache.maven.shared maven-dependency-tree 2.2 Bugs: * [MSHARED-326] - Patch that enables all maven-dependency-tree ITs * [MSHARED-336] - Create a method in the DependencyGraphBuilder that accepts the reactor projects to collect unbuilt dependencies Improvement: * [MSHARED-349] - Upgrade maven version to 2.2.1 Enjoy, -The Maven team Karl-Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Dependency Plugin Version 2.9 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Dependency Plugin, version 2.9 The dependency plugin provides the capability to manipulate artifacts. It can copy and/or unpack artifacts from local or remote repositories to a specified location. http://maven.apache.org/plugins/maven-dependency-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-dependency-plugin 2.9 Release Notes - Maven Dependency Plugin - Version 2.9 http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11214&version=19229 Bugs: * [MDEP-424] - Maven Dependency Plugin homepage should link to dependency:list-repositories * [MDEP-439] - maven-dependency-plugin not compatible with Java 8 * [MDEP-445] - dependency plugin fails with >9 threads * [MDEP-448] - NullPointerException when classifier sources was chosen Improvements: * [MDEP-443] - dependency tree should be the same when using verbose or not * [MDEP-450] - Add goal display-ancestors which will output the line of heritage for parent poms * [MDEP-457] - Enhanced documentation for includeArtifactIds and includeGroupIds * [MDEP-459] - Update maven-dependency-analyzer to 1.5 * [MDEP-460] - Removed dependency plexus-container-default:1.0-alpha-9-stable-1 * [MDEP-461] - Upgrade plexus-archiver to 2.4.4 * [MDEP-462] - Upgrade to Maven Dependency Tree version 2.3 * [MDEP-463] - Fix RAT Report * [MDEP-464] - Upgrade maven-invoker 2.0.11 to 2.1.1 New Feature: * [MDEP-427] - Add user property for addParentPoms option Tasks: * [MDEP-227] - Bump to Doxia 1.1.1 * [MDEP-452] - Use mock repository manager for ITs * [MDEP-453] - Change Maven prerequisite to 2.2.1 Enjoy, -The Apache Maven team Karl-Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Clean Plugin Version 2.6 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Clean Plugin, version 2.6 The Clean Plugin is used when you want to remove files generated at build-time in a project's directory. http://maven.apache.org/plugins/maven-clean-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-clean-plugin 2.6 Release Notes - Maven Clean Plugin - Version 2.6 http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11214&version=19229 Bug: * [MCLEAN-52] - Use new annotations Improvement: * [MCLEAN-57] - Set prerequisites to Maven 2.2.1 Enjoy, -The Apache Maven team Karl-Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven Setup Problem
Hi Doug, On 9/26/14 5:27 PM, Doug Johnson wrote: http://maven.apache.org/SETTINGS/1.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd";> c:/Documents and Settings/djohns2/.m2/repository If this really is what you are using i would suggest to check the end tag of localRepository cause an end tag should look like this: Kind regards Karl-Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven site:deploy hosting providers??
Hi Kevin, have you considered github ? Kind regards Karl-Heinz Marbaise On 9/27/14 8:21 AM, Kevin Burton wrote: This is such an obviously problem I’m amazed there isn’t an easier solution. Bintray looks cool. I just asked them how they feel about static site hosting? I want something that works with mvn site:deploy On Fri, Sep 26, 2014 at 10:49 PM, Manfred Moser wrote: If you just want to have the sites hosted any hosting solution will do it. CDN will be more expensive but I would really wonder if you need that for a static site. You would have to get a LOT of traffic to make it worth it. Bintray focuses on binary distribution and not site hosting. If you want both you could even just run Nexus OSS on any server and host the binaries and the site using a Maven repository for the binaries and a site repository for the site.. manfred Bernd wrote on 26.09.2014 17:41: Have a look at bintray https://bintray.com/docs/uploads/uploads_uploads.html Greetings Bernd Am 26.09.2014 21:39 schrieb "Kevin Burton" : I don’t want to necessarily host our own repositories. They’re just static file repositories. Are there any hosting providers out there that support dav, SCP or HTTP PUT that would work with wagon? Required features are: - SSL - redundant copies on multiple servers (CDN) - dav/scp/ftp/ upload.. anything supported by wagon. - HTTP auth - domain masking … I just want something easy to setup and then never worry about it again. -- Founder/CEO Spinn3r.com Location: *San Francisco, CA* blog: http://burtonator.wordpress.com … or check out my Google+ profile <https://plus.google.com/102718274791889610666/posts> <http://spinn3r.com> - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Surefire and testing plugin issue
Hi, >> Hi, I am using maven-surefire-plugin version 2.17 and testng plugin version 6.3.1 (jdk version is 1.7 ). so ok so far you are using maven-surefire-plugin 2.17 and have configured a dependency to testng in version 6.3.1? First why are you using such an old version of TestNG..(2011?)... Furthermore there is no testng plugin Can you show your pom file which you are using otherwise it's hard to guess what's wrong... Some of our tests are failing and in the testng-results.xml file it is reported as fail. The issue is "maven" is reporting the failed tests as "skipped" and the final build status is SUCCESS. Has anyone faced this issue ? if so what is the soln. I tried with "surefire-testng" plugin instead of "testng" plugin. With this change, maven is properly reporting the failed tests and the final build is reported as FAIL What is the difference between testng and surefire-testng plugin , I don't see any mention in the surefire plugin page, so I am not sure if it is correct to use this plugin. Any help is appreciated Kind regards Karl-Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Surefire and testing plugin issue
Hi,
>
This is the testng plugin version mentioned in maven-surefire-plugin page.
http://maven.apache.org/surefire/maven-surefire-plugin/examples/testng.html
This is not a plugin it's simply the dependency which you should have in
your project if you are using TestNG...
I tried with the latest 6.8.8 and the issue still exists.
...
...
...
...
...
org.apache.maven.plugins
maven-surefire-plugin
2.17
...
...
...
org.testng
testng
6.3.1
test
Thanks,
Subbu
Ah...
Using dependencyManagement is intended to define versions...but it will
not define a real dependency...
If you need have a dependency you need to add the following in your pom
file:
org.testng
testng
...
This is the indicator for maven-surefire-plugin to use the appropriate
TestNG driver withn surefire to run tests with TestNG..
On Sat, Sep 27, 2014 at 8:54 PM, Karl Heinz Marbaise mailto:khmarba...@gmx.de>> wrote:
Hi,
>> Hi,
I am using maven-surefire-plugin version 2.17 and testng
plugin version
6.3.1 (jdk version is 1.7 ).
so ok so far you are using maven-surefire-plugin 2.17 and have
configured a dependency to testng in version 6.3.1?
First why are you using such an old version of TestNG..(2011?)...
Furthermore there is no testng plugin
Can you show your pom file which you are using otherwise it's hard
to guess what's wrong...
Some of our tests are failing and in the
testng-results.xml file it is reported as fail. The issue is
"maven" is
reporting the failed tests as "skipped" and the final build
status is
SUCCESS.
Has anyone faced this issue ? if so what is the soln.
I tried with "surefire-testng" plugin instead of "testng"
plugin. With
this change, maven is properly reporting the failed tests
and the final
build is reported as FAIL
What is the difference between testng and surefire-testng
plugin , I don't
see any mention in the surefire plugin page, so I am not
sure if it is
correct to use this plugin.
Any help is appreciated
Kind regards
Karl-Heinz Marbaise
Kind regards
Karl-Heinz Marbaise
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven site:deploy hosting providers??
Hi, > we have scm-publish plugin for that http://maven.apache.org/plugins/maven-scm-publish-plugin/ I've already used that for GitHub pages...works like a charm... https://github.com/khmarbaise/smpp https://github.com/khmarbaise/uptodate-maven-plugin etc. which makes it very ease... apart from that you can use github-site-plugin which works as well... https://github.com/github/maven-plugins Kind regards Karl-Heinz Marbaise Regards, Hervé Le samedi 27 septembre 2014 10:09:35 Kevin Burton a écrit : I don't think github would work but would love to be wrong. Their static page hosting is acceptable but it's tricky to make sure all pages get added and removed properly. Their binary hosting uses their own proprietary api which isn't supported by wagon. On Sep 27, 2014 4:49 AM, "Jason van Zyl" wrote: I believe there are tools that will allow you to publish your static site to Github pages. On Sep 27, 2014, at 2:21 AM, Kevin Burton wrote: This is such an obviously problem I’m amazed there isn’t an easier solution. Bintray looks cool. I just asked them how they feel about static site hosting? I want something that works with mvn site:deploy On Fri, Sep 26, 2014 at 10:49 PM, Manfred Moser wrote: If you just want to have the sites hosted any hosting solution will do it. CDN will be more expensive but I would really wonder if you need that for a static site. You would have to get a LOT of traffic to make it worth it. Bintray focuses on binary distribution and not site hosting. If you want both you could even just run Nexus OSS on any server and host the binaries and the site using a Maven repository for the binaries and a site repository for the site.. manfred Bernd wrote on 26.09.2014 17:41: Have a look at bintray https://bintray.com/docs/uploads/uploads_uploads.html Greetings Bernd Am 26.09.2014 21:39 schrieb "Kevin Burton" : I don’t want to necessarily host our own repositories. They’re just static file repositories. Are there any hosting providers out there that support dav, SCP or HTTP PUT that would work with wagon? Required features are: - SSL - redundant copies on multiple servers (CDN) - dav/scp/ftp/ upload.. anything supported by wagon. - HTTP auth - domain masking … I just want something easy to setup and then never worry about it again. -- Founder/CEO Spinn3r.com Location: *San Francisco, CA* blog: http://burtonator.wordpress.com … or check out my Google+ profile <https://plus.google.com/102718274791889610666/posts> <http://spinn3r.com> - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Founder/CEO Spinn3r.com Location: *San Francisco, CA* blog: http://burtonator.wordpress.com … or check out my Google+ profile <https://plus.google.com/102718274791889610666/posts> <http://spinn3r.com> Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io - the course of true love never did run smooth ... -- Shakespeare - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven JXR 2.4 site.
Hi James, On 9/29/14 6:11 PM, James Nord (jnord) wrote: Hi all, The default google page when you search for maven-jxr-plugin is http://maven.apache.org/plugins/maven-jxr-plugin/ which is version 2.3 rather than the up-to-date http://maven.apache.org/jxr/maven-jxr-plugin/ This confused me for a while and probably will other users. Is there any chance that a redirect could be added for the out-of-date page (or it being replaced/removed)? I have created a redirect http://maven.apache.org/plugins/maven-jxr-plugin/ to http://maven.apache.org/jxr/which should solve the problem... can you check this... Kind regards Karl-Heinz Marbaise /James -Original Message- From: Michael Osipov [mailto:micha...@apache.org] Sent: 20 December 2013 12:44 To: annou...@maven.apache.org; users@maven.apache.org Cc: Maven Developers List Subject: [ANN] Apache Maven JXR 2.4 released The Apache Maven team is pleased to announce the release of the Apache Maven JXR, version 2.4 This module generates browsable HTML pages from Java source code. http://maven.apache.org/jxr/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-jxr-plugin 2.4 Release Notes - Maven JXR - Version 2.4 ** Bug * [JXR-63] - Bottom line in jxr report does not correspond to Javadoc style * [JXR-85] - JXR generates files with inconsistent line ending style * [JXR-93] - aggregate goal creates blank top-level report * [JXR-96] - [PATCH] JXR Comment handling has several shortcomings * [JXR-103] - All DTD XHTML 1.0 Transitional references are incorrect ** Improvement * [JXR-61] - Include bottom text in all pages * [JXR-87] - Change line number anchor name pattern * [JXR-99] - Improve linguistic style of bottom * [JXR-104] - Remove NOTICE footer/bottom altogether because no other writes this one too * [JXR-106] - Remove Maven 1.x from docs ** Task * [JXR-94] - use the maven-plugins pom as the parent of the maven-jxr-plugin Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven JXR 2.4 site.
Hi James, On 9/30/14 9:39 AM, James Nord (jnord) wrote: Sorry don’t know what happened with my mailer there - hadn't finished writing and wasn't ready for sending. The re-direct works - but shouldn't it redirect to the plugin page rather than the top level jxr page? ie. Would the redirect not be better as http://maven.apache.org/plugins/maven-jxr-plugin/ -> http://maven.apache.org/jxr/maven-jxr-plugin/ has been done by Hervé Boutemy...he improved my redirect. Thanks Hervé... Kind regards Karl-Heinz Marbaise Anyway - thanks for setting this up - will certainly help me in a few months when I forget about it again :) /James I have created a redirect http://maven.apache.org/plugins/maven-jxr-plugin/ to http://maven.apache.org/jxr/which should solve the problem... can you check this... The redirect works - but it sredirect to the plugin page (http://maven.apache.org/jxr/maven-jxr-plugin/) rather than the top level jxr? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Resources Plugin Version 2.7 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Resources Plugin, version 2.7 The Resources Plugin handles the copying of project resources to the output directory. http://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 2.7 Release Notes - Maven Resources Plugin - Version 2.7 http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11145&version=18645 Bug: * [MRESOURCES-182] - Example Custom resource filters incorrect Improvements: * [MRESOURCES-177] - Use version 1.2 of maven-filtering to use improvements * [MRESOURCES-180] - Documentation does not use correct versions * [MRESOURCES-181] - MavenProject/MavenSession Injection as a paremeter instead as a component. * [MRESOURCES-183] - Upgrade to Maven 2.2.1 compatiblity * [MRESOURCES-184] - Removing plexus-container-default dependency Enjoy, -The Apache Maven team Karl-Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: isssue with the deploy plugin
Hi, first question. Why would you like to use git as a Maven repository ? git is not intended to use that way (neither other version control tools as well). There serveral alternatives like Artifactory, Nexus and Archiva... Kind regards karl-Heinz Marbaise On 10/4/14 9:57 PM, sameer chandekar wrote: Hi , I am in process of implementing continuous integration. I amUsing GIT repository to manage source code. I've created a project using apache maven . In POM.xml file I've included distribution management tag and specified the path to remote repository where I want to store my builds generated by maven. GIT GIT repository https://github.com/sameerchandekar/deploy.git now when I execute the deploy goal i get following error INFO] --- maven-deploy-plugin:2.7:deploy (default-deploy) @ KEDB --- Downloading: https://github.com/sameerchandekar/deploy.git/com/kedb/KEDB/0.0.1-SNAPSHOT/maven-metadata.xml Uploading: https://github.com/sameerchandekar/deploy.git/com/kedb/KEDB/0.0.1-SNAPSHOT/KEDB-0.0.1-20141005.131802-1.war Uploading: https://github.com/sameerchandekar/deploy.git/com/kedb/KEDB/0.0.1-SNAPSHOT/KEDB-0.0.1-20141005.131802-1.pom [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 13.868s [INFO] Finished at: Sun Oct 05 01:18:09 GMT-12:00 2014 [INFO] Final Memory: 8M/21M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project KEDB: Failed to deploy artifacts: Could not find artifact com.kedb:KEDB:war:0.0.1-20141005.131802-1 in GIT ( https://github.com/sameerchandekar/deploy.git) -> [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/MojoExecutionException Here it is unable to download maven-metadata.xml and unable to upload war and pom files. Here the repository I created i.e https://github.com/sameerchandekar/deploy.git is not comtaining any files. This same goal if I execute by specifying the path of repository as local file system path it will work fine. see the logs below for successfull cases where the repository specified is file system path [INFO] --- maven-deploy-plugin:2.7:deploy (default-deploy) @ KEDB --- Downloading: file:///E:/itworkshere/com/kedb/KEDB/0.0.1-SNAPSHOT/maven-metadata.xml Downloaded: file:///E:/itworkshere/com/kedb/KEDB/0.0.1-SNAPSHOT/maven-metadata.xml (762 B at 74.4 KB/sec) Uploading: file:///E:/itworkshere/com/kedb/KEDB/0.0.1-SNAPSHOT/KEDB-0.0.1-20141005.132612-2.war Uploaded: file:///E:/itworkshere/com/kedb/KEDB/0.0.1-SNAPSHOT/KEDB-0.0.1-20141005.132612-2.war (123 KB at 1205.4 KB/sec) Uploading: file:///E:/itworkshere/com/kedb/KEDB/0.0.1-SNAPSHOT/KEDB-0.0.1-20141005.132612-2.pom Uploaded: file:///E:/itworkshere/com/kedb/KEDB/0.0.1-SNAPSHOT/KEDB-0.0.1-20141005.132612-2.pom (2 KB at 1418.9 KB/sec) Downloading: file:///E:/itworkshere/com/kedb/KEDB/maven-metadata.xml Downloaded: file:///E:/itworkshere/com/kedb/KEDB/maven-metadata.xml (272 B at 66.4 KB/sec) Uploading: file:///E:/itworkshere/com/kedb/KEDB/0.0.1-SNAPSHOT/maven-metadata.xml Uploaded: file:///E:/itworkshere/com/kedb/KEDB/0.0.1-SNAPSHOT/maven-metadata.xml (762 B at 372.1 KB/sec) Uploading: file:///E:/itworkshere/com/kedb/KEDB/maven-metadata.xml Uploaded: file:///E:/itworkshere/com/kedb/KEDB/maven-metadata.xml (272 B at 265.6 KB/sec) [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 2.082s [INFO] Finished at: Sun Oct 05 01:26:12 GMT-12:00 2014 [INFO] Final Memory: 7M/20M [INFO] Please help to resolve this issue . Thanks , Sameer Chandekar - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Problem with the resource-plugin v2.7 and nonFilteredFileExtensions
Hi, first thanks for going so fast to a new version and finding this issue...if it really is one... On 10/6/14 12:04 PM, Michael Lemler wrote: Hi there, we just tried to update our usage of the maven-resource-plugin to Version 2.7 but afterwards the build failed with the following error message: Failed to execute goal org.apache.maven.plugins:maven-resource-plugin:2.7:resource (default resources) on project XYZ: Mark invalid -> [Help 1] I assume that you are using filtering apart from that I assume you are filtering files which should not being filtered cause this means files are being filtered which have encoding characters which can't correctly copied.. (filtered). I can reproduce the problem if i miss to add an .img extension to my pom file, cause .img is a kind of binary file which is being filtered but should NOT... If i add the appropriate img It works without any problem... Please check the failing build via mvn -X output and search for the filtering locations in the output...like the following: [DEBUG] ignoreDelta true [INFO] Copying 3 resources [DEBUG] file duke-beerjpg.img has a filtered file extension [DEBUG] filtering /Users/kama/apache-maven/maven-plugins/maven-resources-plugin/target/it/possible-bug/src/main/resources/duke-beerjpg.img to /Users/kama/apache-maven/maven-plugins/maven-resources-plugin/target/it/possible-bug/target/classes/duke-beerjpg.img In this case i have a file duke-beerjpg.img which is filtered but should not being filter which is causing the failure... In this case it means that i have to fix my build and add the appropriate nonFilteredFileExtension...to prevent filtering of such files... While my researches I could not find any changes to the usage of this. So I wonder if there is a bug in the new version or if we did anything wrong. It works fine with Version 2.4. and 2.6. >Here the code of our pom file. org.apache.maven.plugins maven-resources-plugin 2.7 woff eot ttf svg Thanks a lot for the help! And best regards Michael Michael Lemler. Software Engineer. Kind regards Karl-Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Best practice for integration tests (vs unit tests)
Hi Kevin, the best suggestion i can give is simply make a separate module where the integration tests should be moved to... This has the advantage having different location for them, cause they are more than unit tests which is expressed by using a separate module furthermore you have the configuration for the integration test within a separate module which is more flexible this includes the configuration of maven-failsafe-plugin as well. maven-failsafe-plugin should be used cause it supports a different naming schema for your integration tests (*IT.java see docs of maven-failsafe-plugin) and you can check the results of the integration tests via maven-failsafe-plugin:verify separately...and break the build if you like... Apart from the above integration tests should run at an other phase (pre-integration-test,integration-test, post-integration) and NOT in test phase...which is handled by maven-failsafe-plugin (see docs http://maven.apache.org/surefire/maven-failsafe-plugin/usage.html) So if you like to run your unit tests parallel you can configure the maven-surefire-plugin which does not influence your integration tests... I would also suggest to put the integration tests into src/test/java within the separated module Kind regards Karl-Heinz Marbaise On 10/8/14 1:28 AM, Kevin Burton wrote: Right now I have an overlap of unit and integration tests and I want to tear out my integration tests and keep them separate. This way our unit tests execute fast and integration testing takes a bit longer. … and now I’m trying to figure out the best strategy for that. Reading this: http://docs.codehaus.org/display/MAVENUSER/Maven+and+Integration+Testing seems to not solve the problem. Seems to me the easiest would be to just have src/main/integration-tests … but would I have to use failsafe or surefire? I’m not sure why I would need another plugin for this. Maybe someone can enlightenment me with some maven wisdom? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Running integration tests
Hi Robert, On 10/6/14 11:31 AM, Robert Mark Bram wrote: Hi All, A couple of questions about integration tests.. 1) Default vs non-default plugins I needed to include the maven-failsafe-plugin plugin to introduce integration tests into my project, but I didn't need to introduce the maven-surefire-plugin to my pom.xml for unit tests. Fair enough, but how do I know which plugins are included by default? This can be read here: http://maven.apache.org/ref/3.1.1/maven-core/default-bindings.html There you can see for which packaging type which plugins are bound to the particular life cycle phases... 2) Just run integration tests? I can see that unit tests are all classes with names like *Test.java and integration tests are all classes with names like IT.java. But mvn verify and mvn test seem to run all tests (unit and integrations). Is there a way to run just one or the other? mvn test should not run integration tests...if it will so you have configured it wrong and not used maven-failsafe-plugin and bound to the wrong life cycle...cause the phases: pre-integration-test, integration-test and post-integration-test ran after package phase... So they will only be reached if you do mvn verify If you like to run only integration tests you can do this via configuring maven-surefire-plugin with a parameter skip... mvn -Dskip.unit.tests=true verify which will skip the unit tests but run the integration tests... 3) Run integration tests after compile? The real reason for question 2 is that I wish to run integration tests only after I have deployed the new application to ensure the integration tests run on the server with the new content. Is there a way to do this? Based on the life cylce this is guaranteed... Thanks for any assistance! You're welcome... Kind regards Karl-Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Why do running modules in parallel take longer to execute than running them in sequence?
Hi,
have paid attention to forkCount ? How did you set it?
How many core's do you have ?
On 10/8/14 8:44 PM, laredotornado-3 wrote:
Hi,
I’m using Maven 3.2.3, Spring 3.2.11.RELEASE, JUnit 4.11, Java 6, and the
Surefire/Failsafe 2.17 plugins. I’m trying to figure out why when running a
couple of modules in parallel, it takes much longer than when I run them
individually. I’m trying to figure out ways to speed up my build. I have
this in my parent pom …
core
…
module-x
module-y
When I run “mvn clean install -T 4”, modules “module-x” and “module-y” run
in parallel. Both have a number of integration tests, all using
@RunWith(SpringJUnit4ClassRunner.class)
@ContextConfiguration({ "classpath:test-context.xml" })
public class MyServiceIT
{
Below are my surefire/failsafe configurations …
org.apache.maven.plugins
maven-surefire-plugin
2.17
true
-Xmx2048m
-XX:MaxPermSize=512M
${skipAllTests}
org.apache.maven.plugins
maven-failsafe-plugin
2.17
true
-Xmx4096m
-XX:MaxPermSize=512M
${skipAllTests}
integration-test
verify
When I run the tests in parallel, the modules take 11 minutes and 13
minutes, respectively, to run. However, running them concurrently (without
the “-T” option), they execute in 6 minutes and 9 minutes, respectively.
I’m confused about why they take so much longer to run when they both run at
the same time and was hoping some folks could suggest some ways I can
troubleshoot this further.
Kind regards
Karl-Heinz Marbaise
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Eclipse Luna and M2Extra
Hi Dan, which version of m2e have you installed ? Kind regards Karl Heinz Marbaise On 10/10/14 3:41 AM, Dan Tran wrote: I am try to install m2extra with eclipse luna using http://ifedorenko.github.com/m2e-extras/ Is it still a valid updatesite, I am running into dependency issue error is Installing com.ifedorenko.m2e.mavendev.feature.feature.group 0.3.0.201410040035. Cannot complete the install because one or more required items could not be found.Installation failed. Software being installed: Maven Development Tools 0.3.0.201410040035 (com.ifedorenko.m2e.mavendev.feature.feature.group 0.3.0.201410040035) Missing requirement: Maven Development Tools 0.3.0.201409160039 (com.ifedorenko.m2e.mavendev 0.3.0.201409160039) requires 'bundle org.eclipse.m2e.workspace.cli 0.1.0' but it could not be found Cannot satisfy dependency: From: Maven Development Tools 0.3.0.201410040035 (com.ifedorenko.m2e.mavendev.feature.feature.group 0.3.0.201410040035) To: com.ifedorenko.m2e.mavendev [0.3.0.201409160039] Any help is very much appreciated - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Source Plugin Version 2.4 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Source Plugin, version 2.4 The Resources Plugin handles the copying of project resources to the output directory. http://maven.apache.org/plugins/maven-source-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-source-plugin 2.4 Release Notes - Maven Source Plugin - Version 2.4 http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11147&version=20597 Improvements: * [MSOURCES-71] - MavenProject/MavenSession Injection as a paremeter instead as a component. * [MSOURCES-72] - Upgrade to Maven 2.2.1 compatiblity * [MSOURCES-73] - Update version of plexus-archiver to 2.6.1 * [MSOURCES-74] - Upgrade to plexus-archiver 2.6.3 Enjoy, -The Apache Maven team Karl Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Linkcheck Plugin Version 1.2 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Linkcheck Plugin, version 1.2 This plug-in allows you to generate a Linkcheck report of your project's documentation using the Doxia Linkcheck Tool. http://maven.apache.org/plugins/maven-linkcheck-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-linkcheck-plugin 1.2 Release Notes - Maven Linkcheck Plugin - Version 1.2 http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=12100&version=16906 Improvements: * [MLINKCHECK-12] - MavenProject/MavenSession Injection as a paremeter instead as a component. * [MLINKCHECK-13] - Upgrade to Maven 2.2.1 compatiblity * [MLINKCHECK-14] - Upgrade maven-invoker 2.0.9 to 2.1.1 * [MLINKCHECK-15] - Update maven-reporting-impl to 2.3 * [MLINKCHECK-16] - Update version of plexus-utils to 3.0.18 * [MLINKCHECK-17] - Upgrade plexus-i18n to 1.0-beta-10 Task: * [MLINKCHECK-11] - use maven-plugin-tools' java 5 annotations Enjoy, -The Apache Maven team Karl Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Enum-type parameters in Guide to Developing Java Plugins
Hi Gerold, > Hi, While searching for something completely different I stumbled across Support Enum-type parameters in mojos - http//jira.codehaus.org/browse/MNG-4292. If that had been in the Guide to Developing Java Plugins - https://maven.apache.org/guides/plugin/guide-java-plugin-development.html I'd realized it much earlier. Correct...it's simply missing on the site...so we should fix it... Where would you suggest to put this kind of information ? within this page ... Before Arrays ? Kind regards Karl Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Enum-type parameters in Guide to Developing Java Plugins
Hi Gerold, you can take a look on the changed docs here: http://maven.staging.apache.org/guides/plugin/guide-java-plugin-development.html If you have any suggestion/improvements please don't hesitate to contact me directly or via this mailing list... On 10/11/14 8:15 PM, Karl Heinz Marbaise wrote: Hi Gerold, > Hi, While searching for something completely different I stumbled across Support Enum-type parameters in mojos - http//jira.codehaus.org/browse/MNG-4292. If that had been in the Guide to Developing Java Plugins - https://maven.apache.org/guides/plugin/guide-java-plugin-development.html I'd realized it much earlier. Correct...it's simply missing on the site...so we should fix it... Where would you suggest to put this kind of information ? within this page ... Before Arrays ? Kind regards Karl Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven WAR Plugin Version 2.5 Released
The Apache Maven team is pleased to announce the release of the Apache Maven WAR Plugin, version 2.5 The WAR Plugin is responsible for collecting all artifact dependencies, classes and resources of the web application and packaging them into a web application archive. 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.5 Release Notes - Maven WAR Plugin - Version 2.5 http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11150&version=19421 Bugs: * [MWAR-305] - Filtering doesn't work as expected after switching from maven-filtering:1.0-beta-2 to maven-filtering:1.1 * [MWAR-306] - [regression] Filtering doesn't work if a lone @ is found in a line to interpolate * [MWAR-311] - Filtering of resources broken in version 2.4 * [MWAR-312] - Document about Skinny War might need update Improvements: * [MWAR-313] - Upgrade maven-filtering to 1.2 * [MWAR-316] - MavenProject/MavenSession Injection as a paremeter instead as a component. * [MWAR-317] - Upgrade to Maven 2.2.1 compatiblity * [MWAR-319] - Fix RAT Report * [MWAR-320] - Update version of plexus-archiver to 2.6.1 * [MWAR-321] - Upgrade plexus archiver to 2.6.3 * [MWAR-322] - Removed dependency plexus-container-default:1.0-alpha-9-stable-1 * [MWAR-323] - Upgrade xstream version to 1.4.4 * [MWAR-324] - Upgrade plexus-io to 2.1.3 * [MWAR-325] - Fixed CPD / Checkstyle WARNINGS Task: * [MWAR-302] - Use the maven-mapping shared component Enjoy, -The Apache Maven team Karl Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Request for functionality in maven-assembly-plugin - ignoreProjectBuildFilters
Hi Tony,
I have taken a look into your patch...looks ok...
This looks like a usefull enhancement so I will integrate your patch...
I have created an appropriate JIRA entry:
http://jira.codehaus.org/browse/MASSEMBLY-717
Kind regards
Karl Heinz Marbaise
On 10/13/14 1:09 AM, Tony Jewell wrote:
Hi,
We hit an issue when using maven-assembly-plugin:2.4.1.
We were using filters in assemblies to filter config property files
according to the assembly we were producing - thus targetting our
various environments.
In the Project Build we defined test filter sources for tests and
running in the IDE.
Unfortunately, the default action in maven-assembly-plugin is to include
all ${project.build.filters} - before the filters defined in the
Assembly configuration. This meant all our assemblies had the Test configs.
I have attached an example project that displays the issue and a patch
to the current trunk maven-assembly-plugin:2.4.2-SNAPSHOT.
A snippet from sample pom.xml showing the proposed new
ignoreProjectBuildFilters config boolean usage is:
org.apache.maven.plugins
maven-assembly-plugin
${maven-assembly-plugin.version}
prod-assemble
package
single
false
src/main/filters/prod.properties
src/main/assemblies/prod-assemble.xml
Thanks,
Tony Jewell
Cregganna Computer Consultants Ltd
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Request for functionality in maven-assembly-plugin - ignoreProjectBuildFilters
Hi Tony, On 10/13/14 8:38 AM, Tony Jewell wrote: Thanks Karl, Two things: 1. I couldn't get access to the JIRA to submit a ticket myself - is this something I am allowed to request? 2. Of course I'm going to ask: when is maven-assembly-plugin:2.4.2 likely to be released? It's likely that this week a release will be done which is called 2.5 ...if nothing really hard will happen... we will see... Kind regards Karl Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Shared Component: Maven Filtering Version 1.3 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Shared Component: Maven Filtering Version 1.3 The goal is to provide a shared component for all plugins that needs to filter resources. http://maven.apache.org/shared/maven-filtering/ You should specify the version in your project's plugin configuration: org.apache.maven.shared maven-filtering 1.3 Release Notes - Maven Filtering - Version 1.3 http://jira.codehaus.org/secure/ReleaseNote.jspa?version=20184&styleName=Text&projectId=11761 Bug: * [MSHARED-325] - maven-filtering 1.2 throws MavenFilteringException: Mark invalid Improvements: * [MSHARED-351] - Update version of plexus-interpolation to 1.19 * [MSHARED-352] - Update version of plexus-utils to 3.0.18 * [MSHARED-353] - Upgrade maven-shared-utils to 0.6 * [MSHARED-354] - Removed dependency plexus-container-default:1.0-alpha-9-stable-1 * [MSHARED-355] - Upgrade to Maven 2.2.1 compatiblity * [MSHARED-366] - Add ability to do Stream/Reader based filtering Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Shared Component: Maven Shared Utils Version 0.7 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Shared Component: Maven Shared Utils Version 0.7 This project aims to be a functional replacement for plexus-utils in Maven. It is not a 100% API compatible replacement though but a replacement with improvements: lots of methods got cleaned up, generics got added and we dropped a lot of unused code. http://maven.apache.org/shared/maven-shared-utils/ You should specify the version in your project's plugin configuration: org.apache.maven.shared maven-shared-utils 0.7 Release Notes - Apache Maven Shared Utils - Version 0.7 http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&version=20207 Bugs: * [MSHARED-242] - [shared-utils] improve shared utils featuers and introduce generics where possible * [MSHARED-313] - port dotted expression parser fixes from plexus-utils * [MSHARED-369] - ReflectionValueExtractor regression; incorrect parsing Improvement: * [MSHARED-364] - Use NIO Delete when possibly in deleteFiles New Features: * [MSHARED-330] - add StringUtils.endsWithIgnoreCase() Wish: * [MSHARED-257] - extract merge feature from Xpp3Dom Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Client-side SSL certifcates and Maven
Hi, may be i miss a thing but wagon can be configured outside of maven via extensions ... ... org.apache.maven.wagon wagon 2.7 ... shouldn't that work too? Kind regards Karl Heinz Marbaise On 11/2/14 7:53 PM, Jeroen Hoek wrote: Some further research on my part shows that a simple connection test using HttpComponents httpclient 4.3.5 does work, but that the version of httpclient used in Wagon 2.6 (httpclient 4.3.1) fails. Apparently the newer version of httpclient fixes the problem I ran into, although I do not know what the problem is exactly. For completeness sake: the simple connection test with httpclient 4.3.5 I used: https://gist.github.com/jdhoek/192a965fc63f459b2bee As it turns out, Wagon 2.7 already uses httpclient 4.3.5. A custom build of Maven 3.2.3 with the Wagon dependency set to 2.7 works! When will a version of Maven 3.2.x built with Wagon 2.7 be released? Is something blocking Maven from depending on Wagon 2.7? 2014-10-29 16:14 GMT+01:00 Jeroen Hoek : Hello, I am trying to get Maven (3.2.2) to work with an instance of Archiva hosted behind a webserver secured with client-side SSL certificates. I have followed the guide at https://maven.apache.org/guides/mini/guide-repository-ssl.html, and imported the server-side SSL certificate into a Java .jks file. The client-side certificate is a PKCS12 file, which works correctly in Firefox and Chromium. I have a simple project that depends on an artifact hosted on my Archiva server. When client-side SSL verification is disabled on the server, `mvn clean install` works as expected, and the dependency is downloaded. But it doesn't work when I activate client-side SSL verification, and try the following command: mvn clean install -Djavax.net.debug=ssl -Djavax.net.ssl.trustStore=PATH_TO_TRUSTDB.jks -Djavax.net.ssl.trustStorePassword= -Djavax.net.ssl.keyStore=PATH_TO_MY_CERT.p12 -Djavax.net.ssl.keyStoreType=pkcs12 -Djavax.net.ssl.keyStorePassword= From what I can see in the output, my .p12 file is read by Maven at the start, as is the trust-store, but it fails to complete requests to the Archiva server, although TLS handshaking appears to work, so the server-side certificate is trusted and accepted. The server throws the "400: No required SSL certificate was sent" error message you get when trying to talk to it without a client-side SSL certificate installed. In the server log I am indeed seeing HTTP GET requests from Maven without any client-side SSL certificate, whereas GETs by a browser do show access with the valid certificate there. Any idea why Maven isn't using the client-side SSL certificate passed via -Djavax.net.ssl.keyStoreType? Is there some configuration option I am overlooking? Kind regards, Jeroen Hoek Lable - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Clean Plugin Version 2.6.1 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Clean Plugin, version 2.6.1 The Clean Plugin is used when you want to remove files generated at build-time in a project's directory. http://maven.apache.org/plugins/maven-clean-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-clean-plugin 2.6.1 Release Notes - Maven Clean Plugin - Version 2.6.1 Bugs: * [MCLEAN-47] - On windows if there are junctions on the cleaned directories, clean deletes .* resources under junction's target along with junction. * [MCLEAN-55] - maven clean seems to use old java.io API to clean the target directory * [MCLEAN-58] - Maven Clean Plugin ignores followSymLinks parameter on Windows Improvements: * [MCLEAN-59] - Upgrade maven-plugins-testing-harness from 1.1 to 1.3 * [MCLEAN-60] - Fixed Checkstyle reported errors / warnings * [MCLEAN-61] - Upgrade to org.apache.maven.plugins:maven-plugins:26 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: explicit dependencies in maven
Hi, to be clear on that point you should never change released versions. The idea of releases is that they are immutable. The scenario you have described should never be done which means: If you change code than make simply a new version like 1.2 or may be better things like 1.1.1 to show it's a bug fix release of 1.1 etc. You should prevent of doing developers such a thing... Apart Kind regrards Karl Heinz Marbaise On 11/4/14 6:06 AM, Irfan Sayed wrote: so, lets say if i am using x dependency with version 1.1 and if the developer changes the code of that dependency, keeping the same version as 1.1 then nexus will not download the latest code changes for that dependency because the version still refers to 1.1 ??? if that is the case, this is really nice regards On Tue, Nov 4, 2014 at 10:20 AM, Ron Wheeler wrote: Have you scanned the Maven books referenced on the Maven web site? Best starting place. With a repository (Nexus), people are prevented from deploying the same version twice so you are guaranteed that if you build with version 2.3.15 of ourNiceUtility, you will always get the same code. The repo will simply not allow them to overwrite version 2.3.15 once it is deployed into the wild(public). Beats firing developers but stops them from doing silly things. On 03/11/2014 11:33 PM, Irfan Sayed wrote: hello, is there any good doc/blog which describes the handling of explicit declaration of dependencies. when we build the code, we use certain dependencies , how we can make sure that when we reproduce the same build after the gap of 6 months , same and exact dependencies will be used. ??? i know we can have artifactory/nexus , but that does not guarantee the exact version of dependency when developer changes the code and make it public keeping the version same please suggest regards - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven JXR Version 2.5 Released
The Apache Maven team is pleased to announce the release of the Apache Maven JXR, version 2.5 This module generates browsable HTML pages from Java source code. http://maven.apache.org/jxr/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-jxr-plugin 2.5 Release Notes - Maven JXR - Version 2.5 Bug: * [JXR-122] - apache-rat-plugin Configuration for DEPENDENCIES file. Improvements: * [JXR-111] - Upgrade to Maven 2.2.1 compatiblity * [JXR-112] - Update version of plexus-utils to 3.0.20 * [JXR-113] - Update maven-reporting-impl to 2.3 * [JXR-114] - Remove deprecated marked entries in the code. * [JXR-115] - Fix WARNING for maven-surefire-plugin and duplicate test output.. * [JXR-116] - Upgrade doxia from 1.2 to 1.4 * [JXR-118] - Fixed Checkstyle reported errors/warnings * [JXR-119] - Upgrade org.apache.maven:maven-parent to version 25 * [JXR-120] - Configure maven release plugin to autoVersionSubmodules * [JXR-121] - Release failed * [JXR-123] - Upgrade maven-plugin-annotations and maven-plugin-plugin from 3.2 to 3.3 Task: * [JXR-109] - use maven-plugin-tools' java 5 annotations Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: explicit dependencies in maven
Hi, On 11/5/14 11:14 PM, Barrie Treloar wrote: On 6 November 2014 05:37, Karl Heinz Marbaise wrote: Hi, to be clear on that point you should never change released versions. The idea of releases is that they are immutable. The scenario you have described should never be done which means: If you change code than make simply a new version like 1.2 or may be better things like 1.1.1 to show it's a bug fix release of 1.1 etc. You should prevent of doing developers such a thing... Read http://semver.org/ Should that change something ? Or do i misunderstand something ? Kind regards Karl Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: explicit dependencies in maven
Hi Barrie, On 11/6/14 11:01 PM, Barrie Treloar wrote: On 6 November 2014 22:15, Karl Heinz Marbaise mailto:khmarba...@gmx.de>> wrote: Hi, On 11/5/14 11:14 PM, Barrie Treloar wrote: On 6 November 2014 05:37, Karl Heinz Marbaise mailto:khmarba...@gmx.de>> wrote: Hi, to be clear on that point you should never change released versions. The idea of releases is that they are immutable. The scenario you have described should never be done which means: If you change code than make simply a new version like 1.2 or may be better things like 1.1.1 to show it's a bug fix release of 1.1 etc. You should prevent of doing developers such a thing... Read http://semver.org/ Should that change something ? Or do i misunderstand something ? No, just more reading for Irfan. Ok. So a misunderstanding on my site...Sorry.. Kind regards Karl Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: fetching a tar.gz URL / dependency via HTTP during a build?
Hi Kevin,
to download a an file from somewhere you could use the
wagon-maven-plugin like this:
org.codehaus.mojo
wagon-maven-plugin
1.0-beta-5
download-test-data
prepare-package
download-single
http://archive.apache.org/dist/abdera/1.1.2/
apache-abdera-1.1.2-src.tar.gz
${project.build.directory}/environment/qa
For unpacking of the tar.gz you
On 11/8/14 7:40 PM, Kevin Burton wrote:
I’m trying to build .debs using jdeb and maven for various projects.
For example, there is no .deb for spark. So I’m just taking the tar.gz and
making a deb that installs to /usr/share/apache-spark.
The problem is I don’t want to put the full binary into git as it’s about
200MB.
I’d rather have the build fetch the tar.gz directly from Apache during the
build, untar it, then build the deb from the output.
Is there and way to do this or should I just write a bash script which uses
wget to fetch the URL?
Kind regards
Karl Heinz Marbaise
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: fetching a tar.gz URL / dependency via HTTP during a build?
Hi Kevin,
On 11/8/14 8:19 PM, Kevin Burton wrote:
Nice.. it works actually. the only problem is that it downloads the
file every time and it’s 180MB… there’s no way to skip it if the file
already exists. hm..
so this sounds like an idea for improvement
Kind regards
Karl Heinz Marbaise
On Sat, Nov 8, 2014 at 11:00 AM, Karl Heinz Marbaise mailto:khmarba...@gmx.de>> wrote:
Hi Kevin,
to download a an file from somewhere you could use the
wagon-maven-plugin like this:
org.codehaus.mojo
wagon-maven-__plugin
1.0-beta-5
download-test-data
prepare-package
download-single
http://archive.apache.__org/dist/abdera/1.1.2/
<http://archive.apache.org/dist/abdera/1.1.2/>
apache-abdera-1.1.2-__src.tar.gz
${project.build.__directory}/environment/qa
For unpacking of the tar.gz you
On 11/8/14 7:40 PM, Kevin Burton wrote:
I’m trying to build .debs using jdeb and maven for various projects.
For example, there is no .deb for spark. So I’m just taking the
tar.gz and
making a deb that installs to /usr/share/apache-spark.
The problem is I don’t want to put the full binary into git as
it’s about
200MB.
I’d rather have the build fetch the tar.gz directly from Apache
during the
build, untar it, then build the deb from the output.
Is there and way to do this or should I just write a bash script
which uses
wget to fetch the URL?
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Common POM Version 16 Released
The Apache Maven team is pleased to announce the release of the Apache Common POM, version 16. This POM (org.apache:apache) configures common Maven settings for projects to use ASF infrastructure. Documentation live at: http://maven.apache.org/poms/asf. To use this parent, you should specify the version in your project's plugin configuration: org.apache apache 16 Changes since previous release: http://svn.apache.org/viewvc/maven/pom/tags/apache-16/pom.xml?view=markup Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Project Parent Version 26 Released
The Apache Maven team is pleased to announce the release of the [Apache Maven Project Parent, version 26](http://maven.apache.org/pom/maven/). This POM (org.apache.maven:maven-parent) contains settings that are likely to be useful to any Maven project that is building and releasing code with Maven 2/3. To use this parent, you should specify the version in your project's plugin configuration: org.apache.maven maven-parent 26 The Changes since previous release can be view by the following link: http://svn.apache.org/viewvc/maven/pom/tags/maven-parent-26/pom.xml?r1=HEAD&r2=1632922&diff_format=h Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Plugins Parent POM Version 27 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Plugins Parent POM Version 27. This POM (org.apache.maven.plugins:maven-plugins) is the common parent of all of the Maven plugins in the Apache Maven project. To use this parent, you should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-plugins 27 Changes since previous release: http://svn.apache.org/viewvc/maven/plugins/tags/maven-plugins-27/pom.xml?r1=HEAD&r2=1632929&diff_format=h Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [ANN] Apache Common POM Version 16 Released
Hi, On 11/17/14 9:59 PM, sebb wrote: On 17 November 2014 19:57, Karl Heinz Marbaise wrote: The Apache Maven team is pleased to announce the release of the Apache Common POM, version 16. This POM (org.apache:apache) configures common Maven settings for projects to use ASF infrastructure. Documentation live at: http://maven.apache.org/poms/asf. To use this parent, you should specify the version in your project's plugin configuration: org.apache apache 16 Changes since previous release: http://svn.apache.org/viewvc/maven/pom/tags/apache-16/pom.xml?view=markup The above URL is wrong; it does NOT show the differences. Unfortunately you are right...here is the correct one: http://svn.apache.org/viewvc/maven/pom/tags/apache-16/pom.xml?r1=HEAD&r2=1627336&diff_format=h sorry... Enjoy, -The Apache Maven team Mit freundlichem Gruß Karl-Heinz Marbaise -- SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893 Dipl.Ing.(FH) Karl-Heinz MarbaiseICQ#: 135949029 Hauptstrasse 177 USt.IdNr: DE191347579 52146 Würselen http://www.soebes.de - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: deploying war artifact to nexus is failing; packaging as jar works.
Hi, have you checked in Nexus if there where errors in the logs? Kind regards Karl Heinz Marbaise On 11/22/14 9:35 PM, Sartaj Hundal wrote: You're getting an IOException (unexpected end of stream). Are you using the right URL? Just an idea. You might have to set some property to 'false' so that maven actually starts reading. Sorry if I couldn't be more help, it's been awhile.. but your problem is definitely to do with IO. On Sat, Nov 22, 2014 at 3:47 AM, John Smith wrote: Hello, I'm trying to distribute my war's artifact to nexus but I'm getting the following error below. If I change the packaging in the pom.xml to jar it will deploy fine. Can anyone see what I am doing wrong? thanks, John. [INFO] --- maven-deploy-plugin:2.8.2:deploy (default-deploy) @ my-webapp --- [INFO] Downloading: http://nexus.lan:38080/nexus/content/repositories/snapshots/me/john/my-webapp/0.0.1-SNAPSHOT/maven-metadata.xml [INFO] Downloaded: http://nexus.lan:38080/nexus/content/repositories/snapshots/me/john/my-webapp/0.0.1-SNAPSHOT/maven-metadata.xml (776 B at 1.9 KB/sec) [INFO] Uploading: http://nexus.lan:38080/nexus/content/repositories/snapshots/me/john/my-webapp/0.0.1-SNAPSHOT/my-webapp-0.0.1-20141122.103704-6.war [INFO] Uploading: http://nexus.lan:38080/nexus/content/repositories/snapshots/me/john/my-webapp/0.0.1-SNAPSHOT/my-webapp-0.0.1-20141122.103704-6.pom [INFO] Uploaded: http://nexus.lan:38080/nexus/content/repositories/snapshots/me/john/my-webapp/0.0.1-SNAPSHOT/my-webapp-0.0.1-20141122.103704-6.pom (5 KB at 197.5 KB/sec) [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 3.133 s [INFO] Finished at: 2014-11-22T10:37:04+00:00 [INFO] Final Memory: 14M/244M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project my-webapp: Failed to deploy artifacts: Could not transfer artifact me.john:my-webapp:war:0.0.1-20141122.103704-6 from/to My_Snapshots (http://nexus.lan:38080/nexus/content/repositories/snapshots/): unexpected end of stream -> [Help 1] - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [VOTE] Change project logo and adopt owl as mascot
Hi, -1 Kind regards Karl Heinz Marbaise On 11/25/14 11:57 AM, Stephen Connolly wrote: For anyone who has been living under a rock, here is the background Background = I think everyone can agree that the site needs a reorganisation and a rewrite. Users cannot find what they need, and the end result is that people keep on abusing maven rather than having maven help them. Try as I might, I have been unable to motivate myself to do the reorganisation with the current dated look and feel of the site... I am not saying that picking a new logo and selecting a mascot will result in making progress, but it can't hurt and I believe it will help Proposed changes === 1. Change the logo font to Alte Haas Grotesk Bold with italics applied by Inkscape 2. Change the highlighted letter from 'a' to 'v' and replace the v with two Apache Feathers 3. Adopt the (currently unnamed) owl as our mascot Here is a link to the font: http://www.dafont.com/alte-haas-grotesk.font Here is a large version of the owl and the logo: http://people.apache.org/~stephenc/maven-logo-contest/maven-owl-final-large.png A regular version of the own and the logo, e.g. a size suitable for use in the top of the standard maven sites: http://people.apache.org/~stephenc/maven-logo-contest/maven-owl-final.png (Note that in all likelihood, the mascot would probably end up on the other side of the title bar from the logo... and that is IF the mascot ends up on the title bar) Here is both of those rendered in a site (as it can be helpful to see the graphics adjacent to text) http://people.apache.org/~stephenc/maven-logo-contest/maven-owl-final-context.png Logo Rational === If we do some searches for the Maven logo: https://www.google.com/search?site=imghp&tbm=isch&q=maven+logo&oq=maven+logo http://www.bing.com/images/search?q=maven+logo&go=Submit&qs=n&form=QBLH&scope=images&pq=maven+logo Our current logo, with a single highlighted letter stands out quite well from the other "maven" logos, so keeping a highlighted letter and an italic rendered font maintains continuity with our current logo. By changing the highlighted letter to the `v` and by using two Apache feathers to create the `v`, we connect our logo back to Apache... we are Apache Maven after all. The `v` is also the common short term for version (e.g.v3 is short for version 3). Apache Maven puts a lot of emphasis on versions of dependencies and plugins... you could say that versions are very important to Maven. The colours of the feather were changed to solid colours to match the owl mascot's scarf, beak and eyebrows Voting rules = Anyone who is subscribed to the dev or users list is eligible to vote. If you vote multiple times, only your final vote will be counted. The vote will be open until 1:00pm GMT on Wed 3rd Dec 2014 The vote is for all three changes as one single change. Partial votes (e.g. for the logo but not the mascot, or vice-versa) will not be counted. I, as the caller of the vote, reserve the right to cancel the vote if this vote is putting the harmony of the community at risk. If a majority of the PMC believe that this vote is putting the harmony of the community at risk, then the PMC may cancel this vote (though if even a small minority of the PMC were of that belief, I will more than likely have cancelled the vote before the PMC would need to decide... I'm just stating this FTR) The decision will be a simple majority, there will be no special veto powers. +1: [ ] Change the logo to the proposed logo and adopt the owl as project mascot 0: [ ] No opinion -1: [ ] No change Please only respond with +1, 0 or -1. If you want to discuss the proposed changes please use a different thread. This thread is for voting only. -Stephen - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Mojo Appassembler Maven Plugin Version 1.9 Released
Hi, The Mojo team is pleased to announce the release of the Appassembler Maven Plugin version 1.9. 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.9 Release Notes: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11780&version=20608 Bug: * [MAPPASM-238] - wrapperLogFile Improvements: * [MAPPASM-239] - Update version of plexus-archiver to 2.5 * [MAPPASM-240] - Update version of plexus-archiver to 2.6.3 * [MAPPASM-241] - Upgrade plexus-utils to 3.0.20 * [MAPPASM-242] - Upgrade to plexus-archiver 2.7.1 * [MAPPASM-243] - Upgrade plexus-interpolation to 1.21 * [MAPPASM-244] - Upgrade to mojo parent version 34 * [MAPPASM-246] - Use maven-dependency-plugin version which is defined by the parent. * [MAPPASM-247] - Upgrade maven-filtering to 1.3 * [MAPPASM-248] - Wrapper script fails on Solaris / SunOS 5.2 when the LC_TYPE is set to a non-single byte locale Task: * [MAPPASM-236] - Removing plexus-container-default dependency Enjoy, The Mojo team. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Bug? maven-ear-plugin 2.9.1 behaves different to 2.9
Hi Martin, first can you create a project which reproduces the problem...otherwise it's really hard to drill down the issue... Furthermore have you defined the dependencies in your ear module which should be skinnyfied... Does you ear module contain other dependencies which could have the jars you don't like to have in your ear as a transitive dependency? Can you post your pom file ? On 11/26/14 3:31 PM, Martin Hoeller wrote: Hi! I'm using the maven-ear-plugin to create an EAR with a skinny WAR. This worked fine till I did an update from version 2.9 to version 2.9.1. The actual problem is quite hard to explain, so I'll try and start with an abstract and provide details below. The problem is, the skinny WAR contains a lot more JARs than it should, but not all that are in the original WAR artifact. So it seems the m-ear-p does build a skinny WAR but the decisions what JARs to pack into the WAR are wrong. Changing the used m-ear-p back to version 2.9 fixes the problem, so this is definitely a regression in v2.9.1. The really strange thing is, this does not happen always! It only happens when I build my project the first time a day and a recent version of dependency of the project was not locally installed but was obtained from our local nexus. So it seems version information (or timestamps as all versions are SNAPSHOTs) of the dependencies matters. A concrete example to make this more clear: * My Project E is the EAR. * E depends on an artifact W, a WAR. * E and W have a common dependency D which is also a project of mine. * E, W and D are all built by a CI-server (jenkins) and SNAPSHOTs are deployed to nexus during the night. In the WAR there is D.jar packaged in WEB-INF/lib. In the EAR there is D.jar packaged in lib/ and the skinny WAR should no longer contain D.jar. With m-ear-p 2.9 this worked as expected. With version 2.9.1 when I build E with "mvn clean install" and D was not locally installed earlier this day, the skinny WAR is not skinny. It contains D.jar! Thus, D.jar is located twice in the EAR which is a bug. That sound really strange cause maven-ear-plugin itself does not download artifacts...but we should try to drill down the problem... As soon as I do a "mvn clean install" for D, the building of E starts to work and the WAR is skinny again... till a nightly deploy provides a newer SNAPSHOT of D. Any ideas what could be wrong here? I'd be happy to provide a sample project but I'm not sure how to provide this as it also seems to depend on the infrastructure. Hm...you say on one side it's a bug of maven-ear-plugin but here you say different... ?... TIA, - martin PS: I reported a (maybe) related issue half a year ago without any feedback. Not sure if this could provide some extra info: http://maven.40175.n5.nabble.com/bug-in-maven-ear-plugin-with-skinny-war-td5792646.html Kind regards Karl Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Fwd: ApacheCon NA 2015 Travel Assistance Applications now open!
Hi to all, for you information about ApacheCON 2015...Travel Assistance Applications... Forwarded Message Subject:ApacheCon NA 2015 Travel Assistance Applications now open! Date: Sat, 13 Dec 2014 13:59:15 +0100 From: jan i Reply-To: Maven Project Management Committee List To: travel-assista...@apache.org Hi pmcs@, The Travel Assistance Committee (TAC) are pleased to announce that travel assistance applications for ApacheCon North America 2015 are now open! This announcement serves as a purpose for you (pmcs@) to let members of your community know about both ApacheConNA 2015 and about the TAC assistance to attend. Could you please forward this announcement to your community, along if possible with information on how your project is involved in ApacheCon this year? We'll be holding ApacheCon North America 2015 in populous Austin, TX April 13 - 17, 2015. TAC exists to help those that would like to attend ApacheCon events, but are unable to do so for financial reasons. For more info on this years applications and qualifying criteria please visit the TAC website at < http://www.apache.org/travel/ >. Applications are already open, so don't delay! *Important dates*... * Sunday 1th February2015 - CFP closes * Friday 6th February 2015 - TAC Applications close Applicants have until the the closing date above to submit their applications (which should contain as much supporting material as required to efficiently and accurately process your request), this will enable TAC to announce successful awards shortly afterwards. As usual TAC expects to deal with a range of applications from a diverse range of backgrounds. We therefore encourage (as always) anyone thinking about sending in an application to do so ASAP. We look forward to greeting everyone in Austin, Texas in April. Kind Regards jan i (On behalf of the Travel Assistance Committee) Kind regards Karl Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Ant Plugin Version 2.4 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Ant Plugin, version 2.4 The Ant Plugin generates build files for Ant 1.6.2 or above from the POM. http://maven.apache.org/plugins/maven-ant-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-ant-plugin 2.4 Release Notes - Maven Ant Plugin - Version 2.4 http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11124&version=15977 Bug: * [MANT-65] - Invalid check for junit Improvements: * [MANT-75] - Removed compatibility with Maven 2.0.X * [MANT-80] - Update version of plexus-utils to 3.0.18 * [MANT-81] - Upgrade ant dep to 1.9.1 * [MANT-82] - Upgrade maven-plugin-testing-harness to 1.3 * [MANT-83] - Upgrade JUnit from 3.8.1 to 4.11 * [MANT-84] - Upgrade ant dep to 1.9.4 to be consistent with maven-antrun-plugin Tasks: * [MANT-69] - use maven-plugin-tools' java 5 annotations * [MANT-76] - MavenProject/MavenSession Injection as a paremeter instead as a component. * [MANT-77] - Upgrade ant dep to 1.8.1 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven AntRun Plugin Version 1.8 Released
The Apache Maven team is pleased to announce the release of the Apache Maven AntRun Plugin, version 1.8 This plugin provides the ability to run Ant tasks from within Maven. You can even embed your Ant scripts in the POM! http://maven.apache.org/plugins/maven-antrun-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-antrun-plugin 1.8 Release Notes - Maven AntRun Plugin - Version 1.8 http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11125&version=18043 Bugs: * [MANTRUN-98] - multiple input tasks leads to exception * [MANTRUN-175] - Documentation for failOnError is wrong Improvements: * [MANTRUN-191] - Update version of plexus-utils to 3.0.18 * [MANTRUN-193] - Upgrade Maven Plugin plugin to 3.3 New Feature: * [MANTRUN-190] - Upgrade Ant to 1.9.x Tasks: * [MANTRUN-176] - use maven-plugin-tools' java 5 annotations * [MANTRUN-187] - Make Plugin only 2.2.1 compatible - get rid of Maven 2.0 * [MANTRUN-188] - MavenProject/MavenSession Injection as a paremeter instead as a component. Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
