snapshot timestamp dependency classpath

Scenario Description: 1) Project Foo has a dependency on Bar-SNAPSHOT. 2) Bar-SNAPSHOT is downloaded correctly from our repository and is timestamped. 3) The classpath of Foo shows Bar-SNAPSHOT, however the included jar has Bar-SNAPSHOT-time-time-time. Questions: q1) Is there a way to rename

Re: Dynamically Modifying the Classpath

will happen first if they are both in the same phase. We can't have this run before the jars are generated! I'd love to find out I'm wrong about this, though. As for adding the directory to the classpath, I am somewhat at a loss. If the folder was created earler, I think we could add it as a test

Re: Dynamically Modifying the Classpath

to update the pom.xml every time it changes. There's still the question of getting directories on the classpath. The directory we need is created during the pre-integration-test phase, so I don't think that adding it as a test resource would work, since the resource copying would happen before

Re: Dynamically Modifying the Classpath

On Sat, May 9, 2009 at 3:36 PM, Jeffrey N Hagelberg jnhagelb...@us.ibm.comwrote: There's still the question of getting directories on the classpath. The directory we need is created during the pre-integration-test phase, so I don't think that adding it as a test resource would work, since

Dynamically Modifying the Classpath

in the same phase. We can't have this run before the jars are generated! I'd love to find out I'm wrong about this, though. As for adding the directory to the classpath, I am somewhat at a loss. If the folder was created earler, I think we could add it as a test resource. However, I think

Exclude dependency from scope runtime test classpath

Hi, I was wondering if there is a way to remove a dependency from the test classpath when using scoperuntime/scope I want to make sure that the jar file is only used when running the application and not when testing it. So it really comes down to, I want to have the dependency (jar file

Re: Exclude dependency from scope runtime test classpath

Hi. did you tried provided scope instead? Hi, I was wondering if there is a way to remove a dependency from the test classpath when using scoperuntime/scope I want to make sure that the jar file is only used when running the application and not when testing it. So it really comes down

Re: Exclude dependency from scope runtime test classpath

to want to test this kind of dependency too in your tests. At least, IMO you'll have to provide a good use case to justify this new feature. Cheers. 2009/5/7 Henrik hen...@team11.org Hi, I was wondering if there is a way to remove a dependency from the test classpath when using scoperuntime

Re: Exclude dependency from scope runtime test classpath

As explained in the documentation, provided is much like compile, and [...] available on the compilation and test classpath. Cheers. 2009/5/7 Fabien Kruba fabien.kr...@gmail.com Hi. did you tried provided scope instead? Hi, I was wondering if there is a way to remove a dependency from

RE: Exclude dependency from scope runtime test classpath

dependency from scope runtime test classpath Hi, I was wondering if there is a way to remove a dependency from the test classpath when using scoperuntime/scope I want to make sure that the jar file is only used when running the application and not when testing it. So it really comes down to, I

Re: Exclude dependency from scope runtime test classpath

@maven.apache.org Subject: Exclude dependency from scope runtime test classpath Hi, I was wondering if there is a way to remove a dependency from the test classpath when using scoperuntime/scope I want to make sure that the jar file is only used when running the application and not when testing it. So

Re: mvn classpath weirdness with eclipse plugin

On Wed, May 6, 2009 at 12:29 AM, Davis Ford davisf...@zenoconsulting.biz wrote: I am at a loss.  We have no exclusions in the pom.  Where should I look next? Hello Davis, I remember, that this has popped up on the mailing list before. If I am not mistaken the suggested fix was to set the

mvn classpath weirdness with eclipse plugin

to the .classpath file, nor do they show up in Reference Libraries under eclipse. I have verified that this happens on multiple developer machines, so it isn't localized to a single environment. What is even stranger is that if you run the same project with mvn idea:idea, the aspectj jars show up

Re: Adding a directory to maven-surefire-plugin's classpath

...@gmail.com wrote: Sadly, no - that gets passed to the JVM running the tests. The problem here is that I need it in the classpath of the Maven JVM itself - Surefire's calling junit's Request.aClass(testClass).getRunner() on our test classes before it forks. Really, I need to get the developer

Re: Adding a directory to maven-surefire-plugin's classpath

Whoops - left off classpath from the subject. A. On Fri, May 1, 2009 at 1:27 PM, Andrew Bayer andrew.ba...@gmail.com wrote: Hi - I'm working on transitioning a large multi-module project from Ant to Maven, and have encountered a truly bizarre use case for Surefire. The unit tests

Re: Adding a directory to maven-surefire-plugin's classpath

, 2009 at 2:21 PM, Andrew Bayer andrew.ba...@gmail.com wrote: Whoops - left off classpath from the subject. A. On Fri, May 1, 2009 at 1:27 PM, Andrew Bayer andrew.ba...@gmail.com wrote: Hi - I'm working on transitioning a large multi-module project from Ant to Maven, and have

Re: Adding a directory to maven-surefire-plugin's classpath

Sadly, no - that gets passed to the JVM running the tests. The problem here is that I need it in the classpath of the Maven JVM itself - Surefire's calling junit's Request.aClass(testClass).getRunner() on our test classes before it forks. Really, I need to get the developer to rewrite the code

Re: mvn eclipse:eclipse - aspecjrt not added to .classpath

for the project, aspecjrt is not added to the .classpath file, but all the other dependencies are added without issues. Do I need to do anything else to add this dependency to the .classpath? Thanks -- View this message in context: http://www.nabble.com/mvn-eclipse%3Aeclipse---aspecjrt

Re: eclipse:eclipse suddenly adding including=**/*.java to .classpath

On Thu, Apr 9, 2009 at 7:58 AM, Arnaud HERITIER aherit...@gmail.com wrote: 1) The Maven convention and good practice is to put ressources files like *.txt in src/main/resources. But *FORCING* this 'convention' on the world is a whole other thing. One of the benefits of using maven is that you

Re: eclipse:eclipse and sorting in .classpath

Oh, thank you for the explaination. Now it is clear and I can accept the reorder :-) Regards Ingo Arnaud HERITIER schrieb: In maven when you are executing tests, tests classes and ressources are in the classpath before your main classes and ressources. In eclipse when you reorder the classpath

Re: eclipse:eclipse suddenly adding including=**/*.java to .classpath

On Thu, Apr 16, 2009 at 12:20 PM, Martijn Dashorst martijn.dasho...@gmail.com wrote: On Thu, Apr 9, 2009 at 7:58 AM, Arnaud HERITIER aherit...@gmail.com wrote: 1) The Maven convention and good practice is to put ressources files like *.txt in src/main/resources. But *FORCING* this

Re: eclipse:eclipse suddenly adding including=**/*.java to .classpath

Convention is convention because it's not a rule :) This also means you don't have to follow it but then it will cost you time/effort/extra configuration (you name it)... And this is valid everywhere where 'convention over configuration' exists (it's kinda by definition)... Best regards, Siarhei

Re: eclipse:eclipse suddenly adding including=**/*.java to .classpath

Once you force a convention the convention stops being convention and becomes a rule/law. So no, in case of maven it is still a convention :) So it's still possible to have resources along with the source code (if it happens that the convention isn't suitable for you). I beleived I had to do it a

Re: eclipse:eclipse suddenly adding including=**/*.java to .classpath

On Thu, Apr 16, 2009 at 3:29 PM, Siarhei Dudzin siarhei.dud...@gmail.com wrote: Convention is convention because it's not a rule :) This also means you don't have to follow it but then it will cost you time/effort/extra configuration (you name it)... Thanks for clarifying! :)

Re: eclipse:eclipse suddenly adding including=**/*.java to .classpath

Hi, The Maven convention and good practice is to put ressources files like *.txt in src/main/resources. This is a bit troublesome for those of us using the AspectJ plugin. We need to place *.aj files in the src/main/java (and test) directory. However, these files are excluded from the build.

Re: eclipse:eclipse and sorting in .classpath

the order of the source folder within the .classpath file of eclipse had changed after I ran mvn eclipse:clean eclipse:eclipse. Now the test folders come first and than the main folder. So the order of my source folders in eclipse is src/main/java, src

Re: eclipse:eclipse and sorting in .classpath

In maven when you are executing tests, tests classes and ressources are in the classpath before your main classes and ressources. In eclipse when you reorder the classpath in the project, you also reorder how entries are displayed in the UI. Our goal is to be sure that you have the same classpath

Re: eclipse:eclipse suddenly adding including=**/*.java to .classpath

On Thu, Apr 16, 2009 at 1:39 AM, Andrew Eisenberg andrew.eisenb...@gmail.com wrote: Hi, The Maven convention and good practice is to put ressources files like *.txt in src/main/resources. This is a bit troublesome for those of us using the AspectJ plugin. We need to place *.aj files in the

Mvn test: how to get classpath when starting another VM?

Dear list, I have a unit test that uses Java's Runtime.exec() method to start another VM and execute code in it. I need this to test recovery from simulated power failure. The code that should run in the VM is a test case itself, from the same project. I do not know what classpath to pass

Re: Mvn test: how to get classpath when starting another VM?

it classpath. http://svn.apache.org/viewvc/maven/surefire/tags/surefire-2.4.3/maven-surefire-plugin/src/main/java/org/apache/maven/plugin/surefire/SurefirePlugin.java?view=markup Hth, Nick Stolwijk ~Java Developer~ Iprofs BV. Claus Sluterweg 125 2012 WS Haarlem www.iprofs.nl On Thu, Apr 16, 2009

Re: eclipse:eclipse and sorting in .classpath

or what happened, but since a week the order of the source folder within the .classpath file of eclipse had changed after I ran mvn eclipse:clean eclipse:eclipse. Now the test folders come first and than the main folder. So the order of my source folders in eclipse is src/main/java, src

eclipse:eclipse and sorting in .classpath

Hello, I don't know what I did or what happened, but since a week the order of the source folder within the .classpath file of eclipse had changed after I ran mvn eclipse:clean eclipse:eclipse. Now the test folders come first and than the main folder. So the order of my source folders

Re: eclipse:eclipse and sorting in .classpath

folder within the .classpath file of eclipse had changed after I ran mvn eclipse:clean eclipse:eclipse. Now the test folders come first and than the main folder. So the order of my source folders in eclipse is src/main/java, src/test/java instead of src/test/java,src/main/java. Does anybody know

Re: eclipse:eclipse suddenly adding including=**/*.java to .classpath

Hi, On Wed, Apr 8, 2009 at 11:28 PM, Zach Cox zcox...@gmail.com wrote: While I realize that technically only .java files should exist in src/main/java, it's a pain to create a duplicate package hierarchy in src/main/resources and this greatly reduces visibility of these .txt files. This is

Re: eclipse:eclipse suddenly adding including=**/*.java to .classpath

1) The Maven convention and good practice is to put ressources files like *.txt in src/main/resources. I totally agree - long-term we will move everything that's not a .java file there. We're still adjusting to doing everything the Maven way. 2) The change you have is due to the new version

eclipse:eclipse suddenly adding including=**/*.java to .classpath

Before this week, running mvn eclipse:eclipse would put a line like this in .classpath: classpathentry kind=src path=src/main/java/ Now this week it is putting this line in .classpath instead: classpathentry kind=src path=src/main/java including=**/*.java/ We have some .txt files that sit

Re: eclipse:eclipse suddenly adding including=**/*.java to .classpath

this in .classpath: classpathentry kind=src path=src/main/java/ Now this week it is putting this line in .classpath instead: classpathentry kind=src path=src/main/java including=**/*.java/ We have some .txt files that sit alongside .java files in the package structure in src/main/java. When running mvn

include current direcory path into jar classpath in manifest.mf file

Hi, I am getting FileNotFoundException while reading resource files in current directory . Can u please help me to include current directory path apart from library jar files path in manifest.mf file of a jar. Thanks Regards Polireddy Reddem VOIP: 6917 Access Identity Management Team ITS -

maven-compiler-plugin resources not in classpath

have to include the jar in the javac classpath to get it to process annotations, you do not have to mention it on the command line. Unforunately if you build your pom.xml to include this file under the resources tag, it gets included in the classpath, and then the compiler complains

Re: maven-compiler-plugin resources not in classpath

Hi David, If I understand the problem correctly, it will be solved by excluding META-INF/services/javax.annotation.processing.Processor file from your module resources (thereby preventing it from being put into the classpath). Please read http://maven.apache.org/pom.html#Resources for more

Re: maven-compiler-plugin resources not in classpath

On Monday 06 April 2009, jie...@gmail.com wrote: Hi David, If I understand the problem correctly, it will be solved by excluding META-INF/services/javax.annotation.processing.Processor file from your module resources (thereby preventing it from being put into the classpath). Please read http

MECLIPSE-544 a.k.a. AJDT support breaks classpath

Alan, can you reconsider the status of this issue, where AspectJ jars are not included in the Eclipse .classpath file by default: http://jira.codehaus.org/browse/MECLIPSE-544 You provided a workaround, but to me this still feels like a bug, especially since it breaks pre-existing POMs

Re: maven-compiler-plugin resources not in classpath

Hello David, Please review the maven-jar-plugin, specifically the includes parameter to the jar goal. http://maven.apache.org/plugins/maven-jar-plugin/jar-mojo.html#includes -jesse On Mon, Apr 6, 2009 at 9:47 AM, David Goodenough david.goodeno...@btconnect.com wrote: But will that not exclude

Re: maven-compiler-plugin resources not in classpath

On Monday 06 April 2009, jie...@gmail.com wrote: Hello David, Please review the maven-jar-plugin, specifically the includes parameter to the jar goal. http://maven.apache.org/plugins/maven-jar-plugin/jar-mojo.html#includes -jesse On Mon, Apr 6, 2009 at 9:47 AM, David Goodenough

Re: include current direcory path into jar classpath in manifest.mf file

I am getting FileNotFoundException while reading resource  files in current directory . Can u please help me to include current directory path apart from library jar files path in manifest.mf file of  a jar. Why don't you provide a few lines of code that aren't working and/or a few lines out

Manifest file classpath

Hello All, Is there any way to change the filenames in the manifest classpath? Ex. more MANIFEST.MF Manifest-Version: 1.0 Archiver-Version: Plexus Archiver Created-By: Apache Maven Built-By: testuser Build-Jdk: 1.5.0_14 Main-Class: com.mnr.gui.MNRgui Class-Path: lib/utils-1.0.0-P1A01

Re: Extracting classpath for an application from maven

Thanks , i think thats the best and proper way to get it .! On Wed, Mar 18, 2009 at 1:18 PM, Nicolas R. nromane...@jaxio.com wrote: Hello, Try to run 'mvn dependency:build-classpath' Here is the doc: http://maven.apache.org/plugins/maven-dependency-plugin/plugin-info.html Nicolas

Re: Extracting classpath for an application from maven

Hello, Try to run 'mvn dependency:build-classpath' Here is the doc: http://maven.apache.org/plugins/maven-dependency-plugin/plugin-info.html Nicolas -- http://www.springfuse.com www.springfuse.com Roman Kournjaev wrote: Hi All I have a maven based application, well now i want to run

classpath ordering

Hi, I'm using gwt, and Google folks had the strange idea to include some old version of apache commons-* in the jar. I get NoSuchMethodError in unit tests becausse I can't specify the classpath ordering of my dependencies during tests. Is there any surefire Hack I could use to EXCLUDE

Re: classpath ordering

I'm using gwt, and Google folks had the strange idea to include some old version of apache commons-* in the jar. I get NoSuchMethodError in unit tests becausse I can't specify the classpath ordering of my dependencies during tests. Even if you could hack Surefire to include the newer Commons

RE: classpath ordering

Defining what version of the jar to use in the depedencyManagement section doesn't work here? --- Todd Thiessen -Original Message- From: Wayne Fay [mailto:wayne...@gmail.com] Sent: Wednesday, March 11, 2009 12:26 PM To: Maven Users List Subject: Re: classpath ordering I'm

Re: classpath ordering

wrote: Defining what version of the jar to use in the depedencyManagement section doesn't work here? --- Todd Thiessen -Original Message- From: Wayne Fay [mailto:wayne...@gmail.com] Sent: Wednesday, March 11, 2009 12:26 PM To: Maven Users List Subject: Re: classpath

Re: classpath ordering

The issue is that gwt-dev INCLUDES org.apache.commons.* classes, it does not depend on some commons-* as maven projet may expect (Gwt guys don't use Maven) I still think you should file a bug against GWT itself and ask them to shade these classes if they're going to package them in their

Extracting classpath for an application from maven

Hi All I have a maven based application, well now i want to run it in cmd mode, it means just executing the compiled class. How do i extract the classpath for this application from my pom easilly ? Thanks in advance. Roman

Re: Extracting classpath for an application from maven

the classpath for this application from my pom easilly ? Thanks in advance. Roman

Re: Extracting classpath for an application from maven

Thanks , that's a nice plugin. But i see it places the jars into some assembled repository, but it would be really nice to get the classpath to the jars that are in my local maven repository. Thanks in advance On Sat, Mar 7, 2009 at 1:23 PM, Wim Deblauwe wim.debla...@gmail.com wrote

Re: Extracting classpath for an application from maven

On Mar 7, 2009, at 3:11 AM, Roman Kournjaev wrote: I have a maven based application, well now i want to run it in cmd mode, it means just executing the compiled class. I use exec:java for this. Trevor - To unsubscribe,

Re: classpath attributes for maven-eclipse-plugin

Andrew, Have you tried m2eclipse [1]? It provides new import wizard for importing Maven projects and also have integration for AJDT, i.e. sets required attributes on classpath entries accordingly [2]. regards, Eugene [1] http://m2eclipse.codehaus.org/ [2] http://docs.codehaus.org/display

classpath attributes for maven-eclipse-plugin

Hi all, I was wondering if it is possible to add classpath attributes to the .classpath file when the maven eclipse plugin creates an eclipse project. For example, this is what i would like to do something like this (the attribute section): ?xml version=1.0 encoding=UTF-8? classpath

Re: classpath attributes for maven-eclipse-plugin

Hi Is it this issue : http://jira.codehaus.org/browse/MECLIPSE-270 ? can you test a 1.6-SNAPSHOT ? arnaud On Wed, Mar 4, 2009 at 7:11 AM, Andrew Eisenberg and...@eisenberg.aswrote: Hi all, I was wondering if it is possible to add classpath attributes to the .classpath file when the maven

Re: Maven Eclipse plugin: How to include source path in .classpath?

Roland Bali wrote: Hi, I would like to add the following to my .classpath when running eclipse:eclipse. How can I do this? classpathentry kind=src path=fixtures/ Use the build-helper plugin [1] to add the fixtures directory to your sources. The maven-eclipse-plugin will pick it up when

Re: Maven Eclipse plugin: How to include source path in .classpath?

Thanks Dirk! The plugin solved my problem. /Roland On Fri, Feb 20, 2009 at 11:20 AM, Dirk Olmes d...@xanthippe.ping.de wrote: Roland Bali wrote: Hi, I would like to add the following to my .classpath when running eclipse:eclipse. How can I do this? classpathentry kind=src path

Maven Eclipse plugin: How to include source path in .classpath?

Hi, I would like to add the following to my .classpath when running eclipse:eclipse. How can I do this? classpathentry kind=src path=fixtures/ /Roland

Maven surefire plugin, TestNG classpath reference to suiteXmlFile

Hello all, Is there a way to configure Maven surefire plugin to lookup TestNG suiteXmlFile as classpath resource? A use case where this would be useful is if one had interfaces, implementation and test of specific api as separate maven modules, where test module would contain testng xml file

Re: Maven surefire plugin, TestNG classpath reference to suiteXmlFile

Is there a way to configure Maven surefire plugin to lookup TestNG suiteXmlFile as classpath resource? I'm not aware of such functionality at this time, but you could probably add it by hacking m-s-p in the constructSurefireBooter() method and adding a corresponding configuration option so

Re: Running Groovy scripts with project's compile classpath

/modelVersion groupIdnet.foogoo.maven.test/groupId artifactIdgroovy-classpath/artifactId version0.0.1-SNAPSHOT/version build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId

Running Groovy scripts with project's compile classpath

://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdnet.foogoo.maven.test/groupId artifactIdgroovy-classpath

Antwort: Eclipse Plugin - No .classpath file.

The trigger is pde || ( Constants.LANGUAGE_JAVA.equals( artifactHandler.getLanguage() ) !Constants.PROJECT_PACKAGING_EAR.equals( packaging ) ); Therefore, if you have a custom packaging type, you need to add the following to META-INF/plexus/components.xml component

Eclipse Plugin - No .classpath file.

How does the maven-eclipse-pluging know to create .classpath for Eclipse? I've created a custom packaging type for my integration test module to prevent undesirable activity. So, for now, only the compile and resources phases are actually doing anything. Now, when I run eclipse:eclipse

Weired classpath pb: class not found in parent dir

. Would anyone have an idea what could cause this classpath problem (if it is any)? Many thanks! Cheers Markus [INFO] [antrun:run {execution: generate-sources}] [INFO] Executing tasks [java] Could not find org.apache.xalan.xslt.Process. Make sure you have it in your classpath

Re: Weired classpath pb: class not found in parent dir

, although I put a dependency to Xalan in the antrun plugin definition. Would anyone have an idea what could cause this classpath problem (if it is any)? If you run a different instacne of the ant-run-plugin first that does not declare this dep. Each plugin is loaded once and only. Use a common

Re: How do I add all the jars in a directory in junit test exeicution classpath

On Wed, Jan 21, 2009 at 3:57 AM, peppinolusuraio uaschits...@libero.it wrote: I have created a directory %M2_REPO%/myNewGroup/myNewArtifacId/ and I have copied all my jar in the lib. It does not work. You need to use the install plugin to put the jars into your local repository. mvn

Re: How do I add all the jars in a directory in junit test exeicution classpath

I have the same problem but I'm not able to make it work. Assume I have to add to CLASSPATH about 10 jars all coming from other products of my society. for the moment all this products are not built using maven, so I have to use them in a quite ANT fashion adding these jars to the classpath

Getting classpath list from non ant-run plugins

Hi all. Using the ant-run plugin, you can get properties, like this: property name=project.build.classpath refid=maven.compile.classpath / What I'd like to do it to get access to the same classpath entries but from a normal (ie not an ant-run derivative) plugin. Ideally, I'd like to use

AW: Getting classpath list from non ant-run plugins

Hi Chris! The classpath to the compiled classes can be injected into your Java Mojo: /** * List of all class path elements that will be searched for... * * @parameter expression=${project.compileClasspathElements} * @required * @readonly */ protected List

mvn eclipse:eclipse - aspecjrt not added to .classpath

My pom.xml has a dependency to aspectrt: dependency groupIdaspectj/groupId artifactIdaspectjrt/artifactId version1.5.3/version /dependency When I run mvn eclipse:eclipse for the project, aspecjrt is not added to the .classpath file Do I need to do anything else to add

Re: mvn eclipse:eclipse - aspecjrt not added to .classpath

My pom.xml has a dependency to aspectrt: dependency groupIdaspectj/groupId artifactIdaspectjrt/artifactId version1.5.3/version /dependency When I run mvn eclipse:eclipse for the project, aspecjrt is not added to the .classpath file, but all the other dependencies are added without

Re: How do I add all the jars in a directory in junit test exeicution classpath

[moved from d...@] On Fri, Jan 9, 2009 at 6:48 AM, Nimbkar, Mandar mandar.nimb...@patni.com wrote: I have few junit test cases to be executed using Maven build. My test classes require all the jars located a directory (say %JBOSS_HOME%\server\default\lib dir) in the classpath. How do I add

Re: classpath question

Hi, I have not tried additional classpath feature in maven2. I am not sure whether you load your xml file as following? InputStream inputStream = YourClass.class. getResourceAsStream(The relative PATH of your XML file); Thanks. Linghua 2008/12/28 Neo Anderson javadeveloper...@yahoo.co.uk I

classpath question

is located at reousrces/project/name/to/file.xml. Unfortunately, when executing the test (via mvn package), it seems the default classpath would be the place where pom.xml exists. Therefore, if in the xmlTest.java I specify xml path like parser.parse(project/name/to/file.xml); The maven throws Running

Re: How to add a local jar to the classpath of exec-maven-plugin

-to-the-classpath-of-exec-maven-plugin-tp20893674p20894581.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: How to add a local jar to the classpath of exec-maven-plugin

version1.1-beta-1/version executions execution goals goalexec/goal /goals /execution /executions configuration executablejava/executable arguments argument-classpath/argument

How to add a local jar to the classpath of exec-maven-plugin

goals goalexec/goal /goals /execution /executions configuration executablejava/executable arguments argument-classpath/argument classpath/ argumentorg.myapp.client.Client/argument

How to place the project classpath into a ressource file?

for the property could look like this for example: app.classpath=lib/commons-logging.jar;lib/commons-httpclient.jar This works perfectly. But instead of hard coding and maintaining the classpath in the configuration file as seen above, I would prefer using some sort of Maven 2 Filter which calculates

Re: How to place the project classpath into a ressource file?

You can use the maven-dependency-plugin:build-classpath goal --Brian (mobile) On Nov 29, 2008, at 11:28 AM, Stephan Niedermeier [EMAIL PROTECTED] wrote: Hi, I'm using Maven2 to build and assemble my project under Win XP. The project contains a Java launcher. This launcher needs to know

Re: How to place the project classpath into a ressource file?

Hi Brian, thanks for the hint, but it seems that the build-classpath goal calculates the full path to the jars (e.g. C:/project/lib/myJar.jar). Is there a way to make this path relatively to, let's say lib/ of the assembled folder? Thanks a lot. Regards Stephan Brian Fox schrieb: You can

Re: How to place the project classpath into a ressource file?

Hi, got it. Thanks. For those interested in: Use the prefix together with the outputFilterFile parameter of the build-classpath goal. Example: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-dependency-plugin/artifactId

Re: How to place the project classpath into a ressource file?

I don't think so but it should be easy to patch --Brian (mobile) On Nov 29, 2008, at 1:39 PM, Stephan Niedermeier [EMAIL PROTECTED] wrote: Hi Brian, thanks for the hint, but it seems that the build-classpath goal calculates the full path to the jars (e.g. C:/project/lib/ myJar.jar

Re: How to place the project classpath into a ressource file?

Heh... I Forgot about that --Brian (mobile) On Nov 29, 2008, at 2:06 PM, Stephan Niedermeier [EMAIL PROTECTED] wrote: Hi, got it. Thanks. For those interested in: Use the prefix together with the outputFilterFile parameter of the build-classpath goal. Example: plugin

Re: Exclude some jar from the classpath generated by eclipse:eclipse

.classpath. Regards, Rice On Thu, Nov 13, 2008 at 6:59 AM, Nick Stolwijk [EMAIL PROTECTED] wrote: It is indeed not clear from the documentation, but if you look the documentation closely you see a Jira issue attached: List of artifact to exclude from eclipse classpath, beeing provided

Re: Exclude some jar from the classpath generated by eclipse:eclipse

. Shouldn't the named jar be excluded from .classpath. Regards, Rice On Thu, Nov 13, 2008 at 6:59 AM, Nick Stolwijk [EMAIL PROTECTED]wrote: It is indeed not clear from the documentation, but if you look the documentation closely you see a Jira issue attached: List of artifact to exclude from

Exclude some jar from the classpath generated by eclipse:eclipse

Hi, How do I configure pom to exclude some jar from the classpath generated by eclipse:eclipse. I have checked the documents of eclipse:eclipse. There is a parameter excludes but there is no example. Regards, Rice

Re: Exclude some jar from the classpath generated by eclipse:eclipse

It is indeed not clear from the documentation, but if you look the documentation closely you see a Jira issue attached: List of artifact to exclude from eclipse classpath, beeing provided by some eclipse classPathContainer [MECLIPSE-79] This jira issue provide the documentation: excludes

Re: Exclude some jar from the classpath generated by eclipse:eclipse

Yes, I tried. But it seems not work. Shouldn't the named jar be excluded from .classpath. Regards, Rice On Thu, Nov 13, 2008 at 6:59 AM, Nick Stolwijk [EMAIL PROTECTED]wrote: It is indeed not clear from the documentation, but if you look the documentation closely you see a Jira issue attached

Re: m2eclipse plugin, debug configuration classpath/sources issue?

This has been fixed in the trunk version of m2eclipse. On 12-Oct-08, at 10:51 AM, Eugeny N Dzhurinsky wrote: Hello! I recently found some really weird issue when doing the debug of the libraries with attached sources in Eclipse. I used projects, which are being built by Maven2. The

m2eclipse plugin and generated-source and Eclipse Classpath

generated code in classpath but m2eclipse is ignoring those classes and I am getting compilation error in eclipse. But it works fine from maven (2.0.9) command for compile or install goal, it always add the generated source in classpath plugin

Re: m2eclipse plugin and generated-source and Eclipse Classpath

when my import was completed, I had some JAXB generated code during build time in maven generate-sources phase, when I use to run mvn eclipse:eclipse it always add those jaxb generated code in classpath but m2eclipse is ignoring those classes and I am getting compilation error in eclipse

Re: m2eclipse plugin, debug configuration classpath/sources issue?

-generated after the dependency was added using maven eclipse plugin - the new sources are resolved immediately. Can somebody please advice? -- View this message in context: http://www.nabble.com/m2eclipse-plugin%2C-debug-configuration-classpath-sources-issue--tp19944085p20240001.html Sent

Re: assembly - grabbing runtime classpath for bat script

of: - our projects jar - a lib dir with all of our projects dependencies - bat scripts to execute the jar However I still need to add all of the jars in the lib to the classpath when invoking java in the bat scripts. Is there any way to have maven add the appropriate dependencies entries

Re: assembly - grabbing runtime classpath for bat script

In my setup the jars are all listed in the manifest but they don't have any directory prepended. The jar with main is in the same directory as the jars listed in its manifest. The script that runs it cds to that directory. It doesn't set classpath since the current directory is normally

<    1   2   3   4   5   6   7   8   9   10   >