Wendy Smoak wrote:
On 10/4/07, Brian E. Fox <[EMAIL PROTECTED]> wrote:
From: Wendy Smoak [mailto:[EMAIL PROTECTED]
There is now (in v9) some config in the plugin parent for staging
sites under maven-whatever-plugin-x.y-SNAPSHOT and I would like to get
that trend started for plugin docs.
Or at
I'd like having the version number added. I don't usually know (or
keep track of) when something gets released. And it's not always
obvious that I'm reading a new feature... and we don't want to stop
eager people in contributing documentation ALONG with their code
patches right? :-)
On 12/8/06,
me good old fashioned web pages as
> the front
> door and then link to the maven generated content from there.
>
> Just my 0.02 worth
>
> Ps. We do intend visiting the core sometime soon to extend the current
> scheme to support full POM identity representation in the and
>
sage-
From: Franz Allan Valencia See [mailto:[EMAIL PROTECTED]
Sent: 07 November 2006 13:26
To: Maven Developers List
Subject: Re: Publishing plugin sites
On 11/6/06, Brett Porter <[EMAIL PROTECTED]> wrote:
Also, maybe the @since tags should be documented as well in [1]?
Yes, but
On 12/8/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
Just a reminder and in case it needs more discussion: we are now
publishing the latest plugin docs from svn, and not waiting for a
release to do it.
Can't we add the version of the plugin matching the status of the
documentation? Even if we h
On 11/6/06, Brett Porter <[EMAIL PROTECTED]> wrote:
Well, its up for discussion. I don't like the idea of having separate
docs per release, since some aspects of docs are updated independent
of version. So, we added the @since flag to mojos and parameters so
that you have an accurate reference f
On 11/8/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
Can someone look at maven-plugin-plugin? I changed its parent to
4-SNAPSHOT locally to get the upload to work, but the header on the
site is wrong.
http://maven.apache.org/plugins/maven-plugin-plugin/
Done: http://jira.codehaus.org/browse/
On 11/8/06, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
One this to think about now is what we should do with old files on the
plugin sites.
...
Should such files be manually deleted from minotaur, to avoid confusion
for the users?
Yes, otherwise they'll keep showing up in web searches.
Do
Wendy Smoak wrote:
On 11/8/06, Vincent Siveton <[EMAIL PROTECTED]> wrote:
It seems that some plugins have not been published yet:
compiler, eclipse, help, jxr, one
Sorry, I must have missed some errors scanning the log file. I needed
to build a few things in shared to get them to work, but no
On 11/8/06, Vincent Siveton <[EMAIL PROTECTED]> wrote:
It seems that some plugins have not been published yet:
compiler, eclipse, help, jxr, one
Sorry, I must have missed some errors scanning the log file. I needed
to build a few things in shared to get them to work, but now those
four are pub
It seems that some plugins have not been published yet:
compiler, eclipse, help, jxr, one
Cheers,
Vincent
2006/11/8, Vincent Siveton <[EMAIL PROTECTED]>:
Thanks a lot Wendy for this!
Vincent
2006/11/8, Wendy Smoak <[EMAIL PROTECTED]>:
> On 11/7/06, Brett Porter <[EMAIL PROTECTED]> wrote:
>
>
Thanks a lot Wendy for this!
Vincent
2006/11/8, Wendy Smoak <[EMAIL PROTECTED]>:
On 11/7/06, Brett Porter <[EMAIL PROTECTED]> wrote:
> Since we still have the problem of circular dependencies in there
> (plugins use the javadoc and other reports, so it can't figure out
> the right order to bui
On 11/7/06, Brett Porter <[EMAIL PROTECTED]> wrote:
Since we still have the problem of circular dependencies in there
(plugins use the javadoc and other reports, so it can't figure out
the right order to build), you can't use the parent to run from, but
you can probably do:
mvn -r '*/pom.xml' si
On 08/11/2006, at 11:27 AM, Wendy Smoak wrote:
On 11/7/06, Brett Porter <[EMAIL PROTECTED]> wrote:
I think the addition of new documentation outweighs the problems
we'll see from snapshot features, but we should mark them up as we
[see] them.
I agree. So, who would like to do do the honors
On 11/7/06, Brett Porter <[EMAIL PROTECTED]> wrote:
I think the addition of new documentation outweighs the problems
we'll see from snapshot features, but we should mark them up as we
[see] them.
I agree. So, who would like to do do the honors and publish the
updated plugin sites?
I'm happy
sage-
From: Franz Allan Valencia See [mailto:[EMAIL PROTECTED]
Sent: 07 November 2006 13:26
To: Maven Developers List
Subject: Re: Publishing plugin sites
On 11/6/06, Brett Porter <[EMAIL PROTECTED]> wrote:
> >
> > Also, maybe the @since tags should be documented as well in [1]?
&
On 11/6/06, Brett Porter <[EMAIL PROTECTED]> wrote:
>
> Also, maybe the @since tags should be documented as well in [1]?
Yes, but isn't this also included in the Maven site somewhere?
hhmm..never seen it in maven2 site. but i've seen some goals
documentation in maven-1.x with the 'since' colu
On 07/11/2006, at 4:50 PM, Franz Allan Valencia See wrote:
So the priority now for the maven plugins docs is to mark them up with
@since tags? If im not mistaken, most (if not all) of those docs do
not have the since tags.
It should only be necessary as new features are added.
And if we're
On 11/6/06, Brett Porter <[EMAIL PROTECTED]> wrote:
On 07/11/2006, at 3:33 PM, Wendy Smoak wrote:
> On 11/6/06, Franz Allan Valencia See <[EMAIL PROTECTED]> wrote:
>
>> I don't think the new plugin docus can be published yet until the
>> plugins themselves are released. Those docus were based o
On 07/11/2006, at 3:33 PM, Wendy Smoak wrote:
On 11/6/06, Franz Allan Valencia See <[EMAIL PROTECTED]> wrote:
I don't think the new plugin docus can be published yet until the
plugins themselves are released. Those docus were based on the
snapshot versions and some information they contain ma
On 11/6/06, Franz Allan Valencia See <[EMAIL PROTECTED]> wrote:
I don't think the new plugin docus can be published yet until the
plugins themselves are released. Those docus were based on the
snapshot versions and some information they contain may not be
applicable to the currently released ver
On 11/6/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
On 11/6/06, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
> Please, let's all help to keep this list up to date, until all plugin
> sites have been published.
Brett posted earlier that he fixed the navigation inheritance problem.
Is there anythin
On 11/6/06, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
Please, let's all help to keep this list up to date, until all plugin
sites have been published.
Brett posted earlier that he fixed the navigation inheritance problem.
Is there anything else preventing us from publishing all of the
plugin
On 11/6/06, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
Dennis Lundberg wrote:
> Wendy Smoak wrote:
>> Are all the plugin websites up to date with svn, or is the policy
>> still to only publish them when a release is done?
>>
>> Thanks,
>
> The published plugin sites are unfortunately not in sync
Dennis Lundberg wrote:
Wendy Smoak wrote:
Are all the plugin websites up to date with svn, or is the policy
still to only publish them when a release is done?
Thanks,
The published plugin sites are unfortunately not in sync with what is in
svn. The published docs should reflect the current r
Well, its up for discussion. I don't like the idea of having separate
docs per release, since some aspects of docs are updated independent
of version. So, we added the @since flag to mojos and parameters so
that you have an accurate reference for all versions. WRT the docs on
the site, it's
On 11/6/06, Brett Porter <[EMAIL PROTECTED]> wrote:
They are currently at releases. We are now in a position (with
@since), to publish all the time, and I've lined them all up, but it
is currently blocked by a bug in the navigation link generation.
So is the plan to keep all the plugin sites up
They are currently at releases. We are now in a position (with
@since), to publish all the time, and I've lined them all up, but it
is currently blocked by a bug in the navigation link generation.
On 07/11/2006, at 6:00 AM, Wendy Smoak wrote:
Are all the plugin websites up to date with svn,
Is it possible to use versioning on the site? So you can select the
site/documentation for a specific
version of the plugin?
For instance: http://ws.apache.org/jaxme/, on the left there's Documentation
per version.
Something like that would be nice for the plugins.
-- Kenney
Dennis Lundberg w
Wendy Smoak wrote:
Are all the plugin websites up to date with svn, or is the policy
still to only publish them when a release is done?
Thanks,
The published plugin sites are unfortunately not in sync with what is in
svn. The published docs should reflect the current release of the
plugin. T
30 matches
Mail list logo
