Hi,
I've asked that question before, yet as I didn't get an answer, I'll try
again:
I configured The Eclipse plugin so that it downloads all sources, and adds
them to my eclipse
project configuration, so that I can click on third Party classes in my code
and see it's source code -
that way I
I will be out of the office starting 07/02/2009 and will not return until
07/07/2009.
I will respond to your message when I return.
Important news about email communications:
If our business rules identify sensitive information, you will receive a
ZixMail
The JDK sources are provided as a ZIP with your JDK and should be detetcted
by eclipse when you configure your installed JDK
JEE sources depends on which API you consider. Some recent SUN official Jars
have sources attached in maven repo, some simply are not available de to
licensing restriction.
Hi All,
Could anybody tell me that is there any new plugin released for enhancing the
persistent classes by kodo enhancer like maven-kodo-plugin-4.0.0-EA3 - this one
is compatible with KODO 4.0.1 but we need it for KODO 4.1.4 or KODO 4.2.
Please note, we are using maven 1.0.2.
Warm Regards,
Kai Weber wrote at Mittwoch, 1. Juli 2009 18:23:
Hello all,
if I read the description of the maven-compiler-plugin 2.0.2 every
option is marked deprecated
$ mvn help:describe
-Dplugin=org.apache.maven.plugins:maven-compiler-plugin -Ddetail
...
source
The -source argument
I copied the Maven 2.2 files, all but settings.xml, and got the error
Unable to start the embedded plexus container.
I then rmoved the new files and reverted to the old, and still get the
error, as below.
Any ideas how I should start debugging this? I'ven ot updated my POM in
ages -- it seems
Hi Nick,
Thanks for your reply.
I adjusted the maven goals/options to indeed use mvn clean instal .
The result of this change was ok. All projects are now compiled even if
there are no changes.
However no none of the JUnit tests are being executed.
Normally about 400 JUnit tests are being
Hi,
today I upgraded from Maven 2.1.0 to the recently released 2.2.0. Compiling
projects and deploying them to our internal repository (Nexus 1.3.3) works
as usual and expected ;-)
I just wanted to perform a release for one of my projects, but mvn
release:perform failed after I successfully ran
Hi
I'm having a strange problem which I don't understand.
First of all, I'm using AspectJ (with OVal) to check method parameters. This is
at the moment only done for test code.
Here is my POM:
?xml version=1.0 encoding=UTF-8?
project xmlns=http://maven.apache.org/POM/4.0.0;
Hi Rafael,
When you say it works fine with ant. I guess you mean the sources? Is
already maven packaging all your source into jar? If so, maybe there'd be
something to look after in the packaging phase?
My 2 cents.
2009/7/1 Rafael Felix fe...@serhmatica.com.br
I'm migrating an Ant Swing
2009/7/2 Jörg Schaible joerg.schai...@gmx.de
Kai Weber wrote at Mittwoch, 1. Juli 2009 18:23:
Hello all,
if I read the description of the maven-compiler-plugin 2.0.2 every
option is marked deprecated
$ mvn help:describe
-Dplugin=org.apache.maven.plugins:maven-compiler-plugin
I would like to augment, during the release:prepare phase, the standard
SVN commit message generated by Maven.
Is there a way to do that?
Thanks
Ovidui
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For
See
http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html#scmCommentPrefix
2009/7/2 Ovidiu Feodorov ovi...@novaordis.com:
I would like to augment, during the release:prepare phase, the standard SVN
commit message generated by Maven.
Is there a way to do that?
Thanks
svn-settings
useCygwinPathtrue/useCygwinPath
/svn-settings
[...]
had no effect whatsoever when I first tried it, and then after looking
at
I didn't understand what could prevent your tests from being run, since it's
just automatic and a kind of prerequisite of the install goal (just before
package, actually, you should read
http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html#Build_Lifecycle_Basics
).
I
Thanks for replying.
I've seen that, but I interpreted it as what it says it is: a prefix
for an automatically Maven-generated message.
It seems to (correctly) generate something along the lines of:
[maven-release-plugin] prepare release maven-release-experiment-1.0.1
I was thinking
Hi Ovidiu,
Ovidiu Feodorov wrote at Donnerstag, 2. Juli 2009 16:23:
svn-settings
useCygwinPathtrue/useCygwinPath
/svn-settings
[...]
had no effect whatsoever when I first tried it, and then after looking
at
Jörg Schaible wrote:
So, do you say that Cygwin's svn has a problem if you call it directly on
command line with an absolute path like
svn info /cygpath/c/path/to/managed/source
I can hardly believe this (cannot test it anymore, Windows free zone). The
error above indicates for me that you
Ryan,
Here is what we now have in the pom.xml to deploy large files
distributionManagement
repository
idreleases/id
urldav:http://nexus_server/content/repositories/releases/url
/repository
snapshotRepository
idsnapshots/id
Jörg Schaible wrote:
The absolute paths are on purpose, see
http://jira.codehaus.org/browse/SCM-368.
Can we make this configurable? useRelativePathstrue/useRelativePaths
or similar? I also annotated http://jira.codehaus.org/browse/SCM-368 ...
All my Can we make this ... questions on this
Thanks, Rakesh... I was just about to respond to let you know that I finally
got this worked out this morning. However, in addition to the change in
protocol in our distributionManagement elements I found that I needed to add
the following extensions to my parent pom:
extensions
Ovidiu Feodorov wrote:
Now that I am thinking about it, what would it be really cool was be
to be able to specify something like:
configuration
...
scmCommentTemplatepath_to_template/scmCommentTemplate
/configuration
Hi,
I am new to maven (about 2 hours in), and I am working through a
tutorial that I download here;
http://www.lulu.com/content/1080910
I can run the Hello world app under eclipse.
However I am having a problem that when I run ;
$ mvn -e clean package
I get an error;
Oh, yeah, sorry, now I realize - that's not maven related, as you configure
this once for your entire projects
and not for each project seperately. K, sorry, my mistake, quite confused!
;-)
Ovidiu Feodorov wrote:
Jörg Schaible wrote:
So, do you say that Cygwin's svn has a problem if you call it directly on
command line with an absolute path like
svn info /cygpath/c/path/to/managed/source
I can hardly believe this (cannot test it anymore, Windows free zone).
The error above
Stephen Connolly-2 wrote:
you need to use buildhelper-maven-plugin to attach the generated-sources
directory. Maven does not know that you've generated additional sources.
Most/all of the source generator maven plugins will add the
generated-sources/pluginname folder as an additional
Jörg Schaible wrote:
Ovidiu Feodorov wrote:
Jörg Schaible wrote:
So, do you say that Cygwin's svn has a problem if you call it directly on
command line with an absolute path like
svn info /cygpath/c/path/to/managed/source
I can hardly believe this (cannot test it anymore, Windows
Hi,
As a starter, you should probably upgrade Maven as version 2.0.4 is
VERY old. You can tell from your attached output that there are newer
surefire plugin versions that can't be used with Maven 2.0.4.
Regarding your problem: Try running with -X (debug) instead of -e
and then check the output.
Stephen,
Thank you very much for the detailed answer.
Hung-
Stephen Connolly-2 wrote:
Move the configuration to inside the execution.
The packaging parameter is read-only for install:install but not for
install:install-file... therefore you want your configuration to apply to
the
I have a command that I'm currently running via the exec plugin where I need
to pass in the version number. This works fine if my version number is
something like 1.0.0 but if I'm working from a snapshot, I need it to only
return the actual version (1.0.0) instead of 1.0.0-SNAPSHOT. Is there a
Hi,
Thanks for the reply, I've some comments in-lined below;
On 02/07/09 20:09, Anders Hammar wrote:
Hi,
As a starter, you should probably upgrade Maven as version 2.0.4 is
VERY old. You can tell from your attached output that there are newer
surefire plugin versions that can't be used with
Oh dear, maven seems to be using a different java to my eclipse
installation;
[t...@localhost simple]$
/usr/lib/jvm/java-1.5.0-gcj-1.5.0.0/jre/bin/java -version
java version 1.5.0
gij (GNU libgcj) version 4.4.0 20090506 (Red Hat 4.4.0-4)
Copyright (C) 2007 Free Software Foundation, Inc.
this may help.
http://mojo.codehaus.org/build-helper-maven-plugin/parse-version-mojo.html
-D
On Thu, Jul 2, 2009 at 1:00 PM, Josh McFarlanejosh.mcfarl...@gmail.com wrote:
I have a command that I'm currently running via the exec plugin where I need
to pass in the version number. This works fine
The surefire plugin forks by default. Possibly there is a bug in the
surefire plugin you're using (and you can't upgrade to the newest one
as it requires a newer Maven version than you're using, hence my
upgrade recommendation). I'm thinking that the class path isn't
correctly passed when forking.
On 02/07/09 21:26, Anders Hammar wrote:
The surefire plugin forks by default. Possibly there is a bug in the
surefire plugin you're using (and you can't upgrade to the newest one
as it requires a newer Maven version than you're using, hence my
upgrade recommendation). I'm thinking that the class
That's actually exactly what I was looking for! Thanks!
On Thu, Jul 2, 2009 at 3:26 PM, Dan Tran dant...@gmail.com wrote:
this may help.
http://mojo.codehaus.org/build-helper-maven-plugin/parse-version-mojo.html
-D
On Thu, Jul 2, 2009 at 1:00 PM, Josh McFarlanejosh.mcfarl...@gmail.com
Ovidiu Feodorov wrote:
Jörg Schaible wrote:
[snip]
What's the content
of /cygdrive/c/Users/ovidiu/AppData/Local/Temp/maven-scm-45206-targets ?
I've pasted it in the previous e-mail. I am doing it again here:
Hi,
I have the following setup:
myproject/
- core
- webapp
Now I run jetty:run within the webapp project. Of course I have to
install the core module first.
Is it possible (and how) to force jetty to not use the core jar from the
local repository but something like
Jörg Schaible wrote:
Ovidiu Feodorov wrote:
Jörg Schaible wrote:
[snip]
What's the content
of /cygdrive/c/Users/ovidiu/AppData/Local/Temp/maven-scm-45206-targets ?
I've pasted it in the previous e-mail. I am doing it again here:
Funny story. I tried replacing the Ant task with a Maven plugin, by writing a
RatsMojo class that invokes xtc.parser.Rats directly and replacing the
plugin element above with
plugin
groupIdedu.nyu.xtc/groupId
artifactIdmaven-xtc-plugin/artifactId
executions
execution
Hi everyone...
I have an error with this description... And I'm confused because I run
mvn clean install with SUCCESSFUL result but when I try to run it on the
host of the customer the build fails... And, more rare, fails only with
webapp submodules...
[INFO] Scanning for projects...
[INFO]
i'll preface this with the fact that i'm new to maven and m2eclipse, so
forgive me if i'm being dense,
but i'm just trying to build a java project in eclipse/galileo using the
m2eclipse plugin,
and i'm specifying the dependency:
Code:
dependency
Oh, that would probably be the problem, thanks! I had just taken what
install put in my local repository and uploaded that. I'll see if I
can get deploy to do the right thing, unfortunately my repository (in
Amazon S3) is not writable via any standard protocol.
On Thu, Jul 2, 2009 at 1:46 AM,
43 matches
Mail list logo
