Status of Generate a sub module from an archetype

2009-08-04 Thread Murali Pottlapelli

Hi All,
I see TBD next to Generate a sub module from an archetype at 
http://maven.apache.org/plugins/maven-archetype-plugin. Is TBD for 
implementation or documentation?


Is it possible to control the files created in a sub-module? Is it also 
possible to sync the content in the files based on meta-data (generated 
property files)? Is there any example archetype to demonstrate the 
functionality?


How to invoke archetype plug-in from a program? Is it possible to invoke 
from another plug-in? example snippet would help


I have searched in glassfish users group, but did not find any help on 
archetype


Regards
Murali

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



Re: Surefire: How to specify jar class loading order?

2009-08-04 Thread Stephen Connolly
OK, well there goes my It's the maven versions that use hashmap and not
linkedhashmap theory...

-Stephen

2009/8/4 David Hoffer dhoff...@gmail.com

 I just verified, all our builds are using 2.1.0.

 -Dave

 On Mon, Aug 3, 2009 at 7:18 PM, David Hoffer dhoff...@gmail.com wrote:

  No, I'm using 2.1x.
 
  -Dave
 
 
  On Mon, Aug 3, 2009 at 4:22 PM, Stephen Connolly 
  stephen.alan.conno...@gmail.com wrote:
 
  I am going to guess that you are using a version of maven  2.0.9
 
  if I am wrong, let us know
 
  Sent from my [rhymes with myPod] ;-)
 
 
  On 3 Aug 2009, at 23:04, David Hoffer dhoff...@gmail.com wrote:
 
   I have found a case where mvn install  deploy work fine but
 site-deploy
  does not.  The reason is that during site-deploy the surefire plugin is
  building a class loading list in the surefirebooter jar's Manifest that
  is
  different.
 
  The reason this matters in my case is that I have some class overrides
 in
  one of my child poms (multi-module project).  Its important that my
 child
  artifact with the overrides gets added to the classpath first.  I don't
  know
  what logic surefire uses to know what order to use but in the case of
  site-deploy it is putting the original before my override.
 
  I want to be able to specify the jar class loading order surefire uses
  (like
  I could do in a war for instance at runtime).  How can I do this with
  surefire?
 
  -Dave
 
 
  -
  To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
  For additional commands, e-mail: users-h...@maven.apache.org
 
 
 



How invoke itblast plugin two times for two different databases?

2009-08-04 Thread Nafter

When I make a build at the end the maven-itblast-plugin is used to kick off
Junit tests.
This is working just fine.

However I would like to run the same set of JUnit tests against an other db
vendor as well.
In fact the Junit tests should be executed on a Oracle database but also on
a SQL server database.

At the moment I'm trying to invoke the maven-itblast-plugin two times, but
this is only executed once.

I call the build by passing the following profile options:

-e clean install -Drun_tests_oracle -Drun_tests_sqlserver


Does somebody know how to really invoke the Unittests twice using the
maven-itblast-plugin?



See below how the -Drun_tests_oracle -Drun_tests_sqlserver are being
configured.
  !-- RUN ACTUAL JUNIT TESTS [ORACLE] --
profile
  idrun_tests_oracle_id/id
  activation
property
  namerun_tests_oracle/name
/property
  /activation
  build
plugins
  plugin
groupIdorg.codehaus.cargo/groupId
artifactIdcargo-maven2-plugin/artifactId
version1.0-beta-2/version

configuration
  !-- Container configuration --
  container
containerIdjboss42x/containerId
home${JBOSS__HOME}/home
  /container
  !-- Configuration to use with the container --
  configuration
typestandalone/type
home${JBOSS__HOME}/server/default/home
properties
  !--cargo.rmi.port${JBOSS_PORT__RMI}/cargo.rmi.port--
 
cargo.jvmargs${VMARGS__TEST_PROPERTY_FILE_ORACLE}/cargo.jvmargs
/properties
  /configuration
/configuration
  /plugin
  
  plugin
artifactIdmaven-surefire-plugin/artifactId
configuration
  skipfalse/skip
  argLine${VMARGS__TEST_PROPERTY_FILE_ORACLE}/argLine
  testFailureIgnorefalse/testFailureIgnore
/configuration
  /plugin

  plugin
groupIdorg.twdata.maven/groupId
artifactIdmaven-itblast-plugin/artifactId
version0.5/version
executions
  execution
phaseverify/phase
goals
  goalexecute/goal
/goals
configuration
  containersjboss42x/containers
  httpPort${JBOSS_PORT__HTTP}/httpPort
  rmiPort${JBOSS_PORT__RMI}/rmiPort
 
functionalTestPattern${JUNIT__TEST_PATTERN}/functionalTestPattern
  systemProperties/systemProperties
/configuration
  /execution
/executions
  /plugin
/plugins
  /build
/profile



!-- RUN ACTUAL JUNIT TESTS [SQL SERVER] --
profile
  idrun_tests_sqlserver_id/id
  activation
property
  namerun_tests_sqlserver/name
/property
  /activation
  build
plugins
  plugin
groupIdorg.codehaus.cargo/groupId
artifactIdcargo-maven2-plugin/artifactId
version1.0-beta-2/version

configuration
  !-- Container configuration --
  container
containerIdjboss42x/containerId
home${JBOSS__HOME}/home
  /container
  !-- Configuration to use with the container --
  configuration
typestandalone/type
home${JBOSS__HOME}/server/default/home
properties
  !--cargo.rmi.port${JBOSS_PORT__RMI}/cargo.rmi.port--
 
cargo.jvmargs${VMARGS__TEST_PROPERTY_FILE_SQLSERVER}/cargo.jvmargs
/properties
  /configuration
/configuration
  /plugin
  
  plugin
artifactIdmaven-surefire-plugin/artifactId
configuration
  skipfalse/skip
  argLine${VMARGS__TEST_PROPERTY_FILE_SQLSERVER}/argLine
  testFailureIgnorefalse/testFailureIgnore
/configuration
  /plugin

  plugin
groupIdorg.twdata.maven/groupId
artifactIdmaven-itblast-plugin/artifactId
version0.5/version
executions
  execution
phaseverify/phase
goals
  goalexecute/goal
/goals
configuration
  containersjboss42x/containers
  httpPort${JBOSS_PORT__HTTP}/httpPort
  rmiPort${JBOSS_PORT__RMI}/rmiPort
 
functionalTestPattern${JUNIT__TEST_PATTERN}/functionalTestPattern
  systemProperties/systemProperties
/configuration
  /execution
/executions
  /plugin
/plugins
  /build
/profile

-- 
View 

filePermissions ignored during site-deploy with SCP

2009-08-04 Thread JeremieB

Hi,

I'm quite new to Maven and facing an issue I could not workaround.

I'm using Maven 2.2.0, and using site-deploy to deploy my generated site to
a webserver, through scp.

Here are the settings server I use :
server
  idGGS-website/id
  usernamemylogin/username
  privateKeyD:\Documents and Settings\mylogin\.ssh\id_rsa/privateKey
  filePermissions777/filePermissions
  directoryPermissions777/directoryPermissions
/server

My distribution management section :
site
idGGS-website/id
nameSite webserver for GGS projects/name

urlscp://${site.host}/opt/apache2/htdocs/projects/${project.groupId}/url
/site

Deployment works well, except that whatever I put in filePermissions or
directoryPermissions, my files get created with permissions 644 on the
webserver.
I tried to use wagon-ssh in version 1.0-beta-6 as I saw issues close to
mine, but it did not correct the issue.

In logs following line confirm rights are set that do not match what I want
:
Executing command: chmod -Rf g+w,a+rX /opt/apache2/htdocs/projects/...

This is blocking issue for me, as it prevents anyone else from publishing
the same website again, as there is no common group assigned on the
webserver (and I can't change that).

I really don't know how to investigate ... How can I check what wagon
version is used for SCP ? I see nothing else in logs, and although I added
extension for 1.0-beta-6, still some dependencies on 1.0-beta-2 are
retrieved and I'm quite confused.

Thanks for help,
Jeremie

-- 
View this message in context: 
http://www.nabble.com/filePermissions-ignored-during-site-deploy-with-SCP-tp24804640p24804640.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



Need to compile apach eusing maven

2009-08-04 Thread Kalaip

We had an idea like to compile and build the openssl, apache using maven
pom.xml
Is it possible to compile and build the apache, openssl using pom.xml
We need to invoke the apache build procedure using pom.xml.

Please let me know if it is possible using the pom.xml. If so please provide
me some examples. 

Thanks,
Kalai:-)
-- 
View this message in context: 
http://www.nabble.com/Need-to-compile-apach-eusing-maven-tp24804947p24804947.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: filePermissions ignored during site-deploy with SCP

2009-08-04 Thread Lukas Theussl


The permission settings in server are not used anymore since maven 2.1 [1]. The 
chmod command is optional and configurable in the current site-plugin-2.1-SNAPSHOT 
[2], you can test it eg like



chmodModeg+w,a+rX/chmodMode
chmodOptions-Rf/chmodOptions

Note however that there are some pitholes [3].

HTH,
-Lukas


[1] http://jira.codehaus.org/browse/MNG-3600
[2] http://jira.codehaus.org/browse/MSITE-141
[3] http://jira.codehaus.org/browse/MSITE-330


JeremieB wrote:

Hi,

I'm quite new to Maven and facing an issue I could not workaround.

I'm using Maven 2.2.0, and using site-deploy to deploy my generated site to
a webserver, through scp.

Here are the settings server I use :
server
  idGGS-website/id
  usernamemylogin/username
  privateKeyD:\Documents and Settings\mylogin\.ssh\id_rsa/privateKey
  filePermissions777/filePermissions
  directoryPermissions777/directoryPermissions
/server

My distribution management section :
site
idGGS-website/id
nameSite webserver for GGS projects/name

urlscp://${site.host}/opt/apache2/htdocs/projects/${project.groupId}/url
/site

Deployment works well, except that whatever I put in filePermissions or
directoryPermissions, my files get created with permissions 644 on the
webserver.
I tried to use wagon-ssh in version 1.0-beta-6 as I saw issues close to
mine, but it did not correct the issue.

In logs following line confirm rights are set that do not match what I want
:
Executing command: chmod -Rf g+w,a+rX /opt/apache2/htdocs/projects/...

This is blocking issue for me, as it prevents anyone else from publishing
the same website again, as there is no common group assigned on the
webserver (and I can't change that).

I really don't know how to investigate ... How can I check what wagon
version is used for SCP ? I see nothing else in logs, and although I added
extension for 1.0-beta-6, still some dependencies on 1.0-beta-2 are
retrieved and I'm quite confused.

Thanks for help,
Jeremie



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



Re: Copy groups of dependencies with dependency plugin

2009-08-04 Thread JeremieB

Hi,

I think the following configuration should do the trick :
build
  plugins
plugin
artifactIdmaven-dependency-plugin/artifactId
version2.0/version
executions
  execution
idunpack-jetty/id
phasepackage/phase
goals
  goalunpack-dependencies/goal
/goals
configuration
  includeGroupIdsorg.mortbay.jetty/includeGroupIds
  outputDirectorytarget/lib/jetty/outputDirectory
/configuration
  /execution
  execution
idunpack-metro/id
phasepackage/phase
goals
  goalunpack-dependencies/goal
/goals
configuration
  includeGroupIdscom.sun.xml.ws/includeGroupIds
  outputDirectorytarget/lib/metro/outputDirectory
/configuration
  /execution
  execution
idunpack-others/id
phasepackage/phase
goals
  goalunpack-dependencies/goal
/goals
configuration
 
excludeGroupIdsorg.mortbay.jetty,com.sun.xml.ws/excludeGroupIds
  outputDirectorytarget/lib/outputDirectory
/configuration
  /execution  
/executions
/plugin
  /plugins
/build

I think also groupIds are exact match, I'm not sure you could use * inside
pattern.
It worked for me, but I adapted it to your sample, so you might have to
adjust some bits.

Hope this helps,
Jeremie



Shef wrote:
 
 I'm having a rough time finding the magic syntax to get 
 maven-dependency-plugin to copy dependencies to the right places. What I 
 want to do is:
 
 1. Copy dependencies with common groupIds to particular subdirectories.
 2. Copy the rest of the compile-scope dependencies to the main /lib 
 directory.
 
 Example output:
 
 /target
/lib
  /jetty
(jetty and transitives go here, groupid=org.mortbay.jetty)
  /metro
(glassfish and transitives go here, groupid=com.sun.xml.ws)
commons-collections.jar
commons-logging.jar
etc. -- rest of compile-scope dependencies here
 
 I don't want to have to specify every artifact and its version in the 
 configuration, because all that's already in the dependencies section 
 of the pom.
 
 
 -
 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://www.nabble.com/Copy-groups-of-dependencies-with-dependency-plugin-tp2476p24805528.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: [PLEASE TEST] Maven 2.2.1-RC2

2009-08-04 Thread Paul MERLIN
Seems to work nicely, done some releases with it today.

/Paul

Le mardi 04 août 2009 01:49:15, John Casey a écrit :
 Hi again,

 After Brett sorted out some issues that got lost in the source-control
 mess on my localhost, and I resolved a couple more stragglers that came
 up as a result of testing out RC1, I think we're in better shape to
 attempt a release again.

 Before we do, I'd like to get as many eyes as possible on this latest
 release candidate:

 https://repository.apache.org/content/repositories/maven-staging-008/org/ap
ache/maven/apache-maven/2.2.1-RC2

 Please file JIRA issues for anything you come across that still seems
 broken. The list of issues we've resolved so far for this release is here:

 http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName=
Htmlversion=15328

 Thanks!

 -john

 ---
 John Casey
 Developer and PMC Member, Apache Maven (http://maven.apache.org)
 Member, Apache Software Foundation

 What we have to learn to do, we learn by doing.
 -Aristotle

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


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



Re: Surefire: How to specify jar class loading order?

2009-08-04 Thread David Hoffer
Any thoughts on how I should resolve this?  Here are some options I thought
of.

1. Does the surefire plugin allow jar order to be specified via
configuration?

2. Put a copy of the overrides in each artifact under test so they always
endup in the classes folder.

3. Apply the overrides to the artifact being overridden.  I could create yet
another child module that patches the overridden artifact so I endup with a
patched version.  This might be the cleanest solution as it removes any
overrides from being in the runtime classpath, however I really don't need
this solution as in wars, etc I can control the ordering of the jar loading.

4. ??

-Dave


On Tue, Aug 4, 2009 at 12:49 AM, Stephen Connolly 
stephen.alan.conno...@gmail.com wrote:

 OK, well there goes my It's the maven versions that use hashmap and not
 linkedhashmap theory...

 -Stephen

 2009/8/4 David Hoffer dhoff...@gmail.com

  I just verified, all our builds are using 2.1.0.
 
  -Dave
 
  On Mon, Aug 3, 2009 at 7:18 PM, David Hoffer dhoff...@gmail.com wrote:
 
   No, I'm using 2.1x.
  
   -Dave
  
  
   On Mon, Aug 3, 2009 at 4:22 PM, Stephen Connolly 
   stephen.alan.conno...@gmail.com wrote:
  
   I am going to guess that you are using a version of maven  2.0.9
  
   if I am wrong, let us know
  
   Sent from my [rhymes with myPod] ;-)
  
  
   On 3 Aug 2009, at 23:04, David Hoffer dhoff...@gmail.com wrote:
  
I have found a case where mvn install  deploy work fine but
  site-deploy
   does not.  The reason is that during site-deploy the surefire plugin
 is
   building a class loading list in the surefirebooter jar's Manifest
 that
   is
   different.
  
   The reason this matters in my case is that I have some class
 overrides
  in
   one of my child poms (multi-module project).  Its important that my
  child
   artifact with the overrides gets added to the classpath first.  I
 don't
   know
   what logic surefire uses to know what order to use but in the case of
   site-deploy it is putting the original before my override.
  
   I want to be able to specify the jar class loading order surefire
 uses
   (like
   I could do in a war for instance at runtime).  How can I do this with
   surefire?
  
   -Dave
  
  
   -
   To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
   For additional commands, e-mail: users-h...@maven.apache.org
  
  
  
 



combining javadoc versus shade

2009-08-04 Thread Benson Margulies
I have a multi-module top-level project. The first set of modules
build ordinary JAR artifacts, and each has some javadoc with it.

The next module just runs maven-shade-plugin to combine then into a shaded jar.

Finally, there's a module to build a release package.

I am not seeing how to organize the aggregation of the javadoc. The
shade project is not itself an 'aggregator' project, and adding an
execution of javadoc:aggregate doesn't seem to do anything.

Do I have to unpack the javadoc artifacts of the contributors with the
dependency plugin to accomplish the task at hand?

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



maven eclipse plugin and wtp

2009-08-04 Thread massive.boisson

Hi, I have a maven project (that is web project by its nature) and I want to
run it in eclipse as WTP project.

I found command (on
http://maven.apache.org/plugins/maven-eclipse-plugin/wtp.html):
mvn -Dwtpversion=R7 eclipse:eclipse
Where wtpversion can be R7, 1.0, 1.5, 2.0 or none (default).


As current wtp version is 3.1, can I use 
mvn -Dwtpversion=3.1 eclipse:eclipse


Or is there a new or prefered way to do this?


Thanks a lot

-MB
-- 
View this message in context: 
http://www.nabble.com/maven-eclipse-plugin-and-wtp-tp24808685p24808685.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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



Re: maven eclipse plugin and wtp

2009-08-04 Thread massive.boisson

Sorry that came out wrong, I know I cannot do -Dwtpversion=3.1, but I am
wondering what are my alternatives.

It seems there should be a new new way to do this, and I cannot find it.

Or maybe 2.0 works as good as 3.1


Thanks

-MB


massive.boisson wrote:
 
 As current wtp version is 3.1, can I use 
 mvn -Dwtpversion=3.1 eclipse:eclipse
 

-- 
View this message in context: 
http://www.nabble.com/maven-eclipse-plugin-and-wtp-tp24808685p24808760.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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



Re: maven eclipse plugin and wtp

2009-08-04 Thread Wes Wannemacher
On Tue, Aug 4, 2009 at 9:27 AM,
massive.boissonmassive.bois...@gmail.com wrote:

 Hi, I have a maven project (that is web project by its nature) and I want to
 run it in eclipse as WTP project.

 I found command (on
 http://maven.apache.org/plugins/maven-eclipse-plugin/wtp.html):
 mvn -Dwtpversion=R7 eclipse:eclipse
 Where wtpversion can be R7, 1.0, 1.5, 2.0 or none (default).


 As current wtp version is 3.1, can I use
 mvn -Dwtpversion=3.1 eclipse:eclipse


 Or is there a new or prefered way to do this?



When you specify the WTP version, you are telling the plugin which
type of configuration to generate. Eclipse has the ability to import
from older versions, so even though WTP version 2.0 is from '08, it
shouldn't hurt to use 2.0, then let eclipse import it.

At the same time, when using the eclipse plugin, you should ask
yourself which you want to depend on more, eclipse or maven? Eclipse
and maven both handle many similar tasks, but if you use the eclipse
functionality, you are locked into eclipse... There are many eclipse
tools that are helpful, but for building and testing, I prefer to
leave it to maven. That being the case, what does WTP give you that is
most important? IMO, it's the ability to run your web-app right from
the IDE... You can install a tomcat runtime right in WTP and tell
eclipse to run your web-app in it. If this is the feature you are
looking for, then I would say that you could do one better and use the
maven-tomcat-plugin to get the same functionality.

Instead of using the maven-eclipse-plugin to generate eclipse
configuration files, try using the m2eclipse eclipse plugin to have
eclipse become more maven-aware. Then, you can create an eclipse run
configuration that launches 'mvn tomcat:run'. You will have the
ability to debug your web-app using the eclipse debugger. In addition,
you will also have the nifty pom editory that comes with m2eclipse.
This will leave you with a project that is more portable across IDEs,
in case someone on your team later decides to use something other than
eclipse. In addition, your build/test process can be run in a CI
environment like hudson.

-Wes

-- 
Wes Wannemacher

Head Engineer, WanTii, Inc.
Need Training? Struts, Spring, Maven, Tomcat...
Ask me for a quote!

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



Re: combining javadoc versus shade

2009-08-04 Thread Daniel Kulp

I talked to Benson on IRC   The solution (more like hack) that CXF uses 
to accomplish this is to use dependency plugin to unpack the source jars for 
everything being shaded and re-run the javadoc plugin on that unpacked source.  
 
It's a complete hack, but it at least works for what we needed it for.

Dan


On Tue August 4 2009 9:03:03 am Benson Margulies wrote:
 I have a multi-module top-level project. The first set of modules
 build ordinary JAR artifacts, and each has some javadoc with it.

 The next module just runs maven-shade-plugin to combine then into a shaded
 jar.

 Finally, there's a module to build a release package.

 I am not seeing how to organize the aggregation of the javadoc. The
 shade project is not itself an 'aggregator' project, and adding an
 execution of javadoc:aggregate doesn't seem to do anything.

 Do I have to unpack the javadoc artifacts of the contributors with the
 dependency plugin to accomplish the task at hand?

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

-- 
Daniel Kulp
dk...@apache.org
http://www.dankulp.com/blog

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



RE: maven eclipse plugin and wtp

2009-08-04 Thread Martin Gainty

m2 is the better solution if you need to debug
curious as to what term CI means?

Martin 
Ask about software clunker upgrade program
__ 
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
 
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger 
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung 
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem 
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. 
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung 
fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le 
destinataire prévu, nous te demandons avec bonté que pour satisfaire informez 
l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est 
interdite. Ce message sert à l'information seulement et n'aura pas n'importe 
quel effet légalement obligatoire. Étant donné que les email peuvent facilement 
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité 
pour le contenu fourni.




 Date: Tue, 4 Aug 2009 09:39:17 -0400
 Subject: Re: maven eclipse plugin and wtp
 From: w...@wantii.com
 To: users@maven.apache.org
 
 On Tue, Aug 4, 2009 at 9:27 AM,
 massive.boissonmassive.bois...@gmail.com wrote:
 
  Hi, I have a maven project (that is web project by its nature) and I want to
  run it in eclipse as WTP project.
 
  I found command (on
  http://maven.apache.org/plugins/maven-eclipse-plugin/wtp.html):
  mvn -Dwtpversion=R7 eclipse:eclipse
  Where wtpversion can be R7, 1.0, 1.5, 2.0 or none (default).
 
 
  As current wtp version is 3.1, can I use
  mvn -Dwtpversion=3.1 eclipse:eclipse
 
 
  Or is there a new or prefered way to do this?
 
 
 
 When you specify the WTP version, you are telling the plugin which
 type of configuration to generate. Eclipse has the ability to import
 from older versions, so even though WTP version 2.0 is from '08, it
 shouldn't hurt to use 2.0, then let eclipse import it.
 
 At the same time, when using the eclipse plugin, you should ask
 yourself which you want to depend on more, eclipse or maven? Eclipse
 and maven both handle many similar tasks, but if you use the eclipse
 functionality, you are locked into eclipse... There are many eclipse
 tools that are helpful, but for building and testing, I prefer to
 leave it to maven. That being the case, what does WTP give you that is
 most important? IMO, it's the ability to run your web-app right from
 the IDE... You can install a tomcat runtime right in WTP and tell
 eclipse to run your web-app in it. If this is the feature you are
 looking for, then I would say that you could do one better and use the
 maven-tomcat-plugin to get the same functionality.
 
 Instead of using the maven-eclipse-plugin to generate eclipse
 configuration files, try using the m2eclipse eclipse plugin to have
 eclipse become more maven-aware. Then, you can create an eclipse run
 configuration that launches 'mvn tomcat:run'. You will have the
 ability to debug your web-app using the eclipse debugger. In addition,
 you will also have the nifty pom editory that comes with m2eclipse.
 This will leave you with a project that is more portable across IDEs,
 in case someone on your team later decides to use something other than
 eclipse. In addition, your build/test process can be run in a CI
 environment like hudson.
 
 -Wes
 
 -- 
 Wes Wannemacher
 
 Head Engineer, WanTii, Inc.
 Need Training? Struts, Spring, Maven, Tomcat...
 Ask me for a quote!
 
 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org
 

_
Get free photo software from Windows Live
http://www.windowslive.com/online/photos?ocid=PID23393::T:WLMTAGL:ON:WL:en-US:SI_PH_software:082009

DefaultArtifact.getSelectedVersion throws N.P.E

2009-08-04 Thread Nord, James
WIth Maven 2.2.0 i'm getting an N.P.E from DefaultArtifact when calling
getSelectedVersion on a dependency.
 
This is in a multimodule project - and several modules build fine before
I hit the one that constantly failes.
 
[INFO] java.lang.NullPointerException
[INFO]  at
org.apache.maven.artifact.DefaultArtifact.getSelectedVersion(DefaultArti
fact.java:621)
[INFO]  at
com.nds.cab.build.enforcer.EngineeringReleaseRule.execute(EngineeringRel
easeRule.java:69)
[INFO]  at
org.apache.maven.plugins.enforcer.EnforceMojo.execute(EnforceMojo.java:1
85)
[INFO]  at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa
nager.java:483)

The code in question (below) is an enforcer rule that does the following
- which looks ok to me.
 
Looking at the DefaultArtifact code there is the following comment
513
http://maven.apache.org/ref/2.2.0/xref/org/apache/maven/artifact/Defaul
tArtifact.html#513  // I am assuming this is happening as a
result of the MNG-1577 work, but somehow the value
514
http://maven.apache.org/ref/2.2.0/xref/org/apache/maven/artifact/Defaul
tArtifact.html#514  // of versionRange just goes null or is not
set. But this is happeningin Yoko and the value is
515
http://maven.apache.org/ref/2.2.0/xref/org/apache/maven/artifact/Defaul
tArtifact.html#515  // set when attaching the JAR and not set
when attaching the test JAR.
516
http://maven.apache.org/ref/2.2.0/xref/org/apache/maven/artifact/Defaul
tArtifact.html#516  if ( versionRange == null )
517
http://maven.apache.org/ref/2.2.0/xref/org/apache/maven/artifact/Defaul
tArtifact.html#517  {
518
http://maven.apache.org/ref/2.2.0/xref/org/apache/maven/artifact/Defaul
tArtifact.html#518  versionRange =
VersionRange.createFromVersion( version );
519
http://maven.apache.org/ref/2.2.0/xref/org/apache/maven/artifact/Defaul
tArtifact.html#519  }

However - the defaultArtifactHandler itself doesn't call getVersionRange
but uses the field diretly, which to me seems a little strange.

public void execute(EnforcerRuleHelper helper) throws
EnforcerRuleException {

   // the following results in a bogus POM during some phases //
MavenProject project = (MavenProject) helper.evaluate( ${project} );
MavenSession session = (MavenSession) helper.evaluate(${session});
MavenProject project = session.getCurrentProject(); Properties props =
session.getExecutionProperties(); if
(props.containsKey(skipEngineeringReleaseRule)) { log.warn(Skipping
EngineeringReleaseRule (user requested)); } else if (
project.getArtifact().isSnapshot() ) { // snapshots can contain
engineering versions } else if
(isEngineeringVersion(project.getArtifact().getSelectedVersion())) { //
project is an engineering version so engineering versions are allowed! }
else { // we are a release version so check the dependencies for any
engineering release. log.info(Checking for engineering dependencies);
Set dependencies = project.getArtifacts(); 66: Iterator i =
dependencies.iterator(); 67: while (i.hasNext()) { 68: Artifact artifact
= (Artifact) i.next(); 69:if
(isEngineeringVersion(artifact.getSelectedVersion())) { 70: //
Engineering releases only come from NDS! 71: if
(artifact.getGroupId().startsWith(com.mycorp)) { throw new
EnforcerRuleException(ERROR_MSG); } } } } 
Am i doing somehting I'm not supposed to?  the quick and dirty is for me
to add a call to getVersionRange() before getSelectedVersion() but this
is masking the issue not nescesarily fixing it and if something deep
down is broken it doesn't leave me with a warm fuzzy feeling.
 
/James
 

**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**


Re: maven eclipse plugin and wtp

2009-08-04 Thread Wes Wannemacher
On Tue, Aug 4, 2009 at 9:56 AM, Martin Gaintymgai...@hotmail.com wrote:

 m2 is the better solution if you need to debug
 curious as to what term CI means?


CI = continuous integration... Things like Hudson, Bamboo, Continuum.

-Wes

-- 
Wes Wannemacher

Head Engineer, WanTii, Inc.
Need Training? Struts, Spring, Maven, Tomcat...
Ask me for a quote!

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



How to create patched artifact?

2009-08-04 Thread David Hoffer
What is the maven way of creating a patched jar?

I have a case where I need to apply some overrides to a binary jar which is
one of my dependencies.  I have the source code for the overrides.  So I
could create a child module with the source and the one dependency that
needs the overrides applied.  What maven plugin would I use to extract the
class files from the dependency, combine with the new generated classes from
source, and then re-jar?  The final artifact would have a new name, i.e.
_patched, so as to not get confused with the original.  How can I then stop
the transitive dependency on the original jar?  I would want the dependency
to be on the new patched version only.

What's the maven way of doing this sort of thing?

-Dave


Re: How to create patched artifact?

2009-08-04 Thread Tim O'Brien
On Tue, Aug 4, 2009 at 9:25 AM, David Hofferdhoff...@gmail.com wrote:
 What is the maven way of creating a patched jar?

 I have a case where I need to apply some overrides to a binary jar which is
 one of my dependencies.  I have the source code for the overrides.  So I
 could create a child module with the source and the one dependency that
 needs the overrides applied.  What maven plugin would I use to extract the
 class files from the dependency, combine with the new generated classes from
 source, and then re-jar?  The final artifact would have a new name, i.e.
 _patched, so as to not get confused with the original.  How can I then stop
 the transitive dependency on the original jar?  I would want the dependency
 to be on the new patched version only.


1. Create a project with a new groupId, artifactId, and version.

2.  Publish this third-party binary to a repository manager - you can
use one of the various repository managers that allow you to manually
upload an artifact.   (Me?  I'd recommend Nexus).

3. Use the dependency plugin to unpack the artifact to your project's
target/classes.   Bind the unpack goal to generate-sources or
generate-resources so that the download and unpack.

Unpack Mojo: 
http://maven.apache.org/plugins/maven-dependency-plugin/examples/unpacking-artifacts.html
Intro to Lifecycle:
http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html

4. Package, publish your new patched artifact to a repository manager
(under a new groupId, artifactId, version).

The key here is that you create a project that patches the original
artifact and then publishes it under a different GAV coordinate.   I
would not recommend patching the JAR and then writing it back to the
repository manager under the same GAV coordinate: 1. You are going to
have a GAV collision, and 2. It makes it difficult to update to a new
version of this binary dependency.

 What's the maven way of doing this sort of thing?


Good luck.

 -Dave


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



Cross-project dependencies

2009-08-04 Thread Lewis, Eric
Hi

I have a problem, which might be solved using Maven's make-like reactor mode - 
but I'm not sure if it is!

Consider the following projects/modules

Project A
+--- Module A1
+--- Module A2
Project B
+--- Module B1
+--- Module B2

Now, if A1 depends on B1, but B2 depends on A2, it's impossible to build a 
refactoring done in the two projects.
Let's say I changed something in A1 and B2, then neither Project A nor Project 
B will build, since they're caught in a kind of deadlock.
I will have to build and deploy some modules by hand until the whole build 
works (talking of snapshots here, of course).

Can the make-like reactor mode help me?

As you can tell, I'm a bit confused  ;-)
Thanks for any hints!

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



Re: filePermissions ignored during site-deploy with SCP

2009-08-04 Thread JeremieB

Hi and thanks for reply,

I'm trying to test this but fail since now.

I added repository for apache snapshots in my archiva proxy connectors list,
but now it seems nothing works anymore ...

My build downloads .pom and metadata for maven-site-plugin 2.1-SNAPSHOT, but
it's not able to download the jar in any way.
Installing manually the .jar seem to make things progress, but still my
build is not able to download any SNAPSHOT dependency of site-plugin from my
archiva server. Logs show only a bunch of Read time out.

I really do not understand a thing of what's happening :/


ltheussl wrote:
 
 
 The permission settings in server are not used anymore since maven 2.1
 [1]. The 
 chmod command is optional and configurable in the current
 site-plugin-2.1-SNAPSHOT 
 [2], you can test it eg like
 
 
 chmodModeg+w,a+rX/chmodMode
 chmodOptions-Rf/chmodOptions
 
 Note however that there are some pitholes [3].
 
 HTH,
 -Lukas
 
 
 [1] http://jira.codehaus.org/browse/MNG-3600
 [2] http://jira.codehaus.org/browse/MSITE-141
 [3] http://jira.codehaus.org/browse/MSITE-330
 

-- 
View this message in context: 
http://www.nabble.com/filePermissions-ignored-during-site-deploy-with-SCP-tp24804640p24810428.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: Need to compile apach eusing maven

2009-08-04 Thread Wayne Fay
 We had an idea like to compile and build the openssl, apache using maven
 pom.xml
 Is it possible to compile and build the apache, openssl using pom.xml
 We need to invoke the apache build procedure using pom.xml.

This is a good question for the Apache HTTP Server email list, not the
Maven list. Last time I checked, they are not using Maven for their
build process, so I doubt this is possible.

Wayne

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



Filtering assembly, but with command line value

2009-08-04 Thread David Weintraub
We have a single file called aim_version.properties. In it is a string
@VERSION@ which is replaced with a property that I get from the command
line. I am building an assembly, and I need to change the @VERSION@ string
with a value of a property that I either get from the command line, or I get
as the default property in the pom.xml.

I looked up the assembly descriptor, and it tells me how to do filtering via
an already built properties file, but I don't want to do that. Instead, I
simply want to take the value of the property and filter this one file with
that property.

How do I do that while I build the assembly? I know how to specify this one
file when building the assembly, and I see how to do the filtering if the
value I want is in a properties file, but I need to take the value off the
command line.

-- 
David Weintraub
qazw...@gmail.com


RE: maven eclipse plugin and wtp

2009-08-04 Thread massive.boisson

Thank you guys,

I do need to debug. 

It was not obvious at all to me how to import existing java web maven
project into eclipse wtp project using m2 eclipse plugin. And I tried to
figure it out.

Do you have a hint or two?

Thanks

-MB


mgainty wrote:
 
 
 m2 is the better solution if you need to debug
 curious as to what term CI means?
 
 Martin 
 Ask about software clunker upgrade program
 __ 
 Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
  
 Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene
 Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte
 Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht
 dient lediglich dem Austausch von Informationen und entfaltet keine
 rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von
 E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.
 Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le
 destinataire prévu, nous te demandons avec bonté que pour satisfaire
 informez l'expéditeur. N'importe quelle diffusion non autorisée ou la
 copie de ceci est interdite. Ce message sert à l'information seulement et
 n'aura pas n'importe quel effet légalement obligatoire. Étant donné que
 les email peuvent facilement être sujets à la manipulation, nous ne
 pouvons accepter aucune responsabilité pour le contenu fourni.
 
 
 
 
 Date: Tue, 4 Aug 2009 09:39:17 -0400
 Subject: Re: maven eclipse plugin and wtp
 From: w...@wantii.com
 To: users@maven.apache.org
 
 On Tue, Aug 4, 2009 at 9:27 AM,
 massive.boissonmassive.bois...@gmail.com wrote:
 
  Hi, I have a maven project (that is web project by its nature) and I
 want to
  run it in eclipse as WTP project.
 
  I found command (on
  http://maven.apache.org/plugins/maven-eclipse-plugin/wtp.html):
  mvn -Dwtpversion=R7 eclipse:eclipse
  Where wtpversion can be R7, 1.0, 1.5, 2.0 or none (default).
 
 
  As current wtp version is 3.1, can I use
  mvn -Dwtpversion=3.1 eclipse:eclipse
 
 
  Or is there a new or prefered way to do this?
 
 
 
 When you specify the WTP version, you are telling the plugin which
 type of configuration to generate. Eclipse has the ability to import
 from older versions, so even though WTP version 2.0 is from '08, it
 shouldn't hurt to use 2.0, then let eclipse import it.
 
 At the same time, when using the eclipse plugin, you should ask
 yourself which you want to depend on more, eclipse or maven? Eclipse
 and maven both handle many similar tasks, but if you use the eclipse
 functionality, you are locked into eclipse... There are many eclipse
 tools that are helpful, but for building and testing, I prefer to
 leave it to maven. That being the case, what does WTP give you that is
 most important? IMO, it's the ability to run your web-app right from
 the IDE... You can install a tomcat runtime right in WTP and tell
 eclipse to run your web-app in it. If this is the feature you are
 looking for, then I would say that you could do one better and use the
 maven-tomcat-plugin to get the same functionality.
 
 Instead of using the maven-eclipse-plugin to generate eclipse
 configuration files, try using the m2eclipse eclipse plugin to have
 eclipse become more maven-aware. Then, you can create an eclipse run
 configuration that launches 'mvn tomcat:run'. You will have the
 ability to debug your web-app using the eclipse debugger. In addition,
 you will also have the nifty pom editory that comes with m2eclipse.
 This will leave you with a project that is more portable across IDEs,
 in case someone on your team later decides to use something other than
 eclipse. In addition, your build/test process can be run in a CI
 environment like hudson.
 
 -Wes
 
 -- 
 Wes Wannemacher
 
 Head Engineer, WanTii, Inc.
 Need Training? Struts, Spring, Maven, Tomcat...
 Ask me for a quote!
 
 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org
 
 
 _
 Get free photo software from Windows Live
 http://www.windowslive.com/online/photos?ocid=PID23393::T:WLMTAGL:ON:WL:en-US:SI_PH_software:082009
 

-- 
View this message in context: 
http://www.nabble.com/maven-eclipse-plugin-and-wtp-tp24808685p24811939.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: Copy groups of dependencies with dependency plugin

2009-08-04 Thread Chris
Thanks. This almost works. I had to add 
includeScopecompile/includeScope to the third execution.


Now a new problem: it copies over the dependencies with a particular 
groupId, but not the transitive dependencies. I guess what I really want 
is jetty plus everything it depends on to go in a directory. Possible 
without having to list every transitive dependency explicitly?



JeremieB wrote:

Hi,

I think the following configuration should do the trick :
build
  plugins
plugin
artifactIdmaven-dependency-plugin/artifactId
version2.0/version
executions
  execution
idunpack-jetty/id
phasepackage/phase
goals
  goalunpack-dependencies/goal
/goals
configuration
  includeGroupIdsorg.mortbay.jetty/includeGroupIds
  outputDirectorytarget/lib/jetty/outputDirectory
/configuration
  /execution
  execution
idunpack-metro/id
phasepackage/phase
goals
  goalunpack-dependencies/goal
/goals
configuration
  includeGroupIdscom.sun.xml.ws/includeGroupIds
  outputDirectorytarget/lib/metro/outputDirectory
/configuration
  /execution
  execution
idunpack-others/id
phasepackage/phase
goals
  goalunpack-dependencies/goal
/goals
configuration
 
excludeGroupIdsorg.mortbay.jetty,com.sun.xml.ws/excludeGroupIds

  outputDirectorytarget/lib/outputDirectory
/configuration
  /execution  
/executions

/plugin
  /plugins
/build

I think also groupIds are exact match, I'm not sure you could use * inside
pattern.
It worked for me, but I adapted it to your sample, so you might have to
adjust some bits.

Hope this helps,
Jeremie



Shef wrote:
I'm having a rough time finding the magic syntax to get 
maven-dependency-plugin to copy dependencies to the right places. What I 
want to do is:


1. Copy dependencies with common groupIds to particular subdirectories.
2. Copy the rest of the compile-scope dependencies to the main /lib 
directory.


Example output:

/target
   /lib
 /jetty
   (jetty and transitives go here, groupid=org.mortbay.jetty)
 /metro
   (glassfish and transitives go here, groupid=com.sun.xml.ws)
   commons-collections.jar
   commons-logging.jar
   etc. -- rest of compile-scope dependencies here

I don't want to have to specify every artifact and its version in the 
configuration, because all that's already in the dependencies section 
of the pom.



-
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



How to delete a directory?

2009-08-04 Thread Chris
I'm using maven-dependency-plugin to make a custom directory of 
dependencies. The trouble is that I can't find a way to delete the 
outputDirectory before the plugin runs so I can be sure there aren't any 
old files left over in it.


I tried to use maven-clean-plugin to do it, but it insists on deleting 
the entire /target directory, which I don't want. It looks like there is 
an excludeDefaultDirectories option available on the command line, but 
putting excludeDefaultDirectoriestrue/excludeDefaultDirectories in 
the configuration section doesn't work.


Any other suggestions?


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



RE: maven eclipse plugin and wtp

2009-08-04 Thread massive.boisson

Let me answer my own question. 

After searching the m2 forum, I found: 
http://www.nabble.com/How-to-convert-or-use-a-Maven-project-as-a-dynamic-web-project--to23430177.html#a23432587

For anyone looking to do this, it's very simple, you just need to make sure
you have installed m2e WTP
Integration optional feature installed. You just import/general/maven
project

Again, thanks, and sorry for extra posting.


massive.boisson wrote:
 
 Thank you guys,
 
 I do need to debug. 
 
 It was not obvious at all to me how to import existing java web maven
 project into eclipse wtp project using m2 eclipse plugin. And I tried to
 figure it out.
 
 Do you have a hint or two?
 
 Thanks
 
 -MB
 
 
 mgainty wrote:
 
 
 m2 is the better solution if you need to debug
 curious as to what term CI means?
 
 Martin 
 Ask about software clunker upgrade program
 __ 
 Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
  
 Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene
 Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede
 unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese
 Nachricht dient lediglich dem Austausch von Informationen und entfaltet
 keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit
 von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.
 Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas
 le destinataire prévu, nous te demandons avec bonté que pour satisfaire
 informez l'expéditeur. N'importe quelle diffusion non autorisée ou la
 copie de ceci est interdite. Ce message sert à l'information seulement et
 n'aura pas n'importe quel effet légalement obligatoire. Étant donné que
 les email peuvent facilement être sujets à la manipulation, nous ne
 pouvons accepter aucune responsabilité pour le contenu fourni.
 
 
 
 
 Date: Tue, 4 Aug 2009 09:39:17 -0400
 Subject: Re: maven eclipse plugin and wtp
 From: w...@wantii.com
 To: users@maven.apache.org
 
 On Tue, Aug 4, 2009 at 9:27 AM,
 massive.boissonmassive.bois...@gmail.com wrote:
 
  Hi, I have a maven project (that is web project by its nature) and I
 want to
  run it in eclipse as WTP project.
 
  I found command (on
  http://maven.apache.org/plugins/maven-eclipse-plugin/wtp.html):
  mvn -Dwtpversion=R7 eclipse:eclipse
  Where wtpversion can be R7, 1.0, 1.5, 2.0 or none (default).
 
 
  As current wtp version is 3.1, can I use
  mvn -Dwtpversion=3.1 eclipse:eclipse
 
 
  Or is there a new or prefered way to do this?
 
 
 
 When you specify the WTP version, you are telling the plugin which
 type of configuration to generate. Eclipse has the ability to import
 from older versions, so even though WTP version 2.0 is from '08, it
 shouldn't hurt to use 2.0, then let eclipse import it.
 
 At the same time, when using the eclipse plugin, you should ask
 yourself which you want to depend on more, eclipse or maven? Eclipse
 and maven both handle many similar tasks, but if you use the eclipse
 functionality, you are locked into eclipse... There are many eclipse
 tools that are helpful, but for building and testing, I prefer to
 leave it to maven. That being the case, what does WTP give you that is
 most important? IMO, it's the ability to run your web-app right from
 the IDE... You can install a tomcat runtime right in WTP and tell
 eclipse to run your web-app in it. If this is the feature you are
 looking for, then I would say that you could do one better and use the
 maven-tomcat-plugin to get the same functionality.
 
 Instead of using the maven-eclipse-plugin to generate eclipse
 configuration files, try using the m2eclipse eclipse plugin to have
 eclipse become more maven-aware. Then, you can create an eclipse run
 configuration that launches 'mvn tomcat:run'. You will have the
 ability to debug your web-app using the eclipse debugger. In addition,
 you will also have the nifty pom editory that comes with m2eclipse.
 This will leave you with a project that is more portable across IDEs,
 in case someone on your team later decides to use something other than
 eclipse. In addition, your build/test process can be run in a CI
 environment like hudson.
 
 -Wes
 
 -- 
 Wes Wannemacher
 
 Head Engineer, WanTii, Inc.
 Need Training? Struts, Spring, Maven, Tomcat...
 Ask me for a quote!
 
 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org
 
 
 _
 Get free photo software from Windows Live
 http://www.windowslive.com/online/photos?ocid=PID23393::T:WLMTAGL:ON:WL:en-US:SI_PH_software:082009
 
 
 

-- 
View this message in context: 
http://www.nabble.com/maven-eclipse-plugin-and-wtp-tp24808685p24813252.html
Sent from the Maven - Users mailing list archive at Nabble.com.



Re: How to create patched artifact?

2009-08-04 Thread David Hoffer
Hum,

I'm getting close but not quite there yet.  Here is my configuration.

plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-dependency-plugin/artifactId
executions
execution
idunpack/id
phasegenerate-sources/phase
goals
goalunpack/goal
/goals
configuration
artifactItems
artifactItem
groupIdwt/groupId
artifactIdwt/artifactId
version4.0-SNAPSHOT/version
typejar/type
overWritetrue/overWrite

outputDirectory${project.build.directory}/classes/outputDirectory
/artifactItem
/artifactItems
overWriteReleasestrue/overWriteReleases
overWriteSnapshotstrue/overWriteSnapshots
/configuration
/execution
/executions
/plugin

For some reason after running the install goal the unpack seems to have
taken precedence over the compile!

Since the generate-sources phase is before compile shouldn't the compile
have over written the unpack?  I'm confused.

-Dave


On Tue, Aug 4, 2009 at 8:39 AM, Tim O'Brien tobr...@discursive.com wrote:

 On Tue, Aug 4, 2009 at 9:25 AM, David Hofferdhoff...@gmail.com wrote:
  What is the maven way of creating a patched jar?
 
  I have a case where I need to apply some overrides to a binary jar which
 is
  one of my dependencies.  I have the source code for the overrides.  So I
  could create a child module with the source and the one dependency that
  needs the overrides applied.  What maven plugin would I use to extract
 the
  class files from the dependency, combine with the new generated classes
 from
  source, and then re-jar?  The final artifact would have a new name, i.e.
  _patched, so as to not get confused with the original.  How can I then
 stop
  the transitive dependency on the original jar?  I would want the
 dependency
  to be on the new patched version only.
 

 1. Create a project with a new groupId, artifactId, and version.

 2.  Publish this third-party binary to a repository manager - you can
 use one of the various repository managers that allow you to manually
 upload an artifact.   (Me?  I'd recommend Nexus).

 3. Use the dependency plugin to unpack the artifact to your project's
 target/classes.   Bind the unpack goal to generate-sources or
 generate-resources so that the download and unpack.

 Unpack Mojo:
 http://maven.apache.org/plugins/maven-dependency-plugin/examples/unpacking-artifacts.html
 Intro to Lifecycle:

 http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html

 4. Package, publish your new patched artifact to a repository manager
 (under a new groupId, artifactId, version).

 The key here is that you create a project that patches the original
 artifact and then publishes it under a different GAV coordinate.   I
 would not recommend patching the JAR and then writing it back to the
 repository manager under the same GAV coordinate: 1. You are going to
 have a GAV collision, and 2. It makes it difficult to update to a new
 version of this binary dependency.

  What's the maven way of doing this sort of thing?
 

 Good luck.

  -Dave
 

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




Re: How to create patched artifact?

2009-08-04 Thread Tim O'Brien
On Tue, Aug 4, 2009 at 1:01 PM, David Hofferdhoff...@gmail.com wrote:
 Hum,

 I'm getting close but not quite there yet.  Here is my configuration.

 plugin
                groupIdorg.apache.maven.plugins/groupId
                artifactIdmaven-dependency-plugin/artifactId
                executions
                    execution
                        idunpack/id
                        phasegenerate-sources/phase
                        goals
                            goalunpack/goal
                        /goals
                        configuration
                            artifactItems
                                artifactItem
                                    groupIdwt/groupId
                                    artifactIdwt/artifactId
                                    version4.0-SNAPSHOT/version
                                    typejar/type
                                    overWritetrue/overWrite

 outputDirectory${project.build.directory}/classes/outputDirectory
                                /artifactItem
                            /artifactItems
                            overWriteReleasestrue/overWriteReleases
                            overWriteSnapshotstrue/overWriteSnapshots
                        /configuration
                    /execution
                /executions
            /plugin

 For some reason after running the install goal the unpack seems to have
 taken precedence over the compile!

install isn't a goal in this case, it is a phase.   When you run
install, you are asking Maven to walk through the entire lifecycle
(except the deploy phase).   Instead of trying to test with the
install phase, run mvn generate-sources then run mvn compile.
Also use the -X flag to get more output.

Take a look at the list of phases here:
http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html



 Since the generate-sources phase is before compile shouldn't the compile
 have over written the unpack?  I'm confused.


Do you have source in src/main/java?   What is your project's packaging?

 -Dave


 On Tue, Aug 4, 2009 at 8:39 AM, Tim O'Brien tobr...@discursive.com wrote:

 On Tue, Aug 4, 2009 at 9:25 AM, David Hofferdhoff...@gmail.com wrote:
  What is the maven way of creating a patched jar?
 
  I have a case where I need to apply some overrides to a binary jar which
 is
  one of my dependencies.  I have the source code for the overrides.  So I
  could create a child module with the source and the one dependency that
  needs the overrides applied.  What maven plugin would I use to extract
 the
  class files from the dependency, combine with the new generated classes
 from
  source, and then re-jar?  The final artifact would have a new name, i.e.
  _patched, so as to not get confused with the original.  How can I then
 stop
  the transitive dependency on the original jar?  I would want the
 dependency
  to be on the new patched version only.
 

 1. Create a project with a new groupId, artifactId, and version.

 2.  Publish this third-party binary to a repository manager - you can
 use one of the various repository managers that allow you to manually
 upload an artifact.   (Me?  I'd recommend Nexus).

 3. Use the dependency plugin to unpack the artifact to your project's
 target/classes.   Bind the unpack goal to generate-sources or
 generate-resources so that the download and unpack.

 Unpack Mojo:
 http://maven.apache.org/plugins/maven-dependency-plugin/examples/unpacking-artifacts.html
 Intro to Lifecycle:

 http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html

 4. Package, publish your new patched artifact to a repository manager
 (under a new groupId, artifactId, version).

 The key here is that you create a project that patches the original
 artifact and then publishes it under a different GAV coordinate.   I
 would not recommend patching the JAR and then writing it back to the
 repository manager under the same GAV coordinate: 1. You are going to
 have a GAV collision, and 2. It makes it difficult to update to a new
 version of this binary dependency.

  What's the maven way of doing this sort of thing?
 

 Good luck.

  -Dave
 

 -
 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 create patched artifact?

2009-08-04 Thread David Hoffer
Yeah, I meant install phase.  My pom's packaging is jar, and I have the
source in src/main/java.

It seems to find the source because for new files I do find the compiled
classes in the right places.  However what I also find is that for classes
in the dependent jar they seem to have overwrote the compiled ones.

I think what is happening is that during the compile phase it simply skips
the compile (or at least the writing of the class file to disk) if it
already exists.  How can I configure the compile to always overwrite?

-Dave

On Tue, Aug 4, 2009 at 12:10 PM, Tim O'Brien tobr...@discursive.com wrote:

 On Tue, Aug 4, 2009 at 1:01 PM, David Hofferdhoff...@gmail.com wrote:
  Hum,
 
  I'm getting close but not quite there yet.  Here is my configuration.
 
  plugin
 groupIdorg.apache.maven.plugins/groupId
 artifactIdmaven-dependency-plugin/artifactId
 executions
 execution
 idunpack/id
 phasegenerate-sources/phase
 goals
 goalunpack/goal
 /goals
 configuration
 artifactItems
 artifactItem
 groupIdwt/groupId
 artifactIdwt/artifactId
 version4.0-SNAPSHOT/version
 typejar/type
 overWritetrue/overWrite
 
  outputDirectory${project.build.directory}/classes/outputDirectory
 /artifactItem
 /artifactItems
 overWriteReleasestrue/overWriteReleases
 overWriteSnapshotstrue/overWriteSnapshots
 /configuration
 /execution
 /executions
 /plugin
 
  For some reason after running the install goal the unpack seems to have
  taken precedence over the compile!

 install isn't a goal in this case, it is a phase.   When you run
 install, you are asking Maven to walk through the entire lifecycle
 (except the deploy phase).   Instead of trying to test with the
 install phase, run mvn generate-sources then run mvn compile.
 Also use the -X flag to get more output.

 Take a look at the list of phases here:

 http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html


 
  Since the generate-sources phase is before compile shouldn't the compile
  have over written the unpack?  I'm confused.
 

 Do you have source in src/main/java?   What is your project's packaging?

  -Dave
 
 
  On Tue, Aug 4, 2009 at 8:39 AM, Tim O'Brien tobr...@discursive.com
 wrote:
 
  On Tue, Aug 4, 2009 at 9:25 AM, David Hofferdhoff...@gmail.com wrote:
   What is the maven way of creating a patched jar?
  
   I have a case where I need to apply some overrides to a binary jar
 which
  is
   one of my dependencies.  I have the source code for the overrides.  So
 I
   could create a child module with the source and the one dependency
 that
   needs the overrides applied.  What maven plugin would I use to extract
  the
   class files from the dependency, combine with the new generated
 classes
  from
   source, and then re-jar?  The final artifact would have a new name,
 i.e.
   _patched, so as to not get confused with the original.  How can I then
  stop
   the transitive dependency on the original jar?  I would want the
  dependency
   to be on the new patched version only.
  
 
  1. Create a project with a new groupId, artifactId, and version.
 
  2.  Publish this third-party binary to a repository manager - you can
  use one of the various repository managers that allow you to manually
  upload an artifact.   (Me?  I'd recommend Nexus).
 
  3. Use the dependency plugin to unpack the artifact to your project's
  target/classes.   Bind the unpack goal to generate-sources or
  generate-resources so that the download and unpack.
 
  Unpack Mojo:
 
 http://maven.apache.org/plugins/maven-dependency-plugin/examples/unpacking-artifacts.html
  Intro to Lifecycle:
 
 
 http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html
 
  4. Package, publish your new patched artifact to a repository manager
  (under a new groupId, artifactId, version).
 
  The key here is that you create a project that patches the original
  artifact and then publishes it under a different GAV coordinate.   I
  would not recommend patching the JAR and then writing it back to the
  repository manager under the same GAV coordinate: 1. You are going to
  have a GAV collision, and 2. It makes it difficult to update to a new
  version of this binary dependency.
 
   What's the maven way of doing this sort of thing?
  
 
  Good luck.
 
   -Dave
  
 
  -
  To 

Re: How to create patched artifact?

2009-08-04 Thread Anders Hammar
Tim,

 4. Package, publish your new patched artifact to a repository manager
 (under a new groupId, artifactId, version).

 The key here is that you create a project that patches the original
 artifact and then publishes it under a different GAV coordinate.   I
 would not recommend patching the JAR and then writing it back to the
 repository manager under the same GAV coordinate: 1. You are going to
 have a GAV collision, and 2. It makes it difficult to update to a new
 version of this binary dependency.

Is it really best practise to change groupId and artifactId? I would
only change the version so that Maven has a chance to detect
collisions. Similar to what Brian recommends for converting a SNAPSHOT
version to a release version in this blog entry (see rule #5):
http://www.sonatype.com/people/2009/01/best-practices-for-releasing-with-3rd-party-snapshot-dependencies/

/Anders

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



Re: How to create patched artifact?

2009-08-04 Thread Tim O'Brien
On Tue, Aug 4, 2009 at 1:27 PM, Anders Hammarand...@hammar.net wrote:
 Tim,

 4. Package, publish your new patched artifact to a repository manager
 (under a new groupId, artifactId, version).

 The key here is that you create a project that patches the original
 artifact and then publishes it under a different GAV coordinate.   I
 would not recommend patching the JAR and then writing it back to the
 repository manager under the same GAV coordinate: 1. You are going to
 have a GAV collision, and 2. It makes it difficult to update to a new
 version of this binary dependency.

 Is it really best practise to change groupId and artifactId? I would
 only change the version so that Maven has a chance to detect
 collisions. Similar to what Brian recommends for converting a SNAPSHOT
 version to a release version in this blog entry (see rule #5):
 http://www.sonatype.com/people/2009/01/best-practices-for-releasing-with-3rd-party-snapshot-dependencies/



If it is something that is public, yes, only change the version.   I
was assuming this was some gnarly internal binary that someone handed
to him because that's what has happened to me in the past.Example:
you work on a system that depends on some proprietary, source-less JAR
binary.  In that case, I'd wrap it with my own GAV and call it a day.
  But, you are right, if you are patching something like commons-lang
or plexus-utils, you would totally preserve the GA and change the V.

 /Anders

 -
 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 create patched artifact?

2009-08-04 Thread Tim O'Brien
On Tue, Aug 4, 2009 at 1:25 PM, David Hofferdhoff...@gmail.com wrote:
 Yeah, I meant install phase.  My pom's packaging is jar, and I have the
 source in src/main/java.

 It seems to find the source because for new files I do find the compiled
 classes in the right places.  However what I also find is that for classes
 in the dependent jar they seem to have overwrote the compiled ones.

 I think what is happening is that during the compile phase it simply skips
 the compile (or at least the writing of the class file to disk) if it
 already exists.  How can I configure the compile to always overwrite?

Move the copy goal that you declared to happen just after compilation.
  Look at the lifecycle list, I think you want process-classes


 -Dave

 On Tue, Aug 4, 2009 at 12:10 PM, Tim O'Brien tobr...@discursive.com wrote:

 On Tue, Aug 4, 2009 at 1:01 PM, David Hofferdhoff...@gmail.com wrote:
  Hum,
 
  I'm getting close but not quite there yet.  Here is my configuration.
 
  plugin
                 groupIdorg.apache.maven.plugins/groupId
                 artifactIdmaven-dependency-plugin/artifactId
                 executions
                     execution
                         idunpack/id
                         phasegenerate-sources/phase
                         goals
                             goalunpack/goal
                         /goals
                         configuration
                             artifactItems
                                 artifactItem
                                     groupIdwt/groupId
                                     artifactIdwt/artifactId
                                     version4.0-SNAPSHOT/version
                                     typejar/type
                                     overWritetrue/overWrite
 
  outputDirectory${project.build.directory}/classes/outputDirectory
                                 /artifactItem
                             /artifactItems
                             overWriteReleasestrue/overWriteReleases
                             overWriteSnapshotstrue/overWriteSnapshots
                         /configuration
                     /execution
                 /executions
             /plugin
 
  For some reason after running the install goal the unpack seems to have
  taken precedence over the compile!

 install isn't a goal in this case, it is a phase.   When you run
 install, you are asking Maven to walk through the entire lifecycle
 (except the deploy phase).   Instead of trying to test with the
 install phase, run mvn generate-sources then run mvn compile.
 Also use the -X flag to get more output.

 Take a look at the list of phases here:

 http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html


 
  Since the generate-sources phase is before compile shouldn't the compile
  have over written the unpack?  I'm confused.
 

 Do you have source in src/main/java?   What is your project's packaging?

  -Dave
 
 
  On Tue, Aug 4, 2009 at 8:39 AM, Tim O'Brien tobr...@discursive.com
 wrote:
 
  On Tue, Aug 4, 2009 at 9:25 AM, David Hofferdhoff...@gmail.com wrote:
   What is the maven way of creating a patched jar?
  
   I have a case where I need to apply some overrides to a binary jar
 which
  is
   one of my dependencies.  I have the source code for the overrides.  So
 I
   could create a child module with the source and the one dependency
 that
   needs the overrides applied.  What maven plugin would I use to extract
  the
   class files from the dependency, combine with the new generated
 classes
  from
   source, and then re-jar?  The final artifact would have a new name,
 i.e.
   _patched, so as to not get confused with the original.  How can I then
  stop
   the transitive dependency on the original jar?  I would want the
  dependency
   to be on the new patched version only.
  
 
  1. Create a project with a new groupId, artifactId, and version.
 
  2.  Publish this third-party binary to a repository manager - you can
  use one of the various repository managers that allow you to manually
  upload an artifact.   (Me?  I'd recommend Nexus).
 
  3. Use the dependency plugin to unpack the artifact to your project's
  target/classes.   Bind the unpack goal to generate-sources or
  generate-resources so that the download and unpack.
 
  Unpack Mojo:
 
 http://maven.apache.org/plugins/maven-dependency-plugin/examples/unpacking-artifacts.html
  Intro to Lifecycle:
 
 
 http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html
 
  4. Package, publish your new patched artifact to a repository manager
  (under a new groupId, artifactId, version).
 
  The key here is that you create a project that patches the original
  artifact and then publishes it under a different GAV coordinate.   I
  would not recommend patching the JAR and then writing it back to the
  repository manager under the same GAV coordinate: 1. You are going to
  have a GAV collision, and 2. It makes it difficult to 

Re: How to create patched artifact?

2009-08-04 Thread David Hoffer
To resolve the overwrite issue I thought I would attach the
maven-dependency-plugin to the process-classes phase so it happens after the
compile.  I then set its overWrite, overWriteReleases  overWriteSnapshots
tags to false so it would not overwrite the just compiled output.  But it
doesn't work, it still overwrites.  So I'm back at square 1.

-Dave

On Tue, Aug 4, 2009 at 12:25 PM, David Hoffer dhoff...@gmail.com wrote:

 Yeah, I meant install phase.  My pom's packaging is jar, and I have the
 source in src/main/java.

 It seems to find the source because for new files I do find the compiled
 classes in the right places.  However what I also find is that for classes
 in the dependent jar they seem to have overwrote the compiled ones.

 I think what is happening is that during the compile phase it simply skips
 the compile (or at least the writing of the class file to disk) if it
 already exists.  How can I configure the compile to always overwrite?

 -Dave


 On Tue, Aug 4, 2009 at 12:10 PM, Tim O'Brien tobr...@discursive.comwrote:

 On Tue, Aug 4, 2009 at 1:01 PM, David Hofferdhoff...@gmail.com wrote:
  Hum,
 
  I'm getting close but not quite there yet.  Here is my configuration.
 
  plugin
 groupIdorg.apache.maven.plugins/groupId
 artifactIdmaven-dependency-plugin/artifactId
 executions
 execution
 idunpack/id
 phasegenerate-sources/phase
 goals
 goalunpack/goal
 /goals
 configuration
 artifactItems
 artifactItem
 groupIdwt/groupId
 artifactIdwt/artifactId
 version4.0-SNAPSHOT/version
 typejar/type
 overWritetrue/overWrite
 
  outputDirectory${project.build.directory}/classes/outputDirectory
 /artifactItem
 /artifactItems
 overWriteReleasestrue/overWriteReleases
 overWriteSnapshotstrue/overWriteSnapshots
 /configuration
 /execution
 /executions
 /plugin
 
  For some reason after running the install goal the unpack seems to have
  taken precedence over the compile!

 install isn't a goal in this case, it is a phase.   When you run
 install, you are asking Maven to walk through the entire lifecycle
 (except the deploy phase).   Instead of trying to test with the
 install phase, run mvn generate-sources then run mvn compile.
 Also use the -X flag to get more output.

 Take a look at the list of phases here:

 http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html


 
  Since the generate-sources phase is before compile shouldn't the compile
  have over written the unpack?  I'm confused.
 

 Do you have source in src/main/java?   What is your project's packaging?

  -Dave
 
 
  On Tue, Aug 4, 2009 at 8:39 AM, Tim O'Brien tobr...@discursive.com
 wrote:
 
  On Tue, Aug 4, 2009 at 9:25 AM, David Hofferdhoff...@gmail.com
 wrote:
   What is the maven way of creating a patched jar?
  
   I have a case where I need to apply some overrides to a binary jar
 which
  is
   one of my dependencies.  I have the source code for the overrides.
  So I
   could create a child module with the source and the one dependency
 that
   needs the overrides applied.  What maven plugin would I use to
 extract
  the
   class files from the dependency, combine with the new generated
 classes
  from
   source, and then re-jar?  The final artifact would have a new name,
 i.e.
   _patched, so as to not get confused with the original.  How can I
 then
  stop
   the transitive dependency on the original jar?  I would want the
  dependency
   to be on the new patched version only.
  
 
  1. Create a project with a new groupId, artifactId, and version.
 
  2.  Publish this third-party binary to a repository manager - you can
  use one of the various repository managers that allow you to manually
  upload an artifact.   (Me?  I'd recommend Nexus).
 
  3. Use the dependency plugin to unpack the artifact to your project's
  target/classes.   Bind the unpack goal to generate-sources or
  generate-resources so that the download and unpack.
 
  Unpack Mojo:
 
 http://maven.apache.org/plugins/maven-dependency-plugin/examples/unpacking-artifacts.html
  Intro to Lifecycle:
 
 
 http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html
 
  4. Package, publish your new patched artifact to a repository manager
  (under a new groupId, artifactId, version).
 
  The key here is that you create a project that patches the original
  artifact and then publishes it under a different 

Re: Release plugin freezes in depednecy check

2009-08-04 Thread Andrew Goktepe
I did encounter the same problem.  The build does eventually proceed, but
after several minutes per module.  In our multi-module build this more than
doubles the release build time.

Setting dependencyLocationsEnabled to false speeds this up:
http://maven.apache.org/plugins/maven-project-info-reports-plugin/dependencies-mojo.html

You might also try dependencyDetailsEnabled=false.  I haven't tried that one
yet.

-Andrew

On Mon, Aug 3, 2009 at 6:26 AM, Jörg Schaible joerg.schai...@gmx.de wrote:

 Hi guys,

 did anyone of you encounter the problem, that the release-plugin freezes in
 preparation performing the dependency check for the snapshots? The project
 itself builds a plugin:

 == % 
 $ mvn org.apache.maven.plugins:maven-release-plugin:2.0-beta-9:prepare
 [INFO] Scanning for projects...
 [INFO]
 
 [INFO] Building Scalaris QMB Plugin
 [INFO]task-segment:
 [org.apache.maven.plugins:maven-release-plugin:2.0-beta-9:prepare]
 (aggregator-style)
 [INFO]
 
 [INFO] [release:prepare {execution: default-cli}]
 [INFO] Verifying that there are no local modifications...
 [INFO] Executing: /bin/sh -c cd /home/jos/work/plugins/qmb-plugin 
 svn --non-interactive status
 [INFO] Working directory: /home/jos/work/plugins/qmb-plugin
 [INFO] Checking dependencies and plugins for snapshots ...
 == % 

 .. and that's it. All I can do is killing the process (after several
 minutes). It does not seem a regression though. I tried with M221-rc1,
 M220, M210, M2010 and M209 in combination with release plugin version
 2.0-beta-9 and 2.0-beta-8. Also it does not give a lot of more log entries
 after invoking the release:prepare goal using -X as start option.

 I can create the dependency-report as well as calling dependency:tree
 though.

 What might cause this? Since I am sure that I do not trigger any snapshot,
 can I omit the dependency check somehow?

 - Jörg


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




Re: Release plugin freezes in depednecy check

2009-08-04 Thread Andrew Goktepe
Nevermind.  I just noticed this is within the release plugin itself, not the
project info reports plugin.

On Tue, Aug 4, 2009 at 11:49 AM, Andrew Goktepe andrewgokt...@gmail.comwrote:

 I did encounter the same problem.  The build does eventually proceed, but
 after several minutes per module.  In our multi-module build this more than
 doubles the release build time.

 Setting dependencyLocationsEnabled to false speeds this up:

 http://maven.apache.org/plugins/maven-project-info-reports-plugin/dependencies-mojo.html

 You might also try dependencyDetailsEnabled=false.  I haven't tried that
 one yet.

 -Andrew


 On Mon, Aug 3, 2009 at 6:26 AM, Jörg Schaible joerg.schai...@gmx.dewrote:

 Hi guys,

 did anyone of you encounter the problem, that the release-plugin freezes
 in
 preparation performing the dependency check for the snapshots? The project
 itself builds a plugin:

 == % 
 $ mvn org.apache.maven.plugins:maven-release-plugin:2.0-beta-9:prepare
 [INFO] Scanning for projects...
 [INFO]
 
 [INFO] Building Scalaris QMB Plugin
 [INFO]task-segment:
 [org.apache.maven.plugins:maven-release-plugin:2.0-beta-9:prepare]
 (aggregator-style)
 [INFO]
 
 [INFO] [release:prepare {execution: default-cli}]
 [INFO] Verifying that there are no local modifications...
 [INFO] Executing: /bin/sh -c cd /home/jos/work/plugins/qmb-plugin 
 svn --non-interactive status
 [INFO] Working directory: /home/jos/work/plugins/qmb-plugin
 [INFO] Checking dependencies and plugins for snapshots ...
 == % 

 .. and that's it. All I can do is killing the process (after several
 minutes). It does not seem a regression though. I tried with M221-rc1,
 M220, M210, M2010 and M209 in combination with release plugin version
 2.0-beta-9 and 2.0-beta-8. Also it does not give a lot of more log entries
 after invoking the release:prepare goal using -X as start option.

 I can create the dependency-report as well as calling dependency:tree
 though.

 What might cause this? Since I am sure that I do not trigger any snapshot,
 can I omit the dependency check somehow?

 - Jörg


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





Re: How to create patched artifact?

2009-08-04 Thread David Hoffer
I think our emails collided.  Just to be clear, here is my new
configuration.  It does not work because it overwrites what the compiler
did.

executions
execution
idunpack/id
phaseprocess-classes/phase
goals
goalunpack/goal
/goals
configuration
artifactItems
artifactItem
groupIdwt/groupId
artifactIdwt/artifactId
version4.0-SNAPSHOT/version
typejar/type
overWritefalse/overWrite

outputDirectory${project.build.directory}/classes/outputDirectory
/artifactItem
/artifactItems
overWriteReleasesfalse/overWriteReleases
overWriteSnapshotsfalse/overWriteSnapshots
/configuration
/execution
/executions

-Dave

On Tue, Aug 4, 2009 at 12:46 PM, Tim O'Brien tobr...@discursive.com wrote:

 On Tue, Aug 4, 2009 at 1:25 PM, David Hofferdhoff...@gmail.com wrote:
  Yeah, I meant install phase.  My pom's packaging is jar, and I have the
  source in src/main/java.
 
  It seems to find the source because for new files I do find the compiled
  classes in the right places.  However what I also find is that for
 classes
  in the dependent jar they seem to have overwrote the compiled ones.
 
  I think what is happening is that during the compile phase it simply
 skips
  the compile (or at least the writing of the class file to disk) if it
  already exists.  How can I configure the compile to always overwrite?

 Move the copy goal that you declared to happen just after compilation.
  Look at the lifecycle list, I think you want process-classes

 
  -Dave
 
  On Tue, Aug 4, 2009 at 12:10 PM, Tim O'Brien tobr...@discursive.com
 wrote:
 
  On Tue, Aug 4, 2009 at 1:01 PM, David Hofferdhoff...@gmail.com wrote:
   Hum,
  
   I'm getting close but not quite there yet.  Here is my configuration.
  
   plugin
  groupIdorg.apache.maven.plugins/groupId
  artifactIdmaven-dependency-plugin/artifactId
  executions
  execution
  idunpack/id
  phasegenerate-sources/phase
  goals
  goalunpack/goal
  /goals
  configuration
  artifactItems
  artifactItem
  groupIdwt/groupId
  artifactIdwt/artifactId
  version4.0-SNAPSHOT/version
  typejar/type
  overWritetrue/overWrite
  
   outputDirectory${project.build.directory}/classes/outputDirectory
  /artifactItem
  /artifactItems
  overWriteReleasestrue/overWriteReleases
  
  overWriteSnapshotstrue/overWriteSnapshots
  /configuration
  /execution
  /executions
  /plugin
  
   For some reason after running the install goal the unpack seems to
 have
   taken precedence over the compile!
 
  install isn't a goal in this case, it is a phase.   When you run
  install, you are asking Maven to walk through the entire lifecycle
  (except the deploy phase).   Instead of trying to test with the
  install phase, run mvn generate-sources then run mvn compile.
  Also use the -X flag to get more output.
 
  Take a look at the list of phases here:
 
 
 http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html
 
 
  
   Since the generate-sources phase is before compile shouldn't the
 compile
   have over written the unpack?  I'm confused.
  
 
  Do you have source in src/main/java?   What is your project's packaging?
 
   -Dave
  
  
   On Tue, Aug 4, 2009 at 8:39 AM, Tim O'Brien tobr...@discursive.com
  wrote:
  
   On Tue, Aug 4, 2009 at 9:25 AM, David Hofferdhoff...@gmail.com
 wrote:
What is the maven way of creating a patched jar?
   
I have a case where I need to apply some overrides to a binary jar
  which
   is
one of my dependencies.  I have the source code for the overrides.
  So
  I
could create a child module with the source and the one dependency
  that
needs the overrides applied.  What maven plugin would I use to
 extract
   the
class files from the dependency, combine with the new generated
  classes
   from
source, and then re-jar?  The final artifact would have a new name,
  i.e.

Re: How to create patched artifact?

2009-08-04 Thread jieryn
Hi David,

If you have all the source code, as you seem to suggest several times
in this convoluted post, then why don't you just deploy a new
-SNAPSHOT yourself to your local repository? You ARE using a
repository manager, right??

http://www.sonatype.com/people/2009/01/best-practices-for-releasing-with-3rd-party-snapshot-dependencies/

-jesse

On Tue, Aug 4, 2009 at 10:25 AM, David Hofferdhoff...@gmail.com wrote:
 What is the maven way of creating a patched jar?

 I have a case where I need to apply some overrides to a binary jar which is
 one of my dependencies.  I have the source code for the overrides.  So I
 could create a child module with the source and the one dependency that
 needs the overrides applied.  What maven plugin would I use to extract the
 class files from the dependency, combine with the new generated classes from
 source, and then re-jar?  The final artifact would have a new name, i.e.
 _patched, so as to not get confused with the original.  How can I then stop
 the transitive dependency on the original jar?  I would want the dependency
 to be on the new patched version only.

 What's the maven way of doing this sort of thing?

 -Dave




-- 
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 create patched artifact?

2009-08-04 Thread David Hoffer
Hum,

Adding overWriteIfNewerfalse/overWriteIfNewer does not help either.  The
behavior I am seeing is that it always overwrites.

-Dave

On Tue, Aug 4, 2009 at 12:49 PM, David Hoffer dhoff...@gmail.com wrote:

 I think our emails collided.  Just to be clear, here is my new
 configuration.  It does not work because it overwrites what the compiler
 did.

 executions
 execution
 idunpack/id
 phaseprocess-classes/phase
 goals
 goalunpack/goal
 /goals
 configuration
 artifactItems
 artifactItem
 groupIdwt/groupId
 artifactIdwt/artifactId
 version4.0-SNAPSHOT/version
 typejar/type
 overWritefalse/overWrite

 outputDirectory${project.build.directory}/classes/outputDirectory
 /artifactItem
 /artifactItems
 overWriteReleasesfalse/overWriteReleases
 overWriteSnapshotsfalse/overWriteSnapshots
 /configuration
 /execution
 /executions

 -Dave


 On Tue, Aug 4, 2009 at 12:46 PM, Tim O'Brien tobr...@discursive.comwrote:

 On Tue, Aug 4, 2009 at 1:25 PM, David Hofferdhoff...@gmail.com wrote:
  Yeah, I meant install phase.  My pom's packaging is jar, and I have the
  source in src/main/java.
 
  It seems to find the source because for new files I do find the compiled
  classes in the right places.  However what I also find is that for
 classes
  in the dependent jar they seem to have overwrote the compiled ones.
 
  I think what is happening is that during the compile phase it simply
 skips
  the compile (or at least the writing of the class file to disk) if it
  already exists.  How can I configure the compile to always overwrite?

 Move the copy goal that you declared to happen just after compilation.
  Look at the lifecycle list, I think you want process-classes

 
  -Dave
 
  On Tue, Aug 4, 2009 at 12:10 PM, Tim O'Brien tobr...@discursive.com
 wrote:
 
  On Tue, Aug 4, 2009 at 1:01 PM, David Hofferdhoff...@gmail.com
 wrote:
   Hum,
  
   I'm getting close but not quite there yet.  Here is my configuration.
  
   plugin
  groupIdorg.apache.maven.plugins/groupId
  artifactIdmaven-dependency-plugin/artifactId
  executions
  execution
  idunpack/id
  phasegenerate-sources/phase
  goals
  goalunpack/goal
  /goals
  configuration
  artifactItems
  artifactItem
  groupIdwt/groupId
  artifactIdwt/artifactId
  version4.0-SNAPSHOT/version
  typejar/type
  overWritetrue/overWrite
  
   outputDirectory${project.build.directory}/classes/outputDirectory
  /artifactItem
  /artifactItems
  
  overWriteReleasestrue/overWriteReleases
  
  overWriteSnapshotstrue/overWriteSnapshots
  /configuration
  /execution
  /executions
  /plugin
  
   For some reason after running the install goal the unpack seems to
 have
   taken precedence over the compile!
 
  install isn't a goal in this case, it is a phase.   When you run
  install, you are asking Maven to walk through the entire lifecycle
  (except the deploy phase).   Instead of trying to test with the
  install phase, run mvn generate-sources then run mvn compile.
  Also use the -X flag to get more output.
 
  Take a look at the list of phases here:
 
 
 http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html
 
 
  
   Since the generate-sources phase is before compile shouldn't the
 compile
   have over written the unpack?  I'm confused.
  
 
  Do you have source in src/main/java?   What is your project's
 packaging?
 
   -Dave
  
  
   On Tue, Aug 4, 2009 at 8:39 AM, Tim O'Brien tobr...@discursive.com
  wrote:
  
   On Tue, Aug 4, 2009 at 9:25 AM, David Hofferdhoff...@gmail.com
 wrote:
What is the maven way of creating a patched jar?
   
I have a case where I need to apply some overrides to a binary jar
  which
   is
one of my dependencies.  I have the source code for the overrides.
  So
  I
could create a child module with the source and the one dependency
  that
needs the overrides applied.  

Re: How to create patched artifact?

2009-08-04 Thread David Hoffer
Perhaps I'm not clear what you are suggesting.  I'm not trying to do a
release, I'm trying to use a snapshot (that a different division at our
company produces).  However I need to make a few overrides to this
snapshot.  yes we do have a process to move our overrides into the
snapshot...but that process takes some time.  In the meantime I have to
build with the snapshot as it exists.

So what I am trying to do is simply unpack the snapshot, compile/replace
classes with my overrides, and re-jar.  I have chosen to rename the jar so
there is no risk of confusing which jar is patched.

yes we use a repository manager, all builds get deployed to it.

-Dave

On Tue, Aug 4, 2009 at 1:01 PM, jie...@gmail.com wrote:

 Hi David,

 If you have all the source code, as you seem to suggest several times
 in this convoluted post, then why don't you just deploy a new
 -SNAPSHOT yourself to your local repository? You ARE using a
 repository manager, right??


 http://www.sonatype.com/people/2009/01/best-practices-for-releasing-with-3rd-party-snapshot-dependencies/

 -jesse

 On Tue, Aug 4, 2009 at 10:25 AM, David Hofferdhoff...@gmail.com wrote:
  What is the maven way of creating a patched jar?
 
  I have a case where I need to apply some overrides to a binary jar which
 is
  one of my dependencies.  I have the source code for the overrides.  So I
  could create a child module with the source and the one dependency that
  needs the overrides applied.  What maven plugin would I use to extract
 the
  class files from the dependency, combine with the new generated classes
 from
  source, and then re-jar?  The final artifact would have a new name, i.e.
  _patched, so as to not get confused with the original.  How can I then
 stop
  the transitive dependency on the original jar?  I would want the
 dependency
  to be on the new patched version only.
 
  What's the maven way of doing this sort of thing?
 
  -Dave
 



 --
 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 delete a directory?

2009-08-04 Thread Alexander
No maven-clean-plugin is more flexible. Read there
http://maven.apache.org/plugins/maven-clean-plugin/examples/delete_additional_files.html
 [?]

2009/8/5 Chris she...@yahoo.com

 I'm using maven-dependency-plugin to make a custom directory of
 dependencies. The trouble is that I can't find a way to delete the
 outputDirectory before the plugin runs so I can be sure there aren't any old
 files left over in it.

 I tried to use maven-clean-plugin to do it, but it insists on deleting the
 entire /target directory, which I don't want. It looks like there is an
 excludeDefaultDirectories option available on the command line, but putting
 excludeDefaultDirectoriestrue/excludeDefaultDirectories in the
 configuration section doesn't work.

 Any other suggestions?


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




-- 
Alexander


Re: How to delete a directory?

2009-08-04 Thread Chris
I can delete the directories ok. What I can't do is prevent it from 
deleting the target directory.



Alexander wrote:
No maven-clean-plugin is more flexible. Read 
there http://maven.apache.org/plugins/maven-clean-plugin/examples/delete_additional_files.html 


2009/8/5 Chris she...@yahoo.com mailto:she...@yahoo.com

I'm using maven-dependency-plugin to make a custom directory of
dependencies. The trouble is that I can't find a way to delete the
outputDirectory before the plugin runs so I can be sure there aren't
any old files left over in it.

I tried to use maven-clean-plugin to do it, but it insists on
deleting the entire /target directory, which I don't want. It looks
like there is an excludeDefaultDirectories option available on the
command line, but putting
excludeDefaultDirectoriestrue/excludeDefaultDirectories in the
configuration section doesn't work.

Any other suggestions?


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




--
Alexander




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



Re: How to create patched artifact?

2009-08-04 Thread Tim O'Brien
Use the excludes config property to exclude the specific files you
don't want to overwrite.

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

The docs on that mojo leave much to be desired.

On Tue, Aug 4, 2009 at 2:10 PM, David Hofferdhoff...@gmail.com wrote:
 Perhaps I'm not clear what you are suggesting.  I'm not trying to do a
 release, I'm trying to use a snapshot (that a different division at our
 company produces).  However I need to make a few overrides to this
 snapshot.  yes we do have a process to move our overrides into the
 snapshot...but that process takes some time.  In the meantime I have to
 build with the snapshot as it exists.

 So what I am trying to do is simply unpack the snapshot, compile/replace
 classes with my overrides, and re-jar.  I have chosen to rename the jar so
 there is no risk of confusing which jar is patched.

 yes we use a repository manager, all builds get deployed to it.

 -Dave

 On Tue, Aug 4, 2009 at 1:01 PM, jie...@gmail.com wrote:

 Hi David,

 If you have all the source code, as you seem to suggest several times
 in this convoluted post, then why don't you just deploy a new
 -SNAPSHOT yourself to your local repository? You ARE using a
 repository manager, right??


 http://www.sonatype.com/people/2009/01/best-practices-for-releasing-with-3rd-party-snapshot-dependencies/

 -jesse

 On Tue, Aug 4, 2009 at 10:25 AM, David Hofferdhoff...@gmail.com wrote:
  What is the maven way of creating a patched jar?
 
  I have a case where I need to apply some overrides to a binary jar which
 is
  one of my dependencies.  I have the source code for the overrides.  So I
  could create a child module with the source and the one dependency that
  needs the overrides applied.  What maven plugin would I use to extract
 the
  class files from the dependency, combine with the new generated classes
 from
  source, and then re-jar?  The final artifact would have a new name, i.e.
  _patched, so as to not get confused with the original.  How can I then
 stop
  the transitive dependency on the original jar?  I would want the
 dependency
  to be on the new patched version only.
 
  What's the maven way of doing this sort of thing?
 
  -Dave
 



 --
 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




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



Re: How to delete a directory?

2009-08-04 Thread Alexander
Oh, you right. But you already answered your question! [?]
Use excludeDefaultDirectories. It works fine, really. Be sure you use 2.3
version of maven-clean-plugin. (as it mentioned in documentation this option
work only since 2.3)

plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-clean-plugin/artifactId
version2.3/version
configuration
excludeDefaultDirectoriestrue/excludeDefaultDirectories
/configuration
/plugin

2009/8/5 Chris she...@yahoo.com

 I can delete the directories ok. What I can't do is prevent it from
 deleting the target directory.


 Alexander wrote:

 No maven-clean-plugin is more flexible. Read there
 http://maven.apache.org/plugins/maven-clean-plugin/examples/delete_additional_files.html
  2009/8/5 Chris she...@yahoo.com mailto:she...@yahoo.com

I'm using maven-dependency-plugin to make a custom directory of
dependencies. The trouble is that I can't find a way to delete the
outputDirectory before the plugin runs so I can be sure there aren't
any old files left over in it.

I tried to use maven-clean-plugin to do it, but it insists on
deleting the entire /target directory, which I don't want. It looks
like there is an excludeDefaultDirectories option available on the
command line, but putting
excludeDefaultDirectoriestrue/excludeDefaultDirectories in the
configuration section doesn't work.

Any other suggestions?


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




 --
 Alexander



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




-- 
Alexander


Re: Filtering assembly, but with command line value

2009-08-04 Thread David Weintraub
I just want to clarify:

If I need to change this aim_version.properties file to use ${version} or
whatever, that's fine with me. If I need to change the name or move this to
another location, that's fine too. If we have to make this an XML file
instead of a properties file, that's fine too.

We use Hudson as our build system, and we simply need the Hudson build
number in this file. We also need this file to sit outside the generated EAR
which is why we use an assembly. (We also have a bunch of other
configuration files and shell scripts that sit outside the ear too, so
having an assembly isn't a problem).

If this was a file inside a JAR or WAR, I could use resource filtering, but
this file has to be easily accessible, so our tech services people can
verify the installation.

I simply need a way to put the Hudson build number (which I can pick up from
the command line) into a file that is easily accessible to our tech services
guys.

On Tue, Aug 4, 2009 at 12:47 PM, David Weintraub qazw...@gmail.com wrote:

 We have a single file called aim_version.properties. In it is a string
 @VERSION@ which is replaced with a property that I get from the command
 line. I am building an assembly, and I need to change the @VERSION@ string
 with a value of a property that I either get from the command line, or I get
 as the default property in the pom.xml.

 I looked up the assembly descriptor, and it tells me how to do filtering
 via an already built properties file, but I don't want to do that. Instead,
 I simply want to take the value of the property and filter this one file
 with that property.

 How do I do that while I build the assembly? I know how to specify this one
 file when building the assembly, and I see how to do the filtering if the
 value I want is in a properties file, but I need to take the value off the
 command line.

 --
 David Weintraub
 qazw...@gmail.com




-- 
David Weintraub
qazw...@gmail.com


Site deploy - missing site descriptor?

2009-08-04 Thread David C. Hicks
I keep getting the error Missing site information in the distribution
management element in the project.., but I clearly have a site
descriptor in that section...

site
idags-utilities.allureglobal.com/id
nameAGS Utilities/name
url${site.deploy.base}/url
/site
/distributionManagement

${site.deploy.base} is defined in a set of properties ahead of the
distributionManagement section.
Can anyone give me any clues how to track down this problem?  The error
is simply not descriptive enough - to me.  :-)
Thanks,
Dave


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



Re: How to delete a directory?

2009-08-04 Thread Brian Fox
Why don't you just make this folder a subfolder of /target and when you want
this cleaned out, you run clean?

On Tue, Aug 4, 2009 at 3:34 PM, Alexander the.malk...@gmail.com wrote:

 Oh, you right. But you already answered your question! [?]
 Use excludeDefaultDirectories. It works fine, really. Be sure you use 2.3
 version of maven-clean-plugin. (as it mentioned in documentation this option
 work only since 2.3)

 plugin
 groupIdorg.apache.maven.plugins/groupId
 artifactIdmaven-clean-plugin/artifactId
 version2.3/version
 configuration
 excludeDefaultDirectoriestrue/excludeDefaultDirectories
 /configuration
 /plugin

 2009/8/5 Chris she...@yahoo.com

 I can delete the directories ok. What I can't do is prevent it from
 deleting the target directory.


 Alexander wrote:

 No maven-clean-plugin is more flexible. Read there
 http://maven.apache.org/plugins/maven-clean-plugin/examples/delete_additional_files.html
  2009/8/5 Chris she...@yahoo.com mailto:she...@yahoo.com

I'm using maven-dependency-plugin to make a custom directory of
dependencies. The trouble is that I can't find a way to delete the
outputDirectory before the plugin runs so I can be sure there aren't
any old files left over in it.

I tried to use maven-clean-plugin to do it, but it insists on
deleting the entire /target directory, which I don't want. It looks
like there is an excludeDefaultDirectories option available on the
command line, but putting
excludeDefaultDirectoriestrue/excludeDefaultDirectories in the
configuration section doesn't work.

Any other suggestions?


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




 --
 Alexander



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




 --
 Alexander




Re: How to create patched artifact?

2009-08-04 Thread Brian Fox
On Tue, Aug 4, 2009 at 3:30 PM, Tim O'Brientobr...@discursive.com wrote:
 Use the excludes config property to exclude the specific files you
 don't want to overwrite.

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

 The docs on that mojo leave much to be desired.


Oh come on, the dependency plugin is very well documented. It's just
got a lot of options so it's non-trivial.

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



Re: How to create patched artifact?

2009-08-04 Thread Brian Fox
Late to the thread here, but why are you unpacking this patched jar?
Why not just deploy it to your repo manager and update your poms to
depend on it?

On Tue, Aug 4, 2009 at 3:10 PM, David Hofferdhoff...@gmail.com wrote:
 Perhaps I'm not clear what you are suggesting.  I'm not trying to do a
 release, I'm trying to use a snapshot (that a different division at our
 company produces).  However I need to make a few overrides to this
 snapshot.  yes we do have a process to move our overrides into the
 snapshot...but that process takes some time.  In the meantime I have to
 build with the snapshot as it exists.

 So what I am trying to do is simply unpack the snapshot, compile/replace
 classes with my overrides, and re-jar.  I have chosen to rename the jar so
 there is no risk of confusing which jar is patched.

 yes we use a repository manager, all builds get deployed to it.

 -Dave

 On Tue, Aug 4, 2009 at 1:01 PM, jie...@gmail.com wrote:

 Hi David,

 If you have all the source code, as you seem to suggest several times
 in this convoluted post, then why don't you just deploy a new
 -SNAPSHOT yourself to your local repository? You ARE using a
 repository manager, right??


 http://www.sonatype.com/people/2009/01/best-practices-for-releasing-with-3rd-party-snapshot-dependencies/

 -jesse

 On Tue, Aug 4, 2009 at 10:25 AM, David Hofferdhoff...@gmail.com wrote:
  What is the maven way of creating a patched jar?
 
  I have a case where I need to apply some overrides to a binary jar which
 is
  one of my dependencies.  I have the source code for the overrides.  So I
  could create a child module with the source and the one dependency that
  needs the overrides applied.  What maven plugin would I use to extract
 the
  class files from the dependency, combine with the new generated classes
 from
  source, and then re-jar?  The final artifact would have a new name, i.e.
  _patched, so as to not get confused with the original.  How can I then
 stop
  the transitive dependency on the original jar?  I would want the
 dependency
  to be on the new patched version only.
 
  What's the maven way of doing this sort of thing?
 
  -Dave
 



 --
 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




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



Re: How to create patched artifact?

2009-08-04 Thread Brian Fox
FWIW, the dependency plugin is looking at a marker file stored in
/target/dependencies to determine if a jar needs to be unpacked again.
It compares the timestamp of the jar with the timestamp of the marker
to determine newness. Once it decides to unpack a jar, it unpacks
_all_ files in there, not just newer ones.

On Tue, Aug 4, 2009 at 4:22 PM, Brian Foxbri...@infinity.nu wrote:
 Late to the thread here, but why are you unpacking this patched jar?
 Why not just deploy it to your repo manager and update your poms to
 depend on it?

 On Tue, Aug 4, 2009 at 3:10 PM, David Hofferdhoff...@gmail.com wrote:
 Perhaps I'm not clear what you are suggesting.  I'm not trying to do a
 release, I'm trying to use a snapshot (that a different division at our
 company produces).  However I need to make a few overrides to this
 snapshot.  yes we do have a process to move our overrides into the
 snapshot...but that process takes some time.  In the meantime I have to
 build with the snapshot as it exists.

 So what I am trying to do is simply unpack the snapshot, compile/replace
 classes with my overrides, and re-jar.  I have chosen to rename the jar so
 there is no risk of confusing which jar is patched.

 yes we use a repository manager, all builds get deployed to it.

 -Dave

 On Tue, Aug 4, 2009 at 1:01 PM, jie...@gmail.com wrote:

 Hi David,

 If you have all the source code, as you seem to suggest several times
 in this convoluted post, then why don't you just deploy a new
 -SNAPSHOT yourself to your local repository? You ARE using a
 repository manager, right??


 http://www.sonatype.com/people/2009/01/best-practices-for-releasing-with-3rd-party-snapshot-dependencies/

 -jesse

 On Tue, Aug 4, 2009 at 10:25 AM, David Hofferdhoff...@gmail.com wrote:
  What is the maven way of creating a patched jar?
 
  I have a case where I need to apply some overrides to a binary jar which
 is
  one of my dependencies.  I have the source code for the overrides.  So I
  could create a child module with the source and the one dependency that
  needs the overrides applied.  What maven plugin would I use to extract
 the
  class files from the dependency, combine with the new generated classes
 from
  source, and then re-jar?  The final artifact would have a new name, i.e.
  _patched, so as to not get confused with the original.  How can I then
 stop
  the transitive dependency on the original jar?  I would want the
 dependency
  to be on the new patched version only.
 
  What's the maven way of doing this sort of thing?
 
  -Dave
 



 --
 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





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



Re: How to create patched artifact?

2009-08-04 Thread Tim O'Brien
I love it how you are so close to the code, you think that this is
sufficient documentation for a plugin goal configuration property on
unpack:

Property: overWriteIfNewer
Documentation: Overwrite if newer

:-)

Like I said, that leave a lot to be desired.

On Tue, Aug 4, 2009 at 3:19 PM, Brian Foxbri...@infinity.nu wrote:
 On Tue, Aug 4, 2009 at 3:30 PM, Tim O'Brientobr...@discursive.com wrote:
 Use the excludes config property to exclude the specific files you
 don't want to overwrite.

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

 The docs on that mojo leave much to be desired.


 Oh come on, the dependency plugin is very well documented. It's just
 got a lot of options so it's non-trivial.

 -
 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: Copy groups of dependencies with dependency plugin

2009-08-04 Thread JeremieB


Shef wrote:
 
 Now a new problem: it copies over the dependencies with a particular 
 groupId, but not the transitive dependencies. I guess what I really want 
 is jetty plus everything it depends on to go in a directory. Possible 
 without having to list every transitive dependency explicitly?
 

It's strange because transitive dependencies seem to be included by default
(see 
http://maven.apache.org/plugins/maven-dependency-plugin/unpack-dependencies-mojo.html
here )
You might try to add excludeTransitivefalse/excludeTransitive, maybe, or
else it's another problem... Maybe only transitive dependencies with same
groupId are included ?


-- 
View this message in context: 
http://www.nabble.com/Copy-groups-of-dependencies-with-dependency-plugin-tp2476p24815731.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: Copy groups of dependencies with dependency plugin

2009-08-04 Thread Brian Fox
The transitive or not applies to the list that it starts with. Then it
starts applying the various filters defined, but you can't currently
filter and then get the transitives.

On Tue, Aug 4, 2009 at 4:33 PM, JeremieBjeremie.bousq...@gmail.com wrote:


 Shef wrote:

 Now a new problem: it copies over the dependencies with a particular
 groupId, but not the transitive dependencies. I guess what I really want
 is jetty plus everything it depends on to go in a directory. Possible
 without having to list every transitive dependency explicitly?


 It's strange because transitive dependencies seem to be included by default
 (see
 http://maven.apache.org/plugins/maven-dependency-plugin/unpack-dependencies-mojo.html
 here )
 You might try to add excludeTransitivefalse/excludeTransitive, maybe, or
 else it's another problem... Maybe only transitive dependencies with same
 groupId are included ?


 --
 View this message in context: 
 http://www.nabble.com/Copy-groups-of-dependencies-with-dependency-plugin-tp2476p24815731.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



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



Re: How to create patched artifact?

2009-08-04 Thread Brian Fox
That stuff is generated from the javadoc annotations. Take a look at
the usage page:

http://maven.apache.org/plugins/maven-dependency-plugin/usage.html#Overwrite%20Rules

Overwrite Rules

Artifacts are copied or unpacked using the following rules:

* If the artifact doesn't exist in the destination, then copy/unpack it.

  Otherwise:
* For copy/unpack mojo only: if artifactItem / overWrite or
overWrite is true, then it will force an overwrite.
* Releases check the overWriteReleases value (default = false). If
true, then it will force an overwrite.
* Snapshots check the overWriteSnapshots value (default = false).
If true, then it will force an overwrite.
* If none of the above is set to true, then it defaults to the
overWriteIfNewer value (default = true). This value, if true, causes
the plugin to only copy if the source is newer than the destination
(or it doesn't exist in the destination). (for unpack, this checks the
existence of the marker file, created in the markersDirectory path. To
avoid unexpected behavior after mvn clean, this path should normally
be contained within the /target hierarchy.)

Examples:

* Using the default settings (overWriteReleases = false,
overWriteSnapshots = false, overWriteIfNewer = true), then a release
or snapshot artifact will only over write the destination if the
source is newer than the destination (or marker file if unpacking).
* If overWriteReleases = true, then a release artifact (ie
foo-1.0.jar) will always overwrite.
* If overWriteSnapshots = true, then a snapshot artifact (ie
foo-1.0-SNAPSHOT.jar) will always overwrite.
* If all of the values are false, then a copy/unpack will only
occur if it doesn't exist in the destination (or markersDirectory if
unpacking).


So I again assert that for a plugin the documentation is good.


On Tue, Aug 4, 2009 at 4:28 PM, Tim O'Brientobr...@discursive.com wrote:
 I love it how you are so close to the code, you think that this is
 sufficient documentation for a plugin goal configuration property on
 unpack:

 Property: overWriteIfNewer
 Documentation: Overwrite if newer

 :-)

 Like I said, that leave a lot to be desired.

 On Tue, Aug 4, 2009 at 3:19 PM, Brian Foxbri...@infinity.nu wrote:
 On Tue, Aug 4, 2009 at 3:30 PM, Tim O'Brientobr...@discursive.com wrote:
 Use the excludes config property to exclude the specific files you
 don't want to overwrite.

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

 The docs on that mojo leave much to be desired.


 Oh come on, the dependency plugin is very well documented. It's just
 got a lot of options so it's non-trivial.

 -
 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: Cross-project dependencies

2009-08-04 Thread Brian Fox
The reactor mode would only help if you had a parent above A and B
that was aggregating both projects. Then all of them would be in the
reactor together and you'd be able to influence what gets built. (by
default it would build them in the correct order based on
dependencies).

On Tue, Aug 4, 2009 at 10:46 AM, Lewis, Ericeric.le...@ipi.ch wrote:
 Hi

 I have a problem, which might be solved using Maven's make-like reactor mode 
 - but I'm not sure if it is!

 Consider the following projects/modules

 Project A
 +--- Module A1
 +--- Module A2
 Project B
 +--- Module B1
 +--- Module B2

 Now, if A1 depends on B1, but B2 depends on A2, it's impossible to build a 
 refactoring done in the two projects.
 Let's say I changed something in A1 and B2, then neither Project A nor 
 Project B will build, since they're caught in a kind of deadlock.
 I will have to build and deploy some modules by hand until the whole build 
 works (talking of snapshots here, of course).

 Can the make-like reactor mode help me?

 As you can tell, I'm a bit confused  ;-)
 Thanks for any hints!

 Best regards,
 Eric
 -
 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 create patched artifact?

2009-08-04 Thread Tim O'Brien
On Tue, Aug 4, 2009 at 3:37 PM, Brian Foxbri...@infinity.nu wrote:
 That stuff is generated from the javadoc annotations. Take a look at
 the usage page:

 http://maven.apache.org/plugins/maven-dependency-plugin/usage.html#Overwrite%20Rules

 Overwrite Rules

 Artifacts are copied or unpacked using the following rules:

    * If the artifact doesn't exist in the destination, then copy/unpack it.

      Otherwise:
    * For copy/unpack mojo only: if artifactItem / overWrite or
 overWrite is true, then it will force an overwrite.
    * Releases check the overWriteReleases value (default = false). If
 true, then it will force an overwrite.
    * Snapshots check the overWriteSnapshots value (default = false).
 If true, then it will force an overwrite.
    * If none of the above is set to true, then it defaults to the
 overWriteIfNewer value (default = true). This value, if true, causes
 the plugin to only copy if the source is newer than the destination
 (or it doesn't exist in the destination). (for unpack, this checks the
 existence of the marker file, created in the markersDirectory path. To
 avoid unexpected behavior after mvn clean, this path should normally
 be contained within the /target hierarchy.)

 Examples:

    * Using the default settings (overWriteReleases = false,
 overWriteSnapshots = false, overWriteIfNewer = true), then a release
 or snapshot artifact will only over write the destination if the
 source is newer than the destination (or marker file if unpacking).
    * If overWriteReleases = true, then a release artifact (ie
 foo-1.0.jar) will always overwrite.
    * If overWriteSnapshots = true, then a snapshot artifact (ie
 foo-1.0-SNAPSHOT.jar) will always overwrite.
    * If all of the values are false, then a copy/unpack will only
 occur if it doesn't exist in the destination (or markersDirectory if
 unpacking).


 So I again assert that for a plugin the documentation is good.


Bleh, I still think it's awful, it reads like it was written by a cyborg.  :-)

If I'm going to unpack something, I'm going to expect that
overwrite would allow me to control whether or not the process of
unpacking was going to be destructive to existing files or not.
That's the conundrum here, I see not other way than excludes to do
this overlay without replacing files that already exist.

The alternative would be to set staleMillis on the compiler plugin to
a value that would always force a compile, but StaleSourceScanner
doesn't support anything like staleMillis = -1.


 On Tue, Aug 4, 2009 at 4:28 PM, Tim O'Brientobr...@discursive.com wrote:
 I love it how you are so close to the code, you think that this is
 sufficient documentation for a plugin goal configuration property on
 unpack:

 Property: overWriteIfNewer
 Documentation: Overwrite if newer

 :-)

 Like I said, that leave a lot to be desired.

 On Tue, Aug 4, 2009 at 3:19 PM, Brian Foxbri...@infinity.nu wrote:
 On Tue, Aug 4, 2009 at 3:30 PM, Tim O'Brientobr...@discursive.com wrote:
 Use the excludes config property to exclude the specific files you
 don't want to overwrite.

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

 The docs on that mojo leave much to be desired.


 Oh come on, the dependency plugin is very well documented. It's just
 got a lot of options so it's non-trivial.

 -
 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



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



Re: Corporate Parent POM

2009-08-04 Thread Brian Fox
Right, if you have that many projects you want a repository manager to
host and share your internal artifacts (as well as proxy external
ones). See here for more info:
http://maven.apache.org/repository-management.html

On Fri, Jul 31, 2009 at 1:56 PM, Kalle
Korhonenkalle.o.korho...@gmail.com wrote:
 And the last missing piece is that you need to make the released
 parent pom available to the other builds. The best way is to use a
 proxy repo that proxies everything (including the company parent),
 then instruct Maven to use that proxy as a mirror for all repos (you
 can distribute/make available a sample settings.xml file for your
 users).

 Kalle


 On Thu, Jul 30, 2009 at 3:27 PM, Edelson,
 Justinjustin.edel...@mtvstaff.com wrote:
 You just refer to the parent as the parent. Maven does not require that
 the parent be in the same SVN repository as the child. If the parent
 isn't (which I would think is typically the case for corporate POMs),
 then it just has to be in a Maven repository somewhere.

 For example, the POM in this project:
 http://kenai.com/projects/boxspring/sources/main/show/trunk references
 the corporate POM I linked to below (well, the last release of it).

 Justin

 -Original Message-
 From: Logachandru X Rajamanickam
 [mailto:logachandru.x.rajamanic...@jpmchase.com]
 Sent: Thursday, July 30, 2009 6:09 PM
 To: Edelson, Justin
 Cc: Maven Users List
 Subject: RE: Corporate Parent POM
 Importance: High

 Hi Justin,

 Thanks for your input and it is very helpful in understanding how this
 can be worked out. Have another question - I am having 100 applications
 in 100 different SVN repositories and in this case how can I refer this
 Corporate POM in the parent POM of the individual applications which are
 residing in 100 different repositories. Can you please throw me some
 ideas on this aspect.



 Thanks  Regards,
 Logu Rajamanickam

 -Original Message-
 From: Edelson, Justin [mailto:justin.edel...@mtvstaff.com]
 Sent: Thursday, July 30, 2009 3:31 PM
 To: Maven Users List
 Subject: RE: Corporate Parent POM

 I think the best way to do this is through properties where you set a
 default in the corporate POM and allow children to override it. If it
 helps you, the open-source version of our corporate poms are on kenai:
 http://kenai.com/projects/mtvn-master-pom/sources/source/show/trunk.
 These are not identical to our internal corporate poms, but they're
 reasonably close.

 Justin

 -Original Message-
 From: Logachandru X Rajamanickam
 [mailto:logachandru.x.rajamanic...@jpmchase.com]
 Sent: Thursday, July 30, 2009 4:05 PM
 To: Maven Users List
 Subject: Corporate Parent POM
 Importance: High

 Hello Experts,

 We have nearly 100 applications and I would like to have a central
 corporate POM which is a parent to the child POMs in all applications.
 How should I design a POM at the top level to govern and delegate the
 functionalities to the child POMs in all the applications? Trying to
 find some examples on the web, but could not find any as such. Can  you
 please point some references to my requirement.


 Thanks  Regards,
 Logu Rajamanickam



 This communication is for informational purposes only. It is not
 intended as an offer or solicitation for the purchase or sale of any
 financial instrument or as an official confirmation of any transaction.
 All market prices, data and other information are not warranted as to
 completeness or accuracy and are subject to change without notice. Any
 comments or statements made herein do not necessarily reflect those of
 JPMorgan Chase  Co., its subsidiaries and affiliates.

 This transmission may contain information that is privileged,
 confidential, legally privileged, and/or exempt from disclosure under
 applicable law. If you are not the intended recipient, you are hereby
 notified that any disclosure, copying, distribution, or use of the
 information contained herein (including any reliance
 thereon) is STRICTLY PROHIBITED. Although this transmission and any
 attachments are believed to be free of any virus or other defect that
 might affect any computer system into which it is received and opened,
 it is the responsibility of the recipient to ensure that it is virus
 free and no responsibility is accepted by JPMorgan Chase  Co., its
 subsidiaries and affiliates, as applicable, for any loss or damage
 arising in any way from its use. If you received this transmission in
 error, please immediately contact the sender and destroy the material in
 its entirety, whether in electronic or hard copy format. Thank you.

 Please refer to http://www.jpmorgan.com/pages/disclosures for
 disclosures relating to European legal entities.

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

 This communication is for informational purposes only. It is not
 intended as an offer or solicitation 

Re: How to create patched artifact?

2009-08-04 Thread Brian Fox

 Bleh, I still think it's awful, it reads like it was written by a cyborg.  :-)

 If I'm going to unpack something, I'm going to expect that
 overwrite would allow me to control whether or not the process of
 unpacking was going to be destructive to existing files or not.
 That's the conundrum here, I see not other way than excludes to do
 this overlay without replacing files that already exist.


Possibly, but this use case simply wasn't included originally but if
someone writes a patch, i will apply it right away. In fact when I
originally wrote unpack it was to get war overlay support and in this
case i definately wanted to overwrite everything from the war that was
contained in what I unpacked. The war plugin was looking at each file
and it actually broke my use case. To each their own ;-)


 The alternative would be to set staleMillis on the compiler plugin to
 a value that would always force a compile, but StaleSourceScanner
 doesn't support anything like staleMillis = -1.


 On Tue, Aug 4, 2009 at 4:28 PM, Tim O'Brientobr...@discursive.com wrote:
 I love it how you are so close to the code, you think that this is
 sufficient documentation for a plugin goal configuration property on
 unpack:

 Property: overWriteIfNewer
 Documentation: Overwrite if newer

 :-)

 Like I said, that leave a lot to be desired.

 On Tue, Aug 4, 2009 at 3:19 PM, Brian Foxbri...@infinity.nu wrote:
 On Tue, Aug 4, 2009 at 3:30 PM, Tim O'Brientobr...@discursive.com wrote:
 Use the excludes config property to exclude the specific files you
 don't want to overwrite.

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

 The docs on that mojo leave much to be desired.


 Oh come on, the dependency plugin is very well documented. It's just
 got a lot of options so it's non-trivial.

 -
 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



 -
 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: Release plugin freezes in depednecy check

2009-08-04 Thread Brian Fox
run with -X and see what it's doing

On Tue, Aug 4, 2009 at 2:49 PM, Andrew Goktepeandrewgokt...@gmail.com wrote:
 Nevermind.  I just noticed this is within the release plugin itself, not the
 project info reports plugin.

 On Tue, Aug 4, 2009 at 11:49 AM, Andrew Goktepe 
 andrewgokt...@gmail.comwrote:

 I did encounter the same problem.  The build does eventually proceed, but
 after several minutes per module.  In our multi-module build this more than
 doubles the release build time.

 Setting dependencyLocationsEnabled to false speeds this up:

 http://maven.apache.org/plugins/maven-project-info-reports-plugin/dependencies-mojo.html

 You might also try dependencyDetailsEnabled=false.  I haven't tried that
 one yet.

 -Andrew


 On Mon, Aug 3, 2009 at 6:26 AM, Jörg Schaible joerg.schai...@gmx.dewrote:

 Hi guys,

 did anyone of you encounter the problem, that the release-plugin freezes
 in
 preparation performing the dependency check for the snapshots? The project
 itself builds a plugin:

 == % 
 $ mvn org.apache.maven.plugins:maven-release-plugin:2.0-beta-9:prepare
 [INFO] Scanning for projects...
 [INFO]
 
 [INFO] Building Scalaris QMB Plugin
 [INFO]    task-segment:
 [org.apache.maven.plugins:maven-release-plugin:2.0-beta-9:prepare]
 (aggregator-style)
 [INFO]
 
 [INFO] [release:prepare {execution: default-cli}]
 [INFO] Verifying that there are no local modifications...
 [INFO] Executing: /bin/sh -c cd /home/jos/work/plugins/qmb-plugin 
 svn --non-interactive status
 [INFO] Working directory: /home/jos/work/plugins/qmb-plugin
 [INFO] Checking dependencies and plugins for snapshots ...
 == % 

 .. and that's it. All I can do is killing the process (after several
 minutes). It does not seem a regression though. I tried with M221-rc1,
 M220, M210, M2010 and M209 in combination with release plugin version
 2.0-beta-9 and 2.0-beta-8. Also it does not give a lot of more log entries
 after invoking the release:prepare goal using -X as start option.

 I can create the dependency-report as well as calling dependency:tree
 though.

 What might cause this? Since I am sure that I do not trigger any snapshot,
 can I omit the dependency check somehow?

 - Jörg


 -
 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: Site deploy - missing site descriptor?

2009-08-04 Thread David C. Hicks
Oops!  Nevermind.  Chalk this one up to blondness.  :-)

David C. Hicks wrote:
 I keep getting the error Missing site information in the distribution
 management element in the project.., but I clearly have a site
 descriptor in that section...

 site
 idags-utilities.allureglobal.com/id
 nameAGS Utilities/name
 url${site.deploy.base}/url
 /site
 /distributionManagement

 ${site.deploy.base} is defined in a set of properties ahead of the
 distributionManagement section.
 Can anyone give me any clues how to track down this problem?  The error
 is simply not descriptive enough - to me.  :-)
 Thanks,
 Dave

   

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



Re: How to create patched artifact?

2009-08-04 Thread David Hoffer
I'm not unpacking a patched jar, rather I'm unpacking the original
jar...trying to create a patched jar if I could only get the unpack to work
correctly. :)

-Dave

On Tue, Aug 4, 2009 at 2:22 PM, Brian Fox bri...@infinity.nu wrote:

 Late to the thread here, but why are you unpacking this patched jar?
 Why not just deploy it to your repo manager and update your poms to
 depend on it?

 On Tue, Aug 4, 2009 at 3:10 PM, David Hofferdhoff...@gmail.com wrote:
  Perhaps I'm not clear what you are suggesting.  I'm not trying to do a
  release, I'm trying to use a snapshot (that a different division at our
  company produces).  However I need to make a few overrides to this
  snapshot.  yes we do have a process to move our overrides into the
  snapshot...but that process takes some time.  In the meantime I have to
  build with the snapshot as it exists.
 
  So what I am trying to do is simply unpack the snapshot, compile/replace
  classes with my overrides, and re-jar.  I have chosen to rename the jar
 so
  there is no risk of confusing which jar is patched.
 
  yes we use a repository manager, all builds get deployed to it.
 
  -Dave
 
  On Tue, Aug 4, 2009 at 1:01 PM, jie...@gmail.com wrote:
 
  Hi David,
 
  If you have all the source code, as you seem to suggest several times
  in this convoluted post, then why don't you just deploy a new
  -SNAPSHOT yourself to your local repository? You ARE using a
  repository manager, right??
 
 
 
 http://www.sonatype.com/people/2009/01/best-practices-for-releasing-with-3rd-party-snapshot-dependencies/
 
  -jesse
 
  On Tue, Aug 4, 2009 at 10:25 AM, David Hofferdhoff...@gmail.com
 wrote:
   What is the maven way of creating a patched jar?
  
   I have a case where I need to apply some overrides to a binary jar
 which
  is
   one of my dependencies.  I have the source code for the overrides.  So
 I
   could create a child module with the source and the one dependency
 that
   needs the overrides applied.  What maven plugin would I use to extract
  the
   class files from the dependency, combine with the new generated
 classes
  from
   source, and then re-jar?  The final artifact would have a new name,
 i.e.
   _patched, so as to not get confused with the original.  How can I then
  stop
   the transitive dependency on the original jar?  I would want the
  dependency
   to be on the new patched version only.
  
   What's the maven way of doing this sort of thing?
  
   -Dave
  
 
 
 
  --
  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
 
 
 

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




Re: Release plugin freezes in depednecy check

2009-08-04 Thread Jörg Schaible
Andrew Goktepe wrote:

 I did encounter the same problem.

I doubt, unless you're as stupid as me ... ;-)

MRELEASE-469

- Jörg


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



Re: Release plugin freezes in depednecy check

2009-08-04 Thread Fabrice Daugan
For each dependencies, URL are checked to retrieve data.
To disable use this tip :
reporting
plugins
plugin
groupIdorg.apache.maven.plugins/groupId

artifactIdmaven-project-info-reports-plugin/artifactId
configuration

dependencyLocationsEnabledfalse/dependencyLocationsEnabled
offlinetrue/offline
/configuration
/plugin
/plugins
/reporting

Also, some data would not present in the dependencies report.

Fabrice

On Tue, Aug 4, 2009 at 8:49 PM, Andrew Goktepeandrewgokt...@gmail.com wrote:
 I did encounter the same problem.  The build does eventually proceed, but
 after several minutes per module.  In our multi-module build this more than
 doubles the release build time.

 Setting dependencyLocationsEnabled to false speeds this up:
 http://maven.apache.org/plugins/maven-project-info-reports-plugin/dependencies-mojo.html

 You might also try dependencyDetailsEnabled=false.  I haven't tried that one
 yet.

 -Andrew

 On Mon, Aug 3, 2009 at 6:26 AM, Jörg Schaible joerg.schai...@gmx.de wrote:

 Hi guys,

 did anyone of you encounter the problem, that the release-plugin freezes in
 preparation performing the dependency check for the snapshots? The project
 itself builds a plugin:

 == % 
 $ mvn org.apache.maven.plugins:maven-release-plugin:2.0-beta-9:prepare
 [INFO] Scanning for projects...
 [INFO]
 
 [INFO] Building Scalaris QMB Plugin
 [INFO]    task-segment:
 [org.apache.maven.plugins:maven-release-plugin:2.0-beta-9:prepare]
 (aggregator-style)
 [INFO]
 
 [INFO] [release:prepare {execution: default-cli}]
 [INFO] Verifying that there are no local modifications...
 [INFO] Executing: /bin/sh -c cd /home/jos/work/plugins/qmb-plugin 
 svn --non-interactive status
 [INFO] Working directory: /home/jos/work/plugins/qmb-plugin
 [INFO] Checking dependencies and plugins for snapshots ...
 == % 

 .. and that's it. All I can do is killing the process (after several
 minutes). It does not seem a regression though. I tried with M221-rc1,
 M220, M210, M2010 and M209 in combination with release plugin version
 2.0-beta-9 and 2.0-beta-8. Also it does not give a lot of more log entries
 after invoking the release:prepare goal using -X as start option.

 I can create the dependency-report as well as calling dependency:tree
 though.

 What might cause this? Since I am sure that I do not trigger any snapshot,
 can I omit the dependency check somehow?

 - Jörg


 -
 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



Exploding a ZIP in a resource directory

2009-08-04 Thread David Weintraub
We have a series of HTML based help files that sit inside our
src/main/resource/help directory. Right now, we store these files as html
files, and everything is fine.

The problem is that the people who build these files create the files in
Microsoft Word, then use a PC program called Robohelp to generate them.

Every time they generate the files, we get a completely different version of
all HTML and GIFS no matter how small the change. We use Subversion, and
each time we generate new help files, the people who maintain them basically
delete the entire Subversion help tree, then re-add in the new set of files.
This causes problems with our developers who now end up downloading and
updating hundreds of files whenever the help changes.

I would like to simply store these help files as a single zipfile in our
source archive, and then unzip these files when I do a build. Is this
possible in Maven?

-- 
David Weintraub
qazw...@gmail.com


Re: Exploding a ZIP in a resource directory

2009-08-04 Thread Alexander
You could declare these documentaion as dependecy. Then use dependency
plugin for unpacking this module. [?]
See http://maven.apache.org/plugins/maven-dependency-plugin/unpack-mojo.html

2009/8/5 David Weintraub qazw...@gmail.com

 We have a series of HTML based help files that sit inside our
 src/main/resource/help directory. Right now, we store these files as html
 files, and everything is fine.

 The problem is that the people who build these files create the files in
 Microsoft Word, then use a PC program called Robohelp to generate them.

 Every time they generate the files, we get a completely different version
 of
 all HTML and GIFS no matter how small the change. We use Subversion, and
 each time we generate new help files, the people who maintain them
 basically
 delete the entire Subversion help tree, then re-add in the new set of
 files.
 This causes problems with our developers who now end up downloading and
 updating hundreds of files whenever the help changes.

 I would like to simply store these help files as a single zipfile in our
 source archive, and then unzip these files when I do a build. Is this
 possible in Maven?

 --
 David Weintraub
 qazw...@gmail.com




-- 
Alexander


Re: Exploding a ZIP in a resource directory

2009-08-04 Thread Brian Fox
http://www.sonatype.com/people/2008/04/how-to-share-resources-across-projects-in-maven/

On Tue, Aug 4, 2009 at 6:51 PM, David Weintraubqazw...@gmail.com wrote:
 We have a series of HTML based help files that sit inside our
 src/main/resource/help directory. Right now, we store these files as html
 files, and everything is fine.

 The problem is that the people who build these files create the files in
 Microsoft Word, then use a PC program called Robohelp to generate them.

 Every time they generate the files, we get a completely different version of
 all HTML and GIFS no matter how small the change. We use Subversion, and
 each time we generate new help files, the people who maintain them basically
 delete the entire Subversion help tree, then re-add in the new set of files.
 This causes problems with our developers who now end up downloading and
 updating hundreds of files whenever the help changes.

 I would like to simply store these help files as a single zipfile in our
 source archive, and then unzip these files when I do a build. Is this
 possible in Maven?

 --
 David Weintraub
 qazw...@gmail.com


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



Re: [PLEASE TEST] Maven 2.2.1-RC2

2009-08-04 Thread Brett Randall
On Tue, Aug 4, 2009 at 9:49 AM, John Casey jdca...@commonjava.org wrote:

 Hi again,

 After Brett sorted out some issues that got lost in the source-control mess
 on my localhost, and I resolved a couple more stragglers that came up as a
 result of testing out RC1, I think we're in better shape to attempt a
 release again.

 Before we do, I'd like to get as many eyes as possible on this latest
 release candidate:


 https://repository.apache.org/content/repositories/maven-staging-008/org/apache/maven/apache-maven/2.2.1-RC2

 Please file JIRA issues for anything you come across that still seems
 broken. The list of issues we've resolved so far for this release is here:


 http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName=Htmlversion=15328

 Thanks!

 -john

 ---
 John Casey
 Developer and PMC Member, Apache Maven (http://maven.apache.org)
 Member, Apache Software Foundation

 What we have to learn to do, we learn by doing.
   -Aristotle

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


Hi John,

in the post 2.2.1-RC2 [maven-release-plugin] prepare for next development
iteration, @800602, it looks like the maven-release-plugin has not bumped

properties
mavenVersion2.2.1-RC2/mavenVersion

... to RC3-SNAPSHOT.  Is this a deploy-regression, or am I missing
something?  This leaves me unable to build 2.2.1-RC3-SNAPSHOT from a clean
repo using Maven 2.2.0, due to missing reactor deps on 2.2.1-RC2

https://svn.apache.org/viewvc/maven/maven-2/branches/maven-2.2.x/pom.xml?r1=800600r2=800602diff_format=h
https://svn.apache.org/viewvc/maven/maven-2/branches/maven-2.2.x/pom.xml?revision=800602content-type=text%2Fplain

Cheers
Brett


Re: [PLEASE TEST] Maven 2.2.1-RC2

2009-08-04 Thread Brian Fox
That's an ld bug in the release plugin. It bumps the property to
the being released version but doesn't bump it to the next dev
version.

On Tue, Aug 4, 2009 at 8:41 PM, Brett Randalljavabr...@gmail.com wrote:
 On Tue, Aug 4, 2009 at 9:49 AM, John Casey jdca...@commonjava.org wrote:

 Hi again,

 After Brett sorted out some issues that got lost in the source-control mess
 on my localhost, and I resolved a couple more stragglers that came up as a
 result of testing out RC1, I think we're in better shape to attempt a
 release again.

 Before we do, I'd like to get as many eyes as possible on this latest
 release candidate:


 https://repository.apache.org/content/repositories/maven-staging-008/org/apache/maven/apache-maven/2.2.1-RC2

 Please file JIRA issues for anything you come across that still seems
 broken. The list of issues we've resolved so far for this release is here:


 http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName=Htmlversion=15328

 Thanks!

 -john

 ---
 John Casey
 Developer and PMC Member, Apache Maven (http://maven.apache.org)
 Member, Apache Software Foundation

 What we have to learn to do, we learn by doing.
       -Aristotle

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


 Hi John,

 in the post 2.2.1-RC2 [maven-release-plugin] prepare for next development
 iteration, @800602, it looks like the maven-release-plugin has not bumped

 properties
    mavenVersion2.2.1-RC2/mavenVersion

 ... to RC3-SNAPSHOT.  Is this a deploy-regression, or am I missing
 something?  This leaves me unable to build 2.2.1-RC3-SNAPSHOT from a clean
 repo using Maven 2.2.0, due to missing reactor deps on 2.2.1-RC2

 https://svn.apache.org/viewvc/maven/maven-2/branches/maven-2.2.x/pom.xml?r1=800600r2=800602diff_format=h
 https://svn.apache.org/viewvc/maven/maven-2/branches/maven-2.2.x/pom.xml?revision=800602content-type=text%2Fplain

 Cheers
 Brett


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



Re: [PLEASE TEST] Maven 2.2.1-RC2

2009-08-04 Thread Brett Randall
On Wed, Aug 5, 2009 at 12:21 PM, Brian Fox bri...@infinity.nu wrote:

 That's an ld bug in the release plugin. It bumps the property to
 the being released version but doesn't bump it to the next dev
 version.

 On Tue, Aug 4, 2009 at 8:41 PM, Brett Randalljavabr...@gmail.com wrote:
  On Tue, Aug 4, 2009 at 9:49 AM, John Casey jdca...@commonjava.org
 wrote:
 
  Hi again,
 
  After Brett sorted out some issues that got lost in the source-control
 mess
  on my localhost, and I resolved a couple more stragglers that came up as
 a
  result of testing out RC1, I think we're in better shape to attempt a
  release again.
 
  Before we do, I'd like to get as many eyes as possible on this latest
  release candidate:
 
 
 
 https://repository.apache.org/content/repositories/maven-staging-008/org/apache/maven/apache-maven/2.2.1-RC2
 
  Please file JIRA issues for anything you come across that still seems
  broken. The list of issues we've resolved so far for this release is
 here:
 
 
 
 http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName=Htmlversion=15328
 
  Thanks!
 
  -john
 
  ---
  John Casey
  Developer and PMC Member, Apache Maven (http://maven.apache.org)
  Member, Apache Software Foundation
 
  What we have to learn to do, we learn by doing.
-Aristotle
 
  -
  To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
  For additional commands, e-mail: users-h...@maven.apache.org
 
 
  Hi John,
 
  in the post 2.2.1-RC2 [maven-release-plugin] prepare for next development
  iteration, @800602, it looks like the maven-release-plugin has not bumped
 
  properties
 mavenVersion2.2.1-RC2/mavenVersion
 
  ... to RC3-SNAPSHOT.  Is this a deploy-regression, or am I missing
  something?  This leaves me unable to build 2.2.1-RC3-SNAPSHOT from a
 clean
  repo using Maven 2.2.0, due to missing reactor deps on 2.2.1-RC2
 
 
 https://svn.apache.org/viewvc/maven/maven-2/branches/maven-2.2.x/pom.xml?r1=800600r2=800602diff_format=h
 
 https://svn.apache.org/viewvc/maven/maven-2/branches/maven-2.2.x/pom.xml?revision=800602content-type=text%2Fplain
 
  Cheers
  Brett
 

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


Thanks Brian - I'll bug the current state of the 2.2.x branch then, and see
if I can find the release plugin bug you refer to and whether it has
regressed or is still open.

Cheers
BRett