[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cross-project-issues-dev] New eclipse-signing-maven-plugin ready
|
for organizational parent poms we often use that single version
notation, see the ASF top level pom
cheers,
jesse
--
jesse mcconnell
jesse.mcconnell@xxxxxxxxx
On Tue, Aug 9, 2011 at 17:44, Matthias Sohn
<matthias.sohn@xxxxxxxxxxxxxx> wrote:
> 2011/8/9 David Carver <d_a_carver@xxxxxxxxx>
>>
>> Several fixes have been deployed for the maven signing plugin. Note that
>> the name of this plugin has changed. It is now:
>> eclipse-signing-maven-plugin. This better follows the maven standard for
>> naming of plugins used during the builds. The following group information
>> should be used:
>>
>> <groupId>org.eclipse.dash.maven</groupId>
>> <artifactId>eclipse-signing-maven-plugin</artifactId>
>> <version>1.0.2</version>
>>
>> Also you will need to make sure you have the following pluginRepository
>> available in your pom.
>>
>> http://maven.eclipse.org/nexus/content/groups/public/
>>
>> Along with this is a restructured and renumbeed eclipse-parent pom. The
>> new version information for the eclipse-parent pom is:
>>
>> <groupId>org.eclipse</groupId>
>> <artifactId>eclipse-parent</artifactId>
>> <version>2</version>
>
> what's the reason to use a non-standard 1-digit-only version number, I would
> expect 2.0.0 here ...
>
> --
> Matthias
>
> _______________________________________________
> cross-project-issues-dev mailing list
> cross-project-issues-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
>
