Re: Creating a Custom Lifecycle
Am Freitag, 9. Juli 2010 00:38:37 schrieb asookazian: Thanks! Now I just need to write a simple Mojo/plugin that will copy the exploded EAR directory to the server/default/deploy directory in JBoss. cool. Or you use the maven-antrun-plugin and save yourself some work :) hth, - martin signature.asc Description: This is a digitally signed message part.
Re: Maven jaxb2 plugin encoding issue
Hi, try to deactivate the header. configuration arguments-no-header/arguments ... regards thomas Am 09.07.2010 04:36, schrieb zhaoyi: I set up jaxb2 plugin in my maven. It will generate code first then compile the code. My problem is that when jaxb2 generate the code, it will generate a commend line in the source code // Generated on: 2010 The time line include Chinese character for that I am using a Chinese version OS. When maven begins to build the source code, I will get an error that maven doesn't map UTF-8 character. How can I change the generated time character on jaxb2 plugin? thanks. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Creating a Custom Lifecycle
Am Freitag, 9. Juli 2010 08:04:20 schrieb Martin Höller: Am Freitag, 9. Juli 2010 00:38:37 schrieb asookazian: Thanks! Now I just need to write a simple Mojo/plugin that will copy the exploded EAR directory to the server/default/deploy directory in JBoss. cool. Or you use the maven-antrun-plugin and save yourself some work :) The cargo plugin is usually used for depolying artifacts to containers and it seems, it can also deploy exploded wars (I haven't use this feature). See http://old.nabble.com/-mvnreloadable-webapps-to7702892.html#a7715823 or use google for some details. hth, - martin signature.asc Description: This is a digitally signed message part.
Re: Maven jaxb2 plugin encoding issue
Below is our configuration. The -no-header doesn't solve the problem.
plugin
groupIdorg.jvnet.jaxb2.maven2/groupId
artifactIdmaven-jaxb2-plugin/artifactId
version0.7.1/version
executions
execution
idgenerate-jaxb/id
phasegenerate-test-sources/phase
goals
goalgenerate/goal
/goals
/execution
/executions
configuration
generatePackagecom.example.ipo.jaxb/generatePackage
generateDirectory${project.build.directory}/jaxb-source/generateDirectory
schemaDirectory${basedir}/src/test/resources/schemaDirectory
schemaIncludes
includeipo.xsd/include
/schemaIncludes
arguments-no-header/arguments
/configuration
/plugin
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-jaxb2-plugin-encoding-issue-tp1045281p1045317.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven jaxb2 plugin encoding issue
Hi,
Afaik the plugin org.jvnet.jaxb2.maven2:maven-jaxb2-plugin is not
maintained here.
We can answer for the plugin [1] : org.codehaus.mojo:jaxb2-maven-plugin
So try with this one if you have the same issue.
[1] http://mojo.codehaus.org/jaxb2-maven-plugin/
2010/7/9 zhaoyi youhaod...@gmail.com:
Below is our configuration. The -no-header doesn't solve the problem.
plugin
groupIdorg.jvnet.jaxb2.maven2/groupId
artifactIdmaven-jaxb2-plugin/artifactId
version0.7.1/version
executions
execution
idgenerate-jaxb/id
phasegenerate-test-sources/phase
goals
goalgenerate/goal
/goals
/execution
/executions
configuration
generatePackagecom.example.ipo.jaxb/generatePackage
generateDirectory${project.build.directory}/jaxb-source/generateDirectory
schemaDirectory${basedir}/src/test/resources/schemaDirectory
schemaIncludes
includeipo.xsd/include
/schemaIncludes
arguments-no-header/arguments
/configuration
/plugin
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-jaxb2-plugin-encoding-issue-tp1045281p1045317.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Olivier
http://twitter.com/olamy
http://fr.linkedin.com/in/olamy
http://www.viadeo.com/fr/profile/olivier.lamy7
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven jaxb2 plugin encoding issue
Hi,
we use
plugin
!-- http://mojo.codehaus.org/jaxb2-maven-plugin/xjc-mojo.html --
groupIdorg.codehaus.mojo/groupId
artifactIdjaxb2-maven-plugin/artifactId
version1.3/version
executions
execution
idjaxb2-maven-plugin-run/id
phasegenerate-sources/phase
goals
goalxjc/goal
/goals
configuration
packageName/packageName
/configuration
/execution
/executions
/plugin
thomas
Am 09.07.2010 08:35, schrieb zhaoyi:
Below is our configuration. The -no-header doesn't solve the problem.
plugin
groupIdorg.jvnet.jaxb2.maven2/groupId
artifactIdmaven-jaxb2-plugin/artifactId
version0.7.1/version
executions
execution
idgenerate-jaxb/id
phasegenerate-test-sources/phase
goals
goalgenerate/goal
/goals
/execution
/executions
configuration
generatePackagecom.example.ipo.jaxb/generatePackage
generateDirectory${project.build.directory}/jaxb-source/generateDirectory
schemaDirectory${basedir}/src/test/resources/schemaDirectory
schemaIncludes
includeipo.xsd/include
/schemaIncludes
arguments-no-header/arguments
/configuration
/plugin
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
pom vs. project
Hi guys,
I am experiencing problems when using the maven-assembly-plugin. In
the main pom.xml i got
plugins
plugin
artifactIdmaven-assembly-plugin/artifactId
...
configuration
descriptors
descriptorsrc/main/assembly/bin.xml/descriptor
descriptorsrc/main/assembly/common.xml/descriptor
/descriptors
/configuration
/plugin
/plugins
In the bin.xml I have different output directories, all looking like that:
fileSet
directorysrc/main/bin/bin/directory
outputDirectorytest-${project.version}/bin/outputDirectory
fileMode0755/fileMode
/fileSet
This compiles well under Ubuntu 10.04. However, under mac the
${project.version} does not get substituted. When I substitute the
${project. through ${pom. everywhere, everything works fine. My setup
is
Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
Java version: 1.6.0_20
Java home: /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home
Default locale: en_US, platform encoding: MacRoman
OS name: mac os x version: 10.6.4 arch: x86_64 Family: mac
From the page http://docs.codehaus.org/display/MAVENUSER/MavenPropertiesGuide
I got, that pom is deprecated and project is the one to use. Which is
it now? Will sustituting $pom everywhere break in future versions?
Thanks,
Robin
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven APIs
I think I would look into how a Maven Repository Manager does this. Personally, I would investigate Nexus, which is OSS. http://nexus.sonatype.org There's a nexus-dev mailing list which you could use. /Anders On Thu, Jul 8, 2010 at 23:50, Robert Dare robert.d...@gmail.com wrote: Hi, Is it possible to re-use some some of the Maven APIs for repository management? For example, if I would like to implement code that saves content on the file system in group_id/artifact_id/version format. Is there a straight-forward path to reuse any Maven jars for that? (sorry if this should be in maven-developer, please let me know and I will cross-post). Regards, Rob
Re: Processing Changes found in SCM
Maybe the update goal of the maven-scm-plugin? http://maven.apache.org/scm/plugins/update-mojo.html /Anders On Fri, Jul 9, 2010 at 07:58, D D dawi...@gmail.com wrote: Hello, I'm running into an issue where a project that carries a very large number of static website files takes too long to deploy. Does anyone know of a mechanism in Maven that would allow me to check out through scm plugin only changed files? Personally I'm opposed to deploying only changed files but higher powers dictate this solution to me. I would rather use Maven than write a shell script to handle this special case. Thanks in advance, Dave
Re: pom vs. project
Yes, pom is deprecated but stills works in 3.0-beta-1 I believe.
/Anders
On Fri, Jul 9, 2010 at 09:40, Robin Wenglewski ro...@wenglewski.de wrote:
Hi guys,
I am experiencing problems when using the maven-assembly-plugin. In
the main pom.xml i got
plugins
plugin
artifactIdmaven-assembly-plugin/artifactId
...
configuration
descriptors
descriptorsrc/main/assembly/bin.xml/descriptor
descriptorsrc/main/assembly/common.xml/descriptor
/descriptors
/configuration
/plugin
/plugins
In the bin.xml I have different output directories, all looking like that:
fileSet
directorysrc/main/bin/bin/directory
outputDirectorytest-${project.version}/bin/outputDirectory
fileMode0755/fileMode
/fileSet
This compiles well under Ubuntu 10.04. However, under mac the
${project.version} does not get substituted. When I substitute the
${project. through ${pom. everywhere, everything works fine. My setup
is
Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
Java version: 1.6.0_20
Java home: /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home
Default locale: en_US, platform encoding: MacRoman
OS name: mac os x version: 10.6.4 arch: x86_64 Family: mac
From the page
http://docs.codehaus.org/display/MAVENUSER/MavenPropertiesGuide
I got, that pom is deprecated and project is the one to use. Which is
it now? Will sustituting $pom everywhere break in future versions?
Thanks,
Robin
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Processing Changes found in SCM
On 09/07/2010 1:58 AM, D D wrote: Hello, I'm running into an issue where a project that carries a very large number of static website files takes too long to deploy. Does anyone know of a mechanism in Maven that would allow me to check out through scm plugin only changed files? Personally I'm opposed to deploying only changed files but higher powers dictate this solution to me. I would rather use Maven than write a shell script to handle this special case. Thanks in advance, Dave Another alternative would be to break the project up into smaller units that could be deployed separately. Ron - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Repository migration
Hello, I was using a repository that was served by maven proxy. Now I will have to use a new version of maven (2.2.1) with a nexus repo. The old repo had libraries that are not in the new one, and I wanted to take the missing libs from my local maven cache and deploy them on the new nexus repo. Another alternative would be to export the libs from the old repo for importing to the new repo, but I don't know if that is possible. How do I do that ? Thanks in advance This message and any attachments (the message) is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) not therefore be liable for the message if modified. Do not print this message unless it is necessary, consider the environment. - Ce message et toutes les pieces jointes (ci-apres le message) sont etablis a l'intention exclusive de ses destinataires et sont confidentiels. Si vous recevez ce message par erreur, merci de le detruire et d'en avertir immediatement l'expediteur. Toute utilisation de ce message non conforme a sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. L'internet ne permettant pas d'assurer l'integrite de ce message, BNP PARIBAS (et ses filiales) decline(nt) toute responsabilite au titre de ce message, dans l'hypothese ou il aurait ete modifie. N'imprimez ce message que si necessaire, pensez a l'environnement.
Re: Repository migration
This question would have been more appropriate for the Nexus user list, but I'll answer here as well. For Nexus there are three alternatives: 1. Deploy via the maven-deploy-plugin (deploy-file goal) 2. Deploy through the UI 3. Use Nexus REST API to deploy There is also a possible forth option. You could copy the necessary files (create the right dirs and copy jars and poms) directly to the file system and issue a reindex job in Nexus. Please post follow up questions to the Nexus list! /Anders On Fri, Jul 9, 2010 at 15:58, daniel.d.san...@externe.bnpparibas.comwrote: Hello, I was using a repository that was served by maven proxy. Now I will have to use a new version of maven (2.2.1) with a nexus repo. The old repo had libraries that are not in the new one, and I wanted to take the missing libs from my local maven cache and deploy them on the new nexus repo. Another alternative would be to export the libs from the old repo for importing to the new repo, but I don't know if that is possible. How do I do that ? Thanks in advance This message and any attachments (the message) is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) not therefore be liable for the message if modified. Do not print this message unless it is necessary, consider the environment. - Ce message et toutes les pieces jointes (ci-apres le message) sont etablis a l'intention exclusive de ses destinataires et sont confidentiels. Si vous recevez ce message par erreur, merci de le detruire et d'en avertir immediatement l'expediteur. Toute utilisation de ce message non conforme a sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. L'internet ne permettant pas d'assurer l'integrite de ce message, BNP PARIBAS (et ses filiales) decline(nt) toute responsabilite au titre de ce message, dans l'hypothese ou il aurait ete modifie. N'imprimez ce message que si necessaire, pensez a l'environnement.
Re: Repository migration
I forgot. If you go with option number four, you will need to rebuild metadata (possibly this is called repo attributes) as well. /Anders On Fri, Jul 9, 2010 at 16:10, Anders Hammar and...@hammar.net wrote: This question would have been more appropriate for the Nexus user list, but I'll answer here as well. For Nexus there are three alternatives: 1. Deploy via the maven-deploy-plugin (deploy-file goal) 2. Deploy through the UI 3. Use Nexus REST API to deploy There is also a possible forth option. You could copy the necessary files (create the right dirs and copy jars and poms) directly to the file system and issue a reindex job in Nexus. Please post follow up questions to the Nexus list! /Anders On Fri, Jul 9, 2010 at 15:58, daniel.d.san...@externe.bnpparibas.comwrote: Hello, I was using a repository that was served by maven proxy. Now I will have to use a new version of maven (2.2.1) with a nexus repo. The old repo had libraries that are not in the new one, and I wanted to take the missing libs from my local maven cache and deploy them on the new nexus repo. Another alternative would be to export the libs from the old repo for importing to the new repo, but I don't know if that is possible. How do I do that ? Thanks in advance This message and any attachments (the message) is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) not therefore be liable for the message if modified. Do not print this message unless it is necessary, consider the environment. - Ce message et toutes les pieces jointes (ci-apres le message) sont etablis a l'intention exclusive de ses destinataires et sont confidentiels. Si vous recevez ce message par erreur, merci de le detruire et d'en avertir immediatement l'expediteur. Toute utilisation de ce message non conforme a sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. L'internet ne permettant pas d'assurer l'integrite de ce message, BNP PARIBAS (et ses filiales) decline(nt) toute responsabilite au titre de ce message, dans l'hypothese ou il aurait ete modifie. N'imprimez ce message que si necessaire, pensez a l'environnement.
Shade plugin: including system-scoped dependencies?
Dear All,
is it possible to include system-scoped dependencies in a shaded jar?
My dependencies look like this:
dependency
groupIdjboss-stuff/groupId
artifactIdjbossall-client/artifactId
version5.1/version
scopesystem/scope
systemPath${jbosshome}/client/jbossall-client.jar/systemPath
/dependency
I've tried adding
artifactSet
includes
includejboss-stuff:*/include
/includes
/artifactSet
but the contents of jbossall-client.jar still don't get included in the
shaded jar.
Am I just making a stupid mistake? Or are system-scoped dependencies
always excluded from shaded jars?
Best regards, Jan
--
+- Jan T. Kim ---+
| email: j@uea.ac.uk |
| WWW: http://www.cmp.uea.ac.uk/people/jtk |
*-= hierarchical systems are for files, not for humans =-*
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Shade plugin: including system-scoped dependencies?
Jan T. Kim wrote:
Dear All,
is it possible to include system-scoped dependencies in a shaded jar?
My dependencies look like this:
dependency
groupIdjboss-stuff/groupId
artifactIdjbossall-client/artifactId
version5.1/version
scopesystem/scope
systemPath${jbosshome}/client/jbossall-client.jar/systemPath
/dependency
I've tried adding
artifactSet
includes
includejboss-stuff:*/include
/includes
/artifactSet
but the contents of jbossall-client.jar still don't get included in the
shaded jar.
Am I just making a stupid mistake? Or are system-scoped dependencies
always excluded from shaded jars?
This jbossall-client.jar contains only a manifest, so what do you expect ?
- Jörg
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
release plugin issue
I've configured the release plugin in my build. I'm using a flat directory structure like: Aggregator Common Ejb Web When I do a release:prepare from the aggregator directory everything seems to work however the aggregator/... is the only path labeled. Also, when I do a release:perform from the aggregator directory it fails looking for the sibling directories in the aggregator/target/sibling. Maven identifies aggregator/target/checkout as the working directory. Is this because of the directory structure I'm using ? Does the release-plugin only work with a hierarchical dir? Is there a way around this or do I need to change the dir structure I'm using ? Thanks - The information in this message may be proprietary and/or confidential, and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify First Data immediately by replying to this message and deleting it from your computer.
Re: Creating a Custom Lifecycle
Martin Höller wrote: Am Freitag, 9. Juli 2010 00:38:37 schrieb asookazian: Thanks! Now I just need to write a simple Mojo/plugin that will copy the exploded EAR directory to the server/default/deploy directory in JBoss. cool. Or you use the maven-antrun-plugin and save yourself some work :) hth, - martin I modified the HardDeployMojo in the jboss-maven-plugin so that it copies the exploded EAR directory and not the packaged EAR file. But the copied exploded EAR does not deploy cleanly in JBoss AS 4.2.2.GA (nor does the packaged EAR). There are several NPEs in the server.log and I'm not sure why... -- View this message in context: http://maven.40175.n5.nabble.com/Creating-a-Custom-Lifecycle-tp1044781p1045577.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Creating a Custom Lifecycle
I'm going to stick with my Ant build.xml explode target that hooks into maven
via macrodef. I was trying to avoid using Ant with Maven but it's taking
too long to get the exploded WAR+EAR working with Maven and JBoss...
target name=unzip
echo message=**Beginning unzip target.../
echo message=Base directory is ${basedir} /
mkdir dir=${basedir}\target\${ear.app.name}\temp/
unzip
src=${basedir}\target\${ear.app.name}\${war.app.name}.war
dest=${basedir}\target\${ear.app.name}\temp/
delete
file=${basedir}\target\${ear.app.name}\${war.app.name}.war/
mkdir
dir=${basedir}\target\${ear.app.name}\${war.app.name}.war/
copy
todir=${basedir}\target\${ear.app.name}\${war.app.name}.war
fileset dir=${basedir}\target\${ear.app.name}\temp /
/copy
delete dir=${basedir}\target\${ear.app.name}\temp/
/target
target name=install
echo message=**Beginning install target.../
maven target=install basedir=${basedir}
arg line=-f ${pom.file} -npu -Dmaven.test.skip=true
/
/maven
/target
target name=clean
echo message=**Beginning clean target.../
echo message=Deleting
${basedir}\com.echo.cis.gui.ear\target\${ear.app.name}\temp directory/
delete
dir=${basedir}\com.echo.cis.gui.ear\target\${ear.app.name}\temp/
maven target=clean basedir=${basedir}
arg line=-f ${pom.file} /
/maven
/target
!-- target name=explode depends=showproperties, clean, install,
unzip
description=Runs mvn clean install and then unzips the EAR/WAR and copies
to JBoss deploy directory --
target name=explode depends=showproperties, clean, install, unzip
echo message=**Beginning explode target.../
mkdir
dir=${jboss.home}/server/${jboss.profile}/deploy/${ear.app.name}.ear /
copy
todir=${jboss.home}/server/${jboss.profile}/deploy/${ear.app.name}.ear
fileset dir=${artifact.dir} /
/copy
tstamp
format property=now pattern=MM/dd/ hh:mm:ss
locale=en,US/
/tstamp
echo message=Current datetime: ${now}/
echo message=The app can be accessed at ${final.url} /
/target
--
View this message in context:
http://maven.40175.n5.nabble.com/Creating-a-Custom-Lifecycle-tp1044781p1045597.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Shade plugin: including system-scoped dependencies?
On Fri, Jul 09, 2010 at 03:44:21PM +0100, J??rg Schaible wrote:
Jan T. Kim wrote:
Dear All,
is it possible to include system-scoped dependencies in a shaded jar?
My dependencies look like this:
dependency
groupIdjboss-stuff/groupId
artifactIdjbossall-client/artifactId
version5.1/version
scopesystem/scope
systemPath${jbosshome}/client/jbossall-client.jar/systemPath
/dependency
I've tried adding
artifactSet
includes
includejboss-stuff:*/include
/includes
/artifactSet
but the contents of jbossall-client.jar still don't get included in the
shaded jar.
Am I just making a stupid mistake? Or are system-scoped dependencies
always excluded from shaded jars?
This jbossall-client.jar contains only a manifest, so what do you expect ?
That's a valid point -- I hadn't noticed that the jbossall-client file
is empty these days. Apologies for providing a bad example and thanks for
looking into this.
Not all jboss-stuff jars are empty, here's another example dependency:
dependency
groupIdjboss-stuff/groupId
artifactIdjnpserver/artifactId
version5.1/version
scopesystem/scope
systemPath${jbosshome}/common/lib/jnpserver.jar/systemPath
/dependency
This time I checked that that's not an empty jar:
% jar tvf jnpserver.jar
[...]
0 Mon May 11 16:47:10 BST 2009 org/
0 Mon May 11 16:47:10 BST 2009 org/jboss/
0 Mon May 11 16:47:10 BST 2009 org/jboss/naming/
0 Mon May 11 16:47:10 BST 2009 org/jnp/
0 Mon May 11 16:47:10 BST 2009 org/jnp/client/
0 Mon May 11 16:47:10 BST 2009 org/jnp/interfaces/
0 Mon May 11 16:47:10 BST 2009 org/jnp/interfaces/java/
0 Mon May 11 16:47:10 BST 2009 org/jnp/interfaces/jnp/
0 Mon May 11 16:47:10 BST 2009 org/jnp/server/
2792 Mon May 11 16:47:10 BST 2009 org/jboss/naming/BindingsInitializer.class
[...]
So I'm trying to get org/jboss/naming/BindingsInitializer.class etc. included
in the shaded jar.
As a bit of background, this is for a command line app. Currently, I've put
the jboss jars that that app depends on into the Class-Path entry in the
jar's manifest. Obviously, that works only as long as the absolute paths to
the jars are the same on all machines the app is used on. However, that's no
longer the case, so now I'm trying to get the jar to include the stuff it
depends on. If anyone has a suggestion for solving this in a more elegant
way, I'd be interested.
Best regards, Jan
--
+- Jan T. Kim ---+
| email: j@uea.ac.uk |
| WWW: http://www.cmp.uea.ac.uk/people/jtk |
*-= hierarchical systems are for files, not for humans =-*
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Naming EJB in an EAR
Hello, I noticed that Maven created an ear for me but the names of ejbs inside are not what my app server expects. How do I specify final names for ejbs going to an ear? Thanks, Dave
RE: Naming EJB in an EAR
http://maven.apache.org/plugins/maven-ear-plugin/examples/customizing-a- module-filename.html -Original Message- From: D D [mailto:dawi...@gmail.com] Sent: Friday, July 09, 2010 1:17 PM To: Maven Users List Subject: Naming EJB in an EAR Hello, I noticed that Maven created an ear for me but the names of ejbs inside are not what my app server expects. How do I specify final names for ejbs going to an ear? Thanks, Dave This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Naming EJB in an EAR
Many thanks! I knew that page was there somewhere. Dave On Fri, Jul 9, 2010 at 12:31 PM, Yanko, Curtis curt_ya...@uhc.com wrote: http://maven.apache.org/plugins/maven-ear-plugin/examples/customizing-a- module-filename.html -Original Message- From: D D [mailto:dawi...@gmail.com] Sent: Friday, July 09, 2010 1:17 PM To: Maven Users List Subject: Naming EJB in an EAR Hello, I noticed that Maven created an ear for me but the names of ejbs inside are not what my app server expects. How do I specify final names for ejbs going to an ear? Thanks, Dave This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Shade plugin: including system-scoped dependencies?
is it possible to include system-scoped dependencies in a shaded jar? Do not use system-scope in your builds, period. jar's manifest. Obviously, that works only as long as the absolute paths to the jars are the same on all machines the app is used on. However, that's no longer the case, so now I'm trying to get the jar to include the stuff it depends on. If anyone has a suggestion for solving this in a more elegant way, I'd be interested. Do not use system-scope. Install or deploy the jars into local Maven repos. Anything else is a hack. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Shade plugin: including system-scoped dependencies?
On Fri, Jul 09, 2010 at 07:11:14PM +0100, Wayne Fay wrote:
is it possible to include system-scoped dependencies in a shaded jar?
Do not use system-scope in your builds, period.
jar's manifest. Obviously, that works only as long as the absolute paths to
the jars are the same on all machines the app is used on. However, that's no
longer the case, so now I'm trying to get the jar to include the stuff it
depends on. If anyone has a suggestion for solving this in a more elegant
way, I'd be interested.
Do not use system-scope. Install or deploy the jars into local Maven
repos. Anything else is a hack.
Ok, it's a hack (in admitting that it's not elegant I had already sort
of agreed to that), but sometimes a hack that works is just what's needed
-- so I'm still interested in how to commit this hack.
As for installing the jars, yes, that's an option I sometimes use. It's
resulting in a growing collection of jars, along with a script that
runs ``mvn install:install-file ... -Dfile=jarfile'' on all these.
I think of that collection and script as a hack as well -- creating
copies of jars in a repository goes against my desire for normalisation
and non-redundancy.
The root of the trouble really is the lack of an indirection mechanism
that would allow building a host dependent component into Class-Path
entries in a jar manifest. The duplication of stuff (whether by installing
into repos or by building shaded jars) could be avoided if something
like
Class-Path: ${JBOSS_HOME}/common/lib/jnpserver.jar
was supported. So it seems to me that since the root of the problem is
not a maven issue, all attempts of using maven to address is are bound
to end up being hacks.
Best regards, Jan
--
+- Jan T. Kim ---+
| email: j@uea.ac.uk |
| WWW: http://www.cmp.uea.ac.uk/people/jtk |
*-= hierarchical systems are for files, not for humans =-*
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Definition of aggregator POM
what exactly is an aggregator POM? I could not find it in the Maven: Definitive Guide. Here is some hint: If you have a multi-module build where the aggregator pom (i.e. the one with packaging of pom and the modules section) http://mojo.codehaus.org/versions-maven-plugin/examples/update-child-modules.html So it sounds like a top-level POM can be an aggregator POM but *must* it be? -- View this message in context: http://maven.40175.n5.nabble.com/Definition-of-aggregator-POM-tp1045740p1045740.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Definition of aggregator POM
http://maven.apache.org/pom.html#Aggregation On Fri, Jul 9, 2010 at 7:00 PM, asookazian asookaz...@gmail.com wrote: what exactly is an aggregator POM? I could not find it in the Maven: Definitive Guide. Here is some hint: If you have a multi-module build where the aggregator pom (i.e. the one with packaging of pom and the modules section) http://mojo.codehaus.org/versions-maven-plugin/examples/update-child-modules.html So it sounds like a top-level POM can be an aggregator POM but *must* it be? -- View this message in context: http://maven.40175.n5.nabble.com/Definition-of-aggregator-POM-tp1045740p1045740.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: release plugin issue
I'm also using a flat structure. I found that the keys to making this work seem to be: 1) use release 2.0 of the release plugin. This is the release with the support for flat hierarchies. Note that the Apache common parent POM version 7 (the latest) still doesn't specify this release, it specifies an earlier one (2.0-beta-9) which doesn't have this support, so you have to override that - if you're using the Apache common parent pom (i.e. http://repo1.maven.org/maven2/org/apache/apache/7/apache-7.pom ). 2) in each pom in the flat hierarchy, insure the scm element is pointing to the right place in your SVN or whatever. If you let these inherit from parent poms, the inheritance makes often wrong assumptions that the children of the parent are located underneath the parent pom directory. Specifying the actual location overrides this behavior. -Marshall Schor On 7/9/2010 11:28 AM, DeGrande, Rick wrote: I've configured the release plugin in my build. I'm using a flat directory structure like: Aggregator Common Ejb Web When I do a release:prepare from the aggregator directory everything seems to work however the aggregator/... is the only path labeled. Also, when I do a release:perform from the aggregator directory it fails looking for the sibling directories in the aggregator/target/sibling. Maven identifies aggregator/target/checkout as the working directory. Is this because of the directory structure I'm using ? Does the release-plugin only work with a hierarchical dir? Is there a way around this or do I need to change the dir structure I'm using ? Thanks - The information in this message may be proprietary and/or confidential, and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify First Data immediately by replying to this message and deleting it from your computer. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
