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
czw., 21 mar 2024 o 20:54 Tamás Cservenák napisał(a):
> Howdy,
>
> What is the use case of "go offline"?
>
For me - I use go-offline to prefetch local repo.
I have a simple project which have a common dependencies like spring-boot
and some home made other commons dependencies in company,
On this
Hey !
First of all, for everyone asking more info to understand where the pom
values come from and how they are computed, I think a very useful command
is:
**
mvn org.apache.maven.plugins:maven-help-plugin:3.4.0:effective-pom
-
Greg,
For example, we recently converted the TrinoDB (
https://github.com/trinodb/trino) build, removed their use of "go offline"
So am just interested in any other patterns out there.
T
On Thu, Mar 21, 2024 at 9:40 PM Greg Chabala wrote:
> I do have an example at hand, though I am not sure I
I do have an example at hand, though I am not sure I would advocate for it:
https://blog.frankel.ch/faster-maven-builds/2/
There are undoubtedly better ways to achieve the author's goals, but I'm
not sure that's the fault of dependency:go-offline.
On Thu, Mar 21, 2024 at 3:19 PM Tamás Cservenák
Ah, rereading the message it does feel it's unclear.
Basically, I would like to execute a plugin goal only on particular modules
which it is present on. The current way I do it fails the build because the
spring-boot plugin is not present on all the modules. But you did push me
towards the right d
Greg,
would like to see such a project, do you have any examples at hand?
Am sure there are much simpler/better/more correct ways to do the same
thing.
T
On Thu, Mar 21, 2024 at 9:15 PM Greg Chabala wrote:
> My understanding is dependency:go-offline is an effective way to
> pre-download plugin
My understanding is dependency:go-offline is an effective way to
pre-download plugins and dependencies, for instance if one is making some
layer in a docker build container for later reuse.
On Thu, Mar 21, 2024 at 2:54 PM Tamás Cservenák wrote:
> Howdy,
>
> What is the use case of "go offline"?
So,
in Maven2, the local repo was really "just a bunch of files" (totally wild
west).
With Maven3, and Resolver (yes, this is true from 3.0) the "enhanced" local
repository is used, that tries to "track" origin (of cached, not installed)
artifacts.
In Maven 3.9 the next step is made, which is a "
Hello Mantas,
I think you did not explain what you are trying to achieve. Or at least I
did not really understand.
Are you trying to lower the build time ?
If yes, then I would advise to use a Maven property for the configuration
in the root pom
Then most of your build could be run with -DskipRepa
Howdy,
What is the use case of "go offline"?
That is yet another goal coming from "Maven2 era" and messes up your local
repository (wrt back tracing dependencies,
https://issues.apache.org/jira/browse/MNG-7619)
I mean, if you do a build (w/o tests, or skipping most time stealing
steps), like "dry
+1 to this list from Slawomir:
- dependency:analyze / dependency:analyze-only
- dependency:copy
- dependency:copy-dependencies
- dependency:go-offline
- dependency:list
- dependency:tree
- dependency:unpack
- dependency:unpack-dependencies
On Thu, Mar 21, 2024 at 2:56 PM Slawomir Jaranowski
wro
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:
> https://maven.apache.org
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
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 wo
> 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
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 the
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-de
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
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 -DoutputFile=reso
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-
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/maven-starter-projects/
The tree goal is my go to for this plugin. I also like the analyze.
A wish I have is to get a more clearer view of the resolved dependencies
version with regard to the declared dependencyManagement and/or the
shortest path to dependency.
For example, when I see the dependency slf4j-api with versi
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,
>
Most of the time I use copy-dependencies goal to build non fat jar
deployments. Meanwhile tree goal helps figure out multimodule dependency
clashes by showing resolved ransitive dependencies.
As for the rest, i can see where and what could use them, but I haven't
used them directly.
On Thu, Mar 2
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 "
I have several spring boot applications in my reactor that need to be
repackaged before deployment. Only those spring boot modules have reference
to the spring boot plugin.
My current approach is to build the entire reactor (via install goal), and
later run repackaging goal only on particular spri
27 matches
Mail list logo
