[JBoss JIRA] (JBIDE-13594) org.jboss.tools.esb.project.ui cannot be build due to missing org.eclipse.zest.core
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13594?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-13594:
---------------------------------------
{quote}So if you have an objection to the jbosstools-integration-stack project in github containing BOTH its aggregate build and its target platform definition, open a new JIRA in the JBTIS component, and complain to Paul Leacu.{quote}
Form build point of view it is not a big deal, since JBTIS TP doesn't depend on aggreagtion. jbosstools-is then just doesn't follow the pattern we have in jbosstools-core when target platform is separated module from aggreagtion site.
> org.jboss.tools.esb.project.ui cannot be build due to missing org.eclipse.zest.core
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-13594
> URL: https://issues.jboss.org/browse/JBIDE-13594
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng, esb, testing-tools
> Affects Versions: 4.1.0.Alpha1
> Reporter: Martin Malina
> Assignee: Nick Boldt
> Fix For: 4.1.0.Alpha2
>
> Attachments: dependencies.png
>
>
> jbosstools integration tests job in jenkins is currently blocked because of unsatisfied dependency:
> {code}
> Internal error: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.jboss.tools.esb.project.ui 1.5.300.Alpha1-v20130128-1848-B1149 to bundle org.eclipse.zest.core 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.esb.project.ui 1.5.300.Alpha1-v20130128-1848-B1149 to bundle org.eclipse.zest.layouts 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.esb.project.ui 1.5.300.Alpha1-v20130215-0533-B1152 to bundle org.eclipse.zest.core 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.esb.project.ui 1.5.300.Alpha1-v20130215-0533-B1152 to bundle org.eclipse.zest.layouts 0.0.0.", "No solution found because the problem is unsatisfiable."] -> [Help 1]
> org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.jboss.tools.esb.project.ui 1.5.300.Alpha1-v20130128-1848-B1149 to bundle org.eclipse.zest.core 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.esb.project.ui 1.5.300.Alpha1-v20130128-1848-B1149 to bundle org.eclipse.zest.layouts 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.esb.project.ui 1.5.300.Alpha1-v20130215-0533-B1152 to bundle org.eclipse.zest.core 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.esb.project.ui 1.5.300.Alpha1-v20130215-0533-B1152 to bundle org.eclipse.zest.layouts 0.0.0.", "No solution found because the problem is unsatisfiable."]
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:168)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> {code}
> See https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBo...
> This happens because zest has been removed from the core target platform into JBTIS target platform as described in JBIDE-13435.
> I originally thought this needs to be fixed by the esb compoment owner, but after learning that zest is now in JBTIS target platform, what actually seems needs to be done is use the JBTIS target platform for the job.
> Or disregard this JIRA and split the integration tests and soa integration tests sites/jobs as suggested in JBIDE-12974.
--
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
13 years, 1 month
[JBoss JIRA] (JBIDE-13594) org.jboss.tools.esb.project.ui cannot be build due to missing org.eclipse.zest.core
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13594?page=com.atlassian.jira.plugi... ]
Denis Golovin edited comment on JBIDE-13594 at 2/27/13 5:00 PM:
----------------------------------------------------------------
{quote}So if you have an objection to the jbosstools-integration-stack project in github containing BOTH its aggregate build and its target platform definition, open a new JIRA in the JBTIS component, and complain to Paul Leacu.{quote}
Form build point of view it is not a big deal, since JBTIS TP doesn't depend on aggreagtion. jbosstools-is then just doesn't follow the pattern we have in jbosstools-core when target platform is separated module from aggreagtion site.
was (Author: dgolovin):
{quote}So if you have an objection to the jbosstools-integration-stack project in github containing BOTH its aggregate build and its target platform definition, open a new JIRA in the JBTIS component, and complain to Paul Leacu.{quote}
Form build point of view it is not a big deal, since JBTIS TP doesn't depend on aggreagtion. jbosstools-is then just doesn't follow the pattern we have in jbosstools-core when target platform is separated module from aggreagtion site.
> org.jboss.tools.esb.project.ui cannot be build due to missing org.eclipse.zest.core
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-13594
> URL: https://issues.jboss.org/browse/JBIDE-13594
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng, esb, testing-tools
> Affects Versions: 4.1.0.Alpha1
> Reporter: Martin Malina
> Assignee: Nick Boldt
> Fix For: 4.1.0.Alpha2
>
> Attachments: dependencies.png
>
>
> jbosstools integration tests job in jenkins is currently blocked because of unsatisfied dependency:
> {code}
> Internal error: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.jboss.tools.esb.project.ui 1.5.300.Alpha1-v20130128-1848-B1149 to bundle org.eclipse.zest.core 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.esb.project.ui 1.5.300.Alpha1-v20130128-1848-B1149 to bundle org.eclipse.zest.layouts 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.esb.project.ui 1.5.300.Alpha1-v20130215-0533-B1152 to bundle org.eclipse.zest.core 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.esb.project.ui 1.5.300.Alpha1-v20130215-0533-B1152 to bundle org.eclipse.zest.layouts 0.0.0.", "No solution found because the problem is unsatisfiable."] -> [Help 1]
> org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.jboss.tools.esb.project.ui 1.5.300.Alpha1-v20130128-1848-B1149 to bundle org.eclipse.zest.core 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.esb.project.ui 1.5.300.Alpha1-v20130128-1848-B1149 to bundle org.eclipse.zest.layouts 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.esb.project.ui 1.5.300.Alpha1-v20130215-0533-B1152 to bundle org.eclipse.zest.core 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.esb.project.ui 1.5.300.Alpha1-v20130215-0533-B1152 to bundle org.eclipse.zest.layouts 0.0.0.", "No solution found because the problem is unsatisfiable."]
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:168)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> {code}
> See https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBo...
> This happens because zest has been removed from the core target platform into JBTIS target platform as described in JBIDE-13435.
> I originally thought this needs to be fixed by the esb compoment owner, but after learning that zest is now in JBTIS target platform, what actually seems needs to be done is use the JBTIS target platform for the job.
> Or disregard this JIRA and split the integration tests and soa integration tests sites/jobs as suggested in JBIDE-12974.
--
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
13 years, 1 month
[JBoss JIRA] (JBIDE-13677) New Page wizard
by Viacheslav Kabanovich (JIRA)
Viacheslav Kabanovich created JBIDE-13677:
---------------------------------------------
Summary: New Page wizard
Key: JBIDE-13677
URL: https://issues.jboss.org/browse/JBIDE-13677
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: jsp/jsf/xml/html source editing
Reporter: Viacheslav Kabanovich
Assignee: Viacheslav Kabanovich
Fix For: 4.1.0.Alpha2
--
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
13 years, 1 month
[JBoss JIRA] (JBIDE-13676) New Text Input wizard
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13676?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich updated JBIDE-13676:
------------------------------------------
Description:
Text with all variations
Wizard
1. Type: text/search/textarea/email/password/color/file etc.
2. Label:
3. ID:
4. Clear Button:
5. Placeholder:
6. Mini:
7. Disabled:
8. Hide Label:
9. Theme:
Result
Type=text
<label for="text-3">Text input: data-clear-btn="true"</label>
<input data-clear-btn="true" name="text-3" id="text-3" value="" type="text">
Type=search
<label for="search-1">Search:</label>
<input name="search-1" id="search-1" value="" type="search">
Type=textarea
<label for="textarea-1">Textarea:</label>
<textarea cols="40" rows="8" name="textarea-1" id="textarea-1"></textarea>
and so on.
> New Text Input wizard
> ---------------------
>
> Key: JBIDE-13676
> URL: https://issues.jboss.org/browse/JBIDE-13676
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: jsp/jsf/xml/html source editing
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: new_and_noteworthy
> Fix For: 4.1.0.Alpha2
>
>
> Text with all variations
> Wizard
> 1. Type: text/search/textarea/email/password/color/file etc.
> 2. Label:
> 3. ID:
> 4. Clear Button:
> 5. Placeholder:
> 6. Mini:
> 7. Disabled:
> 8. Hide Label:
> 9. Theme:
> Result
> Type=text
> <label for="text-3">Text input: data-clear-btn="true"</label>
> <input data-clear-btn="true" name="text-3" id="text-3" value="" type="text">
> Type=search
> <label for="search-1">Search:</label>
> <input name="search-1" id="search-1" value="" type="search">
> Type=textarea
> <label for="textarea-1">Textarea:</label>
> <textarea cols="40" rows="8" name="textarea-1" id="textarea-1"></textarea>
> and so on.
--
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
13 years, 1 month
[JBoss JIRA] (JBIDE-13676) New Text Input wizard
by Viacheslav Kabanovich (JIRA)
Viacheslav Kabanovich created JBIDE-13676:
---------------------------------------------
Summary: New Text Input wizard
Key: JBIDE-13676
URL: https://issues.jboss.org/browse/JBIDE-13676
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: jsp/jsf/xml/html source editing
Reporter: Viacheslav Kabanovich
Assignee: Viacheslav Kabanovich
Fix For: 4.1.0.Alpha2
--
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
13 years, 1 month
[JBoss JIRA] (JBIDE-11602) Provide first class support for client side development
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11602?page=com.atlassian.jira.plugi... ]
Victor Rubezhny edited comment on JBIDE-11602 at 2/27/13 4:24 PM:
------------------------------------------------------------------
The latest VJet version - master, that contains a few changes over v.0.9.1 (Released 2/8/2013) - is aimed to Juno (at least juno is specified as VJet dependency). I didn't find any plans to pblish a Kelper-based version probably because of project incubation period. But the current version is able to be run with JBT 4.1.x and Kepler without a change of VJet plug-ins.
The only change required is the adding of VJet Orbit dependencies to JBT Target Platform (see [^jbosstools-add-vjet-dependencies-patch.patch] patch attached). Similar minimalistic changes are to be done due to run VJet plug-ins along with JBDS 7.0-based builds.
VJet project was cloned from [http://git.eclipse.org/c/vjet/org.eclipse.vjet.all.git/]:
{code}git clone --recursive git://git.eclipse.org/gitroot/vjet/org.eclipse.vjet.all.git{code} and imported as is by Maven along with JBT plug-ins.
The VJet CA works in many cases for JS/HTML Files. JS dependencies are supported in many cases. I didn't see any latencies in the calculation of proposals. The only sad thing is that VJet uses a built model, so it require to save and build a JS file (it's done automatically after save if autobuild is on) due to make a new or changed variables/methods/objects to be shown in Content Assistant. It doesn't works on-the-fly.
||Comment||Content Assist Invoked||Result of insertion||
|Any JS file|!vjet-JS-Content-Assist-On-Any-JS-in-ticket-monster-project.jpg|thumbnail!|!vjet-JS-Content-Assist-On-Any-JS-in-ticket-monster-project-After-Insertion.jpg|thumbnail!|
|JS file in Ticket Monster|!vjet-JS-Content-Assist-On-a-JS-in-ticket-monster-project.jpg|thumbnail!|!vjet-JS-Content-Assist-On-a-JS-in-ticket-monster-project-After-Insertion.jpg|thumbnail!|
|HTML file 1|!vjet-JS-Content-Assist-On-HTML-1-in-ticket-monster-project.jpg|thumbnail!|!vjet-JS-Content-Assist-On-HTML-1-in-ticket-monster-project-After-Insertion.jpg|thumbnail!|
|HTML file 2-1|!vjet-JS-Content-Assist-On-HTML-2-1-in-ticket-monster-project.jpg|thumbnail!|!vjet-JS-Content-Assist-On-HTML-2-1-in-ticket-monster-project-After-Insertion.jpg|thumbnail!|
|HTML file 2-2|!vjet-JS-Content-Assist-On-HTML-2-2-in-ticket-monster-project.jpg|thumbnail!|!vjet-JS-Content-Assist-On-HTML-2-2-in-ticket-monster-project-After-Insertion.jpg|thumbnail!|
JBIDE-9012 (Eclipse complains about jquery minified JS files) - looks like a solved problem in VJet:
|| Comment || jQuery Tag Canvas JS-minified || jQuery 1.5.1.JS-minified ||
| No Errors shown for the files |!jquery.tagcanvas.min.js.jpg|thumbnail!|!jquery-1.5.1.min.js.jpg|thumbnail!|
was (Author: vrubezhny):
The latest VJet version - master, that contains a few changes over v.0.9.1 (Released 2/8/2013) - is aimed to Juno (at least juno is specified as VJet dependency). I didn't find any plans to pblish a Kelper-based version probably because of project incubation period. But the current version is able to be run with JBT 4.1.x and Kepler without a change of VJet plug-ins.
The only change required is the adding of VJet Orbit dependencies to JBT Target Platform (see [^jbosstools-add-vjet-dependencies-patch.patch] patch attached). Similar minimalistic changes are to be done due to run VJet plug-ins along with JBDS 7.0-based builds.
VJet project was cloned from [http://git.eclipse.org/c/vjet/org.eclipse.vjet.all.git/]:
{code}git clone --recursive git://git.eclipse.org/gitroot/vjet/org.eclipse.vjet.all.git{code} and imported as is by Maven along with JBT plug-ins.
The VJet CA works in many cases for JS/HTML Files. JS dependencies are supported in many cases. I didn't see any latencies in the calculation of proposals. The only sad thing is that VJet uses a built model, so it require to save and build a JS file (it's done automatically after save if autobuild is on) due to make a new or changed variables/methods/objects to be shown in Content Assistant. It doesn't works on-the-fly.
||comment||Content Assist Invoked||Result of insertion||
|Any JS file|!vjet-JS-Content-Assist-On-Any-JS-in-ticket-monster-project.jpg|thumbnail!|!vjet-JS-Content-Assist-On-Any-JS-in-ticket-monster-project-After-Insertion.jpg|thumbnail!|
|JS file in Ticket Monster|!vjet-JS-Content-Assist-On-a-JS-in-ticket-monster-project.jpg|thumbnail!|!vjet-JS-Content-Assist-On-a-JS-in-ticket-monster-project-After-Insertion.jpg|thumbnail!|
|HTML file 1|!vjet-JS-Content-Assist-On-HTML-1-in-ticket-monster-project.jpg|thumbnail!|!vjet-JS-Content-Assist-On-HTML-1-in-ticket-monster-project-After-Insertion.jpg|thumbnail!|
|HTML file 2-1|!vjet-JS-Content-Assist-On-HTML-2-1-in-ticket-monster-project.jpg|thumbnail!|!vjet-JS-Content-Assist-On-HTML-2-1-in-ticket-monster-project-After-Insertion.jpg|thumbnail!|
|HTML file 2-2|!vjet-JS-Content-Assist-On-HTML-2-2-in-ticket-monster-project.jpg|thumbnail!|!vjet-JS-Content-Assist-On-HTML-2-2-in-ticket-monster-project-After-Insertion.jpg|thumbnail!|
> Provide first class support for client side development
> -------------------------------------------------------
>
> Key: JBIDE-11602
> URL: https://issues.jboss.org/browse/JBIDE-11602
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Reporter: Sebastien Deleuze
> Assignee: Victor Rubezhny
> Labels: jsdt, vjet
> Fix For: 4.1.x
>
> Attachments: jbosstools-add-vjet-dependencies-patch.patch, jquery-1.5.1.min.js.jpg, jquery.tagcanvas.min.js.jpg, vjet-JS-Content-Assist-On-a-JS-in-ticket-monster-project-After-Insertion.jpg, vjet-JS-Content-Assist-On-a-JS-in-ticket-monster-project.jpg, vjet-JS-Content-Assist-On-Any-JS-in-ticket-monster-project-After-Insertion.jpg, vjet-JS-Content-Assist-On-Any-JS-in-ticket-monster-project.jpg, vjet-JS-Content-Assist-On-HTML-1-in-ticket-monster-project-After-Insertion.jpg, vjet-JS-Content-Assist-On-HTML-1-in-ticket-monster-project.jpg, vjet-JS-Content-Assist-On-HTML-2-1-in-ticket-monster-project-After-Insertion.jpg, vjet-JS-Content-Assist-On-HTML-2-1-in-ticket-monster-project.jpg, vjet-JS-Content-Assist-On-HTML-2-2-in-ticket-monster-project-After-Insertion.jpg, vjet-JS-Content-Assist-On-HTML-2-2-in-ticket-monster-project.jpg
>
>
> Web application development is currently moving in many projects from end to end server side technologies to HTML5 RIA developed with REST Webservices/ Webscoket on serverside + pure client side technologies GUI (Backbone.js for example).
> Eclipse has been always been quite bad in the field of advanced Javascript development. JSDT was a good start, but its development has been stopped for a few years, and in its current status, it is not really a good tool for real HTML5/JS dev. From what I know, there is no roadmap for strong move on this field in the WTP team. The only real Eclipse initiative for client side development is Orion (http://www.eclipse.org/orion/) outside of the IDE.
> The only other alternative is Aptana Studio 3, acquired last year by AppAccelerator.
> My question is : is there any plan to consider client side development as a first class citizen in JBoss Studio, even if this question apply to the whole Eclipse Ecosystem ? Other IDE like Netbeans or IntelliJ Idea have a strong support for these technologies, and my guess is this lack may be a significant blocking point in the following years.
> Thanks in advance for your feedback.
--
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
13 years, 1 month
[JBoss JIRA] (JBIDE-11602) Provide first class support for client side development
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11602?page=com.atlassian.jira.plugi... ]
Victor Rubezhny updated JBIDE-11602:
------------------------------------
Attachment: jquery.tagcanvas.min.js.jpg
> Provide first class support for client side development
> -------------------------------------------------------
>
> Key: JBIDE-11602
> URL: https://issues.jboss.org/browse/JBIDE-11602
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Reporter: Sebastien Deleuze
> Assignee: Victor Rubezhny
> Labels: jsdt, vjet
> Fix For: 4.1.x
>
> Attachments: jbosstools-add-vjet-dependencies-patch.patch, jquery-1.5.1.min.js.jpg, jquery.tagcanvas.min.js.jpg, vjet-JS-Content-Assist-On-a-JS-in-ticket-monster-project-After-Insertion.jpg, vjet-JS-Content-Assist-On-a-JS-in-ticket-monster-project.jpg, vjet-JS-Content-Assist-On-Any-JS-in-ticket-monster-project-After-Insertion.jpg, vjet-JS-Content-Assist-On-Any-JS-in-ticket-monster-project.jpg, vjet-JS-Content-Assist-On-HTML-1-in-ticket-monster-project-After-Insertion.jpg, vjet-JS-Content-Assist-On-HTML-1-in-ticket-monster-project.jpg, vjet-JS-Content-Assist-On-HTML-2-1-in-ticket-monster-project-After-Insertion.jpg, vjet-JS-Content-Assist-On-HTML-2-1-in-ticket-monster-project.jpg, vjet-JS-Content-Assist-On-HTML-2-2-in-ticket-monster-project-After-Insertion.jpg, vjet-JS-Content-Assist-On-HTML-2-2-in-ticket-monster-project.jpg
>
>
> Web application development is currently moving in many projects from end to end server side technologies to HTML5 RIA developed with REST Webservices/ Webscoket on serverside + pure client side technologies GUI (Backbone.js for example).
> Eclipse has been always been quite bad in the field of advanced Javascript development. JSDT was a good start, but its development has been stopped for a few years, and in its current status, it is not really a good tool for real HTML5/JS dev. From what I know, there is no roadmap for strong move on this field in the WTP team. The only real Eclipse initiative for client side development is Orion (http://www.eclipse.org/orion/) outside of the IDE.
> The only other alternative is Aptana Studio 3, acquired last year by AppAccelerator.
> My question is : is there any plan to consider client side development as a first class citizen in JBoss Studio, even if this question apply to the whole Eclipse Ecosystem ? Other IDE like Netbeans or IntelliJ Idea have a strong support for these technologies, and my guess is this lack may be a significant blocking point in the following years.
> Thanks in advance for your feedback.
--
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
13 years, 1 month
[JBoss JIRA] (JBIDE-11602) Provide first class support for client side development
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11602?page=com.atlassian.jira.plugi... ]
Victor Rubezhny updated JBIDE-11602:
------------------------------------
Attachment: jquery-1.5.1.min.js.jpg
> Provide first class support for client side development
> -------------------------------------------------------
>
> Key: JBIDE-11602
> URL: https://issues.jboss.org/browse/JBIDE-11602
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Reporter: Sebastien Deleuze
> Assignee: Victor Rubezhny
> Labels: jsdt, vjet
> Fix For: 4.1.x
>
> Attachments: jbosstools-add-vjet-dependencies-patch.patch, jquery-1.5.1.min.js.jpg, jquery.tagcanvas.min.js.jpg, vjet-JS-Content-Assist-On-a-JS-in-ticket-monster-project-After-Insertion.jpg, vjet-JS-Content-Assist-On-a-JS-in-ticket-monster-project.jpg, vjet-JS-Content-Assist-On-Any-JS-in-ticket-monster-project-After-Insertion.jpg, vjet-JS-Content-Assist-On-Any-JS-in-ticket-monster-project.jpg, vjet-JS-Content-Assist-On-HTML-1-in-ticket-monster-project-After-Insertion.jpg, vjet-JS-Content-Assist-On-HTML-1-in-ticket-monster-project.jpg, vjet-JS-Content-Assist-On-HTML-2-1-in-ticket-monster-project-After-Insertion.jpg, vjet-JS-Content-Assist-On-HTML-2-1-in-ticket-monster-project.jpg, vjet-JS-Content-Assist-On-HTML-2-2-in-ticket-monster-project-After-Insertion.jpg, vjet-JS-Content-Assist-On-HTML-2-2-in-ticket-monster-project.jpg
>
>
> Web application development is currently moving in many projects from end to end server side technologies to HTML5 RIA developed with REST Webservices/ Webscoket on serverside + pure client side technologies GUI (Backbone.js for example).
> Eclipse has been always been quite bad in the field of advanced Javascript development. JSDT was a good start, but its development has been stopped for a few years, and in its current status, it is not really a good tool for real HTML5/JS dev. From what I know, there is no roadmap for strong move on this field in the WTP team. The only real Eclipse initiative for client side development is Orion (http://www.eclipse.org/orion/) outside of the IDE.
> The only other alternative is Aptana Studio 3, acquired last year by AppAccelerator.
> My question is : is there any plan to consider client side development as a first class citizen in JBoss Studio, even if this question apply to the whole Eclipse Ecosystem ? Other IDE like Netbeans or IntelliJ Idea have a strong support for these technologies, and my guess is this lack may be a significant blocking point in the following years.
> Thanks in advance for your feedback.
--
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
13 years, 1 month
[JBoss JIRA] (JBIDE-13671) parent pom should use last-mod-timestamp from git for a plugin/feature instead of current timestamp when building
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13671?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-13671:
------------------------------------
[~maxandersen], [~dgolovin], [~mmalina], [~ldimaggio], [~mickael_istria] ... please review. This is a simple change, but everyone need to be aware that feature and plugin timestamps will in many cases go *BACKWARDS* to reflect the last time they were ACTUALLY changed (2012) instead of each rebuild showing today's date.
> parent pom should use last-mod-timestamp from git for a plugin/feature instead of current timestamp when building
> -----------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13671
> URL: https://issues.jboss.org/browse/JBIDE-13671
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.1.0.Alpha2
>
> Attachments: jbide13671-before-and-after.png
>
>
> This needs to be added to master parent pom:
> {code}
> <plugin>
> <groupId>org.eclipse.tycho</groupId>
> <artifactId>tycho-packaging-plugin</artifactId>
> <version>${tycho.version}</version>
> <dependencies>
> <dependency>
> <groupId>org.eclipse.tycho.extras</groupId>
> <artifactId>tycho-buildtimestamp-jgit</artifactId>
> <version>${tycho-extras.version}</version>
> </dependency>
> </dependencies>
> <configuration>
> <strictBinIncludes>false</strictBinIncludes>
> <format>'v'yyyyMMdd-HHmm</format>
> <timestampProvider>jgit</timestampProvider>
> <jgit.ignore>
> </jgit.ignore>
> </configuration>
> </plugin>
> {code}
> Ref: http://pweclipse.blogspot.ch/2012_09_01_archive.html
--
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
13 years, 1 month