Alberto,
you could bind to the phase "verify" as well, which will package your
artifacts and runs integration-tests (e.g. started with the
failsafe-plugin) additionally.
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/
https://bitbucket.org/mfriedenhag
Thanks, everyone!
Ivo
On Fri, Feb 15, 2013 at 2:10 PM, Baptiste MATHUS wrote:
> True.
> The hard part, you did, Luke ;-)
>
>
> 2013/2/15 Stephen Connolly
>
> > OT. this blind man on a galloping horse cannot tell the exact scm goal
> > names ;-)
> >
> >
> > On 15 February 2013 15:41, Baptiste
True.
The hard part, you did, Luke ;-)
2013/2/15 Stephen Connolly
> OT. this blind man on a galloping horse cannot tell the exact scm goal
> names ;-)
>
>
> On 15 February 2013 15:41, Baptiste MATHUS wrote:
>
> > Just bind the maven-scm-plugin with that goal&conf (which actually seems
> to
> >
> -Original Message-
> From: Alberto Ivo [mailto:alberto...@gmail.com]
> Sent: Friday, February 15, 2013 4:52 AM
> To: Maven Users List
> Subject: Run unit tests before commiting
>
> Hello,
>
> Nowadays When I change the code, I manually run the unit test (suite) and
> then commit using E
Ok, thanks for the clarification.
I was hoping that the plugin would let me know that I'm trying to do something
that can't be done (since the result would be identical to the existing POM).
That is: Issue a warning instead of fail the build.
But anyway: How could I find out myself whether the c
OT. this blind man on a galloping horse cannot tell the exact scm goal
names ;-)
On 15 February 2013 15:41, Baptiste MATHUS wrote:
> Just bind the maven-scm-plugin with that goal&conf (which actually seems to
> be checkin instead of commit) onto the right phase (here it may be "test").
> Look a
version-maven-plugin assumes that if you don't provide /project/version and
instead rely on /project/parent/version being the default value then *the
child must always have the same version as the parent*.
If the child may have a different version, then you specify the version.
This behaves simil
Just bind the maven-scm-plugin with that goal&conf (which actually seems to
be checkin instead of commit) onto the right phase (here it may be "test").
Look at the Maven lifecycle to understand what a phase is
http://maven.apache.org/scm/maven-scm-plugin/checkin-mojo.html#message(search
for "defaul
Hi
I'm using the versions-maven-plugin during our semi-automated release process
to set a version.
However, I have a problem whenever the version of the project is the same as
the one in the parent.
Maven 3 shows a warning if the versions are the same, but if I remove the
version (which seems
Hi Richard,
Thanks for your answer, I think my last example confused everyone :-).
My problem is a bit a different (I think) here it goes again:
*SETTINGS.XML snippet*
company.default.profile
company.default.profile
*
I'm sorry.. I'm noob.. I didn't get it.
Is there a way to do it inside the pom.xml?
Ivo
On Fri, Feb 15, 2013 at 11:15 AM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> mvn clean test scm:commit -Dmessage="I am great"
>
>
> On 15 February 2013 12:51, Alberto Ivo wrote:
>
> > Hel
mvn clean test scm:commit -Dmessage="I am great"
On 15 February 2013 12:51, Alberto Ivo wrote:
> Hello,
>
> Nowadays When I change the code, I manually run the unit test (suite) and
> then commit using Eclipse IDE.
> But I would like to do it via Maven. The code can be committed only after
> th
12 matches
Mail list logo
