Re: [DISCUSS] Maven Dependency Plugin

Howdy, 0.1.3 out, got unpack ability (actually UnpackSink). Here is 0.1.3 in action, doing "side-by-side" and "overlay" way of unpack: https://gist.github.com/cstamas/36c49da724100a19feab1397e7381d0f Oh, and Martin, the sink also unpacks only "unique" artifacts, so it will not

Re: [DISCUSS] Maven Dependency Plugin

Oh, and as a side effect, the plugin is way more snappier as well, look at execution time diffs (I know, this is not "benchmark", but is telling): https://gist.github.com/cstamas/6026436527cbd669ce1a5f183f03fe51 toolbox needs almost only 60% of runtime that m-dep-p have. T On Tue, Mar 26, 2024

Re: [DISCUSS] Maven Dependency Plugin

Rudimentary support for those is already present (equals, startWith, endsWith) :) So one can write ArtifactMatcher "spec expression" (that will be parsed into ArtifactMatcher that is actually Predicate) as: "artifact(gavoid)" where "gavoid" can be "string" or "g:a" or "g:a:v" etc Each field

Re: [DISCUSS] Maven Dependency Plugin

Thanks Tamas for all your work. I'll sure have a look (but not right now as I'm in a train station on a phone). Just to mention a feature I missed yesterday in m-d-p: ability to filter on classifiers including *wildcards*. Because I have dependencies with this kind of classifiers: natives-win,

Re: [DISCUSS] Maven Dependency Plugin

Just for those brave... if you toy with it. The "copy" and "copy-transitive" CLI commands and Mojos have "targetSpec" parameters, that are parsed into ArtifactSink here:

Re: [DISCUSS] Maven Dependency Plugin

Howdy, Yes, m-dep-p is under maintained, it actually would need a rewrite as it still uses MAT (and many other Maven2 archaic stuff) internally. Hence, it will fail if used with 3.9+ features like "split repository" and is suboptimal in many areas. Toolbox 0.1.0 released, btw: jbang

Re: [DISCUSS] Maven Dependency Plugin

Hello Tamás, For context, what are the tensions that you're trying to solve here? Is m-dependency-p too big/getting unmaintainable/becoming a kitchen sink? Do some goals feel like a bad fit? Are you thinking of breaking it up or replacing it? Greg On Tue, Mar 26, 2024 at 8:52 AM Tamás

Re: [DISCUSS] Maven Dependency Plugin

; afterwards. > > Over the years I build a lot of pipelines, added checks to projects and so > on. The dependency plugin was very often my rescue. I can't remember each > single usage and project and its context, but there is a reason why these > goals/functions have been added. >

Re: [DISCUSS] Maven Dependency Plugin

Yes, all of them. purge-local-repository I use very often in Jenkins pipelines to clean up afterwards. Over the years I build a lot of pipelines, added checks to projects and so on. The dependency plugin was very often my rescue. I can't remember each single usage and project and its context

Re: [DISCUSS] Maven Dependency Plugin

ted in how users and devs are using > maven-dependency-plugin: > https://maven.apache.org/plugins/maven-dependency-plugin/ > > I collected some basic questions I'd like to have answered (but feel free > to add more info!): > - which goals are "must have" for you >

Re: [DISCUSS] Maven Dependency Plugin

Many downstream package maintainers use :go-offline to build packages offline in a container w/o outbound network access. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail:

Re: [DISCUSS] Maven Dependency Plugin

ncy:copy > > > - dependency:copy-dependencies > > > - dependency:go-offline > > > - dependency:list > > > - dependency:tree > > > - dependency:unpack > > > - dependency:unpack-dependencies > > > > > > > > > > > >

Re: [DISCUSS] Maven Dependency Plugin

-Dverbose=true ** It will display your effective pom but also will tell you in comments for each value where (which pom) it comes from. Regarding the dependency plugin, what I use very frequently: * copy-dependencies (including

Re: [DISCUSS] Maven Dependency Plugin

> > > > > > > > Hi > > > > > > I use: > > > > > > > > > > > > - dependency:analyze / dependency:analyze-only > > > > > > - dependency:copy > > > > > > - dependency:copy-dependencie

Re: [DISCUSS] Maven Dependency Plugin

t; > > > > s.jaranow...@gmail.com> > > > > wrote: > > > > > > > > > Hi > > > > > I use: > > > > > > > > > > - dependency:analyze / dependency:analyze-only > > > > > - dependency:copy > > > > &g

Re: [DISCUSS] Maven Dependency Plugin

t; > > > - dependency:copy-dependencies > > > > - dependency:go-offline > > > > - dependency:list > > > > - dependency:tree > > > > - dependency:unpack > > > > - dependency:unpack-dependencies > > > > > > > > >

Re: [DISCUSS] Maven Dependency Plugin

t; > - dependency:tree > > > - dependency:unpack > > > - dependency:unpack-dependencies > > > > > > > > > > > > czw., 21 mar 2024 o 17:06 Tamás Cservenák > > > napisał(a): > > > > > > > Howdy, > > > > &

Re: [DISCUSS] Maven Dependency Plugin

dependency:analyze / dependency:analyze-only >> > - dependency:copy >> > - dependency:copy-dependencies >> > - dependency:go-offline >> > - dependency:list >> > - dependency:tree >> > - dependency:unpack >> > - dependency:unpack-depe

Re: [DISCUSS] Maven Dependency Plugin

> czw., 21 mar 2024 o 17:06 Tamás Cservenák > > napisał(a): > > > > > Howdy, > > > > > > I'd would be interested in how users and devs are using > > > maven-dependency-plugin: > > > https://maven.apache.org/plugins/maven-dependency-plugin/

Re: [DISCUSS] Maven Dependency Plugin

gt; czw., 21 mar 2024 o 17:06 Tamás Cservenák > napisał(a): > > > Howdy, > > > > I'd would be interested in how users and devs are using > > maven-dependency-plugin: > > https://maven.apache.org/plugins/maven-dependency-plugin/ > > > > I collected some

Re: [DISCUSS] Maven Dependency Plugin

Like a couple of other folks 90% of my usage is dependency:analyze and dependency:tree. Other goals I barely notice. On Thu, Mar 21, 2024 at 12:06 PM Tamás Cservenák wrote: > > Howdy, > > I'd would be interested in how users and devs are using > maven-dependency-

Re: [DISCUSS] Maven Dependency Plugin

Agreed, Use of "purge-local-repository" is a very bad thing (next to "go offline" and related goals). They all come from the "maven2 era", and should never be used with Maven3... T On Thu, Mar 21, 2024 at 7:50 PM Richard Eckart de Castilho wrote: > > > On 21. Mar 2024, at 19:43, Tamás

Re: [DISCUSS] Maven Dependency Plugin

> I'd would be interested in how users and devs are using > maven-dependency-plugin: > https://maven.apache.org/plugins/maven-dependency-plugin/ > > I collected some basic questions I'd like to have answered (but feel free > to add more info!): > - which goals are "must have

Re: [DISCUSS] Maven Dependency Plugin

> On 21. Mar 2024, at 19:43, Tamás Cservenák wrote: > > I mean, I know what those goals do, I am just unsure WHY you needed those. The current Apache UIMA release guidelines still list them as suggested steps to perform before a local trial build to ensure locally cached artifacts do not

Re: [DISCUSS] Maven Dependency Plugin

> over the time I used all of them in different projects and I think all > of them are needed. > > Viele Grüße > > Oliver > > > Am 21.03.24 um 17:04 schrieb Tamás Cservenák: > > Howdy, > > > > I'd would be interested in how users and devs are using > > m

Re: [DISCUSS] Maven Dependency Plugin

Hi, over the time I used all of them in different projects and I think all of them are needed. Viele Grüße Oliver Am 21.03.24 um 17:04 schrieb Tamás Cservenák: Howdy, I'd would be interested in how users and devs are using maven-dependency-plugin: https://maven.apache.org/plugins/maven

Re: [DISCUSS] Maven Dependency Plugin

Hi, I mostly use the "analyze" (mostly the "analyze-only") and "tree" goals, but I have also already used "copy/unpack-dependencies", "sources", "purge-local-repository" and "resolve". IMHO the "versions" plugin has a few functionalities that feel like could also belong to the dependencies

Re: [DISCUSS] Maven Dependency Plugin

ogress -DoutputFile=resolved.txt > org.apache.maven.plugins:maven-dependency-plugin:3.6.1:resolve > > ...and parse the output for Java module names and whether they are > "automatic". > > > https://github.com/sormuras/maven-starter-projects/blob/c7839302f3552caa4d

Re: [DISCUSS] Maven Dependency Plugin

Hey, mainly tree and analyze (note: we also use enforcer-plugin with some rules for dependencies) Greetings Matthias Am 21.03.2024 um 17:04 schrieb Tamás Cservenák: Howdy, I'd would be interested in how users and devs are using maven-dependency-plugin: https://maven.apache.org/plugins/maven

Re: [DISCUSS] Maven Dependency Plugin

I use the "resolve" goal like this: mvn --batch-mode --no-transfer-progress -DoutputFile=resolved.txt org.apache.maven.plugins:maven-dependency-plugin:3.6.1:resolve ...and parse the output for Java module names and whether they are "automatic". https://github.com/sormuras/ma

Re: [DISCUSS] Maven Dependency Plugin

would be nice to have it on the cli as well. Thanks for reaching out! On Thu, Mar 21, 2024 at 12:35 PM Gary Gregory wrote: > The one I use the most from the command line is "tree" ( > https://maven.apache.org/plugins/maven-dependency-plugin/tree-mojo.html) > > I wish I

Re: [DISCUSS] Maven Dependency Plugin

The one I use the most from the command line is "tree" ( https://maven.apache.org/plugins/maven-dependency-plugin/tree-mojo.html) I wish I could say "ignore test scope" to help me understand my runtime dependencies better. Gary On Thu, Mar 21, 2024, 12:06 PM Tamás Cserve

Re: [DISCUSS] Maven Dependency Plugin

21, 2024, 18:06 Tamás Cservenák wrote: > Howdy, > > I'd would be interested in how users and devs are using > maven-dependency-plugin: > https://maven.apache.org/plugins/maven-dependency-plugin/ > > I collected some basic questions I'd like to have answered (but feel fr

[DISCUSS] Maven Dependency Plugin

Howdy, I'd would be interested in how users and devs are using maven-dependency-plugin: https://maven.apache.org/plugins/maven-dependency-plugin/ I collected some basic questions I'd like to have answered (but feel free to add more info!): - which goals are "must have" for you - w

[ANN] Release Maven Dependency Plugin 3.6.1 released

The Apache Maven team is pleased to announce the release of the Maven Dependency Plugin version 3.6.1. https://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 3.6.1

[ANN] Release Maven Dependency Plugin 3.6.0 released

The Apache Maven team is pleased to announce the release of the Maven Dependency Plugin version 3.6.0. https://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 3.6.0

Some queries regarding maven-dependency plugin

Hi Everyone, I have been using maven-dependency-plugin for resolving artifact path (goal: properties) org.apache.maven.plugins maven-dependency-plugin 3.3.0 getArtifactPath properties And accessing the property ${*groupId:artifactId:jar} . * I am interested in knowing

[ANN] Release Maven Dependency Plugin 3.5.0 released

The Apache Maven team is pleased to announce the release of the Maven Dependency Plugin version 3.5.0. https://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 3.5.0

[ANN] Release Maven Dependency Plugin 3.4.0 released

The Apache Maven team is pleased to announce the release of the Maven Dependency Plugin version 3.4.0. https://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 3.4.0

Re: Please release maven-dependency-plugin 3.3.1

śr., 2 lis 2022 o 17:59 Andreas Sewe napisał(a): > Hi, > > would it be possible to please release the next version of the > maven-dependency-plugin, 3.3.1? > > Besides bug-fix updates to its maven-dependency-analyzer and > maven-dependency-tree dependencies, version

Please release maven-dependency-plugin 3.3.1

Hi, would it be possible to please release the next version of the maven-dependency-plugin, 3.3.1? Besides bug-fix updates to its maven-dependency-analyzer and maven-dependency-tree dependencies, version 3.3.1 also introduces the new configuration options which I need in a project of mine

[ANN] Apache Maven Dependency Plugin 3.3.0 Released

The Apache Maven team is pleased to announce the release of the Apache Maven Dependency Plugin, version 3.3.0 This plugin provides utility goals to work with dependencies like copying, unpacking, analyzing, resolving and many more. https://maven.apache.org/plugins/maven-dependency-plugin/ You

Maven Dependency Plugin not working with JDK 17

Hi, Did anyone tried the most recent version of Maven Dependency Plugin 3.2.0 with JDK 17? I'm getting the following error: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:3.2.0:analyze-only (enforce) on project my-project: Execution enforce of goal

[ANN] Release Maven Dependency Plugin 3.2.0 released

The Apache Maven team is pleased to announce the release of the Maven Dependency Plugin version 3.2.0. https://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 3.2.0

maven-dependency-plugin 3.1.3?

uts at all with version 1.9.2. Many of the maven plugins have been updated and released using this updated version of doxia-site-renderer. Unfortunately maven-dependency-plugin has not been released with this update. So it is impossible to fully update to that version of doxia-site-renderer, as the ve

Re: maven-dependency-plugin unpack goal: do not overwrite existing files

See my answer on StackOverflow. I hope it helps. https://stackoverflow.com/a/67158497/1082681 -- Alexander Kriegisch https://scrum-master.de Amedee Van Gasse schrieb am 19.04.2021 14:42 (GMT +07:00): > I do not ever want maven-dependency-plugin:3.1.2:unpack to overwrite existing >

Re: maven-dependency-plugin unpack goal: do not overwrite existing files

Hi Amedee. Can you post the output of your command again, replacing "install" with "fr.jcgay.maven.plugins:buildplan-maven-plugin:list-phase" Delany On Mon, 19 Apr 2021 at 09:42, Amedee Van Gasse wrote: > I do not ever want maven-dependency-plugin:3.1.2:unpack to ove

maven-dependency-plugin unpack goal: do not overwrite existing files

I do not ever want maven-dependency-plugin:3.1.2:unpack to overwrite existing files in any circumstances. This is my current pom.xml configuration: maven-dependency-plugin 3.1.2 unpack-zip-files generate-test-resources unpack

Re: Dependency plugin unpack plugin dependencies

Hi Alexander, this is an old thread, but no one has replied yet. While I think this is possible – what are you trying to achieve? Or in other words: WHY do you need the dependencies unpacked? What do you do with them? Regards, Ben On 2020/08/19 18:23:06, Alexander Broekhuis wrote: > Hi all, >

Re: Maven Dependency Plugin

gt; release date of Maven 3.7.0 that I could announce there? > -Markus > > > -Ursprüngliche Nachricht- > Von: John Patrick > Gesendet: Montag, 26. Oktober 2020 12:07 > An: Maven Users List > Betreff: Re: Maven Dependency Plugin > > If you read the opening line i

AW: Maven Dependency Plugin

e? -Markus -Ursprüngliche Nachricht- Von: John Patrick Gesendet: Montag, 26. Oktober 2020 12:07 An: Maven Users List Betreff: Re: Maven Dependency Plugin If you read the opening line it talks about Maven 3.7.0, which is not yet released. If you want to use a maven wrapper before v3.7.0

Re: Maven Dependency Plugin

If you read the opening line it talks about Maven 3.7.0, which is not yet released. If you want to use a maven wrapper before v3.7.0, then use this https://github.com/takari/maven-wrapper. The upgrade from takari to maven is easy but does allow you to change your documentation, process and ci

Maven Dependency Plugin

When I am using this plugin https://maven.apache.org/plugins/maven-wrapper-plugin/ then Maven fails because it apparently cannot find needed runtime files on Maven Central. This limitation is not told on that page. Is that a bug or am I doing something wrong? -Markus

Re: [Maven Dependency Plugin] usedDependency vs. ignoredUnusedDeclaredDependencies

/63885408/maven-dependency-plugin-useddependency-vs-ignoredunuseddeclareddependencies > > On 2020/09/02 15:09:43, Shelley wrote: >> What is the difference between the maven-dependency-plugin's >> *ignoredUnusedDeclaredDependencies* [1] and *usedDependencies *[2]? >> >&

Re: [Maven Dependency Plugin] usedDependency vs. ignoredUnusedDeclaredDependencies

I've also posted this question on Stack Overflow: https://stackoverflow.com/questions/63885408/maven-dependency-plugin-useddependency-vs-ignoredunuseddeclareddependencies On 2020/09/02 15:09:43, Shelley wrote: > What is the difference between the maven-dependency-plugi

[Maven Dependency Plugin] usedDependency vs. ignoredUnusedDeclaredDependencies

to accomplish this, so I'd like some clarification as to what the difference is between them, and which to use when. [1] https://maven.apache.org/plugins/maven-dependency-plugin/analyze-mojo.html#ignoredUnusedDeclaredDependencies [2] https://maven.apache.org/plugins/maven-dependency-plugin/analyze

Dependency plugin unpack plugin dependencies

Hi all, I currently have a setup in which I have some custom artifacts that I use as dependencies and unpack using unpack-dependencies. This all works great, but now I also have a custom plugin which needs one of the custom artifacts as dependency. I don't see those dependencies being unpacked.

Re: maven-dependency-plugin:3.1.2:unpack not invoked, then does not unpack specified dependencies

reopening the bash made it work, didn't understand why - thanks anyway all the best, -Simo http://people.apache.org/~simonetripodi/ http://www.99soft.org/ On Tue, Jul 14, 2020 at 2:14 PM Simone Tripodi wrote: > > Hi all mates, > I configured maven-dependency-plugin in my pom.xml

maven-dependency-plugin:3.1.2:unpack not invoked, then does not unpack specified dependencies

Hi all mates, I configured maven-dependency-plugin in my pom.xml in order to unpack an artifact, the issue is that the plugin is not hit in any way; follows below my pom snippet: org.apache.maven.plugins maven-dependency-plugin 3.1.2

Re: Javadoc aggregate fails with MDEP-187 with dependency plugin

all > > modules in my project and generate a single aggregate javadoc jar for the > > whole project, preferable with just running 'mvn -PmyReleaseProfile > > install'. Is this possible? > > > > In my case i have a few modules that use the dependency plugin to copy >

Re: Javadoc aggregate fails with MDEP-187 with dependency plugin

have a few modules that use the dependency plugin to copy > dependencies to a specific location. This seems to interfer with the > javadoc aggregate setup.I've attempted this a few times and keep getting > the MDEP-187 error message. Removing the aggregate javadoc jar setup > resolves the iss

Javadoc aggregate fails with MDEP-187 with dependency plugin

-dependency-plugin 3.0.0 and maven-javadoc-plugin 3.2.0

mvn site vs an unusual maven-dependency-plugin configuration

declare the dependency (it's a zip file in central), then use the maven-dependency-plugin (unpack-dependencies goal) to copy the dependencies to the target folder using the phase "compile". I've tried other phases but this is the only one that i tried whereby this works. Then 'copy-dependen

Problems with dependency-plugin + Mockito + Java 11

Hi, I'm wondering if anyone else has found a solution to this problem. I use the maven-dependency-plugin's analyze-only goal to look issues in my dependency tree. https://maven.apache.org/plugins/maven-dependency-plugin/analyze-only-mojo.html When I started using Java 11, I had to override

Re: Repository authentication when directly invoking dependency plugin

oes-here} > > > > > > When building the project, Maven is able to access the repository > > without any problems, as it's supposed to be. In debugging output, I > > can see it applying the credentials. > > > > But when I try to download an artifact

Re: Repository authentication when directly invoking dependency plugin

the credentials. > > But when I try to download an artifact directly, it doesn't look like > Maven is even considering the settings file. > > mvn org.apache.maven.plugins:maven-dependency-plugin:3.1.1:get \ > -DremoteRepositories=some.idhttps://some.host/artifactory/some.id \

Repository authentication when directly invoking dependency plugin

the settings file. mvn org.apache.maven.plugins:maven-dependency-plugin:3.1.1:get \ -DremoteRepositories=some.idhttps://some.host/artifactory/some.id \ -Dartifact=groupId:artifactId:1.1.1 The username is not transmitted. I can see in the debug output, that the BasicRepositoryConnector

[ANN] Apache Maven Dependency Plugin Version 3.1.1 Released

The Apache Maven team is pleased to announce the release of the Apache Maven Dependency Plugin Version 3.1.1 https://maven.apache.org/plugins/maven-dependency-plugin/ Important Note since 3.1.1: * Maven 3.X only * JDK 7 minimum requirement You should specify the version in your project's

[ANN] Apache Maven Dependency Plugin Version 3.1.0 Released

The Apache Maven team is pleased to announce the release of the Apache Maven Dependency Plugin Version 3.1.0 https://maven.apache.org/plugins/maven-dependency-plugin/ Important Note since 3.1.0: * Maven 3.X only * JDK 7 minimum requirement You should specify the version in your project's

Re: [Maven Dependency Plugin] Inheriting transitive dependencies whilst defining an artifact output directory

Hi Jörg, This is excellent and worked a treat. Thank you so much, for future reference, once the dependencies are declared with a , here is the correct plugin configuration solution org.apache.maven.plugins maven-dependency-plugin

Re: [Maven Dependency Plugin] Inheriting transitive dependencies whilst defining an artifact output directory

the > maven-dependency-plugin configuration as shown above. > The only issue with this workaround is that it is extremely messy, > bloats my POM and is difficult to maintain as I have now introduced > around 50 or so additional dependencies which all have versions, etc. > Thanks a

Re: [Maven Dependency Plugin] Inheriting transitive dependencies whilst defining an artifact output directory

I should also say, that the workaround is to list each and every transitive dependency in the dependency declaration with scope 'provided', such that they are NOT on the normal runtime classpath but ARE correctly copied into the target directory defined within the maven-dependency-plugin

[Maven Dependency Plugin] Inheriting transitive dependencies whilst defining an artifact output directory

Hello users@, I am looking to dynamically load JAR's during a program execution based upon a users input and therefore using the maven-dependency-plugin to do this. Specifically, the plugin configuration looks as follows org.apache.maven.plugins maven-dependency-plugin

[ANN] Apache Maven Dependency Plugin Version 3.0.2 Released

The Apache Maven team is pleased to announce the release of the Apache Maven Dependency Plugin Version 3.0.2. https://maven.apache.org/plugins/maven-dependency-plugin/ Important Note since 3.0.0: * Maven 3.X only * JDK 6 minimum requirement You should specify the version in your project's

[ANN] Apache Maven Dependency Plugin Version 3.0.1 Released

The Apache Maven team is pleased to announce the release of the Apache Maven Dependency Plugin Version 3.0.1. https://maven.apache.org/plugins/maven-dependency-plugin/ Important Note since 3.0.0: * Maven 3.X only * JDK 6 minimum requirement You should specify the version in your project's

Re: maven-dependency-plugin skips unpack goal

then it works. So what this tells me is that the usage of aggregate-jar goal breaks the maven-dependency-plugin in the sense that it no longer can know about all (it does know about some) project artifacts that were previously created by the reactor build via the maven-assembly-plugin. I think

Re: maven-dependency-plugin skips unpack goal

folder) there is some race condition where the dependency plugin does not think/know that an artifact was previously created. That explains what we see in practice. And I say race condition because it sometimes works (e.g. added -X and it worked once at least). I do think this is somehow related

Re: maven-dependency-plugin skips unpack goal

we do the same/similar thing using the maven-assembly-plugin. E.g. our standard practice is to generate artifacts for later consumption using the maven-assembly-plugin and then consume with maven-dependency-plugin. Is this not a valid way to handle this? The assembly is one option...the remot

Re: maven-dependency-plugin skips unpack goal

be worth to check using the maven-remote-resources > plugin for the parts which you are unpackaging into the appropriate > packages...if it's only related to single files etc. ? But I'm not sure... > [dh] I'm not familiar with that plugin. I just took a quick look. It seems we do the same/s

Re: maven-dependency-plugin skips unpack goal

erties (set-additional-system-properties) @ bullpen-jax-ws --- [00:34:49] :[com.issinc.jms.jax.ws.resources:bullpen-jax-ws] [INFO] Set 3 system properties [00:34:49] :[com.issinc.jms.jax.ws.resources:bullpen-jax-ws] [INFO] [00:34:49] :[com.issinc.jms.jax.ws.resources:bullpen-jax-ws] [INFO] --- maven-dependency-plugin

Re: maven-dependency-plugin skips unpack goal

;> rget/failsafe-reports/TEST-*.xml' >>> (not existing file) with 'surefire' processor >>> [00:34:49] :[com.issinc.jms.jax.ws.resources:bullpen-jax-ws] Importing >>> data from >>> 'F:/work/5c4a237177bf7a76/jax-ws-resources/bullpen-jax-ws/ta >>> rget/surefire-reports/TEST-*.xml'

Re: maven-dependency-plugin skips unpack goal

efire' processor >> [00:34:49] :[com.issinc.jms.jax.ws.resources:bullpen-jax-ws] [INFO] >> [00:34:49] :[com.issinc.jms.jax.ws.resources:bullpen-jax-ws] [INFO] --- >> properties-maven-plugin:1.0-alpha-2:set-system-properties >> (set-additional-system-properties) @ bullpen-jax-ws --- >>

Re: maven-dependency-plugin skips unpack goal

properties [00:34:49] :[com.issinc.jms.jax.ws.resources:bullpen-jax-ws] [INFO] [00:34:49] :[com.issinc.jms.jax.ws.resources:bullpen-jax-ws] [INFO] --- maven-dependency-plugin:3.0.0:unpack-dependencies (unpack-bullpen-msg) @ bullpen-jax-ws --- [00:34:49] :[com.issinc.jms.jax.ws.resources:bullpen-jax-

Re: maven-dependency-plugin skips unpack goal

] --- maven-dependency-plugin:3.0.0:unpack-dependencies (unpack-bullpen-msg) @ bullpen-jax-ws --- [DEBUG] Configuring mojo org.apache.maven.plugins:maven-dependency-plugin:3.0.0:unpack-dependencies from plugin realm ClassRealm[plugin>org.apache.maven.plugins:maven-dependency-plugin:3.0.0, par

Re: maven-dependency-plugin skips unpack goal

-- > properties-maven-plugin:1.0-alpha-2:set-system-properties > (set-additional-system-properties) @ bullpen-jax-ws --- > [00:34:49] : [com.issinc.jms.jax.ws.resources:bullpen-jax-ws] [INFO] Set > 3 system properties > [00:34:49] : [com.issinc.jms.jax.ws.resources:bullpen-jax-ws] [INFO]

Re: maven-dependency-plugin skips unpack goal

) @ bullpen-jax-ws --- [00:34:49] : [com.issinc.jms.jax.ws.resources:bullpen-jax-ws] [INFO] Set 3 system properties [00:34:49] : [com.issinc.jms.jax.ws.resources:bullpen-jax-ws] [INFO] [00:34:49] : [com.issinc.jms.jax.ws.resources:bullpen-jax-ws] [INFO] --- maven-dependency-plugin:3.0.0:unpack-dependencies

Re: maven-dependency-plugin skips unpack goal

Hi, On 20/01/17 17:07, Bernd Eckenfels wrote: Any logs (on debug level)? yes and a concrete error message and of course (as Bernd already mentioned log output)... Just a note: Have you correctly defined a dependency to the module which creates the zip/tar/jar from your module which uses

Re: maven-dependency-plugin skips unpack goal

I'll run that right now... -Dave On Fri, Jan 20, 2017 at 9:07 AM, Bernd Eckenfels wrote: > Any logs (on debug level)? > > Am Fri, 20 Jan 2017 08:55:44 -0700 > schrieb David Hoffer : > > > We have a large multi-module build where occasionally (often)

Re: maven-dependency-plugin skips unpack goal

Any logs (on debug level)? Am Fri, 20 Jan 2017 08:55:44 -0700 schrieb David Hoffer : > We have a large multi-module build where occasionally (often) the > maven-dependency-plugin's unpack and unpack-dependencies goal will > skip their work. E.g. The specified artifact is not

maven-dependency-plugin skips unpack goal

ious parts of the build and unzip (usually with file filtering) so that the consuming module can perform some operation on the file(s), e.g. wsimport goal. Note that in all/most cases we use maven-dependency-plugin to unpack more than one artifact. In the one that is failing now, it unpacks

[ANN] Apache Maven Dependency Plugin 3.0.0 Released

The Apache Maven team is pleased to announce the release of the Apache Maven Dependency Plugin, version 3.0.0 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. https

Re: Artefact jars, copied by maven-dependency-plugin, are unrecognisable.

build directory. > For this purpose, I am using maven-dependency-plugin [1]. The code to copy > a PostgreSQL artefact to project sub-dir "lib" looks as in [2]. > > The jar is copied to the specified location (./lib) as expected. However, > the jar cannot be opened and is unusable. >

Artefact jars, copied by maven-dependency-plugin, are unrecognisable.

Hi, I am trying to copy a few maven artefacts to the project's build directory. For this purpose, I am using maven-dependency-plugin [1]. The code to copy a PostgreSQL artefact to project sub-dir "lib" looks as in [2]. The jar is copied to the specified location (./lib) as expecte

Re: maven dependency plugin - build-classpath goal

Hi, Can you show your pom and what's the result you're getting? I have just tested with a sample project and it looks fine: junit junit 4.11 sources org.apache.maven.plugins maven-dependency-plugin 2.10 Command line: mvn dependency:build-classpath -Dmdep.stripClassifier=true

maven dependency plugin - build-classpath goal

Hello, I’m trying to use the maven-dependency plugin (2.10) with the build-classpath goal. I want to strip the classifier but it’s not work: mvn dependency:build-classpath -Dmdep.stripClassifier=true I also add the option -Dmdep.prefix="foo" (needed regarding the documentation)

About goal analyze-duplicate of maven-dependency-plugin

My bom-project use importing other poms in dependencyManagement section to accumulate dependency versions in one, and it seems that analyze-duplicate goal of maven-dependency-plugin is not detect duplication, if same dependency presence in importing pom and bom pom. For reproduce lets create two

Re: Why isn't maven-dependency-plugin copying my artifacts anymore?

On 03/10/2016 10:10 PM, Mark Eggers wrote: David, Are you perhaps running this inside Eclipse? If so, do you have the m2e-connector for maven-dependency-plugin installed? Can you run mvn package from the command line if you're only packaging this from Eclipse? I have run my project from

Re: Why isn't maven-dependency-plugin copying my artifacts anymore?

On 03/10/2016 02:31 PM, David M. Karr wrote: Several days ago, on the advice of someone on another list, I configured the use of the "maven-dependency-plugin" in my POM so that the build would copy some dependencies into a local folder, not inside the target folder. This worke

Re: Why isn't maven-dependency-plugin copying my artifacts anymore?

folder untouched. ‘mvn package’ works as expected. As usual, this still isn't doing anything for me. This time I looked closer at the console output. I'm thinking there's a clue here. I looked closer at the output from "maven-dependency-plugin". This is

Re: Why isn't maven-dependency-plugin copying my artifacts anymore?

; target folder untouched. ‘mvn package’ works as expected. >> > > As usual, this still isn't doing anything for me. > > This time I looked closer at the console output. I'm thinking there's a > clue here. I looked closer at the output from > "maven-dependen

  1   2   3   4   5   6   7   >