[
https://issues.apache.org/jira/browse/TUSCANY-3760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12933914#action_12933914
]
ant elder commented on TUSCANY-3760:
------------------------------------
Thats because I stopped fixing it as it didn't sound like there was consensus
on what to do.
IMHO it doesn't seem correct to put things in the binary distribution which
aren't used by anything in the binary distribution (eg JSPs are only supported
in webapps not standalone), and, it also doesn't really seem right to have the
PDE target in the binary distribution either because the PDE target is used for
developing the source code so you need the source and are never going to be
using it with only the binary distribution.
It seems wrong to me to have webapp only things like implementation.web have
compile dependencies on the things that are known to be provided by the webapp
container and quite un-user friendly to say it would be ok as users can add an
exclude.
So i think it would be better to separate out the PDE target generation from
the binary distribution into something like features/pde-target. Then if you
get the source form either an SVN checkout or from a release source
distribution and you want to use the PDE you do a build with the pde profile
and point eclipse at the target that builds. That makes it much clearer whats
going on in my view than saying you first have to build the all distribution.
I'm happy to finish making these changes but i wont if people aren't happy with
that approach.
> 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.
