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 annoying to me is because I indeed do setup
additional project settings that I would not want to have to redo after each
build.
I'll try this out with pax:clean instead. I'm not really sure where Eclipse
stores my settings. I assume that some of what I do is in the .classpath
file, etc.
So, is there anyway to influence the contents of these files from my pom (or
whatever)?
> > However, when I build normally after that ("mvn clean
> > install") all of the errors that went away show up
> > again, so I need to regenerate the eclipse files all
> > over again.
> correct - it's actually the "additional" content that
> you need to regenerate, not the Eclipse config (ie.
> when you embed jars / other non-local content)
Ok. I don't mind, except for the caveat above: I don't want to "lose" the
additional config stuff.
> if generating this content on each install causes
> you too much grief, feel free to raise a feature
> request* to be able to set the location of the "unpacked
> additional content"
Nah, regeneration is not the problem. It's the fact that I lose all the
custom config on my projects.
Can you tell me if there's a way of influencing this stuff? If not, then
I'll file a feature request.
Thanks!
David
_______________________________________________
general mailing list
general@lists.ops4j.org
http://lists.ops4j.org/mailman/listinfo/general
