heap size for unit tests
Hello, is it possible to increase the heap size for maven especially for the unit tests? --- regards Martin Ritz BTC AG - Unit Softwaredevelopment mailto:[EMAIL PROTECTED]
WG: Continuum 1.1 @ Tomcat 6
Hi Continuum user group, I want to install continuum in my existing Tomcat 6 Server. I followed the instructions on Guide to Install Continuum on Tomcat (http://maven.apache.org/continuum/docs/1.1/installation/tomcat.html). I created an context.xml and added the libraries. But I get still this error: WARN org.apache.commons.configuration.JNDIConfiguration - Internal error javax.naming.NameNotFoundException: Name java:comp is not bound in this Context I can't get my continuum running at the tomcat due to this error. Can anybody help my with this issue? What I have to change/ add? --- rgds Martin Ritz BTC AG - Unit Softwaredevelopment mailto:[EMAIL PROTECTED]
AW: Continuum 1.1 @ Tomcat 6
I followed exactly this instructions but it doesn't work. Martin -Ursprüngliche Nachricht- Von: SlinnHawkins, Jon (ELS-CAM) [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 6. Februar 2008 13:21 An: [EMAIL PROTECTED] Betreff: RE: Continuum 1.1 @ Tomcat 6 Hi Martin I successfully installed by following the instructions on : http://docs.codehaus.org/display/MAVENUSER/Archiva+on+Tomcat HTH Jon -Original Message- From: Ritz, Martin [mailto:[EMAIL PROTECTED] Sent: 06 February 2008 12:15 To: [EMAIL PROTECTED] Subject: WG: Continuum 1.1 @ Tomcat 6 Hi Continuum user group, I want to install continuum in my existing Tomcat 6 Server. I followed the instructions on Guide to Install Continuum on Tomcat (http://maven.apache.org/continuum/docs/1.1/installation/tomcat.html). I created an context.xml and added the libraries. But I get still this error: WARN org.apache.commons.configuration.JNDIConfiguration - Internal error javax.naming.NameNotFoundException: Name java:comp is not bound in this Context I can't get my continuum running at the tomcat due to this error. Can anybody help my with this issue? What I have to change/ add? --- rgds Martin Ritz BTC AG - Unit Softwaredevelopment mailto:[EMAIL PROTECTED] This email is from Elsevier Limited, a company registered in England and Wales with company number 1982084, whose registered office is The Boulevard, Langford Lane, Kidlington, Oxford, OX5 1GB, United Kingdom.
parent inheritence (site plugin)
Hi User Group, I have a project with some submodules and generating the site of the whole project through executing of the parents level. I want to display the parent in the left navigation bar. I found the only way is to do this is the element menu ref=parent inherit=bottom/ in the parent which is inheritanced through the childs. This works only for the goal site:stage but not for my normal goal site site:deploy. I don't want to stage the site. My goal (site site:deploy) works fine unless the parent link in the sidebar. I tried out with some versions (last one: 2.0-beta-7-20071130.000106-1) but there is no difference. Is there another way of creating a link in the childs site to the parent site? Why is site:stage the only goal which works for me? --- rgds Martin Ritz BTC AG - Unit Softwaredevelopment mailto:[EMAIL PROTECTED]
parent inheritence (site plugin)
Hi User Group, I have a project with some submodules and generating the site of the whole project through executing of the parents level. I want to display the parent in the left navigation bar. I found the only way is to do this is the element menu ref=parent inherit=bottom/ in the parent which is inheritanced through the childs. This works only for the goal site:stage but not for my normal goal site site:deploy. I don't want to stage the site. My goal (site site:deploy) works fine unless the parent link in the sidebar. I tried out with some versions (last one: 2.0-beta-7-20071130.000106-1) but there is no difference. Is there another way of creating a link in the childs site to the parent site? Why is site:stage the only goal which works for me? --- rgds Martin Ritz BTC AG - Unit Softwaredevelopment mailto:[EMAIL PROTECTED]
Possibility to bundle a maven project with third party dependencies for transportation
Hello, i have a multimodule project and i search for a way to make the whole project portable. I have many third party dependencies in my locale repository which arent available in the remote repository. So i need a way to identify all dependencies in a project and bundle them in an archive or so to build my project offline at another place. Can somebody help me or give me a hint in which way i can solve my problem? Thx. --- kindly regards Martin Ritz BTC AG - Unit Softwaredevelopment mailto:[EMAIL PROTECTED]
AW: Possibility to bundle a maven project with third party dependencies for transportation
I want to bundle only the third party dependencies. All other available dependencies via maven remote repository shouldn't go into these bundle. Martin You can use dependency:go-offline and then zip up your ~/.m2 directory along with the source directory. Other than this, I do not know of any built-in way to bundle Maven projects with dependencies etc. Wayne On 1/3/08, Ritz, Martin [EMAIL PROTECTED] wrote: Hello, i have a multimodule project and i search for a way to make the whole project portable. I have many third party dependencies in my locale repository which arent available in the remote repository. So i need a way to identify all dependencies in a project and bundle them in an archive or so to build my project offline at another place. Can somebody help me or give me a hint in which way i can solve my problem? Thx. --- kindly regards Martin Ritz BTC AG - Unit Softwaredevelopment mailto:[EMAIL PROTECTED] - 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]
Directory naming in working-directory
Hi Continuum Users, i've a problem with the continuum 1.1. The import and build of my projects works. But one thing I can't get: why takes Continuum not the origin name of the directory to checkout (SVN) and build in the working directory. In my case Continuum takes numbers for the name of the directories. To navigate in these cryptical directories is very confussing. Is there a possibility to take the directories as they are? THX --- kindly regards Martin Ritz BTC AG - Unit Softwaredevelopment mailto:[EMAIL PROTECTED]
how to override artifacts in repository while deploy
Hi, I want to override the existend (in the repository) files when i deploy an artifact. I dont want to have different ones with buildnumber. Is there a way to do this? Thx Martin
how to specify the name of assembled distribution file
Hi, i want to specify the name of one of three triggered assembly descriptors. I have three different assemblies to build and the name of one should be templates.zip instead of test-0.8.7-SNAPSHOT-templates.zip If i declare the name with the finalName i define the element of all assemblies. Is there a way to declare the finalName in the assembly-descriptor? I dont want to use an extra profile. assembly-plugin in my pom ... plugin artifactIdmaven-assembly-plugin/artifactId executions execution goals goalattached/goal /goals /execution /executions configuration descriptors descriptorsrc\main\assembly\a.xml/descriptor descriptorsrc\main\assembly\b.xml/descriptor descriptorsrc\main\assembly\c.xml/descriptor /descriptors /configuration /plugin ... __ regards Martin Ritz
AW: how to specify the name of assembled distribution file
thx for the quick response but i get an error if i split like you told me. Error: the system couln't find the assembly descriptor file... But i have declared the right path and filename and the files are existing. Any hint what i'am doing wrong? Martin Hi, split the plugin configuration in distinct executions: plugin artifactIdmaven-assembly-plugin/artifactId executions execution idexecution-one/id goals goalattached/goal /goals configuration finalNamecustomName/finalName appendAssemblyIdfalse/appendAssemblyId descriptorsrc\main\assembly\a.xml/descriptor /configuration /execution execution idexecution-two/id goals goalattached/goal /goals configuration descriptors descriptorsrc\main\assembly\b.xml/descriptor descriptorsrc\main\assembly\c.xml/descriptor /descriptors /configuration /execution /executions /plugin -Tim Ritz, Martin schrieb: Hi, i want to specify the name of one of three triggered assembly descriptors. I have three different assemblies to build and the name of one should be templates.zip instead of test-0.8.7-SNAPSHOT-templates.zip If i declare the name with the finalName i define the element of all assemblies. Is there a way to declare the finalName in the assembly-descriptor? I dont want to use an extra profile. assembly-plugin in my pom ... plugin artifactIdmaven-assembly-plugin/artifactId executions execution goals goalattached/goal /goals /execution /executions configuration descriptors descriptorsrc\main\assembly\a.xml/descriptor descriptorsrc\main\assembly\b.xml/descriptor descriptorsrc\main\assembly\c.xml/descriptor /descriptors /configuration /plugin ... __ regards Martin Ritz - 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]
AW: AW: how to specify the name of assembled distribution file
) at org.apache.maven.plugin.assembly.io.DefaultAssemblyReader.getAssemblyFromDescriptorFile(DefaultAssemblyReader.java:169) ... 20 more What could be the reason for this error? Thx Martin -Ursprüngliche Nachricht- Von: Tim Kettler [mailto:[EMAIL PROTECTED] Gesendet: Montag, 24. September 2007 12:40 An: Maven Users List Betreff: Re: AW: how to specify the name of assembled distribution file It's working for me with this testproject: . |-- pom.xml `-- src `-- main |-- assembly | |-- A.xml | |-- B.xml | `-- C.xml `-- java `-- TestClass.java pom.xml: project modelVersion4.0.0/modelVersion groupIdmy-test-group/groupId artifactIdmy-test-artifact/artifactId version1.0-SNAPSHOT/version build plugins plugin artifactIdmaven-assembly-plugin/artifactId version2.2-beta-1/version executions execution idexecution-one/id phasepackage/phase goals goalsingle/goal /goals configuration finalNameCUSTOM/finalName appendAssemblyIdfalse/appendAssemblyId descriptors descriptorsrc/main/assembly/A.xml/descriptor /descriptors /configuration /execution execution idexecution-two/id phasepackage/phase goals goalsingle/goal /goals configuration descriptors descriptorsrc/main/assembly/B.xml/descriptor descriptorsrc/main/assembly/C.xml/descriptor /descriptors /configuration /execution /executions /plugin /plugins /build /project The only difference is that I used the 'single' goal instead of the 'attached' one and I changed the lone descriptor/ tag to be in a descriptors/ list as well (I just noticed that the lone descriptor tag will be depricated). If you can't get it working just post the relevant ouptut of 'mvn -X ...' and hopefully we can figure it out together. -Tim Ritz, Martin schrieb: thx for the quick response but i get an error if i split like you told me. Error: the system couln't find the assembly descriptor file... But i have declared the right path and filename and the files are existing. Any hint what i'am doing wrong? Martin Hi, split the plugin configuration in distinct executions: plugin artifactIdmaven-assembly-plugin/artifactId executions execution idexecution-one/id goals goalattached/goal /goals configuration finalNamecustomName/finalName appendAssemblyIdfalse/appendAssemblyId descriptorsrc\main\assembly\a.xml/descriptor /configuration /execution execution idexecution-two/id goals goalattached/goal /goals configuration descriptors descriptorsrc\main\assembly\b.xml/descriptor descriptorsrc\main\assembly\c.xml/descriptor /descriptors /configuration /execution /executions /plugin -Tim Ritz, Martin schrieb: Hi, i want to specify the name of one of three triggered assembly descriptors. I have three different assemblies to build and the name of one should be templates.zip instead of test-0.8.7-SNAPSHOT-templates.zip If i declare the name with the finalName i define the element of all assemblies. Is there a way to declare the finalName in the assembly-descriptor? I dont want to use an extra profile. assembly-plugin in my pom ... plugin artifactIdmaven-assembly-plugin/artifactId executions execution goals goalattached/goal /goals /execution /executions configuration descriptors descriptorsrc\main\assembly\a.xml/descriptor descriptorsrc\main\assembly\b.xml/descriptor descriptorsrc\main\assembly\c.xml/descriptor /descriptors /configuration /plugin ... __ regards Martin Ritz - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED
Way to distribute zip and sources
Hi, what is the easiest way to share artifacts like Zips, and SourceArchives with maven 2? Are there some plugins to handle and provide nightlybuilds on a central place? --- regards Martin Ritz
AW: Way to distribute zip and sources
I have setted up my maven infrastructure with nightlybuilds via Continuum Server. Now I want to provide the artifacts built by continuum (e.g. zips, sources, other archives, .exe, ...) in an flat hierarchy where my team members could easily find and download the artifacts. It should looks like for example http://people.apache.org/builds/james/nightly/ . Im on search for an maven plugin or an continuum extension which could handle the distribution of such directorys. So in this directories only the specific artifacts should be available and not the temporary build files or so on. Some hints/ recommendations would be very helpfull for me. Thx Martin -Ursprüngliche Nachricht- Von: Wayne Fay [mailto:[EMAIL PROTECTED] Gesendet: Montag, 24. September 2007 16:09 An: Maven Users List Betreff: Re: Way to distribute zip and sources Provide more details about your use case and perhaps someone can help. Wayne On 9/24/07, Ritz, Martin [EMAIL PROTECTED] wrote: Hi, what is the easiest way to share artifacts like Zips, and SourceArchives with maven 2? Are there some plugins to handle and provide nightlybuilds on a central place? --- regards Martin Ritz - 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]
Plugin Binding
Hi, is there a way to bind a plugin execution to a other plugin mojo call? I want to bind the webstart plugin execution to the assembly:single mojo. So everytime i execute the assembly plugin the webstart would be also started and I can pack the webstart artifacts in an zip file. I don't want to bind both to a phase because i don't want to execute the assembly in every build. Martin
Re: Re: Maven Antrun Plugin - specific target call
Indeed, Dave is right.
I use the ant plugin only to perform tasks maven could'nt fulfill.
Main works is done by maven but some things I couldn't find ways to perform
with maven.
In my project I have integrated the izpack plugin with ant.
I don't want to execute this task in every build.
The next would be a deploy to the SAP Web Application Server for which I found
only a way with ant.
So this tasks should be executed for different builds and I don't want to
execute this both togetheter in one build.
Profiles would be an option but it's not a really smart way... (because I have
some profiles yet - i dont want to confuse my users to much)
The best way in my opinion would by (like Dave posted) mvn install
-DantTarget=targetToCall or something similar.
So it would be self explanatory and good to remind.
On 9/11/07, Wayne Fay [EMAIL PROTECTED] wrote:
I would just move those targets out to a build.xml file so you
can call them directly with Ant. Then set Maven up so it calls
the targets in the build.xml file rather than embedding the Ant stuff
in your pom.
I use already this way like this:
configuration
tasks
ant antfile = ${basedir}/src/main/scripts/build.xml
target name = copy_resources/
target name = community_build/
target name = custom_build/
target name = inhouse_build/
/ant
/tasks
/configuration
Here i define different targets in the buildscript but I'm not able to call a
specific one so if i run the ant-plugin i have to perform all targets which i
declared.
Martin (OP)
Until the OP responds, we'll never know the answer. We're
both making assumptions here.
Wayne
On 9/11/07, Dave Feltenberger [EMAIL PROTECTED] wrote:
Because ant can inherit the classpaths/dependencies. Presumably he
*is* utilizing the lifecycle, and attaching this ant config
to one of
the phases, but has a need to call specific ant tasks only
sometimes.
Was there something I missed that made you think he was
calling maven
only to call ant, and that he had no interest in utlizing the
lifecycle? I assumed this was a somewhat special case and that it
wasn't just using Maven to wrap an ant build process - that
I agree would be silly.
On 9/11/07, Wayne Fay [EMAIL PROTECTED] wrote:
That just sounds more complicated than it needs to be.
Calling Maven
just so it will call Ant for me is too indirect when I
can just call
Ant directly, right? What's the advantage when it works fine with
ant target and I have no interest in utilizing the Maven
lifecycle for this particular Ant target/call?
Wayne
On 9/11/07, Dave Feltenberger [EMAIL PROTECTED] wrote:
Can't you just pass in a -D argument and execute the argument
that's
passed
in?
e.g.
mvn install -DantTarget=targetToCall
then in the antrun execution:
ant
antfile=src/main/ant-builds/buildJnlps.xml
target=${antTarget} /
On 9/11/07, Wayne Fay [EMAIL PROTECTED] wrote:
I would just move those targets out to a build.xml
file so you
can call them directly with Ant. Then set Maven up so
it calls
the targets in the build.xml file rather than
embedding the Ant stuff in your pom.
Wayne
On 9/11/07, Ritz, Martin [EMAIL PROTECTED] wrote:
I have already two profiles...
I dont want to blow up my pom too much!
Is there no other easier way to call specific targets?
Martin
Profiles will solve your problem.
Wayne
On 9/11/07, Ritz, Martin [EMAIL PROTECTED] wrote:
Hi,
I have some ant targets integrated in my pom.xml.
I declared an ant build script which is therefor called
from
maven.
Now I dont want to perform every ant target on
every build.
Is there a way to call only specific
ant-targets from the
command line (maybe by calling the target or the id)?
---
kind regards
Martin Ritz
BTC AG - Unit Software Engineering
mailto:[EMAIL PROTECTED]
-
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]
- To unsubscribe, e-mail:
[EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
- To unsubscribe, e-mail: [EMAIL PROTECTED
Re: Re: Maven Antrun Plugin - specific target call
You are right the difference is not too big.
The members of my project team used ant for many years so they are used to say
ant which target to call.
And the pom would be much bigger to set up with profiles (only for the
ant-plugin) for every different build.
Martin
Ritz, Martin schrieb:
Indeed, Dave is right.
I use the ant plugin only to perform tasks maven could'nt fulfill.
Main works is done by maven but some things I couldn't find
ways to perform with maven.
In my project I have integrated the izpack plugin with ant.
I don't want to execute this task in every build.
The next would be a deploy to the SAP Web Application
Server for which I found only a way with ant.
So this tasks should be executed for different builds and I
don't want to execute this both togetheter in one build.
Profiles would be an option but it's not a really smart way...
(because I have some profiles yet - i dont want to confuse
my users to
much)
The best way in my opinion would by (like Dave posted) mvn
install -DantTarget=targetToCall or something similar.
So it would be self explanatory and good to remind.
Why would this be more self explanatory than 'mvn
-Pgenerate_izpack install' for example?
-Tim
On 9/11/07, Wayne Fay [EMAIL PROTECTED] wrote:
I would just move those targets out to a build.xml file so you
can call them directly with Ant. Then set Maven up so it calls
the targets in the build.xml file rather than
embedding the Ant stuff in your pom.
I use already this way like this:
configuration
tasks
ant antfile = ${basedir}/src/main/scripts/build.xml
target name = copy_resources/
target name = community_build/
target name = custom_build/
target name = inhouse_build/
/ant
/tasks
/configuration
Here i define different targets in the buildscript but I'm
not able to call a specific one so if i run the ant-plugin i
have to perform all targets which i declared.
Martin (OP)
Until the OP responds, we'll never know the answer. We're
both making
assumptions here.
Wayne
On 9/11/07, Dave Feltenberger [EMAIL PROTECTED] wrote:
Because ant can inherit the classpaths/dependencies.
Presumably he
*is* utilizing the lifecycle, and attaching this ant config
to one of
the phases, but has a need to call specific ant tasks only
sometimes.
Was there something I missed that made you think he was
calling maven
only to call ant, and that he had no interest in utlizing the
lifecycle? I assumed this was a somewhat special case
and that it
wasn't just using Maven to wrap an ant build process - that
I agree would be silly.
On 9/11/07, Wayne Fay [EMAIL PROTECTED] wrote:
That just sounds more complicated than it needs to be.
Calling Maven
just so it will call Ant for me is too indirect when I
can just call
Ant directly, right? What's the advantage when it works
fine with
ant target and I have no interest in utilizing the Maven
lifecycle for this particular Ant target/call?
Wayne
On 9/11/07, Dave Feltenberger
[EMAIL PROTECTED] wrote:
Can't you just pass in a -D argument and execute the argument
that's
passed
in?
e.g.
mvn install -DantTarget=targetToCall
then in the antrun execution:
ant
antfile=src/main/ant-builds/buildJnlps.xml
target=${antTarget} /
On 9/11/07, Wayne Fay [EMAIL PROTECTED] wrote:
I would just move those targets out to a build.xml
file so you
can call them directly with Ant. Then set Maven up so
it calls
the targets in the build.xml file rather than
embedding the Ant stuff in your pom.
Wayne
On 9/11/07, Ritz, Martin [EMAIL PROTECTED] wrote:
I have already two profiles...
I dont want to blow up my pom too much!
Is there no other easier way to call specific targets?
Martin
Profiles will solve your problem.
Wayne
On 9/11/07, Ritz, Martin [EMAIL PROTECTED] wrote:
Hi,
I have some ant targets integrated in my pom.xml.
I declared an ant build script which is therefor called from
maven.
Now I dont want to perform every ant target on
every build.
Is there a way to call only specific
ant-targets from the
command line (maybe by calling the target or the id)?
---
kind regards
Martin Ritz
BTC AG - Unit Software Engineering
mailto:[EMAIL PROTECTED]
-
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]
- To unsubscribe, e-mail:
[EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED
Maven Antrun Plugin - specific target call
Hi, I have some ant targets integrated in my pom.xml. I declared an ant build script which is therefor called from maven. Now I dont want to perform every ant target on every build. Is there a way to call only specific ant-targets from the command line (maybe by calling the target or the id)? --- kind regards Martin Ritz BTC AG - Unit Software Engineering mailto:[EMAIL PROTECTED]
Re: Re: Maven Antrun Plugin - specific target call
I have already two profiles... I dont want to blow up my pom too much! Is there no other easier way to call specific targets? Martin Profiles will solve your problem. Wayne On 9/11/07, Ritz, Martin [EMAIL PROTECTED] wrote: Hi, I have some ant targets integrated in my pom.xml. I declared an ant build script which is therefor called from maven. Now I dont want to perform every ant target on every build. Is there a way to call only specific ant-targets from the command line (maybe by calling the target or the id)? --- kind regards Martin Ritz BTC AG - Unit Software Engineering mailto:[EMAIL PROTECTED] - 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]
AW: Question how to prevent maven from update manually added dependencies (detailed descr)
Hallo, thx for the quick answer. Here a bit longer description: I have some dependencies which I added manually to my local repo because they are not available in the remote repository. Now everytime I build my project maven tries to update this dependency which is not availble in the remote repo. command line output: Downloading: http://commons.ucalgary.ca/pub/m2/***/***/***/1.0/***-1.0.pom Downloading: http://repo1.maven.org/maven2/***/***/***/1.0/***-1.0.pom This job is not necessary and costs time... so I want to prevent it. How can I force Maven to skip this check because I know for sure this dependency isn't in the remote repo. Martin Its not clear what you are trying to do and why. Please explain things better. In the meantime, you can use mvn -o ... for offline mode which will force Maven to use only the artifacts available on your machine for a given build. Wayne On 9/7/07, Ritz, Martin [EMAIL PROTECTED] wrote: Ho Maven Users, I searched a lot around but couldn't find the answer to my question: How can I prevent maven from update manually added dependencies? Scope provided and system doesn't match my requirements - is there a way of doing in a other way? Thx alot --- Martin Ritz BTC AG - Geschäftseinheit Softwarelösungen mailto:[EMAIL PROTECTED] - 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]
AW: Question how to prevent maven from update manually added dependencies (detailed descr)
It doesn't work. Another idea? Martin You can try setting the version in your dependency declaration to [1.0] which will lock down the version, and then Maven should realize that you already have those artifacts in your local repo cache, and it doesn't need to run out and look for updates. Wayne On 9/10/07, Ritz, Martin [EMAIL PROTECTED] wrote: Hallo, thx for the quick answer. Here a bit longer description: I have some dependencies which I added manually to my local repo because they are not available in the remote repository. Now everytime I build my project maven tries to update this dependency which is not availble in the remote repo. command line output: -- -- Downloading: http://commons.ucalgary.ca/pub/m2/***/***/***/1.0/***-1.0.pom Downloading: http://repo1.maven.org/maven2/***/***/***/1.0/***-1.0.pom -- -- This job is not necessary and costs time... so I want to prevent it. How can I force Maven to skip this check because I know for sure this dependency isn't in the remote repo. Martin __ __ Its not clear what you are trying to do and why. Please explain things better. In the meantime, you can use mvn -o ... for offline mode which will force Maven to use only the artifacts available on your machine for a given build. Wayne On 9/7/07, Ritz, Martin [EMAIL PROTECTED] wrote: Ho Maven Users, I searched a lot around but couldn't find the answer to my question: How can I prevent maven from update manually added dependencies? Scope provided and system doesn't match my requirements - is there a way of doing in a other way? Thx alot --- Martin Ritz BTC AG - Geschäftseinheit Softwarelösungen mailto:[EMAIL PROTECTED] - 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] - 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]
AW:Re: AW: Question how to prevent maven from update manually add ed dependencies (detailed descr)
to use the offlien-mode is not an option for me cause I use actual Snapshots! Can you explain the other way a little bit more in detail? - Why add the pom to the repository ?- I don't understand this at all... Martin - You could use the offline-mode (-o), but this will also cut off any other dependencies from being resolved (if they are not available). The best solution will probably be to add the POM for that project in a company-wide repository and add that repo in your POM. On Monday 10 September 2007 16:10, Ritz, Martin wrote: It doesn't work. Another idea? Martin You can try setting the version in your dependency declaration to [1.0] which will lock down the version, and then Maven should realize that you already have those artifacts in your local repo cache, and it doesn't need to run out and look for updates. Wayne On 9/10/07, Ritz, Martin [EMAIL PROTECTED] wrote: Hallo, thx for the quick answer. Here a bit longer description: I have some dependencies which I added manually to my local repo because they are not available in the remote repository. Now everytime I build my project maven tries to update this dependency which is not availble in the remote repo. command line output: -- -- Downloading: http://commons.ucalgary.ca/pub/m2/***/***/***/1.0/***-1.0.pom Downloading: http://repo1.maven.org/maven2/***/***/***/1.0/***-1.0.pom -- -- This job is not necessary and costs time... so I want to prevent it. How can I force Maven to skip this check because I know for sure this dependency isn't in the remote repo. Martin __ __ Its not clear what you are trying to do and why. Please explain things better. In the meantime, you can use mvn -o ... for offline mode which will force Maven to use only the artifacts available on your machine for a given build. Wayne On 9/7/07, Ritz, Martin [EMAIL PROTECTED] wrote: Ho Maven Users, I searched a lot around but couldn't find the answer to my question: How can I prevent maven from update manually added dependencies? Scope provided and system doesn't match my requirements - is there a way of doing in a other way? Thx alot --- Martin Ritz BTC AG - Geschäftseinheit Softwarelösungen mailto:[EMAIL PROTECTED] - 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] - 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] -- Roland Asmann CFC Informationssysteme Entwicklungsgesellschaft m.b.H Bäckerstrasse 1/2/7 A-1010 Wien FN 266155f, Handelsgericht Wien Tel.: +43/1/513 88 77 - 27 Fax.: +43/1/513 88 62 Email: [EMAIL PROTECTED] Web: www.cfc.at - 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]
Question how to prevent maven from update manually added dependencies
Ho Maven Users, I searched a lot around but couldn't find the answer to my question: How can I prevent maven from update manually added dependencies? Scope provided and system doesn't match my requirements - is there a way of doing in a other way? Thx alot --- Martin Ritz BTC AG - Geschäftseinheit Softwarelösungen mailto:[EMAIL PROTECTED]
