Re: Delivery Status Notification (Failure)

2011-04-08 Thread jy hu
Hi
I don't found out the seetings.xml in  - Your settings.xml file
~/.m2/settings.xml
Here is my detail info,does anyone check it for my problem? thanks!

C:\Users\hujunyingset
ALLUSERSPROFILE=C:\ProgramData
APPDATA=C:\Users\hujunying\AppData\Roaming
ClassPath=C:\STAF\samples\demo\STAFDemo.jar;C:\STAF\bin\JSTAF.jar;C:\Program
Fil
es\Java\jdk1.6.0_02\bin;C:\Program Files\Java\jdk1.6.0_02\lib;C:\Program
Files\J
ava\jdk1.6.0_02\lib\dt.jar;C:\Program
Files\Java\jdk1.6.0_02\jre6\lib\rt.jar;C:\
Program Files\Java\jdk1.6.0_02\lib\tools.jar
CommonProgramFiles=C:\Program Files\Common Files
COMPUTERNAME=HUJY-L
ComSpec=C:\Windows\system32\cmd.exe
configsetroot=C:\Windows\ConfigSetRoot
FP_NO_HOST_CHECK=NO
HOMEDRIVE=C:
HOMEPATH=\Users\hujunying
JAVA_HOME=C:\Program Files\Java\jdk1.6.0_02
LOCALAPPDATA=C:\Users\hujunying\AppData\Local
LOGONSERVER=\\SITHLORD
*m2=Q:\my work\apache-maven-3.0.3\bin
m2_HOME=Q:\my work\apache-maven-3.0.3
*
MAN_CHM_INDEX=C:/PROGRA~1/MKS/Toolkit/etc/chm/tkutil.idx;C:/PROGRA~1/MKS/Toolkit
/etc/chm/tkapi.idx;C:/PROGRA~1/MKS/Toolkit/etc/chm/tcltk.idx;C:/PROGRA~1/MKS/Too
lkit/etc/chm/tkcurses.idx;C:/Program
Files/MKS/IntegrityClient/etc/siman.idx;C:/
Program Files/MKS/IntegrityClient/etc/imman.idx;C:/Program
Files/MKS/IntegrityCl
ient/etc/sdman.idx;C:/Program Files/MKS/IntegrityClient/etc/isman.idx
MAN_HTM_PATHS=C:/PROGRA~1/MKS/Toolkit/etc/htm/perl;C:/PROGRA~1/MKS/Toolkit/etc/h
tm/perl/pod;C:/PROGRA~1/MKS/Toolkit/etc/htm/perl/ext;C:/PROGRA~1/MKS/Toolkit/etc
/htm/perl/lib
MAN_TXT_INDEX=C:/PROGRA~1/MKS/Toolkit/etc/tkutil.idx;C:/PROGRA~1/MKS/Toolkit/etc
/tkapi.idx;C:/PROGRA~1/MKS/Toolkit/etc/tcltk.idx;C:/PROGRA~1/MKS/Toolkit/etc/tkc
urses.idx;C:/Program Files/MKS/IntegrityClient/etc/siman.idx;C:/Program
Files/MK
S/IntegrityClient/etc/imman.idx;C:/Program
Files/MKS/IntegrityClient/etc/sdman.i
dx;C:/Program Files/MKS/IntegrityClient/etc/isman.idx
NUMBER_OF_PROCESSORS=4
OS=Windows_NT
Path=C:\Program
Files\MKS\IntegrityClient\bin;C:\STAF\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program
Files\ThinkPad\Bluetooth Software\;C:\Program F
iles\Intel\WiFi\bin\;C:\Program Files\Common
Files\Intel\WirelessCommon\;C:\Prog
ram Files\Common Files\Lenovo;C:\Program Files\Common Files\Ulead
Systems\MPEG;C
:\Program Files\Java\jdk1.6.0_02\bin;C:\PROGRA~1\MKS\Toolkit\mksnt;*Q:\my
work\ap
ache-maven-3.0.3\bin
*
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC;.sh;.ksh;.csh;.sed
;.awk;.pl
PROCESSOR_ARCHITECTURE=x86
PROCESSOR_IDENTIFIER=x86 Family 6 Model 37 Stepping 2, GenuineIntel
PROCESSOR_LEVEL=6
PROCESSOR_REVISION=2502
ProgramData=C:\ProgramData
ProgramFiles=C:\Program Files
PROMPT=$P$G
PSModulePath=C:\Windows\system32\WindowsPowerShell\v1.0\Modules\
PUBLIC=C:\Users\Public
ROOTDIR=C:/PROGRA~1/MKS/Toolkit
RR=C:\Program Files\Lenovo\Rescue and Recovery
SESSIONNAME=Console
STAFCONVDIR=C:\STAF\codepage
SWSHARE=C:\SWSHARE
SystemDrive=C:
SystemRoot=C:\Windows
TEMP=C:\Users\HUJUNY~1\AppData\Local\Temp
TMP=C:\Users\HUJUNY~1\AppData\Local\Temp
TVT=C:\Program Files\Lenovo
TVTCOMMON=C:\Program Files\Common Files\Lenovo
TVTPYDIR=C:\Program Files\Common Files\Lenovo\Python24
USERDNSDOMAIN=ISS.GG.SG
USERDOMAIN=ISS
USERNAME=hujunying
USERPROFILE=C:\Users\hujunying
windir=C:\Windows



On Tue, Apr 5, 2011 at 8:38 PM, Wayne Fay wayne...@gmail.com wrote:

  - Your settings.xml file ~/.m2/settings.xml
  - Maven's global settings.xml under maven's install dir {$M2_HOME}/conf
  - Other files under Maven installation dir
  - M2Eclipse configuration (Preferences-Maven)

 Or the MAVEN_OPTS environment variable is incorrect. Go to MS DOS
 (Command Prompt) and type set then look for the line MAVEN_OPTS=...

 Wayne

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




-- 
**
*Warm wishes,*
*Jaina(hu jun ying)*


Re: Compile failure, package not found

2011-04-08 Thread Erwin Mueller
On Wednesday 06 April 2011 19:37:13 Justin Edelson wrote:
 On Wed, Apr 6, 2011 at 3:25 AM, Erwin Mueller erwin.muel...@deventm.org 
wrote:
 Yes, so true. I realized that but I already send the email. I
  think I was just too tired, I hacked the project together in one day.
  
 But I was confused, because maven could not find the package
  com.google.common.base from commons-lang either.
 
 Perhaps this is because commons-lang contains classes in the
 org.apache.commons.lang package structure, not anything starting with
 com.google.common.
 

Thank you, yes you are correct. The class Preconditions is in the 
Guava Jar and I got it from a different Jar which was in the scope test. I 
could used it in Eclipse without problems, but than maven complained because 
it was in the test scope. The MEclipse plugin should show warnings or errors 
if someone try to use a class from the test scope in src/main/java.

-- 
Erwin Mueller, erwin.muel...@deventm.org
http://www.global-scaling-institute.de/
http://www.deventm.org

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



Re: Checkout and Build all dependencies

2011-04-08 Thread AnasMughal
Yes, that is very similar to our requirement: We need to lock down the build
environment to be able to reproduce the build at anytime in the future.

Here are the high level objectives:

Checkout all projects from SVN
Build projects using Maven and install them to the local Maven repository.
We would need to start with the parent projects.


Totally agree: we will not check in everything in SVN.





On Thu, Apr 7, 2011 at 8:34 AM, Manfred Moser [via Maven] 
ml-node+4288827-1669842602-196...@n5.nabble.com wrote:

   We have a compliance/audit requirement that we need to be able to
 exactly
  reproduce builds. (Current requirement does not allow the build machine
  access to our internal nexus repository.)

 I have had to deal with this sort of requirement in the past in ISO, FDA
 and code repository context. In my opinion you need to be able to build
 without anything else apart from the supplied codebase/artifacts. In the
 Maven world the best way to achieve this is to package up all the source
 code and your repository server setup (or at least the repository used by
 your build with all artifacts as well as Maven in the exact version you
 use.

 You will have to lock down all plugin and dependency versions and be sure
 to have them in the repo and then you will be able to do a complete
 offline build with the repo.

 If you dont do that you will have some major nightmares in terms of
 reproducibility of the build and the used artifacts. Do NOT follow down
 the path of just trying to check everything into svn. If you do that you
 properly you will end up with the repository server in svn. Might as well
 allow the repo server to be an artifact...



 -
 To unsubscribe, e-mail: [hidden 
 email]http://user/SendEmail.jtp?type=nodenode=4288827i=0by-user=t
 For additional commands, e-mail: [hidden 
 email]http://user/SendEmail.jtp?type=nodenode=4288827i=1by-user=t



 --
  If you reply to this email, your message will be added to the discussion
 below:

 http://maven.40175.n5.nabble.com/Checkout-and-Build-all-dependencies-tp4287477p4288827.html
  To unsubscribe from Checkout and Build all dependencies, click 
 herehttp://maven.40175.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_codenode=4287477code=YW5hc211Z2hhbEBnbWFpbC5jb218NDI4NzQ3N3wtMzc0Njc1OTEy.





-- 
Anas Mughal


--
View this message in context: 
http://maven.40175.n5.nabble.com/Checkout-and-Build-all-dependencies-tp4287477p4289419.html
Sent from the Maven - Users mailing list archive at Nabble.com.

maven-dependency-plugin uses target dir instead of artifacts from repository

2011-04-08 Thread Lucas Persson


  
  
Hi
  
  
  I have some issues with the maven-dependency-plugin
  vers 2.2 under Maven3.
  
  In one project I uses the plugin to unpack a sources artifact
  like this:
   plugin
  
  groupIdorg.apache.maven.plugins/groupId
  
  artifactIdmaven-dependency-plugin/artifactId
   executions
   execution
   idunpack-artifact-sources/id
   phasegenerate-resources/phase
   goals
   goalunpack/goal
   /goals
   configuration
   artifactItems
   artifactItem
  
  groupIdoracle.ucs.callcontrol/groupId
  
  artifactIdcallcontrolapi/artifactId
  
  version${project.version}/version
   classifiersources/classifier
   overWritetrue/overWrite
   /artifactItem
   /artifactItems
  
outputDirectory${project.build.directory}/unpack-sources/outputDirectory
   /configuration
   /execution
   /executions
   /plugin
  
  
  This works very well when doing e.g. 'mvn install'
  But when runnning e.g. mvn pmd:pmd on the parent project
  (which also builds the artifact that this project tries to
  unpack)
  then the maven-dependency-plugin
  uses that project's target dir instead taking the sources jar
  form the repository.


[ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.2:unpack (unpack-artifact-sources) on project javadoc: Error unpacking file: /ade/aime_sdp_924164/target/oracle.ucs.callcontrol/callcontrolapi/target/classes to: /ade/aime_sdp_924164/target/oracle.sdp.tools/javadoc/target/unpack-sources


  This is very strange.
  
  Anyone with similar experience?
  
  Thanks
  Lucas



-- 
  
  Lucas Persson | Principal Member of Technical Staff
Phone: +4684773644 | | | Mobile:
+46730946656

Oracle Communications Platform
ORACLE Sweden | Folkungagatan 122 | 116 30 Stockholm
  
  Oracle Svenska AB, Kronborgsgrnd 17, S-164 28 KISTA,
reg.no. 556254-6746
  
  
  Oracle is committed to developing practices and
products that help protect the environment
  
  

  



Re: maven-dependency-plugin uses target dir instead of artifacts from repository

2011-04-08 Thread Anders Hammar
I believe I've run into a similar issue at some time.
However, there are a few things you should understand:
1. An reactor build is executed and for that to work, Maven *should* get
artifacts from the reactor and not the repo
2. executing mvn pmd:pmd will not install any artifacts to the local
repository - the build lifecycle is *not* executed

I think I basically gave up on this as I kind of think it's a hack reusing
the sources from a different project. And it wasn't really my
problem/project, so I told them to refactor instead. :-)
I think that the jira ticket I filed for this is MDEP-291.

/Anders

On Fri, Apr 8, 2011 at 09:28, Lucas Persson lucas.pers...@oracle.comwrote:

  Hi


 I have some issues with the maven-dependency-plugin vers 2.2 under Maven3.

 In one project I uses the plugin to unpack a sources artifact like this:
   plugin
 groupIdorg.apache.maven.plugins/groupId
 artifactIdmaven-dependency-plugin/artifactId
 executions
   execution
 idunpack-artifact-sources/id
 phasegenerate-resources/phase
 goals
   goalunpack/goal
 /goals
 configuration
   artifactItems
 artifactItem
   groupIdoracle.ucs.callcontrol/groupId
   artifactIdcallcontrolapi/artifactId
   version${project.version}/version
   classifiersources/classifier
   overWritetrue/overWrite
 /artifactItem
   /artifactItems

 outputDirectory${project.build.directory}/unpack-sources/outputDirectory
 /configuration
   /execution
 /executions
   /plugin


 This works very well when doing e.g. 'mvn install'
 But when runnning e.g. mvn pmd:pmd on the parent project (which also builds
 the artifact that this project tries to unpack)
 then the maven-dependency-plugin uses that project's target dir instead
 taking the sources jar form the repository.

  [ERROR] Failed to execute goal 
 org.apache.maven.plugins:maven-dependency-plugin:2.2:unpack 
 (unpack-artifact-sources) on project javadoc: Error unpacking file: 
 /ade/aime_sdp_924164/target/oracle.ucs.callcontrol/callcontrolapi/target/classes
  to: 
 /ade/aime_sdp_924164/target/oracle.sdp.tools/javadoc/target/unpack-sources


 This is very strange.

 Anyone with similar experience?

 Thanks
 Lucas


  --
 [image: Oracle] http://www.oracle.com
 Lucas Persson | Principal Member of Technical Staff
 Phone: +4684773644 | | | Mobile: +46730946656
 Oracle Communications Platform
 ORACLE Sweden | Folkungagatan 122 | 116 30 Stockholm

 Oracle Svenska AB, Kronborgsgränd 17, S-164 28 KISTA, reg.no. 556254-6746
 [image: Green Oracle] http://www.oracle.com/commitment Oracle is
 committed to developing practices and products that help protect the
 environment



Re: maven-dependency-plugin uses target dir instead of artifacts from repository

2011-04-08 Thread Lucas Persson


  
  
Thanks Anders
  
  I note I get the same issue for mvn site when the reports shall be
  generated.
  I can understand that during a reactor build artifacts shall be
  fetched from the build but it does not make scenes that the plugin
  tries to use target/classes when I specified a source classifier.
  
  Well I think I perhaps missuse maven here so I need to come up
  with a better solution.
  
  Cheers
  Lucas

On 04/08/2011 09:56 AM, Anders Hammar wrote:
I believe I've run into a similar issue at some time.
  However, there are a few things you should understand:
  1. An reactor build is executed and for that to work, Maven
  *should* get artifacts from the reactor and not the repo
  2. executing "mvn pmd:pmd" will not install any artifacts to the
  local repository - the build lifecycle is *not* executed
  
  I think I basically gave up on this as I kind of think it's a hack
  reusing the sources from a different project. And it wasn't really
  my problem/project, so I told them to refactor instead. :-)
  I think that the jira ticket I filed for this is MDEP-291.
  
  /Anders
  
  On Fri, Apr 8, 2011 at 09:28, Lucas
Persson lucas.pers...@oracle.com
wrote:

   Hi
  
  
  I have some issues with the maven-dependency-plugin

  vers 2.2 under Maven3.
  
  In one project I uses the plugin to unpack a sources
  artifact like this:
   plugin
  
  groupIdorg.apache.maven.plugins/groupId
  
  artifactIdmaven-dependency-plugin/artifactId
   executions
   execution
  
  idunpack-artifact-sources/id
  
  phasegenerate-resources/phase
   goals
   goalunpack/goal
   /goals
   configuration
   artifactItems
   artifactItem
  
  groupIdoracle.ucs.callcontrol/groupId
  
  artifactIdcallcontrolapi/artifactId
  
  version${project.version}/version
  
  classifiersources/classifier
  
  overWritetrue/overWrite
   /artifactItem
   /artifactItems
  
outputDirectory${project.build.directory}/unpack-sources/outputDirectory
   /configuration
   /execution
   /executions
   /plugin
  
  
  This works very well when doing e.g. 'mvn install'
  But when runnning e.g. mvn pmd:pmd on the parent
  project (which also builds the artifact that this
  project tries to unpack)
  then the maven-dependency-plugin

  uses that project's target dir instead taking the
  sources jar form the repository.


[ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.2:unpack (unpack-artifact-sources) on project javadoc: Error unpacking file: /ade/aime_sdp_924164/target/oracle.ucs.callcontrol/callcontrolapi/target/classes to: /ade/aime_sdp_924164/target/oracle.sdp.tools/javadoc/target/unpack-sources


  This is very strange.
  
  Anyone with similar experience?
  
  Thanks
  Lucas



-- 
  
  Lucas Persson | Principal Member of
Technical Staff
Phone: +4684773644 | | | Mobile: +46730946656 
Oracle Communications
Platform
ORACLE Sweden | Folkungagatan 122 | 116 30 Stockholm
  
  Oracle Svenska AB, Kronborgsgrnd
17, S-164 28 KISTA, reg.no.
556254-6746 
   Oracle is committed to developing
practices and products that help protect the environment

  

  
  


-- 
  
  Lucas Persson | Principal Member of Technical Staff
Phone: +4684773644 | | | Mobile:
+46730946656

Oracle Communications Platform
ORACLE Sweden | Folkungagatan 122 | 116 30 Stockholm
  
  Oracle Svenska AB, Kronborgsgrnd 17, S-164 28 KISTA,
reg.no. 556254-6746
  
  
  Oracle is committed to developing practices and
products that help protect the environment
  
  

  



Re: ws.zones.apache.org down

2011-04-08 Thread Ben Short
Hi Benson,

The following shows the relevant part of the dependency tree. Maven fails
while trying to get opensaml:opensaml and bouncycastle:bcprov-jdk13 and
tries to get them from ws.zones.apache.org.

[INFO] +- org.springframework.ws:spring-ws-security:jar:1.5.4:compile
[INFO] |  +- org.springframework:spring-tx:jar:2.5.5:compile
[INFO] |  +- com.sun.xml.wss:xws-security:jar:2.0-FCS:compile
[INFO] |  |  \- javax.xml.crypto:xmldsig:jar:1.0:compile
[INFO] |  | \- com.sun.org.apache.xml.security:xmlsec:jar:2.0:runtime
[INFO] |  +- org.apache.santuario:xmlsec:jar:1.4.0:compile
[INFO] |  \- org.apache.ws.security:wss4j:jar:1.5.4:compile
[INFO] | +- opensaml:opensaml:jar:1.1:compile
[INFO] | +- xalan:xalan:jar:2.7.0:compile
[INFO] | +- xerces:xercesImpl:jar:2.8.1:compile
[INFO] | \- bouncycastle:bcprov-jdk13:jar:132:compile


I've added the two deps to our instance of Nexus and we are able to build
again now.

Ben


On 7 April 2011 17:37, Benson Margulies bimargul...@gmail.com wrote:

 I'm part of ws.apache.org and I've never ever heard of this. What were
 you getting from there?

 On Thu, Apr 7, 2011 at 6:14 AM, Ben Short b...@benshort.co.uk wrote:
  Hi,
 
  Over the last couple of days my builds have been failing because the
  repository hosted at ws.zones.apache.org is down.
 
  Does anyone know whats going on with this server?
 
  Regards
 
  Ben
 

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




Re: ws.zones.apache.org down

2011-04-08 Thread Benson Margulies
They're not in maven central? How interesting.

On Fri, Apr 8, 2011 at 6:11 AM, Ben Short b...@benshort.co.uk wrote:
 Hi Benson,

 The following shows the relevant part of the dependency tree. Maven fails
 while trying to get opensaml:opensaml and bouncycastle:bcprov-jdk13 and
 tries to get them from ws.zones.apache.org.

 [INFO] +- org.springframework.ws:spring-ws-security:jar:1.5.4:compile
 [INFO] |  +- org.springframework:spring-tx:jar:2.5.5:compile
 [INFO] |  +- com.sun.xml.wss:xws-security:jar:2.0-FCS:compile
 [INFO] |  |  \- javax.xml.crypto:xmldsig:jar:1.0:compile
 [INFO] |  |     \- com.sun.org.apache.xml.security:xmlsec:jar:2.0:runtime
 [INFO] |  +- org.apache.santuario:xmlsec:jar:1.4.0:compile
 [INFO] |  \- org.apache.ws.security:wss4j:jar:1.5.4:compile
 [INFO] |     +- opensaml:opensaml:jar:1.1:compile
 [INFO] |     +- xalan:xalan:jar:2.7.0:compile
 [INFO] |     +- xerces:xercesImpl:jar:2.8.1:compile
 [INFO] |     \- bouncycastle:bcprov-jdk13:jar:132:compile


 I've added the two deps to our instance of Nexus and we are able to build
 again now.

 Ben


 On 7 April 2011 17:37, Benson Margulies bimargul...@gmail.com wrote:

 I'm part of ws.apache.org and I've never ever heard of this. What were
 you getting from there?

 On Thu, Apr 7, 2011 at 6:14 AM, Ben Short b...@benshort.co.uk wrote:
  Hi,
 
  Over the last couple of days my builds have been failing because the
  repository hosted at ws.zones.apache.org is down.
 
  Does anyone know whats going on with this server?
 
  Regards
 
  Ben
 

 -
 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: ws.zones.apache.org down

2011-04-08 Thread Colm O hEigeartaigh
WSS4J 1.5.4 used the wrong groupId for Opensaml (opensaml instead of
org.opensaml). It was fixed in WSS4J 1.5.5. The JDK1.3 BouncyCastle
dependency is not in Maven Central, but it was removed as part of
WSS4J 1.5.5.

Colm.

On Fri, Apr 8, 2011 at 11:43 AM, Benson Margulies bimargul...@gmail.com wrote:
 They're not in maven central? How interesting.

 On Fri, Apr 8, 2011 at 6:11 AM, Ben Short b...@benshort.co.uk wrote:
 Hi Benson,

 The following shows the relevant part of the dependency tree. Maven fails
 while trying to get opensaml:opensaml and bouncycastle:bcprov-jdk13 and
 tries to get them from ws.zones.apache.org.

 [INFO] +- org.springframework.ws:spring-ws-security:jar:1.5.4:compile
 [INFO] |  +- org.springframework:spring-tx:jar:2.5.5:compile
 [INFO] |  +- com.sun.xml.wss:xws-security:jar:2.0-FCS:compile
 [INFO] |  |  \- javax.xml.crypto:xmldsig:jar:1.0:compile
 [INFO] |  |     \- com.sun.org.apache.xml.security:xmlsec:jar:2.0:runtime
 [INFO] |  +- org.apache.santuario:xmlsec:jar:1.4.0:compile
 [INFO] |  \- org.apache.ws.security:wss4j:jar:1.5.4:compile
 [INFO] |     +- opensaml:opensaml:jar:1.1:compile
 [INFO] |     +- xalan:xalan:jar:2.7.0:compile
 [INFO] |     +- xerces:xercesImpl:jar:2.8.1:compile
 [INFO] |     \- bouncycastle:bcprov-jdk13:jar:132:compile


 I've added the two deps to our instance of Nexus and we are able to build
 again now.

 Ben


 On 7 April 2011 17:37, Benson Margulies bimargul...@gmail.com wrote:

 I'm part of ws.apache.org and I've never ever heard of this. What were
 you getting from there?

 On Thu, Apr 7, 2011 at 6:14 AM, Ben Short b...@benshort.co.uk wrote:
  Hi,
 
  Over the last couple of days my builds have been failing because the
  repository hosted at ws.zones.apache.org is down.
 
  Does anyone know whats going on with this server?
 
  Regards
 
  Ben
 

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




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



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



How to generate javadocs for only some projects in a multiproject?

2011-04-08 Thread Lucas Persson


  
  
Hi
  
  I want to generate and release the javadoc (e.g. the javadoc.jar
  should be a release artefacts just like any other JAR)
  But only some projects contains public java code that javadoc
  should be generated for.
  And if I have for instance 4 projects for which I want to generate
  javadoc I only want one javadoc.jar in the end with the complete
  source tree.
  
  I really thought that I found the solution to this in 
http://stackoverflow.com/questions/4947215/maven-3-generate-javadoc-for-defined-artifacts
  but the bug reported in http://jira.codehaus.org/browse/MDEP-291
  seem to hinder it.
  
  I really do not want to have some relative path from the 'javadoc
  project' to the projects where the source are in.
  
  
  I have also played around with different combination on
  skip
  like this in the multiproject
   build
   plugins
   plugin
   groupIdorg.apache.maven.plugins/groupId
   artifactIdmaven-javadoc-plugin/artifactId
   inheritedfalse/inherited
   configuration
   skipfalse/skip
   /configuration
   /plugin 
   /plugins
   pluginManagement
   plugins
   plugin
   groupIdorg.apache.maven.plugins/groupId
   artifactIdmaven-javadoc-plugin/artifactId
   configuration
   skiptrue/skip
   /configuration
   /plugin 
   /plugins
  
  And in those subproject that I really want javadoc for added:
   plugin
   groupIdorg.apache.maven.plugins/groupId
   artifactIdmaven-javadoc-plugin/artifactId
   configuration
   skipfalse/skip
   /configuration
   /plugin 
  
  
  
  So I then tried to use includePackageNames but that does
  not exists.
  Only excludePackageNames but then I need to exclude like
  hundred of package names, sigh.
  
  /Lucas
  
  
  

-- 
  
  Lucas Persson | Principal Member of Technical Staff
Phone: +4684773644 | | | Mobile:
+46730946656

Oracle Communications Platform
ORACLE Sweden | Folkungagatan 122 | 116 30 Stockholm
  
  Oracle Svenska AB, Kronborgsgrnd 17, S-164 28 KISTA,
reg.no. 556254-6746
  
  
  Oracle is committed to developing practices and
products that help protect the environment
  
  

  



Re: Checkout and Build all dependencies

2011-04-08 Thread Ron Wheeler

On 07/04/2011 4:49 PM, AnasMughal wrote:

Yes, that is very similar to our requirement: We need to lock down the build
environment to be able to reproduce the build at anytime in the future.

Need to use version numbers to control your plug-ins as well as your own 
stuff.

Need to use SVN to tag and branch your projects.

Here are the high level objectives:

Checkout all projects from SVN
Build projects using Maven and install them to the local Maven repository.
We would need to start with the parent projects.


Sounds like a simple batch job will do this.
Not hard to make a template where you can search and replace on the 
version of the project or plug-ins that you want.
You should probably build this in advance of each release so that, at 
the start of the development, you nail down the official versions of 
plug-ins that your developers use to build.

This should be in your SVN and properly tagged and branched.

Totally agree: we will not check in everything in SVN.


Can't check-out what you don't check-in.


Ron




On Thu, Apr 7, 2011 at 8:34 AM, Manfred Moser [via Maven]
ml-node+4288827-1669842602-196...@n5.nabble.com  wrote:


We have a compliance/audit requirement that we need to be able to
exactly

reproduce builds. (Current requirement does not allow the build machine
access to our internal nexus repository.)

I have had to deal with this sort of requirement in the past in ISO, FDA
and code repository context. In my opinion you need to be able to build
without anything else apart from the supplied codebase/artifacts. In the
Maven world the best way to achieve this is to package up all the source
code and your repository server setup (or at least the repository used by
your build with all artifacts as well as Maven in the exact version you
use.

You will have to lock down all plugin and dependency versions and be sure
to have them in the repo and then you will be able to do a complete
offline build with the repo.

If you dont do that you will have some major nightmares in terms of
reproducibility of the build and the used artifacts. Do NOT follow down
the path of just trying to check everything into svn. If you do that you
properly you will end up with the repository server in svn. Might as well
allow the repo server to be an artifact...



-
To unsubscribe, e-mail: [hidden 
email]http://user/SendEmail.jtp?type=nodenode=4288827i=0by-user=t
For additional commands, e-mail: [hidden 
email]http://user/SendEmail.jtp?type=nodenode=4288827i=1by-user=t



--
  If you reply to this email, your message will be added to the discussion
below:

http://maven.40175.n5.nabble.com/Checkout-and-Build-all-dependencies-tp4287477p4288827.html
  To unsubscribe from Checkout and Build all dependencies, click 
herehttp://maven.40175.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_codenode=4287477code=YW5hc211Z2hhbEBnbWFpbC5jb218NDI4NzQ3N3wtMzc0Njc1OTEy.








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



Re: How to generate javadocs for only some projects in a multiproject?

2011-04-08 Thread Anders Hammar
I think you're asking two different things here:
1. You only want a javadoc for some projects.
2. You want a single aggrgated javadoc jar

For #2, would the aggregate-jar goal of the javadoc plugin work?

/Anders
On Fri, Apr 8, 2011 at 13:36, Lucas Persson lucas.pers...@oracle.comwrote:

  Hi

 I want to generate and release the javadoc (e.g. the javadoc.jar should be
 a release artefacts just like any other JAR)
 But only some projects contains public java code that javadoc should be
 generated for.
 And if I have for instance 4 projects for which I want to generate javadoc
 I only want one javadoc.jar in the end with the complete source tree.

 I really thought that I found the solution to this in

 http://stackoverflow.com/questions/4947215/maven-3-generate-javadoc-for-defined-artifacts
 but the bug reported in http://jira.codehaus.org/browse/MDEP-291 seem to
 hinder it.

 I really do not want to have some relative path from the 'javadoc project'
 to the projects where the source are in.


 I have also played around with different combination on skip
 like this in the multiproject
   build
 plugins
   plugin
 groupIdorg.apache.maven.plugins/groupId
 artifactIdmaven-javadoc-plugin/artifactId
 inheritedfalse/inherited
 configuration
   skipfalse/skip
 /configuration
   /plugin
 /plugins
 pluginManagement
 plugins
   plugin
 groupIdorg.apache.maven.plugins/groupId
 artifactIdmaven-javadoc-plugin/artifactId
 configuration
   skiptrue/skip
 /configuration
   /plugin
 /plugins

 And in those subproject that I really want javadoc for added:
   plugin
 groupIdorg.apache.maven.plugins/groupId
 artifactIdmaven-javadoc-plugin/artifactId
 configuration
   skipfalse/skip
 /configuration
   /plugin



 So I then tried to use includePackageNames but that does not exists.
 Only excludePackageNames but then I need to exclude like hundred of
 package names, sigh.

 /Lucas



  --
 [image: Oracle] http://www.oracle.com
 Lucas Persson | Principal Member of Technical Staff
 Phone: +4684773644 | | | Mobile: +46730946656
 Oracle Communications Platform
 ORACLE Sweden | Folkungagatan 122 | 116 30 Stockholm

 Oracle Svenska AB, Kronborgsgränd 17, S-164 28 KISTA, reg.no. 556254-6746
 [image: Green Oracle] http://www.oracle.com/commitment Oracle is
 committed to developing practices and products that help protect the
 environment



passing objects between plugins

2011-04-08 Thread Justin Edelson
I'm looking for a way to pass an object from a plugin (e.g. in the
process-resources phase) to another plugin (e.g. in the package
phase). I've done similar things using execution properties in the
MavenSession object, but this only support String values. Is there
some other data structure which can be used to pass something other
than a String?

Thanks,
Justin

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



Re: How to generate javadocs for only some projects in a multiproject?

2011-04-08 Thread Lucas Persson


  
  
Hi
  
  Yes but the two things have to happen at the same time :-)
  
  yes javadoc:aggregate-jar will produce a single jar of javadoc but
  I can not see that I can exclude or include projects.
  It seem to take all projects the the multiproject defines.
  /Lucas

On 04/08/2011 02:29 PM, Anders Hammar wrote:
I think you're asking two different things here:
  1. You only want a javadoc for some projects.
  2. You want a single aggrgated javadoc jar
  
  For #2, would the aggregate-jar goal of the javadoc plugin work?
  
  /Anders
  On Fri, Apr 8, 2011 at 13:36, Lucas
Persson lucas.pers...@oracle.com
wrote:

   Hi
  
  I want to generate and release the javadoc (e.g. the
  javadoc.jar should be a release artefacts just like any
  other JAR)
  But only some projects contains public java code that
  javadoc should be generated for.
  And if I have for instance 4 projects for which I want to
  generate javadoc I only want one javadoc.jar in the end
  with the complete source tree.
  
  I really thought that I found the solution to this in 
  http://stackoverflow.com/questions/4947215/maven-3-generate-javadoc-for-defined-artifacts
  but the bug reported in http://jira.codehaus.org/browse/MDEP-291
  seem to hinder it.
  
  I really do not want to have some relative path from the
  'javadoc project' to the projects where the source are in.
  
  
  I have also played around with different combination on
  skip
  like this in the multiproject
   build
   plugins
   plugin
  
  groupIdorg.apache.maven.plugins/groupId
  
  artifactIdmaven-javadoc-plugin/artifactId
   inheritedfalse/inherited
   configuration
   skipfalse/skip
   /configuration
   /plugin 
   /plugins
   pluginManagement
   plugins
   plugin
  
  groupIdorg.apache.maven.plugins/groupId
  
  artifactIdmaven-javadoc-plugin/artifactId
   configuration
   skiptrue/skip
   /configuration
   /plugin 
   /plugins
  
  And in those subproject that I really want javadoc for
  added:
   plugin
  
  groupIdorg.apache.maven.plugins/groupId
  
  artifactIdmaven-javadoc-plugin/artifactId
   configuration
   skipfalse/skip
   /configuration
   /plugin 
  
  
  
  So I then tried to use includePackageNames but
  that does not exists.
  Only excludePackageNames but then I need to
  exclude like hundred of package names, sigh.
  
  /Lucas
  
  
  

-- 
  
  Lucas Persson | Principal Member of
Technical Staff
Phone: +4684773644 | | | Mobile: +46730946656 
Oracle Communications
Platform
ORACLE Sweden | Folkungagatan 122 | 116 30 Stockholm
  
  Oracle Svenska AB, Kronborgsgrnd
17, S-164 28 KISTA, reg.no.
556254-6746 
   Oracle is committed to developing
practices and products that help protect the environment

  

  
  


-- 
  
  Lucas Persson | Principal Member of Technical Staff
Phone: +4684773644 | | | Mobile:
+46730946656

Oracle Communications Platform
ORACLE Sweden | Folkungagatan 122 | 116 30 Stockholm
  
  Oracle Svenska AB, Kronborgsgrnd 17, S-164 28 KISTA,
reg.no. 556254-6746
  
  
  Oracle is committed to developing practices and
products that help protect the environment
  
  

  



Re: How to generate javadocs for only some projects in a multiproject?

2011-04-08 Thread Anders Hammar
Although you can't exclude projects you should be able to what you want by
excluding packages.

In any case, the problems you are running into is mostly because you're
trying to do something isn't the Maven main road. :-) Why isn't a javadoc
jar for each artifact good enough? That's how your IDE wants it in any case.

/Anders

On Fri, Apr 8, 2011 at 15:47, Lucas Persson lucas.pers...@oracle.comwrote:

  Hi

 Yes but the two things have to happen at the same time :-)

 yes javadoc:aggregate-jar will produce a single jar of javadoc but I can
 not see that I can exclude or include projects.
 It seem to take all projects the the multiproject defines.
 /Lucas

 On 04/08/2011 02:29 PM, Anders Hammar wrote:

 I think you're asking two different things here:
 1. You only want a javadoc for some projects.
 2. You want a single aggrgated javadoc jar

 For #2, would the aggregate-jar goal of the javadoc plugin work?

 /Anders
 On Fri, Apr 8, 2011 at 13:36, Lucas Persson lucas.pers...@oracle.comwrote:

  Hi

 I want to generate and release the javadoc (e.g. the javadoc.jar should be
 a release artefacts just like any other JAR)
 But only some projects contains public java code that javadoc should be
 generated for.
 And if I have for instance 4 projects for which I want to generate javadoc
 I only want one javadoc.jar in the end with the complete source tree.

 I really thought that I found the solution to this in

 http://stackoverflow.com/questions/4947215/maven-3-generate-javadoc-for-defined-artifacts
 but the bug reported in http://jira.codehaus.org/browse/MDEP-291 seem to
 hinder it.

 I really do not want to have some relative path from the 'javadoc project'
 to the projects where the source are in.


 I have also played around with different combination on skip
 like this in the multiproject
   build
 plugins
   plugin
 groupIdorg.apache.maven.plugins/groupId
 artifactIdmaven-javadoc-plugin/artifactId
 inheritedfalse/inherited
 configuration
   skipfalse/skip
 /configuration
   /plugin
 /plugins
 pluginManagement
 plugins
   plugin
 groupIdorg.apache.maven.plugins/groupId
 artifactIdmaven-javadoc-plugin/artifactId
 configuration
   skiptrue/skip
 /configuration
   /plugin
 /plugins

 And in those subproject that I really want javadoc for added:
   plugin
 groupIdorg.apache.maven.plugins/groupId
 artifactIdmaven-javadoc-plugin/artifactId
 configuration
   skipfalse/skip
 /configuration
   /plugin



 So I then tried to use includePackageNames but that does not exists.
 Only excludePackageNames but then I need to exclude like hundred of
 package names, sigh.

 /Lucas



  --
 [image: Oracle] http://www.oracle.com
 Lucas Persson | Principal Member of Technical Staff
 Phone: +4684773644 | | | Mobile: +46730946656
 Oracle Communications Platform
 ORACLE Sweden | Folkungagatan 122 | 116 30 Stockholm

 Oracle Svenska AB, Kronborgsgränd 17, S-164 28 KISTA, reg.no. 556254-6746
 [image: Green Oracle] http://www.oracle.com/commitment Oracle is
 committed to developing practices and products that help protect the
 environment



 --
 [image: Oracle] http://www.oracle.com
 Lucas Persson | Principal Member of Technical Staff
 Phone: +4684773644 | | | Mobile: +46730946656
 Oracle Communications Platform
 ORACLE Sweden | Folkungagatan 122 | 116 30 Stockholm

 Oracle Svenska AB, Kronborgsgränd 17, S-164 28 KISTA, reg.no. 556254-6746
 [image: Green Oracle] http://www.oracle.com/commitment Oracle is
 committed to developing practices and products that help protect the
 environment



Re: How to verify that my memory settings are being picked up

2011-04-08 Thread laredotornado-3
What does the Final Memory: 89M/123M  message mean with regards to what is
set in MAVEN_OPTS?  I understand this might have nothing to do with why I
got the error I got, but I'm curious all the same.

- Dave

--
View this message in context: 
http://maven.40175.n5.nabble.com/How-to-verify-that-my-memory-settings-are-being-picked-up-tp4289082p4291251.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-dependency-plugin uses target dir instead of artifacts from repository

2011-04-08 Thread Brian Fox
It's not a hack, the plugin asks maven core to resolve the artifacts and the
objects it gets back have file handles. In reactor builds with sibling
dependencies, those handles point to the sibling target folder. If you do a
compile reactor build, those handles will point to the /target/classes
folder. IOW, this is Maven Core behavior, not the plugin.

On Fri, Apr 8, 2011 at 3:56 AM, Anders Hammar and...@hammar.net wrote:

 I believe I've run into a similar issue at some time.
 However, there are a few things you should understand:
 1. An reactor build is executed and for that to work, Maven *should* get
 artifacts from the reactor and not the repo
 2. executing mvn pmd:pmd will not install any artifacts to the local
 repository - the build lifecycle is *not* executed

 I think I basically gave up on this as I kind of think it's a hack reusing
 the sources from a different project. And it wasn't really my
 problem/project, so I told them to refactor instead. :-)
 I think that the jira ticket I filed for this is MDEP-291.

 /Anders


 On Fri, Apr 8, 2011 at 09:28, Lucas Persson lucas.pers...@oracle.comwrote:

  Hi


 I have some issues with the maven-dependency-plugin vers 2.2 under
 Maven3.

 In one project I uses the plugin to unpack a sources artifact like this:
   plugin
 groupIdorg.apache.maven.plugins/groupId
 artifactIdmaven-dependency-plugin/artifactId
 executions
   execution
 idunpack-artifact-sources/id
 phasegenerate-resources/phase
 goals
   goalunpack/goal
 /goals
 configuration
   artifactItems
 artifactItem
   groupIdoracle.ucs.callcontrol/groupId
   artifactIdcallcontrolapi/artifactId
   version${project.version}/version
   classifiersources/classifier
   overWritetrue/overWrite
 /artifactItem
   /artifactItems

 outputDirectory${project.build.directory}/unpack-sources/outputDirectory
 /configuration
   /execution
 /executions
   /plugin


 This works very well when doing e.g. 'mvn install'
 But when runnning e.g. mvn pmd:pmd on the parent project (which also
 builds the artifact that this project tries to unpack)
 then the maven-dependency-plugin uses that project's target dir instead
 taking the sources jar form the repository.

  [ERROR] Failed to execute goal 
 org.apache.maven.plugins:maven-dependency-plugin:2.2:unpack 
 (unpack-artifact-sources) on project javadoc: Error unpacking file: 
 /ade/aime_sdp_924164/target/oracle.ucs.callcontrol/callcontrolapi/target/classes
  to: 
 /ade/aime_sdp_924164/target/oracle.sdp.tools/javadoc/target/unpack-sources


 This is very strange.

 Anyone with similar experience?

 Thanks
 Lucas


  --
 [image: Oracle] http://www.oracle.com
 Lucas Persson | Principal Member of Technical Staff
 Phone: +4684773644 | | | Mobile: +46730946656
 Oracle Communications Platform
 ORACLE Sweden | Folkungagatan 122 | 116 30 Stockholm

 Oracle Svenska AB, Kronborgsgränd 17, S-164 28 KISTA, reg.no. 556254-6746
 [image: Green Oracle] http://www.oracle.com/commitment Oracle is
 committed to developing practices and products that help protect the
 environment





Re: One Agile automated CI build

2011-04-08 Thread Bryan Keech
Anyone have more ideas or is anyone doing one ci build that goes all the way to 
a production environment?

- Original Message -
From: Bryan Keech [mailto:bryan.keech.h...@statefarm.com]
Sent: Monday, April 04, 2011 05:32 AM
To: Maven Users List users@maven.apache.org
Subject: RE: One Agile automated CI build

Does anyone have the release plugin run each time CI job runs? Do you use batch 
mode?

-Original Message-
From: Manfred Moser [mailto:manf...@mosabuam.com] 
Sent: Friday, April 01, 2011 10:07 AM
To: Maven Users List
Subject: RE: One Agile automated CI build

Yes, that's the idea. 

Bryan Keech bryan.keech.h...@statefarm.com wrote:

So how about this: I have Hudson CI build run the release to automatically 
update the version each time. Would that work? -Original Message- From: 
Manfred Moser [mailto:manf...@mosabuam.com] Sent: Thursday, March 31, 2011 
11:02 PM To: Maven Users List Cc: Bryan Keech Subject: Re: One Agile automated 
CI build You say .. deployment again of that same version(but with changes) I 
say.. don't do that. If it has changes it is NOT the same version. Just use 
release plugin or whatever to automate changing the version. Maven is going to 
make it hard for you to do the wrong thing. Just do the right thing and change 
the version.. manfred  Let me see if I understood... you don't want the 
previous versions that  were  in artifactory to be lost when you upload an 
artifact with changes but  with  the same version configured in pom?   If 
that's what you're looking for, I dont think you would have other  choice  
but to change the version of your artifact before build.   On!
  Fri,
Apr 1, 2011 at 12:02 AM, Bryan Keech  bryan.keech.h...@statefarm.com  
wrote:   In my case we are building J2EE apps.   Maybe me explaining 
what I am after would help. :)   I would like this flow to happen:   - 
Developer commits  - CI build is done on Hudson  - artifacts are stored in 
our remote repository (artifactory)  - artifacts can then be deployed to a 
jvm   Currently if we have a version already deployed to artifactory and we 
do  a  deployment again of that same version(but with changes), it 
overwrites  what  is in artifactory.   I guess I am looking for a way 
for each build to be available in  artifactory.   Thanks  Bryan   
-Original Message-  From: Tim Pizey [mailto:tim.pi...@gmail.com]  
Sent: Wednesday, March 30, 2011 2:02 PM  To: Maven Users List  Cc: Bryan 
Keech  Subject: Re: One Agile automated CI build   Hi Brian,   I 
think we have a very simple system, and we do not use artefactory. !
   I
hope I am right in thinkin g you are deploying a war.   We use jenkins with 
the following command:   mvn clean install deploy tomcat:deploy -Pstaging 
  this stores artifacts, be they snapshot or release, to the repository  
and deploys to staging.   hope this makes sense   cheers  Tim   
On 30 March 2011 19:24, Bryan Keech wrote:   Can anyone give details on how 
they have done this? I am running into  road blocks. If I leave the 
version as a non-snapshot, then Hudson deploys to  artifactory and overwrites 
the same version in the repo. I have toyed  with  using 
install:install-file goal in the install phase. Thanks,   Bryan  
--  Tim Pizey - http://pizey.net/~timp  Centre for Genomics and Global 
Health - http://cggh.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: One Agile automated CI build

2011-04-08 Thread Wayne Fay
 Anyone have more ideas or is anyone doing one ci build that goes all the way 
 to a production environment?

 Does anyone have the release plugin run each time CI job runs? Do you use 
 batch mode?

This discussion may be better received on lists focused on continuous
integration (hudson/jenkins user lists) or Stackoverflow.

Also it sounds like you may be talking about Continuous Delivery which
is a different topic altogether... or possibly just conflating things
a bit.

Wayne

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



Re: passing objects between plugins

2011-04-08 Thread Wayne Fay
 phase). I've done similar things using execution properties in the
 MavenSession object, but this only support String values. Is there
 some other data structure which can be used to pass something other
 than a String?

I was going to suggest via the MavenSession object... so I guess I
can't help here. If you find a solution, post back.

(Couldn't you arguably serialize your object as a string?)

Wayne

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



Re: passing objects between plugins

2011-04-08 Thread Justin Edelson
On Fri, Apr 8, 2011 at 3:48 PM, Wayne Fay wayne...@gmail.com wrote:
 phase). I've done similar things using execution properties in the
 MavenSession object, but this only support String values. Is there
 some other data structure which can be used to pass something other
 than a String?

 I was going to suggest via the MavenSession object... so I guess I
 can't help here. If you find a solution, post back.

 (Couldn't you arguably serialize your object as a string?)

I'm effectively doing this already by saving an XML representation of
the object in the target directory, but I thought something more
direct would be nicer looking :)


 Wayne

 -
 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