[ 
https://issues.apache.org/jira/browse/SLING-1539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alison Heimoz updated SLING-1539:
---------------------------------

    Description: 
http://sling.apache.org/site/getting-and-building-sling.html

1. Would recommend separating installation with / without Eclipse a bit more 
clearly. Encourage newbie's to get the basic example (using curl) working first.
    To quote Bertrand:
        Note that Eclipse is not required at all to work with Sling.
        The minimal setup for building, running and modifying the Sling code is 
a JVM, Maven and any text editor.
        Eclipse or another IDE is convenient, but not required, and especially 
not for kicking Sling's tyres - we might need to be clearer about that
        on our website.
2. Would it be possible to provide links for  "Maven SCM handler for Subclipse" 
or the "Maven SCM handler for Subversive"?
3. Environment Variable Space -> Problem / Platform / Fix
    The text under Fix further describes the problem - not (explicitly) tell 
the user how to fix the issue.
4. Some typos...
5. The section "Simple way to develop new bundle in Eclipse for Sling" 
recommends "Start by copying and adapting an existing Sling pom.xml (eg. the 
pom.xml from the espblog sample)". 
    If so, the espblog example should be updated to set something like: 
        <Sling-Initial-Content>
            initial-content;overwrite:=true;uninstall:=true
        </Sling-Initial-Content>
    And would it be advisable to tell them to remove the <scm> section while 
learning?

  was:
http://sling.apache.org/site/getting-and-building-sling.html

1. Would recommend separating installation with / without Eclipse a bit more 
clearly. Encourage newbie's to get the basic example (using curl) working first.
    To quote Bertrand:
        Note that Eclipse is not required at all to work with Sling.
        The minimal setup for building, running and modifying the Sling code is 
a JVM, Maven and any text editor.
        Eclipse or another IDE is convenient, but not required, and especially 
not for kicking Sling's tyres - we might need to be clearer about that
        on our website.
2. Would it be possible to provide links for  "Maven SCM handler for Subclipse" 
or the "Maven SCM handler for Subversive"?
3. Environment Variable Space -> Problem / Platform / Fix
    The text under Fix further describes the problem - not (explicitly) tell 
the user how to fix the issue.
4. Some typos...

       Priority: Minor  (was: Major)

> Getting and Building Sling
> --------------------------
>
>                 Key: SLING-1539
>                 URL: https://issues.apache.org/jira/browse/SLING-1539
>             Project: Sling
>          Issue Type: Improvement
>          Components: Documentation
>            Reporter: Alison Heimoz
>            Priority: Minor
>
> http://sling.apache.org/site/getting-and-building-sling.html
> 1. Would recommend separating installation with / without Eclipse a bit more 
> clearly. Encourage newbie's to get the basic example (using curl) working 
> first.
>     To quote Bertrand:
>         Note that Eclipse is not required at all to work with Sling.
>         The minimal setup for building, running and modifying the Sling code 
> is a JVM, Maven and any text editor.
>         Eclipse or another IDE is convenient, but not required, and 
> especially not for kicking Sling's tyres - we might need to be clearer about 
> that
>         on our website.
> 2. Would it be possible to provide links for  "Maven SCM handler for 
> Subclipse" or the "Maven SCM handler for Subversive"?
> 3. Environment Variable Space -> Problem / Platform / Fix
>     The text under Fix further describes the problem - not (explicitly) tell 
> the user how to fix the issue.
> 4. Some typos...
> 5. The section "Simple way to develop new bundle in Eclipse for Sling" 
> recommends "Start by copying and adapting an existing Sling pom.xml (eg. the 
> pom.xml from the espblog sample)". 
>     If so, the espblog example should be updated to set something like: 
>         <Sling-Initial-Content>
>             initial-content;overwrite:=true;uninstall:=true
>         </Sling-Initial-Content>
>     And would it be advisable to tell them to remove the <scm> section while 
> learning?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to