Does the individual pom.xml not tell you what kind of repackaging is
happening? The reason for repackaging is that the original artifacts are
not OSGi bundles, so we process them to generate OSGi manifest entries
and repackage them as a new jar.
Thanks,
Sahoo
Harsha Godugu wrote:
> Can somebody blog / write a document about the kind of repackaging
> that happens in v3 build? The question why it happens and how do we
> track the class files to their sources?
> If there are already documents available, a pointer is appreciated?
>
> Also, where are the sources located for the following: (in javaee-api)
> <modules>
> <module>javax.javaee</module> <!-- This is the assembly module-->
> <module>javax.activation</module>
> <module>javax.annotation</module>
> <module>javax.ejb</module>
> <module>javax.enterprise.deploy</module>
> <module>javax.faces</module>
> <module>javax.jms</module>
> <module>javax.jws</module>
> <module>javax.mail</module>
> <module>javax.management.j2ee</module>
> <module>javax.persistence</module>
> <module>javax.resource</module>
> <module>javax.security</module>
> <module>javax.security.auth.message</module>
> <module>javax.servlet</module>
> <module>javax.servlet.jsp</module>
> <module>javax.servlet.jsp.jstl</module>
> <module>javax.transaction</module>
> <module>javax.xml.bind</module>
> <module>javax.xml.rpc</module>
> <module>javax.xml.soap</module>
> <module>javax.xml.stream</module>
> <module>javax.xml.ws</module>
> </modules>
>
> If the above all are open sourced projects, can they have the SCM tag
> in their respective pom.xml files?
>
>
> thanks,
> Harsha
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>