The following issue has been updated:
Updater: marc-antoine garrigue (mailto:[EMAIL PROTECTED])
Date: Tue, 15 Jun 2004 2:49 AM
Comment:
added the jboss:debug goal
Changes:
Attachment changed to jboss.plugin.debug.goal.patch
--
On Tue, 2004-06-15 at 02:16, Vincent Massol wrote:
> Ok. I personally never use a master build.properties but they do on the
> project I'm currently working on.
I wouldn't call it a master build.properties. I don't have many values
in my ~/build.properties. My definition of maven.repo.local and
I'll give you a concrete example of why I want those POM's. I have a plugin
goal that I wrote for my plugin that compares my plugins version against all
the repo's that it can find, looking for a newer (only numeric, no
rc/beta/etc) version of the project. If it finds it, it prints out to the
use
> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> Sent: 15 June 2004 11:02
> To: Maven Developers List
> Subject: Re: project build.properties not overriding user
> build.properties?
>
> On Tue, 2004-06-15 at 01:37, Vincent Massol wrote:
> > Hi,
> >
> > Looking at Ma
On Tue, 2004-06-15 at 01:37, Vincent Massol wrote:
> Hi,
>
> Looking at Maven source it seems to me that any property defined in a
> project's build.properties would override that same property defined in
> the user.home build.properties (and that seems logical to me). However
> this is not happen
Hi,
Looking at Maven source it seems to me that any property defined in a
project's build.properties would override that same property defined in
the user.home build.properties (and that seems logical to me). However
this is not happening.
Is that a wanted behavior?
Thanks
-Vincent
---
Ok cool. Thanks for the explanation. That said wouldn't it be nice that
we put all jelly tags in the mavenhome/lib so that plugin developers can
rely on having them already in the classpath? (I'm sure there must be a
reason for not doing so...) :-)
Thanks
-Vincent
> -Original Message-
> F
vmassol 2004/06/14 21:57:13
Modified:abbotproject.xml
Log:
Always required (as explained by Brett).
Revision ChangesPath
1.4 +0 -2 maven-plugins/abbot/project.xml
Index: project.xml
===
If it is used by the script it is always required. If you are getting different
behaviour on HEAD and 1.0, it's possibly because of a different plugin
installation set where one puts the tags into root for some reason.
- Brett
Quoting [EMAIL PROTECTED]:
> vmassol 2004/06/14 09:45:07
>
> M
The following comment has been added to this issue:
Author: Brett Porter
Created: Mon, 14 Jun 2004 7:09 PM
Body:
yes, you can pas your own stylesheet url (see the xdoc plugin properties
documentation).
Grab the one from XDOc and modify it so that externalLink and newWindow don't
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPECLIPSE-33
Here is an overview of the issue:
-
Ke
vmassol 2004/06/14 09:45:07
Modified:abbotproject.xml
Log:
Added xml jelly tag dependeny as it seems to be required by maven rc3 (but not by
Maven 1.0 head).
Revision ChangesPath
1.3 +10 -1 maven-plugins/abbot/project.xml
Index: project.xml
=
The following issue has been updated:
Updater: Peter Anning (mailto:[EMAIL PROTECTED])
Date: Mon, 14 Jun 2004 12:26 PM
Comment:
cvs diff -u plugin.jelly
Changes:
Attachment changed to plugin-patch.txt
-
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPWAR-27
Here is an overview of the issue:
-
Key: M
The following comment has been added to this issue:
Author: Lars Kühne
Created: Mon, 14 Jun 2004 11:52 AM
Body:
As I said, external links worked fine in RC1... so one way to make it work in every
browser would be to simply remove the "external link" icon altogether. It's rather
u
Right so we've both established that is works for maven (sh) inside cygwin and
maven.bat inside cygwin. In maven.bat in cmd it will either be empty, or set to
what the user has specified.
The property is meant as a fallback for when user.home doesn't match $HOME,
specifically for cygwin on windows
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPXDOC-109
Here is an overview of the issue:
-
Key:
brett 2004/06/14 07:41:13
Modified:artifact plugin.jelly
Log:
make maven.artifact.legacy=false work
Revision ChangesPath
1.6 +0 -1 maven-plugins/artifact/plugin.jelly
Index: plugin.jelly
=
Hi,
Got some questions, but first just a heads up on what I'm doing here. Apologise
for lack of coherency - this is a late brain dump.
So far:
- removed deploy plugin from CVS, added tag library to artifact plugin (no
effect for end users)
- enhanced artifact plugin to handle old deploy propertie
Brett Porter wrote on Monday, June 14, 2004 3:25 PM:
> Do you take issue with maven.bat or maven (the sh script)?
>
> It works on the shell script. HOME is a cygwin path, which I
> convert to a windows path and pass in - but it remains a
> shell path in the parent shell.
This is something that C
Message:
The following issue has been closed.
Resolver: Brett Porter
Date: Mon, 14 Jun 2004 9:46 AM
duplicate of MAVEN-1297.
Design limitation in Maven 1.0 that will be fixed in future versions.
-
View the issue:
The following comment has been added to this issue:
Author: thierry lach
Created: Mon, 14 Jun 2004 9:39 AM
Body:
The resolution to this should not be specific to clean - any goal should be able to
declare that it can run without a dependency check.
---
brett 2004/06/14 06:36:48
Modified:artifact plugin.jelly project.xml
artifact/src/main/org/apache/maven/artifact/deployer
DefaultArtifactDeployer.java
artifact/src/main/org/apache/maven/deploy/deployers
FileD
brett 2004/06/14 06:32:19
maven-plugins/artifact/src/plugin-test - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Do you take issue with maven.bat or maven (the sh script)?
It works on the shell script. HOME is a cygwin path, which I convert to a
windows path and pass in - but it remains a shell path in the parent shell.
For the batch file - maybe it should be %USERDRIVE%%USERHOME%...
Quoting Jörg Schaible
Brett,
I am not sure about this patch for the maven script. Despite a normal Windows shell,
Cygwin defines a HOME of its own and it is one of its variables that are automatically
converted into DOSish style starting a non-Cygwin app from a Cygwin shell. Did you
test this ??
Regards,
Jörg
[EM
Damn, I was hoping nobody would notice :)
I got kicked offline before committing that change. Thanks Vincent.
- Brett
Vincent Massol wrote:
My analysis is wrong of course... Sorry about that. I read too quickly.
The problem is with the maven jelly tag, not maven itself!
I guess it's simply missing
I agree - I think Vincent usually has responsibility for releasing this?
(Let me know if this isn't the case - I don't know enough to release it
though).
- Brett
Carlos Sanchez wrote:
Hi,
I think aspectj-plugin should be released as it has been upgraded to AspectJ
1.2 and at least with the impro
brett 2004/06/14 05:36:49
Modified:src/bin Tag: MAVEN-1_0-BRANCH maven maven.bat
Log:
add way to get $HOME
Revision ChangesPath
No revision
No revision
1.31.4.6 +3 -0 maven/src/bin/maven
Index: maven
Message:
The following issue has been closed.
Resolver: Brett Porter
Date: Mon, 14 Jun 2004 8:26 AM
not working around browser bugs, sorry.
Attach a patch that works in Konqueror and every other web browser, and we'll apply
it, otherwise - use Firefox :)
--
The following comment has been added to this issue:
Author: Brett Porter
Created: Mon, 14 Jun 2004 8:08 AM
Body:
that's a bit simplistic - it needs to be 100% backwards compatible.
This is underway currently.
-
Vi
The following comment has been added to this issue:
Author: Adriano Labate
Created: Mon, 14 Jun 2004 7:09 AM
Body:
Sorry, the version I use is 1.3.
-
View this comment:
http://jira.codehaus.org/browse/MPCHANGES-1
The following comment has been added to this issue:
Author: Arnaud HERITIER
Created: Mon, 14 Jun 2004 6:39 AM
Body:
It works for me.
Which version of the plugin do you use ??
-
View this comment:
http://jira.cod
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPCHANGES-10
Here is an overview of the issue:
-
Ke
> -Original Message-
> From: Vincent Massol [mailto:[EMAIL PROTECTED]
> Sent: Monday, June 14, 2004 6:30 AM
> To: 'Maven Developers List'
> Subject: RE: Why do we need POMs in repo for non-Maven projects?
>
>
> ok. Cool. Thanks for the information. I understand better now.
>
> How do w
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPXDOC-108
Here is an overview of the issue:
-
Key:
36 matches
Mail list logo
