http://java.sun.com/developer/technicalArticles/javaserverpages/code_convention/
It appears the convention is either jsp or jspf for fragments, so it this could be considered a bug with the plugin, I suppose. On the other hand, it is helpful to distinguish from JSPs which compile on their own, and those only suitable for includes, which is why I'm guessing no one has addressed this yet. On Fri, Jan 16, 2009 at 6:13 PM, Mitch Mattek <[email protected]>wrote: > Ah. That's good info. That was exactly the problem I was having. I didn't > realize there was a standard for that. I'll give it a whirl. > > > ------------------------------ > > *From:* Brandon Atkinson [mailto:[email protected]] > *Sent:* Thursday, January 15, 2009 4:05 PM > *To:* [email protected] > *Subject:* Re: [mojo-user] JSPC exclude > > > > I don't think this is possible, if I remember correctly. > > I was trying to filter out jsp fragments, because they won't compile, being > only fragments. > > My solution was to name all the JSP fragments with the proper '.jspf' > extension, as it appears that plugin picks up based on filename extension. > > -Brandon > > On Thu, Jan 15, 2009 at 2:37 PM, Wayne Fay <[email protected]> wrote: > > > Ok, I asked this before, but since we seem to have someone answering > > jspc questions on the list, is it possible to do an exclude of certain > > .jsp files with the plugin.? > > I'm not sure off the top of my head right now. The plugin code is > super simple as with most plugins -- you should take a look. > > If this is not supported functionality, I'm certain it would be pretty > easy to add some configuration in the pom and code in the plugin to do > it. > > Wayne > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > >
