You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cactus-dev@jakarta.apache.org by Julien Dubois <ju...@julien-dubois.com> on 2003/09/27 12:56:26 UTC

Mavenizing!

Hi guys,

I was following your Clover discussion : we'll also need a license for the 
maven-clover-plugin.

Vincent : can you create empty files (project.xml, project.properties, 
maven.xml) in all the samples/ and integration/ subprojects?
I'll then be able to send you some patches.

Julien.



Re: Mavenizing!

Posted by Julien Dubois <ju...@julien-dubois.com>.
Hello everybody,

3 things concerning Maven :

1. CVS access
I can't do a "cvs add" as I've got no write access. At least that's the error 
message I got.
So I put my new files here : http://www.julien-dubois.com/jakarta-cactus/

So I just did this (attached) mostly worthless patch.
I'm using Cervisia (it's the default CVS GUI embedded into Konqueror) to 
create the patch. Tell me if it's working ok.

2. Building the documentation
I can't generate the documentation with the current navigation.xml files. 
Using the Maven/xdocs format, they should be like this :
http://picocontainer.cvs.codehaus.org/viewcvs.cgi/*checkout*/pico/xdocs/
navigation.xml?content-type=text%2Fplain&rev=1.26&root=picocontainer

IMHO, we should copy the current navigation.xml files to some 
navigation-cactus.xml files, and do a search'n replace in the current Ant 
code.
Then we'll be able to have normal navigation.xml files.
I'll do them, no problem, I did many of those last week at work.

3. Testing & mock objects
With my current Maven files, some of the tests will not run. I know it, I've 
got to learn how to use Mock objects first. Because for the moment I've got 
no idea how this is supposed to work. I'll learn that this week.

Julien.

Re: Mavenizing!

Posted by Christopher Lenz <cm...@gmx.de>.
Julien Dubois wrote:
> Hi guys,
> 
> I was following your Clover discussion : we'll also need a license for the 
> maven-clover-plugin.
> 
> Vincent : can you create empty files (project.xml, project.properties, 
> maven.xml) in all the samples/ and integration/ subprojects?
> I'll then be able to send you some patches.

Please not that you can inlude new files in your patch. You just need to 
"cvs add" them, and then run "cvs diff -N -u" (where the -N option means 
"include new files").

The only scenario where this does not work is if you need new 
directories, which need to be present in CVS and thus require you to 
have write access to the repo. But IIUC there is no need for new 
directories here, so the normal patch-creation procedure should be enough.

-- 
Christopher Lenz
/=/ cmlenz at gmx.d


Re: Mavenizing!

Posted by Christopher Lenz <cm...@gmx.de>.
Julien Dubois wrote:
> Hi guys,
> 
> I was following your Clover discussion : we'll also need a license for the 
> maven-clover-plugin.
> 
> Vincent : can you create empty files (project.xml, project.properties, 
> maven.xml) in all the samples/ and integration/ subprojects?
> I'll then be able to send you some patches.

Please not that you can inlude new files in your patch. You just need to 
"cvs add" them, and then run "cvs diff -N -u" (where the -N option means 
"include new files").

The only scenario where this does not work is if you need new 
directories, which need to be present in CVS and thus require you to 
have write access to the repo. But IIUC there is no need for new 
directories here, so the normal patch-creation procedure should be enough.

-- 
Christopher Lenz
/=/ cmlenz at gmx.d


---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org


RE: Mavenizing!

Posted by Vincent Massol <vm...@pivolis.com>.
> -----Original Message-----
> From: Julien Dubois [mailto:julien@julien-dubois.com]
> Sent: 27 September 2003 12:56
> To: Cactus Developers List
> Subject: Mavenizing!
> 
> Hi guys,
> 
> I was following your Clover discussion : we'll also need a license for
the
> maven-clover-plugin.

We have one already... I'm sending the jar to you by private email. Just
drop it in your ANTHOME/lib directory. That said you don't need to use
it to build cactus unless you use the top level "ant release" target or
you turn clovering on.

> 
> Vincent : can you create empty files (project.xml, project.properties,
> maven.xml) in all the samples/ and integration/ subprojects?
> I'll then be able to send you some patches.

Julien, can you send us the full files by email to the cactus dev
mailing lists. We'll then commit them and you will then be able to send
patches against them.

Thanks
-Vincent

> 
> Julien.
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: cactus-dev-help@jakarta.apache.org



RE: Mavenizing!

Posted by Vincent Massol <vm...@pivolis.com>.
> -----Original Message-----
> From: Julien Dubois [mailto:julien@julien-dubois.com]
> Sent: 27 September 2003 12:56
> To: Cactus Developers List
> Subject: Mavenizing!
> 
> Hi guys,
> 
> I was following your Clover discussion : we'll also need a license for
the
> maven-clover-plugin.

We have one already... I'm sending the jar to you by private email. Just
drop it in your ANTHOME/lib directory. That said you don't need to use
it to build cactus unless you use the top level "ant release" target or
you turn clovering on.

> 
> Vincent : can you create empty files (project.xml, project.properties,
> maven.xml) in all the samples/ and integration/ subprojects?
> I'll then be able to send you some patches.

Julien, can you send us the full files by email to the cactus dev
mailing lists. We'll then commit them and you will then be able to send
patches against them.

Thanks
-Vincent

> 
> Julien.
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: cactus-dev-help@jakarta.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org