.
Matthew
>
> From the reported line number it must be a problem with some macro in
> an xdoc file. Can you try to track it down and attach a reproducible
> test case to jira?
>
> Thanks,
> -Lukas
>
>
> Matthew Pocock wrote:
>> Hi,
>>
>> When bui
On Tuesday 13 May 2008, Lukas Theussl wrote:
> Matthew Pocock wrote:
> > Ah, thanks - this works well.
> >
> > Is there a short-hand for including an entire file? I seem to need to
> > supply the id regardless.
>
> This is possible in beta-1 only (not yet rele
> andy law (RI) wrote on Thursday, January 25, 2007 1:47 PM:
>
> [snip]
>
>> Has anyone else done anything as complex (read: STUPID) as
>> this and can
>> anyone suggest any sensible, practical solutions?
>
> Use a dynamic mock implementation like jMock. With the CGLIB extension you
> may even mock
I am having trouble with adding tools.jar to my classpath. I'm compiling
against both the javadoc and apt APIs.
Tinkering with the bootclasspath or manually putting tools.jar into my local
repository are both icky - they work for me but not for anybody else building
the project. Since every jdk
On Monday 06 June 2005 17:29, Emmanuel Venisse wrote:
> you can run "clean" goal before it.
>
> Emmanuel
Not sure that's practical in all cases. In any case, it's just the javac
target that needs a pre-clean. None of the other steps do. I'll try adding
clean as a preGoal for java:compile and see
Hi,
I've got a maven project that builds a jar that must always appear in the
bootclasspath. It's a patch for java.nio, and there's now way to get stuff
working with it added to the normal classpath. Is there some way in the
project.xml file to indicate this so that whenever it appears as a
de
Hi,
I've been using maven to build lots of my projects. Some of these use apt
rather than javac for building. For apt to work propperly, it often needs to
run over all of the source files, not just the dirty ones. Is there a flag to
pass into the javac pluggin to get it to build everything?
T
Hi,
I've been using javacc to process some java5 code. To get this running I
needed to do a bit of hacking around in the pluggin and its dependancies.
Firstly, I manually added javacc-4.0-beta-1.jar to .maven/repository and then
I manually edited maven-javacc-plugin-1.1/project.xml to have a de