Yes, here is the build section of pom.xml:
${artifactId}
maven-compiler-plugin
2.3.1
1.6
1.6
The build runs fine, tests fine and the WAR created in the target folder
is correct. For some reason the WAR uploaded to the maven repository on
"deploy" or "release" is missing most everything. All it has is
META-INF and the compile resources and the class files for the servlets
and .java fi
On Dec 11, 2010, at 3:59 AM, Stephen Connolly wrote:
> My issue with using orofiles for adding modules is that you can end up with
> version numbers out of sync of course that's why I created
> versions-maven-plugin, but that is just a band-aid.
Is this because the release plugin doesn't see
Hello Zac,
thank you for the reply. I will try to provide more details.
In my pre-maven time i had 5 projects for moskito
(http://moskito.anotheria.net), but 3 are enough to illustrate the
problem:
moskito-core
moskito-web
moskito-webui
which are depending on each other webui<- web <- core
i had
The Maven team is pleased to announce the release of the Maven Project
Info Reports Plugin, version 2.3
This plugin is used to generate reports information about the project.
http://maven.apache.org/plugins/maven-project-info-reports-plugin/
You should specify the version in your project's plugi
Stupid me !!
I was using the default install of maven on the iMac and I forgot to copy the
settings.xml file I had on Linux.
Funny, the default maven install on the iMac had no settings.xml file at all.
Did the copy and the build passed.
So sorry to bother you smart people with my mistake
On 11 December 2010 06:26, Brian Topping wrote:
>
> On Dec 10, 2010, at 10:03 PM, Ron Wheeler wrote:
>
> > On 10/12/2010 9:19 PM, Bryan Loofbourrow wrote:
> What is the semantic difference between multiple POMs and a single POM
> containing the different module lists in profiles? It seems l
