Hi,
What about the properties common to many plugins
like the java version used in compiler, javadoc and aspectCompiler ?
Raphaël
2006/8/22, Barrie Treloar <[EMAIL PROTECTED]>:
> I've seen all sorts of format for parameters as with everything the
> format is arbitrary but it would be good to
On 8/22/06, Nathan Beyer <[EMAIL PROTECTED]> wrote:
One thing I noticed was the repository configurations. In particular the
"releases" disabled and "snapshots" enabled. Like this:
[del]
Have you tested this out? I've found that when 'releases' is disabled, the
repository seems to be complete
On 21 Aug 06, at 5:58 PM 21 Aug 06, [EMAIL PROTECTED] wrote:
Author: jdcasey
Date: Mon Aug 21 14:58:39 2006
New Revision: 433384
URL: http://svn.apache.org/viewvc?rev=433384&view=rev
Log:
Adding alternative deployment repository parameter for the
deploy:deploy mojo, and bumping the POM versi
One thing I noticed was the repository configurations. In particular the
"releases" disabled and "snapshots" enabled. Like this:
apache.snapshots
Maven Snapshots
http://people.apache.org/maven-snapshot-repository
false
Hi all,
I've checked out M2 in accordance with "Guide to Building Maven 2.0":
svn co https://svn.apache.org/repos/asf/maven/trunks maven
[EMAIL PROTECTED] ~/maven/components $ env | grep M2_HOME
M2_HOME=/home/maven/bin/maven/current
[EMAIL PROTECTED] ~/maven/components $ echo $PATH
:/home/mave
I've seen all sorts of format for parameters as with everything the
format is arbitrary but it would be good to have a standard guideline
to follow.
Anyone else have any thoughts?
Any guidance on this would be good for consistency.
What is suggested looks good.
Hi,
While working on MJAR-7, John and I discussed a possible standard for
plugin parameters naming conventions. Which basically boil down to:
field/property = noun|verbNoun
expression= prefix.noun|verbNoun
So for MJAR-7 we have
field = forceCreation
expression = jar.forceCre
Hi folks,
can somebody sync the M2 repo from Codehaus please? XStream has released 48h
ago and it does not yet show up at ibiblio ...
Thanks,
Jörg
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EM
On 8/21/06, Brett Porter <[EMAIL PROTECTED]> wrote:
I'm missing the context on this - I'm not sure what primaryArtifact is
set to, but it sounds like you've got the right idea there (though it
should be artifact.getType(), ie war, not aar)
Thank you, I've filed MWAR-69.
Jochen
--
My wife Mar
On 18/8/06 1:26 AM, Arnaud Bailly wrote:
Thanks a lot. I will try to make things moving a bit.
Cool. Keep us up to date with your progress.
- Brett
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:
I think it's best to do repository-side and could be something in Archiva.
The only issue I see here is that you won't want to move the snapshot to
the release because much of the information won't have been repopulated
for the release (eg, the POM that is inside the JAR).
I think you want to
I'm missing the context on this - I'm not sure what primaryArtifact is
set to, but it sounds like you've got the right idea there (though it
should be artifact.getType(), ie war, not aar)
On 17/8/06 5:38 PM, Jochen Wiedmann wrote:
Hi,
the maven-war-plugin contains the following code snipped:
Looks good!
On 16/8/06 12:30 PM, Barrie Treloar wrote:
http://docs.codehaus.org/display/MAVENUSER/Patching+Maven+Plugins
I've written up my notes on what I have done to patch maven plugins
that describes how to build the trunk of a plugin, apply patches, and
deploy the plugin to an internal com
Works fine for me.
Thanks for work on MPECLIPSE-123, as my patch was just a quick & dirty
solution.
Nico.
Stephane Nicoll a écrit :
Hi,
The maven eclipse plugin 1.11.1 is ready to be released (to be
included in m1.1 final).
A snapshot has been deployed [1]. The changes are available in Ji
14 matches
Mail list logo
