I'm working on replacing the POM parser in Maven 1.1, and POMS that
previously parsed with things like this:
../../../../src/messages
**/*.properties
Now fail because the includes format is not legal. It should be:
**/*.properties
The following comment has been added to this issue:
Author: Jim Crossley
Created: Fri, 17 Sep 2004 10:58 PM
Body:
Patch attached that makes the p4 source repository URL and the file activity report
much nicer.
-
V
The following issue has been updated:
Updater: $changelogauthor.fullName (mailto:)
Date: Fri, 17 Sep 2004 10:55 PM
Changes:
Attachment changed to p4-url.patch
-
For a full history of the issue, see:
brett 2004/09/17 18:02:14
Modified:.project.xml
src/java/main/org/apache/maven/jelly/tags/maven
AddPathTag.java PropertyTag.java ReactorTag.java
Log:
depend on maven-1.1-SNAPSHOT
Revision ChangesPath
1.5 +2 -3 ma
Message:
The following issue has been reopened.
Reopener: Ben Walding
Date: Fri, 17 Sep 2004 8:58 PM
Damn I thought I'd get away with closing it ;)
Will take a look at it soon. Overhauling big chunks of it.
-
View
The following comment has been added to this issue:
Author: Ben Walding
Created: Fri, 17 Sep 2004 8:53 PM
Body:
Yeah I noticed this yesterday. Jetty does not like running out of an uberjar anymore.
(Basically it does a getPackage() on a class and this returns null under classworl
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPCHANGELOG-45
Here is an overview of the issue:
-
brett 2004/09/17 15:17:58
Modified:.project.xml
src/java/main/org/apache/maven/jelly/tags/maven
CopyResources.java
Log:
switch to maven-model
upgrade dependencies
Revision ChangesPath
1.4 +11 -5 maven-jelly-tags
I have branched maven-jelly-tags. If you want to make any bugfixes to
the current one for inclusion in Maven 1.0.1, that is the place:
MAVEN-1_0_1-BRANCH.
HEAD is maven-jelly-tags-1.1-SNAPSHOT (not its correspondence with Maven
itself is coincidental!)
The reason for this is so that I can use t
The following comment has been added to this issue:
Author: Mark Hobson
Created: Fri, 17 Sep 2004 4:33 PM
Body:
Still breaks for me - ensure you haven't got MAVEN_HOME set in your environment.
-
View this comment:
ven-proxy-standalone-20040917-uber.jar
/usr/local/maven-proxy/mavenproxy.properties
maven-proxy Unversioned
Saving repository at /var/tmp/proxy-repo
Scanning repository: http://www.ibiblio.org/maven
Scanning repository: http://dist.codehaus.org
Starting...
Internal error:
java.lang.NullPointerExcept
The following issue has been updated:
Updater: John Taylor (mailto:[EMAIL PROTECTED])
Date: Fri, 17 Sep 2004 8:44 AM
Comment:
Attached is a patch, with the corrected code copied verbatim out of the jar plugin.
Changes:
Attachment changed to plugin.jelly
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPWAR-32
Here is an overview of the issue:
-
Key: M
Hi Ben,
[EMAIL PROTECTED] wrote on Thursday, September 16, 2004 1:11 PM:
> Message:
>
>The following issue has been closed.
>
>Resolver: Ben Walding
>Date: Thu, 16 Sep 2004 7:10 AM
>
> Thanks Emmanuel, after thinking a bit more (about the
> stacktrace) I thought it might be mave
Message:
The following issue has been closed.
-
View the issue:
http://jira.codehaus.org/browse/MAVENUPLOAD-216
Here is an overview of the issue:
-
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MAVENUPLOAD-216
Here is an overview of the issue:
-
The following comment has been added to this issue:
Author: Carlos Sanchez
Created: Fri, 17 Sep 2004 4:04 AM
Body:
You should use codehaus repo that is automatically sync'ed to ibiblio
-
View this comment:
http:/
Message:
The following issue has been closed.
Resolver: Carlos Sanchez
Date: Fri, 17 Sep 2004 4:01 AM
Hyphens are not allowed in version, use dots
-
View the issue:
http://jira.codehaus.org/browse/MAVENUPLOAD-213
Brett Porter wrote on Friday, September 17, 2004 9:29 AM:
> It has worked for me very recently - are you sure your
> plugins checkout is untainted? Try a clean checkout? Anything
> dodgy in ~/.maven/cache?
Clean checkout did the trick. Sorry for bothering ...
- Jörg
Message:
The following issue has been closed.
-
View the issue:
http://jira.codehaus.org/browse/MAVENUPLOAD-214
Here is an overview of the issue:
-
It has worked for me very recently - are you sure your plugins checkout is
untainted? Try a clean checkout? Anything dodgy in ~/.maven/cache?
- Brett
Quoting Jörg Schaible <[EMAIL PROTECTED]>:
> Hi folks,
>
> it seems that currently it is not possible to bootstrap the 1.0 branch. After
> builin
Hi folks,
it seems that currently it is not possible to bootstrap the 1.0 branch. After builing
the plugins, the process fails:
=== %< ===
[echo] |
[echo] | BUILDING MAVEN WITH ITSELF...
[echo] |
[echo]
[exec] __ __
[exec] | \/ |__ _Apache__ ___
22 matches
Mail list logo
