https://github.com/asciidoctor/jekyll-asciidoc-quickstart .. find “GitHub
pages” in page.
My blog used to be in textile - overnight GHP dropped support so I had to
batch convert hundreds to markdown. That was years back. I might have
preferred asciidoc, and if it is supported that’s great, but I
I don't think so - it's tied to SHA1 presently and would require updates to
multiple plugins. I mean for your own DAV-style repository you could ALSO
publish SHA256s, but there's no verification cycle as deps are pulled into
a build client-side that'd use them.
CDI came after JSR330 I think. I was on the JSR330 experts group. I could
be wrong there.
Back history of dependency injection - it was an antidote to classic GoF
service-locator being used everywhere in Javaland. When we co-created
PicoContainer we were careful to avoid Singleton as a term or
>
> JSR 330 has a TCK that defines a lot. A system that purports to facilitate
> injection into contained components (plugins or lesser) doesn’t have to
> implement all facets of that TCK but could do so out of the box by just
> using (say) guice or dagger in a class loader tree implementation.
log
> <https://rmannibucau.metawerx.net/> | Old Blog
> <http://rmannibucau.wordpress.com> | Github <
> https://github.com/rmannibucau> |
> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
> <
> https://www.packtpub.com/application-devel
Google for "embedding Maven". Articles like
https://techblog.bozho.net/embedding-maven/ talk about that.
Sounds great. Quick check - this is a fork of Maven somehow? Or additional
plugins that are configurable into standard Maven?
I too published something on quicker Maven builds that's lower tech -
https://paulhammant.com/2021/01/28/dagging-on-maven
- Paul
https://github.com/hboutemy/mcmm-yaml could gain some additional
post-publication meta info :)
Apache used to operate Gump for this purpose, back on the days of Ant and
Maven 1.x.
Corporations that do anti-virus content filtering of incoming GETs, have
occasionally seen corrupt jars in ~/.m2 and their shared
Nexus/Artifactory. In that case there was text content for the jar (insead
of a zip) and if you looked at it, you saw a HTML page talking of the A-V
transgression but
OK, ignore me, you're talking about the other way.
On Thu, Aug 24, 2023 at 1:27 PM Paul Hammant wrote:
> A classic pom.xml at root in a single repo, then multiple levels of child
> directory each with its own pom.xml (and its own src/main/java &
> src.test/java) ?
>
> Br
A classic pom.xml at root in a single repo, then multiple levels of child
directory each with its own pom.xml (and its own src/main/java &
src.test/java) ?
Branching model would be trunk based development (and branch for release),
possibly as short-lived feature branches in the GitHub
I wrote much of
https://cwiki.apache.org/confluence/plugins/servlet/mobile?contentId=118163392#content/view/118163392
20 years back, and still stand by the basic message.
Maven is a build tool though, and aims and reproducibility. Minimal output
should be the default (console and log files). If
Eclipse can't open a pom.xml file from the command line? For Intellij-idea
on Mac, Windows or Linux, I'd just do `idea pom.xml`
- Paul
On Sat, Feb 3, 2024 at 11:44 AM Matthias Bünger
wrote:
> Hey all,
> in this mail I want to share my experiences / thouhgts I had on my way
> from the decision
101 - 114 of 114 matches
Mail list logo
