With subversion you don't know the version of what you are building if you have
made local modifications until you merge and checkin.
The following works for me without hitting the repo (but it does run the svn
command)
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>buildnumber-maven-plugin</artifactId>
<version>1.0-beta-1</version>
<executions>
<execution>
<phase>validate</phase>
<goals>
<goal>create</goal>
</goals>
</execution>
</executions>
<configuration>
<doCheck>false</doCheck>
<doUpdate>false</doUpdate>
</configuration>
</plugin>
-----Original Message-----
From: Ron Wheeler [mailto:[email protected]]
Sent: 20 August 2010 14:20
To: [email protected]
Subject: Re: Getting a useful Manifest
Tried to use it but could never get the SCM configuration to work.
I use Eclipse to access svn and I am not sure I want Maven doing
anything there in any event.
I want the version number of what I am building not the build of what is
currently on the subversion repo.
I am not sure what the plug-in is going to do with info from the repo. I
did turn of DoUpdate and DoCheck but it still wanted to go to the repo
for something.
The SCM stuff seems a bit hard to understand. I tried many variations of
what Eclipse is using but never found a configuration that Maven liked.
http://maven.apache.org/scm/maven-scm-plugin/usage.html seemed the most
useful page along with
http://maven.apache.org/scm/subversion.html
but no joy.
I may come back to this later when I have more time for head banging.
Thanks
Ron
On 20/08/2010 8:25 AM, Nord, James wrote:
> Take a look at the BuildNumber[1] plugin
>
> The date will be the timestamp of the actual file - do you need to get this
> or can you use the file time?
>
> /James
>
> [1] http://mojo.codehaus.org/buildnumber-maven-plugin/
>
> -----Original Message-----
> From: Ron Wheeler [mailto:[email protected]]
> Sent: 20 August 2010 13:07
> To: [email protected]
> Subject: Re: Getting a useful Manifest
>
> PluginManagement works well.
> It took a lot of trial and error to get a working split between the
> information in the parent's plug-in management and the module's plug-in
> description.
>
> There are 2 things that I would like to add.
> The first is the date that the manifest was made.
> The second is the SCM (subversion in my case) version number.
>
> Any ideas about how to get those into the Manifest?
>
> This is the current setup that works
> I put the following in the Parent POM
> <pluginManagement>
> <plugins>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-assembly-plugin</artifactId>
> <version>2.2-beta-5</version>
> <executions>
> <execution>
> <phase>package</phase>
> <goals>
> <goal>single</goal>
> </goals>
>
> <configuration>
> <archive>
> <manifest>
> <addDefaultImplementationEntries>true</addDefaultImplementationEntries>
> <addDefaultSpecificationEntries>true</addDefaultSpecificationEntries>
> </manifest>
> </archive>
> <descriptorRefs>
> <descriptorRef>
> jar-with-dependencies
> </descriptorRef>
> </descriptorRefs>
>
> </configuration>
> </execution>
> </executions>
> </plugin>
>
> </plugins>
> </pluginManagement>
>
> and the following in the module
> <build>
> <plugins>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-assembly-plugin</artifactId>
> </plugin>
> </plugins>
> </build>
>
> This produced a nice MANIFEST.MF with the following:
> Manifest-Version: 1.0
> Archiver-Version: Plexus Archiver
> Created-By: Apache Maven
> Built-By: rwheeler
> Build-Jdk: 1.6.0_17
> Specification-Title: Spring
> Specification-Version: 1.9.1
> Specification-Vendor: Artifact Software
> Implementation-Title: Spring
> Implementation-Version: 1.9.1
> Implementation-Vendor-Id: com.artifact_software.lms
> Implementation-Vendor: Artifact Software
>
>
>
>
>
> On 19/08/2010 4:08 PM, Ron Wheeler wrote:
>> The instructions worked beautifully.
>>
>> Now I have a lot of POMS to modify unless I can add something to my
>> parent pom that will modify the plug-ins in my module poms.
>> In my modules I have this:
>> <plugin>
>> <artifactId>maven-assembly-plugin</artifactId>
>> <version>2.2-beta-2</version>
>> <executions>
>> <execution>
>> <id>create-Jasper-jar</id>
>> <phase>package</phase>
>> <goals>
>> <goal>single</goal>
>> </goals>
>> <configuration>
>> <descriptorRefs>
>> <descriptorRef>
>> jar-with-dependencies
>> </descriptorRef>
>> </descriptorRefs>
>> </configuration>
>> </execution>
>> </executions>
>> </plugin>
>> I would like it to include :
>> <archive>
>> <manifest>
>> <addDefaultImplementationEntries>true</addDefaultImplementationEntries>
>> <addDefaultSpecificationEntries>true</addDefaultSpecificationEntries>
>> </manifest>
>> </archive>
>> to effectively become this:
>> <artifactId>maven-assembly-plugin</artifactId>
>> <version>2.2-beta-2</version>
>> <executions>
>> <execution>
>> <phase>package</phase>
>> <goals>
>> <goal>single</goal>
>> </goals>
>> <configuration>
>> <archive>
>> <manifest>
>> <addDefaultImplementationEntries>true</addDefaultImplementationEntries>
>> <addDefaultSpecificationEntries>true</addDefaultSpecificationEntries>
>> </manifest>
>> </archive>
>> <descriptorRefs>
>> <descriptorRef>
>> jar-with-dependencies
>> </descriptorRef>
>> </descriptorRefs>
>> </configuration>
>> </execution>
>> </executions>
>> </plugin>
>>
>> Any way to get the parent pom to supply a bit of the plug-in
>> configuration?
>>
>>
>> On 19/08/2010 11:43 AM, Anders Hammar wrote:
>>> But you'll file a ticket to get this fixed, right?
>>>
>>> /Anders (mobile)
>>>
>>> Den 2010 8 19 17:36 skrev "Ron Wheeler"<[email protected]>:
>>>> http://maven.apache.org/shared/maven-archiver/examples/manifest.html
>>>> Has a better description of how the mapping is done.
>>>>
>>>> Not sure why
>>>> http://maven.apache.org/guides/mini/guide-manifest.html
>>>> does not provide a link.
>>>>
>>
>> ---------------------------------------------------------------------
>> 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]
>
>
>
> **************************************************************************************
> This message is confidential and intended only for the addressee. If you have
> received this message in error, please immediately notify the
> [email protected] and delete it from your system as well as any copies. The
> content of e-mails as well as traffic data may be monitored by NDS for
> employment and security purposes. To protect the environment please do not
> print this e-mail unless necessary.
>
> NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18
> 4EX, United Kingdom. A company registered in England and Wales. Registered
> no. 3080780. VAT no. GB 603 8808 40-00
> **************************************************************************************
>
> ---------------------------------------------------------------------
> 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]
**************************************************************************************
This message is confidential and intended only for the addressee. If you have
received this message in error, please immediately notify the
[email protected] and delete it from your system as well as any copies. The
content of e-mails as well as traffic data may be monitored by NDS for
employment and security purposes. To protect the environment please do not
print this e-mail unless necessary.
NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX,
United Kingdom. A company registered in England and Wales. Registered no.
3080780. VAT no. GB 603 8808 40-00
**************************************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
