[jbosstools-issues] [JBoss JIRA] (JBIDE-19749) Enhancements to jbosstools-devdoc
Nick Boldt (JIRA)
issues at jboss.org
Fri May 1 13:10:45 EDT 2015
[ https://issues.jboss.org/browse/JBIDE-19749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nick Boldt updated JBIDE-19749:
-------------------------------
Fix Version/s: 4.3.0.Beta1
> Enhancements to jbosstools-devdoc
> ---------------------------------
>
> Key: JBIDE-19749
> URL: https://issues.jboss.org/browse/JBIDE-19749
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build
> Affects Versions: 4.3.0.Beta1
> Reporter: Nick Boldt
> Fix For: 4.3.0.Beta1
>
>
> * Switch URLs to use git:// instead of git@ - https://github.com/jbosstools/jbosstools-devdoc/pull/42/files#r29133660
> * introduce hub earlier and refer to the hub way instead of the git way to do stuff
> * tweak instructions for checking out and tracking branches - https://github.com/jbosstools/jbosstools-devdoc/pull/42/files#r29133881
> {code}
> git checkout -b \{localname} \{remote}/\{upstream-name} - for when you want a local branch name different from upstream
> git checkout --track \{remote}/\{upstreambranchname} - for when you want a local topic branch with the same name as upstream
> {code} - https://github.com/jbosstools/jbosstools-devdoc/pull/42/files#r29175940
> * remove refs to Central/EA target platforms because in Max's definition they're not target platforms unless a dev uses the .target file
> * remove refs to /static/ when talking about target platform publishing locations; create a doc explaining where things are published (JBDS-3208)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
More information about the jbosstools-issues
mailing list