[JBoss JIRA] (JBIDE-18093) Special character "®" in manifest.yml --> Description leads to errors when accessing OSE from JBDS
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18093?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-18093:
-------------------------------------
Labels: application_wizard (was: )
> 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: Bug
> Components: openshift
> Affects Versions: 4.1.1.Final
> Reporter: Max Rydahl Andersen
> Assignee: Andre Dietisheim
> Labels: application_wizard
> Fix For: 4.2.0.CR1
>
> Attachments: illegal-character.png, 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 Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18093?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-18093:
-------------------------------------
Issue Type: Bug (was: Feature Request)
> 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: Bug
> Components: openshift
> Affects Versions: 4.1.1.Final
> Reporter: Max Rydahl Andersen
> Assignee: Andre Dietisheim
> Labels: application_wizard
> Fix For: 4.2.0.CR1
>
> Attachments: illegal-character.png, 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 Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18093?page=com.atlassian.jira.plugi... ]
Andre Dietisheim resolved JBIDE-18093.
--------------------------------------
Resolution: Done
> 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: Bug
> Components: openshift
> Affects Versions: 4.1.1.Final
> Reporter: Max Rydahl Andersen
> Assignee: Andre Dietisheim
> Fix For: 4.2.0.CR1
>
> Attachments: illegal-character.png, 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 Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18093?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-18093:
-------------------------------------
Affects Version/s: 4.1.1.Final
> 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
> Affects Versions: 4.1.1.Final
> Reporter: Max Rydahl Andersen
> Assignee: Andre Dietisheim
> Fix For: 4.2.0.CR1
>
> Attachments: illegal-character.png, 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 Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18093?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-18093 at 8/28/14 11:17 AM:
--------------------------------------------------------------------
I could finally reproduce this in JBDS 7.1.1:
!illegal-character.png!
while I cant in JBDS 8 so the issue is fixed in upcoming JBDS 8 which will become GA in October. So upgrading will fix the issue.
was (Author: adietish):
I could finally reproduce this in JBDS 7.1.1 while I cant in JBDS 8 so the issue is fixed in upcoming JBDS 8 which will become GA in October. So upgrading will fix the issue.
> 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
> Affects Versions: 4.1.1.Final
> Reporter: Max Rydahl Andersen
> Assignee: Andre Dietisheim
> Fix For: 4.2.0.CR1
>
> Attachments: illegal-character.png, 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 Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18093?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-18093:
-------------------------------------
Attachment: illegal-character.png
> 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
> Affects Versions: 4.1.1.Final
> Reporter: Max Rydahl Andersen
> Assignee: Andre Dietisheim
> Fix For: 4.2.0.CR1
>
> Attachments: illegal-character.png, 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 Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18093?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-18093:
------------------------------------------
I could finally reproduce this in JBDS 7.1.1 while I cant in JBDS 8 so the issue is fixed in upcoming JBDS 8 which will become GA in October. So upgrading will fix the issue.
> 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] (JBTIS-312) Generate source bundles for IS component features.
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-312?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBTIS-312:
----------------------------------
Woo! [~lhein] I see you have source features in your https://github.com/fusesource/fuseide/blob/master/site/category.xml already, too.
FYI, I digested the above long list of ways to enable source features/plugins/src-zips here:
https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/buil...
> 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-313) Generate source bundles for IS component features.
by Paul Leacu (JIRA)
Paul Leacu created JBTIS-313:
--------------------------------
Summary: 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
Security Level: Public (Everyone can see)
Components: Fuse IDE
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 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.3.1#6329)
11 years, 7 months