You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Ron Wheeler <rw...@artifact-software.com> on 2010/08/19 17:12:35 UTC
Getting a useful Manifest
http://maven.apache.org/guides/mini/guide-manifest.html
shows an example of a nice MANIFEST.MF that includes a version number.
We do not get a version number in our manifests.
What triggers the addition of the these entries.
Extension-Name: my-app
Specification-Vendor: MyCompany Inc
Implementation-Vendor: MyCompany Inc
Implementation-Title: my-app
Implementation-Version: 1.0-SNAPSHOT
These seem to have names that are foreign to my usage of Maven.
Is there a better reference about how these map to maven properties.
Extension-Name: my-app
Specification-Vendor:
Implementation-Vendor:
Implementation-Title:
Implementation-Version:
Ron
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Getting a useful Manifest
Posted by Anders Hammar <an...@hammar.net>.
Yes, that's the way to go.
What I recommend is that you have a so-called corporate pom, which is
basically a common parent pom for all projects within a company (all Maven
projects don't have to inherit directly, indirectly is just fine). In that
pom you have a pluginManagement section where you put this kind of
configuration that you want to be used all over the company.
/Anders
On Thu, Aug 19, 2010 at 22:45, Ron Wheeler
<rw...@artifact-software.com>wrote:
> It looks like PluginManagement in the parent will do what I want.
> Let you know.
>
> Ron
>
>
>
> 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"<rw...@artifact-software.com>:
>>>
>>>> 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: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: Getting a useful Manifest
Posted by Ron Wheeler <rw...@artifact-software.com>.
It looks like PluginManagement in the parent will do what I want.
Let you know.
Ron
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"<rw...@artifact-software.com>:
>>> 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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Getting a useful Manifest
Posted by Ron Wheeler <rw...@artifact-software.com>.
I am not sure that I want to check in everything that I build since we
do a lot of local testing.
Once I figure out what Maven wants for an SCM configuration that is
different from what Eclipse uses, I will try your configuration.
It looks pretty close to what I found but it is nice to have an example
that you know works.
Thanks
Ron
On 20/08/2010 9:41 AM, Nord, James wrote:
> 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:rwheeler@artifact-software.com]
> Sent: 20 August 2010 14:20
> To: users@maven.apache.org
> 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:rwheeler@artifact-software.com]
>> Sent: 20 August 2010 13:07
>> To: users@maven.apache.org
>> 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"<rw...@artifact-software.com>:
>>>>> 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: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>>
>> **************************************************************************************
>> This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmaster@nds.com 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: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>
> **************************************************************************************
> This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmaster@nds.com 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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Getting a useful Manifest
Posted by "Nord, James" <JN...@nds.com>.
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:rwheeler@artifact-software.com]
Sent: 20 August 2010 14:20
To: users@maven.apache.org
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:rwheeler@artifact-software.com]
> Sent: 20 August 2010 13:07
> To: users@maven.apache.org
> 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"<rw...@artifact-software.com>:
>>>> 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: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>
> **************************************************************************************
> This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmaster@nds.com 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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
**************************************************************************************
This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmaster@nds.com 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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Getting a useful Manifest
Posted by Ron Wheeler <rw...@artifact-software.com>.
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:rwheeler@artifact-software.com]
> Sent: 20 August 2010 13:07
> To: users@maven.apache.org
> 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"<rw...@artifact-software.com>:
>>>> 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: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>
> **************************************************************************************
> This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmaster@nds.com 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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Getting a useful Manifest
Posted by "Nord, James" <JN...@nds.com>.
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:rwheeler@artifact-software.com]
Sent: 20 August 2010 13:07
To: users@maven.apache.org
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"<rw...@artifact-software.com>:
>>> 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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
**************************************************************************************
This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmaster@nds.com 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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Getting a useful Manifest
Posted by Ron Wheeler <rw...@artifact-software.com>.
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"<rw...@artifact-software.com>:
>>> 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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Getting a useful Manifest
Posted by Dennis Lundberg <de...@apache.org>.
On 2010-08-20 16:57, Ron Wheeler wrote:
> On 20/08/2010 10:30 AM, Justin Edelson wrote:
>> I just meant that your blog entry is titled "How to get a consistent
>> MANIFEST.MF for your webapps" but it actually describes how to get a
>> consistent manifest for uberjars and not war files.
> True enough I will fix the title and if I can the analogous process to
> work for WAR files I will add that section or create a new blog.
Fortunately, the configuration syntax for manifest is the same for the
WAR plugin as it is for the JAR plugin. Just add the same configuration
for the WAR plugin.
>
> Ron
>> On 8/20/10 10:21 AM, Ron Wheeler wrote:
>>> You are right but I want to tag everything including the wars.
>>> It is the wars that are actually the bigger problem since the rest of
>>> the build/deploy process is under Eclipse/Maven/Subversion control so we
>>> can track things pretty well.
>>>
>>> The starting point for any issue involving a run-time problem that might
>>> be caused by a bad deployment is to find out what exactly is deployed.
>>>
>>> Ron
>>>
>>> On 20/08/2010 9:17 AM, Justin Edelson wrote:
>>>> What does this have to do with "webapps"? It seems to be about
>>>> uberjars...
>>>>
>>>> I usually use
>>>>
>>>> unzip -p<jarname> META-INF/MANIFEST.MF
>>>>
>>>> to output the manifest to the console. Combined with find, this should
>>>> do what you're looking for.
>>>>
>>>>
>>>> On 8/20/10 8:29 AM, Ron Wheeler wrote:
>>>>> I wrote this up in my blog
>>>>>
>>>>> http://blog.artifact-software.com/tech/?p=47
>>>>>
>>>>> Does anyone have a script that will visit all the webapps and
>>>>> report on
>>>>> what it finds in the MANIFEST.MF files?
>>>>>
>>>>> Ron
>>>>>
>>>>>
>>>>> 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"<rw...@artifact-software.com>:
>>>>>>>> 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: users-unsubscribe@maven.apache.org
>>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>>
>>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Getting a useful Manifest
Posted by Ron Wheeler <rw...@artifact-software.com>.
On 20/08/2010 10:30 AM, Justin Edelson wrote:
> I just meant that your blog entry is titled "How to get a consistent
> MANIFEST.MF for your webapps" but it actually describes how to get a
> consistent manifest for uberjars and not war files.
True enough I will fix the title and if I can the analogous process to
work for WAR files I will add that section or create a new blog.
Ron
> On 8/20/10 10:21 AM, Ron Wheeler wrote:
>> You are right but I want to tag everything including the wars.
>> It is the wars that are actually the bigger problem since the rest of
>> the build/deploy process is under Eclipse/Maven/Subversion control so we
>> can track things pretty well.
>>
>> The starting point for any issue involving a run-time problem that might
>> be caused by a bad deployment is to find out what exactly is deployed.
>>
>> Ron
>>
>> On 20/08/2010 9:17 AM, Justin Edelson wrote:
>>> What does this have to do with "webapps"? It seems to be about
>>> uberjars...
>>>
>>> I usually use
>>>
>>> unzip -p<jarname> META-INF/MANIFEST.MF
>>>
>>> to output the manifest to the console. Combined with find, this should
>>> do what you're looking for.
>>>
>>>
>>> On 8/20/10 8:29 AM, Ron Wheeler wrote:
>>>> I wrote this up in my blog
>>>>
>>>> http://blog.artifact-software.com/tech/?p=47
>>>>
>>>> Does anyone have a script that will visit all the webapps and report on
>>>> what it finds in the MANIFEST.MF files?
>>>>
>>>> Ron
>>>>
>>>>
>>>> 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"<rw...@artifact-software.com>:
>>>>>>> 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: users-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>
>>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Getting a useful Manifest
Posted by Justin Edelson <ju...@gmail.com>.
I just meant that your blog entry is titled "How to get a consistent
MANIFEST.MF for your webapps" but it actually describes how to get a
consistent manifest for uberjars and not war files.
On 8/20/10 10:21 AM, Ron Wheeler wrote:
> You are right but I want to tag everything including the wars.
> It is the wars that are actually the bigger problem since the rest of
> the build/deploy process is under Eclipse/Maven/Subversion control so we
> can track things pretty well.
>
> The starting point for any issue involving a run-time problem that might
> be caused by a bad deployment is to find out what exactly is deployed.
>
> Ron
>
> On 20/08/2010 9:17 AM, Justin Edelson wrote:
>> What does this have to do with "webapps"? It seems to be about
>> uberjars...
>>
>> I usually use
>>
>> unzip -p<jarname> META-INF/MANIFEST.MF
>>
>> to output the manifest to the console. Combined with find, this should
>> do what you're looking for.
>>
>>
>> On 8/20/10 8:29 AM, Ron Wheeler wrote:
>>> I wrote this up in my blog
>>>
>>> http://blog.artifact-software.com/tech/?p=47
>>>
>>> Does anyone have a script that will visit all the webapps and report on
>>> what it finds in the MANIFEST.MF files?
>>>
>>> Ron
>>>
>>>
>>> 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"<rw...@artifact-software.com>:
>>>>>> 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: users-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Getting a useful Manifest
Posted by Ron Wheeler <rw...@artifact-software.com>.
Thanks
I explicitly set the version and have got what I need.
May just have been more careful.
Ron
On 20/08/2010 11:56 AM, Dennis Lundberg wrote:
> When testing issues before the 2.1 release of the WAR plugin I can
> across one issue where the configuration wouldn't "stick" if it was in
> the parent's build/pluginManagement section. When the configuration was
> moved to the child module's build/plugins section it worked. However I
> couldn't understand why.
>
> There's an issue for this in JIRA:
> http://jira.codehaus.org/browse/MWAR-149
>
> On 2010-08-20 16:53, Ron Wheeler wrote:
>> Found a new oddity that perhaps someone can explain.
>> I am trying to build a WAR file using maven-war-plugin
>> If I put the proper configuration in the module's POM I get the Manifest
>> that I want.
>>
>> If I just put it in the parent in the plug-in section without any
>> mention of the plug-in at all in the module I do get a WAR file but I do
>> not get the Manifest that I want.
>>
>> If I put the plugin configuration in the parent's dependencyManagement
>> section and put a reference just to the plug-in in the module, I get the
>> WAR file without the Manifest that I want.
>>
>> This is the whole configuration section that gives me the Manifest.
>>
>> <configuration>
>> <warSourceDirectory>WebContent</warSourceDirectory>
>> <archive>
>> <manifest>
>> <addDefaultImplementationEntries>true</addDefaultImplementationEntries>
>> <addDefaultSpecificationEntries>true</addDefaultSpecificationEntries>
>> </manifest>
>> </archive>
>> </configuration>
>>
>> It appears that Maven is bypassing the plug-in unless it is explicit in
>> the module POM.
>>
>> Is this right or am I missing something to get maven-war-plugin to be
>> configured in the parent POM?
>>
>> Ron
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Getting a useful Manifest
Posted by Dennis Lundberg <de...@apache.org>.
When testing issues before the 2.1 release of the WAR plugin I can
across one issue where the configuration wouldn't "stick" if it was in
the parent's build/pluginManagement section. When the configuration was
moved to the child module's build/plugins section it worked. However I
couldn't understand why.
There's an issue for this in JIRA:
http://jira.codehaus.org/browse/MWAR-149
On 2010-08-20 16:53, Ron Wheeler wrote:
> Found a new oddity that perhaps someone can explain.
> I am trying to build a WAR file using maven-war-plugin
> If I put the proper configuration in the module's POM I get the Manifest
> that I want.
>
> If I just put it in the parent in the plug-in section without any
> mention of the plug-in at all in the module I do get a WAR file but I do
> not get the Manifest that I want.
>
> If I put the plugin configuration in the parent's dependencyManagement
> section and put a reference just to the plug-in in the module, I get the
> WAR file without the Manifest that I want.
>
> This is the whole configuration section that gives me the Manifest.
>
> <configuration>
> <warSourceDirectory>WebContent</warSourceDirectory>
> <archive>
> <manifest>
> <addDefaultImplementationEntries>true</addDefaultImplementationEntries>
> <addDefaultSpecificationEntries>true</addDefaultSpecificationEntries>
> </manifest>
> </archive>
> </configuration>
>
> It appears that Maven is bypassing the plug-in unless it is explicit in
> the module POM.
>
> Is this right or am I missing something to get maven-war-plugin to be
> configured in the parent POM?
>
> Ron
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Getting a useful Manifest
Posted by Ron Wheeler <rw...@artifact-software.com>.
Found a new oddity that perhaps someone can explain.
I am trying to build a WAR file using maven-war-plugin
If I put the proper configuration in the module's POM I get the Manifest
that I want.
If I just put it in the parent in the plug-in section without any
mention of the plug-in at all in the module I do get a WAR file but I do
not get the Manifest that I want.
If I put the plugin configuration in the parent's dependencyManagement
section and put a reference just to the plug-in in the module, I get the
WAR file without the Manifest that I want.
This is the whole configuration section that gives me the Manifest.
<configuration>
<warSourceDirectory>WebContent</warSourceDirectory>
<archive>
<manifest>
<addDefaultImplementationEntries>true</addDefaultImplementationEntries>
<addDefaultSpecificationEntries>true</addDefaultSpecificationEntries>
</manifest>
</archive>
</configuration>
It appears that Maven is bypassing the plug-in unless it is explicit in
the module POM.
Is this right or am I missing something to get maven-war-plugin to be
configured in the parent POM?
Ron
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Getting a useful Manifest
Posted by Ron Wheeler <rw...@artifact-software.com>.
You are right but I want to tag everything including the wars.
It is the wars that are actually the bigger problem since the rest of
the build/deploy process is under Eclipse/Maven/Subversion control so we
can track things pretty well.
The starting point for any issue involving a run-time problem that might
be caused by a bad deployment is to find out what exactly is deployed.
Ron
On 20/08/2010 9:17 AM, Justin Edelson wrote:
> What does this have to do with "webapps"? It seems to be about uberjars...
>
> I usually use
>
> unzip -p<jarname> META-INF/MANIFEST.MF
>
> to output the manifest to the console. Combined with find, this should
> do what you're looking for.
>
>
> On 8/20/10 8:29 AM, Ron Wheeler wrote:
>> I wrote this up in my blog
>>
>> http://blog.artifact-software.com/tech/?p=47
>>
>> Does anyone have a script that will visit all the webapps and report on
>> what it finds in the MANIFEST.MF files?
>>
>> Ron
>>
>>
>> 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"<rw...@artifact-software.com>:
>>>>> 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: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Getting a useful Manifest
Posted by Justin Edelson <ju...@gmail.com>.
What does this have to do with "webapps"? It seems to be about uberjars...
I usually use
unzip -p <jarname> META-INF/MANIFEST.MF
to output the manifest to the console. Combined with find, this should
do what you're looking for.
On 8/20/10 8:29 AM, Ron Wheeler wrote:
> I wrote this up in my blog
>
> http://blog.artifact-software.com/tech/?p=47
>
> Does anyone have a script that will visit all the webapps and report on
> what it finds in the MANIFEST.MF files?
>
> Ron
>
>
> 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"<rw...@artifact-software.com>:
>>>> 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: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Getting a useful Manifest
Posted by Ron Wheeler <rw...@artifact-software.com>.
I wrote this up in my blog
http://blog.artifact-software.com/tech/?p=47
Does anyone have a script that will visit all the webapps and report on
what it finds in the MANIFEST.MF files?
Ron
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"<rw...@artifact-software.com>:
>>> 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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Getting a useful Manifest
Posted by Ron Wheeler <rw...@artifact-software.com>.
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"<rw...@artifact-software.com>:
>> 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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Getting a useful Manifest
Posted by Ron Wheeler <rw...@artifact-software.com>.
If you think that this is the best reference and solution, I would be
delighted to help out in such a non-demanding role.
Ron
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"<rw...@artifact-software.com>:
>> 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.
>>
>>
>>
>> On 19/08/2010 11:12 AM, Ron Wheeler wrote:
>>> http://maven.apache.org/guides/mini/guide-manifest.html
>>> shows an example of a nice MANIFEST.MF that includes a version number.
>>>
>>> We do not get a version number in our manifests.
>>> What triggers the addition of the these entries.
>>>
>>> Extension-Name: my-app
>>> Specification-Vendor: MyCompany Inc
>>> Implementation-Vendor: MyCompany Inc
>>> Implementation-Title: my-app
>>> Implementation-Version: 1.0-SNAPSHOT
>>>
>>> These seem to have names that are foreign to my usage of Maven.
>>> Is there a better reference about how these map to maven properties.
>>>
>>> Extension-Name: my-app
>>> Specification-Vendor:
>>> Implementation-Vendor:
>>> Implementation-Title:
>>> Implementation-Version:
>>>
>>>
>>> Ron
>>>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Getting a useful Manifest
Posted by Ron Wheeler <rw...@artifact-software.com>.
* MNGSITE-118 Improve guide-manifest.html
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"<rw...@artifact-software.com>:
>> 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.
>>
>>
>>
>> On 19/08/2010 11:12 AM, Ron Wheeler wrote:
>>> http://maven.apache.org/guides/mini/guide-manifest.html
>>> shows an example of a nice MANIFEST.MF that includes a version number.
>>>
>>> We do not get a version number in our manifests.
>>> What triggers the addition of the these entries.
>>>
>>> Extension-Name: my-app
>>> Specification-Vendor: MyCompany Inc
>>> Implementation-Vendor: MyCompany Inc
>>> Implementation-Title: my-app
>>> Implementation-Version: 1.0-SNAPSHOT
>>>
>>> These seem to have names that are foreign to my usage of Maven.
>>> Is there a better reference about how these map to maven properties.
>>>
>>> Extension-Name: my-app
>>> Specification-Vendor:
>>> Implementation-Vendor:
>>> Implementation-Title:
>>> Implementation-Version:
>>>
>>>
>>> Ron
>>>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
Re: Getting a useful Manifest
Posted by Anders Hammar <an...@hammar.net>.
But you'll file a ticket to get this fixed, right?
/Anders (mobile)
Den 2010 8 19 17:36 skrev "Ron Wheeler" <rw...@artifact-software.com>:
> 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.
>
>
>
> On 19/08/2010 11:12 AM, Ron Wheeler wrote:
>> http://maven.apache.org/guides/mini/guide-manifest.html
>> shows an example of a nice MANIFEST.MF that includes a version number.
>>
>> We do not get a version number in our manifests.
>> What triggers the addition of the these entries.
>>
>> Extension-Name: my-app
>> Specification-Vendor: MyCompany Inc
>> Implementation-Vendor: MyCompany Inc
>> Implementation-Title: my-app
>> Implementation-Version: 1.0-SNAPSHOT
>>
>> These seem to have names that are foreign to my usage of Maven.
>> Is there a better reference about how these map to maven properties.
>>
>> Extension-Name: my-app
>> Specification-Vendor:
>> Implementation-Vendor:
>> Implementation-Title:
>> Implementation-Version:
>>
>>
>> Ron
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
Re: Getting a useful Manifest
Posted by Ron Wheeler <rw...@artifact-software.com>.
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.
On 19/08/2010 11:12 AM, Ron Wheeler wrote:
> http://maven.apache.org/guides/mini/guide-manifest.html
> shows an example of a nice MANIFEST.MF that includes a version number.
>
> We do not get a version number in our manifests.
> What triggers the addition of the these entries.
>
> Extension-Name: my-app
> Specification-Vendor: MyCompany Inc
> Implementation-Vendor: MyCompany Inc
> Implementation-Title: my-app
> Implementation-Version: 1.0-SNAPSHOT
>
> These seem to have names that are foreign to my usage of Maven.
> Is there a better reference about how these map to maven properties.
>
> Extension-Name: my-app
> Specification-Vendor:
> Implementation-Vendor:
> Implementation-Title:
> Implementation-Version:
>
>
> Ron
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org