[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 updated JBIDE-13671:
-------------------------------
Summary: parent pom should use last-mod-timestamp from git for a plugin/feature instead of current timestamp when building (was: parent pom should use last-mod-timestamp for a plugin/feature instead of current timestamp when building)
> 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
[JBoss JIRA] (JBIDE-13675) openshift-java-client: dont swallow domain deletion errors in tests if deletion is pre-condition
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-13675:
----------------------------------------
Summary: openshift-java-client: dont swallow domain deletion errors in tests if deletion is pre-condition
Key: JBIDE-13675
URL: https://issues.jboss.org/browse/JBIDE-13675
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.1.0.Alpha1
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 4.0.0.Alpha2-SOA
When running UserResourceIntegrationTests there are currently several tests that fail because of an issue in OpenShift (reported in https://bugzilla.redhat.com/show_bug.cgi?id=916323). The UserResourceIntegrationTests therefore fail in
#shouldCreateDomain
#shouldReturnThatHasNoDomain
#shouldReturnEmptyDomains
#shouldNoDefaultDomainAfterRefresh
These tests rely on the fact that the domain(s) could be deleted, no domain is a pre-condition to them.
Unfortunately these tests swallow the exceptions that may occurr when killing these domains. The tests therefore report resulting errors, not the real cause.
We have to ensure exception that occurr when killing domains are not swallowed. They have to make the test fail (since domain deletion is a precondition).
--
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:03 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!|
was (Author: vrubezhny):
The latest VJet version (master, that contains a few changes over v.0.9.1 (Released 2/8/2013)) 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, 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 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 updated JBIDE-13671:
-------------------------------
Attachment: jbide13671-before-and-after.png
Before and after applying this change in parent pom in master branch for Alpha2:
!jbide13671-before-and-after.png!
Note that timestamps in many cases will go BACKWARDS in time, but since the qualifier moves up from Alpha1 to Alpha2, installation should be fine.
Of course this will REQUIRE that all plugins and features have moved up version-wise from their 4.0.x branch versions.
> parent pom should use last-mod-timestamp 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
[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 3:41 PM:
------------------------------------------------------------------
The latest VJet version (master, that contains a few changes over v.0.9.1 (Released 2/8/2013)) 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!|
was (Author: vrubezhny):
The latest VJet version (master, that contains a few changes over v.0.9.1 (Released 2/8/2013)) 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 [git://git.eclipse.org/gitroot/vjet/org.eclipse.vjet.all.git] as is and imported 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, 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 edited comment on JBIDE-11602 at 2/27/13 3:41 PM:
------------------------------------------------------------------
The latest VJet version (master, that contains a few changes over v.0.9.1 (Released 2/8/2013)) 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!|
was (Author: vrubezhny):
The latest VJet version (master, that contains a few changes over v.0.9.1 (Released 2/8/2013)) 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, 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 edited comment on JBIDE-11602 at 2/27/13 3:27 PM:
------------------------------------------------------------------
The latest VJet version (master, that contains a few changes over v.0.9.1 (Released 2/8/2013)) 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 [git://git.eclipse.org/gitroot/vjet/org.eclipse.vjet.all.git] as is and imported 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!|
was (Author: vrubezhny):
The latest VJet version (master, that contains a few changes over v.0.9.1 (Released 2/8/2013)) 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.
The VJet CA works in many cases for JS/HTML Files. JS dependencies are supported in many cases:
||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, 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: vjet-JS-Content-Assist-On-HTML-2-2-in-ticket-monster-project-After-Insertion.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, 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: vjet-JS-Content-Assist-On-HTML-2-1-in-ticket-monster-project-After-Insertion.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, 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: vjet-JS-Content-Assist-On-HTML-2-2-in-ticket-monster-project.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, 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