You’ll want to use maven’s dependency management section. If you don’t supply
one you’re inheriting it from somewhere. It provides for better control of the
ordering and so forth of the dependencies you want.
The idea is that in your parent pom, you use a dependency management section.
Then in
Flavio,
On 28. 3. 2016, at 16:08, Flavio Donadio wrote:
>> […] I am building my apps in Xcode […]
>
> Could you elaborate on this? Are you telling us you use XCode to do Java
> development? How well does it work?
Short answer: I do (essentially, see below re Java), and it works much better
t
On Mar 28, 2016, at 10:25 AM, Andrus Adamchik wrote:
> As a long-time user of maven-release-plugin and various maven repos , I have
> a mixed feeling about them. They are ok for releasing *libraries*, but are
> much less practical for *apps*.
Yeah, that’s another thing. I want release version
As a long-time user of maven-release-plugin and various maven repos , I have a
mixed feeling about them. They are ok for releasing *libraries*, but are much
less practical for *apps*. Our latest solution for the apps is centered around
a CI server (Bamboo in our case, but can be Jenkins, etc.) i
I have a multi-module project that builds with maven. Using the maven release
plugin, I’ve found I can increment the version and store the final artifacts to
nexus.
Now I want to take those artifacts from nexus, and deploy them into
staging/production. I’m having a bit of trouble googling for
OC,
You said,
> […] I am building my apps in Xcode […]
Could you elaborate on this? Are you telling us you use XCode to do Java
development? How well does it work?
Cheers,
Flavio
> On 26/03/2016, at 23:19, OC wrote:
>
> Well I seriously doubt this would really help anyone, but just in cas
