release and latest no longer updated?

Any ideas why release and latest in the maven-metadata.xml for my artifact are no longer being updated? I'm just incrementing the third place (2.4.42 -- 2.4.43) and the maven-deploy-plugin is no longer updating the maven-metadata.xml in my repository with new releases as being latest and release

RE: Maven - Plugin LogLevel

What's the easiest way to temporarily hack the plexus logging level to debug? The maven-filtering classes are performing poorly and I'm trying to debug my issue and the existing debug messages would be good enough if I could just see them. Thanks, Brian Brian E Fox wrote: Unfortunately not

RE: Maven - Plugin LogLevel

those classes? I tried tracing back through plexus-logging but couldn't find where the loggers are initialized. Brian E Fox wrote: Does mvn -x give you what you want? -Original Message- From: jaxzin [mailto:brian.r.jack...@espn3.com] Sent: Monday, January 26, 2009 2:34 PM

Re: Reusing assembly descriptors aka. sharing them between projects

Excellent John!! That's exactly what I was looking for. I definitely need to read through the Sonatype book completely. John Stoneham wrote: Off the top of my head the only viable idea I have is to deploy it in a zip to the Maven repo and use dependency plugin to resolve and unpack

Reusing assembly descriptors aka. sharing them between projects

I've created a standard way for our projects to be bundled for deployment using an assembly descriptor. I'd like all our projects to use it unchanged without having to copy it into each project. Any suggestions? Off the top of my head the only viable idea I have is to deploy it in a zip to

Module site descriptor ignored in multi-module project?

I've deployed the site of a multi-module project and found that the sites for the modules are using the site descriptor for the top-level project rather than each modules site descriptor that I've defined. Is that the expected behavior? -- View this message in context:

Re: Module site descriptor ignored in multi-module project?

are seeing? - Brett On 16/10/2008, at 7:17 AM, jaxzin wrote: I've deployed the site of a multi-module project and found that the sites for the modules are using the site descriptor for the top-level project rather than each modules site descriptor that I've defined

Re: Module site descriptor ignored in multi-module project?

thought it was fixed. - Brett On 16/10/2008, at 7:33 AM, jaxzin wrote: No, it's ignoring the module's site descriptor (mymodule/src/site/ site.xml) completely. We do take advantage of the site descriptor inheritance and that's working properly with inheriting the site descriptor from

Re: Module site descriptor ignored in multi-module project?

Reported http://jira.codehaus.org/browse/MSITE-364. Thanks again for the help. brettporter wrote: If there isn't one already, yes please. On 16/10/2008, at 7:40 AM, jaxzin wrote: I can confirm that downgrading to 2.0-beta-5 fixes my issue and the module's site is generated

Adding plugin dependencies via a profile

I'm writing a custom enforcer rule to enforce that my build contains no snapshot dependencies. I only want to run the rule in a profile call 'release'. But since I'm already using the enforcer plugin in my build outside the profile it can't find my custom rule if I declare the plugin dependency

Re: Adding plugin dependencies via a profile

on the custom rule. jaxzin wrote: I'm writing a custom enforcer rule to enforce that my build contains no snapshot dependencies. I only want to run the rule in a profile call 'release'. But since I'm already using the enforcer plugin in my build outside the profile it can't find my custom

Re: Adding project dependencies and generated classes to classpath of my plugin

So after trying out more complex scenarios with my first solution (like calling Class.forName from a class that was injected by the Plexus container) it turned out it wasn't a complete solution. So learned alot more about Plexus and the ClassWorlds framework and I ended up discovering a much

Classworlds uberjar vs. assembly jar-with-dependencies

Does anyone have some insight as to why the uberjar functionality of the Classworlds project hasn't gotten much support with Maven 2? http://classworlds.codehaus.org/uberjar.html It seems like a really useful setup as it preserves some of the information that the assembly plugin strips, such as

Re: Override an @component hint in the pom?

Thanks Jason, that's exactly what I'm looking for. Jason van Zyl-2 wrote: You can look at the enforcer plugin and the shade plugin for examples of letting users specify custom/specific implementations of components with their own configurations. On 24-Jul-08, at 9:50 PM, jaxzin

RE: Override an @component hint in the pom?

and hold a reference to it. If you look at the ounce code, you'll see this happening. -Original Message- From: jaxzin [mailto:[EMAIL PROTECTED] Sent: Friday, July 25, 2008 1:13 PM To: users@maven.apache.org Subject: Re: Override an @component hint in the pom? Thanks Jason, that's

Re: Adding project dependencies and generated classes to classpath of my plugin

templates in my language for me. Luckily they were already setup to accept an alternate ClassLoader. For that reason, your mileage my vary and you may need to try and pass it to Thread.currentThread().setContextClassLoader(ClassLoader) though I tried that and it did not work for me. jaxzin wrote

Override an @component hint in the pom?

I'm trying to create a mojo that is itself pluggable so that my users can select an implementation of an interface to use. I'm reading about plexus and the @component annotation for mojo fields. It appears the plexus component's roleHint can only be set in the annotation and not in the pom

Adding project dependencies and generated classes to classpath of my plugin

I'm writing a plugin to precompile templates for a language similar to JSP. The plugin needs the dependencies and compiled classes of the project its running in. Does anyone have an example of how to add the containing project's dependencies and target/classes directory to the classpath of the

Re: Assembly plugin resolves dependencies differently than the dependency plugin

So I created an example and reported the bug in the assembly plugin. http://jira.codehaus.org/browse/MASSEMBLY-270 jaxzin wrote: I think here is the case of what is happening: A depends on commons-collection 3.0 B depends on A B declares in its dependencyMgmt to use commons

Assembly plugin resolves dependencies differently than the dependency plugin

Has anyone else experience the following. I run dependency:resolve on my project and it reports that it resolve one my dependencies to version 1.6.2 but yet when I run the assembly a different version 1.6.1 is included? How could this possibly be? Don't they both use the same code to resolve

Re: Assembly plugin resolves dependencies differently than the dependency plugin

this as a small example to confirm. jaxzin wrote: Has anyone else experience the following. I run dependency:resolve on my project and it reports that it resolve one my dependencies to version 1.6.2 but yet when I run the assembly a different version 1.6.1 is included? How could this possibly

Use of AntRun causes clean to fail for multiproject?

So I've whittled my way down to a very simple multiproject that exhibits the same failure I'm seeing on a larger-scale project. Attached is the example. http://www.nabble.com/file/p14017171/test.zip test.zip Here's the summary. The project consists of project 'test' with modules 'test-a' and

How does Maven resolve the RELEASE version?

I've started using the RELEASE keyword to define dependency and parent versions. Does anyone know of documentation that explains how Maven resolves what the latest RELEASE version of a dependency is? -- View this message in context:

Assembly includes 'wrong' version of dependencies

I've created a jar-with-dependencies assembly and it appears to be including a different version of my dependencies compared to the output of mvn project-info-reports:dependencies or the versions I've defined in the dependencyManagement section of my pom. What am I missing? Doesn't the

Re: Setting jar order in maven.compile.classpath

Thanks Manos, What I've found so far by looking at the source is that its dependent on how the Set that MavenProject.getArtifacts() orders itself. I still haven't found which impl of Set is used. That would tell us how predictable the order is. My guess is its a HashSet and so the order will

Re: Setting jar order in maven.compile.classpath

, at least) is forcing you to use Maven! And its open source, so if you need this feature, you can go in and add it yourself. [1] http://maven.apache.org/what-is-maven.html Wayne On 7/25/07, jaxzin [EMAIL PROTECTED] wrote: That's such a cop-out. I've got legacy jars that my project

Re: Setting jar order in maven.compile.classpath

That's such a cop-out. I've got legacy jars that my project depends on that happen to have some overlap in the classes. What's so wrong with AT LEAST obeying the declared order of the dependencies in the POM instead of the random order that currently exists? Wayne Fay wrote: You can't. Set

Re: changelog and perforce

on the command-line? jaxzin wrote: I'm trying to use the changelog with Perforce but after some investigation it appear that the SCM provider for Perforce in not creating the necessary client. The changelog plugin executes this command: p4 -p perforce:1666 -c JACKSBRR-LW-CT-JACKSBRR

Re: changelog and perforce

the changelog report plugin forks the lifecycle. So I'm pretty sure I'm stuck without a bug fix to changelog. I filed a JIRA issue for it: http://jira.codehaus.org/browse/MCHANGELOG-66. jaxzin wrote: Well, I think I fixed the problem but its not ideal. I got the scm:changelog goal to work if I

Re: Compilation issues

The problem (caused by a cut/paste error) was that my packaging in the POM was 'pom' instead of 'jar'. jaxzin wrote: Anyone know why mvn compile runs with no goals needed for project - skipping but mvn compiler:compile runs just fine for my project? Thanks, Brian -- View