>> - I'll try to let gump run the junit tests as well so we'll know when
we
>> break them
I think it's a good idea. But you should make a second Gump project for
that.
Spend the Gump descriptor [1] a second <project>. Have a look at Ant's
[2] descriptor ...
<module name="ivy">
...
<project name="ivy"> ...
<project name="test-ivy">
<depend project="ivy" />
<depend project="junit" />
...
</project>
</module>
[1] http://svn.apache.org/repos/asf/gump/metadata/project/ivy.xml
[2] http://svn.apache.org/repos/asf/gump/metadata/project/ant.xml
>It would be good, but only the offline tests, the online tests
>are too much unreliable.
Maybe a 3rd gump project?
>> - I think it is also possible to publish the snapshot produced by
gump.
>>
>> Its not normally done anymore, primarily for security reasons. too
much
>> untrusted code runs during a gump build; anyone who builds before you
>> could subvert your artifacts. This has never happened -yet- but it is
>> not something you want people to be using and relying on,
>
>If there is security issues I understand, but how could we setup
something
>to publish some kind of nightly build? I think it eases adoption and
>feedback on latest features, so it would be nice to have.
Antoine has written something for Ant - build [3] I think ...
[3] http://svn.apache.org/repos/asf/ant/build/trunk/
Jan
