Re: source inclusion and exclusion out of the box in maven
I meant in Maven2 On 1/28/06, Dave Maung <[EMAIL PROTECTED]> wrote: > > Is there way to include and exclude java source out of the box in maven > instead of using maven-compiler-plugin? > > > ../main/src/java > > eee.java > > Dave >
source inclusion and exclusion out of the box in maven
Is there way to include and exclude java source out of the box in maven instead of using maven-compiler-plugin? ../main/src/java eee.java Dave
Re: [m2] Hibernate3 SchemaExportTask
Frederik Dierickx wrote: Hi, I'm a recent convert to Maven2 and trying to achieve the same functionality I used to do with Ant. Most of the things work pretty well but one of the things I really got stuck on is the SchemaExportTask using Hibernate3. I tried to install the hibernate3 plugin from the codehaus mojo repository but didn't succeed because of missing dependencies. Another way I am currently trying is simply calling the SchemaExportTask using an Ant call. Using this approach, it seems like the SchemaExportTask cannot be found in the classpath. I do have a dependency on Hibernate3 in my POM and am passing a reference to maven.dependency.classpath to and maven-antrun-plugin. For some reason unclear to me it doesn't seem to work out. The hibernate3 plugin is currently in the sandbox so no guarantees there. As a stopgap you can use the antrun plugin in conjunction with the ant tasks that you are used to. I'd encourage you to give feedback to get the hib3 plugin working but use the antrun plugin if you have to: http://maven.apache.org/plugins/maven-antrun-plugin/ -- jvz. Jason van Zyl jason at maven.org http://maven.apache.org A man enjoys hsi work when he understands the whole and when he is responsible for the quality of the whole -- Christopher Alexander, A Pattern Language - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Adding generated source to jxr report
Lee Meador wrote: Is there a way to add the path for some generated sources to the list of things that jxr will put in its cross reference of source files? They aren't? I'm looking at the JXR plugin over at the mojo project and the source directories that are picked up are the MavenProject.getCompileSourceRoots What plugin are you using to generate sources? The plugin has to add them to the compile source roots and then JXR should be picking them up. Thanks. -- Lee Meador Sent from gmail. My real email address is [EMAIL PROTECTED] -- jvz. Jason van Zyl jason at maven.org http://maven.apache.org In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
ActiveMQ Sub Dependencies version specified as ${xxx_version}
I am working with ActiveMQ 4.0-M3 and it seems I have found a bug. James
Strachan has put a fix on the SVN head and asked me to try it out. When I try
to do the build using Maven2, it reports many sub-depenedent JARS are not
found. The real reason they are not found is because the version of each Jar
is specified as a ${variable}.
I noticed that this has already been encoutered.
http://www.mail-archive.com/users@maven.apache.org/msg29763.html Was it
resolved? (I hope, I hope).
Wayne Irwin
Executing mvn test (JUnit)
Hi Folks Perhaps my problems is very simple: I am creating very simple tests creating simple testcases, when I do the smaller and easier test using some class as which is src folder structure, my tests doesn't work, when I do some foo test, it works, are there some additional information I must to inform in pom.xml to execute the tests ? Thanks in adv Ed - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Extending Maven's POM XML
Jason van Zyl wrote: jean safar wrote: Hi, Is it possible to extend the XML description for POMs in Maven 2? No, but we are discussing adding a element to the POM for general extensions. We are thinking about changes to the POM for integration testing so this might all get rolled into 2.0.3. Currently you cannot have custom extensions in the POM. Shouldn't be better to use schemas for that? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
NOTICE: [m1] plugins removal
Hi, As some of you might know, we are still working on a Maven 1.1 release, which is unfortunately quite behind schedule. The advance of Maven 2 has dragged away a lot of attention and we are currently only three people actively developing and maintaining the Maven 1 core and 65 plugins. It has become evident that there are a number of plugins present in the current Maven core distribution, that are now unmaintained and either out of date, non-functional, or too poorly documented to be useful. In an effort to advance on our release schedule towards a stable Maven 1.1-final, the Maven developers have voted to remove the following plugins from the next release (maven-1.1-beta-3): [] repository - the create-upload-bundle goal will be moved to the artifact plugin [] release - has been deprecated for a while, replaced by scm plugin [] j2ee - not functional [] abbot - unmaintained [] castor - unmaintained, not working [] hibernate - unmaintained [] jboss - unmaintained, can be replaced by cargo plugin [] jbuilder - unmaintained, not on the same level as other IDE plugins [] jcoverage - replaced by Cobertura [] jetty - unmaintained, can be replaced by cargo plugin [] jnlp - unmaintained [] uberjar - not working, can be replaced by javaapp plugin Please note: - All these plugins will still be available using plugin:download to get the version available in Maven 1.0.2. - The source code will be available in the sandbox. - If anyone is willing to step up and maintain any of these plugins, they can offer to look after it, and take it to the sourceforge project. This notice is meant to inform the Maven users community about these upcoming changes. Please let us know if you have any concerns or relevant remarks concerning these steps. Thanks, Lukas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m2] Problems compiling mojo-sandbox
Yes, not all the sandbox plugins depend on jars that are published. -Original Message- From: Fredy [mailto:[EMAIL PROTECTED] Sent: Saturday, January 28, 2006 1:03 PM To: users@maven.apache.org Subject: [m2] Problems compiling mojo-sandbox Hi, if I understand all right, so i've to build the sandbox plugIns (bsp.:axistools) on my own. Now i've checked out mojo-sandbox. but "mvn compile" throws the following error: No versions are present in the repository for the artifact with a range [3.0,] com.solarmetric:kodo-jdo:jar:null from the specified remote repositories: Maven Snapshots (http://snapshots.maven.codehaus.org/maven2/), central (http://repo1.maven.org/maven2), snapshots (http://snapshots.maven.codehaus.org/maven2) anybody knows a fix? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Problems compiling mojo-sandbox
It seems to be possible to compile submodules ;-) Sorry! Axistools comile fine. Thanks Fredy "Maven Users List" schrieb am 28.01.06 19:03:57: Hi, if I understand all right, so i've to build the sandbox plugIns (bsp.:axistools) on my own. Now i've checked out mojo-sandbox. but "mvn compile" throws the following error: No versions are present in the repository for the artifact with a range [3.0,] com.solarmetric:kodo-jdo:jar:null from the specified remote repositories: Maven Snapshots (http://snapshots.maven.codehaus.org/maven2/), central (http://repo1.maven.org/maven2), snapshots (http://snapshots.maven.codehaus.org/maven2) anybody knows a fix? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Mit freundlichen Grüßen Fred Robert Hauschel http://www.Hauschel.de Mobil:0179 - 6917092 Telefon: 07427 - 91179 Fax: 07427 - 91178 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] Problems compiling mojo-sandbox
Hi, if I understand all right, so i've to build the sandbox plugIns (bsp.:axistools) on my own. Now i've checked out mojo-sandbox. but "mvn compile" throws the following error: No versions are present in the repository for the artifact with a range [3.0,] com.solarmetric:kodo-jdo:jar:null from the specified remote repositories: Maven Snapshots (http://snapshots.maven.codehaus.org/maven2/), central (http://repo1.maven.org/maven2), snapshots (http://snapshots.maven.codehaus.org/maven2) anybody knows a fix? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] svn: where are the sources for axistools?
Found it: svn://svn.codehaus.org/mojo/scm/trunk/mojo/mojo-sandbox/axistools-maven-plugin Fredy "Maven Users List" schrieb am 28.01.06 18:12:23: Fredy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Mit freundlichen Grüßen Fred Robert Hauschel http://www.Hauschel.de Mobil:0179 - 6917092 Telefon: 07427 - 91179 Fax: 07427 - 91178 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] svn: where are the sources for axistools?
http://mojo.codehaus.org/source-repository.html -- tom - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m2] how to use plugins from a snapshot repository?
http://mojo.codehaus.org/using-sandbox-plugins.html -Original Message- From: Fredy [mailto:[EMAIL PROTECTED] Sent: Saturday, January 28, 2006 12:24 PM To: users@maven.apache.org Subject: [m2] how to use plugins from a snapshot repository? How can i use/reference this in my local enviroment: http://snapshots.maven.codehaus.org/maven2/org/codehaus/mojo/axistools-m aven-plugin/0.1-SNAPSHOT/ Fredy - 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] how to use plugins from a snapshot repository?
How can i use/reference this in my local enviroment: http://snapshots.maven.codehaus.org/maven2/org/codehaus/mojo/axistools-maven-plugin/0.1-SNAPSHOT/ Fredy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] svn: where are the sources for axistools?
Fredy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: SVN/SCM Release Help
Use -Dusername= I'm not sure about the password, I have SVN save it for me. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, January 27, 2006 7:25 PM To: users@maven.apache.org Subject: SVN/SCM Release Help I'm moving from an ANT build script to Maven, and also moving from a windows build machine to linux. Previously, all of the SVN SCM release activities were carried out through TortoiseSVN on that windows machine - I would like to use the release plugin to accomplish what was previously a multi-step manual process.. When I execute the release:prepare step using the following command I get an authorization failed error: mvn release:prepare \ -Dproject.scm.developerConnection=scm:svn:http://MY_URL/trunk \ -DtagBase=http://MY_URL/tags \ -Dmaven.scm.username=MY_UN -Dmaven.scm.password=MY_PW I have verified that svn is in my path and have verified that I can commit when using the svn command direcly from the shell. Can anyone point me in the right direction or offer some suggestions for where else to look? I have read everything I could get my hands on as well as the archives to this list. Thanks in advance, Brian Yoffe + Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'release'. [INFO] [INFO] Building Commons Library [INFO]task-segment: [release:prepare] (aggregator-style) [INFO] [INFO] [release:prepare] [INFO] What tag name should be used? 1.1.2 [INFO] Tagging release with the label 1.1.2. Provider message: The svn tag command failed. Command output: svn: Commit failed (details follow): svn: CHECKOUT of '/svn/repos/platformautotrading_common/!svn/ver/11/tags': authorization failed (http://reuse.ny.jpmorgan.com) [INFO] [ERROR] BUILD ERROR [INFO] [INFO] An error is occurred in the tag process. Embedded error: Error! [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: An error is occurred in the tag process. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default LifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoa l(DefaultLifecycleExecutor.java:485) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL ifecycleExecutor.java:455) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle Failures(DefaultLifecycleExecutor.java:303) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( DefaultLifecycleExecutor.java:216) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec ycleExecutor.java:139) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: An error is occurred in the tag process. at org.apache.maven.plugins.release.PrepareReleaseMojo.tagRelease(PrepareRe leaseMojo.java:1414) at org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareRelea seMojo.java:246) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa nager.java:415) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default LifecycleExecutor.java:531) ... 16 more Caused by: org.apache.maven.scm.ScmException: Error! at org.apache.maven.plugins.release.helpers.ScmHelper.checkResult(ScmHelper .java:124) at org.apache.maven.plugins.release.helpers.ScmHelper.tag(ScmHelper.java:22 6) at org.apache.maven.plugins.release.PrepareReleaseMojo.tagRelease(PrepareRe leaseMojo.java:1410) ... 19 more [INFO] [INFO] Total time: 7 seconds [INFO] Finished at: Fri Jan 27 19:20:04 EST 2
Re: scm checkout directory
according to this page,
http://maven.apache.org/plugins/maven-release-plugin/perform-mojo.html
the only way to change location of checkout dir is
to modify your project.build.directory element in your pom.xml.
you can modify the annotation of workingDirectory ( in PerformMojo.java) to
/**
* @parameter expression=${workingDirectory} default-value="${
project.build.directory}/checkout"
* @required
*/
protected String workingDirectory;
test it out and submit the patch. One implication, mvn clean will no longer
clean up your altered checkout dir
-D
On 9/18/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> Hi ..
> Is there anyway to change SCM checkout directory in Maven2 .
> I'm using mvn release:perform,Please help me
>
>
> Regards
> Saravana
>
scm checkout directory
Hi .. Is there anyway to change SCM checkout directory in Maven2 . I'm using mvn release:perform,Please help me Regards Saravana
