RE: Deploying war from dependency with tomcat7-maven-plugin

2013-09-10 Thread Martin Gainty
 Oliver wrote this plugin so I will reference his doc 



 From: gregory.amer...@liferay.com
 Date: Mon, 9 Sep 2013 11:18:50 +0800
 Subject: Deploying war from dependency with tomcat7-maven-plugin
 To: us...@tomcat.apache.org
 
 Hello all,
 
 I'm trying to use the tomcat7-maven-plugin, specifically running the *mvn
 tomcat7:run* command.
MG
project
  packagingwar/packaging
  build
...
plugins
  plugin
groupIdorg.apache.tomcat.maven/groupId
artifactIdtomcat7-maven-plugin/artifactId
version2.0-beta-1/version
executions
  execution
idtomcat-run/id
goals
  goalexec-war-only/goal
/goals
phasepackage/phase
configuration

 !-- assume ROOT ---

   path//path
   !-- extra dependencies to add jdbc driver mail jars --
  extraDependencies
extraDependency

 However, in my case I have two requirements that are different than the
 documentation provides for and I'm wondering if it is possible with the
 current tomcat7-maven-plugin.
 
 1. need to deploy several jars to the global tomcat classpath (i.e. same as
 copying them into tomcat.home/lib/ext/ folder in a standalone install).

MGCOPY RESOURCES


MGhttp://maven.apache.org/plugins/maven-resources-plugin/examples/copy-resources.html
MGas with tomcat7-maven-plugin bind to package phase

 2. need to deploy a war to the ROOT context
MGsee ROOT above
 but instead of packaging the current project from source, I just need to 
 point to an existing WAR as a dependency.
MGmaven dependency implies required sub-artifact of current artifact you are 
processing
MGcan i assume you want to replace an 'already deployed war'?
MGthen you will want mvn package tomcat7:redeploy
MGhttp://tomcat.apache.org/maven-plugin-2.0-beta-1/context-goals.html#aRedeploying_a_WAR_project
 
 So in my project there will be no webapp source. I simply want to run a
 tomcat with some extra jars in /lib/ext/ directory
MGsee COPY RESOURCES above
 
 and also deploy a war
 that is obtained via a dependency with war type instead of packaged from
 source
MGpackagingwar/packaging
MGhttp://tomcat.apache.org/maven-plugin-2.0-beta-1/executable-war-jar.html
 
 Thanks in advance for any help!
 
 -- 
 Greg Amerson
 Liferay Developer Tools
 Liferay, Inc. www.liferay.com

MGOliver please check accuracy   

Re: Failure to find artifact in Nexus

2013-09-10 Thread Brian Fox
You still have something wrong with the repositories in your pom or the
settings.xml. Making requests to Nexus /releases would generally only
be done for _your_ internal components, not for things like http client or
the clean plugin. You would normally have requests to .../public instead.
I'm pretty sure this is the root cause of all your problems and the maven
opts fix you refer to above is a hack around that.


On Mon, Sep 9, 2013 at 4:02 PM, John Dix john@amdocs.com wrote:

 FYI  https://jira.codehaus.org/browse/MNG-5181 ... The use of the
 MAVEN_OPTS flag has resolved this issue for us. However now it is telling
 us that maven-clean-plugin 2.5 cannot be found in our release repository.
 This might be an ancillary issue as we have not encountered this before
 until I used the workaround given in the Jira bug.

 It feels more like a hack than a fix as I am basically telling it to not
 be 3.1 and act like 2.x, which kind of defeats the purpose of upgrading out
 of 2.x IMO.

 -Original Message-
 From: Ron Wheeler [mailto:rwhee...@artifact-software.com]
 Sent: Friday, September 06, 2013 12:59 PM
 To: users@maven.apache.org
 Subject: Re: Failure to find artifact in Nexus

 What is in your settings.xml file?

 Do you have anything about repos in your POMs?

 Ron
 On 06/09/2013 2:09 PM, John Dix wrote:
  + maven dev team..
 
  -Original Message-
  From: John Dix
  Sent: Friday, September 06, 2013 11:08 AM
  To: Maven Users List; rwhee...@artifact-software.com
  Subject: RE: Failure to find artifact in Nexus
 
  Let me rephrase this. It is finding it in the repository we have it in
 (3rdparty), but when it gets to
 http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releases,
 which is where the artifact ISN'T, maven says Oops. I can't find it I give
 up and craps out DESPITE the fact that it has already found it and
 downloaded the file.
 
  -Original Message-
  From: John Dix
  Sent: Friday, September 06, 2013 10:59 AM
  To: Maven Users List; rwhee...@artifact-software.com
  Subject: RE: Failure to find artifact in Nexus
 
  Yes it is. It downloads the file. I have verified it is in the .m2
 repository on the drive where the build is located. When I execute a second
 time it bypasses the error.
 
  -Original Message-
  From: Ron Wheeler [mailto:rwhee...@artifact-software.com]
  Sent: Thursday, September 05, 2013 6:49 PM
  To: users@maven.apache.org
  Subject: Re: Failure to find artifact in Nexus
 
 
  Is the artifact
 
  commons-httpclient:commons-httpclient:jar:3.1
 
  in the
 http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releasesrepo?
 
  That will split your problem in half.
 
  Ron
 
  On 05/09/2013 8:17 PM, John Dix wrote:
  Mark: We are going to our own Nexus repository:
  http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/release
  s
 
  -Original Message-
  From: Mark Eggers [mailto:its_toas...@yahoo.com]
  Sent: Thursday, September 05, 2013 5:03 PM
  To: Maven Users List
  Subject: Re: Failure to find artifact in Nexus
 
  On 9/5/2013 4:47 PM, John Dix wrote:
  Hello everyone,
 
  I have hit a wall in trying to figure out why we're getting this
 failure:
 
  org.sonatype.aether.transfer.ArtifactNotFoundException: Failure to
  find commons-httpclient:commons-httpclient:jar:3.1 in
  http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releas
  e s was cached in the local repository, resolution will not be
  reattempted until the update interval of qpass-nexus-hosted-releases
  has elapsed or updates are forced
 
  during our builds. On a clean .m2/repository directory(ran rm -rf
 ~/.m2/repository/*) and executing the following command:
 
  mvn -e -DskipTests clean install -f path to our pom. This happens
 the first time and then after that it picks up the file. It happens on the
 SAME file everytime after a wiping of the .ms/repository directory. I have
 looked and visually verified that the jar file it is looking for is in the
 .m2 repo and is the correct version it is looking for. I have tried using
 the -U switch with the maven command to no avail. We are getting this on
 one more jar file after this one gets resolved but it behaves the same:
 rerun and it finds it. We do not encounter this on other products, just
 this one.
 
  Does anyone have any idea on how to move forward on this? I am at a
 loss.
 
  Regards!
  -Caolan.
 
  Maven essentials:
  Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da;
  2013-02-19 13:51:28+) Maven home: /usr/local/maven-3.0.5 Java
  version: 1.7.0_02, vendor: Oracle Corporation Java home:
  /usr/local/jdk1.7.0_02/jre Default locale: en_US, platform encoding:
  UTF-8 OS name: linux, version: 2.6.30.10-105.2.23.fc11.x86_64,
  arch: amd64, family: unix
 
 
  Full Stack:
  [ERROR] Failed to execute goal on project
  applicationContextComponents: Could not resolve dependencies for
  project
  com.amdocs.dc.applicationcontext:applicationContextComponents:jar:1.
  

`mvn generate-sources` skipping my custom executions?

2013-09-10 Thread Andrew Pennebaker
I added executions for `.thrift - .java` as part of the generate-sources
phase, using `maven-antrun-plugin`. But when I enter `mvn
generate-sources`, Maven skips right over this execution.

Any idea why it would do this?

pom.xml:

project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=
http://www.w3.org/2001/XMLSchema-instance;
  xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd;
  modelVersion4.0.0/modelVersion

...

  properties
project.build.sourceEncodingUTF-8/project.build.sourceEncoding
  /properties

  build
plugins
  plugin
artifactIdmaven-antrun-plugin/artifactId
executions
  execution
idgenerate-sources/id
phasegenerate-sources/phase
configuration
  tasks
exec executable=${thrift.executable}
  arg value=--gen /
  arg value=java:beans /
  arg value=-o /
  arg value=src/main/java/com/...  /
  arg value=src/main/thrift/... .thrift /
/exec
  /tasks
/configuration
  /execution
  execution
idclean/id
phaseclean/phase
configuration
  tasks
delete
  fileset dir=src/main/java/com/...  includes=...
.java /
/delete
  /tasks
/configuration
  /execution
/executions
  /plugin
/plugins
  /build

  dependencies
dependency
  groupIdjunit/groupId
  artifactIdjunit/artifactId
  version3.8.1/version
  scopetest/scope
/dependency
  /dependencies
/project

Also posted on StackOverflow http://stackoverflow.com/questions/18721684.


Re: `mvn generate-sources` skipping my custom executions?

2013-09-10 Thread Andrew Pennebaker
Thanks, that did it!


On Tue, Sep 10, 2013 at 11:00 AM, Vincent Latombe vincent.lato...@gmail.com
 wrote:

 Hi,

 you are missing
 goals
   goalrun/goal
 /goals

 from the execution block for antrun.


 Vincent


 2013/9/10 Andrew Pennebaker apenneba...@42six.com

  I added executions for `.thrift - .java` as part of the generate-sources
  phase, using `maven-antrun-plugin`. But when I enter `mvn
  generate-sources`, Maven skips right over this execution.
 
  Any idea why it would do this?
 
  pom.xml:
 
  project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=
  http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
  http://maven.apache.org/xsd/maven-4.0.0.xsd;
modelVersion4.0.0/modelVersion
 
  ...
 
properties
 
 project.build.sourceEncodingUTF-8/project.build.sourceEncoding
/properties
 
build
  plugins
plugin
  artifactIdmaven-antrun-plugin/artifactId
  executions
execution
  idgenerate-sources/id
  phasegenerate-sources/phase
  configuration
tasks
  exec executable=${thrift.executable}
arg value=--gen /
arg value=java:beans /
arg value=-o /
arg value=src/main/java/com/...  /
arg value=src/main/thrift/... .thrift /
  /exec
/tasks
  /configuration
/execution
execution
  idclean/id
  phaseclean/phase
  configuration
tasks
  delete
fileset dir=src/main/java/com/...  includes=...
  .java /
  /delete
/tasks
  /configuration
/execution
  /executions
/plugin
  /plugins
/build
 
dependencies
  dependency
groupIdjunit/groupId
artifactIdjunit/artifactId
version3.8.1/version
scopetest/scope
  /dependency
/dependencies
  /project
 
  Also posted on StackOverflow 
 http://stackoverflow.com/questions/18721684
  .
 



Tooling to help with releases from within a source tree.

2013-09-10 Thread Ian Boston
Hi,
I am wondering if there is tooling available in maven to assist with
this the following scenario.

I have a source tree releasing multiple artifacts, all on different
release cycles, semantically versioned and depending on one another in
a tree.

After one item is released all references to it are set to the release
version, and its version is set to the next SNAPSHOT. Only when a
change is made are upstream poms updated to the SNAPSHOT version.

Is there an existing plugin that will tell what needs to be released
and what doesn't based on the multiproject dependency tree ?

Better still, is there something I can just ask

 release everything that needs to be released to allow artifact X to
be released 

of

That would be excellent.

Best Regards
Ian

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



Re: `mvn generate-sources` skipping my custom executions?

2013-09-10 Thread Vincent Latombe
Hi,

you are missing
goals
  goalrun/goal
/goals

from the execution block for antrun.


Vincent


2013/9/10 Andrew Pennebaker apenneba...@42six.com

 I added executions for `.thrift - .java` as part of the generate-sources
 phase, using `maven-antrun-plugin`. But when I enter `mvn
 generate-sources`, Maven skips right over this execution.

 Any idea why it would do this?

 pom.xml:

 project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=
 http://www.w3.org/2001/XMLSchema-instance;
   xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
 http://maven.apache.org/xsd/maven-4.0.0.xsd;
   modelVersion4.0.0/modelVersion

 ...

   properties
 project.build.sourceEncodingUTF-8/project.build.sourceEncoding
   /properties

   build
 plugins
   plugin
 artifactIdmaven-antrun-plugin/artifactId
 executions
   execution
 idgenerate-sources/id
 phasegenerate-sources/phase
 configuration
   tasks
 exec executable=${thrift.executable}
   arg value=--gen /
   arg value=java:beans /
   arg value=-o /
   arg value=src/main/java/com/...  /
   arg value=src/main/thrift/... .thrift /
 /exec
   /tasks
 /configuration
   /execution
   execution
 idclean/id
 phaseclean/phase
 configuration
   tasks
 delete
   fileset dir=src/main/java/com/...  includes=...
 .java /
 /delete
   /tasks
 /configuration
   /execution
 /executions
   /plugin
 /plugins
   /build

   dependencies
 dependency
   groupIdjunit/groupId
   artifactIdjunit/artifactId
   version3.8.1/version
   scopetest/scope
 /dependency
   /dependencies
 /project

 Also posted on StackOverflow http://stackoverflow.com/questions/18721684
 .



RE: Failure to find artifact in Nexus

2013-09-10 Thread John Dix
Agreed. It is a hack... I am fairly new to maven and I work on a very complex 
system I did not design (in fact nobody here is left who did design it). Do you 
have suggestions on how to approach debugging this problem?

-Original Message-
From: Brian Fox [mailto:bri...@infinity.nu]
Sent: Tuesday, September 10, 2013 4:24 AM
To: Maven Users List
Cc: rwhee...@artifact-software.com
Subject: Re: Failure to find artifact in Nexus

You still have something wrong with the repositories in your pom or the 
settings.xml. Making requests to Nexus /releases would generally only be 
done for _your_ internal components, not for things like http client or the 
clean plugin. You would normally have requests to .../public instead.
I'm pretty sure this is the root cause of all your problems and the maven opts 
fix you refer to above is a hack around that.


On Mon, Sep 9, 2013 at 4:02 PM, John Dix john@amdocs.com wrote:

 FYI  https://jira.codehaus.org/browse/MNG-5181 ... The use of the
 MAVEN_OPTS flag has resolved this issue for us. However now it is
 telling us that maven-clean-plugin 2.5 cannot be found in our release 
 repository.
 This might be an ancillary issue as we have not encountered this
 before until I used the workaround given in the Jira bug.

 It feels more like a hack than a fix as I am basically telling it to
 not be 3.1 and act like 2.x, which kind of defeats the purpose of
 upgrading out of 2.x IMO.

 -Original Message-
 From: Ron Wheeler [mailto:rwhee...@artifact-software.com]
 Sent: Friday, September 06, 2013 12:59 PM
 To: users@maven.apache.org
 Subject: Re: Failure to find artifact in Nexus

 What is in your settings.xml file?

 Do you have anything about repos in your POMs?

 Ron
 On 06/09/2013 2:09 PM, John Dix wrote:
  + maven dev team..
 
  -Original Message-
  From: John Dix
  Sent: Friday, September 06, 2013 11:08 AM
  To: Maven Users List; rwhee...@artifact-software.com
  Subject: RE: Failure to find artifact in Nexus
 
  Let me rephrase this. It is finding it in the repository we have it
  in
 (3rdparty), but when it gets to
 http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releases
 , which is where the artifact ISN'T, maven says Oops. I can't find it
 I give up and craps out DESPITE the fact that it has already found it
 and downloaded the file.
 
  -Original Message-
  From: John Dix
  Sent: Friday, September 06, 2013 10:59 AM
  To: Maven Users List; rwhee...@artifact-software.com
  Subject: RE: Failure to find artifact in Nexus
 
  Yes it is. It downloads the file. I have verified it is in the .m2
 repository on the drive where the build is located. When I execute a
 second time it bypasses the error.
 
  -Original Message-
  From: Ron Wheeler [mailto:rwhee...@artifact-software.com]
  Sent: Thursday, September 05, 2013 6:49 PM
  To: users@maven.apache.org
  Subject: Re: Failure to find artifact in Nexus
 
 
  Is the artifact
 
  commons-httpclient:commons-httpclient:jar:3.1
 
  in the
 http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releasesrepo?
 
  That will split your problem in half.
 
  Ron
 
  On 05/09/2013 8:17 PM, John Dix wrote:
  Mark: We are going to our own Nexus repository:
  http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/relea
  se
  s
 
  -Original Message-
  From: Mark Eggers [mailto:its_toas...@yahoo.com]
  Sent: Thursday, September 05, 2013 5:03 PM
  To: Maven Users List
  Subject: Re: Failure to find artifact in Nexus
 
  On 9/5/2013 4:47 PM, John Dix wrote:
  Hello everyone,
 
  I have hit a wall in trying to figure out why we're getting this
 failure:
 
  org.sonatype.aether.transfer.ArtifactNotFoundException: Failure to
  find commons-httpclient:commons-httpclient:jar:3.1 in
  http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/rele
  as e s was cached in the local repository, resolution will not be
  reattempted until the update interval of
  qpass-nexus-hosted-releases has elapsed or updates are forced
 
  during our builds. On a clean .m2/repository directory(ran rm -rf
 ~/.m2/repository/*) and executing the following command:
 
  mvn -e -DskipTests clean install -f path to our pom. This
  happens
 the first time and then after that it picks up the file. It happens on
 the SAME file everytime after a wiping of the .ms/repository
 directory. I have looked and visually verified that the jar file it is
 looking for is in the
 .m2 repo and is the correct version it is looking for. I have tried
 using the -U switch with the maven command to no avail. We are getting
 this on one more jar file after this one gets resolved but it behaves the 
 same:
 rerun and it finds it. We do not encounter this on other products,
 just this one.
 
  Does anyone have any idea on how to move forward on this? I am at
  a
 loss.
 
  Regards!
  -Caolan.
 
  Maven essentials:
  Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da;
  2013-02-19 13:51:28+) Maven home: 

RE: Failure to find artifact in Nexus

2013-09-10 Thread John Dix
However, we are using the same settings.xml file for all of our projects, not 
just the one we are getting the errors on, and they all seem to work. 

-Original Message-
From: John Dix 
Sent: Tuesday, September 10, 2013 9:43 AM
To: Maven Users List
Cc: rwhee...@artifact-software.com
Subject: RE: Failure to find artifact in Nexus

Agreed. It is a hack... I am fairly new to maven and I work on a very complex 
system I did not design (in fact nobody here is left who did design it). Do you 
have suggestions on how to approach debugging this problem?

-Original Message-
From: Brian Fox [mailto:bri...@infinity.nu]
Sent: Tuesday, September 10, 2013 4:24 AM
To: Maven Users List
Cc: rwhee...@artifact-software.com
Subject: Re: Failure to find artifact in Nexus

You still have something wrong with the repositories in your pom or the 
settings.xml. Making requests to Nexus /releases would generally only be 
done for _your_ internal components, not for things like http client or the 
clean plugin. You would normally have requests to .../public instead.
I'm pretty sure this is the root cause of all your problems and the maven opts 
fix you refer to above is a hack around that.


On Mon, Sep 9, 2013 at 4:02 PM, John Dix john@amdocs.com wrote:

 FYI  https://jira.codehaus.org/browse/MNG-5181 ... The use of the 
 MAVEN_OPTS flag has resolved this issue for us. However now it is 
 telling us that maven-clean-plugin 2.5 cannot be found in our release 
 repository.
 This might be an ancillary issue as we have not encountered this 
 before until I used the workaround given in the Jira bug.

 It feels more like a hack than a fix as I am basically telling it to 
 not be 3.1 and act like 2.x, which kind of defeats the purpose of 
 upgrading out of 2.x IMO.

 -Original Message-
 From: Ron Wheeler [mailto:rwhee...@artifact-software.com]
 Sent: Friday, September 06, 2013 12:59 PM
 To: users@maven.apache.org
 Subject: Re: Failure to find artifact in Nexus

 What is in your settings.xml file?

 Do you have anything about repos in your POMs?

 Ron
 On 06/09/2013 2:09 PM, John Dix wrote:
  + maven dev team..
 
  -Original Message-
  From: John Dix
  Sent: Friday, September 06, 2013 11:08 AM
  To: Maven Users List; rwhee...@artifact-software.com
  Subject: RE: Failure to find artifact in Nexus
 
  Let me rephrase this. It is finding it in the repository we have it 
  in
 (3rdparty), but when it gets to
 http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releases
 , which is where the artifact ISN'T, maven says Oops. I can't find it 
 I give up and craps out DESPITE the fact that it has already found it 
 and downloaded the file.
 
  -Original Message-
  From: John Dix
  Sent: Friday, September 06, 2013 10:59 AM
  To: Maven Users List; rwhee...@artifact-software.com
  Subject: RE: Failure to find artifact in Nexus
 
  Yes it is. It downloads the file. I have verified it is in the .m2
 repository on the drive where the build is located. When I execute a 
 second time it bypasses the error.
 
  -Original Message-
  From: Ron Wheeler [mailto:rwhee...@artifact-software.com]
  Sent: Thursday, September 05, 2013 6:49 PM
  To: users@maven.apache.org
  Subject: Re: Failure to find artifact in Nexus
 
 
  Is the artifact
 
  commons-httpclient:commons-httpclient:jar:3.1
 
  in the
 http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releasesrepo?
 
  That will split your problem in half.
 
  Ron
 
  On 05/09/2013 8:17 PM, John Dix wrote:
  Mark: We are going to our own Nexus repository:
  http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/relea
  se
  s
 
  -Original Message-
  From: Mark Eggers [mailto:its_toas...@yahoo.com]
  Sent: Thursday, September 05, 2013 5:03 PM
  To: Maven Users List
  Subject: Re: Failure to find artifact in Nexus
 
  On 9/5/2013 4:47 PM, John Dix wrote:
  Hello everyone,
 
  I have hit a wall in trying to figure out why we're getting this
 failure:
 
  org.sonatype.aether.transfer.ArtifactNotFoundException: Failure to 
  find commons-httpclient:commons-httpclient:jar:3.1 in 
  http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/rele
  as e s was cached in the local repository, resolution will not be 
  reattempted until the update interval of 
  qpass-nexus-hosted-releases has elapsed or updates are forced
 
  during our builds. On a clean .m2/repository directory(ran rm -rf
 ~/.m2/repository/*) and executing the following command:
 
  mvn -e -DskipTests clean install -f path to our pom. This 
  happens
 the first time and then after that it picks up the file. It happens on 
 the SAME file everytime after a wiping of the .ms/repository 
 directory. I have looked and visually verified that the jar file it is 
 looking for is in the
 .m2 repo and is the correct version it is looking for. I have tried 
 using the -U switch with the maven command to no avail. We are getting 
 this on one more jar file after this one 

[ANN] Apache Maven Install Plugin 2.5 Released

2013-09-10 Thread Robert Scholte
The Apache Maven team is pleased to announce the release of the Apache  
Maven Install Plugin, version 2.5


The Install Plugin is used during the install phase to add artifact(s) to  
the local repository.


http://maven.apache.org/plugins/maven-install-plugin/

You should specify the version in your project's plugin configuration:

plugin
  groupIdorg.apache.maven.plugins/groupId
  artifactIdmaven-install-plugin/artifactId
  version2.5/version
/plugin


Release Notes - Apache Maven Install Plugin - Version 2.5

** Bug
* [MINSTALL-92] - Docs says the skip param is required, which it isn't

** Improvement
* [MINSTALL-39] - Maven Install Plugin always copy the artifact in the  
repository, even if there was no changes
* [MINSTALL-90] - use last plexus-utils 3.0.7 which is faster on  
copying files.

* [MINSTALL-95] - Enhance documentation of install-file

** New Feature
* [MINSTALL-52] - install:install-file should default to a pom file  
found in the jar if available

* [MINSTALL-93] - Add installAtEnd option for multimodule projects


Enjoy,

-The Apache Maven team

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



Class not found

2013-09-10 Thread jamal sasha
Hi,
  I am using the following code base:
https://github.com/larsgeorge/hbase-book/tree/master/ch07

The thing is .. I do the mvn clean package
And it compiles fine.
But when I run one of the code.. it throws an error:
java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
at
org.apache.hadoop.util.ReflectionUtils.newInstance(ReflectionUtils.java:115)
at org.apache.hadoop.mapred.MapTask.runNewMapper(MapTask.java:719)
at org.apache.hadoop.mapred.MapTask.run(MapTask.java:370)
at org.apache.hadoop.mapred.Child$4.run(Child.java:255)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:416)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1093)
at org.apache.hadoop.mapred.Child.main(Child.java:249)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:532)
at
org.apache.hadoop.util.ReflectionUtils.newInstance(ReflectionUtils.java:113)
... 7 more
Caused by: java.lang.NoClassDefFoundError: org/json/simple/parser/JSONParser
at mapreduce.ParseJson$ParseMapper.init(ParseJson.java:49)
... 12 more
Caused by: java.lang.ClassNotFoundException:
org.json.simple.parser.JSONParser
at java.net.URLClassLoader$1.run(URLClassLoader.java:217)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:205)
at java.lang.ClassLoader.loadClass(ClassLoader.java:321)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:294)
at java.lang.ClassLoader.loadClass(ClassLoader.java:266)
... 13 more



Now I am guessing it is not able to find simple-json library.. but I think
they have added it into pom here:
https://github.com/larsgeorge/hbase-book/blob/master/ch07/pom.xml

  dependency
  groupIdcom.googlecode.json-simple/groupId
  artifactIdjson-simple/artifactId
  version1.1/version
/dependency


Also, if I export a jar from eclipse and explicitly ask to include
this jar, the code works just fine?
What am i missing?


need filesystem-level operations in assembly plugin

2013-09-10 Thread Richard Sand
Hi all - I'm using maven-assembly-plugin to create zip distributions of
our web application. It takes in the Apache Tomcat zip artifact, and the
war artifact for the app, and creates an assembly.

There are a couple of file operations I haven't figured out how to do yet.
For example, Tomcat unzips to a folder called apache-tomcat-7.0.42,
which I want to rename to just tomcat. I figured id use the exec plugin
to fork a rm command, which I guess will work in theory but seems
shoddy.

Does anyone support having some swiss army knife file manipulation
capabilities (at least rename  move) in the assembly plugin?

Best regards,

Richard

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



Re: need filesystem-level operations in assembly plugin

2013-09-10 Thread Michael-O

Am 2013-09-11 07:12, schrieb Richard Sand:

Hi all - I'm using maven-assembly-plugin to create zip distributions of
our web application. It takes in the Apache Tomcat zip artifact, and the
war artifact for the app, and creates an assembly.

There are a couple of file operations I haven't figured out how to do yet.
For example, Tomcat unzips to a folder called apache-tomcat-7.0.42,
which I want to rename to just tomcat. I figured id use the exec plugin
to fork a rm command, which I guess will work in theory but seems
shoddy.

Does anyone support having some swiss army knife file manipulation
capabilities (at least rename  move) in the assembly plugin?


If you intend to rebundle Tomcat, use the dependency plugin which will 
unpack [1] the zip in target and then you can readd it to your assembly.


Michael

[1] http://maven.apache.org/plugins/maven-dependency-plugin/unpack-mojo.html


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