settings.xml file inheritance (for lack of a better word)
Hello, My group is working in an NFS mounted environment. I would like to have everyone running maven from a central location, with a centrally located settings.xml file in the conf directory, rather than everyone having their own settings.xml file in their $HOME/.m2 directories. That way, if a change is made to the settings.xml file, it will propogate to all people, rather than having to send out an email to each person telling them to modify their $HOME/.m2/settings.xml file with the change. My concern is that people may individually want to modify certain parts of the settings.xml file for their specific projects (add variables, etc.) that may not apply to other projects, or may have different values than for other projects. Now, my question: If an individual has a settings.xml file in their $HOME/.m2 ** AND ** in their $MAVEN_HOME/conf, does the .m2 version take precedence over the conf version? Does it inherit from the conf version? If so, what fields are inherited? Thanks in advance! Tom - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven Build Notification
Thank you alexandre, I'll take a look at that ... though I'd like to be decoupled from continuum if possible (not that I have anything against continuum :) ) Tom [EMAIL PROTECTED] 07/26/06 2:55 PM You could also use continuum manual build functionnalities. Just don't set any scheduled build if you don't need to. On 7/25/06, Thomas Van Buskirk [EMAIL PROTECTED] wrote: Thank you gscokart and ivolimmen ... I'll check JIRA for the issue. It would be nice to be able to determine the actual project that broke through Maven w/o CI (whereas if I use antrun or just have a script that executes on build failure, I would not have that ability). I'll keep searching ... Thanks again! Tom [EMAIL PROTECTED] 07/24/06 11:54 PM You can use the antrun plugin to send mail at a given phase of your build. But I don't think you can have this when your build fails. When the maven build fail, it stop. I don't think there is any listener. Did you search in jira to see if there is a feature request? If not, you should maybe introduce it. Gilles -- View this message in context: http://www.nabble.com/Maven-Build-Notification-tf1995888.html#a5480753 Sent from the Maven - Users forum at Nabble.com. - 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 Build Notification
Thank you gscokart and ivolimmen ... I'll check JIRA for the issue. It would be nice to be able to determine the actual project that broke through Maven w/o CI (whereas if I use antrun or just have a script that executes on build failure, I would not have that ability). I'll keep searching ... Thanks again! Tom [EMAIL PROTECTED] 07/24/06 11:54 PM You can use the antrun plugin to send mail at a given phase of your build. But I don't think you can have this when your build fails. When the maven build fail, it stop. I don't think there is any listener. Did you search in jira to see if there is a feature request? If not, you should maybe introduce it. Gilles -- View this message in context: http://www.nabble.com/Maven-Build-Notification-tf1995888.html#a5480753 Sent from the Maven - Users forum at Nabble.com. - 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]
Maven Build Notification
Hi everyone, I know this topic has been covered before, but I was wondering if there have been any updates. I'd like to send build failure notifications to an email address without using Continuum (or other CI tool). Is this possible? Thanks! Tom - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven site collapsable menus
You're not alone. I had the same problem and went through and hardcoded all of
the parent and child projects. Yuck! :( Anyone have a solution for this?
Tom
[EMAIL PROTECTED] 07/21/06 4:49 PM
I have been trying to create expandable/collapsable menus on my maven generated
site, but have been unable to do so. I have not used a navigation.xml file, as
recommended in the documentation at http://maven.apache.org/site.html, but have
just put the menu in my site.xml. I have tried the following, but with very
weird results - normally, when I click on the bottom link of the top collapsable
menu, the bottom menu disappears.
My site.xml looks something like:
?xml version=1.0 encoding=ISO-8859-1?
site
bannerLeft
nameStack/name
srchttp://blah/blah.gif/src
hrefhttp://blah.org//href
/bannerLeft
bannerRight
srchttp://blah/blah/blahblah.jpg/src
/bannerRight
body
menu name=Stack
item name=Projects Used href=/ collapse=true
item name=Maven href=maven.html collapse=true/
item name=JPA href=jpa.html collapse=true/
item name=Spring Framework href=spring.html collapse=true/
item name=JSF-RI href=jsf.html collapse=true/
item name=Facelets href=facelets.html collapse=true/
item name=Acegi Security href=acegi.html collapse=true/
/item
item name=Internal Resources href=/ collapse=true
item name=Template Library href=ui.html collapse=true/
item name=Downloads href=downloads.html collapse=true/
/item
/menu
${modules}
${reports}
/body
/site
In short, I have three main questions:
1.Is there a bug in the maven site collapse/expand stuff, or am I just doing
something wrong?
2.Do I have to specify a valid value in the surrounding item's href, or since I
want it only to expand or collapse, and not display a different page when I
click on say Projects Used, or Internal Resources, in my example, would my tag
item name=Projects Used href=/ be valid?
3.Do you have to specify an expand and collapse attribute, if you want it to do
both?
Thanks. I appreciate very much how sweet maven is. I don't think the time
savings we have gained by using maven is even calculable, it is so large, and
this automatic site generation is just the icing on the cake.
Matt W.
--
NOTICE: This email message is for the sole use of the
intended recipient(s) and may contain confidential and
privileged information. Any unauthorized review, use,
disclosure or distribution is prohibited. If you are not the
intended recipient, please contact the sender by reply email
and destroy all copies of the original message.
--
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: RE : Web site generation for multiple projects
Does anyone have a working parent pom and site.xml, and working child pom and site.xml that they're willing to share? This is mine, it does not work correctly. The modules display, but they are just strong (bold), no hyperlink. If I click on one of my reports, the module turns to a hyperlink, but the hyperlink points the index.html of the current POM. I have my parent pom set up like this: project modelVersion4.0.0/modelVersion groupIdcom.mycompany.blah/groupId artifactIdapps/artifactId version1.0/version packagingpom/packaging namemaster POM/name ... modules modulesubproject/module /modules ... reporting plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-project-info-reports-plugin/artifactId /plugin /plugins /reporting ... distributionManagement site idwebsite/id nameMy Maven Website/name urlfile:///home/myhome/site/url /site /distributionManagement /project My Parent site.xml file is as follows: project name=Maven bannerLeft nameMaven/name hrefhttp://maven.apache.org//href srchttp://maven.apache.org/images/apache-maven-project.png/src /bannerLeft bannerRight nameMaven Icon/name srchttp://maven.apache.org/images/maven-small.gif/src /bannerRight body links item name=Maven 2 href=http://maven.apache.org/maven2// /links menu name=Maven 2.0 item name=Introduction href=index.html/ item name=Download href=download.html/ /menu menu ref=modules / /body /project My Child POM is set up like this: project parent groupIdcom.mycompany.blah/groupId artifactIdapps/artifactId version1.0/version relativePath../pom.xml/relativePath /parent modelVersion4.0.0/modelVersion groupIdcom.mycompany.other/groupId artifactIdmy-subproject/artifactId packagingjar/packaging namesubproject/name ... reporting plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-project-info-reports-plugin/artifactId /plugin plugins /reporting ... /project My Child site.xml file is as follows: project name=Maven bannerLeft nameMaven/name hrefhttp://maven.apache.org//href srchttp://maven.apache.org/images/apache-maven-project.png/src /bannerLeft bannerRight nameMaven Icon/name srchttp://maven.apache.org/images/maven-small.gif/src /bannerRight body links item name=Maven 2 href=http://maven.apache.org/maven2// /links menu name=Maven 2.0 item name=Introduction href=index.html/ item name=Download href=download.html/ /menu menu ref=parent / menu ref=reports / /body /project Finally, the directory stucture is: +apps -pom.xml + src + site -site.xml +subproject -pom.xml + src + site -site.xml I then go to file:///home/myhome/site/index.html and it displays the master pom site. There is a Modules heading in the menu, and one item underneath it called subproject, but you cannot click it (it is just bolded). If I then click on Downloads the subproject item becomes selectable and turns blue, but it just takes you back to the master pom home page. Hope this can help some people (even though the inheritance doesn't work correctly). Tom [EMAIL PROTECTED] 07/13/06 10:52 AM In a different thread someone mentioned that the modules won't show up unless modules' POMs inherit from the agregator POM as opposed to inheriting from some top-level POM. However, it is not always possible (convenient) to inherit from the agregator POM. -- View this message in context: http://www.nabble.com/RE-%3A-Web-site-generation-for-multiple-projects-tf1933584.html#a5313355 Sent from the Maven - Users forum at Nabble.com. - 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 : Web site generation for multiple projects
I tried this and the modules didn't display. All I saw was the Modules menu with no modules displayed below them. I looked on JIRA and it seems there is a bug for it: http://jira.codehaus.org/browse/MSITE-86 It says that it's fixed in 2.0-beta-5 (i'm assuming that means 2.0.5) Does anyone have a workaround for version 2.0.4? Thanks! Tom [EMAIL PROTECTED] 07/12/06 10:16 AM Try from the top : mvn site. I mean by top Top (root directory) Pom.xml (root pom) module1 pom.xml module2 pom.xml Add in rootdirectory/src/site/site.xml Something like : menu ref=parent / (module will have link to the parent one) menu ref=reports / menu ref=modules / (top will have link to modules) -- Olivier -Message d'origine- De : HUGOT Franck [mailto:[EMAIL PROTECTED] Envoyé : mercredi 12 juillet 2006 19:09 À : Maven Users List Objet : RE: Web site generation for multiple projects Sorry, this is for m2. What do you mean by using directly the modules? I known how to generate a web site for one module but for multiple in only one web site? Thanks. -Message d'origine- De : Arnaud HERITIER [mailto:[EMAIL PROTECTED] Envoyé : mercredi 12 juillet 2006 19:06 À : Maven Users List Objet : Re: Web site generation for multiple projects m1 or m2 ? m1 - you have to use the multiproject plugin m2 - you use directly the modules Arnaud On 7/12/06, HUGOT Franck [EMAIL PROTECTED] wrote: Hello, Is there a way to generate only one web site for multiple projects? I can't find a way to do this, except generate a web site for each project and develop a specific home page that refer to each project home page. Thanks in advance. - 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]
Artifact Version Variable not Converted into Number in Absolute Path
Hello everyone,
(I appreciate your help in advance)
I'm not sure whether this is a bug, or my problem, but I'm having troubles with
one of my 3rd party jars (apache axis jaxrpc), as seen by the following error
message:
[DEBUG] axis:axis-jaxrpc:jar:1.1:provided (selected for provided)
[DEBUG] axis:axis-wsdl4j:jar:1.5.1:provided (selected for provided)
[DEBUG] Trying repository maven-proxy
Downloading:
http://localhost:/repository//axis/axis-jaxrpc/${axis-jaxrpc.version}/axis-jaxrpc-${axis-jaxrpc.version}.pom
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error building POM (may not be this project's POM).
Project ID: axis:axis-jaxrpc
Reason: Error getting POM for 'axis:axis-jaxrpc' from the repository: Error
transferring file
axis:axis-jaxrpc:pom:${axis-jaxrpc.version}
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
maven-proxy (http://localhost:/repository/)
...
The error message continues on, giving me a IOException 500 error later in the
stack trace.
My thought, however, is that there is a problem with the above line:
http://localhost:/repository//axis/axis-jaxrpc/${axis-jaxrpc.version}/axis-jaxrpc-${axis-jaxrpc.version}.pom
Notice that in the line just before it, maven seems to recognize the version
number (1.1)
In all of my past projects the ${blah.version} gets converted to the number
that I specify in my parent pom.xml. In this one, however, the ${blah.version}
seems to not get converted.
The problem seems similar to: http://jira.codehaus.org/browse/MNG-2049
but I don't think it's exactly the same.
Let me know if you need to see more. Essentially, my settings.xml file has:
axis-jaxrpc.version1.1/axis-jaxrpc.version
My pom.xml just points to that using:
dependency
groupIdaxis/groupId
artifactIdaxis-jaxrpc/artifactId
version${axis-jaxrpc.version}/version
scopeprovided/scope
/dependency
And as you can see, I'm running maven-proxy as my central mirror server.
Thanks for your help!!!
Tom
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Artifact Version Variable not Converted into Number in Absolute Path
If you see a semicolon after the $ sign before the { sign, it's because my mail
server put it in ... that is not the problem :) (I wish it were :) )
Thanks,
Tom
[EMAIL PROTECTED] 07/10/06 2:51 PM
Hello everyone,
(I appreciate your help in advance)
I'm not sure whether this is a bug, or my problem, but I'm having troubles with
one of my 3rd party jars (apache axis jaxrpc), as seen by the following error
message:
[DEBUG] axis:axis-jaxrpc:jar:1.1:provided (selected for provided)
[DEBUG] axis:axis-wsdl4j:jar:1.5.1:provided (selected for provided)
[DEBUG] Trying repository maven-proxy
Downloading:
http://localhost:/repository//axis/axis-jaxrpc/${axis-jaxrpc.version}/axis-jaxrpc-${axis-jaxrpc.version}.pom
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error building POM (may not be this project's POM).
Project ID: axis:axis-jaxrpc
Reason: Error getting POM for 'axis:axis-jaxrpc' from the repository: Error
transferring file
axis:axis-jaxrpc:pom:${axis-jaxrpc.version}
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
maven-proxy (http://localhost:/repository/)
...
The error message continues on, giving me a IOException 500 error later in the
stack trace.
My thought, however, is that there is a problem with the above line:
http://localhost:/repository//axis/axis-jaxrpc/${axis-jaxrpc.version}/axis-jaxrpc-${axis-jaxrpc.version}.pom
Notice that in the line just before it, maven seems to recognize the version
number (1.1)
In all of my past projects the ${blah.version} gets converted to the number
that I specify in my parent pom.xml. In this one, however, the ${blah.version}
seems to not get converted.
The problem seems similar to: http://jira.codehaus.org/browse/MNG-2049
but I don't think it's exactly the same.
Let me know if you need to see more. Essentially, my settings.xml file has:
axis-jaxrpc.version1.1/axis-jaxrpc.version
My pom.xml just points to that using:
dependency
groupIdaxis/groupId
artifactIdaxis-jaxrpc/artifactId
version${axis-jaxrpc.version}/version
scopeprovided/scope
/dependency
And as you can see, I'm running maven-proxy as my central mirror server.
Thanks for your help!!!
Tom
-
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]
