The Apache Maven team is pleased to announce the release of the Maven
Dependency Plugin version 3.8.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
On 26.06.24 21:26, Robert Turner wrote:
On Wed, Jun 26, 2024 at 5:12 AM Karl Heinz Marbaise
wrote:
Hi,
On 26.06.24 03:51, Robert Turner wrote:
On Tue, Jun 25, 2024 at 8:36 PM Karl Heinz Marbaise
wrote:
Hi,
I'm not sure if I understand your problem correct, because based on the
copy-depen
t;
> > > This "builds" the trivial empty JAR file, and copies no dependencies
> (as
> > > none are declared).
> > >
> > >
> > > However, my local Maven repository (cache) now contains a really old
> > > version of log4j:
> > >
>
AR or accessible to the environment executing it.
> >
> >
> >
> >> It would also very helpful to have a full pom file of that project or
> >> maybe a link to a github project (or alike)?
> >>
> >
> >
> > I think what is happening is tha
On Wed, Jun 26, 2024 at 1:36 AM Nils Breunese wrote:
> Robert Turner wrote:
>
> > The "problem" is not that the old log4j gets copied to the output folder,
> > it's that it is fetched into the local Maven cache / repository, which is
> > then picked up by security tooling (which of course compla
will help to explain what
> > I'm seeing (and I think it makes sense now, but still has an
> > undesirable result). (see below)
>
> It was not the question of digging into that... The question was: Why do
> need to use copy-dependencies in your build?
>
>
>
l to have a full pom file of that project or
maybe a link to a github project (or alike)?
I think what is happening is that `maven-dependency-plugin` (3.7.1) depends
transitively on log4j 1.2.12 -- I'm still working through trying to figure
that out though.
Originally (a few months ago), I
Robert Turner wrote:
> The "problem" is not that the old log4j gets copied to the output folder,
> it's that it is fetched into the local Maven cache / repository, which is
> then picked up by security tooling (which of course complains that it is
> ancient and has vulnerabilities).
There is no
). (see below)
>
>
>
>> It would also very helpful to have a full pom file of that project or
>> maybe a link to a github project (or alike)?
>>
>
>
> I think what is happening is that `maven-dependency-plugin` (3.7.1)
> depends transitively on log4j 1.2.12 --
and hopefully this additional information will help to explain what
I'm seeing (and I think it makes sense now, but still has an
undesirable result). (see below)
> It would also very helpful to have a full pom file of that project or
> maybe a link to a github project (or alike)?
>
fic plugin with the
transitive dependency to the offending package [1] is
"maven-javadoc-plugin" (which likely needs some updates of dependencies,
etc, in particular maven-reporting- which seem to be the ones that are
older).
During our build process, "maven-dependency-plugin"
e [1] is
"maven-javadoc-plugin" (which likely needs some updates of dependencies,
etc, in particular maven-reporting- which seem to be the ones that are
older).
During our build process, "maven-dependency-plugin" is used with the goal
"copy-dependencies" to copy runt
The Apache Maven team is pleased to announce the release of the Maven
Dependency Plugin version 3.7.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
The Apache Maven team is pleased to announce the release of the Maven
Dependency Plugin version 3.7.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
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 over-and-over-and-o
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 a
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 curren
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,
nati
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:
https://github.com/maveniverse/toolbox/blob/main/shared/src/main/java/eu/maveniverse/maven/toolbox/shared/internal/ToolboxComman
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 toolbox@mave
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 Cserven
ed 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,
> >>>
> >>
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
- which goals are "
ested 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
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: users-h...@ma
ncy:copy
> > > - dependency:copy-dependencies
> > > - dependency:go-offline
> > > - dependency:list
> > > - dependency:tree
> > > - dependency:unpack
> > > - dependency:unpack-dependencies
> > >
> > >
> > >
> > >
t; 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 &quo
> > > > >
> > > > > > Hi
> > > > > > I use:
> > > > > >
> > > > > > - dependency:analyze / dependency:analyze-only
> > > > > > - dependency:copy
> > > > > > - dependency:c
r Jaranowski <
> > > > s.jaranow...@gmail.com>
> > > > wrote:
> > > >
> > > > > Hi
> > > > > I use:
> > > > >
> > > > > - dependency:analyze / dependency:analyze-only
> > > > > - dependency:copy
> &g
> > > - dependency:copy-dependencies
> > > > - dependency:go-offline
> > > > - dependency:list
> > > > - dependency:tree
> > > > - dependency:unpack
> > > > - dependency:unpack-dependencies
> > > >
> > > >
> &g
gt; - dependency:tree
> > > - dependency:unpack
> > > - dependency:unpack-dependencies
> > >
> > >
> > >
> > > czw., 21 mar 2024 o 17:06 Tamás Cservenák
> > > napisał(a):
> > >
> > > > Howdy,
> > > >
&
dependency:analyze / dependency:analyze-only
>> > - dependency:copy
>> > - dependency:copy-dependencies
>> > - dependency:go-offline
>> > - dependency:list
>> > - dependency:tree
>> > - dependency:unpack
>> > - dependency:unpack-depe
> 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-plu
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
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-depend
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 Cservenák
> 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 "
> 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 inter
; 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
> &
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/
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 plugi
aa151ddabf7bc78/src/GenerateReadme.java#L74
>
> On Thu, Mar 21, 2024 at 5:06 PM 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/mave
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/
ven-starter-projects/blob/c7839302f3552caa4de42bc97aa151ddabf7bc78/src/GenerateReadme.java#L74
On Thu, Mar 21, 2024 at 5:06 PM Tamás Cservenák wrote:
> Howdy,
>
> I'd would be interested in how users and devs are using
> maven-dependency-plugin:
> https://maven.apache.or
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 coul
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
, Mar 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 answer
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 y
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
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
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 the
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
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
ś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 3.3.
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
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
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
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
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
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
> fi
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 overwr
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
s the anticipated
> 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 rea
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, the
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 proc
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
tions/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]?
>&
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-
em 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-plug
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.x
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
en, I 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
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&#
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&#
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
, etc.
> Thanks again for any hints.
> Lewis
>
> On Fri, Feb 23, 2018 at 9:55 AM, lewis john mcgibbney
> wrote:
>
>> Hello users@,
>> I am looking to dynamically load JAR's during a program execution based
>> upon a users input and therefore using the mave
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-depende
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-p
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&#
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&#
ld profile 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
;>" in the output...
>
>
>
>
>>
>>
>> Furthermore I would suggest to test it several times without
>> influence of Teamcity (cause it seemed to be having some kind of
>> watcher running)..I had such issues in Jenkins a while ago (with the
&
I just took a quick look. It
seems 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?
hermore it might 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 qui
rces: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 ---
[00:34:49] :[com.issinc.jms.jax.ws.resources:bullpen-
ata from
>>> 'F:/work/5c4a237177bf7a76/jax-ws-resources/bullpen-jax-ws/ta
>>> rget/failsafe-reports/TEST-*.xml'
>>> (not existing file) with 'surefire' processor
>>> [00:34:49] :[com.issinc.jms.jax.ws.resources:bullpen-jax-w
mporting
>> data from
>> 'F:/work/5c4a237177bf7a76/jax-ws-resources/bullpen-jax-ws/ta
>> rget/surefire-reports/TEST-*.xml'
>> (not existing file) with 'surefire' processor
>> [00:34:49] :[com.issinc.jms.jax.ws.resources:bullpen-jax-ws] [INFO]
>> [00:34:49] :[
INFO] ---
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]
[00:34:49] :[com
] --- 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
ng file) with 'surefire'
> 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 -
.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 ---
[00:34:49] : [com.issinc.jms.jax.ws.resources:bullpen-jax-ws] [INFO] Set 3
syst
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
m
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) the
> > maven-dependency-plugin's unpack and
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 unzipped.
-
n various 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 tw
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
irectory.
> 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.
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
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.stripClass
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)
bu
1 - 100 of 492 matches
Mail list logo
