[ 
https://issues.apache.org/jira/browse/TUSCANY-3760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12931347#action_12931347
 ] 

ant elder commented on TUSCANY-3760:
------------------------------------

If you get the Tuscany source code, either from SVN or a src distribution and 
try to develop that in the Eclipse PDE you need to first tell Eclipse about the 
PDE target. Currently that PDE target is generated and included in the binary 
distribution. That means if the binary distribution does not include all of the 
code or dependencies used by all the src then the target does not work and 
Eclipse reports errors. 

It is quite legitimate for the binary distribution to not include everything 
thats in the src tree, it might be in the unreleased folder, not yet ready for 
release, released somewhere else (like the Tomcat war distribution) or there 
may be a provided scope dependency as is being reported in this JIRA.

So to decouple the PDE target generation from the distribution means that the 
distribution does not have to be exactly the same as what is required by PDE to 
develop all the Tuscany source code in the Eclipse PDE. 

This doesn't need to change the binary distribution at all from what we have 
today, though it would then seem unnecessary to keep the PDE target thats 
included in the binary distribution so we'd probably want to stop doing that. 



> 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.

Reply via email to