Howdy,
just to not let this discussion die off. Let me show a take on a "how
modern Maven plugin should look like" (that targets m-dependency-p goals,
sans analyze and some others) could look like:
https://github.com/maveniverse/toolbox
The "unpack" related goals are missing, not yet done, but
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
I use purge-local-repository sometimes, for some very specific tests
like copy* and unpack* are useful tools in a few builds
Regards,
Hervé
On 2024/03/21 18:43:24 Tamás Cservenák wrote:
> Howdy,
>
> Oliver: all, really?
> I wonder what you used for goals like "purge-local-repository",
>
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-plugin:
>
Hi
I use:
- dependency:analyze / dependency:analyze-only
- dependency:copy
- dependency:copy-dependencies
- dependency:go-offline
- dependency:list
- dependency:tree
- dependency:unpack
- dependency:unpack-dependencies
czw., 21 mar 2024 o 17:06 Tamás Cservenák napisał(a):
> Howdy,
>
> I'd
> 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
Howdy,
Oliver: all, really?
I wonder what you used for goals like "purge-local-repository",
"resolve-plugins" etc :)
I mean, I know what those goals do, I am just unsure WHY you needed those.
T
On Thu, Mar 21, 2024 at 6:41 PM Oliver B. Fischer
wrote:
> Hi,
>
> over the time I used all of
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:
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
Hi
For me it is:
* Tree: human work on transitivity
* List: pre-resolve for the runtime (dump jar list in a file)
* Resolve: CI init phase
Le jeu. 21 mars 2024 à 17:54, Christian Stein a écrit :
> I use the "resolve" goal like this:
>
> mvn --batch-mode --no-transfer-progress
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".
We mainly use in our builds:
* analyze
* analyze-only
* analyze-duplicate
as well as our own "fix" goal which runs on dev machines and auto-corrects
used and declared; used and undeclared; unused and declared:
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 Cservenák wrote:
> Howdy,
>
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
- which goals are
14 matches
Mail list logo