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"<[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]
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to