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

2013-11-17 Thread Benson Margulies
Java 1.7

Maven 3.0.4

Fluido skin 1.3.0

Very boring javadoc spec:

 plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
version2.9.1/version
reportSets
reportSet
iddefault/id
reports
reportjavadoc/report
/reports
/reportSet
/reportSets
/plugin

Results: javadoc with all the styles missing. Looking in the chrome
debugger, it's not failing to load anything. There's just no graphic
decoration.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



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

2013-11-17 Thread Benson Margulies
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 bimargul...@gmail.com wrote:
 Java 1.7

 Maven 3.0.4

 Fluido skin 1.3.0

 Very boring javadoc spec:

  plugin
 groupIdorg.apache.maven.plugins/groupId
 artifactIdmaven-javadoc-plugin/artifactId
 version2.9.1/version
 reportSets
 reportSet
 iddefault/id
 reports
 reportjavadoc/report
 /reports
 /reportSet
 /reportSets
 /plugin

 Results: javadoc with all the styles missing. Looking in the chrome
 debugger, it's not failing to load anything. There's just no graphic
 decoration.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Maven Extension automatic deployment

2013-11-17 Thread James Hutton
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 be
in my lib/ext folder but if it hasn't already been downloaded maven throws
an error that it can't find the artifact.  Are there any options or steps I
can document that would prevent me from having to get the artifact deployed
into all of my maven installations or local repositories?  I saw some
documentation on the Eclipse Tycho project that they seem to believe it
should automatically download, but it did not for me (I think there is a
proxy issue).  My extension is still in a snapshot state, could it be that
if I made a release it would automatically download?

Thanks,
James


Using filters based on environment.

2013-11-17 Thread santtarius
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 that,we have two different data centres in production.We use
same build (profile) for deploying in these two data centres.But we need
different configuration values for these two data centres within the
production environment. How can i use filter to achieve the same,or is there
any other way.

I created separate maven build profiles for these two data centres and
placed the respective filter inside this profile (in pom.xml) .But maven
throws a error when we place filter inside profile.Can some one please guide
me to acheive the same.


Regards
Santhosh kumar N



--
View this message in context: 
http://maven.40175.n5.nabble.com/Using-filters-based-on-environment-tp5775412.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



Error in deploying to TomCat

2013-11-17 Thread SyMVN
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 response code: 405 for URL:
http://localhost:8080/manager/html/deploy?path=%2Fonetwothree-0.0.1-SNAPSHOTwar=
- [Help 1]




--
View this message in context: 
http://maven.40175.n5.nabble.com/Error-in-deploying-to-TomCat-tp5775343.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



Not able to deploy the WAR file in Tomcat

2013-11-17 Thread SyMVN
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: Server
returned HTTP response code: 405 for URL:
http://localhost:8080/manager/html/deploy?path=%2Fonetwothree-0.0.1-SNAPSHOTwar=
- [Help 1]




--
View this message in context: 
http://maven.40175.n5.nabble.com/Not-able-to-deploy-the-WAR-file-in-Tomcat-tp5775340.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: Error in deploying to TomCat

2013-11-17 Thread Olivier Lamy
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 sy_ma...@yahoo.com 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 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 response code: 405 for URL:
 http://localhost:8080/manager/html/deploy?path=%2Fonetwothree-0.0.1-SNAPSHOTwar=
 - [Help 1]




 --
 View this message in context: 
 http://maven.40175.n5.nabble.com/Error-in-deploying-to-TomCat-tp5775343.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




-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: Maven Extension automatic deployment

2013-11-17 Thread Russell Gold
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? More information would 
help us to help you.

Regards,
Russ

On Nov 15, 2013, at 1:31 PM, James Hutton james.a.hut...@gmail.com wrote:

 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 be
 in my lib/ext folder but if it hasn't already been downloaded maven throws
 an error that it can't find the artifact.  Are there any options or steps I
 can document that would prevent me from having to get the artifact deployed
 into all of my maven installations or local repositories?  I saw some
 documentation on the Eclipse Tycho project that they seem to believe it
 should automatically download, but it did not for me (I think there is a
 proxy issue).  My extension is still in a snapshot state, could it be that
 if I made a release it would automatically download?
 
 Thanks,
 James

-
Author, Getting Started with Apache Maven 
http://www.packtpub.com/getting-started-with-apache-maven/video

Come read my webnovel, Take a Lemon http://www.takealemon.com, 
and listen to the Misfile radio play http://www.fuzzyfacetheater.com/misfile/!









Re: Maven Extension automatic deployment

2013-11-17 Thread 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 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, 2013 at 8:21 PM, Russell Gold r...@gold-family.us wrote:

 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? More
 information would help us to help you.

 Regards,
 Russ

 On Nov 15, 2013, at 1:31 PM, James Hutton james.a.hut...@gmail.com
 wrote:

  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
 be
  in my lib/ext folder but if it hasn't already been downloaded maven
 throws
  an error that it can't find the artifact.  Are there any options or
 steps I
  can document that would prevent me from having to get the artifact
 deployed
  into all of my maven installations or local repositories?  I saw some
  documentation on the Eclipse Tycho project that they seem to believe it
  should automatically download, but it did not for me (I think there is a
  proxy issue).  My extension is still in a snapshot state, could it be
 that
  if I made a release it would automatically download?
 
  Thanks,
  James

 -
 Author, Getting Started with Apache Maven 
 http://www.packtpub.com/getting-started-with-apache-maven/video

 Come read my webnovel, Take a Lemon http://www.takealemon.com,
 and listen to the Misfile radio play 
 http://www.fuzzyfacetheater.com/misfile/!










Re: Using filters based on environment.

2013-11-17 Thread Anders Hammar
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 (mobile)
Den 18 nov 2013 02:12 skrev santtarius santtar...@gmail.com:

 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 that,we have two different data centres in production.We use
 same build (profile) for deploying in these two data centres.But we need
 different configuration values for these two data centres within the
 production environment. How can i use filter to achieve the same,or is
 there
 any other way.

 I created separate maven build profiles for these two data centres and
 placed the respective filter inside this profile (in pom.xml) .But maven
 throws a error when we place filter inside profile.Can some one please
 guide
 me to acheive the same.


 Regards
 Santhosh kumar N



 --
 View this message in context:
 http://maven.40175.n5.nabble.com/Using-filters-based-on-environment-tp5775412.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: Maven Extension automatic deployment

2013-11-17 Thread Anders Hammar
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 james.a.hut...@gmail.com:

 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, 2013 at 8:21 PM, Russell Gold r...@gold-family.us wrote:

  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? More
  information would help us to help you.
 
  Regards,
  Russ
 
  On Nov 15, 2013, at 1:31 PM, James Hutton james.a.hut...@gmail.com
  wrote:
 
   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
  be
   in my lib/ext folder but if it hasn't already been downloaded maven
  throws
   an error that it can't find the artifact.  Are there any options or
  steps I
   can document that would prevent me from having to get the artifact
  deployed
   into all of my maven installations or local repositories?  I saw some
   documentation on the Eclipse Tycho project that they seem to believe it
   should automatically download, but it did not for me (I think there is
 a
   proxy issue).  My extension is still in a snapshot state, could it be
  that
   if I made a release it would automatically download?
  
   Thanks,
   James
 
  -
  Author, Getting Started with Apache Maven 
  http://www.packtpub.com/getting-started-with-apache-maven/video
 
  Come read my webnovel, Take a Lemon http://www.takealemon.com,
  and listen to the Misfile radio play 
  http://www.fuzzyfacetheater.com/misfile/!