On 11/3/06, Brett Porter <[EMAIL PROTECTED]> wrote:
Ok, but these are integration tests then that shouldn't be run every
build? Can they be moved out to the latter phase or something similar?
Sure, will do.
- Brett
-
To unsu
The navigation one comes from Maven 1.0.
It's time we start getting these consistent:
- deploy all the new ones to /xsd/
- actually change the version when we change the file :)
Cheers,
Brett
On 03/11/2006, at 4:47 PM, Wendy Smoak wrote:
I added a section on publishing schemas to the developm
I added a section on publishing schemas to the development procedures.
http://docs.codehaus.org/display/MAVEN/Development+Procedures
Looking in /www/maven.apache.org on minotaur, what module does
maven-navigation-1.0.xsd come from? (Is this for site.xml?)
Can we change the filename to maven-na
Time to roll back the recent CSS changes. I'll look into it shortly.
- Brett
On 03/11/2006, at 2:24 PM, Jesse Kuhnert wrote:
An utterly useless observation I know, but are you guys "trying" to
make the
site look worse on purpose?
Compare: http://maven.apache.org
to
Duplicate of (original
On both the trunk maven/components/pom.xml and the 2.0 branch
maven-2.0.x/pom.xml,
- the poms have minotaur.a.o when it should be people.a.o, and
- the for the site doesn't match the development procedures
http://docs.codehaus.org/display/MAVEN/Development+Procedures
Can someone please fix the
An utterly useless observation I know, but are you guys "trying" to make the
site look worse on purpose?
Compare: http://maven.apache.org
to
Duplicate of (original maven theme): http://tapestry.apache.org
Just thought I'd say something cause it was so noticeable..
--
Jesse Kuhnert
Tapestry/Do
On 3 Nov 06, at 7:42 AM 3 Nov 06, Brett Porter wrote:
On 03/11/2006, at 12:55 PM, Jason van Zyl wrote:
On 3 Nov 06, at 7:10 AM 3 Nov 06, Brett Porter wrote:
Ok, this is the same problem Dennis reported. I see it too now.
BTW, why are the tests -so- slow? EarMojoTest consistently takes
o
Issue Subscription
Filter: Design & Best Practices (37 issues)
Subscriber: mavendevlist
Key Summary
MNG-2184Possible problem with @aggregator and forked lifecycles
http://jira.codehaus.org/browse/MNG-2184
MNG-612 implement conflict resolution techniques
htt
+1 - yes please
I don't know exactly what would be included in a 2.0.5 release, but I
would like to lobby for new releases of wagon providers, etc, so that
the beta-2 version can be included. In particular, the HTTP
compression enhancements would be nice to have.
-Nathan
On 11/2/06, Kenney West
Assuming Mike Perham's testing goes OK, I would really like to see my
patch for MNG-1577 in 2.0.5. I cannot move forward with Maven 2 at all
until that issue is resolved.
Ralph
Kenney Westerhof wrote:
Hi,
I've talked to several users in the past period about issues in maven
2.0.4.
It's gett
On 03/11/2006, at 12:55 PM, Jason van Zyl wrote:
On 3 Nov 06, at 7:10 AM 3 Nov 06, Brett Porter wrote:
Ok, this is the same problem Dennis reported. I see it too now.
BTW, why are the tests -so- slow? EarMojoTest consistently takes
over a minute.
He's using the same method as the main
On 3 Nov 06, at 7:10 AM 3 Nov 06, Brett Porter wrote:
Ok, this is the same problem Dennis reported. I see it too now.
BTW, why are the tests -so- slow? EarMojoTest consistently takes
over a minute.
He's using the same method as the main ITs now. They will eventually
be able to use the
Ok, this is the same problem Dennis reported. I see it too now.
BTW, why are the tests -so- slow? EarMojoTest consistently takes over
a minute.
On 02/11/2006, at 6:39 PM, Stephane Nicoll wrote:
What I mean by missing is not the page itself but the reference in the
menu on the left (all I ha
On 11/3/06, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
Probably this will help you
http://jroller.com/page/carlossg?entry=proxying_and_hosting_a_maven
Thanks.
The documentation at
http://maven.apache.org/maven-settings/settings.html#class_mirror
needs updating to indicate that * is valid for mir
On 2 Nov 06, at 11:33 PM 2 Nov 06, Nathan Hamblen wrote:
And while someone's in there, could you also please sync with the
Databinder repository which has scripts in place?
http://databinder.net/maven/
It depends on Wicket 1.2.3. Thanks in advance!
If you take this:
http://svn.apache.org/re
Probably this will help you
http://jroller.com/page/carlossg?entry=proxying_and_hosting_a_maven
On 11/2/06, Barrie Treloar <[EMAIL PROTECTED]> wrote:
Because we are behind a firewall I need to do a couple of things to
get maven to work.
1) Modify ~/.m2/settings.xml to include a entry for every
Because we are behind a firewall I need to do a couple of things to
get maven to work.
1) Modify ~/.m2/settings.xml to include a entry for every
repository that gets named.
2) Ensure that maven-proxy has an entry for the URL that corresponds
to the mirrors name
3) Ensure that our firewall rules g
On 2 Nov 06, at 11:33 PM 2 Nov 06, Nathan Hamblen wrote:
And while someone's in there, could you also please sync with the
Databinder repository which has scripts in place?
http://databinder.net/maven/
It depends on Wicket 1.2.3. Thanks in advance!
I pulled Wicket out of the automated sync b
On Nov 2, 2006, at 1:59 PM, Rollo, Dan wrote:
Are there any user instructions on how people could kick the tires
of a
release candidate AND how to back-out if needed? Given how maven
composes itself on the fly, I'm nervous about trying an RC and finding
out I wasn't really using the right ver
Are there any user instructions on how people could kick the tires of a
release candidate AND how to back-out if needed? Given how maven
composes itself on the fly, I'm nervous about trying an RC and finding
out I wasn't really using the right versions, etc. Providing some good
"howto try an RC" st
Kenney Westerhof wrote:
Hi,
I've talked to several users in the past period about issues in maven
2.0.4.
It's getting frustrating to see users having the same problems over and
over again
due to bugs that were fixed 5 months ago.
There are 53 issues resolved for 2.0.5, and Looking at the num
The patch attached to MNG-2626 is 25 lines of code and is easily
removable. I would be disappointed if it was not be applied before
2.0.5 is released.
-b
On Nov 2, 2006, at 1:45 AM, Kenney Westerhof wrote:
Hi,
I've talked to several users in the past period about issues in
maven 2.0.4.
HI, i want to know if there is a maven plugin that lists the
dependencies by compilation order needed:
For example:
A depends on B, C
and B depends on D
so i need a list like
D , C ,B, A or
C, D,B,A ,etc
Regards
--
Lic Matias Urbieta
---
And while someone's in there, could you also please sync with the
Databinder repository which has scripts in place?
http://databinder.net/maven/
It depends on Wicket 1.2.3. Thanks in advance!
Nathan
On Wed, 2006-11-01 at 20:57 +0100, Martijn Dashorst wrote:
> Dear Maven guru's,
>
> could you p
John Casey wrote:
I totally agree with this, except where regressions from 2.0.4 are
concerned. I think there are a couple of issues in there that are going to
break compatibility...I reverted the fix-for version on the one that I
saw a
little while ago, but where there's one...
Yeah I saw
I totally agree with this, except where regressions from 2.0.4 are
concerned. I think there are a couple of issues in there that are going to
break compatibility...I reverted the fix-for version on the one that I saw a
little while ago, but where there's one...
-john
On 11/2/06, Jason van Zyl <[
+1 I've been waiting for the updates to the ant mojo stuff for a while.
On 11/2/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
On 2 Nov 06, at 10:26 PM 2 Nov 06, Kenney Westerhof wrote:
> Right now they're both scheduled for 2.1 and seem rather complex.
>
> If you can get them fixed in a week w
On 2 Nov 06, at 10:26 PM 2 Nov 06, Kenney Westerhof wrote:
Right now they're both scheduled for 2.1 and seem rather complex.
If you can get them fixed in a week we can definitely push them to
2.0.5,
otherwise we'll wait for 2.0.6, which should come out soon after
(talked to
Jason about th
Right now they're both scheduled for 2.1 and seem rather complex.
If you can get them fixed in a week we can definitely push them to 2.0.5,
otherwise we'll wait for 2.0.6, which should come out soon after (talked to
Jason about this).
Is this acceptable? We want to keep 2.0.5 pretty small and st
+1
2006/11/2, Kenney Westerhof <[EMAIL PROTECTED]>:
Hi,
I've talked to several users in the past period about issues in maven
2.0.4.
It's getting frustrating to see users having the same problems over and
over again
due to bugs that were fixed 5 months ago.
There are 53 issues resolved for 2.
I think we just need to release what's there and pick another small
set of issues. The second we say we're going to release everyone
wants a fix here and there which is understandable. I think we should
try and turn out the RC quickly, release and then try again. If we
start trying to fix t
On 2 Nov 06, at 8:29 PM 2 Nov 06, Kenney Westerhof wrote:
John Casey wrote:
BTW, I'm in favor of the RC staging, then a vote for that binary.
Yes, me too.
I want to clarify something:
I wasn't suggesting we release 2.0.5 immediately; I didn't even
talk about how/what to release, just tha
I'm all for a new release, except that we are having tons of issues with
dual-core processors. Something in plexus is causing thousands of
warnings and worse, it actually builds slower than older single core
machines. The issue for this is: http://jira.codehaus.org/browse/PLX-287
I have been tryin
On Thu, November 2, 2006 4:59 pm, Kenney Westerhof wrote:
> How do we proceed in deciding what to keep and what to move to 2.0.6?
> Bulk change all open issues and move them, then move back some issues
> mentioned
> on this thread and others?
+1.
Regards,
Graham
--
---
John Casey wrote:
BTW, I'm in favor of the RC staging, then a vote for that binary.
Yes, me too.
I want to clarify something:
I wasn't suggesting we release 2.0.5 immediately; I didn't even talk about
how/what to release, just that we cut down the number of issues planned
for 2.0.5 and
Not a developer, but a quick question on the topic: aren't these
fixes for a large part in plugins, and not in the core?
(As a user, hooray for the release schedule, BTW).
On 2 Nov 2006, at 15:26, Wendell Beckwith wrote:
I'm all +1 for more frequent releases too. However, this issue
goes
On Do, November 2, 2006 15:09, Mike Perham wrote:
> MNG-2340 and MNG-1577 are both on my must fix list before release. I
> still need to test the latest patch for 1577.
>
> mike
>
What about MNG-2646 ? I opened it just yesterday. The attached patch needs
an expert's review, of course, but fixes
BTW, I'm in favor of the RC staging, then a vote for that binary.
-john
On 11/2/06, John Casey <[EMAIL PROTECTED]> wrote:
Sounds good to me. +1.
-john
On 11/2/06, Kenney Westerhof <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I've talked to several users in the past period about issues in maven
> 2
Sounds good to me. +1.
-john
On 11/2/06, Kenney Westerhof <[EMAIL PROTECTED]> wrote:
Hi,
I've talked to several users in the past period about issues in maven
2.0.4.
It's getting frustrating to see users having the same problems over and
over again
due to bugs that were fixed 5 months ago.
T
I'm all +1 for more frequent releases too. However, this issue goes to the
core of an issue I brought up previously where maven should publish a build
milestone/release schedule similar to eclipse. For example, no one is
asking the Eclipse platform guys and gals to please make a release because
MNG-2340 and MNG-1577 are both on my must fix list before release. I
still need to test the latest patch for 1577.
mike
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
The cruisecontrol plugin is just a big collection of deprecated methods
(I had proposed to demote it into the sandbox before maven-1.1-beta-3
but the vote didn't pass), I don't think it's useful for anything.
However, I didn't think I'd introduce a compatibility problem with my
last commits -
Definitely +1!
I am also agree with Brett's comment.
Moreover, we need to review issues before and I am pretty sure that we
could close some of them (specially doc). I will investigate.
Cheers,
Vincent
2006/11/2, Brett Porter <[EMAIL PROTECTED]>:
I'm in agreement, but let's do this right - we
double-plus 1!
On 11/2/06, John Tolentino <[EMAIL PROTECTED]> wrote:
Here's my +1 :-)
On 11/2/06, Stephen Duncan <[EMAIL PROTECTED]> wrote:
> I know it's lame to throw out a pet issue that's unfixed, but I'm
> going to do it anyway because it's been such a big problem for me.
> http://jira.cod
Pixel size 8 (on fonts) has been problematic for a while.
This problem is not limited to OSX.
It is also visible on FF running under linux.
I applied a fix for it yesterday
http://svn.apache.org/viewvc/maven/site/trunk/src/site/resources/css/site.css?r1=467813&r2=469927&pathrev=469927&diff_format=
Here's my +1 :-)
On 11/2/06, Stephen Duncan <[EMAIL PROTECTED]> wrote:
I know it's lame to throw out a pet issue that's unfixed, but I'm
going to do it anyway because it's been such a big problem for me.
http://jira.codehaus.org/browse/MNG-2340 is a critical regression
issue that was introduced
I know it's lame to throw out a pet issue that's unfixed, but I'm
going to do it anyway because it's been such a big problem for me.
http://jira.codehaus.org/browse/MNG-2340 is a critical regression
issue that was introduced in 2.0.4 that has made using mvn
eclipse:eclipse (or the Netbeans plugin)
a big +1, we should definitively try to release more often
fabrizio
On 11/2/06, Kenney Westerhof <[EMAIL PROTECTED]> wrote:
Hi,
I've talked to several users in the past period about issues in maven 2.0.4.
It's getting frustrating to see users having the same problems over and over
again
due
+1, especially for the SNAPSHOT download issue.
Stéphane
On 11/2/06, Kenney Westerhof <[EMAIL PROTECTED]> wrote:
Hi,
I've talked to several users in the past period about issues in maven 2.0.4.
It's getting frustrating to see users having the same problems over and over
again
due to bugs that
I'm in agreement, but let's do this right - we should designate a
build as an RC and put it out for some testing. If all goes well, we
can call a vote.
Thanks for pushing this forward Kenney.
Cheers,
Brett
On 02/11/2006, at 8:45 PM, Kenney Westerhof wrote:
Hi,
I've talked to several user
Mark Hobson wrote:
+1, more frequent releases the better.
Absolutely - and more frequent releases of plugins too.
It's becoming increasingly hard to "sell in" the maven idea to projects
due to long-lasting outstanding bugs (or outstanding releases).
I think this would be a lot easier if rele
On Thu, November 2, 2006 11:45 am, Kenney Westerhof wrote:
> I feel that there are enough critical issues resolved for 2.0.5 to warrant
> a release. Could we start planning a 2.0.6 release and move most of the
> open
> issues from 2.0.5 to 2.0.6?
>
> Here's my +1.
+1.
Regards,
Graham
--
-
Yes! Please more frequent releases :-)
+1
--jason
On Nov 2, 2006, at 1:45 AM, Kenney Westerhof wrote:
Hi,
I've talked to several users in the past period about issues in
maven 2.0.4.
It's getting frustrating to see users having the same problems over
and over again
due to bugs that we
Any chances for MNG-2305 (only first active proxy considered/used)?
Greetings
Franz
Kenney Westerhof schrieb:
Hi,
I've talked to several users in the past period about issues in maven
2.0.4.
It's getting frustrating to see users having the same problems over
and over again
due to bugs tha
+1, more frequent releases the better.
Mark
On 02/11/06, Kenney Westerhof <[EMAIL PROTECTED]> wrote:
Hi,
I've talked to several users in the past period about issues in maven 2.0.4.
It's getting frustrating to see users having the same problems over and over
again
due to bugs that were fixed
Hi,
I've talked to several users in the past period about issues in maven 2.0.4.
It's getting frustrating to see users having the same problems over and over
again
due to bugs that were fixed 5 months ago.
There are 53 issues resolved for 2.0.5, and Looking at the number of open issues
for 2.0
> > There's just one problem - inheritance. Should plugins/executions
> > defined
> > in the parent be placed before or after the ones in the child pom?
> > I'd say before, but maybe they need to be interleaved..
>
> This is where an element makes a lot of sense. The order
> doesn't have to be
57 matches
Mail list logo
