Change dynamically pom dependencies
hi
I have a project with several subprojects.
I agragate subproject's sources in order to get clover report.
I need to change dynamically pom dependencies of my main project to
compile and run aggragated sources.
goal name=myproject:aggregate-dependencies
j:set var=initialDependencies value=${pom.dependencies}/
maven:reactor
basedir=${basedir}
postProcessing=true
includes=project/*/project.xml
banner=aggregating dependencies
ignoreFailures=false/
j:forEach var=reactorProject items=${reactorProjects}
j:set var=aggregatedDependencies
value=${aggregatedDependencies}+${reactorProject.dependencies}/
/j:forEach
// here i try to set pom dependencies but it don't seems to work
j:set var=${pom.dependencies} value=${aggregatedDependencies}/
/goal
Do you think there is a way to change dynamically pom dependencies?
Thanks
This message and any attachments (the message) is
intended solely for the addressees and is confidential.
If you receive this message in error, please delete it and
immediately notify the sender. Any use not in accord with
its purpose, any dissemination or disclosure, either whole
or partial, is prohibited except formal approval. The internet
can not guarantee the integrity of this message.
BNP PARIBAS (and its subsidiaries) shall (will) not
therefore be liable for the message if modified.
-
Ce message et toutes les pieces jointes (ci-apres le
message) sont etablis a l'intention exclusive de ses
destinataires et sont confidentiels. Si vous recevez ce
message par erreur, merci de le detruire et d'en avertir
immediatement l'expediteur. Toute utilisation de ce
message non conforme a sa destination, toute diffusion
ou toute publication, totale ou partielle, est interdite, sauf
autorisation expresse. L'internet ne permettant pas
d'assurer l'integrite de ce message, BNP PARIBAS (et ses
filiales) decline(nt) toute responsabilite au titre de ce
message, dans l'hypothese ou il aurait ete modifie.
How can I use environment variables in project.properties?
Hi,
I would like to know how I can use environment variables in project.properties.
I know about system properties like ${user.home}, but I was wondering
if I can also use other enviroment variables.
Regards,
Ruud Wijnands
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: How can I use environment variables in project.properties?
On 24.08.2005, at 11:55, Ruud Wijnands wrote:
I would like to know how I can use environment variables in
project.properties.
I know about system properties like ${user.home}, but I was wondering
if I can also use other enviroment variables.
AFAIK: You can't.
Cheers,
-Ralph.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Merging dependencies from an external file
Hallo *, I am using maven for builing a web application. This application depends on an api that is devoloped in an other country. Onces a week i get a new release of this api as a zip file. The zip file includes: 1- file: dependencies.xml dependencies dependency groupIdisorelax/groupId artifactIdisorelax/artifactId version20020707/version /dependency ...other dependencies /dependencies 2- directory that contains all new artifacts When i integerate the new api into my web aplication i: 1- copy the content of the directory into my internal repository 2- add propertieswar.bundletrue/war.bundle/properties to each dependency in dependencies.xml. 3- copy all dependencies from dependencies.xml into project.xml. 4- maven war This steps have to be done for other projects that depend on the new api. Do you have any idea how to automate this process? Regards, Ehab Die Direct Line Versicherung AG gehoert zur internationalen The Royal Bank of Scotland Group. Sitz der Direct Line Versicherung AG ist Rheinstrasse 7a, 14513 Teltow; eingetragen beim Amtsgericht Potsdam unter der Registernummer HRB 9828. Die zustaendige Aufsichtsbehoerde ist die Bundesanstalt fuer Finanzdienstleistungsaufsicht, Bonn. Diese E-Mail ist nur fuer den Empfaenger bestimmt und kann vertrauliche, urheberrechtlich und gesetzlich geschuetzte Informationen enthalten. Falls diese E-Mail nicht fuer Sie bestimmt ist, sollten Sie uns unverzueglich informieren und diese E-Mail loeschen. Das Kopieren, Ausdrucken, Verteilen, ganz oder teilweise Veroeffentlichen dieser E-Mail ist untersagt. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multiproject build
Hi, i am in the same configuration, but even if i have all my projects depending on my utility project, it is not built in the first place ? So when i do a multiproject:install, my utility project is not on the top list and the build fails Using maven 1.0.2 and multiproject 1.4.1. Thanks Per Abich a écrit : Just put a dependency in your project.xml so that all project depend on your utility project. That should do the trick. Currently, there is no other way of orderig the build process. Per 2005/8/3, [EMAIL PROTECTED] [EMAIL PROTECTED]: Hi, I have a Maven multiproject set up. One of my project is a utility kind of project which is used by my other modules/projects. During the build, can i set up a order in which the projects will be built (or) can i set dependency between my projects so that my utility project will get built first ? newbie gurubaran. * This message and any attachments (the message) are confidential and intended solely for the addressee(s). Any unauthorised use or dissemination is prohibited.E-mails are susceptible to alteration. Neither SOCIETE GENERALE nor any of its subsidiaries or affiliates shall be liable for the message if altered, changed or falsified. * - 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: How can I use environment variables in project.properties?
don't know if it works but you can try something like :
preGoal name=build:start
ant:property environment=env/
/preGoal
Arnaud
On 8/24/05, Ralph Pöllath [EMAIL PROTECTED] wrote:
On 24.08.2005, at 11:55, Ruud Wijnands wrote:
I would like to know how I can use environment variables in
project.properties.
I know about system properties like ${user.home}, but I was wondering
if I can also use other enviroment variables.
AFAIK: You can't.
Cheers,
-Ralph.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
How can I exclude multiple project.xml files via project.properties to assure not building a null-1.0.jar file?
Hi,
I am trying to exclude particular project files via project.properties.
The reason I want this is that maven otherwise builds a null-1.0.jar
file for those directories that have a project.xml file for a
maven:multiproject project and that do not contain any source code or
tests.
I use the following:
maven.multiproject.excludes=project.xml,${basedir}/import/project.xml
For some reason the second one is always ignore resulting a
null-1.0.jar file for that directory.
What am I doing wrong?
Regards,
Ruud Wijnands
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[m1] bootstrap build error
I have been attempting to build m1 via bootstrap again, and have the following compile errors. I did not find the cause from a quick review, and am wondering if this is a known bootstrap problem before I spend more time with it. I have verified the classes exist, visual inspection found no problems. I am wondering about bootstrap classpath, etc.? From revision 239628. [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\org\apache\mav en\ejb\EJBArtifactTypeHandler.java:20: cannot find symbol [exec] [javac] symbol : class MavenException [exec] [javac] location: package org.apache.maven [exec] [javac] import org.apache.maven.MavenException; [exec] [javac] ^ [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\org\apache\mav en\ejb\EJBArtifactTypeHandler.java:21: cannot find symbol [exec] [javac] symbol : class Project [exec] [javac] location: package org.apache.maven.project [exec] [javac] import org.apache.maven.project.Project; [exec] [javac] ^ [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\org\apache\mav en\ejb\EJBArtifactTypeHandler.java:22: package org.apache.maven.repository does not exist [exec] [javac] import org.apache.maven.repository.ArtifactTypeHandler; [exec] [javac]^ [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\org\apache\mav en\ejb\EJBArtifactTypeHandler.java:31: cannot find symbol [exec] [javac] symbol: class ArtifactTypeHandler [exec] [javac] public class EJBArtifactTypeHandler implements ArtifactTypeHandler [exec] [javac]^ [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\org\apache\mav en\ejb\EJBArtifactTypeHandler.java:40: cannot find symbol [exec] [javac] symbol : class Project [exec] [javac] location: class org.apache.maven.ejb.EJBArtifactTypeHandler [exec] [javac] public String constructRepositoryDirectoryPath(String type, Project project) throws MavenException [exec] [javac] ^ [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\org\apache\mav en\ejb\EJBArtifactTypeHandler.java:40: cannot find symbol [exec] [javac] symbol : class MavenException [exec] [javac] location: class org.apache.maven.ejb.EJBArtifactTypeHandler [exec] [javac] public String constructRepositoryDirectoryPath(String type, Project project) throws MavenException [exec] [javac] ^ [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\org\apache\mav en\ejb\EJBArtifactTypeHandler.java:56: cannot find symbol [exec] [javac] symbol : class Project [exec] [javac] location: class org.apache.maven.ejb.EJBArtifactTypeHandler [exec] [javac] public String constructRepositoryFullPath(String type, Project project, String version) throws MavenException [exec] [javac] ^ [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\org\apache\mav en\ejb\EJBArtifactTypeHandler.java:56: cannot find symbol [exec] [javac] symbol : class MavenException [exec] [javac] location: class org.apache.maven.ejb.EJBArtifactTypeHandler [exec] [javac] public String constructRepositoryFullPath(String type, Project project, String version) throws MavenException [exec] [javac] ^ [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\org\apache\mav en\ejb\EJBArtifactTypeHandler.java:58: internal error; cannot instantiate StringBuffer(int) at java.lang.StringBuffer to () [exec] [javac] StringBuffer path = new StringBuffer(constructRepositoryDirectoryPath(type, project)); [exec] [javac] ^ [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\org\apache\mav en\ejb\EJBArtifactTypeHandler.java:70: cannot find symbol [exec] [javac] symbol : class MavenException [exec] [javac] location: class org.apache.maven.ejb.EJBArtifactTypeHandler [exec] [javac] throw new MavenException(Unrecognised ejb type (is + type + )); [exec] [javac] ^ [exec] [javac] 10 errors - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M2] outdated xsd?
I am using maven 2.0 alpha-3. Is there any beta release yet?? In my pom I have: 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; Is this the right one?? Erick. Edwin Punzalan wrote: What version of m2 are you using? For beta, reports is deprecated and reporting replaced it. Erick Dovale wrote: Hi there, I just noticed that when adding reports to my pom.xml file my validator does not recognize the reporting tag; it recognizes the reports though but, when using the reports tag m2 spits out a message saying that it is deprecated and suggest to use reporting. Is this a known bug?? I search for it in Jira and did not find anything like it. cheers, Erick. - 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[2]: Middlgen (Plugin)
Hello Jan, We see you. Wednesday, August 24, 2005, 6:17:06 PM, you wrote: Hello again, and sorry to annoy you. as this had been my first post to the list, and none answered so far, I wondered if anybody except me got this question at all. maybe someone could just post a nifty reply so I know that at least I#ve been heard? Thanx Jan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Best regards, Dmitrymailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] javadocs??
I suppose the javadocs for maven2 are somewhere on the site -- but I cannot locate them. The old, familiar Project Reports is missing. And I've trolled thru most pages looking. I also tried to run m2 site:site on my local SVN checkout (it died). So I'm at a loss... Are there any javadocs available for m2?? Thanks, -- Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
jar:install-snapshot - deprecated jar:snapshot
Hi:
With the jar plug-in 1.7 I noticed that the creation of a versioned jar
file seems to be deprecated.
I was used to get a versioned snapshot file with the
jar:install-snapshot goal which seems not to be the case anymore. From
what I understand, I still can create a versioned snapshot file with
jar:snapshot which on the other hand is deprecated:
http://maven.apache.org/reference/plugins/jar/goals.html
jar:snapshot DEPRECATED. Please use jar:deploy-snapshot or
jar:install-snapshot
Creates a jar file in the Maven build directory with the form
${project.id}-MMDD.hhmmss.jar where
* id - taken from the project.xml of the project being built
* MMDD - The current year in 8 digit format
* hhmmss - the current time in 6 digit format
My question is: Will the versioned jar file disappear in the near
future? What other ways will maven provide to get a versioned snapshot
file or do I have to simulate that in the future with a goal in
maven.xml?
Thanks in advance,
Andreas
This electronic mail message contains information belonging to PaymentOne,
which may be confidential and/or legal privileged. The information is intended
only for the use of the individual or entity named above. If you are not the
intended recipient, you are hereby notified that any disclosure, printing,
copying, distribution, or the taking of any action in reliance on the contents
of this electronically mailed information is strictly prohibited. If you
receive this message in error, please immediately notify us by electronic mail
and delete this message.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Resent: [m1.1] JCoverage fails multiproject:site. Some help required.
All, Ok, it seems to work for maven site but it doesn't seem to work for maven multiproject:site. Is it supposed to? If the answer is yes, this might be a bug, if the answer is no I hope somebody can tell me how to solve this. BUILD FAILED File.. D:\Documents and Settings\Erwin\.maven\cache\maven-multiproject-plugin-1.4.1\plugin.jelly Element... maven:reactor Line.. 104 Column 9 Unable to obtain goal [site] -- D:\Documents and Settings\Erwin\.maven\cache\maven-test-plugin-1.6.2\plugin.jelly:181:54: fail There were test failures. Total time : 2 minutes 36 seconds Finished at : Wednesday, August 24, 2005 10:24:04 AM EDT Thanks, Erwin -Original Message- From: Carlos Sanchez [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 23, 2005 3:33 PM To: Maven Users List Subject: Re: Resent: [m1.1] JCoverage fails multiproject:site. Some help required. setting maven.test.failure.ignore to true *should* be the answer On 8/23/05, Hogeweg, Erwin (GE Infrastructure) [EMAIL PROTECTED] wrote: All, I am still struggling with the issue below. Please let me know if anyone has an answer for me. Your help is highly appreciated. Thanks, Erwin All, How do I prevent that a failing JCoverage JUnit test fails the multiproject:site goal? Obviously fixing the test/code is one answer, but I am looking for the other one ;-) I have already tried to set the property maven.test.failure.ignore to true, but that didn't seem to help. Thanks, Erwin - 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 and Versionless Jar Files
jarbar.jar/jar works for me on 1.0. Bill Worked like a charm. Thanks! -- Regards, Alex - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jar:install-snapshot - deprecated jar:snapshot
As of the 1.5 release of the Maven Artifact plugin, anything with a
SNAPSHOT name will automatically get timestamped.
- Brett
On 8/25/05, Andreas Guther [EMAIL PROTECTED] wrote:
Hi:
With the jar plug-in 1.7 I noticed that the creation of a versioned jar
file seems to be deprecated.
I was used to get a versioned snapshot file with the
jar:install-snapshot goal which seems not to be the case anymore. From
what I understand, I still can create a versioned snapshot file with
jar:snapshot which on the other hand is deprecated:
http://maven.apache.org/reference/plugins/jar/goals.html
jar:snapshot DEPRECATED. Please use jar:deploy-snapshot or
jar:install-snapshot
Creates a jar file in the Maven build directory with the form
${project.id}-MMDD.hhmmss.jar where
* id - taken from the project.xml of the project being built
* MMDD - The current year in 8 digit format
* hhmmss - the current time in 6 digit format
My question is: Will the versioned jar file disappear in the near
future? What other ways will maven provide to get a versioned snapshot
file or do I have to simulate that in the future with a goal in
maven.xml?
Thanks in advance,
Andreas
This electronic mail message contains information belonging to PaymentOne,
which may be confidential and/or legal privileged. The information is
intended only for the use of the individual or entity named above. If you are
not the intended recipient, you are hereby notified that any disclosure,
printing, copying, distribution, or the taking of any action in reliance on
the contents of this electronically mailed information is strictly
prohibited. If you receive this message in error, please immediately notify
us by electronic mail and delete this message.
-
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]
[m2] plugin.getDependencyPath
Hi,
In the bad old days of Jelly, we could type something like::
plugin.getDependendcyPath( 'axis:ant' );
And you got back the full path to a JAR -- so we could use it as::
ant:path id=axis.classpath
ant:pathelement path=${plugin.getDependencyPath('axis:axis')}/
Is there an equivalent helper function like this for Java??
BTW: FWIW: I have no interest in using Marmalade. I want to use *only*
Java + Ant when developing my plugins. In fact, I plan to do as much
as possible with Ant and simply fire it from the Maven plugin
structure. There is no reason to reinvent the wheel. Ant provides
Tasks to do probably 95% of what I need done. Is well understood, well
supported, and well documented. I see this sort of marraige between
Maven and Ant as powerful combination.
Thanks,
-- Chris
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[M2]: Missing maven-ear-plugin?
Maven version: 2.0-alpha-3 (Just started using Maven a few days ago) I am trying to create an ear file from wars and jars... I noticed that the maven-ear-plugin is missing from: http://www.ibiblio.org/maven2/plugins/org/apache/maven/plugins/ even though this plugin is still listed in the plugins.xml file listed here: http://www.ibiblio.org/maven2/plugins/org/apache/maven/plugins/plugins.xml Does anyone know why this plugin is missing? Command that I used to attempt to generate the ear file is below... C:\tmpm2 ear:ear -e + Error stacktraces are turned on. [INFO] [INFO] Building com.wachovia.comm.doctrack:doctrackproj:pom:1.0-SNAPSHOT [INFO] [INFO] maven-ear-plugin: checking for updates from central-plugins [INFO] Retrieving release information for maven-ear-plugin FATAL ERROR: Error executing Maven for a project Error stacktrace: org.apache.maven.reactor.ReactorException: Error executing project within the reactor at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:190) at org.apache.maven.cli.MavenCli.main(MavenCli.java:269) 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:324) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:303) at org.codehaus.classworlds.Launcher.launch(Launcher.java:243) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:416) at org.codehaus.classworlds.Launcher.main(Launcher.java:363) Caused by: org.apache.maven.lifecycle.LifecycleExecutionException: Error resolving plugin version at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:537) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:149) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:133) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:103) at org.apache.maven.DefaultMaven.processProject(DefaultMaven.java:261) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:180) ... 9 more Caused by: org.apache.maven.plugin.version.PluginVersionResolutionException: Error resolving version for 'org.apache.maven.plugins:maven-ear-plugin': Cannot resolve RELEASE version of this plugin. at org.apache.maven.plugin.version.DefaultPluginVersionManager.resolveReleaseVersion(DefaultPluginVersionManager.java:570) at org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.java:130) at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:192) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:528) ... 14 more Caused by: org.apache.maven.artifact.resolver.ArtifactResolutionException: Unable to find release for artifact org.apache.maven.plugins:maven-ear-plugin:maven-plugin:RELEASE org.apache.maven.plugins:maven-ear-plugin:RELEASE:maven-plugin from the specified remote repositories: http://repo1.maven.org/maven2/plugins at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:88) at org.apache.maven.plugin.version.DefaultPluginVersionManager.resolveReleaseVersion(DefaultPluginVersionManager.java:566) ... 17 more Caused by: org.apache.maven.artifact.metadata.ArtifactMetadataRetrievalException: Unable to find release for artifact org.apache.maven.plugins:maven-ear-plugin:maven-plugin:RELEASE at org.apache.maven.artifact.transform.ReleaseArtifactTransformation.retrieveFromRemoteRepository(ReleaseArtifactTransformation.java:86) at org.apache.maven.artifact.transform.AbstractVersionTransformation.resolveVersion(AbstractVersionTransformation.java:104) at org.apache.maven.artifact.transform.ReleaseArtifactTransformation.transformForResolve(ReleaseArtifactTransformation.java:51) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:84) ... 18 more Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: Unable to locate resource in repository at org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:81) at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:70) at
RE : installing maven on linux
Karl, Check that your MAVEN_HOME AND your PATH point to your maven 1.1 location. I had the same problem when I've switch form 1.0 to 1.1, my PATH wasn't correctly set. Pascal -Message d'origine- De : Karl Gustav [mailto:[EMAIL PROTECTED] Envoyé : August 24, 2005 11:00 À : users@maven.apache.org Objet : installing maven on linux Hello, Today i tried to use maven(v. 1.1-beta-1) on our linux machine. On windows i had no problems,but on linux i cant get it working. I found out it has nothing: - to do with the java project - to do with the java version, tried some versions between 1.4.0.2 - 1.5.4 I deleted cache and repository sometimes, but no change. JAVA_HOME is set correctly: echo $JAVA_HOME /usr/java/jdk1.5.0_04 but everytime i do a maven site or something else, i get: __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.1-beta-1 Plugin cache will be regenerated javax.xml.parsers.FactoryConfigurationError: Provider org.apache.xerces.jaxp.SAXParserFactoryImpl could not be instantiated: java.lang.NullPointerException at javax.xml.parsers.SAXParserFactory.newInstance(SAXParserFactory.java:113) at org.apache.maven.plugin.JellyScriptHousing.parse(JellyScriptHousing.java:152 ) at org.apache.maven.plugin.JellyScriptHousing.parse(JellyScriptHousing.java:177 ) at org.apache.maven.plugin.PluginManager.loadUncachedPlugins(PluginManager.java :238) at org.apache.maven.plugin.PluginManager.initialize(PluginManager.java:303) at org.apache.maven.MavenSession.initializePluginManager(MavenSession.java:204) at org.apache.maven.MavenSession.initialize(MavenSession.java:171) at org.apache.maven.cli.App.doMain(App.java:498) at org.apache.maven.cli.App.main(App.java:1258) 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 com.werken.forehead.Forehead.run(Forehead.java:551) at com.werken.forehead.Forehead.main(Forehead.java:581) Any ideas? Karl ___ Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de - 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]
log4j logging in JUnit tests
hi, I'm trying to use log4j logging in my JUnit tests instead of some System.out.println statements I have there... So i did the following: 1) add the following to my test class: private static final Logger logger = Logger.getLogger(StmdsocTest.class); 2) Put this log4j.properties file in the top maven dir: log4j.appender.appenderName=be.ac.ua.fots.stmdsoc.test.StmdsocTest log4j.appender.be.ac.ua.fots.stmdsoc.test.StmdsocTest=org.apache.log4j. ConsoleAppender log4j.category.be.ac.ua.fots.stmdsoc.test.StmdsocTest=INFO However, when the tests commence, I always get this warning: log4j:WARN No appenders could be found for logger (be.ac.ua.fots.stmdsoc.test.StmdsocTest). log4j:WARN Please initialize the log4j system properly. This probably means my log4j.properties file is not found? I also tried putting the file in src/ and adding it as a resource in project.xml, both as a normal resource and a unittest resource, but to no avail... Does anyone have any idea as to how this can be solved? Thanks, Hans pgpVZ5Krj20ko.pgp Description: PGP signature
RE: jar:install-snapshot - deprecated jar:snapshot
Is there a best practices way of cleaning up these timestamped
deployments? We have a continuous integration tool doing the builds (so
there's lots of builds) and the current version of all projects are set
with SNAPSHOT. So it seems that in a not-too-large amount of time our
Maven repository will be filled up with these timestamped snapshot
artifacts.
..David..
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 24, 2005 8:57 AM
To: Maven Users List
Subject: Re: jar:install-snapshot - deprecated jar:snapshot
As of the 1.5 release of the Maven Artifact plugin, anything with a
SNAPSHOT name will automatically get timestamped.
- Brett
On 8/25/05, Andreas Guther [EMAIL PROTECTED] wrote:
Hi:
With the jar plug-in 1.7 I noticed that the creation of a versioned
jar file seems to be deprecated.
I was used to get a versioned snapshot file with the
jar:install-snapshot goal which seems not to be the case anymore.
From what I understand, I still can create a versioned snapshot file
with jar:snapshot which on the other hand is deprecated:
http://maven.apache.org/reference/plugins/jar/goals.html
jar:snapshot DEPRECATED. Please use jar:deploy-snapshot or
jar:install-snapshot
Creates a jar file in the Maven build directory with the form
${project.id}-MMDD.hhmmss.jar where
* id - taken from the project.xml of the project being built
* MMDD - The current year in 8 digit format
* hhmmss - the current time in 6 digit format
My question is: Will the versioned jar file disappear in the near
future? What other ways will maven provide to get a versioned
snapshot file or do I have to simulate that in the future with a goal
in maven.xml?
Thanks in advance,
Andreas
This electronic mail message contains information belonging to
PaymentOne, which may be confidential and/or legal privileged. The
information is intended only for the use of the individual or entity
named above. If you are not the intended recipient, you are hereby
notified that any disclosure, printing, copying, distribution, or the
taking of any action in reliance on the contents of this electronically
mailed information is strictly prohibited. If you receive this message
in error, please immediately notify us by electronic mail and delete
this message.
-
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]
Introducing Maven to developers
Hi all, I'm trying to introduce Maven at the client I'm working at, unfortunately I'm meeting some resistance. They currently work with a number of ant scripts which pulls data in from all over the place, I want to change that but some find it hard to see the added value of Maven. The main arguments are: 1. By splitting the project up into a number of small sub-projects it's going to make it more difficult for the developers to work on the code. Currently everything is in one CVS project which can easily be checked out using Eclipse. How do others deal with this? By working with different sub-projects in IDE or checking out all into one self-made project (within IDE)? 2. There are a few moans about tranferring builds to different environments whereby other ip-addresses/logins are needed for databases etc. Is it possible to configure property files for these environments and have goals to build for each environment? Other ideas , solutions?? THX Colin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jar:install-snapshot - deprecated jar:snapshot
On 8/24/05, David Jackman [EMAIL PROTECTED] wrote:
Is there a best practices way of cleaning up these timestamped
deployments? We have a continuous integration tool doing the builds (so
there's lots of builds) and the current version of all projects are set
with SNAPSHOT. So it seems that in a not-too-large amount of time our
Maven repository will be filled up with these timestamped snapshot
artifacts.
..David..
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 24, 2005 8:57 AM
To: Maven Users List
Subject: Re: jar:install-snapshot - deprecated jar:snapshot
As of the 1.5 release of the Maven Artifact plugin, anything with a
SNAPSHOT name will automatically get timestamped.
- Brett
On 8/25/05, Andreas Guther [EMAIL PROTECTED] wrote:
Hi:
With the jar plug-in 1.7 I noticed that the creation of a versioned
jar file seems to be deprecated.
I was used to get a versioned snapshot file with the
jar:install-snapshot goal which seems not to be the case anymore.
From what I understand, I still can create a versioned snapshot file
with jar:snapshot which on the other hand is deprecated:
http://maven.apache.org/reference/plugins/jar/goals.html
jar:snapshot DEPRECATED. Please use jar:deploy-snapshot or
jar:install-snapshot
Creates a jar file in the Maven build directory with the form
${project.id}-MMDD.hhmmss.jar where
* id - taken from the project.xml of the project being built
* MMDD - The current year in 8 digit format
* hhmmss - the current time in 6 digit format
My question is: Will the versioned jar file disappear in the near
future? What other ways will maven provide to get a versioned
snapshot file or do I have to simulate that in the future with a goal
in maven.xml?
Thanks in advance,
Andreas
This electronic mail message contains information belonging to
PaymentOne, which may be confidential and/or legal privileged. The
information is intended only for the use of the individual or entity
named above. If you are not the intended recipient, you are hereby
notified that any disclosure, printing, copying, distribution, or the
taking of any action in reliance on the contents of this electronically
mailed information is strictly prohibited. If you receive this message
in error, please immediately notify us by electronic mail and delete
this message.
-
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]
Yeah. What was wrong with the old way of having the JAR named
blah-SNAPSHOT.jar???
--
Jamie Bisotti
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] plugin.getDependencyPath
On Wed, 24 Aug 2005, Chris Berry wrote:
Hi,
In m2 you just specify that jar as a dependency in the pom of the plugin.
It's then automatically added to the runtime classpath of that plugin's
execution environment. Further, you can access the Plugin object and
it's properties in a Mojo.
Btw, if you plan to use ant in your plugins, have a look at the
maven-antrun-plugin. If you plan to use it, you should make your plugin
depend upon it, and extend AbstractAntTask. You can then create tasks,
add them to a Target object, and execute them (using a parent method).
(the plugin is part of the m2 svn repository).
-- Kenney
Hi,
In the bad old days of Jelly, we could type something like::
plugin.getDependendcyPath( 'axis:ant' );
And you got back the full path to a JAR -- so we could use it as::
ant:path id=axis.classpath
ant:pathelement path=${plugin.getDependencyPath('axis:axis')}/
Is there an equivalent helper function like this for Java??
BTW: FWIW: I have no interest in using Marmalade. I want to use *only*
Java + Ant when developing my plugins. In fact, I plan to do as much
as possible with Ant and simply fire it from the Maven plugin
structure. There is no reason to reinvent the wheel. Ant provides
Tasks to do probably 95% of what I need done. Is well understood, well
supported, and well documented. I see this sort of marraige between
Maven and Ant as powerful combination.
Thanks,
-- Chris
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Kenney Westerhof
http://www.neonics.com
GPG public key: http://www.gods.nl/~forge/kenneyw.key
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M2]: Missing maven-ear-plugin?
On Wed, 24 Aug 2005 [EMAIL PROTECTED] wrote: The ear plugin is not officially released yet. It will be part of beta-1. The fact that there are RELEASE files present on ibiblio is (AFAIK) by mistake. -- Kenney PS: If you're in a hacking mood, you could upgrade your m2 installation by boostrapping the subversion trunk version, or get the ear plugin from there and try to m2 install it (after downgrading some versions in the pom to alpha-3). Not sure it'll work though, m2 has changed a bit since alpha-3. Maven version: 2.0-alpha-3 (Just started using Maven a few days ago) I am trying to create an ear file from wars and jars... I noticed that the maven-ear-plugin is missing from: http://www.ibiblio.org/maven2/plugins/org/apache/maven/plugins/ even though this plugin is still listed in the plugins.xml file listed here: http://www.ibiblio.org/maven2/plugins/org/apache/maven/plugins/plugins.xml Does anyone know why this plugin is missing? Command that I used to attempt to generate the ear file is below... C:\tmpm2 ear:ear -e + Error stacktraces are turned on. [INFO] [INFO] Building com.wachovia.comm.doctrack:doctrackproj:pom:1.0-SNAPSHOT [INFO] [INFO] maven-ear-plugin: checking for updates from central-plugins [INFO] Retrieving release information for maven-ear-plugin FATAL ERROR: Error executing Maven for a project Error stacktrace: org.apache.maven.reactor.ReactorException: Error executing project within the reactor at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:190) at org.apache.maven.cli.MavenCli.main(MavenCli.java:269) 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:324) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:303) at org.codehaus.classworlds.Launcher.launch(Launcher.java:243) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:416) at org.codehaus.classworlds.Launcher.main(Launcher.java:363) Caused by: org.apache.maven.lifecycle.LifecycleExecutionException: Error resolving plugin version at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:537) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:149) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:133) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:103) at org.apache.maven.DefaultMaven.processProject(DefaultMaven.java:261) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:180) ... 9 more Caused by: org.apache.maven.plugin.version.PluginVersionResolutionException: Error resolving version for 'org.apache.maven.plugins:maven-ear-plugin': Cannot resolve RELEASE version of this plugin. at org.apache.maven.plugin.version.DefaultPluginVersionManager.resolveReleaseVersion(DefaultPluginVersionManager.java:570) at org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.java:130) at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:192) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:528) ... 14 more Caused by: org.apache.maven.artifact.resolver.ArtifactResolutionException: Unable to find release for artifact org.apache.maven.plugins:maven-ear-plugin:maven-plugin:RELEASE org.apache.maven.plugins:maven-ear-plugin:RELEASE:maven-plugin from the specified remote repositories: http://repo1.maven.org/maven2/plugins at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:88) at org.apache.maven.plugin.version.DefaultPluginVersionManager.resolveReleaseVersion(DefaultPluginVersionManager.java:566) ... 17 more Caused by: org.apache.maven.artifact.metadata.ArtifactMetadataRetrievalException: Unable to find release for artifact org.apache.maven.plugins:maven-ear-plugin:maven-plugin:RELEASE at org.apache.maven.artifact.transform.ReleaseArtifactTransformation.retrieveFromRemoteRepository(ReleaseArtifactTransformation.java:86) at org.apache.maven.artifact.transform.AbstractVersionTransformation.resolveVersion(AbstractVersionTransformation.java:104) at
RE: Introducing Maven to developers
We have done both of these with maven 1. 1. We use IDEA and import each sub-project as a module into one big IDEA project. We use the idea maven plugin to generate the module config files. This way the developers only have to import the modules they are interested in seeing. It's more flexible and it avoids maintaining a common IDE project file. 2. We have our configuration in an ldap server, organized by environment, then by sub-project. Most of the system can be configured via a single build parameter (the target environment). For the rest we use velocity to generate the config files. You can avoid a lot of the scripting we did by using build.properties files, but we didn't want to maintain a lot of properties outside of our scm. This required quite a bit of jelly scripting, but you may have a simpler build then ours, so it may not be too bad. We also had to write some java code as well. For example, we wrote our own DataSource factory to grab the connection information from ldap instead of config files. Does anyone else out there have better (or just different) solutions? -Original Message- From: Colin Chalmers [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 24, 2005 11:18 AM To: Maven Users List Subject: Introducing Maven to developers Hi all, I'm trying to introduce Maven at the client I'm working at, unfortunately I'm meeting some resistance. They currently work with a number of ant scripts which pulls data in from all over the place, I want to change that but some find it hard to see the added value of Maven. The main arguments are: 1. By splitting the project up into a number of small sub-projects it's going to make it more difficult for the developers to work on the code. Currently everything is in one CVS project which can easily be checked out using Eclipse. How do others deal with this? By working with different sub-projects in IDE or checking out all into one self-made project (within IDE)? 2. There are a few moans about tranferring builds to different environments whereby other ip-addresses/logins are needed for databases etc. Is it possible to configure property files for these environments and have goals to build for each environment? Other ideas , solutions?? THX Colin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- The information contained in this transmission is intended only for the personal and confidential use of the designated recipients named herein. If the reader of this transmission is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this transmission in error, and that any review, dissemination, distribution, or copying of this transmission is strictly prohibited. If you have received this communication in error, please notify the sender and return and delete the original transmission immediately. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] plugin.getDependencyPath
Hi Kenney,
I am using your plugin. Thanks. In fact, I've already extended it to
allow it to set Ant's message level (so you can see Ant's echo when
you need to).
I believe that Ant + Maven is the sweet spot. What I'm trying to
discern is the cleanest way to accomplish this.
Say you want to use an extended Ant -- pulling in, say, the Axis Ant
Tasks, or the ant-contrib Tasks, or whatever. I'm thinking that I will
simply extend AbstractAntMojo with, say, AxisAntMojo. This will have
the proper dependencies (axis:ant, etc) and when I call ant
inheritAll=true inheritRefs=true antfile= -- then I should be
able to find these Tasks on the inherited Classpath (right??)
I'm hoping that I will be able to ask the Plugin for it's resources --
so that I can find the Ant buildfile easily. I'm still figuring it
out...
Thanks again,
-- Chris
On 8/24/05, Kenney Westerhof [EMAIL PROTECTED] wrote:
On Wed, 24 Aug 2005, Chris Berry wrote:
Hi,
In m2 you just specify that jar as a dependency in the pom of the plugin.
It's then automatically added to the runtime classpath of that plugin's
execution environment. Further, you can access the Plugin object and
it's properties in a Mojo.
Btw, if you plan to use ant in your plugins, have a look at the
maven-antrun-plugin. If you plan to use it, you should make your plugin
depend upon it, and extend AbstractAntTask. You can then create tasks,
add them to a Target object, and execute them (using a parent method).
(the plugin is part of the m2 svn repository).
-- Kenney
Hi,
In the bad old days of Jelly, we could type something like::
plugin.getDependendcyPath( 'axis:ant' );
And you got back the full path to a JAR -- so we could use it as::
ant:path id=axis.classpath
ant:pathelement path=${plugin.getDependencyPath('axis:axis')}/
Is there an equivalent helper function like this for Java??
BTW: FWIW: I have no interest in using Marmalade. I want to use *only*
Java + Ant when developing my plugins. In fact, I plan to do as much
as possible with Ant and simply fire it from the Maven plugin
structure. There is no reason to reinvent the wheel. Ant provides
Tasks to do probably 95% of what I need done. Is well understood, well
supported, and well documented. I see this sort of marraige between
Maven and Ant as powerful combination.
Thanks,
-- Chris
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Kenney Westerhof
http://www.neonics.com
GPG public key: http://www.gods.nl/~forge/kenneyw.key
-
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: Resent: [m1.1] JCoverage fails multiproject:site. Some help required.
Yes, it sounds like a bug. You should try the cobertura plugin instead (http://maven-plugins.sourceforge.net/maven-cobertura-plugin/), which is the next version of jCoverage. On 8/24/05, Hogeweg, Erwin (GE Infrastructure) [EMAIL PROTECTED] wrote: All, Ok, it seems to work for maven site but it doesn't seem to work for maven multiproject:site. Is it supposed to? If the answer is yes, this might be a bug, if the answer is no I hope somebody can tell me how to solve this. BUILD FAILED File.. D:\Documents and Settings\Erwin\.maven\cache\maven-multiproject-plugin-1.4.1\plugin.jelly Element... maven:reactor Line.. 104 Column 9 Unable to obtain goal [site] -- D:\Documents and Settings\Erwin\.maven\cache\maven-test-plugin-1.6.2\plugin.jelly:181:54: fail There were test failures. Total time : 2 minutes 36 seconds Finished at : Wednesday, August 24, 2005 10:24:04 AM EDT Thanks, Erwin -Original Message- From: Carlos Sanchez [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 23, 2005 3:33 PM To: Maven Users List Subject: Re: Resent: [m1.1] JCoverage fails multiproject:site. Some help required. setting maven.test.failure.ignore to true *should* be the answer On 8/23/05, Hogeweg, Erwin (GE Infrastructure) [EMAIL PROTECTED] wrote: All, I am still struggling with the issue below. Please let me know if anyone has an answer for me. Your help is highly appreciated. Thanks, Erwin All, How do I prevent that a failing JCoverage JUnit test fails the multiproject:site goal? Obviously fixing the test/code is one answer, but I am looking for the other one ;-) I have already tried to set the property maven.test.failure.ignore to true, but that didn't seem to help. Thanks, Erwin - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Introducing Maven to developers
On Wed, Aug 24, 2005 at 06:18:25PM +0200, Colin Chalmers wrote: 1. By splitting the project up into a number of small sub-projects it's going to make it more difficult for the developers to work on the code. Currently everything is in one CVS project which can easily be checked out using Eclipse. How do others deal with this? By working with different sub-projects in IDE or checking out all into one self-made project (within IDE)? 2. There are a few moans about tranferring builds to different environments whereby other ip-addresses/logins are needed for databases etc. Is it possible to configure property files for these environments and have goals to build for each environment? Other ideas , solutions?? we handle this with checked in configuration templates, and use the ant:replace task to create a working config wiht a custom goal. All logins etc. go into build.properties. This works well, and an automatic setup for testing is also easy then. hth, lothar - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: log4j logging in JUnit tests
Forgot to mention that I also tried adding the following to project.properties: #setup for junit testing maven.junit.sysproperties=log4j.configuration log4j.configuration=log4j.properties which didn't help either... Hans On Wednesday 24 August 2005 18:13, SainTiss wrote: hi, I'm trying to use log4j logging in my JUnit tests instead of some System.out.println statements I have there... So i did the following: 1) add the following to my test class: private static final Logger logger = Logger.getLogger(StmdsocTest.class); 2) Put this log4j.properties file in the top maven dir: log4j.appender.appenderName=be.ac.ua.fots.stmdsoc.test.StmdsocTest log4j.appender.be.ac.ua.fots.stmdsoc.test.StmdsocTest=org.apache.log4j. ConsoleAppender log4j.category.be.ac.ua.fots.stmdsoc.test.StmdsocTest=INFO However, when the tests commence, I always get this warning: log4j:WARN No appenders could be found for logger (be.ac.ua.fots.stmdsoc.test.StmdsocTest). log4j:WARN Please initialize the log4j system properly. This probably means my log4j.properties file is not found? I also tried putting the file in src/ and adding it as a resource in project.xml, both as a normal resource and a unittest resource, but to no avail... Does anyone have any idea as to how this can be solved? Thanks, Hans -- Ark Linux - Linux for the Masses (http://arklinux.org) If we cannot live so as to be happy, let us at least live so as to deserve it -- Immanuel Hermann Fichte Capitalism: You don't have any cows. The bank will not lend you money to buy cows, because you don't have any cows to put up as collateral. Representative Democracy: You have two cows. Your neighbors pick someone to tell you who gets the milk. In a world without walls and fences, who needs windows and gates? I'm a fool. Therefore I'm not. Hans Schippers Aspirant FWO - Vlaanderen Formal Techniques in Software Engineering (FoTS) University of Antwerp Middelheimlaan 1 2020 Antwerpen - Belgium Phone: +32 3 265 38 71 Fax: +32 3 265 37 77 pgpJExSb8rbJh.pgp Description: PGP signature
Re: [m2] project.artifacts Classpath, etc.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Unfortunately, the answer to the question about a master list of
parameter expressions is currently no. I agree that it'd be nice
(tending toward crucial for new mojo devs) to have some documentation on
parameter expressions. The only excuse I can offer is that we've been
trying to stabilize the parameter expression support as well as get the
implementation in general running and stable before diving into
documentation and complementary tool support (like what you'd need to
query for a parameter expression API). I'll see if I can't put something
together in the maven-projecthelp-plugin...simply massage a reflective
lookup of the get*() methods in certain classes, listed below. In
addition, I've recently introduced the concept of banned and
deprecated parameter expressions...so this plugin would have to query
that info as well.
What I can give you right now is a set of pointers to the source code
where you can calculate the expressions you might need. For specific
questions, of course, we can answer directly as needed. Other than a few
special parameter expressions, like ${localRepository}, all params are
reflective lookups against a few key objects:
* ${project.*} == org.apache.maven.project.MavenProject
~(under maven-project in SVN)
* ${plugin.*} == org.apache.maven.plugin.descriptor.PluginDescriptor
~(under maven-plugin-descriptor in SVN)
* ${session.*} == org.apache.maven.execution.MavenSession
~(under maven-core in SVN)
In addition, we have two syntaxes for accessing plexus components as
parameters (one is deprecated):
* @component role= role-hint=
* @parameter expression=${component.fully.qualified.role} (deprecated)
HTH,
john
Chris Berry wrote:
| Thanks John,
| I guess what would be most helpful would be a list of what properties
| one can access. One can figure out types by trial-and-error -- the
| compiler will let you know. But there is really no guessing the
| property names. Although I gather that the Model (the hierarchy of XML
| elements) is transparently reflected by corresponding properties (e.g.
| project.build.plugins). Is that correct?? But other properties -- like
| those for plugins -- are not obvious. Is there any way (some API) to
| simply print all available properites (similar to
| System.getProperties())?? That would be very convenient.
| Thanks,
| -- Chris
|
|
| On 8/23/05, John Casey [EMAIL PROTECTED] wrote:
|
| Chris,
|
| If you're looking to retrieve only a particular dependency of a plugin
| (the dependencies of the plugin project are what form the plugin's
| classpath), then you might do well to use ${plugin.artifactMap}. This
| Map instance is keyed by an artifact's groupId:artifactId, and you can use
|
| org.apache.maven.artifact.ArtifactUtils.versionlessKey( String
| groupId,String
artifactId)
|
| as a standard way of accessing it. The values are
| org.apache.maven.artifact.Artifact instances, IIRC. If you want to get
| the actual jar, though, you can call Artifact.getFile() which should
| return the jar file used for that artifact.
|
| Sorry to say that the documentation is a little weak right now, as we're
| still killing bugs and firming up the last niggling design issues. As
| you can see, there is a lot of information missing. Until we can firm up
| our documentation, please don't hesitate to keep asking questions. This
| will have the added benefit of showing us how best to document the system.
|
| hope that helps,
|
| -john
|
| Edwin Punzalan wrote:
| | To get the artifacts that's relative only to your plugin, you can use
| | ${plugin.artifacts}.
| |
| | Its the same as ${project.artifacts} except the project object is your
| | plugin.
| |
| |
| |
| | Chris Berry wrote:
| |
| | Thanks much for your answer.
| | When a plugin is called, I'm confused as to what Classpath the plugin
| | itself gets. I see the project gets what I would expect, the
| | dependencies from the POM -- at least that is what I see in
| | project.artifacts.
| |
| | But the plugin doesn't seem to get it's dependencies... When I print
| | System.getProperty(java.class.path) I see only::
| | [INFO] current Classpath=
| |
c:\cwb-tools\ant\maven-2.0-beta-cwb/core/boot/classworlds-1.1-alpha-2.jar
| |
| | Is there a set of properties for plugins like there is for project
| | (i.e. plugin.artifacts)??
| |
| | Does classworlds take care of this somehow?? I know that, for example,
| | Ant must be on my Classpath because teh plugin is able to invoke it...
| |
| | Thanks,
| | -- Chris
| |
| |
| | On 8/23/05, Trygve Laugstøl [EMAIL PROTECTED] wrote:
| |
| |
| | On Tue, Aug 23, 2005 at 05:52:59PM -0500, Chris Berry wrote:
| |
| |
| | Greetings,
| | I am trying to figure out how to pass on the Classpath to Ant. I know
| | how to do this programmatically in Ant (e.g. project.setProperty) .
| | What I am trying to work out is how pass on the Classpath from the
| | *plugin*. By trial and
[m1] get current Maven properties
How should I get the properties that Maven is using in a given moment? For a central Maven server how can I force the plugins and cache folders to remain in /maven-1.0.2/.maven folder instead of $HOME/.maven Where should the defaults.properties should be located in order to Maven actually read the properties set on it? Thank you Alex - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] plugin.getDependencyPath
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
One thing we're considering adding to m2 in the very near term is the
concept of dependencies that are tied directly to a plugin definition.
This is important for several use cases, not the least of which being
the use of non-core ant task libraries. Another use case might be the
inclusion of xdoclet modules, and yet another a testing harness for
integration testing an application.
With this feature, you'd only have to define the antrun plugin, along
with the axis dependency directly under the plugin definition. Then,
your ant script should be able to find the axis tasks in the plugin's
classpath.
As for locating plugin resources, it depends on what you're looking for.
If it's bundled with the plugin or one of its dependencies, you should
be able to use ClassLoader.getResource(..) to retrieve it by name. OTOH,
if you're trying to get the path to one of the plugin dependencies, you
can execute something similar to the following:
/**
~ * @parameter expression=${plugin.artifactMap}
~ * @required
~ * @readonly
~ */
private Map pluginArtifacts;
public void execute()
{
~ String key = ArtifactUtils.versionlessKey( depGroupId,
depArtifactId );
~ Artifact artifact = (Artifact) pluginArtifacts.get( key );
~ File depPath = artifact.getFile();
~ .
~ .
~ .
}
Does this answer your question, or am I misunderstanding?
- -john
Chris Berry wrote:
| Hi Kenney,
| I am using your plugin. Thanks. In fact, I've already extended it to
| allow it to set Ant's message level (so you can see Ant's echo when
| you need to).
|
| I believe that Ant + Maven is the sweet spot. What I'm trying to
| discern is the cleanest way to accomplish this.
|
| Say you want to use an extended Ant -- pulling in, say, the Axis Ant
| Tasks, or the ant-contrib Tasks, or whatever. I'm thinking that I will
| simply extend AbstractAntMojo with, say, AxisAntMojo. This will have
| the proper dependencies (axis:ant, etc) and when I call ant
| inheritAll=true inheritRefs=true antfile= -- then I should be
| able to find these Tasks on the inherited Classpath (right??)
|
| I'm hoping that I will be able to ask the Plugin for it's resources --
| so that I can find the Ant buildfile easily. I'm still figuring it
| out...
|
| Thanks again,
| -- Chris
|
| On 8/24/05, Kenney Westerhof [EMAIL PROTECTED] wrote:
|
|On Wed, 24 Aug 2005, Chris Berry wrote:
|
|Hi,
|
|In m2 you just specify that jar as a dependency in the pom of the plugin.
|It's then automatically added to the runtime classpath of that plugin's
|execution environment. Further, you can access the Plugin object and
|it's properties in a Mojo.
|
|Btw, if you plan to use ant in your plugins, have a look at the
|maven-antrun-plugin. If you plan to use it, you should make your plugin
|depend upon it, and extend AbstractAntTask. You can then create tasks,
|add them to a Target object, and execute them (using a parent method).
|(the plugin is part of the m2 svn repository).
|
|-- Kenney
|
|
|Hi,
|In the bad old days of Jelly, we could type something like::
|plugin.getDependendcyPath( 'axis:ant' );
|And you got back the full path to a JAR -- so we could use it as::
| ant:path id=axis.classpath
|ant:pathelement path=${plugin.getDependencyPath('axis:axis')}/
|Is there an equivalent helper function like this for Java??
|
|BTW: FWIW: I have no interest in using Marmalade. I want to use *only*
|Java + Ant when developing my plugins. In fact, I plan to do as much
|as possible with Ant and simply fire it from the Maven plugin
|structure. There is no reason to reinvent the wheel. Ant provides
|Tasks to do probably 95% of what I need done. Is well understood, well
|supported, and well documented. I see this sort of marraige between
|Maven and Ant as powerful combination.
|
|Thanks,
|-- Chris
|
|-
|To unsubscribe, e-mail: [EMAIL PROTECTED]
|For additional commands, e-mail: [EMAIL PROTECTED]
|
|
|
|--
|Kenney Westerhof
|http://www.neonics.com
|GPG public key: http://www.gods.nl/~forge/kenneyw.key
|
|-
|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]
|
|
|
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.6 (GNU/Linux)
iD8DBQFDDMqEK3h2CZwO/4URAp42AJ9Zzk5jbQtWStXNlTX6UPZztxf3yACfWlaf
tSzvsHb6CfBP9SQB8ZIOf1M=
=IdwA
-END PGP SIGNATURE-
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: log4j logging in JUnit tests
On Aug 24, 2005, at 12:08 PM, SainTiss wrote:
Forgot to mention that I also tried adding the following to
project.properties:
#setup for junit testing
maven.junit.sysproperties=log4j.configuration
log4j.configuration=log4j.properties
which didn't help either...
Hans
log4j is really confusing. The log4j.configuration property should be
a URL, _not_ a path. It doesn't give much of an error when
misconfigured - there's nothing to distinguish between not finding a
system property, finding a system property that didn't parse as a
URL, and being unable to open that URL.
It should work if you change your log4j.configuration line to this:
log4j.configuration=file:${basedir}/log4j.properties
If that doesn't work, try adding log4j.debug:
maven.junit.sysproperties=log4j.configuration log4j.debug
log4j.configuration=file:${basedir}/log4j.properties
log4j.debug=true
IIRC, it returns a bit more useful information then.
--
Scott Lamb http://www.slamb.org/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] plugin.getDependencyPath
Comments inline.
Thanks,
-- Chris
On 8/24/05, John Casey [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
One thing we're considering adding to m2 in the very near term is the
concept of dependencies that are tied directly to a plugin definition.
Don't we already have this?? I have dependencies defined for my plugin
and they are all there when I call my Ant tasks (using an extended
version of AbstractAntMojo). I have verified this.
As for locating plugin resources, it depends on what you're looking for.
If it's bundled with the plugin or one of its dependencies, you should
be able to use ClassLoader.getResource(..) to retrieve it by name. OTOH,
if you're trying to get the path to one of the plugin dependencies, you
can execute something similar to the following:
/**
~ * @parameter expression=${plugin.artifactMap}
~ * @required
~ * @readonly
~ */
private Map pluginArtifacts;
public void execute() {
~ String key = ArtifactUtils.versionlessKey( depGroupId, depArtifactId );
~ Artifact artifact = (Artifact) pluginArtifacts.get( key );
~ File depPath = artifact.getFile();
Does this answer your question, or am I misunderstanding?
Unfortunately, this doesn't really work in my case. Say I have an Ant
build file named axis.xml and I bundle this into my Plugin JAR. I
cannot access this as a File. Yes, it has a path in the URL sense (i.e
jar:/...) But Ant wants a regular old file that I can get an absolute
path to. (BTW: Ant is just an example. The same could hold true for
many other situations)
Is there any way to bundle files (such as axis.xml) into the
repository -- such that I could access it directly as,say,
${localRepository}/blah/plugins/axis-plugin/1.0-SNAPSHOT/axis.xml
Of course, I could unjar the Plugin into /target -- but that seems
like a hack...
Thanks for all your help insight,
Cheers,
-- Chris
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Modifying releases.jsl
I modified the multi-releases plugin to add a column containing the current version of the product. This makes it easier for me to find dependencies that I might have to release before I release my application. The report now looks something like this: Project nameLatest versionReleased dateNext ReleaseASI1.0.32005-07-251.0.3 BARTS1.1.62005-08-221.1.6BOSS1.0.102005-05-191.0.10Bouncer1.0.72005-08-23 1.0.7Boxoffice1.0.72005-08-231.0.7CAVES BTN1.0.72005-03-081.0.7CRABS1.1.8 2005-08-151.1.8East2.0.162005-07-272.0.16East CABS1.0.92005-07-271.0.9 FlatFiles1.3.42005-07-251.3.4Hackney1.2.22005-03-141.2.3 What I'd really like to do is highlight lines where the latest version is different from the next release. Could somebody with a metter understanding of Jelly and jsl give me an idea of how to do this?
Re: [m2] plugin.getDependencyPath
On Wed, 24 Aug 2005, Chris Berry wrote:
One thing we're considering adding to m2 in the very near term is the
concept of dependencies that are tied directly to a plugin definition.
Don't we already have this?? I have dependencies defined for my plugin
and they are all there when I call my Ant tasks (using an extended
version of AbstractAntMojo). I have verified this.
The difference is that the project USING the plugin can define jars that
are included in the _plugin_ classpath ONLY. So you could for instance
enhance the antrun plugin with regexp filemappers by including
jakarta-regexp there. Right now the xdoclet plugin (using the antrun
plugin) has to define ALL xdoclet jars (xdoclet modules), so that any user
can use any ejb doclet task. However, there are a lot of them and most are
not used, so I'd like to only include the core libs (xjavadoc, xdoclet
'core' and some core deps). But that's just one usecase.
[snip on plugin.getArtifactMap]
Unfortunately, this doesn't really work in my case. Say I have an Ant
build file named axis.xml and I bundle this into my Plugin JAR. I
cannot access this as a File. Yes, it has a path in the URL sense (i.e
jar:/...) But Ant wants a regular old file that I can get an absolute
path to. (BTW: Ant is just an example. The same could hold true for
many other situations)
So you're building a mojo that executes a built-in build.xml file?
Why don't you hardcode the tasks in the mojo?
Another solution is to run that file using the ant api to parse it:
System.setProperty(
org.apache.tools.ant.ProjectHelper,
org.apache.tools.ant.helper.ProjectHelper2 // this one has URL support
);
Project proj = new Project(); // plus some initialization
ProjectHelper.getProjectHelper().parse( project, buildfileUrl );
If you use the 'ant' task (or subant..?) you can't let it inherit
everything - the properties are resolved using reflection on the
MavenProject etc., and the inheritance mechanism copies all properties to
the child ant 'process', but as each property is evaluated at runtime,
there's no list to copy.
Is there any way to bundle files (such as axis.xml) into the
repository -- such that I could access it directly as,say,
${localRepository}/blah/plugins/axis-plugin/1.0-SNAPSHOT/axis.xml
Nope. The fact that ant can't handle URL's is ant's fault - it could just
as easily work with URLs instead of files.. ;)
Of course, I could unjar the Plugin into /target -- but that seems
like a hack...
It's not forbidden to make workarounds to use 3rd party libs..
You could use getResource() to get the url of the axis.xml,
and store just that file in target/...
Thanks for all your help insight,
You too :)
Btw, could you send me a patch (or create a JIRA and attach it) for your
fix on making echo work? The only solution I saw was to set the 'stdout'
stream to System.err..
-- Kenney
Cheers,
-- Chris
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Kenney Westerhof
http://www.neonics.com
GPG public key: http://www.gods.nl/~forge/kenneyw.key
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m1] bootstrap build error
I fixed some errors on the core. If you can update it and re-launch the bootstrap. Arnaud -Message d'origine- De : Jeff Jensen [mailto:[EMAIL PROTECTED] Envoyé : mercredi 24 août 2005 14:36 À : 'Maven Users List' Objet : [m1] bootstrap build error I have been attempting to build m1 via bootstrap again, and have the following compile errors. I did not find the cause from a quick review, and am wondering if this is a known bootstrap problem before I spend more time with it. I have verified the classes exist, visual inspection found no problems. I am wondering about bootstrap classpath, etc.? From revision 239628. [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\ org\apache\mav en\ejb\EJBArtifactTypeHandler.java:20: cannot find symbol [exec] [javac] symbol : class MavenException [exec] [javac] location: package org.apache.maven [exec] [javac] import org.apache.maven.MavenException; [exec] [javac] ^ [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\ org\apache\mav en\ejb\EJBArtifactTypeHandler.java:21: cannot find symbol [exec] [javac] symbol : class Project [exec] [javac] location: package org.apache.maven.project [exec] [javac] import org.apache.maven.project.Project; [exec] [javac] ^ [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\ org\apache\mav en\ejb\EJBArtifactTypeHandler.java:22: package org.apache.maven.repository does not exist [exec] [javac] import org.apache.maven.repository.ArtifactTypeHandler; [exec] [javac]^ [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\ org\apache\mav en\ejb\EJBArtifactTypeHandler.java:31: cannot find symbol [exec] [javac] symbol: class ArtifactTypeHandler [exec] [javac] public class EJBArtifactTypeHandler implements ArtifactTypeHandler [exec] [javac] ^ [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\ org\apache\mav en\ejb\EJBArtifactTypeHandler.java:40: cannot find symbol [exec] [javac] symbol : class Project [exec] [javac] location: class org.apache.maven.ejb.EJBArtifactTypeHandler [exec] [javac] public String constructRepositoryDirectoryPath(String type, Project project) throws MavenException [exec] [javac] ^ [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\ org\apache\mav en\ejb\EJBArtifactTypeHandler.java:40: cannot find symbol [exec] [javac] symbol : class MavenException [exec] [javac] location: class org.apache.maven.ejb.EJBArtifactTypeHandler [exec] [javac] public String constructRepositoryDirectoryPath(String type, Project project) throws MavenException [exec] [javac] ^ [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\ org\apache\mav en\ejb\EJBArtifactTypeHandler.java:56: cannot find symbol [exec] [javac] symbol : class Project [exec] [javac] location: class org.apache.maven.ejb.EJBArtifactTypeHandler [exec] [javac] public String constructRepositoryFullPath(String type, Project project, String version) throws MavenException [exec] [javac] ^ [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\ org\apache\mav en\ejb\EJBArtifactTypeHandler.java:56: cannot find symbol [exec] [javac] symbol : class MavenException [exec] [javac] location: class org.apache.maven.ejb.EJBArtifactTypeHandler [exec] [javac] public String constructRepositoryFullPath(String type, Project project, String version) throws MavenException [exec] [javac] ^ [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\ org\apache\mav en\ejb\EJBArtifactTypeHandler.java:58: internal error; cannot instantiate StringBuffer(int) at java.lang.StringBuffer to () [exec] [javac] StringBuffer path = new StringBuffer(constructRepositoryDirectoryPath(type, project)); [exec] [javac] ^ [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\ org\apache\mav en\ejb\EJBArtifactTypeHandler.java:70: cannot find symbol [exec] [javac] symbol : class MavenException [exec] [javac] location: class org.apache.maven.ejb.EJBArtifactTypeHandler [exec] [javac] throw new MavenException(Unrecognised ejb type (is + type + )); [exec] [javac] ^ [exec] [javac] 10 errors
Re: [m2] plugin.getDependencyPath
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Berry wrote:
snip/
|One thing we're considering adding to m2 in the very near term is the
|concept of dependencies that are tied directly to a plugin definition.
|
|
| Don't we already have this?? I have dependencies defined for my plugin
| and they are all there when I call my Ant tasks (using an extended
| version of AbstractAntMojo). I have verified this.
|
What I'm talking about is per-project dependencies for a given plugin.
For example, the xdoclet plugin may only specify the dependencies it
needs to run the engine. If you, as the plugin user, want to have
xdoclet generate an EJB deployment descriptor, you might include the
xdoclet-ejb dependency in your definition of the xdoclet plugin - within
your project. This would allow people to resolve only the xdoclet
artifacts that they really need, rather than the sum total of modules
that xdoclet provides...a collection which would quickly fall out of
date as third parties might write new modules.
NOTE: This is not a question of extending one plugin with another, in
order to redefine the dependencies. This is customizing a list of
optional *additional* dependencies for a given plugin for your project
to use.
snip/
| Unfortunately, this doesn't really work in my case. Say I have an Ant
| build file named axis.xml and I bundle this into my Plugin JAR. I
| cannot access this as a File. Yes, it has a path in the URL sense (i.e
| jar:/...) But Ant wants a regular old file that I can get an absolute
| path to. (BTW: Ant is just an example. The same could hold true for
| many other situations)
It's a bit clunky, but if you're trying to do this from a java-based
mojo (i.e. not from an ant script or the antrun plugin's configuration),
you can try the following:
// note: there are better ways to do this next line...but this generally
// works.
ClassLoader cl = getClass().getClassLoader();
URL resource = cl.getResource(/path/to/resource/in/classpath);
File concreteFile = new File( resource.getPath() );
|
| Is there any way to bundle files (such as axis.xml) into the
| repository -- such that I could access it directly as,say,
| ${localRepository}/blah/plugins/axis-plugin/1.0-SNAPSHOT/axis.xml
It is possible to do that sort of thing, but it means making the
axis.xml some sort of first-class artifact to be built and deployed.
It's a bit of a hack...
|
| Of course, I could unjar the Plugin into /target -- but that seems
| like a hack...
I think you'll find the trick above will be a simpler solution, actually...
Cheers,
- -john
|
| Thanks for all your help insight,
| Cheers,
| -- Chris
|
| -
| To unsubscribe, e-mail: [EMAIL PROTECTED]
| For additional commands, e-mail: [EMAIL PROTECTED]
|
|
|
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.6 (GNU/Linux)
iD8DBQFDDQ0MK3h2CZwO/4URAhAFAJ9zaRW2n1XJeXxJieaqdBe/i9V+7wCZAcHu
AKQpiSNvGNIcUoE7a/Phvbo=
=kNot
-END PGP SIGNATURE-
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M2] outdated xsd?
Hi Erick Try to update your m2 from SVN and bootstrap it. Regards, allan Erick Dovale wrote: I am using maven 2.0 alpha-3. Is there any beta release yet?? In my pom I have: 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; Is this the right one?? Erick. Edwin Punzalan wrote: What version of m2 are you using? For beta, reports is deprecated and reporting replaced it. Erick Dovale wrote: Hi there, I just noticed that when adding reports to my pom.xml file my validator does not recognize the reporting tag; it recognizes the reports though but, when using the reports tag m2 spits out a message saying that it is deprecated and suggest to use reporting. Is this a known bug?? I search for it in Jira and did not find anything like it. cheers, Erick. - 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: [m1] get current Maven properties
On 8/25/05, Mayorgaadame, Alex [IT] [EMAIL PROTECTED] wrote:
How should I get the properties that Maven is using in a given moment?
depends on which properties, but ${maven.home}, ${maven.home.local},
${maven.repo.local} are probably the ones you are talking about.
For a central Maven server how can I force the plugins and cache folders to
remain in
/maven-1.0.2/.maven folder instead of $HOME/.maven
MAVEN_HOME_LOCAL env var
Where should the defaults.properties should be located in order to Maven
actually read the properties set on it?
Inside maven.jar. It's not a recommended way of customising Maven
(that was from a very old document - is it still online and linked
from somewhere?)
You should just use ~/build.properties on a per user basis.
- Brett
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m1] bootstrap build error
Thanks Arnaud. These are the new files pulled down: C:\devroot\reference\mavensvn co http://svn.apache.org/repos/asf/maven/maven-1/core/trunk maven-1/core/trunk U maven-1\core\trunk\src\java\org\apache\maven\repository\AbstractArtifact.jav a U maven-1\core\trunk\src\bin\maven.bat U maven-1\core\trunk Checked out revision 239972. C:\devroot\reference\mavensvn co http://svn.apache.org/repos/asf/maven/maven-1/plugins/trunk maven-1/plugins/trunk U maven-1\plugins\trunk\javadoc\xdocs\changes.xml U maven-1\plugins\trunk\pdf\xdocs\changes.xml Checked out revision 239972. And I get the same build errors. -Original Message- From: Arnaud HERITIER [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 24, 2005 6:30 PM To: 'Maven Users List' Subject: RE: [m1] bootstrap build error I fixed some errors on the core. If you can update it and re-launch the bootstrap. Arnaud -Message d'origine- De : Jeff Jensen [mailto:[EMAIL PROTECTED] Envoyé : mercredi 24 août 2005 14:36 À : 'Maven Users List' Objet : [m1] bootstrap build error I have been attempting to build m1 via bootstrap again, and have the following compile errors. I did not find the cause from a quick review, and am wondering if this is a known bootstrap problem before I spend more time with it. I have verified the classes exist, visual inspection found no problems. I am wondering about bootstrap classpath, etc.? From revision 239628. [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\ org\apache\mav en\ejb\EJBArtifactTypeHandler.java:20: cannot find symbol [exec] [javac] symbol : class MavenException [exec] [javac] location: package org.apache.maven [exec] [javac] import org.apache.maven.MavenException; [exec] [javac] ^ [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\ org\apache\mav en\ejb\EJBArtifactTypeHandler.java:21: cannot find symbol [exec] [javac] symbol : class Project [exec] [javac] location: package org.apache.maven.project [exec] [javac] import org.apache.maven.project.Project; [exec] [javac] ^ [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\ org\apache\mav en\ejb\EJBArtifactTypeHandler.java:22: package org.apache.maven.repository does not exist [exec] [javac] import org.apache.maven.repository.ArtifactTypeHandler; [exec] [javac]^ [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\ org\apache\mav en\ejb\EJBArtifactTypeHandler.java:31: cannot find symbol [exec] [javac] symbol: class ArtifactTypeHandler [exec] [javac] public class EJBArtifactTypeHandler implements ArtifactTypeHandler [exec] [javac] ^ [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\ org\apache\mav en\ejb\EJBArtifactTypeHandler.java:40: cannot find symbol [exec] [javac] symbol : class Project [exec] [javac] location: class org.apache.maven.ejb.EJBArtifactTypeHandler [exec] [javac] public String constructRepositoryDirectoryPath(String type, Project project) throws MavenException [exec] [javac] ^ [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\ org\apache\mav en\ejb\EJBArtifactTypeHandler.java:40: cannot find symbol [exec] [javac] symbol : class MavenException [exec] [javac] location: class org.apache.maven.ejb.EJBArtifactTypeHandler [exec] [javac] public String constructRepositoryDirectoryPath(String type, Project project) throws MavenException [exec] [javac] ^ [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\ org\apache\mav en\ejb\EJBArtifactTypeHandler.java:56: cannot find symbol [exec] [javac] symbol : class Project [exec] [javac] location: class org.apache.maven.ejb.EJBArtifactTypeHandler [exec] [javac] public String constructRepositoryFullPath(String type, Project project, String version) throws MavenException [exec] [javac] ^ [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\ org\apache\mav en\ejb\EJBArtifactTypeHandler.java:56: cannot find symbol [exec] [javac] symbol : class MavenException [exec] [javac] location: class org.apache.maven.ejb.EJBArtifactTypeHandler [exec] [javac] public String constructRepositoryFullPath(String type, Project project, String version) throws MavenException [exec] [javac] ^ [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\ org\apache\mav
Re: [m2] javadocs??
There is a javadoc plugin in svn... here: https://svn.codehaus.org/home/projects/mojo/scm/trunk/mojo Checkout maven-javadoc-plugin and m2 install so you can use it. Most of the plugins in there have not been officially released. And some are even still in progress. Although I can guarantee that javadoc is already usable. ;) The list of plugins and their progress from m1 to m2 can be seen here: http://docs.codehaus.org/display/MAVEN/Maven+Plugin+Matrix. Also, you need to set it up for your site:site, though. So, your pom.xml should have this: . reporting plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId version1.0-SNAPSHOT/version /plugin /plugins /reporting ... Chris Berry wrote: I suppose the javadocs for maven2 are somewhere on the site -- but I cannot locate them. The old, familiar Project Reports is missing. And I've trolled thru most pages looking. I also tried to run m2 site:site on my local SVN checkout (it died). So I'm at a loss... Are there any javadocs available for m2?? Thanks, -- Chris - 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: Introducing Maven to developers
I agree with the incremental approach. One of the first things I did in introducing Maven to my current client is to just set it up to generate site. I started on my PC and generated site to it, sharing a file:// URL for others to use the HTML pages. The value of all the reference docs (Javadoc, xref, FAQs), automated code review results, JUnit results, and Cobertura results became apparent fast, and affected process and standards change - in a very good manner. Since your customers think they are happy with the current build setup, I suggest you generate site first and get that part of the process. Then work on having Maven correctly build the distributables too, and ease into that as site is accepted. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 24, 2005 11:59 AM To: Maven Users List Subject: Re: Introducing Maven to developers Concerning Argument 1: If you can't get them to see the value then you may want to use an incremental approach. This will involve more work on the front end for you though... Instead of changing the structure of their source, you can create a maven/ant script that will download the source and place it into your current directory (on Windows it might be c:\myMavenArea) into a directory structure that maven likes( c:\myMavenArea\projectName\src\main\java\com... ) . Then perform the build as you normally would with maven. That way, you can create the build and show them the value of using Maven without changing any or their source or their existing ant scripts. If you want, you could then hold a lunch time learning session about Maven and show them the massive and complex current ANT scripts compared to the comparitivley small Maven script as well as the other nice project management features you get for free using the maven plugins... Colin Chalmers [EMAIL PROTECTED] wrote on 08/24/2005 12:18:25 PM: 1. By splitting the project up into a number of small sub-projects it's going to make it more difficult for the developers to work on the code. Currently everything is in one CVS project which can easily be checked out using Eclipse. How do others deal with this? By working with different sub-projects in IDE or checking out all into one self-made project (within IDE)? - 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: [m1] bootstrap build error
Hi Jeff, Yes it was these files ;-( The download of dependencies was broken. I had your problem some days ago, which was the use of a bad release of the maven model in the ejb plugin. But it was fixed :-( Arnaud -Message d'origine- De : Jeff Jensen [mailto:[EMAIL PROTECTED] Envoyé : jeudi 25 août 2005 03:21 À : 'Maven Users List' Objet : RE: [m1] bootstrap build error Thanks Arnaud. These are the new files pulled down: C:\devroot\reference\mavensvn co http://svn.apache.org/repos/asf/maven/maven-1/core/trunk maven-1/core/trunk U maven-1\core\trunk\src\java\org\apache\maven\repository\Abstra ctArtifact.jav a U maven-1\core\trunk\src\bin\maven.bat U maven-1\core\trunk Checked out revision 239972. C:\devroot\reference\mavensvn co http://svn.apache.org/repos/asf/maven/maven-1/plugins/trunk maven-1/plugins/trunk U maven-1\plugins\trunk\javadoc\xdocs\changes.xml U maven-1\plugins\trunk\pdf\xdocs\changes.xml Checked out revision 239972. And I get the same build errors. -Original Message- From: Arnaud HERITIER [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 24, 2005 6:30 PM To: 'Maven Users List' Subject: RE: [m1] bootstrap build error I fixed some errors on the core. If you can update it and re-launch the bootstrap. Arnaud -Message d'origine- De : Jeff Jensen [mailto:[EMAIL PROTECTED] Envoyé : mercredi 24 août 2005 14:36 À : 'Maven Users List' Objet : [m1] bootstrap build error I have been attempting to build m1 via bootstrap again, and have the following compile errors. I did not find the cause from a quick review, and am wondering if this is a known bootstrap problem before I spend more time with it. I have verified the classes exist, visual inspection found no problems. I am wondering about bootstrap classpath, etc.? From revision 239628. [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\ org\apache\mav en\ejb\EJBArtifactTypeHandler.java:20: cannot find symbol [exec] [javac] symbol : class MavenException [exec] [javac] location: package org.apache.maven [exec] [javac] import org.apache.maven.MavenException; [exec] [javac] ^ [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\ org\apache\mav en\ejb\EJBArtifactTypeHandler.java:21: cannot find symbol [exec] [javac] symbol : class Project [exec] [javac] location: package org.apache.maven.project [exec] [javac] import org.apache.maven.project.Project; [exec] [javac] ^ [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\ org\apache\mav en\ejb\EJBArtifactTypeHandler.java:22: package org.apache.maven.repository does not exist [exec] [javac] import org.apache.maven.repository.ArtifactTypeHandler; [exec] [javac]^ [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\ org\apache\mav en\ejb\EJBArtifactTypeHandler.java:31: cannot find symbol [exec] [javac] symbol: class ArtifactTypeHandler [exec] [javac] public class EJBArtifactTypeHandler implements ArtifactTypeHandler [exec] [javac] ^ [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\ org\apache\mav en\ejb\EJBArtifactTypeHandler.java:40: cannot find symbol [exec] [javac] symbol : class Project [exec] [javac] location: class org.apache.maven.ejb.EJBArtifactTypeHandler [exec] [javac] public String constructRepositoryDirectoryPath(String type, Project project) throws MavenException [exec] [javac] ^ [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\ org\apache\mav en\ejb\EJBArtifactTypeHandler.java:40: cannot find symbol [exec] [javac] symbol : class MavenException [exec] [javac] location: class org.apache.maven.ejb.EJBArtifactTypeHandler [exec] [javac] public String constructRepositoryDirectoryPath(String type, Project project) throws MavenException [exec] [javac] ^ [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\ org\apache\mav en\ejb\EJBArtifactTypeHandler.java:56: cannot find symbol [exec] [javac] symbol : class Project [exec] [javac] location: class org.apache.maven.ejb.EJBArtifactTypeHandler [exec] [javac] public String constructRepositoryFullPath(String type, Project project, String version) throws MavenException [exec] [javac] ^ [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\
