[JBoss JIRA] (JBDS-3009) use devstudio.redhat.com instead of devstudio.jboss.com in hardcoded URLs within JBDS (eg., Central discovery, updates)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3009?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3009:
-----------------------------
Security: Public (was: RHT+eXo)
> use devstudio.redhat.com instead of devstudio.jboss.com in hardcoded URLs within JBDS (eg., Central discovery, updates)
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3009
> URL: https://issues.jboss.org/browse/JBDS-3009
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: build, installer, updatesite
> Affects Versions: 8.0.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 8.0.0.CR1
>
> Attachments: ssl-enabled-for-filemgmt-but-at-what-cost.png
>
>
> use devstudio.redhat.com instead of devstudio.jboss.com in hardcoded URLs within JBDS (eg., Central discovery, updates)
> Affected files: *.xml, *.inf, etc.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBTIS-314) Generate source bundles for IS component features.
by Paul Leacu (JIRA)
Paul Leacu created JBTIS-314:
--------------------------------
Summary: Generate source bundles for IS component features.
Key: JBTIS-314
URL: https://issues.jboss.org/browse/JBTIS-314
Project: JBoss Tools Integration Stack
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: switchyard
Affects Versions: 8.0.0.Alpha1
Reporter: Paul Leacu
Assignee: Rob Cernich
IS components must generate source bundles for features that will be aggregated (uncategorized) by JBDSIS.
Courtesy Nick Boldt:
How to make maven/tycho build source bundles and features:
In the upstream projects:
http://wiki.eclipse.org/Minerva#Source
Then in the aggregator for JBTIS/JBSIS update site:
https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat...
As a result, users can install sources from within JBDS rather than
needing a separate source zip with .java files. Way more useful, if
you're a java developer using JBDS/Eclipse.
If you also want to produce a zip of actual source files as pulled
from github, I have a script for that, too.
See:
1. https://github.com/jbdevstudio/jbdevstudio-product/tree/master/sources
Produces a zip of the contents of the JBDS product build, so people can
build it offline. Does NOT include upstream sources.
Result:
http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_ma...
(2.4M)
2.
https://github.com/jbosstools/jbosstools-build-ci/blob/master/publish/pub...
Produces a zip of upstream sources based on upstream project zips. This
is the old approach, since pulling a previously-built zip doesn't 100%
guarantee you're getting the correct version AND it requires that the
upstream project produce a source zip.
OR
https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat...
Fetches sources directly from github based on the source-reference in
the specified plugins' manifest.mf files, then collates those sources
into a single zip.
Results:
http://download.jboss.org/jbosstools/builds/nightly/core/master/latest/al...
(35M)
Ref:
(10:02:47 AM) maxandersen: pleacu: for core we've just been providing source bundles for the plugins we provide.
(10:03:55 AM) pleacu: maxandersen, nboldt: sure - and they use tycho to generate them, correct?
(10:04:21 AM) maxandersen: pleacu: yes - jboss tools parent pom somewhat "enforces" it.
(10:05:04 AM) pleacu: maxandersen: ok - I'll look at fuse tooling first since I'm most familiar with that
(10:05:12 AM) maxandersen: pleacu: and nboldt / mistria explicltily aggregates it in uncategorized so it wont show up in default experience.
(10:06:43 AM) nboldt: pleacu: fuse tooling doesn't do source bundles
(10:07:07 AM) nboldt: pleacu: see my email in re: "Where can our customer download source code for jbdevstudio-integration-stack-updatesite-7.0.2.GA.zip?" with details about who does and does not yet produce sources
(10:08:20 AM) nboldt: maxandersen: actually, we don't "aggregate it in uncategorized" because that implies we're specifically putting into a category called "uncategorized"
(10:08:43 AM) nboldt: maxandersen: rather, it's just added to the category.xml w/o setting <category>: https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat... (cc: pleacu )
Components that generate source bundles:
http://download.jboss.org/jbosstools/updates/integration/kepler/integrati...
http://download.jboss.org/jbosstools/updates/stable/kepler/integration-st...
http://download.jboss.org/jbosstools/updates/stable/kepler/integration-st...
http://download.jboss.org/jbosstools/updates/stable/kepler/integration-st...
* Fuse Tooling will for 8.0.0 *
Some that don't:
http://download.jboss.org/jbosstools/updates/integration/kepler/integrati...
http://download.jboss.org/jbosstools/updates/stable/kepler/integration-st...
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-17978) Need to turn on 'angular'-Tern Module automatically in case of AngularJS is detected on a project
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17978?page=com.atlassian.jira.plugi... ]
Alexey Kazakov closed JBIDE-17978.
----------------------------------
> Need to turn on 'angular'-Tern Module automatically in case of AngularJS is detected on a project
> -------------------------------------------------------------------------------------------------
>
> Key: JBIDE-17978
> URL: https://issues.jboss.org/browse/JBIDE-17978
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.2.0.Beta3
> Reporter: Victor Rubezhny
> Assignee: Victor Rubezhny
> Labels: new_and_noteworthy
> Fix For: 4.2.0.CR1
>
> Attachments: dialog.png
>
>
> At the moment, a user cannot use Content Assist for Angular.js by default, because the according Tern module isn't turned on by default.
> So, users have to do the following set up in order to use it:
> Add 'AngularJS module to Tern in order to make anguler-related stuff enabled on the project. In order to do that you should enable 'JBoss Experimental configuration' in Window -> Preferences -> General -> Capabilities first, then enable 'angilar' module in Project properties -> Tern -> Modules.
> We shall detect the angular usage on a project and turn that module on automatically.
> We should ask user to enable AngularJS support for the project when an html file with angularJS usage is opened with JBT HTML Editor (if not enabled yet):
> !dialog.png!
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-17978) Need to turn on 'angular'-Tern Module automatically in case of AngularJS is detected on a project
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17978?page=com.atlassian.jira.plugi... ]
Victor Rubezhny commented on JBIDE-17978:
-----------------------------------------
It looks like Alex is correct and we don't need this dialog.
The situation looks like the following:
When a project is started/imported there is no Tern/Angular associated project object is initialized. Tern/Angular assiciated project object is created on the first usage of that object (on validation or content assist usage or hiperlinking, for instance, but the validator in most cases does it earlier). So, when user don't use any javascript/html editing tools - there will be no Tern/Angular passotiated project initialized. Upon the first usage (either it wil be in JavaScript or HTML Editor is opened) the according configuration end object(-s) is(are) created:
- If this is JavaScript Editor - Tern accociated project is created and is saved into the file ".tern-project" (the only "ecma5" and "browser" libraries are included to this file/object)
- If this is HTML Editor (either the WTP or JBoss Tools one) - Tern associated project is created and is saved into the file ".tern-project" (exactly the same way as for JavaScript), then the Angular accociated project is created and ".tern-project" file is populated with "angularjs" plug-in.
It looks like the politics of angular is always use "angularjs" plug-in if angular is installed and the project is marked as an Angular JS Project (but we're always marking JavaScript projects (by an extension point) as the AngularJS ones, so it's true for all the projects with JavaScript nature). But the configuration process is starting only when requested (in simple words, the according editor is openned).
> Need to turn on 'angular'-Tern Module automatically in case of AngularJS is detected on a project
> -------------------------------------------------------------------------------------------------
>
> Key: JBIDE-17978
> URL: https://issues.jboss.org/browse/JBIDE-17978
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.2.0.Beta3
> Reporter: Victor Rubezhny
> Assignee: Victor Rubezhny
> Labels: new_and_noteworthy
> Fix For: 4.3.x
>
> Attachments: dialog.png
>
>
> At the moment, a user cannot use Content Assist for Angular.js by default, because the according Tern module isn't turned on by default.
> So, users have to do the following set up in order to use it:
> Add 'AngularJS module to Tern in order to make anguler-related stuff enabled on the project. In order to do that you should enable 'JBoss Experimental configuration' in Window -> Preferences -> General -> Capabilities first, then enable 'angilar' module in Project properties -> Tern -> Modules.
> We shall detect the angular usage on a project and turn that module on automatically.
> We should ask user to enable AngularJS support for the project when an html file with angularJS usage is opened with JBT HTML Editor (if not enabled yet):
> !dialog.png!
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18141) Include latest Tern 0.5.0.201408272110 into jbosstools TP
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18141?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-18141:
------------------------------------
With Denis' +1 on https://github.com/jbosstools/jbosstools-discovery/pull/203 I've applied it and it's building here:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-centralta... >=118
> Include latest Tern 0.5.0.201408272110 into jbosstools TP
> ---------------------------------------------------------
>
> Key: JBIDE-18141
> URL: https://issues.jboss.org/browse/JBIDE-18141
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: target-platform
> Affects Versions: 4.2.0.CR1
> Reporter: Victor Rubezhny
> Assignee: Max Rydahl Andersen
> Priority: Blocker
> Labels: new_and_noteworthy
> Fix For: 4.2.0.CR1
>
>
> *Need to switch jst.jsdt to the latest tested Tern v.0.5.0. It contains the important fixes required for JBIDE-17992:
> *Reason:*
> jbosstools-jst is going to provide integration between torn.java and jsdt. torn.java is going to be used to improve JavaScript support
> *License and owner:*
> - Root License is EPL. Owner is Angelo ZERR.
> -- core
> --- org.json.simple - EPL (included into torn-feature below)
> ---- lib/json-simple-1.1.1.jar - Apache License 2.0 (see http://www.apache.org/licenses/LICENSE-2.0.txt)
> --- org.mozilla.javascript
> ---- lib/js.jar - Mozilla Public License Version 2.0 (see http://mozilla.org/MPL/2.0/)
> --- tern.core - EPL (included into tern-feature below)
> --- tern.server.nodejs - EPL (included into tern-server-nodejs-feature below)
> ---- tern.server.nodejs/node_modules/tern/LICENSE
> ----- node_modules/acorn/LICENSE
> ------ node_modules/codemirror/LICENSE
> ------ node_modules/glob/LICENSE
> ------- node_modules/inherits/LICENSE
> ------ node_modules/minimatch/LICENSE
> ------- node_modules/lru-cache/LICENSE
> ------- node_modules/sigmund/LICENSE
> ----- node_modules/typescript/LICENSE - Apache License v. 2.0
> --- tern.eclipse.ide.server.nodejs.ui - EPL (included into tern-server-nodejs-feature below)
> -- eclipse
> --- tern.eclipse.ide.core - EPL (included into tern-feature below)
> --- tern.eclipse.ide.jsdt - EPL (included into tern-jsdt-feature below)
> --- tern.eclipse.ide.server.nodejs.core - EPL (included into tern-server-nodejs-feature below)
> --- tern.eclipse.ide.server.nodejs.ui - EPL (included into tern-server-nodejs-feature below)
> --- tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86 - Supposed to be EPL but it is not included anywhere yet
> ---- node-v0.10.22-linux-x86.zip has several LICENSE files inside (download)
> ----- LICENSE
> ----- lib/node_modules/npm/LICENSE - The Artistic License 2.0
> ----- lib/node_modules/npm/node_modules/*/LICENSE
> --- tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86_64 - EPL (included into tern.eclipse.linux.gtk.x86.feature below)
> ---- node-v0.10.22-linux-x86_64.zip has several LICENSE files inside (download)
> ----- LICENSE
> ----- lib/node_modules/npm/LICENSE - The Artistic License 2.0
> ----- lib/node_modules/npm/node_modules/*/LICENSE
> --- tern.eclipse.ide.server.nodejs.embed.macosx.cocoa.x86_64 - EPL (included into tern.eclipse.macosx.cocoa.x86_64.feature below)
> ---- node-v0.10.22-macosx-x86_64.zip has several LICENSE files inside (download)
> ----- LICENSE
> ----- lib/node_modules/npm - The Artistic License 2.0
> ----- lib/node_modules/npm/node_modules/*/LICENSE
> --- tern.eclipse.ide.server.nodejs.embed.win32.win32.x86 - EPL (include into tern.eclipse.win32.win32.x86.feature below)
> ---- node-v0.10.22-win32-x86.zip has no LICENSE files inside (download)
> ----- node-v0.10.22-win32-x86/node.exe - see http://nodejs.org/download/ for licensing information for node.exe.
> --- tern.eclipse.ide.server.nodejs.embed.win32.win32.x86_64 - EPL (include into tern.eclipse.win32.win32.x86.feature below)
> ---- node-v0.10.22-win32-x86_64.zip has no LICENSE files inside (download)
> ----- node-v0.10.22-win32-x86_64/node.exe - see http://nodejs.org/download/ for licensing information for node.exe.
> --- tern.eclipse.ide.tools.core - EPL (included into tern.eclipse.ide.tools.feature below)
> --- tern.eclipse.ide.tools.ui - EPL (included into tern.eclipse.ide.tools.feature below)
> --- tern.eclipse.ide.ui - EPL (included into tern-feature below)
> --- tern.eclipse - EPL (included into tern-feature below)
> -- update-site
> --- tern-feature - EPL (see licens.httml)
> --- tern-jsdt-feature - EPL (see licens.httml)
> --- tern-server-nodejs-feature - EPL (see licens.httml)
> --- tern.eclipse.ide.tools.feature - EPL (see plicense.html)
> --- tern.eclipse.linux.gtk.x86_64.feature - EPL (see license.html)
> --- tern.eclipse.macosx.cocoa.x86_64.feature - EPL (see license.html)
> --- tern.eclipse.win32.win32.x86.feature - EPL (see license.html)
> *Original repo:* http://oss.opensagres.fr/tern.repository/0.5.0-SNAPSHOT/
> *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/tern/0.5.0.2014...
> *Sources:* https://github.com/angelozerr/tern.java
> *Affected projects:* jbosstools-jst, jbosstools-aerogear
> *Include in JBDS:* No
> *Type of dependency:* distribution
> *List of bundles added/removed:*
> {code}
> mistria@mistria--rh:~/git/jbosstools-target-platforms/jbosstools/multiple$ ~/git/p2diff/org.eclipse.equinox.p2.example.p2diff.packaging/target/products/org.eclipse.equinox.p2.example.p2diff.product/linux/gtk/x86_64/p2diff http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4... file:$(pwd)/target/jbosstools-multiple.target.repo/
> < tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86_64 [0.4.0.201408101311]
> < tern.eclipse.ide.tools.core [0.4.0.201408101311]
> < tern.eclipse.ide.tools.feature.feature.group [0.4.0.201408101311]
> < tern-jsdt-feature.feature.group [0.4.0.201408101311]
> < tern.eclipse.ide.server.nodejs.embed.feature.jar [0.4.0.201408101311]
> < tern.server.nodejs [0.4.0.201408101311]
> < tern-feature.feature.group [0.4.0.201408101311]
> < tern.core [0.4.0.201408101311]
> < tern.eclipse.ide.jsdt [0.4.0.201408101311]
> < tern-jsdt-feature.feature.jar [0.4.0.201408101311]
> < tern.eclipse.ide.ui [0.4.0.201408101311]
> < tern.eclipse.ide.tools.feature.feature.jar [0.4.0.201408101311]
> < tern-server-nodejs-feature.feature.jar [0.4.0.201408101311]
> < tern-feature.feature.jar [0.4.0.201408101311]
> < tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86 [0.4.0.201408101311]
> < tern.eclipse.ide.server.nodejs.core [0.4.0.201408101311]
> < tern.eclipse.ide.tools.ui [0.4.0.201408101311]
> < tern-server-nodejs-feature.feature.group [0.4.0.201408101311]
> < tern.eclipse.ide.server.nodejs.ui [0.4.0.201408101311]
> < tern.eclipse.ide.core [0.4.0.201408101311]
> < tern.eclipse.ide.server.nodejs.embed.feature.group [0.4.0.201408101311]
> < tern.eclipse.ide.server.nodejs.embed.macosx.cocoa.x86_64 [0.4.0.201408101311]
> < tern.eclipse [0.4.0.201408101311]
> < tern.eclipse.ide.server.nodejs.embed.win32.win32.x86_64 [0.4.0.201408101311]
> < tern.eclipse.ide.server.nodejs.embed.win32.win32.x86 [0.4.0.201408101311]
> > tern.eclipse.ide.tools.feature.feature.group [0.5.0.201408272110]
> > tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86_64 [0.5.0.201408272110]
> > tern.eclipse.ide.tools.core [0.5.0.201408272110]
> > tern-jsdt-feature.feature.group [0.5.0.201408272110]
> > tern-feature.feature.group [0.5.0.201408272110]
> > tern.server.nodejs [0.5.0.201408272110]
> > tern.core [0.5.0.201408272110]
> > tern.eclipse.ide.jsdt [0.5.0.201408272110]
> > tern.eclipse.ide.server.nodejs.embed.feature.jar [0.5.0.201408272110]
> > tern.eclipse.ide.server.nodejs.embed.feature.group [0.5.0.201408272110]
> > tern.eclipse [0.5.0.201408272110]
> > tern.eclipse.ide.server.nodejs.embed.macosx.cocoa.x86_64 [0.5.0.201408272110]
> > tern.eclipse.ide.server.nodejs.embed.win32.win32.x86_64 [0.5.0.201408272110]
> > tern.eclipse.ide.server.nodejs.embed.win32.win32.x86 [0.5.0.201408272110]
> > tern.eclipse.ide.tools.ui [0.5.0.201408272110]
> > tern.eclipse.ide.server.nodejs.ui [0.5.0.201408272110]
> > tern-server-nodejs-feature.feature.group [0.5.0.201408272110]
> > tern.eclipse.ide.core [0.5.0.201408272110]
> > tern-jsdt-feature.feature.jar [0.5.0.201408272110]
> > tern.eclipse.ide.tools.feature.feature.jar [0.5.0.201408272110]
> > tern-server-nodejs-feature.feature.jar [0.5.0.201408272110]
> > tern.eclipse.ide.server.nodejs.core [0.5.0.201408272110]
> > tern.eclipse.ide.ui [0.5.0.201408272110]
> > tern-feature.feature.jar [0.5.0.201408272110]
> > tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86 [0.5.0.201408272110]
> === Summary ===
> http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4... contains 25 unique IUs
> file:/home/mistria/git/jbosstools-target-platforms/jbosstools/multiple/target/jbosstools-multiple.target.repo/ contains 25 unique IUs
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-17728) HTML5 Palette: Ionic components
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17728?page=com.atlassian.jira.plugi... ]
Daniel Azarov updated JBIDE-17728:
----------------------------------
Attachment: IonicNavigationWizBan.png
IonicNavigation.png
> HTML5 Palette: Ionic components
> -------------------------------
>
> Key: JBIDE-17728
> URL: https://issues.jboss.org/browse/JBIDE-17728
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Reporter: Alexey Kazakov
> Assignee: Alexey Kazakov
> Labels: new_and_noteworthy
> Fix For: 4.2.0.CR1
>
> Attachments: ActionSheet.png, ActionSheetWizBan.png, Content.png, ContentWizBan.png, ionic.png, IonicButton.png, IonicButtonBar.png, IonicButtonBarWizBan.png, IonicButtonWizBan.png, IonicCheckbox.png, IonicCheckboxWizBan.png, IonicNavigation.png, IonicNavigationWizBan.png, IonicPopup.png, IonicPopupWizBan.png, IonicRadio.png, IonicRadioWizBan.png, IonicRange.png, IonicRangeWizBan.png, IonicRefresher.png, IonicRefresherWizBan.png, IonicSelect.png, IonicSelectWizBan.png, IonicTab.png, IonicTabs.png, IonicTabsWizBan.png, IonicTabWizBan.png, IonicTextInput.png, IonicTextInputWizBan.png, IonicToggle.png, IonicToggleWizBan.png, List.png, ListWizBan.png, scr.png, Scroll.png, ScrollWizBan.png, SideMenu.png, SideMenu.png, SideMenuWizBan.png, SlideBox.png, SlideBoxWizBan.png, SlideMenu.png, SlideMenuWizBan.png
>
>
> http://ionicframework.com/docs/
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18141) Include latest Tern 0.5.0.201408272110 into jbosstools TP
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18141?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-18141:
---------------------------------------
Thanks Nick, I didn't know about jbtearlyaccess-multiple.target ;( PR #203 looks good to me
> Include latest Tern 0.5.0.201408272110 into jbosstools TP
> ---------------------------------------------------------
>
> Key: JBIDE-18141
> URL: https://issues.jboss.org/browse/JBIDE-18141
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: target-platform
> Affects Versions: 4.2.0.CR1
> Reporter: Victor Rubezhny
> Assignee: Max Rydahl Andersen
> Priority: Blocker
> Labels: new_and_noteworthy
> Fix For: 4.2.0.CR1
>
>
> *Need to switch jst.jsdt to the latest tested Tern v.0.5.0. It contains the important fixes required for JBIDE-17992:
> *Reason:*
> jbosstools-jst is going to provide integration between torn.java and jsdt. torn.java is going to be used to improve JavaScript support
> *License and owner:*
> - Root License is EPL. Owner is Angelo ZERR.
> -- core
> --- org.json.simple - EPL (included into torn-feature below)
> ---- lib/json-simple-1.1.1.jar - Apache License 2.0 (see http://www.apache.org/licenses/LICENSE-2.0.txt)
> --- org.mozilla.javascript
> ---- lib/js.jar - Mozilla Public License Version 2.0 (see http://mozilla.org/MPL/2.0/)
> --- tern.core - EPL (included into tern-feature below)
> --- tern.server.nodejs - EPL (included into tern-server-nodejs-feature below)
> ---- tern.server.nodejs/node_modules/tern/LICENSE
> ----- node_modules/acorn/LICENSE
> ------ node_modules/codemirror/LICENSE
> ------ node_modules/glob/LICENSE
> ------- node_modules/inherits/LICENSE
> ------ node_modules/minimatch/LICENSE
> ------- node_modules/lru-cache/LICENSE
> ------- node_modules/sigmund/LICENSE
> ----- node_modules/typescript/LICENSE - Apache License v. 2.0
> --- tern.eclipse.ide.server.nodejs.ui - EPL (included into tern-server-nodejs-feature below)
> -- eclipse
> --- tern.eclipse.ide.core - EPL (included into tern-feature below)
> --- tern.eclipse.ide.jsdt - EPL (included into tern-jsdt-feature below)
> --- tern.eclipse.ide.server.nodejs.core - EPL (included into tern-server-nodejs-feature below)
> --- tern.eclipse.ide.server.nodejs.ui - EPL (included into tern-server-nodejs-feature below)
> --- tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86 - Supposed to be EPL but it is not included anywhere yet
> ---- node-v0.10.22-linux-x86.zip has several LICENSE files inside (download)
> ----- LICENSE
> ----- lib/node_modules/npm/LICENSE - The Artistic License 2.0
> ----- lib/node_modules/npm/node_modules/*/LICENSE
> --- tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86_64 - EPL (included into tern.eclipse.linux.gtk.x86.feature below)
> ---- node-v0.10.22-linux-x86_64.zip has several LICENSE files inside (download)
> ----- LICENSE
> ----- lib/node_modules/npm/LICENSE - The Artistic License 2.0
> ----- lib/node_modules/npm/node_modules/*/LICENSE
> --- tern.eclipse.ide.server.nodejs.embed.macosx.cocoa.x86_64 - EPL (included into tern.eclipse.macosx.cocoa.x86_64.feature below)
> ---- node-v0.10.22-macosx-x86_64.zip has several LICENSE files inside (download)
> ----- LICENSE
> ----- lib/node_modules/npm - The Artistic License 2.0
> ----- lib/node_modules/npm/node_modules/*/LICENSE
> --- tern.eclipse.ide.server.nodejs.embed.win32.win32.x86 - EPL (include into tern.eclipse.win32.win32.x86.feature below)
> ---- node-v0.10.22-win32-x86.zip has no LICENSE files inside (download)
> ----- node-v0.10.22-win32-x86/node.exe - see http://nodejs.org/download/ for licensing information for node.exe.
> --- tern.eclipse.ide.server.nodejs.embed.win32.win32.x86_64 - EPL (include into tern.eclipse.win32.win32.x86.feature below)
> ---- node-v0.10.22-win32-x86_64.zip has no LICENSE files inside (download)
> ----- node-v0.10.22-win32-x86_64/node.exe - see http://nodejs.org/download/ for licensing information for node.exe.
> --- tern.eclipse.ide.tools.core - EPL (included into tern.eclipse.ide.tools.feature below)
> --- tern.eclipse.ide.tools.ui - EPL (included into tern.eclipse.ide.tools.feature below)
> --- tern.eclipse.ide.ui - EPL (included into tern-feature below)
> --- tern.eclipse - EPL (included into tern-feature below)
> -- update-site
> --- tern-feature - EPL (see licens.httml)
> --- tern-jsdt-feature - EPL (see licens.httml)
> --- tern-server-nodejs-feature - EPL (see licens.httml)
> --- tern.eclipse.ide.tools.feature - EPL (see plicense.html)
> --- tern.eclipse.linux.gtk.x86_64.feature - EPL (see license.html)
> --- tern.eclipse.macosx.cocoa.x86_64.feature - EPL (see license.html)
> --- tern.eclipse.win32.win32.x86.feature - EPL (see license.html)
> *Original repo:* http://oss.opensagres.fr/tern.repository/0.5.0-SNAPSHOT/
> *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/tern/0.5.0.2014...
> *Sources:* https://github.com/angelozerr/tern.java
> *Affected projects:* jbosstools-jst, jbosstools-aerogear
> *Include in JBDS:* No
> *Type of dependency:* distribution
> *List of bundles added/removed:*
> {code}
> mistria@mistria--rh:~/git/jbosstools-target-platforms/jbosstools/multiple$ ~/git/p2diff/org.eclipse.equinox.p2.example.p2diff.packaging/target/products/org.eclipse.equinox.p2.example.p2diff.product/linux/gtk/x86_64/p2diff http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4... file:$(pwd)/target/jbosstools-multiple.target.repo/
> < tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86_64 [0.4.0.201408101311]
> < tern.eclipse.ide.tools.core [0.4.0.201408101311]
> < tern.eclipse.ide.tools.feature.feature.group [0.4.0.201408101311]
> < tern-jsdt-feature.feature.group [0.4.0.201408101311]
> < tern.eclipse.ide.server.nodejs.embed.feature.jar [0.4.0.201408101311]
> < tern.server.nodejs [0.4.0.201408101311]
> < tern-feature.feature.group [0.4.0.201408101311]
> < tern.core [0.4.0.201408101311]
> < tern.eclipse.ide.jsdt [0.4.0.201408101311]
> < tern-jsdt-feature.feature.jar [0.4.0.201408101311]
> < tern.eclipse.ide.ui [0.4.0.201408101311]
> < tern.eclipse.ide.tools.feature.feature.jar [0.4.0.201408101311]
> < tern-server-nodejs-feature.feature.jar [0.4.0.201408101311]
> < tern-feature.feature.jar [0.4.0.201408101311]
> < tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86 [0.4.0.201408101311]
> < tern.eclipse.ide.server.nodejs.core [0.4.0.201408101311]
> < tern.eclipse.ide.tools.ui [0.4.0.201408101311]
> < tern-server-nodejs-feature.feature.group [0.4.0.201408101311]
> < tern.eclipse.ide.server.nodejs.ui [0.4.0.201408101311]
> < tern.eclipse.ide.core [0.4.0.201408101311]
> < tern.eclipse.ide.server.nodejs.embed.feature.group [0.4.0.201408101311]
> < tern.eclipse.ide.server.nodejs.embed.macosx.cocoa.x86_64 [0.4.0.201408101311]
> < tern.eclipse [0.4.0.201408101311]
> < tern.eclipse.ide.server.nodejs.embed.win32.win32.x86_64 [0.4.0.201408101311]
> < tern.eclipse.ide.server.nodejs.embed.win32.win32.x86 [0.4.0.201408101311]
> > tern.eclipse.ide.tools.feature.feature.group [0.5.0.201408272110]
> > tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86_64 [0.5.0.201408272110]
> > tern.eclipse.ide.tools.core [0.5.0.201408272110]
> > tern-jsdt-feature.feature.group [0.5.0.201408272110]
> > tern-feature.feature.group [0.5.0.201408272110]
> > tern.server.nodejs [0.5.0.201408272110]
> > tern.core [0.5.0.201408272110]
> > tern.eclipse.ide.jsdt [0.5.0.201408272110]
> > tern.eclipse.ide.server.nodejs.embed.feature.jar [0.5.0.201408272110]
> > tern.eclipse.ide.server.nodejs.embed.feature.group [0.5.0.201408272110]
> > tern.eclipse [0.5.0.201408272110]
> > tern.eclipse.ide.server.nodejs.embed.macosx.cocoa.x86_64 [0.5.0.201408272110]
> > tern.eclipse.ide.server.nodejs.embed.win32.win32.x86_64 [0.5.0.201408272110]
> > tern.eclipse.ide.server.nodejs.embed.win32.win32.x86 [0.5.0.201408272110]
> > tern.eclipse.ide.tools.ui [0.5.0.201408272110]
> > tern.eclipse.ide.server.nodejs.ui [0.5.0.201408272110]
> > tern-server-nodejs-feature.feature.group [0.5.0.201408272110]
> > tern.eclipse.ide.core [0.5.0.201408272110]
> > tern-jsdt-feature.feature.jar [0.5.0.201408272110]
> > tern.eclipse.ide.tools.feature.feature.jar [0.5.0.201408272110]
> > tern-server-nodejs-feature.feature.jar [0.5.0.201408272110]
> > tern.eclipse.ide.server.nodejs.core [0.5.0.201408272110]
> > tern.eclipse.ide.ui [0.5.0.201408272110]
> > tern-feature.feature.jar [0.5.0.201408272110]
> > tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86 [0.5.0.201408272110]
> === Summary ===
> http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4... contains 25 unique IUs
> file:/home/mistria/git/jbosstools-target-platforms/jbosstools/multiple/target/jbosstools-multiple.target.repo/ contains 25 unique IUs
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18168) For JBIDE 4.2.0.CR1: Code Freeze + Branch [LiveReload]
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18168?page=com.atlassian.jira.plugi... ]
Xavier Coulon closed JBIDE-18168.
---------------------------------
Assignee: Xavier Coulon
Resolution: Done
done.
> For JBIDE 4.2.0.CR1: Code Freeze + Branch [LiveReload]
> ------------------------------------------------------
>
> Key: JBIDE-18168
> URL: https://issues.jboss.org/browse/JBIDE-18168
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: livereload
> Reporter: Mickael Istria
> Assignee: Xavier Coulon
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.CR1
>
>
> For JBIDE 4.2.0.CR1 [LiveReload]: 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.CR1
> [Unresolved JIRAs with fixVersion = 4.2.0.CR1, 8.0.0.CR1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...]
> 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.21.0:set-version -DnewVersion=1.0.1-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.2.0.CR1-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.2.0.CR1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.CR1-SNAPSHOT;
> {code}
> mvn clean verify -Dtpc.version=4.40.0.CR1 # (if the TP is already released)
> or
> mvn clean verify -Dtpc.version=4.40.0.CR1-SNAPSHOT # (if still being staged)
> {code}
> 4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.2.x{color}* branch;
> {code}
> git fetch origin master
> git checkout FETCH_HEAD
> git checkout -b jbosstools-4.2.x
> git push origin jbosstools-4.2.x
> {code}
> 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*.
> {code}
> git checkout master
> git pull origin master
> {code}
> 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.2.0.CR2-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.2.0.CR2-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.2.0.CR1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.x{color}* branch, and
> * *{color:orange}4.2.0.CR2-SNAPSHOT{color}* in your *{color:orange}master{color}* branch.
> 7. Close (do not resolve) this JIRA when done.
> 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for LiveReload task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18152) For JBIDE 4.2.0.CR1: Code Freeze + Branch [VPE]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18152?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-18152:
------------------------------------
Reminder, JBIDE-18112 needs to be done before you branch.
> For JBIDE 4.2.0.CR1: Code Freeze + Branch [VPE]
> -----------------------------------------------
>
> Key: JBIDE-18152
> URL: https://issues.jboss.org/browse/JBIDE-18152
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: visual-page-editor-core
> Reporter: Mickael Istria
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.CR1
>
>
> For JBIDE 4.2.0.CR1 [VPE]: 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.CR1
> [Unresolved JIRAs with fixVersion = 4.2.0.CR1, 8.0.0.CR1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...]
> 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.21.0:set-version -DnewVersion=1.0.1-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.2.0.CR1-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.2.0.CR1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.CR1-SNAPSHOT;
> {code}
> mvn clean verify -Dtpc.version=4.40.0.CR1 # (if the TP is already released)
> or
> mvn clean verify -Dtpc.version=4.40.0.CR1-SNAPSHOT # (if still being staged)
> {code}
> 4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.2.x{color}* branch;
> {code}
> git fetch origin master
> git checkout FETCH_HEAD
> git checkout -b jbosstools-4.2.x
> git push origin jbosstools-4.2.x
> {code}
> 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*.
> {code}
> git checkout master
> git pull origin master
> {code}
> 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.2.0.CR2-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.2.0.CR2-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.2.0.CR1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.x{color}* branch, and
> * *{color:orange}4.2.0.CR2-SNAPSHOT{color}* in your *{color:orange}master{color}* branch.
> 7. Close (do not resolve) this JIRA when done.
> 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next.
> [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.1#6329)
11 years, 7 months