[JBoss JIRA] (JBIDE-16795) create CDI features overview for tools.jboss.org
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16795?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-16795.
---------------------------------
> create CDI features overview for tools.jboss.org
> ------------------------------------------------
>
> Key: JBIDE-16795
> URL: https://issues.jboss.org/browse/JBIDE-16795
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: cdi, website
> Reporter: Alexey Kazakov
> Assignee: Alexey Kazakov
> Fix For: 4.2.0.Beta2
>
>
> Create a features/cdi.adoc in jbosstools-website describing the main/cool features
> We are refreshing jboss.org/tools (new name: tools.jboss.org) and one of the areas on the new website is a features overview page to let visitors know what features are actually covered in jboss tools.
> You can see the current list at http://tools-stg.jboss.org/features/ following the pattern of component/project logo + component name + "tag line".
> And then individual pages like http://tools-stg.jboss.org/features/openshift.html which follows the pattern of alternating paragraph + image/screenshot with title/tagline + description for each main feature.
> It would be great if you could help create this page for your component.
> The process is as follows:
> git@github.com:jbosstools/jbosstools-website.git
> cd jbosstools-website/features
> create componentname.adoc (use i.e. openshift.adoc as inspiration with respect to header names)
> Submit this page and related images as pullrequest
> The expected launch of the site is end of march so the sooner the better :)
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-16011) create install/download section
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16011?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-16011.
---------------------------------
> create install/download section
> -------------------------------
>
> Key: JBIDE-16011
> URL: https://issues.jboss.org/browse/JBIDE-16011
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: website
> Reporter: Max Rydahl Andersen
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 4.2.0.Beta1
>
>
> should have download section that explains how and where to get jbosstools installed.
> Should have a page pr. specific version download and a "archive" view to get directly to the past versions.
> Should not require more than a few lines with urls to add a new download/install.
> archived links for anything not on actual released update site urls (i.e. previous GA's in same release train) could start by just having download zip url (no updatesite)
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-16463) For JBIDE 4.2.0.Alpha2: Code Freeze + Branch [Central]
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16463?page=com.atlassian.jira.plugi... ]
Radim Hopp closed JBIDE-16463.
------------------------------
Closing.
> For JBIDE 4.2.0.Alpha2: Code Freeze + Branch [Central]
> ------------------------------------------------------
>
> Key: JBIDE-16463
> URL: https://issues.jboss.org/browse/JBIDE-16463
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: central, maven, project-examples
> Reporter: Nick Boldt
> Assignee: Fred Bricon
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.Alpha2
>
>
> For JBIDE 4.2.0.Alpha2 [Central]: Please perform the following tasks:
> 0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (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.2.0.Alpha2
> [Unresolved JIRAs with fixVersion = 4.2.0.Alpha2, 8.0.0.Alpha2|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.0.1.
> *NOTE:* If you already did this for the previous milestone you do *not* need to do so again.
> {code}
> mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.17.0:set-version -DnewVersion=1.0.1-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.2.0.Alpha2-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.2.0.Alpha2-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.Alpha2;
> {code}
> mvn clean verify -Dtpc.version=4.40.0.Alpha2 # (if the TP is already released)
> or
> mvn clean verify -Dtpc.version=4.40.0.Alpha2-SNAPSHOT # (if still being staged)
> {code}
> 4. Branch from your existing master branch into a new jbosstools-4.2.0.Alpha2x branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.2.0.Alpha2x
> git push origin jbosstools-4.2.0.Alpha2x
> {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 Central task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months