Hi All
Hong and myself have experienced to failure with the build and I
suspect others will see the same issue.
The issue comes from the jsp project which has promoted a new
versioned pom.xml without changing the version number. In such case
folks that already have downloaded that version end up keeping the old
version leading to an OSGi ResolveError on the org.apache.jasper package
Let me reiterate one more time that you cannot publish a new versioned
module with the same version number multiple time, you *have* to
change the version number each time you want to change the content of
the jar or the associated pom.
Jerome