I put this line in the code before it broke:
System.out.println("URL: " +
this.getClass().getClassLoader().getResource("org/codehaus/plexus/util")
);
and it printed:
URL:
jar:file:/c:/opt/maven-2.0.4/core/plexus-utils-1.1.jar!/org/codehaus/ple
xus/util
I've upgraded my maven installation to 2.0
It's a real shame that MNG-3244 had to be reverted.
Now there is no way for an inherited site#url to actually specify the
url for a project.
The current behaviour in which the child artifactId is always appended
is non-intuitive IMHO.
It only makes sense for inherited POMs in multi-modules POMs an
Forget the question at the end of my last email. The call:
ReaderFactory.newXmlReader(bookDescriptor);
in DefaultBookIo#readBook(File) produces a NoClassDefFoundError:
org/codehaus/plexus/util/ReaderFactory. I don't think it can find that
jar at all when I build the plugin.
I'm simple running "m
The issue that caused this (MNG-3244) has been reverted and it's working
now. New candidates posted (http://people.apache.org/~brianf/2.0.8/)
I also created a jira because we have no core IT to cover this.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
o
I'm afraid I'm getting the same exception, although the Maven2 plugin
for Eclipse is no longer showing me plexus-utils:1.0.2 and
plexus-utils:1.4.5.
The unit tests are running and I'm getting the output for an APT source
to docbook target book rendering, which is what I'm trying to do in my
applic
Ok, disregard the last message from me, then. My email wasn't updating
and I didn't get your message, and mine didn't send, until just now.
Thanks.
Jonathan Card
-Original Message-
From: Dennis Lundberg [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 24, 2007 3:11 PM
To: Maven Develo
I understand that there's a lot of discussion going on about a release,
but I had a follow up question to the one below.
With a fresh checkout of the code at
"maven/doxia/doxia/tags/doxia-1.0-alpha-9", I built "doxia-book" and
decompiled "BookModelXpp3Reader.class", which "diff" indicated diffe
Hi Guys,
I recently submitted a patch to a problem listed in JIRA
(http://jira.codehaus.org/browse/ARCHETYPE-35) but I didn't hear any response
after a few weeks. Do I need to post here to bring it to someone's attention?
Maybe an email?
I don't want to be a pest, I just don't know if there
Le mercredi 24 octobre 2007, Dennis Lundberg a écrit :
> [EMAIL PROTECTED] wrote:
> > Author: hboutemy
> > Date: Tue Oct 23 14:36:41 2007
> > New Revision: 587665
> >
> > URL: http://svn.apache.org/viewvc?rev=587665&view=rev
> > Log:
> > encoding fixes
> >
> > Modified:
> >
> > maven/plugins/tr
+1
-Lukas
Carlos Sanchez wrote:
Please vote for a release of maven parent and two of the children
Maven parent 7
- upgraded remote resources plugin and apache resources bundle to latest release
- added javadoc urls
- added developers
maven-shared-components parent
- use latest maven parent
m
+1
-Lukas
Dennis Lundberg wrote:
Hi,
I'd like to once more try to release maven-changes-plugin 2.0-beta-3. On
the second try, Olivier Lamy found an issue with anchors not being
properly encoded in the report. This has now been solved.
Over 20 issues have been resolved for this release. The
MNG-3254.
I have attached a sample project.
--
Olivier
2007/10/24, Brian E. Fox <[EMAIL PROTECTED]>:
>
> This could be related to one of the fixes, please create a jira and I'll
> check it out
>
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
> oliv
Sorry, I forgot,
+1
Arnaud
On 10/24/07, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
>
> Ping.
>
> We need one more PMC vote on this one.
>
> Dennis Lundberg wrote:
> > Hi,
> >
> > I'd like to once more try to release maven-changes-plugin 2.0-beta-3. On
> > the second try, Olivier Lamy found an i
[EMAIL PROTECTED] wrote:
Author: hboutemy
Date: Tue Oct 23 14:36:41 2007
New Revision: 587665
URL: http://svn.apache.org/viewvc?rev=587665&view=rev
Log:
encoding fixes
Modified:
maven/plugins/trunk/maven-project-info-reports-plugin/src/main/java/org/apache/maven/report/projectinfo/Abstract
Dave Syer wrote:
Is anyone actively involved in developing the Confluence module right now?
Several issues have been raised this week (some by me), but no-one seems to
be reviewing them, or working on them. Some are really trivial.
I'm one of the active developers on doxia. I haven't had time
Ping.
We need one more PMC vote on this one.
Dennis Lundberg wrote:
Hi,
I'd like to once more try to release maven-changes-plugin 2.0-beta-3. On
the second try, Olivier Lamy found an issue with anchors not being
properly encoded in the report. This has now been solved.
Over 20 issues have
Unfortunately there was a problem with the dependencies specified in
1.0-alpha-9. I'm working on getting a quick 1.0-alpha-10 out the door
that fixes these problems. It would be really helpful if you could try
the latest 1.0-alpha-10-SNAPSHOT to see if that solves your problems.
Jon Card wrote
This could be related to one of the fixes, please create a jira and I'll
check it out
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
olivier lamy
Sent: Wednesday, October 24, 2007 12:46 PM
To: Maven Developers List
Subject: Re: 2.0.8 Release Candidate
H
Hi Dave,
On Oct 24, 2007, at 7:08 PM, Dave Syer wrote:
Is anyone actively involved in developing the Confluence module
right now?
Several issues have been raised this week (some by me), but no-one
seems to
be reviewing them, or working on them. Some are really trivial.
I guess the answ
Is anyone actively involved in developing the Confluence module right now?
Several issues have been raised this week (some by me), but no-one seems to
be reviewing them, or working on them. Some are really trivial.
--
View this message in context:
http://www.nabble.com/Confluence-module-outsta
Hi,
I have an issue concerning site deployment with multi modules project.
(don't know if it's a know issue).
My root pom contains :
sftp-rec-ap2
sftp://xx.xxx.xxx.xxx/${rootPath}
With mvn 2.0.7 root site is deployed to ${rootPath} and modules to
${rootPath}/{artifactId
Welcome Paul!
Two places to read if you haven't are the roles at the ASF:
http://www.apache.org/foundation/how-it-works.html#meritocracy
http://www.apache.org/foundation/how-it-works.html#roles
It's important to note that sending the CLA alone doesn't make you a
committer - you must first cont
On 10/24/07, Nigel Magnay <[EMAIL PROTECTED]> wrote:
> ... except that this one has been worked on. By my count of jira, it's got
> 27 fixes in it already, 7 of which are marked as critical.
Agreed.
>
> I'd try and help. Really. But the huge stack of technologies involved that
> are, basically, p
... except that this one has been worked on. By my count of jira, it's got
27 fixes in it already, 7 of which are marked as critical.
I'd try and help. Really. But the huge stack of technologies involved that
are, basically, proprietary to maven and aren't documented is a substantial
barrier. That
hi,
i am living with severe bugs (see http://jira.codehaus.org/browse/MNG-3252)
+ transitive resolving which not only comes from assembly plugin (as stated
in http://jira.codehaus.org/browse/MASSEMBLY-242) merely in maven core
transitive resolving too.
i would like to help to fix and to integra
that's the same story everytime. We need people to work on plugins and
on the codebase in general. If nobody has the time to work on those
items, we have no release. It is that simple.
We need to make sure that we deliver the right features. I will not be
happy if the new release solves things but
can't we have a 2.2-beta-3 after this one?
It's been 6 months since the last release...
On 22/10/2007, John Casey <[EMAIL PROTECTED]> wrote:
>
> Sorry guys, I've been pinned at work recently, and haven't had time
> to try hacking away at the remaining issues slated for 2.2-beta-2.
>
> -john
>
> O
+!
Brian E. Fox wrote:
I ran into an issue releasing 2.0.8 due to
http://jira.codehaus.org/browse/MRELEASE-296 and the addition of the
${mavenVersion} in the poms. This release is required for a release of
2.0.8.
Staging repo:
http://people.apache.org/~brianf/staging-repository/
Relea
+1
Emmanuel
Brian E. Fox a écrit :
I ran into an issue releasing 2.0.8 due to
http://jira.codehaus.org/browse/MRELEASE-296 and the addition of the
${mavenVersion} in the poms. This release is required for a release of
2.0.8.
Staging repo:
http://people.apache.org/~brianf/staging-repositor
+1
--
Olivier
2007/10/24, Brian E. Fox <[EMAIL PROTECTED]>:
>
> I ran into an issue releasing 2.0.8 due to
> http://jira.codehaus.org/browse/MRELEASE-296 and the addition of the
> ${mavenVersion} in the poms. This release is required for a release of
> 2.0.8.
>
>
>
> Staging repo:
>
> http://peo
+1
Stéphane
On 10/24/07, Brian E. Fox <[EMAIL PROTECTED]> wrote:
> I ran into an issue releasing 2.0.8 due to
> http://jira.codehaus.org/browse/MRELEASE-296 and the addition of the
> ${mavenVersion} in the poms. This release is required for a release of
> 2.0.8.
>
>
>
> Staging repo:
>
> http://p
31 matches
Mail list logo
