Re: Maven Extension automatic deployment

Strange, you should file a ticket about this. Please provide a simple project to reproduce the issue. /Anders (mobile) Den 18 nov 2013 02:38 skrev "James Hutton" : > Yeah, turns out I just needed to release it. For some reason maven wasn't > downloading the build extension at all when it was a s

Re: Using filters based on environment.

You should handle the properties files outside of your binaries. Then you don't need to play around with profiles. Read properties files from the classpath. Most/all app servers provides support for folders outside of the ear that are added to the classpath. Put the properties files there. /Anders

Re: Maven Extension automatic deployment

Yeah, turns out I just needed to release it. For some reason maven wasn't downloading the build extension at all when it was a snapshot version. After making a release maven pulled down the artifact correctly without it being preloaded in my maven install or local repository. On Sun, Nov 17, 20

Re: Maven Extension automatic deployment

Hi James, There are some things I don’t understand about your scenario. You say you “temporarily” have a maven build extension. What does that mean? Are you currently using ant? And using ant tasks for maven to build the maven portions? Or now using maven and having it call an old build tool? M

Re: Error in deploying to TomCat

first upgrade to last version of this plugin. It's now hosted @ Apache. See: http://tomcat.apache.org/maven-plugin.html On 14 November 2013 13:18, SyMVN wrote: > I try to deploy the WAR to the Tomcat server from Maven but I am getting the > below error. Please let me know, how to overcome this e

Not able to deploy the WAR file in Tomcat

I use the Tomcat plug-in to deploy the WAR file in Tomcat. I get the following error when I try to deploy. Please let me know, How to overcome this issue. Failed to execute goal org.codehaus.mojo:tomcat-maven-plugin:1.1:deploy (default-cli) on project onetwothree: Cannot invoke Tomcat manager: Ser

Error in deploying to TomCat

I try to deploy the WAR to the Tomcat server from Maven but I am getting the below error. Please let me know, how to overcome this error. Failed to execute goal org.codehaus.mojo:tomcat-maven-plugin:1.1:deploy (default-cli) on project onetwothree: Cannot invoke Tomcat manager: Server returned HTTP

Using filters based on environment.

Hi, In our project we have dev,qa and prod environment and we have filter (property) file for each of these environments.I do understand that based on the maven profile (for each of the environment ) we can apply/inject the respective filter values into any configuration file. Our problem is tha

Maven Extension automatic deployment

Hi, I have a project where I need to temporarily have a maven build extension (because we're migrating to maven) and did not know if there is any way to get the maven extension artifact to automatically download. I have seen that if the artifact is in my local repository that it does not need to b

Re: What would cause the javadoc plugin to create 'naked' javadoc?

This is definitely related to java version. When I switch the JAVA_HOME to 1.6 instead of 1.7, all is well. On Sun, Nov 17, 2013 at 2:18 PM, Benson Margulies wrote: > Java 1.7 > > Maven 3.0.4 > > Fluido skin 1.3.0 > > Very boring javadoc spec: > > > org.apache.maven

What would cause the javadoc plugin to create 'naked' javadoc?

Java 1.7 Maven 3.0.4 Fluido skin 1.3.0 Very boring javadoc spec: org.apache.maven.plugins maven-javadoc-plugin 2.9.1 default