Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove outdated IDE, JIRA and Tomcat references [SPR-7521] #12179

Closed
spring-projects-issues opened this issue Sep 2, 2010 · 4 comments
Closed

Remove outdated IDE, JIRA and Tomcat references [SPR-7521] #12179

spring-projects-issues opened this issue Sep 2, 2010 · 4 comments
Assignees
Labels
type: documentation
Milestone

Comments

@spring-projects-issues
Copy link
Collaborator

@spring-projects-issues spring-projects-issues commented Sep 2, 2010

Frank Adcock opened SPR-7521 and commented

The links provided in the Reference Documentation / Spring Java Application Framework 3.0 to the SpringIDE web pages are incorrect.

The errors are in Appendix C.3 Setting Up Your IDE/ Setting Up Eclipse/Section 3.

http://springide.org/blog/ is incorrect.

http://springide.org/project/wiki/SpringideInstall is also incorrect.


Affects: 3.0.4

Referenced from: commits ecf23ff, 08fb613, f1f1c4c

@spring-projects-issues
Copy link
Collaborator Author

@spring-projects-issues spring-projects-issues commented Sep 3, 2010

Chris Beams commented

Thanks, Frank.

@spring-projects-issues
Copy link
Collaborator Author

@spring-projects-issues spring-projects-issues commented Sep 9, 2010

Chris Beams commented

Not only are the links above wrong, but the entire section is out of date, including:

  • references to Eclipse 3.2
  • need to install WTP a la carte
  • no mention of STS
  • links to old atlassian issue tracker
  • IDEA documentation is probably outdated as well

We should revisit the entire section for 3.1. In the meantime, I've commented it out, as confusion is worse than nothing.

@Christian, is this something your team can look at doing? Please reassign as you see fit.

For reference, here are all the places in the reference docs that we currently make mention of STS. These sections should probably refer to this one once it's been overhauled:

spring-framework-reference/src>$ grep -i -B3 -A3 'tool.\?suite' *.xml
beans-annotation-config.xml-      to be used in a non-invasive way, without touching the target components
beans-annotation-config.xml-      source code and that in terms of tooling, all configuration styles are
beans-annotation-config.xml-      supported by the <ulink url="http://www.springsource.com/products/sts"
beans-annotation-config.xml:      >SpringSource Tool Suite</ulink>.</para>
beans-annotation-config.xml-  </sidebar>
beans-annotation-config.xml-
beans-annotation-config.xml-  <para>An alternative to XML setups is provided by annotation-based
--
beans-java.xml-            <literal>@Autowired AccountRepository</literal> bean is declared?
beans-java.xml-            It's not explicit in the code, and this may be just fine. Remember
beans-java.xml-            that the <ulink url="http://www.springsource.com/products/sts"
beans-java.xml:            >SpringSource Tool Suite</ulink> provides tooling that can render
beans-java.xml-            graphs showing how everything is wired up - that may be all you
beans-java.xml-            need. Also, your Java IDE can easily find all declarations and uses
beans-java.xml-            of the <literal>AccountRepository</literal> type, and will quickly
--
beans.xml-      J2EE web descriptor XML in the <literal>web.xml</literal> file of the
beans.xml-      application will typically suffice (see <xref linkend="context-create"/>).
beans.xml-      If you are using the <ulink url="http://www.springsource.com/produts/sts"
beans.xml:      >SpringSource Tool Suite</ulink> Eclipse-powered development environment
beans.xml-      or <ulink url="http://www.springsource.org/roo">Spring Roo</ulink> this
beans.xml-      boilerplate configuration can be easily created with few mouse clicks or
beans.xml-      keystrokes.</para>
--
expressions.xml-    expression language that can be used across all the products in the Spring
expressions.xml-    portfolio. Its language features are driven by the requirements of the
expressions.xml-    projects in the Spring portfolio, including tooling requirements for code
expressions.xml:    completion support within the eclipse based SpringSource Tool Suite. That
expressions.xml-    said, SpEL is based on a technology agnostic API allowing other
expressions.xml-    expression language implementations to be integrated should the need
expressions.xml-    arise.</para>
--
new-in-3.xml-      are driven by the requirements of the projects in the Spring portfolio,
new-in-3.xml-      including tooling requirements for code completion support within the
new-in-3.xml-      Eclipse based <ulink url="http://www.springsource.com/products/sts">SpringSource
new-in-3.xml:      Tool Suite</ulink>.</para>
new-in-3.xml-
new-in-3.xml-      <para>The following is an example of how the Expression Language can be
new-in-3.xml-      used to configure some properties of a database setup <programlisting

@spring-projects-issues
Copy link
Collaborator Author

@spring-projects-issues spring-projects-issues commented Aug 12, 2014

Juergen Hoeller commented

I've cleaned up some remaining outdated references for 4.1 GA / 4.0.7 now. Most of it got addressed in some form before.

Juergen

@spring-projects-issues
Copy link
Collaborator Author

@spring-projects-issues spring-projects-issues commented Aug 12, 2014

Juergen Hoeller commented

Being at it, I've also removed outdated Tomcat 5.x references. We were still explaining how to work around a pre-5.5.20 Tomcat bug...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: documentation
Projects
None yet
Development

No branches or pull requests

2 participants