The following comment has been added to this issue:
Author: Felipe Leme
Created: Wed, 4 Aug 2004 12:24 AM
Body:
Carlos,
Could you please relate this bug to:
http://jira.codehaus.org/browse/MAVEN-128
-- Felipe
-
The following comment has been added to this issue:
Author: Felipe Leme
Created: Wed, 4 Aug 2004 12:22 AM
Body:
It doesn't work with included XML (at least I couldn't get it to :-), as shown in the
test case. It work with code like this:
<[CDATA[
]]>
In fact, that's what we w
The following comment has been added to this issue:
Author: Felipe Leme
Created: Wed, 4 Aug 2004 12:17 AM
Body:
Not only mail-lists.xml but also MailingList.java
I will try to do these changes as this is a relative simple fix but a good exercise
on how to change Maven´s API (so
The following comment has been added to this issue:
Author: dion gillard
Created: Wed, 4 Aug 2004 12:14 AM
Body:
What's wrong with ?
-
View this comment:
http://jira.codehaus.org/browse/MPXDOC-118?page=comments#
The following issue has been updated:
Updater: Felipe Leme (mailto:[EMAIL PROTECTED])
Date: Tue, 3 Aug 2004 11:42 PM
Comment:
Screenshot of the test case
Changes:
Attachment changed to Screenshot-MPXDOC-118.png
---
The following issue has been updated:
Updater: Felipe Leme (mailto:[EMAIL PROTECTED])
Date: Tue, 3 Aug 2004 11:40 PM
Comment:
Test case - just run 'maven xdoc' on it and see the results...
Changes:
Attachment changed to testcase-mpxdoc-118.zip
-
The following issue has been updated:
Updater: Felipe Leme (mailto:[EMAIL PROTECTED])
Date: Tue, 3 Aug 2004 11:39 PM
Comment:
Proposed patch.
Changes:
Attachment changed to mpxdoc-118.patch
-
Fo
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPXDOC-118
Here is an overview of the issue:
-
Key:
The following comment has been added to this issue:
Author: dion gillard
Created: Tue, 3 Aug 2004 9:33 PM
Body:
Does maven scm:cvs-create-patch create a correct patch file, or does that goal need
changing to handle whitespace?
--
Brett Porter wrote:
The Maven developers have been discussing the future repository format so I can speak
with reasonable authority on this.
[X] +1 Put everything in one directory (such as jakarta-taglibs)
Advantage: less groups on ibiblio
Disadvantage: the group is going to be huge (aroun
Carlos Sanchez wrote:
Hi,
I just think that jstl shouldn't be mixed with concrete implementations.
That whats tough about Sun releasing jars as a standard. Where should
the api's be stored! Ultimately, I believe there are distribution
"clauses" in the lisences for these things that allow us to
Brett Porter wrote:
I thought I should discuss a little further since Mark disagrees on some points here.
+1 The decision on which structure to use should be more dependent on
the "type" of group structure you have. If you expect the various
"subgroups" of your group to be releasing on separat
Rather than going over it all, it might be helpful to read this:
http://docs.codehaus.org/display/MAVEN/Repository+-+Layout
Cheers,
Brett
Quoting Carlos Sanchez <[EMAIL PROTECTED]>:
> Hi,
>
> I just think that jstl shouldn't be mixed with concrete implementations.
>
> About the other issues w
The following comment has been added to this issue:
Author: Dennis Lundberg
Created: Tue, 3 Aug 2004 4:39 PM
Body:
MAVEN-1386 solves the documentation issues. The POM in the current, although not yet
released, integrate.xml does validate. We should await MAVEN-1410 before closing
The following issue has been updated:
Updater: Jeff French (mailto:[EMAIL PROTECTED])
Date: Tue, 3 Aug 2004 3:54 PM
Comment:
My bias for UNIX was showing with that TAR file. Here is a ZIP file as well.
Changes:
Attachment changed to maven-1413.zip
--
The following issue has been updated:
Updater: Jeff French (mailto:[EMAIL PROTECTED])
Date: Tue, 3 Aug 2004 3:49 PM
Comment:
I have attached a small project that demonstrates the problem. When you untar, you'll
get an 'ant' and 'maven' directory. Type this at the command line:
a
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MAVEN-1413
Here is an overview of the issue:
-
Key:
The following issue has been updated:
Updater: Dennis Lundberg (mailto:[EMAIL PROTECTED])
Date: Tue, 3 Aug 2004 2:47 PM
Comment:
Added a patch for the XSD for MAVEN-1_0-BRANCH.
Changes:
Attachment changed to maven-project.xsd-1_0-BRANCH.patch
---
The following issue has been updated:
Updater: Dennis Lundberg (mailto:[EMAIL PROTECTED])
Date: Tue, 3 Aug 2004 2:32 PM
Comment:
Oops! An IDE that eats whitespace at the end of lines and a diff-tool with the "Ignore
differences in whitespace"-checkbox checked is a dangerous combina
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MAVENUPLOAD-181
Here is an overview of the issue:
-
The following issue has been updated:
Updater: Felipe Leme (mailto:[EMAIL PROTECTED])
Date: Tue, 3 Aug 2004 1:52 PM
Comment:
Patch that checks if the project's current version is on the POM's versions element.
Changes:
Attachment changed to mpannouncement-14.patch
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPANNOUNCEMENT-14
Here is an overview of the issue:
-
On Tue, 3 Aug 2004 16:29:06 +0200, "Nicolas De Loof"
<[EMAIL PROTECTED]> wrote:
> Just a suggestion, that may be a bad idea...
I don't think it's a bad idea, but...
> What about setting groupid to "taglibs/standard" ?
> That may allow using a more hierarchical repository
(www.ibiblio.org/maven h
Hi,
I just think that jstl shouldn't be mixed with concrete implementations.
About the other issues with group names maybe we should consider the
repository layout. Currently anyone can request an upload to any group and I
think this won't scale well and can lead to conflict problems. Having stri
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MODELLO-9
Here is an overview of the issue:
-
Key:
The following comment has been added to this issue:
Author: Felipe Leme
Created: Tue, 3 Aug 2004 10:33 AM
Body:
> cvs diff -uN
> should do the trick
Yes, it would work only if I had 'cvs added' the files first, but unfortunately that
didn't work neither (see previous post).
:-(
Just a suggestion, that may be a bad idea...
What about setting groupid to "taglibs/standard" ?
That may allow using a more hierarchical repository (www.ibiblio.org/maven has so much
directories...)
repository_root
- taglibs
- standard
-
- artifact-versi
The following comment has been added to this issue:
Author: Brett Porter
Created: Tue, 3 Aug 2004 10:27 AM
Body:
just on new files and CVS:
cvs diff -uN
should do the trick
-
View this comment:
http://jira.code
The following comment has been added to this issue:
Author: Brett Porter
Created: Tue, 3 Aug 2004 10:24 AM
Body:
Thanks - looks good. Could you possibly redo the HEAD patch without the whitespace
changes? diff -wb I think.
The XSD change should be applied to MAVEN-1_0-BRANCH as w
I thought I should discuss a little further since Mark disagrees on some points here.
> +1 The decision on which structure to use should be more dependent on
> the "type" of group structure you have. If you expect the various
> "subgroups" of your group to be releasing on separate schedules and/
The Maven developers have been discussing the future repository format so I can speak
with reasonable authority on this.
> [X] +1 Put everything in one directory (such as jakarta-taglibs)
>Advantage: less groups on ibiblio
>Disadvantage: the group is going to be huge (around 30-80 files o
The following comment has been added to this issue:
Author: Carlos Sanchez
Created: Tue, 3 Aug 2004 10:11 AM
Body:
It would be helpful if the -X output has a ClassCastException to see if it is related
to other previous issues
---
The following comment has been added to this issue:
Author: Brett Porter
Created: Tue, 3 Aug 2004 10:01 AM
Body:
-X output may not be helpful, but you can check it. -D options work for me... and
should win over build.properties settings, but can you check whether it is set there?
The following issue has been updated:
Updater: Felipe Leme (mailto:[EMAIL PROTECTED])
Date: Tue, 3 Aug 2004 9:41 AM
Comment:
I couldn't send a message from my SMTP server at work because I wasn't sending the
HELO message.
So, here is yet another patch, this time using a maven prope
Felipe Leme wrote:
Hi all,
As we haven't reached a common sense on how to name the groups, I think
we should vote for it. The issues are:
1.Multiple directories x one directory:
[ ] +1 Put everything in one directory (such as jakarta-taglibs)
Advantage: less groups on ibiblio
Disadvantage: th
Oops, forgot my votes:
> 1.Multiple directories x one directory:
> [X ] +1 Create one directory for group (ex: taglibs-standard,
> taglibs-request).
> Advantages: easier to locate artifacts; consistent with the way
> Jakarta Commons is organized
> 3.Where to put jstl.jar
> [X] +1 On existing grou
On Tue, 2004-08-03 at 03:44, Nicolas De Loof wrote:
> MAVEN ENHANCEMENT SUGGESTION:
>
> Could'nt we have an automatic way to 'deprecate' some artifcat location, giving the
> alternative group/artifactId to be
> used ? It may been displayed by maven as a warning when downloading dependencies.
> F
On Tue, 2004-08-03 at 02:21, John Casey wrote:
> Just curious, but are you in control of the jakarta-taglibs builds?
Yes, I am one of the committers.
> understand if you're pinging the maven-dev list for best practices (I
Agree, but I'm not subscribed there (and started the thread here). Could
The following comment has been added to this issue:
Author: Carlos Sanchez
Created: Tue, 3 Aug 2004 5:20 AM
Body:
Could you post the output of running maven with the -X option
-
View this comment:
http://jira.cod
Message:
The following issue has been closed.
-
View the issue:
http://jira.codehaus.org/browse/MPMULTIPROJECT-38
Here is an overview of the issue:
-
The following comment has been added to this issue:
Author: Michael Mattox
Created: Tue, 3 Aug 2004 4:12 AM
Body:
It hasn't happened since the upgrade to Maven 1.0. I don't know why or any more
details because it was not consistent. It stopped generating the overview page and
t
The following comment has been added to this issue:
Author: Henning Schmiedehausen
Created: Tue, 3 Aug 2004 3:14 AM
Body:
You should load _either_ the XML file _or_ the properties file. Loading
both will result in "duplicate imports".
I use this patch for a large(ish) project and
42 matches
Mail list logo
