Re: Metagen configuration issue
yes, thats what it did :) -igor On Fri, Nov 18, 2011 at 1:09 PM, Jablow, Eric R wrote: > > -Original Message- > From: Igor Vaynberg [mailto:igor.vaynb...@gmail.com] > Sent: Friday, November 18, 2011 4:04 PM > To: users@wicket.apache.org > Subject: Re: Metagen configuration issue > > sweet, thanks. i will add it to the readme > > -igor >> >> >> org.apache.maven.plugins >> maven-compiler-plugin >> >> -proc:none >> >> >> >> Perhaps the compiler was running the annotation processor itself. And, it >> works! So, with later versions of the compiler plugin, you need to keep it >> from running the annotation processor itself. >> >> Respectfully, >> Eric Jablow > > Note that Eclipse users will be unhappy unless one adds this to the pom: > > > org.apache.maven.plugins > maven-eclipse-plugin > 2.8 > > target/generated-sources/apt > > > > I have no idea about other IDEs. Perhaps the plugin I removed would have > handled that. > > Respectfully, > Eric Jablow > > This communication, along with any attachments, is covered by federal and > state law governing electronic communications and may contain company > proprietary and legally privileged information. If the reader of this > message is not the intended recipient, you are hereby notified that any > dissemination, distribution, use or copying of this message is strictly > prohibited. If you have received this in error, please reply immediately to > the sender and delete this message. Thank you. > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
RE: Metagen configuration issue
-Original Message- From: Igor Vaynberg [mailto:igor.vaynb...@gmail.com] Sent: Friday, November 18, 2011 4:04 PM To: users@wicket.apache.org Subject: Re: Metagen configuration issue sweet, thanks. i will add it to the readme -igor > > > org.apache.maven.plugins > maven-compiler-plugin > > -proc:none > > > > Perhaps the compiler was running the annotation processor itself. And, it > works! So, with later versions of the compiler plugin, you need to keep it > from running the annotation processor itself. > > Respectfully, > Eric Jablow Note that Eclipse users will be unhappy unless one adds this to the pom: org.apache.maven.plugins maven-eclipse-plugin 2.8 target/generated-sources/apt I have no idea about other IDEs. Perhaps the plugin I removed would have handled that. Respectfully, Eric Jablow This communication, along with any attachments, is covered by federal and state law governing electronic communications and may contain company proprietary and legally privileged information. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, use or copying of this message is strictly prohibited. If you have received this in error, please reply immediately to the sender and delete this message. Thank you. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Metagen configuration issue
sweet, thanks. i will add it to the readme -igor On Fri, Nov 18, 2011 at 12:23 PM, Jablow, Eric R wrote: > > > -Original Message- > From: Igor Vaynberg [mailto:igor.vaynb...@gmail.com] > Sent: Friday, November 18, 2011 2:43 PM > To: users@wicket.apache.org > Subject: Re: Metagen configuration issue > > very strange. we are using the configuration on the github page and > its working great here. > > try using the original configuration and add 2.0.5 > to the maven processor plugin, maybe you are just using an old one. > > also add this into your pom so you can get to 2.0.5 > > I think it's the version of the build-helper-maven-plugin. You have 1.3. I > was using the latest, 1.7. I just switched to 1.3 and ran. Now, a build > gives me generated-sources/apt and target/generated-sources/annotations. > > I then switched back to 1.7, and I removed the build-helper plugin. The > maven-processor-plugin usage page claims that > > Sources will be generated into target/generated-sources/apt/main/java. > Test sources into target/generated-sources/apt/test/java Both directories > will be added to the compilation path > > One thing we're missing is the code on the usage page: > > > org.apache.maven.plugins > maven-compiler-plugin > > -proc:none > > > > Perhaps the compiler was running the annotation processor itself. And, it > works! So, with later versions of the compiler plugin, you need to keep it > from running the annotation processor itself. > > Respectfully, > Eric Jablow > > This communication, along with any attachments, is covered by federal and > state law governing electronic communications and may contain company > proprietary and legally privileged information. If the reader of this > message is not the intended recipient, you are hereby notified that any > dissemination, distribution, use or copying of this message is strictly > prohibited. If you have received this in error, please reply immediately to > the sender and delete this message. Thank you. > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
RE: Metagen configuration issue
-Original Message- From: Igor Vaynberg [mailto:igor.vaynb...@gmail.com] Sent: Friday, November 18, 2011 2:43 PM To: users@wicket.apache.org Subject: Re: Metagen configuration issue very strange. we are using the configuration on the github page and its working great here. try using the original configuration and add 2.0.5 to the maven processor plugin, maybe you are just using an old one. also add this into your pom so you can get to 2.0.5 I think it's the version of the build-helper-maven-plugin. You have 1.3. I was using the latest, 1.7. I just switched to 1.3 and ran. Now, a build gives me generated-sources/apt and target/generated-sources/annotations. I then switched back to 1.7, and I removed the build-helper plugin. The maven-processor-plugin usage page claims that Sources will be generated into target/generated-sources/apt/main/java. Test sources into target/generated-sources/apt/test/java Both directories will be added to the compilation path One thing we're missing is the code on the usage page: org.apache.maven.plugins maven-compiler-plugin -proc:none Perhaps the compiler was running the annotation processor itself. And, it works! So, with later versions of the compiler plugin, you need to keep it from running the annotation processor itself. Respectfully, Eric Jablow This communication, along with any attachments, is covered by federal and state law governing electronic communications and may contain company proprietary and legally privileged information. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, use or copying of this message is strictly prohibited. If you have received this in error, please reply immediately to the sender and delete this message. Thank you. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Metagen configuration issue
very strange. we are using the configuration on the github page and its working great here. try using the original configuration and add 2.0.5 to the maven processor plugin, maybe you are just using an old one. also add this into your pom so you can get to 2.0.5 sonatype-repo https://oss.sonatype.org/content/repositories/releases -igor On Fri, Nov 18, 2011 at 11:38 AM, Jablow, Eric R wrote: >>From: Igor Vaynberg [mailto:igor.vaynb...@gmail.com] > Sent: Friday, November 18, 2011 2:21 PM > To: users@wicket.apache.org > Subject: Re: Metagen configuration issue > > try removing the configuration block of the maven-processor-plugin and > change the location of the helper plugin to > generated-sources/annotations > > --- > > This didn't work. Now, I have two identical directories, > generated-sources/annotations, and generated-sources/apt. > > I cleaned my project, and then I replaced generated-sources/annotations with > generated-sources/apt in the build-helper-maven-plugin. That failed, so I put > generated-sources/apt in the maven-processor-plugin. I still have > generated-sources/annotations and generated-sources/apt > > Eric > . > This communication, along with any attachments, is covered by federal and > state law governing electronic communications and may contain company > proprietary and legally privileged information. If the reader of this > message is not the intended recipient, you are hereby notified that any > dissemination, distribution, use or copying of this message is strictly > prohibited. If you have received this in error, please reply immediately to > the sender and delete this message. Thank you. > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
RE: Metagen configuration issue
>From: Igor Vaynberg [mailto:igor.vaynb...@gmail.com] Sent: Friday, November 18, 2011 2:21 PM To: users@wicket.apache.org Subject: Re: Metagen configuration issue try removing the configuration block of the maven-processor-plugin and change the location of the helper plugin to generated-sources/annotations --- This didn't work. Now, I have two identical directories, generated-sources/annotations, and generated-sources/apt. I cleaned my project, and then I replaced generated-sources/annotations with generated-sources/apt in the build-helper-maven-plugin. That failed, so I put generated-sources/apt in the maven-processor-plugin. I still have generated-sources/annotations and generated-sources/apt Eric . This communication, along with any attachments, is covered by federal and state law governing electronic communications and may contain company proprietary and legally privileged information. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, use or copying of this message is strictly prohibited. If you have received this in error, please reply immediately to the sender and delete this message. Thank you. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Metagen configuration issue
try removing the configuration block of the maven-processor-plugin and change the location of the helper plugin to generated-sources/annotations -igor On Fri, Nov 18, 2011 at 10:57 AM, Jablow, Eric R wrote: > I've cut and pasted the Metagen configuration listed in > https://github.com/42Lines/metagen into my project pom, and these > declarations are generating the metamodels twice: in > target/generated-sources/annotations, and in target/metamodel. What must I do > to cut out one of the metamodel locations? I'm a Maven novice. > > Respectfully, > Eric Jablow > > This communication, along with any attachments, is covered by federal and > state law governing electronic communications and may contain company > proprietary and legally privileged information. If the reader of this > message is not the intended recipient, you are hereby notified that any > dissemination, distribution, use or copying of this message is strictly > prohibited. If you have received this in error, please reply immediately to > the sender and delete this message. Thank you. > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Metagen configuration issue
I've cut and pasted the Metagen configuration listed in https://github.com/42Lines/metagen into my project pom, and these declarations are generating the metamodels twice: in target/generated-sources/annotations, and in target/metamodel. What must I do to cut out one of the metamodel locations? I'm a Maven novice. Respectfully, Eric Jablow This communication, along with any attachments, is covered by federal and state law governing electronic communications and may contain company proprietary and legally privileged information. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, use or copying of this message is strictly prohibited. If you have received this in error, please reply immediately to the sender and delete this message. Thank you.
