> Ok, I'm just finishing the generating of the Jelly harness.
> So I'll test that and then I'll put it somewhere for
> download. I wouldn't mind getting some feedback anyway. Be
> warned though that it doesn't much look like the current
> output. It looks like this:
>
> http://www.apache.org/~
On Wed, 2004-05-26 at 13:44, Jeffrey D. Brekke wrote:
> I'd like to give it a spin also. I have 65 projects under reactor and
> currently have to spawn maven for the site goal for it to generate.
Ok, I'm just finishing the generating of the Jelly harness. So I'll test
that and then I'll put it so
I'd like to give it a spin also. I have 65 projects under reactor and
currently have to spawn maven for the site goal for it to generate.
> On Wed, 26 May 2004 18:41:17 +0200, Rafal Krzewski <[EMAIL PROTECTED]> said:
> Jason van Zyl wrote:
>> The new xdoc plugin is deadly fast and if you wa
Jason van Zyl wrote:
The new xdoc plugin is deadly fast and if you want to do a little
experimenting I'll give you a copy of the new xdoc plugin that you can
try with your Objectledge project. Many of the m1 plugins are going to
die a quick death at the hands of well tested m2 plugins that can be
u
On Wed, 2004-05-26 at 06:08, Rafal Krzewski wrote:
> Heritier Arnaud wrote:
> > It's effectively a big problem.
> > The last time I generated the doc for all maven-plugins, I needed 1Gb of memory !!
>
> I cannot generate full docs for Objectledge, no matter how much -Xmx I
> give. Instead of OutO
Heritier Arnaud wrote:
It's effectively a big problem.
The last time I generated the doc for all maven-plugins, I needed 1Gb of memory !!
I cannot generate full docs for Objectledge, no matter how much -Xmx I
give. Instead of OutOfMemory error, I get IOException: cannot allocate
memory when launc
> -Message d'origine-
> De : Brett Porter [mailto:[EMAIL PROTECTED]
> Envoyé : mercredi 26 mai 2004 07:48
> À : 'Maven Developers List'
> Objet : RE: Maven 1.0 final work list
>
>
> > I just committed the last maven.xml for the plugin test.
&
It's effectively a big problem.
The last time I generated the doc for all maven-plugins, I needed 1Gb of memory !!
Arnaud
> -Message d'origine-
> De : Rafal Krzewski [mailto:[EMAIL PROTECTED]
> Envoyé : mercredi 26 mai 2004 10:12
> À : Maven Developers List
> Ob
Brett Porter wrote:
Hi,
Apart from the documentation that I am working on at the moment, is there
anything else that needs to be completed for Maven 1.0?
I'm sorry I haven't wrote about it earlier but I have been really busy.
I did some testing regarding
http://jira.codehaus.org/browse/MPMULTIPROJ
> I just committed the last maven.xml for the plugin test.
> I commented the assertFileExists to not break the build with
> a failing test case. If you have a few minutes to see if it
> seems correct or if there's something weird?
Got it - I'll look into it tonight.
> Thanks. The problem is th
> -Message d'origine-
> De : Brett Porter [mailto:[EMAIL PROTECTED]
> Envoyé : mercredi 26 mai 2004 07:04
> À : 'Maven Developers List'
> Objet : RE: Maven 1.0 final work list
>
> > Actually I fixed MPJAVADOC-24 (doc-files directories are not
>
> Actually I fixed MPJAVADOC-24 (doc-files directories are not
> copied). I removed duplicated classes in the "all classes"
> list. I'm working on MPJAVADOC-5 (enabling javadoc for
> maven.compile.src.set) but I don't succeed to create a test
> case using maven:appPath. I don't know if I have a
> Hi,
Hello
>
> Apart from the documentation that I am working on at the moment, is there
> anything else that needs to be completed for Maven 1.0?
>
> IMO we need to get the javadoc, xdoc plugins cleaned up and release a new
> version (both went out with bugs in RC3 that were introduced late).
Hi,
Apart from the documentation that I am working on at the moment, is there
anything else that needs to be completed for Maven 1.0?
IMO we need to get the javadoc, xdoc plugins cleaned up and release a new
version (both went out with bugs in RC3 that were introduced late). Arnaud -
how is your
14 matches
Mail list logo
