Looks good to me content-wise. I have no issue with the look either :-)
Thanks
-Vincent
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: 26 May 2004 07:35
> To: Maven Developers List ([EMAIL PROTECTED])
> Subject: New site layout
>
> Hi all,
>
> I have started
Hi Rafal,
Thanks for your good feedback. I have 2 comments:
1/ Performing a jar then an unjar and again a jar is time consuming.
There is really no need to do this. It is forced on us by Maven which is
not so good. It's the same situation if you're doing code generation.
ATM you have to pass the
> - The bullet points are a little obtrusive and clash with the
> menu separators, e.g. IDE Integration and Propoganda
Just the same as normal in xdoc though?
> - Run a spell check for 'Propaganda'
Thanks.
>
> Did you want feedback about the content/structure or just layout etc?
Definitely t
The following comment has been added to this issue:
Author: dion gillard
Created: Wed, 26 May 2004 2:17 AM
Body:
Which version of JMeter?
-
View this comment:
http://jira.codehaus.org/browse/MPLATKA-2?page=commen
- The bullet points are a little obtrusive and clash with the menu
separators, e.g. IDE Integration and Propoganda
- Run a spell check for 'Propaganda'
Did you want feedback about the content/structure or just layout etc?
On Wed, 26 May 2004 15:34:35 +1000, Brett Porter
<[EMAIL PROTECTED]> wrote:
> 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
Hi all,
I have started the layout for the new Maven site as we approach 1.0 and
start to make space for the subprojects like Wagon, SCM and so on.
http://www.apache.org/~brett/maven-site-2/
So far just the new navigation and some stuff is missing from the old one,
but feedback is welcome.
Cheer
> -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
> > copied). I removed duplicated classes in
aheritier2004/05/25 22:25:29
Modified:javadoc/src/plugin-test maven.xml
Removed: javadoc/src/plugin-test project.properties
Log:
use path reference instead of property for maven.compile.src.set
Revision ChangesPath
1.7 +4 -4 maven-plugins/javadoc/src/plug
> 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).
Message:
The following issue has been closed.
-
View the issue:
http://jira.codehaus.org/browse/MPJAVADOC-24
Here is an overview of the issue:
-
Ke
Message:
The following issue has been closed.
-
View the issue:
http://jira.codehaus.org/browse/MPCHECKSTYLE-21
Here is an overview of the issue:
-
The following issue has been updated:
Updater: Arnaud HERITIER (mailto:[EMAIL PROTECTED])
Date: Wed, 26 May 2004 12:49 AM
Changes:
Version changed to 1.7
Version changed from 1.8
-
For
Message:
The following issue has been closed.
-
View the issue:
http://jira.codehaus.org/browse/MPXDOC-102
Here is an overview of the issue:
-
Key:
Message:
The following issue has been reopened.
Reopener: Arnaud HERITIER
Date: Wed, 26 May 2004 12:49 AM
must change the affects version
-
View the issue:
http://jira.codehaus.org/browse/MPXDOC-102
Here is an ov
Message:
The following issue has been closed.
-
View the issue:
http://jira.codehaus.org/browse/MPXDOC-102
Here is an overview of the issue:
-
Key:
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
The following issue has been updated:
Updater: Tim Shadel (mailto:[EMAIL PROTECTED])
Date: Tue, 25 May 2004 8:01 PM
Comment:
This patch fixes a typo in the first patch submitted against this issue (ejb.patch,
hence the name for this patch). The patch incorrectly calls ejb:client i
aheritier2004/05/25 15:18:22
Modified:javadoc plugin.jelly
Log:
use a reference to maven.compile.src.set instead of the property.
Revision ChangesPath
1.41 +8 -20 maven-plugins/javadoc/plugin.jelly
Index: plugin.jelly
=
Jason van Zyl wrote:
On Tue, 2004-05-25 at 12:05, Vincent Massol wrote:
Hi Carlos,
I still believe we're missing a "local/private" repository kind of stuff
to share non-public data between projects. Or something equivalent.
I honestly don't understand this requirement. What is really the
differen
In case you didn't notice : jira mails are sent again to the list.
If there are any issues, please add a chore on jira.codehaus.org.
--
Mvgr,
Martin
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [
Performing an update of maven-components ...
Updates occured, build required ...
P maven-plugins/project.xml
P maven-plugins/maven-clean-plugin/project.xml
P maven-plugins/maven-compiler-plugin/project.xml
P maven-plugins/maven-hello-plugin/project.xml
P maven-plugins/maven-jar-plugin/project.xm
Yes it works
Thanks a lot Martin!!
Arnaud.
> -Message d'origine-
> De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Envoyé : mardi 25 mai 2004 19:02
> À : [EMAIL PROTECTED]
> Objet : [jira] Commented: (MPXDOC-67) Add an option to site generation to
> use clover xref files rather th
On Tue, 2004-05-25 at 16:08, [EMAIL PROTECTED] wrote:
> evenisse2004/05/25 13:08:28
>
> Modified:maven-plugins/maven-clean-plugin project.xml
>maven-plugins/maven-compiler-plugin project.xml
>maven-plugins/maven-hello-plugin project.xml
>ma
evenisse2004/05/25 13:08:28
Modified:maven-plugins/maven-clean-plugin project.xml
maven-plugins/maven-compiler-plugin project.xml
maven-plugins/maven-hello-plugin project.xml
maven-plugins/maven-jar-plugin project.xml
maven-plug
> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> Sent: 25 May 2004 19:38
> To: Maven Developers List
> Subject: RE: [Strategy] How to manage several subprojects as one
project?
>
> On Tue, 2004-05-25 at 12:05, Vincent Massol wrote:
> > Hi Carlos,
>
> > I still beli
On Tue, 2004-05-25 at 12:05, Vincent Massol wrote:
> Hi Carlos,
> I still believe we're missing a "local/private" repository kind of stuff
> to share non-public data between projects. Or something equivalent.
I honestly don't understand this requirement. What is really the
difference between refe
The following issue has been updated:
Updater: Martin van den Bemt (mailto:[EMAIL PROTECTED])
Date: Tue, 25 May 2004 1:05 PM
Changes:
Comment was deleted.
-
For a full history of the issue, see:
h
The following comment has been added to this issue:
Author: Martin van den Bemt
Created: Tue, 25 May 2004 1:01 PM
Body:
Please ignore comment.. Test to see if jira mails are arriving again at the maven
mailinglists..
Hi Carlos,
The requirement to have a single Cactus framework jar is a *MUST* have
(like a business requirement). It doesn't make sense to deliver 3 jars:
cactus-share-12-13-14.jar, cactus-share-13-14, cactus-j2ee-.jar. These jars have no functional meaning at all. That
wouldn't do for users.
I st
Hi Vincent,
IMHO points 1 and 2 seem to break Maven "philosophy". The Cactus
distribution should comprise more than one jar, and that shouldn't be a
problem.
I thinked about using files from a dependency jar in order to share
information between different projects, for example Spring database
co
I am not sure if anyone else is having this problem I am trying to
use the maven-latka plugin and using the Jmeter Convert functionality
and it doesn't bring over any of the parameter values. So the newly
created latka suite does not run. I would then need to add all the
parameters to the latka
Performing an update of maven-components ...
Updates occured, build required ...
P maven-core-it/README.txt
---
Building mboot ...
---
--
jvanzyl 2004/05/25 05:49:13
Modified:maven-core-it README.txt
Log:
o adding a couple more integration tests i want to see before the alpha
is released.
Revision ChangesPath
1.2 +6 -0 maven-components/maven-core-it/README.txt
Index: README.txt
===
Jerome,
Thank you for your answers. However my goal is to use Maven and to
discuss a possible strategy within Maven to support this use case. The
Cactus project already has a build and it works fine. I'm trying to
figure out the best possible strategy with Maven.
So far you're the only one to ha
On Mon, 2004-05-24 at 08:09, Vincent Massol wrote:
> Hi Jerome,
>
> > -Original Message-
> > From: Jerome Lacoste [mailto:[EMAIL PROTECTED]
> > Sent: 24 May 2004 06:48
> > To: Maven Developers List
> > Subject: Re: [Strategy] How to manage several subprojects as one
> project?
> >
> > On
Heritier Arnaud wrote:
+1
Couldn't we also move(/copy :-( ) the changelog:create-cvspass" to the scm plug-in.
I think that functionally the create-cvspass is more a scm related function even if it is used for changelog
yup. seems logical.
We could move the changelog:create-cvspass code to scm:creat
+1
Couldn't we also move(/copy :-( ) the changelog:create-cvspass" to the scm plug-in.
I think that functionally the create-cvspass is more a scm related function even if it
is used for changelog
We could move the changelog:create-cvspass code to scm:create-cvspass and then keep
the changelog:
brett 2004/05/25 00:05:46
Modified:dashboard project.properties
dashboard/src/plugin-test maven.xml project.properties
Log:
inheritence woes
Revision ChangesPath
1.7 +3 -0 maven-plugins/dashboard/project.properties
Index: project.propertie
40 matches
Mail list logo
