On Mar 30, 2013, at 10:00 AM, Hervé BOUTEMY wrote:
> yes, the ITs will be modified after the m-site-p release, ie just use
> m-site-p
> 3.3
>
Cool. Just wanted to make sure.
> I didn't have time for the moment to try m-dependency-p:tree and work on a
> fix,
> but that will be the same: the
yes, the ITs will be modified after the m-site-p release, ie just use m-site-p
3.3
I didn't have time for the moment to try m-dependency-p:tree and work on a fix,
but that will be the same: the IT will just need to use the next version,
which will be improved to use the new Maven core API
no p
Hervé,
I don't see any adjustment in the ITs for the site/dependency plugin. I'm going
to cut the release today if I can so are you fine with the release? If you're
fine I'm fine because I haven't tried the site or dependency plugin.
On Mar 27, 2013, at 3:10 AM, Hervé BOUTEMY wrote:
> I just
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
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
fixed, thanks for the report
Regards,
Hervé
Le mardi 19 mars 2013 00:59:03 Stuart McCulloch a écrit :
> BTW, the following files appear to contain merge conflicts:
>
> maven-embedder/src/site/apt/logging.apt
> maven-plugin-api/src/site/apt/index.apt
>
> On 19 Mar 2013, at 00:53, Ja
BTW, the following files appear to contain merge conflicts:
maven-embedder/src/site/apt/logging.apt
maven-plugin-api/src/site/apt/index.apt
On 19 Mar 2013, at 00:53, Jason van Zyl wrote:
> On Mar 18, 2013, at 5:49 PM, Hervé BOUTEMY wrote:
>
>> I just had a look at the failures:
On Mar 18, 2013, at 5:49 PM, Hervé BOUTEMY wrote:
> I just had a look at the failures: they are caused by
> DefaultMavenReportExecutor using Sonatype Aether ExclusionsDependencyFilter
> [1] for MavenPluginManager.setupPluginRealm(...) API call [2] which is
> affected
> by switching to Eclips
I just had a look at the failures: they are caused by
DefaultMavenReportExecutor using Sonatype Aether ExclusionsDependencyFilter
[1] for MavenPluginManager.setupPluginRealm(...) API call [2] which is affected
by switching to Eclipse Aether
We will need some tweaks in maven-reporting-exec to d
In the ITs I have changed the ranges to accommodate these ITs not running with
Eclipse Aether:
MavenITmng3743ForkWithPluginManagementTest: Site plugin
MavenITmng3703ExecutionProjectWithRelativePathsTest: Site plugin
MavenITmng3684BuildPluginParameterTest: Site plugin
MavenITmng3372DirectInvocatio
Hervé, Olivier,
There are two failures due to the SLF4J Simple changes made which only affect
the embedded mode but it's really nice having those clean because they are so
much faster. Hervé, maybe these worked for you locally and you still have some
more work to do? This I can take a looked in
11 matches
Mail list logo