Message:
The following issue has been closed.
Resolver: Carlos Sanchez
Date: Mon, 1 Nov 2004 2:09 PM
Read http://maven.apache.org/repository-upload.html
-
View the issue:
http://jira.codehaus.org/browse/MAVEN-1486
Message:
The following issue has been closed.
Resolver: Carlos Sanchez
Date: Mon, 1 Nov 2004 2:08 PM
Read http://maven.apache.org/repository-upload.html
-
View the issue:
http://jira.codehaus.org/browse/MAVEN-1485
The following issue has been updated:
Updater: fabrizio giustina (mailto:[EMAIL PROTECTED])
Date: Mon, 1 Nov 2004 1:14 PM
Comment:
cvs diff, including as usual:
- patch to plugin.jelly
- documentation (including changes.xml)
- updated unit test
Changes:
Attachment
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPDIST-15
Here is an overview of the issue:
-
Key:
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MAVEN-1486
Here is an overview of the issue:
-
Key:
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MAVEN-1485
Here is an overview of the issue:
-
Key:
Message:
The following issue has been closed.
Resolver: Vincent Massol
Date: Mon, 1 Nov 2004 10:24 AM
Done.
-
View the issue:
http://jira.codehaus.org/browse/MPANNOUNCEMENT-15
Here is an overview of the issue:
--
vmassol 2004/11/01 07:21:32
Modified:announcement/xdocs changes.xml
announcement/src/plugin-resources announcement.jsl
Log:
MPANNOUNCEMENT-15: Modified the announcement text "The ${pom.groupId} team is
pleased..." in favor of "We are pleased..." and changed the
signa
The following comment has been added to this issue:
Author: Shinobu Kawai
Created: Mon, 1 Nov 2004 10:07 AM
Body:
I like
1/ the use of ${pom.name}
better, but wouldn't complain if it were the other.
-
View this
The following comment has been added to this issue:
Author: Vincent Massol
Created: Mon, 1 Nov 2004 10:03 AM
Body:
Which one do you prefer:
1/ the use of ${pom.name}
or
2/ the use of "We are pleased..."
?
-
View t
The following comment has been added to this issue:
Author: Shinobu Kawai
Created: Mon, 1 Nov 2004 9:50 AM
Body:
Hey, that'll be perfect! :)
-
View this comment:
http://jira.codehaus.org/browse/MPANNOUNCEMENT-15
The following comment has been added to this issue:
Author: Vincent Massol
Created: Mon, 1 Nov 2004 9:31 AM
Body:
Thanks for the details. What would you think if we change the template to use
${pom.name} instead?
It would say: "The ${pom.name} team ..."
Or simply "We are pleased
I have no problem with this if someone using clover wants to do it.
There are also pretty clear instructions on how to use your own clover
jar with the plugin, so it should be easy for affected users to upgrade.
This is a non-blocker in my mind though.
- Brett
Fabrizio Giustina wrote:
Hi Brett
th
Hi Brett
there is actually an open issue for the clover plugin which prevents
it from working with a 1.5 jre:
http://jira.codehaus.org/browse/MPCLOVER-26
This is a clover bug that has been fixed in the actual release of
clover (1.3.2): what about updating the version of clover used by the
plugin an
vmassol 2004/11/01 01:26:00
Modified:announcement/xdocs changes.xml properties.xml
announcement/src/plugin-resources announcement.jsl
announcement plugin.jelly plugin.properties
Log:
Added new maven.announcement.repo.remote property and refactored existi
I've done a full search in all maven-plugins and I couldn't find it.
However, I've found that I had already added a
maven.announcement.distributionUrl property which defaults to
${maven.repo.remote}/${pom.groupId}/plugins
That's what I was referring to.
I'll refactor it.
That said, I had also a
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: lundi 1 novembre 2004 09:40
> To: Maven Developers List
> Subject: Re: cvs commit: maven-plugins/announcement/xdocs changes.xml
>
>
> >Unfortunately, there's currently no information in the POM that says
> where
brett 2004/11/01 01:04:21
Modified:.Tag: MAVEN-1_0-BRANCH project.properties
xdocsTag: MAVEN-1_0-BRANCH navigation.xml
Log:
temporarily add ApacheCon logo to the site
Revision ChangesPath
No revision
No re
Unfortunately, there's currently no information in the POM that says where
the artifact can be downloaded from (kind of a but with
the external URL). BTW, that could be something useful to add to m2 as it is
useful for several plugins (multichanges, announcement, etc).
I'm pretty sure it is al
19 matches
Mail list logo
