Added it to my corporate super pom. No complaints there. But if I try
to run mvn install (mvn2) with the added profile I get an enforcer
error saying that the maven-site-plugin has no version specified. If
I remove the 3.0-beta-1-SNAPSHOT m-site-p from the maven-3 profile the
build works again.
Is this a bug in the enforcer plugin? when running
help:active-profiles I can see that the maven-3 profile is not active,
but the presence of the 3.0-beta-1-SNAPSHOT plugin seems to confuse
the enforcer plugin
[INFO] [INFO] [enforcer:enforce {execution: enforce}]
[INFO] [INFO] [enforcer:enforce {execution: enforce-plugin-versions}]
[INFO] [WARNING] Rule 0:
org.apache.maven.plugins.enforcer.RequirePluginVersions failed with
message:
[INFO] Some plugins are missing valid versions:(LATEST RELEASE
SNAPSHOT are not allowed )
[INFO] org.apache.maven.plugins:maven-site-plugin. The version
currently in use is 2.1
[INFO] Best Practice is to always define plugin versions!
[INFO] [INFO]
------------------------------------------------------------------------
[INFO] [ERROR] BUILD ERROR
Raphael
On Fri, Apr 23, 2010 at 12:04, Julien HENRY <henr...@yahoo.fr> wrote:
> Hi,
>
> This profile will only works in your projet pom (or better in your corporate
> super pom). Profiles in settings.xml are not allowed to have a <build>
> section.
>
> Regards,
>
> Julien
>
>
>
> ----- Message d'origine ----
>> De : Raphael Ackermann <raphael.ackerm...@gmail.com>
>> À : Maven Developers List <dev@maven.apache.org>
>> Envoyé le : Ven 23 avril 2010, 11 h 53 min 32 s
>> Objet : Re: [VOTE] Release Apache Maven 3.0-beta-1
>>
>> I copied the profile from the wiki website and added it to my
> settings.xml
>> but get following warnings on maven3 and error with
> maven2:
>
> maven
>> 3
> mvn install -DskipTests=true
> [WARNING]
> [WARNING] Some problems were
>> encountered while building the effective settings
> [WARNING] Unrecognised tag:
>> 'build' (position: START_TAG
>> seen
> ...</activation>\r\n\t\t\t<build>... @34:11) @
>> C:\Dokumente und
> Einstellungen\rackermann\.m2\settings.xml, line 34, column
>> 11
> [WARNING]
>
>
> c:\devel\maven\2.2\maven-2.2.1\bin\mvn
>> install
> Error reading settings.xml: Unrecognised tag: 'build'
>> (position:
> START_TAG seen ...</activation>\r\n\t\t\t<build>...
>> @34:11)
> Line: 34
> Column: 11
>
> any
>> ideas?
>
> On Fri, Apr 23, 2010 at 00:46, Hervé BOUTEMY <
>> ymailto="mailto:herve.bout...@free.fr";
>> href="mailto:herve.bout...@free.fr";>herve.bout...@free.fr> wrote:
>>
>> this can be done simply by adding a profile activated with ${basedir}
>> property:
>> I just added instruction at the end of Wiki page
>> [1]
>>
>> Regards,
>>
>> Hervé
>>
>> [1]
>> href="https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+and+site+plugin";
>> target=_blank
>> >https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+and+site+plugin
>>
>>
>> Le jeudi 22 avril 2010, Niall Pemberton a écrit :
>>> On Tue, Apr 20,
>> 2010 at 8:48 AM, Olivier Lamy <
>> href="mailto:ol...@apache.org";>ol...@apache.org> wrote:
>>> >
>> No.
>>> > It's 3.x prerequisite.
>>>
>>> It would be
>> good if there was some mechanism so that the site
>>> generation could
>> be made to work with either m2 or m3. Perhaps by
>>> activating
>> different profiles dependant on the maven version -
>>> something
>> like:
>>>
>>> <build>
>>>
>> <pluginManagement>
>>> <plugins>
>>>
>> <plugin>
>>>
>> <groupId>org.apache.maven.plugins</groupId>
>>>
>> <artifactId>maven-site-plugin</artifactId>
>>>
>> <version>${site.plugin.version}</version>
>>>
>> </plugin>
>>> </plugins>
>>>
>> </pluginManagement>
>>> </build>
>>>
>>>
>> <profiles>
>>> <profile>
>>>
>> <activation>
>>> <maven>2</maven>
>>>
>> </activation>
>>> <properties>
>>>
>> <site.plugin.version>2.0.1</site.plugin.version>
>>>
>> </properties>
>>> </profile>
>>>
>>>
>> <profile>
>>> <activation>
>>>
>> <maven>3</maven>
>>> </activation>
>>>
>> <properties>
>>>
>> <site.plugin.version>3.0-beta-1</site.plugin.version>
>>>
>> </properties>
>>> </profile>
>>>
>> </profiles>
>>>
>>> > 2010/4/20 Brett Porter <
>> ymailto="mailto:br...@apache.org";
>> href="mailto:br...@apache.org";>br...@apache.org>:
>>> >> On
>> 20/04/2010, at 5:10 PM, Olivier Lamy wrote:
>>> >>>
>> Hi,
>>> >>>
>>> >>> 2010/4/20 Hervé BOUTEMY
>> <
>> href="mailto:herve.bout...@free.fr";>herve.bout...@free.fr>:
>>>
>> >>>> what about releasing maven-site-plugin 3.0-beta-1?
>>>
>> >>>
>>> >>> Yup I can do that and start releasing all
>> needed stuff.
>>> >>>
>>> >>>> Olivier, is
>> there something critical missing?
>>> >>>
>>>
>> >>> No except some spare time :-)
>>> >>
>>>
>> >> Does that also work with Maven 2.x, or will we end up having two
>> strands
>>> >> of development on it?
>>>
>> >>
>>> >> - Brett
>>> >>
>>> >>
>> --
>>> >> Brett Porter
>>> >>
>> ymailto="mailto:br...@apache.org";
>> href="mailto:br...@apache.org";>br...@apache.org
>>> >>
>> href="http://brettporter.wordpress.com/"; target=_blank
>> >http://brettporter.wordpress.com/
>>> >>
>>>
>> >>
>>> >>
>>> >>
>>>
>> >>
>>> >>
>> ---------------------------------------------------------------------
>>>
>> >> To unsubscribe, e-mail:
>> ymailto="mailto:dev-unsubscr...@maven.apache.org";
>> href="mailto:dev-unsubscr...@maven.apache.org";>dev-unsubscr...@maven.apache.org
>>>
>> >> For additional commands, e-mail:
>> ymailto="mailto:dev-h...@maven.apache.org";
>> href="mailto:dev-h...@maven.apache.org";>dev-h...@maven.apache.org
>>>
>> >
>>> > --
>>> > Olivier
>>> >
>> href="http://twitter.com/olamy"; target=_blank
>> >http://twitter.com/olamy
>>> >
>> href="http://fr.linkedin.com/in/olamy"; target=_blank
>> >http://fr.linkedin.com/in/olamy
>>> >
>> href="http://www.viadeo.com/fr/profile/olivier.lamy7"; target=_blank
>> >http://www.viadeo.com/fr/profile/olivier.lamy7
>>> >
>>>
>> >
>> ---------------------------------------------------------------------
>>>
>> > To unsubscribe, e-mail:
>> ymailto="mailto:dev-unsubscr...@maven.apache.org";
>> href="mailto:dev-unsubscr...@maven.apache.org";>dev-unsubscr...@maven.apache.org
>>>
>> > For additional commands, e-mail:
>> ymailto="mailto:dev-h...@maven.apache.org";
>> href="mailto:dev-h...@maven.apache.org";>dev-h...@maven.apache.org
>>>
>>>
>> ---------------------------------------------------------------------
>>>
>> To unsubscribe, e-mail:
>> href="mailto:dev-unsubscr...@maven.apache.org";>dev-unsubscr...@maven.apache.org
>>>
>> For additional commands, e-mail:
>> href="mailto:dev-h...@maven.apache.org";>dev-h...@maven.apache.org
>>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To
>> unsubscribe, e-mail:
>> href="mailto:dev-unsubscr...@maven.apache.org";>dev-unsubscr...@maven.apache.org
>>
>> For additional commands, e-mail:
>> href="mailto:dev-h...@maven.apache.org";>dev-h...@maven.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To
>> unsubscribe, e-mail:
>> href="mailto:dev-unsubscr...@maven.apache.org";>dev-unsubscr...@maven.apache.org
> For
>> additional commands, e-mail:
>> href="mailto:dev-h...@maven.apache.org";>dev-h...@maven.apache.org
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
