On 17/03/2010, at 1:45 AM, Anders Hammar wrote:
> To carry on my own thread, would it be possible to bump the dependency to
> the maven artifact to version 2.1 or later (for all apache plugins)?
> Another solution could be to add dependency management to change the
> transitive dependency to wago
Hi,
I was thinking of releasing the Help plugin. There's only two issues fixed, but
one is the pesky deprecated warnings: http://jira.codehaus.org/browse/MPH-59
There aren't any others in the 2.1.1 bucket, but there are 14 unscheduled
issues. Would anyone like to fix one of them first?
Cheers,
It's for when you release them together, it will match up the versions and
replace them. Either approach works.
I think your change is good, ${project.version} is preferable. It both
indicates to the reader that "it's the same as the current project and that's
important", as well as causing few
I didn't know this one: how can release plugin know that another artifact
version should be kept in sync with current one?
I took this pattern in Maven 3 trunk and found it quite good.
I'm interested in any feeed back
Le mardi 16 mars 2010, Stephen Connolly a écrit :
> I thought best practice wa
To carry on my own thread, would it be possible to bump the dependency to
the maven artifact to version 2.1 or later (for all apache plugins)?
Another solution could be to add dependency management to change the
transitive dependency to wagon to a version with a signature (1.0-beta-3 or
whatever).
Hervé BOUTEMY wrote:
Staging repo:
https://repository.apache.org/content/repositories/maven-008/
+1, looks generally good though IMHO the rendering of tables like in [0,
1] has been degraded due to the enforcement of equal column widths.
Benjamin
[0] http://maven.apache.org/plugins/index
Use a svn client and checkout source.
TortoiseSVN is a good one for Windows.
Subir
-Original Message-
From: Greeny [mailto:markus.milc...@heuboe.de]
Sent: Tuesday, March 16, 2010 4:15 PM
To: dev@maven.apache.org
Subject: Re: Request to Maven Site Plugin
Hey,
i think i've got an idea why
Hey,
i think i've got an idea why this does not work.
It is the length of the domain.
I can change the domain from "hbintern" to "hbin" and it works.
The plugin does not support tlds with more than 4 characters.
By the way: Is there any easier way to copy the sources from a plugin than
copy every
I thought best practice was to leave the version as is and let maven release
plugin update it for you?
On 15 March 2010 17:26, wrote:
> Author: hboutemy
> Date: Mon Mar 15 17:26:16 2010
> New Revision: 923347
>
> URL: http://svn.apache.org/viewvc?rev=923347&view=rev
> Log:
> use ${project.versio
We don't tend to test or support gcj. Have you tried it with a different JDK?
On 16/03/2010, at 12:33 PM, Hugo Vasconcelos Saldanha wrote:
> Hi,
>
> When I try to build maven-2.2.x from SVN repository, it fails with the
> following error. Am I doing something wrong?
>
> (...)
> [INFO]
> --
Hi,
When I try to build maven-2.2.x from SVN repository, it fails with the
following error. Am I doing something wrong?
(...)
[INFO]
[INFO] Building Maven Artifact
[INFO]task-segment: [install]
[INFO] ---
11 matches
Mail list logo
