Am 09/28/16 um 04:48 schrieb Christian Schulte:
> Am 09/28/16 um 04:16 schrieb Christian Schulte:
>> Am 09/27/16 um 15:24 schrieb Stephen Connolly:
>>> I think that may be problematic... but probably not the worst thing to add
>>> to the schema (would just be an extra attribute)
>>
>> Something
Am 09/28/16 um 04:16 schrieb Christian Schulte:
> Am 09/27/16 um 15:24 schrieb Stephen Connolly:
>> I think that may be problematic... but probably not the worst thing to add
>> to the schema (would just be an extra attribute)
>
> Something you can use to identify the entity having produced an
Am 09/27/16 um 15:24 schrieb Stephen Connolly:
> I think that may be problematic... but probably not the worst thing to add
> to the schema (would just be an extra attribute)
Something you can use to identify the entity having produced an artifact
and useable to verify an artifact has not been
GitHub user pabloa opened a pull request:
https://github.com/apache/maven-plugins/pull/92
MDEPLOY-214: Added property "retryFailedDeploymentDelay" on
maven-deploy-plugin
This property impose a delay between 0 seconds to 5 minutes (max)
between retries. Default value: 20
GitHub user pabloa opened a pull request:
https://github.com/apache/maven-shared/pull/18
MDEPLOY-214: Added property "retryFailedDeploymentDelay".
This property impose a delay between 1 second to 5 minutes (max)
between retries. The intention is to make maven more
solid and
Hello,
I noticed in the documentation here[1] that you can use
the @net.jcip.annotations.NotThreadSafe annotation to prevent a test class
from running in parallel. Is it also possible to use
the javax.annotation.concurrent.NotThreadSafe annotation in the same way as
I'd like to not have to
I think that may be problematic... but probably not the worst thing to add
to the schema (would just be an extra attribute)
Btw an alternative schema has a top level tag as a container for
the platform specific artifacts... has advantages with non-atomic deploys
of different artifacts as you can
