[JBoss JIRA] (JBTIS-312) Generate source bundles for IS component features.
by Rob Cernich (JIRA)
[ https://issues.jboss.org/browse/JBTIS-312?page=com.atlassian.jira.plugin.... ]
Rob Cernich commented on JBTIS-312:
-----------------------------------
[~pleacu] you should create JIRA in the specific projects to track this. If this is an important issue, you should also bring it forward in the program management meetings so it can be targeted for a specific release.
> Generate source bundles for IS component features.
> --------------------------------------------------
>
> Key: JBTIS-312
> URL: https://issues.jboss.org/browse/JBTIS-312
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Fuse IDE, switchyard, teiid
> Affects Versions: 8.0.0.Alpha1
> Reporter: Paul Leacu
> Assignee: Paul Leacu
>
> IS components 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.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBTIS-312) Generate source bundles for IS component features.
by Paul Leacu (JIRA)
Paul Leacu created JBTIS-312:
--------------------------------
Summary: Generate source bundles for IS component features.
Key: JBTIS-312
URL: https://issues.jboss.org/browse/JBTIS-312
Project: JBoss Tools Integration Stack
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Fuse IDE, switchyard, teiid
Affects Versions: 8.0.0.Alpha1
Reporter: Paul Leacu
Assignee: Paul Leacu
IS components 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.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-16898) no error handling for nonexisting remote home
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16898?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-16898.
---------------------------------
Assignee: Rob Stryker
Resolution: Done
We now check for the existence of the remote server home, and, if it does not exist, we throw a CoreException, which effectively aborts the launch and pops up a wtp-framework error dialog, and marks the server as stopped.
> no error handling for nonexisting remote home
> ---------------------------------------------
>
> Key: JBIDE-16898
> URL: https://issues.jboss.org/browse/JBIDE-16898
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Reporter: Max Rydahl Andersen
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.2.0.CR1
>
>
> Downloaded EAP 6.2 via downlod runtimes.
> configured it to use remote, entered in bogus name for home folder.
> This is in the console log:
> "/>
> />
> Error: Unable to access jarfile urft/jboss-modules.jar
> JBTOOLS_SERVER_START_CMD:JBoss Enterprise Application Platform 6.1+1395830330282:11785
> />"
> I would have expected some validation or better info in the console on what users should do now.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18125) Error: "Hybrid Mobile Engine Library pre-compilation". For input string: "L"
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18125?page=com.atlassian.jira.plugi... ]
Gorkem Ercan commented on JBIDE-18125:
--------------------------------------
[~vpakan] although most discussion happened on Eclipse bugzilla, we need to spend a few test cycles on this. As part of the fix for this one we have changed how we determined the target level when compiling a cordova project for Android. In the past we were using the highest possible android target on the system to compile cordova projects, now we are using the target from the project.properties file on the cordova distribution to select a target.
To properly test this fix. You can remove all android-19 targets from your system and then observe that the compilation fails with a message for a cordova project that is using a cordova engine 3.3 or later. Also if you have a android-18 target in place switching to cordova 3.2 engine should fix the problem.
Also a second test should involve Android L preview and observe that we can properly create an app and run on that emulator.
> Error: "Hybrid Mobile Engine Library pre-compilation". For input string: "L"
> ----------------------------------------------------------------------------
>
> Key: JBIDE-18125
> URL: https://issues.jboss.org/browse/JBIDE-18125
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Reporter: eduardo de souza
> Assignee: Gorkem Ercan
> Priority: Blocker
> Fix For: 4.2.0.CR1
>
>
> An internal error occurred during: "Hybrid Mobile Engine Library pre-compilation".
> For input string: "L"
> This message appear when I select the wizard -> Mobile -> Hybrid Mobile (Cordova) Application Project
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18093) Special character "®" in manifest.yml --> Description leads to errors when accessing OSE from JBDS
by Brenton Leanhardt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18093?page=com.atlassian.jira.plugi... ]
Brenton Leanhardt commented on JBIDE-18093:
-------------------------------------------
For clarification, the original Bugzilla only changed the cartridge description. For future testing I also changed the Display-Name. The extra  was something I added.
> Special character "®" in manifest.yml --> Description leads to errors when accessing OSE from JBDS
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18093
> URL: https://issues.jboss.org/browse/JBIDE-18093
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Reporter: Max Rydahl Andersen
> Assignee: Andre Dietisheim
> Fix For: 4.2.0.CR1
>
> Attachments: mock1b.png, special-character-mock-cartridges.png
>
>
> Description of problem:
> I have developed a custom cartridge for OSE and placed the special character "®" (registered trademark) in the description field within my "manifest.yml". The cartridge could be installed correctly via WebUI and was also working fine from a technical point of view.
> However, when trying to access the OSE instance from JBDS via the Openshift Explorer plugin, I always got the following error:
> Invalid value for input string: "00ae"
> The string "00ae" is the unicode representation of my special character. After removing everything worked fine again. The OpenShift Explorer was completely unusable in this scenario! So only one installed cartridge with this special character can poison a whole installation and affect ALL users!!!
> Version-Release number of selected component (if applicable):
> OSE 2.2 (Developer Image)
> How reproducible:
> Yes.
> Steps to Reproduce:
> 1. Create a custom cartridge and add a "®" to the description field of your manifest.yml.
> 2. Install the cartridge according to doc.
> 3. Start JBDS and try to work with your OSE instance via the OpenShift Explorer plugin (e.g. try to add an application)
> Actual results:
> Expected results:
> Additional info:
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18093) Special character "®" in manifest.yml --> Description leads to errors when accessing OSE from JBDS
by Brenton Leanhardt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18093?page=com.atlassian.jira.plugi... ]
Brenton Leanhardt edited comment on JBIDE-18093 at 8/28/14 9:47 AM:
--------------------------------------------------------------------
For clarification, the original Bugzilla only changed the cartridge description. For further testing I also changed the Display-Name. The extra  was something I added.
was (Author: bleanhar):
For clarification, the original Bugzilla only changed the cartridge description. For future testing I also changed the Display-Name. The extra  was something I added.
> Special character "®" in manifest.yml --> Description leads to errors when accessing OSE from JBDS
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18093
> URL: https://issues.jboss.org/browse/JBIDE-18093
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Reporter: Max Rydahl Andersen
> Assignee: Andre Dietisheim
> Fix For: 4.2.0.CR1
>
> Attachments: mock1b.png, special-character-mock-cartridges.png
>
>
> Description of problem:
> I have developed a custom cartridge for OSE and placed the special character "®" (registered trademark) in the description field within my "manifest.yml". The cartridge could be installed correctly via WebUI and was also working fine from a technical point of view.
> However, when trying to access the OSE instance from JBDS via the Openshift Explorer plugin, I always got the following error:
> Invalid value for input string: "00ae"
> The string "00ae" is the unicode representation of my special character. After removing everything worked fine again. The OpenShift Explorer was completely unusable in this scenario! So only one installed cartridge with this special character can poison a whole installation and affect ALL users!!!
> Version-Release number of selected component (if applicable):
> OSE 2.2 (Developer Image)
> How reproducible:
> Yes.
> Steps to Reproduce:
> 1. Create a custom cartridge and add a "®" to the description field of your manifest.yml.
> 2. Install the cartridge according to doc.
> 3. Start JBDS and try to work with your OSE instance via the OpenShift Explorer plugin (e.g. try to add an application)
> Actual results:
> Expected results:
> Additional info:
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBDS-3115) Include Ionic Palette in Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3115?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3115:
----------------------------------
[~maxandersen] How does the the wizard know which connector it's installing if there are two with the same ID? How can you guarantee it always picks the "correct" one? IMHO, this is a bad idea.
Does the wizard know about the concept of early access and can it therefore deduce that you want the EA one? What if you only enabled EA for VJET but don't want the angularJS EA stuff?
> Include Ionic Palette in Central
> --------------------------------
>
> Key: JBDS-3115
> URL: https://issues.jboss.org/browse/JBDS-3115
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: p2-product
> Affects Versions: 8.0.0.CR1
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Priority: Blocker
> Fix For: 8.0.0.CR1
>
> Attachments: 3115-jbds-vs-jbt-connector.differences.central.png, 3115-jbds-vs-jbt-connector.differences.png
>
>
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-15931) Explorer: Useless menu items on multiple application selection
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15931?page=com.atlassian.jira.plugi... ]
Marián Labuda resolved JBIDE-15931.
-----------------------------------
Assignee: Marián Labuda
Fix Version/s: 4.2.0.CR1
(was: 4.2.x)
Resolution: Done
This has been fixed in some commit.
> Explorer: Useless menu items on multiple application selection
> --------------------------------------------------------------
>
> Key: JBIDE-15931
> URL: https://issues.jboss.org/browse/JBIDE-15931
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.1.Beta1
> Reporter: Marián Labuda
> Assignee: Marián Labuda
> Priority: Minor
> Labels: explorer
> Fix For: 4.2.0.CR1
>
> Attachments: multipleappselection.png
>
>
> There are 2 useless menu items in context menu of the multiple application selection. See attached image.
> It is useless to have menu item to display details about application, also server adapter is 1 to 1 relation application:adapter, so this is I think useless too.
> Also it's considerable, whether context menu should contain New - Connection menu items (if I am in context menu of application / multiple application I do not expect to have such possibility).
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months