RE: Continuum version 103 (maven2)
See http://maven.apache.org/continuum/faqs.html##how-does-continuum-detect-a-suc cessful-build Sounds like the same issue? Apologies if I'm wrong. James -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: 28 August 2007 16:59 To: continuum-users@maven.apache.org Subject: Re: Continuum version 103 (maven2) We don't have an entry in the faq about the bug in mvn.bat from maven 2.0.7 (http://jira.codehaus.org/browse/MNG-3084 ) James Clinton a écrit : Opps - should of read my original post!. Anwser is for Windows the mvn.bat file needs to be altered...I didn't read the faq's properly. -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: 28 August 2007 16:48 To: continuum-users@maven.apache.org Subject: Re: Continuum version 103 (maven2) Do you use maven 2.0.7? James Clinton a écrit : Hello, I have a project structure like so: - parent - child - child Parent pom is them loaded into CI and the projects are detected. It builds fine, but if there is a compilation error, the status of the build is still 'success'. Is this a known issue? James DISCLAIMER: This e-mail is confidential and may also be legally privileged. If you are not the intended recipient, use of the information contained in this e-mail (including disclosure, copying or distribution) is prohibited and may be unlawful. Please inform the sender and delete the message immediately from your system. This e-mail is attributed to the sender and may not necessarily reflect the views of the Patsystems Group and no member of the Patsystems Group accepts any liability for any action taken in reliance on the contents of this e-mail (other than where it has a legal or regulatory obligation to do so) or for the consequences of any computer viruses which may have been transmitted by this e-mail. The Patsystems Group comprises Patsystems plc and its subsidiary group of companies. DISCLAIMER: This e-mail is confidential and may also be legally privileged. If you are not the intended recipient, use of the information contained in this e-mail (including disclosure, copying or distribution) is prohibited and may be unlawful. Please inform the sender and delete the message immediately from your system. This e-mail is attributed to the sender and may not necessarily reflect the views of the Patsystems Group and no member of the Patsystems Group accepts any liability for any action taken in reliance on the contents of this e-mail (other than where it has a legal or regulatory obligation to do so) or for the consequences of any computer viruses which may have been transmitted by this e-mail. The Patsystems Group comprises Patsystems plc and its subsidiary group of companies. DISCLAIMER: This e-mail is confidential and may also be legally privileged. If you are not the intended recipient, use of the information contained in this e-mail (including disclosure, copying or distribution) is prohibited and may be unlawful. Please inform the sender and delete the message immediately from your system. This e-mail is attributed to the sender and may not necessarily reflect the views of the Patsystems Group and no member of the Patsystems Group accepts any liability for any action taken in reliance on the contents of this e-mail (other than where it has a legal or regulatory obligation to do so) or for the consequences of any computer viruses which may have been transmitted by this e-mail. The Patsystems Group comprises Patsystems plc and its subsidiary group of companies.
RE: Continuum version 103 (maven2)
Ok - many thanks. -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: 28 August 2007 17:07 To: continuum-users@maven.apache.org Subject: Re: Continuum version 103 (maven2) yes and no. The problem is the same but not the patch to do, This entry is for an old maven version The fixed script for maven 2.0.7 is : https://svn.apache.org/repos/asf/maven/components/branches/maven-2.0.x/maven -core/src/bin/mvn.bat Emmanuel James Clinton a écrit : See http://maven.apache.org/continuum/faqs.html##how-does-continuum-detect -a-suc cessful-build Sounds like the same issue? Apologies if I'm wrong. James -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: 28 August 2007 16:59 To: continuum-users@maven.apache.org Subject: Re: Continuum version 103 (maven2) We don't have an entry in the faq about the bug in mvn.bat from maven 2.0.7 (http://jira.codehaus.org/browse/MNG-3084 ) James Clinton a écrit : Opps - should of read my original post!. Anwser is for Windows the mvn.bat file needs to be altered...I didn't read the faq's properly. -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: 28 August 2007 16:48 To: continuum-users@maven.apache.org Subject: Re: Continuum version 103 (maven2) Do you use maven 2.0.7? James Clinton a écrit : Hello, I have a project structure like so: - parent - child - child Parent pom is them loaded into CI and the projects are detected. It builds fine, but if there is a compilation error, the status of the build is still 'success'. Is this a known issue? James DISCLAIMER: This e-mail is confidential and may also be legally privileged. If you are not the intended recipient, use of the information contained in this e-mail (including disclosure, copying or distribution) is prohibited and may be unlawful. Please inform the sender and delete the message immediately from your system. This e-mail is attributed to the sender and may not necessarily reflect the views of the Patsystems Group and no member of the Patsystems Group accepts any liability for any action taken in reliance on the contents of this e-mail (other than where it has a legal or regulatory obligation to do so) or for the consequences of any computer viruses which may have been transmitted by this e-mail. The Patsystems Group comprises Patsystems plc and its subsidiary group of companies. DISCLAIMER: This e-mail is confidential and may also be legally privileged. If you are not the intended recipient, use of the information contained in this e-mail (including disclosure, copying or distribution) is prohibited and may be unlawful. Please inform the sender and delete the message immediately from your system. This e-mail is attributed to the sender and may not necessarily reflect the views of the Patsystems Group and no member of the Patsystems Group accepts any liability for any action taken in reliance on the contents of this e-mail (other than where it has a legal or regulatory obligation to do so) or for the consequences of any computer viruses which may have been transmitted by this e-mail. The Patsystems Group comprises Patsystems plc and its subsidiary group of companies. DISCLAIMER: This e-mail is confidential and may also be legally privileged. If you are not the intended recipient, use of the information contained in this e-mail (including disclosure, copying or distribution) is prohibited and may be unlawful. Please inform the sender and delete the message immediately from your system. This e-mail is attributed to the sender and may not necessarily reflect the views of the Patsystems Group and no member of the Patsystems Group accepts any liability for any action taken in reliance on the contents of this e-mail (other than where it has a legal or regulatory obligation to do so) or for the consequences of any computer viruses which may have been transmitted by this e-mail. The Patsystems Group comprises Patsystems plc and its subsidiary group of companies. DISCLAIMER: This e-mail is confidential and may also be legally privileged. If you are not the intended recipient, use of the information contained in this e-mail (including disclosure, copying or distribution) is prohibited and may be unlawful. Please inform the sender and delete the message immediately from your system. This e-mail is attributed to the sender and may not necessarily reflect the views of the Patsystems Group and no member of the Patsystems Group accepts any liability for any action taken in reliance on the contents of this e-mail (other than where it has a legal or regulatory obligation to do so) or for the consequences of any computer viruses which may have been transmitted by this e-mail. The Patsystems Group comprises Patsystems plc and its subsidiary group of companies.
RE: Community review of the next commons-logging pom
Wayne Fay wrote on Monday, August 27, 2007 8:55 PM: A couple comments... take them or not, entirely your choice: 1. The properties at the bottom -- any reason you aren't just configuring maven-compiler-plugin instead? Although not done here, but you need the same values configuring the javadoc plugin ... and that one you might have to configure in two places ;-) [snip] Other topics already answered by Dennis, Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Community review of the next commons-logging pom
Hi Michael, Michael McCallum wrote on Tuesday, August 28, 2007 12:34 AM: IMO the log4j, logkit, avalon dependencies all need to go... I as I imagine most people do only use one logging implementation in the deployed systems why introduce a dependency on several implementations at the top level? They are optional, so you do not depend on them transitively. check out http://www.slf4j.com for an appropriate break up of the artifacts and use cases Commons logging has a different philosophy. But this is OT for this list. I've generally stopped using dependencyManagement in favour of dependency composition Why? Only with dependencyManagement you're able to manage transitive versions. - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Failing to add a POI dependency
Hello, Here is what I get now that I have changed to org.apache.poi (groupId) and turned on the -e switch: C:\dev\calyonfinancial\ProtideWebmvn -e install + Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] [INFO] Building ProtideWeb [INFO]task-segment: [install] [INFO] [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. Downloading: http://cvs/repository/org/apache/poi/poi/3.0.1-FINAL/poi-3.0.1-FINAL.pom [WARNING] Unable to get resource from repository calyonRepository ( http://cvs/repository) Downloading: http://repo1.maven.org/maven2/org/apache/poi/poi/3.0.1-FINAL/poi-3.0.1-FINAL.pom [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: org.apache.poi:poi Reason: Error getting POM for 'org.apache.poi:poi' from the repository: Error transferring file org.apache.poi:poi:pom:3.0.1-FINAL from the specified remote repositories: central (http://repo1.maven.org/maven2), calyonRepository (http://cvs/repository), jboss repo (http://repository.jboss.com/maven2), maven2 repo (http://repo1.maven.org/maven2) [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Unable to get dependency information: Unable to read the metadata file for artifact ' org.apach e.poi:poi:jar': Error getting POM for 'org.apache.poi:poi' from the repository: Error transferring file org.apache.poi:poi:pom:3.0.1-FINAL from the specified remote repositories: central (http://repo1.maven.org/maven2), calyonRepository (http://cvs/repository), jboss repo (http://repository.jboss.com/maven2), maven2 repo (http://repo1.maven.org/maven2) org.apache.poi:poi:jar:3.0.1-FINAL from the specified remote repositories: central (http://repo1.maven.org/maven2), calyonRepository (http://cvs/repository), jboss repo (http://repository.jboss.com/maven2), maven2 repo (http://repo1.maven.org/maven2) Path to dependency: 1) com.calyonfinancial:protide:war:1.0-SNAPSHOT at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals( DefaultLifecycleExecutor.java:551) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle (DefaultLifecycleExecutor.java:475) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal( DefaultLifecycleExecutor.java:454) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures (DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute( DefaultLifecycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke( NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke( DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java :315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java :430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.artifact.resolver.ArtifactResolutionException: Unable to get dependency information: Unable to read the metadata file for artifact 'org.apache.poi:poi:jar': Error getting POM for 'org.apache.poi:poi' from the repository: Error transferring file org.apache.poi:poi:pom:3.0.1-FINAL from the specified remote repositories: central (http://repo1.maven.org/maven2), calyonRepository (http://cvs/repository), jboss repo (http://repository.jboss.com/maven2), maven2 repo (http://repo1.maven.org/maven2) org.apache.poi:poi:jar:3.0.1-FINAL from the specified remote repositories: central (http://repo1.maven.org/maven2), calyonRepository (http://cvs/repository), jboss repo (http://repository.jboss.com/maven2), maven2 repo (http://repo1.maven.org/maven2) Path to dependency: 1) com.calyonfinancial:protide:war:1.0-SNAPSHOT at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse( DefaultArtifactCollector.java:297) at
Re: Community review of the next commons-logging pom
On 8/28/07, Jörg Schaible [EMAIL PROTECTED] wrote: Michael McCallum wrote on Tuesday, August 28, 2007 12:34 AM: I've generally stopped using dependencyManagement in favour of dependency composition Why? Only with dependencyManagement you're able to manage transitive versions. Michael, could you expand on what you mean by dependency composition as I have the same question as Jörg. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Failing to add a POI dependency
Sorry: I had forgotten to include proxy info in my maven settings.xml. J. 2007/8/28, Julien Martin [EMAIL PROTECTED]: Hello, Here is what I get now that I have changed to org.apache.poi (groupId) and turned on the -e switch: C:\dev\calyonfinancial\ProtideWebmvn -e install + Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] [INFO] Building ProtideWeb [INFO]task-segment: [install] [INFO] [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. Downloading: http://cvs/repository/org/apache/poi/poi/3.0.1-FINAL/poi-3.0.1-FINAL.pom [WARNING] Unable to get resource from repository calyonRepository ( http://cvs/repository) Downloading: http://repo1.maven.org/maven2/org/apache/poi/poi/3.0.1-FINAL/poi-3.0.1-FINAL.pom [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: org.apache.poi:poi Reason: Error getting POM for 'org.apache.poi:poi' from the repository: Error transferring file org.apache.poi:poi:pom:3.0.1-FINAL from the specified remote repositories: central (http://repo1.maven.org/maven2), calyonRepository ( http://cvs/repository), jboss repo (http://repository.jboss.com/maven2), maven2 repo (http://repo1.maven.org/maven2 ) [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Unable to get dependency information: Unable to read the metadata file for artifact ' org.apach e.poi:poi:jar': Error getting POM for 'org.apache.poi:poi' from the repository: Error transferring file org.apache.poi:poi:pom:3.0.1-FINAL from the specified remote repositories: central ( http://repo1.maven.org/maven2), calyonRepository (http://cvs/repository), jboss repo ( http://repository.jboss.com/maven2), maven2 repo (http://repo1.maven.org/maven2) org.apache.poi:poi:jar:3.0.1-FINAL from the specified remote repositories: central (http://repo1.maven.org/maven2), calyonRepository (http://cvs/repository), jboss repo ( http://repository.jboss.com/maven2), maven2 repo (http://repo1.maven.org/maven2) Path to dependency: 1) com.calyonfinancial:protide:war:1.0-SNAPSHOT at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals( DefaultLifecycleExecutor.java:551) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle (DefaultLifecycleExecutor.java :475) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal (DefaultLifecycleExecutor.java:454) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures (DefaultLifecycleExecutor.java :306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute( DefaultLifecycleExecutor.java :140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke( NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke ( DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java :315) at org.codehaus.classworlds.Launcher.launch (Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode( Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.artifact.resolver.ArtifactResolutionException: Unable to get dependency information: Unable to read the metadata file for artifact 'org.apache.poi:poi:jar': Error getting POM for ' org.apache.poi:poi' from the repository: Error transferring file org.apache.poi:poi:pom:3.0.1-FINAL from the specified remote repositories: central (http://repo1.maven.org/maven2), calyonRepository ( http://cvs/repository), jboss repo (http://repository.jboss.com/maven2), maven2 repo (http://repo1.maven.org/maven2 ) org.apache.poi:poi:jar:3.0.1-FINAL from the specified remote repositories: central (http://repo1.maven.org/maven2), calyonRepository ( http://cvs/repository), jboss repo (http://repository.jboss.com/maven2), maven2 repo (http://repo1.maven.org/maven2 ) Path to dependency:
copernic Jeremy wants to chat
--- copernic Jeremy wants to stay in better touch using some of Google's coolest new products. If you already have Gmail or Google Talk, visit: http://mail.google.com/mail/b-343cfbc0c9-62ea441ab5-75f2453e951bd631 You'll need to click this link to be able to chat with copernic Jeremy. To get Gmail - a free email account from Google with over 2,800 megabytes of storage - and chat with copernic Jeremy, visit: http://mail.google.com/mail/a-343cfbc0c9-62ea441ab5-92122ff3f7 Gmail offers: - Instant messaging right inside Gmail - Powerful spam protection - Built-in search for finding your messages and a helpful way of organizing emails into conversations - No pop-up ads or untargeted banners - just text ads and related information that are relevant to the content of your messages All this, and its yours for free. But wait, there's more! By opening a Gmail account, you also get access to Google Talk, Google's instant messaging service: http://www.google.com/talk/ Google Talk offers: - Web-based chat that you can use anywhere, without a download - A contact list that's synchronized with your Gmail account - Free, high quality PC-to-PC voice calls when you download the Google Talk client Gmail and Google Talk are still in beta. We're working hard to add new features and make improvements, so we might also ask for your comments and suggestions periodically. We appreciate your help in making our products even better! Thanks, The Google Team To learn more about Gmail and Google Talk, visit: http://mail.google.com/mail/help/about.html http://www.google.com/talk/about.html (If clicking the URLs in this message does not work, copy and paste them into the address bar of your browser). - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven and macker plugin working??[UPDATES]
Thanks a lot Wayne.
We will try to use it as soon as possible (certainly during september) and
give you our feedback.
Rémy
2007/8/27, Wayne Fay [EMAIL PROTECTED]:
Just FYI... The code is available in the Mojo sandbox SVN and the site
was just deployed:
http://mojo.codehaus.org/macker-maven-plugin/
Wayne
On 8/20/07, Wayne Fay [EMAIL PROTECTED] wrote:
Jeremy et al,
I just checked in the first rough draft of macker-maven-plugin
v1.0.0-SNAPSHOT into Mojo sandbox.
Please grab the source, mvn -U install site, take a look at the site
docs to figure out how to use/configure it, and give it a try. You can
use mvn macker:macker package to test it on your own project once
you're included the plugin in buildplugins and installed the
plugin into your local repo.
As I said before, I appreciate your feedback.
Wayne
On 8/20/07, copernic Jeremy [EMAIL PROTECTED] wrote:
Hi Wayne,
That's a great news for the community!
Please let us informed ASAP when your M2 Macker plugin is available on
the
Mojo sandbox, and I'll try to give you some feedback of it.
regards,
Jeremy
On 8/17/07, Wayne Fay [EMAIL PROTECTED] wrote:
I've seen enough people asking for a M2 Macker plugin in the last
few
months/year that I finally decided to go ahead and write one myself.
In my limited testing, it works great, but I am not really a Macker
user so I'll need some feedback from people to improve it.
I will be submitting it to the Mojo sandbox shortly. I will post
another message when it is available -- you will need to download
the
code and mvn install it on your own machine before using it, just
like all plugins in the sandbox.
Just wanted to let you know. For now, the rules need to be stored in
an external macker-rules.xml file but I will see about allowing the
configuration directly in the pom.xml file as well.
Wayne
On 8/13/07, copernic Jeremy [EMAIL PROTECTED] wrote:
Hi all,
just to let you know some updates on my maven-macker-plugin issue:
I was not able to use the maven-macker-plugin available on repo1
http://repo1.maven.org/maven2/maven-plugins/maven-macker-plugin/
In fact I found a link explaining how to use Macker with Maven 2
through
the
maven-antrun-plugin.
http://docs.codehaus.org/display/MAVENUSER/Running+Macker+with+Maven+2
It works fine for now but I must admit that I would prefer using a
full
maven-macker-plugin without any ant tasks and build.xml files.
I think it could be great if we could define all the macker.xml's
rules
directly into the pom.xml of the maven project, or simply specify
the
location of the macker.xml file like the JettyConfig file style.
Something
like that:
plugin
groupIdmaven-plugins/groupId
artifactIdmaven-macker-plugin/artifactId
version0.4.2/version
configuration
mackerConfig${basedir}src/test/macker.xml/mackerConfig
/configuration
/plugin
or
plugin
groupIdmaven-plugins/groupId
artifactIdmaven-macker-plugin/artifactId
version0.4.2/version
configuration
macker
rulesets
ruleSet
accessRule
frommyClass/from
tosomeJavaClass/to
/accessRule
/ruleSet
/ruleSets
.
/macker
/configuration
/plugin
Maybe someday, someone who knows well Macker and the development
of
maven
plugins could try release one like that?!
Yet, the main Macker developper is aware of these issue and
suggestions
and
he told me that he would suggest them for a futur release so lets
hope!
regards,
Jeremy
-
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]
sorry!
Hi all, just to appologies for the last email, I accidently sent gmail invitation on the mailing list... sorry again and have a nice day! Jeremy
Re: Associate a default goal for a plugin and type the plugin name only on cmdln
not in maven 2. It was only in maven 1. In m2 you have to call aPlugin:aGoal Yes, it's not available in maven 2. I ask for a such feature some time ago and I had this reply that explain why it is not so easy. http://www.nabble.com/-Proposal--New-profile-activation-tf3240038s177.html#a9031422 Rémy
m2 ear plugin and resource filters.
Hi all,
I'm running Maven 2.0.7 and I'm trying to get resource filtering
working with m2's ear plugin. I have a file which I'm trying to get
certain properties replaced on a mvn package.
src/main/application/META-INF/geronimo.xml:
?xml version=1.0 encoding=UTF-8?
application
xmlns=http://geronimo.apache.org/xml/ns/j2ee/application-1.2;
xmlns:dep=http://geronimo.apache.org/xml/ns/deployment-1.2;
environment
xmlns=http://geronimo.apache.org/xml/ns/deployment-1.2;
moduleId
groupId${pom.groupId}/groupId
artifactId${pom.artifactId}/artifactId
version${pom.version}/version
typeear/type
/moduleId
/environment
/application
Ideally, the ${pom.*} properties are replaced with the values from
pom.xml; but for some reason, I can't seem to get it working with:
pom.xml:
?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/xsd/maven-4.0.0.xsd;
modelVersion4.0.0/modelVersion
nameEAR goal test/name
groupIdtest/groupId
artifactIdear-goal/artifactId
version1.0-SNAPSHOT/version
packagingear/packaging
build
resources
resource
filteringtrue/filtering
directorysrc/main/application/META-INF/directory
includes
include*.xml/include
/includes
/resource
/resources
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-ear-plugin/artifactId
configuration
version5/version
/configuration
/plugin
/plugins
/build
/project
Can anyone on the list see what I'm doing wrong? Any help appreciated.
Cheers.
--
Jonathan Chen [EMAIL PROTECTED]
--
Don't worry about avoiding temptation,
as you grow older, it starts avoiding you.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Why does this POM includes the sun's jsf jars??
Hello, Why does this POM includes the sun's jsf jars whereas I never asked for them?? I only want the Myfaces Jars... Can anyone help? How do I know which jars are included in a dependency? Thanks in advance, Julien Martin. 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.calyonfinancial/groupId artifactIdprotide/artifactId packagingwar/packaging version1.0-SNAPSHOT/version nameProtideWeb/name build sourceDirectorysrc/sourceDirectory outputDirectorybuild/outputDirectory finalNameProtideWeb/finalName plugins plugin artifactIdmaven-compiler-plugin/artifactId configuration source1.5/source target1.5/target /configuration /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-war-plugin/artifactId version2.0/version configuration warSourceDirectoryweb/warSourceDirectory /configuration /plugin /plugins /build dependencies dependency groupIdorg.hibernate/groupId artifactIdhibernate/artifactId version3.2.1.ga/version /dependency dependency groupIdorg.hibernate/groupId artifactIdhibernate-annotations/artifactId version3.2.0.ga/version /dependency dependency groupIdjavax.persistence/groupId artifactIdpersistence-api/artifactId version1.0/version /dependency dependency groupIdlog4j/groupId artifactIdlog4j/artifactId version1.2.14/version /dependency dependency groupIdcom.sun.xml.bind/groupId artifactIdjaxb-impl/artifactId version2.0/version /dependency dependency groupIdcom.sun.xml.bind/groupId artifactIdjaxb-xjc/artifactId version2.0/version /dependency dependency groupIdjavax.xml.bind/groupId artifactIdjaxb-api/artifactId version2.0/version /dependency !-- dependency groupIdorg.apache.maven/groupId artifactIdmaven-project/artifactId version2.0.4/version /dependency dependency groupIdorg.apache.maven/groupId artifactIdmaven-plugin-api/artifactId version2.0.4/version /dependency -- dependency groupIdjdbc/groupId artifactIdas400/artifactId version5.1.0.1/version /dependency dependency groupIdjavax.xml.bind/groupId artifactIdjsr173_api/artifactId version1.0/version /dependency dependency groupIdorg.apache.myfaces.core/groupId artifactIdmyfaces-api/artifactId version1.1.5/version /dependency dependency groupIdorg.apache.myfaces.core/groupId artifactIdmyfaces-impl/artifactId version1.1.5/version /dependency dependency groupIdorg.apache.myfaces.tomahawk/groupId artifactIdtomahawk/artifactId version1.1.6/version /dependency dependency groupIdjavax.servlet/groupId artifactIdservlet-api/artifactId version2.4/version scopeprovided/scope /dependency dependency groupIdjavax.servlet/groupId artifactIdjsp-api/artifactId version2.0/version scopeprovided/scope /dependency dependency groupIdorg.ajax4jsf/groupId artifactIdajax4jsf/artifactId version1.1.1/version /dependency dependency groupIdorg.richfaces/groupId artifactIdrichfaces/artifactId version3.0.1/version /dependency dependency groupIdorg.apache.poi/groupId artifactIdpoi/artifactId version3.0.1-FINAL/version /dependency !-- dependency groupIdorg.apache.myfaces.trinidad/groupId artifactIdtrinidad-api/artifactId version1.0.2/version /dependency dependency groupIdorg.apache.myfaces.trinidad/groupId artifactIdtrinidad-impl/artifactId version1.0.2/version /dependency dependency groupIdorg.ajax4jsf/groupId artifactIda4j-trinidad/artifactId version1.0/version /dependency --
Re: Community review of the next commons-logging pom
Hi Dennis, I've got two remarks: - You should really make sure that all plugins have a version declared. There are definitely differences between versions, so the reproducibility of your builds can only be guaranteed by using explicit versions. - The artifacts commons-logging, commons-logging-api and commons-logging-adapters are not mutually exclusive. By that I mean that they share some classes. The problem with this is that it is possible for an artifact to get transitive dependencies on different versions of the same classes (commons-logging-1.1.1 and commons-logging-api-1.1.2 for instance). This can be solved by splitting the code up into different projects and having them depend on each other. Regards, Marcel - Original Message From: Dennis Lundberg [EMAIL PROTECTED] To: Maven Users List users@maven.apache.org Sent: Monday, August 27, 2007 8:30:37 PM Subject: Community review of the next commons-logging pom Hi all The poms for commons logging has taken some beating on this list over the years. The reason for that has been the dependencies section. Previous poms of commons-logging was created for Maven 1. These were then converted into Maven 2 poms with various degree of success. In particular the scope wasn't set properly. We are now preparing the next release of commons-logging (version 1.1.1) which will be built with Maven 2. That means that the pom that ends up in the Maven 2 repository will be the same one that we have created. To make sure that we have covered all bases this time we invite you, the community, to help us get it right. The current pom.xml is available for your viewing in our subversion repository: https://svn.apache.org/viewvc/commons/proper/logging/trunk/pom.xml?revision=568979view=markup Please post any comments you have on the pom to this list, and I will bring the over to the commons community. -- Dennis Lundberg Apache Commons committer and PMC member - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Boardwalk for $500? In 2007? Ha! Play Monopoly Here and Now (it's updated for today's economy) at Yahoo! Games. http://get.games.yahoo.com/proddesc?gamekey=monopolyherenow - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Skiping module during mvn eclipse:eclipse
Hello. I've returned to this subject :) Now I use version 2.4 of maven-eclipse-plugin which gives me a posibility to use 'skip' parameter. After making 'mvn help:effective-pom' I can see for one of my module: plugin artifactIdmaven-eclipse-plugin/artifactId configuration skiptrue/skip ... /configuration /plugin But when I executed 'mvn eclipse:eclipse' (in derictory with top level POM) plugin did not skip one of my module. What I did wrong? Regards, Marcin Marcin Waldowski wrote: Hello. I have a Multiple Module Projects (with top level POM and modules). One of module has ear type (packagingear/packaging) and I don't want to make eclipse project from it. Is it possible to exclude this module from execution of mvn eclipse:eclipse in directory with top level POM? Regards, Marcin - 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]
How to get Maven to include persistence.xml into a web app??
Hello all, How do I get Maven to include persistence.xml into a web app?? Any clue welcome! Julien. Here is my POM: 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.calyonfinancial/groupId artifactIdprotide/artifactId packagingwar/packaging version1.0-SNAPSHOT/version nameProtideWeb/name build sourceDirectorysrc/sourceDirectory outputDirectorybuild/outputDirectory finalNameProtideWeb/finalName plugins plugin artifactIdmaven-compiler-plugin/artifactId configuration source1.5/source target1.5/target /configuration /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-war-plugin/artifactId version2.0/version configuration warSourceDirectoryweb/warSourceDirectory /configuration /plugin plugin groupIdorg.codehaus.mojo/groupId artifactIdhibernate3-maven-plugin/artifactId version2.0-alpha-2/version /plugin /plugins /build dependencies dependency groupIdorg.hibernate/groupId artifactIdhibernate/artifactId version3.2.1.ga/version /dependency dependency groupIdorg.hibernate/groupId artifactIdhibernate-annotations/artifactId version3.2.1.ga/version /dependency dependency groupIdorg.hibernate/groupId artifactIdhibernate-entitymanager/artifactId version3.2.1.ga/version /dependency dependency groupIdorg.hibernate/groupId artifactIdhibernate-commons-annotations/artifactId version3.3.0.ga/version /dependency dependency groupIdorg.hibernate/groupId artifactIdhibernate-validator/artifactId version3.0.0.ga/version /dependency dependency groupIdjavax.persistence/groupId artifactIdpersistence-api/artifactId version1.0/version /dependency dependency groupIdlog4j/groupId artifactIdlog4j/artifactId version1.2.14/version /dependency dependency groupIdcom.sun.xml.bind/groupId artifactIdjaxb-impl/artifactId version2.0/version /dependency dependency groupIdcom.sun.xml.bind/groupId artifactIdjaxb-xjc/artifactId version2.0/version /dependency dependency groupIdjavax.xml.bind/groupId artifactIdjaxb-api/artifactId version2.0/version /dependency !-- dependency groupIdorg.apache.maven/groupId artifactIdmaven-project/artifactId version2.0.4/version /dependency dependency groupIdorg.apache.maven/groupId artifactIdmaven-plugin-api/artifactId version2.0.4/version /dependency -- dependency groupIdjdbc/groupId artifactIdas400/artifactId version5.1.0.1/version /dependency dependency groupIdjavax.xml.bind/groupId artifactIdjsr173_api/artifactId version1.0/version /dependency dependency groupIdorg.apache.myfaces.core/groupId artifactIdmyfaces-api/artifactId version1.1.5/version /dependency dependency groupIdorg.apache.myfaces.core/groupId artifactIdmyfaces-impl/artifactId version1.1.5/version /dependency dependency groupIdorg.apache.myfaces.tomahawk/groupId artifactIdtomahawk/artifactId version1.1.6/version /dependency dependency groupIdjavax.servlet/groupId artifactIdservlet-api/artifactId version2.4/version scopeprovided/scope /dependency dependency groupIdjavax.servlet/groupId artifactIdjsp-api/artifactId version2.0/version scopeprovided/scope /dependency dependency groupIdorg.ajax4jsf/groupId artifactIdajax4jsf/artifactId version1.1.1/version /dependency dependency groupIdorg.richfaces/groupId artifactIdrichfaces/artifactId version3.0.1/version /dependency dependency groupIdorg.apache.poi/groupId
Re: How to get Maven to include persistence.xml into a web app??
persistence.xml needs to be on the class path doesn't it? Create a directory src/main/java/resources and put it in there. When maven packages up your war it will put all files in the resources directory into your war file under the WEB-INF/classes directory. Hope this helps. Ben On 8/28/07, Julien Martin [EMAIL PROTECTED] wrote: Hello all, How do I get Maven to include persistence.xml into a web app?? Any clue welcome! Julien. Here is my POM: 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.calyonfinancial/groupId artifactIdprotide/artifactId packagingwar/packaging version1.0-SNAPSHOT/version nameProtideWeb/name build sourceDirectorysrc/sourceDirectory outputDirectorybuild/outputDirectory finalNameProtideWeb/finalName plugins plugin artifactIdmaven-compiler-plugin/artifactId configuration source1.5/source target1.5/target /configuration /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-war-plugin/artifactId version2.0/version configuration warSourceDirectoryweb/warSourceDirectory /configuration /plugin plugin groupIdorg.codehaus.mojo/groupId artifactIdhibernate3-maven-plugin/artifactId version2.0-alpha-2/version /plugin /plugins /build dependencies dependency groupIdorg.hibernate/groupId artifactIdhibernate/artifactId version3.2.1.ga/version /dependency dependency groupIdorg.hibernate/groupId artifactIdhibernate-annotations/artifactId version3.2.1.ga/version /dependency dependency groupIdorg.hibernate/groupId artifactIdhibernate-entitymanager/artifactId version3.2.1.ga/version /dependency dependency groupIdorg.hibernate/groupId artifactIdhibernate-commons-annotations/artifactId version3.3.0.ga/version /dependency dependency groupIdorg.hibernate/groupId artifactIdhibernate-validator/artifactId version3.0.0.ga/version /dependency dependency groupIdjavax.persistence/groupId artifactIdpersistence-api/artifactId version1.0/version /dependency dependency groupIdlog4j/groupId artifactIdlog4j/artifactId version1.2.14/version /dependency dependency groupIdcom.sun.xml.bind/groupId artifactIdjaxb-impl/artifactId version2.0/version /dependency dependency groupIdcom.sun.xml.bind/groupId artifactIdjaxb-xjc/artifactId version2.0/version /dependency dependency groupIdjavax.xml.bind/groupId artifactIdjaxb-api/artifactId version2.0/version /dependency !-- dependency groupIdorg.apache.maven/groupId artifactIdmaven-project/artifactId version2.0.4/version /dependency dependency groupIdorg.apache.maven/groupId artifactIdmaven-plugin-api/artifactId version2.0.4/version /dependency -- dependency groupIdjdbc/groupId artifactIdas400/artifactId version5.1.0.1/version /dependency dependency groupIdjavax.xml.bind/groupId artifactIdjsr173_api/artifactId version1.0/version /dependency dependency groupIdorg.apache.myfaces.core/groupId artifactIdmyfaces-api/artifactId version1.1.5/version /dependency dependency groupIdorg.apache.myfaces.core/groupId artifactIdmyfaces-impl/artifactId version1.1.5/version /dependency dependency groupIdorg.apache.myfaces.tomahawk/groupId artifactIdtomahawk/artifactId version1.1.6/version /dependency dependency groupIdjavax.servlet/groupId artifactIdservlet-api/artifactId version2.4/version scopeprovided/scope /dependency dependency groupIdjavax.servlet/groupId artifactIdjsp-api/artifactId
RE: shell execution from 1.1-beta-1
Hi! I have the same problem than LJ: Continuum-1.1-beta-2 is calling /bin/bash but my bash command is in another directory: usr/local/bin/bash So, I can't execute any script.sh... Is there a way to change the default command /bin/bash called? (I'm working on Solaris 8) Thanks, Rémi. LAMY Olivier [EMAIL PROTECTED] 06/08/2007 23:04 Veuillez répondre à [EMAIL PROTECTED] A [EMAIL PROTECTED] cc Objet RE: shell execution from 1.1-beta-1 Hi, What is your ? AIX ? -- Olivier -Message d'origine- De : L. J. [mailto:[EMAIL PROTECTED] Envoyé : lundi 6 août 2007 22:11 À : continuum-users Objet : shell execution from 1.1-beta-1 I have a build definition: Build File /usr/bin/sh Arguments buildAdmin.sh It works in alpha and earlier version of continuum. Is the way that the shell script gets executed changed since beta? I got the following error, and wonder why continuum is calling /bin/bash at the very beginning 1705563 [pool-1-thread-1] INFO org.apache.maven.continuum.utils.shell.ShellCommandHelper:default - Executing: /bin/bash -c cd /apps/build/continuum-1.1-beta-1/apps/continuum/webapp/WEB-INF/working-directory/2 /usr/bin/sh buildAdmin.sh 1705563 [pool-1-thread-1] INFO org.apache.maven.continuum.utils.shell.ShellCommandHelper:default - Working directory: /apps/build/continuum-1.1-beta-1 /apps/continuum/webapp/WEB-INF/working-directory/2 1706375 [pool-1-thread-1] ERROR org.codehaus.plexus.action.Action:execute-builder - Error running buildResult org.apache.maven.continuum.execution.ContinuumBuildExecutorException: Error while executing shell command. The most common error is that '/usr/bin/sh' is not in your path. at org.apache.maven.continuum.execution.AbstractBuildExecutor.executeShellCommand (AbstractBuildExecutor.java:218) at org.apache.maven.continuum.execution.shell.ShellBuildExecutor.build( ShellBuildExecutor.java:74) at org.apache.maven.continuum.core.action.ExecuteBuilderContinuumAction.execute (ExecuteBuilderContinuumAction.java:140) at org.apache.maven.continuum.buildcontroller.DefaultBuildController.performAction (DefaultBuildController.java:406) at org.apache.maven.continuum.buildcontroller.DefaultBuildController.build( DefaultBuildController.java:145) at org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask (BuildProjectTaskExecutor.java:50) at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable$1.run (ThreadedTaskQueueExecutor.java:116) at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:442) at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run( FutureTask.java:176) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask (ThreadPoolExecutor.java:665) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:690) at java.lang.Thread.run(Thread.java:801) Caused by: org.codehaus.plexus.util.cli.CommandLineException: Error while executing process. at org.codehaus.plexus.util.cli.Commandline.execute(Commandline.java :652) at org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine( CommandLineUtils.java:102) at org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine( CommandLineUtils.java:89) at org.apache.maven.continuum.utils.shell.DefaultShellCommandHelper.executeShellCommand (DefaultShellCommandHelper.java:114) at org.apache.maven.continuum.utils.shell.DefaultShellCommandHelper.executeShellCommand (DefaultShellCommandHelper.java:59) at org.apache.maven.continuum.execution.AbstractBuildExecutor.executeShellCommand (AbstractBuildExecutor.java:202) ... 11 more Caused by: java.io.IOException: /bin/bash: not found at java.lang.UNIXProcess.fullPath(UNIXProcess.java:365) at java.lang.UNIXProcess.init(UNIXProcess.java:172) at java.lang.ProcessImpl.start(ProcessImpl.java:114) at java.lang.ProcessBuilder.start(ProcessBuilder.java:466) at java.lang.Runtime.exec(Runtime.java:607) at org.codehaus.plexus.util.cli.Commandline.execute(Commandline.java :647) ... 16 more 1706710 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - Performing action deploy-artifac Thanks. LJ This e-mail, any attachments and the information contained therein (this message) are confidential and intended solely for the use of the addressee(s). If you have received this message in error please send it back to the sender and delete it. Unauthorized publication, use, dissemination or disclosure of this message, either in whole or in part is strictly prohibited. -- Ce message électronique et tous les fichiers joints ainsi que les
Re: Why does this POM includes the sun's jsf jars??
Thanks Jorg, Your advice was very useful!!! J. 2007/8/28, Jörg Schaible [EMAIL PROTECTED]: Julien Martin wrote on Tuesday, August 28, 2007 10:23 AM: Hello, Why does this POM includes the sun's jsf jars whereas I never asked for them?? I only want the Myfaces Jars... Can anyone help? How do I know which jars are included in a dependency? Thanks in advance, Julien Martin. The dependency report is your friend. Or look for those artifacts in the console output when you build with -X option. Or use a snapshot of the dependency plugin calling dependency:tree. Sun's JSF jars are referenced as transitive dependency and Maven has no knowledge about that MyFaces contains an alternative implementation. So you must exclude the Sun artifacts in your deps that refer them themselves. In your case this it at least richfaces and ajax4j ... but theere might be more. Don't know all of your deps. - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven repository
Hi, I'm just setting up Maven on a developer's workstation. The developer has no access to the Internet and should therefore always retrieve the latest artifacts from a repository we've set up at our company (which has a connection to the internet). Even when I add the following part to the settings.xml file of the Maven installation on the developer's machine, each Maven command I execute from there still tries to connect to the Maven repository on the Internet. How can this be avoided ? (The repository I've set up is working fine, since I can connect with an Internet Explorer to it) profiles profile iddev/id repositories repository idcentral/id nameMaven Central Proxy Repository/name urlhttp://b2btst04/maven-central-proxy/url /repository /repositories pluginRepositories pluginRepository idcentral/id nameMaven Central Proxy Repository/name urlhttp://b2btst04/maven-central-proxy/url /pluginRepository /pluginRepositories /profile /profiles activeProfiles activeProfiledev/activeProfile /activeProfiles - Visit our website! http://www.nbb.be DISCLAIMER: The content of this e-mail message should not be construed as binding on the part of the National Bank of Belgium (NBB) unless otherwise and previously stated. The opinions expressed in this message are solely those of the author and do not necessarily reflect NBB viewpoints, particularly when the content of this message, or part thereof, is private by nature or does not fall within the professional scope of its author. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Cyclic dependency status
Hello, I've read some post and cyclic dependency between maven artifacts is not supported for the moment i.e. artifact A depends on artifact B which depends on artifact A. I would like to know if something is planned about cyclic dependency support or will it never be managed by Maven ? My use case is : I need to integrate some legacy projects under maven, and I cannot undertake their refactoring (huge work and no profit since it's legacy - we only maintain the projects with no evolutions). Currently those projects are build with eclipse and / or ANT. Thanks for your help ! Découvrez le blog Yahoo! Mail : dernières nouveautés, astuces, conseils.. et vos réactions ! http://blog.mail.yahoo.fr - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Failing to add a POI dependency
Hi Julien, I made a simple test on a maven project I am working on and adding... dependency groupIdorg.apache.poi/groupId artifactIdpoi/artifactId version3.0.1-FINAL/version /dependency ...downloaded the necessary pom and jar files to my local repository. If I were to guess I would say that: - You cannot connect to http://repo1.maven.org/maven2 (behind a proxy, not configured in MAVEN) - You can access your company's repository just fine but it doesn't contain apache.poi yet I would say that your options are: 1/ Configure your proxy to access http://repo1.maven.org/maven2, there should be enough documentation on Internet (i.e. the clean way) 2/ Download manually the content of http://repo1.maven.org/maven2/org/apache/poi/poi/3.0.1-FINAL/ and put it on your company's repository 3/ Same as (2) but simply copy the content to your local repository. This is a very simple way to make sure your pom.xml is correct. Hoping I helped a colleague :) Arnaud -Original Message- From: Julien Martin [mailto:[EMAIL PROTECTED] Sent: mardi 28 août 2007 08:19 To: Maven Users List Subject: Re: Failing to add a POI dependency Hello, Here is what I get now that I have changed to org.apache.poi (groupId) and turned on the -e switch: C:\dev\calyonfinancial\ProtideWebmvn -e install + Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] [INFO] Building ProtideWeb [INFO]task-segment: [install] [INFO] [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. Downloading: http://cvs/repository/org/apache/poi/poi/3.0.1-FINAL/poi-3.0.1-FINAL.pom [WARNING] Unable to get resource from repository calyonRepository ( http://cvs/repository) Downloading: http://repo1.maven.org/maven2/org/apache/poi/poi/3.0.1-FINAL/poi-3.0.1-FINAL.pom [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: org.apache.poi:poi Reason: Error getting POM for 'org.apache.poi:poi' from the repository: Error transferring file org.apache.poi:poi:pom:3.0.1-FINAL from the specified remote repositories: central (http://repo1.maven.org/maven2), calyonRepository (http://cvs/repository), jboss repo (http://repository.jboss.com/maven2), maven2 repo (http://repo1.maven.org/maven2) [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Unable to get dependency information: Unable to read the metadata file for artifact ' org.apach e.poi:poi:jar': Error getting POM for 'org.apache.poi:poi' from the repository: Error transferring file org.apache.poi:poi:pom:3.0.1-FINAL from the specified remote repositories: central (http://repo1.maven.org/maven2), calyonRepository (http://cvs/repository), jboss repo (http://repository.jboss.com/maven2), maven2 repo (http://repo1.maven.org/maven2) org.apache.poi:poi:jar:3.0.1-FINAL from the specified remote repositories: central (http://repo1.maven.org/maven2), calyonRepository (http://cvs/repository), jboss repo (http://repository.jboss.com/maven2), maven2 repo (http://repo1.maven.org/maven2) Path to dependency: 1) com.calyonfinancial:protide:war:1.0-SNAPSHOT at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals( DefaultLifecycleExecutor.java:551) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle (DefaultLifecycleExecutor.java:475) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal( DefaultLifecycleExecutor.java:454) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures (DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute( DefaultLifecycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke( NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke( DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java :315) at
Re: Failing to add a POI dependency
merci 2007/8/28, Arnaud Jeansen [EMAIL PROTECTED]: Hi Julien, I made a simple test on a maven project I am working on and adding... dependency groupIdorg.apache.poi/groupId artifactIdpoi/artifactId version3.0.1-FINAL/version /dependency ...downloaded the necessary pom and jar files to my local repository. If I were to guess I would say that: - You cannot connect to http://repo1.maven.org/maven2 (behind a proxy, not configured in MAVEN) - You can access your company's repository just fine but it doesn't contain apache.poi yet I would say that your options are: 1/ Configure your proxy to access http://repo1.maven.org/maven2, there should be enough documentation on Internet (i.e. the clean way) 2/ Download manually the content of http://repo1.maven.org/maven2/org/apache/poi/poi/3.0.1-FINAL/ and put it on your company's repository 3/ Same as (2) but simply copy the content to your local repository. This is a very simple way to make sure your pom.xml is correct. Hoping I helped a colleague :) Arnaud -Original Message- From: Julien Martin [mailto:[EMAIL PROTECTED] Sent: mardi 28 août 2007 08:19 To: Maven Users List Subject: Re: Failing to add a POI dependency Hello, Here is what I get now that I have changed to org.apache.poi (groupId) and turned on the -e switch: C:\dev\calyonfinancial\ProtideWebmvn -e install + Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] [INFO] Building ProtideWeb [INFO]task-segment: [install] [INFO] [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. Downloading: http://cvs/repository/org/apache/poi/poi/3.0.1-FINAL/poi-3.0.1-FINAL.pom [WARNING] Unable to get resource from repository calyonRepository ( http://cvs/repository) Downloading: http://repo1.maven.org/maven2/org/apache/poi/poi/3.0.1-FINAL/poi-3.0.1-FINAL.pom [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: org.apache.poi:poi Reason: Error getting POM for 'org.apache.poi:poi' from the repository: Error transferring file org.apache.poi:poi:pom:3.0.1-FINAL from the specified remote repositories: central (http://repo1.maven.org/maven2), calyonRepository (http://cvs/repository), jboss repo (http://repository.jboss.com/maven2), maven2 repo (http://repo1.maven.org/maven2) [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Unable to get dependency information: Unable to read the metadata file for artifact ' org.apach e.poi:poi:jar': Error getting POM for 'org.apache.poi:poi' from the repository: Error transferring file org.apache.poi:poi:pom:3.0.1-FINAL from the specified remote repositories: central (http://repo1.maven.org/maven2), calyonRepository (http://cvs/repository), jboss repo (http://repository.jboss.com/maven2), maven2 repo (http://repo1.maven.org/maven2) org.apache.poi:poi:jar:3.0.1-FINAL from the specified remote repositories: central (http://repo1.maven.org/maven2), calyonRepository (http://cvs/repository), jboss repo (http://repository.jboss.com/maven2), maven2 repo (http://repo1.maven.org/maven2) Path to dependency: 1) com.calyonfinancial:protide:war:1.0-SNAPSHOT at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals( DefaultLifecycleExecutor.java:551) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle (DefaultLifecycleExecutor.java:475) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal ( DefaultLifecycleExecutor.java:454) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures (DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute( DefaultLifecycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke( NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke( DelegatingMethodAccessorImpl.java:25) at
Re: How to get Maven to include persistence.xml into a web app??
Thanks Ben, Is there not a way to put it (persistence.xml) into meta-inf instead? Julien. 2007/8/28, ben short [EMAIL PROTECTED]: persistence.xml needs to be on the class path doesn't it? Create a directory src/main/java/resources and put it in there. When maven packages up your war it will put all files in the resources directory into your war file under the WEB-INF/classes directory. Hope this helps. Ben On 8/28/07, Julien Martin [EMAIL PROTECTED] wrote: Hello all, How do I get Maven to include persistence.xml into a web app?? Any clue welcome! Julien. Here is my POM: 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.calyonfinancial/groupId artifactIdprotide/artifactId packagingwar/packaging version1.0-SNAPSHOT/version nameProtideWeb/name build sourceDirectorysrc/sourceDirectory outputDirectorybuild/outputDirectory finalNameProtideWeb/finalName plugins plugin artifactIdmaven-compiler-plugin/artifactId configuration source1.5/source target1.5/target /configuration /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-war-plugin/artifactId version2.0/version configuration warSourceDirectoryweb/warSourceDirectory /configuration /plugin plugin groupIdorg.codehaus.mojo/groupId artifactIdhibernate3-maven-plugin/artifactId version2.0-alpha-2/version /plugin /plugins /build dependencies dependency groupIdorg.hibernate/groupId artifactIdhibernate/artifactId version3.2.1.ga/version /dependency dependency groupIdorg.hibernate/groupId artifactIdhibernate-annotations/artifactId version3.2.1.ga/version /dependency dependency groupIdorg.hibernate/groupId artifactIdhibernate-entitymanager/artifactId version3.2.1.ga/version /dependency dependency groupIdorg.hibernate/groupId artifactIdhibernate-commons-annotations/artifactId version3.3.0.ga/version /dependency dependency groupIdorg.hibernate/groupId artifactIdhibernate-validator/artifactId version3.0.0.ga/version /dependency dependency groupIdjavax.persistence/groupId artifactIdpersistence-api/artifactId version1.0/version /dependency dependency groupIdlog4j/groupId artifactIdlog4j/artifactId version1.2.14/version /dependency dependency groupIdcom.sun.xml.bind/groupId artifactIdjaxb-impl/artifactId version2.0/version /dependency dependency groupIdcom.sun.xml.bind/groupId artifactIdjaxb-xjc/artifactId version2.0/version /dependency dependency groupIdjavax.xml.bind/groupId artifactIdjaxb-api/artifactId version2.0/version /dependency !-- dependency groupIdorg.apache.maven/groupId artifactIdmaven-project/artifactId version2.0.4/version /dependency dependency groupIdorg.apache.maven/groupId artifactIdmaven-plugin-api/artifactId version2.0.4/version /dependency -- dependency groupIdjdbc/groupId artifactIdas400/artifactId version5.1.0.1/version /dependency dependency groupIdjavax.xml.bind/groupId artifactIdjsr173_api/artifactId version1.0/version /dependency dependency groupIdorg.apache.myfaces.core/groupId artifactIdmyfaces-api/artifactId version1.1.5/version /dependency dependency groupIdorg.apache.myfaces.core/groupId artifactIdmyfaces-impl/artifactId version1.1.5/version /dependency dependency groupIdorg.apache.myfaces.tomahawk/groupId artifactIdtomahawk/artifactId version1.1.6/version /dependency dependency
Re: Maven Compile error - java.lang.NoSuchMethodError: org.apache.maven.plugin.descriptor.MojoDescriptor.setSince(Ljava/lang/String;
you got the same error because you are building with the same embedded maven instance. you need to setup netbeans to use the command line tool. the help you refer to seems to refer to old method of adding AU center. The new way is this: Open Tools/Plugins dialog Find the Settings tab, there's an Add button. Voila! Milos On 8/28/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi, I got the same error in NB6 Milestone 10 also. Using 2 extractors. Applying extractor for language: java [ERROR]FATAL ERROR org.apache.maven.plugin.descriptor.MojoDescriptor.setSince(Ljava/lang/String;)V Trace java.lang.NoSuchMethodError: org.apache.maven.plugin.descriptor.MojoDescriptor.setSince(Ljava/lang/String;)V at org.apache.maven.tools.plugin.extractor.java.JavaMojoDescriptorExtractor.createMojoDescriptor(JavaMojoDescriptorExtractor.java:225) at org.apache.maven.tools.plugin.extractor.java.JavaMojoDescriptorExtractor.execute(JavaMojoDescriptorExtractor.java:559) at org.apache.maven.tools.plugin.scanner.DefaultMojoScanner.populatePluginDescriptor(DefaultMojoScanner.java:84) at org.apache.maven.plugin.plugin.AbstractGeneratorMojo.execute(AbstractGeneratorMojo.java:135) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:417) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:610) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:551) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:530) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:309) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:276) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.codehaus.mevenide.netbeans.embedder.exec.MyLifecycleExecutor.execute(MyLifecycleExecutor.java:94) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:393) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:182) at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:760) at org.codehaus.mevenide.netbeans.execute.MavenJavaExecutor.run(MavenJavaExecutor.java:197) at org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:129) Total time: 1 second Finished at: Tue Aug 28 10:22:47 BST 2007 Final Memory: 41M/108M I couldn't add an update center manually to NB 6 MS 10 Manually Registering an Update Center URL See Also If you have not been provided with a module that bundles an update center's URL, you need to register the update center manually. Once you have registered the update center, you can access its modules via the Update Center wizard, which you can access under the Tools menu. There are some changes in the tools- option dialog box. So I followed the help to insert a module update like. The steps I followed are below. Unfortunately the in step four I didn't get the Autoupdate Types node :-(. It is not there in NB 6 MS10. What next? Can I manually patch any NB config files to add an update center link? Help Help! To manually register an update center's URL: 1. Choose Tools Options. The Options window appears. 2. In the Options window, click Advanced Options in the bottom lefthand corner. 3. In the IDE Configuration node, expand the System subnode. 4. In the System subnode, right-click Autoupdate Types, and choose New General Update Center. The General Update Center dialog box appears. 5. Type the name of the autoupdate center. The name can be anything you want it to be. Click Finish. 6. Expand the Autoupdate Types node, select the newly created subnode, and enter the URL to the Update Center in the Server URL field, on the right side of the Options window. Press Enter in the field. 7. Click Close. You have now manually registered the update center's URL. To verify that you have done so successfully, choose Tools Update Center. Your newly registered update center should be included in the list in the Update Center wizard. Select it and click Next to access the modules that are provided by the selected update center. Thanks Regards, Jayaram Jayaram Ganapathy - Tel 01412280277 Jayaram X
RE: shell execution from 1.1-beta-1
Try to add a link on your machine. I use solaris too and I have the following link : bash-2.05$ ls -lrt /bin/ lrwxrwxrwx 1 root root 9 Sep 22 2005 /bin/ - ./usr/bin And my bash is there : bash-2.05$ which bash /usr/bin/bash -- Olivier -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Envoyé : mardi 28 août 2007 11:58 À : [EMAIL PROTECTED] Objet : RE: shell execution from 1.1-beta-1 Hi! I have the same problem than LJ: Continuum-1.1-beta-2 is calling /bin/bash but my bash command is in another directory: usr/local/bin/bash So, I can't execute any script.sh... Is there a way to change the default command /bin/bash called? (I'm working on Solaris 8) Thanks, Rémi. LAMY Olivier [EMAIL PROTECTED] 06/08/2007 23:04 Veuillez répondre à [EMAIL PROTECTED] A [EMAIL PROTECTED] cc Objet RE: shell execution from 1.1-beta-1 Hi, What is your ? AIX ? -- Olivier -Message d'origine- De : L. J. [mailto:[EMAIL PROTECTED] Envoyé : lundi 6 août 2007 22:11 À : continuum-users Objet : shell execution from 1.1-beta-1 I have a build definition: Build File /usr/bin/sh Arguments buildAdmin.sh It works in alpha and earlier version of continuum. Is the way that the shell script gets executed changed since beta? I got the following error, and wonder why continuum is calling /bin/bash at the very beginning 1705563 [pool-1-thread-1] INFO org.apache.maven.continuum.utils.shell.ShellCommandHelper:default - Executing: /bin/bash -c cd /apps/build/continuum-1.1-beta-1/apps/continuum/webapp/WEB-INF/working-directory/2 /usr/bin/sh buildAdmin.sh 1705563 [pool-1-thread-1] INFO org.apache.maven.continuum.utils.shell.ShellCommandHelper:default - Working directory: /apps/build/continuum-1.1-beta-1 /apps/continuum/webapp/WEB-INF/working-directory/2 1706375 [pool-1-thread-1] ERROR org.codehaus.plexus.action.Action:execute-builder - Error running buildResult org.apache.maven.continuum.execution.ContinuumBuildExecutorException: Error while executing shell command. The most common error is that '/usr/bin/sh' is not in your path. at org.apache.maven.continuum.execution.AbstractBuildExecutor.executeShellCommand (AbstractBuildExecutor.java:218) at org.apache.maven.continuum.execution.shell.ShellBuildExecutor.build( ShellBuildExecutor.java:74) at org.apache.maven.continuum.core.action.ExecuteBuilderContinuumAction.execute (ExecuteBuilderContinuumAction.java:140) at org.apache.maven.continuum.buildcontroller.DefaultBuildController.performAction (DefaultBuildController.java:406) at org.apache.maven.continuum.buildcontroller.DefaultBuildController.build( DefaultBuildController.java:145) at org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask (BuildProjectTaskExecutor.java:50) at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable$1.run (ThreadedTaskQueueExecutor.java:116) at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:442) at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run( FutureTask.java:176) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask (ThreadPoolExecutor.java:665) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:690) at java.lang.Thread.run(Thread.java:801) Caused by: org.codehaus.plexus.util.cli.CommandLineException: Error while executing process. at org.codehaus.plexus.util.cli.Commandline.execute(Commandline.java :652) at org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine( CommandLineUtils.java:102) at org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine( CommandLineUtils.java:89) at org.apache.maven.continuum.utils.shell.DefaultShellCommandHelper.executeShellCommand (DefaultShellCommandHelper.java:114) at org.apache.maven.continuum.utils.shell.DefaultShellCommandHelper.executeShellCommand (DefaultShellCommandHelper.java:59) at org.apache.maven.continuum.execution.AbstractBuildExecutor.executeShellCommand (AbstractBuildExecutor.java:202) ... 11 more Caused by: java.io.IOException: /bin/bash: not found at java.lang.UNIXProcess.fullPath(UNIXProcess.java:365) at java.lang.UNIXProcess.init(UNIXProcess.java:172) at java.lang.ProcessImpl.start(ProcessImpl.java:114) at java.lang.ProcessBuilder.start(ProcessBuilder.java:466) at java.lang.Runtime.exec(Runtime.java:607) at org.codehaus.plexus.util.cli.Commandline.execute(Commandline.java :647) ... 16 more 1706710 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - Performing action deploy-artifac Thanks. LJ This e-mail, any attachments and the information contained therein (this message) are confidential and intended solely for
RE: Community review of the next commons-logging pom
Michael McCallum wrote on Tuesday, August 28, 2007 1:15 PM: Why? Only with dependencyManagement you're able to manage transitive versions. In order to keep clean dependency graphs I have used standard OO principles to encasulate functionality in this case I will use spring as an example. Spring provided many artifacts. I have many projects that use different groups of spring projects so I have pulled the spring dependencies out into two compositions one that deals with contexts and the other persistence. [snip] You still did not explain, what composition means. It's no word used in standard Maven terminology. Your description does not make it clear what you *actually* have done. [snip] Commons logging has a different philosophy. But this is OT for this list. If the difference in philosophy means more difficulty in managing dependency graphs then its not OT for this list but very pertinent. It is OT, since it is up to the Apache Commons community how they carve their artifacts. And splitting an artifact into 6 where 5 of them contain a single wrapper class is where philosophy starts. You may discuss this at Apache Commons. - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Community review of the next commons-logging pom
Why? Only with dependencyManagement you're able to manage transitive versions. In order to keep clean dependency graphs I have used standard OO principles to encasulate functionality in this case I will use spring as an example. Spring provided many artifacts. I have many projects that use different groups of spring projects so I have pulled the spring dependencies out into two compositions one that deals with contexts and the other persistence. All my projects depend upon those compositions which means that all aggregations end up with bottleneck in the dependency graph at the point where the actual spring versions are resolved. Hence no conflict in the jars that actually end up in aggregations. On other key thing is a careful use of ranges to restrict which version of the composition is pulled in. For example at the moment i have one for spring [2.0,2.1) and one for [2.1,2.2) its impossible for an aggregation via two different trees to accidentally include spring 2.0.6 and 2.1-beta for example as the maven dependency will complain of an over contrained dependency. This evangenlism is usually accompanied by a A2 page of dependency graph scribbles ;-) They are optional, so you do not depend on them transitively. so in order to enable something thats optional i have to include those same dependencies myself? Rather than depend upon an artifact that will resolve only the dependencies I want and the correct graph for what I need? http://maven.apache.org/guides/introduction/introduction-to-optional-and-excludes-dependencies.html Optional dependencies are used when it's not really possible (for whatever reason) to split a project up into sub-modules. The idea is that some of the dependencies are only used for certain features in the project, and will not be needed if that feature isn't used. Ideally, such a feature would be split into a sub-module that depended on the core functionality project...this new subproject would have only non-optional dependencies, since you'd need them all if you decided to use the subproject's functionality. Commons logging has a different philosophy. But this is OT for this list. If the difference in philosophy means more difficulty in managing dependency graphs then its not OT for this list but very pertinent. On Tuesday 28 August 2007 18:03, Jörg Schaible wrote: Hi Michael, Michael McCallum wrote on Tuesday, August 28, 2007 12:34 AM: IMO the log4j, logkit, avalon dependencies all need to go... I as I imagine most people do only use one logging implementation in the deployed systems why introduce a dependency on several implementations at the top level? They are optional, so you do not depend on them transitively. check out http://www.slf4j.com for an appropriate break up of the artifacts and use cases Commons logging has a different philosophy. But this is OT for this list. I've generally stopped using dependencyManagement in favour of dependency composition Why? Only with dependencyManagement you're able to manage transitive versions. - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Michael McCallum Development Lead Ferrit Ltd cell: 021.576.907 msn: [EMAIL PROTECTED] jabber: [EMAIL PROTECTED] aim: gholamses http://www.ferrit.co.nz - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to get Maven to include persistence.xml into a web app??
I think you can just create /src/main/webapp/META-INF and put it in there. On 8/28/07, Julien Martin [EMAIL PROTECTED] wrote: Thanks Ben, Is there not a way to put it (persistence.xml) into meta-inf instead? Julien. 2007/8/28, ben short [EMAIL PROTECTED]: persistence.xml needs to be on the class path doesn't it? Create a directory src/main/java/resources and put it in there. When maven packages up your war it will put all files in the resources directory into your war file under the WEB-INF/classes directory. Hope this helps. Ben On 8/28/07, Julien Martin [EMAIL PROTECTED] wrote: Hello all, How do I get Maven to include persistence.xml into a web app?? Any clue welcome! Julien. Here is my POM: 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.calyonfinancial/groupId artifactIdprotide/artifactId packagingwar/packaging version1.0-SNAPSHOT/version nameProtideWeb/name build sourceDirectorysrc/sourceDirectory outputDirectorybuild/outputDirectory finalNameProtideWeb/finalName plugins plugin artifactIdmaven-compiler-plugin/artifactId configuration source1.5/source target1.5/target /configuration /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-war-plugin/artifactId version2.0/version configuration warSourceDirectoryweb/warSourceDirectory /configuration /plugin plugin groupIdorg.codehaus.mojo/groupId artifactIdhibernate3-maven-plugin/artifactId version2.0-alpha-2/version /plugin /plugins /build dependencies dependency groupIdorg.hibernate/groupId artifactIdhibernate/artifactId version3.2.1.ga/version /dependency dependency groupIdorg.hibernate/groupId artifactIdhibernate-annotations/artifactId version3.2.1.ga/version /dependency dependency groupIdorg.hibernate/groupId artifactIdhibernate-entitymanager/artifactId version3.2.1.ga/version /dependency dependency groupIdorg.hibernate/groupId artifactIdhibernate-commons-annotations/artifactId version3.3.0.ga/version /dependency dependency groupIdorg.hibernate/groupId artifactIdhibernate-validator/artifactId version3.0.0.ga/version /dependency dependency groupIdjavax.persistence/groupId artifactIdpersistence-api/artifactId version1.0/version /dependency dependency groupIdlog4j/groupId artifactIdlog4j/artifactId version1.2.14/version /dependency dependency groupIdcom.sun.xml.bind/groupId artifactIdjaxb-impl/artifactId version2.0/version /dependency dependency groupIdcom.sun.xml.bind/groupId artifactIdjaxb-xjc/artifactId version2.0/version /dependency dependency groupIdjavax.xml.bind/groupId artifactIdjaxb-api/artifactId version2.0/version /dependency !-- dependency groupIdorg.apache.maven/groupId artifactIdmaven-project/artifactId version2.0.4/version /dependency dependency groupIdorg.apache.maven/groupId artifactIdmaven-plugin-api/artifactId version2.0.4/version /dependency -- dependency groupIdjdbc/groupId artifactIdas400/artifactId version5.1.0.1/version /dependency dependency groupIdjavax.xml.bind/groupId artifactIdjsr173_api/artifactId version1.0/version /dependency dependency groupIdorg.apache.myfaces.core/groupId artifactIdmyfaces-api/artifactId version1.1.5/version /dependency dependency groupIdorg.apache.myfaces.core/groupId
Problem: TRINIDAD and MAVEN
Hello, I am having problems with Trinidad and Maven. Can anyone please help? Thanks in advance, Julien. I get this from the console: C:\dev\calyonfinancial\ProtideWebmvn -e install + Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] [INFO] Building ProtideWeb [INFO]task-segment: [install] [INFO] [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. Downloading: http://cvs/repository/org/apache/myfaces/trinidad/trinidad-impl/1.0.2/trinidad-impl-1.0.2.pom [WARNING] Unable to get resource from repository calyonRepository ( http://cvs/repository) Downloading: http://repo1.maven.org/maven2/org/apache/myfaces/trinidad/trinidad-impl/1.0.2/trinidad-impl-1.0.2.pom 7K downloaded Downloading: http://cvs/repository/org/apache/myfaces/trinidad/trinidad/1.0.2/trinidad-1.0.2.pom [WARNING] Unable to get resource from repository calyonRepository ( http://cvs/repository) Downloading: http://repo1.maven.org/maven2/org/apache/myfaces/trinidad/trinidad/1.0.2/trinidad-1.0.2.pom 17K downloaded Downloading: https://maven-repository.dev.java.net/nonav/repository//org.apache/poms/apache-4.pom [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: org.apache.myfaces.trinidad:trinidad:pom:1.0.2 Reason: Cannot find parent: org.apache:apache for project: org.apache.myfaces.trinidad:trinidad:pom:1.0.2 [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Unable to get dependency information: Unable to read the metadata file for artifact ' org.apach e.myfaces.trinidad:trinidad-impl:jar': Cannot find parent: org.apache:apachefor project: org.apache.myfaces.trinidad:trinidad:pom:1.0.2 org.apache.myfaces.trinidad:trinidad-impl:jar:1.0.2 from the specified remote repositories: central (http://repo1.maven.org/maven2), calyonRepository (http://cvs/repository), jboss repo (http://repository.jboss.com/maven2), maven2 repo (http://repo1.maven.org/maven2) Path to dependency: 1) com.calyonfinancial:protide:war:1.0-SNAPSHOT at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals( DefaultLifecycleExecutor.java:551) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle (DefaultLifecycleExecutor.java:475) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal( DefaultLifecycleExecutor.java:454) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures (DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute( DefaultLifecycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke( NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke( DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java :315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java :430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.artifact.resolver.ArtifactResolutionException: Unable to get dependency information: Unable to read the metadata file for artifact 'org.apache.myfaces.trinidad:trinidad-impl:jar': Cannot find parent: org.apache:apache for project: org.apache.myfaces.trinidad:trinidad:pom: 1.0.2 org.apache.myfaces.trinidad:trinidad-impl:jar:1.0.2 from the specified remote repositories: central (http://repo1.maven.org/maven2), calyonRepository (http://cvs/repository), jboss repo (http://repository.jboss.com/maven2), maven2 repo (http://repo1.maven.org/maven2) Path to dependency: 1) com.calyonfinancial:protide:war:1.0-SNAPSHOT at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse( DefaultArtifactCollector.java:297) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect( DefaultArtifactCollector.java:67) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively (DefaultArtifactResolver.java:223)
Re: Community review of the next commons-logging pom
Why? Only with dependencyManagement you're able to manage transitive versions. In order to keep clean dependency graphs I have used standard OO principles to encasulate functionality in this case I will use spring as an example. Spring provided many artifacts. I have many projects that use different groups of spring projects so I have pulled the spring dependencies out into two compositions one that deals with contexts and the other persistence. All my projects depend upon those compositions which means that all aggregations end up with bottleneck in the dependency graph at the point where the actual spring versions are resolved. Hence no conflict in the jars that actually end up in aggregations. On other key thing is a careful use of ranges to restrict which version of the composition is pulled in. For example at the moment i have one for spring [2.0,2.1) and one for [2.1,2.2) its impossible for an aggregation via two different trees to accidentally include spring 2.0.6 and 2.1-beta for example as the maven dependency will complain of an over contrained dependency. This evangenlism is usually accompanied by a A2 page of dependency graph scribbles ;-) They are optional, so you do not depend on them transitively. so in order to enable something thats optional i have to include those same dependencies myself? Rather than depend upon an artifact that will resolve only the dependencies I want and the correct graph for what I need? http://maven.apache.org/guides/introduction/introduction-to-optional-and-excludes-dependencies.html Optional dependencies are used when it's not really possible (for whatever reason) to split a project up into sub-modules. The idea is that some of the dependencies are only used for certain features in the project, and will not be needed if that feature isn't used. Ideally, such a feature would be split into a sub-module that depended on the core functionality project...this new subproject would have only non-optional dependencies, since you'd need them all if you decided to use the subproject's functionality. Commons logging has a different philosophy. But this is OT for this list. If the difference in philosophy means more difficulty in managing dependency graphs then its not OT for this list but very pertinent. On Tuesday 28 August 2007 18:03, Jörg Schaible wrote: Hi Michael, Michael McCallum wrote on Tuesday, August 28, 2007 12:34 AM: IMO the log4j, logkit, avalon dependencies all need to go... I as I imagine most people do only use one logging implementation in the deployed systems why introduce a dependency on several implementations at the top level? They are optional, so you do not depend on them transitively. check out http://www.slf4j.com for an appropriate break up of the artifacts and use cases Commons logging has a different philosophy. But this is OT for this list. I've generally stopped using dependencyManagement in favour of dependency composition Why? Only with dependencyManagement you're able to manage transitive versions. - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Michael McCallum Enterprise Engineer mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven Compile error - java.lang.NoSuchMethodError: org.apache.maven.plugin.descriptor.MojoDescriptor.setSince(Ljava/lang/String;
Hi, The update center URL which you gave was already present. I can't send you a screen shot because the e-mail with screenshots bounced back. I have maven 2.0.7 and I integrated it. I can now trigger external maven build. Now the problem is where can I see the messages of build? Once I start the build it says build started. I can't make out whether the build ended or was the build successful etc.. Thanks Regards, Jayaram Milos Kleint [EMAIL PROTECTED] 28/08/2007 12:04 Please respond to Maven Users List users@maven.apache.org To Maven Users List users@maven.apache.org cc Subject Re: Maven Compile error - java.lang.NoSuchMethodError: org.apache.maven.plugin.descriptor.MojoDescriptor.setSince(Ljava/lang/String; you got the same error because you are building with the same embedded maven instance. you need to setup netbeans to use the command line tool. the help you refer to seems to refer to old method of adding AU center. The new way is this: Open Tools/Plugins dialog Find the Settings tab, there's an Add button. Voila! Milos On 8/28/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi, I got the same error in NB6 Milestone 10 also. Using 2 extractors. Applying extractor for language: java [ERROR]FATAL ERROR org.apache.maven.plugin.descriptor.MojoDescriptor.setSince(Ljava/lang/String;)V Trace java.lang.NoSuchMethodError: org.apache.maven.plugin.descriptor.MojoDescriptor.setSince(Ljava/lang/String;)V at org.apache.maven.tools.plugin.extractor.java.JavaMojoDescriptorExtractor.createMojoDescriptor(JavaMojoDescriptorExtractor.java:225) at org.apache.maven.tools.plugin.extractor.java.JavaMojoDescriptorExtractor.execute(JavaMojoDescriptorExtractor.java:559) at org.apache.maven.tools.plugin.scanner.DefaultMojoScanner.populatePluginDescriptor(DefaultMojoScanner.java:84) at org.apache.maven.plugin.plugin.AbstractGeneratorMojo.execute(AbstractGeneratorMojo.java:135) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:417) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:610) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:551) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:530) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:309) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:276) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.codehaus.mevenide.netbeans.embedder.exec.MyLifecycleExecutor.execute(MyLifecycleExecutor.java:94) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:393) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:182) at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:760) at org.codehaus.mevenide.netbeans.execute.MavenJavaExecutor.run(MavenJavaExecutor.java:197) at org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:129) Total time: 1 second Finished at: Tue Aug 28 10:22:47 BST 2007 Final Memory: 41M/108M I couldn't add an update center manually to NB 6 MS 10 Manually Registering an Update Center URL See Also If you have not been provided with a module that bundles an update center's URL, you need to register the update center manually. Once you have registered the update center, you can access its modules via the Update Center wizard, which you can access under the Tools menu. There are some changes in the tools- option dialog box. So I followed the help to insert a module update like. The steps I followed are below. Unfortunately the in step four I didn't get the Autoupdate Types node :-(. It is not there in NB 6 MS10. What next? Can I manually patch any NB config files to add an update center link? Help Help! To manually register an update center's URL: 1. Choose Tools Options. The Options window appears. 2. In the Options window, click Advanced Options in the bottom lefthand corner. 3. In the IDE Configuration node, expand the System subnode. 4. In the System subnode, right-click Autoupdate Types, and choose New General Update Center. The General Update Center dialog box appears. 5. Type the name of
Re: Community review of the next commons-logging pom
http://en.wikipedia.org/wiki/Relation_composition group.id.composition.spring 2.0.6 - spring-beans 2.0.6 - spring-context 2.0.6 group.id.composition.spring.persistence 2.0.6 -group.id.composition.spring 2.0.6 - hibernate 3.1.3 - spring-hibernate3 group.id.artifact.a X - group.id.composition.spring.persistence [2.0, 2.1) group.id.artifact.b Y - group.id.composition.spring [2.0, 2.1) group.id.aggregation Z - group.id.artifact.b Y - group.id.artifact.a X when building aggregation - think war or ear - you get a graph with a common composition element when it resolves you only get one of those and the resultant transitions down the graph I will concede the logging artifacts as OT but you may see me on commons later ;-) On Tuesday 28 August 2007 23:28, Jörg Schaible wrote: Michael McCallum wrote on Tuesday, August 28, 2007 1:15 PM: Why? Only with dependencyManagement you're able to manage transitive versions. In order to keep clean dependency graphs I have used standard OO principles to encasulate functionality in this case I will use spring as an example. Spring provided many artifacts. I have many projects that use different groups of spring projects so I have pulled the spring dependencies out into two compositions one that deals with contexts and the other persistence. [snip] You still did not explain, what composition means. It's no word used in standard Maven terminology. Your description does not make it clear what you *actually* have done. [snip] Commons logging has a different philosophy. But this is OT for this list. If the difference in philosophy means more difficulty in managing dependency graphs then its not OT for this list but very pertinent. It is OT, since it is up to the Apache Commons community how they carve their artifacts. And splitting an artifact into 6 where 5 of them contain a single wrapper class is where philosophy starts. You may discuss this at Apache Commons. - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Michael McCallum Enterprise Engineer mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: How to get Maven to include persistence.xml into a web app??
Hi Julien,
you can configure aditional resources through the war plugin.
http://maven.apache.org/plugins/maven-war-plugin/examples/adding-filteri
ng-webresources.html
So you need something like this
!-- All webapps filter and add **/**.xml in src/main/config tp the war
--
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-war-plugin/artifactId
configuration
webResources
resource
filteringfalse/filtering
directory${basedir}/src/main/config-flex/directory
includes
include**/**/include
/includes
/resource
/webResources
/configuration
/plugin
regards,
Bram
--
Bram de Kruijff
Product Architect
GX
open for business
t: 024 - 388 82 61
f: 024 - 388 86 21
e: [EMAIL PROTECTED]
Wijchenseweg 111
6538 SW Nijmegen
www.gx.nl
KvK: 10044410
-Original Message-
From: Julien Martin [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 28, 2007 1:30 PM
To: Maven Users List
Subject: Re: How to get Maven to include persistence.xml
into a web app??
The problem is that I have to use an existing path i.e.
(MyProject\src\conf\persistence.xml) and cannot change that
Is there not a way to modify the POM in order for it to
include my persistence.xml??
Sorry I am a real beginner at Maven...
Julien.
2007/8/28, ben short [EMAIL PROTECTED]:
I think you can just create /src/main/webapp/META-INF and
put it in there.
On 8/28/07, Julien Martin [EMAIL PROTECTED] wrote:
Thanks Ben,
Is there not a way to put it (persistence.xml) into
meta-inf instead?
Julien.
2007/8/28, ben short [EMAIL PROTECTED]:
persistence.xml needs to be on the class path doesn't it?
Create a directory src/main/java/resources and put it in there.
When maven packages up your war it will put all files in the
resources directory into your war file under the
WEB-INF/classes directory.
Hope this helps.
Ben
On 8/28/07, Julien Martin [EMAIL PROTECTED] wrote:
Hello all,
How do I get Maven to include persistence.xml into
a web app??
Any clue welcome!
Julien.
Here is my POM:
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.calyonfinancial/groupId
artifactIdprotide/artifactId
packagingwar/packaging
version1.0-SNAPSHOT/version
nameProtideWeb/name
build
sourceDirectorysrc/sourceDirectory
outputDirectorybuild/outputDirectory
finalNameProtideWeb/finalName
plugins
plugin
artifactIdmaven-compiler-plugin/artifactId
configuration
source1.5/source
target1.5/target
/configuration
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-war-plugin/artifactId
version2.0/version
configuration
warSourceDirectoryweb/warSourceDirectory
/configuration
/plugin
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdhibernate3-maven-plugin/artifactId
version2.0-alpha-2/version
/plugin
/plugins
/build
dependencies
dependency
groupIdorg.hibernate/groupId
artifactIdhibernate/artifactId
version3.2.1.ga/version
/dependency
dependency
groupIdorg.hibernate/groupId
artifactIdhibernate-annotations/artifactId
version3.2.1.ga/version
/dependency
dependency
groupIdorg.hibernate/groupId
artifactIdhibernate-entitymanager/artifactId
version3.2.1.ga/version
/dependency
dependency
groupIdorg.hibernate/groupId
artifactIdhibernate-commons-annotations/artifactId
version3.3.0.ga/version
/dependency
dependency
groupIdorg.hibernate/groupId
artifactIdhibernate-validator/artifactId
version3.0.0.ga/version
/dependency
dependency
groupIdjavax.persistence/groupId
artifactIdpersistence-api/artifactId
version1.0/version
/dependency
dependency
groupIdlog4j/groupId
Re: How to get Maven to include persistence.xml into a web app??
The problem is that I have to use an existing path i.e. (MyProject\src\conf\persistence.xml) and cannot change that Is there not a way to modify the POM in order for it to include my persistence.xml?? Sorry I am a real beginner at Maven... Julien. 2007/8/28, ben short [EMAIL PROTECTED]: I think you can just create /src/main/webapp/META-INF and put it in there. On 8/28/07, Julien Martin [EMAIL PROTECTED] wrote: Thanks Ben, Is there not a way to put it (persistence.xml) into meta-inf instead? Julien. 2007/8/28, ben short [EMAIL PROTECTED]: persistence.xml needs to be on the class path doesn't it? Create a directory src/main/java/resources and put it in there. When maven packages up your war it will put all files in the resources directory into your war file under the WEB-INF/classes directory. Hope this helps. Ben On 8/28/07, Julien Martin [EMAIL PROTECTED] wrote: Hello all, How do I get Maven to include persistence.xml into a web app?? Any clue welcome! Julien. Here is my POM: 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.calyonfinancial/groupId artifactIdprotide/artifactId packagingwar/packaging version1.0-SNAPSHOT/version nameProtideWeb/name build sourceDirectorysrc/sourceDirectory outputDirectorybuild/outputDirectory finalNameProtideWeb/finalName plugins plugin artifactIdmaven-compiler-plugin/artifactId configuration source1.5/source target1.5/target /configuration /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-war-plugin/artifactId version2.0/version configuration warSourceDirectoryweb/warSourceDirectory /configuration /plugin plugin groupIdorg.codehaus.mojo/groupId artifactIdhibernate3-maven-plugin/artifactId version2.0-alpha-2/version /plugin /plugins /build dependencies dependency groupIdorg.hibernate/groupId artifactIdhibernate/artifactId version3.2.1.ga/version /dependency dependency groupIdorg.hibernate/groupId artifactIdhibernate-annotations/artifactId version3.2.1.ga/version /dependency dependency groupIdorg.hibernate/groupId artifactIdhibernate-entitymanager/artifactId version3.2.1.ga/version /dependency dependency groupIdorg.hibernate/groupId artifactIdhibernate-commons-annotations/artifactId version3.3.0.ga/version /dependency dependency groupIdorg.hibernate/groupId artifactIdhibernate-validator/artifactId version3.0.0.ga/version /dependency dependency groupIdjavax.persistence/groupId artifactIdpersistence-api/artifactId version1.0/version /dependency dependency groupIdlog4j/groupId artifactIdlog4j/artifactId version1.2.14/version /dependency dependency groupIdcom.sun.xml.bind/groupId artifactIdjaxb-impl/artifactId version2.0/version /dependency dependency groupIdcom.sun.xml.bind/groupId artifactIdjaxb-xjc/artifactId version2.0/version /dependency dependency groupIdjavax.xml.bind/groupId artifactIdjaxb-api/artifactId version2.0/version /dependency !-- dependency groupIdorg.apache.maven/groupId artifactIdmaven-project/artifactId version2.0.4/version /dependency dependency groupIdorg.apache.maven/groupId artifactIdmaven-plugin-api/artifactId version2.0.4/version /dependency -- dependency groupIdjdbc/groupId artifactIdas400/artifactId version5.1.0.1/version /dependency dependency
RE: Community review of the next commons-logging pom
Michael McCallum wrote on Tuesday, August 28, 2007 1:56 PM: http://en.wikipedia.org/wiki/Relation_composition group.id.composition.spring 2.0.6 - spring-beans 2.0.6 - spring-context 2.0.6 group.id.composition.spring.persistence 2.0.6 -group.id.composition.spring 2.0.6 - hibernate 3.1.3 - spring-hibernate3 group.id.artifact.a X - group.id.composition.spring.persistence [2.0, 2.1) group.id.artifact.b Y - group.id.composition.spring [2.0, 2.1) group.id.aggregation Z - group.id.artifact.b Y - group.id.artifact.a X when building aggregation - think war or ear - you get a graph with a common composition element when it resolves you only get one of those and the resultant transitions down the graph OK. But this will not help you, if you include another artifact that depends transitively on Spring or Hibernate in different versions. And therefore we use a company or at least a master POM for a project with a dependencyManagement section. This way you can overwrite the versions of the transitive deps. I will concede the logging artifacts as OT but you may see me on commons later ;-) You're welcome :D - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to get Maven to include persistence.xml into a web app??
Hi, this should do what you want: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-war-plugin/artifactId configuration webResources resource directorysrc/conf/directory !-- override the destination directory for this resource -- targetPathMETA-INF/targetPath includes includepersistence.xml/include /includes /resource /webResources /configuration /plugin -Tim Julien Martin schrieb: The problem is that I have to use an existing path i.e. (MyProject\src\conf\persistence.xml) and cannot change that Is there not a way to modify the POM in order for it to include my persistence.xml?? Sorry I am a real beginner at Maven... Julien. 2007/8/28, ben short [EMAIL PROTECTED]: I think you can just create /src/main/webapp/META-INF and put it in there. On 8/28/07, Julien Martin [EMAIL PROTECTED] wrote: Thanks Ben, Is there not a way to put it (persistence.xml) into meta-inf instead? Julien. 2007/8/28, ben short [EMAIL PROTECTED]: persistence.xml needs to be on the class path doesn't it? Create a directory src/main/java/resources and put it in there. When maven packages up your war it will put all files in the resources directory into your war file under the WEB-INF/classes directory. Hope this helps. Ben On 8/28/07, Julien Martin [EMAIL PROTECTED] wrote: Hello all, How do I get Maven to include persistence.xml into a web app?? Any clue welcome! Julien. Here is my POM: 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.calyonfinancial/groupId artifactIdprotide/artifactId packagingwar/packaging version1.0-SNAPSHOT/version nameProtideWeb/name build sourceDirectorysrc/sourceDirectory outputDirectorybuild/outputDirectory finalNameProtideWeb/finalName plugins plugin artifactIdmaven-compiler-plugin/artifactId configuration source1.5/source target1.5/target /configuration /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-war-plugin/artifactId version2.0/version configuration warSourceDirectoryweb/warSourceDirectory /configuration /plugin plugin groupIdorg.codehaus.mojo/groupId artifactIdhibernate3-maven-plugin/artifactId version2.0-alpha-2/version /plugin /plugins /build dependencies dependency groupIdorg.hibernate/groupId artifactIdhibernate/artifactId version3.2.1.ga/version /dependency dependency groupIdorg.hibernate/groupId artifactIdhibernate-annotations/artifactId version3.2.1.ga/version /dependency dependency groupIdorg.hibernate/groupId artifactIdhibernate-entitymanager/artifactId version3.2.1.ga/version /dependency dependency groupIdorg.hibernate/groupId artifactIdhibernate-commons-annotations/artifactId version3.3.0.ga/version /dependency dependency groupIdorg.hibernate/groupId artifactIdhibernate-validator/artifactId version3.0.0.ga/version /dependency dependency groupIdjavax.persistence/groupId artifactIdpersistence-api/artifactId version1.0/version /dependency dependency groupIdlog4j/groupId artifactIdlog4j/artifactId version1.2.14/version /dependency dependency groupIdcom.sun.xml.bind/groupId artifactIdjaxb-impl/artifactId version2.0/version /dependency dependency groupIdcom.sun.xml.bind/groupId artifactIdjaxb-xjc/artifactId version2.0/version /dependency dependency groupIdjavax.xml.bind/groupId artifactIdjaxb-api/artifactId version2.0/version /dependency !-- dependency groupIdorg.apache.maven/groupId artifactIdmaven-project/artifactId version2.0.4/version /dependency dependency groupIdorg.apache.maven/groupId artifactIdmaven-plugin-api/artifactId version2.0.4/version /dependency -- dependency groupIdjdbc/groupId artifactIdas400/artifactId version5.1.0.1/version /dependency dependency
Re: Maven Compile error - java.lang.NoSuchMethodError: org.apache.maven.plugin.descriptor.MojoDescriptor.setSince(Ljava/lang/String;
doesn't happen to me, sorry.. I get the output correctly. file a bug at jira.codehaus.org/browse/MEVENIDE there you can attach screenshots, sample projects etc.. Milos On 8/28/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi, The update center URL which you gave was already present. I can't send you a screen shot because the e-mail with screenshots bounced back. I have maven 2.0.7 and I integrated it. I can now trigger external maven build. Now the problem is where can I see the messages of build? Once I start the build it says build started. I can't make out whether the build ended or was the build successful etc.. Thanks Regards, Jayaram Milos Kleint [EMAIL PROTECTED] 28/08/2007 12:04 Please respond to Maven Users List users@maven.apache.org To Maven Users List users@maven.apache.org cc Subject Re: Maven Compile error - java.lang.NoSuchMethodError: org.apache.maven.plugin.descriptor.MojoDescriptor.setSince(Ljava/lang/String; you got the same error because you are building with the same embedded maven instance. you need to setup netbeans to use the command line tool. the help you refer to seems to refer to old method of adding AU center. The new way is this: Open Tools/Plugins dialog Find the Settings tab, there's an Add button. Voila! Milos On 8/28/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi, I got the same error in NB6 Milestone 10 also. Using 2 extractors. Applying extractor for language: java [ERROR]FATAL ERROR org.apache.maven.plugin.descriptor.MojoDescriptor.setSince(Ljava/lang/String;)V Trace java.lang.NoSuchMethodError: org.apache.maven.plugin.descriptor.MojoDescriptor.setSince(Ljava/lang/String;)V at org.apache.maven.tools.plugin.extractor.java.JavaMojoDescriptorExtractor.createMojoDescriptor(JavaMojoDescriptorExtractor.java:225) at org.apache.maven.tools.plugin.extractor.java.JavaMojoDescriptorExtractor.execute(JavaMojoDescriptorExtractor.java:559) at org.apache.maven.tools.plugin.scanner.DefaultMojoScanner.populatePluginDescriptor(DefaultMojoScanner.java:84) at org.apache.maven.plugin.plugin.AbstractGeneratorMojo.execute(AbstractGeneratorMojo.java:135) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:417) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:610) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:551) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:530) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:309) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:276) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.codehaus.mevenide.netbeans.embedder.exec.MyLifecycleExecutor.execute(MyLifecycleExecutor.java:94) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:393) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:182) at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:760) at org.codehaus.mevenide.netbeans.execute.MavenJavaExecutor.run(MavenJavaExecutor.java:197) at org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:129) Total time: 1 second Finished at: Tue Aug 28 10:22:47 BST 2007 Final Memory: 41M/108M I couldn't add an update center manually to NB 6 MS 10 Manually Registering an Update Center URL See Also If you have not been provided with a module that bundles an update center's URL, you need to register the update center manually. Once you have registered the update center, you can access its modules via the Update Center wizard, which you can access under the Tools menu. There are some changes in the tools- option dialog box. So I followed the help to insert a module update like. The steps I followed are below. Unfortunately the in step four I didn't get the Autoupdate Types node :-(. It is not there in NB 6 MS10. What next? Can I manually patch any NB config files to add an update center link? Help Help! To manually register an update center's URL: 1. Choose Tools Options. The Options window appears. 2. In
Re: Community review of the next commons-logging pom
http://en.wikipedia.org/wiki/Object_composition is really just the software equivalent of the first link i sent [snip] You still did not explain, what composition means. It's no word used in standard Maven terminology. Your description does not make it clear what you *actually* have done. [snip] -- Michael McCallum Enterprise Engineer mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Community review of the next commons-logging pom
OK. But this will not help you, if you include another artifact that depends transitively on Spring or Hibernate in different versions. And therefore we use a company or at least a master POM for a project with a dependencyManagement section. This way you can overwrite the versions of the transitive deps. incorrect. maven will resolve the dependencies from closest to furtherest but not tranverse transitions if there is a better match. So if I hide all of the transitions behind a composition in all cases - which means i have to exclude deps from 3rd party libraries in some cases - then the spring libraries are only resolved as transitions of composition and nothing else... as you can have on one instance of an artifact in the graph that gets selected there is on one set of transitions from the selected compositions... and voila consistent dependencies -- Michael McCallum Enterprise Engineer mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven Compile error - java.lang.NoSuchMethodError: org.apache.maven.plugin.descriptor.MojoDescriptor.setSince(Ljava/lang/String;
Hi, Thanks a lot. I was able to fix the problem. It was my mistake. I setup the maven home to the bin directory of maven. So the tool was trying to execute $MAVEN_HOME/bin/bin/mvn.bat which was not present. The output windows never complained that invalid maven home set etc.. It shows as if it triggered command and waiting. I too waited to see the output :-) Thanks Regards, Jayaram Milos Kleint [EMAIL PROTECTED] 28/08/2007 13:02 Please respond to Maven Users List users@maven.apache.org To Maven Users List users@maven.apache.org cc Subject Re: Maven Compile error - java.lang.NoSuchMethodError: org.apache.maven.plugin.descriptor.MojoDescriptor.setSince(Ljava/lang/String; doesn't happen to me, sorry.. I get the output correctly. file a bug at jira.codehaus.org/browse/MEVENIDE there you can attach screenshots, sample projects etc.. Milos On 8/28/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi, The update center URL which you gave was already present. I can't send you a screen shot because the e-mail with screenshots bounced back. I have maven 2.0.7 and I integrated it. I can now trigger external maven build. Now the problem is where can I see the messages of build? Once I start the build it says build started. I can't make out whether the build ended or was the build successful etc.. Thanks Regards, Jayaram Milos Kleint [EMAIL PROTECTED] 28/08/2007 12:04 Please respond to Maven Users List users@maven.apache.org To Maven Users List users@maven.apache.org cc Subject Re: Maven Compile error - java.lang.NoSuchMethodError: org.apache.maven.plugin.descriptor.MojoDescriptor.setSince(Ljava/lang/String; you got the same error because you are building with the same embedded maven instance. you need to setup netbeans to use the command line tool. the help you refer to seems to refer to old method of adding AU center. The new way is this: Open Tools/Plugins dialog Find the Settings tab, there's an Add button. Voila! Milos On 8/28/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi, I got the same error in NB6 Milestone 10 also. Using 2 extractors. Applying extractor for language: java [ERROR]FATAL ERROR org.apache.maven.plugin.descriptor.MojoDescriptor.setSince(Ljava/lang/String;)V Trace java.lang.NoSuchMethodError: org.apache.maven.plugin.descriptor.MojoDescriptor.setSince(Ljava/lang/String;)V at org.apache.maven.tools.plugin.extractor.java.JavaMojoDescriptorExtractor.createMojoDescriptor(JavaMojoDescriptorExtractor.java:225) at org.apache.maven.tools.plugin.extractor.java.JavaMojoDescriptorExtractor.execute(JavaMojoDescriptorExtractor.java:559) at org.apache.maven.tools.plugin.scanner.DefaultMojoScanner.populatePluginDescriptor(DefaultMojoScanner.java:84) at org.apache.maven.plugin.plugin.AbstractGeneratorMojo.execute(AbstractGeneratorMojo.java:135) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:417) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:610) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:551) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:530) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:309) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:276) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.codehaus.mevenide.netbeans.embedder.exec.MyLifecycleExecutor.execute(MyLifecycleExecutor.java:94) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:393) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:182) at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:760) at org.codehaus.mevenide.netbeans.execute.MavenJavaExecutor.run(MavenJavaExecutor.java:197) at org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:129) Total time: 1 second Finished at: Tue Aug 28 10:22:47 BST 2007 Final Memory: 41M/108M I couldn't add an update center manually to NB 6 MS 10 Manually Registering an Update Center URL See Also If you have not been provided with a module that bundles an
Re: Problem: TRINIDAD and MAVEN
Weird, see inline for what I read from the log output: Julien Martin schrieb: Hello, I am having problems with Trinidad and Maven. Can anyone please help? Thanks in advance, Julien. I get this from the console: [...] Downloading: http://cvs/repository/org/apache/myfaces/trinidad/trinidad-impl/1.0.2/trinidad-impl-1.0.2.pom [WARNING] Unable to get resource from repository calyonRepository ( http://cvs/repository) Downloading: http://repo1.maven.org/maven2/org/apache/myfaces/trinidad/trinidad-impl/1.0.2/trinidad-impl-1.0.2.pom 7K downloaded Downloads seems to work since something is downloaded from central. Downloading: http://cvs/repository/org/apache/myfaces/trinidad/trinidad/1.0.2/trinidad-1.0.2.pom [WARNING] Unable to get resource from repository calyonRepository ( http://cvs/repository) Downloading: http://repo1.maven.org/maven2/org/apache/myfaces/trinidad/trinidad/1.0.2/trinidad-1.0.2.pom 17K downloaded The pom for trinidad is downloaded from central. Downloading: https://maven-repository.dev.java.net/nonav/repository//org.apache/poms/apache-4.pom [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: org.apache.myfaces.trinidad:trinidad:pom:1.0.2 Reason: Cannot find parent: org.apache:apache for project: org.apache.myfaces.trinidad:trinidad:pom:1.0.2 Then it tries to download the parent pom of the trinidad pom. And that's where it's getting weird: The repository it tries to download from (java.net repository) is declared in the trinidad pom itself. The artifact it tries to download (org.apache:apache:4) is indeed not present on this repository. But instead of trying to resolve it from the other four repositories you defined (central, calyonRepository, jboss, maven2) it justs fails. What I *guess* is going on here is that the repository definitions in the trinidad pom somehow shadow the other repositories, which is plainly wrong in my opinion. Perhaps somone with more insight into this than can comment. Else I think this is a bug and you should file it in jira [1]. As a workaround you can just download the pom from central [2] by hand and copy in in your local repository. -Tim [1] http://jira.codehaus.org/browse/MNG [2] http://repo1.maven.org/maven2/org/apache/apache/4/apache-4.pom [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Unable to get dependency information: Unable to read the metadata file for artifact ' org.apach e.myfaces.trinidad:trinidad-impl:jar': Cannot find parent: org.apache:apachefor project: org.apache.myfaces.trinidad:trinidad:pom:1.0.2 org.apache.myfaces.trinidad:trinidad-impl:jar:1.0.2 from the specified remote repositories: central (http://repo1.maven.org/maven2), calyonRepository (http://cvs/repository), jboss repo (http://repository.jboss.com/maven2), maven2 repo (http://repo1.maven.org/maven2) Path to dependency: 1) com.calyonfinancial:protide:war:1.0-SNAPSHOT at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals( DefaultLifecycleExecutor.java:551) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle (DefaultLifecycleExecutor.java:475) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal( DefaultLifecycleExecutor.java:454) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures (DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute( DefaultLifecycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke( NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke( DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java :315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java :430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.artifact.resolver.ArtifactResolutionException: Unable to get dependency information: Unable to read the metadata file for artifact 'org.apache.myfaces.trinidad:trinidad-impl:jar': Cannot find parent: org.apache:apache for project:
Re: How to get Maven to include persistence.xml into a web app??
Thanks Tim for you suggestion. I thought I was getting there but apparently the targetPath is COMPLETELY ignored by Maven... Here is where the persistence.xml is copied: the root of the war... Here is my POM for your info. Tis almost identical to your suggestion: 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.calyonfinancial/groupId artifactIdprotide/artifactId packagingwar/packaging version1.0-SNAPSHOT/version nameProtideWeb/name build sourceDirectorysrc/sourceDirectory outputDirectorybuild/outputDirectory finalNameProtideWeb/finalName plugins plugin artifactIdmaven-compiler-plugin/artifactId configuration source1.5/source target1.5/target /configuration /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-war-plugin/artifactId version2.0/version configuration warSourceDirectoryweb/warSourceDirectory webResources resource directorysrc/conf/directory targetPathMETA-INF/targetPath includes includepersistence.xml/include /includes /resource /webResources /configuration /plugin /plugins /build dependencies dependency groupIdorg.hibernate/groupId artifactIdhibernate/artifactId version3.2.1.ga/version /dependency dependency groupIdorg.hibernate/groupId artifactIdhibernate-annotations/artifactId version3.2.1.ga/version /dependency dependency groupIdorg.hibernate/groupId artifactIdhibernate-entitymanager/artifactId version3.2.1.ga/version /dependency dependency groupIdorg.hibernate/groupId artifactIdhibernate-commons-annotations/artifactId version3.3.0.ga/version /dependency dependency groupIdorg.hibernate/groupId artifactIdhibernate-validator/artifactId version3.0.0.ga/version /dependency dependency groupIdjavax.persistence/groupId artifactIdpersistence-api/artifactId version1.0/version /dependency dependency groupIdlog4j/groupId artifactIdlog4j/artifactId version1.2.14/version /dependency dependency groupIdcom.sun.xml.bind/groupId artifactIdjaxb-impl/artifactId version2.0/version /dependency dependency groupIdcom.sun.xml.bind/groupId artifactIdjaxb-xjc/artifactId version2.0/version /dependency dependency groupIdjavax.xml.bind/groupId artifactIdjaxb-api/artifactId version2.0/version /dependency !-- dependency groupIdorg.apache.maven/groupId artifactIdmaven-project/artifactId version2.0.4/version /dependency dependency groupIdorg.apache.maven/groupId artifactIdmaven-plugin-api/artifactId version2.0.4/version /dependency -- dependency groupIdjdbc/groupId artifactIdas400/artifactId version5.1.0.1/version /dependency dependency groupIdjavax.xml.bind/groupId artifactIdjsr173_api/artifactId version1.0/version /dependency dependency groupIdorg.apache.myfaces.core/groupId artifactIdmyfaces-api/artifactId version1.1.5/version /dependency dependency groupIdorg.apache.myfaces.core/groupId artifactIdmyfaces-impl/artifactId version1.1.5/version /dependency dependency groupIdorg.apache.myfaces.tomahawk/groupId artifactIdtomahawk/artifactId version1.1.6/version /dependency dependency groupIdjavax.servlet/groupId artifactIdservlet-api/artifactId version2.4/version scopeprovided/scope /dependency dependency groupIdjavax.servlet/groupId artifactIdjsp-api/artifactId version2.0/version scopeprovided/scope /dependency dependency
Re: Problem: TRINIDAD and MAVEN
Thank you Tim!!! As a workaround you can just download the pom from central [2] by hand and copy in in your local repository. This worked a charm!!
Re: Debugging Maven in Netbeans
that's in project's popup menu. last item on the list.. Properties.. there in Run tab, you set the main class. Milos On 8/28/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi, I have opened few maven project. I use NB6 Ms10 with external maven build enabled. The maven version I have is 2.0.7. I am able to compile( mvn install) the project. Now when I try to execute the same I get the following message. In order to run the project, Netbeans needs a custom profile in your pom.xml . To create and customise the profile, go to the project's Properties dialog and update the Run Panel. I can see profiles tag in settings.xml but nothing in pom.xml. Any help appretiated. I want to run the programs in debug mode to understand what happens. Thanks Regards, Jayaram This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase Co., its subsidiaries and affiliates. This transmission may contain information that is privileged, confidential, legally privileged, and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMorgan Chase Co., its subsidiaries and affiliates, as applicable, for any loss or damage arising in any way from its use. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. Please refer to http://www.jpmorgan.com/pages/disclosures for disclosures relating to UK legal entities. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Debugging Maven in Netbeans
Hi, I have opened few maven project. I use NB6 Ms10 with external maven build enabled. The maven version I have is 2.0.7. I am able to compile( mvn install) the project. Now when I try to execute the same I get the following message. In order to run the project, Netbeans needs a custom profile in your pom.xml . To create and customise the profile, go to the project's Properties dialog and update the Run Panel. I can see profiles tag in settings.xml but nothing in pom.xml. Any help appretiated. I want to run the programs in debug mode to understand what happens. Thanks Regards, Jayaram This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase Co., its subsidiaries and affiliates. This transmission may contain information that is privileged, confidential, legally privileged, and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMorgan Chase Co., its subsidiaries and affiliates, as applicable, for any loss or damage arising in any way from its use. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. Please refer to http://www.jpmorgan.com/pages/disclosures for disclosures relating to UK legal entities.
assembly project properties
Hi All,
I am interested to know if there is any documentation that specifies
which exact project properties will be filtered when filtering is
used. I searched the list and the assembly and resources plugins
documentation but I could not find a proper list.
I am particularly interested into accessing the dependency version
number (or even artifactId). for example, if my projects depends on
foo:artifact-1.0, how can I have a text file with any ${} expansion
rule that will expand in the mentioned dependency?
Many thanks in advance.
Stefano
--
Stefano Fornari - Funambol Chief Architect / Funambol CTO
===
Home:
http://www.funambol.org
Documents:
http://www.funambol.org/documentation/documents.html
FAQ:
http://www.funambol.org/support/faq.html
WIKI:
https://wiki.objectweb.org/sync4j/
Mailinglist archives:
http://groups.yahoo.com/group/Sync4j (login required)
http://sourceforge.net/mailarchive/forum.php?forum_id=215 (sync4j-users)
http://sourceforge.net/mailarchive/forum.php?forum_id=48877
(funambol-dev)
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
installing a ueber jar
Hi there,
I´m developing an applet that has many dependencies. To speed-up the load
phase, I´m using the ueber plugin [1].
The ueber plugins works fine.. It creates a smaller jar, but with a suffix
-uber under target directory.
The issue that I´m facing is how install this ueber jar under repository?
I´ve already tried many tricks like above, and none work:
- set the final name of the generated jar by ueber equal to final name.
- configure a install-file execution under pom.xml like:
...
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-install-plugin/artifactId
executions
execution
idinstall2/id
phaseinstall/phase
goals
goalinstall-file/goal
/goals
configuration
groupId${groupId}/groupId
artifactId${artifactId}/artifactId
version${version}-ueber/version
packagingjar/packaging
file
${basedir}/build/${artifactId}-${version}-ueber.jar
/file
generatePomtrue/generatePom
/configuration
/execution
/executions
/plugin
But maven complains that the properties like artifactId is read-only
Does anyone has a clue about installing a file like uber under local repository?
Thanks in advance
[1] - http://mojo.codehaus.org/minijar-maven-plugin/ueberjar-mojo.html
Atenciosamente
Msc. Domingos Creado
DRT - CPqD Telecom IT Solutions
Tel.: +55 19 3705-6423 / Fax: +55 19 3705-7268
Cel.: +55 19 8183-1003
[EMAIL PROTECTED]
www.cpqd.com.br
Que ninguém se engane, só se consegue a simplicidade através de muito
trabalho.
Clarice Lispector
Simplicidade é a sofisticação máxima.
Leonardo da Vinci
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Community review of the next commons-logging pom
Michael McCallum wrote on Tuesday, August 28, 2007 2:39 PM: OK. But this will not help you, if you include another artifact that depends transitively on Spring or Hibernate in different versions. And therefore we use a company or at least a master POM for a project with a dependencyManagement section. This way you can overwrite the versions of the transitive deps. incorrect. maven will resolve the dependencies from closest to furtherest but not tranverse transitions if there is a better match. So if I hide all of the transitions behind a composition in all cases That's the point. By using the compositions you have to update them or create new ones everytime you add a new dep. I simply add it to my dependencyManagement. - which means i have to exclude deps from 3rd party libraries in some cases - then the spring libraries are only resolved as transitions of composition and nothing else... as you can have on one instance of an artifact in the graph that gets selected there is on one set of transitions from the selected compositions... and voila consistent dependencies Since the depMgmnt oiverwrites the version of the inherited deps: voila no inconsistent dep ;-) But you have your point. By using compositions you can combine them individually, while the depMgmnt approach is kind of all or nothing for a project. - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Cyclic dependency status
I can't forsee Maven ever realistically making it possible/easy to introduce cyclical dependencies into your dependency graphs. This goes against the basic principles of the tool. Wayne On 8/28/07, Adrian Gonzalez [EMAIL PROTECTED] wrote: Hello, I've read some post and cyclic dependency between maven artifacts is not supported for the moment i.e. artifact A depends on artifact B which depends on artifact A. I would like to know if something is planned about cyclic dependency support or will it never be managed by Maven ? My use case is : I need to integrate some legacy projects under maven, and I cannot undertake their refactoring (huge work and no profit since it's legacy - we only maintain the projects with no evolutions). Currently those projects are build with eclipse and / or ANT. Thanks for your help ! Découvrez le blog Yahoo! Mail : dernières nouveautés, astuces, conseils.. et vos réactions ! http://blog.mail.yahoo.fr - 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]
Re: installing a ueber jar
Use build-helper-m-p and attach your artifact to the build/project.
Wayne
On 8/28/07, Domingos Antonio Pereira Creado Júnior [EMAIL PROTECTED] wrote:
Hi there,
I´m developing an applet that has many dependencies. To speed-up the load
phase, I´m using the ueber plugin [1].
The ueber plugins works fine.. It creates a smaller jar, but with a suffix
-uber under target directory.
The issue that I´m facing is how install this ueber jar under repository?
I´ve already tried many tricks like above, and none work:
- set the final name of the generated jar by ueber equal to final name.
- configure a install-file execution under pom.xml like:
...
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-install-plugin/artifactId
executions
execution
idinstall2/id
phaseinstall/phase
goals
goalinstall-file/goal
/goals
configuration
groupId${groupId}/groupId
artifactId${artifactId}/artifactId
version${version}-ueber/version
packagingjar/packaging
file
${basedir}/build/${artifactId}-${version}-ueber.jar
/file
generatePomtrue/generatePom
/configuration
/execution
/executions
/plugin
But maven complains that the properties like artifactId is read-only
Does anyone has a clue about installing a file like uber under local
repository?
Thanks in advance
[1] - http://mojo.codehaus.org/minijar-maven-plugin/ueberjar-mojo.html
Atenciosamente
Msc. Domingos Creado
DRT - CPqD Telecom IT Solutions
Tel.: +55 19 3705-6423 / Fax: +55 19 3705-7268
Cel.: +55 19 8183-1003
[EMAIL PROTECTED]
www.cpqd.com.br
Que ninguém se engane, só se consegue a simplicidade através de muito
trabalho.
Clarice Lispector
Simplicidade é a sofisticação máxima.
Leonardo da Vinci
-
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]
Re: m2 ear plugin and resource filters.
1. Try ${project.*} instead.
2. Consider writing a geronimo plugin (or patching the existing
maven-ear-plugin), and contributing it back. It would be helpful for
other people who need to generate these geronimo.xml files. And I
think it would be pretty simple.
Wayne
On 8/28/07, Jonathan Chen [EMAIL PROTECTED] wrote:
Hi all,
I'm running Maven 2.0.7 and I'm trying to get resource filtering
working with m2's ear plugin. I have a file which I'm trying to get
certain properties replaced on a mvn package.
src/main/application/META-INF/geronimo.xml:
?xml version=1.0 encoding=UTF-8?
application
xmlns=http://geronimo.apache.org/xml/ns/j2ee/application-1.2;
xmlns:dep=http://geronimo.apache.org/xml/ns/deployment-1.2;
environment
xmlns=http://geronimo.apache.org/xml/ns/deployment-1.2;
moduleId
groupId${pom.groupId}/groupId
artifactId${pom.artifactId}/artifactId
version${pom.version}/version
typeear/type
/moduleId
/environment
/application
Ideally, the ${pom.*} properties are replaced with the values from
pom.xml; but for some reason, I can't seem to get it working with:
pom.xml:
?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/xsd/maven-4.0.0.xsd;
modelVersion4.0.0/modelVersion
nameEAR goal test/name
groupIdtest/groupId
artifactIdear-goal/artifactId
version1.0-SNAPSHOT/version
packagingear/packaging
build
resources
resource
filteringtrue/filtering
directorysrc/main/application/META-INF/directory
includes
include*.xml/include
/includes
/resource
/resources
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-ear-plugin/artifactId
configuration
version5/version
/configuration
/plugin
/plugins
/build
/project
Can anyone on the list see what I'm doing wrong? Any help appreciated.
Cheers.
--
Jonathan Chen [EMAIL PROTECTED]
--
Don't worry about avoiding temptation,
as you grow older, it starts avoiding you.
-
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]
RE: deploy goal fails
Hi, Did you find a solution for this? I'm having the same problem: Error deploying artifact: C:\projects\Portal2\code\workflow\web\target\classes (Access is denied) The point is that it only fails when adding a classifier to the war. mvn install OTOH works fine (I also get the : altDeploymentRepository = null ) Regards Ivan John Coleman-6 wrote: It's strange because this is a mapped drive over a local disk, and the folder exists and contains classes. But this looks somewhat like a network permissions problem? Other deployments from this drive work fine. John -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: 21 August 2007 16:53 To: Maven Users List Subject: Re: deploy goal fails Caused by: java.io.FileNotFoundException: Z:\jcoleman\projects\eTraderII\trunk\target\classes (Access is denied) at java.io.FileInputStream.open(Native Method) That's your root problem. I can't tell you why its happening or what it means, but that's the reason your deploy is failing. Wayne On 8/21/07, John Coleman [EMAIL PROTECTED] wrote: I have used a classifier on the war plugin, and it looks like this spoils the deploy, but the error message doesn't seem related. Does anyone understand this error pls? TIA John [deploy:deploy] altDeploymentRepository = null [INFO]Retrieving previous build number from repo [DEBUG]repository metadata for: 'snapshot com.eurobase:eTraderII:1.2-SNAPSHOT' could not be found on repository: repo [INFO]Error for project: eTraderII Project (during deploy) [INFO]-- -- [INFO]Error deploying artifact: Z:\jcoleman\projects\eTraderII\trunk\target\classes (Access is denied) [INFO]-- -- [DEBUG]Trace org.apache.maven.lifecycle.LifecycleExecutionException: Error deploying artifact: Z:\jcoleman\projects\eTraderII\trunk\target\classes (Access is denied) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default LifecycleExecutor.java:635) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec ycle(DefaultLifecycleExecutor.java:551) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL ifecycleExecutor.java:530) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle Failures(DefaultLifecycleExecutor.java:309) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( DefaultLifecycleExecutor.java:276) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec ycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:393) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:182) at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:760) at org.codehaus.mevenide.netbeans.execute.MavenJavaExecutor.run(MavenJavaEx ecutor.java:257) at org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:131) Caused by: org.apache.maven.plugin.MojoExecutionException: Error deploying artifact: Z:\jcoleman\projects\eTraderII\trunk\target\classes (Access is denied) at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:174) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa nager.java:417) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default LifecycleExecutor.java:610) ... 10 more Caused by: org.apache.maven.artifact.deployer.ArtifactDeploymentException: Error deploying artifact: Z:\jcoleman\projects\eTraderII\trunk\target\classes (Access is denied) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(Defaul tArtifactDeployer.java:95) at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:162) ... 12 more Caused by: java.io.FileNotFoundException: Z:\jcoleman\projects\eTraderII\trunk\target\classes (Access is denied) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.init(FileInputStream.java:106) at org.codehaus.plexus.util.FileUtils.copyFile(FileUtils.java:820) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(Defaul tArtifactDeployer.java:74) ... 13 more [INFO]-- -- [INFO]BUILD ERRORS [INFO]-- -- [INFO]Total time: 1 minute 1 second [INFO]Finished at: Tue Aug 21 15:26:01 BST 2007 [INFO]Final Memory: 52M/105M [INFO]-- -- Eurobase International Limited and its subsidiaries
Re: Embedded Tomcat within a Maven Unit Test
Hi, I may not have made this clear in my initial post, but I do have all of the tomcat jar's listed as Maven dependancies. That's why I'm confused. Is there any way for maven to handle this, or do I need to pre-compile the jsp's? -Josh On Aug 27, 2007, at 7:36 PM, Joshua ChaitinPollak wrote: Hello, I have an application with an embedded instance of tomcat. When I run a unittest in maven like this: mvn -Dtest=RunAppTest test (which isn't really a test, it launches the application for a while) and then I browse to http://localhost:8080/distrosite I get a compiler error in the logs. It appears that the compiler Jasper compiler cannot find the servlet-api.jar and other dependancies on the compile classpath (see the CP in the logs below). What do I need to do to make sure my embedded Tomcat compile sees all of my 3rd party jars? Thanks, Josh Compile failed; see the compiler error output for details. at org.apache.tools.ant.taskdefs.Javac.compile(Javac.java:933) at org.apache.tools.ant.taskdefs.Javac.execute(Javac.java:757) at org.apache.jasper.compiler.AntCompiler.generateClass (AntCompiler.java:219) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:297) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:276) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:264) at org.apache.jasper.JspCompilationContext.compile (JspCompilationContext.java:563) at org.apache.jasper.servlet.JspServletWrapper.service (JspServletWrapper.java:303) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java: 314) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) at javax.servlet.http.HttpServlet.service(HttpServlet.java: 802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter (ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter (ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke (StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke (StandardContextValve.java:178) at org.apache.catalina.core.StandardHostValve.invoke (StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke (ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke (StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service (CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process (Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol $Http11ConnectionHandler.processConnection(Http11BaseProtocol.java: 667) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket (PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt (LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool $ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:595) 2007-08-27 19:17:46,239 [http-8080-Processor4] ERROR apache.jasper.compiler.Compiler - Env: Compile: javaFileName=/home/jpollak/src/software/java/trunk/work/mhsEngine/ kiva/distrosite//org/apache/jsp/launch/index_jsp.java classpath=/home/jpollak/src/software/java/trunk/work/mhsEngine/kiva/ distrosite:/tmp/surefirebooter14150.jar:/usr/lib/jvm/java-1.5.0- sun-1.5.0.11/jre/lib/ext/dnsns.jar:/usr/lib/jvm/java-1.5.0- sun-1.5.0.11/jre/lib/ext/sunpkcs11.jar:/usr/lib/jvm/java-1.5.0- sun-1.5.0.11/jre/lib/ext/sunjce_provider.jar:/usr/lib/jvm/ java-1.5.0-sun-1.5.0.11/jre/lib/ext/localedata.jar cp=/tmp/surefirebooter14150.jar cp=/home/jpollak/src/software/java/trunk/work/mhsEngine/kiva/ distrosite cp=/tmp/surefirebooter14150.jar cp=/usr/lib/jvm/java-1.5.0-sun-1.5.0.11/jre/lib/ext/dnsns.jar cp=/usr/lib/jvm/java-1.5.0-sun-1.5.0.11/jre/lib/ext/sunpkcs11.jar cp=/usr/lib/jvm/java-1.5.0-sun-1.5.0.11/jre/lib/ext/ sunjce_provider.jar cp=/usr/lib/jvm/java-1.5.0-sun-1.5.0.11/jre/lib/ext/localedata.jar work dir=/home/jpollak/src/software/java/trunk/work/mhsEngine/kiva/ distrosite extension dir=/usr/lib/jvm/java-1.5.0-sun-1.5.0.11/jre/lib/ext srcDir=/home/jpollak/src/software/java/trunk/work/mhsEngine/kiva/ distrosite compilerTargetVM=1.5 compilerSourceVM=1.5 include=org/apache/jsp/launch/index_jsp.java 2007-08-27 19:17:46,240 [http-8080-Processor4] ERROR apache.jasper.compiler.Compiler - Error compiling file: /home/jpollak/src/software/java/trunk/work/mhsEngine/kiva/ distrosite//org/apache/jsp/launch/index_jsp.java [javac] Compiling 1 source file /home/jpollak/src/software/java/trunk/work/mhsEngine/kiva/ distrosite/org/apache/jsp/launch/index_jsp.java:3: package javax.servlet does not exist import javax.servlet.*; ^
Re: Skiping module during mvn eclipse:eclipse
can you reproduce in a smaller set of projects? On 8/28/07, Marcin Waldowski [EMAIL PROTECTED] wrote: Hello. I've returned to this subject :) Now I use version 2.4 of maven-eclipse-plugin which gives me a posibility to use 'skip' parameter. After making 'mvn help:effective-pom' I can see for one of my module: plugin artifactIdmaven-eclipse-plugin/artifactId configuration skiptrue/skip ... /configuration /plugin But when I executed 'mvn eclipse:eclipse' (in derictory with top level POM) plugin did not skip one of my module. What I did wrong? Regards, Marcin Marcin Waldowski wrote: Hello. I have a Multiple Module Projects (with top level POM and modules). One of module has ear type (packagingear/packaging) and I don't want to make eclipse project from it. Is it possible to exclude this module from execution of mvn eclipse:eclipse in directory with top level POM? Regards, Marcin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE : Re: Cyclic dependency status
Thanks for the answer Fay. Just posted the question cause there's already been some users having the same need (trying to put legacy libraries under maven) - and I think personnally it can be a 'common' need. But no problem, I'll try to cope with that. --- Wayne Fay [EMAIL PROTECTED] a écrit : I can't forsee Maven ever realistically making it possible/easy to introduce cyclical dependencies into your dependency graphs. This goes against the basic principles of the tool. Wayne On 8/28/07, Adrian Gonzalez [EMAIL PROTECTED] wrote: Hello, I've read some post and cyclic dependency between maven artifacts is not supported for the moment i.e. artifact A depends on artifact B which depends on artifact A. I would like to know if something is planned about cyclic dependency support or will it never be managed by Maven ? My use case is : I need to integrate some legacy projects under maven, and I cannot undertake their refactoring (huge work and no profit since it's legacy - we only maintain the projects with no evolutions). Currently those projects are build with eclipse and / or ANT. Thanks for your help ! Découvrez le blog Yahoo! Mail : dernières nouveautés, astuces, conseils.. et vos réactions ! http://blog.mail.yahoo.fr - 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] _ Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Cyclic dependency problem
Hi all.
I have just joined the list, so please forgive me if the exact same
question has already been posted.
Here is my use case :
I have a project CORE_A which exposes a facade in the form of an EJB,
which is built in a separate project EJB_A.
I have a project CORE_B which exposes a facade in the form of an EJB,
which is built in a separate project EJB_B.
CORE_A needs to call remote EJB_B, so it has a dependency on the client
jar of EJB_B.
CORE_B needs to call remote EJB_A, so it has a dependency on the client
jar of EJB_A.
EJB_A depends on CORE_A for its build.
EJB_B depends on CORE_B for its build.
In my CORE_A and CORE_B POM files, I have tried to avoid getting a
cyclic dependency error in the build phase
by :
- using a client classifier for the depency of CORE to EJB client
- using an exclusion
e.g. for the pom.xml of the CORE_A project :
dependency
groupIdcom.acme/groupId
artifactIdEJB-B/artifactId
version${applicationVersion}/version
classifierclient/classifier
exclusions
exclusion
groupIdcom.acme/groupId
artifactIdCORE-B/artifactId
/exclusion
/exclusions
/dependency
But when I launch the install goal, I immediately get a cyclic
dependency error message, which seems to indicate that Maven
is ignoring my classifier or exclusion modifiers, and basing its
graph calculation solely on the list of depencies.
I use Maven 2.0.7.
Has anyone got a solution ?
Regards,
Fabien Coppens
This message contains information that may be privileged or confidential and is
the property of the Capgemini Group. It is intended only for the person to whom
it is addressed. If you are not the intended recipient, you are not authorized
to read, print, retain, copy, disseminate, distribute, or use this message or
any part thereof. If you receive this message in error, please notify the
sender immediately and delete all copies of this message.
Re: m2 ear plugin and resource filters.
You're hacking the ear's plugin own resource directory with a standard
resource. This own resource dir was a design error in the early
days.
Anyway, you might be able to configure a custom execution of the
resource plugin with filtering enabled. But move your files out of
src/main/application first. There's an issue in Jira to automatically
support filtering for this directory. I guess I'll do that.
Vote/comment if you're interested.
Thanks,
Stéphane
Move your stuff to src/main/resources
On 8/28/07, Jonathan Chen [EMAIL PROTECTED] wrote:
Hi all,
I'm running Maven 2.0.7 and I'm trying to get resource filtering
working with m2's ear plugin. I have a file which I'm trying to get
certain properties replaced on a mvn package.
src/main/application/META-INF/geronimo.xml:
?xml version=1.0 encoding=UTF-8?
application
xmlns=http://geronimo.apache.org/xml/ns/j2ee/application-1.2;
xmlns:dep=http://geronimo.apache.org/xml/ns/deployment-1.2;
environment
xmlns=http://geronimo.apache.org/xml/ns/deployment-1.2;
moduleId
groupId${pom.groupId}/groupId
artifactId${pom.artifactId}/artifactId
version${pom.version}/version
typeear/type
/moduleId
/environment
/application
Ideally, the ${pom.*} properties are replaced with the values from
pom.xml; but for some reason, I can't seem to get it working with:
pom.xml:
?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/xsd/maven-4.0.0.xsd;
modelVersion4.0.0/modelVersion
nameEAR goal test/name
groupIdtest/groupId
artifactIdear-goal/artifactId
version1.0-SNAPSHOT/version
packagingear/packaging
build
resources
resource
filteringtrue/filtering
directorysrc/main/application/META-INF/directory
includes
include*.xml/include
/includes
/resource
/resources
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-ear-plugin/artifactId
configuration
version5/version
/configuration
/plugin
/plugins
/build
/project
Can anyone on the list see what I'm doing wrong? Any help appreciated.
Cheers.
--
Jonathan Chen [EMAIL PROTECTED]
--
Don't worry about avoiding temptation,
as you grow older, it starts avoiding you.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Large Systems Suck: This rule is 100% transitive. If you build one,
you suck -- S.Yegge
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
How do I run a bat file as a build
How would I set up a project if I would like a bat file to run? Let's say I have the bat file in c:\bat and its called foo.bat. I have tried to enter a local scm url, but I still get errors: Exception: Cannot checkout sources. The module isn't a directory. I guess I have missed something in the configuration, but I don't really know what to change. -- View this message in context: http://www.nabble.com/How-do-I-run-a-bat-file-as-a-build-tf4342442.html#a12370237 Sent from the Continuum - Users mailing list archive at Nabble.com.
Re: How do I run a bat file as a build
what is your scm url? Joakim Zetterberg a écrit : How would I set up a project if I would like a bat file to run? Let's say I have the bat file in c:\bat and its called foo.bat. I have tried to enter a local scm url, but I still get errors: Exception: Cannot checkout sources. The module isn't a directory. I guess I have missed something in the configuration, but I don't really know what to change.
RE: installing a ueber jar
Thanks Wayne!!
it worked really fine :-)
Now my pom.xml is some like:
...
build
plugins
plugin
artifactIdminijar-maven-plugin/artifactId
groupIdorg.codehaus.mojo/groupId
executions
execution
phasepackage/phase
goals
goalueberjar/goal
/goals
configuration
stripUnusedClassestrue/stripUnusedClasses
/configuration
/execution
/executions
/plugin
plugin
artifactIdbuild-helper-maven-plugin/artifactId
groupIdorg.codehaus.mojo/groupId
executions
execution
goals
goalattach-artifact/goal
/goals
configuration
artifacts
artifact
classifierueber/classifier
filetarget/${artifactId}-${version}-ueber.jar/file
/artifact
/artifacts
/configuration
/execution
/executions
/plugin
/plugins
/build
...
-Original Message-
From: Wayne Fay [mailto:[EMAIL PROTECTED]
Sent: terça-feira, 28 de agosto de 2007 11:38
To: Maven Users List
Subject: Re: installing a ueber jar
Use build-helper-m-p and attach your artifact to the build/project.
Wayne
On 8/28/07, Domingos Antonio Pereira Creado Júnior
[EMAIL PROTECTED] wrote:
Hi there,
I´m developing an applet that has many dependencies. To
speed-up the load phase, I´m using the ueber plugin [1].
The ueber plugins works fine.. It creates a smaller jar,
but with a suffix -uber under target directory.
The issue that I´m facing is how install this ueber jar
under repository?
I´ve already tried many tricks like above, and none work:
- set the final name of the generated jar by ueber equal to
final name.
- configure a install-file execution under pom.xml like:
...
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-install-plugin/artifactId
executions
execution
idinstall2/id
phaseinstall/phase
goals
goalinstall-file/goal
/goals
configuration
groupId${groupId}/groupId
artifactId${artifactId}/artifactId
version${version}-ueber/version
packagingjar/packaging
file
${basedir}/build/${artifactId}-${version}-ueber.jar
/file
generatePomtrue/generatePom
/configuration
/execution
/executions
/plugin
But maven complains that the properties like artifactId is
read-only
Does anyone has a clue about installing a file like uber
under local repository?
Thanks in advance
[1] -
http://mojo.codehaus.org/minijar-maven-plugin/ueberjar-mojo.html
Atenciosamente
Msc. Domingos Creado
DRT - CPqD Telecom IT Solutions
Tel.: +55 19 3705-6423 / Fax: +55 19 3705-7268
Cel.: +55 19 8183-1003
[EMAIL PROTECTED]
www.cpqd.com.br
Que ninguém se engane, só se consegue a simplicidade através de muito
trabalho.
Clarice Lispector
Simplicidade é a sofisticação máxima.
Leonardo da Vinci
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Continuum version 103 (maven2)
Found the problem. Basically CI doesn't work if you have your parent pom at the same level as its child modules because CI creates a temporary directory which breaks the path from the parent to the child. This is true for the stable and 1.1 build. -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: 28 August 2007 16:48 To: [EMAIL PROTECTED] Subject: Re: Continuum version 103 (maven2) Do you use maven 2.0.7? James Clinton a écrit : Hello, I have a project structure like so: - parent - child - child Parent pom is them loaded into CI and the projects are detected. It builds fine, but if there is a compilation error, the status of the build is still 'success'. Is this a known issue? James DISCLAIMER: This e-mail is confidential and may also be legally privileged. If you are not the intended recipient, use of the information contained in this e-mail (including disclosure, copying or distribution) is prohibited and may be unlawful. Please inform the sender and delete the message immediately from your system. This e-mail is attributed to the sender and may not necessarily reflect the views of the Patsystems Group and no member of the Patsystems Group accepts any liability for any action taken in reliance on the contents of this e-mail (other than where it has a legal or regulatory obligation to do so) or for the consequences of any computer viruses which may have been transmitted by this e-mail. The Patsystems Group comprises Patsystems plc and its subsidiary group of companies. DISCLAIMER: This e-mail is confidential and may also be legally privileged. If you are not the intended recipient, use of the information contained in this e-mail (including disclosure, copying or distribution) is prohibited and may be unlawful. Please inform the sender and delete the message immediately from your system. This e-mail is attributed to the sender and may not necessarily reflect the views of the Patsystems Group and no member of the Patsystems Group accepts any liability for any action taken in reliance on the contents of this e-mail (other than where it has a legal or regulatory obligation to do so) or for the consequences of any computer viruses which may have been transmitted by this e-mail. The Patsystems Group comprises Patsystems plc and its subsidiary group of companies.
Re: Maven Multi-Project - Modules are Numbers when checked out --repl y
The problem I have now is when the build fails, say due to a unit test, the status of the build is SUCCESS. Although the log states FAILED. Is there some configuration I am missing here or is the problem related to me setup? It is a known issue in 2.0.7. http://jira.codehaus.org/browse/MNG-3084 You can update the bat file in your local install as described in the bug and it will start working. Emmanuel
Re: Continuum version 103 (maven2)
We don't have an entry in the faq about the bug in mvn.bat from maven 2.0.7 (http://jira.codehaus.org/browse/MNG-3084 ) James Clinton a écrit : Opps - should of read my original post!. Anwser is for Windows the mvn.bat file needs to be altered...I didn't read the faq's properly. -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: 28 August 2007 16:48 To: [EMAIL PROTECTED] Subject: Re: Continuum version 103 (maven2) Do you use maven 2.0.7? James Clinton a écrit : Hello, I have a project structure like so: - parent - child - child Parent pom is them loaded into CI and the projects are detected. It builds fine, but if there is a compilation error, the status of the build is still 'success'. Is this a known issue? James DISCLAIMER: This e-mail is confidential and may also be legally privileged. If you are not the intended recipient, use of the information contained in this e-mail (including disclosure, copying or distribution) is prohibited and may be unlawful. Please inform the sender and delete the message immediately from your system. This e-mail is attributed to the sender and may not necessarily reflect the views of the Patsystems Group and no member of the Patsystems Group accepts any liability for any action taken in reliance on the contents of this e-mail (other than where it has a legal or regulatory obligation to do so) or for the consequences of any computer viruses which may have been transmitted by this e-mail. The Patsystems Group comprises Patsystems plc and its subsidiary group of companies. DISCLAIMER: This e-mail is confidential and may also be legally privileged. If you are not the intended recipient, use of the information contained in this e-mail (including disclosure, copying or distribution) is prohibited and may be unlawful. Please inform the sender and delete the message immediately from your system. This e-mail is attributed to the sender and may not necessarily reflect the views of the Patsystems Group and no member of the Patsystems Group accepts any liability for any action taken in reliance on the contents of this e-mail (other than where it has a legal or regulatory obligation to do so) or for the consequences of any computer viruses which may have been transmitted by this e-mail. The Patsystems Group comprises Patsystems plc and its subsidiary group of companies.
Re: Continuum version 103 (maven2)
Do you use maven 2.0.7? James Clinton a écrit : Hello, I have a project structure like so: - parent - child - child Parent pom is them loaded into CI and the projects are detected. It builds fine, but if there is a compilation error, the status of the build is still 'success'. Is this a known issue? James DISCLAIMER: This e-mail is confidential and may also be legally privileged. If you are not the intended recipient, use of the information contained in this e-mail (including disclosure, copying or distribution) is prohibited and may be unlawful. Please inform the sender and delete the message immediately from your system. This e-mail is attributed to the sender and may not necessarily reflect the views of the Patsystems Group and no member of the Patsystems Group accepts any liability for any action taken in reliance on the contents of this e-mail (other than where it has a legal or regulatory obligation to do so) or for the consequences of any computer viruses which may have been transmitted by this e-mail. The Patsystems Group comprises Patsystems plc and its subsidiary group of companies.
Re: Continuum version 103 (maven2)
yes and no. The problem is the same but not the patch to do, This entry is for an old maven version The fixed script for maven 2.0.7 is : https://svn.apache.org/repos/asf/maven/components/branches/maven-2.0.x/maven-core/src/bin/mvn.bat Emmanuel James Clinton a écrit : See http://maven.apache.org/continuum/faqs.html##how-does-continuum-detect-a-suc cessful-build Sounds like the same issue? Apologies if I'm wrong. James -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: 28 August 2007 16:59 To: [EMAIL PROTECTED] Subject: Re: Continuum version 103 (maven2) We don't have an entry in the faq about the bug in mvn.bat from maven 2.0.7 (http://jira.codehaus.org/browse/MNG-3084 ) James Clinton a écrit : Opps - should of read my original post!. Anwser is for Windows the mvn.bat file needs to be altered...I didn't read the faq's properly. -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: 28 August 2007 16:48 To: [EMAIL PROTECTED] Subject: Re: Continuum version 103 (maven2) Do you use maven 2.0.7? James Clinton a écrit : Hello, I have a project structure like so: - parent - child - child Parent pom is them loaded into CI and the projects are detected. It builds fine, but if there is a compilation error, the status of the build is still 'success'. Is this a known issue? James DISCLAIMER: This e-mail is confidential and may also be legally privileged. If you are not the intended recipient, use of the information contained in this e-mail (including disclosure, copying or distribution) is prohibited and may be unlawful. Please inform the sender and delete the message immediately from your system. This e-mail is attributed to the sender and may not necessarily reflect the views of the Patsystems Group and no member of the Patsystems Group accepts any liability for any action taken in reliance on the contents of this e-mail (other than where it has a legal or regulatory obligation to do so) or for the consequences of any computer viruses which may have been transmitted by this e-mail. The Patsystems Group comprises Patsystems plc and its subsidiary group of companies. DISCLAIMER: This e-mail is confidential and may also be legally privileged. If you are not the intended recipient, use of the information contained in this e-mail (including disclosure, copying or distribution) is prohibited and may be unlawful. Please inform the sender and delete the message immediately from your system. This e-mail is attributed to the sender and may not necessarily reflect the views of the Patsystems Group and no member of the Patsystems Group accepts any liability for any action taken in reliance on the contents of this e-mail (other than where it has a legal or regulatory obligation to do so) or for the consequences of any computer viruses which may have been transmitted by this e-mail. The Patsystems Group comprises Patsystems plc and its subsidiary group of companies. DISCLAIMER: This e-mail is confidential and may also be legally privileged. If you are not the intended recipient, use of the information contained in this e-mail (including disclosure, copying or distribution) is prohibited and may be unlawful. Please inform the sender and delete the message immediately from your system. This e-mail is attributed to the sender and may not necessarily reflect the views of the Patsystems Group and no member of the Patsystems Group accepts any liability for any action taken in reliance on the contents of this e-mail (other than where it has a legal or regulatory obligation to do so) or for the consequences of any computer viruses which may have been transmitted by this e-mail. The Patsystems Group comprises Patsystems plc and its subsidiary group of companies.
classifier for maven deploy plugin
Hi, Is there a way to use a classifier with the maven deploy plugin by configuring the plugin in the pom rather that using command line properties? TIA, John Eurobase International Limited and its subsidiaries (Eurobase) are unable to exercise control over the content of information in E-Mails. Any views and opinions expressed may be personal to the sender and are not necessarily those of Eurobase. Eurobase will not enter into any contractual obligations in respect of any part of its business in any E-mail. Privileged / confidential information may be contained in this message and /or any attachments. This E-mail is intended for the use of the addressee(s) only and may contain confidential information. If you are not the / an intended recipient, you are hereby notified that any use or dissemination of this communication is strictly prohibited. If you receive this transmission in error, please notify us immediately, and then delete this E-mail. Neither the sender nor Eurobase accepts any liability whatsoever for any defects of any kind either in or arising from this E-mail transmission. E-Mail transmission cannot be guaranteed to be secure or error-free, as messages can be intercepted, lost, corrupted, destroyed, contain viruses, or arrive late or incomplete. Eurobase does not accept any responsibility for viruses and it is your responsibility to scan any attachments. Eurobase Systems Limited is the main trading company in the Eurobase International Group; registered in England and Wales as company number 02251162; registered address: Essex House, 2 County Place, Chelmsford, Essex CM2 0RE, UK.
Re: Associate a default goal for a plugin and type the plugin name only on cmdln
Thanks Remy... On 8/28/07, Rémy Sanlaville [EMAIL PROTECTED] wrote: not in maven 2. It was only in maven 1. In m2 you have to call aPlugin:aGoal Yes, it's not available in maven 2. I ask for a such feature some time ago and I had this reply that explain why it is not so easy. http://www.nabble.com/-Proposal--New-profile-activation-tf3240038s177.html#a9031422 Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to get Maven to include persistence.xml into a web app??
Thank!! 2007/8/28, Tim Kettler [EMAIL PROTECTED]: Strange, it's working for me with this simple test project: project modelVersion4.0.0/modelVersion artifactIdmy-test-app/artifactId groupIdmy-test-group/groupId version1.0-SNAPSHOT/version packagingwar/packaging build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-war-plugin/artifactId configuration webResources resource directorysrc/conf/directory !-- override the destination directory for this resource -- targetPathMETA-INF/targetPath includes includepersistence.xml/include /includes /resource /webResources /configuration /plugin /plugins /build /project Additionally you have to put an empty stub in 'src/main/webapp/WEB-INF/web.xml' and in 'src/conf/persistence.xml'. The war-plugin version I use is 2.0.2. -Tim Julien Martin schrieb: Thanks Tim for you suggestion. I thought I was getting there but apparently the targetPath is COMPLETELY ignored by Maven... Here is where the persistence.xml is copied: the root of the war... Here is my POM for your info. Tis almost identical to your suggestion: 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.calyonfinancial/groupId artifactIdprotide/artifactId packagingwar/packaging version1.0-SNAPSHOT/version nameProtideWeb/name build sourceDirectorysrc/sourceDirectory outputDirectorybuild/outputDirectory finalNameProtideWeb/finalName plugins plugin artifactIdmaven-compiler-plugin/artifactId configuration source1.5/source target1.5/target /configuration /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-war-plugin/artifactId version2.0/version configuration warSourceDirectoryweb/warSourceDirectory webResources resource directorysrc/conf/directory targetPathMETA-INF/targetPath includes includepersistence.xml/include /includes /resource /webResources /configuration /plugin /plugins /build dependencies dependency groupIdorg.hibernate/groupId artifactIdhibernate/artifactId version3.2.1.ga/version /dependency dependency groupIdorg.hibernate/groupId artifactIdhibernate-annotations/artifactId version3.2.1.ga/version /dependency dependency groupIdorg.hibernate/groupId artifactIdhibernate-entitymanager/artifactId version3.2.1.ga/version /dependency dependency groupIdorg.hibernate/groupId artifactIdhibernate-commons-annotations/artifactId version3.3.0.ga/version /dependency dependency groupIdorg.hibernate/groupId artifactIdhibernate-validator/artifactId version3.0.0.ga/version /dependency dependency groupIdjavax.persistence/groupId artifactIdpersistence-api/artifactId version1.0/version /dependency dependency groupIdlog4j/groupId artifactIdlog4j/artifactId version1.2.14/version /dependency dependency groupIdcom.sun.xml.bind/groupId artifactIdjaxb-impl/artifactId version2.0/version /dependency dependency groupIdcom.sun.xml.bind/groupId artifactIdjaxb-xjc/artifactId version2.0/version /dependency dependency groupIdjavax.xml.bind/groupId artifactIdjaxb-api/artifactId version2.0/version /dependency !-- dependency groupIdorg.apache.maven/groupId artifactIdmaven-project/artifactId version2.0.4/version /dependency dependency groupIdorg.apache.maven/groupId
targetPath tag COMPLETELY ignored by Maven......
Hello, Apparently the targetPath tag is COMPLETELY ignored by Maven... The persistence.xml is copied at the root of the war... Can anyone please help? Julien. Here is my POM: code: -- 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; http://maven.apache.org/maven-v4_0_0.xsd modelVersion4.0.0/modelVersion groupIdcom.calyonfinancial/groupId artifactIdprotide/artifactId packagingwar/packaging version1.0-SNAPSHOT/version nameProtideWeb/name build sourceDirectorysrc/sourceDirectory outputDirectorybuild/outputDirectory finalNameProtideWeb/finalName plugins plugin artifactIdmaven-compiler-plugin/artifactId configuration source1.5/source target1.5/target /configuration /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-war-plugin/artifactId version2.0/version configuration warSourceDirectoryweb/warSourceDirectory webResources resource directorysrc/conf/directory targetPathMETA-INF/targetPath includes includepersistence.xml/include /includes /resource /webResources /configuration /plugin /plugins /build dependencies dependency groupIdorg.hibernate/groupId artifactIdhibernate/artifactId version3.2.1.ga/version /dependency dependency groupIdorg.hibernate/groupId artifactIdhibernate-annotations/artifactId version3.2.1.ga/version /dependency dependency groupIdorg.hibernate/groupId artifactIdhibernate-entitymanager/artifactId version3.2.1.ga/version /dependency dependency groupIdorg.hibernate/groupId artifactIdhibernate-commons-annotations/artifactId version3.3.0.ga/version /dependency dependency groupIdorg.hibernate/groupId artifactIdhibernate-validator/artifactId version3.0.0.ga/version /dependency dependency groupIdjavax.persistence/groupId artifactIdpersistence-api/artifactId version1.0/version /dependency dependency groupIdlog4j/groupId artifactIdlog4j/artifactId version1.2.14/version /dependency dependency groupIdcom.sun.xml.bind/groupId artifactIdjaxb-impl/artifactId version2.0/version /dependency dependency groupIdcom.sun.xml.bind/groupId artifactIdjaxb-xjc/artifactId version2.0/version /dependency dependency groupIdjavax.xml.bind/groupId artifactIdjaxb-api/artifactId version2.0/version /dependency !-- dependency groupIdorg.apache.maven/groupId artifactIdmaven-project/artifactId version2.0.4/version /dependency dependency groupIdorg.apache.maven/groupId artifactIdmaven-plugin-api/artifactId version2.0.4/version /dependency -- dependency groupIdjdbc/groupId artifactIdas400/artifactId version5.1.0.1/version /dependency dependency groupIdjavax.xml.bind/groupId artifactIdjsr173_api/artifactId version1.0/version /dependency dependency groupIdorg.apache.myfaces.core/groupId artifactIdmyfaces-api/artifactId version1.1.5/version /dependency dependency groupIdorg.apache.myfaces.core/groupId artifactIdmyfaces-impl/artifactId version1.1.5/version /dependency dependency groupIdorg.apache.myfaces.tomahawk/groupId artifactIdtomahawk/artifactId version1.1.6/version /dependency dependency groupIdjavax.servlet/groupId artifactIdservlet-api/artifactId version2.4/version scopeprovided/scope /dependency dependency groupIdjavax.servlet/groupId artifactIdjsp-api/artifactId version2.0/version scopeprovided/scope /dependency dependency groupIdorg.ajax4jsf/groupId
Re: How to get Maven to include persistence.xml into a web app??
Strange, it's working for me with this simple test project: project modelVersion4.0.0/modelVersion artifactIdmy-test-app/artifactId groupIdmy-test-group/groupId version1.0-SNAPSHOT/version packagingwar/packaging build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-war-plugin/artifactId configuration webResources resource directorysrc/conf/directory !-- override the destination directory for this resource -- targetPathMETA-INF/targetPath includes includepersistence.xml/include /includes /resource /webResources /configuration /plugin /plugins /build /project Additionally you have to put an empty stub in 'src/main/webapp/WEB-INF/web.xml' and in 'src/conf/persistence.xml'. The war-plugin version I use is 2.0.2. -Tim Julien Martin schrieb: Thanks Tim for you suggestion. I thought I was getting there but apparently the targetPath is COMPLETELY ignored by Maven... Here is where the persistence.xml is copied: the root of the war... Here is my POM for your info. Tis almost identical to your suggestion: 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.calyonfinancial/groupId artifactIdprotide/artifactId packagingwar/packaging version1.0-SNAPSHOT/version nameProtideWeb/name build sourceDirectorysrc/sourceDirectory outputDirectorybuild/outputDirectory finalNameProtideWeb/finalName plugins plugin artifactIdmaven-compiler-plugin/artifactId configuration source1.5/source target1.5/target /configuration /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-war-plugin/artifactId version2.0/version configuration warSourceDirectoryweb/warSourceDirectory webResources resource directorysrc/conf/directory targetPathMETA-INF/targetPath includes includepersistence.xml/include /includes /resource /webResources /configuration /plugin /plugins /build dependencies dependency groupIdorg.hibernate/groupId artifactIdhibernate/artifactId version3.2.1.ga/version /dependency dependency groupIdorg.hibernate/groupId artifactIdhibernate-annotations/artifactId version3.2.1.ga/version /dependency dependency groupIdorg.hibernate/groupId artifactIdhibernate-entitymanager/artifactId version3.2.1.ga/version /dependency dependency groupIdorg.hibernate/groupId artifactIdhibernate-commons-annotations/artifactId version3.3.0.ga/version /dependency dependency groupIdorg.hibernate/groupId artifactIdhibernate-validator/artifactId version3.0.0.ga/version /dependency dependency groupIdjavax.persistence/groupId artifactIdpersistence-api/artifactId version1.0/version /dependency dependency groupIdlog4j/groupId artifactIdlog4j/artifactId version1.2.14/version /dependency dependency groupIdcom.sun.xml.bind/groupId artifactIdjaxb-impl/artifactId version2.0/version /dependency dependency groupIdcom.sun.xml.bind/groupId artifactIdjaxb-xjc/artifactId version2.0/version /dependency dependency groupIdjavax.xml.bind/groupId artifactIdjaxb-api/artifactId version2.0/version /dependency !-- dependency groupIdorg.apache.maven/groupId artifactIdmaven-project/artifactId version2.0.4/version /dependency dependency groupIdorg.apache.maven/groupId artifactIdmaven-plugin-api/artifactId version2.0.4/version /dependency -- dependency groupIdjdbc/groupId artifactIdas400/artifactId version5.1.0.1/version /dependency dependency
Can't find settings.xml
We occasionally have the following error: Error reading settings.xml: Error reading settings file Anyone seen this before? Stinks to have a 90+ min build fail even though this file is there... The solution seems to be to delete it (and let the boot strapping process copy it back in there).
Re: classifier for maven deploy plugin
I am going to assume that you want to deploy artifacts that are not built by maven. You can create a pom and configure build-helper-maven-plugin to attach all your artifacts to maven, and finally call 'maven deploy' -D On 8/28/07, John Coleman [EMAIL PROTECTED] wrote: Hi, Is there a way to use a classifier with the maven deploy plugin by configuring the plugin in the pom rather that using command line properties? TIA, John Eurobase International Limited and its subsidiaries (Eurobase) are unable to exercise control over the content of information in E-Mails. Any views and opinions expressed may be personal to the sender and are not necessarily those of Eurobase. Eurobase will not enter into any contractual obligations in respect of any part of its business in any E-mail. Privileged / confidential information may be contained in this message and /or any attachments. This E-mail is intended for the use of the addressee(s) only and may contain confidential information. If you are not the / an intended recipient, you are hereby notified that any use or dissemination of this communication is strictly prohibited. If you receive this transmission in error, please notify us immediately, and then delete this E-mail. Neither the sender nor Eurobase accepts any liability whatsoever for any defects of any kind either in or arising from this E-mail transmission. E-Mail transmission cannot be guaranteed to be secure or error-free, as messages can be intercepted, lost, corrupted, destroyed, contain viruses, or arrive late or incomplete. Eurobase does not accept any responsibility for viruses and it is your responsibility to scan any attachments. Eurobase Systems Limited is the main trading company in the Eurobase International Group; registered in England and Wales as company number 02251162; registered address: Essex House, 2 County Place, Chelmsford, Essex CM2 0RE, UK. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: targetPath tag COMPLETELY ignored by Maven......
Try bumping your version to 2.0.2 which is apparently the latest available... http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-war-plugin/ Don't know if that will do anything, just an idea. Wayne On 8/28/07, Julien Martin [EMAIL PROTECTED] wrote: Hello, Apparently the targetPath tag is COMPLETELY ignored by Maven... The persistence.xml is copied at the root of the war... Can anyone please help? Julien. Here is my POM: code: -- 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; http://maven.apache.org/maven-v4_0_0.xsd modelVersion4.0.0/modelVersion groupIdcom.calyonfinancial/groupId artifactIdprotide/artifactId packagingwar/packaging version1.0-SNAPSHOT/version nameProtideWeb/name build sourceDirectorysrc/sourceDirectory outputDirectorybuild/outputDirectory finalNameProtideWeb/finalName plugins plugin artifactIdmaven-compiler-plugin/artifactId configuration source1.5/source target1.5/target /configuration /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-war-plugin/artifactId version2.0/version configuration warSourceDirectoryweb/warSourceDirectory webResources resource directorysrc/conf/directory targetPathMETA-INF/targetPath includes includepersistence.xml/include /includes /resource /webResources /configuration /plugin /plugins /build dependencies dependency groupIdorg.hibernate/groupId artifactIdhibernate/artifactId version3.2.1.ga/version /dependency dependency groupIdorg.hibernate/groupId artifactIdhibernate-annotations/artifactId version3.2.1.ga/version /dependency dependency groupIdorg.hibernate/groupId artifactIdhibernate-entitymanager/artifactId version3.2.1.ga/version /dependency dependency groupIdorg.hibernate/groupId artifactIdhibernate-commons-annotations/artifactId version3.3.0.ga/version /dependency dependency groupIdorg.hibernate/groupId artifactIdhibernate-validator/artifactId version3.0.0.ga/version /dependency dependency groupIdjavax.persistence/groupId artifactIdpersistence-api/artifactId version1.0/version /dependency dependency groupIdlog4j/groupId artifactIdlog4j/artifactId version1.2.14/version /dependency dependency groupIdcom.sun.xml.bind/groupId artifactIdjaxb-impl/artifactId version2.0/version /dependency dependency groupIdcom.sun.xml.bind/groupId artifactIdjaxb-xjc/artifactId version2.0/version /dependency dependency groupIdjavax.xml.bind/groupId artifactIdjaxb-api/artifactId version2.0/version /dependency !-- dependency groupIdorg.apache.maven/groupId artifactIdmaven-project/artifactId version2.0.4/version /dependency dependency groupIdorg.apache.maven/groupId artifactIdmaven-plugin-api/artifactId version2.0.4/version /dependency -- dependency groupIdjdbc/groupId artifactIdas400/artifactId version5.1.0.1/version /dependency dependency groupIdjavax.xml.bind/groupId artifactIdjsr173_api/artifactId version1.0/version /dependency dependency groupIdorg.apache.myfaces.core/groupId artifactIdmyfaces-api/artifactId version1.1.5/version /dependency dependency groupIdorg.apache.myfaces.core/groupId artifactIdmyfaces-impl/artifactId version1.1.5/version /dependency dependency groupIdorg.apache.myfaces.tomahawk/groupId artifactIdtomahawk/artifactId version1.1.6/version /dependency dependency groupIdjavax.servlet/groupId artifactIdservlet-api/artifactId version2.4/version
Re: targetPath tag COMPLETELY ignored by Maven......
Thanks! That was the problem... Julien. 2007/8/28, Wayne Fay [EMAIL PROTECTED]: Try bumping your version to 2.0.2 which is apparently the latest available... http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-war-plugin/ Don't know if that will do anything, just an idea. Wayne On 8/28/07, Julien Martin [EMAIL PROTECTED] wrote: Hello, Apparently the targetPath tag is COMPLETELY ignored by Maven... The persistence.xml is copied at the root of the war... Can anyone please help? Julien. Here is my POM: code: -- 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; http://maven.apache.org/maven-v4_0_0.xsd modelVersion4.0.0/modelVersion groupIdcom.calyonfinancial/groupId artifactIdprotide/artifactId packagingwar/packaging version1.0-SNAPSHOT/version nameProtideWeb/name build sourceDirectorysrc/sourceDirectory outputDirectorybuild/outputDirectory finalNameProtideWeb/finalName plugins plugin artifactIdmaven-compiler-plugin/artifactId configuration source1.5/source target1.5/target /configuration /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-war-plugin/artifactId version2.0/version configuration warSourceDirectoryweb/warSourceDirectory webResources resource directorysrc/conf/directory targetPathMETA-INF/targetPath includes includepersistence.xml/include /includes /resource /webResources /configuration /plugin /plugins /build dependencies dependency groupIdorg.hibernate/groupId artifactIdhibernate/artifactId version3.2.1.ga/version /dependency dependency groupIdorg.hibernate/groupId artifactIdhibernate-annotations/artifactId version3.2.1.ga/version /dependency dependency groupIdorg.hibernate/groupId artifactIdhibernate-entitymanager/artifactId version3.2.1.ga/version /dependency dependency groupIdorg.hibernate/groupId artifactIdhibernate-commons-annotations/artifactId version3.3.0.ga/version /dependency dependency groupIdorg.hibernate/groupId artifactIdhibernate-validator/artifactId version3.0.0.ga/version /dependency dependency groupIdjavax.persistence/groupId artifactIdpersistence-api/artifactId version1.0/version /dependency dependency groupIdlog4j/groupId artifactIdlog4j/artifactId version1.2.14/version /dependency dependency groupIdcom.sun.xml.bind/groupId artifactIdjaxb-impl/artifactId version2.0/version /dependency dependency groupIdcom.sun.xml.bind/groupId artifactIdjaxb-xjc/artifactId version2.0/version /dependency dependency groupIdjavax.xml.bind/groupId artifactIdjaxb-api/artifactId version2.0/version /dependency !-- dependency groupIdorg.apache.maven/groupId artifactIdmaven-project/artifactId version2.0.4/version /dependency dependency groupIdorg.apache.maven/groupId artifactIdmaven-plugin-api/artifactId version2.0.4/version /dependency -- dependency groupIdjdbc/groupId artifactIdas400/artifactId version5.1.0.1/version /dependency dependency groupIdjavax.xml.bind/groupId artifactIdjsr173_api/artifactId version1.0/version /dependency dependency groupIdorg.apache.myfaces.core/groupId artifactIdmyfaces-api/artifactId version1.1.5/version /dependency dependency groupIdorg.apache.myfaces.core/groupId artifactIdmyfaces-impl/artifactId version1.1.5/version /dependency dependency groupIdorg.apache.myfaces.tomahawk/groupId
environment variable for location of settings.xml?
All, Does maven 2.x looking at any environment variables for the location of settings.xml? I know the default location is user_home_dir/.m2 but I want to be able to change the default behavior when you type mvn. Thanks. B.
Re: environment variable for location of settings.xml?
mvn -? -s,--settings Alternate path for the user settings file Wayne On 8/28/07, Baz [EMAIL PROTECTED] wrote: All, Does maven 2.x looking at any environment variables for the location of settings.xml? I know the default location is user_home_dir/.m2 but I want to be able to change the default behavior when you type mvn. Thanks. B. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Community review of the next commons-logging pom
Yes, it is enough, but by adding optionaltrue/optional we wanted to show that the dependency is also optional. You will only need it if you use certain features of commons-logging. And scopeprovided/scope says that it will be provided by the container, if you decide to use those features. Stephane Nicoll wrote: For the servlet-api dependency, provided scope is enough (provided is not transitive). Thanks, Stéphane On 8/27/07, Dennis Lundberg [EMAIL PROTECTED] wrote: Hi all The poms for commons logging has taken some beating on this list over the years. The reason for that has been the dependencies section. Previous poms of commons-logging was created for Maven 1. These were then converted into Maven 2 poms with various degree of success. In particular the scope wasn't set properly. We are now preparing the next release of commons-logging (version 1.1.1) which will be built with Maven 2. That means that the pom that ends up in the Maven 2 repository will be the same one that we have created. To make sure that we have covered all bases this time we invite you, the community, to help us get it right. The current pom.xml is available for your viewing in our subversion repository: https://svn.apache.org/viewvc/commons/proper/logging/trunk/pom.xml?revision=568979view=markup Please post any comments you have on the pom to this list, and I will bring the over to the commons community. -- Dennis Lundberg Apache Commons committer and PMC member - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Community review of the next commons-logging pom
Michael McCallum wrote: IMO the log4j, logkit, avalon dependencies all need to go... I as I imagine most people do only use one logging implementation in the deployed systems why introduce a dependency on several implementations at the top level? Commons-logging only has one level, the top level. So these all need to be in the one, and only, pom we have. If we decide in the future (not for this patch release) to mavenize commons-logging there would be a hierarchy of poms. check out http://www.slf4j.com for an appropriate break up of the artifacts and use cases I will not get into a debate on which logging library to use. The purpose of my first mail was to make sure that the pom for commons-logging is as good as it can be, for the way commons-logging works. I've generally stopped using dependencyManagement in favour of dependency composition On Tuesday 28 August 2007 10:06, Stephane Nicoll wrote: For the servlet-api dependency, provided scope is enough (provided is not transitive). Thanks, Stéphane On 8/27/07, Dennis Lundberg [EMAIL PROTECTED] wrote: Hi all The poms for commons logging has taken some beating on this list over the years. The reason for that has been the dependencies section. Previous poms of commons-logging was created for Maven 1. These were then converted into Maven 2 poms with various degree of success. In particular the scope wasn't set properly. We are now preparing the next release of commons-logging (version 1.1.1) which will be built with Maven 2. That means that the pom that ends up in the Maven 2 repository will be the same one that we have created. To make sure that we have covered all bases this time we invite you, the community, to help us get it right. The current pom.xml is available for your viewing in our subversion repository: https://svn.apache.org/viewvc/commons/proper/logging/trunk/pom.xml?revisi on=568979view=markup Please post any comments you have on the pom to this list, and I will bring the over to the commons community. -- Dennis Lundberg Apache Commons committer and PMC member - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: environment variable for location of settings.xml?
Other than -s, nothing else is built in. Of course, you can easily alter the mvn.bat file for your company and add other parameters, check for environment variables etc. But then you need to make sure everyone is running your modified mvn.bat file. Wayne On 8/28/07, Baz [EMAIL PROTECTED] wrote: Wayne, Thanks for your reply. If I dont use -s then it will only look at user_home/.m2 ? No environment variable will change this behaviour right? B. On 8/28/07, Wayne Fay [EMAIL PROTECTED] wrote: mvn -? -s,--settings Alternate path for the user settings file Wayne On 8/28/07, Baz [EMAIL PROTECTED] wrote: All, Does maven 2.x looking at any environment variables for the location of settings.xml? I know the default location is user_home_dir/.m2 but I want to be able to change the default behavior when you type mvn. Thanks. B. - 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]
RE: integration testing
Ok, this looks like I cleared this up myself, but the NEW question is, what happens when there is ANOTHER module that depends on the assembly of another. So one of our app server artifact has integration tests, but it needs one of these registry type servers up and running. How can I say, during your integration test phase, install reg-srv and start it up THEN run your own integration tests?? -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 28, 2007 2:40 PM To: Maven Users List Subject: integration testing I'm kinda dancing around a local solution, but how is the rest of the maven world doing something like integration tests where the tests require a running instance of the code they're trying to test? We have things like registry services that we'd like to integration test, but the tests would require an instance of the actual registry to be up and running. The problem I'm seeing with this approach is we'd have to do something like mvn install assembly:directory-inline integrationtestgoal site which seems kinda hokey. How is everyone else doing this? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: environment variable for location of settings.xml?
Wayne, Thanks for your reply. If I dont use -s then it will only look at user_home/.m2 ? No environment variable will change this behaviour right? B. On 8/28/07, Wayne Fay [EMAIL PROTECTED] wrote: mvn -? -s,--settings Alternate path for the user settings file Wayne On 8/28/07, Baz [EMAIL PROTECTED] wrote: All, Does maven 2.x looking at any environment variables for the location of settings.xml? I know the default location is user_home_dir/.m2 but I want to be able to change the default behavior when you type mvn. Thanks. B. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Community review of the next commons-logging pom
Marcel Schutte wrote: Hi Dennis, I've got two remarks: - You should really make sure that all plugins have a version declared. There are definitely differences between versions, so the reproducibility of your builds can only be guaranteed by using explicit versions. Yes we should, as pointed out by Wayne as well. We're missing versions for antrun-plugin and assembly-plugin as far as I can see. Note that some versions are specified in the parent pom. - The artifacts commons-logging, commons-logging-api and commons-logging-adapters are not mutually exclusive. By that I mean that they share some classes. The problem with this is that it is possible for an artifact to get transitive dependencies on different versions of the same classes (commons-logging-1.1.1 and commons-logging-api-1.1.2 for instance). This can be solved by splitting the code up into different projects and having them depend on each other. Yes, this is unfortunate, but not something that we can change without breaking backward compatibility. So it will have to wait for the next major version. We have instructions on our web site explaining when to use which jar. Regards, Marcel Thanks Marcel! - Original Message From: Dennis Lundberg [EMAIL PROTECTED] To: Maven Users List users@maven.apache.org Sent: Monday, August 27, 2007 8:30:37 PM Subject: Community review of the next commons-logging pom Hi all The poms for commons logging has taken some beating on this list over the years. The reason for that has been the dependencies section. Previous poms of commons-logging was created for Maven 1. These were then converted into Maven 2 poms with various degree of success. In particular the scope wasn't set properly. We are now preparing the next release of commons-logging (version 1.1.1) which will be built with Maven 2. That means that the pom that ends up in the Maven 2 repository will be the same one that we have created. To make sure that we have covered all bases this time we invite you, the community, to help us get it right. The current pom.xml is available for your viewing in our subversion repository: https://svn.apache.org/viewvc/commons/proper/logging/trunk/pom.xml?revision=568979view=markup Please post any comments you have on the pom to this list, and I will bring the over to the commons community. -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
integration testing
I'm kinda dancing around a local solution, but how is the rest of the maven world doing something like integration tests where the tests require a running instance of the code they're trying to test? We have things like registry services that we'd like to integration test, but the tests would require an instance of the actual registry to be up and running. The problem I'm seeing with this approach is we'd have to do something like mvn install assembly:directory-inline integrationtestgoal site which seems kinda hokey. How is everyone else doing this?
Re: Community review of the next commons-logging pom
This is the OSGi technical whitepaper: http://www.osgi.org/documents/collateral/OSGiTechnicalWhitePaper.pdf . Most relevant here is the Modularity section of the Architecture chapter. To be usable in an OSGi setting, the jar manifest needs to have some entries added. Most important are the name and version, and a list of packages that are provided and/or used by the plugin. The Apache Felix project has a maven-bundle-plugin that automates this process. More info here: http://cwiki.apache.org/confluence/display/FELIX/Maven+Bundle+Plugin+%28BND%29 One of the things you can also do with this plugin, is select which packages end up in your jar. Looking at the current POM, that might be useful. On 8/27/07, Dennis Lundberg [EMAIL PROTECTED] wrote: Hi Tom I've heard the term OSGi from time to time, but have never took the time to learn more about it. Do you know of a good place where I can find out more about it? A quick look at Google suggests that it has something to do with entries in the manifest in the jar file, is that correct? What would they look like and what is the benefit for the community if we add them? Tom Huybrechts wrote: Is there any chance that OSGi headers could be added ? On 8/27/07, Dennis Lundberg [EMAIL PROTECTED] wrote: Hi all The poms for commons logging has taken some beating on this list over the years. The reason for that has been the dependencies section. Previous poms of commons-logging was created for Maven 1. These were then converted into Maven 2 poms with various degree of success. In particular the scope wasn't set properly. We are now preparing the next release of commons-logging (version 1.1.1) which will be built with Maven 2. That means that the pom that ends up in the Maven 2 repository will be the same one that we have created. To make sure that we have covered all bases this time we invite you, the community, to help us get it right. The current pom.xml is available for your viewing in our subversion repository: https://svn.apache.org/viewvc/commons/proper/logging/trunk/pom.xml?revision=568979view=markup Please post any comments you have on the pom to this list, and I will bring the over to the commons community. -- Dennis Lundberg Apache Commons committer and PMC member - 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] -- Dennis Lundberg - 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]
Re: maven plugin for ckjm ...
Finally got around to submitting the code into the Sandbox... Thanks in advance for any feedback. You can find the (rough draft) code for the ckjm-maven-plugin in the Codehaus Sandbox: https://svn.codehaus.org/mojo/trunk/sandbox/ckjm-maven-plugin I also deployed the snapshot and site, so you could use the snapshot if you didn't want to build and install the code yourself. The site is here: http://mojo.codehaus.org/ckjm-maven-plugin/ Wayne On 8/16/07, Giovanni Azua [EMAIL PROTECTED] wrote: Wow cool! That was fast :) so we would get xml but no html or? Many many thanks! Good job! Regards, Giovanni -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Thursday, August 16, 2007 5:23 AM To: Maven Users List Subject: Re: maven plugin for ckjm ... I got bored and wrote the plugin tonight... ;-) For now, it simply outputs a ckjm.xml file (or plain text file) in ./target. If you want to do the full run ckjm, then make a report with it and add it to the site then you will really need to handle that bit yourself. At least, if you want that report in any reasonable time period... For now, I'll propose this plugin at Codehaus (Mojo project) and, assuming its accepted, you'll see it in the sandbox shortly. I also built a test project so you can see it working. Wayne On 8/15/07, Wayne Fay [EMAIL PROTECTED] wrote: If you want to get ckjm functionality in Maven, I'd encourage you to look into creating the plugin yourself. Its really not that tough in general. Wayne On 8/15/07, Giovanni Azua [EMAIL PROTECTED] wrote: ckjm and Jdepend have overlapping only couple of same metrics e.g. AC but Jdepend misses the most important ones e.g. WMC, RFC and LCOM. -Original Message- From: Mick Knutson [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 15, 2007 8:40 PM To: Maven Users List Subject: Re: maven plugin for ckjm ... this sounds like JDepend and there is a plugin for that On 8/15/07, Giovanni Azua [EMAIL PROTECTED] wrote: Hi all, Any existing plugin around ckjm? http://www.spinellis.gr/sw/ckjm/ regards, Giovanni - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven plugin for ckjm ...
One last thing I forgot... Since the ckjm utility itself does not currently exist in the Central repo, you will need to download it from the site and mvn install it with groupId=gr.spinellis, artifactId=ckjm, and version=1.8 so the ckjm-maven-plugin can find it and use it as needed. Wayne On 8/28/07, Wayne Fay [EMAIL PROTECTED] wrote: Finally got around to submitting the code into the Sandbox... Thanks in advance for any feedback. You can find the (rough draft) code for the ckjm-maven-plugin in the Codehaus Sandbox: https://svn.codehaus.org/mojo/trunk/sandbox/ckjm-maven-plugin I also deployed the snapshot and site, so you could use the snapshot if you didn't want to build and install the code yourself. The site is here: http://mojo.codehaus.org/ckjm-maven-plugin/ Wayne On 8/16/07, Giovanni Azua [EMAIL PROTECTED] wrote: Wow cool! That was fast :) so we would get xml but no html or? Many many thanks! Good job! Regards, Giovanni -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Thursday, August 16, 2007 5:23 AM To: Maven Users List Subject: Re: maven plugin for ckjm ... I got bored and wrote the plugin tonight... ;-) For now, it simply outputs a ckjm.xml file (or plain text file) in ./target. If you want to do the full run ckjm, then make a report with it and add it to the site then you will really need to handle that bit yourself. At least, if you want that report in any reasonable time period... For now, I'll propose this plugin at Codehaus (Mojo project) and, assuming its accepted, you'll see it in the sandbox shortly. I also built a test project so you can see it working. Wayne On 8/15/07, Wayne Fay [EMAIL PROTECTED] wrote: If you want to get ckjm functionality in Maven, I'd encourage you to look into creating the plugin yourself. Its really not that tough in general. Wayne On 8/15/07, Giovanni Azua [EMAIL PROTECTED] wrote: ckjm and Jdepend have overlapping only couple of same metrics e.g. AC but Jdepend misses the most important ones e.g. WMC, RFC and LCOM. -Original Message- From: Mick Knutson [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 15, 2007 8:40 PM To: Maven Users List Subject: Re: maven plugin for ckjm ... this sounds like JDepend and there is a plugin for that On 8/15/07, Giovanni Azua [EMAIL PROTECTED] wrote: Hi all, Any existing plugin around ckjm? http://www.spinellis.gr/sw/ckjm/ regards, Giovanni - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Question on maven-buildnumber-plugin
I've been amazed myself by the fact that the plugin (nor any other one)
doesn't just provide a straight-up timestamp. buildnumber plugin comes the
closest, but if you want to use both svn version number and a timestamp, you
are frustratingly out of luck. Looking at buildnumber plugin source, it'd be
super simple to add the timestamp as different property rather than re-using
buildNumber. Hey Julian, any chance you could add ${timestamp} in the next
version? I'm sure a lot of people would be grateful for this, so that not
everyone would need to create weird hacks or implement their plugin versions
just for this.
Kalle
On 8/20/07, [EMAIL PROTECTED] [EMAIL PROTECTED]
wrote:
Hi,
I'm using the maven-buildnumber--plugin version 0.9.5
It works but I would like to have both a timestamp and the build number
from svn?
Is this possible?
Regards
Gunnar
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Question on maven-buildnumber-plugin
There is something like this in the sandbox:
https://svn.apache.org/repos/asf/maven/sandbox/trunk/plugins/maven-property-setting-plugin/
You'll have to build it yourself. I haven't tried it, but the example
seems to indicate that it does what you are looking for.
Please provide feedback to this list if you find the plugin useful.
Kalle Korhonen wrote:
I've been amazed myself by the fact that the plugin (nor any other one)
doesn't just provide a straight-up timestamp. buildnumber plugin comes the
closest, but if you want to use both svn version number and a timestamp, you
are frustratingly out of luck. Looking at buildnumber plugin source, it'd be
super simple to add the timestamp as different property rather than re-using
buildNumber. Hey Julian, any chance you could add ${timestamp} in the next
version? I'm sure a lot of people would be grateful for this, so that not
everyone would need to create weird hacks or implement their plugin versions
just for this.
Kalle
On 8/20/07, [EMAIL PROTECTED] [EMAIL PROTECTED]
wrote:
Hi,
I'm using the maven-buildnumber--plugin version 0.9.5
It works but I would like to have both a timestamp and the build number
from svn?
Is this possible?
Regards
Gunnar
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Dennis Lundberg
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: m2 ear plugin and resource filters.
On Tue, Aug 28, 2007 at 05:32:25PM +0200, Stephane Nicoll wrote: You're hacking the ear's plugin own resource directory with a standard resource. This own resource dir was a design error in the early days. Anyway, you might be able to configure a custom execution of the resource plugin with filtering enabled. But move your files out of src/main/application first. There's an issue in Jira to automatically support filtering for this directory. I guess I'll do that. Thanks for that. The vote is in. -- Jonathan Chen [EMAIL PROTECTED] -- The reason why worry kills more people than work is that more people worry than work. - Robert Frost - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Community review of the next commons-logging pom
but i want it managed across 75 artifacts in 11 groups with 9 aggregations... using inheritance to manage a change in the version of spring for example is way too time consuming and prone to error. Unless i specify all the deps in the aggregation i can never be sure of what version of any library i actually end up with it might make more sense if you saw how i have the structure set up... the most important part of the development environment for me is that i can check out any maven artifact in isolation and work on it and release it... On Wednesday 29 August 2007 02:06, Jörg Schaible wrote: Michael McCallum wrote on Tuesday, August 28, 2007 2:39 PM: OK. But this will not help you, if you include another artifact that depends transitively on Spring or Hibernate in different versions. And therefore we use a company or at least a master POM for a project with a dependencyManagement section. This way you can overwrite the versions of the transitive deps. incorrect. maven will resolve the dependencies from closest to furtherest but not tranverse transitions if there is a better match. So if I hide all of the transitions behind a composition in all cases That's the point. By using the compositions you have to update them or create new ones everytime you add a new dep. I simply add it to my dependencyManagement. - which means i have to exclude deps from 3rd party libraries in some cases - then the spring libraries are only resolved as transitions of composition and nothing else... as you can have on one instance of an artifact in the graph that gets selected there is on one set of transitions from the selected compositions... and voila consistent dependencies Since the depMgmnt oiverwrites the version of the inherited deps: voila no inconsistent dep ;-) But you have your point. By using compositions you can combine them individually, while the depMgmnt approach is kind of all or nothing for a project. - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Michael McCallum Enterprise Engineer mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
SCM plugin and non-verbose mode
Is there any way to tell an SCM configuration to use 'quiet' or
'non-verbose' mode? I have a scenario where I need to use the checkin
goal to checkin files but if there are files that need to be added (e.g.
add_test.txt) the maven build stops with the following error:
[WARNING] Unknown checkin ouput: add_test.txt : No files matching
file_NOT_in_starteam.txt were found in the StarTeam repository.
Here's the configuration for checkin goal
execution
idcheckin-docbuild-destination/id
goals
goalcheckin/goal
/goals
phaseinstall/phase
configuration
connectionTypeconnection/connectionType
connectionUrl${dest.base.scm.url}/${webhelp.dir}/connectionUrl
workingDirectory${dest.checkout.directory}/workingDirectory
includes**/*/includes
messageNew DocServices Build Checkin/message
/configuration
/execution
If I add an execution of the 'add' goal before the 'checkin' goal I get
the following error:
[WARNING] Unknown add ouput: borlandhelp.css : No files matching
file_already_in_starteam.txt were found on the local disk that were
not already in the repository.
Here's the configuration for the add goal:
execution
idadd-docbuild-destination/id
goals
goaladd/goal
/goals
phaseinstall/phase
configuration
connectionTypeconnection/connectionType
connectionUrl${dest.base.scm.url}/${webhelp.dir}/connectionUrl
workingDirectory${dest.checkout.directory}/workingDirectory
includes**/*/includes
messageAdding Files From New DocServices Build/message
/configuration
/execution
The only way I've found to get around this is by invoking the same
starteam add and checkin commands that maven is invoking but add a '-q'
argument. This silently ignores the errors above. However, I can't
figure out how to configure 'quite' mode in Maven.
Eric
Maven Ant Tasks 2.0.7
Hi all, I ran into something strange while using the Maven Ant Tasks (2.0.7). My Ant build now includes a POM which refers to a parent POM. If I have the parent POM available in my local repository everything works fine. If not, then the build fails because it can't download the parent POM. (If I use Maven instead of Maven Ant Tasks then it works regardless.) My settings.xml contains the remote repository's location and my build.xml contains: ?xml version=1.0 encoding=UTF-8? project xmlns:artifact=urn:maven-artifact-ant default=build target name=build typedef resource=org/apache/maven/artifact/ant/antlib.xml uri=urn:maven-artifact-ant classpath pathelement location=lib/maven-ant-tasks-2.0.7.jar/ /classpath /typedef artifact:pom id=maven.project file=pom.xml/ artifact:dependencies verbose=true filesetId=maven-ant-tasks.dependency.fileset pom refid=maven.project/ artifact:remoteRepository id=remote url=http://maven.example.com/repository/ /artifact:dependencies /target /project Firstly, removing artifact:remoteRepository from build.xml fails the build. Apparently, settings.xml is ignored? Secondly, why doesn't it download the parent POM? It's in the same repository as the JARs and those *are* downloaded (provided I've installed the parent POM locally). Cheers, Hilco - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Community review of the next commons-logging pom
You can ping the people from Apache Felix, they create bundles of apache projects for consumption in OSGi with the goal of contributing it back to the projects. They will tell you if it's ready or not for the projects. On 8/27/07, Dennis Lundberg [EMAIL PROTECTED] wrote: Hi Tom I've heard the term OSGi from time to time, but have never took the time to learn more about it. Do you know of a good place where I can find out more about it? A quick look at Google suggests that it has something to do with entries in the manifest in the jar file, is that correct? What would they look like and what is the benefit for the community if we add them? Tom Huybrechts wrote: Is there any chance that OSGi headers could be added ? On 8/27/07, Dennis Lundberg [EMAIL PROTECTED] wrote: Hi all The poms for commons logging has taken some beating on this list over the years. The reason for that has been the dependencies section. Previous poms of commons-logging was created for Maven 1. These were then converted into Maven 2 poms with various degree of success. In particular the scope wasn't set properly. We are now preparing the next release of commons-logging (version 1.1.1) which will be built with Maven 2. That means that the pom that ends up in the Maven 2 repository will be the same one that we have created. To make sure that we have covered all bases this time we invite you, the community, to help us get it right. The current pom.xml is available for your viewing in our subversion repository: https://svn.apache.org/viewvc/commons/proper/logging/trunk/pom.xml?revision=568979view=markup Please post any comments you have on the pom to this list, and I will bring the over to the commons community. -- Dennis Lundberg Apache Commons committer and PMC member - 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] -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Manually Install Dependency to Archiva Managed Repository
I believe for jta, the zip file is the jar, so can just be deployed as is (with -Dpackaging=jar). As for the POM - the default created should be fine, or the one you get from the central repo is good too. - Brett On 29/08/07, Wendy Smoak [EMAIL PROTECTED] wrote: On 8/28/07, Cameron Jones [EMAIL PROTECTED] wrote: Run into a new problem now in that jta 1.1 is only a zip file and contains no pom... am i right in thinking i would have to write my own pom to get it in the repo? When you deploy the jar, by default Maven will generate a minimal pom (just artifactId, groupId, version, etc.) Is there a jar inside that zip file? Or should it be renamed as .jar? -- Wendy -- Brett Porter Blog: http://www.devzuz.org/blogs/bporter/
Re: SCM plugin and non-verbose mode
dont think there is a solution for case, please file a request against
maven scm.
Best if you directly enhance maven-scm's starteam provider to get you going,
and then submit a patch
-D
On 8/28/07, Eric Roberts [EMAIL PROTECTED] wrote:
Is there any way to tell an SCM configuration to use 'quiet' or
'non-verbose' mode? I have a scenario where I need to use the checkin
goal to checkin files but if there are files that need to be added (e.g.
add_test.txt) the maven build stops with the following error:
[WARNING] Unknown checkin ouput: add_test.txt : No files matching
file_NOT_in_starteam.txt were found in the StarTeam repository.
Here's the configuration for checkin goal
execution
idcheckin-docbuild-destination/id
goals
goalcheckin/goal
/goals
phaseinstall/phase
configuration
connectionTypeconnection/connectionType
connectionUrl${dest.base.scm.url}/${webhelp.dir}/connectionUrl
workingDirectory${dest.checkout.directory}/workingDirectory
includes**/*/includes
messageNew DocServices Build Checkin/message
/configuration
/execution
If I add an execution of the 'add' goal before the 'checkin' goal I get
the following error:
[WARNING] Unknown add ouput: borlandhelp.css : No files matching
file_already_in_starteam.txt were found on the local disk that were
not already in the repository.
Here's the configuration for the add goal:
execution
idadd-docbuild-destination/id
goals
goaladd/goal
/goals
phaseinstall/phase
configuration
connectionTypeconnection/connectionType
connectionUrl${dest.base.scm.url}/${webhelp.dir}/connectionUrl
workingDirectory${dest.checkout.directory}/workingDirectory
includes**/*/includes
messageAdding Files From New DocServices Build/message
/configuration
/execution
The only way I've found to get around this is by invoking the same
starteam add and checkin commands that maven is invoking but add a '-q'
argument. This silently ignores the errors above. However, I can't
figure out how to configure 'quite' mode in Maven.
Eric
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
