[JBoss JIRA] (JBIDE-14072) Messaging for JPP 6 in JBDS plugin
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14072?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-14072:
---------------------------------------
We can do the following:
- add a description to the project examples xml files
- add a WTP facet requirement/fix that a project example requires a particular wtp facet
- set GateIn 3.5/JPP 6.0 AS server to require JSF >= 2.0
In my opinion, the third solution is the best solution.
> Messaging for JPP 6 in JBDS plugin
> ----------------------------------
>
> Key: JBIDE-14072
> URL: https://issues.jboss.org/browse/JBIDE-14072
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: Portal/GateIn
> Affects Versions: 4.0.2.Final, 4.1.0.Beta1
> Environment: All
> Reporter: Divya Mehra
> Assignee: Snjezana Peco
> Priority: Minor
> Fix For: 4.1.0.Beta1
>
>
> Starting from GateIn 3.5/JPP 6.0, Maven quick starts would be the recommended way to bootstrap a portal project.
> Older technology, for example JSF 1.2 and Rich Faces 3 portlets, would not work if deployed on GateIn 3.5/JPP 6.0 (or later versions).
> It is desirable that we message prominently in the JBDS plugin for portal that the developer should use the quick starts (instead of the plugin) for deployments on GateIn 3.5/JPP 6.0 or later versions.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (JBIDE-14370) Add 32bit swt libraries to eclipse64 module as a result of the build
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14370?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-14370:
----------------------------------------
None of those options would require you to make changes: the category.xml file would use version "0.0.0" which means "the best from target-platform". In our case where we manage TP to avoid multiple versions of same bundle, it would mean "the unique version from TP".
This "0.0.0" would not need to be changed when we change TP.
> Add 32bit swt libraries to eclipse64 module as a result of the build
> --------------------------------------------------------------------
>
> Key: JBIDE-14370
> URL: https://issues.jboss.org/browse/JBIDE-14370
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: browsersim
> Reporter: Konstantin Marmalyukov
> Assignee: Mickael Istria
> Priority: Critical
> Fix For: 4.1.0.Beta1
>
>
> We need to have latest 32-bit SWT libraries in resources folder of eclipse64 browsersim module to make user able to run browserSim from x64 eclipse.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months