On Wed, Sep 14, 2016 at 4:51 AM, jieryn wrote:
> Maybe it is different for Spring than for Arquillian, but with
> Arquillian, they will (imho) correctly import a bom inside another
> bom, and sometimes those get out of sync. So if I import the latest
> arquillian:bom and the latest arquillian-tra
GitHub user max-norris opened a pull request:
https://github.com/apache/maven-archetype/pull/14
Fix for batch mode not being able to replace required properties
https://issues.apache.org/jira/browse/ARCHETYPE-509
If I specify a required property and then use that in another
Maybe it is different for Spring than for Arquillian, but with
Arquillian, they will (imho) correctly import a bom inside another
bom, and sometimes those get out of sync. So if I import the latest
arquillian:bom and the latest arquillian-transaction:bom, the
arquillian-transaction:bom might refere
On Tue, 13 Sep 2016 09:34:38 +0200, Christofer Dutz
wrote:
Hi,
I know there are several discussions underway in the context of pom 4.1
and alike. The problem with this is however that it was impossible for
me to follow those threads without putting my paid-work on hold ... a
short sum
On Tue, Sep 13, 2016 at 2:50 PM, jieryn wrote:
> I reported this for Arquillian, earlier...
> https://mail-archives.apache.org/mod_mbox/maven-dev/201608.mbox/%
> 3CCAArU9ia0C7bdvHEMTX3BU%3DChnrb-_chtw8N3xokvKO2_
> Rnzf1A%40mail.gmail.com%3E
>
> Arquillian also follows that style of multiple type=
I reported this for Arquillian, earlier...
https://mail-archives.apache.org/mod_mbox/maven-dev/201608.mbox/%3CCAArU9ia0C7bdvHEMTX3BU%3DChnrb-_chtw8N3xokvKO2_Rnzf1A%40mail.gmail.com%3E
Arquillian also follows that style of multiple type=bom concentrators
which are recommended practice. Even though
Hi,
This command creates a vanilla project using Spring Cloud that has a
hierarchy of BOMs
curl https://start.spring.io/starter.zip -d
dependencies=cloud-config-client -o demo.zip
extract and run and you'll get plenty of warnings[1]
I am trying to make sense of this message:
To resolve this co
Hi,
I know there are several discussions underway in the context of pom 4.1 and
alike. The problem with this is however that it was impossible for me to follow
those threads without putting my paid-work on hold ... a short summary of the
current state would probably be a good Idea to get peopl
