[JBoss JIRA] (JBIDE-18678) Make dependencies to org.jboss.tools.usage optional
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18678?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-18678:
-----------------------------------
Fix Version/s: 4.4.x
(was: 4.3.0.Beta2)
> Make dependencies to org.jboss.tools.usage optional
> ---------------------------------------------------
>
> Key: JBIDE-18678
> URL: https://issues.jboss.org/browse/JBIDE-18678
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: browsersim, usage
> Affects Versions: 4.2.0.CR1
> Reporter: Kaloyan Raev
> Assignee: Alexey Kazakov
> Fix For: 4.4.x
>
>
> I am interested in adopting the CordovaSim feature in our product. However, most of the browsersim bundles have a strong dependency to org.jboss.tools.usage bundle, which force a Usage Reporting popup on startup. I want to avoid this and have the org.jboss.tools.usage excluded from my build.
> Is it possible to make the dependencies to org.jboss.tools.usage optional?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-13725) Keep HTML5 jQuery Mobile Page Template up to date
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13725?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-13725:
-----------------------------------
Fix Version/s: 4.3.0.CR1
(was: 4.3.0.Beta2)
> Keep HTML5 jQuery Mobile Page Template up to date
> -------------------------------------------------
>
> Key: JBIDE-13725
> URL: https://issues.jboss.org/browse/JBIDE-13725
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: jsp/jsf/xml/html source editing
> Reporter: Alexey Kazakov
> Assignee: Alexey Kazakov
> Labels: new_and_noteworthy
> Fix For: 4.3.0.CR1
>
>
> Current jQuery Mobile js/css which is used by HTML5 jQuery Mobile Page Template is 1.3.0 (+ jQuery 1.9.1). We have to make sure that the final version of JBT 4.1.0 will have the latest jQuery Mobile links in this template.
> So far it's JQM 1.3.0 but it may change by the time of GA release.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-17989) keyword used for plugin tracking is missing majority of times on GA
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17989?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-17989:
-----------------------------------
Fix Version/s: 4.3.0.CR1
(was: 4.3.0.Beta2)
> keyword used for plugin tracking is missing majority of times on GA
> -------------------------------------------------------------------
>
> Key: JBIDE-17989
> URL: https://issues.jboss.org/browse/JBIDE-17989
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: usage
> Reporter: Max Rydahl Andersen
> Assignee: Alexey Kazakov
> Priority: Critical
> Fix For: 4.3.0.CR1
>
> Attachments: devstudio-january.png, graphformissingstats.png, jbds.png, scr.png
>
>
> looking at tracking numbers i'm seeing more and more requests where the keywords are not making it into the result.
> Meaning we can't see how many have installed the various plugins.
> What is weird *some* do and others do not have it.
> Need to track down the reason for that being missed.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-17727) CSS content assist for class attribute in custom HTML tags
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17727?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-17727:
-----------------------------------
Fix Version/s: 4.3.x
(was: 4.3.0.Beta2)
> CSS content assist for class attribute in custom HTML tags
> ----------------------------------------------------------
>
> Key: JBIDE-17727
> URL: https://issues.jboss.org/browse/JBIDE-17727
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.2.0.Beta2
> Reporter: Alexey Kazakov
> Assignee: Alexey Kazakov
> Fix For: 4.3.x
>
>
> Right now, content assist for CSS classes works only for standart HTML tags. But some frameworks use custom html tags (AngularJS and its extensions like ionic framework for example). It would be useful if our CSS content assist also worked for such tags.
> For example:
> {code}
> <ion-tabs class="tabs-positive tabs-icon-only">
> <ion-tab title="Home" icon-on="ion-ios7-filing" icon-off="ion-ios7-filing-outline">
> </ion-tab>
> </ion-tabs>
> {code}
> Currently the content assis works only if you change <ion-tabs> to <div> or any other standart HTML tags.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20171) buildinfo.json reader fails if upstream MANIFEST.MF contains no SHA
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20171?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-20171 at 7/7/15 2:48 PM:
------------------------------------------------------------
Now in the build log we get these warnings:
{code}
[WARNING] Cannot fetch jbosstools-xulrunner sources: no Eclipse-SourceReferences in org.mozilla.xpcom_1.9.2.16.jar MANIFEST.MF
[WARNING]
/mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/sources/aggregate/site/target/buildinfo/buildinfo_jbosstools-xulrunner.json
contains 2edce933f7d64efbb4d7a5b16be8dadae8de766e, but upstream jbosstools-xulrunner project's MANIFEST.MF has no Eclipse-SourceReferences commitId.
Using sources from 2edce933f7d64efbb4d7a5b16be8dadae8de766e.
[INFO] Downloaded: jbosstools-xulrunner_2edce933f7d64efbb4d7a5b16be8dadae8de766e_sources.zip (46.5 M)
{code}
And the JBT sources zip is larger as it includes the Xulrunner sources too.
http://download.jboss.org/jbosstools/mars/staging/builds/jbosstools-4.3.0... *285M*
http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bui... *332M*
was (Author: nickboldt):
Now in the build log we get these harmless warning:
{code}
[WARNING] Cannot fetch jbosstools-xulrunner sources: no Eclipse-SourceReferences in org.mozilla.xpcom_1.9.2.16.jar MANIFEST.MF
[WARNING]
/mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/sources/aggregate/site/target/buildinfo/buildinfo_jbosstools-xulrunner.json
contains 2edce933f7d64efbb4d7a5b16be8dadae8de766e, but upstream jbosstools-xulrunner project's MANIFEST.MF has no Eclipse-SourceReferences commitId.
Using sources from 2edce933f7d64efbb4d7a5b16be8dadae8de766e.
[INFO] Downloaded: jbosstools-xulrunner_2edce933f7d64efbb4d7a5b16be8dadae8de766e_sources.zip (46.5 M)
{code}
And the JBT sources zip is larger as it includes the Xulrunner sources too.
http://download.jboss.org/jbosstools/mars/staging/builds/jbosstools-4.3.0... *285M*
http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bui... *332M*
> buildinfo.json reader fails if upstream MANIFEST.MF contains no SHA
> -------------------------------------------------------------------
>
> Key: JBIDE-20171
> URL: https://issues.jboss.org/browse/JBIDE-20171
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: build
> Affects Versions: 4.3.0.Beta2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.0.Beta2
>
>
> Since the addition of a check that verifies exactly this condition:
> https://github.com/jbosstools/jbosstools-maven-plugins/commit/916f4521ba6...
> I've now got a situation where it's OK to have no SHA in the MANIFEST.MF, but a SHA in buildinfo.json.
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sites.aggregate.site_master/10216/console}
> [ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:repository-utils:0.22.1-SNAPSHOT:fetch-sources-from-manifests (fetch-sources) on project org.jboss.tools.site.core: Problem occurred checking upstream buildinfo.json files!
> [ERROR] /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/sources/aggregate/site/target/buildinfo/buildinfo_jbosstools-xulrunner.json
> [ERROR] contains 2edce933f7d64efbb4d7a5b16be8dadae8de766e, but upstream project's MANIFEST.MF has Eclipse-SourceReferences
> [ERROR] commitId .
> [ERROR] If you have locally built projects which are aggregated here,
> [ERROR] ensure they are built from the latest SHA from HEAD, not a local topic branch.
> [ERROR] Or, use -DskipCheckSHAs=true to bypass this check.
> [ERROR] -> [Help 1]{code}
> This happened after I put a buildinfo.json file here:
> http://download.jboss.org/jbosstools/updates/requirements/xulrunner-1.9.2...
> I've since moved the file here to temporarily work around the build failure:
> http://download.jboss.org/jbosstools/updates/requirements/xulrunner-1.9.2...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20171) buildinfo.json reader fails if upstream MANIFEST.MF contains no SHA
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20171?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-20171:
------------------------------------
Now in the build log we get these harmless warning:
{code}
[WARNING] Cannot fetch jbosstools-xulrunner sources: no Eclipse-SourceReferences in org.mozilla.xpcom_1.9.2.16.jar MANIFEST.MF
[WARNING]
/mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/sources/aggregate/site/target/buildinfo/buildinfo_jbosstools-xulrunner.json
contains 2edce933f7d64efbb4d7a5b16be8dadae8de766e, but upstream jbosstools-xulrunner project's MANIFEST.MF has no Eclipse-SourceReferences commitId.
Using sources from 2edce933f7d64efbb4d7a5b16be8dadae8de766e.
[INFO] Downloaded: jbosstools-xulrunner_2edce933f7d64efbb4d7a5b16be8dadae8de766e_sources.zip (46.5 M)
{code}
And the JBT sources zip is larger as it includes the Xulrunner sources too.
http://download.jboss.org/jbosstools/mars/staging/builds/jbosstools-4.3.0... *285M*
http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bui... *332M*
> buildinfo.json reader fails if upstream MANIFEST.MF contains no SHA
> -------------------------------------------------------------------
>
> Key: JBIDE-20171
> URL: https://issues.jboss.org/browse/JBIDE-20171
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: build
> Affects Versions: 4.3.0.Beta2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.0.Beta2
>
>
> Since the addition of a check that verifies exactly this condition:
> https://github.com/jbosstools/jbosstools-maven-plugins/commit/916f4521ba6...
> I've now got a situation where it's OK to have no SHA in the MANIFEST.MF, but a SHA in buildinfo.json.
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sites.aggregate.site_master/10216/console}
> [ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:repository-utils:0.22.1-SNAPSHOT:fetch-sources-from-manifests (fetch-sources) on project org.jboss.tools.site.core: Problem occurred checking upstream buildinfo.json files!
> [ERROR] /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/sources/aggregate/site/target/buildinfo/buildinfo_jbosstools-xulrunner.json
> [ERROR] contains 2edce933f7d64efbb4d7a5b16be8dadae8de766e, but upstream project's MANIFEST.MF has Eclipse-SourceReferences
> [ERROR] commitId .
> [ERROR] If you have locally built projects which are aggregated here,
> [ERROR] ensure they are built from the latest SHA from HEAD, not a local topic branch.
> [ERROR] Or, use -DskipCheckSHAs=true to bypass this check.
> [ERROR] -> [Help 1]{code}
> This happened after I put a buildinfo.json file here:
> http://download.jboss.org/jbosstools/updates/requirements/xulrunner-1.9.2...
> I've since moved the file here to temporarily work around the build failure:
> http://download.jboss.org/jbosstools/updates/requirements/xulrunner-1.9.2...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20171) buildinfo.json reader fails if upstream MANIFEST.MF contains no SHA
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20171?page=com.atlassian.jira.plugi... ]
Nick Boldt resolved JBIDE-20171.
--------------------------------
Resolution: Done
OK, so instead of rebuilding xulrunner, I've done three things:
a) support the usecase where there's an buildinfo.json file for the build, but the Eclipse-SourceReferences SHA is null / missing
b) enable the source fetcher to fetch from the buildinfo.json's SHA, rather than just the SHA in the upstream project's MANIFEST.MF
b) create a buildinfo.json file for Xulrunner, which the JBT agg site can use to fetch sources and aggregate into its combined buildinfo.json file.
Commits:
https://github.com/jbosstools/jbosstools-maven-plugins/commit/bfee320d5f5...
https://github.com/jbosstools/jbosstools-build-sites/commit/9491c23b80c3e...
Results posted here:
https://issues.jboss.org/browse/JBIDE-20168?focusedCommentId=13087533&pag...
> buildinfo.json reader fails if upstream MANIFEST.MF contains no SHA
> -------------------------------------------------------------------
>
> Key: JBIDE-20171
> URL: https://issues.jboss.org/browse/JBIDE-20171
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: build
> Affects Versions: 4.3.0.Beta2
> Reporter: Nick Boldt
> Assignee: Max Rydahl Andersen
> Fix For: 4.3.0.Beta2
>
>
> Since the addition of a check that verifies exactly this condition:
> https://github.com/jbosstools/jbosstools-maven-plugins/commit/916f4521ba6...
> I've now got a situation where it's OK to have no SHA in the MANIFEST.MF, but a SHA in buildinfo.json.
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sites.aggregate.site_master/10216/console}
> [ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:repository-utils:0.22.1-SNAPSHOT:fetch-sources-from-manifests (fetch-sources) on project org.jboss.tools.site.core: Problem occurred checking upstream buildinfo.json files!
> [ERROR] /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/sources/aggregate/site/target/buildinfo/buildinfo_jbosstools-xulrunner.json
> [ERROR] contains 2edce933f7d64efbb4d7a5b16be8dadae8de766e, but upstream project's MANIFEST.MF has Eclipse-SourceReferences
> [ERROR] commitId .
> [ERROR] If you have locally built projects which are aggregated here,
> [ERROR] ensure they are built from the latest SHA from HEAD, not a local topic branch.
> [ERROR] Or, use -DskipCheckSHAs=true to bypass this check.
> [ERROR] -> [Help 1]{code}
> This happened after I put a buildinfo.json file here:
> http://download.jboss.org/jbosstools/updates/requirements/xulrunner-1.9.2...
> I've since moved the file here to temporarily work around the build failure:
> http://download.jboss.org/jbosstools/updates/requirements/xulrunner-1.9.2...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20171) buildinfo.json reader fails if upstream MANIFEST.MF contains no SHA
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20171?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-20171:
----------------------------------
Assignee: Nick Boldt (was: Max Rydahl Andersen)
> buildinfo.json reader fails if upstream MANIFEST.MF contains no SHA
> -------------------------------------------------------------------
>
> Key: JBIDE-20171
> URL: https://issues.jboss.org/browse/JBIDE-20171
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: build
> Affects Versions: 4.3.0.Beta2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.0.Beta2
>
>
> Since the addition of a check that verifies exactly this condition:
> https://github.com/jbosstools/jbosstools-maven-plugins/commit/916f4521ba6...
> I've now got a situation where it's OK to have no SHA in the MANIFEST.MF, but a SHA in buildinfo.json.
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sites.aggregate.site_master/10216/console}
> [ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:repository-utils:0.22.1-SNAPSHOT:fetch-sources-from-manifests (fetch-sources) on project org.jboss.tools.site.core: Problem occurred checking upstream buildinfo.json files!
> [ERROR] /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/sources/aggregate/site/target/buildinfo/buildinfo_jbosstools-xulrunner.json
> [ERROR] contains 2edce933f7d64efbb4d7a5b16be8dadae8de766e, but upstream project's MANIFEST.MF has Eclipse-SourceReferences
> [ERROR] commitId .
> [ERROR] If you have locally built projects which are aggregated here,
> [ERROR] ensure they are built from the latest SHA from HEAD, not a local topic branch.
> [ERROR] Or, use -DskipCheckSHAs=true to bypass this check.
> [ERROR] -> [Help 1]{code}
> This happened after I put a buildinfo.json file here:
> http://download.jboss.org/jbosstools/updates/requirements/xulrunner-1.9.2...
> I've since moved the file here to temporarily work around the build failure:
> http://download.jboss.org/jbosstools/updates/requirements/xulrunner-1.9.2...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20168) create buildinfo.json files for old project builds which predate buildinfo.json generator
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20168?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-20168 at 7/7/15 2:42 PM:
------------------------------------------------------------
OK, so instead of rebuilding xulrunner, I've done three things:
a) support the usecase where there's an buildinfo.json file for the build, but the Eclipse-SourceReferences SHA is null / missing
b) enable the source fetcher to fetch from the buildinfo.json's SHA, rather than just the SHA in the upstream project's MANIFEST.MF
c) create a buildinfo.json file for Xulrunner, which the JBT agg site can use to fetch sources and aggregate into its combined buildinfo.json file.
Commits:
https://github.com/jbosstools/jbosstools-maven-plugins/commit/bfee320d5f5...
https://github.com/jbosstools/jbosstools-build-sites/commit/9491c23b80c3e...
was (Author: nickboldt):
OK, so instead of rebuilding xulrunner, I've done three things:
a) support the usecase where there's an buildinfo.json file for the build, but the Eclipse-SourceReferences SHA is null / missing
b) enable the source fetcher to fetch from the buildinfo.json's SHA, rather than just the SHA in the upstream project's MANIFEST.MF
b) create a buildinfo.json file for Xulrunner, which the JBT agg site can use to fetch sources and aggregate into its combined buildinfo.json file.
Commits:
https://github.com/jbosstools/jbosstools-maven-plugins/commit/bfee320d5f5...
https://github.com/jbosstools/jbosstools-build-sites/commit/9491c23b80c3e...
> create buildinfo.json files for old project builds which predate buildinfo.json generator
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-20168
> URL: https://issues.jboss.org/browse/JBIDE-20168
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.3.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.0.Beta2
>
>
> Max asked:
> {quote}
> i'm asking what shah's was used in the build for these components.
> No sure if you are trolling me by us keeping having these conversations everytime we need to tag :)
> Checking jbosstools-portlet the latest 4.3.0 tags are same as master but the link above you are pointing to Luna so that can't be right.
> and jbosstools-xulrunner seem to have very little tags at all - so again; which tag/sha1 of these was put into our release so we can actually know what source is actually included ?
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months