[jira] Updated: (MAVEN-125) Documentation enhancements

2004-11-20 Thread jira
The following issue has been updated:

Updater: Brett Porter (mailto:[EMAIL PROTECTED])
   Date: Sat, 20 Nov 2004 6:14 PM
Changes:
 Fix Version changed to 1.0.2
 Fix Version changed from 1.1
-
For a full history of the issue, see:

  http://jira.codehaus.org/browse/MAVEN-125?page=history

-
View the issue:
  http://jira.codehaus.org/browse/MAVEN-125

Here is an overview of the issue:
-
Key: MAVEN-125
Summary: Documentation enhancements
   Type: Improvement

 Status: Open
   Priority: Minor

 Original Estimate: 1 week
 Time Spent: Unknown
  Remaining: 1 week

Project: maven
 Components: 
 documentation
   Fix Fors:
 1.0.2

   Assignee: Brett Porter
   Reporter: dion gillard

Created: Tue, 1 Oct 2002 10:44 PM
Updated: Sat, 20 Nov 2004 6:14 PM

Description:
Ok,
Here are some changes I would recommend (as dIon asked for it ;-):
1) Change the welcome page to have direct links to gettting started. This is
what I want to see when I visit the front page
2) The user guide should have information from the download and install
sections to make it a more complete user's guide
3) getting started and user's guide should possibly be rethought into user's
guide and developer's guide.
4) The plug-ins should be split into core and additional (or optional)
5) Someone who has written a plug-in should write a plug-in development
howto and integrate that with the developer's guide.
6) Plug-ins should be described on the listing page
7) In the user's guide it would be nice to have a link to an example
maven.xml file

Let me know what you guys think, when I get a chance to look at it further I
may have some further suggestions (and maybe patches ;-).

-warner

+warner onstine+



-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[jira] Updated: (MAVEN-125) Documentation enhancements

2004-12-03 Thread jira
The following issue has been updated:

Updater: Brett Porter (mailto:[EMAIL PROTECTED])
   Date: Fri, 3 Dec 2004 4:16 PM
Changes:
 Fix Version changed to 1.1-beta-1
 Fix Version changed from 1.0.2
-
For a full history of the issue, see:

  http://jira.codehaus.org/browse/MAVEN-125?page=history

-
View the issue:
  http://jira.codehaus.org/browse/MAVEN-125

Here is an overview of the issue:
-
Key: MAVEN-125
Summary: Documentation enhancements
   Type: Improvement

 Status: Open
   Priority: Minor

 Original Estimate: 1 week
 Time Spent: Unknown
  Remaining: 1 week

Project: maven
 Components: 
 documentation
   Fix Fors:
 1.1-beta-1

   Assignee: Brett Porter
   Reporter: dion gillard

Created: Tue, 1 Oct 2002 10:44 PM
Updated: Fri, 3 Dec 2004 4:16 PM

Description:
Ok,
Here are some changes I would recommend (as dIon asked for it ;-):
1) Change the welcome page to have direct links to gettting started. This is
what I want to see when I visit the front page
2) The user guide should have information from the download and install
sections to make it a more complete user's guide
3) getting started and user's guide should possibly be rethought into user's
guide and developer's guide.
4) The plug-ins should be split into core and additional (or optional)
5) Someone who has written a plug-in should write a plug-in development
howto and integrate that with the developer's guide.
6) Plug-ins should be described on the listing page
7) In the user's guide it would be nice to have a link to an example
maven.xml file

Let me know what you guys think, when I get a chance to look at it further I
may have some further suggestions (and maybe patches ;-).

-warner

+warner onstine+



-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[jira] Updated: (MAVEN-125) Documentation enhancements

2003-08-03 Thread jira
The following issue has been updated:

Updater: dion gillard (mailto:[EMAIL PROTECTED])
   Date: Sun, 3 Aug 2003 11:33 PM
Changes:
 environment changed to 
 Fix Version changed to 1.1
-
For a full history of the issue, see:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-125&page=history

-
View the issue:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-125


Here is an overview of the issue:
-
Key: MAVEN-125
Summary: Documentation enhancements
   Type: Improvement

 Status: Assigned
   Priority: Minor

 Time Spent: Unknown
  Remaining: 1 week

Project: maven
   Fix Fors:
 1.1

   Assignee: dion gillard
   Reporter: dion gillard

Created: Tue, 1 Oct 2002 10:44 PM
Updated: Sun, 3 Aug 2003 11:33 PM

Description:
Ok,
Here are some changes I would recommend (as dIon asked for it ;-):
1) Change the welcome page to have direct links to gettting started. This is
what I want to see when I visit the front page
2) The user guide should have information from the download and install
sections to make it a more complete user's guide
3) getting started and user's guide should possibly be rethought into user's
guide and developer's guide.
4) The plug-ins should be split into core and additional (or optional)
5) Someone who has written a plug-in should write a plug-in development
howto and integrate that with the developer's guide.
6) Plug-ins should be described on the listing page
7) In the user's guide it would be nice to have a link to an example
maven.xml file

Let me know what you guys think, when I get a chance to look at it further I
may have some further suggestions (and maybe patches ;-).

-warner

+warner onstine+



-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[jira] Updated: (MAVEN-125) Documentation enhancements

2003-12-02 Thread jira
The following issue has been updated:

Updater: Jason van Zyl (mailto:[EMAIL PROTECTED])
   Date: Tue, 2 Dec 2003 4:14 PM
Changes:
 environment changed to 
 Component changed to documentation
-
For a full history of the issue, see:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-125&page=history

-
View the issue:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-125


Here is an overview of the issue:
-
Key: MAVEN-125
Summary: Documentation enhancements
   Type: Improvement

 Status: Open
   Priority: Minor

 Original Estimate: 1 week
 Time Spent: Unknown
  Remaining: 1 week

Project: maven
 Components: 
 documentation
   Fix Fors:
 1.1

   Assignee: dion gillard
   Reporter: dion gillard

Created: Tue, 1 Oct 2002 10:44 PM
Updated: Tue, 2 Dec 2003 4:14 PM

Description:
Ok,
Here are some changes I would recommend (as dIon asked for it ;-):
1) Change the welcome page to have direct links to gettting started. This is
what I want to see when I visit the front page
2) The user guide should have information from the download and install
sections to make it a more complete user's guide
3) getting started and user's guide should possibly be rethought into user's
guide and developer's guide.
4) The plug-ins should be split into core and additional (or optional)
5) Someone who has written a plug-in should write a plug-in development
howto and integrate that with the developer's guide.
6) Plug-ins should be described on the listing page
7) In the user's guide it would be nice to have a link to an example
maven.xml file

Let me know what you guys think, when I get a chance to look at it further I
may have some further suggestions (and maybe patches ;-).

-warner

+warner onstine+



-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[jira] Updated: (MAVEN-125) Documentation enhancements

2004-04-20 Thread jira
The following issue has been updated:

Updater: Brett Porter (mailto:[EMAIL PROTECTED])
   Date: Tue, 20 Apr 2004 9:12 PM
Changes:
 assignee changed to Brett Porter
 environment changed to 
 Fix Version changed to 1.0
 Fix Version changed from 1.1
-
For a full history of the issue, see:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-125&page=history

-
View the issue:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-125

Here is an overview of the issue:
-
Key: MAVEN-125
Summary: Documentation enhancements
   Type: Improvement

 Status: Open
   Priority: Minor

 Original Estimate: 1 week
 Time Spent: Unknown
  Remaining: 1 week

Project: maven
 Components: 
 documentation
   Fix Fors:
 1.0

   Assignee: Brett Porter
   Reporter: dion gillard

Created: Tue, 1 Oct 2002 10:44 PM
Updated: Tue, 20 Apr 2004 9:12 PM

Description:
Ok,
Here are some changes I would recommend (as dIon asked for it ;-):
1) Change the welcome page to have direct links to gettting started. This is
what I want to see when I visit the front page
2) The user guide should have information from the download and install
sections to make it a more complete user's guide
3) getting started and user's guide should possibly be rethought into user's
guide and developer's guide.
4) The plug-ins should be split into core and additional (or optional)
5) Someone who has written a plug-in should write a plug-in development
howto and integrate that with the developer's guide.
6) Plug-ins should be described on the listing page
7) In the user's guide it would be nice to have a link to an example
maven.xml file

Let me know what you guys think, when I get a chance to look at it further I
may have some further suggestions (and maybe patches ;-).

-warner

+warner onstine+



-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[jira] Updated: (MAVEN-125) Documentation enhancements

2005-12-05 Thread Brett Porter (JIRA)
 [ http://jira.codehaus.org/browse/MAVEN-125?page=all ]

Brett Porter updated MAVEN-125:
---

Assign To: (was: Brett Porter)

> Documentation enhancements
> --
>
>  Key: MAVEN-125
>  URL: http://jira.codehaus.org/browse/MAVEN-125
>  Project: Maven
> Type: Improvement
>   Components: documentation
> Reporter: dion gillard
> Priority: Minor
>  Fix For: 1.1-rc1

>
>
> Ok,
> Here are some changes I would recommend (as dIon asked for it ;-):
> 1) Change the welcome page to have direct links to gettting started. This is
> what I want to see when I visit the front page
> 2) The user guide should have information from the download and install
> sections to make it a more complete user's guide
> 3) getting started and user's guide should possibly be rethought into user's
> guide and developer's guide.
> 4) The plug-ins should be split into core and additional (or optional)
> 5) Someone who has written a plug-in should write a plug-in development
> howto and integrate that with the developer's guide.
> 6) Plug-ins should be described on the listing page
> 7) In the user's guide it would be nice to have a link to an example
> maven.xml file
> Let me know what you guys think, when I get a chance to look at it further I
> may have some further suggestions (and maybe patches ;-).
> -warner
> +warner onstine+

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[jira] Updated: (MAVEN-125) Documentation enhancements

2005-05-16 Thread Brett Porter (JIRA)
 [ http://jira.codehaus.org/browse/MAVEN-125?page=all ]

Brett Porter updated MAVEN-125:
---

Fix Version: (was: 1.1-beta-1)
 1.1-beta-2

> Documentation enhancements
> --
>
>  Key: MAVEN-125
>  URL: http://jira.codehaus.org/browse/MAVEN-125
>  Project: maven
> Type: Improvement
>   Components: documentation
> Reporter: dion gillard
> Assignee: Brett Porter
> Priority: Minor
>  Fix For: 1.1-beta-2

>
> Original Estimate: 1 week
> Remaining: 1 week
>
> Ok,
> Here are some changes I would recommend (as dIon asked for it ;-):
> 1) Change the welcome page to have direct links to gettting started. This is
> what I want to see when I visit the front page
> 2) The user guide should have information from the download and install
> sections to make it a more complete user's guide
> 3) getting started and user's guide should possibly be rethought into user's
> guide and developer's guide.
> 4) The plug-ins should be split into core and additional (or optional)
> 5) Someone who has written a plug-in should write a plug-in development
> howto and integrate that with the developer's guide.
> 6) Plug-ins should be described on the listing page
> 7) In the user's guide it would be nice to have a link to an example
> maven.xml file
> Let me know what you guys think, when I get a chance to look at it further I
> may have some further suggestions (and maybe patches ;-).
> -warner
> +warner onstine+

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[jira] Updated: (MAVEN-125) Documentation enhancements

2005-08-21 Thread Brett Porter (JIRA)
 [ http://jira.codehaus.org/browse/MAVEN-125?page=all ]

Brett Porter updated MAVEN-125:
---

   Description: 
Ok,
Here are some changes I would recommend (as dIon asked for it ;-):
1) Change the welcome page to have direct links to gettting started. This is
what I want to see when I visit the front page
2) The user guide should have information from the download and install
sections to make it a more complete user's guide
3) getting started and user's guide should possibly be rethought into user's
guide and developer's guide.
4) The plug-ins should be split into core and additional (or optional)
5) Someone who has written a plug-in should write a plug-in development
howto and integrate that with the developer's guide.
6) Plug-ins should be described on the listing page
7) In the user's guide it would be nice to have a link to an example
maven.xml file

Let me know what you guys think, when I get a chance to look at it further I
may have some further suggestions (and maybe patches ;-).

-warner

+warner onstine+

  was:
Ok,
Here are some changes I would recommend (as dIon asked for it ;-):
1) Change the welcome page to have direct links to gettting started. This is
what I want to see when I visit the front page
2) The user guide should have information from the download and install
sections to make it a more complete user's guide
3) getting started and user's guide should possibly be rethought into user's
guide and developer's guide.
4) The plug-ins should be split into core and additional (or optional)
5) Someone who has written a plug-in should write a plug-in development
howto and integrate that with the developer's guide.
6) Plug-ins should be described on the listing page
7) In the user's guide it would be nice to have a link to an example
maven.xml file

Let me know what you guys think, when I get a chance to look at it further I
may have some further suggestions (and maybe patches ;-).

-warner

+warner onstine+

Remaining Estimate: (was: 1 week)
 Original Estimate: (was: 604800)
   Environment: 

> Documentation enhancements
> --
>
>  Key: MAVEN-125
>  URL: http://jira.codehaus.org/browse/MAVEN-125
>  Project: Maven
> Type: Improvement
>   Components: documentation
> Reporter: dion gillard
> Assignee: Brett Porter
> Priority: Minor
>  Fix For: 1.1-beta-2

>
>
> Ok,
> Here are some changes I would recommend (as dIon asked for it ;-):
> 1) Change the welcome page to have direct links to gettting started. This is
> what I want to see when I visit the front page
> 2) The user guide should have information from the download and install
> sections to make it a more complete user's guide
> 3) getting started and user's guide should possibly be rethought into user's
> guide and developer's guide.
> 4) The plug-ins should be split into core and additional (or optional)
> 5) Someone who has written a plug-in should write a plug-in development
> howto and integrate that with the developer's guide.
> 6) Plug-ins should be described on the listing page
> 7) In the user's guide it would be nice to have a link to an example
> maven.xml file
> Let me know what you guys think, when I get a chance to look at it further I
> may have some further suggestions (and maybe patches ;-).
> -warner
> +warner onstine+

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[jira] Updated: (MAVEN-125) Documentation enhancements

2005-08-23 Thread Brett Porter (JIRA)
 [ http://jira.codehaus.org/browse/MAVEN-125?page=all ]

Brett Porter updated MAVEN-125:
---

Fix Version: (was: 1.1-beta-2)
 1.1-rc1

> Documentation enhancements
> --
>
>  Key: MAVEN-125
>  URL: http://jira.codehaus.org/browse/MAVEN-125
>  Project: Maven
> Type: Improvement
>   Components: documentation
> Reporter: dion gillard
> Assignee: Brett Porter
> Priority: Minor
>  Fix For: 1.1-rc1

>
>
> Ok,
> Here are some changes I would recommend (as dIon asked for it ;-):
> 1) Change the welcome page to have direct links to gettting started. This is
> what I want to see when I visit the front page
> 2) The user guide should have information from the download and install
> sections to make it a more complete user's guide
> 3) getting started and user's guide should possibly be rethought into user's
> guide and developer's guide.
> 4) The plug-ins should be split into core and additional (or optional)
> 5) Someone who has written a plug-in should write a plug-in development
> howto and integrate that with the developer's guide.
> 6) Plug-ins should be described on the listing page
> 7) In the user's guide it would be nice to have a link to an example
> maven.xml file
> Let me know what you guys think, when I get a chance to look at it further I
> may have some further suggestions (and maybe patches ;-).
> -warner
> +warner onstine+

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]