RE: AW: AW: AW: mvn release:prepare does not update parent version

2013-11-09 Thread Martin Gainty
> Date: Sat, 9 Nov 2013 08:31:21 -0500 > Subject: Re: AW: AW: AW: mvn release:prepare does not update parent version > From: gordon.c...@zafin.com > To: users@maven.apache.org > > You may want to upgrade maven itself once more. It is not just maven itself > but the combination of plugins tha

Android Maven Plugin 3.8.0 released

2013-11-09 Thread Manfred Moser
The Android Maven Plugin team is pleased to announce the release of version 3.8.0 of the plugin. This release marks a change in the plugin since we now require Apache Maven 3.1.1 (or higher). New features/bug fixes are - Migrated to require Apache Maven 3.1.1 or higher - Updated to builder libra

Re: AW: AW: AW: mvn release:prepare does not update parent version

2013-11-09 Thread Robert Scholte
I'm pretty sure that by far most projects are released with 2.0, since this has been the default for Apache Maven for many releases. IIRC this has been updated for Maven 3.0.3, so if you don't specify the version, 2.0 will be used. Now let's review this thread: 1. Markus describes his issue

Re: AW: AW: AW: mvn release:prepare does not update parent version

2013-11-09 Thread Gordon Cody
You may want to upgrade maven itself once more. It is not just maven itself but the combination of plugins that are used and your environment matters. Ensure that each maven goal you plan on using in your environment actually works in your environment before you need it for real. Maven has to work

RE: AW: AW: AW: mvn release:prepare does not update parent version

2013-11-09 Thread Martin Gainty
> From: k...@quipsy.de > To: users@maven.apache.org > Date: Fri, 8 Nov 2013 16:30:30 +0100 > Subject: AW: AW: AW: mvn release:prepare does not update parent version > > Martin, > > thank you for your explanations, but as it turned out the problem is fixed > simply by using version 2.4.2

RE: AW: AW: AW: mvn release:prepare does not update parent version

2013-11-09 Thread Markus Karg
Robert, no need to teach me about completeness of reports -- I am in the reverse situation day by day as you can imagine. The problem was that I had the problem since I migrated to Maven 3 from day one with even the smallest possible POM (it looked 'obvious' to me) and did not have the idea the

Re: Imports of required classes have classname only without package path within the class compiled by maven

2013-11-09 Thread brandenberger
As announced, here a little summary about the experiences with the WebeSphere developer tools for eclipse 4. Positive: It works! Eclipse generates a valid build, as well as does maven! and even debugging is possible. Negative: The marketplace seems to have a problem. At least I was unable to in