how to organize profiles for test-environment?
Hi, for the definiton of our test-environment the integration-tests need to run on, I´m thinking about using profiles. What is best practice to organize the test-environment in profiles? - defining a parent pom.xml containing all profiles makes the build dependant on that environment - if environment will change, all modules need to be changed - defining the profiles in each pom.xml of each integration-test module will blew up the pom.xml code and result in a lot of redundant information. - defining the profiles in a profiles.xml is an option, but how to share that profiles.xml among all projects? I couldn´t find an option to define an alternate profiles.xml location. Is the global settings.xml the solution for that? But how do I handle branches and parallel releases, working with the same Maven version than? Another profile for each release? mvn clean install -Pdb2,testsystem1,v181 ? Thanx for some best practice hints, torsten
maven hanging
I am running my install script during pre-integration-test And after my install script is done, as prints out its Install Complete message, maven hangs... I'm using a wrapper and calling sudo so that the install runs as root. I've commited out the call to my install and maven stops hanging. So, there is something about my install script that is causing maven to hang even though the install script exits. I've had tried using maven-exec plugin and ant-exec and they both do the same thing.. D/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven 3 warning on dependency scope import?
Hi, I just checked the documentation, import scope in to be used in the depMgmt section. See http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Scope *import* *(only available in Maven 2.0.9 or later)* This scope is only used on a dependency of type pom in the dependencyManagement section. It indicates that the specified POM should be replaced with the dependencies in that POM's dependencyManagementsection. Since they are replaced, dependencies with a scope of import do not actually participate in limiting the transitivity of a dependency. Cheers 2010/1/25 gabe97330 gabe97...@gmail.com The Sonatype blog republished a tip from October 2009 in their best of series (see http://www.sonatype.com/people/2009/10/maven-tips-and-tricks-grouping-dependencies/ ) that didn't use scope import for specifying a POM dependency. I tried this with 3.0 and it works and avoids the warning (see below). The confusing thing is that the Maven documentation indicates that scope=import should be used for POM dependencies (see http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Scope ). Is this a case of using POM dependencies in dependencyManagement vs build? gabe97330 wrote: I'm using maven 3.0-alpha-3 and getting a warning on use of dependencies of scope import in sub-modules although everything works as it did in 2.x. there a way to address this warning either through correcting my usage (assuming it is a valid warning) or some sort of pragma to turn off the warning? Thanks, Gabe - Blog: Gabe's Groove Twitter: Gabe97330 - Blog: http://gabe97330.begeddov.com Gabe's Groove Twitter: http://twitter.com/gabe97330 Gabe97330 -- View this message in context: http://old.nabble.com/maven-3-warning-on-dependency-scope-import--tp26385938p27308001.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 -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
Re: Shade Plugin: How to include artifacts and all their dependencies?
Hi, Which configuration do you use? Have you read the documentation? Could you provide a simple example/illustration of your problem? Cheers 2010/1/22 Peter Niederwieser pnied...@gmail.com I'd like to include a specific set of artifacts and all their transitive dependencies. However, includes only includes the artifacts themselves, but not their dependencies. Is there a way to achieve my goal? Cheers, Peter -- View this message in context: http://old.nabble.com/Shade-Plugin%3A-How-to-include-artifacts-and-all-their-dependencies--tp27279215p27279215.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 -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
RE: Resource Filter files
Thanks Manuel!!
-Original Message-
From: Manuel Grau [mailto:mang...@gmail.com]
Sent: Monday, January 25, 2010 2:09 PM
To: Maven Users List
Subject: Re: Resource Filter files
Yes, is possible, I did it in my work recently. But, there is a better way.
Notice what I'm doing. I have 4 profiles, activated with a var called env. So,
when I call maven I always do:
mvn -Denv=pre compile (or anything)
I have four files called ${env}.pom.properties. So, you can put this in your
main build tag:
filters
filter${env}.pom.properties/filter
filters
So, when activate pre profile, the properties file loaded is pre.pom.properties.
El 25/01/2010, a las 21:01, david.a.willi...@sungard.com escribió:
Is it possible to define filters by profile? See below for example.
build
...
filters
filter [a filter property] /filter
/filters
...
/build
Thanks,
David
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Dependency plugin strange behavior
Hi there,
I'm facing a strange behavior with the dependency plugin. Here is my
configuration
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-dependency-plugin/artifactId
version2.1/version
executions
execution
idcopy-dependencies/id
phaseprocess-sources/phase
goals
goalcopy-dependencies/goal
/goals
configuration
outputDirectory${basedir}/target/site/demo/outputDirectory
overWriteReleasesfalse/overWriteReleases
overWriteSnapshotstrue/overWriteSnapshots
overWriteIfNewertrue/overWriteIfNewer
excludeTransitivetrue/excludeTransitive
/configuration
/execution
execution
idunpack/id
phaseprocess-sources/phase
goals
goalunpack/goal
/goals
configuration
artifactItems
artifactItem
groupIdnet.sourceforge.floggy/groupId
artifactIdfloggy-persistence-weaver/artifactId
outputDirectory${basedir}/target/site/outputDirectory
includesschema/*/includes
/artifactItem
/artifactItems
/configuration
/execution
/executions
/plugin
For the copy-dependencies execution it works fine but for the unpack
execution it claims that cannot revolve the dependency
net.sourceforge.floggy:floggy-persistence-weaver BUT this dependency is
declared at dependencies section and it is a sibling project of the current
one in a multi module project. The only difference that I can observe is
that in one execution (unpack ID) I made an explicit reference to the
dependency.
Any clue why? Any workaround?
Thanks
Thiago Moreira
Re: Dependency plugin strange behavior
On Tue, Jan 26, 2010 at 9:29 AM, Thiago Moreira (timba) tmoreira2...@gmail.com wrote: For the copy-dependencies execution it works fine but for the unpack execution it claims that cannot revolve the dependency net.sourceforge.floggy:floggy-persistence-weaver BUT this dependency is declared at dependencies section and it is a sibling project of the current one in a multi module project. The only difference that I can observe is that in one execution (unpack ID) I made an explicit reference to the dependency. Any clue why? Any workaround? What command are you executing, and in what directory/at what level in the project? -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Resource Filter files
You're welcome!!
2010/1/26 david.a.willi...@sungard.com
Thanks Manuel!!
-Original Message-
From: Manuel Grau [mailto:mang...@gmail.com]
Sent: Monday, January 25, 2010 2:09 PM
To: Maven Users List
Subject: Re: Resource Filter files
Yes, is possible, I did it in my work recently. But, there is a better way.
Notice what I'm doing. I have 4 profiles, activated with a var called env.
So, when I call maven I always do:
mvn -Denv=pre compile (or anything)
I have four files called ${env}.pom.properties. So, you can put this in
your main build tag:
filters
filter${env}.pom.properties/filter
filters
So, when activate pre profile, the properties file loaded is
pre.pom.properties.
El 25/01/2010, a las 21:01, david.a.willi...@sungard.com escribió:
Is it possible to define filters by profile? See below for example.
build
...
filters
filter [a filter property] /filter
/filters
...
/build
Thanks,
David
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Everything should be made as simple as possible, but not simpler Albert
Einstein
Re: Dependency plugin strange behavior
dependency:unpack works on artifacts that are not produced as part of your
build and are not listed as dependencies, as a result you must specify the
full GAV coordinates to resolve the artifact, and if you are foolish enough
to use it for an artifact that is produced as part of the same build that
your project is part of, then you will not be able to release that
multi-module project with the maven-release-plugin.
dependency:unpack-dependencies works on artifacts that are produced in the
reactor (i.e. all the projects in the multi-module build that your project
is part of).
This same pairing exists with dependency:copy vs
dependency:copy-dependencies
-Stephen
2010/1/26 Thiago Moreira (timba) tmoreira2...@gmail.com
Hi there,
I'm facing a strange behavior with the dependency plugin. Here is my
configuration
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-dependency-plugin/artifactId
version2.1/version
executions
execution
idcopy-dependencies/id
phaseprocess-sources/phase
goals
goalcopy-dependencies/goal
/goals
configuration
outputDirectory${basedir}/target/site/demo/outputDirectory
overWriteReleasesfalse/overWriteReleases
overWriteSnapshotstrue/overWriteSnapshots
overWriteIfNewertrue/overWriteIfNewer
excludeTransitivetrue/excludeTransitive
/configuration
/execution
execution
idunpack/id
phaseprocess-sources/phase
goals
goalunpack/goal
/goals
configuration
artifactItems
artifactItem
groupIdnet.sourceforge.floggy/groupId
artifactIdfloggy-persistence-weaver/artifactId
outputDirectory${basedir}/target/site/outputDirectory
includesschema/*/includes
/artifactItem
/artifactItems
/configuration
/execution
/executions
/plugin
For the copy-dependencies execution it works fine but for the unpack
execution it claims that cannot revolve the dependency
net.sourceforge.floggy:floggy-persistence-weaver BUT this dependency is
declared at dependencies section and it is a sibling project of the current
one in a multi module project. The only difference that I can observe is
that in one execution (unpack ID) I made an explicit reference to the
dependency.
Any clue why? Any workaround?
Thanks
Thiago Moreira
Re: Customizing maven site
The next question is that it appears when mvn site is running that maven is trying to build the source code. Is it possible to build the site without maven attempting to build the source? Thanks for your help, jay -- View this message in context: http://old.nabble.com/Customizing-maven-site-tp27249142p27327121.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: Customizing maven site
On 2010-01-26 19:08, jaybytez wrote: The next question is that it appears when mvn site is running that maven is trying to build the source code. Is it possible to build the site without maven attempting to build the source? If you run this command instead, it will build only the site and nothing else. This will mean that you might loose some of the reports though. mvn site:site Thanks for your help, jay -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Customizing maven site
Awesome...thanks for the clarification. Again...I building mvn site for COBOL code... hahahahawho knows what kinda sites I will build. jay Dennis Lundberg-2 wrote: On 2010-01-26 19:08, jaybytez wrote: The next question is that it appears when mvn site is running that maven is trying to build the source code. Is it possible to build the site without maven attempting to build the source? If you run this command instead, it will build only the site and nothing else. This will mean that you might loose some of the reports though. mvn site:site Thanks for your help, jay -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- View this message in context: http://old.nabble.com/Customizing-maven-site-tp27249142p27328076.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
Maven dependency tracker…
I wrote this little plugin at work. Some of you might be interested so here you go: http://sam.leberrigaud.org/2010/01/maven-dependency-heaven.html I could summarise what the plugin does by Know your dependencies at all time SaM - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Dependency plugin strange behavior
Hi Stephen,
Thank you for the explanation. The documentation is not clear about which
dependency the plugin will work on (from the repository or produced by the
build). For those of you interested in the configuration that fixed my issue
here it go:
execution
idcopy-dependencies/id
phaseprocess-sources/phase
goals
goalcopy-dependencies/goal
/goals
configuration
excludeArtifactIdsfloggy-persistence-weaver/excludeArtifactIds
outputDirectory${basedir}/target/site/demo/outputDirectory
overWriteReleasesfalse/overWriteReleases
overWriteSnapshotstrue/overWriteSnapshots
overWriteIfNewertrue/overWriteIfNewer
excludeTransitivetrue/excludeTransitive
/configuration
/execution
execution
idunpack/id
phaseprocess-sources/phase
goals
goalunpack-dependencies/goal
/goals
configuration
includeArtifactIdsfloggy-persistence-weaver/includeArtifactIds
outputDirectory${basedir}/target/site/outputDirectory
includesschema/*/includes
/configuration
/execution
Thanks!
Thiago Moreira
On Tue, Jan 26, 2010 at 3:18 PM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
dependency:unpack works on artifacts that are not produced as part of your
build and are not listed as dependencies, as a result you must specify the
full GAV coordinates to resolve the artifact, and if you are foolish enough
to use it for an artifact that is produced as part of the same build that
your project is part of, then you will not be able to release that
multi-module project with the maven-release-plugin.
dependency:unpack-dependencies works on artifacts that are produced in the
reactor (i.e. all the projects in the multi-module build that your project
is part of).
This same pairing exists with dependency:copy vs
dependency:copy-dependencies
-Stephen
2010/1/26 Thiago Moreira (timba) tmoreira2...@gmail.com
Hi there,
I'm facing a strange behavior with the dependency plugin. Here is my
configuration
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-dependency-plugin/artifactId
version2.1/version
executions
execution
idcopy-dependencies/id
phaseprocess-sources/phase
goals
goalcopy-dependencies/goal
/goals
configuration
outputDirectory${basedir}/target/site/demo/outputDirectory
overWriteReleasesfalse/overWriteReleases
overWriteSnapshotstrue/overWriteSnapshots
overWriteIfNewertrue/overWriteIfNewer
excludeTransitivetrue/excludeTransitive
/configuration
/execution
execution
idunpack/id
phaseprocess-sources/phase
goals
goalunpack/goal
/goals
configuration
artifactItems
artifactItem
groupIdnet.sourceforge.floggy/groupId
artifactIdfloggy-persistence-weaver/artifactId
outputDirectory${basedir}/target/site/outputDirectory
includesschema/*/includes
/artifactItem
/artifactItems
/configuration
/execution
/executions
/plugin
For the copy-dependencies execution it works fine but for the unpack
execution it claims that cannot revolve the dependency
net.sourceforge.floggy:floggy-persistence-weaver BUT this dependency is
declared at dependencies section and it is a sibling project of the
current
one in a multi module project. The only difference that I can observe is
that in one execution (unpack ID) I made an explicit reference to the
dependency.
Any clue why? Any workaround?
Thanks
Thiago Moreira
[ANN] Release Maven Findbugs plugin version 2.3.1
The Findbugs Maven plugin team is pleased to announce the release of version 2.3.1 FindBugs uses static analysis to inspect Java bytecode for occurrences of bug patterns. You can see more about the plugin at: http://mojo.codehaus.org/findbugs-maven-plugin/ You can find release notes for this version below, or at: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11701version=16025 Release Notes - Maven 2.x FindBugs Plugin - Version 2.3.1 ** Bug * [MFINDBUGS-102] - When including tests Findbugs needs test classpath not compile classpath * [MFINDBUGS-105] - No default locale * [MFINDBUGS-106] - Bugs with an Experimental category aren't reported correctly in 2.2+ versions of the reporting plugin * [MFINDBUGS-107] - Invalid XML report: the node BugInstance should be a child of file Enjoy,
How to locate the plugin at execute time
Hello, I package my plugin to include all the native files (ie dll), at runtime, I will need to locate the plugin it self and extract the native stuff out. What is the conventional way to locate the plugin? Thanks -Dan - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
maven release plugin branch and merge question
Hi, I am using the following steps to release projects using maven release plugin - 1)create a branch from trunk using maven release plugin 2)development/testing in branch 3)release the project using maven release plugin 4)merge the changes from the branch back to trunk using svn Now the question is after step 4, the SCM connection details in trunk has been overwritten with the branch URLs, I have to then fix them and commit back into trunk manually, which sometime is annoying, is this what I am supposed to do or I am missing anything? Thanks for your help. -- View this message in context: http://old.nabble.com/maven-release-plugin-branch-and-merge-question-tp2784p2784.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: How to locate the plugin at execute time
ummm, i totally forgot the plugin is in the classpath :-) sorry for the noice -Dan On Tue, Jan 26, 2010 at 6:44 PM, Dan Tran dant...@gmail.com wrote: Hello, I package my plugin to include all the native files (ie dll), at runtime, I will need to locate the plugin it self and extract the native stuff out. What is the conventional way to locate the plugin? Thanks -Dan - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
maven in ecipse
Hi, I have a project that I've loaded into eclipse. Under windows, I already have M2_Home as env variable pointing to project directory Description Resource Path Location Type Unbound classpath variable: 'M2_REPO/junit/junit/3.8.1/junit-3.8.1.jar' in project 'jung-api' jung-api Build path Build Path Problem Do I need to set something in eclipse? Thanks Brian - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: failsafe-maven-plugin configuration issues
I did this earlier using maven build helper plugin and adding additional source
directories, so that compiler plugin gets those during test-compile phase.
Simple examples can be found under build helper plugin site.
Subir
-Original Message-
From: Adam Retter [mailto:adam.ret...@googlemail.com]
Sent: Monday, January 25, 2010 7:14 PM
To: Stephen Connolly
Cc: Maven Users List
Subject: Re: failsafe-maven-plugin configuration issues
I tried to add a second compile phase but this didnt seem to help -
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
configuration
source1.6/source
target1.6/target
/configuration
executions
execution
idcompile-it/id
phasepre-integration-test/phase
goals
goalcompile/goal
/goals
configuration
includes
include${basedir}/src/systest/java/**/*.java/include
/includes
/configuration
/execution
/executions
/plugin
Any chance, you could explain to me a simple pom.xml where I have my Unit tests
and Integration tests separated?
2010/1/25 Stephen Connolly stephen.alan.conno...@gmail.com:
failsafe surefire do not compile the classes. m-compiler-p is
responsible for compiling the classes
2010/1/25 Adam Retter adam.ret...@googlemail.com
Just wondering how they compile when I change the inclusion to
*/*.java for the failsafe plugin?
Is there some better way of doing this whilst keeping the Unit Tests
and Integration Tests in separate folders?
2010/1/25 Stephen Connolly stephen.alan.conno...@gmail.com:
you are failing to also compile your integration tests you'd
need a second execution of compiler:testCompile
2010/1/25 Adam Retter adam.ret...@googlemail.com
I have both Unit tests and Integration tests in my project and was
attempting to manage this with the Surefire plugin in this way -
http://weblogs.java.net/blog/johnsmart/archive/2008/06/unit_tests_
are.html
But I ran into problems -
http://markmail.org/search/?q=list%3Aorg.apache.maven.users#query:
list%3Aorg.apache.maven.users+page:4+mid:om7z6osunu5pz4gm+state:re
sults
It was recommended that I switch to the failsafe-maven-plugin for
managing my integration tests and as such I modified my project
layout so it looks like this -
src/main/java
src/main/resources
src/test/java
src/test/resources
src/systest/java
src/systest/resources
So the idea is that I keep my tests in src/test and my integration
tests in src/systest. I added the following to my pom.xml -
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdfailsafe-maven-plugin/artifactId
!-- version2.4.3-alpha-1/version --
configuration
testSourceDirectory${basedir}/src/systest/java/testSourceDirect
ory
includes
include*.java/include
/includes
/configuration
executions
execution
idintegration-test/id
phaseintegration-test/phase
goals
goalintegration-test/goal
/goals
/execution
execution
idverify/id
phaseverify/phase
goals
goalverify/goal
/goals
/execution
/executions
/plugin
But only the unit tests are run in the test goal and no
integration tests are found or run during the integration-test goal.
If I change the inclusion to **/*.java, then the problem is that
the unit tests are run during the test goal and the unit tests and
integration tests are mixed up and run together during the
integration-test goal. The idea is that the integration-test goal
should just run the integration tests (obviously after running the
unit tests as part of the test goal).
So what am I doing wrong here?
--
Adam Retter
skype :adam.retter
http://www.adamretter.org.uk
--
Adam Retter
skype :adam.retter
http://www.adamretter.org.uk
--
Adam Retter
skype :adam.retter
http://www.adamretter.org.uk
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Please do not print this email unless it is absolutely necessary.
The information contained in this electronic message and any attachments to
this message are intended for the exclusive use of the addressee(s) and may
contain proprietary,
Re: maven in ecipse
Hi Brian,
as I understand the problem, yes, you have to define a classpath variable
for this in Eclipse: Window\Preferences\Java\Build Path\Classpath Variables
- the name of the variable should be M2_REPO and should point to the Local
Maven Repository (not to the maven home) - by default it is at
${user.home}/.m2/repository.
Best regards,
Balazs
2010/1/27 brian brw...@gmail.com
Hi,
I have a project that I've loaded into eclipse.
Under windows, I already have M2_Home as env variable pointing to project
directory
Description Resource Path Location Type
Unbound classpath variable: 'M2_REPO/junit/junit/3.8.1/junit-3.8.1.jar' in
project 'jung-api' jung-api Build path Build Path Problem
Do I need to set something in eclipse?
Thanks
Brian
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: maven in ecipse
You should also try using eclipse plugin for maven
To name
- m2eclipse
Regards,
Vijay Shanker Dubey
On Wed, Jan 27, 2010 at 1:11 PM, Balazs Tothfalussy
balazs.tothfalu...@gmail.com wrote:
Hi Brian,
as I understand the problem, yes, you have to define a classpath variable
for this in Eclipse: Window\Preferences\Java\Build Path\Classpath Variables
- the name of the variable should be M2_REPO and should point to the Local
Maven Repository (not to the maven home) - by default it is at
${user.home}/.m2/repository.
Best regards,
Balazs
2010/1/27 brian brw...@gmail.com
Hi,
I have a project that I've loaded into eclipse.
Under windows, I already have M2_Home as env variable pointing to project
directory
Description Resource Path Location Type
Unbound classpath variable: 'M2_REPO/junit/junit/3.8.1/junit-3.8.1.jar'
in
project 'jung-api' jung-api Build path Build Path Problem
Do I need to set something in eclipse?
Thanks
Brian
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Configure External Repository Credentials in POM
How can you set external repository credentials in the POM file? I know that you can create a settings.xml file with values below, but how can I configure a POM file with username/password. I looked at http://maven.apache.org/maven-v4_0_0.xsd and I don't see a username and password. ?xml version=1.0? settings profiles profile idexample.archiva/id activation activeByDefaulttrue/activeByDefault /activation repositories repository idexample.internal/id nameExample's Repository/name urlhttp://maven-secure.example.com/archiva/repository/example.internal/url /repository /repositories pluginRepositories pluginRepository idexample.internal/id nameexample's Repository/name urlhttp://maven-secure.example.com/archiva/repository/example.internal/url /pluginRepository /pluginRepositories /profile /profiles servers server idexample.internal/id usernameusername/username passwordp...@s$w0rd/password /server /servers /settings Brig Lamoreaux This message is private and confidential. If you have received it in error, please notify the sender and remove it from your system.
Adding archetype to internal catalogue?
Hi, I'm rather new to maven so sorry if I'm asking nonsense. Basically I would like to know if it is possible to add archetypes to the internal catalogue, and if yes, how? We have a framework [1] that would benefit quite a bit from having a maven archetype accessible in a simple fashion, just as it is possible for many others at the moment. I remember having read something about archetype repositories on the maven documentation pages just last week, yet I can't find it back now. From what I understood things changed quite a bit recently in regard to artifact repositories (and hence I assume also in regard to archetype repositories). Thanks, Manuel [1] http://www.makumba.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Dependencies in multi-module project
Hello. Say, I have two projects: A and B. I always want them to be compiled and deployed in one time and I decided to use multi-module project: In the upper directory I've created pom.xml with the following content: modules moduleA/module moduleB/module /modules And it works fine. But module B depends on module A. When I do some changes in A and run mvn compile on the top level, I want both modules to be recompiled and module B should be compiled with newly compiled A. How can I do it? If I simply add dependency in module B's pom.xml -- it will use A from repository, and if I did not do mvn deploy there would not be one! Of course I can add system dependency to module B and hardcode path to module A (like ../A/target/classes) but that's an ugly hack. What is the best way to do that? Thanks. WBR, Ilya Kazakevich - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: maven in ecipse
I gotta admit, m2eclipse works like a charm!
Except that you may need to be awared of the 'shared target folder'
issue.
--
Best Regards,
AdRiAN ShUM
-Original Message-
From: vijay shanker [mailto:vijay.s...@gmail.com]
Sent: Wednesday, January 27, 2010 3:45 PM
To: Maven Users List
Subject: Re: maven in ecipse
You should also try using eclipse plugin for maven
To name
- m2eclipse
Regards,
Vijay Shanker Dubey
On Wed, Jan 27, 2010 at 1:11 PM, Balazs Tothfalussy
balazs.tothfalu...@gmail.com wrote:
Hi Brian,
as I understand the problem, yes, you have to define a classpath
variable for this in Eclipse: Window\Preferences\Java\Build
Path\Classpath Variables
- the name of the variable should be M2_REPO and should point to the
Local
Maven Repository (not to the maven home) - by default it is at
${user.home}/.m2/repository.
Best regards,
Balazs
2010/1/27 brian brw...@gmail.com
Hi,
I have a project that I've loaded into eclipse.
Under windows, I already have M2_Home as env variable pointing to
project directory
Description Resource Path Location Type
Unbound classpath variable:
'M2_REPO/junit/junit/3.8.1/junit-3.8.1.jar'
in
project 'jung-api' jung-api Build path Build Path Problem
Do I need to set something in eclipse?
Thanks
Brian
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
This email is confidential. If you are not the intended recipient, please
delete it from your system and notify the sender immediately. Any unauthorized
use, disclosure, dissemination or copying of this email is prohibited. Taifook
Securities Group, its group companies and their content providers (Parties)
shall not be responsible for the accuracy or completeness of this email or its
attachment, if any, which could contain virus, be corrupted, destroyed,
incomplete, intercepted, lost or arrive late. The Parties do not accept
liability for any damage caused by this email.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
