On Mon, Feb 15, 2010 at 6:14 AM, Igor Fedorenko wrote:
> I am not 100% sure, but I think this may break MavenMetadataCache, which
> caches Artifact instances and assumes they do not change. In m2e, for
> example, we do not flash the cache before each build, only when project
> pom.xml changes. So
I am not 100% sure, but I think this may break MavenMetadataCache, which
caches Artifact instances and assumes they do not change. In m2e, for
example, we do not flash the cache before each build, only when project
pom.xml changes. So if one of mojos changes cached Artifact instance,
next build ma
I can't see any reason they'd need to be separate, though my inclination would
be to move away from sharing that information via the 'file' property and
resolving it from the correct place when needed. I'm not up to date on how
trunk is handling these objects though.
On 14/02/2010, at 7:34 AM,
On 15/02/2010, at 4:22 AM, Benjamin Bentmann wrote:
> Brett Porter wrote:
>
>> The staging repo is available here:
>> https://repository.apache.org/content/repositories/maven-staging-002/
>
> +1
>
>> The distribution files are here:
>> http://people.apache.org/builds/maven/2.0.11/
>
> Somethi
+1
-Lukas
Brett Porter wrote:
Hi,
This is a vote to release Maven 2.0.11, as we discussed late last year. It has
been available for testing for several months with a few positive reports and
no issues raised. It passes all of the integration tests for that version.
It includes 36 issues:
Brett Porter wrote:
The staging repo is available here:
https://repository.apache.org/content/repositories/maven-staging-002/
+1
The distribution files are here:
http://people.apache.org/builds/maven/2.0.11/
Something is wrong with
http://people.apache.org/builds/maven/2.0.11/binaries/apac
Hi,
The vote has passed with the following result:
+1 (binding): Benjamin Bentmann, Jason van Zyl, Olivier Lamy, Brian Fox
+1 (non-binding): Tony Chemit
I will promote the artifacts to the central repository and continue with
the release.
Benjamin
-
