Automate modifying Maven site index when releasing
As part of our release process we create a distribution package that is automatically published with site deploy to make it available for users to download it (we also use changes plugin to send release announcement automatically). One small, but annoying manual step we still haven't been able to automate is to add a link to the new release on our site index page (we use APT format with Velocity filtering - i.e. index.apt.vm for example). The links to the previous releases are preserved on the page, so basically the page would have to modified then checked back in while doing release:prepare. Is anybody doing anything like this, any suggestions how to make it all automatic? Alternative ways - like always generating the links to releases from the the available tags might work as well (perhaps doable but doesn't look very straightforwarded to me). Kalle
Re: project structure and maven.
On Wed, Feb 4, 2009 at 1:11 AM, MacMohan wrote: > [INFO] Trace > java.lang.NullPointerException >at > org.codehaus.plexus.util.DirectoryScanner.scandir(DirectoryScanner.ja > va:712) >at Maybe this? http://jira.codehaus.org/browse/PLXUTILS-46 You could try a mvn -X as well to get more information. -- Geoffrey Wiseman http://www.geoffreywiseman.ca/
Re: project structure and maven.
Thanks Geoffrey, for your quick response. I read into pom.xml in detail and updated the same. Now when im telling maven to compile its giving me a fatal error: [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [INFO] Trace java.lang.NullPointerException at org.codehaus.plexus.util.DirectoryScanner.scandir(DirectoryScanner.ja va:712) at org.codehaus.plexus.util.DirectoryScanner.scandir(DirectoryScanner.ja va:727) at org.codehaus.plexus.util.DirectoryScanner.scan(DirectoryScanner.java: 593) at org.apache.maven.plugin.resources.ResourcesMojo.copyResources(Resourc esMojo.java:158) at org.apache.maven.plugin.resources.ResourcesMojo.execute(ResourcesMojo .java:100) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi nManager.java:451) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:558) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi fecycle(DefaultLifecycleExecutor.java:499) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau ltLifecycleExecutor.java:478) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan dleFailures(DefaultLifecycleExecutor.java:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen ts(DefaultLifecycleExecutor.java:291) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi fecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) i used mvn compile -e comand and this is the result. Can you sight the problem please? Thanks, MacMohan. > The pom allows you to tell Maven where to find your source files, your > resources, test resources, and so on. > -- View this message in context: http://www.nabble.com/project-structure-and-maven.-tp21824471p21824991.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: project structure and maven.
On Wed, Feb 4, 2009 at 12:01 AM, Geoffrey Wiseman < geoffrey.wise...@gmail.com> wrote: > On Tue, Feb 3, 2009 at 11:55 PM, MacMohan wrote: > >> i m using ant 1.6 to make war files. But now my company wants me to use >> Maven to do nightly builds and deployment of project for testing and >> development environment. >> >> My question is: Do i have to re arrange my project structure to standard >> directory layout to use maven? > > > Not necessarily - Maven's pretty flexible if you want it to be. You can > redefine the locations as need be for the most part. That said, if you > stuck with Maven for the long haul, I probably would restructure the project > at some point, either a piece at a time or in one big > ... chunk. Sorry, sent early. if no then how to make maven understand what my project structure is? The pom allows you to tell Maven where to find your source files, your resources, test resources, and so on. > an if yes, do you think i need to migrate to maven from ant just for > nightly > builds and deployment? Can't i do that some other way? > Well, I don't know anything about the tools and processes in your company, but it's certainly possible to do nightly builds and deployment using Ant. - Geoffrey -- Geoffrey Wiseman http://www.geoffreywiseman.ca/
Re: project structure and maven.
On Tue, Feb 3, 2009 at 11:55 PM, MacMohan wrote: > i m using ant 1.6 to make war files. But now my company wants me to use > Maven to do nightly builds and deployment of project for testing and > development environment. > > My question is: Do i have to re arrange my project structure to standard > directory layout to use maven? Not necessarily - Maven's pretty flexible if you want it to be. You can redefine the locations as need be for the most part. That said, if you stuck with Maven for the long haul, I probably would restructure the project at some point, either a piece at a time or in one big > > > my-app > |-- pom.xml > `-- src >|-- main >| `-- java >| `-- com >| `-- mycompany >| `-- app >| `-- App.java >`-- test >`-- java >`-- com >`-- mycompany >`-- app >`-- AppTest.java > > if no then how to make maven understand what my project structure is? > > an if yes, do you think i need to migrate to maven from ant just for > nightly > builds and deployment? Can't i do that some other way? > > Please help. > > Regards, > MacMohan. > -- > View this message in context: > http://www.nabble.com/project-structure-and-maven.-tp21824471p21824471.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > -- Geoffrey Wiseman http://www.geoffreywiseman.ca/
project structure and maven.
hi, presently the project structure my company is using is that of a tomcat project. myApplication |-- CSS(folder) |-- images |-- java scripts(folder) |-- JSP(folder) |-- WEB_INF(folder) ||-- classes ||-- lib ||-- src || |-- com || |-- companyName || |-- applicationName || |-- Java files in their respective folders || || ||--struts-config.xml | |--build.xm |--build.properties i m using ant 1.6 to make war files. But now my company wants me to use Maven to do nightly builds and deployment of project for testing and development environment. My question is: Do i have to re arrange my project structure to standard directory layout to use maven? my-app |-- pom.xml `-- src |-- main | `-- java | `-- com | `-- mycompany | `-- app | `-- App.java `-- test `-- java `-- com `-- mycompany `-- app `-- AppTest.java if no then how to make maven understand what my project structure is? an if yes, do you think i need to migrate to maven from ant just for nightly builds and deployment? Can't i do that some other way? Please help. Regards, MacMohan. -- View this message in context: http://www.nabble.com/project-structure-and-maven.-tp21824471p21824471.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: surefire with jboss embedded
Is there an example out there which shows how these are supposed to work
together? I'm seeing one issue after another. This whole thing has been
incredibly frustrating.
monkeyden wrote:
>
> project structure:
> main pom
> \-ear
> \-ejb
> \-war
>
> I have the ejb pom set up to run surefire and testng, like so:
>
>
> org.apache.maven.plugins
> maven-surefire-plugin
> ${surefire.version}
>
>
>
> user.timezone
> Etc/UTC
>
>
> java.protocol.handler.pkgs
> org.jboss.virtual.protocol
>
>
> sun.lang.ClassLoader.allowArraySyntax
> true
>
>
>
> -Xms128m -Xmx256m -XX:PermSize=128m -XX:MaxPermSize=256m
>
> false
> once
> tests
> 1
>
>
> ${basedir}/src/test/resources/testng.xml
>
>
>
>
> ${basedir}/bootstrap
>
>
> ${basedir}/bootstrap/deploy/quartz-ra.rar/quartz-ra.jar
>
>
> plain
> false
>
>
>
>
> ...
>
> org.testng
> testng
> ${testng.version}
> jdk15
> test
>
>
>
> I'm getting this error when I run "mvn test". Not sure what the error is,
> and there is nothing on the web with this error message. I do have the
> jboss-embedded bootstrap directory setup for the project. Can someone
> translate this error for a maven noob? Thanks!
>
> ---
> T E S T S
> ---
> Running TestSuite
> org.apache.maven.surefire.booter.SurefireExecutionException: Cannot set
> option parallel with value tests; nested exception is java.lang.refl
> ect.InvocationTargetException: null; nested exception is
> org.apache.maven.surefire.util.NestedRuntimeException: Cannot set option
> parallel w
> ith value tests; nested exception is
> java.lang.reflect.InvocationTargetException: null
> org.apache.maven.surefire.util.NestedRuntimeException: Cannot set option
> parallel with value tests; nested exception is java.lang.reflect.In
> vocationTargetException: null
> java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
> org.apache.maven.surefire.testng.conf.AbstractDirectConfigurator$Setter.invoke(AbstractDirectConfigurator.java:87)
> at
> org.apache.maven.surefire.testng.conf.AbstractDirectConfigurator.configure(AbstractDirectConfigurator.java:58)
> at
> org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:73)
> at
> org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:92)
> at org.apache.maven.surefire.Surefire.run(Surefire.java:177)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
> org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:334)
> at
> org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:980)
> Caused by: java.lang.NullPointerException
> at org.testng.TestNG.setParallel(TestNG.java:345)
> ... 15 more
> [INFO]
>
> [ERROR] BUILD FAILURE
> [INFO]
>
> [INFO] There are test failures.
>
> Please refer to
> E:\workspace\testproject\seam-full\admin\admin-ejb\target\surefire-reports
> for the individual test results.
> [INFO]
>
> [DEBUG] Trace
> org.apache.maven.BuildFailureException: There are test failures.
>
> Please refer to
> E:\workspace\testproject\seam-full\admin\admin-ejb\target\surefire-reports
> for the individual test results.
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:579)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
> at
> org.apache.maven.life
RE: [SPAM] RE: Maven deploy project on a server different from remote repo server
So basically, I've to have maven installed on server2. do a mvn package with dependecy:copy-dependencies option in the pom file and it will copy the dependecies to whichever directory I specify on server2, correct? Shahzad Qureshi Systems Analyst/Programmer Applications Directorate, CIOB Environment Canada shahzad.qure...@ec.gc.ca -Original Message- From: Sommers, Elizabeth [mailto:somme...@pragmatics.com] Sent: Monday, February 02, 2009 1:38 PM To: Maven Users List Subject: RE: [SPAM] RE: Maven deploy project on a server different from remote repo server I am doing something like this using dependency:unpack-dependencies at the generate-resources phase. This way I don't have to think about a jar of jars or classpath. -Original Message- From: Brian E. Fox [mailto:bri...@reply.infinity.nu] Sent: Monday, February 02, 2009 12:19 PM To: Maven Users List Subject: [SPAM] RE: Maven deploy project on a server different from remote repo server Importance: Low You could use the assembly plugin to produce a bundle with the dependencies. Or you could patch something together with dependency:copy-dependencies and dependency:build-classpath -Original Message- From: Qureshi,Shahzad [Ontario] [mailto:shahzad.qure...@ec.gc.ca] Sent: Monday, February 02, 2009 11:26 AM To: users@maven.apache.org Subject: Maven deploy project on a server different from remote repo server Hi all, Here is the situation. Our internal remote repository is on server1 and my application that will require some of the jars sitting on the remote repo is on server2. Now my application is in jar format (created using maven) and is used by a web coldfusion based application. Now, do I simply figure out which dependencies my app requires and manually put them somewhere on server2 and use the classpath way of doing things to run this app or is there a better way to do this using Maven? I have been using Maven for a few months now and I understand how it works but I am not sure what to do in this deployment scenario that I mentioned above Any insights will be appreciated. Thank you Shahzad Qureshi Systems Analyst/Programmer Applications Directorate, CIOB Environment Canada shahzad.qure...@ec.gc.ca - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Bizarre test failures appear when adding a dependency
I have a maven project which defines a jar build type to be used as a jSecurity realm to be used with Sonatype Nexus. I finished developing the Realm, and went on to work on the additional metadata classes and encountered a problem I really can't explain. When I issue 'mvn test' all of my tests light up green. No problem. However, when I add the following dependency, all tests fail. org.sonatype.jsecurity plexus-delegating-realm 1.0.5 provided Note that I have not added a class which actually uses (or even does a package import) the dependency yet. $ mvn -v Maven version: 2.0.9 Java version: 1.5.0_16 OS name: "mac os x" version: "10.5.6" arch: "i386" Family: "unix" Please refer to /path/to/surefire-reports for the individual test results. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLife cycleExecutor.java:579) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle (DefaultLifecycleExecutor.java:499) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifec ycleExecutor.java:478) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFail ures(DefaultLifecycleExecutor.java:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(Defa ultLifecycleExecutor.java:291) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycle Executor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39 ) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl .java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoFailureException: There are test failures. Please refer to /path/to/surefire-reports for the individual test results. at org.apache.maven.plugin.surefire.SurefirePlugin.execute(SurefirePlugin.java: 530) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManage r.java:451) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLife cycleExecutor.java:558) ... 16 more The actual test error is: java.lang.NoClassDefFoundError: org/slf4j/LoggerFactory at org.apache.commons.logging.impl.SLF4JLogFactory.getInstance(SLF4JLogFactory. java:155) at org.apache.commons.logging.impl.SLF4JLogFactory.getInstance(SLF4JLogFactory. java:131) at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:685) at org.jsecurity.realm.AuthenticatingRealm.(AuthenticatingRealm.java:53 ) at edu.utexas.its.eis.infra.jsecurity.authn.TedAuthnRealmTest.authnSucceds(TedA uthnRealmTest.java:14) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39 ) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl .java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod. java:44) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.j ava:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.ja va:41) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.jav a:20) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28 ) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.jav a:73) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.jav a:46) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:180) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:41) at org.junit.runners.ParentRunner$1.evaluate(ParentRunner.java:173) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28 ) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) at org.junit.runners.ParentRunner.run(ParentRunner.java:220) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62 ) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(Ab stractDirectoryTestSuite.java:140) at or
Re: surefire with jboss embedded
So after getting past this I ran into some more errors and realized that I'm a little confused as to how maven+surefire+testng works with jboss embedded. All of the example projects I have seen make no mention of a tomcat installation, nor do they reference a tomcat/jboss deploy directory in the configuration of the surfire plugin. I also have noticed that all of the projects only have the "jboss-embedded" files in the ejb module, not the ear module, where you can integration test everything. Suppose I had a client of an EJB in my war and wanted to test that? Any direction on this is very much appreciated. Thanks -- View this message in context: http://www.nabble.com/surefire-with-jboss-embedded-tp21814900p21816476.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: surefire with jboss embedded
Hi Wayne. Thanks for your reply. I did notice that and removed it. I was also able to find this jira: http://jira.codehaus.org/browse/SUREFIRE-361 http://jira.codehaus.org/browse/SUREFIRE-361 Upgrading to testng 5.7 did the trick. Unfortunately it's like walking down path, and it revealed some other errors. Thanks Wayne Fay wrote: > >> >>-Xms128m -Xmx256m -XX:PermSize=128m -XX:MaxPermSize=256m >> >>false >>once >>tests >>1 > > I'm no Surefire expert, but I assume the values "tests" and > "false" cannot be set simultaneously. > > Wayne > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > > -- View this message in context: http://www.nabble.com/surefire-with-jboss-embedded-tp21814900p21816442.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Multimodule, multilevel project
On Tue, Feb 3, 2009 at 1:28 PM, Wayne Fay wrote: > In that case, I would probably use profiles (which were designed for > this purpose exactly) and structure the project as follows: > no dev1, dev2 directories > common has all files including config in the proper directory > (src/main/resources) > create "dev1" and "dev2" profiles with various values that are > filtered into the config files during the build, also the profiles > would set classifiers "dev1" and "dev2" or whatnot > > Then you would issue "mvn install -Pdev1" and it would build the code > with the dev1 values substituted into the config files, and "mvn > install -Pdev2" would do the same for dev2 values. > If you're not expecting to distribute and test both versions, I'd probably go this way; if you're expecting to treat both as a final artifact, then I'd probably go for sub-modules. I'm not sure what the config differences are intended for, so it's hard to speculate. -- Geoffrey Wiseman http://www.geoffreywiseman.ca/
Re: surefire with jboss embedded
> >-Xms128m -Xmx256m -XX:PermSize=128m -XX:MaxPermSize=256m > >false >once >tests >1 I'm no Surefire expert, but I assume the values "tests" and "false" cannot be set simultaneously. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Multimodule, multilevel project
> The source code must be common, dev1, dev2 etc. are different environments > differs only in configuration files. In that case, I would probably use profiles (which were designed for this purpose exactly) and structure the project as follows: no dev1, dev2 directories common has all files including config in the proper directory (src/main/resources) create "dev1" and "dev2" profiles with various values that are filtered into the config files during the build, also the profiles would set classifiers "dev1" and "dev2" or whatnot Then you would issue "mvn install -Pdev1" and it would build the code with the dev1 values substituted into the config files, and "mvn install -Pdev2" would do the same for dev2 values. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Multimodule, multilevel project
On Tue, Feb 3, 2009 at 5:34 AM, Czollli wrote: > The source code must be common, dev1, dev2 etc. are different environments > differs > only in configuration files. > That is the reason why I can't keep the standard structure... > I have configurations at the different levels too, which inherited from the > upper levels. > But if you have another idee... > Can you give me some hints how can I do that? Well, based on my limited understanding of your project, and my understanding of "the maven way", I'd probably structure it like this: parent (pom, multi-module; any common dependencies or dependency management, plugin management, etc.) - common (common source code; jar) - dev1 (depends on common; adds config; can overlay/flatten/shade jar if you like) - dev2 (same as dev1, but with its own config) Each of common, dev1 and dev2 would have their own pom, and be modules under the parent build. - Geoffrey -- Geoffrey Wiseman http://www.geoffreywiseman.ca/
Deployment of non-Maven Files into Maven Repository
We have a project that produces about a dozen separate JAR files. These JARS are in turn used by a project that is built with Maven. I can do the deployment like this: $ mvn deploy:deploy-file -DrepositoryId="snapshot" \ -Durl="http://aladdin.solbright.com:8082/nexus/content/repositories/snapshots/"; \ -Dfile="_build/tmp/api-lib/adbilling.jar" \ -DgroupId="com.solbright" -DartifactId="adbilling" \ -Dversion="1.0-SNAPSHOT" \ -Dpackaging="jar" -DgeneratePom="true" For each one. That works. It goes into my Maven repository, and my Maven project can do the download. However, I am using Hudson which makes it a bit difficult to use a shell script (not impossible, but difficult). It would be nicer if I could use a pom.xml to set all of these settings. Actually, what I really want is a way in a POM file where I can specify all of these files at once. That is, specify in the pom all of the files that need to be deployed. Is that possible without specifying multiple POM files? -- David Weintraub qazw...@gmail.com - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
surefire with jboss embedded
project structure:
main pom
\-ear
\-ejb
\-war
I have the ejb pom set up to run surfire, like so:
org.apache.maven.plugins
maven-surefire-plugin
${surefire.version}
user.timezone
Etc/UTC
java.protocol.handler.pkgs
org.jboss.virtual.protocol
sun.lang.ClassLoader.allowArraySyntax
true
-Xms128m -Xmx256m -XX:PermSize=128m -XX:MaxPermSize=256m
false
once
tests
1
${basedir}/src/test/resources/testng.xml
${basedir}/bootstrap
${basedir}/bootstrap/deploy/quartz-ra.rar/quartz-ra.jar
plain
false
I'm getting this error when I run "mvn test". Not sure what the error is,
and there is nothing on the web with this error message. I do have the
jboss-embedded bootstrap directory setup for the project. Can someone
translate this error for a maven noob? Thanks!
---
T E S T S
---
Running TestSuite
org.apache.maven.surefire.booter.SurefireExecutionException: Cannot set
option parallel with value tests; nested exception is java.lang.refl
ect.InvocationTargetException: null; nested exception is
org.apache.maven.surefire.util.NestedRuntimeException: Cannot set option
parallel w
ith value tests; nested exception is
java.lang.reflect.InvocationTargetException: null
org.apache.maven.surefire.util.NestedRuntimeException: Cannot set option
parallel with value tests; nested exception is java.lang.reflect.In
vocationTargetException: null
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.maven.surefire.testng.conf.AbstractDirectConfigurator$Setter.invoke(AbstractDirectConfigurator.java:87)
at
org.apache.maven.surefire.testng.conf.AbstractDirectConfigurator.configure(AbstractDirectConfigurator.java:58)
at
org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:73)
at
org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:92)
at org.apache.maven.surefire.Surefire.run(Surefire.java:177)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:334)
at
org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:980)
Caused by: java.lang.NullPointerException
at org.testng.TestNG.setParallel(TestNG.java:345)
... 15 more
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] There are test failures.
Please refer to
E:\workspace\testproject\seam-full\admin\admin-ejb\target\surefire-reports
for the individual test results.
[INFO]
[DEBUG] Trace
org.apache.maven.BuildFailureException: There are test failures.
Please refer to
E:\workspace\testproject\seam-full\admin\admin-ejb\target\surefire-reports
for the individual test results.
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:579)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
at sun.reflect.NativeMethodAccessorImpl.invoke
[aspectj-maven-plugin] problem
hi all, i'm trying to compile my maven project but i have this error each time i try: at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) 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:597) 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.codehaus.mojo.aspectj.CompilationFailedException: Compiler errors : i'm pretty sur i have configurated my pom to use the maven aspectJ plagin: org.codehaus.mojo aspectj-maven-plugin com.proj.ws WsCommon org.springframework spring-aspects 1.5 true compile have any one an idea about what this mean or how to get over it? -- View this message in context: http://www.nabble.com/-aspectj-maven-plugin--problem-tp21814110p21814110.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Re-use global distributionManagement
I just figured that when you declare node what you refer there is by default something in maven repo. it seems like defining a company-parent pom.xml with packaging: pom would be a solution. As long as this pom is deployed to maven repo other projects should have no trouble resolving it and inheriting from it... Any thoughts, insights appreciated... Regards, -Guillaume From: Jeudy, Guillaume [mailto:gje...@teksystems.com] Sent: Tue 03/02/2009 11:12 AM To: users@maven.apache.org Subject: Re-use global distributionManagement Hi maven users, I have distributionManagement information that is common to all projects at my company. Do you know of any tricks to ensure all projects share the same distributionManagement info? I don't want to use pom hierarchy if possible because that would mean I would need a master top-level pom that sits somewhere in SVN that everyone need to checkout for it to be resolved. Ideally I would like to inherit pom distributionManagement from a dependency that lives in the repo. Is it possible to do this? This way no matter from where you are building a proj you can inherit firmwide pom settings as long as the pom artifact is stored in the company repo. Thanks, -Guillaume This electronic mail (including any attachments) may contain information that is privileged, confidential, and/or otherwise protected from disclosure to anyone other than its intended recipient(s). Any dissemination or use of this electronic email or its contents (including any attachments) by persons other than the intended recipient(s) is strictly prohibited. If you have received this message in error, please notify us immediately by reply email so that we may correct our internal records. Please then delete the original message (including any attachments) in its entirety. Thank you. This electronic mail (including any attachments) may contain information that is privileged, confidential, and/or otherwise protected from disclosure to anyone other than its intended recipient(s). Any dissemination or use of this electronic email or its contents (including any attachments) by persons other than the intended recipient(s) is strictly prohibited. If you have received this message in error, please notify us immediately by reply email so that we may correct our internal records. Please then delete the original message (including any attachments) in its entirety. Thank you.
Re-use global distributionManagement
Hi maven users, I have distributionManagement information that is common to all projects at my company. Do you know of any tricks to ensure all projects share the same distributionManagement info? I don't want to use pom hierarchy if possible because that would mean I would need a master top-level pom that sits somewhere in SVN that everyone need to checkout for it to be resolved. Ideally I would like to inherit pom distributionManagement from a dependency that lives in the repo. Is it possible to do this? This way no matter from where you are building a proj you can inherit firmwide pom settings as long as the pom artifact is stored in the company repo. Thanks, -Guillaume This electronic mail (including any attachments) may contain information that is privileged, confidential, and/or otherwise protected from disclosure to anyone other than its intended recipient(s). Any dissemination or use of this electronic email or its contents (including any attachments) by persons other than the intended recipient(s) is strictly prohibited. If you have received this message in error, please notify us immediately by reply email so that we may correct our internal records. Please then delete the original message (including any attachments) in its entirety. Thank you.
Re: maven with jgoodies
Norbert, he's better off with the .form files in src/java IntelliJ expects them there and does it's post-processing of the .class files on the basis that the .form files are beside the .java files. The .form files should *not* end up on the classpath, but are to be post-processed into the .class files Crazy... but true -Stephen 2009/2/3 Dirk Olmes : > Norbert Lazzeri wrote: >> well this is where intellij put them. >> >> im fine with this since each form-file belongs exactly to one java file. >> they are tied to each other and putting them to src clarifies that fact. >> i also put hibernate-mappings into src. >> >> all other resources i put into src/main/resources >> >> however this had no impact on the build so why do you ask? > > Because the maven-resources-plugin will only pick up resources from the > default resource path unless configured otherwise. So if you leave your > resources lying around in src/main/java don't expect them in the final > jar if you build from scratch using Maven. I'm sure the IDE will pick up > resources from the source dir and copy them to target/classes but expect > trouble when building with pure Maven. > > You could configure your pom to include src/main/java as resource dir, > though, just make sure you exclude your .java files in that case. > > -dirk > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven with jgoodies
Norbert Lazzeri wrote: > well this is where intellij put them. > > im fine with this since each form-file belongs exactly to one java file. > they are tied to each other and putting them to src clarifies that fact. > i also put hibernate-mappings into src. > > all other resources i put into src/main/resources > > however this had no impact on the build so why do you ask? Because the maven-resources-plugin will only pick up resources from the default resource path unless configured otherwise. So if you leave your resources lying around in src/main/java don't expect them in the final jar if you build from scratch using Maven. I'm sure the IDE will pick up resources from the source dir and copy them to target/classes but expect trouble when building with pure Maven. You could configure your pom to include src/main/java as resource dir, though, just make sure you exclude your .java files in that case. -dirk - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven with jgoodies
well this is where intellij put them. im fine with this since each form-file belongs exactly to one java file. they are tied to each other and putting them to src clarifies that fact. i also put hibernate-mappings into src. all other resources i put into src/main/resources however this had no impact on the build so why do you ask? Dirk Olmes schrieb: Norbert Lazzeri wrote: hi, ive used intellij to write a swing-application. i also used the jgoodies plugin. for each form i created, the builder created 2 files: TheClass.form (xml-data), TheClass.java Where do you put the .form files? In Maven philosophy they're application resources and belong into src/main/resources, not src/main/java. -dirk - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven with jgoodies
awesome! didnt think it would be this easy. you saved my day. thx a lot! Stephen Connolly schrieb: http://mojo.codehaus.org/ideauidesigner-maven-plugin/ 2009/2/3 Norbert Lazzeri : i forgoth to say that its a spring-application, so the swing container is responsible to initialize the gui-components.. Norbert Lazzeri schrieb: hi, ive used intellij to write a swing-application. i also used the jgoodies plugin. for each form i created, the builder created 2 files: TheClass.form (xml-data), TheClass.java now running the application under intellij works fine (just klicking the run button). but when i package the project with maven i get a nullpointer-exception when it comes to initialize the gui-components. it looks like the application isnt aware of the *.form files containing information about the gui. until now i allways wrote swing apps by hand putting all the code into one java file for each form so im not sure about this: do i have to do further configuration than just adding the jgoodie - jars to the classpath? i just added a dependency to the pom.xml, configured the dependency plugin to copy all jars into the target directory and set the classpath in the jar-plugin. ill also ask for help in the jgoodie - mailing list but i wanted also to ask you guys if its a maven related thing like missing a setting cheers - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven with jgoodies
Norbert Lazzeri wrote: > hi, > > ive used intellij to write a swing-application. i also used the jgoodies > plugin. > > for each form i created, the builder created 2 files: TheClass.form > (xml-data), TheClass.java Where do you put the .form files? In Maven philosophy they're application resources and belong into src/main/resources, not src/main/java. -dirk - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven with jgoodies
http://mojo.codehaus.org/ideauidesigner-maven-plugin/ 2009/2/3 Norbert Lazzeri : > i forgoth to say that its a spring-application, so the swing container is > responsible to initialize the gui-components.. > > Norbert Lazzeri schrieb: >> >> hi, >> >> ive used intellij to write a swing-application. i also used the jgoodies >> plugin. >> >> for each form i created, the builder created 2 files: TheClass.form >> (xml-data), TheClass.java >> >> now running the application under intellij works fine (just klicking the >> run button). but when i package the project with maven i get a >> nullpointer-exception when it comes to initialize the gui-components. >> >> it looks like the application isnt aware of the *.form files containing >> information about the gui. >> >> until now i allways wrote swing apps by hand putting all the code into one >> java file for each form so im not sure about this: do i have to do further >> configuration than just adding the jgoodie - jars to the classpath? >> >> i just added a dependency to the pom.xml, configured the dependency plugin >> to copy all jars into the target directory and set the classpath in the >> jar-plugin. >> >> >> ill also ask for help in the jgoodie - mailing list but i wanted also to >> ask you guys if its a maven related thing like missing a setting >> >> >> cheers >> >> - >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven with jgoodies
i forgoth to say that its a spring-application, so the swing container is responsible to initialize the gui-components.. Norbert Lazzeri schrieb: hi, ive used intellij to write a swing-application. i also used the jgoodies plugin. for each form i created, the builder created 2 files: TheClass.form (xml-data), TheClass.java now running the application under intellij works fine (just klicking the run button). but when i package the project with maven i get a nullpointer-exception when it comes to initialize the gui-components. it looks like the application isnt aware of the *.form files containing information about the gui. until now i allways wrote swing apps by hand putting all the code into one java file for each form so im not sure about this: do i have to do further configuration than just adding the jgoodie - jars to the classpath? i just added a dependency to the pom.xml, configured the dependency plugin to copy all jars into the target directory and set the classpath in the jar-plugin. ill also ask for help in the jgoodie - mailing list but i wanted also to ask you guys if its a maven related thing like missing a setting cheers - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
maven with jgoodies
hi, ive used intellij to write a swing-application. i also used the jgoodies plugin. for each form i created, the builder created 2 files: TheClass.form (xml-data), TheClass.java now running the application under intellij works fine (just klicking the run button). but when i package the project with maven i get a nullpointer-exception when it comes to initialize the gui-components. it looks like the application isnt aware of the *.form files containing information about the gui. until now i allways wrote swing apps by hand putting all the code into one java file for each form so im not sure about this: do i have to do further configuration than just adding the jgoodie - jars to the classpath? i just added a dependency to the pom.xml, configured the dependency plugin to copy all jars into the target directory and set the classpath in the jar-plugin. ill also ask for help in the jgoodie - mailing list but i wanted also to ask you guys if its a maven related thing like missing a setting cheers - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Release 2.0.10 will we ever see it?
Cheers thanks for the info. brettporter wrote: > > > On 03/02/2009, at 8:13 PM, PaulG wrote: > >> >> Will Maven 2.0.10 ever be released? > > Brian has rolled another RC that should be published shortly. It's > about ready to go. > >> >> >> If not when can we expect Maven 2.1? I can not push out Milestone >> releases >> to our dev team. > > A new milestone will be out within the week circumstances permitting, > and the issues in JIRA are locked down barring any regressions - it > should follow very soon. > > Cheers, > Brett > > -- > Brett Porter > br...@apache.org > http://blogs.exist.com/bporter/ > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > > -- View this message in context: http://www.nabble.com/Release-2.0.10-will-we-ever-see-it--tp21806234p21809428.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: 5 minute guide - Incorrect documentation/documentation improvement?
>>I recently gave a talk on Maven to the Java London Users group. Which I attended and found to be very good :-) -Original Message- From: Martijn Verburg [mailto:martijnverb...@gmail.com] Sent: 02 February 2009 10:37 To: users@maven.apache.org Subject: 5 minute guide - Incorrect documentation/documentation improvement? Hi all, I recently gave a talk on Maven to the Java London Users group. One small thing I noticed while researching is that the instructions at: http://maven.apache.org/guides/getting-started/maven-in-five-minutes.htm l talk about using mvn archetype:create Since that is now deprecated in favour of archetype:generate, should the documentation be updated to use the non deprecated project creation method? Cheers, Martijn - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: 5 minute guide - Incorrect documentation/documentation improvement?
Yeah I'm already poking about the ear plugin code so I'll see if I can find the svn for the main site and make a doc patch. Sent while on the move On 3 Feb 2009, at 00:29, Barrie Treloar wrote: On Tue, Feb 3, 2009 at 10:34 AM, Wayne Fay wrote: Since that is now deprecated in favour of archetype:generate, should the documentation be updated to use the non deprecated project creation method? All Maven bugs, including those in documentation, go in JIRA... And if you checkout the code and attach a patch, it is more likely to get fixed :) - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: 5 minute guide - Incorrect documentation/documentation improvement?
Yep aware of that, just wanted opinion so on whether it was a bug or my misunderstanding. I'll Jira it :) Sent while on the move On 3 Feb 2009, at 00:04, Wayne Fay wrote: Since that is now deprecated in favour of archetype:generate, should the documentation be updated to use the non deprecated project creation method? All Maven bugs, including those in documentation, go in JIRA... Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Multimodule, multilevel project
Wayne Fay wrote: > >> dev1 and dev2 should contain in their target dir the jar file, generated >> from src. > > You could do this... but why would you possibly want to, other than > "don't want to change structure of old codebase"? Move the source code > for dev1 to dev1/src/main/java, and the source code for dev2 to > dev2/src/main/java. > > The source code must be common, dev1, dev2 etc. are different environments differs only in configuration files. That is the reason why I can't keep the standard structure... I have configurations at the different levels too, which inherited from the upper levels. But if you have another idee... Can you give me some hints how can I do that? Regards Czollli -- View this message in context: http://www.nabble.com/Multimodule%2C-multilevel-project-tp21806770p21807333.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Multimodule, multilevel project
> dev1 and dev2 should contain in their target dir the jar file, generated > from src. You could do this... but why would you possibly want to, other than "don't want to change structure of old codebase"? Move the source code for dev1 to dev1/src/main/java, and the source code for dev2 to dev2/src/main/java. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Release 2.0.10 will we ever see it?
On 03/02/2009, at 8:13 PM, PaulG wrote: Will Maven 2.0.10 ever be released? Brian has rolled another RC that should be published shortly. It's about ready to go. If not when can we expect Maven 2.1? I can not push out Milestone releases to our dev team. A new milestone will be out within the week circumstances permitting, and the issues in JIRA are locked down barring any regressions - it should follow very soon. Cheers, Brett -- Brett Porter br...@apache.org http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Multimodule, multilevel project
Hello, The main task would be to generate jar files in the leaf projects: main (pom.xml) | | default (contains src and pom.xml) | |___ dev (only pom.xml) | |_ dev1 (only pom.xml) | |_ dev2 (only pom.xml) dev1 and dev2 should contain in their target dir the jar file, generated from src. Did anybody already meet this problem? Can anybody suggest a solution? Thanks a lot! Czollli -- View this message in context: http://www.nabble.com/Multimodule%2C-multilevel-project-tp21806770p21806770.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Release 2.0.10 will we ever see it?
Will Maven 2.0.10 ever be released? If not when can we expect Maven 2.1? I can not push out Milestone releases to our dev team. Cheers Paul -- View this message in context: http://n2.nabble.com/Release-2.0.10-will-we-ever-see-it--tp2262340p2262340.html Sent from the maven users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
