date:20100519

The dependency plugin has nothing to do with Maven's dependency management,
which is what you want to controll. Your original config would affect that.

/Anders

On Wed, May 19, 2010 at 15:07, C. Benson Manica cbman...@gmail.com wrote:

Thanks, that did solve the problem, although I'm still curious why the
original config I posted didn't work - the documentation certainly makes it
seem like it should...

On Tue, May 18, 2010 at 1:21 PM, Ron Wheeler
rwhee...@artifact-software.com
wrote:

We have the same situation.

Include the Spring that you need directly in a dependency in the POM and
use exclusions on all versions of Spring in the dependencies that are
transitively bringing in 2.0.x that you do not want.

Ron

On 18/05/2010 12:54 PM, C. Benson Manica wrote:

I have a project which depends on artifacts which transitively depend on
different Spring versions. I need to manually exclude all spring*-2.0.8
artifacts from being included in the project, since they don't play
nicely
with the 2.5 artifacts. How do I do this? The documentation has led me
to
believe that

plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-dependency-plugin/artifactId
version2.1/version
configuration
!-- Try to prevent the spring security libs at 2.0
from
dragging in old spring core libs --
excludeArtifactIds

org.springframework.spring-core,org.springframework.spring-support,org.springframework.spring-context
/excludeArtifactIds
excludeTransitivetrue/excludeTransitive
/configuration
/plugin

would work, but it doesn't - mvn dependency:resolve on a clean
repository
still shows lines like

Downloading:

http://ide-svn.turner.com/artifactory/repo/org/springframework/spring-context/2.0.8/spring-context-2.0.8.pom

What am I doing wrong?

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

--
C. Benson Manica
cbman...@gmail.com

Re: Exclude all transitive dependencies by version?

Sorry, should be Your original config would NOT affect that.

/Anders

On Wed, May 19, 2010 at 15:32, Anders Hammar and...@hammar.net wrote:

The dependency plugin has nothing to do with Maven's dependency management,
which is what you want to controll. Your original config would affect that.

/Anders

On Wed, May 19, 2010 at 15:07, C. Benson Manica cbman...@gmail.comwrote:

Thanks, that did solve the problem, although I'm still curious why the
original config I posted didn't work - the documentation certainly makes
it
seem like it should...

On Tue, May 18, 2010 at 1:21 PM, Ron Wheeler
rwhee...@artifact-software.com
wrote:

We have the same situation.

Include the Spring that you need directly in a dependency in the POM and
use exclusions on all versions of Spring in the dependencies that are
transitively bringing in 2.0.x that you do not want.

Ron

On 18/05/2010 12:54 PM, C. Benson Manica wrote:

I have a project which depends on artifacts which transitively depend
on
different Spring versions. I need to manually exclude all
spring*-2.0.8
artifacts from being included in the project, since they don't play
nicely
with the 2.5 artifacts. How do I do this? The documentation has led
me
to
believe that

org.springframework.spring-core,org.springframework.spring-support,org.springframework.spring-context
/excludeArtifactIds
excludeTransitivetrue/excludeTransitive
/configuration
/plugin

would work, but it doesn't - mvn dependency:resolve on a clean
repository
still shows lines like

Downloading:

http://ide-svn.turner.com/artifactory/repo/org/springframework/spring-context/2.0.8/spring-context-2.0.8.pom

What am I doing wrong?

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

--
C. Benson Manica
cbman...@gmail.com

Re: Central repository, bundle-create and distribution of licenses

2010-05-19 Thread Mark H. Wood

On Tue, May 18, 2010 at 07:52:48PM +0100, Bruno Harbulot wrote:
 I'm not saying that the central repo should investigate each and every 
 case to check that it's indeed true, but it should make it mandatory to 
 have a licence at least so as to avoid to put software that is 
 mistakenly unattributed (and thus often in breach of the licence).

What is the URL for the license to software which is placed in the
public domain?  If you can answer that, then yes, I'd agree that it
would be reasonable for a repo. to check that the POM lists a license
and even that the link is not broken.  What is *in* that target
document is probably beyond the scope of the present software.  If
it's a copy of Jabberwocky or Lorem Ipsum, that's the submitter's
problem.

 As a publisher of a piece of software, I did put the LICENSE.txt file in 
 my bundle linked from http://jira.codehaus.org/browse/MAVENUPLOAD-2293 
 (via the default settings of maven-repository-plugin 2.0 at the time), 
 having the expectation that it would be distributed along with the 
 artifacts in the bundle.

What led you to believe that this would happen?  If you put it into a
src/main/resources directory then it should have been packed up into
the archive, but I don't see anything which says that anything else
shall be done with it.

-- 
Mark H. Wood, Lead System Programmer   mw...@iupui.edu
Balance your desire for bells and whistles with the reality that only a 
little more than 2 percent of world population has broadband.
-- Ledford and Tyler, _Google Analytics 2.0_


pgppbMvNnITRI.pgp
Description: PGP signature

Chaining Maven goals of different Base Directories

2010-05-19 Thread Daniel Hoffmann

Hello,

is there any way to chain goals located in different Base Directories?
For deploying my project ear to my JBoss Application Server I have to
execute two steps:

1.) myproject/makewar clean install
2.) myproject/makeear clean install cargo:deploy

Makewar and makeear are two seperate maven projects. Is there any simple way
of chaining these two steps without adding them to a new Maven project or
changing the 'myproject' Maven project? I can´t execute 'clean install
cargo:deploy' on 'myproject', because it contains more subprojects I don´t
want to deploy (and I don´t want to change this main project).

Best regards,
 Daniel

Re: how to move folder from res to res${BUILD_NUMBER} in maven?

Is there no way of doing the below?  This is like the most typical thing in
web applications so the browser will get the newest css, js, jpg files when
a new release comes out.

thanks,
Dean

On Tue, May 18, 2010 at 3:28 PM, Dean Hiller d...@alvazan.com wrote:

 Our resource folder in webapps named res(which has images, js, css, etc) is
 renamed every release.  This then makes it so
 when we fix a css, customers get the fresh one instead of the old stale one
 from their cache(ie. they get the fix we made since
 this folder is always renamed).

 So, in maven, I had
 plugin
 artifactIdmaven-antrun-plugin/artifactId
 executions
 execution
 phasetest/phase
 goals
 goalrun/goal
 /goals
 configuration
 tasks
 move file=${project.build.directory}/${
 project.name}-${project.version}/res
 todir=${project.build.directory}/${
 project.name}-${project.version}/res${BUILD_NUMBER} /
 delete
 file=${project.build.directory}/${
 project.name}-${project.version}/WEB-INF/components.xml /
 copy
 file=src/main/descriptors/jboss/WEB-INF/components.xml
 tofile=${project.build.directory}/${
 project.name}-${project.version}/WEB-INF/components.xml /
 /tasks
 /configuration
 /execution
 /executions
 /plugin

 but the staging area for the webapp in target directory seems not to exist
 when my ant tasks run :( and so our build keeps on
 failing.
 1. How do I move the target/webappstaging/res folder to
 target/webappstaging/resBUILDNUMBER folder OR
 2. How do I move the src/main/webapp/res folder to
 target/webappstaging/resBUILD_NUMBER folder and delete
 target/webappstaging/res folder

 thanks,
 Dean

Re: Chaining Maven goals of different Base Directories

2010-05-19 Thread Jesse Farinacci

Hi Daniel,

On Wed, May 19, 2010 at 9:47 AM, Daniel Hoffmann
biggibig...@googlemail.com wrote:

 1.) myproject/makewar clean install
 2.) myproject/makeear clean install cargo:deploy

  Daniel

Why not attach cargo:deploy to the deploy phase and then call mvn clean deploy?

-Jesse

-- 
There are 10 types of people in this world, those
that can read binary and those that can not.

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

RE: how to move folder from res to res${BUILD_NUMBER} in maven?

The correct property for accessing the target directory is
${project.build.outputDirectory}. So if you change in your todir to
use ${project.build.outputDirectory} that should work. I would suggest
investigating another approach though, there has to be a simpler
solution to resolve .css caching.

Thanks

-Jeff

-Original Message-
From: dean.hil...@gmail.com [mailto:dean.hil...@gmail.com] On Behalf Of
Dean Hiller
Sent: Wednesday, May 19, 2010 8:53 AM
To: users@maven.apache.org
Subject: Re: how to move folder from res to res${BUILD_NUMBER} in maven?

Is there no way of doing the below?  This is like the most typical thing
in web applications so the browser will get the newest css, js, jpg
files when a new release comes out.

thanks,
Dean

On Tue, May 18, 2010 at 3:28 PM, Dean Hiller d...@alvazan.com wrote:

 Our resource folder in webapps named res(which has images, js, css, 
 etc) is renamed every release.  This then makes it so when we fix a 
 css, customers get the fresh one instead of the old stale one from 
 their cache(ie. they get the fix we made since this folder is always 
 renamed).

 So, in maven, I had
 plugin
 artifactIdmaven-antrun-plugin/artifactId
 executions
 execution
 phasetest/phase
 goals
 goalrun/goal
 /goals
 configuration
 tasks
 move 
 file=${project.build.directory}/${
 project.name}-${project.version}/res
 
 todir=${project.build.directory}/${
 project.name}-${project.version}/res${BUILD_NUMBER} /
 delete
 
 file=${project.build.directory}/${
 project.name}-${project.version}/WEB-INF/components.xml /
 copy
 file=src/main/descriptors/jboss/WEB-INF/components.xml
 
 tofile=${project.build.directory}/${
 project.name}-${project.version}/WEB-INF/components.xml /
 /tasks
 /configuration
 /execution
 /executions
 /plugin

 but the staging area for the webapp in target directory seems not to 
 exist when my ant tasks run :( and so our build keeps on failing.
 1. How do I move the target/webappstaging/res folder to 
 target/webappstaging/resBUILDNUMBER folder OR 2. How do I move the 
 src/main/webapp/res folder to target/webappstaging/resBUILD_NUMBER 
 folder and delete target/webappstaging/res folder

 thanks,
 Dean








The information contained in this communication may be confidential, is intended
only for the use of the recipient(s) named above, and may be legally privileged.
If the reader of this message is not the intended recipient, you are hereby
notified that any dissemination, distribution, or copying of this communication,
or any of its contents, is strictly prohibited. If you have received this
communication in error, please notify the sender immediately and destroy or
delete the original message and any copy of it from your computer system. If
you have any questions concerning this message, please contact the sender.




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

Re: how to move folder from res to res${BUILD_NUMBER} in maven?

actually, this pattern is very typical to release new versions of css, js,
etc.  Projects like richfaces and TinyMCE both use this pattern(not to
mention many more).  I don't know of any other way to get css, js fixes
immediately out to customers without the renaming(in fact, I doubt a better
solution exists here as this solution has worked great for our last 4
releases but I am open to ideas).

As far as ${project.build.outputDirectory}, I did try that but that seems to
deal with the target/classes directory which then goes to WEB-INF/classes
when packaging a war file.  I need the files in the base level of the
war(and the property below references that correctly, BUT the directory
doesn't exist yet).

The only solution I am aware of for css, js, jpg fixes to go out in a new
release is to rename the path to the file(or the file itself) as it is a
very easy solution in build tools typically(at least it was in ant).

Dean



On Wed, May 19, 2010 at 8:06 AM, Moll, Jeff jm...@glhec.org wrote:

 The correct property for accessing the target directory is
 ${project.build.outputDirectory}. So if you change in your todir to
 use ${project.build.outputDirectory} that should work. I would suggest
 investigating another approach though, there has to be a simpler
 solution to resolve .css caching.

 Thanks

 -Jeff

 -Original Message-
 From: dean.hil...@gmail.com [mailto:dean.hil...@gmail.com] On Behalf Of
 Dean Hiller
 Sent: Wednesday, May 19, 2010 8:53 AM
 To: users@maven.apache.org
 Subject: Re: how to move folder from res to res${BUILD_NUMBER} in maven?

 Is there no way of doing the below?  This is like the most typical thing
 in web applications so the browser will get the newest css, js, jpg
 files when a new release comes out.

 thanks,
 Dean

 On Tue, May 18, 2010 at 3:28 PM, Dean Hiller d...@alvazan.com wrote:

  Our resource folder in webapps named res(which has images, js, css,
  etc) is renamed every release.  This then makes it so when we fix a
  css, customers get the fresh one instead of the old stale one from
  their cache(ie. they get the fix we made since this folder is always
  renamed).
 
  So, in maven, I had
  plugin
  artifactIdmaven-antrun-plugin/artifactId
  executions
  execution
  phasetest/phase
  goals
  goalrun/goal
  /goals
  configuration
  tasks
  move
  file=${project.build.directory}/${
  project.name}-${project.version}/res
 
  todir=${project.build.directory}/${
  project.name}-${project.version}/res${BUILD_NUMBER} /
  delete
 
  file=${project.build.directory}/${
  project.name}-${project.version}/WEB-INF/components.xml /
  copy
  file=src/main/descriptors/jboss/WEB-INF/components.xml
 
  tofile=${project.build.directory}/${
  project.name}-${project.version}/WEB-INF/components.xml /
  /tasks
  /configuration
  /execution
  /executions
  /plugin
 
  but the staging area for the webapp in target directory seems not to
  exist when my ant tasks run :( and so our build keeps on failing.
  1. How do I move the target/webappstaging/res folder to
  target/webappstaging/resBUILDNUMBER folder OR 2. How do I move the
  src/main/webapp/res folder to target/webappstaging/resBUILD_NUMBER
  folder and delete target/webappstaging/res folder
 
  thanks,
  Dean
 
 
 
 
 
 


 
 The information contained in this communication may be confidential, is
 intended
 only for the use of the recipient(s) named above, and may be legally
 privileged.
 If the reader of this message is not the intended recipient, you are hereby
 notified that any dissemination, distribution, or copying of this
 communication,
 or any of its contents, is strictly prohibited. If you have received this
 communication in error, please notify the sender immediately and destroy or
 delete the original message and any copy of it from your computer system.
 If
 you have any questions concerning this message, please contact the sender.

 



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

RE: how to move folder from res to res${BUILD_NUMBER} in maven?

 
Try running on the package goal instead, the test phase doesn't require
the code to be packaged and thus isn't creating the folder structure you
are looking for.

Thanks,

-Jeff


-Original Message-
From: dean.hil...@gmail.com [mailto:dean.hil...@gmail.com] On Behalf Of
Dean Hiller
Sent: Wednesday, May 19, 2010 9:20 AM
To: Maven Users List
Subject: Re: how to move folder from res to res${BUILD_NUMBER} in maven?

actually, this pattern is very typical to release new versions of css,
js, etc.  Projects like richfaces and TinyMCE both use this pattern(not
to mention many more).  I don't know of any other way to get css, js
fixes immediately out to customers without the renaming(in fact, I doubt
a better solution exists here as this solution has worked great for our
last 4 releases but I am open to ideas).

As far as ${project.build.outputDirectory}, I did try that but that
seems to deal with the target/classes directory which then goes to
WEB-INF/classes when packaging a war file.  I need the files in the base
level of the war(and the property below references that correctly, BUT
the directory doesn't exist yet).

The only solution I am aware of for css, js, jpg fixes to go out in a
new release is to rename the path to the file(or the file itself) as it
is a very easy solution in build tools typically(at least it was in
ant).

Dean



On Wed, May 19, 2010 at 8:06 AM, Moll, Jeff jm...@glhec.org wrote:

 The correct property for accessing the target directory is 
 ${project.build.outputDirectory}. So if you change in your todir to 
 use ${project.build.outputDirectory} that should work. I would suggest

 investigating another approach though, there has to be a simpler 
 solution to resolve .css caching.

 Thanks

 -Jeff

 -Original Message-
 From: dean.hil...@gmail.com [mailto:dean.hil...@gmail.com] On Behalf 
 Of Dean Hiller
 Sent: Wednesday, May 19, 2010 8:53 AM
 To: users@maven.apache.org
 Subject: Re: how to move folder from res to res${BUILD_NUMBER} in
maven?

 Is there no way of doing the below?  This is like the most typical 
 thing in web applications so the browser will get the newest css, js, 
 jpg files when a new release comes out.

 thanks,
 Dean

 On Tue, May 18, 2010 at 3:28 PM, Dean Hiller d...@alvazan.com wrote:

  Our resource folder in webapps named res(which has images, js, css,
  etc) is renamed every release.  This then makes it so when we fix a 
  css, customers get the fresh one instead of the old stale one from 
  their cache(ie. they get the fix we made since this folder is always

  renamed).
 
  So, in maven, I had
  plugin
  artifactIdmaven-antrun-plugin/artifactId
  executions
  execution
  phasetest/phase
  goals
  goalrun/goal
  /goals
  configuration
  tasks
  move 
  file=${project.build.directory}/${
  project.name}-${project.version}/res
 
  todir=${project.build.directory}/${
  project.name}-${project.version}/res${BUILD_NUMBER} /
  delete
 
  file=${project.build.directory}/${
  project.name}-${project.version}/WEB-INF/components.xml /
  copy 
  file=src/main/descriptors/jboss/WEB-INF/components.xml
 
  tofile=${project.build.directory}/${
  project.name}-${project.version}/WEB-INF/components.xml /
  /tasks
  /configuration
  /execution
  /executions
  /plugin
 
  but the staging area for the webapp in target directory seems not to

  exist when my ant tasks run :( and so our build keeps on failing.
  1. How do I move the target/webappstaging/res folder to 
  target/webappstaging/resBUILDNUMBER folder OR 2. How do I move the 
  src/main/webapp/res folder to target/webappstaging/resBUILD_NUMBER
  folder and delete target/webappstaging/res folder
 
  thanks,
  Dean
 
 
 
 
 
 


 --
 -- The information contained in this communication may be 
 confidential, is intended only for the use of the recipient(s) named 
 above, and may be legally privileged.
 If the reader of this message is not the intended recipient, you are 
 hereby notified that any dissemination, distribution, or copying of 
 this communication, or any of its contents, is strictly prohibited. If

 you have received this communication in error, please notify the 
 sender immediately and destroy or delete the original message and any 
 copy of it from your computer system.
 If
 you have any questions concerning this message, please contact the
sender.

 ==
 ==



 -
 To

RE: how to move folder from res to res${BUILD_NUMBER} in maven?

Correction, package phase. 


Jeff Moll
E-Commerce Development
Great Lakes Educational Loan Services, Inc.
(608) 246-1460 x2256

-Original Message-
From: Moll, Jeff [mailto:jm...@glhec.org] 
Sent: Wednesday, May 19, 2010 9:42 AM
To: Maven Users List
Subject: RE: how to move folder from res to res${BUILD_NUMBER} in maven?

 
Try running on the package goal instead, the test phase doesn't require
the code to be packaged and thus isn't creating the folder structure you
are looking for.

Thanks,

-Jeff


-Original Message-
From: dean.hil...@gmail.com [mailto:dean.hil...@gmail.com] On Behalf Of
Dean Hiller
Sent: Wednesday, May 19, 2010 9:20 AM
To: Maven Users List
Subject: Re: how to move folder from res to res${BUILD_NUMBER} in maven?

actually, this pattern is very typical to release new versions of css,
js, etc.  Projects like richfaces and TinyMCE both use this pattern(not
to mention many more).  I don't know of any other way to get css, js
fixes immediately out to customers without the renaming(in fact, I doubt
a better solution exists here as this solution has worked great for our
last 4 releases but I am open to ideas).

As far as ${project.build.outputDirectory}, I did try that but that
seems to deal with the target/classes directory which then goes to
WEB-INF/classes when packaging a war file.  I need the files in the base
level of the war(and the property below references that correctly, BUT
the directory doesn't exist yet).

The only solution I am aware of for css, js, jpg fixes to go out in a
new release is to rename the path to the file(or the file itself) as it
is a very easy solution in build tools typically(at least it was in
ant).

Dean



On Wed, May 19, 2010 at 8:06 AM, Moll, Jeff jm...@glhec.org wrote:

 The correct property for accessing the target directory is 
 ${project.build.outputDirectory}. So if you change in your todir to 
 use ${project.build.outputDirectory} that should work. I would suggest

 investigating another approach though, there has to be a simpler 
 solution to resolve .css caching.

 Thanks

 -Jeff

 -Original Message-
 From: dean.hil...@gmail.com [mailto:dean.hil...@gmail.com] On Behalf 
 Of Dean Hiller
 Sent: Wednesday, May 19, 2010 8:53 AM
 To: users@maven.apache.org
 Subject: Re: how to move folder from res to res${BUILD_NUMBER} in
maven?

 Is there no way of doing the below?  This is like the most typical 
 thing in web applications so the browser will get the newest css, js, 
 jpg files when a new release comes out.

 thanks,
 Dean

 On Tue, May 18, 2010 at 3:28 PM, Dean Hiller d...@alvazan.com wrote:

  Our resource folder in webapps named res(which has images, js, css,
  etc) is renamed every release.  This then makes it so when we fix a 
  css, customers get the fresh one instead of the old stale one from 
  their cache(ie. they get the fix we made since this folder is always

  renamed).
 
  So, in maven, I had
  plugin
  artifactIdmaven-antrun-plugin/artifactId
  executions
  execution
  phasetest/phase
  goals
  goalrun/goal
  /goals
  configuration
  tasks
  move 
  file=${project.build.directory}/${
  project.name}-${project.version}/res
 
  todir=${project.build.directory}/${
  project.name}-${project.version}/res${BUILD_NUMBER} /
  delete
 
  file=${project.build.directory}/${
  project.name}-${project.version}/WEB-INF/components.xml /
  copy 
  file=src/main/descriptors/jboss/WEB-INF/components.xml
 
  tofile=${project.build.directory}/${
  project.name}-${project.version}/WEB-INF/components.xml /
  /tasks
  /configuration
  /execution
  /executions
  /plugin
 
  but the staging area for the webapp in target directory seems not to

  exist when my ant tasks run :( and so our build keeps on failing.
  1. How do I move the target/webappstaging/res folder to 
  target/webappstaging/resBUILDNUMBER folder OR 2. How do I move the 
  src/main/webapp/res folder to target/webappstaging/resBUILD_NUMBER
  folder and delete target/webappstaging/res folder
 
  thanks,
  Dean
 
 
 
 
 
 


 --
 -- The information contained in this communication may be 
 confidential, is intended only for the use of the recipient(s) named 
 above, and may be legally privileged.
 If the reader of this message is not the intended recipient, you are 
 hereby notified that any dissemination, distribution, or copying of 
 this communication, or any of its contents, is strictly prohibited. If

 you have received this communication in error, please notify the 
 sender immediately and

Re: how to move folder from res to res${BUILD_NUMBER} in maven?

2010-05-19 Thread Ron Wheeler

Can you not figure out a way to rename the source of the copy so that 
the names are changed before maven moves them to the output?


Ron


On 19/05/2010 10:20 AM, Dean Hiller wrote:

actually, this pattern is very typical to release new versions of css, js,
etc.  Projects like richfaces and TinyMCE both use this pattern(not to
mention many more).  I don't know of any other way to get css, js fixes
immediately out to customers without the renaming(in fact, I doubt a better
solution exists here as this solution has worked great for our last 4
releases but I am open to ideas).

As far as ${project.build.outputDirectory}, I did try that but that seems to
deal with the target/classes directory which then goes to WEB-INF/classes
when packaging a war file.  I need the files in the base level of the
war(and the property below references that correctly, BUT the directory
doesn't exist yet).

The only solution I am aware of for css, js, jpg fixes to go out in a new
release is to rename the path to the file(or the file itself) as it is a
very easy solution in build tools typically(at least it was in ant).

Dean



On Wed, May 19, 2010 at 8:06 AM, Moll, Jeffjm...@glhec.org  wrote:

   

The correct property for accessing the target directory is
${project.build.outputDirectory}. So if you change in your todir to
use ${project.build.outputDirectory} that should work. I would suggest
investigating another approach though, there has to be a simpler
solution to resolve .css caching.

Thanks

-Jeff

-Original Message-
From: dean.hil...@gmail.com [mailto:dean.hil...@gmail.com] On Behalf Of
Dean Hiller
Sent: Wednesday, May 19, 2010 8:53 AM
To: users@maven.apache.org
Subject: Re: how to move folder from res to res${BUILD_NUMBER} in maven?

Is there no way of doing the below?  This is like the most typical thing
in web applications so the browser will get the newest css, js, jpg
files when a new release comes out.

thanks,
Dean

On Tue, May 18, 2010 at 3:28 PM, Dean Hillerd...@alvazan.com  wrote:

 

Our resource folder in webapps named res(which has images, js, css,
etc) is renamed every release.  This then makes it so when we fix a
css, customers get the fresh one instead of the old stale one from
their cache(ie. they get the fix we made since this folder is always
renamed).

So, in maven, I had
 plugin
 artifactIdmaven-antrun-plugin/artifactId
 executions
 execution
 phasetest/phase
 goals
 goalrun/goal
 /goals
 configuration
 tasks
 move
file=${project.build.directory}/${
project.name}-${project.version}/res

todir=${project.build.directory}/${
project.name}-${project.version}/res${BUILD_NUMBER} /
 delete

file=${project.build.directory}/${
project.name}-${project.version}/WEB-INF/components.xml /
 copy
file=src/main/descriptors/jboss/WEB-INF/components.xml

tofile=${project.build.directory}/${
project.name}-${project.version}/WEB-INF/components.xml /
 /tasks
 /configuration
 /execution
 /executions
 /plugin

but the staging area for the webapp in target directory seems not to
exist when my ant tasks run :( and so our build keeps on failing.
1. How do I move the target/webappstaging/res folder to
target/webappstaging/resBUILDNUMBER folder OR 2. How do I move the
src/main/webapp/res folder to target/webappstaging/resBUILD_NUMBER
folder and delete target/webappstaging/res folder

thanks,
Dean






   



The information contained in this communication may be confidential, is
intended
only for the use of the recipient(s) named above, and may be legally
privileged.
If the reader of this message is not the intended recipient, you are hereby
notified that any dissemination, distribution, or copying of this
communication,
or any of its contents, is strictly prohibited. If you have received this
communication in error, please notify the sender immediately and destroy or
delete the original message and any copy of it from your computer system.
If
you have any questions concerning this message, please contact the sender.





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


 
   



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

Re: how to move folder from res to res${BUILD_NUMBER} in maven?

I tried that yesterday I believe(and right now our repository ran out of
space so I can't retry that to make sure :( ).

hm, I think I know how to do it now though, and then my question is just
why my filtering is not working on the war plugin.I think I can
1. copy from src/main/webapps/res to target/webdir-1.0.0/resBUILDNUMBER
2. then filter in war pluginI may be back with why my filtering is not
working though for a next question because I was trying to do some filtering
the other day and could not get it to work except on resources outside of
the webapps directory.

a little bit closer to a solution now I think...thanks!!!

Dean

On Wed, May 19, 2010 at 8:41 AM, Moll, Jeff jm...@glhec.org wrote:


 Try running on the package goal instead, the test phase doesn't require
 the code to be packaged and thus isn't creating the folder structure you
 are looking for.

 Thanks,

 -Jeff


 -Original Message-
 From: dean.hil...@gmail.com [mailto:dean.hil...@gmail.com] On Behalf Of
 Dean Hiller
 Sent: Wednesday, May 19, 2010 9:20 AM
 To: Maven Users List
 Subject: Re: how to move folder from res to res${BUILD_NUMBER} in maven?

 actually, this pattern is very typical to release new versions of css,
 js, etc.  Projects like richfaces and TinyMCE both use this pattern(not
 to mention many more).  I don't know of any other way to get css, js
 fixes immediately out to customers without the renaming(in fact, I doubt
 a better solution exists here as this solution has worked great for our
 last 4 releases but I am open to ideas).

 As far as ${project.build.outputDirectory}, I did try that but that
 seems to deal with the target/classes directory which then goes to
 WEB-INF/classes when packaging a war file.  I need the files in the base
 level of the war(and the property below references that correctly, BUT
 the directory doesn't exist yet).

 The only solution I am aware of for css, js, jpg fixes to go out in a
 new release is to rename the path to the file(or the file itself) as it
 is a very easy solution in build tools typically(at least it was in
 ant).

 Dean



 On Wed, May 19, 2010 at 8:06 AM, Moll, Jeff jm...@glhec.org wrote:

  The correct property for accessing the target directory is
  ${project.build.outputDirectory}. So if you change in your todir to
  use ${project.build.outputDirectory} that should work. I would suggest

  investigating another approach though, there has to be a simpler
  solution to resolve .css caching.
 
  Thanks
 
  -Jeff
 
  -Original Message-
  From: dean.hil...@gmail.com [mailto:dean.hil...@gmail.com] On Behalf
  Of Dean Hiller
  Sent: Wednesday, May 19, 2010 8:53 AM
  To: users@maven.apache.org
  Subject: Re: how to move folder from res to res${BUILD_NUMBER} in
 maven?
 
  Is there no way of doing the below?  This is like the most typical
  thing in web applications so the browser will get the newest css, js,
  jpg files when a new release comes out.
 
  thanks,
  Dean
 
  On Tue, May 18, 2010 at 3:28 PM, Dean Hiller d...@alvazan.com wrote:
 
   Our resource folder in webapps named res(which has images, js, css,
   etc) is renamed every release.  This then makes it so when we fix a
   css, customers get the fresh one instead of the old stale one from
   their cache(ie. they get the fix we made since this folder is always

   renamed).
  
   So, in maven, I had
   plugin
   artifactIdmaven-antrun-plugin/artifactId
   executions
   execution
   phasetest/phase
   goals
   goalrun/goal
   /goals
   configuration
   tasks
   move
   file=${project.build.directory}/${
   project.name}-${project.version}/res
  
   todir=${project.build.directory}/${
   project.name}-${project.version}/res${BUILD_NUMBER} /
   delete
  
   file=${project.build.directory}/${
   project.name}-${project.version}/WEB-INF/components.xml /
   copy
   file=src/main/descriptors/jboss/WEB-INF/components.xml
  
   tofile=${project.build.directory}/${
   project.name}-${project.version}/WEB-INF/components.xml /
   /tasks
   /configuration
   /execution
   /executions
   /plugin
  
   but the staging area for the webapp in target directory seems not to

   exist when my ant tasks run :( and so our build keeps on failing.
   1. How do I move the target/webappstaging/res folder to
   target/webappstaging/resBUILDNUMBER folder OR 2. How do I move the
   src/main/webapp/res folder to target/webappstaging/resBUILD_NUMBER
   folder and delete target/webappstaging/res folder
  
   thanks,
   Dean
  
  
  
  
  
  
 
 
  --

Re: how to move folder from res to res${BUILD_NUMBER} in maven?

heh, I went that direction and that hosed my dev environment up/SCM such
taht SCM wanted to check the changes in(I then figured it is really a bad
idea to generate files at all during a build in the src or input
directories).

but as in my last email, I think I am close to a solution.  Just have to try
it after we fix our artifactory from being filled up.

Dean


On Wed, May 19, 2010 at 8:49 AM, Ron Wheeler rwhee...@artifact-software.com
 wrote:

 Can you not figure out a way to rename the source of the copy so that the
 names are changed before maven moves them to the output?

 Ron



 On 19/05/2010 10:20 AM, Dean Hiller wrote:

 actually, this pattern is very typical to release new versions of css, js,
 etc.  Projects like richfaces and TinyMCE both use this pattern(not to
 mention many more).  I don't know of any other way to get css, js fixes
 immediately out to customers without the renaming(in fact, I doubt a
 better
 solution exists here as this solution has worked great for our last 4
 releases but I am open to ideas).

 As far as ${project.build.outputDirectory}, I did try that but that seems
 to
 deal with the target/classes directory which then goes to WEB-INF/classes
 when packaging a war file.  I need the files in the base level of the
 war(and the property below references that correctly, BUT the directory
 doesn't exist yet).

 The only solution I am aware of for css, js, jpg fixes to go out in a new
 release is to rename the path to the file(or the file itself) as it is a
 very easy solution in build tools typically(at least it was in ant).

 Dean



 On Wed, May 19, 2010 at 8:06 AM, Moll, Jeffjm...@glhec.org  wrote:



 The correct property for accessing the target directory is
 ${project.build.outputDirectory}. So if you change in your todir to
 use ${project.build.outputDirectory} that should work. I would suggest
 investigating another approach though, there has to be a simpler
 solution to resolve .css caching.

 Thanks

 -Jeff

 -Original Message-
 From: dean.hil...@gmail.com [mailto:dean.hil...@gmail.com] On Behalf Of
 Dean Hiller
 Sent: Wednesday, May 19, 2010 8:53 AM
 To: users@maven.apache.org
 Subject: Re: how to move folder from res to res${BUILD_NUMBER} in maven?

 Is there no way of doing the below?  This is like the most typical thing
 in web applications so the browser will get the newest css, js, jpg
 files when a new release comes out.

 thanks,
 Dean

 On Tue, May 18, 2010 at 3:28 PM, Dean Hillerd...@alvazan.com  wrote:



 Our resource folder in webapps named res(which has images, js, css,
 etc) is renamed every release.  This then makes it so when we fix a
 css, customers get the fresh one instead of the old stale one from
 their cache(ie. they get the fix we made since this folder is always
 renamed).

 So, in maven, I had
 plugin
 artifactIdmaven-antrun-plugin/artifactId
 executions
 execution
 phasetest/phase
 goals
 goalrun/goal
 /goals
 configuration
 tasks
 move
 file=${project.build.directory}/${
 project.name}-${project.version}/res

 todir=${project.build.directory}/${
 project.name}-${project.version}/res${BUILD_NUMBER} /
 delete

 file=${project.build.directory}/${
 project.name}-${project.version}/WEB-INF/components.xml /
 copy
 file=src/main/descriptors/jboss/WEB-INF/components.xml

 tofile=${project.build.directory}/${
 project.name}-${project.version}/WEB-INF/components.xml /
 /tasks
 /configuration
 /execution
 /executions
 /plugin

 but the staging area for the webapp in target directory seems not to
 exist when my ant tasks run :( and so our build keeps on failing.
 1. How do I move the target/webappstaging/res folder to
 target/webappstaging/resBUILDNUMBER folder OR 2. How do I move the
 src/main/webapp/res folder to target/webappstaging/resBUILD_NUMBER
 folder and delete target/webappstaging/res folder

 thanks,
 Dean










 
 The information contained in this communication may be confidential, is
 intended
 only for the use of the recipient(s) named above, and may be legally
 privileged.
 If the reader of this message is not the intended recipient, you are
 hereby
 notified that any dissemination, distribution, or copying of this
 communication,
 or any of its contents, is strictly prohibited. If you have received this
 communication in error, please notify the sender immediately and destroy
 or
 delete the original message and any copy of it from your computer system.
 If
 you have any questions concerning this message, please contact the
 sender.

java.lang.OutOfMemoryError: Java heap space in Wagon

2010-05-19 Thread Ron Wheeler

I am trying to build a shared library containing the CXF package and the 
upload is running out of heap space.


The jar is built and is 25Mb.

I have added this to every mvn.bat in sight.
set MAVEN_OPTS=-Xmx1024M

This is running under the latest STS version of Eclipse which is started 
by this shortcut.
C:\Program Files\SpringSource\sts-2.3.2.RELEASE\STS.exe -vmargs 
-XX:PermSize=256M -XX:MaxPermSize=1024M


The Eclipse preference for Maven points to my 2.2.1 version of maven

If I try the same pom on another PC with STS using its embedded Maven it 
also fails with a slightly different stack. It fails on the read side. 
BufferedInputStream.fill runs out of Java Heap Space.


What do I have to do get this file uploaded by wagon?



Uploading: 
http://xxx.artifact-software.com/nexus/content/repositories/releases/com/artifact_software/lms/lms-pom-cxf/1.8.2/lms-pom-cxf-1.8.2-jar-with-dependencies.jar
[INFO] 


[ERROR] FATAL ERROR
[INFO] 


[INFO] Java heap space
[INFO] 


[INFO] Trace
java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copyOf(Arrays.java:2786)
at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:94)
at 
sun.net.www.http.PosterOutputStream.write(PosterOutputStream.java:61)
at 
org.apache.maven.wagon.AbstractWagon.transfer(AbstractWagon.java:492)
at 
org.apache.maven.wagon.AbstractWagon.transfer(AbstractWagon.java:457)
at 
org.apache.maven.wagon.AbstractWagon.putTransfer(AbstractWagon.java:411)
at 
org.apache.maven.wagon.AbstractWagon.transfer(AbstractWagon.java:392)
at 
org.apache.maven.wagon.AbstractWagon.putTransfer(AbstractWagon.java:365)

at org.apache.maven.wagon.StreamWagon.put(StreamWagon.java:163)
at 
org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:317)
at 
org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:227)
at 
org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:107)
at 
org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:190)
at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)

at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at 
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at 
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)

at org.codehaus.classworlds.Launcher.main(Launcher.java:375)

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

Use profile to define property which is used in another profile activation

2010-05-19 Thread sebb

A profile (A) can be automatically activated by a property (P).

A profile (B) can also define a property (P).

So if profile B is activated it will define property P.

Will this then always activate profile A?

Seems to me that this will depend on the order in which profiles are processed.

Is this order documented and guaranteed, or might it change?

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

Maven filtering adding backslashes into Windows file paths?

2010-05-19 Thread Laird Nelson

I have an XML file that uses ${user.home} in an attribute.

When Maven filters this and expands it, it expands to:

C\:\Documents and Settings\...(and so on)

Note the backslash before the colon, which of course makes this an invalid
path on Windows.

How can I prevent Maven from doing this?

Best,
Laird

Child dependencies listed in parent pom failure to download

2010-05-19 Thread Conrad CRAMPTON PSE 52704

Hi,
Very frustrating issue that been troubling me for a couple of days now.
I am trying to use JBoss Drools in a Maven project using the following
 
dependency
groupIdorg.drools/groupId
artifactIddrools/artifactId
version5.0.1/version
typepom/type
  /dependency
 
the repository http://repository.jboss.com/maven2/org/drools/ has all the 
necessary dependencies listed in the drools pom. There is no specific jar file 
for drools but the pom just lists all the other child module dependencies. My 
expectation is that including the dependency as above will download and include 
all the child dependencies. It doesn't though. All I get is the pom downloaded.
If I use the -X option I get this listed (abbreviated). Which appears to show 
the jars being referenced but not downloaded.
 
[DEBUG] Adding managed dependencies for org.drools:drools
[DEBUG]   org.drools:drools-api:jar:5.0.1
[DEBUG]   org.drools:drools-core:jar:5.0.1
[DEBUG]   org.drools:drools-core:test-jar:tests:5.0.1:test
[DEBUG]   org.drools:drools-compiler:jar:5.0.1
[DEBUG]   org.drools:drools-compiler:test-jar:tests:5.0.1:test
[DEBUG]   org.drools:drools-jsr94:jar:5.0.1
[DEBUG]   org.drools:drools-jsr94:test-jar:tests:5.0.1:test
[DEBUG]   org.drools:drools-templates:jar:5.0.1
[DEBUG]   org.drools:drools-templates:test-jar:tests:5.0.1:test
[DEBUG]   org.drools:drools-decisiontables:jar:5.0.1
[DEBUG]   org.drools:drools-decisiontables:test-jar:tests:5.0.1:test
[DEBUG]   org.drools:drools-process-task:jar:5.0.1
[DEBUG]   org.drools:drools-docs:jar:5.0.1
[DEBUG]   org.drools:drools-server:jar:5.0.1
[DEBUG]   org.drools:drools-ant:jar:5.0.1
[DEBUG]   org.drools:drools-ant:test-jar:tests:5.0.1:test
[DEBUG]   org.drools:drools-verifier:jar:5.0.1
[DEBUG]   org.drools:drools-verifier:test-jar:tests:5.0.1:test
[DEBUG]   org.drools:drools-server:test-jar:tests:5.0.1:test
[DEBUG]   org.drools:drools-repository:jar:5.0.1
[DEBUG]   org.drools:drools-repository:test-jar:tests:5.0.1:test
[DEBUG]   org.drools:drools-pipeline:jar:5.0.1
[DEBUG]   org.drools:drools-transformer-jaxb:jar:5.0.1
[DEBUG]   org.drools:drools-transformer-jxls:jar:5.0.1
[DEBUG]   org.drools:drools-transformer-smooks:jar:5.0.1
[DEBUG]   org.drools:drools-transformer-xstream:jar:5.0.1
[DEBUG]   org.drools:drools-messenger-jms:jar:5.0.1
[DEBUG]   org.drools:drools-guvnor:jar:5.0.1
[DEBUG]   org.drools:drools-guvnor:test-jar:tests:5.0.1:test
[DEBUG]   org.drools:drools-eclipse-plugin:jar:5.0.1
[DEBUG]   org.drools.solver:drools-solver-core:jar:5.0.1
[DEBUG]   org.drools.solver:drools-solver-examples:jar:5.0.1
[DEBUG]   com.thoughtworks.xstream:xstream:jar:1.3.1
[DEBUG]   xpp3:xpp3:jar:1.1.3.4.O
[DEBUG]   org.mvel:mvel2:jar:2.0.10
[DEBUG]   joda-time:joda-time:jar:1.6
[DEBUG]   org.antlr:antlr-runtime:jar:3.1.1
[DEBUG]   org.antlr:antlr:jar:3.1.1
[DEBUG]   org.eclipse.jdt:core:jar:3.4.2.v_883_R34x
[DEBUG]   janino:janino:jar:2.5.15
[DEBUG]   xerces:xercesImpl:jar:2.9.1
[DEBUG]   xml-apis:xml-apis:jar:2.0.2
[DEBUG]   jsr94:jsr94:jar:1.1
[DEBUG]   jsr94:jsr94-tck:jar:1.0.3
[DEBUG]   jsr94:jsr94-sigtest:jar:1.1
[DEBUG]   jexcelapi:jxl:jar:2.4.2
[DEBUG]   net.sf.jxls:jxls-reader:jar:0.9.6
[DEBUG]   jboss:jboss-remoting:jar:1.4.4
[DEBUG]   org.slf4j:slf4j-api:jar:1.5.0
[DEBUG]   org.slf4j:slf4j-log4j12:jar:1.5.0
[DEBUG]   log4j:log4j:jar:1.2.14
[DEBUG]   org.apache.jackrabbit:jackrabbit-core:jar:1.4.5
[DEBUG]   javax.jcr:jcr:jar:1.0
[DEBUG]   org.tmatesoft:svnkit:jar:1.1.2
[DEBUG]   hsqldb:hsqldb:jar:1.8.0.2
[DEBUG]   javax.servlet:servlet-api:jar:2.3:provided
[DEBUG]   com.google.gwt:gwt-servlet:jar:1.5.2
[DEBUG]   commons-fileupload:commons-fileupload:jar:1.2.1
[DEBUG]   commons-io:commons-io:jar:1.4
[DEBUG]   com.gwtext:gwtext:jar:2.0.5
[DEBUG]   foxtrot:foxtrot:jar:2.0
[DEBUG]   com.jgoodies:looks:jar:2.2.0
[DEBUG]   com.jgoodies:forms:jar:1.2.1
[DEBUG]   commons-lang:commons-lang:jar:2.3
[DEBUG]   org.apache.commons:commons-io:jar:1.3.2
[DEBUG]   org.jboss:jboss-vfs:jar:2.0.0.GA
[DEBUG]   org.drools:drools:pom:5.0.1:compile (selected for compile)
[DEBUG] Plugin dependencies for:
 
Can anyone help here as this is driving me nuts? I don't particularly want to 
download all of these individually and add to my archiva repository. (I don't 
know if this is relevant but I am using Archiva with a couple of proxy 
connectors to main maven repo and to JBoss repository).
 
Thanks
Conrad
 
 
Conrad Crampton


Software Development Manager
Force Headquarters
8 Edinburgh Square
Sutton Road
Maidstone
ME15 9BZ
01622 652885 (ext)
19-2885 (internal)
07972 004551  (mobile)
conrad.cramp...@kent.pnn.police.uk

-- 
This email and any other accompanying document (s) contain information from 
Kent Police, which is confidential or privileged.  The information is intended 
to be for the exclusive use of the individual(s) or bodies to whom it is 
addressed. The content including any subsequent replies could be disclosable if 
relating to a criminal investigation or civil

Re: java.lang.OutOfMemoryError: Java heap space in Wagon

2010-05-19 Thread Richard Seddon

M2Eclipse doesn't launch the external Maven with mvn.bat.

You can set the heap options in the JRE tab of the Maven launch configuration.

Rich

On May 19, 2010, at 10:14 AM, Ron Wheeler wrote:

 I am trying to build a shared library containing the CXF package and the 
 upload is running out of heap space.
 
 The jar is built and is 25Mb.
 
 I have added this to every mvn.bat in sight.
 set MAVEN_OPTS=-Xmx1024M
 
 This is running under the latest STS version of Eclipse which is started by 
 this shortcut.
 C:\Program Files\SpringSource\sts-2.3.2.RELEASE\STS.exe -vmargs 
 -XX:PermSize=256M -XX:MaxPermSize=1024M
 
 The Eclipse preference for Maven points to my 2.2.1 version of maven
 
 If I try the same pom on another PC with STS using its embedded Maven it also 
 fails with a slightly different stack. It fails on the read side. 
 BufferedInputStream.fill runs out of Java Heap Space.
 
 What do I have to do get this file uploaded by wagon?
 
 
 
 Uploading: 
 http://xxx.artifact-software.com/nexus/content/repositories/releases/com/artifact_software/lms/lms-pom-cxf/1.8.2/lms-pom-cxf-1.8.2-jar-with-dependencies.jar
 [INFO] 
 
 [ERROR] FATAL ERROR
 [INFO] 
 
 [INFO] Java heap space
 [INFO] 
 
 [INFO] Trace
 java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copyOf(Arrays.java:2786)
at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:94)
at sun.net.www.http.PosterOutputStream.write(PosterOutputStream.java:61)
at org.apache.maven.wagon.AbstractWagon.transfer(AbstractWagon.java:492)
at org.apache.maven.wagon.AbstractWagon.transfer(AbstractWagon.java:457)
at org.apache.maven.wagon.AbstractWagon.putTransfer(AbstractWagon.java:411)
at org.apache.maven.wagon.AbstractWagon.transfer(AbstractWagon.java:392)
at org.apache.maven.wagon.AbstractWagon.putTransfer(AbstractWagon.java:365)
at org.apache.maven.wagon.StreamWagon.put(StreamWagon.java:163)
at 
 org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:317)
at 
 org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:227)
at 
 org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:107)
at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:190)
at 
 org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
 
 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org
 


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

Re: move folder from res to res${BUILD_NUMBER} easy Filtering problem...

ok, so tried out my solution and the copy is working ;) but it is not
filtering our the res folder in the war file plugin for some reason.  How do
I fix this xml so it filters out res folder...

execution
phasetest/phase
goals
goalrun/goal
/goals
configuration
tasks
echo message=Running jboss ant
tasks/
mkdir
dir=${project.build.directory}/${project.name
}-${project.version}/res-${BUILD_NUMBER}/
copy
todir=${project.build.directory}/${project.name
}-${project.version}/res-${BUILD_NUMBER}
fileset
dir=src/main/webapp/res
  include name=**/
/fileset
/copy
copy
file=src/main/descriptors/jboss/WEB-INF/components.xml

tofile=${project.build.directory}/${project.name}-${project.version}/WEB-INF/components.xml
/
/tasks
/configuration
/execution
/executions
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-war-plugin/artifactId
version2.0/version
configuration
  webResources
resource
  !-- this is relative to the pom.xml directory
--
  directorysrc/main/webapp/directory
  !-- the list has a default value of ** --
  excludes
excluderes**/exclude
  /excludes
/resource
  /webResources

archive
manifestEntries

Svn-Revision${SVN_REVISION}/Svn-Revision
Build-Tag${BUILD_TAG}/Build-Tag

Build-Number${BUILD_NUMBER}/Build-Number
Build-Id${BUILD_ID}/Build-Id
/manifestEntries
/archive
/configuration
/plugin

On Wed, May 19, 2010 at 8:53 AM, Dean Hiller d...@alvazan.com wrote:

 heh, I went that direction and that hosed my dev environment up/SCM such
 taht SCM wanted to check the changes in(I then figured it is really a bad
 idea to generate files at all during a build in the src or input
 directories).

 but as in my last email, I think I am close to a solution.  Just have to
 try it after we fix our artifactory from being filled up.

 Dean



 On Wed, May 19, 2010 at 8:49 AM, Ron Wheeler 
 rwhee...@artifact-software.com wrote:

 Can you not figure out a way to rename the source of the copy so that the
 names are changed before maven moves them to the output?

 Ron



 On 19/05/2010 10:20 AM, Dean Hiller wrote:

 actually, this pattern is very typical to release new versions of css,
 js,
 etc.  Projects like richfaces and TinyMCE both use this pattern(not to
 mention many more).  I don't know of any other way to get css, js fixes
 immediately out to customers without the renaming(in fact, I doubt a
 better
 solution exists here as this solution has worked great for our last 4
 releases but I am open to ideas).

 As far as ${project.build.outputDirectory}, I did try that but that seems
 to
 deal with the target/classes directory which then goes to WEB-INF/classes
 when packaging a war file.  I need the files in the base level of the
 war(and the property below references that correctly, BUT the directory
 doesn't exist yet).

 The only solution I am aware of for css, js, jpg fixes to go out in a new
 release is to rename the path to the file(or the file itself) as it is a
 very easy solution in build tools typically(at least it was in ant).

 Dean



 On Wed, May 19, 2010 at 8:06 AM, Moll, Jeffjm...@glhec.org  wrote:



 The correct property for accessing the target directory is
 ${project.build.outputDirectory}. So if you change in your todir to
 use ${project.build.outputDirectory} that should work. I would suggest
 investigating another approach though, there has to be a simpler
 solution to resolve .css caching.

 Thanks

 -Jeff

 -Original Message-
 From: dean.hil...@gmail.com [mailto:dean.hil...@gmail.com] On Behalf Of
 Dean Hiller
 Sent: Wednesday, May 19, 2010 8:53 AM
 To: users@maven.apache.org
 Subject: Re: how to move folder from res to res${BUILD_NUMBER} in maven?

 Is there no

Broken mvn site

2010-05-19 Thread Tim Fulmer

Hello,

Yesterday we noticed an error when running mvn site to generate cobertura
reports to track down some coverage issues.  Turns out this was caused by a
snapshot update mandated by the special way Maven handles plugin versioning.
 Things got even more special when trying to specify a version of
org.apache.maven.plugins:maven-project-info-reports-plugin.  Turns out
plugin management doesn't work for reporting.  The version specified in
plugin management is ignored in reporting and the current version is used.
 Even though the current documentation on configuring reporting shows a
plugin management configuration.  The solution was to spam a version
configuration across 20 some odd POM files.  I'm sure we missed a few.

This isn't the first time we've been bitten by Maven's special plugin
versioning and dependency management.  Other's have ongoing issues with this
as well. My question is why hasn't this been fixed yet?  Why is plugin
management the one place where Maven's own versioning and dependency
management practices are completely ignored in favor of something that's
obviously broken?  When is it going to be fixed?

-- Tim

RE: Maven filtering adding backslashes into Windows file paths?

2010-05-19 Thread Jamie Whitehouse

I think you want to be using a maven-resources-plugin that's version
2.4.1 or greater, see MRESOURCES-100 and MRESOURCES-106.

http://jira.codehaus.org/browse/MRESOURCES-100 
http://jira.codehaus.org/browse/MRESOURCES-106

 -Original Message-
 From: Laird Nelson [mailto:ljnel...@gmail.com] 
 Sent: Wednesday, May 19, 2010 11:55 AM
 To: Maven Users List
 Subject: Maven filtering adding backslashes into Windows file paths?
 
 I have an XML file that uses ${user.home} in an attribute.
 
 When Maven filters this and expands it, it expands to:
 
 C\:\Documents and Settings\...(and so on)
 
 Note the backslash before the colon, which of course makes 
 this an invalid path on Windows.
 
 How can I prevent Maven from doing this?
 
 Best,
 Laird
 


---
CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain 
confidential and proprietary information of Alcatel-Lucent and/or its 
affiliated entities. Access by the intended recipient only is authorized. Any 
liability arising from any party acting, or refraining from acting, on any 
information contained in this e-mail is hereby excluded. If you are not the 
intended recipient, please notify the sender immediately, destroy the original 
transmission and its attachments and do not disclose the contents to any other 
person, use it for any purpose, or store or copy the information in any medium. 
Copyright in this e-mail and any attachments belongs to Alcatel-Lucent and/or 
its affiliated entities.


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

Re: Child dependencies listed in parent pom failure to download

2010-05-19 Thread Wendy Smoak

On Wed, May 19, 2010 at 12:13 PM, Conrad CRAMPTON PSE 52704
conrad.cramp...@kent.pnn.police.uk wrote:

 the repository http://repository.jboss.com/maven2/org/drools/ has all the 
 necessary dependencies listed in the drools pom. There is no specific jar 
 file for drools but the pom just lists all the other child module 
 dependencies. My expectation is that including the dependency as above will 
 download and include all the child dependencies. It doesn't though. All I get 
 is the pom downloaded.

child module dependencies doesn't make sense.  Being listed as a
module is not the same as being listed as a dependency.  Modules are
for building, but they do not mean that if you depend on that pom, you
will get all the sub-modules as transitive dependencies.

I looked in the pom, and as the message says, they are listed as
_managed_ dependencies (in dependencyManagement).  That's for the
Drools build, not for consumers of it.

You probably want to declare a dependency on drools-core and some of
the others depending on what your project needs.

-- 
Wendy

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

RE: move folder from res to res${BUILD_NUMBER} easy Filtering problem...

Make sure you have the resource filtering turned on. By default it is
not so you will need something like this:

  build
resources
  resource
directorysrc/main/resources/directory
filteringtrue/filtering
  /resource
/resources
  /build 



-Original Message-
From: dean.hil...@gmail.com [mailto:dean.hil...@gmail.com] On Behalf Of
Dean Hiller
Sent: Wednesday, May 19, 2010 12:03 PM
To: Maven Users List
Subject: Re: move folder from res to res${BUILD_NUMBER} easy Filtering
problem...

ok, so tried out my solution and the copy is working ;) but it is not
filtering our the res folder in the war file plugin for some reason.
How do I fix this xml so it filters out res folder...

execution
phasetest/phase
goals
goalrun/goal
/goals
configuration
tasks
echo message=Running jboss ant
tasks/
mkdir
dir=${project.build.directory}/${project.name
}-${project.version}/res-${BUILD_NUMBER}/
copy
todir=${project.build.directory}/${project.name
}-${project.version}/res-${BUILD_NUMBER}
fileset
dir=src/main/webapp/res
  include name=**/
/fileset
/copy
copy
file=src/main/descriptors/jboss/WEB-INF/components.xml

tofile=${project.build.directory}/${project.name}-${project.version}/WE
B-INF/components.xml
/
/tasks
/configuration
/execution
/executions
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-war-plugin/artifactId
version2.0/version
configuration
  webResources
resource
  !-- this is relative to the pom.xml
directory
--
  directorysrc/main/webapp/directory
  !-- the list has a default value of **
--
  excludes
excluderes**/exclude
  /excludes
/resource
  /webResources

archive
manifestEntries

Svn-Revision${SVN_REVISION}/Svn-Revision
Build-Tag${BUILD_TAG}/Build-Tag

Build-Number${BUILD_NUMBER}/Build-Number
Build-Id${BUILD_ID}/Build-Id
/manifestEntries
/archive
/configuration
/plugin

On Wed, May 19, 2010 at 8:53 AM, Dean Hiller d...@alvazan.com wrote:

 heh, I went that direction and that hosed my dev environment up/SCM 
 such taht SCM wanted to check the changes in(I then figured it is 
 really a bad idea to generate files at all during a build in the src 
 or input directories).

 but as in my last email, I think I am close to a solution.  Just have 
 to try it after we fix our artifactory from being filled up.

 Dean



 On Wed, May 19, 2010 at 8:49 AM, Ron Wheeler  
 rwhee...@artifact-software.com wrote:

 Can you not figure out a way to rename the source of the copy so that

 the names are changed before maven moves them to the output?

 Ron



 On 19/05/2010 10:20 AM, Dean Hiller wrote:

 actually, this pattern is very typical to release new versions of 
 css, js, etc.  Projects like richfaces and TinyMCE both use this 
 pattern(not to mention many more).  I don't know of any other way to

 get css, js fixes immediately out to customers without the 
 renaming(in fact, I doubt a better solution exists here as this 
 solution has worked great for our last 4 releases but I am open to 
 ideas).

 As far as ${project.build.outputDirectory}, I did try that but that 
 seems to deal with the target/classes directory which then goes to 
 WEB-INF/classes when packaging a war file.  I need the files in the 
 base level of the war(and the property below references that 
 correctly, BUT the directory doesn't exist yet).

 The only solution I am aware of for css, js, jpg fixes to go out in 
 a new release is to rename the path to the file(or the file itself) 
 as it is a very easy solution in build tools typically(at least it
was in ant).

 Dean



 On Wed, May 19, 2010 at 8:06 AM, Moll,

Re: Maven filtering adding backslashes into Windows file paths?

2010-05-19 Thread Laird Nelson

On Wed, May 19, 2010 at 12:47 PM, Jamie Whitehouse 
jamie.whiteho...@alcatel-lucent.com wrote:

 I think you want to be using a maven-resources-plugin that's version
 2.4.1 or greater, see MRESOURCES-100 and MRESOURCES-106.


Thank you; that did it.

Best,
Laird

Re: move folder from res to res${BUILD_NUMBER} easy Filtering problem...

I am missing just one more thing.  The doc here
http://maven.apache.org/guides/getting-started/index.html#How_do_I_filter_resource_files

is about slipping in property files oddly enough not about filtering out
files(I just want to exclude one folder during the build).  I see the

filters
   filtersome properties file for slipping in params/filter
/filters

How do I add my exclusion of my res folder?

I tried copying the example you gave into the build element and adding
excludes as well...

   resources
 resource
   directorysrc/main/webapp/directory
   filteringtrue/filtering
   excludes
  exclude**res**/exclude
/excludes

/resource
/resources

Still not working :(

thanks,
Dean

On Wed, May 19, 2010 at 11:29 AM, Moll, Jeff jm...@glhec.org wrote:

 Make sure you have the resource filtering turned on. By default it is
 not so you will need something like this:

  build
resources
  resource
directorysrc/main/resources/directory
filteringtrue/filtering
  /resource
/resources
  /build



 -Original Message-
 From: dean.hil...@gmail.com [mailto:dean.hil...@gmail.com] On Behalf Of
 Dean Hiller
 Sent: Wednesday, May 19, 2010 12:03 PM
 To: Maven Users List
 Subject: Re: move folder from res to res${BUILD_NUMBER} easy Filtering
 problem...

 ok, so tried out my solution and the copy is working ;) but it is not
 filtering our the res folder in the war file plugin for some reason.
 How do I fix this xml so it filters out res folder...

execution
phasetest/phase
goals
goalrun/goal
/goals
configuration
tasks
echo message=Running jboss ant
 tasks/
mkdir
 dir=${project.build.directory}/${project.name
 }-${project.version}/res-${BUILD_NUMBER}/
copy
 todir=${project.build.directory}/${project.name
 }-${project.version}/res-${BUILD_NUMBER}
fileset
 dir=src/main/webapp/res
  include name=**/
/fileset
/copy
copy
 file=src/main/descriptors/jboss/WEB-INF/components.xml

 tofile=${project.build.directory}/${project.name}-${project.version}/WE
 B-INF/components.xml
 /
/tasks
/configuration
/execution
/executions
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-war-plugin/artifactId
version2.0/version
configuration
  webResources
resource
  !-- this is relative to the pom.xml
 directory
 --
  directorysrc/main/webapp/directory
  !-- the list has a default value of **
 --
  excludes
excluderes**/exclude
  /excludes
/resource
  /webResources

archive
manifestEntries

 Svn-Revision${SVN_REVISION}/Svn-Revision
Build-Tag${BUILD_TAG}/Build-Tag

 Build-Number${BUILD_NUMBER}/Build-Number
Build-Id${BUILD_ID}/Build-Id
/manifestEntries
/archive
/configuration
/plugin

 On Wed, May 19, 2010 at 8:53 AM, Dean Hiller d...@alvazan.com wrote:

  heh, I went that direction and that hosed my dev environment up/SCM
  such taht SCM wanted to check the changes in(I then figured it is
  really a bad idea to generate files at all during a build in the src
  or input directories).
 
  but as in my last email, I think I am close to a solution.  Just have
  to try it after we fix our artifactory from being filled up.
 
  Dean
 
 
 
  On Wed, May 19, 2010 at 8:49 AM, Ron Wheeler 
  rwhee...@artifact-software.com wrote:
 
  Can you not figure out a way to rename the source of the copy so that

  the names are changed before maven moves them to the output?
 
  Ron
 
 
 
  On 19/05/2010 10:20 AM, Dean Hiller wrote:
 
  actually, this

Re: Broken mvn site

I'm pretty sure you're close to pissing some people off. why hasn't this
been fixed yet and When is it going to be fixed is not the right wording
for open source projects where you're not shipping in anything yourself.
Creating jiras and providing patches (with test cases) is the way to go.

/Anders

On Wed, May 19, 2010 at 19:05, Tim Fulmer tful...@dslextreme.com wrote:

 Hello,

 Yesterday we noticed an error when running mvn site to generate cobertura
 reports to track down some coverage issues.  Turns out this was caused by a
 snapshot update mandated by the special way Maven handles plugin
 versioning.
  Things got even more special when trying to specify a version of
 org.apache.maven.plugins:maven-project-info-reports-plugin.  Turns out
 plugin management doesn't work for reporting.  The version specified in
 plugin management is ignored in reporting and the current version is used.
  Even though the current documentation on configuring reporting shows a
 plugin management configuration.  The solution was to spam a version
 configuration across 20 some odd POM files.  I'm sure we missed a few.

 This isn't the first time we've been bitten by Maven's special plugin
 versioning and dependency management.  Other's have ongoing issues with
 this
 as well. My question is why hasn't this been fixed yet?  Why is plugin
 management the one place where Maven's own versioning and dependency
 management practices are completely ignored in favor of something that's
 obviously broken?  When is it going to be fixed?

 -- Tim

Re: maven-plugin-api com.thoughtworks.qdox.parser.ParseException: syntax error

2010-05-19 Thread Kaeptenblaubaer


Hi

I m also facing the same issue . Where you able to solve your issue?

-- 
View this message in context: 
http://old.nabble.com/maven-plugin-api-com.thoughtworks.qdox.parser.ParseException%3A-syntax-error-tp23874877p28612065.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: Broken mvn site

2010-05-19 Thread Lukas Theussl



Thanks!

-Lukas


Anders Hammar wrote:

I'm pretty sure you're close to pissing some people off. why hasn't this
been fixed yet and When is it going to be fixed is not the right wording
for open source projects where you're not shipping in anything yourself.
Creating jiras and providing patches (with test cases) is the way to go.

/Anders

On Wed, May 19, 2010 at 19:05, Tim Fulmertful...@dslextreme.com  wrote:


Hello,

Yesterday we noticed an error when running mvn site to generate cobertura
reports to track down some coverage issues.  Turns out this was caused by a
snapshot update mandated by the special way Maven handles plugin
versioning.
  Things got even more special when trying to specify a version of
org.apache.maven.plugins:maven-project-info-reports-plugin.  Turns out
plugin management doesn't work for reporting.  The version specified in
plugin management is ignored in reporting and the current version is used.
  Even though the current documentation on configuring reporting shows a
plugin management configuration.  The solution was to spam a version
configuration across 20 some odd POM files.  I'm sure we missed a few.

This isn't the first time we've been bitten by Maven's special plugin
versioning and dependency management.  Other's have ongoing issues with
this
as well. My question is why hasn't this been fixed yet?  Why is plugin
management the one place where Maven's own versioning and dependency
management practices are completely ignored in favor of something that's
obviously broken?  When is it going to be fixed?

-- Tim





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

Re: java.lang.OutOfMemoryError: Java heap space in Wagon

2010-05-19 Thread Ron Wheeler


Thank you.

That was it and I am back on the build binge again. Only 20 more 
projects to deploy. :-)


Ron


On 19/05/2010 12:44 PM, Richard Seddon wrote:

M2Eclipse doesn't launch the external Maven with mvn.bat.

You can set the heap options in the JRE tab of the Maven launch configuration.

Rich

On May 19, 2010, at 10:14 AM, Ron Wheeler wrote:

   

I am trying to build a shared library containing the CXF package and the upload 
is running out of heap space.

The jar is built and is 25Mb.

I have added this to every mvn.bat in sight.
set MAVEN_OPTS=-Xmx1024M

This is running under the latest STS version of Eclipse which is started by 
this shortcut.
C:\Program Files\SpringSource\sts-2.3.2.RELEASE\STS.exe -vmargs 
-XX:PermSize=256M -XX:MaxPermSize=1024M

The Eclipse preference for Maven points to my 2.2.1 version of maven

If I try the same pom on another PC with STS using its embedded Maven it also 
fails with a slightly different stack. It fails on the read side. 
BufferedInputStream.fill runs out of Java Heap Space.

What do I have to do get this file uploaded by wagon?



Uploading: 
http://xxx.artifact-software.com/nexus/content/repositories/releases/com/artifact_software/lms/lms-pom-cxf/1.8.2/lms-pom-cxf-1.8.2-jar-with-dependencies.jar
[INFO] 
[ERROR] FATAL ERROR
[INFO] 
[INFO] Java heap space
[INFO] 
[INFO] Trace
java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copyOf(Arrays.java:2786)
at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:94)
at sun.net.www.http.PosterOutputStream.write(PosterOutputStream.java:61)
at org.apache.maven.wagon.AbstractWagon.transfer(AbstractWagon.java:492)
at org.apache.maven.wagon.AbstractWagon.transfer(AbstractWagon.java:457)
at org.apache.maven.wagon.AbstractWagon.putTransfer(AbstractWagon.java:411)
at org.apache.maven.wagon.AbstractWagon.transfer(AbstractWagon.java:392)
at org.apache.maven.wagon.AbstractWagon.putTransfer(AbstractWagon.java:365)
at org.apache.maven.wagon.StreamWagon.put(StreamWagon.java:163)
at 
org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:317)
at 
org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:227)
at 
org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:107)
at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:190)
at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)

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

 


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


   



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

Re: Broken mvn site

2010-05-19 Thread Tim Fulmer

Yeah, realized that just after hitting send.  Sorry about that.  It's just a
little frustrating cause I'm not sure what to do.  Usually I can hack the
source code and figure something out, but honestly with this one I don't
know where to start.  Again, sorry if I pissed anyone off.  Maven is a great
project, probably one of the best things to happen to Java.  It's a tool I
use all day, every day.  Thanks definitely go out to the Maven team for all
the hard work.  This was definitely not the appropriate forum to vent
frustration.  I really should have known better.

-- Tim


On Wed, May 19, 2010 at 10:53 AM, Anders Hammar and...@hammar.net wrote:

 I'm pretty sure you're close to pissing some people off. why hasn't this
 been fixed yet and When is it going to be fixed is not the right wording
 for open source projects where you're not shipping in anything yourself.
 Creating jiras and providing patches (with test cases) is the way to go.

 /Anders

 On Wed, May 19, 2010 at 19:05, Tim Fulmer tful...@dslextreme.com wrote:

  Hello,
 
  Yesterday we noticed an error when running mvn site to generate cobertura
  reports to track down some coverage issues.  Turns out this was caused by
 a
  snapshot update mandated by the special way Maven handles plugin
  versioning.
   Things got even more special when trying to specify a version of
  org.apache.maven.plugins:maven-project-info-reports-plugin.  Turns out
  plugin management doesn't work for reporting.  The version specified in
  plugin management is ignored in reporting and the current version is
 used.
   Even though the current documentation on configuring reporting shows a
  plugin management configuration.  The solution was to spam a version
  configuration across 20 some odd POM files.  I'm sure we missed a few.
 
  This isn't the first time we've been bitten by Maven's special plugin
  versioning and dependency management.  Other's have ongoing issues with
  this
  as well. My question is why hasn't this been fixed yet?  Why is plugin
  management the one place where Maven's own versioning and dependency
  management practices are completely ignored in favor of something that's
  obviously broken?  When is it going to be fixed?
 
  -- Tim

Re: Broken mvn site

2010-05-19 Thread Wendy Smoak

On Wed, May 19, 2010 at 1:05 PM, Tim Fulmer tful...@dslextreme.com wrote:

  Even though the current documentation on configuring reporting shows a
 plugin management configuration.  The solution was to spam a version
 configuration across 20 some odd POM files.  I'm sure we missed a few.

What docs were you looking at, so they can be improved?  At least
mention it here, but it needs to get into JIRA so it won't be
overlooked.

You might be able to set a property once and use an ${expression} for
the version to avoid repeating it all over the place, depending on how
your pom hierarchy is arranged.  Do you have an organization level
parent pom in place?

What Maven version are you using?  No idea if this is something that's
better in Maven 3, but you might try the latest release and see if
you're not already using it.

-- 
Wendy

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

Re: Broken mvn site

2010-05-19 Thread Benson Margulies

Doesn't the new 'no variables in versions' policy in mvn 3 make this
situation, ahem, even more difficult? Or doesn't that policy apply to plugin
version elements in the reporting section.

In defense of the OP: he followed a published official example that was
actively misleading. I for one think he's entitled to a small show of
temper.

On Wed, May 19, 2010 at 2:55 PM, Wendy Smoak wsm...@gmail.com wrote:

 On Wed, May 19, 2010 at 1:05 PM, Tim Fulmer tful...@dslextreme.com
 wrote:

   Even though the current documentation on configuring reporting shows a
  plugin management configuration.  The solution was to spam a version
  configuration across 20 some odd POM files.  I'm sure we missed a few.

 What docs were you looking at, so they can be improved?  At least
 mention it here, but it needs to get into JIRA so it won't be
 overlooked.

 You might be able to set a property once and use an ${expression} for
 the version to avoid repeating it all over the place, depending on how
 your pom hierarchy is arranged.  Do you have an organization level
 parent pom in place?

 What Maven version are you using?  No idea if this is something that's
 better in Maven 3, but you might try the latest release and see if
 you're not already using it.

 --
 Wendy

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

[ANN] FEST JavaFX Compiler Maven Plug-in 1.0b2 released!

2010-05-19 Thread Alex Ruiz

Greetings,

I'm happy to announce that the FEST JavaFX Compiler Maven Plug-in 1.0b2 is
out. This version allows compilation of JavaFX test sources.

More details (including an example on how to use it) can be found at
http://alexruiz.developerblogs.com/?p=1197

Cheers,
-Alex

Anyone have experience using maven with Aldon Lifecycle Manager

2010-05-19 Thread Gordon Cody

Has anyone on the list had to integrate maven with the
Aldon Lifecycle Manager ? Any experiences to share ?

-Regards
Gord Cody

Re: should be an easy Filtering question?

This question should be really easyI would assume even novices would
know the answer here??  Any takersplease  I would really like to get
this working.

On Wed, May 19, 2010 at 11:46 AM, Dean Hiller d...@alvazan.com wrote:

 I am missing just one more thing.  The doc here
 http://maven.apache.org/guides/getting-started/index.html#How_do_I_filter_resource_files

 is about slipping in property files oddly enough not about filtering out
 files(I just want to exclude one folder during the build).  I see the

 filters
filtersome properties file for slipping in params/filter
 /filters

 How do I add my exclusion of my res folder?

 I tried copying the example you gave into the build element and adding
 excludes as well...

resources
  resource
directorysrc/main/webapp/directory
filteringtrue/filtering

excludes
   exclude**res**/exclude
 /excludes

 /resource
 /resources

 Still not working :(

 thanks,
 Dean


 On Wed, May 19, 2010 at 11:29 AM, Moll, Jeff jm...@glhec.org wrote:

 Make sure you have the resource filtering turned on. By default it is
 not so you will need something like this:

  build
resources
  resource
directorysrc/main/resources/directory
filteringtrue/filtering
  /resource
/resources
  /build



 -Original Message-
 From: dean.hil...@gmail.com [mailto:dean.hil...@gmail.com] On Behalf Of
 Dean Hiller
 Sent: Wednesday, May 19, 2010 12:03 PM
 To: Maven Users List
 Subject: Re: move folder from res to res${BUILD_NUMBER} easy Filtering
 problem...

 ok, so tried out my solution and the copy is working ;) but it is not
 filtering our the res folder in the war file plugin for some reason.
 How do I fix this xml so it filters out res folder...

execution
phasetest/phase
goals
goalrun/goal
/goals
configuration
tasks
echo message=Running jboss ant
 tasks/
mkdir
 dir=${project.build.directory}/${project.name
 }-${project.version}/res-${BUILD_NUMBER}/
copy
 todir=${project.build.directory}/${project.name
 }-${project.version}/res-${BUILD_NUMBER}
fileset
 dir=src/main/webapp/res
  include name=**/
/fileset
/copy
copy
 file=src/main/descriptors/jboss/WEB-INF/components.xml

 tofile=${project.build.directory}/${project.name}-${project.version}/WE
 B-INF/components.xml
 /
/tasks
/configuration
/execution
/executions
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-war-plugin/artifactId
version2.0/version
configuration
  webResources
resource
  !-- this is relative to the pom.xml
 directory
 --
  directorysrc/main/webapp/directory
  !-- the list has a default value of **
 --
  excludes
excluderes**/exclude
  /excludes
/resource
  /webResources

archive
manifestEntries

 Svn-Revision${SVN_REVISION}/Svn-Revision
Build-Tag${BUILD_TAG}/Build-Tag

 Build-Number${BUILD_NUMBER}/Build-Number
Build-Id${BUILD_ID}/Build-Id
/manifestEntries
/archive
/configuration
/plugin

 On Wed, May 19, 2010 at 8:53 AM, Dean Hiller d...@alvazan.com wrote:

  heh, I went that direction and that hosed my dev environment up/SCM
  such taht SCM wanted to check the changes in(I then figured it is
  really a bad idea to generate files at all during a build in the src
  or input directories).
 
  but as in my last email, I think I am close to a solution.  Just have
  to try it after we fix our artifactory from being filled up.
 
  Dean
 
 
 
  On Wed, May 19, 2010 at 8:49 AM, Ron Wheeler

Re: Ear Plugin Version 5 issue

2010-05-19 Thread Stephane Nicoll

Sorry I don't understand. Can you create an issue and attach a project that
reproduce the problem?

On Tue, May 18, 2010 at 4:00 PM, Wale12 chris.w...@ontario.ca wrote:

I changed the

earSourceDirectory./earSourceDirectory

earSourceDirectory${basedir}/earSourceDirectory

No difference in my build though.

Thanks.

Wale12 wrote:

I go into the maven repository to
\org\apache\maven\plugins\maven-ear-plugin and delete the 2.4.1. folder
then run the build again.

snicoll wrote:

And it probably doesn't. I am not sure I get your it works if I delete
the
plugin thing. Can you replace the . by ${basedir} to avoid any
reactor-related issue?

Thx,
S.

On Fri, May 14, 2010 at 6:01 PM, Wale12 chris.w...@ontario.ca wrote:

Fair point.

I am using hudson so this is all I get.

Deployment descriptor:

D:\Hudson\jobs\HCV_1.0_Dev\workspace\hud_HCV_1.0_view1\UcmVob08A\Src_Java\HCVWebService\HCVServiceEAR\target\HCVServiceEAR\META-INF\application.xml
does not exist.

snicoll wrote:

uh? Why on Earth would you do this:

earSourceDirectory./earSourceDirectory

Can you post the full stacktrace. Are you running from the reactor
when
it
happens?

On Fri, May 14, 2010 at 4:21 PM, Wale12 chris.w...@ontario.ca
wrote:

I have a weird issue with a project I have. I am using maven 2 and
version
2.4.1 of the ear plugin and am using the version 5 no
application.xml
options for packing the ear.

plugin
artifactIdmaven-ear-plugin/artifactId
version2.4.1/version
configuration
version5/version
generateApplicationXmlfalse/generateApplicationXml
earSourceDirectory./earSourceDirectory

earSourceExcludespom.xml,pom.properties,.settings\,lib\,target\,.project/earSourceExcludes

finalName${project.artifactId}-${project.version}.${BUILD_NUMBER}/finalName
modules
:
/modules
archive
addMavenDescriptorfalse/addMavenDescriptor
manifestEntries

Implementation-Version${PRJVERSION}/Implementation-Version
/manifestEntries
/archive
/configuration
/plugin

On one of my projects that use these option, I have several, I am
finding
that I need to delete the plugin in the maven repository so that I
get a
fresh download of the plugin to get it to package the ear and not
complain
about not having an application xml file. Any time I already have
the
plugin in the repository and build the project it fails with the
application.xml does not exist error. If I go and then delete the
plugin
again and built the project it builds fine.

This does not happen with other project that I have using the same
options?

Any idea why this would happen?

Thanks.

--
View this message in context:

http://old.nabble.com/Ear-Plugin-Version-5-issue-tp28560014p28560014.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

--
View this message in context:

http://old.nabble.com/Ear-Plugin-Version-5-issue-tp28560014p28561249.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

--
View this message in context:
http://old.nabble.com/Ear-Plugin-Version-5-issue-tp28560014p28596361.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: should be an easy Filtering question?

Try this page is you have not done so yet, this may be more helpful than
the previous example I passed along assuming you are using the
war-plug-in.
http://maven.apache.org/plugins/maven-war-plugin/examples/adding-filteri
ng-webresources.html

-Jeff

-Original Message-
From: dean.hil...@gmail.com [mailto:dean.hil...@gmail.com] On Behalf Of
Dean Hiller
Sent: Wednesday, May 19, 2010 3:17 PM
To: Maven Users List
Subject: Re: should be an easy Filtering question?

This question should be really easyI would assume even novices would
know the answer here??  Any takersplease  I would really like to
get this working.

On Wed, May 19, 2010 at 11:46 AM, Dean Hiller d...@alvazan.com wrote:

 I am missing just one more thing.  The doc here 
 http://maven.apache.org/guides/getting-started/index.html#How_do_I_fil
 ter_resource_files

 is about slipping in property files oddly enough not about filtering 
 out files(I just want to exclude one folder during the build).  I see 
 the

 filters
filtersome properties file for slipping in params/filter 
 /filters

 How do I add my exclusion of my res folder?

 I tried copying the example you gave into the build element and adding

 excludes as well...

resources
  resource
directorysrc/main/webapp/directory
filteringtrue/filtering

excludes
   exclude**res**/exclude
 /excludes

 /resource
 /resources

 Still not working :(

 thanks,
 Dean


 On Wed, May 19, 2010 at 11:29 AM, Moll, Jeff jm...@glhec.org wrote:

 Make sure you have the resource filtering turned on. By default it is

 not so you will need something like this:

  build
resources
  resource
directorysrc/main/resources/directory
filteringtrue/filtering
  /resource
/resources
  /build



 -Original Message-
 From: dean.hil...@gmail.com [mailto:dean.hil...@gmail.com] On Behalf 
 Of Dean Hiller
 Sent: Wednesday, May 19, 2010 12:03 PM
 To: Maven Users List
 Subject: Re: move folder from res to res${BUILD_NUMBER} easy 
 Filtering problem...

 ok, so tried out my solution and the copy is working ;) but it is not

 filtering our the res folder in the war file plugin for some reason.
 How do I fix this xml so it filters out res folder...

execution
phasetest/phase
goals
goalrun/goal
/goals
configuration
tasks
echo message=Running jboss 
 ant tasks/
mkdir 
 dir=${project.build.directory}/${project.name
 }-${project.version}/res-${BUILD_NUMBER}/
copy 
 todir=${project.build.directory}/${project.name
 }-${project.version}/res-${BUILD_NUMBER}
fileset 
 dir=src/main/webapp/res
  include name=**/
/fileset
/copy
copy 
 file=src/main/descriptors/jboss/WEB-INF/components.xml

 tofile=${project.build.directory}/${project.name}-${project.version}
 /WE
 B-INF/components.xml
 /
/tasks
/configuration
/execution
/executions
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-war-plugin/artifactId
version2.0/version
configuration
  webResources
resource
  !-- this is relative to the pom.xml 
 directory
 --
  directorysrc/main/webapp/directory
  !-- the list has a default value of **
 --
  excludes
excluderes**/exclude
  /excludes
/resource
  /webResources

archive
manifestEntries

 Svn-Revision${SVN_REVISION}/Svn-Revision

 Build-Tag${BUILD_TAG}/Build-Tag

 Build-Number${BUILD_NUMBER}/Build-Number
Build-Id${BUILD_ID}/Build-Id
/manifestEntries
/archive
/configuration
/plugin

 On Wed,

Which Jira to use for items concerning the Apache Common Parent POM?

2010-05-19 Thread Marshall Schor

Hi,

I've posted earlier about a couple of possible improvements to the
Apache Common Parent POM - used by Apache projects [1].

I'd like to add some Jira issues for these, but I was unable to
determine what Jira system to use.  Does anyone know the right Jira to
use for this?

-Marshall Schor

[1]http://repo1.maven.org/maven2/org/apache/apache/7/apache-7.pom

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

Re: AW: How to create a report based on annotations

2010-05-19 Thread Wayne Fay

 to customize your Maven site. But I want to know how to write a
 sophisticated report plugin.

Pick a sophisticated report or two that you like.
If it is open source, get the source code.
If it is not open source, pick a different one.
Using the source code, build your own sophisticated report plugin.

Wayne

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

Re: should be an easy Filtering question?

My original example is based off that page below(the longer snippet of xml
below has it), and that is not working at all :(.

thanks,
Dean

On Wed, May 19, 2010 at 2:27 PM, Moll, Jeff jm...@glhec.org wrote:

 Try this page is you have not done so yet, this may be more helpful than
 the previous example I passed along assuming you are using the
 war-plug-in.
 http://maven.apache.org/plugins/maven-war-plugin/examples/adding-filteri
 ng-webresources.htmlhttp://maven.apache.org/plugins/maven-war-plugin/examples/adding-filteri%0Ang-webresources.html

 -Jeff

 -Original Message-
 From: dean.hil...@gmail.com [mailto:dean.hil...@gmail.com] On Behalf Of
 Dean Hiller
 Sent: Wednesday, May 19, 2010 3:17 PM
 To: Maven Users List
 Subject: Re: should be an easy Filtering question?

 This question should be really easyI would assume even novices would
 know the answer here??  Any takersplease  I would really like to
 get this working.

 On Wed, May 19, 2010 at 11:46 AM, Dean Hiller d...@alvazan.com wrote:

  I am missing just one more thing.  The doc here
  http://maven.apache.org/guides/getting-started/index.html#How_do_I_fil
  ter_resource_files
 
  is about slipping in property files oddly enough not about filtering
  out files(I just want to exclude one folder during the build).  I see
  the
 
  filters
 filtersome properties file for slipping in params/filter
  /filters
 
  How do I add my exclusion of my res folder?
 
  I tried copying the example you gave into the build element and adding

  excludes as well...
 
 resources
   resource
 directorysrc/main/webapp/directory
 filteringtrue/filtering
 
 excludes
exclude**res**/exclude
  /excludes
 
  /resource
  /resources
 
  Still not working :(
 
  thanks,
  Dean
 
 
  On Wed, May 19, 2010 at 11:29 AM, Moll, Jeff jm...@glhec.org wrote:
 
  Make sure you have the resource filtering turned on. By default it is

  not so you will need something like this:
 
   build
 resources
   resource
 directorysrc/main/resources/directory
 filteringtrue/filtering
   /resource
 /resources
   /build
 
 
 
  -Original Message-
  From: dean.hil...@gmail.com [mailto:dean.hil...@gmail.com] On Behalf
  Of Dean Hiller
  Sent: Wednesday, May 19, 2010 12:03 PM
  To: Maven Users List
  Subject: Re: move folder from res to res${BUILD_NUMBER} easy
  Filtering problem...
 
  ok, so tried out my solution and the copy is working ;) but it is not

  filtering our the res folder in the war file plugin for some reason.
  How do I fix this xml so it filters out res folder...
 
 execution
 phasetest/phase
 goals
 goalrun/goal
 /goals
 configuration
 tasks
 echo message=Running jboss
  ant tasks/
 mkdir
  dir=${project.build.directory}/${project.name
  }-${project.version}/res-${BUILD_NUMBER}/
 copy
  todir=${project.build.directory}/${project.name
  }-${project.version}/res-${BUILD_NUMBER}
 fileset
  dir=src/main/webapp/res
   include name=**/
 /fileset
 /copy
 copy
  file=src/main/descriptors/jboss/WEB-INF/components.xml
 
  tofile=${project.build.directory}/${project.name}-${project.version}
  /WE
  B-INF/components.xml
  /
 /tasks
 /configuration
 /execution
 /executions
 /plugin
 plugin
 groupIdorg.apache.maven.plugins/groupId
 artifactIdmaven-war-plugin/artifactId
 version2.0/version
 configuration
   webResources
 resource
   !-- this is relative to the pom.xml
  directory
  --
   directorysrc/main/webapp/directory
   !-- the list has a default value of **
  --
   excludes
 excluderes**/exclude
   /excludes
 /resource
   /webResources
 
 archive

Re: Which Jira to use for items concerning the Apache Common Parent POM?