If it works, it works. It sounds like you're not really using Maven to
build software in this case, you're only using (or abusing) it to download
binaries.
If the binaries you were downloading were actually libraries that Maven was
using to compile software against, it would be more conventional
Thanks for the write up.
I'm watching a few videos on youtube, trying to understand the pros of using
Dependencies and I'm still not understanding, Vs what I have currently mark up
tags that pertain to the ISOs that I want to download under and
tags.
-Original Message-
From:
Sounds like you're all set, but as you asked for an example with the
dependencies tag:
http://maven.apache.org/POM/4.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd;>
Thanks for the help on this as it was very helpful.
All I needed was the following tag:
${depStagingArea}
This places the multiple ISOs under the correct directory in RHEL OS where it
was defined under the following tag:
/dropbox/foo
-Original Message-
From: Nick Stolwijk
Sorry, forgot to include the mvn command I'm running to download all of the
ISOs:
mvn dependency:copy -f multi_iso_downloader_pom_modified.xml -s
~/.m2/settings.xml
Do you have an example I can reference artifacts that are defined in a top
level tag?
thanks
-Original
We worked with all sorts of repos and I have to say GitHub provided the
least stressful environment. The combination of Git functionality with
GitHub actions is delightful. You can ditch your CI and bug tracker.
Especially nice the VSCode integration where a //TODO in code reflects as
issue in
In one of my projects, we started with Github packages. After a while
and having a lot of projects and various organisations, it turned out to
be very complicated to manage all these different repositories in the
setting.xml files of the developers. So, it was hard to stay on the top
of the
I played with GitHub packages thinking I could use it as a general binary repo,
but NO! It turned out that what is published on GitHub packages are only
available from within GitHub! Anything built with GitHub CI can use GitHub
packages. If you want to build locally you cannot access Github
Hi all,
Just wondering if anyone has any thoughts on using GitHub Packages as a company
repo vs Nexus.
Right now we (about 30-40 devs) are using an ageing version of Sonatype Nexus
for onsite builds and S3 for “cloud” based builds (a process inherited from
using Spring Boot).
Now there is a
Is there a guide or tool to make sense of the "Dependency collection stats"
that `mvn -X` produces?
Thanks,
Delany
10 matches
Mail list logo
