[JBoss JIRA] (ERT-502) Cannot run hybrid app on ios simulator when eclipse runs in osx sandbox [EBZ#514543]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created ERT-502:
---------------------------------------
Summary: Cannot run hybrid app on ios simulator when eclipse runs in osx sandbox [EBZ#514543]
Key: ERT-502
URL: https://issues.jboss.org/browse/ERT-502
Project: Eclipse Release Train
Issue Type: Task
Components: Thym
Reporter: Friendly Jira Robot
Priority: Critical
Fix For: Neon (4.6)
stack tracke:
--------------
Instruments Error: Could not create output document '/private/var/folders/40/nmzqdw3n2f50bt94vlp0rq440000gn/T/AppTranslocation/FBD47789-8BCA-44F6-80C3-EC62388C5339/d/Eclipse-neon3.app/Contents/MacOS/instrumentscli0.trace': The volume “FBD47789-8BCA-44F6-80C3-EC62388C5339” is read only
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBDS-4362) Consider eliminating the devstudio EAP installer bundle?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4362?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4362:
----------------------------------
[~jeffmaury][~tim.moran][~mbenitez][~dgolovin] WDYT?
Is it time to retire the devstudio EAP bundle installer?
> Consider eliminating the devstudio EAP installer bundle?
> --------------------------------------------------------
>
> Key: JBDS-4362
> URL: https://issues.jboss.org/browse/JBDS-4362
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer, integration-platform
> Affects Versions: 10.4.0.AM3
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 11.0.0.AM1
>
>
> For devstudio 11, we might want to eliminate the devstudio EAP installer.
> If we could do so, we would no longer require an internal-facing server (eg., www.qa or wonka.mw) since everything in devstudio would be completely open source and free.
> This would also make releases simpler and faster as I wouldn't have to push bits to BOTH the internal and external staging servers - we could stage 100% on the public devstudio.redhat.com server.
> Since EAP releases don't align very well with devstudio releases, maybe it's time to decouple entirely?
> That way only the devSUITE installer would include EAP.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBDS-4362) Consider eliminating the devstudio EAP installer bundle?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4362?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4362:
-----------------------------
Affects Version/s: 10.4.0.AM3
(was: 11.0.0.AM1)
> Consider eliminating the devstudio EAP installer bundle?
> --------------------------------------------------------
>
> Key: JBDS-4362
> URL: https://issues.jboss.org/browse/JBDS-4362
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer, integration-platform
> Affects Versions: 10.4.0.AM3
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 11.0.0.AM1
>
>
> For devstudio 11, we might want to eliminate the devstudio EAP installer.
> If we could do so, we would no longer require an internal-facing server (eg., www.qa or wonka.mw) since everything in devstudio would be completely open source and free.
> This would also make releases simpler and faster as I wouldn't have to push bits to BOTH the internal and external staging servers - we could stage 100% on the public devstudio.redhat.com server.
> Since EAP releases don't align very well with devstudio releases, maybe it's time to decouple entirely?
> That way only the devSUITE installer would include EAP.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBDS-4362) Consider eliminating the devstudio EAP installer bundle?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4362?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4362:
-----------------------------
Fix Version/s: 11.0.0.AM1
> Consider eliminating the devstudio EAP installer bundle?
> --------------------------------------------------------
>
> Key: JBDS-4362
> URL: https://issues.jboss.org/browse/JBDS-4362
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer, integration-platform
> Affects Versions: 11.0.0.AM1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 11.0.0.AM1
>
>
> For devstudio 11, we might want to eliminate the devstudio EAP installer.
> If we could do so, we would no longer require an internal-facing server (eg., www.qa or wonka.mw) since everything in devstudio would be completely open source and free.
> This would also make releases simpler and faster as I wouldn't have to push bits to BOTH the internal and external staging servers - we could stage 100% on the public devstudio.redhat.com server.
> Since EAP releases don't align very well with devstudio releases, maybe it's time to decouple entirely?
> That way only the devSUITE installer would include EAP.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBDS-4362) Consider eliminating the devstudio EAP installer bundle?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4362?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4362:
-----------------------------
Description:
For devstudio 11, we might want to eliminate the devstudio EAP installer.
If we could do so, we would no longer require an internal-facing server (eg., www.qa or wonka.mw) since everything in devstudio would be completely open source and free.
This would also make releases simpler and faster as I wouldn't have to push bits to BOTH the internal and external staging servers - we could stage 100% on the public devstudio.redhat.com server.
Since EAP releases don't align very well with devstudio releases, maybe it's time to decouple entirely?
That way only the devSUITE installer would include EAP.
was:
For devstudio 11, we might want to eliminate the devstudio EAP installer.
If we could do so, we would no longer require an internal-facing server (eg., www.qa or wonka.mw) since everything in devstudio would be completely open source and free.
This would also make releases simpler and faster as I wouldn't have to push bits to BOTH the internal and external staging servers - we could stage 100% on the public devstudio.redhat.com server.
Since EAP releases don't align very well with devstudio releases, maybe it's time to decouple entirely?
That way only the devSUITE installer would include EAP.
> Consider eliminating the devstudio EAP installer bundle?
> --------------------------------------------------------
>
> Key: JBDS-4362
> URL: https://issues.jboss.org/browse/JBDS-4362
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer, integration-platform
> Affects Versions: 11.0.0.AM1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 11.0.0.AM1
>
>
> For devstudio 11, we might want to eliminate the devstudio EAP installer.
> If we could do so, we would no longer require an internal-facing server (eg., www.qa or wonka.mw) since everything in devstudio would be completely open source and free.
> This would also make releases simpler and faster as I wouldn't have to push bits to BOTH the internal and external staging servers - we could stage 100% on the public devstudio.redhat.com server.
> Since EAP releases don't align very well with devstudio releases, maybe it's time to decouple entirely?
> That way only the devSUITE installer would include EAP.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBDS-4362) Consider eliminating the devstudio EAP installer bundle?
by Nick Boldt (JIRA)
Nick Boldt created JBDS-4362:
--------------------------------
Summary: Consider eliminating the devstudio EAP installer bundle?
Key: JBDS-4362
URL: https://issues.jboss.org/browse/JBDS-4362
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Bug
Components: installer, integration-platform
Affects Versions: 11.0.0.AM1
Reporter: Nick Boldt
For devstudio 11, we might want to eliminate the devstudio EAP installer.
If we could do so, we would no longer require an internal-facing server (eg., www.qa or wonka.mw) since everything in devstudio would be completely open source and free.
This would also make releases simpler and faster as I wouldn't have to push bits to BOTH the internal and external staging servers - we could stage 100% on the public devstudio.redhat.com server.
Since EAP releases don't align very well with devstudio releases, maybe it's time to decouple entirely?
That way only the devSUITE installer would include EAP.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBDS-4362) Consider eliminating the devstudio EAP installer bundle?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4362?page=com.atlassian.jira.plugin.... ]
Nick Boldt reassigned JBDS-4362:
--------------------------------
Assignee: Nick Boldt
> Consider eliminating the devstudio EAP installer bundle?
> --------------------------------------------------------
>
> Key: JBDS-4362
> URL: https://issues.jboss.org/browse/JBDS-4362
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer, integration-platform
> Affects Versions: 11.0.0.AM1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
>
> For devstudio 11, we might want to eliminate the devstudio EAP installer.
> If we could do so, we would no longer require an internal-facing server (eg., www.qa or wonka.mw) since everything in devstudio would be completely open source and free.
> This would also make releases simpler and faster as I wouldn't have to push bits to BOTH the internal and external staging servers - we could stage 100% on the public devstudio.redhat.com server.
> Since EAP releases don't align very well with devstudio releases, maybe it's time to decouple entirely?
> That way only the devSUITE installer would include EAP.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24240) Include newer version of wtp in JBT/devstudio Neon.3 target platform (4.63.x)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24240?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-24240:
------------------------------------
Fixed in JBT 4.4.4.AM3 / devstudio 10.4.0.AM3 by simply installing the Abridged / BYOE category (or using the installer):
!install-jbt-abridged-including-patch-feature.png|thumbnail!
!patched-in-devstudio.png|thumbnail!
> Include newer version of wtp in JBT/devstudio Neon.3 target platform (4.63.x)
> -----------------------------------------------------------------------------
>
> Key: JBIDE-24240
> URL: https://issues.jboss.org/browse/JBIDE-24240
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: target-platform
> Affects Versions: 4.4.4.AM2
> Reporter: Aurélien Pupier
> Assignee: Nick Boldt
> Fix For: 4.4.4.AM3
>
> Attachments: install-jbt-abridged-including-patch-feature.png, patched-in-devstudio.png, wtp383-cannot-be-installed-in-EclipseNeon3JavaEE_EPP.png, wtp383plugin-only-cannot-be-installed-in-EclipseNeon3JavaEE_EPP.png
>
>
> the neon.3 contains a regression which is impacting a lot of m2e users and prevents Fuse Tooling to migrate to Neon.3 safely
> I provided a patch to fix it and hope to have a new version of the plugin available soon, see
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=511793#c9
> We will need to include this new version in the TP for JBoss Tools 4.4.4
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months