[JBoss JIRA] (JBIDE-21608) "Show In -> Web Browser via Live Reload" on EJB module should be disabled
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21608?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-21608:
-------------------------------------
please make sure the openshift server can still use livereload
> "Show In -> Web Browser via Live Reload" on EJB module should be disabled
> -------------------------------------------------------------------------
>
> Key: JBIDE-21608
> URL: https://issues.jboss.org/browse/JBIDE-21608
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: livereload
> Affects Versions: 4.3.1.Beta2
> Reporter: Martin Malina
> Assignee: Dmitry Bocharov
> Fix For: 4.4.x
>
>
> This is a followup of JBIDE-21138 . When you deploy an ejb module, all the items in Server View under Show in are enabled, but they don't do anything. They should be disabled.
> Rob did his part for Show in Server, but he says separate JIRAs are needed in other components.
> So for Livereload, there are these two items that should be disabled on an ejb module:
> Show in -> Web Browser via Livereload
> Show in -> Web Browser on External device
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22586) JBT agg site build fetches sources from master instead of 4.4.0.x branch, resulting in SHA conflict.
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22586?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-22586:
------------------------------------
And, when I build locally, I get the correct a86 sha:
{code:title=/home/nboldt/eclipse/workspace-jboss/jbosstools-github-master/jbosstools-base/common/plugins/org.jboss.tools.common/target/org.jboss.tools.common-3.8.0-SNAPSHOT.jar/META-INF/MANIFEST.MF}
Eclipse-SourceReferences: scm:git:https://github.com/jbosstools/jbosst
ools-base.git;path="common/plugins/org.jboss.tools.common";commitId=a
86fe511763b04d7f43059082ad49aa96bed1bc5{code}
> JBT agg site build fetches sources from master instead of 4.4.0.x branch, resulting in SHA conflict.
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22586
> URL: https://issues.jboss.org/browse/JBIDE-22586
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, updatesite
> Affects Versions: 4.4.0.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.x
>
> Attachments: base-wrong-sources-in-src.zip.png, base-wrong-sources-in-src.zip2.png, base-wrong-sources-in-src.zip3.png
>
>
> For some reason the current JBT agg site build is attempting to fetch sources from master branch instead of 4.4.0.x branch, resulting in this SHA conflict.
> {code}
> [ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:repository-utils:0.25.0-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_4.4.neon/sources/aggregate/site/target/buildinfo/buildinfo_jbosstools-base.json
> [ERROR] contains a86fe511763b04d7f43059082ad49aa96bed1bc5, but upstream jbosstools-base project's MANIFEST.MF has Eclipse-SourceReferences
> [ERROR] commitId 971627a3892e034feee31845f7a01d1cb45cf585.
> [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.{code}
> -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/devst...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22586) JBT agg site build fetches sources from master instead of 4.4.0.x branch, resulting in SHA conflict.
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22586?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-22586:
------------------------------------
Should mention too that the base build is using the correct SHA a86fe511763b04d7f43059082ad49aa96bed1bc5 when building [1], and the aggregate fetches the correct json too [2]. So no idea why the org.jboss.tools.common plugin itself has a different SHA in its MANIFEST.MF 's Eclipse-SourceReferences = 971627a3892e034feee31845f7a01d1cb45cf585.
[1] http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bas...
[2] http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bui...
> JBT agg site build fetches sources from master instead of 4.4.0.x branch, resulting in SHA conflict.
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22586
> URL: https://issues.jboss.org/browse/JBIDE-22586
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, updatesite
> Affects Versions: 4.4.0.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.x
>
> Attachments: base-wrong-sources-in-src.zip.png, base-wrong-sources-in-src.zip2.png, base-wrong-sources-in-src.zip3.png
>
>
> For some reason the current JBT agg site build is attempting to fetch sources from master branch instead of 4.4.0.x branch, resulting in this SHA conflict.
> {code}
> [ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:repository-utils:0.25.0-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_4.4.neon/sources/aggregate/site/target/buildinfo/buildinfo_jbosstools-base.json
> [ERROR] contains a86fe511763b04d7f43059082ad49aa96bed1bc5, but upstream jbosstools-base project's MANIFEST.MF has Eclipse-SourceReferences
> [ERROR] commitId 971627a3892e034feee31845f7a01d1cb45cf585.
> [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.{code}
> -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/devst...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22586) JBT agg site build fetches sources from master instead of 4.4.0.x branch, resulting in SHA conflict.
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22586?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-22586:
------------------------------------
Same version of base sources fetched in devstudio build, so same problem there too:
{code}
[INFO] --- repository-utils:0.25.0-SNAPSHOT:fetch-sources-from-manifests (fetch-sources) @ com.jboss.devstudio.core.site ---
[INFO] Downloaded: jbosstools-base_971627a3892e034feee31845f7a01d1cb45cf585_sources.zip (23.6 M)
{code}
> JBT agg site build fetches sources from master instead of 4.4.0.x branch, resulting in SHA conflict.
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22586
> URL: https://issues.jboss.org/browse/JBIDE-22586
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, updatesite
> Affects Versions: 4.4.0.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.x
>
> Attachments: base-wrong-sources-in-src.zip.png, base-wrong-sources-in-src.zip2.png, base-wrong-sources-in-src.zip3.png
>
>
> For some reason the current JBT agg site build is attempting to fetch sources from master branch instead of 4.4.0.x branch, resulting in this SHA conflict.
> {code}
> [ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:repository-utils:0.25.0-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_4.4.neon/sources/aggregate/site/target/buildinfo/buildinfo_jbosstools-base.json
> [ERROR] contains a86fe511763b04d7f43059082ad49aa96bed1bc5, but upstream jbosstools-base project's MANIFEST.MF has Eclipse-SourceReferences
> [ERROR] commitId 971627a3892e034feee31845f7a01d1cb45cf585.
> [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.{code}
> -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/devst...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22586) JBT agg site build fetches sources from master instead of 4.4.0.x branch, resulting in SHA conflict.
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22586?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-22586 at 6/10/16 9:27 AM:
-------------------------------------------------------------
Same version of base sources fetched in devstudio build, so same problem there too:
{code}
[INFO] --- repository-utils:0.25.0-SNAPSHOT:fetch-sources-from-manifests (fetch-sources) @ com.jboss.devstudio.core.site ---
[INFO] Downloaded: jbosstools-base_971627a3892e034feee31845f7a01d1cb45cf585_sources.zip (23.6 M)
{code}
-- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/devst...
was (Author: nickboldt):
Same version of base sources fetched in devstudio build, so same problem there too:
{code}
[INFO] --- repository-utils:0.25.0-SNAPSHOT:fetch-sources-from-manifests (fetch-sources) @ com.jboss.devstudio.core.site ---
[INFO] Downloaded: jbosstools-base_971627a3892e034feee31845f7a01d1cb45cf585_sources.zip (23.6 M)
{code}
> JBT agg site build fetches sources from master instead of 4.4.0.x branch, resulting in SHA conflict.
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22586
> URL: https://issues.jboss.org/browse/JBIDE-22586
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, updatesite
> Affects Versions: 4.4.0.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.x
>
> Attachments: base-wrong-sources-in-src.zip.png, base-wrong-sources-in-src.zip2.png, base-wrong-sources-in-src.zip3.png
>
>
> For some reason the current JBT agg site build is attempting to fetch sources from master branch instead of 4.4.0.x branch, resulting in this SHA conflict.
> {code}
> [ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:repository-utils:0.25.0-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_4.4.neon/sources/aggregate/site/target/buildinfo/buildinfo_jbosstools-base.json
> [ERROR] contains a86fe511763b04d7f43059082ad49aa96bed1bc5, but upstream jbosstools-base project's MANIFEST.MF has Eclipse-SourceReferences
> [ERROR] commitId 971627a3892e034feee31845f7a01d1cb45cf585.
> [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.{code}
> -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/devst...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22586) JBT agg site build fetches sources from master instead of 4.4.0.x branch, resulting in SHA conflict.
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22586?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-22586:
-------------------------------
Attachment: base-wrong-sources-in-src.zip.png
base-wrong-sources-in-src.zip2.png
base-wrong-sources-in-src.zip3.png
> JBT agg site build fetches sources from master instead of 4.4.0.x branch, resulting in SHA conflict.
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22586
> URL: https://issues.jboss.org/browse/JBIDE-22586
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, updatesite
> Affects Versions: 4.4.0.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.x
>
> Attachments: base-wrong-sources-in-src.zip.png, base-wrong-sources-in-src.zip2.png, base-wrong-sources-in-src.zip3.png
>
>
> For some reason the current JBT agg site build is attempting to fetch sources from master branch instead of 4.4.0.x branch, resulting in this SHA conflict.
> {code}
> [ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:repository-utils:0.25.0-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_4.4.neon/sources/aggregate/site/target/buildinfo/buildinfo_jbosstools-base.json
> [ERROR] contains a86fe511763b04d7f43059082ad49aa96bed1bc5, but upstream jbosstools-base project's MANIFEST.MF has Eclipse-SourceReferences
> [ERROR] commitId 971627a3892e034feee31845f7a01d1cb45cf585.
> [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.{code}
> -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/devst...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22586) JBT agg site build fetches sources from master instead of 4.4.0.x branch, resulting in SHA conflict.
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22586?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-22586:
------------------------------------
Curiously, the a86 commit is the correct one, done in master branch but also in 4.4.0.x:
https://github.com/jbosstools/jbosstools-base/commit/a86fe511763b04d7f430...
https://github.com/jbosstools/jbosstools-base/commits/jbosstools-4.4.0.x
But the sources fetched into the aggregate zip are those from the 971 commit, which is the wrong source:
https://github.com/jbosstools/jbosstools-base/commit/971627a3892e034feee3...
Functionally, I don't think this glitch shouldn't block the release. It's just ugly that the source zip contains sources for 4.4.1.Alpha1 bits instead of 4.4.0.Final.
If I could figure out how to make the build use the correct SHA when fetching sources, I'd respin... but I've no idea how to fix this, or why it's ONLY happening for base.
> JBT agg site build fetches sources from master instead of 4.4.0.x branch, resulting in SHA conflict.
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22586
> URL: https://issues.jboss.org/browse/JBIDE-22586
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, updatesite
> Affects Versions: 4.4.0.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.x
>
>
> For some reason the current JBT agg site build is attempting to fetch sources from master branch instead of 4.4.0.x branch, resulting in this SHA conflict.
> {code}
> [ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:repository-utils:0.25.0-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_4.4.neon/sources/aggregate/site/target/buildinfo/buildinfo_jbosstools-base.json
> [ERROR] contains a86fe511763b04d7f43059082ad49aa96bed1bc5, but upstream jbosstools-base project's MANIFEST.MF has Eclipse-SourceReferences
> [ERROR] commitId 971627a3892e034feee31845f7a01d1cb45cf585.
> [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.{code}
> -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/devst...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months