Configure FROM mailbox
Hi! I configured file plexus.xml (continuum 1.1), and also section "Mail". But while starting continuum, following line are printed into log: org.codehaus.plexus.notification.notifier.Notifier:mail - The from mailbox is not configured, will use the nag email address from the project. So, how can I set FROM mailbox and where? Thanks
Multimodule distribution
Hello, guys! We have a project consisting of a main module (we call it core) and several configurable plugin modules (we call it component). By the application design each module is highly customizable and depends on one or more configuration files. When the application starts the "conf" folder is scanned and application configuration is constructed from all conf-files located in that folder. Depending on the usage scenario several combinations of configuration files may be used The basic aim we want to achieve is: 1) Have all possible configuration files stored in some folder of a module, e.g. for component A we have Aconf1.xml, Aconf2.xml and for component B Bconf1.xml and Bconf2.xml 2) For each target usage scenario we want to predefine a set of configuration files in a pom file that will build a distribution. E.g. for Scenario1 we should use Aconf1.xml and Bconf2.xml, but for Scenario2 we should use Aconf2.xml and Bconf1.xml 3) The resulting layout should look like ./lib - all *.jar files (core and components used) and ./conf - subset of configuration files specified in a distribution pom file. Can you suggest how this goal can be achieved with maven and distribution or assembly plugin? -- View this message in context: http://maven.40175.n5.nabble.com/Multimodule-distribution-tp4574067p4574067.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 distribution
Thanks for quick answers! Actually we want the exactly solution you suggest: one pom - one distribution package. Packing a config in a jar file is not acceptable because configuration can be altered by the end-user and in case of component update he will loose all the modifications. Solution with packages is exactly what we want with one exception: assembly descriptor should contain not only the component jar, but some configs out-of-the jar. The actual problem that we cannot solve is: how to publish several artifacts for a module and during the distribution phase pull the arbitrary subset of component's artifacts. i.e. the structure we want to achieve is: Root \---JARS | \---Core | \---Component A (Deps: Core; Aconf1.xml Aconf2.xml) | \---Component B (Deps: Core) | \--- ... \---PACKAGES \--- PACKAGE 1 (Deps: Component A (Aconf1.xml), Component B) \--- PACKAGE 2 (Deps: Component A (Aconf2.xml), Component B) \--- ... The most close soultion that we saw is to place config files in main/resources/conf directory and then unpack them from sources with assembly plugin, but it will unpack the whole dir. Is there a way to filter files according to rules in a pom? Or probably there is a more clean way to do it? -- View this message in context: http://maven.40175.n5.nabble.com/Multimodule-distribution-tp4574067p4575146.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 distribution
Thanks for quick answers! Actually we want the exactly solution you suggest: one pom - one distribution package. Packing a config in a jar file is not acceptable because configuration can be altered by the end-user and in case of component update he will loose all the modifications. Solution with packages is exactly what we want with one exception: assembly descriptor should contain not only the component jar, but some configs out-of-the jar. The actual problem that we cannot solve is: how to publish several artifacts for a module and during the distribution phase pull the arbitrary subset of component's artifacts. i.e. the structure we want to achieve is: Root \---JARS | \---Core | \---Component A (Deps: Core; Aconf1.xml Aconf2.xml) | \---Component B (Deps: Core) | \--- ... \---PACKAGES \--- PACKAGE 1 (Deps: Component A (Aconf1.xml), Component B) \--- PACKAGE 2 (Deps: Component A (Aconf2.xml), Component B) \--- ... The most close soultion that we saw is to place config files in main/resources/conf directory and then unpack them from sources with assembly plugin, but it will unpack the whole dir. Is there a way to filter files according to rules in a pom? Or probably there is a more clean way to do it? -- View this message in context: http://maven.40175.n5.nabble.com/Multimodule-distribution-tp4574067p4575148.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
Using Maven without an intyernet connection
Hi, I am integrating several open source projects into an application and some of these projects are built with Maven, which I have not used to date. I have read the FAQs etc. but I could not find a mention of being able to do a Maven build on a machine that is not directly connected to the Internet or whether such a connection is a prerequisite. My situation is that my development machine is not connected but I do need to be able to build some of these projects. Is there some way that Maven supports this "disconnected" build? Thanks. Best wishes, Ivan.
RE: Using Maven without an internet connection
Dear All, I am very glad to hear that Maven has taken into account the disconnected build use case. Thank you all very much for your insights and all the good references too. This has certainly set me off in the right direction. Best wishes, Ivan -Original Message- From: Eric Redmond [mailto:[EMAIL PROTECTED] Sent: Monday, March 19, 2007 8:01 AM To: Maven Users List Subject: Re: Using Maven without an intyernet connection Yes, do not wget the repository: http://maven.apache.org/community.html under "Being a Good Maven Citizen" Eric On 3/19/07, Thierry Lach <[EMAIL PROTECTED]> wrote: > > Yep - rsync will definitely work better than wget. > > On 3/19/07, Wendy Smoak <[EMAIL PROTECTED]> wrote: > > > > On 3/19/07, Paul Gier <[EMAIL PROTECTED]> wrote: > > > > > What's the easiest way to download the whole central repository? Is > > > there a maven plugin to do that? Or is there some way to get a zip of > > > the whole thing? > > > > See 'Creating your own mirror' at the bottom of this page: > > > > http://maven.apache.org/guides/mini/guide-mirror-settings.html > > > > -- > > Wendy > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > -- Eric Redmond http://codehaus.org/~eredmond - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Download some artifact using command line mvn tool
Is it possible to download some artifact (groupId, artifactId and version are known) using the mvn tool? It is quite inconvenient to browse repositories manually. Something like this: mvn dependency:download -DartifactId=junit -DgroupId=junit -Dversion=3.8.1 -- WBR, Ivan S. Dubrov signature.asc Description: OpenPGP digital signature
provided dependency packaged into war
Hello, I am packaging a war archive and list dependency in pom file: javax.servlet jsp-api 2.0 provided the problem is that jsp-api-2.0.jar (and also servlet-api-2.4.jar) get packaged into WEB-INF/lib even though that they are always mentioned as provided dependencies. Our project depends on multiple other our projects. One of them is another war, which gets merged into our war. Other are simple jars. jsp-api is mentioned as dependency in some of them, but always as "provided". My intention is to package only our jars into WEB-INF/lib. I want to keep the third party ones in server lib. The primary project is called non_combustion. It depends on our cms_classes and cms_web projects and some others, such as dsutil_web. These depend on many other libraries, especially spring and related. Rough structure: non_combustion (war) jsp-api (provided) dsutil_web (jar) (compile) jsp-api (provided) .. cms_web (war) (compile) depends on jsp-api (provided) cms_classes (jar) (compile) .. .. I did proper clean and install of all these project into local repository. When I do mvn package -X on non_combustion I get a war file with jsp-api in WEB-INF/lib. However other libraries (such as spring) are not packaged (just as I wanted). If I search the debug output for the package command for jsp-api I get the parts below. From them it is clear that jsp-api is everywhere mentioned as provided, but in the final step it is included in the WEB-INF/lib. Could anyone help? Is this a bug? If some additional info is required I can send it (the log below is 180KB long). I am just starting with maven so I ask here first before submitting a bug report or other. I am using maven 2.0.4 installed recently. Thanks for any answers, Ivan ... [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [DEBUG] sk.digitalsystems:non_combustion:war:1.1.2.0-SNAPSHOT (selected for null) [DEBUG] Skipping disabled repository central [DEBUG] perobs_spring: using locally installed snapshot [DEBUG] sk.digitalsystems:perobs_spring:jar:1.1.4.0-SNAPSHOT:compile (selected for compile) [DEBUG] Skipping disabled repository central [DEBUG] perobs: using locally installed snapshot [DEBUG] sk.digitalsystems:perobs:jar:1.1.9.0-SNAPSHOT:compile (selected for compile) [DEBUG] Skipping disabled repository central [DEBUG] dsutil: using locally installed snapshot [DEBUG] sk.digitalsystems:dsutil:jar:1.1.7.0-SNAPSHOT:compile (selected for compile) [DEBUG] Skipping disabled repository central [DEBUG] cms_classes: using locally installed snapshot [DEBUG] sk.digitalsystems:cms_classes:jar:1.1.0.0-SNAPSHOT:compile (selected for compile) [DEBUG] Skipping disabled repository central [DEBUG] dsutil_web: using locally installed snapshot [DEBUG] sk.digitalsystems:dsutil_web:jar:1.1.2.0-SNAPSHOT:compile (selected for compile) [DEBUG] junit:junit:jar:3.8.1:test (selected for test) [DEBUG] javax.servlet:jsp-api:jar:2.0:provided (selected for provided) [DEBUG] javax.servlet:servlet-api:jar:2.4:provided (selected for provided) [DEBUG] Skipping disabled repository central [DEBUG] cms: using locally installed snapshot [DEBUG] sk.digitalsystems:cms:war:1.1.2.0-SNAPSHOT:compile (selected for compile) [DEBUG] Retrieving parent-POM: org.acegisecurity:acegi-security-parent::1.0.3 for project: null:acegi-security:jar:1.0.3 from the repository. [DEBUG] org.acegisecurity:acegi-security:jar:1.0.3:provided (selected for provided) [DEBUG] Retrieving parent-POM: org.springframework:spring-parent::1.2.8 for project: null:spring-support:jar:1.2.8 from the repository. [DEBUG] org.springframework:spring-support:jar:1.2.8:provided (selected for provided) [DEBUG] commons-codec:commons-codec:jar:1.3:provided (selected for provided) [DEBUG] commons-logging:commons-logging:jar:1.0.4:provided (selected for provided) [DEBUG] log4j:log4j:jar:1.2.9:provided (selected for provided) [DEBUG] commons-lang:commons-lang:jar:2.1:provided (selected for provided) [DEBUG] commons-collections:commons-collections:jar:3.1:provided (selected for provided) [DEBUG] Retrieving parent-POM: org.springframework:spring-parent::1.2.8 for project: null:spring-remoting:jar:1.2.8 from the repository. [DEBUG] org.springframework:spring-remoting:jar:1.2.8:provided (selected for provided) [DEBUG] Retrieving parent-POM: org.springframework:spring-parent::1.2.8 for project: null:spring-webmvc:jar:1.2.8 from the repository. [DEBUG] org.springframework:spring-webmvc:jar:1.2.8:provided (selected for provided) [DEBUG] Retrieving parent-POM: org.springframework:spring-parent::1.2.8 for project: null:spring-web:jar:1.2.8 from the repository. [DEBUG] org.springframework:spring-web:jar:1.2.8:provided (selected for provided) [DEBUG] Retrieving
Re: provided dependency packaged into war
Thanks for help.. it was my mistake. provided works also fine. I have quite a complicated structure of projects and I was referencing wrong versions already stored in local repository. But the debug output confused me a bit.. On Wed, Jan 31, 2007 at 08:22:32AM +0100, [EMAIL PROTECTED] wrote: > Hi > > Don't use provided - Use : > > true > > > This will add an entry in the claspath section of the meta-inf.xml file, but > not add it to the web-inf/libdirectory > > Hermod > > -Original Message- > From: Ivan Strohner [mailto:[EMAIL PROTECTED] > Sent: Tuesday, January 30, 2007 6:15 PM > To: users@maven.apache.org > Subject: provided dependency packaged into war > > > Hello, > > I am packaging a war archive and list dependency in pom file: > > javax.servlet > jsp-api > 2.0 > provided > > > the problem is that jsp-api-2.0.jar (and also servlet-api-2.4.jar) get > packaged into WEB-INF/lib even though that they are always mentioned as > provided dependencies. > > Our project depends on multiple other our projects. One of them is another > war, which gets merged into our war. Other are simple jars. jsp-api is > mentioned as dependency in some of them, but always as "provided". > > My intention is to package only our jars into WEB-INF/lib. I want to keep the > third party ones in server lib. The primary project is called non_combustion. > It depends on our cms_classes and cms_web projects and some others, such as > dsutil_web. These depend on many other libraries, especially spring and > related. > > Rough structure: > > non_combustion (war) > jsp-api (provided) > dsutil_web (jar) (compile) > jsp-api (provided) > .. > cms_web (war) (compile) > depends on jsp-api (provided) > cms_classes (jar) (compile) > .. > .. > > I did proper clean and install of all these project into local repository. > When I do mvn package -X on non_combustion I get a war file with jsp-api > in WEB-INF/lib. However other libraries (such as spring) are not packaged > (just as I wanted). > > If I search the debug output for the package command for jsp-api I get the > parts below. From them it is clear that jsp-api is everywhere mentioned as > provided, but in the final step it is included in the WEB-INF/lib. > > Could anyone help? Is this a bug? If some additional info is required I can > send it (the log below is 180KB long). I am just starting with maven so I ask > here first before submitting a bug report or other. > > I am using maven 2.0.4 installed recently. > > Thanks for any answers, > Ivan > > > ... > [INFO] [resources:resources] > [INFO] Using default encoding to copy filtered resources. > [DEBUG] sk.digitalsystems:non_combustion:war:1.1.2.0-SNAPSHOT (selected for > null) > [DEBUG] Skipping disabled repository central > [DEBUG] perobs_spring: using locally installed snapshot > [DEBUG] sk.digitalsystems:perobs_spring:jar:1.1.4.0-SNAPSHOT:compile > (selected for compile) > [DEBUG] Skipping disabled repository central > [DEBUG] perobs: using locally installed snapshot > [DEBUG] sk.digitalsystems:perobs:jar:1.1.9.0-SNAPSHOT:compile (selected > for compile) > [DEBUG] Skipping disabled repository central > [DEBUG] dsutil: using locally installed snapshot > [DEBUG] sk.digitalsystems:dsutil:jar:1.1.7.0-SNAPSHOT:compile (selected > for compile) > [DEBUG] Skipping disabled repository central > [DEBUG] cms_classes: using locally installed snapshot > [DEBUG] sk.digitalsystems:cms_classes:jar:1.1.0.0-SNAPSHOT:compile > (selected for compile) > [DEBUG] Skipping disabled repository central > [DEBUG] dsutil_web: using locally installed snapshot > [DEBUG] sk.digitalsystems:dsutil_web:jar:1.1.2.0-SNAPSHOT:compile > (selected for compile) > [DEBUG] junit:junit:jar:3.8.1:test (selected for test) > [DEBUG] javax.servlet:jsp-api:jar:2.0:provided (selected for provided) > [DEBUG] javax.servlet:servlet-api:jar:2.4:provided (selected for provided) > [DEBUG] Skipping disabled repository central > [DEBUG] cms: using locally installed snapshot > [DEBUG] sk.digitalsystems:cms:war:1.1.2.0-SNAPSHOT:compile (selected for > compile) > [DEBUG] Retrieving parent-POM: org.acegisecurity:acegi-security-parent::1.0.3 > for project: null:acegi-security:jar:1.0.3 from the repository. > [DEBUG] org.acegisecurity:acegi-security:jar:1.0.3:provided (selected for > provided) > [DEBUG] Retrieving parent-POM: org.springframework:spring-parent::1.2.8 for > project: null:spring-support:jar:1.2.8 from the reposito
I would like to host a mirror of the maven repository. How can I do it?
I would like to host a mirror of the maven repository. How can I do it?
release:perform fails because of bad working directory
Hi, I have a problem releasing a multi-module project with the following structure: \---project-master | pom.xml +---project-api | pom.xml \---project-app pom.xml release:prepare creates the tag under http://svn_host/my/project/tags/project-master-1.0.3/project-master release:perform checkouts the tagged sources under target/checkout/project-mster, but release:perform complains that it cannot find the pom.xml . The problem is that the working directory for the deploy goals is target/checkout but should be target/checkout/project-master : [INFO] Checking out the project to perform the release ... [INFO] Executing: cmd.exe /X /C "svn --non-interactive checkout http://svn_host/my/project/tags/project-master-1.0.3 C:\workspace\co\svn\project-1.0.x\project-master\target\checkout" [INFO] Working directory: C:\workspace\co\svn\project\project-master\target [INFO] Executing goals 'deploy'... [WARNING] Maven will be executed in interactive mode, but no input stream has been configured for this MavenInvoker inst ance. [INFO] [INFO] Scanning for projects... [INFO] [INFO] [INFO] [INFO] Building Maven Default Project [INFO] [INFO]task-segment: [deploy] [INFO] [INFO] [INFO] [INFO] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] [INFO] [INFO] Cannot execute mojo: resources. It requires a project with an existing pom.xml, but the build is not using Is there any configuration that we missed in order to perform the release correctly? Your help is highly appreciated. -- Ivan BOGOUCHEV
RE: deploy goal fails
Hi, Did you find a solution for this? I'm having the same problem: Error deploying artifact: C:\projects\Portal2\code\workflow\web\target\classes (Access is denied) The point is that it only fails when adding a classifier to the war. mvn install OTOH works fine (I also get the : altDeploymentRepository = null ) Regards Ivan John Coleman-6 wrote: > > It's strange because this is a mapped drive over a local disk, and the > folder exists and contains classes. But this looks somewhat like a > network permissions problem? > > Other deployments from this drive work fine. > > John > > -Original Message- > From: Wayne Fay [mailto:[EMAIL PROTECTED] > Sent: 21 August 2007 16:53 > To: Maven Users List > Subject: Re: deploy goal fails > > Caused by: java.io.FileNotFoundException: > Z:\jcoleman\projects\eTraderII\trunk\target\classes (Access is denied) >at java.io.FileInputStream.open(Native Method) > > That's your root problem. I can't tell you why its happening or what > it means, but that's the reason your deploy is failing. > > Wayne > > On 8/21/07, John Coleman <[EMAIL PROTECTED]> > wrote: >> I have used a classifier on the war plugin, and it looks like this >> spoils the deploy, but the error message doesn't seem related. >> >> >> >> Does anyone understand this error pls? >> >> >> >> TIA >> >> John >> >> >> >> >> >> [deploy:deploy] >> >> altDeploymentRepository = null >> >> [INFO]Retrieving previous build number from repo >> >> [DEBUG]repository metadata for: 'snapshot >> com.eurobase:eTraderII:1.2-SNAPSHOT' could not be found on repository: >> repo >> >> [INFO]Error for project: eTraderII Project (during deploy) >> >> > [INFO]-- >> -- >> >> [INFO]Error deploying artifact: >> Z:\jcoleman\projects\eTraderII\trunk\target\classes (Access is denied) >> >> > [INFO]-- >> -- >> >> [DEBUG]Trace >> >> org.apache.maven.lifecycle.LifecycleExecutionException: Error > deploying >> artifact: Z:\jcoleman\projects\eTraderII\trunk\target\classes (Access > is >> denied) >> >> >> >> at >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default >> LifecycleExecutor.java:635) >> >> at >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec >> ycle(DefaultLifecycleExecutor.java:551) >> >> at >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL >> ifecycleExecutor.java:530) >> >> at >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle >> Failures(DefaultLifecycleExecutor.java:309) >> >> at >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( >> DefaultLifecycleExecutor.java:276) >> >> at >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec >> ycleExecutor.java:143) >> >> at >> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:393) >> >> at > org.apache.maven.DefaultMaven.execute(DefaultMaven.java:182) >> >> at >> > org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:760) >> >> at >> > org.codehaus.mevenide.netbeans.execute.MavenJavaExecutor.run(MavenJavaEx >> ecutor.java:257) >> >> at >> > org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:131) >> >> Caused by: org.apache.maven.plugin.MojoExecutionException: Error >> deploying artifact: > Z:\jcoleman\projects\eTraderII\trunk\target\classes >> (Access is denied) >> >> at >> org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:174) >> >> at >> > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa >> nager.java:417) >> >> at >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default >> LifecycleExecutor.java:610) >> >> ... 10 more >> >> Caused by: >> org.apache.maven.artifact.deployer.ArtifactDeploymentException: Error >> deploying artifact: > Z:\jcoleman\projects\eTraderII\trunk\target\classes >> (Access is denied) >> >> at >> >
RE: deploy goal fails
Hi, we manage to get this working adding an execution goal to the war plugin, as per: http://jira.codehaus.org/browse/MNG-1893#action_77870 Hope it helps you too Regards Ivan Ivan Garcia wrote: > > Hi, > > Did you find a solution for this? > > I'm having the same problem: > Error deploying artifact: > C:\projects\Portal2\code\workflow\web\target\classes (Access is denied) > > The point is that it only fails when adding a classifier to the war. > > mvn install OTOH works fine > > (I also get the : altDeploymentRepository = null ) > > > Regards > Ivan > > > > John Coleman-6 wrote: >> >> It's strange because this is a mapped drive over a local disk, and the >> folder exists and contains classes. But this looks somewhat like a >> network permissions problem? >> >> Other deployments from this drive work fine. >> >> John >> >> -Original Message- >> From: Wayne Fay [mailto:[EMAIL PROTECTED] >> Sent: 21 August 2007 16:53 >> To: Maven Users List >> Subject: Re: deploy goal fails >> >> Caused by: java.io.FileNotFoundException: >> Z:\jcoleman\projects\eTraderII\trunk\target\classes (Access is denied) >>at java.io.FileInputStream.open(Native Method) >> >> That's your root problem. I can't tell you why its happening or what >> it means, but that's the reason your deploy is failing. >> >> Wayne >> >> On 8/21/07, John Coleman <[EMAIL PROTECTED]> >> wrote: >>> I have used a classifier on the war plugin, and it looks like this >>> spoils the deploy, but the error message doesn't seem related. >>> >>> >>> >>> Does anyone understand this error pls? >>> >>> >>> >>> TIA >>> >>> John >>> >>> >>> >>> >>> >>> [deploy:deploy] >>> >>> altDeploymentRepository = null >>> >>> [INFO]Retrieving previous build number from repo >>> >>> [DEBUG]repository metadata for: 'snapshot >>> com.eurobase:eTraderII:1.2-SNAPSHOT' could not be found on repository: >>> repo >>> >>> [INFO]Error for project: eTraderII Project (during deploy) >>> >>> >> [INFO]-- >>> -- >>> >>> [INFO]Error deploying artifact: >>> Z:\jcoleman\projects\eTraderII\trunk\target\classes (Access is denied) >>> >>> >> [INFO]-- >>> -- >>> >>> [DEBUG]Trace >>> >>> org.apache.maven.lifecycle.LifecycleExecutionException: Error >> deploying >>> artifact: Z:\jcoleman\projects\eTraderII\trunk\target\classes (Access >> is >>> denied) >>> >>> >>> >>> at >>> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default >>> LifecycleExecutor.java:635) >>> >>> at >>> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec >>> ycle(DefaultLifecycleExecutor.java:551) >>> >>> at >>> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL >>> ifecycleExecutor.java:530) >>> >>> at >>> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle >>> Failures(DefaultLifecycleExecutor.java:309) >>> >>> at >>> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( >>> DefaultLifecycleExecutor.java:276) >>> >>> at >>> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec >>> ycleExecutor.java:143) >>> >>> at >>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:393) >>> >>> at >> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:182) >>> >>> at >>> >> org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:760) >>> >>> at >>> >> org.codehaus.mevenide.netbeans.execute.MavenJavaExecutor.run(MavenJavaEx >>> ecutor.java:257) >>> >>> at >>> >> org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:131) >>> >>> Caused by: org.apache.maven.plugin.MojoExecutionException: Error &
Surefire-plugin 2.3.1 xml-apis classpath issue
Hi there, Was there any change in surefire-plugin from version 3.2 to 3.2.1 that changes the way xml apis are loaded for tests? With version 3.2, I can add xercesIml in scope:test and use XSD validation. After getting the upgrade to version 2.3.1 I'm getting this error: nested exception is javax.xml.parsers.ParserConfigurationException: Unable to validate using XSD: Your JAXP provider [EMAIL PROTECTED] does not support XML Schema. Are you running on Java 1.4 or below with Apache Crimson? Upgrade to Apache Xerces (or Java 1.5) for full XSD support. Caused by: javax.xml.parsers.ParserConfigurationException: Unable to validate using XSD: Your JAXP provider [EMAIL PROTECTED] does not support XML Schema. Are you running on Java 1.4 or below with Apache Crimson? Upgrade to Apache Xerces (or Java 1.5) for full XSD support. I have xercesImpl as test scope dependency and also have it installed in the jdk/jre. Using 3.2 plugin version XSD validation works fine Any idea if this must be reported as a bug? Thanks Ivan Garcia -- View this message in context: http://www.nabble.com/Surefire-plugin-2.3.1-xml-apis-classpath-issue-tp14707599s177p14707599.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Aggregate modules and parallel builds
Hi, During non-parallel build aggregate POMs are built last provided there is no parent-child relationships between it and its submodules (correct me if I am wrong). Is that preserved during parallel builds? Can I assume that root POM is built after all its submodules are built? According to the build logs, it seems like the answer is "no", but maybe I am missing something. If answer is "no", how can I ensure that aggregate POM is built last? For example, I want to run assembly plugin after all submodules are built (in parallel build)? Of course, I can run separate "mvn -N assembly:assembly" command to assemble built stuff, but is there a way to do that during regular build? I don't want to specify dependencies explicitly since it could be error-prone (submodules dependencies could change, for example). Can we have this convention back? Make org.apache.maven.project.ProjectsSorter to add "weak" dependencies from aggregate module to all its submodules? -- WBR, Ivan Dubrov
Aggregate modules and parallel builds
Hi, During non-parallel build aggregate POMs are built last provided there is no parent-child relationships between it and its submodules (correct me if I am wrong). Is that preserved during parallel builds? Can I assume that root POM is built after all its submodules are built? According to the build logs, it seems like the answer is "no", but maybe I am missing something. If answer is "no", how can I ensure that aggregate POM is built last? For example, I want to run assembly plugin after all submodules are built (in parallel build)? Of course, I can run separate "mvn -N assembly:assembly" command to assemble built stuff, but is there a way to do that during regular build? I don't want to specify dependencies explicitly since it could be error-prone (submodules dependencies could change, for example). Can we have this convention back? Make org.apache.maven.project.ProjectsSorter to add "weak" dependencies from aggregate module to all its children? -- WBR, Ivan Dubrov
Re: Aggregate modules and parallel builds
This approach is kind of error prone. The assembly I want to make basically packages whole directory. So I want it to be invoked after _all_ submodules are built, with an assumption that set of the submodules could change over time and I don't want to fix assembling every time this happens. On Fri, Nov 16, 2012 at 1:25 PM, Ansgar Konermann < ansgar.konerm...@googlemail.com> wrote: > Read this first (the useAllReactorProjects flag notes, especially): > > > https://maven.apache.org/plugins/maven-assembly-plugin/examples/multimodule/module-binary-inclusion-simple.html > > > https://maven.apache.org/plugins/maven-assembly-plugin/faq.html#module-binaries > > Create a new child module to produce the assembly, have this module depend > on the child modules you want to include the binaries from AND use an > assembly descriptor having useAllReactorPlugins set to true. > > Am 16.11.2012 22:06 schrieb "Ivan Dubrov" : > > > > Hi, > > > > During non-parallel build aggregate POMs are built last provided there is > > no parent-child relationships between it and its submodules (correct me > if > > I am wrong). > > > > Is that preserved during parallel builds? Can I assume that root POM is > > built after all its submodules are built? According to the build logs, it > > seems like the answer is "no", but maybe I am missing something. > > > > If answer is "no", how can I ensure that aggregate POM is built last? For > > example, I want to run assembly plugin after all submodules are built (in > > parallel build)? Of course, I can run separate "mvn -N assembly:assembly" > > command to assemble built stuff, but is there a way to do that during > > regular build? > > I don't want to specify dependencies explicitly since it could be > > error-prone (submodules dependencies could change, for example). > > > > Can we have this convention back? Make > > org.apache.maven.project.ProjectsSorter to add "weak" dependencies from > > aggregate module to all its submodules? > > > > -- > > WBR, > > Ivan Dubrov > -- WBR, Ivan Dubrov
Re: Maven Assembly Plugin: Is there a way to specify the assembly location in the assembly descriptor?
On Nov 21, 2012, at 3:16 PM, Javier Ortiz wrote: > Is there a way to specify the location of the assembly? Sure. https://maven.apache.org/plugins/maven-assembly-plugin/single-mojo.html#outputDirectory > > Can I specify the file's full name instead of the default appending the id > to the project file name? Yep. First, disable appending id (https://maven.apache.org/plugins/maven-assembly-plugin/single-mojo.html#appendAssemblyId). Second, specify https://maven.apache.org/plugins/maven-assembly-plugin/single-mojo.html#finalName - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Converting ant build project to Maven based project
I wrote this guide some time ago which might be help some http://www.pazmino.ec/tools/mavenizing-an-existing-project.html Regards, IP 2012/2/14 Brian Topping > On Feb 14, 2012, at 2:22 PM, Bobbepalli, Purnachandrarao wrote: > > > Hi Good Afternoon to everybody > > > > This is PurnachandraRao, my first day in this maven users list. > > > > I want to how to convert Ant Build based project to Maven based project. > > Some resources for you to review first: > > 0. http://www.sonatype.com/books/mvnref-book > 1. http://www.lmgtfy.com?q=convert+Ant+Build+based+project+to+Maven > 2. http://catb.org/esr/faqs/smart-questions.html > > When you get stuck with specific questions that aren't documented > anywhere, this list is a great resource, but Maven is a mature product and > most of what you need to know is easy to find in Google. You may want to > consider a class, > http://www.developintelligence.com/catalog/software-engineering-training/development-tools/working-with-apache-mavenis > a good one that I have taught to folks in the past. > > Good luck! > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Adding compile source root from Ant-based plugin
Hello, I have Ant-based MOJO that generates some Java sources. What is the preferred way to add the directory with the generated sources as an additional source root? I do not want to configure manually build-helper-maven-plugin (http://mojo.codehaus.org/build-helper-maven-plugin/) from my project descriptor, since I think my generator-plugin should take the appropriate actions itself. Probably, there is a way to call MOJO from Ant script (in that case, I could invoke build-helper:add-source from my Ant target)? P.S. Please, add me to the cc, I'm not subscribed to the list. -- WBR, Ivan S. Dubrov - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Adding compile source root from Ant-based plugin [again and still unanswered]
I haven't tested this functionality personally, but it looks like the maven-antrun-plugin already has explicit support for what you are describing via the sourceRoot parameter: http://maven.apache.org/plugins/maven-antrun-plugin/run-mojo.html -Max I do not use maven-antrun-plugin, In my POM I use my custom plugin, based on Ant (maven-plugin-tools-ant). -- WBR, Ivan S. Dubrov - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
