Tim,
did anything ever come of this?
- Brett
Tim O'Brien wrote:
Brett,
Sure will do, I think a JIRA task wouldn't do this justice. I'm working on
a mockup in Adobe Illustrator ;-)
On 3/9/06, Brett Porter <[EMAIL PROTECTED]> wrote:
Tim,
There's plenty of points here and on your blog. Can y
Done
http://jira.codehaus.org/browse/MNG-2143
Raphaël
Brett Porter a écrit :
Cool. I think this is a good idea.
In my original proposal:
"* The documentation is a big list of links. I think we should categorise
them by topic instead of type, or perhaps as Jesse suggests we should
have a cross
Brett,
Sure will do, I think a JIRA task wouldn't do this justice. I'm working on
a mockup in Adobe Illustrator ;-)
On 3/9/06, Brett Porter <[EMAIL PROTECTED]> wrote:
>
> Tim,
>
> There's plenty of points here and on your blog. Can you please put this
> in a proposal form for how to make specifi
On 3/9/06, Brett Porter <[EMAIL PROTECTED]> wrote:
> Tim O'Brien wrote:
> > I read your response, clicked on the Geronimo site, and wanted to
> believe
> > that that was possible with Maven. But, if you look at
> > https://svn.apache.org/repos/asf/geronimo/site/
> >
> > It's either Maven 1.x or
I'm sorry,
I don't know what to say to the jira issue
As you know i'm a bit new to open source processes.
I never released the freeform plugin because i don't know how.
Regards,
Raphaël
2006/3/10, Brett Porter <[EMAIL PROTECTED]>:
>
> Cool. I think this is a good idea.
>
> In my original propos
Cool. I think this is a good idea.
In my original proposal:
"* The documentation is a big list of links. I think we should categorise
them by topic instead of type, or perhaps as Jesse suggests we should
have a cross reference/index - so we could have a page that lists all
the howtos and guides, t
It aims to be a page or a couple of pages.
I don't have clear idea on it.
yesterday i wrote it in two pages : a main page with sample doco and an
advanced page with an exhautive doco (not in my sample be should be)
But i think it is not a navigation.
Raphaël
2006/3/10, Brett Porter <[EMAIL PRO
Thanks for attempting this.
IS this intended to be a navigation, a page, a series of pages? I'm a
little confused.
Do you have any feedback on my original proposal on this thread? It
tried to examine many of the same problems.
- Brett
Raphaël Piéroni wrote:
> Hi,
>
> So here is a cleaner propo
Tim O'Brien wrote:
> And again, I think that the "Maven site" should be a lot more like a
> community site that aggregates blogs, lists articles, news items. In the
> absence of a runtime container uses some Javscript to display RSS feeds of
> the last 10 user posts.
I don't know about making the
Tim O'Brien wrote:
> I read your response, clicked on the Geronimo site, and wanted to believe
> that that was possible with Maven. But, if you look at
> https://svn.apache.org/repos/asf/geronimo/site/
>
> It's either Maven 1.x or Ant the directory contains a v3 POM, but it also
> contains an .
Brian K. Wallace wrote:
> Then there's the content debate... "Getting Started" with Maven goes on
> _forever_. To get started?!? And that's entirely outside the scope of
> the documentation link (which doesn't quite go on forever - just links
> forever). And the first link on documentation? Getting
Tim,
There's plenty of points here and on your blog. Can you please put this
in a proposal form for how to make specific improvements. ie, for
everything that you think is wrong, say how you'd make it right, in
point form so each can be specifically addressed and turned into jira
tasks.
- Brett
Tim O'Brien wrote:
> Something to think about is maybe not having the initial Maven page be a
> Maven site. ASF sites in general seems to be more Developer focused than
> user focused. What if the initial Maven site were more like the front pages
> of Mozilla or Rails. An attractive logo, links
Please review:
http://mail-archives.apache.org/mod_mbox/maven-dev/200602.mbox/[EMAIL PROTECTED]
And provide feedback.
Closely related to:
http://mail-archives.apache.org/mod_mbox/maven-dev/200602.mbox/[EMAIL PROTECTED]
These have been kicking around since early January and I haven't
received fee
On 3/9/06, John Casey <[EMAIL PROTECTED]> wrote:
>
>
>
> I agree with you on that point. My point was that physical separation of
> the websites might not be appropriate or necessary, since IMO every ASF
> project that releases a product (not an API) should apply this advice,
> and therefore shou
of things
that would help a user to use the product.
Maybe I should just shut up and write the
maven-end-user-site plugin? But, it's one reason why I didn't get too
exctied about contributing to the site last year. I don't think another 100
APT documents are the right di
Hi,
So here is a cleaner proposition for the site.
This proposition is focused on the documentation for the user.
I assume the user is a java developer but may not be a maven developer.
What do a developer (and maven user) want to know:
- where to find the software,
- how to install it,
- how to
missing :
Languages
-guides
- plugins (c#, aspectj)
Deployment
- guides
- plugins (jboss, tomcat)
Test
- guides
- plugins (surefire, cargo)
Continuous integration
- guides
Packaging
- guides
- plugins
and also some doco that do not fit into the guide/plugins separation like
getting started,
Hi,
what about this kind of cutting :
Reports
- guides
- plugins (jxr, javancss, ...)
Archetypes
- guides
- plugins (quickstart,...)
Generators
- guides
- plugins (modello, torque, ...)
IDE
- guides
- plugins
Associated artifacts
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It uses anakia to transform, but in true Maven spirit it should be able
to be done - with a plugin. ;-) And maybe maven-site is suited to it
just fine (not a maven-site expert for user sites AT ALL - I'm with
Jesse here that so much more 'whiz-bang' is
On 3/9/06, Brian K. Wallace <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Jesse Kuhnert wrote:
> > I think what everyone is saying sounds more or less correct, but what is
> the
> > solution then?
> >
> > If they can't rely on a runtime container to host the site
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jesse Kuhnert wrote:
> I think what everyone is saying sounds more or less correct, but what is the
> solution then?
>
> If they can't rely on a runtime container to host the site, options become
> MUCH more limited.
>
> Complaints about the UI are f
her good one, click on a Guide, then click on the banner
> logo.
> > That links back to /guide, click on the same banner logo, that links
> back to
> > the home page. The Maven site is full of these inconsistencies, and
> it's
> > not something that people can
ches. IMO, the site plugin
> needs serious rework. It doesn't create good web sites, especially
> for multi-projects.
>
> I guess I've just pissed off the Maven development team by telling all of
> you that Maven doesn't do a good job of creating web sites for
> u
es for
users. There, I said it. Maven creates so-so web sites for developers, but
doesn't do a good job creating web sites for end-users. Maybe that was
never the goal. Maybe I should just shut up and write the
maven-end-user-site plugin? But, it's one reason why I didn't get t
That separates the core site, but there is still a two issues, and,
unfortunately, I'm not sure if there is an easy way to address it.
First, it is easy to publish specific versions of projects to different
directories. But, the Maven documentation consists of a bunch of related
sites. I think t
Good to see discussion on this. I'll choose more controversial topics
next time, because I've already discussed this with myself at length on
this list.
As I've said recently, I'm just waiting for 2.0.3 to my plan into action.
- Brett
Tim O'Brien wrote:
> Having to choose between publishing the
We already have that in place for the core, the site url is
maven.apache.org/ref/${project.version}/
see
http://svn.apache.org/viewcvs.cgi/maven/components/trunk/pom.xml?rev=382904&view=markup
We're missing the continuous integration part to auto deploy site
everytime it's changed
On 3/8/06, Tim
Comments inline.
-john
Tim O'Brien wrote:
Sorry, gmail confused me and I sent that last one by mistake John.
I don't think you'll be trading look and feel here. I think you'd just be
doing something like making the site.xml for trunk point to a logo or banner
GIF that just added a "trunk", "d
2006/3/8, Arnaud HERITIER <[EMAIL PROTECTED]>:
>
> The problem will be also with reports.
> Do we need all reports for all releases ?
> Documentation reports like javadoc, jxr, are needed for each release.
> But is it useful for quality reports (pmd, simian, linkcheck, ...) ? These
> reports are us
The problem will be also with reports.
Do we need all reports for all releases ?
Documentation reports like javadoc, jxr, are needed for each release.
But is it useful for quality reports (pmd, simian, linkcheck, ...) ? These
reports are useful for the development team to improve their code. But fo
Sorry, gmail confused me and I sent that last one by mistake John.
I don't think you'll be trading look and feel here. I think you'd just be
doing something like making the site.xml for trunk point to a logo or banner
GIF that just added a "trunk", "draft", or "development" stamp. If this was
do
Right, I think confusion is a good word. I approach Maven as an end-user
most often, and if I need to dive into a plugin source to finally figure out
how it works I do. But, I've had the displeasure of
On 3/8/06, John Casey <[EMAIL PROTECTED]> wrote:
>
> +1
>
> Maybe we can put a banner at the t
+1
Maybe we can put a banner at the top of each page that marks the version
it refers to or something. If we styled the reference doco as a manual,
it could be part of the page layout that ties it together. I'd be
willing to trade a bit of the look&feel for that sort of information, as
it see
I think that's a good idea. In m1 we are already using the
maven.site.stage.address property to publish sites more frequently to
our personal pages (eg [1]) and I refer people to this site
occasionally. This has the obvious drawback that the
'latest-and-greatest' docs for different plugins are
Having to choose between publishing the latest and greatest docs and only
the released version is a problem that Maven seems to have created for
itself. Same issue comes up in other projects frequently - Commons has a
problem because some of the sites only publish on a release. Latest and
greates
, March 07, 2006 9:01 PM
To: Maven Developers List
Subject: Re: Making the current web site suck less
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wendy Smoak wrote:
> On 3/7/06, Brett Porter <[EMAIL PROTECTED]> wrote:
>
>> * I'm still a little torn on where plugin do
that becomes an epic adventure, close to none of the methods/classes
have a usable javadoc (most have none). the same applies to plugin
parameters, I always go to the plugin doc first, but then realize it's
useless and try finding stuff in the other site documentation. Also
please consider removing
They are already there
http://maven.apache.org/ref/current/index.html
Note the new Reference link in the left menu
On 3/7/06, Rinku <[EMAIL PROTECTED]> wrote:
> Since we talk about 'latest and greatest', I wonder why javadocs
> published online cannot serve as 'latest and greatest' docs?
>
> I am
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wendy Smoak wrote:
> On 3/7/06, Brian K. Wallace <[EMAIL PROTECTED]> wrote:
>
>> While I agree that it would be nice to have the 'latest and greatest'
>> docs on the main site, I don't believe having them as the only
>> documentation is a good idea at
On 3/7/06, Brian K. Wallace <[EMAIL PROTECTED]> wrote:
> While I agree that it would be nice to have the 'latest and greatest'
> docs on the main site, I don't believe having them as the only
> documentation is a good idea at all. The documentation should be able to
> evolve after a release to mak
Since we talk about 'latest and greatest', I wonder why javadocs
published online cannot serve as 'latest and greatest' docs?
I am +1 to Carlos' idea about documenting almost all methods. If we were
to publish API docs for Maven and Plugins on the website (some separate
URL) with every Maven r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wendy Smoak wrote:
> On 3/7/06, Brett Porter <[EMAIL PROTECTED]> wrote:
>
>> * I'm still a little torn on where plugin docs go. No hurry on this, but
>> something to ponder. We definitely need to make the references for those
>> integrate better. Site
On 3/7/06, Brett Porter <[EMAIL PROTECTED]> wrote:
> * I'm still a little torn on where plugin docs go. No hurry on this, but
> something to ponder. We definitely need to make the references for those
> integrate better. Site/skin inheritance will help
No matter where they go, I think they need t
Ok, something more practical right now. I'd meant to bring it up at the
same time as my other mail, but thanks to Jesse for reminding me.
I'm embarrassed to say that the front page looks a whole lot like the
one I created about this time last year for 2.0 alpha 1. I think it
needs an update. IMO,
45 matches
Mail list logo
