[
https://issues.apache.org/jira/browse/SLING-2636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Klco updated SLING-2636:
----------------------------
Attachment: SLING-2636-Import-IN-PROGRESS.diff
Okay, cool. I have some code (attached) that is a work in progress, if you want
that.
One of the things I was thinking is that the FileInfo class would be a lot more
useful if it could be directly instantiated from the Eclipse internal classes
and then from it you could get the Filesystem File, Eclipse resource and
corresponding Resource path.
Also, how were you planning on parsing/constructing the JSON? It seems like
Apache projects can use org.json code
(http://www.apache.org/legal/resolved.html#json), so I was using that, but I
don't think it's really optimal to directly include the source in our project.
That being said, the way dependencies are handled in Eclipse plugins makes
loading the code from the POM awkward as the classes handling the JSON parsing
would have to be ouside of the reactor build.
> [Tooling] Add ability to Import from Sling Repository
> -----------------------------------------------------
>
> Key: SLING-2636
> URL: https://issues.apache.org/jira/browse/SLING-2636
> Project: Sling
> Issue Type: Sub-task
> Components: Extensions
> Reporter: Dan Klco
> Assignee: Antonio Sanso
> Priority: Minor
> Attachments: SLING-2636-Import-IN-PROGRESS.diff,
> SLING-2636-Import-Wizard.diff
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
