I think we should include the documents also in the zip distribution.
And there should be a jar distribution as well, as we are targeting it
to be used inside other Java programs. So IMHO the packaging structure
and names can be as follows:
wso2registry-1.0-alpha.war
==================
Webapp with relevant jars and other resources to be deployed in servlet
containers.
This provides the web UI for human interaction and APP interface for
interaction with other systems.
wso2registry-1.0-alpha.jar
=================
Registry library to be embedded and used inside Java programs. Once this
is embedded, Java programs
can interact with the Registry using the provided Java API.
wso2registry-1.0-alpha-src.zip
====================
Source distribution with the source of both core library and webapp modules.
wso2registry-1.0-alpha-docs.zip
=====================
Registry user guide and java docs.
wso2registry-1.0-alpha.zip
==================
Complete distribution containing wso2registry-1.0-alpha.war,
wso2registry-1.0-alpha.jar and wso2registry-1.0-alpha-docs.zip.
If we all agree with above structure, I can proceed with that.
Thanks,
Chathura
Deepal Jayasinghe wrote:
Hi all,
I think we need to discuss and figure out the way we are going to do the
registry packaging. At the moment I think we can have four release
artifacts in the distributions as follows,
- WAR distribution
- Will contain webapp and all the relevant jar files
-ZIP distribution
- Will contain WAR file as well as wso2regitry.jar file
-Source distribution (source.zip)
-Document distribution (docs.zip)
In addition to that , I think we can release remote registry as a the
separate distribution ,however wso2regitry.jar will contain all the jar
file related to that.
Thanks
Deepal
_______________________________________________
Registry-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/registry-dev
_______________________________________________
Registry-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/registry-dev
