/trunk/jetjwis/jbi/jmbl-xslt/target/classes/
To me this is a critical bug that would almost certainly cause every
projects unit tests that access test resources to fail.
--
View this message in context:
http://www.nabble.com/Test-classpath-issue-with-v2.0.8-and-v2.0.9
/workspace/checkout/weather/trunk/jetjwis/jbi/jmbl-xslt/target/classes/
To me this is a critical bug that would almost certainly cause every
projects unit tests that access test resources to fail.
--
View this message in context:
http://www.nabble.com/Test-classpath-issue-with-v2.0.8
in the plugin but my question is not about ensuring
that the plugin's dependencies are on the runtime classpath of the
jvm. I understand how to do this using the
${plugin.getDependencyPath()} call.
The purpose of the plugin is to create a file for the distribution -
essentially metadata for the app
hi,
i got problems with the classpath entries MANIFEST.MF. some classes cannot
be found, though they exist as entry in MANIFEST.MF. weird thing is, that
some jars are included correctly (i get some basic startup, which needs some
dependency jars, but in the end all crashes).
startup, which
aldana schrieb:
hi,
i got problems with the classpath entries MANIFEST.MF. some classes cannot
be found, though they exist as entry in MANIFEST.MF. weird thing is, that
some jars are included correctly (i get some basic startup, which needs some
dependency jars, but in the end all crashes
://www.aldana-online.de
--
View this message in context:
http://www.nabble.com/classpath-entries-in-maven-archiver-generated-MANIFEST.MF-cannot-be-referenced-tp17229567p17230602.html
Sent from the Maven - Users mailing list archive at Nabble.com
i tried different things and my guess is that the problems occur because the
problematic module is a webapplication running in the lightweight jetty
container. it seems that the jetty-classloader cannot cope with some
classpath entries. all other non-webapp components i am using
:
http://www.nabble.com/Modify-Classpath-tp17215208p17236473.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]
/com.ibm.ws.ast.st.runtime.runtimeTarget.v61/was.base.v61
/classpathContainer
classpathContainerorg.eclipse.jst.j2ee.internal.module.container/
classpathContainer
/classpathContainers
running mvn eclipse:eclipse will generate the appriate .classpath file:
classpath
classpathentry kind=src path=src/main/java/
classpathentry
I have written a custom Java rule. I'm now trying to make it run inside
mvn.
One project builds the rule, the others run PMD with it.
To code the rule to begin with, I added a POM dependency for the pmd/pmd
artifact, version 4.2. At runtime, I get a failure complaining that I'm
trying to
as jars
are indeed on my classpath when I run maven exec. But dependencies on the
artifacts packaged as wars are not resolved in such a way that classes
directory inside these wars are put on the classpath. I do not want to
explicitly specify a classpath in the configuration of maven exec plugin.
Instead
Have a look at the build-classpath goal of the dependency plugin:
http://maven.apache.org/plugins/maven-dependency-plugin/build-classpath-mojo.html
-Olivier
On Tue, 2008-05-13 at 11:23 -0700, vicki wrote:
Hello,
I have a maven's subproject that runs tests against the artifacts of its
piers
Olivier, thank you very much for the advice. Unfortunately, my quick test of
build-classpath did did not solve my runtime classpath problem. First of
all, the examples of the build-classpath goal that I saw, show how to output
the project's classpath to a file. What I need is to add project
my tests with maven's exec plugin. All the artifacts packaged as jars
are indeed on my classpath when I run maven exec. But dependencies on the
artifacts packaged as wars are not resolved in such a way that classes
directory inside these wars are put on the classpath.
Java simply has
on the artifacts produced by the other subprojects.
I run my tests with maven's exec plugin. All the artifacts packaged as
jars are indeed on my classpath when I run maven exec. But dependencies
on the artifacts packaged as wars are not resolved in such a way that
classes directory inside these wars
: Modify Classpath
Olivier, thank you very much for the advice. Unfortunately, my quick
test of
build-classpath did did not solve my runtime classpath problem. First of
all, the examples of the build-classpath goal that I saw, show how to
output
the project's classpath to a file. What I need is to add
in my particular case i needed the code for integration tests so was
borderline as to whether the artifact was actually separate or not...
but in general i would agree
On Wed, 14 May 2008 12:02:13 Brian E. Fox wrote:
If you have classes that you need outside a war, the correct way is to
make
plugin 2.0 : ClassPath in manifest
I'm not real familiar with that part of maven, but ...
Did you try adding a finalName to the pom for test to give it the name
without the version number included?
Alternatively, there might be a problem inheriting the dependency plugin
configurations in the toto
Jar plugin 2.0 : ClassPath in manifest
Thanks for replying :)
I've tried to put finalName to the pom for test, it didn't change anything. I
ve check the exported-pom and indeed the tag was already set to
finalName${artifactId}finalName even without adding your suggestion (it
inherits that part
Clicked on send before pasting the link:
http://jira.codehaus.org/browse/MJAR-61
Tomas Darbois
-Message d'origine-
De : Thomas Darbois
Envoyé : mercredi 23 avril 2008 11:00
À : 'Maven Users List'
Objet : RE: Maven Jar plugin 2.0 : ClassPath in manifest
Well i ve found the Jira
Hello
I'm having trouble with a multi module project that I m working on.
I need a class path inside the manifest of the built jar (plugin maven jar and
configuration addClasspathtrue/addClasspath in my parent pom defined in
pluginManagement).
The classpath is perfectly formatted when I'm
with a multi module project that I m working on.
I need a class path inside the manifest of the built jar (plugin maven jar
and configuration addClasspathtrue/addClasspath in my parent pom defined
in pluginManagement).
The classpath is perfectly formatted when I'm running the project from
files ). I also tried
another .jar file for a commercial product ( p6spy ) and am getting the same
problems: class not found errors.
Thanks if you have any ideas!
Isaac
--
View this message in context:
http://www.nabble.com/locally-installed-jars-are-not-found-in-classpath-tp16786887s177p16786887
for a commercial product ( p6spy ) and am getting the same
problems: class not found errors.
Thanks if you have any ideas!
Isaac
--
View this message in context:
http://www.nabble.com/locally-installed-jars-are-not-found-in-classpath-tp16786887s177p16786887.html
Sent from the Maven
nicolas de loof-3 wrote:
Could you create a Jira issue for this ?
You can find the issue here: http://jira.codehaus.org/browse/MECLIPSE-437
Greets
Patrick
--
View this message in context:
http://www.nabble.com/Maven2-Eclipse-Plugin---ordering-of-.classpath-entries
Hello
I'm having trouble with a multi module project that I m working on.
I need a class path inside the manifest of the built jar (plugin maven jar and
configuration addClasspathtrue/addClasspath in my parent pom defined in
pluginmanagement).
The classpath is perfectly formatted when I'm
Hello,
in a plugin, you can get the classpath like this:
/**
* The project we are dealing with.
* @parameter expression=${project}
*/
private MavenProject m_project;
ListString classPath = m_project.getRuntimeClasspathElements();
Greetings,
David
-Original Message-
From: Eric
Hi everybody,
I am using Maven2 with the Maven2 Eclipse plugin and in my project I would
like to use a newer version of JaxWS (https://jax-ws.dev.java.net/) than the
one supplied with JDK6. When using the eclipse goal ($ mvn eclipse:eclipse)
the generated .classpath file in my project directory
I get a similar issue, but using StandardVMType/J2SE-1.5 as JRE container
on a JDK 6.0
This creates (unmodifiable) allowed/forbidden acces rules on eclipse
classpath. As the JRE is first in library ordering, I cannot include jax-ws
API that is allways resolved as forbidden.
Having any hook
I'm doing a demo app using JUnit 4 and Spring annotations and having
some trouble getting maven to run my tests. They launch and run
correctly in eclipse, but mvn test cannot find my xml context files
because they're not on the classpath (they're in /webapp/WEB-INF/) and
my JUnit test
in eclipse, but mvn test cannot find my xml context files
because they're not on the classpath (they're in /webapp/WEB-INF/)
and my JUnit test is using @ContextConfiguration(locations = { /
todo-application-context.xml, /todo-data.xml }). I saw
maven.plugin.classpath and maven.test.classpath (though
://www.nabble.com/classpath-property-tp16706768s177p16706768.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]
Hello,
I am trying to specify the Sure Fire additionalClasspathElements
Additional elements to be appended to the classpath. and being a
Maven2 newbe I am a bit lost when I'm told to set the plugin values as
a java.util.List.
=== FROM: http://maven.apache.org/plugins/maven-surefire-plugin/test
On Monday 07 April 2008 Andreas Guther wrote:
We see a difference in classpath loading between Surefire 2.3 and 2.4.
Search the archive of this list on nabble.com for surefire 2.4 classpath
and you'll find your answer. Note, that there was a bug in maven 2.0.7, so
updating to a newer maven
another article about classpath ordering (not relevant
to you, but it has come up a few times):
http://docs.codehaus.org/display/MAVENUSER/Classpath+Ordering+Bugs+in+Maven+Surefire
-Dan
-
To unsubscribe, e-mail: [EMAIL PROTECTED
that this was the default behavior in
Surefire 2.3 and that it was reversed in Surefire 2.4.
-Original Message-
From: Andreas Guther [mailto:[EMAIL PROTECTED]
Sent: Monday, April 07, 2008 12:07 PM
To: Maven Users List
Subject: Classpath Loader Differences between Surefire 2.3 and 2.4
causes tests to fail
Hi,
We see a difference in classpath loading between Surefire 2.3 and 2.4.
If we run the attached test against Surefire 2.3 and TestNG 5.1 we get
the following output:
mvn test -Pthree
---
T E S T S
/dependency
!-- The java sources must be in the
classpath --
!-- Group id and artifact id are not
important --
!-- ${project.build.sourceDirectory}
is unknown here
Hi Nicolas,
We're already using the gwt-maven-plugin (perhaps the issue your talking
about is a classpath too long problem, comming from my colleague ;-)).
But an important improvement for us would be a plugin launching the GWT
compilation only if there are changes in java source code
Can anyone tell me the best way to get the project classpath from with
a plug-in including transitive dependencies?
I've tried mavenProject.getCompileClasspath() but it doesn't seem to
have the transitive deps
Some problem with mavenProject.getDependencies()
I think I need
me the best way to get the project classpath from with
a plug-in including transitive dependencies?
I've tried mavenProject.getCompileClasspath() but it doesn't seem to
have the transitive deps
Some problem with mavenProject.getDependencies()
I think I need mavenProject.getArtifacts() but how
Hi all,
Using the antrun plugin, I'm trying to call an ant task which is launching
the GWT compiler. This ant task is based on the Joachim work at
http://braindump.dk/tech/gwt-task-for-ant/.
Something specific with GWT is that you must include the java source
directory in your classpath before
directory in your classpath before calling the compiler. Unfortunatelly, I
can add all the needed jars in my classpath (gwt-user.jar,
gwt-dev-windows.jar, my ant-compile.jar ) using dependencies, but I don't
know how to add my source directory.
I tried to build an ant reference classpath
I'd like to change the output directory of the eclipse classpath.
mvn eclipse:eclipse defaults to project/target/classes
Is this possible?
DISCLAIMER: This e-mail is confidential and may also be legally privileged. If
you are not the intended recipient, use of the information contained
Hello,
When I try to create a test-jar that depends of another test-jar
I cant include this second test-jar in the first.
I put the second test-jar in the pom.xml of the first as
typetest-jar/typescopetest/scope but the manifest built by maven do
not
Hi
I managed alter the classpath like this:
classpath./src/main/webapp/WEB-INF/lib/cocoon-2.1.11.jar${path.separator}./src/main/webapp/WEB-INF/lib/avalon-framework-api-4.3.jar/classpath
BIG ISSUE: Now maven cannot find the test-scope jars added
Hi,
I am adding some Unit tests to a legacy application before I make any changes.
As part of the tests I start the application. When the application
starts it scans all the classes on the classpath. Unfortunately the
only jar on the classpath is the classworlds.jar due to the way maven
handles
on the classpath. Unfortunately the
only jar on the classpath is the classworlds.jar due to the way maven
handles dependencies. The application will use a system property
called java.class.path if present. So I have configured the surefire
plugin as shown below.
plugin
application before I make any
changes.
As part of the tests I start the application. When the application
starts it scans all the classes on the classpath. Unfortunately the
only jar on the classpath is the classworlds.jar due to the way maven
handles dependencies. The application
Hi Petr,
I have a default.persistence.properties in the artifact with the EJB3
abstract test case. There I can specify whatever I like. Also, in the
jboss in deploy/ejb3.deployer/META-INF there is another
persistence.properties where I specify the production properties.
Stefan
Petr Nejedly
Hi everybody,
I'm new to maven. I have a simple question that I can't find an answer anywhere:
I want to include additional classes in the classpath while compiling my project
but I can't find any
obvious solution for this.
- The classes I want to include can not be installed in a maven
I had concept/misconception that target/classes gets added to the classpath
by maven as default?
Are you dealing with generated sources?
Regards,
Amit
On Tue, Mar 4, 2008 at 4:34 PM, [EMAIL PROTECTED] wrote:
Hi everybody,
I'm new to maven. I have a simple question that I can't find
[EMAIL PROTECTED] schrieb:
Hi everybody,
I'm new to maven. I have a simple question that I can't find an answer
anywhere:
I want to include additional classes in the classpath while compiling my
project
but I can't find any
obvious solution for this.
- The classes I want to include can
PROTECTED]:
I had concept/misconception that target/classes gets added to the classpath
by maven as default?
Are you dealing with generated sources?
Regards,
Amit
On Tue, Mar 4, 2008 at 4:34 PM, [EMAIL PROTECTED] wrote:
Hi everybody,
I'm new to maven. I have a simple question that I can't
but it
should
be something much simpler I guess?
Thanks
Quoting amit kumar [EMAIL PROTECTED]:
I had concept/misconception that target/classes gets added to the
classpath
by maven as default?
Are you dealing with generated sources?
Regards,
Amit
On Tue, Mar 4, 2008 at 4:34 PM, [EMAIL
Thanks Stefan,
Very helpful. Just a question:
You said you're using only one persistence.xml for both, testing and
live deployment. How do you specify different Hibernate properties for
those, eg dialect (Oracle vs HSQLDB), auto create schema (on vs off),
etc?
Cheers, Petr
The
but in this case SureFire can
see all the resource files on its classpath and tries to use them (eg
persistence.xml - tries to deploy test AND live persistence units which
fails the tests).
I kind of hacked it so that I'm able to run tests in one module and
package it. I end up with the following
(-client)) {
myJar = f;
break;
}
}
if (myJar != null) {
appendPathToClasspath(myJar.getAbsolutePath());
} else {
System.err.println(WARNING: JAR could not be found in the
classpath
). The classpath for the new JVM needs jar files which
are defined as test dependencies (derby is available in the form of
maven artifacts, and I want to test it against the same derby version
against which the actual code is written). The problem is that due to
the surefire boot mechanism, it's
25.02.2008 um 20:58 schrieb Alexander Klimetschek:
Hi all,
I have a test case which starts another JVM (a derby database
server in network mode). The classpath for the new JVM needs jar
files which are defined as test dependencies (derby is available
in the form of maven artifacts, and I want
Yes, that client was just because from within an Maven execution the
classpath would give me the -client.jar first, but I needed the jar
without client.
Stefan
Alexander Klimetschek wrote:
Thanks Stefan, nice hack ;-) I didn't know that you can get the Jar file
via the class resource URL
Hi all,
I have a test case which starts another JVM (a derby database server
in network mode). The classpath for the new JVM needs jar files which
are defined as test dependencies (derby is available in the form of
maven artifacts, and I want to test it against the same derby version
behave the same without two different configurations.
Alex
Am 25.02.2008 um 20:58 schrieb Alexander Klimetschek:
Hi all,
I have a test case which starts another JVM (a derby database server
in network mode). The classpath for the new JVM needs jar files
which are defined as test dependencies
I took a copy of the project POM and put it in the surefire-integration-tests
directory. The tests failed. I then trawled through the project POM and then
its parent POM commenting out plugins, reporting, dependencies, and other bits
until the test passed.
The thing that was causing the test
Hi,
Is it possible to add a newly created folder(and its contents) to the
classpath at the runtime(on the fly) using maven.
I am using this pde-maven-plugin where I am copying the dependencies to the
lib folder inside the ${basedir} and wants it to be available while
compiling the source code
Ben Lidgey wrote:
Made the tests pass. I've no idea why. Do you want me to raise this as a
bug?
Yes... nice work! That sounds like a Core bug and not a Surefire bug, so
file it against Maven 2 (MNG) in JIRA.
Thanks!
-Dan
-Original Message-
From: Dan Fabulich [mailto:[EMAIL PROTECTED]
Sent: 18 February 2008 22:23
To: Maven Users List
Subject: RE: Surefire 2.4.1 classpath order
[snip]
Looks like we'll need to try some more debugging. :-)
1) If you run mvn -X you'll see lots of useful debugging
From: Dan Fabulich [mailto:[EMAIL PROTECTED]
2) Try pulling down our classpath-order test project here:
http://svn.apache.org/repos/asf/maven/surefire/trunk/surefire-
integration-tests/src/test/resources/classpath-order
http://tinyurl.com/3csqca
Run mvn test and confirm that you see
-Original Message-
From: Dan Fabulich [mailto:[EMAIL PROTECTED]
Sent: 15 February 2008 22:52
To: Maven Users List
Subject: Re: Surefire 2.4.1 classpath order
Ben Lidgey wrote:
We are running tests using Surefire 2.4.1 and Maven 2.0.8.
[...]
[snip]
I'm not 100% certain you're
; it contains only a META-INF/MANIFEST.MF file,
specifying a Main-Class and a Class-Path to run the code. Make sure that
the manifest looks correct and that the jars/dirs appear in the correct
order.
2) Try pulling down our classpath-order test project here:
http://svn.apache.org/repos/asf/maven/surefire
Dan -
Do you know if that bug was introduced in 2.0.7 (or some other earlier
release)? My team is using 2.0.4 and we encountered a problem with the
classpath ordering recently that caused builds to that were previously
working to suddenly start failing.
Thanks,
Ken
On 2/15/08, Dan Fabulich
is an Improvement and
not a Bug; it was filed in July of 2007, but for all I know Maven has
been behaving the old bad way since 2.0.0.
What's complex about this problem is that the two issues obfuscate each
other. For many users, Maven was trying to use the wrong classpath, but
Surefire was accidentally
loaded.
Looking at the debug output shows:
[DEBUG] Test Classpath :
[DEBUG] C:\Documents and
Settings\benl\.m2\repository\junit\junit\4.2\junit-4.2.jar
[more jars]
[DEBUG] c:\Development\Projects\MyProject\target\classes
[DEBUG] c:\Development\Projects\MyProject\target\test-classes
Which
are expecting to load a properties file from src/test/resources with
the same name as a properties file in src/main/resources to load test data
etc. However the src/main/resources properties file is being loaded.
Looking at the debug output shows:
[DEBUG] Test Classpath :
[DEBUG] C:\Documents
On Today at 4:50pm, ak=amit kumar [EMAIL PROTECTED] wrote:
ak Hi,
ak I have another related query regarding surefire, all of a sudden from
ak today we started getting this error while executing JUnit tasks, the
ak compilation of source file happens fine and the when compiling the
ak test
the
target/test-classes folder is being put on the classpath before my
target/classes folder. My log4j properties and other properties files in
my src/test/resources get moved into the target/test-classes and take
precedence on the classpath.
I really don't even want the test-classes on the classpath
Not sure if this is an eclipse question or a side effect of how maven sets up
a WTP project.
What's happening is when I deploy my project to tomcat under WTP the
target/test-classes folder is being put on the classpath before my
target/classes folder. My log4j properties and other properties
Ben Lidgey wrote:
We are running tests using Surefire 2.4.1 and Maven 2.0.8.
[...]
Looking at the debug output shows:
[DEBUG] Test Classpath :
[DEBUG] C:\Documents and
Settings\benl\.m2\repository\junit\junit\4.2\junit-4.2.jar
[more jars]
[DEBUG] c:\Development\Projects\MyProject
:
*[INFO] Not executing Javadoc as the project is not a Java classpath-capable
package*
I downloaded the source code of maven-javadoc-plugin and added the debug
statement before the above line is printed in this block of code snippet:
ArtifactHandler artifactHandler = project
.getArtifact
, it
always throws me this info without doing anything:
*[INFO] Not executing Javadoc as the project is not a Java
classpath-capable
package*
I downloaded the source code of maven-javadoc-plugin and added the debug
statement before the above line is printed in this block of code
snippet
nicolas de loof wrote:
The ejb plugin has the option to generate the EJB classpath in MANIFEST
based on the declared dependencies
Is there any support in the ear plugin to automagically package thoses
dependencies as jarModules ?
My objective in a probably similar situation was to package
This is allready the case ... sorry for the noise :-/
2008/2/12, nicolas de loof [EMAIL PROTECTED]:
Hello,
The ejb plugin has the option to generate the EJB classpath in MANIFEST
based on the declared dependencies
Is there any support in the ear plugin to automagically package thoses
Hello,
The ejb plugin has the option to generate the EJB classpath in MANIFEST
based on the declared dependencies
Is there any support in the ear plugin to automagically package thoses
dependencies as jarModules ?
Nico.
under Project, it
always throws me this info without doing anything:
*[INFO] Not executing Javadoc as the project is not a Java classpath-capable
package*
I downloaded the source code of maven-javadoc-plugin and added the debug
statement before the above line is printed in this block of code
other jars and
when SurefireBooter starts a new jvm it do not add these to the
classpath. just a few surefire jars are added afaik.
here is the output when i run in debug mode:
Forking command line: java
-javaagent:/home/stalep/.m2/repository/org/jboss/aop/jboss-aop/2.0.0.CR3/jboss-aop-2.0.0.CR3.jar
executions
execution
idclasspath/id
goals
goalbuild-classpath/goal
/goals
configuration
excludeGroupIdscom.eurobase/excludeGroupIds
Is it just printing the classpath instead, or is it not doing anything?
-Original Message-
From: John Coleman [mailto:[EMAIL PROTECTED]
Sent: Friday, February 01, 2008 7:09 AM
To: Maven Users List
Subject: Dependency:build-classpath
I'm trying to use the dependency plugin to record
java.class.path under maven2 won't give you the path for the project
dependencies ... it's different from under maven1
On 1/30/08, Rex Huang [EMAIL PROTECTED] wrote:
the application use System.getProperty(java.class.path) to get
classpath.
Rex
On Jan 30, 2008 10:46 AM, Rex Huang [EMAIL
Hi,
Somehow I managed to get an alpha version in my repos, once I changed
version to specify 2.0, was fine!
Regards,
John
-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED]
Sent: 01 February 2008 14:41
To: Maven Users List
Subject: RE: Dependency:build-classpath
the application use System.getProperty(java.class.path) to get classpath.
Rex
On Jan 30, 2008 10:46 AM, Rex Huang [EMAIL PROTECTED] wrote:
exec-maven-plugin is good, but in my case, the application also run javac
to generate jar file, and it use its classpath instead of dependency
exec-maven-plugin is good, but in my case, the application also run javac to
generate jar file, and it use its classpath instead of dependency
information.
I use java to run it with classpath is ok.
BR//Rex
On Jan 29, 2008 7:53 PM, Wayne Fay [EMAIL PROTECTED] wrote:
The exec-maven-plugin
information as
classpath.
Can this work?
BR//Rex
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
I just give mainclass and parameters information,
then maven runs the mainclass and use dependence artifact information as
classpath.
Can this work?
BR//Rex
is not a Java classpath-capable
package
Thanks
Ryan
The exec-maven-plugin should interest you:
http://mojo.codehaus.org/exec-maven-plugin/usage.html
Wayne
On 1/29/08, Rex Huang [EMAIL PROTECTED] wrote:
I just give mainclass and parameters information,
then maven runs the mainclass and use dependence artifact information as
classpath.
Can
/appassembler-maven-plugin/
Rex Huang wrote:
I just give mainclass and parameters information,
then maven runs the mainclass and use dependence artifact information as
classpath.
Can this work?
BR//Rex
-
To unsubscribe, e-mail
report for
all multiple projects). However, when I run javadoc:jar, it starts
complaining it ...
[INFO] [javadoc:jar]
[INFO] Not executing Javadoc as the project is not a Java classpath-capable
package
Thanks
Ryan
]
[INFO] Building MyProjects POM
[INFO]
[INFO] No goals needed for project - skipping
*[INFO] [javadoc:jar]
[INFO] Not executing Javadoc as the project is not a Java classpath-capable
package
*[INFO
javadoc:jar, it starts
complaining it ...
[INFO] [javadoc:jar]
[INFO] Not executing Javadoc as the project is not a Java
classpath-capable
package
Thanks
Ryan
-
To unsubscribe, e-mail: [EMAIL PROTECTED
I have a multiple module project. Most of the modules package as a jar. I am
trying to run a class using the exec plugin. Here is the command I use (note
it is configured using netbens6)
Executing:C:\Apps\apache-maven-2.0.8\bin\mvn.bat -Dexec.args=full -classpath
-Dexec.mainClass
601 - 700 of 1706 matches
Mail list logo
