Re: Maven Extension

Hello, Release 0.8.3 is out, mainly to fix Apache Foundation Trademark Policy violations (thanks Sylwester). The new project name is Talos . I hope I'm good now and no lawyer is coming after me ;) I'm gonna stop spamming the mailing lists on this subjec

Re: Maven Extension

Hello, Release 0.8.2 is out. Outside a few bugs fixes, the HTML report is the biggest addition. I think I reached the point there the extension does everything I wanted to have. There is one more feature missing

Re: Maven Extension

On Mon, Jan 27, 2025 at 12:58 PM Olivier Lamy wrote: > > You are using the old Jenkins maven-plugin which is totally deprecated and > not really maintained anymore And it does not work with Guice 7.0+ pending MNG-8027. - To uns

Re: Maven Extension

en On Thu, 23 Jan 2025, 16:25 Adrian Tarau, <mailto:adr...@tarau.net> wrote: Hello everybody, I'm building a Maven extension to change the behavior of Maven while building, to scratch an itch had had for many years now. If others have this itch

Re: Maven Extension

sign of the output! >> Have you tested the extension in an CI environment? That might be useful, >> especially combined with mvnd or mvn -T... >> >> - Ben >> >> On Thu, 23 Jan 2025, 16:25 Adrian Tarau, >> wrote: >> >> >> Hello everybody,

Re: Maven Extension

output! Have you tested the extension in an CI environment? That might be useful, especially combined with mvnd or mvn -T... - Ben On Thu, 23 Jan 2025, 16:25 Adrian Tarau, <mailto:adr...@tarau.net> wrote: Hello everybody, I'm building a Maven extension to cha

Re: Maven Extension

/2025 5:42 PM, Benjamin Marwell wrote: > > Nice design of the output! > Have you tested the extension in an CI environment? That might be useful, > especially combined with mvnd or mvn -T... > > - Ben > > On Thu, 23 Jan 2025, 16:25 Adrian Tarau, > wrote: > > >

Re: Maven Extension

:25 Adrian Tarau, wrote: Hello everybody, I'm building a Maven extension to change the behavior of Maven while building, to scratch an itch had had for many years now. If others have this itch and this helps with that itch, that would be even better :) An overview of the extensions, it

Re: Maven Extension

Nice design of the output! Have you tested the extension in an CI environment? That might be useful, especially combined with mvnd or mvn -T... - Ben On Thu, 23 Jan 2025, 16:25 Adrian Tarau, wrote: > Hello everybody, > > I'm building a Maven extension to change the behavior

Re: Maven Extension

:25 PM Adrian Tarau wrote: Hello everybody, I'm building a Maven extension to change the behavior of Maven while building, to scratch an itch had had for many years now. If others have this itch and this helps with that itch, that would be even better :) An overview of the extensions, it&#x

Re: Maven Extension

Howdy, This sounds great. Will take a peek once we are out with 4 rc3. Thanks for your patience and contribution! T On Thu, Jan 23, 2025 at 4:25 PM Adrian Tarau wrote: > > Hello everybody, > > I'm building a Maven extension to change the behavior of Maven while > building

Maven Extension

Hello everybody, I'm building a Maven extension to change the behavior of Maven while building, to scratch an itch had had for many years now. If others have this itch and this helps with that itch, that would be even better :) An overview of the extensions, it's goals and future p

Re: A Maven extension for dependency tracking

Thanks Tamas. I'm looking at https://github.com/apache/maven-resolver/pull/182 today (and apologies for delay - other tasks...). See inline. pt., 27 maj 2022 o 21:19 Tamás Cservenák napisał(a): > Howdy, inline, also PR updated, simplified, and added a "demo" listener > that does exactly what you

Re: A Maven extension for dependency tracking

Howdy, inline, also PR updated, simplified, and added a "demo" listener that does exactly what you wanted. On Fri, May 27, 2022 at 8:24 AM Grzegorz Grzybek wrote: > Hello and thank you very much for your time ;) > > This looks exactly how I imagined it ;) - that the path is reachable via > the R

Re: A Maven extension for dependency tracking

Hello and thank you very much for your time ;) wt., 24 maj 2022 o 15:54 Tamás Cservenák napisał(a): > Howdy, > > take a look at this: > https://github.com/apache/maven-resolver/pull/182 > (demos are "mutilated" just to run them and observe output, changes there > are unrelated) > This looks ex

Re: A Maven extension for dependency tracking

Howdy, take a look at this: https://github.com/apache/maven-resolver/pull/182 (demos are "mutilated" just to run them and observe output, changes there are unrelated) But still, I am on edge: I still don't see why all this is "better", then just observe the collection end graph (having all, and t

Re: A Maven extension for dependency tracking

wt., 24 maj 2022 o 11:17 Tamás Cservenák napisał(a): > Howdy, > > inline only the "interesting" part: > > So, after playing a bit with 1.8.0[.1] of the BF/DF resolvers and your #176 > > PR, I see that example > > > > > org.eclipse.aether.internal.impl.collect.DependencyCollectorDelegate#dependenc

Re: A Maven extension for dependency tracking

Howdy, inline only the "interesting" part: So, after playing a bit with 1.8.0[.1] of the BF/DF resolvers and your #176 > PR, I see that example > > org.eclipse.aether.internal.impl.collect.DependencyCollectorDelegate#dependencyCollected() > extension point you've introduced is a bit too early for

Re: A Maven extension for dependency tracking

changes > >> > > > >> > > Thanks > >> > > Tamas > >> > > > >> > > On Thu, Apr 28, 2022 at 9:01 PM Tamás Cservenák < > ta...@cservenak.net> > >> > > wrote: > >> > > > >> > >&

Re: A Maven extension for dependency tracking

t; in > >> > >> resolver coming from totally different angles. > >> > >> > >> > >> And yes, the resolver collector is not quite "extension" friendly, > >> but > >> > we > >> > >> will make it right. >

Re: A Maven extension for dependency tracking

er (1.8.0) there are actually two >> > >> implementations: depth-first (original) and depth-first. >> > >> >> > >> By looking at your code: collection is most critical regarding >> > >> performance and memory in the resolver, so "hooking" into

Re: A Maven extension for dependency tracking

r each step) might not be the best, but still, what kind of > > >> extension points would you envision in the collector? > > >> > > >> For example, to achieve what you want, it would be completely enough > to > > >> receive the final CollectResult (the

Re: A Maven extension for dependency tracking

> >> > >> For example, to achieve what you want, it would be completely enough to > >> receive the final CollectResult (the full graph), no? > >> As -- from a resolver perspective -- that would be simplest, especially > >> that now we have two collector

Re: A Maven extension for dependency tracking

ctor implementations... >> >> Also, in case of multi threading, your shared stack would not cut, would >> it? >> >> I personally was also looking into these, especially after some of the >> latest additions to resolver in 1.8.0 and current master >> >

Re: A Maven extension for dependency tracking

t, would > it? > > I personally was also looking into these, especially after some of the > latest additions to resolver in 1.8.0 and current master > > > Thanks > T > > > On Thu, Apr 28, 2022 at 12:45 PM Grzegorz Grzybek > wrote: > >> Hello >> >>

Re: A Maven extension for dependency tracking

github.com/grgrzybek/tracking-maven-extension > > I'd like to share some proof of concept I made. It all started with a > question "why I'm getting log4j:log4j:1.2.12" in my local Maven repository > when building trivial project with fresh local repo? > > I k

A Maven extension for dependency tracking

Hello TL;DR: https://github.com/grgrzybek/tracking-maven-extension I'd like to share some proof of concept I made. It all started with a question "why I'm getting log4j:log4j:1.2.12" in my local Maven repository when building trivial project with fresh local repo? I knew it

[GitHub] [maven-site] olamy merged pull request #271: Update "Maven/ Available Extensions", add OpenTelemetry Maven Extension

olamy merged pull request #271: URL: https://github.com/apache/maven-site/pull/271 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...

[GitHub] [maven-site] olamy merged pull request #271: Update "Maven/ Available Extensions", add OpenTelemetry Maven Extension

olamy merged pull request #271: URL: https://github.com/apache/maven-site/pull/271 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...

[GitHub] [maven-site] cyrille-leclerc opened a new pull request #271: Update "Maven/ Available Extensions", add OpenTelemetry Maven Extension

cyrille-leclerc opened a new pull request #271: URL: https://github.com/apache/maven-site/pull/271 Update "[Maven/ Available Extensions](https://maven.apache.org/extensions/index.html)", add the [OpenTelemetry Maven Extension](https://github.com/open-telemetry/opentelemetry-ja

[maven-surefire-plugin] Registering a surefire RunListener from a Maven extension

Dear community, Context: We are building a Maven extension to observe Maven builds as distributed traces with OpenTelemetry (1) and we would like to listen to the execution of unit test. *Question: is there a solution to inject a surefire RunListener <https://maven.apache.org/surefire-archi

Re: Maven Extension Configuration

Yes it is, Karl Heinz beat me already in 2015! -- Origineel bericht -- Van: "Falko Modler" Aan: dev@maven.apache.org Verzonden: 31-8-2021 23:21:33 Onderwerp: Re: Maven Extension Configuration Hi Robert, this is basically https://issues.apache.org/jira/browse/MNG-5897, no?

Re: Maven Extension Configuration

Sounds reasonable, probably like mojo, with properties override so maybe @Param support too or so. Le mar. 31 août 2021 à 23:21, Falko Modler a écrit : > Hi Robert, > > this is basically https://issues.apache.org/jira/browse/MNG-5897, no? > > I left a few thouhts there a while ago. > > Cheers, >

Re: Maven Extension Configuration

Hi Robert, this is basically https://issues.apache.org/jira/browse/MNG-5897, no? I left a few thouhts there a while ago. Cheers, Falko Am 31.08.2021 um 22:50 schrieb Robert Scholte: Hi, I see quite some Maven extensions that rely on configuration. There's no convention for this, so they all

Maven Extension Configuration

Hi, I see quite some Maven extensions that rely on configuration. There's no convention for this, so they all pick their own format and location. Looking at the build-cache it seems there's again configuration required. I think with Maven 4 we should make it possible to add a configuration-b

Re: Eclipse LemMinX & Maven extension: a Language Server for pom files

On Mon, May 4, 2020 at 2:40 PM Nick Stolwijk wrote: > Hi Mickael, > Hi, I was wondering if you send this intentionally to the dev mailinglist? I > think this is better suitable for the user mailinglist, also you have a > much broader audience there. > To be honest, we're not much looking for e

Re: Eclipse LemMinX & Maven extension: a Language Server for pom files

provides some XML and schema > validation and code assistance (completion, hover documentation, tree-based > outline...) for the pom files thanks to the Maven XSD schema; the Maven > extension adds some Maven specific smartness to it, like proper > understanding of GAVs, repositories (and in

Eclipse LemMinX & Maven extension: a Language Server for pom files

While the XML language server already provides some XML and schema validation and code assistance (completion, hover documentation, tree-based outline...) for the pom files thanks to the Maven XSD schema; the Maven extension adds some Maven specific smartness to it, like proper understanding of

Re: scm-changes-maven-extension, and retiring maven-reactor-plugin

Today, I've rewritten that functionality as a Maven build extension, which I'm tentatively calling scm-changes-maven-extension.  (But I'm not so happy with that name; alternative suggestions are welcome.) It's checked in to sandbox/trunk/shared: https://svn.apache.org/repo

Re: scm-changes-maven-extension, and retiring maven-reactor-plugin

eful (it's quite popular here where I work), but > it's also busted in M3. > > Today, I've rewritten that functionality as a Maven build extension, which > I'm tentatively calling scm-changes-maven-extension.  (But I'm not so happy > with that name; alter

scm-changes-maven-extension, and retiring maven-reactor-plugin

feature is really useful (it's quite popular here where I work), but it's also busted in M3. Today, I've rewritten that functionality as a Maven build extension, which I'm tentatively calling scm-changes-maven-extension. (But I'm not so happy with that name; alternative

Re: svn commit: r696326 - in /maven/components/trunk: maven-core/src/main/java/org/apache/maven/extension/ maven-core/src/main/java/org/apache/maven/plugin/ maven-project/src/main/java/org/apache/mave

>> plugin. >> >> Modified: >> >> maven/components/trunk/maven-core/src/main/java/org/apache/maven/extension/DefaultBuildExtensionScanner.java >> >> maven/components/trunk/maven-core/src/main/java/org/apache/maven/plugin/DefaultPluginManager.java >&g

Re: svn commit: r696326 - in /maven/components/trunk: maven-core/src/main/java/org/apache/maven/extension/ maven-core/src/main/java/org/apache/maven/plugin/ maven-project/src/main/java/org/apache/mave

ugin. Modified: maven/components/trunk/maven-core/src/main/java/org/apache/maven/ extension/DefaultBuildExtensionScanner.java maven/components/trunk/maven-core/src/main/java/org/apache/maven/ plugin/DefaultPluginManager.java maven/components/trunk/maven-project/src/main/java/org/apache/ m

Re: svn commit: r586543 - in /maven/components/trunk/maven-core/src: main/java/org/apache/maven/execution/ main/java/org/apache/maven/extension/ test/java/org/apache/maven/extension/

windows > > where forceDelete(..) fails. > > > > Modified: > > > > maven/components/trunk/maven-core/src/main/java/org/apache/maven/execution/MavenProjectSession.java > > > > maven/components/trunk/maven-core/src/main/java/org/ap

Re: svn commit: r586543 - in /maven/components/trunk/maven-core/src: main/java/org/apache/maven/execution/ main/java/org/apache/maven/extension/ test/java/org/apache/maven/extension/

fix for the extension manager test that may help things on windows > where forceDelete(..) fails. > > Modified: > > maven/components/trunk/maven-core/src/main/java/org/apache/maven/execution/MavenProjectSession.java > > maven/components/trunk/maven-core/src/

Re: [resolved] maven extension : adding a custom ArtifactHandler

This artifact handler bug has proven a problem for me as well. Maven does pick up and maintain the handlers from the components.xml file; it just doesn't add them to the ArtifactHandlerManager, making the handlers inaccessible to the ArtifactFactory, which creates the respective artifacts. If you n

Re: [resolved] maven extension : adding a custom ArtifactHandler

I had this problem (It's a bug and also a problem in the conception of the core) and I solved it like this : package com.octo.mtg.plugin; import java.io.File; import org.apache.maven.artifact.handler.ArtifactHandler; import org.apache.maven.plugin.MojoExecutionException; import org.apache.maven.

[resolved] maven extension : adding a custom ArtifactHandler

I just understood I have to configure the plugin in the build/plugins element with true What's the meaning of the build/extensions element ? 2007/10/1, nicolas de loof <[EMAIL PROTECTED]>: > Hello, > > I'd like to add support in maven for a custom packaging. > I've created a META-INF/plexus/compo

maven extension : adding a custom ArtifactHandler

Hello, I'd like to add support in maven for a custom packaging. I've created a META-INF/plexus/components.xml to define a new ArtifactHandler : org.apache.maven.artifact.handler.ArtifactHandler javascript org.apache.maven.artifact.handler.DefaultArtifactHandler

Re: svn commit: r503171 - in /maven/components/branches/maven-trunk-caching-update: maven-core/src/main/java/org/apache/maven/ maven-core/src/main/java/org/apache/maven/extension/ maven-core/src/main/

On 05/02/2007, at 1:17 PM, Jason van Zyl wrote: That doesn't answer my question. No cache in Maven at all, or somewhere else? (Neither option being in the project builder). A cache in the reactor manager, or somewhere else that would provide control at the session level. Even in the embedd

Re: svn commit: r503171 - in /maven/components/branches/maven-trunk-caching-update: maven-core/src/main/java/org/apache/maven/ maven-core/src/main/java/org/apache/maven/extension/ maven-core/src/main/

On 4 Feb 07, at 5:31 PM 4 Feb 07, Brett Porter wrote: On 05/02/2007, at 12:15 PM, Jason van Zyl wrote: It's bleeding memory because there are thousands of POMs in the repository, and the hashmap has no limiting. A cache would allow them to be expired, size, limited, etc. so the memory con

Re: svn commit: r503171 - in /maven/components/branches/maven-trunk-caching-update: maven-core/src/main/java/org/apache/maven/ maven-core/src/main/java/org/apache/maven/extension/ maven-core/src/main/

On 05/02/2007, at 12:15 PM, Jason van Zyl wrote: It's bleeding memory because there are thousands of POMs in the repository, and the hashmap has no limiting. A cache would allow them to be expired, size, limited, etc. so the memory consumption is fixed. That's just not the function of

Re: svn commit: r503171 - in /maven/components/branches/maven-trunk-caching-update: maven-core/src/main/java/org/apache/maven/ maven-core/src/main/java/org/apache/maven/extension/ maven-core/src/main/

On 4 Feb 07, at 4:12 PM 4 Feb 07, Brett Porter wrote: On 05/02/2007, at 11:01 AM, Jason van Zyl wrote: I think there is something wrong in that we would need a cache. It's bleeding memory why and how is a cache implementation over a HashMap going to help? It's bleeding memory because th

Re: svn commit: r503171 - in /maven/components/branches/maven-trunk-caching-update: maven-core/src/main/java/org/apache/maven/ maven-core/src/main/java/org/apache/maven/extension/ maven-core/src/main/

I'd like to see more people test this branch against their own code. Test it on their own system, use the integration tests. I'm a bit surprised there was so little problems with it on my end. - Joakim Brett Porter wrote: On 05/02/2007, at 11:01 AM, Jason van Zyl wrote: I think there is somet

Re: svn commit: r503171 - in /maven/components/branches/maven-trunk-caching-update: maven-core/src/main/java/org/apache/maven/ maven-core/src/main/java/org/apache/maven/extension/ maven-core/src/main/

On 05/02/2007, at 11:01 AM, Jason van Zyl wrote: I think there is something wrong in that we would need a cache. It's bleeding memory why and how is a cache implementation over a HashMap going to help? It's bleeding memory because there are thousands of POMs in the repository, and the ha

Re: svn commit: r503171 - in /maven/components/branches/maven-trunk-caching-update: maven-core/src/main/java/org/apache/maven/ maven-core/src/main/java/org/apache/maven/extension/ maven-core/src/main/

On 4 Feb 07, at 3:30 PM 4 Feb 07, Brett Porter wrote: I said the branch. I'd like this in maven 2.0.x since it's simply swapping an implementation, but it will allow Continuum and Archiva to stop bleeding memory. I assumed it was going to need to be on trunk first to meet the 'develop on

Re: svn commit: r503171 - in /maven/components/branches/maven-trunk-caching-update: maven-core/src/main/java/org/apache/maven/ maven-core/src/main/java/org/apache/maven/extension/ maven-core/src/main/

I said the branch. I'd like this in maven 2.0.x since it's simply swapping an implementation, but it will allow Continuum and Archiva to stop bleeding memory. I assumed it was going to need to be on trunk first to meet the 'develop on trunk first' requirement, but if it's a hassle that's no

Re: svn commit: r503171 - in /maven/components/branches/maven-trunk-caching-update: maven-core/src/main/java/org/apache/maven/ maven-core/src/main/java/org/apache/maven/extension/ maven-core/src/main/

Please don't apply this to the trunk until the project builder is cleaned up. Jason. On 4 Feb 07, at 3:02 PM 4 Feb 07, Brett Porter wrote: On 03/02/2007, at 3:28 PM, [EMAIL PROTECTED] wrote: Author: joakime Date: Fri Feb 2 20:28:21 2007 New Revision: 503171 URL: http://svn.apache.org/vi

Re: svn commit: r503171 - in /maven/components/branches/maven-trunk-caching-update: maven-core/src/main/java/org/apache/maven/ maven-core/src/main/java/org/apache/maven/extension/ maven-core/src/main/

On 03/02/2007, at 3:28 PM, [EMAIL PROTECTED] wrote: Author: joakime Date: Fri Feb 2 20:28:21 2007 New Revision: 503171 URL: http://svn.apache.org/viewvc?view=rev&rev=503171 Log: Updated maven-project to utilize plexus-cache w/hashmap provider. Seems to pass all integration tests ok. Review?

svn commit: r227147 - in /maven/components/trunk: maven-core/src/main/java/org/apache/maven/extension/ maven-core/src/main/resources/META-INF/plexus/ maven-project/src/main/java/org/apache/maven/project/

s of resolving all artifacts referenced by a project much simpler and more consistent (namely, for the release plugin) Modified: maven/components/trunk/maven-core/src/main/java/org/apache/maven/extension/DefaultExtensionManager.java maven/components/trunk/maven-core/src/main/resources/META

svn commit: r225480 - in /maven/components/trunk: maven-artifact/src/main/java/org/apache/maven/artifact/factory/ maven-core/src/main/java/org/apache/maven/extension/ maven-core/src/main/java/org/apache/maven/lifecycle/

tory/ArtifactFactory.java maven/components/trunk/maven-artifact/src/main/java/org/apache/maven/artifact/factory/DefaultArtifactFactory.java maven/components/trunk/maven-core/src/main/java/org/apache/maven/extension/DefaultExtensionManager.java maven/components/trunk/maven-core/src/main/java/org/apache/m

svn commit: r225463 - in /maven/components/trunk: maven-artifact/src/main/java/org/apache/maven/artifact/factory/ maven-core/src/main/java/org/apache/maven/extension/ maven-core/src/main/java/org/apache/maven/lifecycle/ maven-core/src/main/resources/ME...

Author: brett Date: Tue Jul 26 23:14:20 2005 New Revision: 225463 URL: http://svn.apache.org/viewcvs?rev=225463&view=rev Log: PR: MNG-226 implement extension mechanism Added: maven/components/trunk/maven-core/src/main/java/org/apache/maven/extension/ maven/components/trunk/maven-