[JBoss JIRA] (JBTIS-392) Generate jbdsis target platform without community bits
by Paul Leacu (JIRA)
Paul Leacu created JBTIS-392:
--------------------------------
Summary: Generate jbdsis target platform without community bits
Key: JBTIS-392
URL: https://issues.jboss.org/browse/JBTIS-392
Project: JBoss Tools Integration Stack
Issue Type: Bug
Components: target-platform
Affects Versions: 4.2.1.CR1-TP
Reporter: Paul Leacu
Assignee: Paul Leacu
Currently the JBDSIS production target platform repo is a copy of the JBTIS target platform repo. This introduces community bits where they don't belong. e.g.
<unit id="org.jboss.tools.community.central.feature.feature.group" version="1.3.0.Final-v20141016-1914-B105"/>
<unit id="org.jboss.tools.community.project.examples.feature.feature.group" version="2.0.0.Final-v20141016-1914-B105"/>
*Reason:* ...
*Project page/sources:* ...
*Version:* ....
*License and owner:* ...
*Original p2 repo:* http://third-party-vendor.com/path/to/updates-site/
*JBoss mirror:* http://downloads.jboss.org/jbosstools/updates/requirements/<projectName>
*Include Sources:* Yes|No
*Affected projects:*
*Include in JBDS:* Yes|No
*Type of dependency:* testing|central-only|distribution
*List of bundles added/removed:*
{code}
suggested diff on the .target files
{code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBDS-3199) Creating a new HTML5 "from scratch" retains "kitchensink" string in datasources instead of picking up actual project names
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-3199?page=com.atlassian.jira.plugin.... ]
Fred Bricon commented on JBDS-3199:
-----------------------------------
In richfaces kitchensink, when enabling the debug profile, the build breaks with "Project build error: 'dependencies.dependency.version' for com.sun.faces:jsf-impl:jar is missing"
I don't think that profile is useful/needed at all. JBT/JBDS is capable of identifying the exact JSF impl used by the application server, while debugging the app.
{noformat}
<profile>
<!-- Activate this profile to identify to the IDE which version of the JSF impl is being used by the
application server.-->
<!-- Be sure to include the JBoss maven repository, as the JBoss jsf-impl artifacts are not in maven
central. -->
<!-- See: https://community.jboss.org/wiki/MavenGettingStarted-Developers -->
<id>debug</id>
<dependencies>
<!-- Import the JSF impl, to allow for application debugging -->
<dependency>
<groupId>com.sun.faces</groupId>
<artifactId>jsf-impl</artifactId>
<scope>provided</scope>
</dependency>
</dependencies>
</profile>
{noformat}
other minor annoyance is the kitchensink cheatsheet that needs to s/Kitchensink-rf/${artifactId}/g
> Creating a new HTML5 "from scratch" retains "kitchensink" string in datasources instead of picking up actual project names
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3199
> URL: https://issues.jboss.org/browse/JBDS-3199
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: central, upstream
> Affects Versions: 8.0.0.GA
> Reporter: Len DiMaggio
> Assignee: Fred Bricon
> Fix For: 8.1.0.GA
>
>
> These "kitchensink" strings are retained:
> grep -ir kitchen *
> main/resources/META-INF/persistence.xml: <jta-data-source>java:jboss/datasources/KitchensinkHTML5MobileQuickstartDS</jta-data-source>
> main/webapp/WEB-INF/kitchensink-quickstart-ds.xml: <datasource jndi-name="java:jboss/datasources/KitchensinkHTML5MobileQuickstartDS"
> main/webapp/WEB-INF/kitchensink-quickstart-ds.xml: pool-name="kitchensink-quickstart" enabled="true"
> test/resources/arquillian-ds.xml: <datasource jndi-name="java:jboss/datasources/KitchensinkHTML5MobileTestDS"
> test/resources/META-INF/test-persistence.xml: <jta-data-source>java:jboss/datasources/KitchensinkHTML5MobileTestDS</jta-data-source>
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-18974) Latest Ionic app based on tabs template is not shown on HTM5 Preview
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18974?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov updated JBIDE-18974:
-------------------------------------------
Fix Version/s: 4.3.0.Alpha2
(was: 4.3.0.Alpha1)
> Latest Ionic app based on tabs template is not shown on HTM5 Preview
> --------------------------------------------------------------------
>
> Key: JBIDE-18974
> URL: https://issues.jboss.org/browse/JBIDE-18974
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 4.2.1.Final
> Environment: Fedora 20 Linux x86_64
> OpenJDK 7
> SWT_GTK3=1
> Reporter: Denis Golovin
> Assignee: Konstantin Marmalyukov
> Fix For: 4.3.0.Alpha2
>
> Attachments: screenshot1.png, screenshot2.png
>
>
> The app works fine in internal browser, bit not in HTML5 Preview (see image screenshot1.png below).
> The same issue when I open external browser form preview. But after a while Refresh in external browser finally shows the page (see screenshot2.png below).
> After that it appears in preview as well.
> !screenshot1.png!
> !screenshot2.png!
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-18227) JS console.debug() displays message to console with LOG prefix
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18227?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov updated JBIDE-18227:
-------------------------------------------
Fix Version/s: 4.3.0.Alpha2
(was: 4.3.0.Alpha1)
> JS console.debug() displays message to console with LOG prefix
> --------------------------------------------------------------
>
> Key: JBIDE-18227
> URL: https://issues.jboss.org/browse/JBIDE-18227
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim, cordovasim
> Affects Versions: 4.2.0.CR1
> Environment: JBDS 8.0.0.CR1-v20140831-0335-B201
> Reporter: Vlado Pakan
> Assignee: Ilya Buziuk
> Priority: Minor
> Fix For: 4.3.0.Alpha2
>
>
> JavaScript command console.debug("debug message") invoked within page opened in Browsersim is displaying this string to Eclipse console:
> {noformat}
> !JavaScript LOG: debug message
> {noformat}
> It should display this message maybe also with different color then log message is displayed:
> {noformat}
> !JavaScript DEBUG: debug message
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19181) correct naming of internal packages so that they're consistent across all openshift plugins
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19181?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-19181:
-------------------------------------
Description:
Internal packages across the openshift plugins are non-consistent:
ex.
org.jboss.tools.openshift.client: org.jboss.tools.openshift.client.internal
org.jboss.tools.openshift.express.client: org.jboss.tools.openshift.express.client.internal
the base is imho org.jboss.tools.openshift and thus internal packages should always be at org.jboss.tools.openshift.internal across plugins.
For reference, here's the official Eclipse documentation on the topic: http://wiki.eclipse.org/index.php/Naming_Conventions#Java_Packages
{quote}
org.eclipse.jdt.internal.core.compiler - Correct usage
org.eclipse.jdt.core.internal.compiler - Incorrect. internal should immediately follow subproject name.
org.eclipse.core.internal.resources - Correct usage
org.eclipse.internal.core.resources - Incorrect. internal should never immediately follow org.eclipse.
org.eclipse.core.resources.internal - Incorrect. internal should immediately follow Eclipse Platform component name.
{quote}
was:
Internal packages across the openshift plugins are non-consistent:
ex.
org.jboss.tools.openshift.client: org.jboss.tools.openshift.client.internal
org.jboss.tools.openshift.express.client: org.jboss.tools.openshift.express.client.internal
the base is imho org.jboss.tools.openshift and thus internal packages should always be at org.jboss.tools.openshift.internal across plugins.
For reference, here's the official Eclipse: http://wiki.eclipse.org/index.php/Naming_Conventions#Java_Packages
{quote}
org.eclipse.jdt.internal.core.compiler - Correct usage
org.eclipse.jdt.core.internal.compiler - Incorrect. internal should immediately follow subproject name.
org.eclipse.core.internal.resources - Correct usage
org.eclipse.internal.core.resources - Incorrect. internal should never immediately follow org.eclipse.
org.eclipse.core.resources.internal - Incorrect. internal should immediately follow Eclipse Platform component name.
{quote}
> correct naming of internal packages so that they're consistent across all openshift plugins
> -------------------------------------------------------------------------------------------
>
> Key: JBIDE-19181
> URL: https://issues.jboss.org/browse/JBIDE-19181
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.0.Alpha1
> Reporter: Andre Dietisheim
> Fix For: 4.3.0.Alpha1
>
>
> Internal packages across the openshift plugins are non-consistent:
> ex.
> org.jboss.tools.openshift.client: org.jboss.tools.openshift.client.internal
> org.jboss.tools.openshift.express.client: org.jboss.tools.openshift.express.client.internal
> the base is imho org.jboss.tools.openshift and thus internal packages should always be at org.jboss.tools.openshift.internal across plugins.
> For reference, here's the official Eclipse documentation on the topic: http://wiki.eclipse.org/index.php/Naming_Conventions#Java_Packages
> {quote}
> org.eclipse.jdt.internal.core.compiler - Correct usage
> org.eclipse.jdt.core.internal.compiler - Incorrect. internal should immediately follow subproject name.
> org.eclipse.core.internal.resources - Correct usage
> org.eclipse.internal.core.resources - Incorrect. internal should never immediately follow org.eclipse.
> org.eclipse.core.resources.internal - Incorrect. internal should immediately follow Eclipse Platform component name.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months