That's very true in principle. However when you've been having a
0.9 or beta or rc for more than 2 years, it has no meaning at all!
People have already been using it in production and you just simply
can't break them completely, even though it's a beta or rc... :-)
At least, we should make an
> > We should create a set tag as well I guess.
>
> Yep. That would be great. Only problem with this (as with
> pluginVar - which is not too well named BTW if we add a set
> tag) is that plugins who uses it will not be compatible with
> previous Maven versions...
I don't think we can support o
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: 22 April 2004 07:41
> To: 'Maven Developers List'
> Subject: RE: [Q] Setting a property so that it's visible from another
> plugin
>
> We should create a set tag as well I guess.
Yep. That would be great. Only p
We should create a set tag as well I guess.
If you just want to load the plugin, I think you need to do the depedency
handle. We ended up deciding this was the best way rather than using
dependencies on dummy goals (like war:load).
I know you know how this works because cactus has a dependency ha
The following comment has been added to this issue:
Author: Brett Porter
Created: Thu, 22 Apr 2004 1:37 AM
Body:
I know enough about jelly contexts to say this won't be useful in the current
incarnation. Really we just need to get the doco up to scratch and I intend to do that
be
The following comment has been added to this issue:
Author: Arnaud HERITIER
Created: Thu, 22 Apr 2004 1:33 AM
Body:
Another think that can interesting is to have an option to retreive all properties
used by installed plugins.
I don't yet know if it is possible.
I'll try to work o
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: 22 April 2004 01:38
> To: 'Maven Developers List'
> Subject: RE: [Q] Setting a property so that it's visible from another
> plugin
>
> While plugin.getPluginContext works, it relies on the plugin being
> initiali
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPJBUILDER-10
Here is an overview of the issue:
Cool - thanks Emmanuel!
Can you update changes.xml too please?
Cheers,
Brett
> -Original Message-
> From: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
> Sent: Thursday, 22 April 2004 12:30 AM
> To: Maven Developers List
> Subject: Re: cvs commit: maven/src/java/org/apache/maven/util
> Ht
While plugin.getPluginContext works, it relies on the plugin being
initialised. You can do that by declaring a dummy tag in the plugin (the
dependency handle, and most importantly, adding the uri to your names space
in the calling plugin).
An easier way is to use maven:pluginVar as it will initial
Vincent's POMv4 changes are still on HEAD. I created the branch for 1.0
before they were added.
HEAD is up to date as at RC2. It will work with everything except
multiproject which now uses some RC3 extensions to reactor. I'll merge again
at RC3.
If anyone wants to start migrating maven-model and
The following comment has been added to this issue:
Author: Brett Porter
Created: Wed, 21 Apr 2004 7:31 PM
Body:
you read my mind! I did this in the morning and will commit soon.
-
View this comment:
http://jira
On Wed, 2004-04-21 at 16:50, Vincent Massol wrote:
> The reason I'm asking is to judge whether we can commit it to HEAD
> easily. I would like to avoid as much as possible big changes that take
> long time. Remember the problem we had a few months back when we made
> some big change in HEAD and HE
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1243
Here is an overview of the issue:
---
> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> Sent: 21 April 2004 21:58
> To: Maven Developers List
> Subject: RE: Is there a problem to adding the POM element
> now+POM4in Maven 1.0?
>
> On Wed, 2004-04-21 at 15:39, Vincent Massol wrote:
>
> > Sounds ok to me
On Wed, 2004-04-21 at 15:39, Vincent Massol wrote:
> Sounds ok to me in principle. Is it a big change?
I'm honestly not sure how much work it is, but I don't imagine more than
a days work looking at the code.
> Can it be done
> relatively quickly on HEAD?
I don't think quickly is as important
Sounds ok to me in principle. Is it a big change? Can it be done
relatively quickly on HEAD? Will it be backward compatible for 1.0
users?
Thanks
-Vincent
> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> Sent: 21 April 2004 21:22
> To: Maven Developers List
> Subject
On Wed, 2004-04-21 at 15:12, Vincent Massol wrote:
> I know I was missing something! I had somehow forgotten we were in a rc
> cycle! :-)
>
> I can use HEAD for this. Brett, do you know if HEAD is up to date with
> the 1.0 branch?
If this will be for subsequent 1.x releases then I would like the
I know I was missing something! I had somehow forgotten we were in a rc
cycle! :-)
I can use HEAD for this. Brett, do you know if HEAD is up to date with
the 1.0 branch?
Thanks
-Vincent
> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> Sent: 21 April 2004 20:59
> To:
On Wed, 2004-04-21 at 14:38, Vincent Massol wrote:
> Hi,
>
> Would it be a problem to add the element for Maven RC3?
It most likely wouldn't be a problem, but during RC is not the time to
be changing the model.
You can see the differences here between v3 and v4. Anything with 3.0.0+
is carried
Hi,
Would it be a problem to add the element for Maven RC3? If we
make it optional (and default for example to "jar") I think it will be
100% backward compatible. The plugins will not use it for now. But at
least the users will be able to start using it to type their projects.
Actually I don't r
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=WAGONFTP-2
Here is an overview of the issue:
---
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=SCM-7
Here is an overview of the issue:
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=WAGON-10
Here is an overview of the issue:
-
Message:
The following issue has been closed.
Resolver: Jason van Zyl
Date: Wed, 21 Apr 2004 12:34 PM
Space has been setup:
http://docs.codehaus.org/display/SCM/Home
-
View the issue:
http://jira.codehaus.org/sec
Message:
The following issue has been closed.
Resolver: Jason van Zyl
Date: Wed, 21 Apr 2004 12:33 PM
Space has been setup:
http://docs.codehaus.org/display/SCM/Home
-
View the issue:
http://jira.codehaus.org/sec
Hi Nicolas,
Cool. Could you propose it to the Cactus mailing list (this is where the
Maven plugin for Cactus is developed)? Could you create a JIRA issue for
it (http://issues.apache.org/jira) and attach your proposal as a patch?
Thanks
-Vincent
> -Original Message-
> From: Nicolas De Lo
Hi guys,
Here's a proposal for a new goal on multiproject plugin. It allows to run cactus tests
on all sub-projects of "war"
type, the same way junit tests can be run.
I use it from cruisecontrol scripts to update, compile and test my app (having 3 web
modules and 4 jars).
Nico.
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1242
Here is an overview of the issue:
---
Hi,
I used to know how to do this but somehow it's not working anymore for
(I'm using RC3). I have 2 plugins one of them is calling the other
through attainGoal. The calling plugin also sets a property that is
supposed to be visible from the other plugin.
I've tried without success the following:
- Original Message -
From: "Vincent Massol" <[EMAIL PROTECTED]>
To: "'Maven Developers List'" <[EMAIL PROTECTED]>
Sent: Wednesday, April 21, 2004 4:14 PM
Subject: RE: cvs commit: maven/src/java/org/apache/maven/util HttpUtils.java
> Hi Emmanuel,
>
> That's cool. Would it be possible to
Hi Emmanuel,
That's cool. Would it be possible to add some comments to explain why
this additional check is required?
Is it to support web servers that do not support ifModifiedSince HTTP
headers?
Thanks
-Vincent
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
>
Message:
The following issue has been closed.
Resolver: Emmanuel Venisse
Date: Wed, 21 Apr 2004 9:54 AM
Fixed
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1226
Here is an overview of
evenisse2004/04/21 06:53:53
Modified:src/java/org/apache/maven/util Tag: MAVEN-1_0-BRANCH
HttpUtils.java
Log:
Fix MAVEN-1226. Snapshot is download only if the remote version is more recent than
local version.
Revision ChangesPath
No
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=SCM-6
Here is an overview of the issue:
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=SCM-5
Here is an overview of the issue:
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=SCM-4
Here is an overview of the issue:
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=SCM-3
Here is an overview of the issue:
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=SCM-2
Here is an overview of the issue:
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=SCM-1
Here is an overview of the issue:
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=WAGON-9
Here is an overview of the issue:
--
The following issue has been updated:
Updater: Jason van Zyl (mailto:[EMAIL PROTECTED])
Date: Wed, 21 Apr 2004 8:55 AM
Changes:
Version changed to 0.92
Fix Version changed to 0.92
-
For
The following issue has been updated:
Updater: Jason van Zyl (mailto:[EMAIL PROTECTED])
Date: Wed, 21 Apr 2004 8:54 AM
Changes:
Version changed to 0.91
Fix Version changed to 0.91
-
For
The following issue has been updated:
Updater: Jason van Zyl (mailto:[EMAIL PROTECTED])
Date: Wed, 21 Apr 2004 8:54 AM
Changes:
Version changed to 0.91
Fix Version changed to 0.91
-
For
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1241
Here is an overview of the issue:
---
The following issue has been updated:
Updater: Jason van Zyl (mailto:[EMAIL PROTECTED])
Date: Wed, 21 Apr 2004 8:52 AM
Changes:
Fix Version changed to 0.9
-
For a full history of the issue, see:
The following issue has been updated:
Updater: Jason van Zyl (mailto:[EMAIL PROTECTED])
Date: Wed, 21 Apr 2004 8:51 AM
Changes:
Fix Version changed to 0.9
-
For a full history of the issue, see:
The following issue has been updated:
Updater: Jason van Zyl (mailto:[EMAIL PROTECTED])
Date: Wed, 21 Apr 2004 8:53 AM
Changes:
Fix Version changed to 0.9
-
For a full history of the issue, see:
The following issue has been updated:
Updater: Jason van Zyl (mailto:[EMAIL PROTECTED])
Date: Wed, 21 Apr 2004 8:52 AM
Changes:
Fix Version changed to 0.9
-
For a full history of the issue, see:
The following issue has been updated:
Updater: Jason van Zyl (mailto:[EMAIL PROTECTED])
Date: Wed, 21 Apr 2004 8:52 AM
Changes:
Fix Version changed to 0.9
-
For a full history of the issue, see:
evenisse2004/04/21 01:20:54
Modified:src/java/org/apache/maven Tag: MAVEN-1_0-BRANCH
MavenSession.java
src/java/org/apache/maven/cli Tag: MAVEN-1_0-BRANCH App.java
Log:
Fix missing exception
Revision ChangesPath
No
> -Original Message-
> From: Vincent Massol [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, April 20, 2004 10:19 PM
> To: 'Maven Developers List'
> Subject: Should the multiproject plugin strategy be changed?
>
>
> Hi,
>
> I've taken the time review the multiproject plugin in order to asses
52 matches
Mail list logo
