distributionManagement
Hi to all, I would like to know if distributionManagement tag should be exist in pom.xml ? I am using makepom command - so who can I adding this distributionManagement tag to pom.xml ? Best regards, Yos
Re: distributionManagement
I am not sure what makepom is, so I went to google. It seems likely an Ivy Question With regards to distributionManagement: It is optional -- -- Aldrin Leal, ald...@leal.eng.br / http://www.leal.eng.br/mnemetica/ On Sun, Jun 26, 2011 at 6:03 AM, Brosh, Yossi yossi.br...@sap.com wrote: Hi to all, I would like to know if distributionManagement tag should be exist in pom.xml ? I am using makepom command - so who can I adding this distributionManagement tag to pom.xml ? Best regards, Yos
Artifact[ejb:org.jboss.seam:jboss-seam] is not a dependency of the project.
Could someone tell me what's wrong with the attached POM. It
should basically build an EAR with application.xml defining
jboss-seam as only EJB module. The problem is I'm getting:
$ mvn package
[INFO] Scanning for projects...
[INFO]
[INFO] Building seam-ear
[INFO]task-segment: [package]
[INFO]
[INFO] [ear:generate-application-xml {execution:
default-generate-application-xml}]
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Artifact[ejb:org.jboss.seam:jboss-seam] is not a dependency of the
project.
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 1 second
[INFO] Finished at: Sun Jun 26 12:46:16 EEST 2011
[INFO] Final Memory: 8M/154M
[INFO]
I've really included jboss-seam as a dependency and I even expect
I don't need to define it as ejbModule in the EAR plugin
configuration, as it is already declared as packagingejb/packaging,
but without defining it as ejbModule it ends up packaged as
ordinary lib and not included in the application.xml (this might
be related to the main problem).
I'm using Maven 2.2.1 on Windows.
--
Stanimir
?xml version=1.0 encoding=UTF-8 ?
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd;
modelVersion4.0.0/modelVersion
groupIdnet.example.ear/groupId
artifactIdseam-ear/artifactId
version0.0.1-SNAPSHOT/version
packagingear/packaging
nameseam-ear/name
build
finalName${project.artifactId}/finalName
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-ear-plugin/artifactId
version2.6/version
configuration
version5/version
defaultLibBundleDirlib/defaultLibBundleDir
fileNameMappingno-version/fileNameMapping
modules
ejbModule
groupIdorg.jboss.seam/groupId
artifactIdjboss-seam/artifactId
/ejbModule
/modules
/configuration
/plugin
/plugins
/build
dependencies
dependency
groupIdorg.jboss.seam/groupId
artifactIdjboss-seam/artifactId
version2.0.2.SP1/version
!-- typeejb/type --
/dependency
/dependencies
repositories
repository
idpublic-jboss/id
urlhttps://repository.jboss.org/nexus/content/groups/public-jboss//url
/repository
/repositories
/project
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: distributionManagement
It goes in the parent pom for the project since it is shared by all modules in the project. This should make your problem go away. Define the repositories and distribution management once in the parent. Each module in the project merely points to the parent to get set up correctly. That is probably why distribution management is not part of the output from the utility that you are using. Ron On 26/06/2011 5:25 AM, Aldrin Leal wrote: I am not sure what makepom is, so I went to google. It seems likely an Ivy Question With regards to distributionManagement: It is optional -- -- Aldrin Leal,ald...@leal.eng.br / http://www.leal.eng.br/mnemetica/ On Sun, Jun 26, 2011 at 6:03 AM, Brosh, Yossiyossi.br...@sap.com wrote: Hi to all, I would like to know if distributionManagement tag should be exist in pom.xml ? I am using makepom command - so who can I adding this distributionManagement tag to pom.xml ? Best regards, Yos - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Artifact[ejb:org.jboss.seam:jboss-seam] is not a dependency of the project.
Sun, 26 Jun 2011 12:59:10 +0300, /Stanimir Stamenkov/:
I've really included jboss-seam as a dependency and I even
expect I don't need to define it as ejbModule in the EAR plugin
configuration, as it is already declared as
packagingejb/packaging, but without defining it as ejbModule
it ends up packaged as ordinary lib and not included in the
application.xml (this might be related to the main problem).
O.k. I've tried with my own EJB module and I've found I have to
specify typeejb/type for the dependency to get automatically
included as EJB module in the EAR. So the attached pom.xml
appears to build as expected.
However I seem to get problem when jboss-seam is declared in
dependencyManagement in a parent POM. Place the attached
parent-pom.xml and ear-pom.xml in a same directory (the same
happens using standard layout having the EAR pom.xml in a child
directory) and build using either one of them:
$ mvn -f parent-pom.xml install
or
$ mvn -f ear-pom.xml install
I get:
[INFO] Scanning for projects...
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] Error building POM (may not be this project's POM).
Project ID: net.example.ear:seam-ear
POM Location: ...\ear-pom.xml
Validation Messages:
[0] 'dependencies.dependency.version' is missing for
org.jboss.seam:jboss-seam:ejb
Reason: Failed to validate POM for project net.example.ear:seam-ear at
...\ear-pom.xml
Specifying the jboss-seam version additionally in the EAR POM
seems to fix the things, but why one has to do it given the version
is specified in the parent POM?
--
Stanimir
?xml version=1.0 encoding=UTF-8 ?
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd;
modelVersion4.0.0/modelVersion
groupIdnet.example.ear/groupId
artifactIdseam-ear/artifactId
version0.0.1-SNAPSHOT/version
packagingear/packaging
nameseam-ear/name
build
finalName${project.artifactId}/finalName
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-ear-plugin/artifactId
version2.6/version
configuration
version5/version
defaultLibBundleDirlib/defaultLibBundleDir
fileNameMappingno-version/fileNameMapping
/configuration
/plugin
/plugins
/build
dependencies
dependency
groupIdorg.jboss.seam/groupId
artifactIdjboss-seam/artifactId
version2.0.2.SP1/version
typeejb/type
/dependency
/dependencies
repositories
repository
idpublic-jboss/id
urlhttps://repository.jboss.org/nexus/content/groups/public-jboss//url
/repository
/repositories
/project
?xml version=1.0 encoding=UTF-8 ?
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd;
modelVersion4.0.0/modelVersion
groupIdnet.example.ear/groupId
artifactIdseam-ear-parent/artifactId
version0.0.2-SNAPSHOT/version
packagingpom/packaging
nameseam-ear-parent/name
modules
module./ear-pom.xml/module
/modules
properties
project.build.sourceEncodingUTF-8/project.build.sourceEncoding
maven.compiler.source1.6/maven.compiler.source
maven.compiler.target1.6/maven.compiler.target
ejb.ejbVersion3.0/ejb.ejbVersion
jboss.seamVersion2.0.2.SP1/jboss.seamVersion
/properties
build
pluginManagement
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-ejb-plugin/artifactId
version2.3/version
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-ear-plugin/artifactId
version2.6/version
/plugin
/plugins
/pluginManagement
/build
dependencyManagement
dependencies
dependency
groupIdorg.jboss.seam/groupId
artifactIdjboss-seam/artifactId
version${jboss.seamVersion}/version
!-- typeejb/type --
/dependency
/dependencies
/dependencyManagement
repositories
repository
idpublic-jboss/id
urlhttps://repository.jboss.org/nexus/content/groups/public-jboss//url
/repository
RE: distributionManagement
public accessible url to obtain this artifact http://maven.apache.org/pom.html#Distribution_Management Martin -- __ Jogi és Bizalmassági kinyilatkoztatás/Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Ez az üzenet bizalmas. Ha nem ön az akinek szánva volt, akkor kérjük, hogy jelentse azt nekünk vissza. Semmiféle továbbítása vagy másolatának készítése nem megengedett. Ez az üzenet csak ismeret cserét szolgál és semmiféle jogi alkalmazhatósága sincs. Mivel az electronikus üzenetek könnyen megváltoztathatóak, ezért minket semmi felelöség nem terhelhet ezen üzenet tartalma miatt. 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: Sun, 26 Jun 2011 06:25:40 -0300 Subject: Re: distributionManagement From: ald...@leal.eng.br To: users@maven.apache.org I am not sure what makepom is, so I went to google. It seems likely an Ivy Question With regards to distributionManagement: It is optional -- -- Aldrin Leal, ald...@leal.eng.br / http://www.leal.eng.br/mnemetica/ On Sun, Jun 26, 2011 at 6:03 AM, Brosh, Yossi yossi.br...@sap.com wrote: Hi to all, I would like to know if distributionManagement tag should be exist in pom.xml ? I am using makepom command - so who can I adding this distributionManagement tag to pom.xml ? Best regards, Yos
Programmatically instantiating a pom.xml as a MavenProject
Hi all, I am trying to read a pom.xml and instantiate it as a MavenProject for testing. I am able to read it using the Xpp3Reader and then I gave the Model to a MavenProject. The problem now, is that most of my attributes are not set. The most important one for me (at the moment) is the parent, which for some reason is null in the MavenProject. It is correctly set in the Model though. Do I need to instantiate the MavenProject differently or tell it to resolve all attributes or something? Current code is this: MavenXpp3Reader reader = new MavenXpp3Reader(); Model model = reader.read(pomFile); MavenProject project = new MavenProject(model); return project.getParent(); Any help is appreciated! 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: Programmatically instantiating a pom.xml as a MavenProject
Am 26.06.2011 16:07, schrieb Asmann, Roland: I am trying to read a pom.xml and instantiate it as a MavenProject for testing. You also might want to have a look at http://maven.apache.org/shared/maven-invoker/ http://maven.apache.org/plugins/maven-invoker-plugin/ http://maven.apache.org/ref/3.0.3/maven-embedder/ I use maven invoker plugin to instantiate poms for testing purposes, and it works great. Depending on your needs, maven-invoker and maven-embedder might be better for your case. AFAIK, the approach you currently follow using Xpp3Reader will give you a static XML-like model of the pom's xml text (think JAXB or JDOM), but this is far from a fully initialized maven project. Best regards Ansgar - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Programmatically instantiating a pom.xml as a MavenProject
That won't work for me, I don't want to run the whole build. I just want to have an instantiated MavenProject and call methods on it, not run the build. On 26-06-11 16:45, Ansgar Konermann wrote: Am 26.06.2011 16:07, schrieb Asmann, Roland: I am trying to read a pom.xml and instantiate it as a MavenProject for testing. You also might want to have a look at http://maven.apache.org/shared/maven-invoker/ http://maven.apache.org/plugins/maven-invoker-plugin/ http://maven.apache.org/ref/3.0.3/maven-embedder/ I use maven invoker plugin to instantiate poms for testing purposes, and it works great. Depending on your needs, maven-invoker and maven-embedder might be better for your case. AFAIK, the approach you currently follow using Xpp3Reader will give you a static XML-like model of the pom's xml text (think JAXB or JDOM), but this is far from a fully initialized maven project. Best regards Ansgar - 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
Re: Artifact[ejb:org.jboss.seam:jboss-seam] is not a dependency of the project.
Sun, 26 Jun 2011 16:00:35 +0300, /Stanimir Stamenkov/:
O.k. I've tried with my own EJB module and I've found I have to
specify typeejb/type for the dependency to get automatically
included as EJB module in the EAR. So the attached pom.xml appears
to build as expected.
However I seem to get problem when jboss-seam is declared in
dependencyManagement in a parent POM.
[...]
Specifying the jboss-seam version additionally in the EAR POM
seems to fix the things, but why one has to do it given the version
is specified in the parent POM?
So, as far as I've been able to find out, I have to declare
typeejb/type in the dependencyManagement of the parent POM and
in every child POM I refer to the given dependency. This appears
mentioned in Introduction to the Dependency Mechanism - Dependency
Management
http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Management:
NOTE: In two of these dependency references, we had to specify the
type/ element. This is because the minimal set of information for
matching a dependency reference against a dependencyManagement
section is actually {groupId, artifactId, type, classifier}...
This makes me wonder how Maven distinguish between ejb and jar
types (they are both packaged as JARs)?
--
Stanimir
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Hit java.lang.IllegalStateException with Wagon-ssh
Hi, I want to use wagon-ssh (1.0-beta-7) plugin to deploy my assembled (via assembly:assembly) application to another server using SSH. It failed with a fatal error, [INFO] [ERROR] FATAL ERROR [INFO] [INFO] The plugin descriptor for the plugin Plugin [org.apache.maven.wagon:wagon-ssh] was not found. Please verify that the plugin JAR /Users/sshark/.m2/repository/org/apache/maven/wagon/wagon-ssh/1.0-beta-7/wagon-ssh-1.0-beta-7.jar is intact. [INFO] [INFO] Trace java.lang.IllegalStateException: The plugin descriptor for the plugin Plugin [org.apache.maven.wagon:wagon-ssh] was not found. Please verify that the plugin JAR /Users/sshark/.m2/repository/org/apache/maven/wagon/wagon-ssh/1.0-beta-7/wagon-ssh-1.0-beta-7.jar is intact. My maven and OS versions are stated below. Can anyone help me as of why the wagon plug in is not intact? Does it require maven 3? Thanks Apache Maven 2.2.1 (r801777; 2009-08-07 03:16:01+0800) Java version: 1.6.0_24 Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home Default locale: en_US, platform encoding: MacRoman OS name: mac os x version: 10.6.8 arch: x86_64 Family: mac /lim/ -- View this message in context: http://maven.40175.n5.nabble.com/Hit-java-lang-IllegalStateException-with-Wagon-ssh-tp4525974p4525974.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: Hit java.lang.IllegalStateException with Wagon-ssh
Hi! maven-2.2.1 is fine. Maybe you had a download problem? Try to rm -rf /Users/sshark/.m2/repository/org/apache/maven/wagon and start your build again. LieGrue, strub --- On Sun, 6/26/11, thlim ssh...@gmail.com wrote: From: thlim ssh...@gmail.com Subject: Hit java.lang.IllegalStateException with Wagon-ssh To: users@maven.apache.org Date: Sunday, June 26, 2011, 4:13 PM Hi, I want to use wagon-ssh (1.0-beta-7) plugin to deploy my assembled (via assembly:assembly) application to another server using SSH. It failed with a fatal error, [INFO] [ERROR] FATAL ERROR [INFO] [INFO] The plugin descriptor for the plugin Plugin [org.apache.maven.wagon:wagon-ssh] was not found. Please verify that the plugin JAR /Users/sshark/.m2/repository/org/apache/maven/wagon/wagon-ssh/1.0-beta-7/wagon-ssh-1.0-beta-7.jar is intact. [INFO] [INFO] Trace java.lang.IllegalStateException: The plugin descriptor for the plugin Plugin [org.apache.maven.wagon:wagon-ssh] was not found. Please verify that the plugin JAR /Users/sshark/.m2/repository/org/apache/maven/wagon/wagon-ssh/1.0-beta-7/wagon-ssh-1.0-beta-7.jar is intact. My maven and OS versions are stated below. Can anyone help me as of why the wagon plug in is not intact? Does it require maven 3? Thanks Apache Maven 2.2.1 (r801777; 2009-08-07 03:16:01+0800) Java version: 1.6.0_24 Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home Default locale: en_US, platform encoding: MacRoman OS name: mac os x version: 10.6.8 arch: x86_64 Family: mac /lim/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: distributionManagement
He is talking about apache ivy I think http://ant.apache.org/ivy/history/2.0.0/use/makepom.html On Sun, Jun 26, 2011 at 4:25 AM, Aldrin Leal ald...@leal.eng.br wrote: I am not sure what makepom is, so I went to google. It seems likely an Ivy Question With regards to distributionManagement: It is optional -- -- Aldrin Leal, ald...@leal.eng.br / http://www.leal.eng.br/mnemetica/ On Sun, Jun 26, 2011 at 6:03 AM, Brosh, Yossi yossi.br...@sap.com wrote: Hi to all, I would like to know if distributionManagement tag should be exist in pom.xml ? I am using makepom command - so who can I adding this distributionManagement tag to pom.xml ? Best regards, Yos -- Those who do not understand Unix are condemned to reinvent it, poorly. Any sufficiently recent Microsoft OS contains an ad hoc, informally-specified, bug-ridden, slow implementation of half of Unix.
Re: Confusion with property resolution
I am suspecting that there is some plugin that is responsible for evaluating the properties and the version in use are different for the 2 cases, can some please help me identify which plugins could be responsible for it, then I can include it in the plugin management. There is no plugin, this is a core function of Maven. If the Maven versions are the same then it should generally be working the same. There are many complexities in builds and I suspect there is something else different between your modules that would explain why you are seeing this. If you can create and share a sample project that demonstrates this issue, then someone can look into it and help you understand it. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Artifact[ejb:org.jboss.seam:jboss-seam] is not a dependency of the project.
This makes me wonder how Maven distinguish between ejb and jar types (they are both packaged as JARs)? Maven only knows that one is an ejb type by you specifying typeejb/type in the dependency declaration, and by the project declaring packagingejb/packaging in their pom. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
