[jbosstools-issues] [JBoss JIRA] (JBDS-2802) Investigate use of SpringIDE 3.4 in JBT/JBDS Central

[Marián Labuda (JIRA)]

    [ https://issues.jboss.org/browse/JBDS-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12829543#comment-12829543 ] 

Marián Labuda edited comment on JBDS-2802 at 11/1/13 2:54 PM:
--------------------------------------------------------------

JBDS-2691 - after import of the project there are several errors (all related to "Build path is incomplete. Cannot find class file for org/aspect/weave/BCException") and warnings in Problems view, but after delete it from view and validate project there is only that one problem - "invalid" element altough it is valid - that one I´ve mentioned (application deployed on EAP runs without any visible issues). I am not sure, how that Jirka thought - if all "steps to reproduce" is necessary to see given errors or it had appeared while executing those steps... If those given errors are shown after executed all the steps, than it´s solved AFAIK.

JBDS-2690 - the given error is not shown after installation of the IDE, but after appearing mentioned errors (in JBDS-2691) in Problems view. When I add Spring nature to the project, every other created archetype project has already included Spring nature and observing the given errors is almost impossible. To let "build path incompletion" errors be shown it´s required to remove spring nature, try to validate project, add spring nature again etc. - trying to "play" with it and if you are lucky, it appears.

My opinion - I´m not aware of any blocker / critical issue related to the new Spring IDE version (3.4.0.x) AFAIK. If you think, we could provide 3.4 in Central, I´m in.
                
      was (Author: mlabuda):
    JBDS-2691 - after import of the project there are several errors (all related to "Build path is incomplete. Cannot find class file for org/aspect/weave/BCException") and warnings in Problems view, but after delete it from view and validate project there is only that one problem - "invalid" element altough it is valid - that one I´ve mentioned (application deployed on EAP runs without any visible issues). I am not sure, how that Jirka thought - if all "steps to reproduce" is necessary to see given errors or it had appeared while executing those steps... If those given errors are shown after executed all the steps, than it´s solved AFAIK.

JBDS-2690 - the given error is not shown after installation of the IDE, but after showing mentioned errors (in JBDS-2691) in Problems view. When I add Spring nature to the project, every other created archetype project has already included Spring nature and showing the given error is almost impossible. To let "build path incompletion" errors be shown it´s required to remove spring nature, try to validate project, add spring nature again etc. - trying to "play" with it and if you are lucky, it appears.

My opinion - I´m not aware of any blocker / critical issue related to the new Spring IDE version (3.4.0.x) AFAIK. If you think, we could provide 3.4 in Central, I´m in.
                  
> Investigate use of SpringIDE 3.4 in JBT/JBDS Central
> ----------------------------------------------------
>
>                 Key: JBDS-2802
>                 URL: https://issues.jboss.org/browse/JBDS-2802
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: 3rd-party-certification, 3rd-party-dependencies, central
>    Affects Versions: 7.1.0.Alpha2
>            Reporter: Nick Boldt
>            Assignee: Marián Labuda
>
> New mirror for SpringIDE 3.4.0.201310051539-RELEASE:
> http://download.jboss.org/jbosstools/updates/requirements/springide/3.4.0.201310051539-RELEASE/

--
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