[
https://issues.jboss.org/browse/JBIDE-11319?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-11319:
----------------------------------------
SourceReferences are read by PDE and allow to use "Import Source" which sets up
the repo and import the project for you. It's a cool thing, although I'm not sure
it's widely used...
Using Git, it's easy to have Eclipse-SourceReference set with Tycho:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=380872
Snippet:
{code}
<plugin>
<groupId>org.eclipse.tycho</groupId>
<artifactId>tycho-packaging-plugin</artifactId>
<version>${tycho-version}</version>
<configuration>
<sourceReferences>
<generate>true</generate>
</sourceReferences>
</configuration>
<dependencies>
<dependency>
<groupId>org.eclipse.tycho.extras</groupId>
<artifactId>tycho-sourceref-jgit</artifactId>
<version>${tycho-extras-version}</version>
</dependency>
</dependencies>
</plugin>
{code}
However, I'm more concerned about how this piece of code would behave without Git (ie
for DevStudio).
Use Eclipse-SourceReferences
----------------------------
Key: JBIDE-11319
URL:
https://issues.jboss.org/browse/JBIDE-11319
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: Build/Releng
Reporter: Mickael Istria
Assignee: Mickael Istria
Priority: Optional
Fix For: 4.1.x
In order to provide nice entry points to turn users into contributors, it could be
efficient to set Eclipse-SourceReferences in Manifest:
http://wiki.eclipse.org/PDE/UI/SourceReferences
--
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