[jira] Commented: (MAVEN-835) zip files don't go to maven.dependency.classpath

2004-02-23 Thread jira
The following comment has been added to this issue:

 Author: Willie Vu
Created: Tue, 24 Feb 2004 2:37 AM
   Body:
Using jar and ... won't solve the problem because artifact 
directory is based on artifact type, i.e.

/s/
-
View this comment:
  
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-835&page=comments#action_17088

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

Here is an overview of the issue:
-
Key: MAVEN-835
Summary: zip files don't go to maven.dependency.classpath
   Type: Improvement

 Status: Closed
   Priority: Major
 Resolution: WON'T FIX

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven
   Fix Fors:
 1.0-rc1
   Versions:
 1.0-beta-10

   Assignee: 
   Reporter: Alexey Krasnoriadtsev

Created: Fri, 19 Sep 2003 6:15 PM
Updated: Tue, 24 Feb 2004 2:37 AM

Description:
[EMAIL PROTECTED]:test]$ cat project.xml


test


ant
1.5.3-1


oracle
classes12
zip
9.2.0.3-1.2



[EMAIL PROTECTED]:test]$ !maven
maven -X
 __  __
|  \/  |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
|_|  |_\__,_|\_/\___|_||_|  v. 1.0-beta-10

[DEBUG] Adding reference: maven.dependency.classpath -> 
/export/tools/maven-1.0-beta-10/repository/ant/jars/ant-1.5.3-1.jar
[DEBUG] Adding reference: maven-classpath ->
BUILD SUCCESSFUL
Total time:  7 seconds



-
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]



Maven Plugin Problems

2004-02-23 Thread Dave Chen
Developers,
 
I have written a Maven plug-in putting into the repository having a goal
to execute a java program:
 
   
 
However, after I installing the plug-in and run this goal,
 
I got this error:
 
   java.lang.NoClassDefFoundError: foo/bar/TransformValidator
 
Does anyone know how to get the repository path as the root classpath? I
tried ${maven.build.dir} and ${basepath} both not work.
 
Thanks,
Dave


cvs commit: maven-plugins/pom project.xml

2004-02-23 Thread brett
brett   2004/02/23 14:39:21

  Modified:antlrproject.xml
   docbook  project.xml
   latkaproject.xml
   pom  project.xml
  Log:
  update on mainline too
  
  Revision  ChangesPath
  1.24  +7 -0  maven-plugins/antlr/project.xml
  
  Index: project.xml
  ===
  RCS file: /home/cvs/maven-plugins/antlr/project.xml,v
  retrieving revision 1.23
  retrieving revision 1.24
  diff -u -r1.23 -r1.24
  --- project.xml   10 Feb 2004 12:49:43 -  1.23
  +++ project.xml   23 Feb 2004 22:39:20 -  1.24
  @@ -15,6 +15,13 @@
   scm:cvs:pserver:[EMAIL 
PROTECTED]:/home/cvspublic:maven-plugins/antlr/
   http://cvs.apache.org/viewcvs/maven-plugins/antlr/
 
  +  
  +
  +  1.1
  +  1.1
  +  MAVEN_ANTLR_1_1
  +
  +  
 
   
 Vincent Massol
  
  
  
  1.25  +7 -0  maven-plugins/docbook/project.xml
  
  Index: project.xml
  ===
  RCS file: /home/cvs/maven-plugins/docbook/project.xml,v
  retrieving revision 1.24
  retrieving revision 1.25
  diff -u -r1.24 -r1.25
  --- project.xml   22 Feb 2004 00:58:14 -  1.24
  +++ project.xml   23 Feb 2004 22:39:20 -  1.25
  @@ -13,6 +13,13 @@
   scm:cvs:pserver:[EMAIL 
PROTECTED]:/home/cvspublic:maven-plugins/docbook/
   http://cvs.apache.org/viewcvs/maven-plugins/docbook/
 
  +  
  +
  +  1.1
  +  1.1
  +  MAVEN_DOCBOOK_1_1
  +
  +  
 
   
 Jason van Zyl
  
  
  
  1.25  +7 -0  maven-plugins/latka/project.xml
  
  Index: project.xml
  ===
  RCS file: /home/cvs/maven-plugins/latka/project.xml,v
  retrieving revision 1.24
  retrieving revision 1.25
  diff -u -r1.24 -r1.25
  --- project.xml   10 Feb 2004 12:49:42 -  1.24
  +++ project.xml   23 Feb 2004 22:39:21 -  1.25
  @@ -14,6 +14,13 @@
   scm:cvs:pserver:[EMAIL 
PROTECTED]:/home/cvspublic:maven-plugins/latka/
   http://cvs.apache.org/viewcvs/maven-plugins/latka/
 
  +  
  +
  +  1.3
  +  1.3
  +  MAVEN_LATKA_1_3
  +
  +  
 
 
 
  
  
  
  1.32  +7 -0  maven-plugins/pom/project.xml
  
  Index: project.xml
  ===
  RCS file: /home/cvs/maven-plugins/pom/project.xml,v
  retrieving revision 1.31
  retrieving revision 1.32
  diff -u -r1.31 -r1.32
  --- project.xml   10 Feb 2004 12:49:44 -  1.31
  +++ project.xml   23 Feb 2004 22:39:21 -  1.32
  @@ -14,6 +14,13 @@
   scm:cvs:pserver:[EMAIL 
PROTECTED]:/home/cvspublic:maven-plugins/pom/
   http://cvs.apache.org/viewcvs/maven-plugins/pom/
 
  +  
  +
  +  1.3
  +  1.3
  +  MAVEN_POM_1_3
  +
  +  
 
   
 Bob McWhirter
  
  
  

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



RE: [Fwd: Re: [commons-site] Alternate Horizontal Project Navigat ion]

2004-02-23 Thread Chad McHenry
> My only beef with the current style is what happens when you have
tons
> of sub-projects, as in the case of Jakarta Commons. When you start
> stacking many different scopes of detail on top of one another down
the
> left sidebar, it becomes hard to differentiate between scope
divisions.
> I know, the headers should be a clue, but it does get a bit 
> overwhelming... Maven's plugins reference would have a similar
problem,
> if it were constructed in this way.

There's already a patch for this on jira, though not yet in CVS:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPXDOC-78


__
Do you Yahoo!?
Yahoo! Mail SpamGuard - Read only the mail you want.
http://antispam.yahoo.com/tools

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



cvs commit: maven/xdocs/reference/developers releasing-plugins.xml

2004-02-23 Thread brett
brett   2004/02/23 14:37:37

  Modified:xdocs/reference/developers Tag: MAVEN-1_0-BRANCH
releasing-plugins.xml
  Log:
  update plugin release documentation
  
  Revision  ChangesPath
  No   revision
  No   revision
  1.4.4.1   +55 -58maven/xdocs/reference/developers/releasing-plugins.xml
  
  Index: releasing-plugins.xml
  ===
  RCS file: /home/cvs/maven/xdocs/reference/developers/releasing-plugins.xml,v
  retrieving revision 1.4
  retrieving revision 1.4.4.1
  diff -u -r1.4 -r1.4.4.1
  --- releasing-plugins.xml 14 Oct 2003 01:19:36 -  1.4
  +++ releasing-plugins.xml 23 Feb 2004 22:37:36 -  1.4.4.1
  @@ -7,7 +7,7 @@
 
   
 This page describes what Maven contributors or developers need to do when
  -  modifying a Maven plugin in Maven CVS:
  +  modifying a Maven component or plugin in Maven CVS:
   
   
 
  @@ -17,14 +17,13 @@
   or the format of the file.
 
 
  -Update the xdocs/goals.xml,
  -xdocs/properties.xml and other documentation files
  -in xdocs/, reflecting your change.
  -If the plugin has no xdocs, please generate skeletons using 
  +Update the other documentation files in xdocs/, reflecting 
your change.
  +For plugins, consider especially the xdocs/goals.xml and
  +xdocs/properties.xml files. If the plugin has no xdocs, 
please generate skeletons using 
   maven plugin:generate-docs
 
 
  -Ensure that the version in plugin.xml is a SNAPSHOT, e.g. 
  +Ensure that the version in project.xml is a SNAPSHOT, e.g. 
   1.1-SNAPSHOT,
   and not 
1.1.
   Unless you are in the process of creating a release of course.
  @@ -38,77 +37,85 @@
 
   
 
  -Modify the  in 
project.xml to remove the
  -  -SNAPSHOT part 
  + Add a download link in the project navigation 
(navigation.xml).
  +Example:
   
  +
 
 
  -Modify the / in 
project.xml
  -  and ensure the correct id, name and expected tag.
  + Create an announcements directory in the project and 
inside create a 
  +[major].[minor].ann text file containing the announce of the 
release.
  +For an example, see 
  +http://cvs.apache.org/viewcvs.cgi/maven-plugins/scm/announcements/";>the SCM 
plugin announcements
   
 
 
  - Modify changes.xml to put the release date  
  +Modify the  in 
project.xml to remove the
  +  -SNAPSHOT part 
   
 
 
  - Add a download link in the project navigation 
(navigation.xml).
  -Example:
  +Modify the / in 
project.xml
  +  and ensure the correct id, name and expected tag.
   
  -
  -
  -  ;
  -
  -
 
 
  - Create an announcements directory in the project and 
inside create a 
  -[major].[minor].ann text file containing the announce of the 
release.
  -For an example, see 
  -http://cvs.apache.org/viewcvs.cgi/maven/src/plugins-build/cactus/announcements/";>cactus
  + Modify changes.xml to put the release date  
   
 
  -  Commit your changes to CVS
  -  Produce a clean build of the plugin using maven clean 
plugin
  -  
  +  Commit your changes to CVS
  +  
   Tag the plugin project dir in CVS with 
MAVEN_[PROJECTNAME]_[MAJOR]_[MINOR]
   (for example MAVEN_CACTUS_2_0). 
  -  
  -  
  +  
  +  Produce a clean build of the plugin using maven clean 
plugin
  +  
   Upload the new version to 
   http://www.ibiblio.org/maven/maven/plugins/";>http://www.ibiblio.org/maven/maven/plugins/
  -using maven -DgroupId=maven -Dtype=plugin -Dartifact=/path/to/file 
repository:copy-artifact
  +using
 
 
Send a quick release email to the Maven user list, using the content of 
   [major].[minor].ann. 
   
 
  -   
  - Increase the version in project.xml and don't forget to 
  -prepend -SNAPSHOT
  -
  -  
  -  
  - Update project.xml to add a new 

  -tag for HEAD
  -
  - Relax!' 
  -  
   
 
 
   
 
Q: When would I do a release?
  - A: At the moment, the plugins have the same 
  -lifecycle as Maven as a whole. Thus the plugi

cvs commit: maven-plugins/pom project.xml

2004-02-23 Thread brett
brett   2004/02/23 14:33:15

  Modified:pom  Tag: MAVEN_POM_1_3-branch project.xml
  Log:
  add version info
  
  Revision  ChangesPath
  No   revision
  No   revision
  1.27.2.1  +7 -0  maven-plugins/pom/project.xml
  
  Index: project.xml
  ===
  RCS file: /home/cvs/maven-plugins/pom/project.xml,v
  retrieving revision 1.27
  retrieving revision 1.27.2.1
  diff -u -r1.27 -r1.27.2.1
  --- project.xml   29 Sep 2003 05:19:13 -  1.27
  +++ project.xml   23 Feb 2004 22:33:15 -  1.27.2.1
  @@ -14,6 +14,13 @@
   scm:cvs:pserver:[EMAIL 
PROTECTED]:/home/cvspublic:maven/src/plugins-build/pom/
   http://cvs.apache.org/viewcvs/maven/src/plugins-build/pom/
 
  +  
  +
  +  1.3
  +  1.3
  +  MAVEN_POM_1_3
  +
  +  
 
   
 dIon Gillard
  
  
  

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



cvs commit: maven-plugins/latka project.xml

2004-02-23 Thread brett
brett   2004/02/23 14:29:48

  Modified:latkaTag: MAVEN_LATKA_1_3-branch project.xml
  Log:
  add version info
  
  Revision  ChangesPath
  No   revision
  No   revision
  1.20.2.1  +7 -0  maven-plugins/latka/project.xml
  
  Index: project.xml
  ===
  RCS file: /home/cvs/maven-plugins/latka/project.xml,v
  retrieving revision 1.20
  retrieving revision 1.20.2.1
  diff -u -r1.20 -r1.20.2.1
  --- project.xml   29 Sep 2003 05:19:12 -  1.20
  +++ project.xml   23 Feb 2004 22:29:48 -  1.20.2.1
  @@ -14,6 +14,13 @@
   scm:cvs:pserver:[EMAIL 
PROTECTED]:/home/cvspublic:maven/src/plugins-build/latka/
   http://cvs.apache.org/viewcvs/maven/src/plugins-build/latka/
 
  +  
  +
  +  1.3
  +  1.3
  +  MAVEN_LATKA_1_3
  +
  +  
 
   
 dIon Gillard
  
  
  

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



cvs commit: maven-plugins/docbook project.xml

2004-02-23 Thread brett
brett   2004/02/23 14:27:27

  Modified:docbook  Tag: MAVEN_DOCBOOK_1_1-branch project.xml
  Log:
  add version info
  
  Revision  ChangesPath
  No   revision
  No   revision
  1.15.2.1  +7 -0  maven-plugins/docbook/project.xml
  
  Index: project.xml
  ===
  RCS file: /home/cvs/maven-plugins/docbook/project.xml,v
  retrieving revision 1.15
  retrieving revision 1.15.2.1
  diff -u -r1.15 -r1.15.2.1
  --- project.xml   29 Sep 2003 05:19:11 -  1.15
  +++ project.xml   23 Feb 2004 22:27:27 -  1.15.2.1
  @@ -13,6 +13,13 @@
   scm:cvs:pserver:[EMAIL 
PROTECTED]:/home/cvspublic:maven/src/plugins-build/docbook/
   http://cvs.apache.org/viewcvs/maven/src/plugins-build/docbook/
 
  +  
  +
  +  1.1
  +  1.1
  +  MAVEN_DOCBOOK_1_1
  +
  +  
 
   
 dIon Gillard
  
  
  

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



cvs commit: maven-plugins/antlr project.xml

2004-02-23 Thread brett
brett   2004/02/23 14:24:12

  Modified:antlrTag: MAVEN_ANTLR_1_1-branch project.xml
  Log:
  add version info
  
  Revision  ChangesPath
  No   revision
  No   revision
  1.17.2.1  +7 -0  maven-plugins/antlr/project.xml
  
  Index: project.xml
  ===
  RCS file: /home/cvs/maven-plugins/antlr/project.xml,v
  retrieving revision 1.17
  retrieving revision 1.17.2.1
  diff -u -r1.17 -r1.17.2.1
  --- project.xml   29 Sep 2003 05:19:10 -  1.17
  +++ project.xml   23 Feb 2004 22:24:11 -  1.17.2.1
  @@ -14,6 +14,13 @@
   scm:cvs:pserver:[EMAIL 
PROTECTED]:/home/cvspublic:maven/src/plugins-build/antlr/
   http://cvs.apache.org/viewcvs/maven/src/plugins-build/antlr/
 
  +  
  +
  +  1.1
  +  1.1
  +  MAVEN_ANTLR_1_1
  +
  +  
 
   
 Vincent Massol
  
  
  

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



[jira] Commented: (MAVENUPLOAD-80) xml-commons-resolver upload request

2004-02-23 Thread jira
The following comment has been added to this issue:

 Author: Per Olesen
Created: Mon, 23 Feb 2004 5:27 PM
   Body:
But how should I do that? I'm not a maven committer, and I do not have ssh access to 
Apache servers. Is there some other way for me to access the repository you are 
referring to at apache?
 
> Mark Diggory was the one who set this up.
> Although copying into a dir
> like /www/www.apache.org/dist/java-repository 
> should end up with it mirrored appropriately.

Would that not require ssh access to some server?

-
View this comment:
  
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVENUPLOAD-80&page=comments#action_17082

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

Here is an overview of the issue:
-
Key: MAVENUPLOAD-80
Summary: xml-commons-resolver upload request
   Type: Task

 Status: Resolved
   Priority: Minor
 Resolution: FIXED

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven-upload-requests

   Assignee: Jason van Zyl
   Reporter: Per Olesen

Created: Mon, 23 Feb 2004 1:27 PM
Updated: Mon, 23 Feb 2004 5:27 PM

Description:
Norman Walsh's entity resolver for Apaches Xerces/Xalan tools have been included in 
the apache xml-commons project as the xml-commons-resolver jar.

I would like it included in repository.

Do not know precisely what the groupId should be, but i suggest "xml-commons", as 
there are other xml-commons-xxx jars.



-
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]



cvs commit: maven-plugins/war/xdocs changes.xml goals.xml

2004-02-23 Thread brett
brett   2004/02/23 14:20:27

  Modified:war  plugin.jelly
   war/xdocs changes.xml goals.xml
  Log:
  add description of changes, add guard against cleaning source files
  
  Revision  ChangesPath
  1.35  +3 -1  maven-plugins/war/plugin.jelly
  
  Index: plugin.jelly
  ===
  RCS file: /home/cvs/maven-plugins/war/plugin.jelly,v
  retrieving revision 1.34
  retrieving revision 1.35
  diff -u -r1.34 -r1.35
  --- plugin.jelly  23 Feb 2004 00:45:52 -  1.34
  +++ plugin.jelly  23 Feb 2004 22:20:27 -  1.35
  @@ -211,7 +211,9 @@
   description="Remove all artifacts created by war plugin">  
   
 
  -  
  +  
  +
  +  
   
   
   
  
  
  
  1.17  +7 -0  maven-plugins/war/xdocs/changes.xml
  
  Index: changes.xml
  ===
  RCS file: /home/cvs/maven-plugins/war/xdocs/changes.xml,v
  retrieving revision 1.16
  retrieving revision 1.17
  diff -u -r1.16 -r1.17
  --- changes.xml   9 Nov 2003 23:24:34 -   1.16
  +++ changes.xml   23 Feb 2004 22:20:27 -  1.17
  @@ -15,6 +15,13 @@
   Use the new caller plugin to isolate the 
   java compilation goal called from its implementation.
 
  +  
  +Add war:inplace goal for building the webapp into maven.war.src. You should 
cvsignore WEB-INF/lib and
  +WEB-INF/classes
  +  
  +  
  +Add target path to dependencies so you can copy to elsewhere than 
WEB-INF/lib. Useful for applets.
  +  
   
   
   
  
  
  
  1.5   +10 -1 maven-plugins/war/xdocs/goals.xml
  
  Index: goals.xml
  ===
  RCS file: /home/cvs/maven-plugins/war/xdocs/goals.xml,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- goals.xml 5 Jul 2003 17:10:45 -   1.4
  +++ goals.xml 23 Feb 2004 22:20:27 -  1.5
  @@ -54,7 +54,16 @@
   war:clean
   Delete all artifacts created by war plugin
   
  +  
  +war:inplace
  +
  +  Build an exploded web application into ${maven.war.src}. This allows you 
to mount it in your application
  +  server, and you only need to run it again for dependency and class 
changes, not JSP changes.
  +  This goal will not clean old dependencies - due to the dangers involved 
in automating this for your
  +  source tree, you must do that yourself.
  +
  +
 
 
 
  -
  \ No newline at end of file
  +
  
  
  

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



cvs commit: maven-plugins/xdoc project.xml

2004-02-23 Thread brett
brett   2004/02/23 14:14:06

  Modified:cruisecontrol project.xml
   developer-activity project.xml
   eclipse  project.xml
   file-activity project.xml
   idea project.xml
   jar  project.xml
   junit-report project.xml
   jxr  project.xml
   linkcheck project.xml
   site project.xml
   test project.xml
   xdoc project.xml
  Log:
  describe requirement. This will do until it is a POM element proper.
  
  Revision  ChangesPath
  1.11  +3 -1  maven-plugins/cruisecontrol/project.xml
  
  Index: project.xml
  ===
  RCS file: /home/cvs/maven-plugins/cruisecontrol/project.xml,v
  retrieving revision 1.10
  retrieving revision 1.11
  diff -u -r1.10 -r1.11
  --- project.xml   10 Feb 2004 12:49:43 -  1.10
  +++ project.xml   23 Feb 2004 22:14:06 -  1.11
  @@ -5,7 +5,9 @@
 maven-cruisecontrol-plugin
 Maven Cruise Control Plug-in
 1.1-SNAPSHOT
  -  A plugin to handle the generating and maintaining of Cruise Control 
configuration
  +  A plugin to handle the generating and maintaining of Cruise Control 
configuration.
  +Requires Maven 1.0 RC2.
  +  
 Cruise Control Plugin for Maven
 http://maven.apache.org/reference/plugins/cruisecontrol/
 
/www/maven.apache.org/reference/plugins/cruisecontrol/
  
  
  
  1.21  +2 -1  maven-plugins/developer-activity/project.xml
  
  Index: project.xml
  ===
  RCS file: /home/cvs/maven-plugins/developer-activity/project.xml,v
  retrieving revision 1.20
  retrieving revision 1.21
  diff -u -r1.20 -r1.21
  --- project.xml   3 Feb 2004 10:56:44 -   1.20
  +++ project.xml   23 Feb 2004 22:14:06 -  1.21
  @@ -6,7 +6,8 @@
 maven-developer-activity-plugin
 Maven Developer Activity Plug-in
 1.4-SNAPSHOT
  -  This document provides a report of activity in terms of CVS commits 
and breaks it out by developer.
  +  This document provides a report of activity in terms of CVS commits 
and breaks it out by developer.
  +Requires Maven 1.0 RC2.
 Developer Activity report
 http://maven.apache.org/reference/plugins/developer-activity/
 
/www/maven.apache.org/reference/plugins/developer-activity/
  
  
  
  1.22  +2 -1  maven-plugins/eclipse/project.xml
  
  Index: project.xml
  ===
  RCS file: /home/cvs/maven-plugins/eclipse/project.xml,v
  retrieving revision 1.21
  retrieving revision 1.22
  diff -u -r1.21 -r1.22
  --- project.xml   10 Feb 2004 12:49:42 -  1.21
  +++ project.xml   23 Feb 2004 22:14:06 -  1.22
  @@ -6,7 +6,8 @@
 maven-eclipse-plugin
 Maven Eclipse Plug-in
 1.6-SNAPSHOT
  -  A plugin to generate various files for the Eclipse IDE and ease the 
use of Maven within that environment
  +  A plugin to generate various files for the Eclipse IDE and ease the 
use of Maven within that environment.
  +Requires Maven 1.0 RC2.
 Eclipse Plugin for Maven
 http://maven.apache.org/reference/plugins/eclipse/
 /www/maven.apache.org/reference/plugins/eclipse/
  
  
  
  1.23  +2 -1  maven-plugins/file-activity/project.xml
  
  Index: project.xml
  ===
  RCS file: /home/cvs/maven-plugins/file-activity/project.xml,v
  retrieving revision 1.22
  retrieving revision 1.23
  diff -u -r1.22 -r1.23
  --- project.xml   10 Feb 2004 12:49:43 -  1.22
  +++ project.xml   23 Feb 2004 22:14:06 -  1.23
  @@ -9,7 +9,8 @@
 
   
 jakarta
  -  This document provides a report of activity in terms of CVS commits 
and breaks it out by file.
  +  This document provides a report of activity in terms of CVS commits 
and breaks it out by file.
  +Requires Maven 1.0 RC2.
 File activity Report
 http://maven.apache.org/reference/plugins/file-activity/
 
/www/maven.apache.org/reference/plugins/file-activity/
  
  
  
  1.18  +1 -0  maven-plugins/idea/project.xml
  
  Index: project.xml
  ===
  RCS file: /home/cvs/maven-plugins/idea/project.xml,v
  retrieving revision 1.17
  retrieving revision 1.18
  diff -u -r1.17 -r1.18
  --- project.xml   10 Feb 2004 12:49:44 -  1.17
  +++ project.xml   23 Feb 2004 22:14:06 -  1.18
  @@ -7,6 +7,7 @@
 Maven IDEA Plug-in
 1.3-SNAPSHOT
 IDEA Plugin for Maven
  +  IDEA Plugin for Maven. Requires Maven 1.0 RC2.
 http://maven.apache.org/reference/plugins/idea/
 /www/maven.apache.org/reference/plugins/idea/
 
  
  
  
  1.17  +1 -1  maven-plugins/jar/project.xml
  
  Index: project.xml
  ==

[jira] Resolved: (MAVENUPLOAD-80) xml-commons-resolver upload request

2004-02-23 Thread jira
Message:

   The following issue has been resolved as FIXED.

   Resolver: Ben Walding
   Date: Mon, 23 Feb 2004 5:01 PM

You should be able to do this by loading the pom + jar into the Apache repository at 
apache.  ibiblio syncs from this every 4 hours or so.

Mark Diggory was the one who set this up.  Although copying into a dir like 
/www/www.apache.org/dist/java-repository should end up with it mirrored appropriately.
-
View the issue:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVENUPLOAD-80

Here is an overview of the issue:
-
Key: MAVENUPLOAD-80
Summary: xml-commons-resolver upload request
   Type: Task

 Status: Resolved
   Priority: Minor
 Resolution: FIXED

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven-upload-requests

   Assignee: Jason van Zyl
   Reporter: Per Olesen

Created: Mon, 23 Feb 2004 1:27 PM
Updated: Mon, 23 Feb 2004 5:01 PM

Description:
Norman Walsh's entity resolver for Apaches Xerces/Xalan tools have been included in 
the apache xml-commons project as the xml-commons-resolver jar.

I would like it included in repository.

Do not know precisely what the groupId should be, but i suggest "xml-commons", as 
there are other xml-commons-xxx jars.



-
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] Created: (MPECLIPSE-20) add general .classpath and .project modification goals

2004-02-23 Thread jira
Message:

  A new issue has been created in JIRA.

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

Here is an overview of the issue:
-
Key: MPECLIPSE-20
Summary: add general .classpath and .project modification goals
   Type: New Feature

 Status: Open
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven-eclipse-plugin

   Assignee: Vincent Massol
   Reporter: Ryan Sonnek

Created: Mon, 23 Feb 2004 2:04 PM
Updated: Mon, 23 Feb 2004 2:04 PM

Description:
allow other plugins to use the current eclipse plugin to update/modify the .classpath 
and .project files.  adding another goal like add-classpath-callback and 
add-project-callback where plugin users can pass options (groupId, artifactId, 
version) of the addition, and the plugin would check if it exists, and add it as 
needed. 

this would be a great addition to allow for external plugins to work WITH the eclipse 
plugin instead of lumping everything INTO the eclipse plugin.  not too long ago, the 
eclipse plugin had a dependency on the cactus plugin for this same problem.  the 
cactus plugin could simply add a goal to add it's jars to the classpath.


-
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] Created: (MPXDOC-84) Compilation breaks on #nix system.

2004-02-23 Thread jira
Message:

  A new issue has been created in JIRA.

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

Here is an overview of the issue:
-
Key: MPXDOC-84
Summary: Compilation breaks on #nix system.
   Type: Bug

 Status: Open
   Priority: Minor

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven-xdoc-plugin

   Assignee: Jason van Zyl
   Reporter: Sebastien Sahuc

Created: Mon, 23 Feb 2004 1:49 PM
Updated: Mon, 23 Feb 2004 1:49 PM
Environment: NacOsX

Description:
Here is the patch. Otherwise it complains of missing Users directory. check the 
maven-users list for dicusccion on that subject.

Index: xdoc/plugin.jelly
===
RCS file: /home/cvspublic/maven-plugins/xdoc/plugin.jelly,v
retrieving revision 1.54
diff -r1.54 plugin.jelly
365c365
<   
---
>   



-
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] Created: (MAVENSCM-1) scm goal uses -C option which break on some system (MacOSX)

2004-02-23 Thread jira
Message:

  A new issue has been created in JIRA.

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

Here is an overview of the issue:
-
Key: MAVENSCM-1
Summary:  scm goal uses -C option which break on some system (MacOSX)
   Type: Bug

 Status: Open
   Priority: Critical

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: Maven-SCM

   Assignee: Emmanuel Venisse
   Reporter: Sebastien Sahuc

Created: Mon, 23 Feb 2004 1:33 PM
Updated: Mon, 23 Feb 2004 1:33 PM
Environment: MacOSX

Description:
Somehow the -C option is used in the scm:prepare-release, which  
unfortunately is not available in the cvs shipped by default with  
MacOSX (Both Jaguar and Panther version).

See below for the result:
 
[dhcp121 xml]$ maven scm:prepare-release
  __  __
|  \/  |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
|_|  |_\__,_|\_/\___|_||_|  v. 1.0-rc2-SNAPSHOT

Using SCM method: cvs
Using CVSROOT: :pserver:[EMAIL PROTECTED]:/cvs/n3
Using module: xml
Verifying no modifications are present
build:start:

scm:validate:

scm:prepare-release:
scm:cvs-prepare-release:
 [copy] Copying 1 file to /Users/Shared/Projects/yosemite/xml
 [cvs] Using cvs passfile: /Users/sebastiensahuc/.cvspass
 [cvs] update: invalid option -- C
 [cvs] Usage: cvs update [-APdflRp] [-k kopt] [-r rev|-D 
date] [-j  
rev]
 [cvs] [-I ign] [-W spec] [files...]
 [cvs]   -A  Reset any sticky tags/date/kopts.
 [cvs]   -P  Prune empty directories.
 [cvs]   -d  Build directories, like checkout does.
 [cvs]   -f  Force a head revision match if tag/date not  
found.
 [cvs]   -l  Local directory only, no recursion.
 [cvs]   -R  Process directories recursively.
 [cvs]   -p  Send updates to standard output (avoids  
stickiness).
 [cvs]   -k kopt Use RCS kopt -k option on checkout.
 [cvs]   -r rev  Update using specified revision/tag 
(is sticky).
 [cvs]   -D date Set date to update from (is sticky).
 [cvs]   -j rev  Merge in changes made between 
current revision  
and rev.
 [cvs]   -I ign  More files to ignore (! to reset).
 [cvs]   -W spec Wrappers specification line.
 [cvs] (Specify the --help global option for a list of 
other help  
options)

BUILD FAILED
File..  
file:/Users/sebastiensahuc/.maven/plugins/maven-scm-plugin-1.2- 
SNAPSHOT/plugin.jelly
Element... ant:cvs
Line.. 215
Column 9
cvs exited with error code 1
Command line was [Executing 'cvs' with arguments: 
'-d:pserver:[EMAIL PROTECTED]:/cvs/n3'
'-q'
'update'
'-C'
'project.xml'

The ' characters around the executable and arguments are
not part of the command.



-
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] Commented: (MAVENUPLOAD-80) xml-commons-resolver upload request

2004-02-23 Thread jira
The following comment has been added to this issue:

 Author: Per Olesen
Created: Mon, 23 Feb 2004 1:31 PM
   Body:
And the URL from which the resource can be downloaded is:

http://apache.mirrors.hoobly.com/xml/commons/xml-commons-resolver-1.1.tar.gz

Or, if mirror is down, go to: "http://xml.apache.org/commons/"; and chose download.

-
View this comment:
  
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVENUPLOAD-80&page=comments#action_17075

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

Here is an overview of the issue:
-
Key: MAVENUPLOAD-80
Summary: xml-commons-resolver upload request
   Type: Task

 Status: Open
   Priority: Minor

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven-upload-requests

   Assignee: Jason van Zyl
   Reporter: Per Olesen

Created: Mon, 23 Feb 2004 1:27 PM
Updated: Mon, 23 Feb 2004 1:31 PM

Description:
Norman Walsh's entity resolver for Apaches Xerces/Xalan tools have been included in 
the apache xml-commons project as the xml-commons-resolver jar.

I would like it included in repository.

Do not know precisely what the groupId should be, but i suggest "xml-commons", as 
there are other xml-commons-xxx jars.



-
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: (MAVENUPLOAD-80) xml-commons-resolver upload request

2004-02-23 Thread jira
The following issue has been updated:

Updater: Per Olesen (mailto:[EMAIL PROTECTED])
   Date: Mon, 23 Feb 2004 1:29 PM
Comment:
This is the project descriptor for the upload request
Changes:
 Attachment changed to xml-commons-resolver.request.xml
-
For a full history of the issue, see:

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

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

Here is an overview of the issue:
-
Key: MAVENUPLOAD-80
Summary: xml-commons-resolver upload request
   Type: Task

 Status: Open
   Priority: Minor

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven-upload-requests

   Assignee: Jason van Zyl
   Reporter: Per Olesen

Created: Mon, 23 Feb 2004 1:27 PM
Updated: Mon, 23 Feb 2004 1:29 PM

Description:
Norman Walsh's entity resolver for Apaches Xerces/Xalan tools have been included in 
the apache xml-commons project as the xml-commons-resolver jar.

I would like it included in repository.

Do not know precisely what the groupId should be, but i suggest "xml-commons", as 
there are other xml-commons-xxx jars.



-
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] Created: (MAVENUPLOAD-80) xml-commons-resolver upload request

2004-02-23 Thread jira
Message:

  A new issue has been created in JIRA.

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

Here is an overview of the issue:
-
Key: MAVENUPLOAD-80
Summary: xml-commons-resolver upload request
   Type: Task

 Status: Open
   Priority: Minor

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven-upload-requests

   Assignee: Jason van Zyl
   Reporter: Per Olesen

Created: Mon, 23 Feb 2004 1:27 PM
Updated: Mon, 23 Feb 2004 1:27 PM

Description:
Norman Walsh's entity resolver for Apaches Xerces/Xalan tools have been included in 
the apache xml-commons project as the xml-commons-resolver jar.

I would like it included in repository.

Do not know precisely what the groupId should be, but i suggest "xml-commons", as 
there are other xml-commons-xxx jars.



-
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]



Re: [Fwd: Re: [commons-site] Alternate Horizontal Project Navigat ion]

2004-02-23 Thread Mark R. Diggory
I'd like to chat more on this, but I'm totally swamped today. Maybe I 
can respond later tonite. I agree with alot of the discussion, what I 
built is primarily a prototype with tons of room for input. Anyone who 
wants to step up to bat and play around with it, I will provide the 
alternate site.jsl and various css styles in the commons-site cvs tree 
for play. Later tonite I illtry to catchup with the discussion and see 
if I can work on some implementation.

-Mark

Jason van Zyl wrote:

On Mon, 2004-02-23 at 11:37, [EMAIL PROTECTED] wrote:

My only beef with the current style is what happens when you have tons of
sub-projects, as in the case of Jakarta Commons. When you start stacking
many different scopes of detail on top of one another down the left sidebar,
it becomes hard to differentiate between scope divisions. I know, the
headers should be a clue, but it does get a bit overwhelming... Maven's
plugins reference would have a similar problem, if it were constructed in
this way.


Dealing with umbrella sites is definitely something that people want
some advice on how to do best. An umbrella page is really an aggregation
of all information contained within all the subprojects. So in this case
maybe we need a different kind of page. Possibly having a page with a
reference to all the projects contained within instead of trying to
stuff them all in the navigation.
The umbrella page can contain all the things like project goals,
licenses, pointers to mailing lists and the like but maybe we need a
standard format for an umbrella project? I agree that the navigation for
the commons is a little unweildly and will become moreso as the number
of components grows.
Come up with a clean page with a nicely formatted table of all the
projects contained within, possibly with a short summary (taken from the
short description) and a pointer to the subproject page.

Another problem with the volume of information is that it tends to lead
off-screen, where scrolling to read destroys the coherence of the sidebar
information. 


Definitely, this is where I think a page containing a list of the
subprojects would be good. Having to scroll does indeed make wandering
through a site annoying.

Personally, I'd much rather have a dashboard at the top (where
applications, not just _web_ applications traditionally have a menubar)
where I can see the operations near at hand, like details of this project.
This may seem like replication of the top part of the sidebar, but it pops
out to the eye quite a bit more readily than a subsection of this gigantic
list on the left (all of the same font size, etc.).


For an application I too like the dashboard. For a maven generated site
I have always been of the mind that the front page first paragraph of of
the first section should tell you "What is this beast?". I'm sure it's a
matter of habit for me now, but I read that first paragraph and then I
wander left to the navigation and in the first navigation section is
where the hot items should go like javadoc, downloads, cvs repos.
Looking at the first page of the commons-math site, I am immediately
presented with a list of things: there is no summary of what the project
is or does which. Instead of having a link to "About Math" it should
tell you right there on the first page and the user guide be a hot item
in the first set of navigations. 

Additionally, Maven's users guide suffers the same problem where
scrolling of the table of contents is necessary. Though commons-math is
much better in that you link to each section so you can click around
without scrolling much.
There are certainly some guidelines for good sites like Jacob Nielsen's
books but to a large extent I think there is an element of conditioning
and if we come up with a reasonably sensible, standard format then
everyone benefits. I agree with you 100% that navigation without
scrolling should be a goal to strive for and we can help with that by
providing tools to make easily navigable user guides, FAQs and templates
for aggregated sites.

Final note: The content area is what you define it to be. If you frame a
page properly, it will be obvious what is and is not the content area.
Top/Left are premium real estate because they naturally frame any page
content, so maybe shrinking the _huge_ logo at the top and/or allowing the
embedding of some navigation in that top 10% of the page (I'm guessing)
would help free up some space for the actual content. Another would be to
take a page from the Safari website, and allow the user to "hide" the
sidebar, in order to read the content.


All good ideas, and these are the things I would like to incorporate
into the xdoc plugin.

I know that the Commons website isn't probably organized in the best
possible way wrt what is/isn't on the sidebar, but I definitely think the
site rendering should provide some not-so-subtle visual clues about what is
nearby, or important. Prepending these links to the top of a long list
without even changing the text 

RE: [Fwd: Re: [commons-site] Alternate Horizontal Project Navigat ion]

2004-02-23 Thread Jason van Zyl
On Mon, 2004-02-23 at 11:37, [EMAIL PROTECTED] wrote:
> My only beef with the current style is what happens when you have tons of
> sub-projects, as in the case of Jakarta Commons. When you start stacking
> many different scopes of detail on top of one another down the left sidebar,
> it becomes hard to differentiate between scope divisions. I know, the
> headers should be a clue, but it does get a bit overwhelming... Maven's
> plugins reference would have a similar problem, if it were constructed in
> this way.

Dealing with umbrella sites is definitely something that people want
some advice on how to do best. An umbrella page is really an aggregation
of all information contained within all the subprojects. So in this case
maybe we need a different kind of page. Possibly having a page with a
reference to all the projects contained within instead of trying to
stuff them all in the navigation.

The umbrella page can contain all the things like project goals,
licenses, pointers to mailing lists and the like but maybe we need a
standard format for an umbrella project? I agree that the navigation for
the commons is a little unweildly and will become moreso as the number
of components grows.

Come up with a clean page with a nicely formatted table of all the
projects contained within, possibly with a short summary (taken from the
short description) and a pointer to the subproject page.

> Another problem with the volume of information is that it tends to lead
> off-screen, where scrolling to read destroys the coherence of the sidebar
> information. 

Definitely, this is where I think a page containing a list of the
subprojects would be good. Having to scroll does indeed make wandering
through a site annoying.

> Personally, I'd much rather have a dashboard at the top (where
> applications, not just _web_ applications traditionally have a menubar)
> where I can see the operations near at hand, like details of this project.
> This may seem like replication of the top part of the sidebar, but it pops
> out to the eye quite a bit more readily than a subsection of this gigantic
> list on the left (all of the same font size, etc.).

For an application I too like the dashboard. For a maven generated site
I have always been of the mind that the front page first paragraph of of
the first section should tell you "What is this beast?". I'm sure it's a
matter of habit for me now, but I read that first paragraph and then I
wander left to the navigation and in the first navigation section is
where the hot items should go like javadoc, downloads, cvs repos.

Looking at the first page of the commons-math site, I am immediately
presented with a list of things: there is no summary of what the project
is or does which. Instead of having a link to "About Math" it should
tell you right there on the first page and the user guide be a hot item
in the first set of navigations. 

Additionally, Maven's users guide suffers the same problem where
scrolling of the table of contents is necessary. Though commons-math is
much better in that you link to each section so you can click around
without scrolling much.

There are certainly some guidelines for good sites like Jacob Nielsen's
books but to a large extent I think there is an element of conditioning
and if we come up with a reasonably sensible, standard format then
everyone benefits. I agree with you 100% that navigation without
scrolling should be a goal to strive for and we can help with that by
providing tools to make easily navigable user guides, FAQs and templates
for aggregated sites.

> Final note: The content area is what you define it to be. If you frame a
> page properly, it will be obvious what is and is not the content area.
> Top/Left are premium real estate because they naturally frame any page
> content, so maybe shrinking the _huge_ logo at the top and/or allowing the
> embedding of some navigation in that top 10% of the page (I'm guessing)
> would help free up some space for the actual content. Another would be to
> take a page from the Safari website, and allow the user to "hide" the
> sidebar, in order to read the content.

All good ideas, and these are the things I would like to incorporate
into the xdoc plugin.

> I know that the Commons website isn't probably organized in the best
> possible way wrt what is/isn't on the sidebar, but I definitely think the
> site rendering should provide some not-so-subtle visual clues about what is
> nearby, or important. Prepending these links to the top of a long list
> without even changing the text formatting in my opinion doesn't handle this
> very well.

Point taken, coherent navigation is not a simple task. Maybe the first
set of navigations could be visually slightly different in some way?

> -john
> 
> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED] 
> Sent: Monday, February 23, 2004 11:24 AM
> To: Maven Developers List
> Subject: Re: [Fwd: Re: [commons-site] Alternate Horizontal Project
> Navigat

RE: [Fwd: Re: [commons-site] Alternate Horizontal Project Navigat ion]

2004-02-23 Thread CaseyJD
My only beef with the current style is what happens when you have tons of
sub-projects, as in the case of Jakarta Commons. When you start stacking
many different scopes of detail on top of one another down the left sidebar,
it becomes hard to differentiate between scope divisions. I know, the
headers should be a clue, but it does get a bit overwhelming... Maven's
plugins reference would have a similar problem, if it were constructed in
this way.

Another problem with the volume of information is that it tends to lead
off-screen, where scrolling to read destroys the coherence of the sidebar
information. Personally, I'd much rather have a dashboard at the top (where
applications, not just _web_ applications traditionally have a menubar)
where I can see the operations near at hand, like details of this project.
This may seem like replication of the top part of the sidebar, but it pops
out to the eye quite a bit more readily than a subsection of this gigantic
list on the left (all of the same font size, etc.).

Final note: The content area is what you define it to be. If you frame a
page properly, it will be obvious what is and is not the content area.
Top/Left are premium real estate because they naturally frame any page
content, so maybe shrinking the _huge_ logo at the top and/or allowing the
embedding of some navigation in that top 10% of the page (I'm guessing)
would help free up some space for the actual content. Another would be to
take a page from the Safari website, and allow the user to "hide" the
sidebar, in order to read the content.

I know that the Commons website isn't probably organized in the best
possible way wrt what is/isn't on the sidebar, but I definitely think the
site rendering should provide some not-so-subtle visual clues about what is
nearby, or important. Prepending these links to the top of a long list
without even changing the text formatting in my opinion doesn't handle this
very well.

-john

-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED] 
Sent: Monday, February 23, 2004 11:24 AM
To: Maven Developers List
Subject: Re: [Fwd: Re: [commons-site] Alternate Horizontal Project
Navigation]

On Mon, 2004-02-23 at 07:55, Mark R. Diggory wrote:
> I thought it'd be good to forward this onto you "Crazy Maven 
> Developers". What do you think about horizontal project navigation:
> 
> http://www.apache.org/~mdiggory/commons/math/userguide/index.html

What you have in the tabs across the top is akin to what I would like to
see as the first entries on the left in the navigation.

I honestly don't much like the tabs and like the navigation in the nav
bar on the left or in the breadcrumb bar. I think having navigation in
the body of the page with the content isn't a good thing.

I think people will naturally look to the upper left (as the majority of
people dealing with computer stuff use English as the primary language
which reads left to right) to find things of importance and that's where
I would honestly like to see the things of navigational importance go.

I've given up on trying to make the sites all look exactly the same as
far as colour and general style but I would really, really not like to
see each project start changing the navigation style. I realize the
currently generated site is lacking in terms of ease of use but I would
like to incorporate any ideas like you have into the standard xdoc
plugin so that the sites being generated remain functioning the same at
least in terms of navigational style.

> -Mark
> 
>  Original Message 
> 
> Ok I added the following:
> 
> 1.) first three navi levels stay the same height if content present or
not.
> 2.) nested custom project documentation menus under "About "
> (requires special formating (and menu/@type="tab" attribute to be
> visible there).
> 3.) disabled "Development Process" button (working on removing it).
> 
> As an example of three levels being filled:
> http://www.apache.org/~mdiggory/commons/math/userguide/index.html
> 
> -Mark
> 
> Tim O'Brien wrote:
> 
> > I think this helps.  Although the "About Math" tab should have a blank 
> > subtab for consistency.
> > 
> > ...now the left nav - it is s busy.
> > 
> > Tim
> > 
> > 
> > Mark R. Diggory wrote:
> > 
> >> I worked out the kinks on an alternate project navigation, please have 
> >> a look and comment:
> >>
> >> http://www.apache.org/~mdiggory/commons/math/project-info.html
> >>
> >> Pro's
> >>
> >> 1.) Navigation better integrated into page layout.
> >> 2.) Horizontal positioning at top of page more traditional for 
> >> navigation.
> >> 3.) Strong CSS control over look and feel, 0% javascript
> >> 4.) Clearly separates "Shared Commons Navigation" from "Individual 
> >> Project Navigation".
> >>
> >> Con's
> >>
> >> 1.) Limits number of items on a level to the width of the page
> >> (although it does provide "wrapping" when items are greater than
width).
> >>
> >> 2.) Currently limited to menus nested three levels deep.
> >> (but e

RE: [Fwd: Re: [commons-site] Alternate Horizontal Project Navigat ion]

2004-02-23 Thread CaseyJD
I like the idea of the blue bgcolor for non-focused tabs, but I'd also say
to use a lighter gray for the fg of those tabs (increases contrast and
readability). As for the pipes, it's a simple solution and seems very
effective on other sites.

One thing, though: I think the part that needs the most attention is that
tertiary nav (Overview, Statistics, etc.). It's not really contained by
anything visually (other than a rule < hr/ > ?), and would probably benefit
greatly from the piping, etc. or maybe some type of different font or
font-style, font-weight, etc.  I dunno exactly what I'm trying to do here
visually, only that it needs to stand out a little more. 

I played around a little in EditCSS, and thought this, combined with the
piping, might work:

div.bar ul.subnav2 {
z-index: 101;
background-color:#eee;
position:relative;
margin: 0px;
margin-top: 0px;
padding: 0px 0px 1px 50px;
/*padding: 1px 0px 3px 30px;*/
/*border-top:1px solid #fff;*/
border-bottom:1px solid #999;
height: 15px;
clear:both;
}

Please keep in mind that I'm infinitely better at critiquing other work than
producing my own when it comes to web interfacing. :)

Cheers,
John



-Original Message-
From: Mark R. Diggory [mailto:[EMAIL PROTECTED] 
Sent: Monday, February 23, 2004 11:02 AM
To: Maven Developers List
Subject: Re: [Fwd: Re: [commons-site] Alternate Horizontal Project
Navigation]

Can you make any recommendations on colors for tab background or fonts 
that would be better? I'm think of maybe using the "h1" background color 
for the active tabs (blue) with the "h2" class as the bgcolor for 
inactive tabs.

I also was going to use a css property to place a pipe delimiter between 
the menu options, I glad someone else recognized value in this as well.

-Mark

John Casey wrote:
> Personally, I like how it works with an umbrella project (Jakarta), but
> really don't like the current contrast of the menus. It's hard to read,
> and hard to visually pull out the link breaks. But I'd say it's really
> close to being a nice alternative.
> 
> Just my 2c.
> 
> -john
> 
> On Mon, 2004-02-23 at 07:55, Mark R. Diggory wrote:
> 
>>I thought it'd be good to forward this onto you "Crazy Maven 
>>Developers". What do you think about horizontal project navigation:
>>
>>http://www.apache.org/~mdiggory/commons/math/userguide/index.html
>>
>>-Mark
>>
>> Original Message 
>>
>>Ok I added the following:
>>
>>1.) first three navi levels stay the same height if content present or
not.
>>2.) nested custom project documentation menus under "About "
>>(requires special formating (and menu/@type="tab" attribute to be
>>visible there).
>>3.) disabled "Development Process" button (working on removing it).
>>
>>As an example of three levels being filled:
>>http://www.apache.org/~mdiggory/commons/math/userguide/index.html
>>
>>-Mark
>>
>>Tim O'Brien wrote:
>>
>>
>>>I think this helps.  Although the "About Math" tab should have a blank 
>>>subtab for consistency.
>>>
>>>...now the left nav - it is s busy.
>>>
>>>Tim
>>>
>>>
>>>Mark R. Diggory wrote:
>>>
>>>
I worked out the kinks on an alternate project navigation, please have 
a look and comment:

http://www.apache.org/~mdiggory/commons/math/project-info.html

Pro's

1.) Navigation better integrated into page layout.
2.) Horizontal positioning at top of page more traditional for 
navigation.
3.) Strong CSS control over look and feel, 0% javascript
4.) Clearly separates "Shared Commons Navigation" from "Individual 
Project Navigation".

Con's

1.) Limits number of items on a level to the width of the page
(although it does provide "wrapping" when items are greater than width).

2.) Currently limited to menus nested three levels deep.
(but easily extendable to more).
3.) Currently doesn't integrate custom project navigation.
(but could easily be adapted for such support, I had initially 
included it, but encountered small issues with merging two separate 
"menu sets").


I think its important to clearly separate the "Projects Navigation" 
from the overall shared "Commons Navigation", I believe positioning 
them in very separate locations of the site gives the user a much 
clearer path and ease in determining the level of the site they are 
within.

-Mark
>>>
>>>
>>>
>>>
>>>-
>>>To unsubscribe, e-mail: [EMAIL PROTECTED]
>>>For additional commands, e-mail: [EMAIL PROTECTED]
>>>
>>
>>-- 
>>Mark Diggory
>>Software Developer
>>Harvard MIT Data Center
>>http://www.hmdc.harvard.edu
>>
>>-
>>To unsubscribe, e-mail: [EMAIL PROTECTED]
>>For additional commands, e-mail: [EMAIL PROTECTED]

-- 
Mark Diggory
Software Developer
Harvard MIT Data Cente

Re: [Fwd: Re: [commons-site] Alternate Horizontal Project Navigation]

2004-02-23 Thread Jason van Zyl
On Mon, 2004-02-23 at 07:55, Mark R. Diggory wrote:
> I thought it'd be good to forward this onto you "Crazy Maven 
> Developers". What do you think about horizontal project navigation:
> 
> http://www.apache.org/~mdiggory/commons/math/userguide/index.html

What you have in the tabs across the top is akin to what I would like to
see as the first entries on the left in the navigation.

I honestly don't much like the tabs and like the navigation in the nav
bar on the left or in the breadcrumb bar. I think having navigation in
the body of the page with the content isn't a good thing.

I think people will naturally look to the upper left (as the majority of
people dealing with computer stuff use English as the primary language
which reads left to right) to find things of importance and that's where
I would honestly like to see the things of navigational importance go.

I've given up on trying to make the sites all look exactly the same as
far as colour and general style but I would really, really not like to
see each project start changing the navigation style. I realize the
currently generated site is lacking in terms of ease of use but I would
like to incorporate any ideas like you have into the standard xdoc
plugin so that the sites being generated remain functioning the same at
least in terms of navigational style.

> -Mark
> 
>  Original Message 
> 
> Ok I added the following:
> 
> 1.) first three navi levels stay the same height if content present or not.
> 2.) nested custom project documentation menus under "About "
> (requires special formating (and menu/@type="tab" attribute to be
> visible there).
> 3.) disabled "Development Process" button (working on removing it).
> 
> As an example of three levels being filled:
> http://www.apache.org/~mdiggory/commons/math/userguide/index.html
> 
> -Mark
> 
> Tim O'Brien wrote:
> 
> > I think this helps.  Although the "About Math" tab should have a blank 
> > subtab for consistency.
> > 
> > ...now the left nav - it is s busy.
> > 
> > Tim
> > 
> > 
> > Mark R. Diggory wrote:
> > 
> >> I worked out the kinks on an alternate project navigation, please have 
> >> a look and comment:
> >>
> >> http://www.apache.org/~mdiggory/commons/math/project-info.html
> >>
> >> Pro's
> >>
> >> 1.) Navigation better integrated into page layout.
> >> 2.) Horizontal positioning at top of page more traditional for 
> >> navigation.
> >> 3.) Strong CSS control over look and feel, 0% javascript
> >> 4.) Clearly separates "Shared Commons Navigation" from "Individual 
> >> Project Navigation".
> >>
> >> Con's
> >>
> >> 1.) Limits number of items on a level to the width of the page
> >> (although it does provide "wrapping" when items are greater than width).
> >>
> >> 2.) Currently limited to menus nested three levels deep.
> >> (but easily extendable to more).
> >> 3.) Currently doesn't integrate custom project navigation.
> >> (but could easily be adapted for such support, I had initially 
> >> included it, but encountered small issues with merging two separate 
> >> "menu sets").
> >>
> >>
> >> I think its important to clearly separate the "Projects Navigation" 
> >> from the overall shared "Commons Navigation", I believe positioning 
> >> them in very separate locations of the site gives the user a much 
> >> clearer path and ease in determining the level of the site they are 
> >> within.
> >>
> >> -Mark
> > 
> > 
> > 
> > 
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> > 
> 
> -- 
> Mark Diggory
> Software Developer
> Harvard MIT Data Center
> http://www.hmdc.harvard.edu
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]

-- 
jvz.

Jason van Zyl
[EMAIL PROTECTED]
http://maven.apache.org

happiness is like a butterfly: the more you chase it, the more it will
elude you, but if you turn your attention to other things, it will come
and sit softly on your shoulder ...

 -- Thoreau 


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



Re: [Fwd: Re: [commons-site] Alternate Horizontal Project Navigation]

2004-02-23 Thread Mark R. Diggory
Can you make any recommendations on colors for tab background or fonts 
that would be better? I'm think of maybe using the "h1" background color 
for the active tabs (blue) with the "h2" class as the bgcolor for 
inactive tabs.

I also was going to use a css property to place a pipe delimiter between 
the menu options, I glad someone else recognized value in this as well.

-Mark

John Casey wrote:
Personally, I like how it works with an umbrella project (Jakarta), but
really don't like the current contrast of the menus. It's hard to read,
and hard to visually pull out the link breaks. But I'd say it's really
close to being a nice alternative.
Just my 2c.

-john

On Mon, 2004-02-23 at 07:55, Mark R. Diggory wrote:

I thought it'd be good to forward this onto you "Crazy Maven 
Developers". What do you think about horizontal project navigation:

http://www.apache.org/~mdiggory/commons/math/userguide/index.html

-Mark

 Original Message 

Ok I added the following:

1.) first three navi levels stay the same height if content present or not.
2.) nested custom project documentation menus under "About "
(requires special formating (and menu/@type="tab" attribute to be
visible there).
3.) disabled "Development Process" button (working on removing it).
As an example of three levels being filled:
http://www.apache.org/~mdiggory/commons/math/userguide/index.html
-Mark

Tim O'Brien wrote:


I think this helps.  Although the "About Math" tab should have a blank 
subtab for consistency.

...now the left nav - it is s busy.

Tim

Mark R. Diggory wrote:


I worked out the kinks on an alternate project navigation, please have 
a look and comment:

http://www.apache.org/~mdiggory/commons/math/project-info.html

Pro's

1.) Navigation better integrated into page layout.
2.) Horizontal positioning at top of page more traditional for 
navigation.
3.) Strong CSS control over look and feel, 0% javascript
4.) Clearly separates "Shared Commons Navigation" from "Individual 
Project Navigation".

Con's

1.) Limits number of items on a level to the width of the page
(although it does provide "wrapping" when items are greater than width).
2.) Currently limited to menus nested three levels deep.
(but easily extendable to more).
3.) Currently doesn't integrate custom project navigation.
(but could easily be adapted for such support, I had initially 
included it, but encountered small issues with merging two separate 
"menu sets").

I think its important to clearly separate the "Projects Navigation" 
from the overall shared "Commons Navigation", I believe positioning 
them in very separate locations of the site gives the user a much 
clearer path and ease in determining the level of the site they are 
within.

-Mark




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Mark Diggory
Software Developer
Harvard MIT Data Center
http://www.hmdc.harvard.edu
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Mark Diggory
Software Developer
Harvard MIT Data Center
http://www.hmdc.harvard.edu
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: [Fwd: Re: [commons-site] Alternate Horizontal Project Navigation]

2004-02-23 Thread John Casey
Personally, I like how it works with an umbrella project (Jakarta), but
really don't like the current contrast of the menus. It's hard to read,
and hard to visually pull out the link breaks. But I'd say it's really
close to being a nice alternative.

Just my 2c.

-john

On Mon, 2004-02-23 at 07:55, Mark R. Diggory wrote:
> I thought it'd be good to forward this onto you "Crazy Maven 
> Developers". What do you think about horizontal project navigation:
> 
> http://www.apache.org/~mdiggory/commons/math/userguide/index.html
> 
> -Mark
> 
>  Original Message 
> 
> Ok I added the following:
> 
> 1.) first three navi levels stay the same height if content present or not.
> 2.) nested custom project documentation menus under "About "
> (requires special formating (and menu/@type="tab" attribute to be
> visible there).
> 3.) disabled "Development Process" button (working on removing it).
> 
> As an example of three levels being filled:
> http://www.apache.org/~mdiggory/commons/math/userguide/index.html
> 
> -Mark
> 
> Tim O'Brien wrote:
> 
> > I think this helps.  Although the "About Math" tab should have a blank 
> > subtab for consistency.
> > 
> > ...now the left nav - it is s busy.
> > 
> > Tim
> > 
> > 
> > Mark R. Diggory wrote:
> > 
> >> I worked out the kinks on an alternate project navigation, please have 
> >> a look and comment:
> >>
> >> http://www.apache.org/~mdiggory/commons/math/project-info.html
> >>
> >> Pro's
> >>
> >> 1.) Navigation better integrated into page layout.
> >> 2.) Horizontal positioning at top of page more traditional for 
> >> navigation.
> >> 3.) Strong CSS control over look and feel, 0% javascript
> >> 4.) Clearly separates "Shared Commons Navigation" from "Individual 
> >> Project Navigation".
> >>
> >> Con's
> >>
> >> 1.) Limits number of items on a level to the width of the page
> >> (although it does provide "wrapping" when items are greater than width).
> >>
> >> 2.) Currently limited to menus nested three levels deep.
> >> (but easily extendable to more).
> >> 3.) Currently doesn't integrate custom project navigation.
> >> (but could easily be adapted for such support, I had initially 
> >> included it, but encountered small issues with merging two separate 
> >> "menu sets").
> >>
> >>
> >> I think its important to clearly separate the "Projects Navigation" 
> >> from the overall shared "Commons Navigation", I believe positioning 
> >> them in very separate locations of the site gives the user a much 
> >> clearer path and ease in determining the level of the site they are 
> >> within.
> >>
> >> -Mark
> > 
> > 
> > 
> > 
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> > 
> 
> -- 
> Mark Diggory
> Software Developer
> Harvard MIT Data Center
> http://www.hmdc.harvard.edu
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
-- 
John Casey
[EMAIL PROTECTED]
CommonJava Open Components Project
http://www.commonjava.org


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



[Fwd: Re: [commons-site] Alternate Horizontal Project Navigation]

2004-02-23 Thread Mark R. Diggory
I thought it'd be good to forward this onto you "Crazy Maven 
Developers". What do you think about horizontal project navigation:

http://www.apache.org/~mdiggory/commons/math/userguide/index.html

-Mark

 Original Message 

Ok I added the following:

1.) first three navi levels stay the same height if content present or not.
2.) nested custom project documentation menus under "About "
(requires special formating (and menu/@type="tab" attribute to be
visible there).
3.) disabled "Development Process" button (working on removing it).
As an example of three levels being filled:
http://www.apache.org/~mdiggory/commons/math/userguide/index.html
-Mark

Tim O'Brien wrote:

I think this helps.  Although the "About Math" tab should have a blank 
subtab for consistency.

...now the left nav - it is s busy.

Tim

Mark R. Diggory wrote:

I worked out the kinks on an alternate project navigation, please have 
a look and comment:

http://www.apache.org/~mdiggory/commons/math/project-info.html

Pro's

1.) Navigation better integrated into page layout.
2.) Horizontal positioning at top of page more traditional for 
navigation.
3.) Strong CSS control over look and feel, 0% javascript
4.) Clearly separates "Shared Commons Navigation" from "Individual 
Project Navigation".

Con's

1.) Limits number of items on a level to the width of the page
(although it does provide "wrapping" when items are greater than width).
2.) Currently limited to menus nested three levels deep.
(but easily extendable to more).
3.) Currently doesn't integrate custom project navigation.
(but could easily be adapted for such support, I had initially 
included it, but encountered small issues with merging two separate 
"menu sets").

I think its important to clearly separate the "Projects Navigation" 
from the overall shared "Commons Navigation", I believe positioning 
them in very separate locations of the site gives the user a much 
clearer path and ease in determining the level of the site they are 
within.

-Mark




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Mark Diggory
Software Developer
Harvard MIT Data Center
http://www.hmdc.harvard.edu
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


--
Mark Diggory
Software Developer
Harvard MIT Data Center
http://www.hmdc.harvard.edu
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


[jira] Updated: (MAVEN-1171) wsdl2java plugin

2004-02-23 Thread jira
The following issue has been updated:

Updater: Dominik Dahlem (mailto:[EMAIL PROTECTED])
   Date: Mon, 23 Feb 2004 5:40 AM
Comment:
an initial version of the wsdl2java plugin. It has targets to generate .java files 
from wsdl definitions, can generate the testcases, and compile all java files and 
testcases.
The plugin can take a single URL to a .wsdl file. As a default it points to 
${maven.src.dir}/wsdl directory and takes all .wsdl files in them to generate the java 
files.
ToDo:
 * do not generate the .java files if the wsdl definition has not been updated.
 * implement the java2wsdl goal.
 * documentation.
Changes:
 Attachment changed to maven-wsdl2java-plugin.tar.gz
-
For a full history of the issue, see:

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

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

Here is an overview of the issue:
-
Key: MAVEN-1171
Summary: wsdl2java plugin
   Type: New Feature

 Status: Unassigned
   Priority: Minor

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven

   Assignee: 
   Reporter: Dominik Dahlem

Created: Mon, 23 Feb 2004 5:29 AM
Updated: Mon, 23 Feb 2004 5:40 AM
Environment: all

Description:
Implement a wsdl2java plugin which uses the axis-ant.jar tasks.


-
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] Created: (MAVEN-1171) wsdl2java plugin

2004-02-23 Thread jira
Message:

  A new issue has been created in JIRA.

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

Here is an overview of the issue:
-
Key: MAVEN-1171
Summary: wsdl2java plugin
   Type: New Feature

 Status: Unassigned
   Priority: Minor

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven

   Assignee: 
   Reporter: Dominik Dahlem

Created: Mon, 23 Feb 2004 5:29 AM
Updated: Mon, 23 Feb 2004 5:29 AM
Environment: all

Description:
Implement a wsdl2java plugin which uses the axis-ant.jar tasks.


-
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]