Re: Resource plugin - LifecycleExecutionException - Input length = 1

Op wo 12 aug. 2020 om 21:47 schreef Tobias : > > > Failed to execute goal > org.apache.maven.plugins:maven-resources-plugin:3.2.0:testResources > (default-testResources) on project XXX: Input length = 1 > > See [2] below for a more detailed stack trace. > > Do you know what goes wrong and how

mismatch between maven-release-plugin site and available artifacts

There is a mismatch between the published site and the available artifact. https://maven.apache.org/maven-release/maven-release-plugin/index.html lists 3.0.0-M2 published 2020-04-07 as the current release, but it cannot be downloaded from eg.

Re: Best Practice for distributing test utilities?

refactor foo to a multimodule one with the test utilities as an artifact and one with the code + tests for original foo, you can then depend on the test module with scope test in the main module and keep everything in source repo making it easy to stay in sync On 12-03-2020 14:55, Andreas

Re: Configure default execution phase

You should be able to change the default execution phase of a plugin (as well as bind a goal to any other phase) by configuring explicit executions bound to a phase see: https://maven.apache.org/guides/mini/guide-default-execution-ids.html You would need to use an id of "default-update" to

Re: is there a maven plugin to identify ancient pom dependencies

On 21-12-19 21:02, Maarten Mulders wrote: Maybe this can help you: https://github.com/portofrotterdam/versiondebt-plugin As far as I can see, it doesn't allow you to configure "what is old". It does tell you how old dependencies are. not really; it seems that it uses the "last modified"

Re: Maven Release Plugin Message Format

don' t recall any commits like that, generally I see that the last commit in a tag is "[maven-release-plugin] prepare release ..." and in my master branch I see "[maven-release-plugin] prepare release

Re: Not a chance to show conflicts in dependency tree?

On 11-09-18 10:56, Nicolas Peifer wrote: Hi, I'm trying to show dependency conflicts using "mvn dependency:tree -Dverbose -Dincludes=commons-collections" as described in the documentation[1]. Unfortunately, this gives the following error: "Verbose not supported since maven-dependency-plugin

Re: repository element was not specified in the POM inside distributionManagement element or in -DaltDeploymentRepository=id::layout::url parameter ->

On 30-06-18 16:39, Karen Goh wrote: Hi expert, I used maven build and run goal : deploy to see how my spring framework project run but I got the above error. There is this stackoverflow person which has similar problem as mine:

Re: site with file copy

On 03-05-18 08:03, Philipp Kraus wrote: Hello, I’m using „mvn site“ command to build for my project the project website as HTML code, During the site goal is running I need to copy some files into the target/site directory, how can I do this? I need to copy some single files to the output

Re: How to hide internal build details from deployed pom.xml ?

You can deploy artifacts using a custom, cleaned up pom that doesn't have a build section -- Disclaimer; This message is just a reflection of what I thought at the time of sending. The message may contain information that is not intended for you or that you don't understand.

Re: maven-war-plugin addClasspath useless, because it cannot add absolute paths

2018-01-25 11:43 GMT+01:00 Basin Ilya : > Hi List. > As far as I know, Class-Path in MANIFEST.MF of a .war file is only useful > when you need to add jars that are not in WEB-INF/lib and not provided by > the container. > this really depends on the classloader of the

Re: Avoid guava version conflict with hbase by shading

On 21-01-18 08:21, Debraj Manna wrote: Mark One more query if some other dependency (let's say elasticsearch for example) leaks its usage of guava then it may happen I end up again with two incompatible versions of guava. What is the recommended way of handling this? You would need to find

Re: Avoid guava version conflict with hbase by shading

my code? On Sat, Jan 20, 2018 at 1:44 PM, Mark Prins <mc.pr...@gmail.com> wrote: > You could try shading the new guava to a different package and use that in > your code. > E.g. jena-shaded-guava does that > > Op 20 jan. 2018 09:02 schreef "Debraj Manna" <s

Re: Avoid guava version conflict with hbase by shading

the > latest guava in my code and let hadoop and hbase use the old guava. > > On 20-Jan-2018 1:19 PM, "Mark Prins" <mc.pr...@gmail.com> wrote: > > > It seems that the guava versions are not API compatible, so shading is > > unlikely to help. You will need t

Re: Avoid guava version conflict with hbase by shading

It seems that the guava versions are not API compatible, so shading is unlikely to help. You will need to downgrade to a compatible version of guava or get the other projects to upgrade. -M Op 20 jan. 2018 07:51 schreef "Debraj Manna" : I have posted more details in

Re: Package failed

2017-10-31 10:27 GMT+01:00 Oleg Lempert : > Hi > I running project with option / -Dmaven.test.skip=true > this hint is just for the compiler/surefire/failsafe plugin, but does not mean that dependency resolution will not happen for this artifact because in fact it will (and

Re: failsafe: proper shutdown on failure

On 02-10-17 12:12, Veit Guna wrote: Hi. I'm using maven failsafe 2.20.1 to setup my test environment (redis, via fabric8/docker-maven-plugin) before ITs using pre-integration-test and shut it down on post-integration-test. It works just fine when tests are succeeding or failing "normally".

Re: Maven not getting latest artefact after deploy:deploy-file

On 03-08-17 17:57, Mehul Sanghvi wrote: I will do my best to illustrate with as simple an example as I can. Hopefully I don't miss anything by simplifying it. Project-A: com.my.dept dept-artefact 11.3.0.1.0-SNAPSHOT The above is uploaded to Nexus using deploy:deploy-file Project-B depends

Re: Is there a way to make mvn default to Java 8?

Op 13 jan. 2017 18:15 schreef "John Patrick" : If you only have Java 8 installed, would that work? Or does target still default to something older? The default value for the compiler plugin is 1.5 even when using java 8 runtime. You may want to look into toolchains as

Re: Uploading of parent pom of third party library to nexus.

On 13-12-16 17:31, Tester wrote: Hi, I'm able to use the mvn deploy-file commando to upload all the child libraries (powermock-core, powermock-reflect, ...), with for example, the following command: mvn deploy:deploy-file -DpomFile=xxx\powermock-core-1.2.5.pom

Re: AW: Maven-Site-Plugin: Generated content?

You probably want to create a reporting plugin that you can add to your pom to create that eXtra content, it 's how maven works

Re: Building maven project and certain specified dependencies to a certain jdk version

%22%20AND%20a%3A%22validation-api%22 good luck; personnaly I would rather upgrade to a current version of java and weblogic first On Sep 8, 2016, at 6:29 PM, Mark Prins <mc.pr...@gmail.com> wrote: You might be able to get away with explicitly declaring a java 5 version of validati

Re: Building maven project and certain specified dependencies to a certain jdk version

You might be able to get away with explicitly declaring a java 5 version of validation-api in your pom and hope it's api compatible. -m -- Disclaimer; This message is just a reflection of what I thought at the time of sending. The message may contain information that is not intended for you or

RE: [EXTERNAL] SCM APIs cause "ref HEAD is not a symbolic ref"

Op 15 jun. 2016 16:10 schreef "Justin Georgeson" : > > Is the failure happening during CI with a shallow clone? I've seen a few systems > > > -Original Message- > > From: simone.trip...@gmail.com [mailto:simone.trip...@gmail.com] On > > Behalf Of Simone Tripodi > >

Re: Problem With Maven Compiler Plugin

On 10-05-16 16:12, michael.ctr.taru...@faa.gov wrote: When attempting to build with Maven from Eclipse I am getting the following error: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile (default-compile) on project camel-activemq: Fatal error

integration testing a plugin when using a forked lifecycle

I'm trying (but failing) to reliably test a reporting plugin that requires some code analysis to be done to produce report input. (code analysis produces xml that is xsl transformed to html) Sometimes my test works, sometimes it doesn't; the test just uses the

Re: disabling default plugin from phase?

On 04-12-15 02:58, Martin Gainty wrote: was asked by a local resource to look into resurrecting flex-mojos for a local company Thanks to Jeff, Mirko and Adrien I was able to exec thru all the phases to make flexmojos operational ..but.. I am disturbed by EOL notice from code.google.com to