Skip to content
This repository has been archived by the owner on Jul 30, 2021. It is now read-only.

outputDirectory not cleaned during incremental updates or project clean in Eclipse #15

Open
benze opened this issue Nov 22, 2012 · 6 comments

Comments

@benze
Copy link

benze commented Nov 22, 2012

I don't know if this is a plugin issue, a configuration issue, or just plain not feasible. But I've noticed that when I make changes to my classes the plugin will make incremental changes to the Q-classes. That is great.

However, if I clean the project, then all the generated files in the outputDirectory remain. Furthermore, if I refactor a classname, the old Q-class remains even though the new Q class is generated as well. I can, of couse, clean the outputDirectory by issuing: mvn clean

I currently have my outputDirectory configured as:
target/generated-sources/apt

Is this a configuration issue on my behalf, or if it is an issue in the plugin.

I'm using m2e 1.2, and plugin 1.0.7.

Thanks,

Eric

@timowest timowest reopened this Nov 22, 2012
@timowest
Copy link
Member

However, if I clean the project, then all the generated files in the outputDirectory remain. Furthermore, if I refactor a classname, the old Q-class remains even though the new Q class is generated as well.

I wil take a look if this can be better handled for IDE based builds.

@benze
Copy link
Author

benze commented Nov 22, 2012

I also noticed in refactoring a class name, that although the new QClass is properly generated, all code still refers to the old Q class. I don't know if there would be a way to indicate to Eclipse that the Q class' name is being changed by the Entity class name change and to include it in the refactor process.

@timowest
Copy link
Member

It's possible to get the deleted source in the plugin but I don't yet how to get access to the generated files.

@luisfpg
Copy link

luisfpg commented Aug 21, 2014

I have worked-around this by creating a new Ant builder in the Eclipse project, and made it delete every generated sources in a given target. Then, in the builder Targets tab, select that target's name in the During a Clean field.
Then, any Project > clean will properly remove and trigger the re-generation of those files.

@timowest
Copy link
Member

@benze Could you also try this pull request #27

It populates the output directory now in a smarter way.

@benze
Copy link
Author

benze commented Oct 12, 2014

I've been moved onto another project at the moment (which is much different
technology), so wouldn't be of much help validating the plugin at the
moment. As soon as I get a chance to get back to a QDSL project, I'll give
it a shot.

Thx!

Eric

On Sat, Oct 11, 2014 at 9:58 AM, Timo Westkämper [email protected]
wrote:

@benze https://github.com/benze Could you also try this pull request #27
#27

It populates the output directory now in a smarter way.


Reply to this email directly or view it on GitHub
#15 (comment)
.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants