please deploy a snapshot, make sure you have your server setting to 775.
I will run your snapshot against my production.
Thank you for putting time to get this going.
-Dan
On 9/11/06, Brett Porter <[EMAIL PROTECTED]> wrote:
Thanks Brian!
- Brett
On 12/09/2006, at 12:17 PM, Brian E. Fox wr
Thanks Brian!
- Brett
On 12/09/2006, at 12:17 PM, Brian E. Fox wrote:
Must have been a psychic connection here. I finally started working on
this tonight and have resolved many issues before seeing this email. I
have also finally been using 2.0 in production with no problems...it's
at least as
Hi,
I'd like to propose moving the plugin-tools and reporting-impl to
shared, to decouple plugin releases from the maven core releases.
Right now, building the plugins is blocked around maven 2.0.5.
The one downside to this is that the bootstrap requires the plugin
tools to build plugins
Must have been a psychic connection here. I finally started working on
this tonight and have resolved many issues before seeing this email. I
have also finally been using 2.0 in production with no problems...it's
at least as stable as 1.0 from what I can tell. Once I get the existing
patches applie
No, the plugin-plugin can only scan source files for the annotations and doesn't
re-use parent class info. You'll need to redefine that parameter if you want to
use it in the xdoclet plugin.
It would be neat to let the plugin-plugin scan the parent class'
META-INF/maven/plugin.xml
and add those
Xdoclet plugin is subclassing a class in the Antrun plugin. This
antrun class has an injected property that works when used as part of
an antrun execution but is null when xdoclet plugin is executed.
Should this work?
public abstract class AbstractAntMojo
extends AbstractMojo
{
/**
*
You can test a build generated by our CI :
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/
Arnaud
On 9/9/06, Todd Nine <[EMAIL PROTECTED]> wrote:
Sure did, here's the settings.xml I'm using
Also, this seems to be a bug, I've found this issue in Jira
http://jira.codehaus.org
