Re: authorization denied
Brett, and Stephen, Thanks for your quick response. This all makes sense. Setting guest's role to observer worked. But backing up a moment, in the case where I use my own account, not the guest accout, from where would maven get the username/password to send to archiva? From the settings file? If so, sorry, I am not finding it in the settings.xml guide. I don't think proxy is for this purpose. Does maven use the process id to get the user name? If so, how does it get the password? Thanks, John -- View this message in context: http://www.nabble.com/authorization-denied-tf3145308.html#a8729556 Sent from the archiva-users mailing list archive at Nabble.com.
assembly plugin and test scope
We have an artifact that is used only during testing: our unit test framework. It has a compile time dependency on xmlunit, junit artifacts. I want to assemble a production artifact that has a test scope dependency on our unit test framework artifact. The jars-with-dependencies descriptor, which includes dependencies with 'runtime' scope, includes the unit test framework and its compile time dependencies (junit, xmlunit). I wrote a one-off of the jars-with-dependencies descriptor to try to define one which will not include test scoped dependencies, but what else can I do beyond setting the scope of a dependency set to 'runtime'?? I think I have to explicitly exclude the unit test framework and its dependencies. Any comment? I'm using assembly plugin 2.1. Thanks, John -- View this message in context: http://www.nabble.com/assembly-plugin-and-test-scope-tf3119201s177.html#a8641820 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: codehaus xmlbeans and eclipse
Gregory, Thanks for your reply. For the record, I found a acceptable work around. I configured the xmlbeans plugin to create a schema jar file in the target directory. Then I put this jar file on my eclipse classpath. I haven't checked yet whether this configuration affects the rest of the build in maven. However, it looks like the xmlbeans plugin still generates source and bizarre schemaorg_apache_xmlbeans directories , so I believe this is no impact on the rest of the maven build. Thanks again, John -- View this message in context: http://www.nabble.com/codehaus-xmlbeans-and-eclipse-tf3029668s177.html#a8434372 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
codehaus xmlbeans and eclipse
I have some issues with xmlbeans and eclipse. Is anyone successful? 1) I have a maven project with xml beans generated code. The xmlbeans maven plugin creates a directory 'target/classes/schemaorg_apache_xmlbeans. Eclipse removes this directory on a 'project clean' or build classpath configuration. 2) After losing target/classes/schemaorg_apache_xmlbeans, the xmlbeans maven plugin will not recreate it, because the other directory it creates, target/xmlbeans-source is still present. Removing target/xmlbeans-source from command line causes eclipse to automatically remove xmlbeans-source from the source path. So, after regenerating both subdirectories, restoring xmlbeans-source as a source directory causes the first problem above to occur. 3) Eclipse is not 'seeing' target/classes/schemaorg_apache_xmlbeans and so the generated source code in xmlbeans-source cannot be built. Specifically, schemaorg_apache_xmlbeans/system/big honkin' dir name/TypeSystemHolder is NOT getting resolved. I am using eclipse 3.2.1, xmlbeans-maven-plugin 2.0, maven 2.0.4, eclipse maven plugin 2.3. Is anyone using xmlbeans, maven and eclipse with success? Are you struggling with this? Is there workaround? Thanks, John -- View this message in context: http://www.nabble.com/codehaus-xmlbeans-and-eclipse-tf3029668s177.html#a8418392 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: assembly permutations
John, Thanks. The functionality of 2.2-SNAPSHOT appears to have what I could use: point the assembly plugin at a set of assembly descriptors, each containing a different assembly permutation. I guess this would generate a distinct assembly for each descriptor. Hopefully, this functionality is not dependent on a multlevel project. Assume that the clients are not in the same project as the service module. The clients and service are all on unique release schedules - a multi-level project constrains all modules on the same release schedule (if I'm wrong, let me know, maybe I will post a new message on this question.) Your OTOH is helpful, too. I will explore both. In either case, because the artifacts to assemble are in seperate projects, I need to create a special assembly project. Regards, John John Casey wrote: If you're using 2.2-SNAPSHOT of the assembly plugin, you should have quite a few options for including the binaries of modules. This means that you could, in theory, setup the assembly plugin to run once from the top level project, and point it at a set of assembly descriptors, each containing a different assembly permutation. However, there are two drawbacks to this approach: 1. The improved ModuleSet processing for the 2.2-SNAPSHOT version is not documented yet. It's on my TODO list, but I haven't completed it. 2. Because of a quirk with the way Maven processes multimodule builds, and its effect on the assembly logic, you may have to call it in this way: mvn package assembly:assembly to ensure that the module artifacts are produced *before* the assembly plugin tries to add them to the archive. OTOH, you could create assembly-producing projects for each permutation, and list the appropriate base/client-1/client-n as dependencies...which would probably be the simplest solution using the 2.1 assembly plugin. HTH, John On 11/17/06, Lee Meador [EMAIL PROTECTED] wrote: A more maveny way IMHO would have a project for each thing you are trying to build. That would include the base, each client and each assembly.Tobuld an assembly you go to its project folder and type: mvn assembly:assembly This goes against our built-in lazyness where we want to have as few folders full of stuff as possible. But it works well and organizes things well. -- Lee On 11/17/06, flyboy [EMAIL PROTECTED] wrote: Here is a question about maven assembly. Maybe it is a best practice question. Say there is a Base project that provides common services. Then there are multiple projects (Client-1, Client-2,...) which use the common service. Say I want to build assemblies which include the Base and various different permutations of Clients. Example: Assembly-1 contains Base, Client-1, Client-3. Assembly-2 contains Base, Client-3, Client-4. Assembly-3 contains Base, Client-1, Client-2, Client-4. and on and on All clients depend on Base. Each assemlbly would contain 1 or more clients. I think I will create an seperate project, AssemblyProy. The pom would describe all clients as dependencies. The pom would parameterize the assembly descriptor and the assembly name. Each descriptor would represent a diffeferent combintation of Clients. To build an assembly, would run: mvn -Passembly=Assembly-1 assemble Is this THE WAY in maven? If not, what is? If there currently isn't a WAY, is the above reasonable? Are there alternatives? Thanks, John -- View this message in context: http://www.nabble.com/assembly-permutations-tf2655047s177.html#a7406601 Sent from the Maven - Users mailing list archive at Nabble.com. -- -- Lee Meador Sent from gmail. My real email address is lee AT leemeador.com -- View this message in context: http://www.nabble.com/assembly-permutations-tf2655047s177.html#a7421347 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: assembly permutations
Lee, Thanks. OK. I see that the idea of using a command line parameter to specify the assembly-descriptor is not a 'best' or 'good' practice. Regards, John Lee Meador-3 wrote: A more maveny way IMHO would have a project for each thing you are trying to build. That would include the base, each client and each assembly.To buld an assembly you go to its project folder and type: mvn assembly:assembly This goes against our built-in lazyness where we want to have as few folders full of stuff as possible. But it works well and organizes things well. -- Lee -- -- Lee Meador Sent from gmail. My real email address is lee AT leemeador.com -- View this message in context: http://www.nabble.com/assembly-permutations-tf2655047s177.html#a7421505 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
assembly permutations
Here is a question about maven assembly. Maybe it is a best practice question. Say there is a Base project that provides common services. Then there are multiple projects (Client-1, Client-2,...) which use the common service. Say I want to build assemblies which include the Base and various different permutations of Clients. Example: Assembly-1 contains Base, Client-1, Client-3. Assembly-2 contains Base, Client-3, Client-4. Assembly-3 contains Base, Client-1, Client-2, Client-4. and on and on All clients depend on Base. Each assemlbly would contain 1 or more clients. I think I will create an seperate project, AssemblyProy. The pom would describe all clients as dependencies. The pom would parameterize the assembly descriptor and the assembly name. Each descriptor would represent a diffeferent combintation of Clients. To build an assembly, would run: mvn -Passembly=Assembly-1 assemble Is this THE WAY in maven? If not, what is? If there currently isn't a WAY, is the above reasonable? Are there alternatives? Thanks, John -- View this message in context: http://www.nabble.com/assembly-permutations-tf2655047s177.html#a7406601 Sent from the Maven - Users mailing list archive at Nabble.com.
m2: package, war: moving webapp file, or resource requires clean?
Hi, 1) I run mvn clean package 1) I rename a webapp file, for example, from src/main/webapp/old-app.html to src/main/webapp/new-app.html 2) I run mvn package Result: both old-app.html and new-app.html exist in war output (webapp directory and war file). The same kind of thing happens when I use webResources. If I rename a file in the directory of webResources, both old and new files exist in war output. 'mvn clean package' is the only way I know of removing the old resource file from the target directory, but that forces a whole rebuild, which I don't want. Any thoughts? Thanks, John -- View this message in context: http://www.nabble.com/m2%3A-package%2C-war%3A-moving-webapp-file%2C-or-resource-requires-clean--tf2240827.html#a6214767 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
m2: container config using maven-war-plugin
Hi,
I don't know if what I did is best, so I'm posting for comments. I've read
some of the postings on this list regarding resource filtering in war
plugin. I've been able to get it to work using version 2.0.1 of the
plugin.
In some other posting, the point is made that web resources are not really
resources. This is fine for me, but I have need to filter the web.xml and
context.xml files.
I noticed that if I create src/main/resources/META-INF/context.xml and
src/main/resources/WEB-INF/web.xml, I get two copies of each in my war. One
copy is from the action of the resource plugin and appears in
${webappDirectory}/WEB-INF/classes/META-INF and WEB-INF , the other from the
action of the warResources that I configured to suck from src/main/resources
and appears where I expect in ${webappDirectory}/META-INF and WEB-INF.
To avoid this:
1) I put the files in src/main/container/META-INF and WEB-INF
2) I configure webResources to filter src/main/container.
3) My src/main/resources is empty
4) I have other files, which do not need to be filtered, in
src/main/webapp/WEB-INF
Regards,
John
--
View this message in context:
http://www.nabble.com/m2%3A-container-config-using-maven-war-plugin-tf2204582.html#a6105417
Sent from the Maven - Users forum at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
