On Nov 14, 2007 7:29 AM, Adriano Crestani <[EMAIL PROTECTED]>
wrote:

<snip>

Luciano:
> Distribution artifact names : I'd follow the same naming of previous
> native releases [1] and use tuscany_das_cpp-1.0-incubator-M4-bin.zip
> I'm also not sure if the native project wants to start using
> incubating in the name, to follow the same pattern being used in the
> java releases.
>

I think its currently "incubating" thats prefered these days, "incubator"
was an older one.


>
> [1]
>
> http://people.apache.org/dist/incubator/tuscany/cpp/1.0-incubator-M2/win32/
>
> Sorry, I have added a new property on plataform.properties file that
> defines
> the distribution file name, I just forgot to set it before pack the
> distribution files, then it used the default value that is
> "tuscany_das_cpp". But, I will be using
> "tuscany_das_cpp-1.0-incubator-M4-<type>.<extension>"
> naming pattern, following the last sdo and sca cpp release.
>
>
> Release artifact names : Should DLL and other artifacts have
> incubator/incubating on their names ? So, tuscany_das.dll would become
> tuscany-das-1.0-incubator-M4.dll
>
> I was just following the last cpp bin releases. So, I think I'm not the
> right person to answer that. But for me, it's ok to keep "tuscany_das.dll"
> ;
> )
>
>
The things that need to include "incubating" in the name are the artiacts
that will be distributed individually somewhere , so the binary and src
distributions do as they're on the download page, in Java all the jars that
go in the the maven repository need it which is why all the sca/module jars
have it but the sca/samples don't, so if the .dll's are available somewhere
outside of the binary distribution they need it otherwise probably not.

   ...ant

Reply via email to