> The layout in repository was intentionally fixed. There are good reasons
for
> that.
> I think that support for other protocols than file:// and http:// can be
> considered
> if there will be more users demanding it.
> If you want to use ftp:// you can rise an issue in JIRA.
>
> I personally th
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, June 03, 2003 1:15 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Setting up Maven-New
>
>
> > > In particular because I have seen better decomposition allowing me to
> > > e.g. extend the Project class a
> > In particular because I have seen better decomposition allowing me to
> > e.g. extend the Project class and parse the project.xml myself.
> >
> Certainly there are side effects of the decomposition made in maven-new
> which might result in such temptation to "personalize" your instance
> of mav
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, June 03, 2003 12:26 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Setting up Maven-New
>
>
> I know that Maven new is not really usable yet,
I would say: it is really unusable ;)
>but the
> committers
I know that Maven new is not really usable yet, but the committers have got
a setup that they can use to test their changes, right? I want to have this
kind of setup, enabling me to evaluate Maven new. If I have to create my
own plugins, I want to make sure I use Maven new instead of Maven. In
p
AFAIK: maven-new is not yet usable.
Michal
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, June 03, 2003 12:09 PM
> To: [EMAIL PROTECTED]
> Subject: Setting up Maven-New
>
>
> Can someone guide me through the process of setting up and using
> M
Can someone guide me through the process of setting up and using Maven New?
I always seem to get an XMLRPC exception upon execution of "run-client -g",
so I must be doing something wrong...
On the client
Exception in thread "main" java.lang.reflect.InvocationTargetException
at sun.reflect.
> -Original Message-
> From: Matt Johnson [mailto:[EMAIL PROTECTED]
> Sent: 03 June 2003 10:41
> To: Maven Developers List
> Subject: Re: maven.bat and -Xmx, remove MAVEN_DEFAULT_OPTS?
>
> How 'bout just defaulting MAVEN_OPTS if and only if it ain't already
set
> (see attached diff). Th
How 'bout just defaulting MAVEN_OPTS if and only if it ain't already set
(see attached diff). This basically abolishes MAVEN_DEFAULT_OPTS and
sets MAVEN_OPTS if it's not already set. If the user sets it at all, it
overrides the -Xmx160m.
(Disclaimer: Works On My Machine)
Matt
Vincent Massol
> -Original Message-
> From: news [mailto:[EMAIL PROTECTED] On Behalf Of dIon Gillard
> Sent: 03 June 2003 04:20
> To: [EMAIL PROTECTED]
> Subject: Re: maven.bat and -Xmx, remove MAVEN_DEFAULT_OPTS?
>
> Vincent Massol wrote:
>
> >>Isn't this what MAVEN_OPTS is for?
> >>
> >>The user can
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: 03 June 2003 08:24
> To: Maven Developers List
> Subject: Re: [clean] Documentation update
>
> Just creating an issue will do. Jira will mail all the committers when
a
> new issue is created.
I don't know w
dion2003/06/02 23:36:56
Modified:src/plugins-build/clean project.properties plugin.jelly
project.xml
src/plugins-build/clean/xdocs goals.xml changes.xml
index.xml
Log:
Apply patch for MAVEN-459
Fix bugs in 'new' goa
Just creating an issue will do. Jira will mail all the committers when a
new issue is created.
--
dIon Gillard, Multitask Consulting
Blog: http://www.freeroller.net/page/dion/Weblog
Work: http://www.multitask.com.au
Gabriel Sjoberg <[EMAIL PROTECTED]> wrote on 03/06/2003 04:08:48 PM:
dIon Gillard wrote:
I've created MAVEN-459 for this and extracted the diff as an
attachment to that issue.
Right. So from now on I'll post to the list *and* create an issue (both
with attached patches).
--GS
-
To unsubscribe,
[EMAIL PROTECTED] wrote:
What follows is a diff of the clean plugin, for your approval.
Index: xdocs/goals.xml
I've created MAVEN-459 for this and extracted the diff as an attachment
to that issue.
--
dIon Gillard, Multitask Consulting
Blog: http://www.freeroller.net/page/dion/Weblog
Work:
dion2003/06/02 22:20:35
Modified:src/plugins-build/deploy plugin.jelly
Log:
Comment about maven 458
Revision ChangesPath
1.6 +1 -0 maven/src/plugins-build/deploy/plugin.jelly
Index: plugin.jelly
===
dion2003/06/02 22:17:58
Modified:src/java/org/apache/maven/project Project.java
Log:
Fix comment
Revision ChangesPath
1.81 +3 -3 maven/src/java/org/apache/maven/project/Project.java
Index: Project.java
=
It's a hog while running, but not during the build (and it's only a hog
because the cache is kept in the target dir and is wiped out during the
clean goal).
There's absolutely no reason it shouldn't build and install during
bootstrap.
I'm just going to sit in the corner and blame the leaky c
Vincent Massol wrote:
Isn't this what MAVEN_OPTS is for?
The user can set stuff in MAVEN_OPTS and override the defaults
hum... are you saying that the following works:
java -Xmx160m -Xmx256m [...]
?
Even if it works, it doesn't look like a valid solution but more like a
trick to me. What
Gabriel,
I hope u haven't taken me the wrong way, I'd love to get some more docs
for both the plugins and the core. Please help us!
It'd be helpful to know what people think the shortcomings are for the
docs.
--
dIon Gillard, Multitask Consulting
Blog: http://www.freeroller.net/page/dion/W
LinkCheck is a bit of a hog...
Peter Royal wrote:
On Sunday, June 1, 2003, at 08:23 PM, Mike Bowler wrote:
Ben Walding wrote:
This typically is not the fault of LinkCheck. You can remove the
LinkCheck dir and it will just fail on the next one.
That's the behaviour I was expecting but is not
On Mon, 2003-06-02 at 22:15, Gabriel Sjoberg wrote:
> [EMAIL PROTECTED] wrote:
>
> >However to say that much of the project has little or no documentation is
> >a little misleading. I believe all plugins have a little documentation and
> >that there is a chunk of docs for the core.
> >
> >
> I
[EMAIL PROTECTED] wrote:
However to say that much of the project has little or no documentation is
a little misleading. I believe all plugins have a little documentation and
that there is a chunk of docs for the core.
I will not disagree that there is some documentation; what documentation
e
Hi Dave,
it would be so much easier to apply the patch if it was an attachment,
or filed in jira. I've created MAVEN-457 from this email.
See http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-457
--
dIon Gillard, Multitask Consulting
Blog: http://www.freeroller.net/page/dion/Webl
The Eclipse plugin creates a .classpath file with tags like:
Eclipse also supports an excluding attribute that filters out any files
matching the supplied pattern. I tweaked plugin.jelly (patch below) to check
for a maven.eclipse.exclude property in project.properties and modify
kind="src" entri
I'm +1 on docs.
However to say that much of the project has little or no documentation is
a little misleading. I believe all plugins have a little documentation and
that there is a chunk of docs for the core.
--
dIon Gillard, Multitask Consulting
Blog: http://www.freeroller.net/page/dion/We
+1 from me.. Can I make a suggestion, while it is a pain, submit the issues
in the issue tracker. It makes sure your valuable contributions are not
missed by the committers.
Eric Pugh
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Monday, June 02, 2003 2:37 P
On Sunday, June 1, 2003, at 08:23 PM, Mike Bowler wrote:
Ben Walding wrote:
This typically is not the fault of LinkCheck. You can remove the
LinkCheck dir and it will just fail on the next one.
That's the behaviour I was expecting but is not actually what happens.
I deleted the linkcheck directo
Much of the maven project has little or no documentation, so I have started to write
some simple docs, starting with the plugins. I am going to write them as I find the
need. If anyone wants something specific documented let me know. I don't have any
upload access, so I will be submitting dif
What follows is a diff of the clean plugin, for your approval.
Index: xdocs/goals.xml
===
RCS file: /home/cvspublic/maven/src/plugins-build/clean/xdocs/goals.xml,v
retrieving revision 1.1
diff -u -r1.1 goals.xml
--- xdocs/goals.xml
> -Original Message-
> From: news [mailto:[EMAIL PROTECTED] On Behalf Of dIon Gillard
> Sent: 02 June 2003 16:56
> To: [EMAIL PROTECTED]
> Subject: Re: maven.bat and -Xmx, remove MAVEN_DEFAULT_OPTS?
>
> Isn't this what MAVEN_OPTS is for?
>
> The user can set stuff in MAVEN_OPTS and over
Isn't this what MAVEN_OPTS is for?
The user can set stuff in MAVEN_OPTS and override the defaults
dIon
Vincent Massol wrote:
Hi,
I've noticed we've hard coded the jvm max memory to:
SET MAVEN_DEFAULT_OPTS="-Xmx160m"
I need to adjust this memory to a greater value and I think it would be
n
32 matches
Mail list logo
