Since the question of choosing an Eclipse Integration is often asked, I
just worked on the "Eclipse Integration" page from Maven Users Wiki:
http://docs.codehaus.org/display/MAVENUSER/Eclipse+Integration
I started a comparison matrix with basic project informations.
This Wiki is public: feel free
Selon Rodrigo Madera <[EMAIL PROTECTED]>:
> Nice work.
thank you
>
> However there is a deprecated indicator on the OSGi Bundles item (under
> Eclipse Developer).
> What exactly do you mean with it?
*I* don't mean anything: it was in the page before I changed it. Since I don't
know the topic, I l
1. MPIR version
MPIR is a plugin, with its own version independant from any other plugin, even
from m-site-p
Then you need to choose the plugin version like any other version (the fact
that it is not only a classical plugin but also a reporting plugin does not
change anything)
then see pluginMan
there is one misconception: the project *is not built with* Maven Webapp
Archetype, but it *was generated from* Maven Webapp Archetype
Once a project is generated from a Maven Archetype, it is a normal project, you
can forget about its inception: the whole generated content is yours, to be
main
Hi,
I don't see where Maven Ant Tasks creates such threads
Did you find more explicit traces on /where/ the threads are created?
BTW, please precise your config (versions of JVM/Ant/Maven Ant Tasks).
Regards,
Hervé
- Mail original -
De: "Wei Feng Niu"
À: users@maven.apache.org
Envoyé:
18-SNAPSHOT is ready
but there are a few feedbacks on edge case issues: I'm torn if we should
release now or wait for 3.5.1
Regards,
Hervé
- Mail original -
De: "Maxim Solodovnik"
À: "Maven Users List"
Envoyé: Jeudi 3 Mars 2016 09:54:10
Objet: Re: maven-site-plugin 3.5 ClassNotFoundE
no, there is no feature like this: in general, toolchains configuration is
static
in your case, using a variable like this makes the configuration ambiguous,
since the jdk 1.6 and 1.7 point to the same location: I'm not sur it's a good
idea.
But perhaps it can be useful to others.
We are worki
I must admit the "download the internet" effect is true: everybody can see it
when running Maven for the first time on a computer.
Is that really a problem? IMHO no:
- for personal use, this is done only once (and my ADSL line is fine)
- for corporate use, a repository manager is really welcome,
this is unCheckedPluginList (singular plugin), not unCheckedPluginsList
:)
Regards,
Hervé
- Mail Original -
De: "nicolas de loof"
À: "Maven Users List"
Envoyé: Lundi 17 Août 2009 16h23:53 GMT +01:00 Amsterdam / Berlin / Berne /
Rome / Stockholm / Vienne
Objet: enforcer and unCheckedPl
there is a convention for Maven POMs: [1]
"in the wild", since Maven defines its POM model with Modello, the order
defined in maven.mdo is the order naturally used when writing POMs using
MavenXpp3Writer: see the descriptor reference [2] and MavenXpp3Writer javadoc
[3]
maven.mdo was modified in
release plugin has an update-versions goal
https://maven.apache.org/maven-release/maven-release-plugin/update-versions-mojo.html
- Mail original -
De: "Stephane Passignat"
À: "Maven Users List"
Envoyé: Vendredi 24 Juin 2022 21:19:18
Objet: plugin to update version to patch version
Hell
I see one clarification to add to your "by value" explanation: what is imported
is the dependencyManagement content from the *effective* imported model, ie
with its interpolation (properties substitution) already done
I don't see how any property from the imported model could affect the importi
>> importing model
>>
> OK, good to know.
It also can't be overwritten from the importing model, so what purpose does
it serve to publish these properties in a bom?
Regards,
Delany
On Thu, 18 Aug 2022 at 20:56, Laird Nelson wrote:
> On Wed, Aug 17, 2022 at 11:33 PM Herve Bou
documentation probably also needs love:
you found the mini-guide, but not the plugin reference documentation that
explains much more:
https://maven.apache.org/archetype/maven-archetype-plugin/index.html
I'm not sure mini guide was updated as it should
Regards,
Hervé
On 2023/10/05 20:38:20 Dav
:15:50 Herve Boutemy wrote:
> documentation probably also needs love:
> you found the mini-guide, but not the plugin reference documentation that
> explains much more:
> https://maven.apache.org/archetype/maven-archetype-plugin/index.html
>
> I'm not sure mini guide w
lled
> archetype in a work directory, which fails with the given error. I'm
> thinking that running "c-f-p" in the root of the archetype project is not
> exactly what is required, but I have no idea.
>
> I still have no idea why it's saying it's not an arc
investigate why it has not been recognized as an archetype
Regards,
Hervé
On 2023/10/07 10:05:06 Herve Boutemy wrote:
> it looks you're getting an issue finding your archetype jar in your local
> repository, and the message is misleading: I'd love to improve it
>
> can yo
we'll probably need to improve over
https://issues.apache.org/jira/browse/MCOMPILER-499
Regards,
Hervé
On 2023/10/07 16:24:53 "Gary D. Gregory" wrote:
> I just saw this on the console:
>
> [INFO] --- compiler:3.11.0:compile (default-compile) @ commons-io ---
> [INFO] Changes detected - recompi
issue created https://issues.apache.org/jira/browse/MCOMPILER-549
On 2023/10/07 20:36:15 Herve Boutemy wrote:
> we'll probably need to improve over
> https://issues.apache.org/jira/browse/MCOMPILER-499
>
> Regards,
>
> Hervé
>
> On 2023/10/07 16:24:53 "Gary
I tried to build the project and see the failure, but could not
and reading explanations did not help me
what we need is a basic commit that works, followed by a PR upgrading Doxia and
that does not work with the NPE that you are saying happens
Regards,
Hervé
On 2023/10/10 02:44:08 Alexander K
et/it/CreateReport/build.log
> # At the end of the file, there is the error.
> # Scroll up a bit to see the Maven stacktrace.
>
> --------
>
> Hope this helps.
> --
> Alexander Kriegisch
> https://scrum-master.de
> I also want to require a description for each module.
you mean enforce a different description in a module vs its parent value?
- Mail original -
De: "Delany"
À: "Maven Users List"
Envoyé: Jeudi 8 Février 2024 06:27:55
Objet: enforce module descriptions
Hi. I'm using enforcer to requ
I did a schema to represent the flow between all pieces:
https://maven.apache.org/plugins/maven-site-plugin/history.html
You're interested into Doxia + Doxia Site Tools, which are independent.
The fact that there is an artifact at the beginning of Doxia Site Tools is due
to the skin, that is an a
23 matches
Mail list logo
