nsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/Maven-Philosophy...-tf2048781.html#a5681748
Sent from the Maven - Users forum at Nabble.com.
-
> -Original Message-
> From: Jimisola Laursen [mailto:[EMAIL PROTECTED]
> Sent: dimanche 6 août 2006 19:49
> To: users@maven.apache.org
> Subject: Re: Maven Philosophy...
>
>
>
> Scott Battaglia wrote:
> >
> > Projects released under an open s
Yes, and anything you feel like building from scratch or implementing
a Maven plugin for... ;-)
Wayne
On 8/6/06, Jimisola Laursen <[EMAIL PROTECTED]> wrote:
That leaves me with Cobertura and Emma. Correct?
Regards,
Jimisola
--
View this message in context:
http://www.nabble.com
ing of in my previous post but I wrote
non-commercial when I meant commercial. That is, this is for a commercial
product - not a non-commercial.
That leaves me with Cobertura and Emma. Correct?
Regards,
Jimisola
--
View this message in context:
http://www.nabble.com/Maven-Philosophy...-tf204
]
Sent: dimanche 6 août 2006 15:05
To: users@maven.apache.org
Subject: RE: Maven Philosophy...
vmassol wrote:
[snip]
FWIW this is currently supported in the Clover plugin. The plugin does
this
by creating clovered artifacts that it installs in your local repository
and
swaps a project&#
> -Original Message-
> From: Jimisola Laursen [mailto:[EMAIL PROTECTED]
> Sent: dimanche 6 août 2006 15:05
> To: users@maven.apache.org
> Subject: RE: Maven Philosophy...
>
>
>
> vmassol wrote:
> >
> > [snip]
> > FWIW this is currently su
ura doesn't play well with AspectJ (at least to my knowledge) and Emma
doesn't seem to have a Maven 2 Plugin works at the time. Am I wrong? Are
there any other alternatives?
Regards,
Jimisola
--
View this message in context:
http://www.nabble.com/Maven-Philosophy...-t
> -Original Message-
> From: Nelson Carpentier [mailto:[EMAIL PROTECTED]
> Sent: vendredi 4 août 2006 02:47
> To: users@maven.apache.org
> Subject: Maven Philosophy...
[snip]
> 2) Coverage. Not only do we want to know what our "unit test" coverages
>
I've encountered some nigh-philosophical difficulties with the
adoption of Maven, and I was
wondering if anyone here could help me talk through them...?
I think Maven is a great idea, and adopting some of the best practices
has made my life
as the build developer a lot easier. I have been a Maven
rbanisation Des Développements
DSI/PAT/DAOS/SUDD
Tel : (+33) 01 60 76 54 66
[EMAIL PROTECTED]
~
-Message d'origine-
De: dan tran [mailto:[EMAIL PROTECTED]
Envoyé: lundi 17 juillet 2006 17:25
À: Maven Users List
Objet: Re: SCM with Maven
01 60 76 54 66
[EMAIL PROTECTED]
~
-Message d'origine-
De : dan tran [mailto:[EMAIL PROTECTED]
Envoyé : lundi 17 juillet 2006 17:25
À : Maven Users List
Objet : Re: SCM with Maven philosophy
The main purpose if scm:checkout is to all
The main purpose if scm:checkout is to allow user to fetch the source base
on a scmurl input ( thru -DconnectionUrl),
However it also can pickup the connectionUrl in the pom.xml of the execution
directory ( your pom). Because of that
and to work for both cases, your source files are checked out to
Hello,
I'd like to know what is the philosophy of using maven2 scm plugin.
I put my pom.xml at the root dir of my project.
Projet under SVN :
MyProject/Pom.xml
MyProject/Src/main/java/...
...
So with the maven checkout command (mvn scm:checkout...), this pom is located
in
13 matches
Mail list logo
