Re: EJB Jar packaging
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 EJB jar's manifest classpath, whether or not they are in a lib directory. If they are in a lib directory, then the manifest classpath entries must include lib/ for each jar. Now it's possible that WAS 5.1 had a non-portable extension that had the JEE5 behavior - I know that WebLogic certainly had a similar feature. But this behavior was not added to the standard until JEE5. In any event, Glen does not mention EAR files at all, so I was just trying to establish what he was trying to do. ** 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. **
Re: Archetype sample for multi-projects
I had similar issues, and no answers here, so I'll try to help. s[e]th h[o]lth [EMAIL PROTECTED] wrote on 11/07/2008 03:18:36: Hello, Since monday i'm trying to build a multi-projects archetype without success... I tried many differents way to do it but i didn't reach this goal :x - I tried by myself after reading the (poor ?) documentation on the website - I tried using some sample (like j2ee archetype but there is no java classes in the subprojects) - I tried using archetype:create-from-project with not result What failed. This is the step that I followed. If someone can send me an example with a pom parent and at least one subproject with some java classes inside that can be package relocatable with a -Dpackage option when using mvn archetype:create it would be GREAT ! :) I've used generate instead of create. Attached a sample to you privately. -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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Proper Dependency Management - HowTo?
Michael McCallum [EMAIL PROTECTED] wrote on 03/07/2008 14:05:09: 11) don't mix inheritance and aggregation. that means a parent pom NEVER ever has modules, if you think about the concept for a minute - or longer - there will be a moment of enlightenment Sorry for jumping in here, but wehy not? The only time (admitedely) I use this is for a multi module J2EE project, where each module (WAR, EAR, EJB, JAR etc) all have the multi module pom as their parent, and the multi module pom has the corporate one as it's parent. I was told to do this, and in fact, if you you use archetype:create-from-project (?) that is how it generates the pom structure of the generated archetype. So, I'm curious as to why you would say not to do this. -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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to use DB2's JCC jars as a single dependency.
I was asked privately how to: Can you explain what should I do to use db2 jcc library as one dependency in my maven project? What commands I should execute to gain such feature? Simple, you need to install (into your local repo) or deploy (into your corporate one, if you have one) the jars files individually (all three of them) and the pom file (that holds them all together) into the repo. These are the files that I have (the jars are from DB2 V8, FP15): 1,139 db2-v8-fp15.pom 1,216,068 db2jcc.jar 2,063 db2jcc_license_cisuz.jar 1,013 db2jcc_license_cu.jar You need to construct a POM that acts as a library/aggregrate pom that holds them all together, making use of the transative nature of maven 2. This is what mine looks like: ?xml version=1.0 encoding=UTF-8? project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdcom.ibm.db2.jcc/groupId artifactIdruntime/artifactId versionV8-FP15/version packagingpom/packaging descriptionLibrary POM for the DB2 Universal Driver runtime jars from DB2 V8 FP15./description dependencies dependency groupIdcom.ibm.db2.jcc/groupId artifactIddb2jcc/artifactId versionV8-FP15/version /dependency dependency groupIdcom.ibm.db2.jcc/groupId artifactIddb2jcc_license_cisuz/artifactId versionV8-FP15/version /dependency dependency groupIdcom.ibm.db2.jcc/groupId artifactIddb2jcc_license_cu/artifactId versionV8-FP15/version /dependency /dependencies /project Then you need to install/deploy them all, I have a batch file that does them all in one hit: This is how I deploy them: call mvn deploy:deploy-file -Dfile=db2jcc.jar -DgroupId=com.ibm.db2.jcc -DartifactId=db2jcc -Dversion=V8-FP15 -Dpackaging=jar -DgeneratePom=true -DrepositoryId=? -Durl=? call mvn deploy:deploy-file -Dfile=db2jcc_license_cisuz.jar -DgroupId=com.ibm.db2.jcc -DartifactId=db2jcc_license_cisuz -Dversion=V8-FP15 -Dpackaging=jar -DgeneratePom=true -DrepositoryId=? -Durl=? call mvn deploy:deploy-file -Dfile=db2jcc_license_cu.jar -DgroupId=com.ibm.db2.jcc -DartifactId=db2jcc_license_cu -Dversion=V8-FP15 -Dpackaging=jar -DgeneratePom=true -DrepositoryId=? -Durl=? call mvn deploy:deploy-file -Dfile=db2-v8-fp15.pom -DpomFile=db2-v8-fp15.pom -DrepositoryId=? -Durl=? You'll just need to the the repositoryId and url to your local situation (I can not help you on this one). -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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maintaining versions across multi-module project
I remove the version from all of the module poms entirely and just have
the multi module build pom have it. It works for me.
-Chris
Kallin Nagelberg [EMAIL PROTECTED] wrote on 01/07/2008
04:55:00:
Can anyone tell me what is the best/simplest way to maintain a version
number across all the poms in a multi-module project?
They are all to be deployed with the same version every time.
Ideally, the version could be declared in one place (the superpom), and
all
children would know to use it.
I've tried doing something like this in the root POM:
properties
parent.groupIdcom.something/parent.groupId
parent.artifactIdsomething_parent/parent.artifactId
parent.version2.0/parent.version
/properties
and then
groupId${parent.groupId}/groupId
artifactId${parent.artifactId}/artifactId
version${varent.version}/version
in the ROOT POM as well.
Then I have my modules below set their parent to be:
groupId${parent.groupId}/groupId
artifactId${parent.artifactId}/artifactId
version${varent.version}/version
This sort of works, but not great.
What's the best way to do something like this?
The following message has been automatically added by the Internet mail
gateway to comply with the Group's Information Security requirements.
This e-mail has arrived via the Internet, and therefore you should be
cautious about its origin and content. Replies which contain sensitive
information and / or legal/contractual obligations are particularly
vulnerable.
In these cases you should not reply unless you are authorised to do so,
and adequate encryption is employed.
If you have any questions, please contact the IS Service Desk.
**
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Manipulation of ibm-webservices-bnd.xmi
Hello David! Hmmm, upon reading, it may work. If I get some time I may investigate, but for the moment it works for me. -Chris [EMAIL PROTECTED] wrote on 30/06/2008 23:52:34: On Mon, 30 Jun 2008, [EMAIL PROTECTED] wrote: Hi All. I don't mind not having this file generated, but I do need to manipulate it. The issue arises with the name attribute of the routerModules element. It needs the name of the war file that hosts the router modules. Maybe you can use this goal: http://mojo.codehaus.org/was6-maven-plugin/wsDefaultBindings-mojo.html along with some configuration in http://mojo.codehaus.org/was6-maven-plugin/wsDefaultBindings-mojo.html#strategy -- David J. M. Karlsen - +47 90 68 22 43 http://www.davidkarlsen.com http://mp3.davidkarlsen.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] The following message has been automatically added by the Internet mail gateway to comply with the Group's Information Security requirements. This e-mail has arrived via the Internet, and therefore you should be cautious about its origin and content. Replies which contain sensitive information and / or legal/contractual obligations are particularly vulnerable. In these cases you should not reply unless you are authorised to do so, and adequate encryption is employed. If you have any questions, please contact the IS Service Desk. ** 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven WebSphere 6.1
Hi Jon, Not to my knowledge. I used the list that RSA V7 uses as the WebSphere Application Server v6.1 Runtime classpath container, so that is what RSA uses itself to compile against. Which from Maven's point of view, it should be all that we need. I've not run into issues with that list yet. -Chris news [EMAIL PROTECTED] wrote on 27/06/2008 23:09:09: Hi Chris This is exactly what i was looking for - you mentioned below that this was part of the batch file you use. Are there any WAS 6.1 libraries missing from the list below. Cheers Jon [EMAIL PROTECTED] wrote: Hi. I do not get maven to actually generate the EJB deployment code, WebSphere itself will do it at deployment time, so I do. If nothing else, this will give you a list of the jars that you need. Using RSA V7, it defines a classpath container that has all of the necessary jars in it needed to support complete websphere 6.1 development. What I have done is to define a runtime library/aggregrate pom for the websphere runtime. I have not needed to define one for the JRE. This is part of a batch file that I used to copy the necessary runtime files (as defined in the classpath container) to a temp holding dir, and then install/deploy them into your repo. md C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\WMQ\java\lib\com.ibm.mq.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\WMQ\java\lib\com.ibm.mqjms.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\bootstrap.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\j2ee.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\mail-impl.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\marshall.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.ejbportable_6.1.0.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.emf_2.1.0.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.portletcontainer_2.0.0.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.runtime.dist_6.1.0.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.runtime_6.1.0.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.sib.server_2.0.0.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.sip.container_6.1.0.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.wccm_6.1.0.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.webcontainer_2.0.0.jar C:\Temp\Maven\WAS61 That should have these files in the C:\Temp\maven\WAS61 dir: 50,767 bootstrap.jar 430,143 com.ibm.mq.jar 1,238,366 com.ibm.mqjms.jar 77,523 com.ibm.ws.ejbportable_6.1.0.jar 3,355,425 com.ibm.ws.emf_2.1.0.jar 622,223 com.ibm.ws.portletcontainer_2.0.0.jar 1,927,102 com.ibm.ws.runtime.dist_6.1.0.jar 53,066,732 com.ibm.ws.runtime_6.1.0.jar 11,771,638 com.ibm.ws.sib.server_2.0.0.jar 1,179,014 com.ibm.ws.sip.container_6.1.0.jar 9,221,353 com.ibm.ws.wccm_6.1.0.jar 3,267,808 com.ibm.ws.webcontainer_2.0.0.jar 546,698 j2ee.jar 202,255 mail-impl.jar 72,730 marshall.jar I deployed them to the repo (in this case proximity) using: call mvn deploy:deploy-file -Dfile=com.ibm.mq.jar -DgroupId=com.ibm.websphere.appserver -DartifactId=com.ibm.mq -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true call mvn deploy:deploy-file -Dfile=com.ibm.mqjms.jar -DgroupId=com.ibm.websphere.appserver -DartifactId=com.ibm.mqjms -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true call mvn deploy:deploy-file -Dfile=bootstrap.jar -DgroupId=com.ibm.websphere.appserver -DartifactId=bootstrap -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true call mvn deploy:deploy-file -Dfile=j2ee.jar -DgroupId=com.ibm.websphere.appserver -DartifactId=j2ee -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true call mvn deploy:deploy-file -Dfile=mail-impl.jar -DgroupId=com.ibm.websphere.appserver -DartifactId=mail-impl -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true call mvn deploy:deploy-file -Dfile=marshall.jar -DgroupId=com.ibm.websphere.appserver -DartifactId=marshall -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true call mvn deploy:deploy-file -Dfile=com.ibm.ws.ejbportable_6.1.0.jar -DgroupId=com.ibm.websphere.appserver -DartifactId=com.ibm.ws.ejbportable_6.1.0
Manipulation of ibm-webservices-bnd.xmi
Hi All. I don't mind not having this file generated, but I do need to manipulate it. The issue arises with the name attribute of the routerModules element. It needs the name of the war file that hosts the router modules. ?xml version=1.0 encoding=UTF-8? com.ibm.etools.webservice.wsbnd:WSBinding xmi:version=2.0 xmlns:xmi= http://www.omg.org/XMI; xmlns:com.ibm.etools.webservice.wsbnd= http://www.ibm.com/websphere/appserver/schemas/5.0.2/wsbnd.xmi; xmi:id= WSBinding_1214542480718 wsdescBindings xmi:id=WSDescBinding_1214542480718 wsDescNameLink= ClickToTalkEJBService pcBindings xmi:id=PCBinding_1214542480718 pcNameLink= ClickToTalkEJB / /wsdescBindings routerModules xmi:id=RouterModule_1214542497796 transport=http name=DiallerWeb.war / /com.ibm.etools.webservice.wsbnd:WSBinding Is there a way that I can get this file manipulated to allow me to change this: routerModules xmi:id=RouterModule_1214542497796 transport= http name=DiallerWeb.war / To this: routerModules xmi:id=RouterModule_1214542497796 transport= http name=DiallerWeb-3.0-SNAPSHOT.war / ? Currently, I've worked around this by using the warName config element to specify the name without the version. -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. **
Re: properties in archetypes?
[EMAIL PROTECTED] wrote on 18/06/2008 16:50:05:
Can we make use of our own properties/variables in archetypes?
The m2eclipse plugin allows us to define properties to be used at
arcetype
generation time.
The problem is, I've not see a single references as to _how_ to do
this!???
For example:
dependency
groupId${groupId}/groupId
artifactId${projectName}Web/artifactId
version1.0-SNAPSHOT/version
typewar/type
/dependency
I would like to be able to define the value of the variable projectName,
so, if I defined projectName = Blah, it would expand to:
artifactIdBlahWeb/artifactId
-Chris
To answer my own question (with a little help from some - thanks!):
Create a file called archetype-metadata.xml in the
\src\main\resources\META-INF\maven directory, and put this into it:
?xml version=1.0 encoding=UTF-8?
archetype-descriptor name=basic-ear
fileSets
fileSet filtered=true packaged=false
directory/directory
includes
include**/*/include
/includes
/fileSet
/fileSets
requiredProperties
requiredProperty key=projectName /
/requiredProperties
/archetype-descriptor
That will process and generate what is needed.
Now, when you call the generate stage, you need to define the the property
projectName as a system property, by defining it as a system property:
mvn archetype:generate
-Darchetype.interactive=false
-DarchetypeCatalog=local
-DarchetypeGroupId=au.com.warpspeed.archetypes
-DarchetypeArtifactId=basic-ear
-DarchetypeVersion=1.0
-DgroupId=au.com.warpspeed.test
-DartifactId=SampleEAR
-Dversion=1.0-SNAPSHOT
-DprojectName=Sample
If you get an error similar to this:
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] : org.apache.maven.archetype.exception.ArchetypeNotConfigured:
Archetype au.com.warpspeed.archetypes:build:1.0 is
not configured
Archetype au.com.warpspeed.archetypes:build:1.0 is not configured
Archetype au.com.warpspeed.archetypes:build:1.0 is not configured
It means that the property has not been specified. Hope this helps.
The full doco can be found at:
http://maven.apache.org/plugins/maven-archetype-plugin/specification/archetype-metadata.html
-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.
**
properties in archetypes?
Can we make use of our own properties/variables in archetypes?
The m2eclipse plugin allows us to define properties to be used at arcetype
generation time.
The problem is, I've not see a single references as to _how_ to do
this!???
For example:
dependency
groupId${groupId}/groupId
artifactId${projectName}Web/artifactId
version1.0-SNAPSHOT/version
typewar/type
/dependency
I would like to be able to define the value of the variable projectName,
so, if I defined projectName = Blah, it would expand to:
artifactIdBlahWeb/artifactId
-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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: location of application.xml?
Bernhard David [EMAIL PROTECTED] wrote on 18/06/2008 16:21:06: Hello, I think you just need to declare src/main/application as a resource folder in your pom - resources resource directorysrc/main/application/directory /resource and it should work exactly as src/main/resources does. Hi David. Thanks for following up. That leaves me with one final problem if I only have one application.xml file (irrespective of it's location). Eclipse will put in the project names of the web and ejb projects into application.xml, eg BlahWeb and BlahEJB. Maven when it creates application.xml, it will use the version information as well, eg BlahWeb-1.0-SNAPSHOT etc (unless I use a final name). The problem arises when maven will not generate application.xml when it is already in \src\main\application. Is there a way to tell it to do so? Or, are you aware of any other way to do it? Thanks for your help. -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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
location of application.xml?
I'm not sure when you put META-INF\application.xml. Does it go under src\main\resources or src\main\application? mvn eclipse:eclipse generates a source dir reference to src\main\application, and that is what it appears to need to be able to run the test app in the environment. However, although maven generates a correct application.xml (one that uses the correct version numbers from the war/ejb modules) it does not put it in the generated ear file - not if I use src\main\application. If I use src\main\application then it uses what is in the file system and not generate one. Which almost makes me take the approach of using both src\main\resources and src\main\application - yuk! Which is correct? -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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven WebSphere 6.1
Hello Siarhei. No, we don't need to generate the stubs and ties in the IDE for a remote deployment. However, obviously you would have to do that when using the local test environment, and I use the IDE to do that. It is much easier (and more natural for me at least) to have the IDE to generate such things than to use maven for that task. So I simply skip it. We do not deploy from a CI environment, and probably never will do so. All (most?) of our application communicate with one or more mainframes, and they sometimes need to deploy their code as well... :-) That would not work from a CI environment, as it requires more manual integration with other code (on the M/F). However, if the app was _entirely_ self contained, ie did everything itself and have no other external links etc, then I may consider gettting the build to do it, but at this point, I don't see the point. Basically, the model that I have in my head at the moment, is that we'll use CI to automate the builds, run the tests, produce the reports, and (when I work out how to) upload the ear to the remote server but not deploy it. We have a web app (deploy site) that allows us deploy our ear artifacts to the necessary instances, retrieve logs from production etc. That is what we have to use to deploy apps, that we can only do in our system test (real websphere on AIX) env. We have a separate team that manages the websphere environment for us. When we deploy, and the stubs and ties are done for us, here is the output: ADMA5018I: The EJBDeploy command is running on enterprise archive (EAR) file /tmp/app38179.ear. Starting workbench. framework search path: /ibmapp2/websphere61/base/deploytool/itp/plugins Creating the project. Deploying jar DiallerEJB-1.0-SNAPSHOT Generating deployment code Invoking RMIC. Writing output file Shutting down workbench. EJBDeploy complete. 0 Errors, 0 Warnings, 0 Informational Messages ADMA5007I: The EJBDeploy command completed on /ibmapp2/websphere61/deploymgr/wstemp/wstemp/app_11a7f4e92be/dpl/dpl_dial.ear I would recommend that you (well, everyone really) do a manual deployment of an ear file using the admin console, just so that they understand what is done and the issues involved. -Chris Siarhei Dudzin [EMAIL PROTECTED] wrote on 13/06/2008 08:09:36: Hi Chris, This is very interesting approach. Does that mean you have to actually generate stubssceletons in IDE before you can build with maven? How do you deploy your apps to a server in CI environment? Do you use hot deployment (then you might have timing issues) or do you not deploy at all and only do unit testing? Regards, Siarhei On Wed, Jun 11, 2008 at 3:35 AM, [EMAIL PROTECTED] wrote: Hi. I do not get maven to actually generate the EJB deployment code, WebSphere itself will do it at deployment time, so I do. If nothing else, this will give you a list of the jars that you need. The following message has been automatically added by the Internet mail gateway to comply with the Group's Information Security requirements. This e-mail has arrived via the Internet, and therefore you should be cautious about its origin and content. Replies which contain sensitive information and / or legal/contractual obligations are particularly vulnerable. In these cases you should not reply unless you are authorised to do so, and adequate encryption is employed. If you have any questions, please contact the IS Service Desk. ** 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AW: Maven WebSphere 6.1
Hi Kuno. I understand why you've done what you've done, but it is not a very CI friendly approach (as it does require a local install). Multiple versions, and even fix pack variations, and especially when you may wish to consider feature packs (ejb 3, web services etc), putting it into the repository makes far better sense. Which is why I provided the steps that I used to create it and supplied the pom. I should save someone a few hours. I would be interested to see an example of your system scope pointing to the local file system, could you please share an example? Ta. As always, use whatever works best for you! -Chris Baeriswyl Kuno - Extern (IT-BA-MV) [EMAIL PROTECTED] wrote on 11/06/2008 15:26:43: Hello! I've got another approach. First, I've defined a WAS_HOME constant in my parent pom. Second, I've defined the websphere dependencies with system scope. Or in other words, I've defined the dependencies with a link to the local filesystem using the WAS_HOME constant. With this approach you don't need to copy the libraties into the repository. Furthermore, you can handle different Websphere versions. Though, it requires a local copy of WAS. And preferably with identical install path. In case the install path isn't identical, the constant WAS_HOME an be changed at runtime. At the beginning, I've copied the libraries to the repository too, however, I've stated that I need the WAS_HOME constant anyway when I started using was6 Plugin. Regards Kuno -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 11. Juni 2008 03:35 An: Maven Users List Betreff: Re: Maven WebSphere 6.1 Hi. I do not get maven to actually generate the EJB deployment code, WebSphere itself will do it at deployment time, so I do. If nothing else, this will give you a list of the jars that you need. Using RSA V7, it defines a classpath container that has all of the necessary jars in it needed to support complete websphere 6.1 development. What I have done is to define a runtime library/aggregrate pom for the websphere runtime. I have not needed to define one for the JRE. This is part of a batch file that I used to copy the necessary runtime files (as defined in the classpath container) to a temp holding dir, and then install/deploy them into your repo. md C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\WMQ\java\lib\com.ibm.mq.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\WMQ\java\lib\com. ibm.mqjms.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\bootstrap.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\j2ee.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\mail-impl.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\marshall.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws. ejbportable_6.1.0.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws. emf_2.1.0.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws. portletcontainer_2.0.0.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws. runtime.dist_6.1.0.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws. runtime_6.1.0.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws. sib.server_2.0.0.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws. sip.container_6.1.0.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws. wccm_6.1.0.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws. webcontainer_2.0.0.jar C:\Temp\Maven\WAS61 That should have these files in the C:\Temp\maven\WAS61 dir: 50,767 bootstrap.jar 430,143 com.ibm.mq.jar 1,238,366 com.ibm.mqjms.jar 77,523 com.ibm.ws.ejbportable_6.1.0.jar 3,355,425 com.ibm.ws.emf_2.1.0.jar 622,223 com.ibm.ws.portletcontainer_2.0.0.jar 1,927,102 com.ibm.ws.runtime.dist_6.1.0.jar 53,066,732 com.ibm.ws.runtime_6.1.0.jar 11,771,638 com.ibm.ws.sib.server_2.0.0.jar 1,179,014 com.ibm.ws.sip.container_6.1.0.jar 9,221,353 com.ibm.ws.wccm_6.1.0.jar 3,267,808 com.ibm.ws.webcontainer_2.0.0.jar 546,698 j2ee.jar 202,255 mail-impl.jar 72,730 marshall.jar I deployed them to the repo (in this case proximity) using: call mvn deploy:deploy-file -Dfile=com.ibm.mq.jar -DgroupId=com.ibm. websphere.appserver -DartifactId=com.ibm.mq -Dversion=6.1
Eclipse: How to create a Simple Project type
Hi all. How can we get maven to create a simple eclipse project (not a Java one)? Ie, get it to generate a .project file: ?xml version=1.0 encoding=UTF-8? projectDescription nameBlah/name comment/comment projects/projects buildSpec/buildSpec natures/natures /projectDescription The type of the project from the pom.xml is pom, ie: packagingpom/packaging Can this be done? -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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven WebSphere 6.1
Hi. I do not get maven to actually generate the EJB deployment code, WebSphere itself will do it at deployment time, so I do. If nothing else, this will give you a list of the jars that you need. Using RSA V7, it defines a classpath container that has all of the necessary jars in it needed to support complete websphere 6.1 development. What I have done is to define a runtime library/aggregrate pom for the websphere runtime. I have not needed to define one for the JRE. This is part of a batch file that I used to copy the necessary runtime files (as defined in the classpath container) to a temp holding dir, and then install/deploy them into your repo. md C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\WMQ\java\lib\com.ibm.mq.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\WMQ\java\lib\com.ibm.mqjms.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\bootstrap.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\j2ee.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\mail-impl.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\marshall.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.ejbportable_6.1.0.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.emf_2.1.0.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.portletcontainer_2.0.0.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.runtime.dist_6.1.0.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.runtime_6.1.0.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.sib.server_2.0.0.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.sip.container_6.1.0.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.wccm_6.1.0.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.webcontainer_2.0.0.jar C:\Temp\Maven\WAS61 That should have these files in the C:\Temp\maven\WAS61 dir: 50,767 bootstrap.jar 430,143 com.ibm.mq.jar 1,238,366 com.ibm.mqjms.jar 77,523 com.ibm.ws.ejbportable_6.1.0.jar 3,355,425 com.ibm.ws.emf_2.1.0.jar 622,223 com.ibm.ws.portletcontainer_2.0.0.jar 1,927,102 com.ibm.ws.runtime.dist_6.1.0.jar 53,066,732 com.ibm.ws.runtime_6.1.0.jar 11,771,638 com.ibm.ws.sib.server_2.0.0.jar 1,179,014 com.ibm.ws.sip.container_6.1.0.jar 9,221,353 com.ibm.ws.wccm_6.1.0.jar 3,267,808 com.ibm.ws.webcontainer_2.0.0.jar 546,698 j2ee.jar 202,255 mail-impl.jar 72,730 marshall.jar I deployed them to the repo (in this case proximity) using: call mvn deploy:deploy-file -Dfile=com.ibm.mq.jar -DgroupId=com.ibm.websphere.appserver -DartifactId=com.ibm.mq -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true call mvn deploy:deploy-file -Dfile=com.ibm.mqjms.jar -DgroupId=com.ibm.websphere.appserver -DartifactId=com.ibm.mqjms -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true call mvn deploy:deploy-file -Dfile=bootstrap.jar -DgroupId=com.ibm.websphere.appserver -DartifactId=bootstrap -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true call mvn deploy:deploy-file -Dfile=j2ee.jar -DgroupId=com.ibm.websphere.appserver -DartifactId=j2ee -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true call mvn deploy:deploy-file -Dfile=mail-impl.jar -DgroupId=com.ibm.websphere.appserver -DartifactId=mail-impl -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true call mvn deploy:deploy-file -Dfile=marshall.jar -DgroupId=com.ibm.websphere.appserver -DartifactId=marshall -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true call mvn deploy:deploy-file -Dfile=com.ibm.ws.ejbportable_6.1.0.jar -DgroupId=com.ibm.websphere.appserver -DartifactId=com.ibm.ws.ejbportable_6.1.0 -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true call mvn deploy:deploy-file -Dfile=com.ibm.ws.emf_2.1.0.jar -DgroupId=com.ibm.websphere.appserver -DartifactId=com.ibm.ws.emf_2.1.0 -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true call mvn deploy:deploy-file -Dfile=com.ibm.ws.portletcontainer_2.0.0.jar -DgroupId=com.ibm.websphere.appserver -DartifactId=com.ibm.ws.portletcontainer_2.0.0 -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true call mvn deploy:deploy-file -Dfile=com.ibm.ws.runtime.dist_6.1.0.jar -DgroupId=com.ibm.websphere.appserver -DartifactId=com.ibm.ws.runtime.dist_6.1.0 -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true call mvn deploy:deploy-file -Dfile=com.ibm.ws.runtime_6.1.0.jar -DgroupId=com.ibm.websphere.appserver -DartifactId=com.ibm.ws.runtime_6.1.0 -Dversion=6.1
Re: AW: modifying version number in POM
No, I meant exactly what I said. Maven itself needs to be able to check in/out etc from your SCM. We use ClearCase in with UCM Dynamic Views, which is not supported (particularly well (if at all?)) by maven. So, in that instance, we will need to basically to a release manually. If maven fully supports your SCM, then yes, release:prepare etc will work for you. Just something that you need to be aware of. -Chris Niranjan Deshpande [EMAIL PROTECTED] wrote on 05/06/2008 16:49:34: Hi Chris, So you meant to say that SNAPSHOT will be repaced by a timestamp at the run time? also, can we avoid the chekin of the pom and tagging of the project that happens after mvn release:prepare? i am rather experimenting on things and dnt want to invite the wrath of other developers if ther repository is contaminated ;) On 6/5/08, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Mark Struberg [EMAIL PROTECTED] wrote on 04/06/2008 22:53:35: Maybe i missed the point, or you did. The usual behaviour is to always have a SNAPSHOT version in your SCM e.g. version1.4-SNAPSHOT/version If you make a build, you simply use the maven-release-plugin $mvn release:prepare this will .) ask you the release-version which will default to 1.4 and the next- version which defaults to 1.5-SNAPSHOT .) does some usefull checks .) checkin pom with the 1.4 into SCM and tag the project .) set the next version in the pom to 1.5-SNAPSHOT or whatever you provided in step 1 after this, do a $mvn release:perform to build the project with the freshly tagged build version So there is usually no need to set versions in the pom manually. So long as maven supports your scm... -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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Regards, Niranjan Deshpande Shut yourself from the world and create the reality you want The following message has been automatically added by the Internet mail gateway to comply with the Group's Information Security requirements. This e-mail has arrived via the Internet, and therefore you should be cautious about its origin and content. Replies which contain sensitive information and / or legal/contractual obligations are particularly vulnerable. In these cases you should not reply unless you are authorised to do so, and adequate encryption is employed. If you have any questions, please contact the IS Service Desk. ** 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AW: modifying version number in POM
Mark Struberg [EMAIL PROTECTED] wrote on 05/06/2008 18:32:23: So long as maven supports your scm... But then it is still much better to get this SCM supported then having hundred of developers tweaking around manually. Which SCM you need isn't supported yet? Since I already wrote the maven-scm-providers-git, I maybe can help you in writing another one. ClearCase UCM with Dynamic Views. http://maven.apache.org/scm/clearcase.html Look at the last section, ClearCase dynamic views. :-( I contacted Dan Tran, who worked on it originally, but now is not involved (has no access to ClearCase). -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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Simple Archetype Question
Hi All. Can an archetype create more than one project? Ta. -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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AW: modifying version number in POM
Mark Struberg [EMAIL PROTECTED] wrote on 04/06/2008 22:53:35: Maybe i missed the point, or you did. The usual behaviour is to always have a SNAPSHOT version in your SCM e.g. version1.4-SNAPSHOT/version If you make a build, you simply use the maven-release-plugin $mvn release:prepare this will .) ask you the release-version which will default to 1.4 and the next- version which defaults to 1.5-SNAPSHOT .) does some usefull checks .) checkin pom with the 1.4 into SCM and tag the project .) set the next version in the pom to 1.5-SNAPSHOT or whatever you provided in step 1 after this, do a $mvn release:perform to build the project with the freshly tagged build version So there is usually no need to set versions in the pom manually. So long as maven supports your scm... -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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Über Archetype ?
Hi All, Does maven support the concept of an Über Archetype? That is, a single archetype that can create multiple projects in one invocation. Ideally, what I am looking for is a single archetype that can create a full J2EE project as a multi module build, along with all of it's EJB, EAR and WAR subprojects. Can this be done? TIA. -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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Advanced exclude pattern for Skinny Wars
Baeriswyl Kuno - Extern (IT-BA-MV) [EMAIL PROTECTED] 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: warSourceExcludesWEB-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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Advanced exclude pattern for Skinny Wars
Baeriswyl Kuno - Extern (IT-BA-MV) [EMAIL PROTECTED] 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: warSourceExcludesWEB-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;
modelVersion4.0.0/modelVersion
parent
groupIdau.com.aami/groupId
artifactIdaami-parent/artifactId
version1-SNAPSHOT/version
/parent
groupIdau.com.aami.dialler/groupId
artifactIdDiallerWeb/artifactId
packagingwar/packaging
version1.0-SNAPSHOT/version
nameDiallerWeb Project/name
descriptionDiallerWeb Project/description
urlhttp://centre.ourspace.int.corp.sun/it/sd/webapplications//url
dependencies
dependency
groupIdjunit/groupId
artifactIdjunit/artifactId
version${junit.version}/version
scopetest/scope
/dependency
dependency
groupIdau.com.aami/groupId
artifactIdAAMITools/artifactId
version1.0-SNAPSHOT/version
/dependency
dependency
groupIdau.com.aami.dialler/groupId
artifactIdDiallerResources/artifactId
version1.0-SNAPSHOT/version
/dependency
dependency
groupIdau.com.aami.dialler/groupId
artifactIdDiallerEJB/artifactId
version1.0-SNAPSHOT/version
typeejb/type
/dependency
dependency
groupIdcom.ibm.websphere.appserver/groupId
artifactIdruntime/artifactId
version6.1/version
typepom/type
scopeprovided/scope
/dependency
/dependencies
properties
junit.version3.8.1/junit.version
/properties
build
plugins
plugin
artifactIdmaven-war-plugin/artifactId
configuration
!-- This is broken in maven-war-plugin 2.0, works in
2.0.1 --
warSourceExcludesWEB-INF/lib/*.jar/
warSourceExcludes
archive
manifest
addClasspathtrue/addClasspath
!--
classpathPrefixlib//classpathPrefix
--
/manifest
/archive
/configuration
/plugin
plugin
artifactIdmaven-eclipse-plugin/artifactId
configuration
wtpversion1.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.web6.1/
com.ibm.websphere.extended.web
com.ibm.websphere.coexistence.web6.1/
Re: Multi Module Projects - manifest question
Hi Martin.
Yes I did. I had some issues with the EJB jar needing the type of
it to be specifially set.
?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;
modelVersion4.0.0/modelVersion
parent
groupIdau.com.aami/groupId
artifactIdaami-parent/artifactId
version1-SNAPSHOT/version
/parent
groupIdau.com.aami.dialler/groupId
artifactIdDiallerWeb/artifactId
packagingwar/packaging
version1.0-SNAPSHOT/version
nameDiallerWeb Project/name
descriptionDiallerWeb Project/description
urlhttp://centre.ourspace.int.corp.sun/it/sd/webapplications//url
dependencies
dependency
groupIdjunit/groupId
artifactIdjunit/artifactId
version${junit.version}/version
scopetest/scope
/dependency
dependency
groupIdau.com.aami/groupId
artifactIdAAMITools/artifactId
version1.0-SNAPSHOT/version
/dependency
dependency
groupIdau.com.aami.dialler/groupId
artifactIdDiallerResources/artifactId
version1.0-SNAPSHOT/version
/dependency
dependency
groupIdau.com.aami.dialler/groupId
artifactIdDiallerEJB/artifactId
version1.0-SNAPSHOT/version
typeejb/type
/dependency
dependency
groupIdcom.ibm.websphere.appserver/groupId
artifactIdruntime/artifactId
version6.1/version
typepom/type
scopeprovided/scope
/dependency
/dependencies
properties
junit.version3.8.1/junit.version
/properties
build
plugins
plugin
artifactIdmaven-war-plugin/artifactId
configuration
!-- This is broken in maven-war-plugin 2.0, works in
2.0.1 --
warSourceExcludesWEB-INF/lib/*.jar/
warSourceExcludes
archive
manifest
addClasspathtrue/addClasspath
!--
classpathPrefixlib//classpathPrefix
--
/manifest
/archive
/configuration
/plugin
plugin
artifactIdmaven-eclipse-plugin/artifactId
configuration
wtpversion1.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.web6.1/
com.ibm.websphere.extended.web
com.ibm.websphere.coexistence.web6.1/
com.ibm.websphere.coexistence.web
/additionalProjectFacets
/configuration
/plugin
/plugins
/build
/project
Now I need to get it work for fhe actual EJB jar itself.
-Chris
Martin [EMAIL PROTECTED] wrote on 29/05/2008 22:28:24:
Hi Chris-
Have you looked at configuring the manifest-entries in the maven war
plugin
http://maven.apache.org/plugins/maven-war-plugin/examples/war-manifest-guide.html
Martin
- Original Message -
From: [EMAIL PROTECTED]
To: Maven Users List users@maven.apache.org
Sent: Thursday, May 29, 2008 1:57 AM
Subject: Multi Module Projects - manifest question
Hi,
I have a multi module ear project.
One of the modules is a standard jar (just a resource jar with
no
dependencies of it's own).
One of the other modules is a war file.
How do I get the manifest file of the war file to reference the
(utility) jar
Re: MultiModule checkstyle config
gommo [EMAIL PROTECTED] wrote on 30/05/2008 10:53:48:
Did you ever solve this? I'm having the same problem
I did, but took a slightly different appoach. It works for me (so far at
least):
Take this pom:
?xml version=1.0 encoding=UTF-8?
project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=
http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=
http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
parent
groupIdau.com.warpspeed/groupId
artifactIdwarpspeed-dynamic-parent/artifactId
version1-SNAPSHOT/version
/parent
groupIdau.com.warpspeed/groupId
artifactIdbuild-tools/artifactId
packagingjar/packaging
version1.0-SNAPSHOT/version
nameWarpSpeed Build Tools Extension/name
descriptionProvides resources to aid the common maven build./
description
/project
I have created this dir structure:
\src\main\resources\checkstyle-supressions.xml
\src\main\resources\warpspeed_checkstyle_4_4.xml
\src\main\resources\warpspeed-header.txt
Use you own content.
Install it into your repo.
And this is what I have in the parent:
reporting
plugins
plugin
artifactIdmaven-checkstyle-plugin/artifactId
version${maven-checkstyle-plugin.version}/version
inheritedtrue/inherited
configuration
enableRulesSummaryfalse/enableRulesSummary
configLocation${checkstyle.config.location}/
configLocation
headerLocation${checkstyle.header.location}/
headerLocation
!--
headerFile${checkstyle.header.location}/headerFile
--
suppressionsLocation
${checkstyle.suppressions.location}/suppressionsLocation
/configuration
/plugin
/plugins
/reporting
build
plugins
plugin
artifactIdmaven-checkstyle-plugin/artifactId
version${maven-checkstyle-plugin.version}/version
executions
execution
phaseverify/phase
goals
goalcheck/goal
/goals
/execution
/executions
configuration
configLocation${checkstyle.config.location}/
configLocation
headerLocation${checkstyle.header.location}/
headerLocation
suppressionsLocation
${checkstyle.suppressions.location}/suppressionsLocation
/configuration
dependencies
dependency
groupIdau.com.warpspeed/groupId
artifactIdbuild-tools/artifactId
version${build-tools.version}/version
/dependency
dependency
groupIdcheckstyle/groupId
artifactIdcheckstyle/artifactId
version4.4/version
/dependency
/dependencies
/plugin
/plugins
/build
properties
build-tools.version1.0-SNAPSHOT/build-tools.version
checkstyle.config.locationwarpspeed_checkstyle_4_4.xml/
checkstyle.config.location
checkstyle.header.locationwarpspeed-header.txt/
checkstyle.header.location
checkstyle.suppressions.locationcheckstyle-suppressions.xml/
checkstyle.suppressions.location
/properties
Note how I've set them as dependencies of the plugin. This requires maven
2.0.9 (min) and is what Brian Fox suggested. It basically places them on
the classpath, so I've used the same technique to get them available for
the plugin.
It works for me.
However, adding in this section may work for you, I've commented it out
for me (it lives in the build section):
!--
extensions
extension
groupIdau.com.warpspeed/groupId
artifactIdbuild-tools/artifactId
version${build-tools.version}/version
/extension
/extensions
--
HTH.
-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,
Copying Artifacts
Hi All. I would like to copy the produced artifact of the package step (in this case an ear file) to a remote unix server. How do I do this? In this case I need to copy the ear file to a remote unix machine (under ant I used pscp from the putty suite) for deployment. Note this is NOT a deployment into a maven repository, it is simply a copy of the artifact to a unix box so that I can then deploy it into WebSphere. One final requirement: each artifact uses a different userid/password (two ears, two user id's etc). Most of what I've found is all written around deploying to various maven repositories, which does not apply in this case. TIA. -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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Multi Module Projects - manifest question
Hi, I have a multi module ear project. One of the modules is a standard jar (just a resource jar with no dependencies of it's own). One of the other modules is a war file. How do I get the manifest file of the war file to reference the (utility) jar in that is correctly packaged in the ear file? The ear is being correctly built and all of the required modules are being placed in it. However, the final issue that I face is to get the manifests of the war file to be correct. As this is a multi module project, the war project does not actually list the resource jar as a dependency. Should it? I would not have thought so, as the resource jar itself should not be installed into the repository. Help! I've spent about 4 weeks bashing maven into shape, and as far as I can tell, this appears to be pretty much the last hurdle. Otherwise I have to scap maven. -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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: RAD7 Support
Hendlmeier Georg (extern) [EMAIL PROTECTED] wrote on 27/05/2008 23:48:11: Hi all, is there currently any RAD7 support in maven-eclipse-plugin? As far as i tested, RAD7 does not recognize e.g. ear project etc. and is not able to deploy to WAS. Is there something wrong or something in the pipe or something else? ;) Welcome to the world of maven centric thinking. I've managed to get EJB project working. Here is my POM as a reference. There are also other threads on their forum, search the history if you can. -Chris ?xml version=1.0 encoding=UTF-8? project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi= http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation= http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdau.com.warpspeed/groupId artifactIdProjectEJB/artifactId packagingejb/packaging version1.0-SNAPSHOT/version nameProjectEJB Project/name dependencies dependency groupIdjboss/groupId artifactIdjboss-j2ee/artifactId version4.0.2/version scopeprovided/scope /dependency /dependencies properties junit.version3.8.1/junit.version /properties build plugins plugin artifactIdmaven-eclipse-plugin/artifactId configuration wtpversion1.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.module.container/classpathContainer /classpathContainers additionalProjectFacets com.ibm.websphere.extended.ejb6.1/ com.ibm.websphere.extended.ejb /additionalProjectFacets /configuration /plugin /plugins /build /project It is the setup in the build section that is the critical bit, as that is what defines the metadata used by eclipse to be recognised as an EJB, WAR, EAR project etc. HTH. -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. **
CheckStyle and Path Issues with Hudson
Hi All. I have an issue running Maven under Hudson, when in conjunction with ClearCase. Hudson is correctly creating a workspace and creating a snapshot view of the UCM Project. As an artifact of using ClearCase, there will always be a reference to the VOB in the pathname, under the workspace. Under Hudson, when it creates a workspace, you will normally check your code out directly into it - as the root. CVS and SVN handle this easily. However, under ClearCase, the viewname, vob and any other directories will be created underneath it. Ie: ...\workspace\hudson_view\TOOLS_VOB\TOOL_Folder\Tools\pom.xml The issue here is that Hudson wants to run everything with the workspace as the root directory. But due to ClearCase I need to use the -f hudson_view\...\...\Tools\pom.xml This results in the following error: [INFO] [ERROR] BUILD ERROR [INFO] [INFO] An error has occurred in Checkstyle report generation. Embedded error: Unable to find configuration file location. Unable to find location 'src/main/config/CheckStyle_4_4.xml' as URL, File or Resource. [INFO] [INFO] For more information, run Maven with the -e switch [INFO] However, if I manually change to the Tools directory and run maven from there it works perfectly. So, is there a problem with the maven checkstyle plugin that it is not resolving paths correctly with the -f switch or am I doing something else incorrectly? TIA. -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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
sourcing from property files
Hi All. I know that this is backwards to the maven way of thinking, but: Is it possible to actually take a version number from a property file and have that used in the POM rather than the other way around? Ie, Property File - POM rather than, POM - Property File. Speaking of which how/can we get the version number in the pom written to a property file that is then used at runtime? Working this way just works better with our existing processes. TIA. -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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: sourcing from property files
Wayne Fay [EMAIL PROTECTED] wrote on 21/05/2008 00:22:05:
On Tue, May 20, 2008 at 1:39 AM, [EMAIL PROTECTED] wrote:
Is it possible to actually take a version number from a property
file and have that used in the POM rather than the other way around?
Not natively. But you could write a plugin to do it or use the
Properties Plugin from the Codehaus sandbox:
https://svn.codehaus.org/mojo/trunk/sandbox/properties-maven-plugin/
The Properties Maven Plugin is here to make life a little easier when
dealing with properties. It provides goals to read and write
properties from files.
Speaking of which how/can we get the version number in the pom
written to a property file that is then used at runtime?
You just need to set up a file with the token ${version} in it and
tell Maven to filter it during resource processing. Alternatively, it
seems that the Properties plugin would also handle this.
Thank you very much wayne for the detailed response. It is exactly what I
was looking for.
-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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: AW: AW: AW: maven-eclipse-plugin: Facet Issues
Baeriswyl Kuno - Extern (IT-BA-MV) [EMAIL PROTECTED] wrote on 15/05/2008 16:47:26: That's why I'm using the runtime argument. I guess that my point, is that I do not really have a good idea on the fit of and the point in having the eclipse plugin itself. Having to specify the workspace, not only not being portable (ok, you can specify it on the command line, but that is a hack at best) just smells to me of something utterly wrong - at the base concept level. However, the workspace must be indicated, otherwise it won't generate correct eclipse files. If you have a bit more time, the you should have a closer look to the eclipse plugin source code. The plugin does consider the target application server and generates the files according to the needs of the specified environement. That's why the workspace argument is required. It looks up your applications server configuration in your workspace that matches with configuration given in wtpdefaultserver. The recognising of an EJB project is a matter the maven packaging option. All of which has to be specified in the POM. It is issues like this that leads me to agree with the original Maven 1 developers point of view. Keep the build and descriptive details separate. However, those philosophical issues aside, I did get my approach to work and not having to supply the workspace. Once I cleaned up the facet issues that is. The issue was that RSA was not showing the deployment descriptor in the Project Navigator View of the J2EE Perspective. If I get a sec, I'll have a look further at your approach. -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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AW: AW: maven-eclipse-plugin: Facet Issues
Thank you very much for your help. It wasn't even recognised as an EJB project, but I didn't play with it entensively. If I get a sec, I'll give it another go. It also appears that you can put the workspace location into the settings section, which to me defeats the entire purpose of portable builds. -Chris Baeriswyl Kuno - Extern (IT-BA-MV) [EMAIL PROTECTED] wrote on 15/05/2008 16:14:55: Hi Chris, in my case it's working fine. I've got RAD7 and WAS 6.1. What exactly doesn't work? Here a better example how to call the mojo mvn -Declipse.workspace=D:/myworkspace eclipse:eclipse Kuno -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 15. Mai 2008 02:04 An: Maven Users List Betreff: Re: AW: maven-eclipse-plugin: Facet Issues Hi Kuno, Thanks for that, however it does not work for me. However, I'll see if I can incorporate the server settings etc. -Chris Baeriswyl Kuno - Extern (IT-BA-MV) [EMAIL PROTECTED] wrote on 14/05/2008 19:32:24: Hello Chris, for me, following works: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-eclipse-plugin/artifactId configuration wtpdefaultserverWebSphere Application Server v6.1/wtpdefaultserver wtpmanifesttrue/wtpmanifest wtpapplicationxmltrue/wtpapplicationxml wtpversion1.5/wtpversion additionalBuildcommands buildcommandorg. eclipse.jdt.core.javabuilder/buildcommand buildcommandorg. eclipse.wst.common.project.facet.core.builder/buildcommand buildcommandorg. eclipse.wst.validation.validationbuilder/buildcommand /additionalBuildcommands additionalProjectnatures projectnatureorg. eclipse.jdt.core.javanature/projectnature projectnatureorg. eclipse.wst.common.project.facet.core.nature/projectnature projectnatureorg. eclipse.wst.common.modulecore.ModuleCoreNature/projectnature /additionalProjectnatures classpathContainers classpathContainerorg. eclipse.jdt.launching.JRE_CONTAINER/classpathContainer classpathContainerorg. eclipse.jst.j2ee.internal.module. container/classpathContainer /classpathContainers /configuration /plugin Important: wtpdefaultserver and version must be defined. And the you must ensure to pass the runtime argument -Declipse.workspace to the eclipse:eclipse mojo. Kuno -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 14. Mai 2008 08:43 An: users@maven.apache.org Cc: [EMAIL PROTECTED] Betreff: maven-eclipse-plugin: Facet Issues Hi All. Using V2.5.1 of the maven-eclipse-plugin, I have some issues in getting the generated artifacts being correct. Take this section of the POM: additionalProjectFacets jst.java5.0/jst.java jst.ejb2.1/jst.ejb com.ibm.websphere.extended.ejb6.1/com.ibm.websphere.extended.ejb /additionalProjectFacets Generates this: faceted-project fixed facet=jst.java/ fixed facet=jst.utility/ installed facet=jst.utility version=1.0/ installed facet=jst.java version=5.0/ installed facet=com.ibm.websphere.extended.ejb version=6.1/ installed facet=jst.ejb version=2.1/ installed facet=jst.java version=5.0/ /faceted-project You'll see that the jst.java facet is in there twice. Removing the facet from the list: additionalProjectFacets jst.ejb2.1/jst.ejb com.ibm.websphere.extended.ejb6.1/com.ibm.websphere.extended.ejb /additionalProjectFacets Generates this: faceted-project fixed facet=jst.java/ fixed facet=jst.utility/ installed facet=jst.utility version=1.0/ installed facet=jst.java version=5.0/ installed facet=com.ibm.websphere.extended.ejb version=6.1/ installed facet=jst.ejb version=2.1/ /faceted-project Which is a little more correct. I consider this a bug, as the facets (by their very definition) are unique and should not be repeated. Additionally, when compared to a RSA (V7) generated one, it is missing the standard XML header: ?xml version=1.0 encoding=UTF-8? Also, where does the jst.utility facet come from? It's inclusion is getting in the way of RSA recognising it as a true J2EE
maven-eclipse-plugin: Facet Issues
Hi All. Using V2.5.1 of the maven-eclipse-plugin, I have some issues in getting the generated artifacts being correct. Take this section of the POM: additionalProjectFacets jst.java5.0/jst.java jst.ejb2.1/jst.ejb com.ibm.websphere.extended.ejb6.1/com.ibm.websphere.extended.ejb /additionalProjectFacets Generates this: faceted-project fixed facet=jst.java/ fixed facet=jst.utility/ installed facet=jst.utility version=1.0/ installed facet=jst.java version=5.0/ installed facet=com.ibm.websphere.extended.ejb version=6.1/ installed facet=jst.ejb version=2.1/ installed facet=jst.java version=5.0/ /faceted-project You'll see that the jst.java facet is in there twice. Removing the facet from the list: additionalProjectFacets jst.ejb2.1/jst.ejb com.ibm.websphere.extended.ejb6.1/com.ibm.websphere.extended.ejb /additionalProjectFacets Generates this: faceted-project fixed facet=jst.java/ fixed facet=jst.utility/ installed facet=jst.utility version=1.0/ installed facet=jst.java version=5.0/ installed facet=com.ibm.websphere.extended.ejb version=6.1/ installed facet=jst.ejb version=2.1/ /faceted-project Which is a little more correct. I consider this a bug, as the facets (by their very definition) are unique and should not be repeated. Additionally, when compared to a RSA (V7) generated one, it is missing the standard XML header: ?xml version=1.0 encoding=UTF-8? Also, where does the jst.utility facet come from? It's inclusion is getting in the way of RSA recognising it as a true J2EE component project (the EJB Deployment descriptor tree element does not display in the Project Explorer view in the J2EE Perspective). This is the complete RSA generated one, for reference: ?xml version=1.0 encoding=UTF-8? faceted-project runtime name=WebSphere Application Server v6.1/ fixed facet=jst.ejb/ fixed facet=jst.java/ installed facet=jst.ejb version=2.1/ installed facet=jst.java version=5.0/ installed facet=com.ibm.websphere.extended.ejb version=6.1/ /faceted-project (Which raises another question, how do we specify the runtime items and if something is fixed or not?) However, to get it to be correctly recognised, all we need is this: faceted-project fixed facet=jst.java/ installed facet=jst.java version=5.0/ installed facet=jst.ejb version=2.1/ installed facet=com.ibm.websphere.extended.ejb version=6.1/ /faceted-project I hope that you can help. -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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
pom settings for RSA V7 EJB project settings
For those of you who are interested... Using the maven-eclipse-plugin V2.5.1: This is what I have for an EJB project. build plugins plugin artifactIdmaven-eclipse-plugin/artifactId configuration wtpversion1.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.module.container/classpathContainer /classpathContainers additionalProjectFacets jst.java5.0/jst.java jst.ejb2.1/jst.ejb com.ibm.websphere.extended.ejb6.1/ com.ibm.websphere.extended.ejb /additionalProjectFacets /configuration /plugin /plugins /build You'll need to edit the org.eclipse.wst.common.project.facet.core.xml file and remove the references to the jst.util facets and you'll be fine with RSA V7. (so far at least) -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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: wtpversion = R7
Thank you for the heads up. -Chris Arnaud HERITIER [EMAIL PROTECTED] wrote on 14/05/2008 17:54:33: We have to update the documentation (we have an issue about it) http://maven.apache.org/plugins/maven-eclipse-plugin/wtp.html R7 is an old old old version of WTP. I think it was the one bundled in eclipse 3.0 (maybe 2.3, I don't remember) Arnaud On Wed, May 14, 2008 at 3:24 AM, [EMAIL PROTECTED] wrote: Hi All, There is next to no documentation on this, other than simply listing that it exists. Is this for RSA V7? -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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] The following message has been automatically added by the Internet mail gateway to comply with the Group's Information Security requirements. This e-mail has arrived via the Internet, and therefore you should be cautious about its origin and content. Replies which contain sensitive information and / or legal/contractual obligations are particularly vulnerable. In these cases you should not reply unless you are authorised to do so, and adequate encryption is employed. If you have any questions, please contact the IS Service Desk. ** 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: RA V7 Maven Support
I think that the best way to think of the differences is like this: RSA = RAD + UML Modeling + a few other goods. Ie, what works with RAD (from a pluging point of view) should work fine with RSA. -Chris Arnaud HERITIER [EMAIL PROTECTED] wrote on 14/05/2008 17:56:23: people had use this plugin with RAD 7 (with more or less success) but I never saw a thread about RSA. Arnaud On Wed, May 14, 2008 at 3:27 AM, [EMAIL PROTECTED] wrote: Hi All, I am attempting to, and so far it has been a rather futile effort, to set up the maven-eclipse-plugin settings so that it can create an EJB project as it I had manually created an EJB Project inside RSA V7 itself. Ideally targeting WAS 6.1. Eventually it will be set up as an archetype. Has anyone managed to do this? -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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] The following message has been automatically added by the Internet mail gateway to comply with the Group's Information Security requirements. This e-mail has arrived via the Internet, and therefore you should be cautious about its origin and content. Replies which contain sensitive information and / or legal/contractual obligations are particularly vulnerable. In these cases you should not reply unless you are authorised to do so, and adequate encryption is employed. If you have any questions, please contact the IS Service Desk. ** 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven-eclipse-plugin: Facet Issues
Done. http://jira.codehaus.org/browse/MECLIPSE-449 However, this leads me to another question. We can specify the classpath container entries, fine, and that works. However, doesn't this conflict with the dependencies section (which in turn generates the .classpath entries which will result in duplicate entried). Adding in the classpath container entries fine fine from within eclipse. However, what happens when you are attempting to build the app outside of eclipse (ie, from Hudson or other similar CI tool). I do not have a good handle on how all of this is meant to work. -Chris Arnaud HERITIER [EMAIL PROTECTED] wrote on 14/05/2008 18:03:17: Hi Chris, Thanks a lot for your feedback. Can you open an issue in Jira. We'll try to fix this issue in the next release. I think we have several others issues about facet issues. Arnaud On Wed, May 14, 2008 at 8:42 AM, [EMAIL PROTECTED] wrote: Hi All. Using V2.5.1 of the maven-eclipse-plugin, I have some issues in getting the generated artifacts being correct. Take this section of the POM: additionalProjectFacets jst.java5.0/jst.java jst.ejb2.1/jst.ejb com.ibm.websphere.extended.ejb6.1/com.ibm.websphere.extended.ejb /additionalProjectFacets Generates this: faceted-project fixed facet=jst.java/ fixed facet=jst.utility/ installed facet=jst.utility version=1.0/ installed facet=jst.java version=5.0/ installed facet=com.ibm.websphere.extended.ejb version=6.1/ installed facet=jst.ejb version=2.1/ installed facet=jst.java version=5.0/ /faceted-project You'll see that the jst.java facet is in there twice. Removing the facet from the list: additionalProjectFacets jst.ejb2.1/jst.ejb com.ibm.websphere.extended.ejb6.1/com.ibm.websphere.extended.ejb /additionalProjectFacets Generates this: faceted-project fixed facet=jst.java/ fixed facet=jst.utility/ installed facet=jst.utility version=1.0/ installed facet=jst.java version=5.0/ installed facet=com.ibm.websphere.extended.ejb version=6.1/ installed facet=jst.ejb version=2.1/ /faceted-project Which is a little more correct. I consider this a bug, as the facets (by their very definition) are unique and should not be repeated. Additionally, when compared to a RSA (V7) generated one, it is missing the standard XML header: ?xml version=1.0 encoding=UTF-8? Also, where does the jst.utility facet come from? It's inclusion is getting in the way of RSA recognising it as a true J2EE component project (the EJB Deployment descriptor tree element does not display in the Project Explorer view in the J2EE Perspective). This is the complete RSA generated one, for reference: ?xml version=1.0 encoding=UTF-8? faceted-project runtime name=WebSphere Application Server v6.1/ fixed facet=jst.ejb/ fixed facet=jst.java/ installed facet=jst.ejb version=2.1/ installed facet=jst.java version=5.0/ installed facet=com.ibm.websphere.extended.ejb version=6.1/ /faceted-project (Which raises another question, how do we specify the runtime items and if something is fixed or not?) However, to get it to be correctly recognised, all we need is this: faceted-project fixed facet=jst.java/ installed facet=jst.java version=5.0/ installed facet=jst.ejb version=2.1/ installed facet=com.ibm.websphere.extended.ejb version=6.1/ /faceted-project I hope that you can help. -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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] The following message has been automatically added by the Internet mail gateway to comply with the Group's Information Security requirements. This e-mail has arrived via the Internet, and therefore you should be cautious about its origin and content. Replies which contain sensitive information and / or legal/contractual obligations are particularly vulnerable. In these
classpath container issues
Given this fragment: 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 classpathContainerorg.eclipse.jst.j2ee.internal.module.container/ classpathContainer /classpathContainers running mvn eclipse:eclipse will generate the appriate .classpath file: classpath classpathentry kind=src path=src/main/java/ classpathentry kind=src path=src/test/java output= target/test-classes/ classpathentry kind=output path=target/classes/ classpathentry kind=con path= org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/WebSphere v6.1 JRE/ classpathentry kind=con path= org.eclipse.jst.server.core.container/com.ibm.ws.ast.st.runtime.runtimeTarget.v61/was.base.v61 / classpathentry kind=con path= org.eclipse.jst.j2ee.internal.module.container/ classpathentry kind=var path= M2_REPO/junit/junit/3.8.1/junit-3.8.1.jar sourcepath= M2_REPO/junit/junit/3.8.1/junit-3.8.1-sources.jar/ /classpath Any dependencies listed in the POM will all be added as a variable extension using the M2_REPO variable. This leads me to a question. We can specify the classpath container entries, fine, and that works. However, doesn't this conflict with the dependencies section (which in turn generates the .classpath entries which will result in duplicate entried). Adding in the classpath container entries fine fine from within eclipse. However, what happens when you are attempting to build the app outside of eclipse (ie, from Hudson or other similar CI tool). I do not have a good handle on how all of this is meant to work. -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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AW: maven-eclipse-plugin: Facet Issues
Hi Kuno, Thanks for that, however it does not work for me. However, I'll see if I can incorporate the server settings etc. -Chris Baeriswyl Kuno - Extern (IT-BA-MV) [EMAIL PROTECTED] wrote on 14/05/2008 19:32:24: Hello Chris, for me, following works: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-eclipse-plugin/artifactId configuration wtpdefaultserverWebSphere Application Server v6.1/wtpdefaultserver wtpmanifesttrue/wtpmanifest wtpapplicationxmltrue/wtpapplicationxml wtpversion1.5/wtpversion additionalBuildcommands buildcommandorg. eclipse.jdt.core.javabuilder/buildcommand buildcommandorg. eclipse.wst.common.project.facet.core.builder/buildcommand buildcommandorg. eclipse.wst.validation.validationbuilder/buildcommand /additionalBuildcommands additionalProjectnatures projectnatureorg. eclipse.jdt.core.javanature/projectnature projectnatureorg. eclipse.wst.common.project.facet.core.nature/projectnature projectnatureorg. eclipse.wst.common.modulecore.ModuleCoreNature/projectnature /additionalProjectnatures classpathContainers classpathContainerorg. eclipse.jdt.launching.JRE_CONTAINER/classpathContainer classpathContainerorg. eclipse.jst.j2ee.internal.module.container/classpathContainer /classpathContainers /configuration /plugin Important: wtpdefaultserver and version must be defined. And the you must ensure to pass the runtime argument -Declipse.workspace to the eclipse:eclipse mojo. Kuno -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 14. Mai 2008 08:43 An: users@maven.apache.org Cc: [EMAIL PROTECTED] Betreff: maven-eclipse-plugin: Facet Issues Hi All. Using V2.5.1 of the maven-eclipse-plugin, I have some issues in getting the generated artifacts being correct. Take this section of the POM: additionalProjectFacets jst.java5.0/jst.java jst.ejb2.1/jst.ejb com.ibm.websphere.extended.ejb6.1/com.ibm.websphere.extended.ejb /additionalProjectFacets Generates this: faceted-project fixed facet=jst.java/ fixed facet=jst.utility/ installed facet=jst.utility version=1.0/ installed facet=jst.java version=5.0/ installed facet=com.ibm.websphere.extended.ejb version=6.1/ installed facet=jst.ejb version=2.1/ installed facet=jst.java version=5.0/ /faceted-project You'll see that the jst.java facet is in there twice. Removing the facet from the list: additionalProjectFacets jst.ejb2.1/jst.ejb com.ibm.websphere.extended.ejb6.1/com.ibm.websphere.extended.ejb /additionalProjectFacets Generates this: faceted-project fixed facet=jst.java/ fixed facet=jst.utility/ installed facet=jst.utility version=1.0/ installed facet=jst.java version=5.0/ installed facet=com.ibm.websphere.extended.ejb version=6.1/ installed facet=jst.ejb version=2.1/ /faceted-project Which is a little more correct. I consider this a bug, as the facets (by their very definition) are unique and should not be repeated. Additionally, when compared to a RSA (V7) generated one, it is missing the standard XML header: ?xml version=1.0 encoding=UTF-8? Also, where does the jst.utility facet come from? It's inclusion is getting in the way of RSA recognising it as a true J2EE component project (the EJB Deployment descriptor tree element does not display in the Project Explorer view in the J2EE Perspective). This is the complete RSA generated one, for reference: ?xml version=1.0 encoding=UTF-8? faceted-project runtime name=WebSphere Application Server v6.1/ fixed facet=jst.ejb/ fixed facet=jst.java/ installed facet=jst.ejb version=2.1/ installed facet=jst.java version=5.0/ installed facet=com.ibm.websphere.extended.ejb version=6.1/ /faceted-project (Which raises another question, how do we specify the runtime items and if something is fixed or not?) However, to get it to be correctly recognised, all we need is this: faceted-project fixed facet=jst.java/ installed facet=jst.java version=5.0/ installed
wtpversion = R7
Hi All, There is next to no documentation on this, other than simply listing that it exists. Is this for RSA V7? -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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RA V7 Maven Support
Hi All, I am attempting to, and so far it has been a rather futile effort, to set up the maven-eclipse-plugin settings so that it can create an EJB project as it I had manually created an EJB Project inside RSA V7 itself. Ideally targeting WAS 6.1. Eventually it will be set up as an archetype. Has anyone managed to do this? -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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven and Eclipse: getting started
And I've tried running mvn eclipse realizing that that is way too
naive as a starting point. I'm guessing that to create a Dynamic Web
Project under Maven control for use in Eclipse, I have to create a BLANK
PROJECT on the command line in Maven, but there's something about the
Eclipse workbench plugin that will give me all the right directories and
a fully WTP-armed POM. Then, I can copy (?) this blank somewhere and use
it ever after (or just use Maven to create a new blank every time I need
one)?
Look at archetypes.
(Hint: http://docs.codehaus.org/display/M2ECLIPSE/New+and+Noteworthy)
More importantly, have a look at:
http://www.sonatype.com/book/
Also, use this:
http://m2eclipse.codehaus.org/
The questions I'm looking to answer are:
- How do I invoke the Maven plugin inside Eclipse to tell Maven to
create me a fully WTP-armed POM?
mvn archetype:create ^
-DarchetypeGroupId=group id of the appropriate archetype ^
-DarchetypeArtifactId=aart. id of the appropriate archetype ^
-DarchetypeVersion=1.0-SNAPSHOT ^
-DgroupId=Project Group Id ^
-DartifactId=Project Name
cd Project Name
mvn eclipse:eclipse
That will get you started.
We've set up a parent POM that has this section in it:
build
pluginManagement
plugins
plugin
artifactIdmaven-eclipse-plugin/artifactId
version${maven-eclipse-plugin.version}/version
configuration
downloadSources${ide.download.sources}/
downloadSources
downloadJavadocs${ide.download.javadoc}/
downloadJavadocs
wtpversion${eclipse.wtp.version}/wtpversion
/configuration
/plugin
/plugins
/pluginManagement
/build
properties
maven-eclipse-plugin.version2.5.1/maven-eclipse-plugin.version
ide.download.sourcestrue/ide.download.sources
ide.download.javadocfalse/ide.download.javadoc
eclipse.wtp.version1.5/eclipse.wtp.version
/properties
- What does it leave lying around that tells me this has succeeded?
- What Maven command do I use on the Windoz/DOS command line to
create this mythical project with Eclipse .classpath/.metadata/etc.
stuff in it?
That is what the mvn eclipse:eclipse tasks does (by it's very definition)
- How do I import the new project into Eclipse so I can get
developing?
Import it like any other (existing) eclipse project...
- Will the full-octane, WTP-armed POM and project hierarchy come
with /faces-config.xml/, /web.xml/, etc.
Depends on what archetypes you've used/parent pom's you've inherited from.
I have heard that this is possible and that Maven is going to do all
these cools things for me, but after hours of research reading link
after followed link, I've only stumbled on more or less how to install
and nothing about how to use. I'm not looking for anyone to do the work
for me, but a list of URLs or some pointers would be greatly helpful.
Not not that far ahead of you myself, and yes it is painfully difficult...
**
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.
**
RE: Checkstyle Versions
Hi Brian. Thank you very much for that. I'd asked before but to no avail. Thanks for taking the time to answer. -Chris Brian E. Fox [EMAIL PROTECTED] wrote on 24/04/2008 04:08:18: Chris, this is a commonly requested feature and you can see more info here: http://blogs.sonatype.com/brian/2008/04/23/120896598.html -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 22, 2008 9:00 PM To: Maven Users List Subject: Checkstyle Versions Hi All. The blurb on Maven 2.0.9 stated that you could force a specific version of a jar, mainly to get newer versions, and the specifically listed checkstyle (amongst others). How do you actually do it? The maven checkstyle plugin uses checkstyle 4.1 and 4.4 is available (and that is what I'm using). Can someone please help me out. Ta. -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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] The following message has been automatically added by the Internet mail gateway to comply with the Group's Information Security requirements. This e-mail has arrived via the Internet, and therefore you should be cautious about its origin and content. Replies which contain sensitive information and / or legal/contractual obligations are particularly vulnerable. In these cases you should not reply unless you are authorised to do so, and adequate encryption is employed. If you have any questions, please contact the IS Service Desk. ** 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Checkstyle Versions
Hi All. The blurb on Maven 2.0.9 stated that you could force a specific version of a jar, mainly to get newer versions, and the specifically listed checkstyle (amongst others). How do you actually do it? The maven checkstyle plugin uses checkstyle 4.1 and 4.4 is available (and that is what I'm using). Can someone please help me out. Ta. -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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How can I generate a POM file for dependency?
For instance: mvn install:install-file -Dfile=doccheck.jar -DgroupId=com.sun.tools.doclets -DartifactId=doccheck -Dversion=1.2b2 -Dpackaging=jar -DgeneratePom=true -Chris youhaodeyi [EMAIL PROTECTED] wrote on 15/04/2008 15:42:28: Some dependencies downloaded by Maven would not contain POM file, so every time I run Maven compile, it will try to get the POM file from remote repository. How can I generate a POM file for them? ** 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. **
Re: Dependency Relationships in EARs
What is the output of: mvn dependency:tree -Chris David Weintraub [EMAIL PROTECTED] 11/04/2008 10:23 Please respond to Maven Users List users@maven.apache.org To Maven Users List users@maven.apache.org cc Subject Re: Dependency Relationships in EARs Sure: Here's the POM for the Foundation: project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdcom.solbright/groupId artifactIdfoundation/artifactId packagingjar/packaging version0.1/version namefoundation/name urlhttp://maven.apache.org/url dependencies dependency groupIdjunit/groupId artifactIdjunit/artifactId version3.8.1/version scopetest/scope /dependency dependency groupIdjboss/groupId artifactIdjboss-j2ee/artifactId version4.0.0/version /dependency dependency groupIdlog4j/groupId artifactIdlog4j/artifactId version1.2.4/version /dependency dependency groupIdjdom/groupId artifactIdjdom/artifactId versionb7/version /dependency dependency groupIdjavax.servlet/groupId artifactIdjsp-api/artifactId version2.0/version /dependency dependency groupIdorg.log4j/groupId artifactIdlog4j/artifactId version0.0.1/version /dependency dependency groupIdcom.enterprisedt/groupId artifactIdedtFTPj/artifactId version1.5.3/version /dependency dependency groupIdcom.oracle/groupId artifactIdojdbc14/artifactId version10.2.0.2/version /dependency dependency groupIdde.dankomannhaupt/groupId artifactIdjdbcappender/artifactId version2.1.01/version /dependency dependency groupIdcom.oracle/groupId artifactIdxsu/artifactId version1.2/version /dependency dependency groupIdorg.springframework/groupId artifactIdspring-jdbc/artifactId version1.2.8/version /dependency dependency groupIdcom.lowagie/groupId artifactIditext/artifactId version1.3/version /dependency dependency groupIdnet.sourceforge/groupId artifactIdjox/artifactId version1.17b3/version /dependency dependency groupIdorg.apache.xmlgraphics/groupId artifactIdfop/artifactId version0.20.4/version /dependency dependency groupIdgnu-regexp/groupId artifactIdgnu-regexp/artifactId version1.1.4/version /dependency dependency groupIdcom.oreilly/groupId artifactIdservlet-cos/artifactId version20Nov2000/version /dependency dependency groupIdcommons-beanutils/groupId artifactIdcommons-beanutils/artifactId version1.6/version /dependency dependency groupIdjavax.activation/groupId artifactIdactivation/artifactId version1.1/version /dependency /dependencies /project And here's the sample EAR: project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdcom.solbright/groupId artifactIdtest-ear/artifactId packagingear/packaging version1.0-SNAPSHOT/version nametest-ear/name urlhttp://maven.apache.org/url dependencies dependency groupIdcom.solbright/groupId artifactIdfoundation/artifactId version0.1/version /dependency dependency groupIdjunit/groupId artifactIdjunit/artifactId version3.8.1/version scopetest/scope /dependency /dependencies /project There's nothing in the EAR except for this dependency of foundation.jar which is stored in our company's remote repository. I saw that the pom.xml for Foundation is stored in the foundation.jar, and I thought that's where it gets the dependency list from. I'm thinking that the problem isn't in the POM as much as it is in the repository setup. On Thu, Apr 10, 2008 at 4:49 PM, Wayne Fay [EMAIL PROTECTED] wrote: The dependencies of your dependencies are called transitive dependencies. Normally, Maven2 is able to figure out what you need and build/package things properly. So, you must be doing something wrong to get these results. Can you send the 2 pom.xml files you
Maven 2 Bug? Not Processing Children
Following Nick's suggestion to how to report a bug: On this issue: http://www.nabble.com/Class-Path-Test-Problem.-tt16556171s177.html I have solved the problem. If the consolidated pom has a scope in it, it fails to resolve it's child dependencies. Consider this from a top level pom: dependency groupIdcom.ibm.db2.jcc/groupId artifactIdlibrary/artifactId versionV8-FP15/version typepom/type scopetest/scope /dependency This is what works: ?xml version=1.0 encoding=UTF-8? project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi= http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation= http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdcom.ibm.db2.jcc/groupId artifactIdlibrary/artifactId versionV8-FP15/version packagingpom/packaging nameMaster POM for the DB2 Universal Drivers from V8 FP15./name descriptionPOM was created from install:install-file/description dependencies dependency groupIdcom.ibm.db2.jcc/groupId artifactIddb2jcc/artifactId versionV8-FP15/version /dependency dependency groupIdcom.ibm.db2.jcc/groupId artifactIddb2jcc_license_cisuz/artifactId versionV8-FP15/version /dependency dependency groupIdcom.ibm.db2.jcc/groupId artifactIddb2jcc_license_cu/artifactId versionV8-FP15/version /dependency /dependencies /project If I add a scope of anything to each dependency, it fails to resolve it's children. I consider this a bug. If you are depending on a pom of type pom and the scope attribute is not needed (it should be specified in the top level dependency definition), then it should be ignored. At the very least it should not cease processing it's children. This is the broken one, for reference: ?xml version=1.0 encoding=UTF-8? project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi= http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation= http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdcom.ibm.db2.jcc/groupId artifactIdlibrary/artifactId versionV8-FP15/version packagingpom/packaging nameMaster POM for the DB2 Universal Drivers from V8 FP15./name descriptionPOM was created from install:install-file/description dependencies dependency groupIdcom.ibm.db2.jcc/groupId artifactIddb2jcc/artifactId versionV8-FP15/version scoperuntime/scope /dependency dependency groupIdcom.ibm.db2.jcc/groupId artifactIddb2jcc_license_cisuz/artifactId versionV8-FP15/version scoperuntime/scope /dependency dependency groupIdcom.ibm.db2.jcc/groupId artifactIddb2jcc_license_cu/artifactId versionV8-FP15/version scoperuntime/scope /dependency /dependencies /project -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. **
Newer Jar Override
Hi All. The org.apache.maven.plugins:maven-checkstyle-plugin dependon upon checkstyle 4.1. I'd like to use checkstyle 4.4 (that matches by eclipse version). Is there any way to override it and get it to use 4.4 instead of 4.1? TIA, -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. **
Class Path Test Problem.
Hello All. I am having an issue in attempting to set up a consolidated dependencies POM. I am trying to set up a single POM that represents the DB2 Universal Drivers, which for me, basically consists of three different jars. Each of the three jars have been added into the repo and are working correctly. Everything works in my primary POM if I do this: dependency groupIdcom.ibm.db2.jcc/groupId artifactIddb2jcc/artifactId versionV8-FP15/version scoperuntime/scope /dependency dependency groupIdcom.ibm.db2.jcc/groupId artifactIddb2jcc_license_cisuz/artifactId versionV8-FP15/version scoperuntime/scope /dependency dependency groupIdcom.ibm.db2.jcc/groupId artifactIddb2jcc_license_cu/artifactId versionV8-FP15/version scoperuntime/scope /dependency I have set up a library POM, that is referenced like this: dependency groupIdcom.ibm.db2.jcc/groupId artifactIdlibrary/artifactId versionV8-FP15/version scopetest/scope typepom/type /dependency At this point it does not work. Interestingly enough, if I use the same library pom as a parent, it **DOES** work, which makes me think that everything in all of the POMs is actually correct. This is the parent section: parent groupIdcom.ibm.db2.jcc/groupId artifactIdlibrary/artifactId versionV8-FP15/version /parent If I run mvn dependency:tree I get: (either as the three individual deps or as a parent) [INFO] [INFO] Building test [INFO]task-segment: [dependency:tree] [INFO] [INFO] [dependency:tree] [INFO] au.com.warpspeed.test:test:jar:1.0-SNAPSHOT [INFO] +- com.ibm.db2.jcc:db2jcc:jar:V8-FP15:test [INFO] +- com.ibm.db2.jcc:db2jcc_license_cisuz:jar:V8-FP15:test [INFO] +- com.ibm.db2.jcc:db2jcc_license_cu:jar:V8-FP15:test [INFO] +- junit:junit:jar:3.8.1:test [INFO] +- jdom:jdom:jar:1.0:compile [INFO] +- log4j:log4j:jar:1.2.14:compile [INFO] +- javax.servlet:servlet-api:jar:2.4:provided [INFO] +- jboss:jboss-j2ee:jar:4.0.2:compile [INFO] +- maven-plugins:maven-cobertura-plugin:jar:1.4:compile [INFO] | +- net.sourceforge.cobertura:cobertura:jar:1.9:compile [INFO] | | \- org.apache.ant:ant:jar:1.7.0:compile [INFO] | | \- org.apache.ant:ant-launcher:jar:1.7.0:compile [INFO] | +- oro:oro:jar:2.0.8:compile [INFO] | +- asm:asm:jar:2.2.1:compile [INFO] | +- asm:asm-tree:jar:2.2.1:compile [INFO] | \- commons-jelly:commons-jelly-tags-log:jar:1.0:compile [INFO] +- javax.mail:mail:jar:1.4:compile [INFO] | \- javax.activation:activation:jar:1.1:compile [INFO] +- javax.servlet.jsp:jsp-api:jar:2.1:compile [INFO] +- au.com.warpspeed:kleinbottle:jar:0.1:test [INFO] +- Acme:Acme:jar:1.0:compile [INFO] \- com.javaexchange:dbConnectionBroker:jar:1.0:compile [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 7 seconds [INFO] Finished at: Tue Apr 08 03:56:02 GMT 2008 [INFO] Final Memory: 9M/17M [INFO] If I run the tree with the consolidated POM, I get: [INFO] [INFO] Building test [INFO]task-segment: [dependency:tree] [INFO] [INFO] [dependency:tree] [INFO] au.com.warpspeed.test:test:jar:1.0-SNAPSHOT [INFO] +- junit:junit:jar:3.8.1:test [INFO] +- jdom:jdom:jar:1.0:compile [INFO] +- log4j:log4j:jar:1.2.14:compile [INFO] +- javax.servlet:servlet-api:jar:2.4:provided [INFO] +- jboss:jboss-j2ee:jar:4.0.2:compile [INFO] +- maven-plugins:maven-cobertura-plugin:jar:1.4:compile [INFO] | +- net.sourceforge.cobertura:cobertura:jar:1.9:compile [INFO] | | \- org.apache.ant:ant:jar:1.7.0:compile [INFO] | | \- org.apache.ant:ant-launcher:jar:1.7.0:compile [INFO] | +- oro:oro:jar:2.0.8:compile [INFO] | +- asm:asm:jar:2.2.1:compile [INFO] | +- asm:asm-tree:jar:2.2.1:compile [INFO] | \- commons-jelly:commons-jelly-tags-log:jar:1.0:compile [INFO] +- javax.mail:mail:jar:1.4:compile [INFO] | \- javax.activation:activation:jar:1.1:compile [INFO] +- javax.servlet.jsp:jsp-api:jar:2.1:compile [INFO] +- au.com.warpspeed:kleinbottle:jar:0.1:test [INFO] +- Acme:Acme:jar:1.0:compile [INFO] +- com.javaexchange:dbConnectionBroker:jar:1.0:compile [INFO] \- com.ibm.db2.jcc:library:pom:V8-FP15:test [INFO]
