[
https://issues.apache.org/jira/browse/TOMEE-1361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14147950#comment-14147950
]
jieryn commented on TOMEE-1361:
-------------------------------
I don't know of any specific openjpa problems - I mean only that TomEE had to
bundle their own to work around whatever issues. By having it at different
actual coordinates instead of a separate version number, it requires a
fantastic amount of maven-fu to work around.. whereas a simple namespaced
version deployment org.apache.openjpa:openjpa:2.3.0-openejb-r123 would have
worked and been easier on users to just do a simple version change in
dependencyManagement.
Yes, I agree that an example is almost always required and probably especially
in this case as it is probably classpath related. I'm just saying that like
your time isn't free, neither is mine. And there's a real cost to work through
all these issues just to finally get to a point where I can create a testcase.
I want this bug fixed, so the duty is on me; I just wish it were easier to help
contribute, the current TomEE development environment/mechanisms and
documentation issues are real inhibitors.
> tomee-m-p automatic reload leaves previously deployed @Path JAX-RS resources
> undeployed
> ---------------------------------------------------------------------------------------
>
> Key: TOMEE-1361
> URL: https://issues.apache.org/jira/browse/TOMEE-1361
> Project: TomEE
> Issue Type: Bug
> Components: TomEE Maven Plugin
> Reporter: jieryn
>
> I am running a web application via tomee:run:1.6.0.2 and have a dependency on
> another module packaging=war which contains @Path JAX-RS resouces. When I
> make a change to the current module's index.html page, e.g., the overlayed
> JAX-RS resources are not available after tomee automatically reloads itself.
> This is a huge problem for developer productivity.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
