You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Martin Burger <mb...@cs.uni-sb.de> on 2006/04/25 10:09:43 UTC
[m2] How to generate "Download report" using Maven 2
Hello!
In Maven 1 it was possible to add a download report to the generated
site (maven.xdoc.distributionUrl). I cannot found any information about
this feature in the documentation of Maven 2. Is this feature missing?
Regards,
Martin Burger
--
Martin Burger
Researcher
Software Engineering Chair (Prof. Zeller)
Saarland University, Dept. of Informatics
Tel. +49 (0)681 302-64783 � Fax +49 (0)681 302-64012
mburger@cs.uni-sb.de � http://www.st.cs.uni-sb.de/~mburger/
Re: [m2] How to generate "Download report" using Maven 2
Posted by mburger <mb...@cs.uni-sb.de>.
mburger wrote:
>
> In Maven 1 it was possible to add a download report to the generated
> site (maven.xdoc.distributionUrl). I cannot found any information about
> this feature in the documentation of Maven 2. Is this feature missing?
>
Any news about this topic? Do you create your download pages manually? Any
best practices when publishing assemblies?
Regards
Martin Burger
--
View this message in context: http://www.nabble.com/-m2--How-to-generate-%22Download-report%22-using-Maven-2-tp4078325p17537090.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: advanced exclude pattern for Skinny Wars
Posted by Wayne Fay <wa...@gmail.com>.
Oh, I see this was a mistake, you weren't done with the email... Nevermind!
On 5/29/08, Wayne Fay <wa...@gmail.com> wrote:
> Is this a question? Or a suggestion for an improvement in the
> documentation somehow? Or something else entirely? Its just not clear
> to me. ;-)
>
> Wayne
>
> On 5/29/08, Baeriswyl Kuno - Extern (IT-BA-MV) <ku...@sbb.ch> wrote:
> > Hello,
> >
> > in der Maven documentation is an article about a workaround for creating skinny wars. http://maven.apache.org/plugins/maven-war-plugin/examples/skinny-wars.html
> >
> > In this approach, all libs in WEB-INF/lib are exluded by applying following pattern configuration:
> > <warSourceExcludes>WEB-INF/lib/*.jar</warSourceExcludes>
> >
> > ---------------------------------------------------------------------
> > 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: advanced exclude pattern for Skinny Wars
Posted by Wayne Fay <wa...@gmail.com>.
Is this a question? Or a suggestion for an improvement in the
documentation somehow? Or something else entirely? Its just not clear
to me. ;-)
Wayne
On 5/29/08, Baeriswyl Kuno - Extern (IT-BA-MV) <ku...@sbb.ch> wrote:
> Hello,
>
> in der Maven documentation is an article about a workaround for creating skinny wars. http://maven.apache.org/plugins/maven-war-plugin/examples/skinny-wars.html
>
> In this approach, all libs in WEB-INF/lib are exluded by applying following pattern configuration:
> <warSourceExcludes>WEB-INF/lib/*.jar</warSourceExcludes>
>
> ---------------------------------------------------------------------
> 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
AW: Advanced exclude pattern for Skinny Wars for RAD / WAS
Posted by "Baeriswyl Kuno - Extern (IT-BA-MV)" <ku...@sbb.ch>.
Hello,
sorry, for the confusion..outlook "automatically" send my draft..;-}
back to my problem. Unfortunately, your approach doesn't work with RAD 7.0 / Websphere 6.1, since RAD's J2EE Dependency configuration for the WAR project relies on the Manifest file in WEB-INF/lib. If I set the Provided scope to libraries, Maven won't generate an classpath entry in the Manifest file. As a consequence, The web app classloader won't see this dependency.
Kuno
-----Ursprüngliche Nachricht-----
Von: Wayne Fay [mailto:waynefay@gmail.com]
Gesendet: Donnerstag, 29. Mai 2008 17:27
An: Maven Users List
Betreff: Re: Advanced exclude pattern for Skinny Wars
I think the best way to achieve this would be by simply configuring the <scope> of the various dependencies.
Thus your Struts libraries would be "compile" scope and the utility libraries would be "provided". Then you will need to include the utility libs in the EAR module (as dependencies) as well so they are pulled into the EAR.
Wayne
On 5/29/08, Baeriswyl Kuno - Extern (IT-BA-MV) <ku...@sbb.ch> wrote:
> Hello,
>
> in der Maven documentation is an article about a workaround for
> creating skinny wars.
> http://maven.apache.org/plugins/maven-war-plugin/examples/skinny-wars.
> html
>
> In this approach, all libs in WEB-INF/lib are exluded by applying
> following pattern configuration:
> <warSourceExcludes>WEB-INF/lib/*.jar</warSourceExcludes>
>
> Is it possible to exclude only certain libraries? Respectively, can I
> configure the war plugin in way that I it keeps the web specific
> dependencies, e.g. Struts libraries, in the web application and shares
> only the utility libraries in the EAR classloader?
>
> Thanks
>
> Kuno
>
>
> ---------------------------------------------------------------------
> 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: Advanced exclude pattern for Skinny Wars
Posted by Wayne Fay <wa...@gmail.com>.
I think the best way to achieve this would be by simply configuring
the <scope> of the various dependencies.
Thus your Struts libraries would be "compile" scope and the utility
libraries would be "provided". Then you will need to include the
utility libs in the EAR module (as dependencies) as well so they are
pulled into the EAR.
Wayne
On 5/29/08, Baeriswyl Kuno - Extern (IT-BA-MV) <ku...@sbb.ch> wrote:
> Hello,
>
> in der Maven documentation is an article about a workaround for creating skinny wars. http://maven.apache.org/plugins/maven-war-plugin/examples/skinny-wars.html
>
> In this approach, all libs in WEB-INF/lib are exluded by applying following pattern configuration: <warSourceExcludes>WEB-INF/lib/*.jar</warSourceExcludes>
>
> Is it possible to exclude only certain libraries? Respectively, can I configure the war plugin in way that I it keeps the web specific dependencies, e.g. Struts libraries, in the web application and shares only the utility libraries in the EAR classloader?
>
> Thanks
>
> Kuno
>
>
> ---------------------------------------------------------------------
> 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: Advanced exclude pattern for Skinny Wars
Posted by gpborges <gp...@gmail.com>.
Hi Chris.... I was doing the same thing these days here at IBM on a migration
project from WAS 4.7 to WAS 6.1. So I've applied maven to organize the
projects that are no "so good" hehehee...
I've already added some of the configurations you've added for the
maven-eclipse-plugin (m2eclipse specific goal) but the JRE System Library I
was not using like yours... I was using in this way:
<classpathContainer>org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType</classpathContainer>
and in your previous message where you've added your complete pom you've
used in this way:
<classpathContainer>
org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/WebSphere
v6.1 JRE</classpathContainer>
However, when I run the eclipse:m2eclipse to generate the RAD files
(.project, .classpath, .settings and etc..) I got this on my .classpath and
I think it's no ok:
<classpathentry kind="con"
path="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/WebSphere 							v6.1
JRE"/>
I think the problem is only the end of the value... Is it "WebSphere v6.1
JRE" (with a space between WebSphere and v6.1) or "WebSpherev6.1 JRE" (with
no space) ???
Other questions... Where on the RAD installation did you get the dependency
to deploy on your private repository??? I have and Artifactory server in
place and I'd like to do that as well... The dependency I'm asking is this
one:
<dependency>
<groupId>com.ibm.websphere.appserver</groupId>
<artifactId>runtime</artifactId>
<version>6.1</version>
<type>pom</type>
<scope>provided</scope>
</dependency>
I'm looking forward your feedback...
Thaks in advance.
ChrisGWarp wrote:
>
> "Baeriswyl Kuno - Extern (IT-BA-MV)" <ku...@sbb.ch> wrote on
> 30/05/2008 00:37:53:
>
>> Hello,
>>
>> in der Maven documentation is an article about a workaround for creating
>
>> skinny wars. http://maven.apache.org/plugins/maven-war-
>> plugin/examples/skinny-wars.html
>>
>> In this approach, all libs in WEB-INF/lib are exluded by applying
>> following pattern configuration: <warSourceExcludes>WEB-INF/lib/*.
>> jar</warSourceExcludes>
>>
>> Is it possible to exclude only certain libraries? Respectively, can I
>> configure the war plugin in way that I it keeps the web specific
>> dependencies, e.g. Struts libraries, in the web application and shares
>> only the utility libraries in the EAR classloader?
>
> I've managed to do just that! :-)
>
> The tools, resources are the utility ones and the ejb one is added as
> well.
>
> I had issues previously when adding in the dependencies - gave wierd
> errors about things not being able to be found. The final one was the ejb
> jar. It needed the type of ejb being set specifically as it otherwise
> defaults to jar.
>
> This is my complete pom for the war file:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <project xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd" xmlns:xsi=
> "http://www.w3.org/2001/XMLSchema-instance">
>
> <modelVersion>4.0.0</modelVersion>
>
> <parent>
> <groupId>au.com.aami</groupId>
> <artifactId>aami-parent</artifactId>
> <version>1-SNAPSHOT</version>
> </parent>
>
> <groupId>au.com.aami.dialler</groupId>
> <artifactId>DiallerWeb</artifactId>
> <packaging>war</packaging>
> <version>1.0-SNAPSHOT</version>
> <name>DiallerWeb Project</name>
> <description>DiallerWeb Project</description>
> <url>http://centre.ourspace.int.corp.sun/it/sd/webapplications/</url>
>
> <dependencies>
> <dependency>
> <groupId>junit</groupId>
> <artifactId>junit</artifactId>
> <version>${junit.version}</version>
> <scope>test</scope>
> </dependency>
>
> <dependency>
> <groupId>au.com.aami</groupId>
> <artifactId>AAMITools</artifactId>
> <version>1.0-SNAPSHOT</version>
> </dependency>
>
> <dependency>
> <groupId>au.com.aami.dialler</groupId>
> <artifactId>DiallerResources</artifactId>
> <version>1.0-SNAPSHOT</version>
> </dependency>
>
> <dependency>
> <groupId>au.com.aami.dialler</groupId>
> <artifactId>DiallerEJB</artifactId>
> <version>1.0-SNAPSHOT</version>
> <type>ejb</type>
> </dependency>
>
> <dependency>
> <groupId>com.ibm.websphere.appserver</groupId>
> <artifactId>runtime</artifactId>
> <version>6.1</version>
> <type>pom</type>
> <scope>provided</scope>
> </dependency>
>
> </dependencies>
>
> <properties>
> <junit.version>3.8.1</junit.version>
> </properties>
>
> <build>
> <plugins>
> <plugin>
> <artifactId>maven-war-plugin</artifactId>
> <configuration>
> <!-- This is broken in maven-war-plugin 2.0, works in
> 2.0.1 -->
> <warSourceExcludes>WEB-INF/lib/*.jar</
> warSourceExcludes>
> <archive>
> <manifest>
> <addClasspath>true</addClasspath>
> <!--
> <classpathPrefix>lib/</classpathPrefix>
> -->
> </manifest>
> </archive>
> </configuration>
> </plugin>
>
> <plugin>
> <artifactId>maven-eclipse-plugin</artifactId>
> <configuration>
> <wtpversion>1.5</wtpversion>
>
> <additionalBuildcommands>
> <buildcommand>
> org.eclipse.wst.validation.validationbuilder</buildcommand>
> <buildcommand>
> org.eclipse.wst.common.project.facet.core.builder</buildcommand>
> </additionalBuildcommands>
>
> <additionalProjectnatures>
> <projectnature>
> org.eclipse.wst.common.project.facet.core.nature</projectnature>
> <projectnature>
> org.eclipse.wst.common.modulecore.ModuleCoreNature</projectnature>
> </additionalProjectnatures>
>
> <classpathContainers>
> <classpathContainer>
> org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/WebSphere
> v6.1 JRE</classpathContainer>
> <classpathContainer>
> org.eclipse.jst.server.core.container/com.ibm.ws.ast.st.runtime.runtimeTarget.v61/was.base.v61
> </classpathContainer>
> <classpathContainer>
> org.eclipse.jst.j2ee.internal.web.container</classpathContainer>
> <classpathContainer>
> org.eclipse.jst.j2ee.internal.module.container</classpathContainer>
> </classpathContainers>
>
> <additionalProjectFacets>
> <com.ibm.websphere.extended.web>6.1</
> com.ibm.websphere.extended.web>
> <com.ibm.websphere.coexistence.web>6.1</
> com.ibm.websphere.coexistence.web>
> </additionalProjectFacets>
>
> </configuration>
> </plugin>
> </plugins>
> </build>
>
> </project>
>
> It runs under RSA V7.
>
> Now, if only I could get the same manifest stuff to work for the actual
> EJB jar itself...
>
> -Chris
>
>
> **********************************************************************
> CAUTION - This message is intended for the addressee named above. It may
> contain privileged or confidential information.
>
> If you are not the intended recipient of this message you must:
> - Not use, copy, distribute or disclose it to anyone other than the
> addressee;
> - Notify the sender via return email; and
> - Delete the message (and any related attachments) from your computer
> immediately.
>
> Internet emails are not necessarily secure. Australian Associated Motors
> Insurers Limited ABN 92 004 791 744 (AAMI), and its related entities, do
> not accept responsibility for changes made to this message after it was
> sent.
>
> Unless otherwise stated, views expressed within this email are the
> author's own and do not represent those of AAMI.
> **********************************************************************
>
--
View this message in context: http://www.nabble.com/-m2--How-to-generate-%22Download-report%22-using-Maven-2-tp4078325p18114192.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Advanced exclude pattern for Skinny Wars
Posted by Ch...@aami.com.au.
"Baeriswyl Kuno - Extern (IT-BA-MV)" <ku...@sbb.ch> wrote on
30/05/2008 00:37:53:
> Hello,
>
> in der Maven documentation is an article about a workaround for creating
> skinny wars. http://maven.apache.org/plugins/maven-war-
> plugin/examples/skinny-wars.html
>
> In this approach, all libs in WEB-INF/lib are exluded by applying
> following pattern configuration: <warSourceExcludes>WEB-INF/lib/*.
> jar</warSourceExcludes>
>
> Is it possible to exclude only certain libraries? Respectively, can I
> configure the war plugin in way that I it keeps the web specific
> dependencies, e.g. Struts libraries, in the web application and shares
> only the utility libraries in the EAR classloader?
I am having exactly the same issue. (See the current thread with subject:
Multi Module Projects - manifest question).
Upon reading the doco on the warSourceExcludes attribute (
http://maven.apache.org/plugins/maven-war-plugin/war-mojo.html#warSourceExcludes)
the value of the tag is a comma separated list.
Yes, for things such as struts, spring etc, it may be a very long list,
but from what I can infer from the doco, that is what is needed.
I'll be testing that out a little further today. I'll let you know how I
go.
-Chris
**********************************************************************
CAUTION - This message is intended for the addressee named above. It may contain privileged or confidential information.
If you are not the intended recipient of this message you must:
- Not use, copy, distribute or disclose it to anyone other than the addressee;
- Notify the sender via return email; and
- Delete the message (and any related attachments) from your computer immediately.
Internet emails are not necessarily secure. Australian Associated Motors Insurers Limited ABN 92 004 791 744 (AAMI), and its related entities, do not accept responsibility for changes made to this message after it was sent.
Unless otherwise stated, views expressed within this email are the author's own and do not represent those of AAMI.
**********************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
AW: Advanced exclude pattern for Skinny Wars
Posted by "Baeriswyl Kuno - Extern (IT-BA-MV)" <ku...@sbb.ch>.
thanks,
actually, I didn't realize that a comma separated list is possible. I think, this should do it.
Kuno
-----Ursprüngliche Nachricht-----
Von: Chris_Graham@aami.com.au [mailto:Chris_Graham@aami.com.au]
Gesendet: Freitag, 30. Mai 2008 03:32
An: Maven Users List
Betreff: Re: Advanced exclude pattern for Skinny Wars
"Baeriswyl Kuno - Extern (IT-BA-MV)" <ku...@sbb.ch> wrote on 30/05/2008 00:37:53:
> Hello,
>
> in der Maven documentation is an article about a workaround for
> creating
> skinny wars. http://maven.apache.org/plugins/maven-war-
> plugin/examples/skinny-wars.html
>
> In this approach, all libs in WEB-INF/lib are exluded by applying
> following pattern configuration: <warSourceExcludes>WEB-INF/lib/*.
> jar</warSourceExcludes>
>
> Is it possible to exclude only certain libraries? Respectively, can I
> configure the war plugin in way that I it keeps the web specific
> dependencies, e.g. Struts libraries, in the web application and shares
> only the utility libraries in the EAR classloader?
I've managed to do just that! :-)
The tools, resources are the utility ones and the ejb one is added as well.
I had issues previously when adding in the dependencies - gave wierd errors about things not being able to be found. The final one was the ejb jar. It needed the type of ejb being set specifically as it otherwise defaults to jar.
This is my complete pom for the war file:
<?xml version="1.0" encoding="UTF-8"?>
<project xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd" xmlns:xsi= "http://www.w3.org/2001/XMLSchema-instance">
<modelVersion>4.0.0</modelVersion>
<parent>
<groupId>au.com.aami</groupId>
<artifactId>aami-parent</artifactId>
<version>1-SNAPSHOT</version>
</parent>
<groupId>au.com.aami.dialler</groupId>
<artifactId>DiallerWeb</artifactId>
<packaging>war</packaging>
<version>1.0-SNAPSHOT</version>
<name>DiallerWeb Project</name>
<description>DiallerWeb Project</description>
<url>http://centre.ourspace.int.corp.sun/it/sd/webapplications/</url>
<dependencies>
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>${junit.version}</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>au.com.aami</groupId>
<artifactId>AAMITools</artifactId>
<version>1.0-SNAPSHOT</version>
</dependency>
<dependency>
<groupId>au.com.aami.dialler</groupId>
<artifactId>DiallerResources</artifactId>
<version>1.0-SNAPSHOT</version>
</dependency>
<dependency>
<groupId>au.com.aami.dialler</groupId>
<artifactId>DiallerEJB</artifactId>
<version>1.0-SNAPSHOT</version>
<type>ejb</type>
</dependency>
<dependency>
<groupId>com.ibm.websphere.appserver</groupId>
<artifactId>runtime</artifactId>
<version>6.1</version>
<type>pom</type>
<scope>provided</scope>
</dependency>
</dependencies>
<properties>
<junit.version>3.8.1</junit.version>
</properties>
<build>
<plugins>
<plugin>
<artifactId>maven-war-plugin</artifactId>
<configuration>
<!-- This is broken in maven-war-plugin 2.0, works in 2.0.1 -->
<warSourceExcludes>WEB-INF/lib/*.jar</
warSourceExcludes>
<archive>
<manifest>
<addClasspath>true</addClasspath>
<!--
<classpathPrefix>lib/</classpathPrefix>
-->
</manifest>
</archive>
</configuration>
</plugin>
<plugin>
<artifactId>maven-eclipse-plugin</artifactId>
<configuration>
<wtpversion>1.5</wtpversion>
<additionalBuildcommands>
<buildcommand> org.eclipse.wst.validation.validationbuilder</buildcommand>
<buildcommand> org.eclipse.wst.common.project.facet.core.builder</buildcommand>
</additionalBuildcommands>
<additionalProjectnatures>
<projectnature> org.eclipse.wst.common.project.facet.core.nature</projectnature>
<projectnature> org.eclipse.wst.common.modulecore.ModuleCoreNature</projectnature>
</additionalProjectnatures>
<classpathContainers>
<classpathContainer> org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/WebSphere
v6.1 JRE</classpathContainer>
<classpathContainer> org.eclipse.jst.server.core.container/com.ibm.ws.ast.st.runtime.runtimeTarget.v61/was.base.v61
</classpathContainer>
<classpathContainer> org.eclipse.jst.j2ee.internal.web.container</classpathContainer>
<classpathContainer> org.eclipse.jst.j2ee.internal.module.container</classpathContainer>
</classpathContainers>
<additionalProjectFacets>
<com.ibm.websphere.extended.web>6.1</
com.ibm.websphere.extended.web>
<com.ibm.websphere.coexistence.web>6.1</
com.ibm.websphere.coexistence.web>
</additionalProjectFacets>
</configuration>
</plugin>
</plugins>
</build>
</project>
It runs under RSA V7.
Now, if only I could get the same manifest stuff to work for the actual EJB jar itself...
-Chris
**********************************************************************
CAUTION - This message is intended for the addressee named above. It may contain privileged or confidential information.
If you are not the intended recipient of this message you must:
- Not use, copy, distribute or disclose it to anyone other than the addressee;
- Notify the sender via return email; and
- Delete the message (and any related attachments) from your computer immediately.
Internet emails are not necessarily secure. Australian Associated Motors Insurers Limited ABN 92 004 791 744 (AAMI), and its related entities, do not accept responsibility for changes made to this message after it was sent.
Unless otherwise stated, views expressed within this email are the author's own and do not represent those of AAMI.
**********************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Advanced exclude pattern for Skinny Wars
Posted by Ch...@aami.com.au.
"Baeriswyl Kuno - Extern (IT-BA-MV)" <ku...@sbb.ch> wrote on
30/05/2008 00:37:53:
> Hello,
>
> in der Maven documentation is an article about a workaround for creating
> skinny wars. http://maven.apache.org/plugins/maven-war-
> plugin/examples/skinny-wars.html
>
> In this approach, all libs in WEB-INF/lib are exluded by applying
> following pattern configuration: <warSourceExcludes>WEB-INF/lib/*.
> jar</warSourceExcludes>
>
> Is it possible to exclude only certain libraries? Respectively, can I
> configure the war plugin in way that I it keeps the web specific
> dependencies, e.g. Struts libraries, in the web application and shares
> only the utility libraries in the EAR classloader?
I've managed to do just that! :-)
The tools, resources are the utility ones and the ejb one is added as
well.
I had issues previously when adding in the dependencies - gave wierd
errors about things not being able to be found. The final one was the ejb
jar. It needed the type of ejb being set specifically as it otherwise
defaults to jar.
This is my complete pom for the war file:
<?xml version="1.0" encoding="UTF-8"?>
<project xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd" xmlns:xsi=
"http://www.w3.org/2001/XMLSchema-instance">
<modelVersion>4.0.0</modelVersion>
<parent>
<groupId>au.com.aami</groupId>
<artifactId>aami-parent</artifactId>
<version>1-SNAPSHOT</version>
</parent>
<groupId>au.com.aami.dialler</groupId>
<artifactId>DiallerWeb</artifactId>
<packaging>war</packaging>
<version>1.0-SNAPSHOT</version>
<name>DiallerWeb Project</name>
<description>DiallerWeb Project</description>
<url>http://centre.ourspace.int.corp.sun/it/sd/webapplications/</url>
<dependencies>
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>${junit.version}</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>au.com.aami</groupId>
<artifactId>AAMITools</artifactId>
<version>1.0-SNAPSHOT</version>
</dependency>
<dependency>
<groupId>au.com.aami.dialler</groupId>
<artifactId>DiallerResources</artifactId>
<version>1.0-SNAPSHOT</version>
</dependency>
<dependency>
<groupId>au.com.aami.dialler</groupId>
<artifactId>DiallerEJB</artifactId>
<version>1.0-SNAPSHOT</version>
<type>ejb</type>
</dependency>
<dependency>
<groupId>com.ibm.websphere.appserver</groupId>
<artifactId>runtime</artifactId>
<version>6.1</version>
<type>pom</type>
<scope>provided</scope>
</dependency>
</dependencies>
<properties>
<junit.version>3.8.1</junit.version>
</properties>
<build>
<plugins>
<plugin>
<artifactId>maven-war-plugin</artifactId>
<configuration>
<!-- This is broken in maven-war-plugin 2.0, works in
2.0.1 -->
<warSourceExcludes>WEB-INF/lib/*.jar</
warSourceExcludes>
<archive>
<manifest>
<addClasspath>true</addClasspath>
<!--
<classpathPrefix>lib/</classpathPrefix>
-->
</manifest>
</archive>
</configuration>
</plugin>
<plugin>
<artifactId>maven-eclipse-plugin</artifactId>
<configuration>
<wtpversion>1.5</wtpversion>
<additionalBuildcommands>
<buildcommand>
org.eclipse.wst.validation.validationbuilder</buildcommand>
<buildcommand>
org.eclipse.wst.common.project.facet.core.builder</buildcommand>
</additionalBuildcommands>
<additionalProjectnatures>
<projectnature>
org.eclipse.wst.common.project.facet.core.nature</projectnature>
<projectnature>
org.eclipse.wst.common.modulecore.ModuleCoreNature</projectnature>
</additionalProjectnatures>
<classpathContainers>
<classpathContainer>
org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/WebSphere
v6.1 JRE</classpathContainer>
<classpathContainer>
org.eclipse.jst.server.core.container/com.ibm.ws.ast.st.runtime.runtimeTarget.v61/was.base.v61
</classpathContainer>
<classpathContainer>
org.eclipse.jst.j2ee.internal.web.container</classpathContainer>
<classpathContainer>
org.eclipse.jst.j2ee.internal.module.container</classpathContainer>
</classpathContainers>
<additionalProjectFacets>
<com.ibm.websphere.extended.web>6.1</
com.ibm.websphere.extended.web>
<com.ibm.websphere.coexistence.web>6.1</
com.ibm.websphere.coexistence.web>
</additionalProjectFacets>
</configuration>
</plugin>
</plugins>
</build>
</project>
It runs under RSA V7.
Now, if only I could get the same manifest stuff to work for the actual
EJB jar itself...
-Chris
**********************************************************************
CAUTION - This message is intended for the addressee named above. It may contain privileged or confidential information.
If you are not the intended recipient of this message you must:
- Not use, copy, distribute or disclose it to anyone other than the addressee;
- Notify the sender via return email; and
- Delete the message (and any related attachments) from your computer immediately.
Internet emails are not necessarily secure. Australian Associated Motors Insurers Limited ABN 92 004 791 744 (AAMI), and its related entities, do not accept responsibility for changes made to this message after it was sent.
Unless otherwise stated, views expressed within this email are the author's own and do not represent those of AAMI.
**********************************************************************
Advanced exclude pattern for Skinny Wars
Posted by "Baeriswyl Kuno - Extern (IT-BA-MV)" <ku...@sbb.ch>.
Hello,
in der Maven documentation is an article about a workaround for creating skinny wars. http://maven.apache.org/plugins/maven-war-plugin/examples/skinny-wars.html
In this approach, all libs in WEB-INF/lib are exluded by applying following pattern configuration: <warSourceExcludes>WEB-INF/lib/*.jar</warSourceExcludes>
Is it possible to exclude only certain libraries? Respectively, can I configure the war plugin in way that I it keeps the web specific dependencies, e.g. Struts libraries, in the web application and shares only the utility libraries in the EAR classloader?
Thanks
Kuno
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
advanced exclude pattern for Skinny Wars
Posted by "Baeriswyl Kuno - Extern (IT-BA-MV)" <ku...@sbb.ch>.
Hello,
in der Maven documentation is an article about a workaround for creating skinny wars. http://maven.apache.org/plugins/maven-war-plugin/examples/skinny-wars.html
In this approach, all libs in WEB-INF/lib are exluded by applying following pattern configuration:
<warSourceExcludes>WEB-INF/lib/*.jar</warSourceExcludes>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2] How to generate "Download report" using Maven 2
Posted by mburger <mb...@cs.uni-sb.de>.
mburger wrote:
>
> In Maven 1 it was possible to add a download report to the generated
> site (maven.xdoc.distributionUrl). I cannot found any information about
> this feature in the documentation of Maven 2. Is this feature missing?
>
Any news about this topic? Do you create your download pages manually? Any
best practices when publishing assemblies?
Regards
Martin Burger
--
View this message in context: http://www.nabble.com/-m2--How-to-generate-%22Download-report%22-using-Maven-2-tp4078325p17536236.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org