Hi Andrei,
the benefits of SCM-1.8 and SCM-1.8.1 are less then the pains, especially
for GIT users, so with MRELEASE-830 I've reverted that dependency back to
1.7 until we've fixed those issues.
Robert
Op Wed, 27 Mar 2013 23:08:11 +0100 schreef Andrei Pozolotin
:
Robert
1) great, tha
Robert
1) great, thank you!
2) does it mean 2.4.1 does not blow up with this:
http://jira.codehaus.org/browse/SCM-709
?
Andrei
Original Message
Subject: [ANN] Maven Release Plugin 2.4.1 Released
From: Robert Scholte
To: annou...@maven.apache.org, us...@maven.apache.org
Cc: de
*Robert:*
I actually relaxed "no module nesting" requirement. just not tested
well yet.
Thank you,
Andrei
Original Message
Subject: Re: Multi-project releases
From: Robert Scholte
To: Maven Developers List
Date: Wed 27 Mar 2013 03:59:42 PM CDT
> @Andrei,
Yes I need to grök the fake SCM that people use for integration tests
On Wednesday, 27 March 2013, Robert Scholte wrote:
> @Andrei,
>
> I've taken a look at your project and I think I understand what you're
> trying to do with the maven-cascade-release-plugin. It requires a
> non-chained project
@Andrei,
I've taken a look at your project and I think I understand what you're
trying to do with the maven-cascade-release-plugin. It requires a
non-chained project structure, that's not an option for us.
If these local-aggregators can be under source control and if they can be
layered we
The Apache Maven team is pleased to announce the release of the Maven
Release Plugin, version 2.4.1
This plugin is used to release a project with Maven, saving a lot of
repetitive, manual work. Releasing a project is made in two steps: prepare
and perform.
http://maven.apache.org/plugins/
Cool.
On Mar 27, 2013, at 3:10 AM, Hervé BOUTEMY wrote:
> I just fixed
> http://jira.codehaus.org/browse/MSITE-683 /
> http://jira.codehaus.org/browse/MSHARED-280
>
> Any tests from others are welcome
>
> Regards,
>
> Hervé
>
> Le mardi 19 mars 2013 01:49:08 Hervé BOUTEMY a écrit :
>> I j
2013/3/27 Manuel Blechschmidt :
> Hi Hervé,
> thanks a lot for responding to my email.
>
> The ticket in JIRA already contains a test project that reproduces the bug, a
> test case that reproduces the bug and a patch that is fixing the but.
>
> If there is more that I should do feel free to add th
Hi Hervé,
thanks a lot for responding to my email.
The ticket in JIRA already contains a test project that reproduces the bug, a
test case that reproduces the bug and a patch that is fixing the but.
If there is more that I should do feel free to add the necessary comments onto
the JIRA ticket.
Manuel,
I'll try to find time to work with you: we'll cut a new Doxia release soon, so
any good fixes will be immediately useful
Regards,
Hervé
Le lundi 18 mars 2013 18:37:27 Manuel Blechschmidt a écrit :
> I am interested in the following areas:
> DOXIA-CORE-1.3
>
> I observed that nobody is
Future Maven 3.1-alpha-1 will require a new m-site-p version to accomodate
Aether switch (yes, as expected, the code to execute report plugins is highly
coupled to core)
I have some issues I want to fix in m-site-p before the release, and I want a
new Doxia release to fix Markdown support (DOXI
I just fixed
http://jira.codehaus.org/browse/MSITE-683 /
http://jira.codehaus.org/browse/MSHARED-280
Any tests from others are welcome
Regards,
Hervé
Le mardi 19 mars 2013 01:49:08 Hervé BOUTEMY a écrit :
> I just had a look at the failures: they are caused by
> DefaultMavenReportExecutor usi
12 matches
Mail list logo
