[JBoss JIRA] (JBDS-4059) RPM errors: Installing rh-eclipse46-devstudio.10.1 into rh-eclipse46 beta.
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-4059?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov edited comment on JBDS-4059 at 10/20/16 10:56 PM:
-----------------------------------------------------------------
Just test it on my GTK3 linux with all features installed. HTML5 preview part of the VPE editor for html files works. Visual part for JSF files doesn't work because of GTK3.
So, I rather include useless VPE stuff for RHEL users then get HTML5 preview lost. We can't get the preview only. Both or nothing. So, let's keep everything as it is now.
was (Author: akazakov):
Just test it on my GTK3 linux with all features installed. HTML5 preview part of the VPE editor for html files works. Visual part for JSF files doesn't work because of GTK3.
So, I rather include useless VPE stuff for RHEL users then get HTML5 preview lost. So, let's keep everything as it is now.
> RPM errors: Installing rh-eclipse46-devstudio.10.1 into rh-eclipse46 beta.
> --------------------------------------------------------------------------
>
> Key: JBDS-4059
> URL: https://issues.jboss.org/browse/JBDS-4059
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build
> Reporter: Pavol Srna
> Assignee: Nick Boldt
> Fix For: 10.2.0.AM3
>
>
> [~vkadlcik] has run some rpm sanity tests. The findings can be seen here: http://nest.test.redhat.com/mnt/qa/scratch/bkr-hv03-guest19/2016:24366/tp...
> [~nickboldt] can you please investigate? Thanks!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBDS-4059) RPM errors: Installing rh-eclipse46-devstudio.10.1 into rh-eclipse46 beta.
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-4059?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov commented on JBDS-4059:
--------------------------------------
Just realized that vpe.preview feature won't work without plugins from both vpe and xulrunner features. They won't compile. I guess it's not so easy to decouple the HTML5 preview part from the core of our VPE editor.
So, I see two options here:
1. Just remove vpe from rpm completely. So, rpm users won't have our HTML5 preview.
2. Keep everything at it is.
[~nickboldt] this issue is just about excluding the functionality (VPE) which won't work on RHEL anyway, correct? So, #2 is acceptable. It won't break anything.
[~ibuziuk] on the GTK3 system when VPE is not supported, will our HTML5 preview (in HTML editor) work? If not, then it doesn't make sense to keep HTML5 preview and we can go with #1.
> RPM errors: Installing rh-eclipse46-devstudio.10.1 into rh-eclipse46 beta.
> --------------------------------------------------------------------------
>
> Key: JBDS-4059
> URL: https://issues.jboss.org/browse/JBDS-4059
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build
> Reporter: Pavol Srna
> Assignee: Nick Boldt
> Fix For: 10.2.0.AM3
>
>
> [~vkadlcik] has run some rpm sanity tests. The findings can be seen here: http://nest.test.redhat.com/mnt/qa/scratch/bkr-hv03-guest19/2016:24366/tp...
> [~nickboldt] can you please investigate? Thanks!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23380) MOJO that fails or logs errors for build if manifest in .core plugin has .ui dependency
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23380?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-23380.
------------------------------
Resolution: Done
Closing. Works and was used to generate a bunch of warnings (see linked JIRAs) which have already contributed to Rob fixing some issues in Server and Base. So... \o/
> MOJO that fails or logs errors for build if manifest in .core plugin has .ui dependency
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-23380
> URL: https://issues.jboss.org/browse/JBIDE-23380
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build
> Reporter: Rob Stryker
> Assignee: Nick Boldt
> Fix For: 4.4.2.AM3
>
>
> At a minimum, the mojo should:
> foreach plugin, if plugin ends in .core, check plugin/META-INF/MANIFEST for Dependencies manifest header, and verify .ui is not included in the dependencies at all.
> However, this minimum goal would not have solved the issue we are experiencing with foundation.checkup. The foundation.checkup plugin does not end in .core and so would be skipped by this simple algorithm.
> So... we may wish to check transitive dependencies *only in the same repo*. For example, foundation.core depends on foundation.checker, and foundation.checker is in the same repo, so foundation.checker should also be checked for ui deps or fail.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months