On Mon, Sep 17, 2012 at 8:49 AM, David M Williams
<david_williams@xxxxxxxxxx> wrote:
If it is a fix or change to the code of
org.apache.jasper.glassfish, then you only option is to work with the original
project and have them fix their code and have a new maintenance release.
To be clear, though, there are times
when we in Orbit can made a mistake in the way we "OSGi-ify"
the bundle and those are fixes we can make directly in Orbit. jasper.glassfish
is a current case,
see bug 389510.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=389510
Haha, yeah. That's my ticket!
However, I would like to propose a change to the underlying library such that Jasper would allow injection or deceleration of a "custom" JavaFileManager factory.
This way it would be a cinch to allow it to support an OSGi aware (or any custom) JavaFileManager thus avoiding most of the workarounds currently needed to make JSP compilation work in OSGi.
- Ray
From:
Raymond Auge <raymond.auge@xxxxxxxxxxx>
To:
Equinox development
mailing list <equinox-dev@xxxxxxxxxxx>,
Date:
09/17/2012 08:32 AM
Subject:
[equinox-dev]
process for requesting change in an orbit based bundle
Sent by:
equinox-dev-bounces@xxxxxxxxxxx
Hello All,
How do I go about getting a change into an orbit bundle?
Case is for org.apache.jasper.glassfish.
As I understand it, orbit bundles come from an upstream
source, so I'm assuming technically that Eclipse doesn't have the source
to change.
So, how do you handle bugs or change requests in those?
Thanks,
--
Raymond
Augé | Senior
Software Architect | Liferay,
Inc.
---
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev