Re: Including resources from java folder in M2
David,
According to the standard directory layout, resources should be put
under /src/main/resources.
Anyway, what you need to do is to add resources/resource into pom.xml. e.g.
${basedir}/src/main/resources
**/*.xconfig
Regards,
Willie
On 5/29/06, David Leangen <[EMAIL PROTECTED]> wrote:
Hello!
I'm new to M2, but I'm familiar with this type of build system.
I have some xml config files that normally should be distributed side by
side with a class file. So, the files are located in the java folder:
src
main
com/mystuff
SomeClass.java
SomeClass.xconfig
However, it seems that only the *.java files are copied over to the
classes directory.
How can I include other types files that are in the java directory,
since I do not want to have to recreate the build path in the resources
directory?
Thank you!
David
-
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]
Internal plugin repository - how to populate?
In many corporate environments it is unacceptable to let users download Maven plugins automatically and directly from the Internet (even not through a proxy). Therefore, it is necessary to set up an internal plugin repository. Question: Is there an easy way how to initially populate the internal repository with all the maven plugins needed? I considered the following ways: 1. mvn deploy:deploy-file for all the plugin jars. Problem: This seems to be a rather inconvenient approach with lots of manual work. 2. First popule a local repository by running all desired Maven goals, and then copy the local repository contents to the internal remote repository. Problem: As far as I understood, this wouldn't work, because a remote repository contains some extra XML definition files, that are not available in the local repository. Any other ideas? Thanks in advance, Arne -- View this message in context: http://www.nabble.com/Internal+plugin+repository+-+how+to+populate--t1697509.html#a4606575 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Including resources from java folder in M2
Hello! I'm new to M2, but I'm familiar with this type of build system. I have some xml config files that normally should be distributed side by side with a class file. So, the files are located in the java folder: src main com/mystuff SomeClass.java SomeClass.xconfig However, it seems that only the *.java files are copied over to the classes directory. How can I include other types files that are in the java directory, since I do not want to have to recreate the build path in the resources directory? Thank you! David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re : log within surefire 2.2
Can we discribe surefire plugin in the pom to tell him where is the configuration file. Or, is it a missing feature ? Yan. - Message d'origine De : Wim Deblauwe <[EMAIL PROTECTED]> À : Maven Users List Envoyé le : Dimanche, 28 Mai 2006, 2h12mn 24s Objet : Re: log within surefire 2.2 It was through searching I got the below mail, but I saw it is unanswered, hence my mail... I hope someone can help us out... regards, Wim 2006/5/27, Andreas Guther <[EMAIL PROTECTED]>: > > Did you search the mailing list archive? I think I read not too long > ago a thread on that issue with a similar problem. > > Andreas > > > > -Original Message- > From: Wim Deblauwe [mailto:[EMAIL PROTECTED] > Sent: Saturday, May 27, 2006 11:36 AM > To: Maven Users List; langlois yan > Subject: Re: log within surefire 2.2 > > I got the same problem, anyone got a solution for this? > > 2006/5/16, langlois yan <[EMAIL PROTECTED]>: > > > > The new release of the surefire plugin does not use my log4j which is > in > > the src/main/resources. How can I tell surefire to use it ? > > > > Yan. > > > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: attach mojo plugin to the build lifecycle
Running a plugin goal like hello:sayhi can be set to be run after the compile phase if you put the plugin annotation: @execute phase="compile" With the annotation, CLI invocation of the goal will always build the project up to the compile phase and then run your plugin. However, you can't put @phase and @execute on the same plugin goal bec it would lead to your project being built twice. You can do what the assembly plugin currently does... declare two goals, one is attached to a phase (assembly:attached -> @phase) and the other requiring a build phase (assembly:assembly -> @execute). Hope that helps. ^_^ cristal wrote: Hi, I had a test mojo plugin which I tried to attach it to the compile phase of the lifecycle. I did all these following the guide at this link: http://maven.apache.org/guides/plugin/guide-java-plugin-development.html So, I was able to run the command "mvn compile" - I can see the sample hello:sayhi plugin got executed at compile phase. However, I am wondering if there is a way to trigger the compile by simply typing "mvn hello:sayhi" so that one day I can rename the goal from hello:sayhi to "cristal:build" to have my project compiled, instead of typing "mvn compile". Basically this is what we had in maven1 but maven2 doesn't seem to do it. Thanks for any tips on this. -- View this message in context: http://www.nabble.com/attach+mojo+plugin+to+the+build+lifecycle-t1682566.html#a4563639 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: problems withcobertura plugins
There's no parameter for the "check" goal. alexis parratte wrote: hi, i have a problem with cobertura plugin v-2.0 this is a part of my build: org.codehaus.mojo cobertura-maven-plugin 2.0 pre-site clean check 30 30 **/*Impl* the goal "check" is ok but it don't take account the part and i always have these classes in the report someone have an idea thanks Alexis - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Assembly plugin and optional dependencies
Sorry, but there's no such feature in assembly. Either you put all the optional deps in the includes or put all the non-optional deps in the excludes. Or you can create an feature in jira: http://jira.codehaus.org/secure/BrowseProject.jspa?id=11126 ^_^ Guilherme Silveira wrote: I have a pom file which includes dependency=A as scope=compile, optional=true. I would like the assembly plugin to add all optional dependencies in a separate directory than the non-optional ones... any way to do this? I currently have: false runtime And it puts both optional and non-optional in the same directory... Guilherme Silveira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Java-Bean: True
Hi, Using maven 2, how can you tag some classes in a jar as java beans? The MANIFEST.MF file I want is (in part): Manifest-Version: 1.0 Archiver-Version: Plexus Archiver Created-By: Apache Maven ... Class-Path: htmllexer.jar sax-2.0.1.jar Name: org/htmlparser/Parser.class Java-Bean: True etc. As usual, the documentation lies and says setting src/main/resources/MANIFEST.MF is an option; but that doesn't work. I've tried guessing the usual things in the maven-jar-plugin manifest and manifestEntries sections of the POM, but can only get an error message like: [INFO] Failed to configure plugin parameters for: org.apache.maven.plugins:maven-jar-plugin:2.0 Cause: Cannot find setter nor field in org.apache.maven.archiver.ManifestConfigu ration for 'name' or [INFO] Error assembling JAR Embedded error: Specify the section name using the "name" attribute of the element rather than using a "Name" manifest attribute Any help would be appreciated. Derrick
Re: Delegating to other Mojo
You can use Maven Embedder to call another Mojo from within your Mojo.
Below is a snippet that I hope will help.
Cheers,
Rahul
snip
MavenEmbedder maven = new MavenEmbedder ();
ClassLoader classLoader = Thread.currentThread ().getContextClassLoader
();
maven.setClassLoader (classLoader);
maven.setLogger (new MavenEmbedderConsoleLogger ());
try {
maven.start ();
File targetDirectory = new File (targetDir);
File pomFile = new File (targetDirectory, pomXml);
MavenProject pom = maven.readProjectWithDependencies (pomFile);
EventMonitor eventMonitor = new DefaultEventMonitor (new
PlexusLoggerAdapter (new MavenEmbedderConsoleLogger ()));
if (getLog ().isDebugEnabled ())
getLog ().debug ("Executing embedded Maven instance...");
if (getLog ().isInfoEnabled ())
getLog ().info ("delegating goal(s) now to embedded m2 instance.");
maven.execute (pom, goals, eventMonitor, new ConsoleDownloadMonitor (),
null, targetDirectory);
if (getLog ().isInfoEnabled ())
getLog ().info ("Embedded Maven executed successfully!");
} catch (Exception e) {
// TODO : catch specific Exceptions (this is for demonstration)
}
--- snip -
- Original Message -
From: "Wilfred Springer" <[EMAIL PROTECTED]>
To: "Maven Users List"
Sent: Monday, May 29, 2006 2:10 AM
Subject: m2: Delegating to other Mojo
All,
Is there any way to force execution of some Mojo from another Mojo?
Thanks,
Wilfred
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[ANN] Maven Ear Plugin 2.2 for Maven 2 Released
The Maven team is pleased to announce the release of the Maven Ear Plugin, version 2.2 http://maven.apache.org/plugins/maven-ear-plugin/ You can run mvn -U to get the latest version of the plugin, or specify the version in your project's plugin configuration: org.apache.maven.plugins maven-ear-plugin 2.2 Changes: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11132&fixfor=12146 ** Bug * [MEAR-3] - ear includes and excludes don't handle comma separated tokens * [MEAR-25] - EAR plugin fails when project contains a dependency of type pom ** Improvement * [MEAR-8] - Add security role definitions to maven-ear-plugin * [MEAR-20] - System dependency management * [MEAR-21] - Wrong example in howto.apt * [MEAR-23] - Move the description of the mojo from @description to the top of the class's comment block * [MEAR-28] - Patch to support JEE5 application.xml format ** New Feature * [MEAR-24] - Ear Plugin should allow the user to set "earName" like "jarName" in Jar Plugin * [MEAR-26] - Ability to configure and use custom artifact types ** Wish * [MEAR-18] - The EAR plugin will not properly handle WSR (Jboss web service archives) specified as dependencies in the pom.xml Have fun! -The Maven team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Subclassign AbstractAntMojo
Just FYI: I appeared to be working with the maven-antrun-plugin v. 1.1 instead of 1.0 in the Maven XDoclet plugin. Moving to 1.0 solved the problem. Thanks! On Sat, 2006-05-27 at 21:20 +0200, Kenney Westerhof wrote: > On Sat, 27 May 2006, Wilfred Springer wrote: > > Hi, > > take a look at xdoclet-maven-plugin, it subclasses the antrun plugin. > > See https://svn.codehaus.org/mojo/trunk/mojo/xdoclet-maven-plugin. > > -- Kenney > > > All, > > > > I tried to subclass AbstractAntMojo for another project, and I fail to > > see how to configure it correctly. I figured that either the existing > > components.xml fiel in maven-antrun-plugin would be picked by the > > classloader, or otherwise add a components.xml file of my own to > > src/main/resources in my own file. No matter what I try, my own plugin > > gets an NPE somewhere in executeTasks, and I don't see why. Since I have > > been working from my intuition only, I assume that I just don't have a > > clue on how to do this properly. > > > > So the question is if anybody has ever given this a try and knows what > > to do to make it work? > > > > Thanks, > > > > Wilfred > > > > -- > Kenney Westerhof > http://www.neonics.com > GPG public key: http://www.gods.nl/~forge/kenneyw.key > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > >
m2: Delegating to other Mojo
All, Is there any way to force execution of some Mojo from another Mojo? Thanks, Wilfred
Re: [M2] questions about migrating to maven
Hi Carlos, re FILTERING PROPERTIES FILES FOR ENVIRONMENTS I usually don't like this approach for the inconvinients you mention, you need to rebuild your artifacts for each environments, which is usually prone to errors, you test x-dev in your machine, and then build x-prod for production, with no guarantees that it's the same stuff you tested. My suggestion is to externalie that configuration options in a way that your artifact is always the same, and only configuration changes. You can do reading your config files from the classpath or better using JNDI. You can also have dev config as default so your developers don't have to setup anything and you do it only in prod or preprod. re INTER-PROJECT DEPENDENCIES With maven the best way is not to rebuild all your dependencies every time, but to depend on the binaries generated by the other projects as SNAPSHOTs. You can ensure the repo has the latest snapshot by setting up continuum to deploy everytime somebody changes the project. That way developers don't have to go through the extra time consuming process of building the dependencies. Regards Carlos On 5/26/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: I am pretty sure that I am over thinking this ;) However, I am having trouble thinking how best to migrate our ant based build process to maven. Principally: - Filtering properties files for environments, and - Inter-project dependencies FILTERING PROPERTIES FILES FOR ENVIRONMENTS As with most projects, our apps use properties files for configuring a host of settings. Many of these (e.g. db settings, log4j settings, web service host:port etc) are environment specific. Our projects have properties files for various target environments, such as production, pre-production, cruisecontrol. Each developer also has a local props file that they can tailor for their particular needs (e.g. for debugging you may want to log springframework as DEBUG and suppress all others). Ant uses these files to filter the application properties. The result is a build tailored for a particular environment. Since all environment specific properties, beside the local, are source controlled we have a high degree of confidence in consistent and reproducible builds to our shared infrastructure. In maven I have been able to reproduce this behavior with profiles. However, I am not sure what to do with the resulting artifacts. Each artifact is "tainted" with environment specific properties. Should artifacts generated with "local" only be installed in each developers local repository? What about the artifacts for the testing and production environments? Should the internal repository only be used to store "production" artifacts? Should there be multiple shared internal repositories, one for production and one for pre-prod? INTER-PROJECT DEPENDENCIES Currently we have a web based application broken out into four projects: 1 - user-presentation-layer 2 - admin-presentation-layer 3 - web-service-layer 4 - common-utils Each project generates a primary artifact, and the web-service-layer also generates a client jar. Currently in order to generate a fresh build of say the user-presentation-layer, you must have the web-service-layer and common-utils checked out in your workspace. The ant build file for the user-presentation-layer will end up calling the other two build files. These builds in turn, get an update from cvs and then generating the appropriate artifact. Granted it took some time to get this process up and running, but it currently works and works pretty well. From my readings, it seems that this process is frowned upon. With maven, the appropriate process would be to "mvn scm:update install" on the web-service-layer and common-utils projects. Then run the build for the user-presentation-layer. Or better yet, have each user pull the dependencies (web-service-layer and common-utils) from an internal repository that is updated by developers checking in changes or by some source control repository. However, as noted above, because of environmental impacts, I am not sure a shared repository would work for artifacts used in development. Currently, our environment profiles only effect configuration settings. They do not modify or impact the source code directly. While the maven dependencies are a result of class dependencies, which should not be impacted by using an artifact configured for "production" versus one configured for "preproduction". What is the best way to handle this problem? I am sure people much smarter than myself have already tackled these problems and come up with very simple solutions. Any and all help sorting myself out would be really appreciated! Carlos - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- I could give you my word as a Spaniard. No good. I've known too many Spaniards.
Re: problem getting source maven-proxy
They are aware of the problems. We can just be patient On 5/28/06, Wayne Fay <[EMAIL PROTECTED]> wrote: I'm getting the same thing. I assume this is related to the hard disk failures experience at Codehaus. Not sure where to file the issue/who to tell, but it is certainly something they should fix when they have time. Probably easiest to just report in #codehaus? Wayne On 5/28/06, Wouter de Vaal <[EMAIL PROTECTED]> wrote: > Hi, > > When I try to check out the source for maven-proxy (I wish to patch it with > ntlm user/pass support), I > get the following error: > > Could not connect to > :pserver:[EMAIL PROTECTED]:/scm/maven-proxy/: > I/O exception occurred: Connection refused: Server configuration missing > --allow-root in inetd.conf > > Is this related to the codehaus problems? Or am I missing something? > > Regards, > Wouter > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Surefire report when tests fail
Wim, you can either configure Surefire to not use the text files with
this configuration (below) or use -Dsurefire.useFile=false to get
Surefire to write output to the screen rather than to those text
files:
maven-surefire-plugin
false
As for the "a way to distinguish between builds" etc issue, you should
probably resolve that issue through proper use of Profiles and
Properties. So you would use:
${your-property-here}
and perhaps
${same-or-different-property-here}
And then either pass -Dyour-property-here=true/false or more ideally
set the property in a profile. So when you are building to deploy the
site, you use the -P site profile which specifies TRUE, and otherwise
the default profile specifies FALSE for this property.
Wayne
On 5/28/06, Wim Deblauwe <[EMAIL PROTECTED]> wrote:
hmmm.. okay, I'll try to find out. But this seems like a very reasonable
question. Who wants to go through all the .txt files surefire generates to
find out what test has failed?
regards,
Wim
2006/5/27, Andreas Guther <[EMAIL PROTECTED]>:
>
> In
>
>
>
> org.apache.maven.plugins
> maven-surefire-plugin
> 2.2
>
> true
>
>
> ...
>
> I think there is a way to distinguish between builds where you want to
> not ignore and site generation when you want to ignore in order to
> generate the site. I am currently not using it but if you come across
> the solution it would be great if you could share it here.
>
> Andreas
>
>
>
> -Original Message-
> From: Wim Deblauwe [mailto:[EMAIL PROTECTED]
> Sent: Saturday, May 27, 2006 11:20 AM
> To: Maven Users List
> Subject: [m2] Surefire report when tests fail
>
> Hi,
>
> when I run mvn site, the surefire report is not generated when my unit
> tests
> fail. How can I get the report?
>
> I added the surefire-report-maven-plugin to the reporting section of my
> pom.
>
> regards,
>
> Wim
>
> -
> 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 - Junit Testcase Issue with Surefire
While all that information is interesting, if you actually want someone to help with your issue, you'll need to post your specific, detailed failure/debug output. In other words, send the useful lines from mvn -X test as plain text in a response email, not as an attachment. Wayneyour On 5/26/06, Zhang,Dafang <[EMAIL PROTECTED]> wrote: Hi, I'm currently having an issue running Junit test from Maven2 command line (Windows XP SP2). The same Junit testcase is running fine from IBM Rational Application Developer (RAD) 6. The command line JRE environment is the same as in the RAD6 (RAD6 runtimes\base_v6\java). They are pointing to the same Maven local repository. The only difference is that the Junit test is running from RAD6 Junit integration and the Maven2 command line uses Surefire's IsolatedClassLoader. Log from running "mvn -X test" is available upon request. Any help would be greatly appreciated. Best Regards, Dafang - CONFIDENTIALITY NOTICE This message and any included attachments are from Cerner Corporation and are intended only for the addressee. The information contained in this message is confidential and may constitute inside or non-public information under international, federal, or state securities laws. Unauthorized forwarding, printing, copying, distribution, or use of such information is strictly prohibited and may be unlawful. If you are not the addressee, please promptly delete this message and notify the sender of the delivery error by e-mail or you may call Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1) (816)221-1024. --- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: problem getting source maven-proxy
I'm getting the same thing. I assume this is related to the hard disk failures experience at Codehaus. Not sure where to file the issue/who to tell, but it is certainly something they should fix when they have time. Probably easiest to just report in #codehaus? Wayne On 5/28/06, Wouter de Vaal <[EMAIL PROTECTED]> wrote: Hi, When I try to check out the source for maven-proxy (I wish to patch it with ntlm user/pass support), I get the following error: Could not connect to :pserver:[EMAIL PROTECTED]:/scm/maven-proxy/: I/O exception occurred: Connection refused: Server configuration missing --allow-root in inetd.conf Is this related to the codehaus problems? Or am I missing something? Regards, Wouter - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Status on mavenide (maven2) IDEA plugin?
well, about a month ago me, milos and jason chatted on irc and mapped the features and (rough) outline/scope of the plugin(s). jason is to publish a docu of that as a summary when he will find the time, and then we can start plan the technical details of the idea plugin to make things worse, I left the mevenide-idea cvs head in a bit of a flux, cause I was in the middle of restructuring it when I started working on a project which took all of my time (and more...). but there's a tag for the 0.1 release which is stable. my gut feeling, though, is that we should start from scratch and not use the mevenide code (or atleast do very selective copying) because the mevenide plugin is very m1-oriented we can schedule a meeting on irc and start planning the technical details if you wish... On 5/28/06, ben short <[EMAIL PROTECTED]> wrote: Trygve, So how do we move forward with the idea plugin? Ben On 5/26/06, Trygve Laugstøl <[EMAIL PROTECTED]> wrote: > Arik Kfir wrote: > > Hi guys, > > > > I developed the initial mevenide for idea (m1) a while ago, when m2 > > was only in the horizon. I've planned to start working on m2 > > integration but lately my time is more limited and I can't devote much > > time to it so the mevenide for idea plugin is basically frozen. > > > > Lately jason, milos and myself started planning the m2 integration > > into tools (milos already implemented it for netbeans as you know, and > > there's a working plugin for eclipse i believe) so expect some > > progress on this - but it will take some time (atleast for idea). > > I've noticed this effort and it's an effort that I will join as soon as > possible. > > Arik: do you have any code that could be useful for a Maven 2 plugin in > your Mevenide work? > > > in the meantime, the maven-idea-plugin which generates the idea > > project files works great and I have no real issues with it so I > > believe it suffices for now. Integrating idea as an external tool also > > works very good and that's what I'd recommend. > > The biggest bonus for me over idea:idea and the Maven 2 external tool > that I have is the speed. > > Calling the install phase on a small already built jar (i.e. all the > classes where already compiles) project takes less than a second. > > -- > Trygve > > - > 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] -- __ Cheers, Arik Kfir [EMAIL PROTECTED] Linux user, number 415067 - http://counter.li.org/ http://corleon.dnsalias.org
problem getting source maven-proxy
Hi, When I try to check out the source for maven-proxy (I wish to patch it with ntlm user/pass support), I get the following error: Could not connect to :pserver:[EMAIL PROTECTED]:/scm/maven-proxy/: I/O exception occurred: Connection refused: Server configuration missing --allow-root in inetd.conf Is this related to the codehaus problems? Or am I missing something? Regards, Wouter
Re: Status on mavenide (maven2) IDEA plugin?
Trygve, So how do we move forward with the idea plugin? Ben On 5/26/06, Trygve Laugstøl <[EMAIL PROTECTED]> wrote: Arik Kfir wrote: > Hi guys, > > I developed the initial mevenide for idea (m1) a while ago, when m2 > was only in the horizon. I've planned to start working on m2 > integration but lately my time is more limited and I can't devote much > time to it so the mevenide for idea plugin is basically frozen. > > Lately jason, milos and myself started planning the m2 integration > into tools (milos already implemented it for netbeans as you know, and > there's a working plugin for eclipse i believe) so expect some > progress on this - but it will take some time (atleast for idea). I've noticed this effort and it's an effort that I will join as soon as possible. Arik: do you have any code that could be useful for a Maven 2 plugin in your Mevenide work? > in the meantime, the maven-idea-plugin which generates the idea > project files works great and I have no real issues with it so I > believe it suffices for now. Integrating idea as an external tool also > works very good and that's what I'd recommend. The biggest bonus for me over idea:idea and the Maven 2 external tool that I have is the speed. Calling the install phase on a small already built jar (i.e. all the classes where already compiles) project takes less than a second. -- Trygve - 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] Surefire report when tests fail
hmmm.. okay, I'll try to find out. But this seems like a very reasonable question. Who wants to go through all the .txt files surefire generates to find out what test has failed? regards, Wim 2006/5/27, Andreas Guther <[EMAIL PROTECTED]>: In org.apache.maven.plugins maven-surefire-plugin 2.2 true ... I think there is a way to distinguish between builds where you want to not ignore and site generation when you want to ignore in order to generate the site. I am currently not using it but if you come across the solution it would be great if you could share it here. Andreas -Original Message- From: Wim Deblauwe [mailto:[EMAIL PROTECTED] Sent: Saturday, May 27, 2006 11:20 AM To: Maven Users List Subject: [m2] Surefire report when tests fail Hi, when I run mvn site, the surefire report is not generated when my unit tests fail. How can I get the report? I added the surefire-report-maven-plugin to the reporting section of my pom. regards, Wim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: log within surefire 2.2
It was through searching I got the below mail, but I saw it is unanswered, hence my mail... I hope someone can help us out... regards, Wim 2006/5/27, Andreas Guther <[EMAIL PROTECTED]>: Did you search the mailing list archive? I think I read not too long ago a thread on that issue with a similar problem. Andreas -Original Message- From: Wim Deblauwe [mailto:[EMAIL PROTECTED] Sent: Saturday, May 27, 2006 11:36 AM To: Maven Users List; langlois yan Subject: Re: log within surefire 2.2 I got the same problem, anyone got a solution for this? 2006/5/16, langlois yan <[EMAIL PROTECTED]>: > > The new release of the surefire plugin does not use my log4j which is in > the src/main/resources. How can I tell surefire to use it ? > > Yan. > > > > - > 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: RMI plugin for Maven 1.x
Or you could use ours: http://java.freehep.org/freehep-rmic-plugin/ regards Mark Donszelmann On May 27, 2006, at 5:25 PM, Steven Coco wrote: Re: Is a plugin for doing rmic available for Maven 1.x ? Regards, Kanakambaran Can you do this with an execution plugin? I have used the Ant plugin to execute processes during builds; and there is a maven- exec plugin at codehaus.org, but I haven't used that: see: http://mojo.codehaus.org/exec-maven-plugin/ Good luck. Steven Coco. - 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]
Subclassign AbstractAntMojo
All, I tried to subclass AbstractAntMojo for another project, and I fail to see how to configure it correctly. I figured that either the existing components.xml fiel in maven-antrun-plugin would be picked by the classloader, or otherwise add a components.xml file of my own to src/main/resources in my own file. No matter what I try, my own plugin gets an NPE somewhere in executeTasks, and I don't see why. Since I have been working from my intuition only, I assume that I just don't have a clue on how to do this properly. So the question is if anybody has ever given this a try and knows what to do to make it work? Thanks, Wilfred
M2 - Junit Testcase Issue with Surefire
Hi, I'm currently having an issue running Junit test from Maven2 command line (Windows XP SP2). The same Junit testcase is running fine from IBM Rational Application Developer (RAD) 6. The command line JRE environment is the same as in the RAD6 (RAD6 runtimes\base_v6\java). They are pointing to the same Maven local repository. The only difference is that the Junit test is running from RAD6 Junit integration and the Maven2 command line uses Surefire's IsolatedClassLoader. Log from running "mvn -X test" is available upon request. Any help would be greatly appreciated. Best Regards, Dafang - CONFIDENTIALITY NOTICE This message and any included attachments are from Cerner Corporation and are intended only for the addressee. The information contained in this message is confidential and may constitute inside or non-public information under international, federal, or state securities laws. Unauthorized forwarding, printing, copying, distribution, or use of such information is strictly prohibited and may be unlawful. If you are not the addressee, please promptly delete this message and notify the sender of the delivery error by e-mail or you may call Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1) (816)221-1024. ---
Re: Rant (very long)
Franz Fehringer wrote: I asked this before and now try again. Can Maven2 access https repositories from behind a proxy/firewall? 1) Browse to http://maven.apache.org 2) Press "documentation" 3) Seach for "prox" and click on: http://maven.apache.org/guides/mini/guide-proxies.html -- Trygve - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ismicro-commons] Proximity: possible to have config files outside of WEB-INF?
Hi Jeff,
first of all, i would like to ask you to continue this debate on Maven
Users List , since this mailing list is hosted
on "site" (my machine) with very lousy (adsl) uplink and is not meant to
be public :) It is my mistake that on Proximity site I listed this
mailing list.
Well, your question regards mere the J2EE webapp then Proximity itself.
It is possible what you asking, but this way you will VIOLATE the J2EE
guidelines. Nevertheless, as long as you use some "relaxed" container
(eg. Tomcat and not JBoss) everything should be fine (i think, never
tested it actually).
Since in web.xml you cannot reference file outside the webapp root, you
should create a Spring "stub" application context, which will in turn
include the "real" application context. Since this configuration is done
by Spring, not the servlet container it would be possible to achieve it.
I modelled this by placing files in my $HOME/tmp. Files attached.
Steps to achieve this:
1. Move /WEB-INF/applicationContext.xml to where you want and rename it
to proximity.xml (in my case $HOME/tmp)
2. Move /WEB-INF/proximity.properties to be beside proximity.xml (in my
case $HOME/tmp)
3. Set up both files as you want, use SCM on it etc.
4. I attached a Spring "stub" context, drop it in
/WEB-INF/applicationContext.xml REPLACING the original one.
5. Configure the stub to point where your proximity.xml is.
And that's it!
The bad thing about this config is that in case of path modification you
have TWO places to update: one in /WEB-INF/applicationContext.xml "stub"
and one in proximity.xml. But since you have "taken-out" the config from
webapp, you could simply drop the proximity properties file, replace and
maintain the proximity.xml file only by inserting values directly and
remove the "propertyConfigurer" bean from proximity.xml. The properties
file in this case is not a benefit.
Have fun
cstamas
Jeff Jensen wrote:
> Hi,
>
> Since we source control product config files, it is much easier for us when
> we can configure products to point to their config files in our desired
> location (i.e. into a dir in the SCM's workspace).
>
> So far with Proximity, we have changed settings in proximity.properties and
> applicationContext.xml.
>
> Not sure of all settings yet - is it possible to customize Proximity to load
> those files from a specified location instead of always from web-inf?
>
> ___
> ismicro-commons mailing list
> [EMAIL PROTECTED]
> http://mail.is-micro.hu/mailman/listinfo/ismicro-commons
>
http://www.springframework.org/dtd/spring-beans.dtd";>
messages
# proximity.properties
# The directory of the index files used by LuceneIndexer
indexer.dir=${user.home}/proximity/indexer
# The directory of repositories local storage.
# IMPORTANT! If local storage is metadata-aware (the default), then
# from the given directory Proximity will create two sub-dirs, one for
# metadata and one for actual files.
inhouseFSStorage.baseDir=${user.home}/proximity/inhouse
extFreeFSStorage.baseDir=${user.home}/proximity/ext-free
extNonFreeFSStorage.baseDir=${user.home}/proximity/ext-non-free
centralFSStorage.baseDir=${user.home}/proximity/central
ibiblioFSStorage.baseDir=${user.home}/proximity/ibiblio
codehausFSStorage.baseDir=${user.home}/proximity/codehaus
http://www.springframework.org/dtd/spring-beans.dtd";>
file:/home/cstamas/tmp/proximity.properties
http://repo1.maven.org/maven2/"; />
http://www.ibiblio.org/maven2/"; />
http://dist.codehaus.org/"; />
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Page not Found when searching for the Info.
Sharma, Jaikumar wrote: Can somebody really have a serious view for the following ? Works for me. -- Trygve - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Status on mavenide (maven2) IDEA plugin?
Arik Kfir wrote: Hi guys, I developed the initial mevenide for idea (m1) a while ago, when m2 was only in the horizon. I've planned to start working on m2 integration but lately my time is more limited and I can't devote much time to it so the mevenide for idea plugin is basically frozen. Lately jason, milos and myself started planning the m2 integration into tools (milos already implemented it for netbeans as you know, and there's a working plugin for eclipse i believe) so expect some progress on this - but it will take some time (atleast for idea). I've noticed this effort and it's an effort that I will join as soon as possible. Arik: do you have any code that could be useful for a Maven 2 plugin in your Mevenide work? in the meantime, the maven-idea-plugin which generates the idea project files works great and I have no real issues with it so I believe it suffices for now. Integrating idea as an external tool also works very good and that's what I'd recommend. The biggest bonus for me over idea:idea and the Maven 2 external tool that I have is the speed. Calling the install phase on a small already built jar (i.e. all the classes where already compiles) project takes less than a second. -- Trygve - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to native properties files with maven2
Hi,
I copied tools.jar to ${m2_home}/lib and the plugin works. Thanks any way.
ð �� <[EMAIL PROTECTED]> wrote: Hi Jakub,
I have tried your plugin. I think your idea is wonderful. But I can not mvn
compile your test project. The following is the error. Please help me. Thanks.
E:\test-project>mvn -e compile
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO]
---
[INFO] Building Maven Quick Start Archetype
[INFO]task-segment: [compile]
[INFO]
---
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] No sources to compile
[INFO] [ants:native2ascii {execution: default}]
native2ascii:
[delete] Deleting 2 files from E:\standino\tools\maven-ant-plugin\test-proje
t\target\classes
[native2ascii] Converting 2 files from E:\standino\tools\maven-ant-plugin\test-
roject\src\main\resources to E:\standino\tools\maven-ant-plugin\test-project\ta
get\classes
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to execute: Executing Ant script: /native2ascii.build.xml [native
ascii]: Failed to execute.
sun/tools/native2ascii/Main
[INFO]
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute: Exec
ting Ant script: /native2ascii.build.xml [native2ascii]: Failed to execute.
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Def
ultLifecycleExecutor.java:559)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithL
fecycle(DefaultLifecycleExecutor.java:475)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defa
ltLifecycleExecutor.java:454)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHa
dleFailures(DefaultLifecycleExecutor.java:306)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegme
ts(DefaultLifecycleExecutor.java:273)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultL
fecycleExecutor.java:140)
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:256)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcce
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)
Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to execute: E
ecuting Ant script: /native2ascii.build.xml [native2ascii]: Failed to execute.
at org.apache.maven.script.ant.AntMojoWrapper.execute(AntMojoWrapper.ja
a:37)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlug
nManager.java:412)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Def
ultLifecycleExecutor.java:534)
... 16 more
Caused by: org.codehaus.plexus.component.factory.ant.AntComponentExecutionExcep
ion: Executing Ant script: /native2ascii.build.xml [native2ascii]: Failed to ex
cute.
at org.codehaus.plexus.component.factory.ant.AntScriptInvoker.invoke(An
ScriptInvoker.java:227)
at org.apache.maven.script.ant.AntMojoWrapper.execute(AntMojoWrapper.ja
a:33)
... 18 more
Caused by: java.lang.NoClassDefFoundError: sun/tools/native2ascii/Main
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1225)
at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
at org.codehaus.plexus.component.factory.ant.AntScriptInvoker.invoke(An
ScriptInvoker.java:222)
... 19 more
Caused by: java.lang.NoClassDefFoundError: sun/tools/native2ascii/Main
at org.apache.tools.ant.taskdefs.optional.Native2Ascii.convert(Native2A
cii.java:248)
at org.apache.tools.ant.taskdefs.optional.Native2Ascii.execute(Native2A
cii.java:196)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at org.apache.tools.ant.Target.performTasks(Target.java:369)
at org.apache.tools.ant.Project.executeSortedTargets(Pro
Re: NullPointerException in Release Plugin 2.0-beta-4
OK. There's an issue beeing filed under MRELEASE-122 now. see http://jira.codehaus.org/browse/MRELEASE-122 Stefan 2006/5/28, Stefan Hübner <[EMAIL PROTECTED]>: uhm, not yet, I guess. I was off the list for a couple of days, so sorry for not replying. You will find the issue soon. Stefan 2006/5/24, Mark Hobson <[EMAIL PROTECTED]>: > Was an issue raised for this? > > On 23/05/06, Alexandre Poitras <[EMAIL PROTECTED]> wrote: > > Yup, solves the problem thank. > > > > On 5/23/06, Emmanuel Venisse <[EMAIL PROTECTED]> wrote: > > > I think you'll can fix your pb if you define the version of the extension in your pom. > > > File an issue about it and we'll fix this problem. > > > > > > Emmanuel > > > > > > Stefan Hübner a écrit : > > > > Any news on this issue, Emmanuel? > > > > > > > > Stefan > > > > > > > > 2006/5/19, Stefan Hübner <[EMAIL PROTECTED]>: > > > > > > > >> Hi Emmanuel, > > > >> > > > >> sorry for the delay! > > > >> > > > >> 2006/5/18, Emmanuel Venisse <[EMAIL PROTECTED]>: > > > >> > The pb seems to be in extension rewriting. > > > >> > Do you have some extensions in your poms? > > > >> > Do you have a version for them? > > > >> > > > > >> > > > >> yes, there's an extension defined in the parent POM: > > > >> > > > >> ... > > > >> ki-commons > > > >> ki-commons-parent > > > >> pom > > > >> KI Commons Parent > > > >> 1.1 > > > >> > > > >> > > > >> > > > >> org.apache.maven.wagon > > > >> wagon-ssh-external > > > >> > > > >> > > > >> > > > >> as you see, there's no version to the wagen-extension. is that > > > >> problematic? > > > >> > > > >> Stefan > > > >> > > > >> > Stefan Hübner a écrit : > > > >> > > oh, sorry! But, yes there is a version in my pom: > > > >> > > > > > >> > > > > > >> > > > > > >> > > > > > >> > >ki-commons-parent > > > >> > >ki-commons > > > >> > >1.1 > > > >> > > > > > >> > > 4.0.0 > > > >> > > ki-commons > > > >> > > ki-foundation > > > >> > > KI Foundation > > > >> > > 1.17.2-SNAPSHOT > > > >> > > ... > > > >> > > > > > >> > > Stefan > > > >> > > > > > >> > > > > > >> > > > > > >> > > > > > >> > > > > > >> > > 2006/5/18, Emmanuel Venisse <[EMAIL PROTECTED]>: > > > >> > > > > > >> > >> I didn't talk about release plugin version but about your pom > > > >> version > > > >> > >> > > > >> > >> Emmanuel > > > >> > >> > > > >> > >> Stefan Hübner a écrit : > > > >> > >> > no, but the latest version of maven-release-plugin in my local > > > >> > >> > repository is 2.0-beta-4 > > > >> > >> > > > > >> > >> > Stefan > > > >> > >> > > > > >> > >> > 2006/5/18, Emmanuel Venisse <[EMAIL PROTECTED]>: > > > >> > >> > > > > >> > >> >> Do you have a version defined in your pom? > > > >> > >> >> > > > >> > >> >> Emmanuel > > > >> > >> >> > > > >> > > > > >> > > > > >> > - > > > >> > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > >> > For additional commands, e-mail: [EMAIL PROTECTED] > > > >> > > > > >> > > > > >> > > > > > > > > > - > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: NullPointerException in Release Plugin 2.0-beta-4
uhm, not yet, I guess. I was off the list for a couple of days, so sorry for not replying. You will find the issue soon. Stefan 2006/5/24, Mark Hobson <[EMAIL PROTECTED]>: Was an issue raised for this? On 23/05/06, Alexandre Poitras <[EMAIL PROTECTED]> wrote: > Yup, solves the problem thank. > > On 5/23/06, Emmanuel Venisse <[EMAIL PROTECTED]> wrote: > > I think you'll can fix your pb if you define the version of the extension in your pom. > > File an issue about it and we'll fix this problem. > > > > Emmanuel > > > > Stefan Hübner a écrit : > > > Any news on this issue, Emmanuel? > > > > > > Stefan > > > > > > 2006/5/19, Stefan Hübner <[EMAIL PROTECTED]>: > > > > > >> Hi Emmanuel, > > >> > > >> sorry for the delay! > > >> > > >> 2006/5/18, Emmanuel Venisse <[EMAIL PROTECTED]>: > > >> > The pb seems to be in extension rewriting. > > >> > Do you have some extensions in your poms? > > >> > Do you have a version for them? > > >> > > > >> > > >> yes, there's an extension defined in the parent POM: > > >> > > >> ... > > >> ki-commons > > >> ki-commons-parent > > >> pom > > >> KI Commons Parent > > >> 1.1 > > >> > > >> > > >> > > >> org.apache.maven.wagon > > >> wagon-ssh-external > > >> > > >> > > >> > > >> as you see, there's no version to the wagen-extension. is that > > >> problematic? > > >> > > >> Stefan > > >> > > >> > Stefan Hübner a écrit : > > >> > > oh, sorry! But, yes there is a version in my pom: > > >> > > > > >> > > > > >> > > > > >> > > > > >> > >ki-commons-parent > > >> > >ki-commons > > >> > >1.1 > > >> > > > > >> > > 4.0.0 > > >> > > ki-commons > > >> > > ki-foundation > > >> > > KI Foundation > > >> > > 1.17.2-SNAPSHOT > > >> > > ... > > >> > > > > >> > > Stefan > > >> > > > > >> > > > > >> > > > > >> > > > > >> > > > > >> > > 2006/5/18, Emmanuel Venisse <[EMAIL PROTECTED]>: > > >> > > > > >> > >> I didn't talk about release plugin version but about your pom > > >> version > > >> > >> > > >> > >> Emmanuel > > >> > >> > > >> > >> Stefan Hübner a écrit : > > >> > >> > no, but the latest version of maven-release-plugin in my local > > >> > >> > repository is 2.0-beta-4 > > >> > >> > > > >> > >> > Stefan > > >> > >> > > > >> > >> > 2006/5/18, Emmanuel Venisse <[EMAIL PROTECTED]>: > > >> > >> > > > >> > >> >> Do you have a version defined in your pom? > > >> > >> >> > > >> > >> >> Emmanuel > > >> > >> >> > > >> > > > >> > > > >> > - > > >> > To unsubscribe, e-mail: [EMAIL PROTECTED] > > >> > For additional commands, e-mail: [EMAIL PROTECTED] > > >> > > > >> > > > >> > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M2] questions about migrating to maven
Is it not possible to alter the artifactId's finalName and the dependencies with profiles also? Then you would not get tainted builds... Not sure how to do this but I have read about it somewhere. Konstantin On 5/26/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: I am pretty sure that I am over thinking this ;) However, I am having trouble thinking how best to migrate our ant based build process to maven. Principally: - Filtering properties files for environments, and - Inter-project dependencies FILTERING PROPERTIES FILES FOR ENVIRONMENTS As with most projects, our apps use properties files for configuring a host of settings. Many of these (e.g. db settings, log4j settings, web service host:port etc) are environment specific. Our projects have properties files for various target environments, such as production, pre-production, cruisecontrol. Each developer also has a local props file that they can tailor for their particular needs (e.g. for debugging you may want to log springframework as DEBUG and suppress all others). Ant uses these files to filter the application properties. The result is a build tailored for a particular environment. Since all environment specific properties, beside the local, are source controlled we have a high degree of confidence in consistent and reproducible builds to our shared infrastructure. In maven I have been able to reproduce this behavior with profiles. However, I am not sure what to do with the resulting artifacts. Each artifact is "tainted" with environment specific properties. Should artifacts generated with "local" only be installed in each developers local repository? What about the artifacts for the testing and production environments? Should the internal repository only be used to store "production" artifacts? Should there be multiple shared internal repositories, one for production and one for pre-prod? INTER-PROJECT DEPENDENCIES Currently we have a web based application broken out into four projects: 1 - user-presentation-layer 2 - admin-presentation-layer 3 - web-service-layer 4 - common-utils Each project generates a primary artifact, and the web-service-layer also generates a client jar. Currently in order to generate a fresh build of say the user-presentation-layer, you must have the web-service-layer and common-utils checked out in your workspace. The ant build file for the user-presentation-layer will end up calling the other two build files. These builds in turn, get an update from cvs and then generating the appropriate artifact. Granted it took some time to get this process up and running, but it currently works and works pretty well. From my readings, it seems that this process is frowned upon. With maven, the appropriate process would be to "mvn scm:update install" on the web-service-layer and common-utils projects. Then run the build for the user-presentation-layer. Or better yet, have each user pull the dependencies (web-service-layer and common-utils) from an internal repository that is updated by developers checking in changes or by some source control repository. However, as noted above, because of environmental impacts, I am not sure a shared repository would work for artifacts used in development. Currently, our environment profiles only effect configuration settings. They do not modify or impact the source code directly. While the maven dependencies are a result of class dependencies, which should not be impacted by using an artifact configured for "production" versus one configured for "preproduction". What is the best way to handle this problem? I am sure people much smarter than myself have already tackled these problems and come up with very simple solutions. Any and all help sorting myself out would be really appreciated! Carlos - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
