[JBoss JIRA] (JBIDE-19038) Arquillian should not be in JBT EA catalog
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19038?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen edited comment on JBIDE-19038 at 1/14/15 5:48 PM:
----------------------------------------------------------------------
I dont think there was any comment in Radim's description about removing the connector - just not classify it as early access.
so yes, move it to the normal discovery.
was (Author: maxandersen):
I dont think there was any comment in Radim's description about removing the connector - just not classify it as early access.
> Arquillian should not be in JBT EA catalog
> ------------------------------------------
>
> Key: JBIDE-19038
> URL: https://issues.jboss.org/browse/JBIDE-19038
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: updatesite
> Affects Versions: 4.2.2.Final
> Reporter: Radim Hopp
> Assignee: Nick Boldt
>
> In JBIDE-18995 Arquillian was removed from EA (by removing it from jbosstools-earlyaccess.properties), but on Software/Update page it is still displayed under EA features.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBIDE-19038) Arquillian should not be in JBT EA catalog
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19038?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-19038:
---------------------------------------------
I dont think there was any comment in Radim's description about removing the connector - just not classify it as early access.
> Arquillian should not be in JBT EA catalog
> ------------------------------------------
>
> Key: JBIDE-19038
> URL: https://issues.jboss.org/browse/JBIDE-19038
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: updatesite
> Affects Versions: 4.2.2.Final
> Reporter: Radim Hopp
> Assignee: Nick Boldt
>
> In JBIDE-18995 Arquillian was removed from EA (by removing it from jbosstools-earlyaccess.properties), but on Software/Update page it is still displayed under EA features.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBDS-3270) Cordova App Icon Support
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-3270?page=com.atlassian.jira.plugin.... ]
Len DiMaggio commented on JBDS-3270:
------------------------------------
Do we have any details on this? Will it simply be a matter of enabling the developers to reference a .jpeg file?
> Cordova App Icon Support
> ------------------------
>
> Key: JBDS-3270
> URL: https://issues.jboss.org/browse/JBDS-3270
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: aerogear-hybrid
> Reporter: Burr Sutter
> Assignee: Gorkem Ercan
> Fix For: 9.0.0.CR1
>
>
> As a HTML5-focused, Cordova mobile app developer, I need to change the icon associated with my mobile application. The icon on the end-user's home screen.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBDS-3284) Ionic Palette - version selection, detection
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3284?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov commented on JBDS-3284:
--------------------------------------
[~ldimaggio] we already have that capability to handle multiple versions. It works fine for jQuery Mobile.
> Ionic Palette - version selection, detection
> --------------------------------------------
>
> Key: JBDS-3284
> URL: https://issues.jboss.org/browse/JBDS-3284
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Reporter: Burr Sutter
> Assignee: Alexey Kazakov
> Fix For: 9.0.0.Alpha1
>
>
> As a Cordova-focused hybrid mobile app developer, I need to be able to import existing Ionic projects and modify the version of the Ionic framework, where the Palette is flexible enough to handle version changes, including addition/subtraction of specific widgets only available in particular versions.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBTIS-379) Support early access and production releases - distribution infrastructure.
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-379?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBTIS-379:
----------------------------------
{quote}should I create two p2 update sites (similar to the jbdevstudio proposal)? {quote}
Yes, you need two sites: one for released content, and one for EA.
> Support early access and production releases - distribution infrastructure.
> ---------------------------------------------------------------------------
>
> Key: JBTIS-379
> URL: https://issues.jboss.org/browse/JBTIS-379
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: distribution
> Affects Versions: 8.0.0.GA
> Reporter: Paul Leacu
> Assignee: Paul Leacu
>
> It's necessary to split the IS update sites into strictly released content (.Final features) and early access content (.Final features + Beta, etc)
> * Need one p2 site for IS released stuff and a second one for EA stuff, in order to prevent a customer from accidentally installing EA (Alpha/Beta) content from a Final zip; also need two discovery sites/plugins/etc.
> * What do we call the zips?
> jbdevstudio-integration-stack-8.0.0-updatesite.zip
> jbdevstudio-integration-stack-8.0.0-updatesite-earlyaccess.zip
> jbdevstudio-integration-stack-8.0.1-updatesite.zip
> jbdevstudio-integration-stack-8.0.1-updatesite-earlyaccess.zip
> jbdevstudio-integration-stack-8.0.2-updatesite.zip (no EA after this)
> jbdevstudio-integration-stack-8.0.3-updatesite.zip (maintenance build)
> jbdevstudio-integration-stack-8.0.4-updatesite.zip (etc.)
> * Where do we put the content?
> https://devstudio.redhat.com/updates/8.0/devstudio-directory.xml (just need one plugin, but have it point to a composite site of the two IS sites (released + earlyaccess))
> * Is in necessary to have two p2 community sites as well?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBDS-3276) JBDS-IS Installer
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-3276?page=com.atlassian.jira.plugin.... ]
Len DiMaggio commented on JBDS-3276:
------------------------------------
Paul said:
??In order to address Max's concern - we should spin a new IS whenever JBDS releases a minor version update.??
So, if we do that repeatedly over time, Max's reference to ??"with extra stuff" 9.0.0?? will actually be what? The user will have to perform an on-line software update for each JBDSIS update - or will we ship a new downloadable .zip of JBDSIS for each update?
> JBDS-IS Installer
> -----------------
>
> Key: JBDS-3276
> URL: https://issues.jboss.org/browse/JBDS-3276
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: installer, integration-platform
> Affects Versions: 8.0.0.GA
> Reporter: Burr Sutter
>
> As a Fuse, integration-focused developer, I need a downloadable installer that will allow me to quickly and easily install JBDS with Fuse capabilities.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBIDE-18869) migrate Thym from TP to being an aggregated component
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18869?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-18869 at 1/14/15 4:19 PM:
-------------------------------------------------------------
PR [6] to set new default path for Thym mirror applied in master branch parent pom:
[6] https://github.com/jbosstools/jbosstools-build/pull/164/files
Once 4.2.2 is released, we can apply this similar change [6] into the 4.2.x parent pom. Eventually we may need a stable /mars/ site for Thym, but for now, since Thym 0.1.0 is compatible w/ both Luna and Mars, it's OK to source the same URL [3]:
[3] http://download.jboss.org/jbosstools/updates/integration/luna/core/thym/
was (Author: nickboldt):
PR to set new default path for Thym mirror applied in master branch parent pom:
https://github.com/jbosstools/jbosstools-build/pull/164/files
> migrate Thym from TP to being an aggregated component
> -----------------------------------------------------
>
> Key: JBIDE-18869
> URL: https://issues.jboss.org/browse/JBIDE-18869
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: aerogear-hybrid, build, target-platform, updatesite
> Affects Versions: 4.2.0.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.2.3.Final, 4.3.0.Alpha1
>
>
> Because Thym changes frequently, and because Gorkem runs the project, we should treat it like a JBT project, not part of the TP.
> This would allow it to be incorporated into builds more easily and would avoid TP churn.
> This should be fixed in master then backported for 4.2.2 (or 4.2.3).
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBTIS-379) Support early access and production releases - distribution infrastructure.
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-379?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBTIS-379:
----------------------------------
"stable" = Final; cannot include Beta/CR.
you need a "development" site for Beta/CR. Or an Early Access one.
Since you're mixing concerns here, perhaps the simplest is this:
http://download.jboss.org/jbosstools/updates/stable/luna/integration-stac...
and
http://download.jboss.org/jbosstools/updates/stable/luna/integration-stac...
> Support early access and production releases - distribution infrastructure.
> ---------------------------------------------------------------------------
>
> Key: JBTIS-379
> URL: https://issues.jboss.org/browse/JBTIS-379
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: distribution
> Affects Versions: 8.0.0.GA
> Reporter: Paul Leacu
> Assignee: Paul Leacu
>
> It's necessary to split the IS update sites into strictly released content (.Final features) and early access content (.Final features + Beta, etc)
> * Need one p2 site for IS released stuff and a second one for EA stuff, in order to prevent a customer from accidentally installing EA (Alpha/Beta) content from a Final zip; also need two discovery sites/plugins/etc.
> * What do we call the zips?
> jbdevstudio-integration-stack-8.0.0-updatesite.zip
> jbdevstudio-integration-stack-8.0.0-updatesite-earlyaccess.zip
> jbdevstudio-integration-stack-8.0.1-updatesite.zip
> jbdevstudio-integration-stack-8.0.1-updatesite-earlyaccess.zip
> jbdevstudio-integration-stack-8.0.2-updatesite.zip (no EA after this)
> jbdevstudio-integration-stack-8.0.3-updatesite.zip (maintenance build)
> jbdevstudio-integration-stack-8.0.4-updatesite.zip (etc.)
> * Where do we put the content?
> https://devstudio.redhat.com/updates/8.0/devstudio-directory.xml (just need one plugin, but have it point to a composite site of the two IS sites (released + earlyaccess))
> * Is in necessary to have two p2 community sites as well?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBDS-3279) Screencasts: Maven
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-3279?page=com.atlassian.jira.plugin.... ]
Len DiMaggio commented on JBDS-3279:
------------------------------------
Can we add a subtopic - on running tests and on avoiding running tests (-DskipTests=true) to one of these screencasts? Thx!
> Screencasts: Maven
> ------------------
>
> Key: JBDS-3279
> URL: https://issues.jboss.org/browse/JBDS-3279
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: documentation, maven
> Reporter: Burr Sutter
> Assignee: Fred Bricon
> Fix For: 9.0.x
>
>
> As a Java EE developer, new to using Eclipse + Maven, I need short, sub-6 minute screencasts of individual key Maven focused use cases, so that I can better understand how Maven is integrated into the Eclipse + Java EE development workflow.
> Use cases include:
> - creation of a new project and its pom.xml, with the pom.xml editor
> - dependencies adds/removes
> - Import maven projects - from a SVN or Git repo
> - multi-module maven projects
> - run on server
> - package vs install
> - update - the magic "update project" that helps get Eclipse and Maven back into agreement
> - adjust profiles - address the Arquillian profile
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months