Hi Mark; I set this *provided*,because these jars are all provided with the Java EE containers. If someone uses the web container like, Jetty or Tomcat then he has to add some Java EE jars (not all, because some of them are provided by them like servlet-api, jsp-api etc.) into the classpath.
Our main concern is the Java EE containers, not the standalone web containers. Moreover, if we change the *compile* then *guess* application has packaged with all dependencies. It is unwanted structure for Java EE containers. I think that the current configuration is the good for the time being; Cheers; Gurkan ________________________________ From: Mark Struberg <[email protected]> To: [email protected] Sent: Wednesday, February 11, 2009 4:58:04 PM Subject: webbeans-impl dependencies Hi! Currently many dependencies of the webbeans-impl module do have the <scope>provided</scope>.http://www.mechsoft.com.tr/Download/Fujipoly/fujipolyseminarkayit.htm May we change this to the default scope 'compile'? The reason: scenario 1) If I like to use OpenWebBeans standalone in e.g. a WAR, then maven usually resolves all dependencies with scopes 'runtime' and 'compile' and adds them to WEB-INF/lib, but obviously doesn't do this for 'provided'. scenario 2) If I like to build a webapp for deploying it in a J2EE container like Geronimo, then OpenWebBeans (or any other jSR-299 impl) will be there already, so my webapp doesn't need any webbeans-impl dependency (and therefore there are no transitive dependencies) but only webbeans-api with scope 'provided'. So my proposal is to change all (have to review this again) 'provided' scoped dependencies to the default of 'compile'. After this I'll checkin a new profile 'jetty' to the guess samples pom.xml so one can start it via $> mvn -Pjetty clean package jetty:run as standalone jetty application ;) LieGrue, strub
