[JBoss JIRA] (JBIDE-23127) blog about the improvements RH Eclipse teams did to Neon
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23127?page=com.atlassian.jira.plugi... ]
Ilya Buziuk commented on JBIDE-23127:
-------------------------------------
FYI, blog "JavaScript Tools - what is new in Neon.1?" has been published - http://tools.jboss.org/blog/2016-09-29-javascript-development-tools-neon1...
I also got in touch with Roxanne from Eclipse Foundation - the article would also be shared or republished on the eclipse.org
> blog about the improvements RH Eclipse teams did to Neon
> --------------------------------------------------------
>
> Key: JBIDE-23127
> URL: https://issues.jboss.org/browse/JBIDE-23127
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: website
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
>
> Neon is out and we did a lot of great stuff in the platform
> around smart import, auto download of extensions, zoom, etc.
> I thought it would be great to do a blog posting about this work
> on tools.jboss.org for the Eclipse Neon release
> Audience: users of Eclipse and making internal and external to Red Hat aware of the improvements made.
> The target would be http://developers.redhat.com/blog
> _The following is the current ToC of the blog, it's going to evolve as content is gathered_
> Neon.0:
> * JavaScript plugins and “Eclipse for JavaScript Developers” package
> * JSon Editor
> * Docker Tools
> * Vagrant Tools
> * Smarter and easier Import of projects in the IDE
> * Zoom In/Out with Ctrl+/Ctrl- in text editors
> * Discovery and proposal of Marketplace extensions for unknown file types
> * SWT on GTK3
> * Theming off
> For Neon.1 - released September 28th:
> * More Docker: https://wiki.eclipse.org/Linux_Tools_Project/News/NewIn51
> * Image viewer in the Eclipse IDE
> For Eclipse Oxygen, next major release to be shipped in June 2018, here are our plans:
> * generic and extensible code editor
> * Integration with the language server protocol
> * UI/UX efforts
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23068) Unknown extension points and bundles can't be resolved in jbt-base and jbt-server
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23068?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-23068:
-------------------------------------
Fix Version/s: 4.4.2.Final
(was: 4.4.x)
> Unknown extension points and bundles can't be resolved in jbt-base and jbt-server
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-23068
> URL: https://issues.jboss.org/browse/JBIDE-23068
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform
> Reporter: Dmitrii Bocharov
> Assignee: Dmitrii Bocharov
> Fix For: 4.4.2.Final
>
> Attachments: magic_error_disapperance.webm
>
>
> Builds in terminal (mvn clean install) run successfully. However in eclipse i have 3 errors for jjbt-base and 3 for jbt-server:
> jbt-base:
> Unknown extension point: 'org.eclipse.mylyn.tasks.bugs.support' in /org.jboss.tools.common.mylyn
> Unknown extension point: 'org.eclipse.mylyn.tasks.core.templates' in /org.jboss.tools.common.mylyn
> Unknown extension point: 'org.eclipse.ui.activities' plugin.xml in /org.jboss.tools.common.model.ui.capabilities
> jbt-server:
> Bundle 'org.jboss.ide.eclipse.as.management.eap61plus' cannot be resolved in /org.jboss.tools.as.management.itests/META-INF
> Unknown extension point: 'org.eclipse.help.contexts' in /org.jboss.ide.eclipse.as.doc.user
> Unknown extension point: 'org.eclipse.help.toc' in /org.jboss.ide.eclipse.as.doc.user
> [dbocharo@dbocharo jbosstools-target-platforms]$ git pull upstream 4.60.x
> From https://github.com/jbosstools/jbosstools-target-platforms
> * branch 4.60.x -> FETCH_HEAD
> Already up-to-date.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23274) Rename of batch artefact should affect batch.xml file
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23274?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-23274:
----------------------------------
Issue Type: Enhancement (was: Feature Request)
> Rename of batch artefact should affect batch.xml file
> -----------------------------------------------------
>
> Key: JBIDE-23274
> URL: https://issues.jboss.org/browse/JBIDE-23274
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: batch
> Affects Versions: 4.4.2.AM1
> Reporter: Lukáš Valach
> Assignee: Alexey Kazakov
> Fix For: 4.5.x
>
> Attachments: BatchRenameManualTest.zip
>
>
> There are three ways how to refer batch artefact in job.xml file.
> * Using @Name annotation
> * Using fully qualified class name
> * Using batch.xml
> I noticed that the class name is not changed in batch.xml file during refactoring and the job.xml file become invalid for this reason.
> There is a way how to avoid this problem. User can check the "Update fully qualified names in non-Java text files" option in Rename window, but this solution is not intuitive/is not user friendly I think.
> In another case, when I don't use batch.xml and use the name comming from @Named annotation. The artefact is renamed in job.xml file even if the "Update fully qualified names in non-Java text files" option aren't selected. Non-Java text file (job.xml) is updated automatically in this case.
> There is attached project that you can use to reproduce this problem.
> [^BatchRenameManualTest.zip]. Just try to rename Writer class.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23275) Rename doesn't change fully qualified name in job.xml file
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23275?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-23275:
----------------------------------
Priority: Minor (was: Major)
> Rename doesn't change fully qualified name in job.xml file
> ----------------------------------------------------------
>
> Key: JBIDE-23275
> URL: https://issues.jboss.org/browse/JBIDE-23275
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: batch
> Affects Versions: 4.4.2.AM1
> Environment: Fedora 24
> Reporter: Lukáš Valach
> Priority: Minor
> Fix For: 4.5.x
>
> Attachments: BatchRenameManualTest.zip
>
>
> Refactoring doesn't modify job.xml when I renaming class which is referred in job.xml using the fully qualified name.
> For example, when I have batchlet class
> {code:java}
> package test;
> public class BatchletWithProperty extends AbstractBatchlet {
> ...
> }
> {code}
> ...and job.xml
> {code:xml}
> <job ...>
> <step id="step1">
> <batchlet ref="test.BatchletWithProperty"> <!-- linked using the fully qualified name -->
> ...
> </batchlet>
> </step>
> ...
> </job>
> {code}
> ...then, when I try to rename test.BatchletWithProperty the refactoring doesn't change fully qualified name in job.xml.
> Renaming works properly when I refer to class using name coming from @Named annotation.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23275) Rename doesn't change fully qualified name in job.xml file
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23275?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-23275:
----------------------------------
Priority: Major (was: Minor)
> Rename doesn't change fully qualified name in job.xml file
> ----------------------------------------------------------
>
> Key: JBIDE-23275
> URL: https://issues.jboss.org/browse/JBIDE-23275
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: batch
> Affects Versions: 4.4.2.AM1
> Environment: Fedora 24
> Reporter: Lukáš Valach
> Fix For: 4.5.x
>
> Attachments: BatchRenameManualTest.zip
>
>
> Refactoring doesn't modify job.xml when I renaming class which is referred in job.xml using the fully qualified name.
> For example, when I have batchlet class
> {code:java}
> package test;
> public class BatchletWithProperty extends AbstractBatchlet {
> ...
> }
> {code}
> ...and job.xml
> {code:xml}
> <job ...>
> <step id="step1">
> <batchlet ref="test.BatchletWithProperty"> <!-- linked using the fully qualified name -->
> ...
> </batchlet>
> </step>
> ...
> </job>
> {code}
> ...then, when I try to rename test.BatchletWithProperty the refactoring doesn't change fully qualified name in job.xml.
> Renaming works properly when I refer to class using name coming from @Named annotation.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23278) Validation of class reference in job.xml produces false-positive warning
by Lukáš Valach (JIRA)
Lukáš Valach created JBIDE-23278:
------------------------------------
Summary: Validation of class reference in job.xml produces false-positive warning
Key: JBIDE-23278
URL: https://issues.jboss.org/browse/JBIDE-23278
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: batch
Affects Versions: 4.4.2.AM1
Environment: Fedora 24
Reporter: Lukáš Valach
Attachments: BatchRenameManualTest.zip, Rename-Warning.png
When I refer to some class using fully qualified name and that class is annotated by @Named or is mentioned in bean.xml, then the eclipse shows warning "Item ... not found." although class exists and code is valid (test passes).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months