[JBoss JIRA] (JBTIS-462) JBTIS 4.3.0.Alpha1 final updates
by Paul Leacu (JIRA)
Paul Leacu created JBTIS-462:
--------------------------------
Summary: JBTIS 4.3.0.Alpha1 final updates
Key: JBTIS-462
URL: https://issues.jboss.org/browse/JBTIS-462
Project: JBoss Tools Integration Stack
Issue Type: Feature Request
Components: distribution
Affects Versions: 4.3.0.Alpha1
Reporter: Paul Leacu
Assignee: Paul Leacu
Final updates to 4.3.0.Alpha1 (components, category.xml, etc).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBTIS-234) DSL Validation
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-234?page=com.atlassian.jira.plugin.... ]
Paul Leacu commented on JBTIS-234:
----------------------------------
[~KrisVerlaenen] [~jtyrrell]
Hey - this issues hasn't seen any updates in 18 months - please comment on it by Friday.
> DSL Validation
> --------------
>
> Key: JBTIS-234
> URL: https://issues.jboss.org/browse/JBTIS-234
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: drools/ jBPM
> Environment: All
> Reporter: Jim Tyrrell
> Assignee: Kris Verlaenen
>
> When authoring a DLS file you will typically have variable names of the type: "{disabilityType}"=customer: Customer(disabilityType == "{disabilityType}") or something like this. If the Customer object does not exist some sort of problem should be noted in the Problems section. Also a DSL might look like this:
> {percentage}=eval(customer.disabledPercent >= {percentage}) This to is a little harder as the customer is a variable that is implied.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBTIS-233) Highlighting a line in the Domain Specific Editor, the Delete key should work
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-233?page=com.atlassian.jira.plugin.... ]
Paul Leacu commented on JBTIS-233:
----------------------------------
[~KrisVerlaenen] [~jtyrrell]
Hey - this appears to be an enhancement request that hasn't moved in 18 months. Please comment by Friday.
> Highlighting a line in the Domain Specific Editor, the Delete key should work
> -----------------------------------------------------------------------------
>
> Key: JBTIS-233
> URL: https://issues.jboss.org/browse/JBTIS-233
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: drools/ jBPM
> Environment: All
> Reporter: Jim Tyrrell
> Assignee: Kris Verlaenen
> Attachments: Screen shot 2010-06-09 at 8.24.52 AM.png
>
>
> When I am editing or creating a Domain Specific Language it would be nice to have an Accelerator on the delete key to delete the highlighted line instead of having to click "Remove". It should also be possible to highlight all of them and be able to delete them all, although this might get in the way of what you happens when you click "Edit"
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-19349) Fix ShrinkWrap Archive file location validation issues
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19349?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-19349:
---------------------------------------
You are right. I have fixed the issue. Thanks.
> Fix ShrinkWrap Archive file location validation issues
> ------------------------------------------------------
>
> Key: JBIDE-19349
> URL: https://issues.jboss.org/browse/JBIDE-19349
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: arquillian
> Affects Versions: 4.3.0.Alpha1
> Reporter: Lucia Jelinkova
> Assignee: Snjezana Peco
> Fix For: 4.3.0.Beta2
>
>
> In JBIDE-14782, the validation was solved only partially. These issues still remain:
> - EAR - no validation for application.xml
> - WAR
> -- validation for beans.xml and web.xml going to WEB-INF
> --- addAsManifestResource - OK
> --- addAsWebResource - NOK
> -- validation for persistence.xml and ejb-jar.xml
> --- addAsWebInfResource - OK
> --- addAsWebResource - NOK
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-19505) Angular Code Assist doesn't work for jboss-kitchensink-angularjs app
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19505?page=com.atlassian.jira.plugi... ]
Victor Rubezhny edited comment on JBIDE-19505 at 7/14/15 12:35 PM:
-------------------------------------------------------------------
The discussion on the issue goes here: https://github.com/angelozerr/angularjs-eclipse/issues/118#issuecomment-1...
I see few issues here:
1) JSDT Tern Core Plugin wasn't forced to start for some reason (probably because of latest refactorings on the project): https://github.com/angelozerr/tern.java/commit/db1314d2e10f677b82abd60940... - it's fixed at the moment for coming v.0.10.
2) 'messages' variable is defined in ng-repeat attribute of {code}<li ng-repeat="message in successMessages">{{message}}</li>{code} tag attribute which isn't a supported case at the moment. This is not a something we can fix in upstream at the moment.
3) other variables aren't shown (like errors.name, errors.email, errors.phoneNumber) - not sure where they should came from... it looks like from the controller's $scope, but I don't think AngularJS-Eclipse is able to deal with such a controller... On the other hand there is an error marker on ng-app='kitchensink' attribute on index.html page that says: "Cannot find module with name kitchensink." - this could be a main problem to show these variables. (This error marker stays the same even after the first problem was fixed see #1 in this list)
was (Author: vrubezhny):
The discussion on the issue goes here: https://github.com/angelozerr/angularjs-eclipse/issues/118#issuecomment-1...
I see few issues here:
1) JSDT Tern Core Plugin wasn't forced to start for some reason (probably because of latest refactorings on the project): https://github.com/angelozerr/tern.java/commit/db1314d2e10f677b82abd60940... - it's fixed at the moment for coming v.1.0.
2) 'messages' variable is defined in ng-repeat attribute of {code}<li ng-repeat="message in successMessages">{{message}}</li>{code} tag attribute which isn't a supported case at the moment. This is not a something we can fix in upstream at the moment.
3) other variables aren't shown (like errors.name, errors.email, errors.phoneNumber) - not sure where they should came from... it looks like from the controller's $scope, but I don't think AngularJS-Eclipse is able to deal with such a controller... On the other hand there is an error marker on ng-app='kitchensink' attribute on index.html page that says: "Cannot find module with name kitchensink." - this could be a main problem to show these variables. (This error marker stays the same even after the first problem was fixed see #1 in this list)
> Angular Code Assist doesn't work for jboss-kitchensink-angularjs app
> --------------------------------------------------------------------
>
> Key: JBIDE-19505
> URL: https://issues.jboss.org/browse/JBIDE-19505
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing, upstream
> Affects Versions: 4.3.0.Alpha1
> Environment: JBDS 9.0.0.Alpha1-v20150216-1042-B11, Linux
> Reporter: Vlado Pakan
> Assignee: Victor Rubezhny
> Priority: Blocker
> Fix For: 4.3.0.Beta2
>
>
> 1. Import jboss-kitchensink-angularjs from JBoss Central
> 2. Open partials/home.html page
> 3. Open Angular Explorer and lind modules > MemberService > MembersCtrl to controler
> 4. Find this line {code}<li ng-repeat="message in errorMessages">{{message}}</li>{code} and invoke Code Assist for {{m
> ERROR: Code Assist doesn't contain proposal for message variable
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months