[JBoss JIRA] (JBIDE-19813) Optimize incremental rebuild of CDI model
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19813?page=com.atlassian.jira.plugi... ]
Alexey Kazakov closed JBIDE-19813.
----------------------------------
Resolution: Done
> Optimize incremental rebuild of CDI model
> -----------------------------------------
>
> Key: JBIDE-19813
> URL: https://issues.jboss.org/browse/JBIDE-19813
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: cdi
> Affects Versions: 4.3.0.Alpha2
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Fix For: 4.3.0.Beta1
>
>
> One of very common cases is when user modifies java code in editor and saves it. Java and CDI dependencies between classes make it generally a hard problem to do incremental rebuild, but if imports and super types are not changed, we do not need to reset all references to Java model objects in all CDI model objects, as it is done now 'to be on the safe side'. Request to JDT are time consuming and we can gain a lot if only changed CDI model objects reset references.
> It is not safe to try this optimization when imports or super types are changed, but they happen not so often as many minor changes.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBDS-3379) Error message in JBDS when installing into existing folder needs work
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3379?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3379:
--------------------------------
Sprint: Sprint #4 May 2015 (was: Sprint #3 May 2015)
> Error message in JBDS when installing into existing folder needs work
> ---------------------------------------------------------------------
>
> Key: JBDS-3379
> URL: https://issues.jboss.org/browse/JBDS-3379
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 8.1.0.Beta1
> Reporter: Nick Boldt
> Assignee: Denis Golovin
> Fix For: 9.0.0.Beta1
>
> Attachments: over-the-top-message-JBDS8.1Beta1.png
>
>
> Got an error message trying to install JBDS into an existing JBDS folder:
> {quote}You can't upgrade by installing over the top (sic){quote}
> !over-the-top-message-JBDS8.1Beta1.png!
> We should consider fixing this message in JBDS 9. Perhaps something like this?
> {quote}Specified folder already contains a JBoss Developer Studio installation. One does not simply install into an existing install folder. Choose another folder or cancel this installer and run JBoss Developer Studio to perform an update.{quote}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19542) Installing "JBoss Tools Common - Mylyn" from JBoss Tools result in errors being logged until "Mylyn Issue Tracker Connectors" is installed from Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19542?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-19542:
------------------------------------
Building in https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... >=706
> Installing "JBoss Tools Common - Mylyn" from JBoss Tools result in errors being logged until "Mylyn Issue Tracker Connectors" is installed from Central
> --------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19542
> URL: https://issues.jboss.org/browse/JBIDE-19542
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core
> Affects Versions: 4.2.3.Final
> Reporter: Len DiMaggio
> Assignee: Nick Boldt
> Priority: Minor
> Fix For: 4.3.0.Beta1
>
>
> Steps to recreate the error:
> * Install Eclipse (eclipse-jee-luna-SR2-linux-gtk-x86_64.tar.gz)
> * Configure JBoss Tools as an update site (http://download.jboss.org/jbosstools/updates/staging/luna/)
> * Install JBoss Tools Common - Mylyn (3.6.2.Final-v20150325-0456-B99, org.jboss.tools.common.mylyn.feature.feature.group)
> * Whenever eclipse is started, this error is written to the .log
> ============================================================================
> cat .log
> !SESSION 2015-03-31 14:33:50.481 -----------------------------------------------
> eclipse.buildId=4.4.2.M20150204-1700
> java.version=1.7.0_55
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product org.eclipse.epp.package.jee.product
> Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.jee.product
> !ENTRY org.eclipse.mylyn.tasks.core 4 0 2015-03-31 14:34:00.231
> !MESSAGE Unexpected error while loading repository template extensions
> !SUBENTRY 1 org.eclipse.mylyn.tasks.core 4 0 2015-03-31 14:34:00.231
> !MESSAGE Could not load repository template extension contributed by 'org.jboss.tools.common.mylyn' with connectorKind 'jira'
> ============================================================================
> Workaround:
> * From JBoss Central, install: "Mylyn Issue Tracker Connectors"
> * This results in the following packages being installed
> * Mylyn Commons 3.14.2.v20150217-2244 org.eclipse.mylyn.commons.feature.group
> * Mylyn Context Connector: Eclipse IDE 3.14.2.v20150218-0125 org.eclipse.mylyn.ide_feature.feature.group
> * Mylyn Context Connector: Java Development 3.14.2.v20150218-0125 org.eclipse.mylyn.java_feature.feature.group
> * Mylyn Context Connector: Plug-in Development 3.14.2.v20150218-0125 org.eclipse.mylyn.pde_feature.feature.group
> * Mylyn Context Connector: Team Support 3.14.2.v20150218-0125 org.eclipse.mylyn.team_feature.feature.group
> * Mylyn Task List 3.14.2.v20150217-2341 org.eclipse.mylyn_feature.feature.group
> * Mylyn Task-Focused Interface 3.14.2.v20150218-0125 org.eclipse.mylyn.context_feature.feature.group
> * Mylyn Tasks Connector: Bugzilla 3.14.2.v20150217-2341 org.eclipse.mylyn.bugzilla_feature.feature.group
> * Mylyn Versions 1.6.2.v20150217-2249 org.eclipse.mylyn.versions.feature.group
> After installing this^, the error is not generated
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBDS-3440) Consider using TestNG 6.9.4.201505110455 in JBDS 9
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3440?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3440:
-----------------------------
Fix Version/s: 9.0.0.Beta1
> Consider using TestNG 6.9.4.201505110455 in JBDS 9
> --------------------------------------------------
>
> Key: JBDS-3440
> URL: https://issues.jboss.org/browse/JBDS-3440
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: 3rd-party-certification, 3rd-party-dependencies, installer, upstream
> Affects Versions: 9.0.0.Beta1
> Reporter: Nick Boldt
> Assignee: Len DiMaggio
> Fix For: 9.0.0.Beta1
>
>
> We currently include TestNG 6.8.6.20141201_2240.
> But the latest available is 6.9.4.201505110455.
> Do we want something newer?
> You can try the latest from here:
> http://beust.com/eclipse/
> If we decide we want something newer, I can pull a mirror and add it to the Beta1 target platform (JBIDE-19776) already in progress.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months