Brett,
> Right, I see your point. Being XML I'm sure concatenating them
> and modifying the unique IDs isn't going to be a huge issue
> though - I'm sure at some point in the past someone has had to
> do this?
Have to ever looked at Jira's database structure? The XML is nothing more
than a refle
> Have to ever looked at Jira's database structure? The XML is
> nothing more than a reflection of their structure. Tables,
> keys, normalized relations, etc.
Yes, it is very normalized. I've done a few hacks myself to make our
transition from bugzilla a bit better, and find it was quite easy
On Thu, 2003-10-23 at 21:27, Noel J. Bergman wrote:
> Jason,
> Ask what? Ask if it was OK for the ASF to migrate ASF projects back to the
> ASF infrastructure
You said in process which means we weren't even made aware of the
process and absolutely you should ask. If I didn't say anything would
The following issue has been updated:
Updater: Paul O'Fallon (mailto:[EMAIL PROTECTED])
Date: Thu, 23 Oct 2003 10:38 PM
Comment:
This is the patch.
Changes:
Attachment changed to patch.txt
-
For
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-966
Here is an overview of the issue:
--
> bugzilla import is completely broken in 2.4.1,
> whereas it works quite well in the 2.5 beta :)
Aha! I was wondering about that problem. :-)
> But regarding maven and codehaus projects moving - I currently agree with
> Jason that we should wait until Apache's bugzilla has been moved at least,
> Are you guys using JIRA 2.5? It's currently beta-2, but due
> for release in a week or so and looks very nice. I've been
> trialling it out here and its stable as far as I can tell.
Jira 2.4.1, but I'm sure we'll update when 2.5 is released.
Actually, it might be worth trying the 2.5 release ca
Jason,
The notice was a heads up. We have no intention of migrating the ASF
projects from codehaus until the Jira installation and migration is stable,
and at the moment, there remain issues. As a point of interest, the Maven
Roadmap is one of the issues. We have submitted a problem report to
A
Right, I see your point. Being XML I'm sure concatenating them and modifying
the unique IDs isn't going to be a huge issue though - I'm sure at some
point in the past someone has had to do this? We possibly need a way to do
it consistently as other projects join ASF and bring their previous issue
t
Last 500 lines of a clean bootstrap build of maven at 20031023-2200
[exec] +
[exec] build:
[exec] [echo] D succeeds on purpose
[exec] [echo] failure-1 failed correctly
[exec] [echo] failure-2 failed correctly
[exec
Well, for one bugzilla import is completely broken in 2.4.1, whereas it
works quite well in the 2.5 beta :)
But regarding maven and codehaus projects moving - I currently agree with
Jason that we should wait until Apache's bugzilla has been moved at least,
then worry about other projects. Minimise
Antoehr thing that is worrying here is that you are copying resources out of
the target directory. I assume this is because you have preprocessed
something else in some way into target, and are then copying that into
target/classes via a resource.
If you really need to do this, I'd actually use a
It's set in the java:compile preGoal of the parent project this project
is inherited from. The problem is that there are other things using
this variable that remain consistent across projects, so I want to be
able to use the variable here, too. Having to rely on the basedir form
eliminates consi
Where is my.meta.dir set? Anyway, the basedir form seems a lot better. You
can even omit basedir in rc1.
- Brett
> -Original Message-
> From: Sean Timm [mailto:[EMAIL PROTECTED]
> Sent: Friday, 24 October 2003 10:49 AM
> To: Maven Developers List
> Subject: RE: POM Build Resources and Pa
I'm using RC1. Upon further research, it's not a slash issue. I
thought it was, but it's something else. I modified my variable to
convert all slashes to backslashes, and it still failed. Here's the
relevant resources section:
${my.meta.dir}
Never had a problem using forward slashes on windows. This sounds unrelated.
What does your section look like? What version of maven?
- Brett
> -Original Message-
> From: Sean Timm [mailto:[EMAIL PROTECTED]
> Sent: Friday, 24 October 2003 10:13 AM
> To: [EMAIL PROTECTED]
> Subject: POM
I was having some bizarre issues where the jar plugin was grabbing
everything in my project folder as a resource, and I finally tracked it
down to a problem with the '/' vs. the '\' in a directory. By default,
maven.build.dir is set to something like the following:
C:\mySource\currentDirectory/tar
On Thu, 2003-10-23 at 16:25, Noel J. Bergman wrote:
> Guys,
>
> This is just a HEADS UP. Apache has set up Jira on nagoya. We are in the
> process of working with codehaus to migrate all of the ASF projects.
Please do not move the Maven issues to Apache.
We are currently happy with the install
Are you guys using JIRA 2.5? It's currently beta-2, but due for release in a
week or so and looks very nice. I've been trialling it out here and its
stable as far as I can tell.
Cheers,
Brett
> -Original Message-
> From: Noel J. Bergman [mailto:[EMAIL PROTECTED]
> Sent: Friday, 24 Octobe
Guys,
This is just a HEADS UP. Apache has set up Jira on nagoya. We are in the
process of working with codehaus to migrate all of the ASF projects.
We're currently using a test load from codehaus. Once we've ascertained
that there are no kinks, we'll load the final live data from Bob, at which
The following comment has been added to this issue:
Author: Per Olesen
Created: Thu, 23 Oct 2003 3:06 PM
Body:
To Don:
> Give us your version of a better message
Hmm, ... looking back, I might be better able to interpret the given message now. But
now I also know more about mav
The following comment has been added to this issue:
Author: Per Olesen
Created: Thu, 23 Oct 2003 3:00 PM
Body:
To Ludovic:
Are you sure it is *perfectly* the same error message. Just had a look in the (HEAD)
sources, seeing that it expects *exactly* 6 tokens. And you can get two
evenisse2003/10/23 12:07:43
Modified:xdocs/misc articles.xml
Log:
Add a new article by Rob Herbst on onjava
Revision ChangesPath
1.3 +5 -0 maven/xdocs/misc/articles.xml
Index: articles.xml
=
Running build-bootstrap.xml from CVS on OS X 10.2.8. Hangs on
org.apache.maven.linkcheck.LinkCheckTest.
What follows is nothing you haven't seen before. It just gets to
LinkCheckTest and stops.
[exec] clean:
[exec] plugin:
[exec] java:prepare-filesystem:
[exec] [mkdir] Cr
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-965
Here is an overview of the issue:
--
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-964
Here is an overview of the issue:
--
The following comment has been added to this issue:
Author: nicolas de loof
Created: Thu, 23 Oct 2003 10:08 AM
Body:
Problem comes from URL notation for property "maven.repo.remote"
assuming RFC http://www.w3.org/Addressing/rfc1738.txt, file protocol URL should have
syntax
file
When trying to use the jcoverage plugin I've been repeatedly getting
exceptions. The exception is a NumberFormatException thrown from within the
CoverageReport's generatePercentResult(..) method. The string being parsed
is "?" but I can't see that in the source xml report other than the xml
prolo
The following comment has been added to this issue:
Author: Emmanuel Venisse
Created: Thu, 23 Oct 2003 9:43 AM
Body:
We support other jdk version that don't have this property. So, we can't use this
property in Maven. We must use a generic mecanism usable by all jdk.
-
The following comment has been added to this issue:
Author: Chris Rauschuber
Created: Thu, 23 Oct 2003 9:05 AM
Body:
Forgot to mention that the patch is for maven-eclipse-1.4-SNAPSHOT/plugin.jelly.
-
View the issue
The following issue has been updated:
Updater: Chris Rauschuber (mailto:[EMAIL PROTECTED])
Date: Thu, 23 Oct 2003 9:02 AM
Comment:
This should fix it.
It uses maven:makeRelativePath, which I found in the 1.4 version of the eclipse plugin.
Changes:
Attachment changed
The following comment has been added to this issue:
Author: Martin Skopp
Created: Thu, 23 Oct 2003 8:45 AM
Body:
Seems this is solved at least for Java 1.4.2:
Ewan Harrow <[EMAIL PROTECTED]>Ewan Harrow <[EMAIL PROTECTED]> wrote on Thu, 23 Oct
2003 08:51:48 +0100 (BST) on the mave
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-963
Here is an overview of the issue:
--
--- khote <[EMAIL PROTECTED]> wrote:
> I checked out xdoclet-all from sourceforge.
>
> Of course I'm asking about the use of the old-style
> maven plugin
> dependencies declarations used in the project.xml:
>
>
> xdoclet+xjavadoc
> @XJAVADOC_VERSION@
>
>
> causes the m
The following issue has been updated:
Updater: Martin Skopp (mailto:[EMAIL PROTECTED])
Date: Thu, 23 Oct 2003 6:30 AM
Comment:
Ok Brett, heres a patch for source + doc.
I did a short test with and without the file in
$HOME/.maven/ - worked fine.
Changes:
Attachmen
[EMAIL PROTECTED] wrote:
How about dist.directory?
the idea behind the category/group was that it labeled the artifact
with a property (eg, "shared", "tools") and that was then used as a
key to determine the directory to deploy to in the dist
via the additional property, eg
dist.dependencies.categ
I checked out xdoclet-all from sourceforge.
Of course I'm asking about the use of the old-style maven plugin
dependencies declarations used in the project.xml:
xdoclet+xjavadoc
@XJAVADOC_VERSION@
causes the maven-xdoclet-plugin to look for xdoclet-xjavadoc-1.0.1.jar (in
37 matches
Mail list logo
