Hello,
For my project I would like to have the classes in the jar file and
the resources in a
directory, unpacked
I was wondering if the following was possible:
-when you create an artifact, have the classes packaged in a jar file
and the resources in a separate directory/jar.
-when you use assem
Hi
I am using maven2 to package a EJB3 jar and I was wondering how I
package the dependencies into the EJB3 jar file? Looks like you can do
it with maven 1 with ejb.bundle but I cannot find any documentation for
maven 2?
Thanks Glen
Drinkwater, GJ (Glen) schrieb:
> I am using maven2 to package a EJB3 jar and I was wondering how I
> package the dependencies into the EJB3 jar file? Looks like you can do
> it with maven 1 with ejb.bundle but I cannot find any documentation for
> maven 2?
So far I am using assembly:assembly / ja
The usual way of doing this is to package the EJB jar together with
its dependencies in an EAR file. In a JEE5 environment the deps can
either go in a "lib" directory in the EAR or (and for J2EE 1.3/4) be
at the root of the EAR and a manifest classpath entry added to the EJB
jar. This stuff
hat J2EE 1.3/4 must go into
the root of the ear, which is not the case.
-Chris
--
View this message in context:
http://www.nabble.com/EJB-Jar-packaging-tp18402174p18426698.html
Sent from the Maven - Users mailing list archive at Nabble.com.
s
can go.
We were using a lib directory in the root of the ear quite happily
with
WebSphere 5.1 (J2EE 1.3).
The above post implies (the way that I read it) that J2EE 1.3/4 must
go into
the root of the ear, which is not the case.
-Chris
--
View this message in context:
http://www.nab
Stephen Coy <[EMAIL PROTECTED]> wrote on 13/07/2008 21:07:57:
> In JEE5, jars in an EAR's "lib" directory do not need to be in the EJB
> jar's manifest classpath.
Ah. Thanks makes it a lot clearer!
Thanks for clearing that up for me.
> In J2EE 1.3/1.4 these jars normally need to be in the EJ
party other than intended recipient. Sender does
not necessarily endorse content contained within this transmission.
> To: users@maven.apache.org
> Subject: Re: EJB Jar packaging
> From: [EMAIL PROTECTED]
> Date: Mon, 14 Jul 2008 10:38:55 +1000
>
> Stephen Coy <[EMAIL PROTECTE
Sphere 5.1 (J2EE 1.3).
The above post implies (the way that I read it) that J2EE 1.3/4
must go into
the root of the ear, which is not the case.
-Chris
--
View this message in context:
http://www.nabble.com/EJB-Jar-packaging-tp18402174p184266
Kristian Rink
Sent: 11 July 2008 13:54
To: users@maven.apache.org
Subject: Re: EJB Jar packaging
Drinkwater, GJ (Glen) schrieb:
> I am using maven2 to package a EJB3 jar and I was wondering how I
> package the dependencies into the EJB3 jar file? Looks like you can
> do it with mav
Dear Maven Users,
My project contains three sub-projects as follows:
mylib
|
+-mylib-core (jar packaging)
|
+-mylib-demo (jar packaging)
|
+-mylib-dist (jar packaging)
I want the last sub-project to produce a jar-file containing the
following:
index.html
demo.html
demo.jnlp
juice-core-.jar
Rob Dickens a écrit :
Dear Maven Users,
My project contains three sub-projects as follows:
mylib
|
+-mylib-core (jar packaging)
|
+-mylib-demo (jar packaging)
|
+-mylib-dist (jar packaging)
I want the last sub-project to produce a jar-file containing the
following:
index.html
demo.html
On 29 Mar 2006, at 13:35, Emmanuel Venisse wrote:
You can use the assembly plugin (http://maven.apache.org/guides/
mini/guide-assemblies.html), it will be the best solution.
The preferred format is what you want ;-) (zip, tar, tar.gz,
tar.bz2, jar...)
Emmanuel
Many thanks for this reply.
Hi,
I have an unusual requirement where I want to replace
maven-compiler-plugin by another compiler-plugin. Is there a way I can
do this? My situation is like this:
I want to use hk2-maven-plugin [1] as the compiler plugin. This plugin
automatically executes if I change my project's packaging
Hi all,
I am trying to setup a multi-module project. One module produce a JAR
(jar-module) and another one a WAR which uses jar produced by "jar-module".
jar-modules has some configuration files - Spring xml and .property files.
Rather then package them as part of the jar I wanted to deploy them
we plan to use the META-INF/maven/../pom.properties to read the
application/jar version and parent.artifactId at runtime.
Current pom.properties:
#Generated by Maven
#Sun Nov 11 19:49:00 PST 2007
version=1.0.0-SNAPSHOT
groupId=com.mycompany.myproject
artifactId=myproject-web-common
I want to ad
I think you are out of luck. What is the other plugin that breaks, and does
the hk2-jar packaging produce artifacts that have the type hk2-jar or do
they have the type jar?
I suspect that this bold 3rd plugin is expecting artifacts of type jar and
you are producing artifacts of type hk2-jar which
Try
maven-compiler-plugin
**/*.*
or something similar.
Stefan
Sahoo wrote:
Hi,
I have an unusual requirement where I want to replace
maven-compiler-plugin by another compiler-plugin. Is there a way I can
do this? My situation is like this:
I want to use hk2-maven-plugin [1] as the
search their page, you shall find that it mentions it has
supportedProjectTypes defaults to "jar","bundle."
Thanks,
Sahoo
Stephen Connolly wrote:
I think you are out of luck. What is the other plugin that breaks,
and does
the hk2-jar packaging produce artifacts that have th
think you are out of luck. What is the other plugin that breaks, and does
the hk2-jar packaging produce artifacts that have the type hk2-jar or do
they have the type jar?
I suspect that this bold 3rd plugin is expecting artifacts of type jar and
you are producing artifacts of type hk2-jar which
Yes, your suggestion works, only thing is there is a slight modification
needed. I had to write:
**/*.*
, otherwise mvn would complain that a String can't be assigned to a Set
type.
Thanks,
Sahoo
VUB Stefan Seidel wrote:
Try
maven-compiler-plugin
**/*.*
or something similar.
Stefa
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
-
___
http://stubb
gt;>>
>>> [1] https://hk2.dev.java.net/hk2-maven-plugin/hk2-compile-mojo.html
>>>
>>> -
>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>> For additional commands, e-mail: [EMAIL PR
Hi Alexi,
The way we've done this is to package the applicationContext.xml in the
war - not in the jar. You can do this by adding it to the war's
src/main/resources directory. In order to run unit tests in the jar
module, we have added an applicationContext.xml in the jar's
src/test/resources
somebody point me in direction of how to
>> achieve
>> it. Such as how I install additional artifacts in 1. above and then how I
>> do
>> 3.
>>
>> Thanks, Alexi
>>
>
> -
Hi Alexi,
Thanks for clarifying. So what you could do is keep the
applicationContext.xml packaged in your jar and update your war's POM to
use the "dependency:unpack" mojo to copy it to the right location to be
included in your war.
The dependency plugin page has an example of unpacking spec
**/*.*
**/*.*
--
View this message in context:
http://maven-users.828.n2.nabble.com/Re-How-to-disable-maven-compiler-plugin-for-jar-packaging
27 matches
Mail list logo
