facebook

JSP Compiler errors for files not in source tree

  1. MyEclipse Archived
  2.  > 
  3. Bugs
Viewing 6 posts - 31 through 36 (of 36 total)
  • Author
    Posts
  • #201158 Reply

    Riyad Kalla
    Member

    1) awesome about the enhancement
    2) Kivus that actually isn’t such a bad idea (the JSP compilations). Does this fit your needs or do you really need the on-the-fly error reporting and such? Can you change the app’s docBase to point to your dev dir, so instead of leetting ME find the errors, just hit refresh in your browser and the compiler will give them to you?

    #201174 Reply

    No Operation
    Member

    Currently, the JSP editor will compile all JSP’s in a project. There is already an open enhancement request to allow the user to specify a policy on handling JSP’s outside the web root (ignore, warning, error).

    This will remove the error messages for you, but also disables the checkin for all files outside.

    I also agree with NOP that the application structure could be modified to work with how ME requires its project defitions, but I will not be able to convince management to license the project if it’s going to require all developers to change their environments.

    Where is the big deal?

    1 Person performs the changes, and checks them in.
    All other just do a checkout.
    Done.

    Where I work developers also complain if something must be changed, but if it’s reasonable the company forces it. So all complained when we switched the IDE, today they are happy to use Eclipse.

    NOP

    #201187 Reply

    Riyad Kalla
    Member

    not everyone works with people that eventually STOP complaining 😉

    #201338 Reply

    kivus
    Member

    Sorry, got lost in the Christmas spriti for a few days there…

    Anyway, I’ve read back over your responses and I know that turning off JSP complilation will work. The other alternative (which I will probably employ) is to only have one application per domain. The problem with that is obviously maintaining JAR files, but the positives of having JSP compilation will work.

    The enhancement of turning off the JSP complilation warnings still doesn’t help me because I cannot have over laping projects with eclipse (not a ME issue). So I would still be forced to have only one web application per domain.

    Is there a way to request an ehancement to allow the web root to be the project root? Basically, this would solve all my issues. Until then, I will continue to use ME personally, but I will not having the feature set necessary to propose its adoption throughout my company. As rkalla said, not everyone works with people that stop complaining.

    Thank you all for you help.

    #201340 Reply

    support-michael
    Keymaster

    Is there a way to request an ehancement to allow the web root to be the project root? Basically, this would solve all my issues.

    Last week I entered your issues as an enhancement request. We understand the issue and it is being actively discussing how to make the change. I’m not sure if/when this will be addressed but it has development’s attention now.

    Regards,

    Michael
    MyEclipse Support

    #201347 Reply

    kivus
    Member

    Cool. Thank you Michael.

Viewing 6 posts - 31 through 36 (of 36 total)
Reply To: JSP Compiler errors for files not in source tree

You must be logged in to post in the forum log in