AW: AW: Dependency on pom-project not resolved in reactor on multi-module build
Hi Florian,
since testing your problem I've some trouble with my workspace ;-)
I'm not understanding the behavior (of my ws) yet!
I'm using m3, there your problem seems to be fixed.
So it looks more like a bug than a feature!
Fredy
#
Maven 2.2.1:
#
C:\temp\pom-dep-problemD:\IDE\apache-maven-2.2.1\bin\mvn.bat -version
Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
Java version: 1.6.0_21
Java home: C:\Program Files\Java\jdk1.6.0_21\jre
Default locale: de_DE, platform encoding: Cp1252
OS name: windows xp version: 5.1 arch: x86 Family: windows
C:\temp\pom-dep-problemD:\IDE\apache-maven-2.2.1\bin\mvn.bat clean package
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] Unnamed - mygroup:parent:pom:1.0-SNAPSHOT
[INFO] Unnamed - mygroup:A:pom:1.0-SNAPSHOT
[INFO] Unnamed - mygroup:B:jar:1.0-SNAPSHOT
[INFO]
[INFO] Building Unnamed - mygroup:parent:pom:1.0-SNAPSHOT
[INFO]task-segment: [clean, package]
[INFO]
[INFO] [clean:clean {execution: default-clean}]
[INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
[INFO]
[INFO] Building Unnamed - mygroup:A:pom:1.0-SNAPSHOT
[INFO]task-segment: [clean, package]
[INFO]
[INFO] [clean:clean {execution: default-clean}]
[INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
[INFO]
[INFO] Building Unnamed - mygroup:B:jar:1.0-SNAPSHOT
[INFO]task-segment: [clean, package]
[INFO]
[INFO] [clean:clean {execution: default-clean}]
[INFO] [resources:resources {execution: default-resources}]
[WARNING] Using platform encoding (Cp1252 actually) to copy filtered resources,
i.e. build is platform dependent!
[INFO] skip non existing resourceDirectory
C:\temp\pom-dep-problem\B\src\main\resources
Downloading:
http://xxx:8180/px-webapp/repository/jboss.org.snapshot/mygroup/A/1.0-SNAPSHOT/A-1.0-SNAPSHOT.pom
[INFO] Unable to find resource 'mygroup:A:pom:1.0-SNAPSHOT' in repository
jboss.snapshots (http://xxx:8180/px-webapp/repository/jboss.org.snapshot)
Downloading:
http://xxx:8180/px-webapp/repository/xxx.snapshot/mygroup/A/1.0-SNAPSHOT/A-1.0-SNAPSHOT.pom
[INFO] Unable to find resource 'mygroup:A:pom:1.0-SNAPSHOT' in repository
xxx.snapshots (http://xxx:8180/px-webapp/repository/xxx.snapshot)
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to resolve artifact.
Missing:
--
1) mygroup:A:pom:1.0-SNAPSHOT
Path to dependency:
1) mygroup:B:jar:1.0-SNAPSHOT
2) mygroup:A:pom:1.0-SNAPSHOT
--
1 required artifact is missing.
for artifact:
mygroup:B:jar:1.0-SNAPSHOT
from the specified remote repositories:
xxx.snapshots (http://xxx:8180/px-webapp/repository/xxx.snapshot),
jboss.org (http://xxx:8180/px-webapp/repository/jboss.org),
jboss.snapshots (http://xxx:8180/px-webapp/repository/jboss.org.snapshot),
xxx (http://xxx:8180/px-webapp/repository/xxx),
xxx_public (http://xxx:8180/px-webapp/repository/public)
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 2 seconds
[INFO] Finished at: Mon Dec 20 09:22:57 CET 2010
[INFO] Final Memory: 12M/28M
[INFO]
#
Maven 3.0:
#
C:\temp\pom-dep-problemmvn -version
Apache Maven 3.0 (r1004208; 2010-10-04 13:50:56+0200)
Java version: 1.6.0_21
Java home: C:\Program Files\Java\jdk1.6.0_21\jre
Default locale: de_DE, platform encoding: Cp1252
OS name: windows xp version: 5.1 arch: x86 Family: windows
C:\temp\pom-dep-problemmvn clean package
[INFO] Scanning for projects...
[INFO]
[INFO] Reactor Build Order:
[INFO]
[INFO] parent
[INFO] A
[INFO] B
[INFO]
[INFO]
[INFO] Building parent 1.0-SNAPSHOT
[INFO]
[INFO]
[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
REPOST: How does the default annotation processors discovery process apply?
http://stackoverflow.com/questions/4488237/how-does-the-default-annotation-processors-discovery-process-apply In question how-to-process-annotations-with-mavenhttp://stackoverflow.com/questions/4487338/how-to-process-annotations-with-mavenI posted a link for a maven project that processes annotations. That link declares the annotation processors used in a file under resources. I wonder if there wasn't another way all within the pom? Note that the annotations are to be processed for test files within the same project (they indeed test the annotations and their processors). In other words, how can I let maven-compiler-plugin figure out the processors (from within the project and the dependecies) that process the annotations used? Will I always need to specify the processors used? As with the previous question, any sample project? -- Regards, K. Gabriele --- unchanged since 20/9/10 --- P.S. If the subject contains [LON] or the addressee acknowledges the receipt within 48 hours then I don't resend the email. subject(this) ∈ L(LON*) ∨ ∃x. (x ∈ MyInbox ∧ Acknowledges(x, this) ∧ time(x) Now + 48h) ⇒ ¬resend(I, this). If an email is sent by a sender that is not a trusted contact or the email does not contain a valid code then the email is not received. A valid code starts with a hyphen and ends with X. ∀x. x ∈ MyInbox ⇒ from(x) ∈ MySafeSenderList ∨ (∃y. y ∈ subject(x) ∧ y ∈ L(-[a-z]+[0-9]X)).
Maven plugin (or other tool) to handle encryption of server passwords
I'm looking for a plugin or some tool that helps out encrypting the server passwords in Maven. I know the manual command line way of doing this, but I'm looking for any easier way of doing this. If you're having lots of devs, a few are very likely not to get this right... Anyone seen such a plugin or tool? /Anders
Re: How to resolve 'LATEST'
Hi! Have a look at versions-maven-plugin. It provides a goal for updating the parent [0]. Maybe you can reuse code from it. hth, - martin [0] http://mojo.codehaus.org/versions-maven-plugin/update-parent-mojo.html On Friday 17 December 2010 Asmann, Roland wrote: Currently I am not using this, but I want the enforcer to check which version 'LATEST' is and tell the user he should update to that version! On 17-12-10 17:04, Brian Fox wrote: Don't use RELEASE or LATEST. On Fri, Dec 17, 2010 at 7:43 AM, Asmann, Roland roland.asm...@adesso.at wrote: Hi all, I'm writing an enforcer-rule, that should check if my parent is the LATEST version. How can I get the actual version for 'LATEST'? Thanks! -- Roland Asmann Senior Software Engineer adesso Austria GmbH Floridotower 26. Stock T +43 1 2198790-27 Floridsdorfer Hauptstr. 1 F +43 1 2198790-927 A-1210 Wien M +43 664 88657566 E roland.asm...@adesso.at W www.adesso.at - business. people. technology. - - 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 signature.asc Description: This is a digitally signed message part.
[ANN] Apache Archiva 1.3.3 released
The Apache Archiva team would like to announce the release of Archiva 1.3.3. All users are advised to upgrade. Archiva is available for download from: * http://archiva.apache.org/download.html Archiva is an application for managing one or more remote artifact repositories, including administration, artifact handling, browsing and searching. If you have any questions, please consult: * the web site: http://archiva.apache.org/ * the archiva-user mailing list: http://archiva.apache.org/mail-lists.html ** Release Notes for Archiva 1.3.3 ** This release brings significant performance and memory improvements to large or frequent scanning and indexing operations, as well as diagnostic tools for reviewing the current server performance. [MRM-1097] - Error 500 too many open files [MRM-1369] - Editing user roles in archiva clobbers continuum redback roles [MRM-1396] - Purge task problem : Not enough parts to the path [MRM-1421] - Archiva repository purge incorrectly purges based on file timestamps even when the snapshot timestamp is known [MRM-1443] - repository statistics collection can cause server to hang [MRM-1416] - upgrade to Redback 1.2.5 [MRM-1439] - improve indexing performance [MRM-1440] - system status page [MRM-1441] - monitor repository scanning progress [MRM-1442] - track time spent in each consumer during a scan, to help diagnose poor scanning performance [MRM-1445] - disable referrer check by default -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven assembly
I am trying to get the maven assembly working but I dont get it to work the way I want. I got a multi-project I got a root - under_root - project (pom.xml) Now I want ALL my modules latest releases in a tar.gz package. How do I do this the simplest way??? Where do I add the plugin in (in which pom?) Will I need to create a new pom that starts all this packing? (its ok if that is the way) And so on I have tried to follow diffrent guides but i can get the jar files to jump into the tar gz file. So is there any kind person who could tell me how to do this? -- View this message in context: http://maven.40175.n5.nabble.com/Maven-assembly-tp3311934p3311934.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 assembly
I recommend creating a separate project to do this. In that project you declare dependency to all artifacts you want to pack. Then create your assembly xml (or use any one of the provided ones). /Anders On Mon, Dec 20, 2010 at 14:08, mickeys nero2...@hotmail.com wrote: I am trying to get the maven assembly working but I dont get it to work the way I want. I got a multi-project I got a root - under_root - project (pom.xml) Now I want ALL my modules latest releases in a tar.gz package. How do I do this the simplest way??? Where do I add the plugin in (in which pom?) Will I need to create a new pom that starts all this packing? (its ok if that is the way) And so on I have tried to follow diffrent guides but i can get the jar files to jump into the tar gz file. So is there any kind person who could tell me how to do this? -- View this message in context: http://maven.40175.n5.nabble.com/Maven-assembly-tp3311934p3311934.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
Problem with classpath for tests
Hi all, I've been trying to get some projects running on my Hudson server, abd am running into problems. I've hunted down the problem to being the version of Maven that I use! On my Hudson I am running both 2.0.10 (for some older projects) and 2.2.1. On both these versions I have a project that is failing. Now, I asked the developer and he told me he is on Maven 2.0.9... When I run with that version, everything works as it should! From the output generated by Maven, I can see that there is a difference in the classpath for the tests. It appears that starting with 2.0.10, the 'target/classes' and 'target/test-classes' are no longer the first entries on the classpath, but the last. This seems to be the problem I'm having, and tbh I have no idea on how I could fix this problem and get my tests running again... Does anybody have an idea or suggestion on how to fix this? Thanks! -- Roland Asmann Senior Software Engineer adesso Austria GmbH Floridotower 26. Stock T +43 1 2198790-27 Floridsdorfer Hauptstr. 1 F +43 1 2198790-927 A-1210 Wien M +43 664 88657566 E roland.asm...@adesso.at W www.adesso.at - business. people. technology. - - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Problem with classpath for tests
Sorry, I got the location of the directories wrong... They were last but are now first! On 20.12.2010 14:47, Asmann, Roland wrote: Hi all, I've been trying to get some projects running on my Hudson server, abd am running into problems. I've hunted down the problem to being the version of Maven that I use! On my Hudson I am running both 2.0.10 (for some older projects) and 2.2.1. On both these versions I have a project that is failing. Now, I asked the developer and he told me he is on Maven 2.0.9... When I run with that version, everything works as it should! From the output generated by Maven, I can see that there is a difference in the classpath for the tests. It appears that starting with 2.0.10, the 'target/classes' and 'target/test-classes' are no longer the first entries on the classpath, but the last. This seems to be the problem I'm having, and tbh I have no idea on how I could fix this problem and get my tests running again... Does anybody have an idea or suggestion on how to fix this? Thanks! -- Roland Asmann Senior Software Engineer adesso Austria GmbH Floridotower 26. Stock T +43 1 2198790-27 Floridsdorfer Hauptstr. 1 F +43 1 2198790-927 A-1210 Wien M +43 664 88657566 E roland.asm...@adesso.at W www.adesso.at - business. people. technology. - - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Roland Asmann Senior Software Engineer adesso Austria GmbH Floridotower 26. Stock T +43 1 2198790-27 Floridsdorfer Hauptstr. 1 F +43 1 2198790-927 A-1210 Wien M +43 664 88657566 E roland.asm...@adesso.at W www.adesso.at - business. people. technology. - - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
release:prepare does not inherit plugins from the parent project?
Hi, I'm having problems using release:prepare plugin on a project that inherits from a parent project. It seems that it cannot see the plugins from the parent project and fails on compiling java vesion 1.6 classes claiming that 1.3 version does not support annotations. It works fine with clean install. The maven-compiler-plugin is defined in the parent project. What can be the problem? thanks in advance, Piotr
Re: release:prepare does not inherit plugins from the parent project?
Check the project's effective pom. mvn help:effective-pom Most likely what you think should be inherited isn't. How is m-compiler-p declared in the parent? /Anders On Mon, Dec 20, 2010 at 14:50, Piotr Skawinski piotr.skawinski.ma...@gmail.com wrote: Hi, I'm having problems using release:prepare plugin on a project that inherits from a parent project. It seems that it cannot see the plugins from the parent project and fails on compiling java vesion 1.6 classes claiming that 1.3 version does not support annotations. It works fine with clean install. The maven-compiler-plugin is defined in the parent project. What can be the problem? thanks in advance, Piotr
releas:perform with profiles fails
Hi list, I've a multi module with differences between the prod and dev environment. Threfor I've defined some profiles. mvn clean install -P devContainerSettings,dependencies,!eclipse works fine! but mvn --batch-mode release:prepare -P devContainerSettings,dependencies,!eclipse fails with compilations errors! Any idea?? Apache Maven 3.0 (r1004208; 2010-10-04 13:50:56+0200) Java version: 1.6.0_21 Java home: C:\Program Files\Java\jdk1.6.0_21\jre Default locale: de_DE, platform encoding: Cp1252 OS name: windows xp version: 5.1 arch: x86 Family: windows Fredy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: release:prepare does not inherit plugins from the parent project?
Hi again, Actually when running mvn help:effective-pom I can see all plugins from the parent as expected, but when running it after release:prepare (which actually faills) they are not there anymore. It seems that release:prepare ignores the parent's plugins for the project it runs the release for. Though, when plugins are defined in the project's scope and not the parent's the release:prepare works as expected. The plugin in the parent is defines parent as follows: project . . . build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId version2.0.2/version configuration source1.6/source target1.6/target encodingUTF-8/encoding /configuration /plugin plugins build project Piotr On Mon, Dec 20, 2010 at 2:57 PM, Anders Hammar and...@hammar.net wrote: Check the project's effective pom. mvn help:effective-pom Most likely what you think should be inherited isn't. How is m-compiler-p declared in the parent? /Anders On Mon, Dec 20, 2010 at 14:50, Piotr Skawinski piotr.skawinski.ma...@gmail.com wrote: Hi, I'm having problems using release:prepare plugin on a project that inherits from a parent project. It seems that it cannot see the plugins from the parent project and fails on compiling java vesion 1.6 classes claiming that 1.3 version does not support annotations. It works fine with clean install. The maven-compiler-plugin is defined in the parent project. What can be the problem? thanks in advance, Piotr
AW: releas:perform with profiles fails
Found a workarround: http://www.tutorials.de/java/347377-maven-release-plugin-und-profile-activation.html Fredy -Ursprüngliche Nachricht- Von: Hauschel Fred Robert [mailto:fredrobert.hausc...@cirquent.de] Gesendet: Montag, 20. Dezember 2010 15:23 An: Maven Users List Betreff: releas:perform with profiles fails Hi list, I've a multi module with differences between the prod and dev environment. Threfor I've defined some profiles. mvn clean install -P devContainerSettings,dependencies,!eclipse works fine! but mvn --batch-mode release:prepare -P devContainerSettings,dependencies,!eclipse fails with compilations errors! Any idea?? Apache Maven 3.0 (r1004208; 2010-10-04 13:50:56+0200) Java version: 1.6.0_21 Java home: C:\Program Files\Java\jdk1.6.0_21\jre Default locale: de_DE, platform encoding: Cp1252 OS name: windows xp version: 5.1 arch: x86 Family: windows Fredy - 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: releas:perform with profiles fails
http://blog.artifact-software.com/tech/ includes a blog entry on using JNDI to get environment stuff out of projects. Got tired of writing it every week here. Putting environmental stuff inside your modules is a recipe for long frustrating Maven discussions and hours of fruitless screwing about. If you want anyone to guess as to what causes a compilation error, you will have to give us some hints about it. What error? What does Maven say is happening? Separation of concerns between development and deployment will make both sides of the job much easier and much less prone to run-time screw-ups in production. As you get further into the process, you will likely get a lot more environments to support - current production, customer acceptance testing, pre-release testing, integration testing, localhost testing, etc. If you have customization for customers or multiple releases in production, your problems multiply. Get the deployment stuff out of your codebase ASAP. Ron On 20/12/2010 9:23 AM, Hauschel Fred Robert wrote: Hi list, I've a multi module with differences between the prod and dev environment. Threfor I've defined some profiles. mvn clean install -P devContainerSettings,dependencies,!eclipse works fine! but mvn --batch-mode release:prepare -P devContainerSettings,dependencies,!eclipse fails with compilations errors! Any idea?? Apache Maven 3.0 (r1004208; 2010-10-04 13:50:56+0200) Java version: 1.6.0_21 Java home: C:\Program Files\Java\jdk1.6.0_21\jre Default locale: de_DE, platform encoding: Cp1252 OS name: windows xp version: 5.1 arch: x86 Family: windows Fredy - 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
maven3: custom repository layout gives NoRepositoryConnectorException
Hi I am trying to migrate to maven3. And I have a couple of custom repository layouts registered that works all right in maven2. But in maven3 I got this exception (when running with mvn -e) Caused by: org.sonatype.aether.transfer.NoRepositoryConnectorException: No connector available to access repository adminserver-series (file:///ade/lupersso_sdp_main/adminserver/dist/oracle.jrf.dms/modules) of type fmw using the available factories WagonRepositoryConnectorFactory at org.sonatype.aether.impl.internal.DefaultRemoteRepositoryManager.getRepositoryConnector(DefaultRemoteRepositoryManager.java:365) at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:407) at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:187) I have added the getId() method that was added in the interface in Maven3. My repository layout class gets loaded, that I have tested by remote debuging maven. I suppose that there is some wirering I have missed. 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: AW: releas:perform with profiles fails
On 20/12/2010 10:20 AM, Hauschel Fred Robert wrote: Found a workarround: http://www.tutorials.de/java/347377-maven-release-plugin-und-profile-activation.html Fredy You will be back. Search this forum for discussions of profiles and environments. The road to Maven hell is paved with profiles. Just as good intentions are wonderful on their own, profiles can lead you to do things that will get you into bad situations. Not to say that they are evil in themselves and do not have good uses. This is not one of them. Ron -Ursprüngliche Nachricht- Von: Hauschel Fred Robert [mailto:fredrobert.hausc...@cirquent.de] Gesendet: Montag, 20. Dezember 2010 15:23 An: Maven Users List Betreff: releas:perform with profiles fails Hi list, I've a multi module with differences between the prod and dev environment. Threfor I've defined some profiles. mvn clean install -P devContainerSettings,dependencies,!eclipse works fine! but mvn --batch-mode release:prepare -P devContainerSettings,dependencies,!eclipse fails with compilations errors! Any idea?? Apache Maven 3.0 (r1004208; 2010-10-04 13:50:56+0200) Java version: 1.6.0_21 Java home: C:\Program Files\Java\jdk1.6.0_21\jre Default locale: de_DE, platform encoding: Cp1252 OS name: windows xp version: 5.1 arch: x86 Family: windows Fredy - 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:prepare does not inherit plugins from the parent project?
Where is the reference to 1.3 coming from? I think that was what the effective-pom was for, not to see if the plug-ins were there but to find out who is asking for 1.3. Ron On 20/12/2010 10:05 AM, Piotr Skawinski wrote: Hi again, Actually when running mvn help:effective-pom I can see all plugins from the parent as expected, but when running it after release:prepare (which actually faills) they are not there anymore. It seems that release:prepare ignores the parent's plugins for the project it runs the release for. Though, when plugins are defined in the project's scope and not the parent's the release:prepare works as expected. The plugin in the parent is defines parent as follows: project . . . build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId version2.0.2/version configuration source1.6/source target1.6/target encodingUTF-8/encoding /configuration /plugin plugins build project Piotr On Mon, Dec 20, 2010 at 2:57 PM, Anders Hammarand...@hammar.net wrote: Check the project's effective pom. mvn help:effective-pom Most likely what you think should be inherited isn't. How is m-compiler-p declared in the parent? /Anders On Mon, Dec 20, 2010 at 14:50, Piotr Skawinski piotr.skawinski.ma...@gmail.com wrote: Hi, I'm having problems using release:prepare plugin on a project that inherits from a parent project. It seems that it cannot see the plugins from the parent project and fails on compiling java vesion 1.6 classes claiming that 1.3 version does not support annotations. It works fine with clean install. The maven-compiler-plugin is defined in the parent project. What can be the problem? thanks in advance, Piotr - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Problems with maven assembly and mar files
Hello, i trying package my project with the plugin maven assembly. The command that i use is mvn assembly:assembly -DdescriptorId=jar-with-dependencies, but the following error is showed: [ERROR] BUILD ERROR [INFO] [INFO] Failed to create assembly: Error adding file-set for 'org.apache.axis2:addressing:mar:1.4' to archive: Error adding archived file-set. PlexusIoResourceCollection not found for: /home/joabelfa/workspace/.m2/repository/org/apache/axis2/addressing/1.4/addressing-1.4.mar No such archiver: 'mar'. I think that the problem is for use the rampart library. How to packaging all libraries in one jar in order to user ca import in eclipse projectes?? Regards. This message was sent using IMP, the Internet Messaging Program. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: release:prepare does not inherit plugins from the parent project?
Analyzing the debug and error output should also give a clue. Maybe focus on that and ignore the effective pom for now. /Anders (mobile) Den 20 dec 2010 17.05 skrev Ron Wheeler rwhee...@artifact-software.com: Where is the reference to 1.3 coming from? I think that was what the effective-pom was for, not to see if the plug-ins were there but to find out who is asking for 1.3. Ron On 20/12/2010 10:05 AM, Piotr Skawinski wrote: Hi again, Actually when running mvn help:effective-pom I can see all plugins from the parent as expected, but when running it after release:prepare (which actually faills) they are not there anymore. It seems that release:prepare ignores the parent's plugins for the project it runs the release for. Though, when plugins are defined in the project's scope and not the parent's the release:prepare works as expected. The plugin in the parent is defines parent as follows: project . . . build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId version2.0.2/version configuration source1.6/source target1.6/target encodingUTF-8/encoding /configuration /plugin plugins build project Piotr On Mon, Dec 20, 2010 at 2:57 PM, Anders Hammarand...@hammar.net wrote: Check the project's effective pom. mvn help:effective-pom Most likely what you think should be inherited isn't. How is m-compiler-p declared in the parent? /Anders On Mon, Dec 20, 2010 at 14:50, Piotr Skawinski piotr.skawinski.ma...@gmail.com wrote: Hi, I'm having problems using release:prepare plugin on a project that inherits from a parent project. It seems that it cannot see the plugins from the parent project and fails on compiling java vesion 1.6 classes claiming that 1.3 version does not support annotations. It works fine with clean install. The maven-compiler-plugin is defined in the parent project. What can be the problem? thanks in advance, Piotr - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
How to build sub-modules selectively?
With a structure like the following: umbrella-module core-module optional-module-1 optional-module-2 How can the maven pom files be configured so that a user can build: 1) either, core-module with configuration and jar files from optional-module-1 as dependencies 2) or, core-module with configuration and jar files from optional-module-2 as dependencies based on what command is issued via the command line: mvn install mod1 or mvn install mod2 I'm guessing that some sort of condition will need to be put into place in the core-module's pom.xml file to let it know which dependency it needs? Based on what is specified in an env variable or on the command line? How can that condition be set up? If there is a different / better approach to this, please let me know. Thanks! - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to build sub-modules selectively?
I'm guessing that some sort of condition will need to be put into place in the core-module's pom.xml file to let it know which dependency it needs? Based on what is specified in an env variable or Whenever you are looking for this kind of conditional building of your projects, you should immediately think of profiles. This is well documented online if you just search for it. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven3: custom repository layout gives NoRepositoryConnectorException
ok I have investigated this a bit more It looks like that the WagonRepositoryConnectorFactory throws exception if the repository layout is != "default". So I guess that means that if you want your own layout you also need to create your own RepositoryConnectorFactory (which most likely will be a copy of the WagonRepositoryConnectorFactory)??? Can it really like that? Cheers Lucas On 12/20/2010 04:30 PM, Lucas Persson wrote: Hi I am trying to migrate to maven3. And I have a couple of custom repository layouts registered that works all right in maven2. But in maven3 I got this exception (when running with mvn -e) Caused by: org.sonatype.aether.transfer.NoRepositoryConnectorException: No connector available to access repository adminserver-series (file:///ade/lupersso_sdp_main/adminserver/dist/oracle.jrf.dms/modules) of type fmw using the available factories WagonRepositoryConnectorFactory at org.sonatype.aether.impl.internal.DefaultRemoteRepositoryManager.getRepositoryConnector(DefaultRemoteRepositoryManager.java:365) at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:407) at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:187) I have added the getId() method that was added in the interface in Maven3. My repository layout class gets loaded, that I have tested by remote debuging maven. I suppose that there is some wirering I have missed. 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: How to build sub-modules selectively?
On 20/12/2010 1:11 PM, Wayne Fay wrote: I'm guessing that some sort of condition will need to be put into place in the core-module's pom.xml file to let it know which dependency it needs? Based on what is specified in an env variable or Whenever you are looking for this kind of conditional building of your projects, you should immediately think of profiles. You should also think Why are my modules optional? Am I really trying to build separate artifacts? Should I have a simple project that just builds the artifact with optional module 1 and another that just builds with optional module 2 rather than a project that is hopelessly complex and prone to errors and requires a lot of maintenance. Am I mixing deployment environment information(properties, database connections, site info, web service endpoints) with code. This should not be done at all. Ron /Maven Profiles are like Good Intentions. They are far from evil but they both can pave the way to hell./ This is well documented online if you just search for it. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Can I release:perform without release:prepare?
I've already manually done the release:prepare because for some reason my release:prepare didn't successfully push to github. I'm using Maven 2.2.1. -K - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven 3 polyglot and/or attribute based configuration
Hi, I have long been a user of Maven, but disfavoured the xml verbosity. With Maven 3 I am aware of the polyglot capabilities of using Groovy or YAML for pom files, but I would still prefer the xml syntax for a while. A few years ago, a JIRA was raised [1], and an experimental branch created as a proof-of-concept, introducing attributed based configuration, having entities like: dependencies dependency groupId=junit artifactId=junit version=3.8.1 scope=test/ /dependencies Which I think is a good format. It is easier to compact a full pom file and see what goes on, and it still verifies against a DTD. However, it may contradict existing tools and behaviours. Alternatively mix the current model with a namespaced schema-extension, which could provide attributed based primitives for the most common items. Does anyone know if this has been reconsider inside Maven 3 at all or is the polyglot solution the path to the future maven configuration? Regards Niels B Nielsen | Lead Engineer J.P. Morgan | IBTech Global Rates Derivatives [1] http://jira.codehaus.org/browse/MNG-3397 This email is confidential and subject to important disclaimers and conditions including on offers for the purchase or sale of securities, accuracy and completeness of information, viruses, confidentiality, legal privilege, and legal entity disclaimers, available at http://www.jpmorgan.com/pages/disclosures/email.
m2eclipse plugin builder or launcher
Hi, I have a question regarding the m2eclipse plugin. Let me know if this is not the right place to ask. I'm writing my own custom plugin, and I would like to execute the mvn package command. Meaning: I want to run the m2eclipse builder, so that it would run the Run As-Maven package. Anyone has some source code or can give me a tip how to do this? I'm guessing that I would need to create a new LaunchConfiguration, but I've no idea how to start... Thanks, Csaba - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
