Michal,
Catching up with emails, I noticed the following. This message alarms
me a bit because:
- You may not check-in third-party code to the Eclipse repository
without Eclipse Legal approval. This is very clear in the entire Eclipse
IP Policy that all committers agree to follow (also see the
poster).
- There are no Contribution
Questionnaires for the technology.bpel project, so no approval has
been requested for Jaxen.
- Clearance to use Jaxen has been requested by ohf
and higgins
but not the bpel project.
- As an incubating project, the BPEL project can use the Parallel
IP process, but even that requires Eclipse Legal approval before
checking in third-party code.
- I notice that the code was checked in the repository by Michal
Chmeilewski on April 11th. Given that there is no IP clearance for
this, this situation is not good.
Michal - please explain the situation here. If I don't receive an
explanation by Friday, I will be forced to remove the unapproved code
from the repository.
- Bjorn
I am about to check-in the validator code and wanted to ask a couple of
questions.
1) I have used the Jaxen XPath library to parse XPath code and validate
the expressions.
That's an external library, how best to check it in ? As binary .jar ?
I am sure there is an Eclipse Protocol to follow here ...
2) I actually modified that library a bit to include source point
offsets so that I can position the markers correctly. How best to
capture that ?
|
