> the only thing I can suggest is to build from the top and save the
> .project / .classpath files, then build locally and save them again.
> (perhaps also save the manifest file)
>
> then compare the 2 sets of files to spot any differences - if these
> files are identical then it's another probl
>
> looks like this option appeared in the recently released 2.5
> maven-eclipse-plugin
> (see MECLIPSE-79) whereas the pax-plugin currently extends 2.4, so an
> update
> would be needed to support this.
Ok, cool! That answers that, then. :-)
> Are the issues I mention above related to
2008/4/28 David Leangen <[EMAIL PROTECTED]>:
>
> > When I do a top-level build
> >
> > is this a top-level build in Maven or Eclipse?
>
> Maven.
>
> So, I build in maven, then when I refresh in Eclipse, the problematic
> project no longer compiles (in Eclipse).
>
> However, if I build from
2008/4/28 David Leangen <[EMAIL PROTECTED]>:
>
> Hi, Stuart.
>
> > However, I am still getting lots of compiler warnings, and any
> > changes I
> > make to my .classpath file are being overwritten.
> >
> > ideally you shouldn't need to change the classpath,
> > can you list
> When I do a top-level build
>
> is this a top-level build in Maven or Eclipse?
Maven.
So, I build in maven, then when I refresh in Eclipse, the problematic
project no longer compiles (in Eclipse).
However, if I build from the project level (in maven) and refresh in
Eclipse, no proble
Hi, Stuart.
> However, I am still getting lots of compiler warnings, and any
> changes I
> make to my .classpath file are being overwritten.
>
> ideally you shouldn't need to change the classpath,
> can you list the changes you're making that aren't in
> the generated .cl
2008/4/28 David Leangen <[EMAIL PROTECTED]>:
>
> > So, is there anyway to influence the contents of these files
> > from my pom (or
> > whatever)?
> >
> >
> > yes, see the docs for the maven-eclipse-plugin (those configuration
> > options can be used with the maven-pax-plug
2008/4/28 David Leangen <[EMAIL PROTECTED]>:
> > Ok, you're right. I am no longer getting build errors when I add the
> > following to my pom:
>
> Well, I lied.
>
> When I do a top-level build
is this a top-level build in Maven or Eclipse?
> , Eclipse complains that there is no such
> class or
> Ok, you're right. I am no longer getting build errors when I add the
> following to my pom:
Well, I lied.
When I do a top-level build, Eclipse complains that there is no such
class org.example.com.json.JSonObject. It is (for whatever reason)
searching in the current project (which has a org.exa
> So, is there anyway to influence the contents of these files
> from my pom (or
> whatever)?
>
>
> yes, see the docs for the maven-eclipse-plugin (those configuration
> options can be used with the maven-pax-plugin, because it extends
> the eclipse mojo). But I
2008/4/26 David Leangen <[EMAIL PROTECTED]>:
>
> Thanks a lot, Stuart.
>
> I'll try this out when I get back into the office on Monday.
>
> In the meantime, some questions/comments (inline)...
>
> > > FYI, "mvn pax:clean" will also remove the generated
> > > stuff (except .settings)
>
> Ok, maybe
Thanks a lot, Stuart.
I'll try this out when I get back into the office on Monday.
In the meantime, some questions/comments (inline)...
> > FYI, "mvn pax:clean" will also remove the generated
> > stuff (except .settings)
Ok, maybe this is what I need... not sure.
The main reason why this is a
2008/4/25 David Leangen <[EMAIL PROTECTED]>:
>
> Stuart,
>
> Thanks for the help over IM.
>
> More troubles...
>
> After I run "mvn eclipse:clean pax:eclipse", the project files are now
> generated correctly.
>
FYI, "mvn pax:clean" will also remove the generated stuff (except .settings)
However,
13 matches
Mail list logo
