On 6/30/06, Torsten Curdt <[EMAIL PROTECTED]> wrote:
FYI
-- Forwarded message --
From: Bertrand Delacretaz <[EMAIL PROTECTED]>
Date: Jun 30, 2006 5:58 PM
Subject: [RANT] This Maven thing is killing us
To: dev@cocoon.apache.org
Is anyone here using Cocoon? They could probab
I don't know what he complains about. True sometimes the repository
quality sucks but just submit a patch and it usually take 3 to 4 days
until the problem is solves. Really I don't want to seem arrogant but
I haven't had those kind of troubles.
On 6/30/06, Mike Perham <[EMAIL PROTECTED]> wrote:
In geronimo, we have a plugin that uses a lot of core geronimo
functionality, that we would like to use to construct pieces of the
server. We seem to have run into a design decision of m2 that a
plugin cannot be built and used in the same build.
Is this correct, or are we doing something w
"I'll spare you the details on that one"
This does nothing to solve the problem. We can't fix what we don't know
about.
The quality of the repository metadata has always struck me as something
that will make or break the long-term success of Maven. We can only
document it as best as possible -
Brett means to make a new release to prevent people to use the old broken jar.
I've fixed it now, ibiblio should be correct now. I think somebody put
that wrong jar in the apache repo some time ago and that was it ended
in ibiblio.
On 6/30/06, Otis Gospodnetic <[EMAIL PROTECTED]> wrote:
Sorry,
FYI
-- Forwarded message --
From: Bertrand Delacretaz <[EMAIL PROTECTED]>
Date: Jun 30, 2006 5:58 PM
Subject: [RANT] This Maven thing is killing us
To: dev@cocoon.apache.org
Hi gang,
It's Friday, I'm tired and a bit depressed after losing about two more
hours unsuccessfully
Sorry, I'no Maven expert, and I'm not sure what you mean.
2.0.1 - are you referring to Lucene? We don't have 2.0.1 yet - 2.0.0 is the
latest release.
The 394k Jar is the Lucene's binary Jar (all .class files inside), so I'm not
sure why you say that should be removed.
Looking at http://www.ibib
Hi,
is there some way to enumerate the individual directories of the default
Maven2 directory layout as described in
http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html
in order to avoid having to hardcode the directories in some client code
which needs
I don't see any new stuff in the rsync process.
Also there must be something wrong with the jar at
http://www.ibiblio.org/maven2/org/apache/lucene/lucene-core/2.0.0/
because it's 394k. I think I should delete it in the meantime so
people don't get it corrupt.
On 6/30/06, Brett Porter <[EMAIL PROT
Hi Brett,
That was the only regression I noticed - a 2.0.2 release would be great thanks.
Cheers,
Mark
On 30/06/06, Brett Porter <[EMAIL PROTECTED]> wrote:
Hi Mark,
I think we should do a release soon (or we get in the situation like
2.0.1 where I fixed it, voted straight away, and then came
Heh, probably shouldn't have been ignoring these
/export/home/maven/m2-build/surefire/trunk/maven-surefire/surefire-booter/src/main/java/org/apache/maven/surefire/booter/output/FileOutputConsumerProxy.java:[115,18]
cannot resolve symbol
symbol : constructor RuntimeException (java.io.IOExc
I forgot to post the result on this one...
+1 (binding): Emmanuel, Brett, Stephane
+1 (committer): Fabrice
+1 (user): Thierry
I'm not going to post the announcement on this one until we decide if
there'll be a 2.0.2 which I'll merge if we do.
... Brett
I'd like to release the WAR plugin 2.0.
Hi Mark,
I think we should do a release soon (or we get in the situation like
2.0.1 where I fixed it, voted straight away, and then came back to
release it a month later :)
Are there any other issues that need attention?
- Brett
On 29/06/2006 1:24 AM, Mark Hobson wrote:
Thanks for fixing t
On 29/06/2006 2:54 AM, Alexandre Poitras wrote:
I had started some documentation based on the Trails idea :
http://docs.codehaus.org/display/MAVENUSER/The+Maven+2+tutorial
but stopped since "Better Builds with Maven" was exactly what I wanted
to produce. Feel to use anything.
Sorry to discoura
14 matches
Mail list logo