Re: xdoc generating non relative paths? or ignoring base...

[Ben Walding]

What version of Maven?

Make sure your navigation links start with / as there is a hole in the 
tests which means that it can get confused if your links don't start 
with / or one of the other special tags (site or absolute).  Your link 
should look like <item href="/foo.html" name="Foot"/>.  Maven will 
generate the appropriate link depending on the page you are viewing.

If you are doing that...

Then are you using cvs head?

I recently moved most of the navigation handling into DVSLPathTool and 
added a series of test cases.  If you can find out how you are getting 
past the test cases that would make life easier for me (always a plus!). 
(Add some System.out.printlns to calculateLink on 
src/org/apache/maven/DVSLPathTool.java)

Cheers,

Ben

Paulo Silveira wrote:

hi all

I am generating maven site, and all navigation links gets to /foo.html.
1beta8 generated ./foo.html, or am not configuring something?
------------------------
Paulo Silveira
http://www.paulo.com.br/
http://www.guj.com.br/
 

-----Original Message-----
From: Ben Walding [mailto:[EMAIL PROTECTED] 
Sent: quinta-feira, 13 de março de 2003 21:07
To: Turbine Maven Users List
Subject: Re: jar manifest extension dependency list

I have raised MAVEN-334 to cover these issues.

- see jira.werken.com

Vincenz Braun wrote:

   

Hello,

i do not know whether this is the right place for this issue,
but i do not know the component responsible for creating
the manifest files in maven.
I really appreciate that maven builds jars with version 
     

information in 
   

the manifest. But this is not conforming to the extension versioning 
specification.

1. Why not using the correct attribute name for extensions?

Example from the spec:

Extension-Name: javax.help
Specification-Vendor: Sun Microsystems, Inc
Specification-Version: 1.0 
Implementation-Vendor-Id: com.sun 
Implementation-Vendor: Sun Microsystems, Inc 
Implementation-Version: 1.0 

Maven uses the attribute name Name instead of Extension-Name.

2. Why not include dependency information?

Example from the spec:

Extension-List: javahelp java3d
javahelp-Extension-Name: javax.help 
javahelp-Specification-Version: 1.0 
javahelp-Implementation-Version: 1.0.3 
javahelp-Implementation-Vendor-Id: com.sun 
javahelp-Implementation-URL:
http://java.sun.com/products/stdext/javahelp.jar 
java3d-Extension-Name: javax.3d 
java3d-Specification-Version: 1.0 
java3d-Implementation-Version: 1.2.1 
java3d-Implementation-Vendor-Id: com.sun 
java3d-Implementation-URL: 
     

http://java.sun.com/products/stdext/java3d.jar 
   

3. Why not 
     

include download URL locations?
   

See example above.

Can someone tell me the component responsible for creating 
     

the manifest 
   

files in maven?

Is this a known issue (I did not find it on the user mailing list)?
Can this feature be added in future releases?
Thanks,
Vincenz
---------------------------------------------------------------------
To unsubscribe, e-mail: 
[EMAIL PROTECTED]
For additional commands, e-mail: 
     

[EMAIL PROTECTED]
   



     

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



   



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



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