[GitHub] [maven-doxia] elharo merged pull request #20: [MNGSITE-393] remove old Maven 1 and 2 info

[GitBox]

elharo merged pull request #20: [MNGSITE-393] remove old Maven 1 and 2 info
URL: https://github.com/apache/maven-doxia/pull/20
 
 
   


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.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Release maven anton plugin...sorry

[Vladimir Sitnikov]

Enrico>signed by another Apache committer (not strictly from Maven project)

AFAIK that is not required:
https://infra.apache.org/release-distribution.html#sigs-and-sums
The key must be in Maven's KEYS file though.

Vladimir

Re: Release maven anton plugin...sorry

[Enrico Olivelli]

Il Dom 5 Apr 2020, 19:16 Elliotte Rusty Harold  ha
scritto:

> Are there up to date instructions for releasing a Maven plugin
> somewhere? If so, I could probably do this. I see
> https://maven.apache.org/developers/release/index.html but that covers
> core and the parent POM, not plugins like antrun.
>

Just follow the 'common' procedure.
I will be happy to help you on slack tomorrow (my timezone, Europe/Rome)

Start by checking jenkins and performing its locally.

You also need a gpg private key for your apache.org address.
You should have this key signed by another Apache committer (not strictly
from Maven project)

Then the procedure will be quite simple

Thanks
Enrico

>
> On Sun, Apr 5, 2020 at 12:44 PM Enrico Olivelli 
> wrote:
> >
> > Hi guys
> > I am sorry but I am not finding time for a release of maven antrun
> plugin.
> >
> > It has been a long awaited release
> >
> > Does any committer have cycles?
> >
> > Enrico
>
>
>
> --
> Elliotte Rusty Harold
> elh...@ibiblio.org
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: Release maven anton plugin...sorry

[Anton Tanasenko]

Sorry for the offtopic, but you probably got attention of a lot of Antons
with that subject :)

вс, 5 апр. 2020 г. в 20:16, Elliotte Rusty Harold :

> Are there up to date instructions for releasing a Maven plugin
> somewhere? If so, I could probably do this. I see
> https://maven.apache.org/developers/release/index.html but that covers
> core and the parent POM, not plugins like antrun.
>
> On Sun, Apr 5, 2020 at 12:44 PM Enrico Olivelli 
> wrote:
> >
> > Hi guys
> > I am sorry but I am not finding time for a release of maven antrun
> plugin.
> >
> > It has been a long awaited release
> >
> > Does any committer have cycles?
> >
> > Enrico
>
>
>
> --
> Elliotte Rusty Harold
> elh...@ibiblio.org
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

-- 
Regards,
Anton.

Re: Release maven anton plugin...sorry

[Elliotte Rusty Harold]

Are there up to date instructions for releasing a Maven plugin
somewhere? If so, I could probably do this. I see
https://maven.apache.org/developers/release/index.html but that covers
core and the parent POM, not plugins like antrun.

On Sun, Apr 5, 2020 at 12:44 PM Enrico Olivelli  wrote:
>
> Hi guys
> I am sorry but I am not finding time for a release of maven antrun plugin.
>
> It has been a long awaited release
>
> Does any committer have cycles?
>
> Enrico



-- 
Elliotte Rusty Harold
elh...@ibiblio.org

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Release maven anton plugin...sorry

[Enrico Olivelli]

Hi guys
I am sorry but I am not finding time for a release of maven antrun plugin.

It has been a long awaited release

Does any committer have cycles?

Enrico

[GitHub] [maven-doxia] elharo opened a new pull request #20: [MNGSITE-393] remove old Maven 1 and 2 info

[GitBox]

elharo opened a new pull request #20: [MNGSITE-393] remove old Maven 1 and 2 
info
URL: https://github.com/apache/maven-doxia/pull/20
 
 
   @hboutemy


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.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Maven Runtime Metrics

[Enrico Olivelli]

I have managed to use @Inject and the extensions mechanism.
Thank you for your advices.

I am now implementing some useful "simple" metrics providers (two
"extensions") in order to see this stuff working.
My idea is to have two interesting implementations:
- Dump stats at the end of the CLI session (using local DropWizard
counters/summaries)
- Send stats to some Metrics Systems: I am using Prometheus.io at work
so I will use that system

It will be interesting to have some Grafana dashboard that tells be
how Maven is working on my laptop or on Jenkins.

Once my POC is ready the next step will be to start instrumenting
useful places in Maven Core.
We should instrument only "useful" parts of Maven Core.
Many Metrics libraries provide standard JVM metrics by default.
I think it will be mostly up to the plugins to expose use full value.

Personally I am interesting in seeing this stuff:
- execution time for checkstyle, spotbugs...
- execution time for javac
- number of network transfers (Wagon HTTP) and bandwidth
- time to write to disk artifacts (to local repository, in 'install',
to "target")

Enrico

Il giorno dom 29 mar 2020 alle ore 10:40 Romain Manni-Bucau
 ha scritto:
>
> It depends how it is done.
>
> @Inject MetricsSystem ms; will likely fail but if you inject the container
> and do the lookup you can handle the absence of the metrics, less elegant
> but working as well.
>
> Alternative is to inject a custom compiler component and have 2 components
> impl (hints being different), one with injected metrics, one with noop
> metrics hardcoded.
> Depending the current maven version you select the right hint.
> Think it is more or less what we do to handle aether change in some earlier
> maven version.
>
> Romain Manni-Bucau
> @rmannibucau  |  Blog
>  | Old Blog
>  | Github  |
> LinkedIn  | Book
> 
>
>
> Le dim. 29 mars 2020 à 10:33, Enrico Olivelli  a
> écrit :
>
> > Self answer: I had written the DefaultMetricsSystem file in the wrong
> > directory ! (in maven core tests!)
> > Sorry fo the noise
> >
> > I have just one problem.
> > Currently I am using Jsr300 to plug the MetricsSystem to Maven Core
> > and this would be the expected way for Plugins.
> >
> > Say now that I want to use my MetricsSystem bean (@Inject
> > MetricsSystem) in the Maven Compiler Plugin or in Wagon...
> > let's say we do a 3.8.2 Maven Compiler plugin and that we deliver this
> > MetricsSystem in Maven 3.7.0...
> > Will Maven compiler plugin 3.8.2 work on Maven 3.6.x that does not
> > bundle the definition of the MetricsSytem ?
> >
> > Ideally I would like to have a "null" value or a Default NOOP
> > implementation when the plugin is not running on Maven 3.7.0
> > Will it work ?
> >
> > I will continue with the POC then I will share my model.
> > The change to Maven Core is almost there.
> > Now my plan is:
> > - Create an independent "Maven Extension" (in my github space, non ASF
> > by now, to make it clear that this system is totally pluggable with
> > extensions) that wraps Dropwizard Metrics and outputs the results to
> > file at the end of the build
> > - Add some initial metrics in Maven runtime
> > - Try with some plugin
> >
> >
> >
> >
> > Enrico
> >
> > Il giorno sab 28 mar 2020 alle ore 15:57 Enrico Olivelli
> >  ha scritto:
> > >
> > > Hi,
> > > I have pushed a new version of my prof-of-concept
> > > https://github.com/apache/maven-studies/compare/maven-metrics?expand=1
> > >
> > > I am introducing a MetricsSystem interface and a DefaultMetricsSystem
> > CDI bean.
> > > I am new to sisu/plexsus container.
> > > It looks like that DefaultMetricsSystem is getting instantiated in
> > > Maven Core tests
> > >
> > > This is my work:
> > > https://github.com/apache/maven-studies/compare/maven-metrics?expand=1
> > >
> > > But if I run Maven from the command line I get the error below
> > >
> > > Maybe I missing some config/annotation
> > >
> > > Any help is appreciated !
> > >
> > > Enrico
> > >
> > >
> > > eolivelli@LAPTOP-OODVV59Q apache-maven-3.7.0-SNAPSHOT]$ bin/mvn
> > > [WARNING] Error injecting: org.apache.maven.DefaultMaven
> > > com.google.inject.ProvisionException: Unable to provision, see the
> > > following errors:
> > >
> > > 1) No implementation for org.apache.maven.metrics.MetricsSystem was
> > bound.
> > >   at ClassRealm[plexus.core, parent: null] (via modules:
> > > org.eclipse.sisu.wire.WireModule ->
> > > org.eclipse.sisu.plexus.PlexusBindingModule)
> > >   while locating org.apache.maven.lifecycle.internal.LifecycleStarter
> > >   while locating org.apache.maven.DefaultMaven
> > >
> > > 1 error
> > > at
> > com.google.inject.internal.InternalProvisionException.toProvisionException
> > > (InternalProvisionException.java:226)
> > > at 

Re: [VOTE] Release Apache Maven Verifier version 1.7.1

[Karl Heinz Marbaise]

Hi,

+1 from me.

Kind regards
Karl Heinz Marbaise
On 03.04.20 21:36, Robert Scholte wrote:

Hi,

We solved 1 issue:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12347880=Text

There are still a couple of issues left in JIRA:
issues.apache.org/jira/issues/?jql=project%20%3D%2012317922%20AND%20component%20%3D%20maven-verifier%20%20AND%20resolution%20%3D%20Unresolved%20%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC

Staging repo:
https://repository.apache.org/content/repositories/maven-1559/
https://repository.apache.org/content/repositories/maven-1559/org/apache/maven/shared/maven-verifier/1.7.1/maven-verifier-1.7.1-source-release.zip

Source release checksum(s):
maven-verifier-1.7.1-source-release.zip sha512: 
84f7d634d0dada9d08506466cfb5a066c84fce696c33116ae6decbeaba609ef864e2d8e0bacb1f08e757dcda16c61a72ac8dbffd5a0b7ce4043204f1237c7ef1

Staging site:
https://maven.apache.org/shared-archives/maven-verifier-LATEST/

Guide to testing staged releases:
https://maven.apache.org/guides/development/guide-testing-releases.html

NOTE: maven-verifier 1.7.0 was required to have maven wrapper support, but it 
introduced a bug, hence this small release.

Vote open for at least 72 hours.

[ ] +1
[ ] +0
[ ] -1


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Release Apache Maven Verifier version 1.7.1

[Robert Scholte]

+1

On 3-4-2020 21:36:43, Robert Scholte  wrote:
Hi,

We solved 1 issue:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12347880=Text

There are still a couple of issues left in JIRA:
issues.apache.org/jira/issues/?jql=project%20%3D%2012317922%20AND%20component%20%3D%20maven-verifier%20%20AND%20resolution%20%3D%20Unresolved%20%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC

Staging repo:
https://repository.apache.org/content/repositories/maven-1559/
https://repository.apache.org/content/repositories/maven-1559/org/apache/maven/shared/maven-verifier/1.7.1/maven-verifier-1.7.1-source-release.zip

Source release checksum(s):
maven-verifier-1.7.1-source-release.zip sha512: 
84f7d634d0dada9d08506466cfb5a066c84fce696c33116ae6decbeaba609ef864e2d8e0bacb1f08e757dcda16c61a72ac8dbffd5a0b7ce4043204f1237c7ef1

Staging site:
https://maven.apache.org/shared-archives/maven-verifier-LATEST/

Guide to testing staged releases:
https://maven.apache.org/guides/development/guide-testing-releases.html

NOTE: maven-verifier 1.7.0 was required to have maven wrapper support, but it 
introduced a bug, hence this small release.

Vote open for at least 72 hours.

[ ] +1
[ ] +0
[ ] -1