Ant

Please validate the below.. I am going through the RAT stuff.. and will fix the licenses within the JAR files.. what about concatenating all licenses into one file.. ? Would you be able to do that.. also I do not intend to put an ASL license in all resource files (such as sample synapse.xml configs, xslts etc).. is this really required?

ant elder wrote:
A comment you often see on ipmc reviews of incubating releases is that the distributions should unpack into a top level directory which includes the release number [1]. How about changing Synapse to do this, so for the 0.90 release the distro binary distro would unzip into a directory named synapse-0.90 and the src distro into synapse-src-0.90?
Source Dist : synapse-0.90-SNAPSHOT-incubating-src.zip
   Unpacks to: synapse-0.90-SNAPSHOT-src\....

Binary dist : synapse-0.90-SNAPSHOT-incubating-bin.zip
   Unpacks to: synapse-0.90-SNAPSHOT....

There was a comment about one of our Tuscany releases saying the release number should go before the '-incubating-', [2]. Thats maybe a maven2 thing, does that also apply to maven v1?
Done
The zip and jar names aren't so consistent right now either, theres Apache-Synapse-Incubating-0.90.jar, extension_mediators.jar, nhttp.jar, syanpse-0.90.mar. How about changing those to be synapse-0.90-incubating.jar , synapse-extensions-0.90-incubating.jar, synapse-nhttp-0.90-incubating.jar, synapse-0.90-incubating.mar. And for all the distro zips name them similarly, eg synapse-0.90-incubating-bin.zip, synapse-0.90-incubating-src.zip , synapse-extensions-0.90-incubating-bin.zip etc?

I prefer to leave the "incubating" off JARs and MARs.. cause otherwise its difficult to set dependencies on these from other projects.. please advice

synapse-core-0.90-SNAPSHOT.jar
synapse-extensions-0.90-SNAPSHOT.jar
synapse-samples-0.90-SNAPSHOT.jar

synapse-0.90-SNAPSHOT.mar


thanks
asankha

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to