Hi,
I have started on it (branch created [1]) and I have an issue building
with the current trunk.
The log says :
org.apache.maven.project.ProjectBuildingException: Failed to build
project for
/local/olamy/.m2/repository/org/apache/maven/doxia/doxia-site-renderer/1.0/doxia-site-renderer-1.0.pom
for project [unknown] at
/local/olamy/.m2/repository/org/apache/maven/doxia/doxia-site-renderer/1.0/doxia-site-renderer-1.0.pom
at
org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:118)
at
org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:179)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:51)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:79)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:67)
at
org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.getProjects(ProcessRemoteResourcesMojo.java:505)
at
org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.configureVelocityContext(ProcessRemoteResourcesMojo.java:665)
.....
Caused by: org.apache.maven.model.ModelBuildingException: 1 problem
was encountered during construction of the effective model:
o Invalid repository apache.snapshots in POM org.apache:apache:4:
org.apache.maven.model.Repository cannot be cast to
org.apache.maven.artifact.repository.ArtifactRepository
at
org.apache.maven.model.DefaultModelBuilder.build(DefaultModelBuilder.java:191)
at
org.apache.maven.model.DefaultModelBuilder.build(DefaultModelBuilder.java:106)
at
org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:113)
... 21 more
?
--
Olivier
[1]
https://svn.apache.org/repos/asf/maven/plugins/branches/maven-site-plugin-3.x/
2009/6/16 Jason van Zyl <[email protected]>:
>
> On 16-Jun-09, at 12:42 PM, Brett Porter wrote:
>
>>
>> On 14/06/2009, at 3:53 PM, Jason van Zyl wrote:
>>
>>> What we can do internally for people who want to use their POMs "as-is"
>>> with 3.x is to provide some internal mapping from the POM to the
>>> configuration element of the new site-plugin. When 3.0 is release no one
>>> should have to change their POMs i.e flip all the configuration into the
>>> maven-site-plugin configuration but they will have to use the new version of
>>> the site-plugin.
>>
>> What about using the site lifecycle (which could be moved to the site
>> plugin if they can be loaded from there easily) so that the reports become
>> normal plugin goals? The advantage is that it works with Maven 2.x today.
>>
>
> I'm not sure what you're talking about, it's going to work exactly as it
> does in 2.x.
>
>> - Brett
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder, Apache Maven
> http://twitter.com/jvanzyl
> http://twitter.com/SonatypeNexus
> http://twitter.com/SonatypeM2E
> ----------------------------------------------------------
>
> We all have problems. How we deal with them is a measure of our worth.
>
> -- Unknown
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
