Agreed. There was a misunderstanding between Kin-Man and myself. We plan
to remove the module from svn, as it is no longer needed. The published
artifact will remain untouched in maven repo.
Thanks,
Sahoo
Stephen Connolly wrote:
> Once something is deployed to an m2 repo, you should never remove it
> (unless there are legal reasons for you having to stop)... and you can
> _never_ replace it with an updated binary.... you'd need a new version
> number for the update
>
> On Fri, Aug 1, 2008 at 7:39 PM, Kin-man Chung <Kin-Man.Chung_at_sun.com
> <mailto:Kin-Man.Chung_at_sun.com>> wrote:
>
> jasper-jsr199 was never a module in V3. I deposited jasper-199.jar in
> maven repository because its binary could not be built when V2 was
> built
> (it can only be built with JDK 6). But that's no longer necessary
> since
> JSP is now separate from V3.
>
> Perhaps you meant removing it from the maven repo? I don't have the
> karma for that.
>
> -Kin-man
>
>
> Sahoo wrote:
>
> svn rm?
>
> Kin-man Chung wrote:
>
> I thought it WAS removed. There is no reference to it
> from any module.
>
> -Kin-man
>
> Sahoo wrote:
>
> That's good news. Will you then remove it from v3?
>
> Thanks,
> Sahoo
>
> Kin-man Chung wrote:
>
> jasper-jsr199 is no longer needed. It is now
> included in jspimpl.jar.
>
> Sahoo wrote:
>
> If you look at v3/distributions/external
> directory, you shall find we repackage around
> a dozen of jar files to add OSGi meta data.
> The artifacts fall into two categories, viz:
> artifacts originally developed by some other
> group in Sun and artifacts from some other
> open source projects. Of the current list of
> artifacts being repackaged, we shall
> definitely remove grizzly*, jaxb by HCF time.
> We will then be left with the following Sun
> produced artifacts:
> jasper-jsr199,
> jmxremote_optional,
> ldapbp,
> sysnet-registration.
>
> Can owner of every module that primarily
> require the aforementioned artifacts to
> contact the original artifact suppliers to get
> OSGied versions so that we don't have to
> repackage them in v3 workspace?
>
> Thanks,
> Sahoo
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> dev-unsubscribe_at_glassfish.dev.java.net
> <mailto:dev-unsubscribe_at_glassfish.dev.java.net>
> For additional commands, e-mail:
> dev-help_at_glassfish.dev.java.net
> <mailto:dev-help_at_glassfish.dev.java.net>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> dev-unsubscribe_at_glassfish.dev.java.net
> <mailto:dev-unsubscribe_at_glassfish.dev.java.net>
> For additional commands, e-mail:
> dev-help_at_glassfish.dev.java.net
> <mailto:dev-help_at_glassfish.dev.java.net>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> dev-unsubscribe_at_glassfish.dev.java.net
> <mailto:dev-unsubscribe_at_glassfish.dev.java.net>
> For additional commands, e-mail:
> dev-help_at_glassfish.dev.java.net
> <mailto:dev-help_at_glassfish.dev.java.net>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> dev-unsubscribe_at_glassfish.dev.java.net
> <mailto:dev-unsubscribe_at_glassfish.dev.java.net>
> For additional commands, e-mail:
> dev-help_at_glassfish.dev.java.net
> <mailto:dev-help_at_glassfish.dev.java.net>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> <mailto:dev-unsubscribe_at_glassfish.dev.java.net>
> For additional commands, e-mail:
> dev-help_at_glassfish.dev.java.net
> <mailto:dev-help_at_glassfish.dev.java.net>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> <mailto:dev-unsubscribe_at_glassfish.dev.java.net>
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
> <mailto:dev-help_at_glassfish.dev.java.net>
>
>