[JBoss JIRA] (JBIDE-18541) Add ability to generate "flavours" of the site
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18541?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-18541 at 10/8/14 10:33 AM:
--------------------------------------------------------------
We could do this instead, using SPECIFIC releases, not pointers:
{code}
<references size="6">
<repository options="1" type="0" uri="http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4..." ... />
<repository options="1" type="1" uri="http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4..." ... />
<repository options="1" type="0" uri="http://download.jboss.org/jbosstools/static/releases/jbosstools-4.2.0.CR1..." ... />
<repository options="1" type="1" uri="http://download.jboss.org/jbosstools/static/releases/jbosstools-4.2.0.CR1..." ... />
<repository options="1" type="0" uri="http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.0.Be..." url="http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.0.Be..."/>
<repository options="1" type="1" uri="http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.0.Be..." url="http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.0.Be..."/>
</references>
{code}
was (Author: nickboldt):
We could do this instead, using SPECIFIC releases, not pointers:
{code}
<references size="6">
<repository options="1" type="0" uri="http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4..." ... />
<repository options="1" type="1" uri="http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4..." ... />
<repository options="1" type="0" uri="http://download.jboss.org/jbosstools/static/releases/jbosstools-4.2.0.CR1..." ... />
<repository options="1" type="1" uri="http://download.jboss.org/jbosstools/static/releases/jbosstools-4.2.0.CR1..." ... />
<repository options="1" type="0" uri="http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/luna/is-..." url="http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/luna/is-..."/>
<repository options="1" type="1" uri="http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/luna/is-..." url="http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/luna/is-..."/>
</references>
{code}
> Add ability to generate "flavours" of the site
> ----------------------------------------------
>
> Key: JBIDE-18541
> URL: https://issues.jboss.org/browse/JBIDE-18541
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build
> Affects Versions: 4.2.0.CR2
> Reporter: Mickael Istria
> Assignee: Mickael Istria
>
> Instead of associating statically sites (target-platform) when creating a repository, the generate-repository-facade mojo could create some indirection files allowing to access the repository in 2 flavours:
> * One plain content only, without any reference: for downstream project aggregation
> * One that also references its dependencies for easy install and testers
> Example:
> {code}
> /integration-stack <-- composited without side effects into /earlyaccess/development/luna/
> content.jar
> artifacts.jar
> /withdeps <--- good for testing/single installs
> /compositeContent.xml -> ../ and ../targetplatform-link/
> /compositeArtifacts.xml
> /targetplatform-link <--- point to what is needed for install (not to be used by higher up composites/aggregates [JBT content, JBT IS content, JBT TP, JBT IS TP, etc.]
> content.xml -> associate pointer to TP using ONLY:
> <references size="4">
> <repository options="1" type="0" uri="http://download.jboss.org/jbosstools/updates/development/luna/" url="http://download.jboss.org/jbosstools/updates/development/luna/"/> (this currently includes *latest* JBT + JBT TP)
> <repository options="1" type="1" uri="http://download.jboss.org/jbosstools/updates/development/luna/" url="http://download.jboss.org/jbosstools/updates/development/luna/"/>
> <repository options="1" type="0" uri="http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/luna/is-..." url="http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/luna/is-..."/>
> <repository options="1" type="1" uri="http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/luna/is-..." url="http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/luna/is-..."/>
> </references>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18541) Add ability to generate "flavours" of the site
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18541?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-18541:
-----------------------------------
Description:
Instead of associating statically sites (target-platform) when creating a repository, the generate-repository-facade mojo could create some indirection files allowing to access the repository in 2 flavours:
* One plain content only, without any reference: for downstream project aggregation
* One that also references its dependencies for easy install and testers
Example:
{code}
/integration-stack <-- composited without side effects into /earlyaccess/development/luna/
content.jar
artifacts.jar
/withdeps <--- good for testing/single installs
/compositeContent.xml -> ../ and ../targetplatform-link/
/compositeArtifacts.xml
/targetplatform-link <--- point to what is needed for install (not to be used by higher up composites/aggregates [JBT content, JBT IS content, JBT TP, JBT IS TP, etc.]
content.xml -> associate pointer to TP using ONLY:
<references size="4">
<repository options="1" type="0" uri="http://download.jboss.org/jbosstools/updates/development/luna/" url="http://download.jboss.org/jbosstools/updates/development/luna/"/> (this currently includes *latest* JBT + JBT TP)
<repository options="1" type="1" uri="http://download.jboss.org/jbosstools/updates/development/luna/" url="http://download.jboss.org/jbosstools/updates/development/luna/"/>
<repository options="1" type="0" uri="http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/luna/is-..." url="http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/luna/is-..."/>
<repository options="1" type="1" uri="http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/luna/is-..." url="http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/luna/is-..."/>
</references>
{code}
was:
Instead of associating statically sites (target-platform) when creating a repository, the generate-repository-facade mojo could create some indirection files allowing to access the repository in 2 flavours:
* One plain content only, without any reference: for downstream project aggregation
* One that also references its dependencies for easy install and testers
{code}
/integration-stack <-- composited without side effects into /earlyaccess/development/luna/
content.jar
artifacts.jar
/withdeps <--- good for testing/single installs
/compositeContent.xml -> ../ and ../targetplatform-link/
/compositeArtifacts.xml
/targetplatform-link <--- point to what is needed for install (not to be used by higher up composites/aggregates [JBT content, JBT IS content, JBT TP, JBT IS TP, etc.]
content.xml -> associate pointer to TP using ONLY:
<references size="4">
<repository options="1" type="0" uri="http://download.jboss.org/jbosstools/updates/development/luna/" url="http://download.jboss.org/jbosstools/updates/development/luna/"/> (this currently includes *latest* JBT + JBT TP)
<repository options="1" type="1" uri="http://download.jboss.org/jbosstools/updates/development/luna/" url="http://download.jboss.org/jbosstools/updates/development/luna/"/>
<repository options="1" type="0" uri="http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/luna/is-..." url="http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/luna/is-..."/>
<repository options="1" type="1" uri="http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/luna/is-..." url="http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/luna/is-..."/>
</references>
{code}
> Add ability to generate "flavours" of the site
> ----------------------------------------------
>
> Key: JBIDE-18541
> URL: https://issues.jboss.org/browse/JBIDE-18541
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build
> Affects Versions: 4.2.0.CR2
> Reporter: Mickael Istria
>
> Instead of associating statically sites (target-platform) when creating a repository, the generate-repository-facade mojo could create some indirection files allowing to access the repository in 2 flavours:
> * One plain content only, without any reference: for downstream project aggregation
> * One that also references its dependencies for easy install and testers
> Example:
> {code}
> /integration-stack <-- composited without side effects into /earlyaccess/development/luna/
> content.jar
> artifacts.jar
> /withdeps <--- good for testing/single installs
> /compositeContent.xml -> ../ and ../targetplatform-link/
> /compositeArtifacts.xml
> /targetplatform-link <--- point to what is needed for install (not to be used by higher up composites/aggregates [JBT content, JBT IS content, JBT TP, JBT IS TP, etc.]
> content.xml -> associate pointer to TP using ONLY:
> <references size="4">
> <repository options="1" type="0" uri="http://download.jboss.org/jbosstools/updates/development/luna/" url="http://download.jboss.org/jbosstools/updates/development/luna/"/> (this currently includes *latest* JBT + JBT TP)
> <repository options="1" type="1" uri="http://download.jboss.org/jbosstools/updates/development/luna/" url="http://download.jboss.org/jbosstools/updates/development/luna/"/>
> <repository options="1" type="0" uri="http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/luna/is-..." url="http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/luna/is-..."/>
> <repository options="1" type="1" uri="http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/luna/is-..." url="http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/luna/is-..."/>
> </references>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18519) Cannot run Browsersim on RHEL6 with GTK3 - error instructs user to install package that is already installed
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18519?page=com.atlassian.jira.plugi... ]
Len DiMaggio updated JBIDE-18519:
---------------------------------
Labels: respin-a (was: )
> Cannot run Browsersim on RHEL6 with GTK3 - error instructs user to install package that is already installed
> ------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18519
> URL: https://issues.jboss.org/browse/JBIDE-18519
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 4.2.0.CR2
> Environment: RHEL 6.5
> Oracle 1.7, 1.8
> Reporter: Len DiMaggio
> Assignee: Konstantin Marmalyukov
> Priority: Critical
> Labels: respin-a
> Fix For: 4.2.0.Final
>
>
> In browsersim properties, GTK2 is the default - and if a RHEL6 user uses Java 1.7 JDK or Java 1.8 on RHEL6 - browsersim seems to function correctly.
> But - is a user attempts to configure GTK3 (with either Oracle 1.7 or 1.8) - in the browsersim properties, browsersim fails to open with this error:
> "To use BrowserSim please install webkitgtk 1.2.0 or higher or run BrowserSim with Oracle Java 7u7 and higher."
> Also see <a href="http://tools.jboss.org/documentation/faq/browsersim.html">BrowserSim FAQ</a>.
> Stack trace:
> org.eclipse.swt.SWTError: To use BrowserSim please install webkitgtk 1.2.0 or higher or run BrowserSim with Oracle Java 7u7 and higher.
> at org.jbos
> The error is displayed even though this package is installed:
> webkitgtk-1.2.6-5.el6.x86_64
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18423) iOS Push Fail
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18423?page=com.atlassian.jira.plugi... ]
Vlado Pakan closed JBIDE-18423.
-------------------------------
Verified with JBDS 8.0.0.CR2
> iOS Push Fail
> -------------
>
> Key: JBIDE-18423
> URL: https://issues.jboss.org/browse/JBIDE-18423
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Reporter: Burr Sutter
> Assignee: Gorkem Ercan
> Priority: Blocker
> Fix For: 4.2.0.CR2
>
> Attachments: helloworldcli2.zip, helloworldjbds2.zip
>
>
> The Hybrid Mobile Project created inside of JBoss Tools seems to be somewhat incompatible with iOS + Aerogear Push Plugin. I will attach a CLI generated project which works and a JBDS Export Native Project that does not. And will upload a video of my attempt to record things within JBDS.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18423) iOS Push Fail
by Tadeas Kriz (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18423?page=com.atlassian.jira.plugi... ]
Tadeas Kriz commented on JBIDE-18423:
-------------------------------------
Verified to work properly in JBDS 8 CR2.
> iOS Push Fail
> -------------
>
> Key: JBIDE-18423
> URL: https://issues.jboss.org/browse/JBIDE-18423
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Reporter: Burr Sutter
> Assignee: Gorkem Ercan
> Priority: Blocker
> Fix For: 4.2.0.CR2
>
> Attachments: helloworldcli2.zip, helloworldjbds2.zip
>
>
> The Hybrid Mobile Project created inside of JBoss Tools seems to be somewhat incompatible with iOS + Aerogear Push Plugin. I will attach a CLI generated project which works and a JBDS Export Native Project that does not. And will upload a video of my attempt to record things within JBDS.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months