I'm sorry to see a VETO here while the technical discussion is still active.
Anyway, going back to the technical side, here is the description from the maven doc about the "provided" scope: provided This is much like compile, but indicates you expect the JDK or a container to provide the dependency at runtime. For example, when building a web application for the Java Enterprise Edition, you would set the dependency on the Servlet API and related Java EE APIs to scope provided because the web container provides those classes. This scope is only available on the compilation and test classpath, and is not transitive. The key is that we assume the hosting environment will provide the jar if we use "provided" scope. In fact, Tuscany supports quite a few hosting environment out of the box and it can be embedded into other environment. Let me list a few: * Standalone launcher * Use Node API with the application * Eclipse plugin * Eclipse IDE with PDE * OSGi runtime * Webapp * Google App Engine * Tomcat deep integration Do we have all the hosting environment that provide the servlet/jsp jars? Maybe some of us only care about a subset of the options, but we need to understand if the dependency is really provided? IMO, we probably need to deal with these exclusions at maven assembly level when the distributions (for example, the WAR) are produced. Thanks, Raymond ________________________________________________________________ Raymond Feng [email protected] Apache Tuscany PMC member and committer: tuscany.apache.org Co-author of Tuscany SCA In Action book: www.tuscanyinaction.com Personal Web Site: www.enjoyjava.com ________________________________________________________________ On Nov 23, 2010, at 5:06 AM, ant elder (JIRA) wrote: > > [ > https://issues.apache.org/jira/browse/TUSCANY-3760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12934823#action_12934823 > ] > > ant elder commented on TUSCANY-3760: > ------------------------------------ > > Also see ML http://apache.markmail.org/message/dwemu7p72hi6elku > > In case it wasn't clear from the previous comment that -1 was a VETO, I've > reverted that change now. I have updated features/eclipse-pde to include > those dependencies now which should fix the problem so can you try using that > please? If you still have issues please work with me on or off list to > resolve them. > >> Stripes and Implementation-Web-Runtime modules have POM & MANIFEST errors >> that causes execution failures with main build under OSGi >> ----------------------------------------------------------------------------------------------------------------------------------- >> >> Key: TUSCANY-3760 >> URL: https://issues.apache.org/jira/browse/TUSCANY-3760 >> Project: Tuscany >> Issue Type: Bug >> Components: Java SCA Misc Implementation Extensions >> Affects Versions: Java-SCA-2.0-M5 >> Reporter: Mike Edwards >> Fix For: Java-SCA-2.x >> >> >> Stripes: >> a) MANIFEST contains these entries: >> javax.servlet.jsp, >> javax.servlet.jsp.tagext, >> ...these are not actually supplied in any dependency of Stripes, but they >> are also not used by Stripes either. >> Earlier versions of the servlet-api package used to contain these packages, >> but not the most recent ones, which thus causes a resolution failure under >> OSGi, even though the code will actually execute successfully. >> b) POM problems: >> Dependency net.sourceforge.stripes.stripes is declared as "provided" but >> does not appear in the main build at all, leading to an OSGI resolution >> failure. >> b) Implementation-Web-Runtime: >> Dependencies: >> javax.servlet.servlet-api >> org.apache.geronimo.specs.geronimo-jsp_2.1_spec >> org.apache.geronimo.specs.geronimo-el_1.0_spec >> ...are declared as "provided" scope, but don't turn up in the main >> distribution build, leading to a resolution failure for this module under >> OSGi > > -- > This message is automatically generated by JIRA. > - > You can reply to this email to add a comment to the issue online. >
