I consider 2.3 totally and horribly broken, thus it is urgent to get 2.4
out asap. After that we can move to 2.5 as soon as someone has time to
apply the patches, test and release.
-Original Message-
From: Benjamin Bentmann [mailto:[EMAIL PROTECTED]
Sent: Saturday, March 08, 2008 5:52 PM
[MJAVADOC-154] - Bump to plexus-utils:1.4.6
Hm, this task is linked to an issue about a defect in BourneShell. Another
BourneShell defect has been fixed in PLXUTILS-54 for plexus-utils:1.4.9.
Maybe worth to update once again to latest version?
Also, maven-javadoc-plugin:2.4 is known to ignore g
It's time to release the next Javadoc plugin. Besides the fixes listed
below, the most important change is the reverting of javadoc acting as
an aggregator. This caused most users tons of grief during releases. The
issue for this is MJAVADOC-137 (reverted MJAVADOC-104)
The plugin is staged at:
I'm on it.
-Original Message-
From: Wendy Smoak [mailto:[EMAIL PROTECTED]
Sent: Saturday, March 08, 2008 12:49 PM
To: Maven Developers List
Subject: Re: Javadoc plugin
On Sat, Mar 8, 2008 at 9:06 AM, Wendy Smoak <[EMAIL PROTECTED]> wrote:
> Thanks, Brett. I'm trying it now on Leopard
Hi,
5) Reading and Writing Text Files
Textual content is composed of characters while file systems merely store
byte streams. A file encoding (aka charset) is used to convert between bytes
and characters. The challenge is using the right file encoding...
The JVM has this notion of a default enc
On Sat, Mar 8, 2008 at 9:06 AM, Wendy Smoak <[EMAIL PROTECTED]> wrote:
> Thanks, Brett. I'm trying it now on Leopard with this workaround.
Vincent and/or Brian, it's all yours! (No luck with Brett's
workaround or my attempts to further edit the command line.)
--
Wendy
--
I think I've been misunderstood. I am referring to the
element that can contain whatever is necessary for configuration.
Oh, I see, but...
If the site is generated through a plugin, then by all means, configure
the plugin.
... this issue is about site deployment, not site generation. And th
Hi,
Yes. The Jira projects will be:
* plugintools: MPLUGIN (or MPA-107 if someone think it will be better)
* testingtools: see MPA-110
Cheers,
Vincent
2008/3/8, Brian E. Fox <[EMAIL PROTECTED]>:
> Just so we're clear, each of these trees will have a single jira project
> (with each child as a
On Fri, Mar 7, 2008 at 10:51 PM, Brett Porter <[EMAIL PROTECTED]> wrote:
> This is how I worked around the Leopard things until the release
> plugin allows you to turn off --non-interactive:
>
>
> http://blogs.exist.com/bporter/2008/02/25/working-around-non-interactive-problems-in-leopards-sub
Just so we're clear, each of these trees will have a single jira project
(with each child as a component) and they will be released together as a
unit?
With that clarification, +1
-Original Message-
From: Vincent Siveton [mailto:[EMAIL PROTECTED]
Sent: Saturday, March 08, 2008 10:25 AM
T
Cool, I can be the backup if you have trouble.
-Original Message-
From: Vincent Siveton [mailto:[EMAIL PROTECTED]
Sent: Saturday, March 08, 2008 9:29 AM
To: Maven Developers List
Subject: Re: Javadoc plugin
Hi Benjamin,
No problem.
BTW I will try to get the release out this week end.
C
Hi,
According recent threads on plugin-tools, I propose to:
* create a new SCM entry for maven/plugin-testing which will include
maven-plugin-testing-harness, maven-plugin-testing-tools and
maven-test-tools
* created a new groupId for them, ie org.apache.maven.plugin.testingtools
* created a new g
I think I've been misunderstood. I am referring to the
element that can contain whatever is necessary for configuration. If the
site is generated through a plugin, then by all means, configure the plugin.
See my first response.
Paul
On Sat, Mar 8, 2008 at 3:05 AM, Benjamin Bentmann <[EMAIL PROTE
Hi Benjamin,
No problem.
BTW I will try to get the release out this week end.
Cheers,
Vincent
2008/3/8, Benjamin Bentmann <[EMAIL PROTECTED]>:
>
> > I'm not having any luck staging the Javadoc plugin for a 2.4 release
>
>
> I just added a patch for MJAVADOC-162 which was originally planned for
> I'm not having any luck staging the Javadoc plugin for a 2.4 release
I just added a patch for MJAVADOC-162 which was originally planned for this
release. If it's not too late, it would be cool to see it applied.
Benjamin
--
View this message in context:
http://www.nabble.com/Javadoc-plugin
Why does the configuration option require a bump in version?
The primary place for configurations regarding the build is the POM. A
new option means a change to the POM schema, a new schema means to bump the
version.
it is a perfect fit for 2.0.x as well.
Besides, you proposed to break the c
16 matches
Mail list logo