Radim Kubacki wrote >> 1. Eclipse does not recognize it due to missing jst.utiltiy facet > > I will need some time to look at this. Some things in WTP support are > strange and it is complex area.
Ok, maybe http://www.eclipse.org/webtools/development/proposals/WtpProjectFacets.html#_Jst.utility helps you a bit to understand it better. Radim Kubacki wrote >> I have tested with a project in question by creating an own gradle >> version using the "install" task. > > If I understand correctly you want to make sure that dependencies like > junit (coming from test/testRuntime configuratio) that are on a classpath > of you library do not get added into your WAR. OTOH we would like to be > able still run tests for that library project, right? If you patches > address that then it would be welcome. Yes, you can configure the behavior such that every configuration you would like to add to "Deployment Assembly" can be, but the default behavior is to just add "compile" configuration. I will add some integration tests showing this. Radim Kubacki wrote >> 1. Is there anything else to be aware of or can I just create a pull >> request after implementing some tests? > > I believe accompanying your patch with a good test(s) will make your > intent more obvious and it makes integration process easier. Thanks for > your interest. Ok, I will add some tests :-) Radim Kubacki wrote >> 2. Furthermore, I want to configure the "eclipse.wtp.facet" on my "jar" >> project but I need to use "gradle.projectsEvaluated" (see also my >> comment: >> >> http://forums.gradle.org/gradle/topics/wtp_elipse_requires_ear_or_war_i_need_wtp_to_build_ejb_modules_but_i_dont_want_an_ear_artifact#reply_14825115 >> ). >> This is required because in >> "org.gradle.plugins.ide.eclipse.EclipseWtpPlugin" all the configuration >> is done in "doLaterWithEachDependedUponEclipseProject(Project)". I have >> tried to remove the "project.gradle.projectsEvaluated" closure but has >> not helped. Even worse, this causes the "eclipse.wtp.facet" to be not >> configurated at all :-( >> >> I have also tried to add a configuration for "JavaPlugin" not just >> "WarPlugin" and "EarPlugin" but this causes the complete >> "EclipseWtpPlugin" to break down for "war"s (IMHO due to "WarPlugin" >> also applies "JavaPlugin" and the ".withType" is always executed first >> for "JavaPlugin", not for "WarPlugin" if available). >> >> >> I am really curious to get further information about this. Also I would >> be interessted in helping with the "Improved Tooling & IDE support" on >> the roadmap. >> > > We are at the point where we need to re-evaluate current integration and > feedback like this definitely helps us better see what are common use > cases. What do you mean with that? And can you answer the above question, how I could get rid of the "gradle.projectsEvaluated" surrounding the "eclipse.wtp..." configuration for my war-depended subprojects? How can I help you understanding this problem, or is there the possibility to have a call using screen sharing etc.? I really appreciate the fast answer, thanks for further help in advance. -- View this message in context: http://gradle.1045684.n5.nabble.com/Default-configurations-for-Eclipse-WTP-plugin-on-dependent-jar-tp5713163p5713166.html Sent from the gradle-dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
