I've updated the log to:
MWAR-45: add config prop to specify webapp classes should be zipped and
placed into WEB-INF/lib/xxx.jar instead of placed in WEB-INF/classes/
Submitted by: Prasad Kashyap
- Brett
On 12/06/2006 2:06 PM, Brett Porter wrote:
[EMAIL PROTECTED] wrote:
Author: jvanzyl
Dat
Hi,
I have written a plugin, which I currently call maven-xml-plugin. This first
version is able to validate XML documents (test phase) or to transform XML
documents by applying an XSLT stylesheet (generate-resources). So far
development is finished (including a test suite), the exception being d
Are you changing these because you think these are the best final value,
or because the current code isn't close to complying?
If it's the former, that's cool; if it's the latter I'd suggest we
should keep the checkstyle plugin in the "ideal" configuration, and
override it in Maven itself.
-
Are these linked or configured from anywhere?
Any reason not to point directly at the SVN version which will always be
up to date?
- Brett
On 21/06/2006 8:57 AM, [EMAIL PROTECTED] wrote:
Author: carlos
Date: Tue Jun 20 15:57:13 2006
New Revision: 415835
URL: http://svn.apache.org/viewvc?rev
Jesse,
Please revert these commits.
Apache snapshots go to the Apache repo, which this pom was already
inheriting (if it wasn't working we can figure it out from there).
BTW, do you think we should terminate this branch and instead use trunk
from now on? I only created this to roll the alpha
plus one
On 21/06/2006 1:06 AM, John Casey wrote:
Hi everyone.
I just wanted to reopen this vote to see if we can release a bugfix version
of the deploy plugin. This version doesn't have any new features, but does
fix two critical ones found when using the deploy:deploy-file mojo:
* POM and ar
On 20/06/2006 10:27 PM, jerome lacoste wrote:
On 6/10/06, Brett Porter <[EMAIL PROTECTED]> wrote:
+1, but considering it an exception to the rule, not a change to the
rule.
I'd rather we were doing .x releases every 6 months instead.
+1: 2
-1: 0
Is that sufficient?
Kenney makes 3, but th
I've set the Fix For version for MDEPLOY-23.
-john
On 6/20/06, jerome lacoste <[EMAIL PROTECTED]> wrote:
On 6/20/06, John Casey <[EMAIL PROTECTED]> wrote:
> Hi everyone.
>
> I just wanted to reopen this vote to see if we can release a bugfix
version
> of the deploy plugin. This version doesn't
+1
Fabrice
On 6/20/06, John Casey <[EMAIL PROTECTED]> wrote:
Hi everyone.
I just wanted to reopen this vote to see if we can release a bugfix
version
of the deploy plugin. This version doesn't have any new features, but does
fix two critical ones found when using the deploy:deploy-file mojo:
On 6/20/06, John Casey <[EMAIL PROTECTED]> wrote:
Hi everyone.
I just wanted to reopen this vote to see if we can release a bugfix version
of the deploy plugin. This version doesn't have any new features, but does
fix two critical ones found when using the deploy:deploy-file mojo:
* POM and art
John Casey wrote:
Hi everyone.
I just wanted to reopen this vote to see if we can release a bugfix version
of the deploy plugin. This version doesn't have any new features, but does
fix two critical ones found when using the deploy:deploy-file mojo:
* POM and artifact build numbers are out of s
+1
Emmanuel
John Casey a écrit :
Hi everyone.
I just wanted to reopen this vote to see if we can release a bugfix version
of the deploy plugin. This version doesn't have any new features, but does
fix two critical ones found when using the deploy:deploy-file mojo:
* POM and artifact build num
Hi everyone.
I just wanted to reopen this vote to see if we can release a bugfix version
of the deploy plugin. This version doesn't have any new features, but does
fix two critical ones found when using the deploy:deploy-file mojo:
* POM and artifact build numbers are out of sync when using -Dpo
I'm not sure if we're talking about the same reports section. IMO, the
project-info links on the landing page (see
http://maven.apache.org/jxr.htmlfor example) don't help anything. If
we want to have a list of contributors
or information about the mailing lists, then maybe we should:
1. clean up
On 6/10/06, Brett Porter <[EMAIL PROTECTED]> wrote:
+1, but considering it an exception to the rule, not a change to the rule.
I'd rather we were doing .x releases every 6 months instead.
+1: 2
-1: 0
Is that sufficient? If so, who's responsible to apply this change onto
the branch ?
Jerome
Hi again,
A quick update to let everyone know that we have posted some updates to
Plexus website and would like to get some feedback on them.
Please note that a few pages are still in the process of being updated.
The website is accessible at:
http://plexus.codehaus.org/index.html
We apprec
16 matches
Mail list logo
