The following comment has been added to this issue:
Author: Martin Jaeger
Created: Mon, 14 Jun 2004 1:48 AM
Body:
Hi Brett
Your duplication removal fixed the plugin. Now the -source parameter is not longer in
the javac call.
Thanks
The following comment has been added to this issue:
Author: Rafael Santiago, Jr.
Created: Mon, 14 Jun 2004 12:43 AM
Body:
Woops, meant to say that the quick fix is to set "pom.repository.url" in your
build.properties as well.
---
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPCHANGELOG-43
Here is an overview of the issue:
-
ok. Cool. Thanks for the information. I understand better now.
How do we deal with different versions of the same artifact in the
dependency list?
It seems to me that once we get transitive dependencies, we'll have lots
of "clashes" between different versions of the same artifacts. How will
Mave
The following comment has been added to this issue:
Author: Rafael Santiago, Jr.
Created: Mon, 14 Jun 2004 12:07 AM
Body:
Currently, it seems that the plugin only onderstands cvspass lines in the format
created by running "maven -Dpassword=XX changelog:create-cvspass", namely:
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MAVENUPLOAD-138
Here is an overview of the issue:
-
aheritier2004/06/13 15:56:55
Modified:pdf/src/plugin-resources fo-layouts.xslt
Log:
PR: MPPDF-10
Submitted By: M. Sean Gilligan
Reviewed By: Arnaud Heritier
Add USLetter (8.5"x11") as a paperType
Revision ChangesPath
1.7 +2 -0 maven-plugins/pdf/src/plugi
Message:
The following issue has been closed.
Resolver: Arnaud HERITIER
Date: Sun, 13 Jun 2004 6:55 PM
Applied in CVS. Thanks.
-
View the issue:
http://jira.codehaus.org/browse/MPPDF-10
Here is an overview of the
aheritier2004/06/13 15:55:27
Modified:pdf project.xml
pdf/xdocs changes.xml properties.xml
Log:
PR: MPPDF-10
Submitted By: M. Sean Gilligan
Reviewed By: Arnaud Heritier
Add USLetter (8.5"x11") as a paperType
Revision ChangesPath
1.39 +1 -3
The following comment has been added to this issue:
Author: M. Sean Gilligan
Created: Sun, 13 Jun 2004 6:34 PM
Body:
I suppose the properties documentation page should be updated too:
Index: properties.xml
===
RCS fil
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPPDF-10
Here is an overview of the issue:
-
Key: M
On Sun, 2004-06-13 at 14:11, Vincent Massol wrote:
> Hi,
>
> A stupid question: Why do we need POMs in repo for non-Maven projects?
Those non-maven projects have dependencies and projects who state a
dependency on that non-maven project can take advantage of transitive
dependencies and any other
Sure, but dependencies don't necessarily mean build-time stuff.
My project might depend on NonMavenProject-A, which also depends on
NonMavenProject-B.
So, I build my project against their NonMavenProject-A.jar file, and then
to *use* my project at runtime, I have to include NonMavenProject-B.jar
Hi,
A stupid question: Why do we need POMs in repo for non-Maven projects?
It seems to me, this is for supporting transitive dependencies. However
Maven will not try to build non-Maven projects, right? Is there a use
case where it's still useful to have POM information for non-Maven
projects?
I'
Message:
The following issue has been closed.
Resolver: Vincent Massol
Date: Sun, 13 Jun 2004 1:32 PM
done
-
View the issue:
http://jira.codehaus.org/browse/MPABBOT-1
Here is an overview of the issue:
---
The following comment has been added to this issue:
Author: Vincent Massol
Created: Sun, 13 Jun 2004 1:32 PM
Body:
Done. POMs have been uploaded. Am I right in assuming that POMs for projects not using
Maven do not need to contain dependencies as they're not going to be used. It's
vmassol 2004/06/13 10:17:22
Modified:jboss/src/plugin-resources debug.bat
Log:
Binary --> Ascii
Revision ChangesPath
1.2 +0 -0 maven-plugins/jboss/src/plugin-resources/debug.bat
Index: debug.bat
===
The following comment has been added to this issue:
Author: Vincent Massol
Created: Sun, 13 Jun 2004 1:16 PM
Body:
Applied. However, I don't see where these debug scripts are triggered from.
-
View this comment:
vmassol 2004/06/13 10:16:52
Modified:jboss/src/plugin-resources debug
Log:
Binary --> Ascii
Revision ChangesPath
1.2 +0 -0 maven-plugins/jboss/src/plugin-resources/debug
Index: debug
===
R
vmassol 2004/06/13 10:15:58
Modified:jboss/xdocs properties.xml changes.xml
jbossplugin.properties project.xml plugin.jelly
Added: jboss/src/plugin-resources debug debug.bat
Log:
Applied MPJBOSS-14. Add new debug scripts to start jboss in debug mode.
R
The following comment has been added to this issue:
Author: Vincent Massol
Created: Sun, 13 Jun 2004 12:19 PM
Body:
>Your proposal sounds good, but I have one comment on it: how to
> distinguish between the group, atid and aid? How does this show in
> the textual format?
>
> Wrong
vmassol 2004/06/13 09:16:48
Modified:changes/xdocs properties.xml
Log:
Added explanations for using the different trackers
Revision ChangesPath
1.5 +3 -1 maven-plugins/changes/xdocs/properties.xml
Index: properties.xml
===
vmassol 2004/06/13 09:13:22
Modified:changes plugin.properties
Log:
Added comment for using the sourceforge tracker
Revision ChangesPath
1.6 +3 -0 maven-plugins/changes/plugin.properties
Index: plugin.properties
=
The following comment has been added to this issue:
Author: Martijn Dashorst
Created: Sun, 13 Jun 2004 12:11 PM
Body:
The patch updates the plugin.properties file to show the sourceforge example
and updates the properties.xml file in the xdoc directory to give examples of JIRA,
s
The following issue has been updated:
Updater: Martijn Dashorst (mailto:[EMAIL PROTECTED])
Date: Sun, 13 Jun 2004 12:10 PM
Changes:
Attachment changed to MPCHANGES-9.patch
-
For a full history of th
The following comment has been added to this issue:
Author: Martijn Dashorst
Created: Sun, 13 Jun 2004 11:53 AM
Body:
Thanks, Fabrizio, I hadn't tried using just the aid. Supplying the groupId as well
*doesn't* work.
Vincent, shall I supply a patch for the documentation?
Martijn
The following comment has been added to this issue:
Author: Martijn Dashorst
Created: Sun, 13 Jun 2004 11:50 AM
Body:
I was thinking about a more general solution, but figured to solve the sourceforge
first ;-).
Your proposal sounds good, but I have one comment on it: how to dist
The following comment has been added to this issue:
Author: fabrizio giustina
Created: Sun, 13 Jun 2004 11:49 AM
Body:
Sourceforge also supports linking issues with the single "aid" parameter.
You can use the following template to make actual plugin working with sourceforge:
maven
The following comment has been added to this issue:
Author: Vincent Massol
Created: Sun, 13 Jun 2004 11:49 AM
Body:
Any progress Dominique? :-)
Thanks
-Vincent
-
View this comment:
http://jira.codehaus.org/brows
vmassol 2004/06/13 08:45:45
Modified:xdocsTag: MAVEN-1_0-BRANCH repository-upload.xml
Log:
Adding more information about the minimal elements required in artifact POMs
Revision ChangesPath
No revision
No revision
1.7.4.8 +11 -
The following comment has been added to this issue:
Author: Vincent Massol
Created: Sun, 13 Jun 2004 11:38 AM
Body:
Hi,
I'd prefer to have something more generic that would work for any issue tracker.
Instead I'm proposing the following:
1/ We only have a single attribute: "issu
The following comment has been added to this issue:
Author: Martijn Dashorst
Created: Sun, 13 Jun 2004 11:29 AM
Body:
I'm proposing the following syntax:
project.properties:
maven.changes.issue.template=%URL%?func=detail&group_id=54321&atid=%TRACKER%&aid=%ISSUE%
changes.xml:
Wron
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPCHANGES-9
Here is an overview of the issue:
-
Key
> For each version, I agree. But also for each artifact generated by the
> project, no?
>
> Imagine the aspectj jars. There are 2: aspectjrt.jar and
> aspectjtools.jar. We need 2 POMs, one for each, right?
Definitely. Simply in maven-land those are two projects so we need two poms.
Michal
--
On Sun, 2004-06-13 at 10:13, Vincent Massol wrote:
>
> ATM, I just want to help deploy artifacts to ibiblio. At the very least
> I need to understand the end format required on ibiblio so that I can
> mimic it manually.
Hokay.
--
jvz.
Jason van Zyl
[EMAIL PROTECTED]
http://maven.apache.org
h
On Sun, 2004-06-13 at 10:13, Vincent Massol wrote:
>
> > You need 3 poms (so 2 poms are needed for maven-jar-plugin)
> > You need to have a pom for each combinataion of a triple
> > (artifactId, groupId, version)
>
> For each version, I agree. But also for each artifact generated by the
> projec
> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> Sent: 13 June 2004 19:26
> To: Maven Developers List
> Subject: Re: More details required on new upload procedure
>
> On Sun, 2004-06-13 at 08:57, Vincent Massol wrote:
> > Hi,
> >
> > I'm in the process of uploading
> -Original Message-
> From: Michal Maczka [mailto:[EMAIL PROTECTED]
> Sent: 13 June 2004 19:22
> To: Maven Developers List
> Subject: RE: More details required on new upload procedure
>
>
> > >
> > > We need one POM per each version of the project but for upload
process
> > > it is san
On Sun, 2004-06-13 at 11:21, Vincent Massol wrote:
> > > 4/ Where is located the tool that will take an upload bundle
> > > (result of create-upload-bundle)? I'd like to see what
> > > operations it does so that I can deliver something equivalent
> > > or even better, use it...
> >
> > Don't know
On Sun, 2004-06-13 at 08:57, Vincent Massol wrote:
> Hi,
>
> I'm in the process of uploading the abbot jars on ibiblio. With the new
> procedure I also need to upload some POM (please note that the abbot
> build does not use maven). I've read
> http://maven.apache.org/repository-upload.html but I
> >
> > We need one POM per each version of the project but for upload process
> > it is sane to required a presence of the pom everytime even if it is
> > already in the repository.
>
> Are you sure? That's not exactly what's on ibiblio. In several places,
> there is one POM per artifact, which
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MAVEN-1320
Here is an overview of the issue:
-
Key:
> -Original Message-
> From: Michal Maczka [mailto:[EMAIL PROTECTED]
> Sent: 13 June 2004 19:04
> To: Maven Developers List
> Subject: Re: More details required on new upload procedure
>
> On Sun, 2004-06-13 at 14:57, Vincent Massol wrote:
> > Hi,
> >
> > I'm in the process of uploading
On Sun, 2004-06-13 at 14:57, Vincent Massol wrote:
> Hi,
>
> I'm in the process of uploading the abbot jars on ibiblio. With the new
> procedure I also need to upload some POM (please note that the abbot
> build does not use maven). I've read
> http://maven.apache.org/repository-upload.html but I
The following comment has been added to this issue:
Author: Lars Kühne
Created: Sun, 13 Jun 2004 9:29 AM
Body:
Yes, the HTML is probably correct and the old Konqueror version is buggy. My point is
that Maven should generate HTML that is at least readable in every browser.
The pro
+1
Eric
> -Original Message-
> From: Michal Maczka [mailto:[EMAIL PROTECTED]
> Sent: Sunday, June 13, 2004 2:22 PM
> To: Maven Developers List
> Subject: Re: [VOTE] release various plugins
>
>
> On Sun, 2004-06-13 at 06:43, Brett Porter wrote:
> > As mentioned, can we formalize the relea
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MAVENUPLOAD-137
Here is an overview of the issue:
-
On Sun, 2004-06-13 at 06:43, Brett Porter wrote:
> As mentioned, can we formalize the release of:
>
> clean, cruisecontrol, idea, javadoc,
> jcoverage, pmd, scm, test, xdoc
>
> to their next incarnation from CVS? Changes are in respective changes.xml files.
>
> +1 from me
>
> - Brett
>
+1
Mic
+1 for me.
Emmanuel
- Original Message -
From: "Brett Porter" <[EMAIL PROTECTED]>
To: "Maven Developers List" <[EMAIL PROTECTED]>; "Brett Porter"
<[EMAIL PROTECTED]>
Sent: Sunday, June 13, 2004 7:07 AM
Subject: Re: [VOTE] release various plugins
> Sorry, revised list for the vote (I ha
> -Original Message-
> From: Carlos Sanchez [mailto:[EMAIL PROTECTED]
> Sent: 13 June 2004 13:14
> To: 'Maven Developers List'
> Subject: RE: More details required on new upload procedure
>
> Hi Vincent,
>
> Hope it helps
>
I does, thanks. See below.
>
> > -Original Message-
+1
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: 13 June 2004 07:08
> To: Maven Developers List; Brett Porter
> Subject: Re: [VOTE] release various plugins
>
> Sorry, revised list for the vote (I have changed them to not download
> maven-1.0-rc2.jar)
>
> cha
Hi Vincent,
Hope it helps
> -Original Message-
> From: Vincent Massol [mailto:[EMAIL PROTECTED]
> Sent: Sunday, June 13, 2004 2:58 PM
> To: 'Maven Developers List'
> Subject: More details required on new upload procedure
>
> Hi,
>
> I'm in the process of uploading the abbot jars on i
vmassol 2004/06/13 04:06:53
Modified:abbotproject.properties
Log:
By default, do not run unit tests as they require a display and a display may not be
available on build server.
Revision ChangesPath
1.2 +4 -0 maven-plugins/abbot/project.properties
Ind
vmassol 2004/06/13 04:05:56
Modified:.Tag: MAVEN-1_0-BRANCH project.properties
Log:
re-added abbot to the plugin that are built as it should work fine now
Revision ChangesPath
No revision
No revision
1.51.2.28 +1 -1 mav
vmassol 2004/06/13 03:51:19
Modified:linkcheck project.xml
Log:
Added missing dependency on maven jelly tag (required for the unit tests)
Revision ChangesPath
1.49 +5 -1 maven-plugins/linkcheck/project.xml
Index: project.xml
==
The following comment has been added to this issue:
Author: Vincent Massol
Created: Sun, 13 Jun 2004 6:39 AM
Body:
I have uploaded both jars. Now waiting for more information on the POM that also has
to be uploaded.
-
My analysis is wrong of course... Sorry about that. I read too quickly.
The problem is with the maven jelly tag, not maven itself!
I guess it's simply missing a dependency in the linkcheck project. I'll
try adding it to see if it works.
-Vincent
> -Original Message-
> From: Vincent Masso
vmassol 2004/06/13 03:08:38
Modified:abbotproject.xml
Log:
mrj toolkit version is 1.0 (see
http://developer.apple.com/samplecode/MRJToolkitStubs/MRJToolkitStubs.html)
Revision ChangesPath
1.2 +1 -1 maven-plugins/abbot/project.xml
Index: project.xml
vmassol 2004/06/13 02:24:34
Modified:.Tag: MAVEN-1_0-BRANCH project.properties
Log:
Do not build the abbot plugin for now. There are still a few things to solve before
we can do that (uploading dependencies + possibly turning off the unit tests as they
may require a display
Hi,
I'm in the process of uploading the abbot jars on ibiblio. With the new
procedure I also need to upload some POM (please note that the abbot
build does not use maven). I've read
http://maven.apache.org/repository-upload.html but I still have a few
questions:
1/ Should there be a POM file per
Hello Vincent,
Actually there's also a problem with the abbot plugin :
http://jira.codehaus.org/browse/MPABBOT-1
Arnaud
> -Message d'origine-
> De : Vincent Massol [mailto:[EMAIL PROTECTED]
> Envoyé : dimanche 13 juin 2004 13:01
> À : 'Maven Developers List'
> Cc : 'Brett Porter'
> Obje
+1 for me.
Arnaud
> -Message d'origine-
> De : Brett Porter [mailto:[EMAIL PROTECTED]
> Envoyé : dimanche 13 juin 2004 07:08
> À : Maven Developers List; Brett Porter
> Objet : Re: [VOTE] release various plugins
>
> Sorry, revised list for the vote (I have changed them to not download
>
The following comment has been added to this issue:
Author: Emmanuel Boudrant
Created: Sun, 13 Jun 2004 4:51 AM
Body:
Is it possible to fix this before maven 1.0 final release ?
The only thing to do is replace the deploy/install goals by this (Am I wrong?) and
remove goal jar:sna
Hi,
I think aspectj-plugin should be released as it has been upgraded to AspectJ
1.2 and at least with the improvement in MPASPECTJ-10 (Use maxmem only when
fork=true to avoid aspectj warnings)
Thanks,
Carlos Sanchez
A Coruña, Spain
Oness Project
http://oness.sourceforge.net
> -Original M
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MAVENUPLOAD-136
Here is an overview of the issue:
-
I think it's due to the change brought recently by Brett with the jar
override for maven.jar. That would work *only* if you already have a
maven installed.
Thus when you build Maven (ant -f build-bootstrap.xml) it fails in the
linkcheck plugin:
Testsuite: org.apache.maven.linkcheck.LinkCheckTest
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPCLEAN-3
Here is an overview of the issue:
-
Key:
67 matches
Mail list logo
