JSPWiki
  1. JSPWiki
  2. JSPWIKI-731

http://www.jspwiki.org/ reference in 6 files

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Done
    • Affects Version/s: Graduating
    • Fix Version/s: Graduating, 2.10
    • Component/s: None
    • Labels:
      None

      Description

      in the following files is still the reference to http://www.jspwiki.org/
      should be the future Apache TLP-page

      templates\default\EditTemplate.jsp
      Error.jsp
      WEB-INF\jspwiki.properties
      templates\default\UploadTemplate.jsp
      templates\default\ViewTemplate.jsp
      WEB-INF\web.xml

        Activity

        Hide
        Juan Pablo Santos Rodríguez added a comment -

        transitioning resolved to closed on pending graduating-version issues, in order to close that milestone on JIRA.

        Show
        Juan Pablo Santos Rodríguez added a comment - transitioning resolved to closed on pending graduating-version issues, in order to close that milestone on JIRA.
        Hide
        Juan Pablo Santos Rodríguez added a comment -

        completed on 2.10.0-svn-65

        Show
        Juan Pablo Santos Rodríguez added a comment - completed on 2.10.0-svn-65
        Hide
        Florian Holeczek added a comment -

        I've just committed all changes that made sense to me for a graduation release in v2.9.0-incubating-9 (svn rev 1364362).

        Show
        Florian Holeczek added a comment - I've just committed all changes that made sense to me for a graduation release in v2.9.0-incubating-9 (svn rev 1364362).
        Hide
        Janne Jalkanen added a comment -

        The idea behind doc.jspwiki.org was to provide version-specific documentation that could be simply downloaded and zipped together with the release distribution. It's a separate wiki because it's cleaner that way; otherwise the docs get awfully complicated with "This feature is only available from 2.2 to 2.4" and "This document is obsolete for v2.6 onwards, please check..." because you would still need to keep the references alive, otherwise there would be no online documentation for older versions...

        I can keep jspwiki.org still up for some time; it's not a question of server resources but more about legal stuff.

        Show
        Janne Jalkanen added a comment - The idea behind doc.jspwiki.org was to provide version-specific documentation that could be simply downloaded and zipped together with the release distribution. It's a separate wiki because it's cleaner that way; otherwise the docs get awfully complicated with "This feature is only available from 2.2 to 2.4" and "This document is obsolete for v2.6 onwards, please check..." because you would still need to keep the references alive, otherwise there would be no online documentation for older versions... I can keep jspwiki.org still up for some time; it's not a question of server resources but more about legal stuff.
        Hide
        Florian Holeczek added a comment -

        Hi all,

        I was thinking of making jspwiki.org read-only for now anyway, so stuff could be moved fairly trivially.

        @Janne: That's a good idea! Regarding redirection, domain/server movement etc., could that wait a bit, until graduation is through? Can't be that long anymore.

        Regarding the domain name references, here's my proposal. I'm thinking of three sorts of references:

        a) technical references, like XML namespace references
        b) project-administration-specific references, like links to the project page, references to mailing list etc.
        c) content-specific references. These are mainly references to online documentation

        I'd like to change a) to Apache now, b) to Apache now and leave c) at jspwiki.org, reorganizing it later on.

        Regarding Apache (a and b), the question is which link to choose:
        Can incubator.apache.org/jspwiki be forwarded to the tlp address later on? Regarding a), does it make sense to first choose i.a.o/j and later j.a.o? I guess not.

        Regarding c), I think it makes sense to discuss and define the structure of (doc.)jspwiki.org, and only afterwards adapt the links to it. I for one don't really get the concept behind the current doc.jspwiki.org, which doesn't mean it's bad - I just think it should be made explicit.

        Regards
        Florian

        Show
        Florian Holeczek added a comment - Hi all, I was thinking of making jspwiki.org read-only for now anyway, so stuff could be moved fairly trivially. @Janne: That's a good idea! Regarding redirection, domain/server movement etc., could that wait a bit, until graduation is through? Can't be that long anymore. Regarding the domain name references, here's my proposal. I'm thinking of three sorts of references: a) technical references, like XML namespace references b) project-administration-specific references, like links to the project page, references to mailing list etc. c) content-specific references. These are mainly references to online documentation I'd like to change a) to Apache now , b) to Apache now and leave c) at jspwiki.org, reorganizing it later on. Regarding Apache (a and b), the question is which link to choose: Can incubator.apache.org/jspwiki be forwarded to the tlp address later on? Regarding a), does it make sense to first choose i.a.o/j and later j.a.o? I guess not. Regarding c), I think it makes sense to discuss and define the structure of (doc.)jspwiki.org, and only afterwards adapt the links to it. I for one don't really get the concept behind the current doc.jspwiki.org, which doesn't mean it's bad - I just think it should be made explicit. Regards Florian
        Hide
        Janne Jalkanen added a comment -

        I can set up a redirection from www.jspwiki.org/(.*) to jspwiki.apache.org/wiki/$1 for example. I was thinking of making jspwiki.org read-only for now anyway, so stuff could be moved fairly trivially.

        Show
        Janne Jalkanen added a comment - I can set up a redirection from www.jspwiki.org/(.*) to jspwiki.apache.org/wiki/$1 for example. I was thinking of making jspwiki.org read-only for now anyway, so stuff could be moved fairly trivially.
        Hide
        Florian Holeczek added a comment -

        We need to decide what to do here before releasing the third RC...

        My mail on the list:

        JSPWIKI-731 is listing some references in the code to jspwiki.org and proposes to replace them with jspwiki.apache.org.

        Do we really want to replace them?
        Do we maybe have to replace them in order to graduate?
        Are there any implications regarding the core system as a whole on the one hand, and third party software like plugins etc. on the other hand?

        Maybe making a difference between code-wise links and documentation links makes sense: code goes to jspwiki.apache.org, documentation goes to jspwiki.org.

        Juan Pablos answer:

        I'd better let them as they are now, at least until we graduate, to avoid
        having to change the domains twice.. Regarding the occurrences noted at
        JSPWIKI-731, I think it make sense to change them, they are either
        references to the "official" site or xmnls namespaces. For any other cases,
        I'd leave them pointing to jspwiki.org.

        Show
        Florian Holeczek added a comment - We need to decide what to do here before releasing the third RC... My mail on the list: — JSPWIKI-731 is listing some references in the code to jspwiki.org and proposes to replace them with jspwiki.apache.org. Do we really want to replace them? Do we maybe have to replace them in order to graduate? Are there any implications regarding the core system as a whole on the one hand, and third party software like plugins etc. on the other hand? Maybe making a difference between code-wise links and documentation links makes sense: code goes to jspwiki.apache.org, documentation goes to jspwiki.org. — Juan Pablos answer: — I'd better let them as they are now, at least until we graduate, to avoid having to change the domains twice.. Regarding the occurrences noted at JSPWIKI-731 , I think it make sense to change them, they are either references to the "official" site or xmnls namespaces. For any other cases, I'd leave them pointing to jspwiki.org. —
        Hide
        Florian Holeczek added a comment -

        Hi all,

        as far as I could see, all old Tomcat links have been corrected now.

        However, the main issue here are references to jspwiki.org. Apart from the named ones, there are many more in the wikipages.

        Do we really want to replace them?
        Do we maybe have to replace them in order to graduate?
        Are there any implications regarding the core system as a whole on the one hand, and third party software like plugins etc. on the other hand?

        Regards
        Florian

        Show
        Florian Holeczek added a comment - Hi all, as far as I could see, all old Tomcat links have been corrected now. However, the main issue here are references to jspwiki.org. Apart from the named ones, there are many more in the wikipages. Do we really want to replace them? Do we maybe have to replace them in order to graduate? Are there any implications regarding the core system as a whole on the one hand, and third party software like plugins etc. on the other hand? Regards Florian
        Hide
        fpientka added a comment -

        sorry harry there are still two further links to correct
        1) Install Tomcat from http://jakarta.apache.org/ (or any other servlet
        container)
        First, install a JSP engine and a web server. You can download Tomcat
        from http://jakarta.apache.org/tomcat/.
        and perhapse for
        JSPWiki authors can be contacted on the jspwiki-users mailing list.
        You can see the instructions on http://www.jspwiki.org/wiki/JSPWikiMailingList.
        Mailing list dev jspwiki-dev@incubator.apache.org
        . user jspwiki-user@incubator.apache.org
        . commits jspwiki-commits@incubator.apache.org

        Show
        fpientka added a comment - sorry harry there are still two further links to correct 1) Install Tomcat from http://jakarta.apache.org/ (or any other servlet container) First, install a JSP engine and a web server. You can download Tomcat from http://jakarta.apache.org/tomcat/ . and perhapse for JSPWiki authors can be contacted on the jspwiki-users mailing list. You can see the instructions on http://www.jspwiki.org/wiki/JSPWikiMailingList . Mailing list dev jspwiki-dev@incubator.apache.org . user jspwiki-user@incubator.apache.org . commits jspwiki-commits@incubator.apache.org
        Hide
        Harry Metske added a comment -

        The tomcat links in README have been corrected in both 2.8 and 2.9.

        Thanks,
        Harry

        Show
        Harry Metske added a comment - The tomcat links in README have been corrected in both 2.8 and 2.9. Thanks, Harry
        Hide
        fpientka added a comment -

        In Readme link should be changed from http://jakarta.apache.org/tomcat to http://tomcat.apache.org/ and whe available
        The rest of the documentation is at http://doc.jspwiki.org/2.8/ to http://jspwiki.apache.org

        Show
        fpientka added a comment - In Readme link should be changed from http://jakarta.apache.org/tomcat to http://tomcat.apache.org/ and whe available The rest of the documentation is at http://doc.jspwiki.org/2.8/ to http://jspwiki.apache.org

          People

          • Assignee:
            Unassigned
            Reporter:
            fpientka
          • Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development