You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by GitBox <gi...@apache.org> on 2021/06/21 10:38:49 UTC

[GitHub] [jena-site] rvesse opened a new pull request #60: Correct Javadoc .asf.yaml publishing

rvesse opened a new pull request #60:
URL: https://github.com/apache/jena-site/pull/60


   The subdir path needs to be the full path in the destination branch which is not the same as the path as it appears in the final website i.e. the leading content/ was missing
   
   Note that I verified this was the case by setting up a staging profile and you can see that this is working at https://jena.staged.apache.org/documentation/javadoc/jena/index.html


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [jena-site] afs removed a comment on pull request #60: Correct Javadoc .asf.yaml publishing

Posted by GitBox <gi...@apache.org>.
afs removed a comment on pull request #60:
URL: https://github.com/apache/jena-site/pull/60#issuecomment-864955911


   But it works currently with `subdir: documentation/javadoc` when `/source/documentation/javadoc` exists in `main`.
   
   Being git (no empty directories), there has to be a dummy file in `documentation/javadoc/` (called "file" in `main`).
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [jena-site] afs commented on pull request #60: Correct Javadoc .asf.yaml publishing

Posted by GitBox <gi...@apache.org>.
afs commented on pull request #60:
URL: https://github.com/apache/jena-site/pull/60#issuecomment-864955911


   But it works currently with `subdir: documentation/javadoc` when `/source/documentation/javadoc` exists in `main`.
   
   Being git (no empty directories), there has to be a dummy file in `documentation/javadoc/` (called "file" in `main`).
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [jena-site] afs removed a comment on pull request #60: Correct Javadoc .asf.yaml publishing

Posted by GitBox <gi...@apache.org>.
afs removed a comment on pull request #60:
URL: https://github.com/apache/jena-site/pull/60#issuecomment-864955911


   But it works currently with `subdir: documentation/javadoc` when `/source/documentation/javadoc` exists in `main`.
   
   Being git (no empty directories), there has to be a dummy file in `documentation/javadoc/` (called "file" in `main`).
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [jena-site] rvesse commented on pull request #60: Correct Javadoc .asf.yaml publishing

Posted by GitBox <gi...@apache.org>.
rvesse commented on pull request #60:
URL: https://github.com/apache/jena-site/pull/60#issuecomment-864976614


   All the documented examples I've seen from ASF Infrastructure don't use a leading `/` so I've just followed what those have done


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [jena-site] afs commented on pull request #60: Correct Javadoc .asf.yaml publishing

Posted by GitBox <gi...@apache.org>.
afs commented on pull request #60:
URL: https://github.com/apache/jena-site/pull/60#issuecomment-864955911


   But it works currently with `subdir: documentation/javadoc` when `/source/documentation/javadoc` exists in `main`.
   
   Being git (no empty directories), there has to be a dummy file in `documentation/javadoc/` (called "file" in `main`).
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [jena-site] rvesse commented on pull request #60: Correct Javadoc .asf.yaml publishing

Posted by GitBox <gi...@apache.org>.
rvesse commented on pull request #60:
URL: https://github.com/apache/jena-site/pull/60#issuecomment-864976614


   All the documented examples I've seen from ASF Infrastructure don't use a leading `/` so I've just followed what those have done


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [jena-site] rvesse merged pull request #60: Correct Javadoc .asf.yaml publishing

Posted by GitBox <gi...@apache.org>.
rvesse merged pull request #60:
URL: https://github.com/apache/jena-site/pull/60


   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [jena-site] afs commented on pull request #60: Correct Javadoc .asf.yaml publishing

Posted by GitBox <gi...@apache.org>.
afs commented on pull request #60:
URL: https://github.com/apache/jena-site/pull/60#issuecomment-865860559


   Good reason to keep it as it is!


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org