Hi Paul,
Thanks for sharing this!
Wouldn't it be more useful, though, if you tried to implement this as a
feature of Maven itself? I'm not known to be the biggest fan of Gradle, but
Gradle does know what needs to be rebuilt upon a change and will build
incrementally.
I'm really impressed how the
Hi,
I was working on a few of the issues for the 6.0-SNAPSHOT together with
Tamas.
There's still a few things to clean up before it would make sense to make a
new release.
- There's a lot of references to Nexus*. I was working on making this more
generic, so that there is no classes that have tha
> > [0] http://swagger.io
> > [1] http://apiblueprint.org
> > [2] http://raml.org
> > [3] https://github.com/swagger-api/swagger-spec#additional-libraries
> >
> >
> > On Mon, Nov 17, 2014 at 7:55 PM, Martin Todorov
> > wrote:
> >
> >>
REST API-s
I'm aware of Enunciate... Is that the only option, or are there any others
that can be used with Maven plugins?
Thanks in advance for any hints!
Kind regards,
Martin Todorov
ouldn't
have been ignored at all...
In the end, it's all up to you, but I'd recommend playing it as safe as
possible! :-)
On Fri, Sep 19, 2014 at 6:08 PM, Curtis Rueden wrote:
> Hi Kevin,
>
> > Is there a way to retry a flakey test?
>
> In general I agree with M
ice; I hope it's worth something to you.
Kind regards,
Martin Todorov
On Fri, Sep 19, 2014 at 5:24 PM, Kevin Burton wrote:
> Is there a way to retry a flakey test?
>
> I’d basically like to have a flag that retries a failing test 2 or 3 times.
>
> Flakey and non deterministic
ar
plugin running too late (or exporting the variables within a different
context to what is visible to the maven-resources-plugin)?
Thanks in advance and looking forward to your comments!
Martin Todorov
Hi Aitor,
You should place all your configuration files under src/main/resources. For
example: src/main/resources/myconf/myconf.properties. All files under
src/main/resources will get packaged into your artifact's jar file.
Furthermore, all your test resources should be placed (likewise) under
src
You cannot conditionally trigger one profile from within the other. You
will need to have two separate ones.
On Thu, Jul 24, 2014 at 6:17 PM, hanuman wrote:
> thanks very much(martin and brend) for your prompt replies .
>
> i.e.., can I conditionally invoke a profile within the other profile?
>
Hi,
I would suggest adding a second profile which is triggered only when the
other property is specified and only executes the third script. It's a bit
of duplication, but it should work.
When both profiles get activated, the plugin configurations will get merged.
I hope this helps!
Kind regards,
10 matches
Mail list logo