I just updated the documentation: it should be more accurate now
https://maven.apache.org/doxia/developers/modules.html
Regards,
Hervé
Le mercredi 4 juillet 2018, 07:55:25 CEST Hervé BOUTEMY a écrit :
> Hi Peter,
>
> IIUC, you want to create a JspWiki parser, to be able to writ
The Apache Maven team is pleased to announce the release of the
Apache Software Foundation Parent POM Version 20.
https://maven.apache.org/pom/asf/
You should specify the version in your project as parent like the following:
org.apache
apache
20
You can download the appropriate
Hi,
I didn't really tried, but please read carefully the 2 notes in the page:
Prefer maven-scm-publish-plugin to publish your site to SCM
Note for Maven 3 users: The site plugin behaves differently, require these
be added as dependencies instead of extensions. See Adding a Protocol to
The Apache Maven team is pleased to announce the release of the Apache
Maven Plugin Tools, version 3.5, including Apache Maven Plugin Plugin 3.5
The Maven Plugin Tools contains the necessary tools to generate
rebarbative content like descriptor, help and documentation. In addition,
it
strange
can you provide a test project, please?
Regards,
Hervé
Le mardi 13 mars 2018, 18:56:45 CET Laird Nelson a écrit :
> I am finding that the sourcepath for javadoc:jar (when run as part of the
> release profile) is different from the sourcepath for javadoc:javadoc in my
> project that
The Apache Maven team is pleased to announce the release of the Apache Maven
Archetype Bundles, version 1.3
Apache Maven Archetype Bundles is a collection of archetypes.
https://maven.apache.org/archetypes/
You can download the appropriate sources etc. from the download page:
The Apache Maven team is pleased to announce the release of the Apache
Maven Doxia Sitetools, version 1.8.1
Doxia Sitetools is an extension of base Doxia component that generates
either HTML sites, consisting of decoration and content that was generated
by Doxia, or documents like RTF or
The Apache Maven team is pleased to announce the release of the Apache Maven
Remote Resources Plugin, version 1.6.0
This plugin is used to retrieve JARs of resources from remote repositories,
process those resources, and incorporate them into JARs you build with Maven.
; On 01/11/18 23:55, Hervé BOUTEMY wrote:
> > Hi,
> >
> > Ah, I forgot about Nexus staging checks...
> >
> > I also forgot to merge MNG-6059 [1], which changes the attributes names
> > for
> > more flexibility on scm urls.
> >
> > Looks like Maven
ute and make its value explicit in the pom file.
>
> Robert
>
> On Sat, 03 Nov 2018 12:36:30 +0100, Karl Heinz Marbaise
>
> wrote:
> > Hi Hervé,
> >
> > On 03/11/18 12:29, Hervé BOUTEMY wrote:
> >> yes, sorry...
> >
> > No problem..
> &
Le samedi 3 novembre 2018, 12:36:30 CET Karl Heinz Marbaise a écrit :
> Hi Hervé,
>
> On 03/11/18 12:29, Hervé BOUTEMY wrote:
> > yes, sorry...
>
> No problem..
>
> > I already marked MNG-6059 as "fix for: 3.6.1"
> >
> > I suppose we should f
Hi,
Ah, I forgot about Nexus staging checks...
I also forgot to merge MNG-6059 [1], which changes the attributes names for
more flexibility on scm urls.
Looks like Maven 3.6.0 is not fully ready for this feature, will require 3.6.1
to have a definitive solution: sorry for the mistakes, and
for that, you can copy content to the generatedSiteDirectory [1]:
either $generatedSiteDirectory/resources if you already have html content, or
$generatedSiteDirectory/markdown if the generated content is in Markdown, and
so on
another option that I sometimes use is to include generated content
moving forward
>
> Thanks
>
> -D
>
> On Sun, Nov 4, 2018 at 3:33 AM Hervé BOUTEMY wrote:
> > good idea, that's a good opportunity: let's try
> >
> > Regards,
> >
> > Hervé
> >
> > Le samedi 3 novembre 2018, 13:01:34 CET Robert Scholte a
Hi Konrad,
> The only way to
> validate would be to include the checksum as text in the vote email and
> everyone verifying would need to check against his own build.
the checksum has to be validated against the downloaded zip file: yes, not
automagic, but not so complex
> Also we often have
Hi Christofer,
I know C/C++ people who used nar-maven-plugin [1] with success: did you have a
look?
Notice: in Maven, "polyglot" term has always been used for other POM format
than XML.
Here, it's more on Maven support for non-java languages
One key requirement in such multi-languages context
thinking at it: which Maven version are you using?
Did you try Maven 3.6.0? There was a cache added in MNG-6311 that could
perhaps help.
Regards,
Hervé
Le vendredi 18 janvier 2019, 10:36:13 CET Hervé BOUTEMY a écrit :
> Hi,
>
> Wow, 1600 modules and 4000 entries in dependencyM
type.
> So I guess this would be a quite generic requirement. One I seem to
> encounter multiple times with different languages.
> In my current example of PLC4X with C++, I simply statically link
> everything.
> Chris
>
>
>
> Am 08.01.19, 02:59 schrieb "Her
Hi,
Wow, 1600 modules and 4000 entries in dependencyManagement?
Did you try to use a memory profiler to see where the memory goes?
Is there something shareable in public to dig into details?
Regards,
Hervé
Le jeudi 17 janvier 2019, 18:28:57 CET Canivet, Guillaume a écrit :
> Hi,
>
> Here is
I think there are 2 separate debates:
1. supporting *late profile activation*, in addition to current *early*
activation (see the first step of phase 1 [1]), which is IMHO a more accurate
description of what you call "inheritable profile".
a side effect of late profile activation is that there
The Apache Maven team is pleased to announce the release of the Apache Maven
Archetype Bundles, version 1.4
Apache Maven Archetype Bundles is a collection of archetypes.
https://maven.apache.org/archetypes/
You can download the appropriate sources etc. from the download page:
Thank you for the report: yes, this should be improved to work in current
latest version of everything
I updated the command line to use version 1.3 of maven-archetype-quickstart,
which is the latest version and compiles with Java 7 target.
Unfortunately, when build with Java 11, the build now
Le jeudi 29 novembre 2018, 17:40:58 CET Alex O'Ree a écrit :
> I'm looking for an example on how to use the code snippet macro from doxia
> within a markdown file. I've found this
> https://maven.apache.org/guides/mini/guide-snippet-macro.html
> but it only covers apt and xdoc, but nothing for
eally like to have this solved or
> help with solving it (I'm not expecting you folks to do that for me)
> Chris
>
>
> PS: I'm currently using the cmake maven plugin abstracting even more from
> the actual build
>
> Am 05.01.19, 08:31 schrieb "Hervé BOUTEMY"
Thank you for transforming a learning done on the mailing list into a PR
We already have some feedback on the PR from Maven developers, but feedback
from users would be awesome also, since it's about making sure the
explanations are easy to understand, then the more eyes, the better
Regards,
Hi
Good question: I did not yet find the official answer, but I can share what I
know on this.
flatten-maven-plugin has the exact same issue, and this was fixed in the past
by adding a new API in Maven core (in 3.2.5) to be called by the plugin:
see
The Apache Maven team is pleased to announce the release of the Maven Parent
POMs Version 33.
Maven Parent POMs include Maven Parent POM itself, but also Maven Plugins
Parent POM, Maven Shared Components Parent POM, Maven Skins Parent POM and
Maven Doxia Tools Parent POM.
thank you, merged
regarding setting target Java Version as parameter, in theory this is a good
idea, but in practice, IMHO it makes the archetype more complex: people will
modify pom.xml when they want
Regards,
Hervé
Le dimanche 9 décembre 2018, 07:02:52 CET Bernd Eckenfels a écrit :
> I
Hi,
Yes, there are multiple reasons:
1. you should not rely on default version (defined in Maven version your using)
but lock your own choice in your pom (or parent)
2. for people not having locked their version, having a change of default
version based on Maven version is a side effect we want
Hi François,
I just checked, and the profile merging is perfectly happening.
If you run:
$ mvn -Papache-release
org.apache.maven.plugins:maven-help-plugin:3.2.0:effective-pom -Dverbose -N
you'll see the checksum-maven-plugin injected in plugins section
Perhaps what is confusing you is that you
The Apache Maven team is pleased to announce the release of the Apache Maven
Help Plugin, version 3.2.0
The Maven Help Plugin is used to get relative information about a project or
the system. It can be used to get a description of a particular plugin,
including the plugin's goals with their
the 'standard' way of
> doing things prove that there is some place for additional workflows/tools
> like jgitver.
>
> Regards,
>
> Matthieu
>
> On Fri, Aug 2, 2019 at 8:03 AM Hervé BOUTEMY wrote:
> > thank you Matthieu for sharing
> >
> > to me, one key in
thank you Matthieu for sharing
to me, one key interesting part is:
> An issue with solutions like yours is reproducibility : `git checkout X.Y.Z
> && mvn install`will not build again artifact-X.Y.Z ; but this can be
> considered minor depending on the use cases & needs.
and with jgitver, there
I'm working on that, to do (binary) Reproducible Builds with Maven:
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=74682318
There is a plexus-archiver GitHub issue
https://github.com/codehaus-plexus/plexus-archiver/pull/124
Currently, on maven-assembly-plugin, this API will be
The Apache Maven team is pleased to announce the release of the Apache Maven
JAR Plugin, version 3.2.0
This plugin provides the capability to build jars.
https://maven.apache.org/plugins/maven-jar-plugin/
You should specify the version in your project's plugin configuration:
The Apache Maven team is pleased to announce the release of the Apache Maven
Source Plugin, version 3.2.0
This plugin creates a jar archive of the source files of the current project.
https://maven.apache.org/plugins/maven-source-plugin/
You should specify the version in your project's plugin
The Apache Maven team is pleased to announce the release of the Apache Maven
Assembly Plugin, version 3.2.0
This plugin is primarily intended to allow users to aggregate the project
output along with its dependencies, modules, site documentation, and other
files into a single distributable
The Apache Maven team is pleased to announce the release of the Apache Maven
JAR Plugin, version 3.2.0
This plugin provides the capability to build jars.
https://maven.apache.org/plugins/maven-jar-plugin/
You should specify the version in your project's plugin configuration:
notice that the url of the Google's Central mirror was recently updated:
you'll need to change your settings configuration
Regards,
Hervé
Le dimanche 3 novembre 2019, 21:30:13 CET Greg Chabala a écrit :
> I would take that up with gcs-maven-mir...@googlegroups.com as noted here:
>
The Apache Maven team is pleased to announce the release of the Apache Maven
Release Plugin, version 3.0.0-M1.
This plugin is used to release a project with Maven, saving a lot of
repetitive, manual work. Releasing a project is made in two steps: prepare and
perform.
looks like there is WIP on that:
https://issues.apache.org/jira/browse/MRELEASE-980
Help welcome (testing, providing feedback, ...)
Regards,
Hervé
Le jeudi 31 octobre 2019, 02:31:47 CET Scott Rossillo a écrit :
> We're using the maven-release-plugin and all our tags end up looking like:
>
>
we talk about the maven-release-plugin, but I think that we should also talk
about the release profile = the way we extend the goals run during a non-
release build with a few additional goals on a release build
see for example the "apache-release" profile documentation of ASF parent
The Apache Maven team is pleased to announce the release of the Apache Maven
Source Plugin, version 3.2.1
This plugin creates a jar archive of the source files of the current project.
https://maven.apache.org/plugins/maven-source-plugin/
You should specify the version in your project's plugin
maven-ant-tasks have been deprecated in favor of Maven Artifact Resolver Ant
Tasks: https://maven.apache.org/resolver-ant-tasks/
Did you consider upgrading?
The new tasks are a little bit different, but they are equivalent and built
against Maven 3 resolution.
Regards,
Hervé
Le mercredi 12
The Apache Maven team is pleased to announce the release of the Apache Maven
Shade Plugin, version 3.2.2
This plugin provides the capability to package the artifact in an uber-jar,
including its dependencies and to shade - i.e. rename - the packages of some of
the dependencies.
The Apache Maven team is pleased to announce the release of the Apache Software
Foundation Parent POM Version 23.
https://maven.apache.org/pom/asf/
You should specify the version in your project as parent like the following:
org.apache
apache
23
You can download the appropriate
The Apache Maven team is pleased to announce the release of the Maven Parent
POMs Version 34.
Maven Parent POMs include Maven Parent POM itself, but also Maven Plugins
Parent POM, Maven Shared Components Parent POM, Maven Skins Parent POM and
Maven Doxia Tools Parent POM.
Hi,
We have a plan: instead of upgrading, we'll remove the dependencies, see
https://issues.apache.org/jira/browse/DOXIASITETOOLS-215
Doxia Sitetools 1.9.2 release is planned in a few days, then we'll need to
release every reporting plugin after.
Notice that these components are vulnerable,
Le mardi 18 février 2020, 03:00:44 CET Tim N a écrit :
> > maven-ant-tasks have been deprecated in favor of Maven Artifact Resolver
>
> Ant Tasks: https://maven.apache.org/resolver-ant-tasks/
>
> Fantastic, I'll give that a go. Is it possible to add a link to that
> project from
I see multiple options:
- use Maven Ant Tasks for that
- use exec
Le vendredi 21 février 2020, 05:03:10 CET Tim N a écrit :
> Maven Ant Tasks had some support for calling Maven from Ant:
> https://maven.apache.org/ant-tasks/examples/mvn.html.
>
The Apache Maven team is pleased to announce the release of the Apache Maven
Doxia Sitetools, version 1.9.2
Doxia Sitetools is an extension of base Doxia component that generates either
HTML sites, consisting of decoration and content that was generated by Doxia,
or documents like RTF or
The Apache Maven team is pleased to announce the release of the Apache Software
Foundation Parent POM Version 22.
https://maven.apache.org/pom/asf/
You should specify the version in your project as parent like the following:
org.apache
apache
22
You can download the appropriate
WARNING: finalName is read-only
There is a bug in Maven 3 that does not check, but this will be fixed in Maven
3.7.0 (see MNG-5001 [1]), then you'll get soon the expected failure
Either you should rename parent artifact to zookeeper, then you'll have to
rename the current zookeeper to
valent to our apache-maven module.
And given you need a specific assembly for the bin distribution, this would not
be an issue, isn't it?
Regards,
Hervé
[1] https://www-us.apache.org/dist/zookeeper/current/
>
> Thanks for your help
> Enrico
>
> Il sab 18 gen 2020, 12:46 Hervé BOU
't it?
>
> I will try, thank you for this good suggestion
>
>
> Enrico
>
> > Regards,
> >
> > Hervé
> >
> > [1] https://www-us.apache.org/dist/zookeeper/current/
> >
> > > Thanks for your help
> > > Enrico
> > >
> &
The Apache Maven team is pleased to announce the release of the Apache Maven
AntRun Plugin, version 3.0.0
This plugin provides the ability to run Ant tasks from within Maven. You can
even embed your Ant scripts in the POM!
https://maven.apache.org/plugins/maven-antrun-plugin/
You should
The Apache Maven team is pleased to announce the release of the Apache Maven
Shade Plugin, version 3.2.3
This plugin provides the capability to package the artifact in an uber-jar,
including its dependencies and to shade - i.e. rename - the packages of some of
the dependencies.
gt; > Create a nice day!
> > Stephan H. Wissel
> >
> > Phone: +65 96673269
> > Blog <https://www.wissel.net/blog> Twitter
> > <http://twitter.com/notessensei> LinkedIn
> > <http://sg.linkedin.com/in/notessensei> Xing
> > <https://www.xing.co
;
> Would that work for providing a demo?
>
> Create a nice day!
> Stephan H. Wissel
>
> Phone: +65 96673269
> Blog <https://www.wissel.net/blog> Twitter <http://twitter.com/notessensei>
> LinkedIn <http://sg.linkedin.com/in/notessensei> Xing
> <h
lution, but could add a can of
> (support) worms.
>
> What do you think?
>
> Create a nice day!
> Stephan H. Wissel
>
> Phone: +65 96673269
> Blog <https://www.wissel.net/blog> Twitter <http://twitter.com/notessensei>
> LinkedIn <http://sg.linkedin.com/in
tessensei>
> LinkedIn <http://sg.linkedin.com/in/notessensei> Xing
> <https://www.xing.com/profile/StephanH_Wissel>
>
> On Mon, Apr 6, 2020 at 6:16 AM Hervé BOUTEMY wrote:
> > you can create a GitHub repository, or a collection of repositories
> > whatever is necessa
Hi Stefan,
The code for Markdown parsing and extensions activation is in Doxia Markdown
module:
https://maven.apache.org/doxia/doxia/doxia-modules/doxia-module-markdown/xref/org/apache/maven/doxia/module/markdown/MarkdownParser.html#L133
I don't really reviewed how extensions are really
for reference, useful discussion on dev@maven of:
- plugins read-only parameters, per plugin conception,
- Maven 3.x bug that allows configuring such supposed read-only parameter (was
properly forbidden in Maven 2)
- this Maven core bug will be fixed in future Maven 3.7.0
- then some builds using
Le vendredi 24 avril 2020, 19:43:02 CEST Evan Ross a écrit :
> I have an Excel spreadsheet in my resources and find that my maven build
> vailes with “The process cannot access the file because it is being used by
> another process” when the sheet is open in Excel.
I don't have easily access to a
The Apache Maven team is pleased to announce the release of the Apache Maven
Site Plugin, version 3.9.0
This plugin is used to generate a site for the project. The generated site also
includes the project's reports that were configured in the POM.
Hello,
Maven uses HTTP ReasonPhrase: see MNG-6584 [1]
Notice that ReasonPhrase support has been removed in HTTP/2, then we should
define a new strategy: waiting for contributors from different horizons to be
interested in working on that to define (and this time properly document) a new
,
Hervé
Le jeudi 1 octobre 2020, 09:16:12 CEST Martin Höller a écrit :
> Hi!
>
> On 01. Okt. 2020 Hervé Boutemy wrote:
> > The Maven team is pleased to announce the release of the Apache Maven EAR
> > Plugin, version 3.1.0
> With maven-ear-plugin 3.1.0 I get this exception
The Maven team is pleased to announce the release of the Apache Maven EAR
Plugin, version 3.1.0
This plugin generates a J2EE Enterprise Archive (EAR) file.
https://maven.apache.org/plugins/maven-ear-plugin/
You should specify the version in your project's plugin configuration:
I just created a "buildconsumer" branch in Doxia [1] to have a live example of
the new simplified build POM that Maven 3.7.0 will allow [2]
As expected, this branch can't build with Maven 3.6.3, but can with Maven
3.7.0-SNAPSHOT.
And in my favorite IDE, as expected, dependency resolution does
The Maven team is pleased to announce the release of the Apache Maven WAR
Plugin, version 3.3.1
This plugin builds a Web Application Archive (WAR) file from the project output
and its dependencies.
https://maven.apache.org/plugins/maven-war-plugin/
You should specify the version in your
yes, sorry, I published 3.0.0-M2 release site, but I forgot that the release
had been cancelled...
will revert to the current effective release = 3.0.0-M1
Regards,
Hervé
Le vendredi 10 juillet 2020, 15:17:26 CEST Mark Prins a écrit :
> There is a mismatch between the published site and the
Le mardi 30 juin 2020, 15:27:37 CEST Charles Herrick a écrit :
> Thanks Greg, those urls do indeed resolve.
>
> We are left with urls in the Maven online documentation that still have the
> old org.codehaus.mojo forms that do NOT resolve.
> Do we have a plan to edit these links in the
when the shell itself
> can handle the sequences?
Windows shell can't handle ANSI escape code: that's the purpose of Jansi, and
what is represented in JAnsi front page http://fusesource.github.io/jansi/
What makes you say that a Windows shell can handle the sequences?
Regards,
Hervé
&g
as written in the documentation [2], you just need to add the property in your
root POM, and maven-release-plugin (if upgraded to 3.0.0-M1) will take care of
updating its value during release
I'm interested in any update in the doc to make this more clear, given it
seems it is not yet
Le samedi 11 juillet 2020, 20:38:28 CEST Lukasz Lenart a écrit :
> On 2020/07/11 17:38:32, Lukasz Lenart wrote:
> > As far I understood, I must define the property with a value "now" as
> > mentioned in the ticket [1]
> >
> > [1] https://issues.apache.org/jira/browse/MRELEASE-1029
>
>
the Maven Checkstyle Plugin source code is here:
https://github.com/apache/maven-checkstyle-plugin/
with links to CI and issue tracking
IMHO, updating its code should be easier than trying to tweak scripting with
Ant run.
And with the integration tests (in src/its, launched with "mvn -Prun-its
on crashes, I don't have any clue: details welcome
but on the performance impact of Jansi on Windows (to detect ANSI codes) when
there is much content (like with Surefire output), there is some partial work
started to improve by removing flush:
see https://github.com/fusesource/jansi/pull/150
The Apache Maven team is pleased to announce the release of the Apache Maven
Reporting Exec, version 1.5.1
This component provides an API to prepare report plugins execution with Maven 3.
https://maven.apache.org/shared/maven-reporting-exec/
You can download the appropriate sources etc. from
The Apache Maven team is pleased to announce the release of the Apache Maven
Site Plugin, version 3.9.1
This plugin is used to generate a site for the project. The generated site also
includes the project's reports that were configured in the POM.
w version and it seems
> https://maven.apache.org/plugins/maven-war-plugin/exploded-mojo.html#archive
> Classes Is not working anymore :(
>
> Is it intended?
>
> On Tue, 9 Jun 2020 at 18:43, Hervé Boutemy wrote:
> > The Maven team is pleased to announce the release of the Apa
The Maven team is pleased to announce the release of the Apache Maven WAR
Plugin, version 3.3.0
This plugin builds a Web Application Archive (WAR) file from the project output
and its dependencies.
https://maven.apache.org/plugins/maven-war-plugin/
You should specify the version in your
The Maven team is pleased to announce the release of the Apache Maven EJB
Plugin, version 3.1.0
This plugin generates a Java Enterprise JavaBean (EJB) file as well as the
associated client JAR.
https://maven.apache.org/plugins/maven-ejb-plugin/
You should specify the version in your project's
The Maven team is pleased to announce the release of the Apache Maven Shade
Plugin, version 3.2.4
This plugin repackages the project classes together with their dependencies
into a single uber-jar, optionally renaming classes or removing unused classes.
The Apache Maven team is pleased to announce the release of the Apache Maven
Archetype, version 3.2.0.
The Archetype Plugin allows the user to create a Maven project from an existing
template called an archetype.
It also allows the user to create an archetype from an existing project.
The Maven team is pleased to announce the release of the Apache Maven SCM
Publish Plugin, version 3.1.0
The maven-scm-publish-plugin is a utility plugin to allow publishing Maven
website to any supported SCM.
https://maven.apache.org/plugins/maven-scm-publish-plugin/
You should specify the
as Tomo said:
1. version ranges make dependencies selection unstable: is it really
necessary? (I personnally never use because of the build instability it adds,
given I'm trying to go even beyond stable build: I'm working hard on
Reproducible Builds [1]. Then my experience on detailed behaviour
The Maven team is pleased to announce the release of the Apache Maven EAR
Plugin, version 3.2.0
This plugin generates a J2EE Enterprise Archive (EAR) file.
https://maven.apache.org/plugins/maven-ear-plugin/
You should specify the version in your project's plugin configuration:
if you need to have consistent executable flags, you need to avoid getting it
from filesystem, because it is dependent on OS and user configuration
that's why for example, on such requirements in Maven (core), we use a
dedicated assembly descriptor instead of the generic one [1]
HTH
Hervé
[1]
there is a broader plan that tries to be documented at
https://maven.apache.org/developers/compatibility-plan.html
but given each plugin has its own lifecycle, without precise release schedule,
and voluntary work, it is followed at a "soft" speed
I know that one of my personal dreams on this
> Can anybody enlighten me on what is happening here and if this behaviour
> is documented anywhere? Or is this just the "read the freakin' source
> code, pal" kind of detail?
order in the same phase is not expected to be guaranteed: that's a design
choice (even if "choice" is not the best term
Le samedi 8 mai 2021, 17:03:05 CEST Alexander Kriegisch a écrit :
> Nooo! I don't need extra phases, nor do I have any desire to create
> custom lifecycles, even though I know this is possible. My point was: If
> we cannot rely on a specific order when executing plugins and executions
> within
Le dimanche 9 mai 2021, 07:52:21 CEST Alexander Kriegisch a écrit :
> Hervé BOUTEMY schrieb am 09.05.2021 03:31 (GMT +07:00):
> > Le samedi 8 mai 2021, 17:03:05 CEST Alexander Kriegisch a écrit :
> >> My question was how to achieve reliably predictable ordering. That
&g
The Maven team is pleased to announce the release of the Apache Maven GPG
Plugin, version 3.0.1
Signs the project artifacts with GnuPG.
https://maven.apache.org/plugins/maven-gpg-plugin/
You should specify the version in your project's plugin configuration:
org.apache.maven.plugins
The Maven team is pleased to announce the release of the Apache Maven Artifact
Plugin, version 3.1.0
Plugin to manage artifacts tasks
https://maven.apache.org/plugins/maven-artifact-plugin/
You should specify the version in your project's plugin configuration:
org.apache.maven.plugins
Stolwijk
>
> ~~~ Try to leave this world a little better than you found it and, when
> your turn comes to die, you can die happy in feeling that at any rate you
> have not wasted your time but have done your best ~~~
>
> Lord Baden-Powell
>
> On Fri, May
Hi,
To me, looking at javadoc or jxr output during "mvn site:run" is not supposed
to work: "mvn site:run" is here to help write markup for the site, to quickly
see the output when you update markdown/apt/... source
Why are you trying to use site:run to look at javadoc or jxr?
Notice, whatever
I just fixed it
https://github.com/mojohaus/versions-maven-plugin/issues/458
Regards,
Hervé
Le jeudi 29 avril 2021, 22:25:23 CEST Niels Basjes a écrit :
> Hi,
>
> Just now I wanted to lookup the documentation for the versions-maven-plugin
> yet I found that website
ok, I'll try againt to do a release: I hope users tested during that year, so
I won't have to cancel the vote again...
Regards,
Hervé
Le mercredi 5 mai 2021, 15:02:10 CEST Konrad Windszus a écrit :
> Hi,
> the current release 1.6 is from 2015 and I am suffering from
>
every existing plugin version can't be defined by Maven itself, given diversity
of plugins
then we need something extensible
there is https://issues.apache.org/jira/browse/MNG-5588 , proposing to mimic
dependencyManagement import to get an equivalent pluginManagement import
I love this idea,
not exactly: this already has been done for release 3.5.1
https://issues.apache.org/jira/browse/MPLUGIN-326
so you just need to upgrade a little bit :)
Regards,
Hervé
Le samedi 6 mars 2021, 22:22:36 CET Lutz Horn a écrit :
> > After creating a maven plugin I am seeing the automated text
> >
401 - 500 of 553 matches
Mail list logo
