[JBoss JIRA] (JBIDE-19248) Import examples from git repo
by Fred Bricon (JIRA)
Fred Bricon created JBIDE-19248:
-----------------------------------
Summary: Import examples from git repo
Key: JBIDE-19248
URL: https://issues.jboss.org/browse/JBIDE-19248
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: project-examples
Affects Versions: 4.2.2.Final
Reporter: Fred Bricon
Currently, project examples for wfk and eap needs to be assembled individually into zip files and downloaded separately.
It'd be easier, from a "go offline" scenario and also in general maintenance context, to be able to import the examples from git
Project examples descriptor (or another mechanism) could define :
- git repo url
- sha1/tag
- example folder
The import process would then :
- clone the repo to a user defined location (~/.jbosstools/offline) by default if it doesn't exist, or update the repo if it exists
- traverse the sha1/tag tree to extract the chosen examples and copy them to another user defined location.
Once the repo has been cloned, every project creation would likely be very, very fast
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19248) Import examples from git repo
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19248?page=com.atlassian.jira.plugi... ]
Fred Bricon reassigned JBIDE-19248:
-----------------------------------
Assignee: Fred Bricon
> Import examples from git repo
> -----------------------------
>
> Key: JBIDE-19248
> URL: https://issues.jboss.org/browse/JBIDE-19248
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: project-examples
> Affects Versions: 4.2.2.Final
> Reporter: Fred Bricon
> Assignee: Fred Bricon
>
> Currently, project examples for wfk and eap needs to be assembled individually into zip files and downloaded separately.
> It'd be easier, from a "go offline" scenario and also in general maintenance context, to be able to import the examples from git
> Project examples descriptor (or another mechanism) could define :
> - git repo url
> - sha1/tag
> - example folder
> The import process would then :
> - clone the repo to a user defined location (~/.jbosstools/offline) by default if it doesn't exist, or update the repo if it exists
> - traverse the sha1/tag tree to extract the chosen examples and copy them to another user defined location.
> Once the repo has been cloned, every project creation would likely be very, very fast
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19229) For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [VPE]
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19229?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov reassigned JBIDE-19229:
----------------------------------------------
Assignee: Konstantin Marmalyukov
> For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [VPE]
> --------------------------------------------------
>
> Key: JBIDE-19229
> URL: https://issues.jboss.org/browse/JBIDE-19229
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: visual-page-editor-core
> Reporter: Nick Boldt
> Assignee: Konstantin Marmalyukov
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.Alpha1
>
>
> For JBIDE 4.3.0.Alpha1 [VPE]: Please perform the following tasks:
> 0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Alpha1
> [Unresolved JIRAs with fixVersion = 4.3.0.Alpha1, 9.0.0.Alpha1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...]
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0, or from 1.2.2 to 1.2.100.
> *NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.3.0.Alpha1-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.0.Alpha1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha1;
> {code}
> mvn clean verify -Dtpc.version=4.50.0.Alpha1 # (if the TP is already released)
> {code}
> 4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha1x branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.3.0.Alpha1x
> git push origin jbosstools-4.3.0.Alpha1x
> {code}
> 5. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for VPE task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19229) For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [VPE]
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19229?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov closed JBIDE-19229.
------------------------------------------
Resolution: Done
> For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [VPE]
> --------------------------------------------------
>
> Key: JBIDE-19229
> URL: https://issues.jboss.org/browse/JBIDE-19229
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: visual-page-editor-core
> Reporter: Nick Boldt
> Assignee: Konstantin Marmalyukov
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.Alpha1
>
>
> For JBIDE 4.3.0.Alpha1 [VPE]: Please perform the following tasks:
> 0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Alpha1
> [Unresolved JIRAs with fixVersion = 4.3.0.Alpha1, 9.0.0.Alpha1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...]
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0, or from 1.2.2 to 1.2.100.
> *NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.3.0.Alpha1-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.0.Alpha1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha1;
> {code}
> mvn clean verify -Dtpc.version=4.50.0.Alpha1 # (if the TP is already released)
> {code}
> 4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha1x branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.3.0.Alpha1x
> git push origin jbosstools-4.3.0.Alpha1x
> {code}
> 5. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for VPE task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months