Skip Resources for War
Hi, I have few XML files under src/main/resources. The project packging is War. I would like to avoid these files getting into War file. I could exclude them from being part of target/classes by using resources exclude inside build tag. Any clue how to skip them for war? Well, copying them into some external resources directory would solve the purpose, however if to be done with present settings. Regards, Yuvaraj Yuvaraj Vanarase, Lead Technology - Software Phone: +91.20.40262000 Ext 2305|Mobile: +91.9850818870 | http://www.synechron.com SYNECHRON - - Top 10 Best IT Employers for 4 consecutive years (linkhttp://www.synechron.com/news/news_best_employer_sep2010.htm). - Celebrating 10 Years!
Re: Skip Resources for War
2011/7/6 Yuvaraj Vanarase yuvaraj.vanar...@synechron.com I have few XML files under src/main/resources. The project packging is War. I would like to avoid these files getting into War file. I could exclude them from being part of target/classes by using resources exclude inside build tag. Any clue how to skip them for war? Resources in src/main/resources will be put in WEB-INF/classes and they can be excluded like you did for Jar-packaged projects. Did you try it? Didn't it work? Antonio
RE: Skip Resources for War
Yeah.
I tried using:
resources
resource
directorysrc/main/resources/directory
filteringfalse/filtering
excludes
exclude**/*.*/exclude
/excludes
/resource
Under build tag. It does avoid copying files into target/classes directory,
however built War file does have them under WEB-INF/classes.
Using:
webResources
resource
directory${basedir}/src/main/resources/directory
excludes
exclude**/*.*/exclude
/excludes
/resource
/webResources
Inside War plug-in configuration doesn't help either.
Any suggestions?
Regards,
Yuvaraj
Yuvaraj Vanarase,
Lead Technology - Software
Phone: +91.20.40262000 Ext 2305|Mobile: +91.9850818870 |
http://www.synechron.com
SYNECHRON -
- Top 10 Best IT Employers for 4 consecutive years (link).
- Celebrating 10 Years!
-Original Message-
From: Antonio Petrelli [mailto:antonio.petre...@gmail.com]
Sent: Wednesday, July 06, 2011 3:26 PM
To: Maven Users List
Subject: Re: Skip Resources for War
2011/7/6 Yuvaraj Vanarase yuvaraj.vanar...@synechron.com
I have few XML files under src/main/resources. The project packging is War.
I would like to avoid these files getting into War file. I could exclude
them from being part of target/classes by using resources exclude inside
build tag.
Any clue how to skip them for war?
Resources in src/main/resources will be put in WEB-INF/classes and they can
be excluded like you did for Jar-packaged projects.
Did you try it? Didn't it work?
Antonio
RE: Skip Resources for War
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-war-plugin/artifactId
configuration
webResources
resource
!-- exclude all resources --
excludes
exclude**/*.*/exclude
/excludes
/resource
/webResources
/configuration
http://maven.apache.org/plugins/maven-war-plugin/examples/adding-filtering-webresources.html
does this not work for you?
Martin Gainty
__
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.
From: yuvaraj.vanar...@synechron.com
To: users@maven.apache.org
Date: Wed, 6 Jul 2011 06:46:41 -0500
Subject: RE: Skip Resources for War
Yeah.
I tried using:
resources
resource
directorysrc/main/resources/directory
filteringfalse/filtering
excludes
exclude**/*.*/exclude
/excludes
/resource
Under build tag. It does avoid copying files into target/classes directory,
however built War file does have them under WEB-INF/classes.
Using:
webResources
resource
directory${basedir}/src/main/resources/directory
excludes
exclude**/*.*/exclude
/excludes
/resource
/webResources
Inside War plug-in configuration doesn't help either.
Any suggestions?
Regards,
Yuvaraj
Yuvaraj Vanarase,
Lead Technology - Software
Phone: +91.20.40262000 Ext 2305|Mobile: +91.9850818870 |
http://www.synechron.com
SYNECHRON -
- Top 10 Best IT Employers for 4 consecutive years (link).
- Celebrating 10 Years!
-Original Message-
From: Antonio Petrelli [mailto:antonio.petre...@gmail.com]
Sent: Wednesday, July 06, 2011 3:26 PM
To: Maven Users List
Subject: Re: Skip Resources for War
2011/7/6 Yuvaraj Vanarase yuvaraj.vanar...@synechron.com
I have few XML files under src/main/resources. The project packging is War.
I would like to avoid these files getting into War file. I could exclude
them from being part of target/classes by using resources exclude inside
build tag.
Any clue how to skip them for war?
Resources in src/main/resources will be put in WEB-INF/classes and they can
be excluded like you did for Jar-packaged projects.
Did you try it? Didn't it work?
Antonio
Re: Skip Resources for War
did you do a mvn clean after you made the change to the pom?
On 6 July 2011 12:46, Yuvaraj Vanarase yuvaraj.vanar...@synechron.comwrote:
Yeah.
I tried using:
resources
resource
directorysrc/main/resources/directory
filteringfalse/filtering
excludes
exclude**/*.*/exclude
/excludes
/resource
Under build tag. It does avoid copying files into target/classes directory,
however built War file does have them under WEB-INF/classes.
Using:
webResources
resource
directory${basedir}/src/main/resources/directory
excludes
exclude**/*.*/exclude
/excludes
/resource
/webResources
Inside War plug-in configuration doesn't help either.
Any suggestions?
Regards,
Yuvaraj
Yuvaraj Vanarase,
Lead Technology - Software
Phone: +91.20.40262000 Ext 2305|Mobile: +91.9850818870 |
http://www.synechron.com
SYNECHRON -
- Top 10 Best IT Employers for 4 consecutive years (link).
- Celebrating 10 Years!
-Original Message-
From: Antonio Petrelli [mailto:antonio.petre...@gmail.com]
Sent: Wednesday, July 06, 2011 3:26 PM
To: Maven Users List
Subject: Re: Skip Resources for War
2011/7/6 Yuvaraj Vanarase yuvaraj.vanar...@synechron.com
I have few XML files under src/main/resources. The project packging is
War.
I would like to avoid these files getting into War file. I could exclude
them from being part of target/classes by using resources exclude
inside
build tag.
Any clue how to skip them for war?
Resources in src/main/resources will be put in WEB-INF/classes and they can
be excluded like you did for Jar-packaged projects.
Did you try it? Didn't it work?
Antonio
RE: Skip Resources for War
Well, need to add directory${basedir}/src/main/resources/directory under
resources, else it gives NullPointer.
I tried again and now its working. No clue why it wasn't working earlier.
Thanks Martin.
Regards,
Yuvaraj
Yuvaraj Vanarase,
Lead Technology - Software
Phone: +91.20.40262000 Ext 2305|Mobile: +91.9850818870
| http://www.synechron.com
SYNECHRON -
- Top 10 Best IT Employers for 4 consecutive years (link).
- Celebrating 10 Years!
-Original Message-
From: Martin Gainty [mailto:mgai...@hotmail.com]
Sent: Wednesday, July 06, 2011 5:45 PM
To: users@maven.apache.org
Subject: RE: Skip Resources for War
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-war-plugin/artifactId
configuration
webResources
resource
!-- exclude all resources --
excludes
exclude**/*.*/exclude
/excludes
/resource
/webResources
/configuration
http://maven.apache.org/plugins/maven-war-plugin/examples/adding-filtering-webresources.html
does this not work for you?
Martin Gainty
__
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.
From: yuvaraj.vanar...@synechron.com
To: users@maven.apache.org
Date: Wed, 6 Jul 2011 06:46:41 -0500
Subject: RE: Skip Resources for War
Yeah.
I tried using:
resources
resource
directorysrc/main/resources/directory
filteringfalse/filtering
excludes
exclude**/*.*/exclude
/excludes
/resource
Under build tag. It does avoid copying files into target/classes directory,
however built War file does have them under WEB-INF/classes.
Using:
webResources
resource
directory${basedir}/src/main/resources/directory
excludes
exclude**/*.*/exclude
/excludes
/resource
/webResources
Inside War plug-in configuration doesn't help either.
Any suggestions?
Regards,
Yuvaraj
Yuvaraj Vanarase,
Lead Technology - Software
Phone: +91.20.40262000 Ext 2305|Mobile: +91.9850818870 |
http://www.synechron.com
SYNECHRON -
- Top 10 Best IT Employers for 4 consecutive years (link).
- Celebrating 10 Years!
-Original Message-
From: Antonio Petrelli [mailto:antonio.petre...@gmail.com]
Sent: Wednesday, July 06, 2011 3:26 PM
To: Maven Users List
Subject: Re: Skip Resources for War
2011/7/6 Yuvaraj Vanarase yuvaraj.vanar...@synechron.com
I have few XML files under src/main/resources. The project packging is War.
I would like to avoid these files getting into War file. I could exclude
them from being part of target/classes by using resources exclude inside
build tag.
Any clue how to skip them for war?
Resources in src/main/resources will be put in WEB-INF/classes and they can
be excluded like you did for Jar-packaged projects.
Did you try it? Didn't it work?
Antonio
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Skip Resources for War
Well, copying them into some external resources directory would solve the purpose, however if to be done with present settings. I don't know why you don't just move the files to /src/external/resources or something. That seems to be the easiest solution. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Welcome Robert Scholte to the Apache Maven team!
Hi Maven folks! The Apache Maven PMC is glad to welcome Robert Scholte as new Apache Maven Committer! Most of us know Robert already from his dedicated work on lots of Maven plugins over at codehaus-mojo, so I guess I don't have to add much ;) Robert, congratulations and happy hacking! LieGrue, strub - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
axistools-maven-plugin classpath issue
Hi,
I have a situation where I have to generate wsdd
(web-service-deployment-descriptors) for a couple of projects.
I'm using the axistools-maven-plugin admin goal to accomplish this.
In order to get it to work, I find that I have to include the project
dependencies within the plugin dependencies, i.e.:
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdaxistools-maven-plugin/artifactId
executions
execution
id${project.artifactId}-gen-server-wsdd/id
goalsgoaladmin/goal/goals
configuration
configOutputDirectory${project.build.outputDirectory}/WEB-INF/configOutputDirectory
isServerConfigtrue/isServerConfig
inputFiles
include${SERVER_WSDD}/include
/inputFiles
/configuration
/execution
/executions
dependencies
dependency
groupIdaxis/groupId
artifactIdaxis/artifactId
version1.2.1/version
/dependency
dependency
LOCAL_ARTIFACT_A
/dependency
/dependencies
/plugin
Not sure why the LOCAL_ARTIFACT dependencies have to appear within
the plugin deps, and this may be the source of the problem.
Rest assured that it is not declared there, the plugin does not use
the project dependencies (as I think it should), and so the task
fails with missing class errors.
The above works fine when I build locally.
However, when I add a second use of the plugin in a different pom,
but in the same reactor, the classpath from the first instance is
used and the wsdd generation fails.
As a work-around, I have included both LOCAL_ARTIFACT dependencies in
the plugin declaration, so no matter which one gets called first, it
will have a full classpath that will work for either project. If I
added a third project, I would have to keep doing this.
Not the most desirable situation.
So my question is, is this a maven classloading issue, or a plugin
issue? Has anyone else encountered this sticky classpath issue
with other plugins?
mvn --version
Apache Maven 2.2.1 (r801777; 2009-08-06 12:16:01-0700)
Java version: 1.5.0_24
Java home: /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home
Default locale: en_US, platform encoding: MacRoman
OS name: mac os x version: 10.6.6 arch: i386 Family: unix
tia,
-Russ
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Welcome Robert Scholte to the Apache Maven team!
Welcome Robert! On 6 July 2011 20:40, Mark Struberg strub...@yahoo.de wrote: Hi Maven folks! The Apache Maven PMC is glad to welcome Robert Scholte as new Apache Maven Committer! Most of us know Robert already from his dedicated work on lots of Maven plugins over at codehaus-mojo, so I guess I don't have to add much ;) Robert, congratulations and happy hacking! LieGrue, strub - 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: Welcome Robert Scholte to the Apache Maven team!
Nice to see here Robert ! 2011/7/6 Mark Struberg strub...@yahoo.de: Hi Maven folks! The Apache Maven PMC is glad to welcome Robert Scholte as new Apache Maven Committer! Most of us know Robert already from his dedicated work on lots of Maven plugins over at codehaus-mojo, so I guess I don't have to add much ;) Robert, congratulations and happy hacking! LieGrue, strub - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy http://twitter.com/olamy | http://www.linkedin.com/in/olamy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Referencing modules in a sibling folder
Hello, I'm very new to Maven. I'm trying to convert my company's build environment from a proprietary configuration to Maven's. We components that are dependent on one another and they lie in sibling folders. e.g. We may have components ./myComponents/A ./myComponents/B ./myComponents/C ./myComponents/D Let's suppose component A depends on B and C. Component B depends on D. And Component C depends on D. A couple of questions: 1) How do I reference component D from B? In the examples, it seems that the folder of component D has to be within the folder of component B. But component B is also a module for component C so I don't want to move it underneath B. 2) What should the packaging value of B be? Should it be pom since it refers to submodule D? Or should it be a jar since it contains its own classes and is referenced by A? Thanks in advance, Kane -- View this message in context: http://maven.40175.n5.nabble.com/Referencing-modules-in-a-sibling-folder-tp4559091p4559091.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: Referencing modules in a sibling folder
Dependency does not imply folder structure. Just the opposite. If each of these projects builds a jar, each is has the default packaging (jar). You indicate dependency by adding a dependency element to the pom. You probably want a pom in the myComponents dir that has packagingpom/packaging and lists all the subdirs as modules. On Wed, Jul 6, 2011 at 6:05 PM, kanesee kane...@gmail.com wrote: Hello, I'm very new to Maven. I'm trying to convert my company's build environment from a proprietary configuration to Maven's. We components that are dependent on one another and they lie in sibling folders. e.g. We may have components ./myComponents/A ./myComponents/B ./myComponents/C ./myComponents/D Let's suppose component A depends on B and C. Component B depends on D. And Component C depends on D. A couple of questions: 1) How do I reference component D from B? In the examples, it seems that the folder of component D has to be within the folder of component B. But component B is also a module for component C so I don't want to move it underneath B. 2) What should the packaging value of B be? Should it be pom since it refers to submodule D? Or should it be a jar since it contains its own classes and is referenced by A? Thanks in advance, Kane -- View this message in context: http://maven.40175.n5.nabble.com/Referencing-modules-in-a-sibling-folder-tp4559091p4559091.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 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Referencing modules in a sibling folder
I thought the dependency section was just for artifacts that are located in the repository. For artifacts that consist of my own code, aren't those modules? I may be confusing the two. Our code base actually contains several different products, so I don't think it makes sense to have one pom that lists all of the subdirs as modules. My understanding is that I would have a pom-package for each of our products, which references only the subdirs (modules or dependencies) that it needed. Is my understanding correct? -- View this message in context: http://maven.40175.n5.nabble.com/Referencing-modules-in-a-sibling-folder-tp4559091p4559177.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: Referencing modules in a sibling folder
Dependencies are also used for interdependencies of your components.
It's common to see
dependencygroupIdmy.group.id/groupId
artifactIdmy.sibling/artifactId
version${project.version}/version
/dependency
modules are only used in a project of packaging 'pom' to tell Maven to
include a collection of other projects into the reactor. Those
projects are ordinary and relate to each other via dependencies.
On Wed, Jul 6, 2011 at 6:37 PM, kanesee kane...@gmail.com wrote:
I thought the dependency section was just for artifacts that are located in
the repository.
For artifacts that consist of my own code, aren't those modules? I may be
confusing the two.
Our code base actually contains several different products, so I don't think
it makes sense to have one pom that lists all of the subdirs as modules. My
understanding is that I would have a pom-package for each of our products,
which references only the subdirs (modules or dependencies) that it needed.
Is my understanding correct?
--
View this message in context:
http://maven.40175.n5.nabble.com/Referencing-modules-in-a-sibling-folder-tp4559091p4559177.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
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Referencing modules in a sibling folder
You will generally find it helpful to grab a look at some significant open source project that addresses some of what you are looking to do. Have, for example, a look at cxf.apache.org. On Wed, Jul 6, 2011 at 6:37 PM, kanesee kane...@gmail.com wrote: I thought the dependency section was just for artifacts that are located in the repository. For artifacts that consist of my own code, aren't those modules? I may be confusing the two. Our code base actually contains several different products, so I don't think it makes sense to have one pom that lists all of the subdirs as modules. My understanding is that I would have a pom-package for each of our products, which references only the subdirs (modules or dependencies) that it needed. Is my understanding correct? -- View this message in context: http://maven.40175.n5.nabble.com/Referencing-modules-in-a-sibling-folder-tp4559091p4559177.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 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Referencing modules in a sibling folder
I tried using dependency but I'm getting a similar error, that it can't find
the artifact.
{
ERROR] Failed to execute goal on project developmentenvironment: Could not
resolve dependencies for project
com.inferlink.entitybase:developmentenvironment:jar:1.0-SNAPSHOT: Could not
find artifact com.inferlink.entitybase:bootstrap:jar:1.0-SNAPSHOT - [Help
1]
}
Here's part of my pom for the dependency:
{
...
modelVersion4.0.0/modelVersion
groupIdcom.inferlink.entitybase/groupId
artifactIdbootstrap/artifactId
packagingjar/packaging
version1.0-SNAPSHOT/version
namebootstrap/name
...
}
How does Maven know where to look for this other artifact? I thought all
dependencies come from the repository (I'm just pointing to the default
central repository).
Do I need to upload/publish my artifact before it can be used as a
dependency by others?
If so, do I need to set up my own repository proxy (Nexus?) to do so?
--
View this message in context:
http://maven.40175.n5.nabble.com/Referencing-modules-in-a-sibling-folder-tp4559091p4559280.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: Referencing modules in a sibling folder
The modules are not more than a maven project and as such they build to an artifact that can be in your local machine repository or in a remote repository like maven central. You can reference them by using the dependency tag as Benson said. If you have have a multi-module project like it seems to be the case you usually do something like: mvn clean install and it will put the artifacts in your local repository for maven use. If you haven't already you might want to create a parent pom that agregates the build. The maven reactor will find the right order to build them. If you do not have a parent pom then you will have to build each project and run 'mvn clean install' On Wed, Jul 6, 2011 at 5:55 PM, Benson Margulies bimargul...@gmail.comwrote: You will generally find it helpful to grab a look at some significant open source project that addresses some of what you are looking to do. Have, for example, a look at cxf.apache.org. On Wed, Jul 6, 2011 at 6:37 PM, kanesee kane...@gmail.com wrote: I thought the dependency section was just for artifacts that are located in the repository. For artifacts that consist of my own code, aren't those modules? I may be confusing the two. Our code base actually contains several different products, so I don't think it makes sense to have one pom that lists all of the subdirs as modules. My understanding is that I would have a pom-package for each of our products, which references only the subdirs (modules or dependencies) that it needed. Is my understanding correct? -- View this message in context: http://maven.40175.n5.nabble.com/Referencing-modules-in-a-sibling-folder-tp4559091p4559177.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 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- 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: Referencing modules in a sibling folder
Ah thanks. I forgot the mvn install part of it, which I guess makes it available in the repository for other artifacts to use. I just did a mvn compile on the dependency component. I've got different errors now--a sign of progress. Thanks guys, Kane -- View this message in context: http://maven.40175.n5.nabble.com/Referencing-modules-in-a-sibling-folder-tp4559091p4559294.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
Setting up internal repository
Hi folks, I have been researching options for setting up internal maven repository - free software. Based on my research it seems like nexus is most recommended choice. Wondering if people here have any opinions/suggestions. Ours is a small setup with less than 20 developers. Ideally we would like to share servers for multiple tasks and would prefer if we can put behind apache. We have limited/slow network bandwidth and is one of the important reasons for setting up the repository. Other reasons such as using same versions of dependencies etc are of course valid reasons. Regards, Niranjan - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Setting up internal repository
On Thu, Jul 7, 2011 at 12:59 PM, Niranjan Rao nhr...@gmail.com wrote: Hi folks, I have been researching options for setting up internal maven repository - free software. Based on my research it seems like nexus is most recommended choice. Wondering if people here have any opinions/suggestions. Nexus Open Source works (http://nexus.sonatype.org/download-nexus.html) Archiva works (http://archiva.apache.org/) Both are open source projects. You'd have to check out the features sets to compare, but I suspect if you picked either you wouldn't have a problem. Ours is a small setup with less than 20 developers. Ideally we would like to share servers for multiple tasks and would prefer if we can put behind apache. These tend to be standalone instances, its not something you need to put behind apache. Why do you want to share servers? One repository manager instance is plenty. Once the repo manager has downloaded the artifact it doesn't do much but serve it out again, once each developer has a local copy the repo manager doesn't do anything but idle. We have limited/slow network bandwidth and is one of the important reasons for setting up the repository. This is a good reason, speed of downloading is better since its all local network traffic. Other reasons such as using same versions of dependencies etc are of course valid reasons. You dont get this from a repo manager. You get this from maven and locking down versions in your poms and using enforcer and enable the convergence rule http://maven.apache.org/enforcer/enforcer-rules/dependencyConvergence.html If you want to have a repo manager that contains only sanctioned artifacts I think you are need to buy Nexus Pro. I dont know if Archiva has this feature. Or you need to manually work this process somehow. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Setting up internal repository
Barrie, Thanks for the quick reply. When I said shared server, I meant that we want to have multiple applications on the same server - repository application will be one of them. I don't know what we will be putting on this server, yet, but one thing is for sure, it has to multi task. Based on what you said, it seems to be possible. Other information was very helpful. thanks for the help, Niranjan On Thu, 2011-07-07 at 13:16 +0930, Barrie Treloar wrote: On Thu, Jul 7, 2011 at 12:59 PM, Niranjan Rao nhr...@gmail.com wrote: Hi folks, I have been researching options for setting up internal maven repository - free software. Based on my research it seems like nexus is most recommended choice. Wondering if people here have any opinions/suggestions. Nexus Open Source works (http://nexus.sonatype.org/download-nexus.html) Archiva works (http://archiva.apache.org/) Both are open source projects. You'd have to check out the features sets to compare, but I suspect if you picked either you wouldn't have a problem. Ours is a small setup with less than 20 developers. Ideally we would like to share servers for multiple tasks and would prefer if we can put behind apache. These tend to be standalone instances, its not something you need to put behind apache. Why do you want to share servers? One repository manager instance is plenty. Once the repo manager has downloaded the artifact it doesn't do much but serve it out again, once each developer has a local copy the repo manager doesn't do anything but idle. We have limited/slow network bandwidth and is one of the important reasons for setting up the repository. This is a good reason, speed of downloading is better since its all local network traffic. Other reasons such as using same versions of dependencies etc are of course valid reasons. You dont get this from a repo manager. You get this from maven and locking down versions in your poms and using enforcer and enable the convergence rule http://maven.apache.org/enforcer/enforcer-rules/dependencyConvergence.html If you want to have a repo manager that contains only sanctioned artifacts I think you are need to buy Nexus Pro. I dont know if Archiva has this feature. Or you need to manually work this process somehow. - 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: Setting up internal repository
Here, we often install nexus under a standard tomcat install, and it just works, sometimes sharing with Jenkins. Seems not to be a problem, compared to other heavy-weights like the ones from a major Java Tools supplier I wouldn't dare to name here, which end up needing to use a full, stand-alone install for each instance. -- -- Aldrin Leal, ald...@leal.eng.br / http://www.leal.eng.br/mnemetica/ On Thu, Jul 7, 2011 at 1:15 AM, Niranjan Rao nhr...@gmail.com wrote: Barrie, Thanks for the quick reply. When I said shared server, I meant that we want to have multiple applications on the same server - repository application will be one of them. I don't know what we will be putting on this server, yet, but one thing is for sure, it has to multi task. Based on what you said, it seems to be possible. Other information was very helpful. thanks for the help, Niranjan On Thu, 2011-07-07 at 13:16 +0930, Barrie Treloar wrote: On Thu, Jul 7, 2011 at 12:59 PM, Niranjan Rao nhr...@gmail.com wrote: Hi folks, I have been researching options for setting up internal maven repository - free software. Based on my research it seems like nexus is most recommended choice. Wondering if people here have any opinions/suggestions. Nexus Open Source works (http://nexus.sonatype.org/download-nexus.html ) Archiva works (http://archiva.apache.org/) Both are open source projects. You'd have to check out the features sets to compare, but I suspect if you picked either you wouldn't have a problem. Ours is a small setup with less than 20 developers. Ideally we would like to share servers for multiple tasks and would prefer if we can put behind apache. These tend to be standalone instances, its not something you need to put behind apache. Why do you want to share servers? One repository manager instance is plenty. Once the repo manager has downloaded the artifact it doesn't do much but serve it out again, once each developer has a local copy the repo manager doesn't do anything but idle. We have limited/slow network bandwidth and is one of the important reasons for setting up the repository. This is a good reason, speed of downloading is better since its all local network traffic. Other reasons such as using same versions of dependencies etc are of course valid reasons. You dont get this from a repo manager. You get this from maven and locking down versions in your poms and using enforcer and enable the convergence rule http://maven.apache.org/enforcer/enforcer-rules/dependencyConvergence.html If you want to have a repo manager that contains only sanctioned artifacts I think you are need to buy Nexus Pro. I dont know if Archiva has this feature. Or you need to manually work this process somehow. - 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
