Re: How to use ${project.build.directory}?
I second Wendy's or Michael's suggestions - avoid system scope at all costs.
Moreover, it may be removed in future versions of Maven, so don't depend on
it being there forever. May as well make preperations now :)
--
Eric Redmond
http://blog.propellors.net
On 7/30/07, Wendy Smoak [EMAIL PROTECTED] wrote:
On 7/20/07, Tawfik, Sameh E [EMAIL PROTECTED] wrote:
Hi,
I'm using the following code:
dependency
groupIdconnector/groupId
artifactIdconnector/artifactId
version1_0/version
scopesystem/scope
systemPath${Build_base}/ma-jdm-tck/lib/connector_1_0.jar/systemPath
/dependency
This code is working fine, but it requires everyone to define the
Build_base system variable, so is there is another way, where I can
reference the folder where this jar is located without using a system
variable?
I would have the developers use 'mvn install:install-file' to add the
jar to their local repository, and then you can declare it as a normal
dependency.
--
Wendy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to use ${project.build.directory}?
When we run maven JUnits - and ensure that testing is successful. - run mvn test but its through out exception and looks like it did not run properly JUnit in project. How the first step to check where is error in configuration / setting sof maven and fix this error thanks, DT www.ejinz.com Search Shopping - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to use ${project.build.directory}?
On 7/20/07, Tawfik, Sameh E [EMAIL PROTECTED] wrote:
Hi,
I'm using the following code:
dependency
groupIdconnector/groupId
artifactIdconnector/artifactId
version1_0/version
scopesystem/scope
systemPath${Build_base}/ma-jdm-tck/lib/connector_1_0.jar/systemPath
/dependency
This code is working fine, but it requires everyone to define the
Build_base system variable, so is there is another way, where I can
reference the folder where this jar is located without using a system
variable?
I would have the developers use 'mvn install:install-file' to add the
jar to their local repository, and then you can declare it as a normal
dependency.
--
Wendy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: How to use ${project.build.directory}?
Hi,
I have also have some Failed to validate POM warning on a dependency from a
project of mine. When I run mvn validate on this particular dependency, it's ok
so I'm still wondering why such warnings.
does anyone has solved this issue ? (its not so big deal but it produces a lot
of warning trace which makes maven execution trace hard to read).
Can this issue be solved by using an inhouse repository ?
-Message d'origine-
De : Tawfik, Sameh E [mailto:[EMAIL PROTECTED]
Envoyé : mardi 24 juillet 2007 21:12
À : Maven Users List
Objet : RE: How to use ${project.build.directory}?
Hi Michael,
Thanks for the information, I tried this approach and it worked, and
even though the jdm.interfaces module was built correctly with no errors
or warnings, when I tried to build another module that depends on the
jdm.interfaces module, it generated the following warning:
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[WARNING] POM for 'com.mbpa:jdm-interfaces:pom:2.0:compile' is invalid.
It will be ignored for artifact resolution. Reason: Failed to validate
POM
So, probably your second suggestion would work better, by using an
in-house repository.
Thanks,
Sameh
-Original Message-
From: Michael Meyer [mailto:[EMAIL PROTECTED]
Sent: Saturday, July 21, 2007 1:51 AM
To: Maven Users List
Subject: Re: How to use ${project.build.directory}?
Hi,
yes you can use maven properties. This should do what you want:
dependency
groupIdconnector/groupId
artifactIdconnector/artifactId
version1_0/version
scopesystem/scope
systemPath${basedir}/../ma-jdm-tck/lib/connector_1_0.jar/systemPath
/dependency
But please don't do it! If you use a continuus integration tool like
continuum or hudson they will try to build your modules individually.
This will not work if you have this kind of dependencies between your
modules. So if I where you I would really go for an inhouse repository
(It's only a webserver like apache after all). You can then deploy your
3rd party jars once to this repository with 'mvn deploy:deploy-file'. In
my opinion a much nicer solution :-)
Cheers, michael
Tawfik, Sameh E schrieb:
Hi,
I'm using the following code:
dependency
groupIdconnector/groupId
artifactIdconnector/artifactId
version1_0/version
scopesystem/scope
systemPath${Build_base}/ma-jdm-tck/lib/connector_1_0.jar/systemPath
/dependency
This code is working fine, but it requires everyone to define the
Build_base system variable, so is there is another way, where I can
reference the folder where this jar is located without using a system
variable?
For example, can I use something like ${project.build.directory}?
I've a parent folder Project where all the build modules are under
it
as sub projects, so it would be nice to be able to reference the
parent
folder, and then point to any needed third party jar file in any one
of
the subfolders.
I know I can also use mvn install:install-file -DgroupId=connector
-DartifactId=connector -Dversion=1_0 -Dpackaging=jar
-Dfile=/path/to/file
But, it would be nice to just reference specific files by pointing at
them using their path, so does Maven support this feature?
Thanks,
Sameh
This email and any files transmitted with it are confidential,
proprietary
and intended solely for the individual or entity to whom they are
addressed.
If you have received this email in error please delete it immediately.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
This email and any files transmitted with it are confidential, proprietary
and intended solely for the individual or entity to whom they are addressed.
If you have received this email in error please delete it immediately.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: How to use ${project.build.directory}?
Hi Michael,
Thanks for the information, I tried this approach and it worked, and
even though the jdm.interfaces module was built correctly with no errors
or warnings, when I tried to build another module that depends on the
jdm.interfaces module, it generated the following warning:
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[WARNING] POM for 'com.mbpa:jdm-interfaces:pom:2.0:compile' is invalid.
It will be ignored for artifact resolution. Reason: Failed to validate
POM
So, probably your second suggestion would work better, by using an
in-house repository.
Thanks,
Sameh
-Original Message-
From: Michael Meyer [mailto:[EMAIL PROTECTED]
Sent: Saturday, July 21, 2007 1:51 AM
To: Maven Users List
Subject: Re: How to use ${project.build.directory}?
Hi,
yes you can use maven properties. This should do what you want:
dependency
groupIdconnector/groupId
artifactIdconnector/artifactId
version1_0/version
scopesystem/scope
systemPath${basedir}/../ma-jdm-tck/lib/connector_1_0.jar/systemPath
/dependency
But please don't do it! If you use a continuus integration tool like
continuum or hudson they will try to build your modules individually.
This will not work if you have this kind of dependencies between your
modules. So if I where you I would really go for an inhouse repository
(It's only a webserver like apache after all). You can then deploy your
3rd party jars once to this repository with 'mvn deploy:deploy-file'. In
my opinion a much nicer solution :-)
Cheers, michael
Tawfik, Sameh E schrieb:
Hi,
I'm using the following code:
dependency
groupIdconnector/groupId
artifactIdconnector/artifactId
version1_0/version
scopesystem/scope
systemPath${Build_base}/ma-jdm-tck/lib/connector_1_0.jar/systemPath
/dependency
This code is working fine, but it requires everyone to define the
Build_base system variable, so is there is another way, where I can
reference the folder where this jar is located without using a system
variable?
For example, can I use something like ${project.build.directory}?
I've a parent folder Project where all the build modules are under
it
as sub projects, so it would be nice to be able to reference the
parent
folder, and then point to any needed third party jar file in any one
of
the subfolders.
I know I can also use mvn install:install-file -DgroupId=connector
-DartifactId=connector -Dversion=1_0 -Dpackaging=jar
-Dfile=/path/to/file
But, it would be nice to just reference specific files by pointing at
them using their path, so does Maven support this feature?
Thanks,
Sameh
This email and any files transmitted with it are confidential,
proprietary
and intended solely for the individual or entity to whom they are
addressed.
If you have received this email in error please delete it immediately.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
This email and any files transmitted with it are confidential, proprietary
and intended solely for the individual or entity to whom they are addressed.
If you have received this email in error please delete it immediately.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to use ${project.build.directory}?
Hi,
yes you can use maven properties. This should do what you want:
dependency
groupIdconnector/groupId
artifactIdconnector/artifactId
version1_0/version
scopesystem/scope
systemPath${basedir}/../ma-jdm-tck/lib/connector_1_0.jar/systemPath
/dependency
But please don't do it! If you use a continuus integration tool like continuum or hudson they will try to build your modules individually. This will not work if you have this kind of dependencies
between your modules. So if where you I would really go for an inhouse repository (It's only a webserver like apache after all). You can then deploy your 3rd party jars once to this repository with
'mvn deploy:deploy-file'. In my opinion a much nicer solution :-)
Cheers, michael
Tawfik, Sameh E schrieb:
Hi,
I'm using the following code:
dependency
groupIdconnector/groupId
artifactIdconnector/artifactId
version1_0/version
scopesystem/scope
systemPath${Build_base}/ma-jdm-tck/lib/connector_1_0.jar/systemPath
/dependency
This code is working fine, but it requires everyone to define the
Build_base system variable, so is there is another way, where I can
reference the folder where this jar is located without using a system
variable?
For example, can I use something like ${project.build.directory}?
I've a parent folder Project where all the build modules are under it
as sub projects, so it would be nice to be able to reference the parent
folder, and then point to any needed third party jar file in any one of
the subfolders.
I know I can also use mvn install:install-file -DgroupId=connector
-DartifactId=connector -Dversion=1_0 -Dpackaging=jar
-Dfile=/path/to/file
But, it would be nice to just reference specific files by pointing at
them using their path, so does Maven support this feature?
Thanks,
Sameh
This email and any files transmitted with it are confidential, proprietary
and intended solely for the individual or entity to whom they are addressed.
If you have received this email in error please delete it immediately.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: How to use ${project.build.directory}?
Hi,
I'm using the following code:
dependency
groupIdconnector/groupId
artifactIdconnector/artifactId
version1_0/version
scopesystem/scope
systemPath${Build_base}/ma-jdm-tck/lib/connector_1_0.jar/systemPath
/dependency
This code is working fine, but it requires everyone to define the
Build_base system variable, so is there is another way, where I can
reference the folder where this jar is located without using a system
variable?
For example, can I use something like ${project.build.directory}?
I've a parent folder Project where all the build modules are under it
as sub projects, so it would be nice to be able to reference the parent
folder, and then point to any needed third party jar file in any one of
the subfolders.
I know I can also use mvn install:install-file -DgroupId=connector
-DartifactId=connector -Dversion=1_0 -Dpackaging=jar
-Dfile=/path/to/file
But, it would be nice to just reference specific files by pointing at
them using their path, so does Maven support this feature?
Thanks,
Sameh
This email and any files transmitted with it are confidential, proprietary
and intended solely for the individual or entity to whom they are addressed.
If you have received this email in error please delete it immediately.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
