[JBoss JIRA] (JBTIS-294) JBTIS build fails because SwitchYard is not compatible with EMF Compare 3.0
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-294?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky closed JBTIS-294.
-----------------------------------
Closed as obsolete
> JBTIS build fails because SwitchYard is not compatible with EMF Compare 3.0
> ---------------------------------------------------------------------------
>
> Key: JBTIS-294
> URL: https://issues.jboss.org/browse/JBTIS-294
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: switchyard
> Affects Versions: 4.2.0.Final
> Reporter: Paul Leacu
> Assignee: Rob Cernich
> Fix For: 4.2.0.Final
>
>
> Temporarily removed SwitchYard from the Luna IS component capture.
> [INFO] {osgi.ws=cocoa, osgi.os=macosx, osgi.arch=x86, org.eclipse.update.install.features=true}
> [ERROR] Cannot resolve project dependencies:
> [ERROR] Software being installed: site raw:4.2.0.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):4.2.0-SNAPSHOT
> [ERROR] Missing requirement: org.switchyard.tools.feature.feature.group 1.1.5.v20140403-2328-H5-Final requires 'org.eclipse.emf.compare.feature.group [2.1.0,3.0.0)' but it could not be found
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBTIS-291) New 4.2.0 alpha of base target required
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-291?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky closed JBTIS-291.
-----------------------------------
Closed as obsolete
> New 4.2.0 alpha of base target required
> ---------------------------------------
>
> Key: JBTIS-291
> URL: https://issues.jboss.org/browse/JBTIS-291
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 4.2.0.Final-TP
> Reporter: Paul Richardson
> Assignee: Paul Leacu
> Priority: Critical
> Fix For: 4.2.0.Final-TP
>
>
> The locus component of the base target has been respun hence the plugins are appended with v20131024-0922-B66 and no longer v20131024-0922-B64.
> Consequently, the target does not resolve correctly due to
> {code}
> Adding repository https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/lo...
> [exec] [ERROR] Internal error: java.lang.RuntimeException: Failed to resolve target definition /home/scorpion/.m2/repository/org/jboss/tools/target-platforms/komodo/1.0.0-SNAPSHOT/komodo-1.0.0-SNAPSHOT-komodo.target: Could not find "org.jboss
> .tools.locus.jcip.annotations/1.0.0.Final-v20131024-0922-B64" in the repositories of the current location -> [Help 1]
> [exec] org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: Failed to resolve target definition /home/scorpion/.m2/repository/org/jboss/tools/target-platforms/komodo/1.0.0-SNAPSHOT/komodo-1.0.0-SNAPSHOT-komodo.
> target
> {code}
> Note: komodo is the renamed base target.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBTIS-313) Generate source bundles for IS component features.
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-313?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky closed JBTIS-313.
-----------------------------------
Verified with JBDS-IS 8.0.6.GA
> Generate source bundles for IS component features.
> --------------------------------------------------
>
> Key: JBTIS-313
> URL: https://issues.jboss.org/browse/JBTIS-313
> Project: JBoss Tools Integration Stack
> Issue Type: Sub-task
> Components: Fuse IDE
> Affects Versions: 8.0.0.GA
> Reporter: Paul Leacu
> Assignee: Paul Leacu
> Fix For: 4.2.0.Final , 8.0.0.GA
>
>
> 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...
> Some that don't:
> http://download.jboss.org/jbosstools/updates/integration/kepler/integrati...
> 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.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBTIS-314) Generate source bundles for IS component features.
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-314?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky closed JBTIS-314.
-----------------------------------
Verified with JBDS-IS 8.0.6.GA
> 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
> Components: switchyard
> Affects Versions: 8.0.0.GA
> Reporter: Paul Leacu
> Assignee: Paul Leacu
>
> 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.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBTIS-318) Generate source bundles for IS component features.
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-318?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky closed JBTIS-318.
-----------------------------------
Verified with JBDS-IS 8.0.1.GA
> Generate source bundles for IS component features.
> --------------------------------------------------
>
> Key: JBTIS-318
> URL: https://issues.jboss.org/browse/JBTIS-318
> Project: JBoss Tools Integration Stack
> Issue Type: Sub-task
> Components: drools/ jBPM
> Affects Versions: 4.2.0.Final , 8.0.0.GA
> Reporter: Paul Leacu
> Assignee: Kris Verlaenen
> Fix For: 4.0.0, 4.2.0.Final
>
>
> jBPM/ Drools must generate source bundles for features that will be aggregated (uncategorized) by JBDSIS.
> Courtesy [~nickboldt]:
> 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...
> Some that don't:
> http://download.jboss.org/jbosstools/updates/integration/kepler/integrati...
> 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.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBTIS-315) Generate source bundles for IS component features.
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-315?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky closed JBTIS-315.
-----------------------------------
Verified with JBDS-IS 8.0.0.GA
> Generate source bundles for IS component features.
> --------------------------------------------------
>
> Key: JBTIS-315
> URL: https://issues.jboss.org/browse/JBTIS-315
> Project: JBoss Tools Integration Stack
> Issue Type: Sub-task
> Components: teiid
> Affects Versions: 8.0.0.GA
> Reporter: Paul Leacu
> Assignee: Barry LaFond
> Fix For: 4.2.0.Final , 8.0.0.GA
>
>
> 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.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22361) OpenShift Explorer: Watcher does not work
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22361?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-22361:
----------------------------------
Description: When I am trying to create a new application based on eap 6.4 template and I am having only one project in OpenShift Explorer view, watcher does not work. Once I create a new EAP 6.4 application there is eap-app-1-build pod all the time in running state. Once watcher should update resources automatically, service is collapsed, also project is collapsed, but after expanding those tree items, there is still old pod. Current pod is visible only upon refresh of a project. (was: When I am trying to create a new application based on eap 6.4 template and I am having only one project in OpenShift Explorer view, watcher does not work. Service is collapsed, sometimes even several times. Upon expanding an existing service it still contains old pod (either application on build pod). So once I create a new EAP 6.4 application there is eap-app-1-build pod all the time in running state. Application pod is visible only upon refresh of a project.)
> OpenShift Explorer: Watcher does not work
> -----------------------------------------
>
> Key: JBIDE-22361
> URL: https://issues.jboss.org/browse/JBIDE-22361
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha2
> Reporter: Marián Labuda
> Priority: Critical
> Labels: explorer, openshift_v3
>
> When I am trying to create a new application based on eap 6.4 template and I am having only one project in OpenShift Explorer view, watcher does not work. Once I create a new EAP 6.4 application there is eap-app-1-build pod all the time in running state. Once watcher should update resources automatically, service is collapsed, also project is collapsed, but after expanding those tree items, there is still old pod. Current pod is visible only upon refresh of a project.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22361) OpenShift Explorer: Watcher does not work
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-22361:
-------------------------------------
Summary: OpenShift Explorer: Watcher does not work
Key: JBIDE-22361
URL: https://issues.jboss.org/browse/JBIDE-22361
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.4.0.Alpha2
Reporter: Marián Labuda
When I am trying to create a new application based on eap 6.4 template and I am having only one project in OpenShift Explorer view, watcher does not work. Service is collapsed, sometimes even several times. Upon expanding an existing service it still contains old pod (either application on build pod). So once I create a new EAP 6.4 application there is eap-app-1-build pod all the time in running state. Application pod is visible only upon refresh of a project.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months