Re: properties in maven-remote-resources-plugin

2021-04-09 Thread Delany
Solved. The remote project was packaging type pom. Perhaps a mention of this could be added to the documentation? Thanks, Delany On Fri, 9 Apr 2021 at 14:14, Delany wrote: > Hi. I'm able to use the maven-remote-resources-plugin when the source > project is included in the reactor, but not

Re: properties in maven-remote-resources-plugin

2021-04-09 Thread Delany
Hi. I'm able to use the maven-remote-resources-plugin when the source project is included in the reactor, but not when I'm just building the destination project. So for example `mvn clean install -pl :commondb,:credmanagementdb` yields [INFO] --- maven-remote-resources-plugin:1.7.0:bundle

Re: properties in maven-remote-resources-plugin

2021-03-09 Thread Delany
Ok, no images thank you. So I was barking up the wrong tree using the properties tag in the plugin. I still don't know what I did wrong, but it works now. Now there's another issue. If I bundle resources in a *descriptorgenerator* directory, the process goal will create an empty

Re: properties in maven-remote-resources-plugin

2021-02-28 Thread Hervé BOUTEMY
please try to write: 1.12 in you pom.xml = it defines a custom property with the value you want this will permit "dbs:commondb:${dep.dbs.commondb}" to get the value replaced Notice that images are removed, then we don't understand what you're trying to show Regards, Hervé Le

Re: properties in maven-remote-resources-plugin

2021-02-26 Thread Delany
because project.version is one of the default properties the plugin passes through to its templating logic, I quote "Additional properties to be passed to Velocity. Several properties are automatically added:" https://maven.apache.org/plugins/maven-remote-resources-plugin/process-mojo.html#properties

Re: properties in maven-remote-resources-plugin

2021-02-26 Thread Anthony Whitford
I’m honestly unclear on your precise scenario. 1. If you are expecting a dependency to have a pom with a variable in it, that then you would specify before using it, then Maven doesn’t work that way. (And if you think about it, it creates a chicken-egg problem.) 2. If you are expecting to use

Re: properties in maven-remote-resources-plugin

2021-02-23 Thread Delany
Thanks I know how to use properties, but this plugin doesn't, it seems. It has some special way of importing them: https://maven.apache.org/plugins/maven-remote-resources-plugin/process-mojo.html [image: image.png] It can do this org.test:shared-resources:${project.version} But this is the

Re: properties in maven-remote-resources-plugin

2021-02-23 Thread Anthony Whitford
The tag is documented here: https://maven.apache.org/guides/introduction/introduction-to-the-pom.html#properties > On Feb 23, 2021, at 3:34 AM, Delany wrote: > > I don't want to hardcode the version

Re: properties in maven-remote-resources-plugin

2021-02-23 Thread Delany
Well I gave it my best shot maven-remote-resources-plugin process-remote-resources process dbs:commondb:${bully} 3

properties in maven-remote-resources-plugin

2021-02-23 Thread Delany
I don't want to hardcode the version number of the remote project into this plugin config, so I've used a property made available in a parent pom. But it's not being resolved. What am I doing wrong? maven-remote-resources-plugin