that appears in my classpath for
test is 1.0.4, NOT 1.1 as it appears that it ought to be. Additionally, this
means that avalon-framework is not present in my surefire test classpath,
causing tests to break.
If removed - nearer found: 1.0.4 is the last thing you see, then
that's the version Maven has
, it's the tests that don't. This is
actually not because of commons-logging, but one of the dependencies that
1.1 includes, but 1.0.4 does not.
I also have another problem elsewhere where tests *randomly* fail, because
commons-lang isn't on the test classpath, even though it's the very first
jar
that
1.1 includes, but 1.0.4 does not.
I also have another problem elsewhere where tests *randomly* fail, because
commons-lang isn't on the test classpath, even though it's the very first
jar file specified in the POM!
This leads me to suspect that the dependencies are being stuffed in a
hashmap
Hi,
I wrote a simple shell script that helps people who works with multiple
branches of one project in Eclipse. We can use a separate workspace for
each branch, but it's somewhat cumbersome. I tested the script in a various
project settings such as a complex multiproject. Here's the page that
an arbitrary classpath order but the spring sand box Jar
always seems to come first in the classpath and the wrong Assert class
is loaded. This problem rears it's heading during unit testing so we
keep getting NoSuchMethodError's. Can anyone confirm whether we are SOL
or if there is a solution that solves
they have
incompatible method signatures. The correct Assert class is the one in
the spring jar, not the one in the spring sand box jar. It appears that
Maven 2 has an arbitrary classpath order but the spring sand box Jar
always seems to come first in the classpath and the wrong Assert class
is loaded
In my multiproject, I use commons-lang. In my pom.xml (atend) I have the
dependency set (excluded once to avoid a conflict).
However, the build sometimes fails, but not always, trying to find a class
in commons-lang. Doing a mvn -X shows it isn't present
on the test classpath.
Is there some way
Hi,
I'm working on a Maven plugin and need to modify the classpath. It
appears that maven runs the plugin with all of its dependencies, but the
plugin itself can't see them. The only classpath entry I have is
C:\dev\maven\core\boot\classworlds-1.1.jar.
Any help would be appreciated. My guess
Maven manages its classloader hierarchy through classworlds (
http://classworlds.codehaus.org/). If you want to do some manipulation of
the hierarchy, you must do it through that. Unless you actually need to
modify the classpath for some other third party execution, in which case set
the system
-exec-plugin to execute the jarred application from the
command line using using mvn exec:exec. I have tried all combinations of
configurations and ... my goal is not to have to copy the log4j jar into my
target directory. That's the only way I can see the jar on the classpath.
The maven-exec-plugin
I can see the jar on the classpath.
The maven-exec-plugin site says that the jars will be seen on the
classpath
automatically.
1- do not crospost if possible.
2- this is probbably wrong
classpath
!-- automatically creates the classpath using all project
dependencies
Hi,
Thank you for the reply. I tried changing the scope to provided for the
resin jar, but it still seems to be used in the test classpath. What would
be nice is if I could actually remove it completelt from the test classpath
- is there a way to do this with Maven?
thanks
--
View
On 27/11/06, rking999 [EMAIL PROTECTED] wrote:
Thank you for the reply. I tried changing the scope to provided for the
resin jar, but it still seems to be used in the test classpath. What would
be nice is if I could actually remove it completelt from the test classpath
- is there a way to do
because
the local jars are not on maven's default compile classpath.
How to add local jars to maven's compile classpath? Any suggestions are
appreciated. I'm looking for a solution that adds the lcoal jars
programmatically (so we can have this set in our plugin code). But if
anyone knows how
sources using standard maven compiler plugin.
However, the compilation needs some jars that's installed locally on user's
machine (not present in maven repository). The compilation fails because
the local jars are not on maven's default compile classpath.
How to add local jars to maven's compile
to compile the java source.
There doesnt seem to be a way to change the order of the test classpath to
move the xmlParserApis jar above the resin one
Any help would be greatly appreciated. thanks in advance.
--
View this message in context:
http://www.nabble.com/Test-Classpath-Order
as it is needed to compile the java source.
There doesnt seem to be a way to change the order of the test classpath to
move the xmlParserApis jar above the resin one
Any help would be greatly appreciated. thanks in advance.
--
View this message in context:
http://www.nabble.com/Test
that it is
not inserted in the root of the classpath that my ant tasks use. Does anyone
have any idea?
Regards,
Roozbeh Maadani
--
View this message in context:
http://www.nabble.com/Classpath-problem-tf2689837s177.html#a7500843
Sent from the Maven - Users mailing list archive at Nabble.com
moduleweb/module
/modules
each of the modules contains a pom.xml of its own, well the usual stuff.
in the standalone version (without eclipse) everything works fine.
the problem occurs when i import that project into eclipse and try to
compile
the project. after creating the
.classpath and .project
The maven eclipse plugin creates eclipse .project and .classpath files
for each maven project ( : pom.xml file).
You should read this guide :
http://maven.apache.org/guides/mini/guide-ide-eclipse.html
2006/11/22, AndreasWuest [EMAIL PROTECTED]:
hello,
i have a question concerning the usage
i have seen the guide, but it did not really convice me. so this guide
tells me that i need at least two eclipse instances.
one that only servers as a cvs client, and one which is used as java ide.
i can't see the disadvantage of having a .project and a .classpath
created in the parent
a .project and a .classpath
created in the parent, with properly set src and output folders.
correct me if i am wrong, but the only disadvantage would be the fact,
that it might be complicated to collect all the
data and create the correct paths, or do i miss something ? once the src
and output folders
a .project and a .classpath
created in the parent, with properly set src and output folders.
correct me if i am wrong, but the only disadvantage would be the fact,
that it might be complicated to collect all the
data and create the correct paths, or do i miss something ? once the src
and output folders
On 11/21/06, Deluigi Marcus [EMAIL PROTECTED] wrote:
We ported an existing project from ant to maven and it seems as if the
classpath of one module is different to the classpath to the parent
modules which causes the junit tests to fail in the parent modules.
Since the junit tests fail
:
We ported an existing project from ant to maven and it seems as if the
classpath of one module is different to the classpath to the parent
modules which causes the junit tests to fail in the parent modules.
Since the junit tests fail, it is not possible to proceed to the install
phase.
I
I tried that within my java project:
System.out.println(System.property(..))
Unfortunately, it's not working.
All I see is a global classpath which points to a Maven jar.
Maven is using a customized classloader, so it's hard to get the
module-specific classpath.
When using the '-X' switch
Hi
It seems like a stupid question, but how do I let maven print the actual
class path within a specific module?
I did not find any information about this anywhere.
Thanks!
Marcus
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
On 11/20/06, Deluigi Marcus [EMAIL PROTECTED] wrote:
It seems like a stupid question, but how do I let maven print the actual
class path within a specific module?
I did not find any information about this anywhere.
If you add -X to the command line:
mvn install -X
it will print out more
classpath :
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-compiler-plugin:2.0.1:compile' --
[DEBUG] (f) basedir =
C:\pragmaticus-sea-ias\eclipse-3.1.2-workspaces\dev-ep1x\eportal
[DEBUG] (f) buildDirectory =
C:\pragmaticus-sea-ias\eclipse-3.1.2-workspaces\dev-ep1x\eportal\target
On 11/14/06, Wayne Fay [EMAIL PROTECTED] wrote:
Scope test is not included in build classpath. Both problem jars are
scoped test. The others have no scope so they default to compile.
Wayne
I get confused by the scope thing.If scope is test , does that mean
the jars will only be used
:
.) pre-integration-test
.) integration-test
.) post-integration-test
plus the phases from the site lifecycle (for building
test reports)
lg,
strub
--- Jeff Mutonho [EMAIL PROTECTED] schrieb:
On 11/14/06, Wayne Fay [EMAIL PROTECTED] wrote:
Scope test is not included in build classpath.
Both
, On 2006-11-14 11:03 AM:
On 11/14/06, Wayne Fay [EMAIL PROTECTED] wrote:
Scope test is not included in build classpath. Both problem jars are
scoped test. The others have no scope so they default to compile.
Wayne
I get confused by the scope thing.If scope is test , does that mean
the jars
Scope test is not included in build classpath. Both problem jars are
scoped test. The others have no scope so they default to compile.
Wayne
On 11/14/06, Jeff Mutonho [EMAIL PROTECTED] wrote:
I have a small proof of concept I'm trying to build.In the project's
super pom , I have a dependency
Thanx ...much appreciated
Jeff Mutonho
Cape Town
South Africa
GoogleTalk : ejbengine
Skype: ejbengine
Registered Linux user number 366042
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:
Hello Remy,
Thank you for this post.
I have exactly the same problem as you. I wonder if anybody else use xdoclet
and maven 2 with antRun ...
I've tried your solution and I would like to add that we must use
the maven.dependency.classpath as xdoclet classpath.
I agree with you
Hello,
I am :)
yes found problems, you already mention solutions.. :)
in my case, maven classpath was not enough so i had to add also external jar
files (i m using jbossws with xdoclet for J2EE 1.3 beans)
additionally, for anyone who might find same problems, if you have a
multiproject
to the Ant classpath. Does
anybody have a clue?
Using these properties:
* maven.dependency.classpath
* maven.compile.classpath
* maven.runtime.classpath
* maven.test.classpath
* maven.plugin.classpath
doesn't work.
Thanks,
Wilfred
--
View
version1.5R4.1/version
/dependency
which seems to work. Here is a snippet from my build.xml file:
project
target name=prepare-docbkx
mkdir dir=target/docbkx/
taskdef name=script
classname=org.apache.tools.ant.taskdefs.optional.Script
classpath path
Hi
You can use the was-plugin-anttasks in the codehaus sandbox. I wrote an ant
task that will get the dependencies from your project and transform them
into a classpath list in Ant. If you want to look at how it is used, look at
the was5-maven-plugin.
Hermod
-Opprinnelig melding-
Fra
the site, the reporting
plugin fails. It seems that it dos not find my components.xml. I have check
tht it is in the jar.
What's the classpath use for the reporting plugin ? How to add artifact
specific for a reporting plugin ?
--
View this message in context:
http://www.nabble.com/Classpath
Ryan
Chief Technology Officer
Soaring Eagle L.L.C.
[EMAIL PROTECTED]
www.soaringeagleco.com
(303) 263-3044
-Original Message-
From: Dmystery [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 02, 2006 8:55 PM
To: users@maven.apache.org
Subject: RE: [M2]weblogic:appc classpath issue
I
-Original Message-
From: Dmystery [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 02, 2006 8:55 PM
To: users@maven.apache.org
Subject: RE: [M2]weblogic:appc classpath issue
I downloaded the code from codehaus SNV and it working fine now. Thanks
again!
Any plans to include autotypes
Hi
Is it possible to add a single jar to the classpath (MANIFEST) of
another jar, without using dependencies in Maven2?
I can't use dependencies, because the jar which should be named in the
classpath is not generated by Maven at the moment I generate the other
jar.
But it will be generated some
that documentation. This fixes the classpath issue both
in
appc and the client gen mojos. I have not updated the 2.9.0 version as
the
9.2 release broke all the apis I was using so i need to refactor to use
the
new API's.
Let me know if you would prefer I push up the 2.8.0 version now and just
post
Also, you mention the 9.2 release. As we're using WLS 8.1.3 will we miss out on
this fix?
/jonas
-Ursprungligt meddelande-
Från: Manu [mailto:[EMAIL PROTECTED]
Skickat: den 2 november 2006 10:27
Till: Maven Users List
Ämne: Re: [M2]weblogic:appc classpath issue
Can you also tell
, November 01, 2006 9:06 PM
To: users@maven.apache.org
Subject: RE: [M2]weblogic:appc classpath issue
Thanks Scott. It would be great if you can push the latest snapshot to the
repository now.
Scott Ryan-2 wrote:
I have refactored the 2.8.0 plugin to fix that problem. I have changed
some
-Original Message-
From: Jonas Olsson [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 02, 2006 2:41 AM
To: Maven Users List
Subject: SV: [M2]weblogic:appc classpath issue
Also, you mention the 9.2 release. As we're using WLS 8.1.3 will we miss out
on this fix?
/jonas
-Ursprungligt
@maven.apache.org
Subject: RE: [M2]weblogic:appc classpath issue
Thanks Scott. It would be great if you can push the latest snapshot to the
repository now.
Scott Ryan-2 wrote:
I have refactored the 2.8.0 plugin to fix that problem. I have changed
some
of the parameters and since
have completed that documentation. This fixes the classpath issue both in
appc and the client gen mojos. I have not updated the 2.9.0 version as the
9.2 release broke all the apis I was using so i need to refactor to use the
new API's.
Let me know if you would prefer I push up the 2.8.0 version
The fix is in the code on the branch 2.8.0. i am trying to publish the
fixes if I can get authorization. You can pull down the code and build it
and that should fix your classpath issues.
Scott Ryan
Chief Technology Officer
Soaring Eagle L.L.C.
[EMAIL PROTECTED]
www.soaringeagleco.com
(303) 263
]
Sent: Monday, October 30, 2006 11:47 PM
To: users@maven.apache.org
Subject: RE: [M2]weblogic:appc classpath issue
Alos, looking at AppcMojo.class file, i dont see any default classpath being
set. Here is the stack trace when i try to run the plugin.
[INFO] Detailed Appc settings information
a page to describe the new settings for the 2.8.0
plugin. I will be pushing the latest snapshot up to the repository once I
have completed that documentation. This fixes the classpath issue both in
appc and the client gen mojos. I have not updated the 2.9.0 version as
the
9.2 release broke all
Hi,
I have the same problem. I need to explicitly set the entire classpath by
hand to have it worked. In other words, I'm defining another time all the
dependencies that already are in the pom. The plugin does not seem to take
into account the dependencies.
By the way, i'm using version 2.8.0
I still have issue in compiling the ejb jar file. It simply fails to find all
the dependencies in the classpath.
Here is the plugin definition again.
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdweblogic-maven-plugin/artifactId
version2.8.0-SNAPSHOT/version
configuration
Alos, looking at AppcMojo.class file, i dont see any default classpath being
set. Here is the stack trace when i try to run the plugin.
[INFO] Detailed Appc settings information AppcMojo[basicClientJar = false
classpath = null
compiler = null
debugging = true
deprecation = false
Hi
I have a maybe very easy question, but I can't find it in the docu of
Maven2.
Is it possible to add a single jar to the classpath of another single
jar, without using dependencies in Maven?
I can't use dependencies, because the jar which should be named in the
classpath is not generated
this option [Main-Class:classname], the JAR file is the
source of all user classes, and other user class path settings are ignored.
I was trying to extend the classpath from outside the jar (-cp xxx)
and this is what does not work according to the specs.
I did not try to extend the classpath
good docs for this. If you want maven to include your dependencies,
say this:
archive
manifest
mainClasscom.example.App/mainClass
addClasspathtrue/addClasspath
/manifest
/archive
To give your own classpath (or prepend to what maven writes), do this:
archive
...
manifestEntries
is included in
the war.
--
View this message in context:
http://www.nabble.com/Classpath-Generation-tf2523810.html#a7039856
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED
to provided the addClasspath setting in the
archiver
does not include the element in the classpaht. If I set the dependency to
runtime then it is included in the manifest but the library is included in
the war.
--
View this message in context:
http://www.nabble.com/Classpath-Generation-tf2523810
. What I think happens is that when you list
a dependency as provided it is ignored when generating the classpath for the
WAR in the maven-war-plugin module.
Alexander Sack-3 wrote:
Specify them as provided with addClassPath but also specify them in your
EAR
plugin under javaModule tags
in its
class-path
-- but to NOT have
those jar files included in the lib directory of the war file (as they are
included in the
root directory of the ear file. What I think happens is that when you
list
a dependency as provided it is ignored when generating the classpath for
the
WAR in the maven-war
snapshot of 2.2 yet, so I didn't test with that, so I can't
confirm. However, as I understand it, fix for means that is should be
fixed before that release, not that it's fixed.
--
View this message in context:
http://www.nabble.com/Add-Directory-to-Jar-Manifest-Classpath-tf2504507.html#a7006293
it, fix for means that is should be
fixed before that release, not that it's fixed.
--
View this message in context:
http://www.nabble.com/Add-Directory-to-Jar-Manifest-Classpath-tf2504507.html#a7014719
Sent from the Maven - Users mailing list archive at Nabble.com
:
http://www.nabble.com/Add-Directory-to-Jar-Manifest-Classpath-tf2504507.html#a7016118
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail
=jar help:describe.
--
View this message in context:
http://www.nabble.com/Add-Directory-to-Jar-Manifest-Classpath-tf2504507.html#a7016303
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e
SingleShot wrote:
I am building an executable JAR that depends on a handful of other JARs and a
few config files being on the classpath. I want the config files to be
editable by the end user, so did not add them as internal JAR resources.
I've configured the maven-jar-plugin to generate
files being on the classpath. I want the config files to be
editable by the end user, so did not add them as internal JAR resources.
I've configured the maven-jar-plugin to generate a manifest and add the
dependencies to its classpath (and create a mainclass entry), but cannot
figure out how
SingleShot wrote:
Is it possible to add a directory to the classpath of a Maven-generated
Manifest?
In theory, yes:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-jar-plugin/artifactId
configuration
archive
manifest
Hi,
I would like to use mapper regexp with ant but we must add
ant-apache-jarkarta.jar and ant-apache-jarkata-oro into the ant classpath.
I'v tried to add them to the antrun plugin classpath like this :
plugin
groupIdorg.apache.maven.plugins/groupId
Goeschl
Elid OR wrote:
Hi,
I would like to use mapper regexp with ant but we must add
ant-apache-jarkarta.jar and ant-apache-jarkata-oro into the ant classpath.
I'v tried to add them to the antrun plugin classpath like this :
plugin
groupIdorg.apache.maven.plugins/groupId
you for your response !
Elid
-Original Message-
From: Siegfried Goeschl [mailto:[EMAIL PROTECTED]
Sent: Wed 10/25/2006 2:07 PM
To: Maven Users List
Cc:
Subject:Re: [m2/ant] How to add jar to Ant root classpath with AntRun
plugin ?
Hi Elid,
the message
Deleting .project backup
del .project_backup
Best regards,
Eric
-Ursprüngliche Nachricht-
Von: James Mitchell [mailto:[EMAIL PROTECTED]
Gesendet: Samstag, 21. Oktober 2006 08:42
An: Maven Users List
Betreff: Re: AW: Create only .classpath with eclipse:eclipse?
I see. Well, I suppose you
behind us and what lies in front of us is of little concern to
what lies within us. -Ralph Waldo Emerson
--
View this message in context:
http://www.nabble.com/Malformed-manifest-classpath-entry-tf2497595.html#a7001669
Sent from the Maven - Users mailing list archive at Nabble.com
in context:
http://www.nabble.com/Add-Directory-to-Jar-Manifest-Classpath-tf2504507.html#a7001786
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail
to
what lies within us. -Ralph Waldo Emerson
--
View this message in context:
http://www.nabble.com/Malformed-manifest-classpath-entry-tf2497595.html#a7001669
Sent from the Maven - Users mailing list archive at Nabble.com
this message in context:
http://www.nabble.com/Malformed-manifest-classpath-entry-tf2497595.html#a7002290
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
to exclude transitive dependencies
would be a good idea. You could override it on a per-dependency basis.
Paul
--
View this message in context:
http://www.nabble.com/Malformed-manifest-classpath-entry-tf2497595.html#a7002290
Sent from the Maven - Users mailing list archive at Nabble.com
I agree that it is ugly, but the Jar Specification requires the
wrapping, see Line length in this section:
http://java.sun.com/j2se/1.3/docs/guide/jar/jar.html#Notes%20on%20Manifest%20and%20Signature%20Files
The plugin is doing the right thing.
-Max
pjungwir wrote:
Yeah, I wish maven
Glassfish's application verifier (SJAS 9.1) actually complains about
any Class-Path entry in your EAR MANIFEST... Apparently the most
recent J2EE spec disallows this, haven't looked into it much myself,
we're finally targeting JEE5 for our next release so I'm sure I'll
learn a lot of new things.
Wayne, that seems like a different error. You shouldn't have Class-Path
entries in the EAR's manifest (including Java EE 1.4) These entries belong
in the modules within the ear, i.e. the EJB JAR's, etc.
Though Max is technically right, its still ugly!!! :D!
Alex
On 10/25/06, Wayne Fay [EMAIL
Ok, I'll do it, as soon as I find a bit more time :-)
Best regards,
Eric
-Ursprüngliche Nachricht-
Von: Wayne Fay [mailto:[EMAIL PROTECTED]
Gesendet: Montag, 23. Oktober 2006 20:40
An: Maven Users List
Betreff: Re: AW: Create only .classpath with eclipse:eclipse?
Write the code
Hello - I am getting started with Maven. I am looking at online guides and
literature, and I'm trying to not be retarded
All I want to do is somehow point to a directory of jar files (./lib) and
add these to the classpath so I can compile my code in maven.
I can see that there's this idea
PROTECTED]
Sent: Tuesday, October 24, 2006 11:54 AM
To: users@maven.apache.org
Subject: Maven Noobie - How can I just add a directory of jars to my
classpath?
Hello - I am getting started with Maven. I am looking at online guides and
literature, and I'm trying to not be retarded
All I want to do
I am building an executable JAR that depends on a handful of other JARs and a
few config files being on the classpath. I want the config files to be
editable by the end user, so did not add them as internal JAR resources.
I've configured the maven-jar-plugin to generate a manifest and add
:[EMAIL PROTECTED]
Gesendet: Samstag, 21. Oktober 2006 08:42
An: Maven Users List
Betreff: Re: AW: Create only .classpath with eclipse:eclipse?
I see. Well, I suppose you could keep a backup copy and just
overwrite the incorrectly gen'd one every time, but that would be
frustrating I'm sure.
I
[mailto:[EMAIL PROTECTED]
Gesendet: Samstag, 21. Oktober 2006 08:42
An: Maven Users List
Betreff: Re: AW: Create only .classpath with eclipse:eclipse?
I see. Well, I suppose you could keep a backup copy and just
overwrite the incorrectly gen'd one every time, but that would be
frustrating I'm sure
Hello,
I just finished a launch4j plugin. You can find info on it here:
http://9stmaryrd.com/tools/launch4j-maven-plugin/
Paul
--
View this message in context:
http://www.nabble.com/-M2--Ant-based-plugin-and-target-classpath-tf2485665.html#a6960634
Sent from the Maven - Users mailing list
a launch4j plugin. You can find info on it here:
http://9stmaryrd.com/tools/launch4j-maven-plugin/
Paul
--
View this message in context:
http://www.nabble.com/-M2--Ant-based-plugin-and-target-classpath-tf2485665.html#a6960634
Sent from the Maven - Users mailing list archive at Nabble.com
Hi Everybody,
I did check the email archives on this one and I'm not sure what's what...
If I specify a manifest entry such as:
archive
manifestEntries
Class-Pathlib/some1.jar lib/some2.jar lib/some3.jar lib/some4.jar
lib/some5.jar/Class-Path
/manifestEntries
/archive --
The actual
' or 'additionalBuildcommands' if
I already have a fully working project.
Best regards,
Eric
-Ursprüngliche Nachricht-
Von: James Mitchell [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 20. Oktober 2006 00:56
An: Maven Users List
Betreff: Re: Create only .classpath with eclipse:eclipse?
The eclipse plugin can
That is what i thought. I should not a classpath. Most of my dependencies
are with compile scope and yes i have an ejb jar file that i'm trying to
compile. i cannot send u the exact snippet as i'm on a vacation :). Will get
in touch next week.
thanks.
Scott Ryan-2 wrote:
You should
I'm trying to develop a Launch4j Maven2 plugin by reading this
tutorial:
http://maven.apache.org/guides/plugin/guide-ant-plugin-development.html
Now I have a problem because launch4j uses a custom ant task so I need
to specify a classpath that indicates where to find launch4j.jar
(which I have
Soaring Eagle L.L.C.
[EMAIL PROTECTED]
www.soaringeagleco.com
(303) 263-3044
-Original Message-
From: Dmystery [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 18, 2006 2:39 AM
To: users@maven.apache.org
Subject: [M2]weblogic:appc classpath issue
I'm using weblogic-maven-plugin
:[EMAIL PROTECTED]
Gesendet: Freitag, 20. Oktober 2006 00:56
An: Maven Users List
Betreff: Re: Create only .classpath with eclipse:eclipse?
The eclipse plugin can handle most anything you throw at it. What
specifically is wrong with the output .project file?
What type of project is it? Web Tools
The eclipse plugin can handle most anything you throw at it. What
specifically is wrong with the output .project file?
What type of project is it? Web Tools? MyEclipse? RAD?
--
James Mitchell
678.910.8017
On Oct 19, 2006, at 11:59 AM, Lewis, Eric wrote:
Hi
I'm new to this list,
}-${project.version}.jar/objectPath
verbosetrue/verbose
debuggingtrue/debugging
nowarningsfalse/nowarnings
lineNumberstrue/lineNumbers
keepGeneratedtrue/keepGenerated
classpath${project.runtimeClasspathElements}/classpath
/configuration
executions
execution
I am new to Maven. I am trying to compile commons-discovery with JDK
1.5, but the dependent jars don't seem to be in my classpath. Here is
my pom.xml:
project
modelVersion4.0.0/modelVersion
groupIdorg.apache.commons/groupId
artifactIdcommons-discovery/artifactId
version0.2/version
On 10/18/06, Devine, James [EMAIL PROTECTED] wrote:
I am new to Maven. I am trying to compile commons-discovery with JDK
1.5, but the dependent jars don't seem to be in my classpath. Here is
my pom.xml:
...
scopecompiler/scope
Unless that's a typo, it should either be 'compile' or just
Sorry...that is a typo. I get the same error with compile or no tag.
-Original Message-
From: Wendy Smoak [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 18, 2006 12:57 PM
To: Maven Users List
Subject: Re: Maven 2.0 Classpath Dependency Issue
On 10/18/06, Devine, James [EMAIL
1001 - 1100 of 1706 matches
Mail list logo
