Re: Source directory for the maven-apt-plugin plugin
Le 25 avr. 2013 16:26, Stephane-3 mittiprove...@yahoo.se a écrit :
[Snip]
I'm then trying to specify a source directory, with the following:
sourceDirectory${basedir}/core/src/main/java/com/thalasoft/learnintouch/core/jpa/domain/sourceDirectory
Why do you define sourceDirectory? Its default value is already
${basedir}/src/main/java
-- Baptiste
Re: Source directory for the maven-apt-plugin plugin
Hello,
Yes, but then my source directory is not found, because it sits in the core/
child module as I explained in my original post.
Kind Regards,
Stephane
De : Baptiste MATHUS [via Maven] ml-node+s40175n575438...@n5.nabble.com
À : Stephane-3 mittiprove...@yahoo.se
Envoyé le : Vendredi 26 avril 2013 8h48
Objet : Re: Source directory for the maven-apt-plugin plugin
Le 25 avr. 2013 16:26, Stephane-3 [hidden email] a écrit :
[Snip]
I'm then trying to specify a source directory, with the following:
sourceDirectory${basedir}/core/src/main/java/com/thalasoft/learnintouch/core/jpa/domain/sourceDirectory
Why do you define sourceDirectory? Its default value is already
${basedir}/src/main/java
-- Baptiste
If you reply to this email, your message will be added to the discussion
below:http://maven.40175.n5.nabble.com/Source-directory-for-the-maven-apt-plugin-plugin-tp5754338p5754382.html
To unsubscribe from Source directory for the maven-apt-plugin plugin, click
here.
NAML
--
View this message in context:
http://maven.40175.n5.nabble.com/Source-directory-for-the-maven-apt-plugin-plugin-tp5754338p5754383.html
Sent from the Maven - Users mailing list archive at Nabble.com.
Re: Source directory for the maven-apt-plugin plugin
OK, I think I misread your first message.
So, it seems you're trying to run the plugin from the parent to access
sources from a child module.
If so, then you should know it's a bad idea. Modules should generally be
independent in their execution.
If that plugin is needed in your core module, then configure it just in
that plugin.
Here, the first error is related to the fact the plugin is trying to
execute for the parent pom, but there's logically no sources. So the
execution stops there.
Then I think the second one is the core module execution inheriting the
parent configuration, but for this module ${basedir} is already containing
core, so there's core twice.
Cheers
2013/4/26 Stephane-3 mittiprove...@yahoo.se
Hello,
Yes, but then my source directory is not found, because it sits in the
core/ child module as I explained in my original post.
Kind Regards,
Stephane
De : Baptiste MATHUS [via Maven] ml-node+s40175n575438...@n5.nabble.com
À : Stephane-3 mittiprove...@yahoo.se
Envoyé le : Vendredi 26 avril 2013 8h48
Objet : Re: Source directory for the maven-apt-plugin plugin
Le 25 avr. 2013 16:26, Stephane-3 [hidden email] a écrit :
[Snip]
I'm then trying to specify a source directory, with the following:
sourceDirectory${basedir}/core/src/main/java/com/thalasoft/learnintouch/core/jpa/domain/sourceDirectory
Why do you define sourceDirectory? Its default value is already
${basedir}/src/main/java
-- Baptiste
If you reply to this email, your message will be added to the discussion
below:
http://maven.40175.n5.nabble.com/Source-directory-for-the-maven-apt-plugin-plugin-tp5754338p5754382.html
To unsubscribe from Source directory for the maven-apt-plugin plugin,
click here.
NAML
--
View this message in context:
http://maven.40175.n5.nabble.com/Source-directory-for-the-maven-apt-plugin-plugin-tp5754338p5754383.html
Sent from the Maven - Users mailing list archive at Nabble.com.
--
Baptiste Batmat MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor ! nbsp;!
jsp compilation
Hi, I am using jspc-maven-plugin for compiling jsp files to avoid runtime exceptions. These compiled Java files will not get packaged in war file. This build is just for verification. Currently how it is building is if i give mvn install after compiling jsps, war file is getting created. But my requirement is jsp compilation should happen after pckaging war file, both these activities should be independent. How to separate packaging war file and jsp compilation as separate actions? Any inputs, highly appreciated.. Thanks Virg
Re: jsp compilation
Well, seems like you just want to bind jspc-m-p to a phase after package? Maybe bind it to verify? or integration-tests? From the code, it seems like jspc is binding by default to process-classes phase. If what phases are is not clear to you, please read http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html#Lifecycle_Reference Cheers 2013/4/26 virg g 06v...@gmail.com Hi, I am using jspc-maven-plugin for compiling jsp files to avoid runtime exceptions. These compiled Java files will not get packaged in war file. This build is just for verification. Currently how it is building is if i give mvn install after compiling jsps, war file is getting created. But my requirement is jsp compilation should happen after pckaging war file, both these activities should be independent. How to separate packaging war file and jsp compilation as separate actions? Any inputs, highly appreciated.. Thanks Virg -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! nbsp;!
Re: jsp compilation
Perhaps simply don't bind the plugin to your build at all, and just call it manually when you want to run jsp compilation? From the command line, this can be done via: mvn groupId:pluginId:version:mojo (but obviously you need to specify the proper plugin information) Wayne On Fri, Apr 26, 2013 at 4:40 AM, virg g 06v...@gmail.com wrote: Hi, I am using jspc-maven-plugin for compiling jsp files to avoid runtime exceptions. These compiled Java files will not get packaged in war file. This build is just for verification. Currently how it is building is if i give mvn install after compiling jsps, war file is getting created. But my requirement is jsp compilation should happen after pckaging war file, both these activities should be independent. How to separate packaging war file and jsp compilation as separate actions? Any inputs, highly appreciated.. Thanks Virg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Is there a way to specify encoding of files configured in filters?
We have sites in countries where the local language uses non-8859-1 characters, and the local people would like to write interpolated externalized property values in UTF-8. Understandably, they would rather not resort to nearly-unintelligible escape sequences. Is there some way to get buildfilters or a buildfiltersfilter to use UTF-8 encoding when reading a serialized Properties? Our projects have long used project.build.sourceEncodingUTF-8/project.build.sourceEncoding but it has no effect on this. It appears that this only applies to files *read by Maven*, and that Maven understandably uses java.util.Properties.load(), which takes no notice of POM values, to read .properties files. -- Mark H. Wood, Lead System Programmer mw...@iupui.edu Machines should not be friendly. Machines should be obedient. signature.asc Description: Digital signature
Can't get pomFileName to work in release:perform
[INFO] Working directory: /Users/benson/x/perceptron-segmentation-models/common/target/checkout [INFO] Executing goals 'deploy'... [INFO] pomFileName is already set, ignoring the -f argument and then fails to find the pom. pluginManagement plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-release-plugin/artifactId version2.3/version configuration releaseProfilesrelease/releaseProfiles pomFileNamecommon/pom.xml/pomFileName /configuration /plugin /plugins /pluginManagement
Are there any guidelines I can follow when I split apart a wep-app into a multimodule project?
For example, I have a SSH project, how many modules should I split? A service-module, a DAO-module, a action-module and a web-app module? Are there any guidelines or rules I should follow? Thanks~~ -- View this message in context: http://maven.40175.n5.nabble.com/Are-there-any-guidelines-I-can-follow-when-I-split-apart-a-wep-app-into-a-multimodule-project-tp5754421.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Are there any guidelines I can follow when I split apart a wep-app into a multimodule project?
This is not really a maven. You might want to ask in the Java community. My advice would be to group the code into projects in such a way that changes affect the smallest number of projects. On the other hand, you also want to make it easy to figure out which project contains the class that you want to change. Ron On 26/04/2013 11:03 PM, zhu19774279 wrote: For example, I have a SSH project, how many modules should I split? A service-module, a DAO-module, a action-module and a web-app module? Are there any guidelines or rules I should follow? Thanks~~ -- View this message in context: http://maven.40175.n5.nabble.com/Are-there-any-guidelines-I-can-follow-when-I-split-apart-a-wep-app-into-a-multimodule-project-tp5754421.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
