[2.x] what are all the profiles for?

[Simon Laws <si...@googlemail.com>]

I see quite a few profiles in the the top level pom.xml file. What are
they all for and do we need to maintain them. I've has a go add
identifying the ones that I know about

default           - builds all the source and tests (builds a distro
dir now rather than zrchives)
distribution     - sames a default except that is builds distro archives

sources          - ?
eclipse           - builds eclipse projects
osgi               - ?
dependencies - ?
security          - runs the build with Java security turned on but I
don't think we've tried it recently. Should be part of the distro
build?
sourcecheck   - source formatting etc. no idea if we ever run this
release           - ?
base              - ?
jms                - ?

Can you describe the profiles that you think should stay. At some
point I'll remove the ones that no one sticks up for.

Simon

-- 
Apache Tuscany committer: tuscany.apache.org
Co-author of a book about Tuscany and SCA: tuscanyinaction.com

Re: [2.x] what are all the profiles for?

[ant elder <an...@gmail.com>]

On Tue, Nov 24, 2009 at 12:49 PM, Simon Laws <si...@googlemail.com> wrote:
> I see quite a few profiles in the the top level pom.xml file. What are
> they all for and do we need to maintain them. I've has a go add
> identifying the ones that I know about
>
> default           - builds all the source and tests (builds a distro
> dir now rather than zrchives)
> distribution     - sames a default except that is builds distro archives
>
> sources          - ?
> eclipse           - builds eclipse projects
> osgi               - ?
> dependencies - ?
> security          - runs the build with Java security turned on but I
> don't think we've tried it recently. Should be part of the distro
> build?
> sourcecheck   - source formatting etc. no idea if we ever run this
> release           - ?
> base              - ?
> jms                - ?
>
> Can you describe the profiles that you think should stay. At some
> point I'll remove the ones that no one sticks up for.
>
> Simon
>
> --
> Apache Tuscany committer: tuscany.apache.org
> Co-author of a book about Tuscany and SCA: tuscanyinaction.com
>

The base and jms ones are for testing with profiles to only build
whats needed for a minimal runtime and the JMS extenesion. The release
one was trying to get the maven release plugin working but it doesnt
work with Tuscany yet.

   ...ant