Re: Automatically appended artifactId in inherited SCM element

On 2015-08-08T20:20:25 +0200 Karl Heinz Marbaise wrote: > Hi, > Hello! > The first thing which i saw where the wrong SCM connections given: Corrected. I've actually switched to the https URIs, as those allow anonymous cloning and authenticated pushes. > Apart from that it would be helpfull t

Re: Automatically appended artifactId in inherited SCM element

On 2015-08-08T20:20:25 +0200 Karl Heinz Marbaise wrote: > Hi, > Hello! > The first thing which i saw where the wrong SCM connections given: Corrected. I've actually switched to the https URIs, as those allow anonymous cloning and authenticated pushes. > Apart from that it would be helpfull t

Re: Automatically appended artifactId in inherited SCM element

Hi, On 8/8/15 6:04 PM, org.apache.maven.u...@io7m.com wrote: Hello. I'm trying to reduce the redundancy of my existing POM files with inheritance. I've run into an issue with the generated sites. The parent pom: http://waste.io7m.com/2015/08/08/jnull.pom A submodule pom: http://waste.

Automatically appended artifactId in inherited SCM element

Hello. I'm trying to reduce the redundancy of my existing POM files with inheritance. I've run into an issue with the generated sites. The parent pom: http://waste.io7m.com/2015/08/08/jnull.pom A submodule pom: http://waste.io7m.com/2015/08/08/jnull-core.pom The deployed site, note the co

Re: Plugin Configuration params take precedence over CLI Arguments?

When you don't specify the value in the POM you are *effectively*[1] specifying ${demoName} So what you have done is disabled configuration via the CLI. [1] I say *effectively* because if you did configure that and the property was undefined then that explicit configuration would evaluate to the

Re: Where to put context.xml in webapp archetype ?

I personally find this a bit weird, but it's because the JPA persistence.xml needs to end up in war!WEB-INF/classes/META-INF/persistence.xml whereas Tomcat will expect to find context.xml in war!WEB-INF/context.xml. I suppose you could put it in src/main/webapp/WEB-INF/classes/META-INF/persistence.

Re: Where to put context.xml in webapp archetype ?

Thanks On Sat, Aug 8, 2015 at 4:05 PM, jieryn wrote: > src/main/resources/META-INF/persistence.xml > src/main/webapp/WEB-INF/context.xml > > On Fri, Aug 7, 2015 at 3:24 PM, Sreyan Chakravarty > wrote: > > I am using Maven for building a simple webapp that uses JDBC connection > > pooling along

Re: Where to put context.xml in webapp archetype ?

src/main/resources/META-INF/persistence.xml src/main/webapp/WEB-INF/context.xml On Fri, Aug 7, 2015 at 3:24 PM, Sreyan Chakravarty wrote: > I am using Maven for building a simple webapp that uses JDBC connection > pooling along with Hibernate. > > I am using the Maven Webapp Archetype to build th

Re: Facing problem whith Maven for Portals-pom 1.4

Hi, are you behind a corporate firewall / proxy ? Furthermore have you correctly configured your nexus? Have you tried to get the pom via browser / curl ? https://repo.maven.apache.org/maven2/org/apache/portals/portals-pom/1.4/portals-pom-1.4.pom Have you tried the following url as central UR

Re: Where to put context.xml in webapp archetype ?

there is one misconception: the project *is not built with* Maven Webapp Archetype, but it *was generated from* Maven Webapp Archetype Once a project is generated from a Maven Archetype, it is a normal project, you can forget about its inception: the whole generated content is yours, to be main