-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
No one is saying you have to follow the party line here. You're free to
develop your own maven plugins to solve any problem you like, even run
your toaster if you want. Maven will load your plugin, provided you add
your groupId to the list of
, correct?
|
| Wb
|
|
| On 9/20/05, John Casey [EMAIL PROTECTED] wrote:
|
| I've actually done something just like this in the past, in order to
| call a Make-based build. IMO, you want to wrap a command line call in a
| plugin, to formalize the parameters - required and optional - which
| constitutes
command from their pom.
|
| This is my 1st m2 plugin so if I'm now one of those clueless users, then
| please correct me where I'm wrong.
|
| Wb
| On 9/20/05, John Casey [EMAIL PROTECTED] wrote:
|
|-BEGIN PGP SIGNED MESSAGE-
|Hash: SHA1
|
|
|I guess I don't understand what's wrong
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
it's not a command line execution...it's a java main() call...right?
Trygve Laugstøl wrote:
| On Tue, 2005-09-20 at 13:09 -0500, Wendell Beckwith wrote:
|
|I just re-read you email and I'm confused by your comment, please
clarify if
|possible. But
, I can completely agree with you that
| embedding this stuff in a pom would definitely lead to cut-n-paste code
| which s why I'm actively moving nearly 100 dev's from ant to maven 2
| starting with my project.
|
| Wb
|
| On 9/20/05, John Casey [EMAIL PROTECTED] wrote:
|
| that sounds perfectly
is
dead,
| which is why I want the ability to run this java main() in a separate
| process. Makes sense?
|
| Wb
|
| On 9/20/05, John Casey [EMAIL PROTECTED] wrote:
|
| it's not a command line execution...it's a java main() call...right?
|
| Trygve Laugstøl wrote:
| | On Tue, 2005-09-20 at 13:09
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
any time.
Wendell Beckwith wrote:
| I will look into commons-exec since I wasn't aware of it and thnx for all
| the help.
|
| Wb
|
|
| On 9/20/05, John Casey [EMAIL PROTECTED] wrote:
|
| Ok, fair enough...but the maven process should probably
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
yeah, that looks like it. I wasn't aware of that issue...too new, I guess :)
Thanks, Mark.
john
Mark Hobson wrote:
| Isn't this covered by http://jira.codehaus.org/browse/MNG-932 ?
|
| Mark
|
| On 20/09/05, John Casey [EMAIL PROTECTED] wrote
on top of this, validating it's
usage pattern)
|
| I passed my AntRun plugin to John Casey (one of the Maven gurus), and
| I hope that The Powers That Be will allow it into the HEAD of the SVN
| tree.
|
| Cheers,
| -- Chris
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've implemented a fix that *should* work based on your suggestion
below. However, it will still break for non-Sun, non-Apple JVMs, so I
need to think about fixing it for the long run, and for other JVMs...
Try it now, and let me know.
Thanks,
)
| at org.codehaus.surefire.SurefireBooter.run
| (SurefireBooter.java:73)
| at org.apache.maven.test.SurefirePlugin.execute
| (SurefirePlugin.java:229)
| ... 16 more
|
|
| On 15 Sep 2005, at 20:09, John Casey wrote:
|
| I've implemented a fix that *should* work based on your suggestion
| below. However
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
We've been considering writing a mojo language adaptor for Ant
scripts/scriptlets for awhile now...it's more a matter of available time
than anything else that this hasn't happened yet. I know there are quite
a few people out there who would love to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
First, you'd be well-served to use the svn trunk version for this type
of problem, since you'll have better help for the second thing, which is:
Use profiles.
Inside your pom.xml, you could add the following:
project
~ ...
~ profiles
~
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Comments inline...
Cheers,
john
Ashley Williams wrote:
| I'm glad this is on the cards!
|
| On 14 Sep 2005, at 15:07, John Casey wrote:
|
| We've been considering writing a mojo language adaptor for Ant
| scripts/scriptlets for awhile now...it's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
First, please post this sort of question to the users@ list in future.
I'm CC'ing this message there...
We're working to expand Maven into supporting other languages, but our
original use cases were Java-centric. This means the potential exists
for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark Hobson wrote:
| On 14/09/05, Ashley Williams [EMAIL PROTECTED] wrote:
| [snip]
|
|Well if an ant adapter was worked upon, wouldn't this mean some of
|the existing plugin work is redundant, thus freeing up time? I mean
|fast forward to a time
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Actually, what I'd really like to see in the future is the convergence
of Ant APIs and Maven build process to form one ultra-rich platform for
running builds and developing build plugins. If you still want to run
Ant scripts, you have an optional
through the eclipse plugin a lot more - loads of people use
| Eclipse
|
| What a great story that would be to take onto your random new project.
|
| On 14 Sep 2005, at 17:08, John Casey wrote:
|
| Actually, what I'd really like to see in the future is the convergence
| of Ant APIs and Maven build process
Message-
| From: John Casey [mailto:[EMAIL PROTECTED]
| Sent: Wednesday, September 14, 2005 10:54 AM
| To: Maven Users List
| Subject: Re: [m2] whether to use ant
|
|
| We know that documentation is currently inhibiting adoption of Maven 2,
| to say nothing of attracting developers to do work
Sep 2005, at 19:24, John Casey wrote:
|
| Some of the problems with the eclipse plugin are from an impedance
| mismatch. Eclipse doesn't allow nesting of projects, while that's the
| bread and butter for Maven. Therefore, for Eclipse users (like me), you
| have to sort of graft multiproject support
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
not entirely sure (my maven-1 is a bit rusty...), but try leaving off
the '${basedir}/' prefix for sourceDirectory and unitTestSourceDirectory.
HTH,
john
Qin Ding wrote:
| I am learning to use Maven. Following the tutorial on serverside.com
|
from it because it looked like it was an Alpha.
|
| K.C.
|
| -Original Message-
| From: John Casey [mailto:[EMAIL PROTECTED]
| Sent: Wednesday, September 14, 2005 12:16 PM
| To: Maven Users List
| Subject: Re: How do I package dependent jars in my distribution?
|
|
| you probably want to look
| property
| namemyname/name
| valuemyvalue/value
| /property
| property
| namemyname2/name
| valuemyvalue2/value
| /property
| /properties
|/project
|
|AW
|
|On 13 Sep 2005, at 02:53, John Casey wrote:
|
|
| Actually, no. It's *like* the properties defined
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Actually, no. It's *like* the properties defined in profiles in syntax,
but this is a properties section that is specified as a direct child of
the project element. So:
project
~ ...
~ properties
~namevalue/name
~ /properties
/project
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
If you're deploying a snapshot, you need to define snapshotRepository/
in your distributionManagement/ IIRC. The format is the same as the
repository/ specification in there, but this is meant to support
separate repositories for snapshots vs.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
That's correct. I've added this functionality to my local working copy,
and will commit it as soon as I've verified that it doesn't break the build.
What I'm adding is a properties/ section directly inside the
project/ element. You will then have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It seems to me that there was a JIRA filed for sourceModifications in
m2, but I think it's been pushed for now...maybe until 2.1, I dunno for
sure.
I understand the position you're in, and that you don't really have the
power to dictate a mass
been
added...if not, it's on the list.
John Casey wrote:
| It seems to me that there was a JIRA filed for sourceModifications in
| m2, but I think it's been pushed for now...maybe until 2.1, I dunno for
| sure.
|
| I understand the position you're in, and that you don't really have the
| power
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Comments inline.
Cheers,
john
Ashley Williams wrote:
| Hi John,
|
| Looking forward to the properties code btw
It's in. Good luck! :)
snip/
| I won't lecture you on the ins and outs of modular source trees - I'm
| sure you know already - but I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Can you please file a jira issue for this? It's a bug.
Thanks,
john
Ashley Williams wrote:
| Just ran the install lifecycle against a pom with a made-up name but
| the code eventually looks for a file called pom.xml. Here's the command
| I ran
|
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I think there should already be a JIRA issue for it...it was assigned to
me at one point. :) It's the one about project.getParent().getBasedir()
being the same as project.getBasedir() I think...
- -john
Brett Porter wrote:
| I've filed MNG-805 to
|
|
| On 8/23/05, John Casey [EMAIL PROTECTED] wrote:
|
| Chris,
|
| If you're looking to retrieve only a particular dependency of a plugin
| (the dependencies of the plugin project are what form the plugin's
| classpath), then you might do well to use ${plugin.artifactMap}. This
| Map instance is keyed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
One thing we're considering adding to m2 in the very near term is the
concept of dependencies that are tied directly to a plugin definition.
This is important for several use cases, not the least of which being
the use of non-core ant task libraries.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Berry wrote:
snip/
|One thing we're considering adding to m2 in the very near term is the
|concept of dependencies that are tied directly to a plugin definition.
|
|
| Don't we already have this?? I have dependencies defined for my plugin
|
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
if not there, the source code for parsing the annotations is in
maven-plugin-tools/maven-plugin-tools-java, and the plugin.xml generator
is in maven-plugin-tools/maven-plugin-tools-api.
Let me know if you need more specifics.
- -john
dan tran
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris,
If you're looking to retrieve only a particular dependency of a plugin
(the dependencies of the plugin project are what form the plugin's
classpath), then you might do well to use ${plugin.artifactMap}. This
Map instance is keyed by an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
just FYI, if you don't specify a distributionManagement/ section, you
won't have much luck deploying your project, even accidentally. ;-)
- -john
Scott Goldstein wrote:
| I have a quick newbie question. In Maven 2, from the documention, it
appears
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I *believe* that the test classes/resources are ahead of everything else
on the test classpath, which means that they should be picked up first
on a ClassLoader.getResourceAsStream(..) for instance. At least, that
has always been the case for me.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Actually, no. Mojo.class is an interface, and basically provides the API
that Maven uses to invoke the mojo. Classes that implement Mojo will
have fields marked with @parameter expression=${someExpression} in the
javadocs, which mark that field as a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Can you be a little more specific? I'm assuming you're using Maven
1.x...? Also, which class is it trying unsuccessfully to find?
Without that info, it'll be hard-to-impossible for anyone to help much,
I'm afraid...
- -john
Michael Mattox wrote:
|
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Haven you tried following the suggestions of SVN? Buried in the below
output, it suggests running 'svn cleanup'...did that not help? It looks
like some sort of problem with disk space, or permissions or something
for the svn internal temporary
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
disregard; I hadn't read through enough of my inbox.
John Casey wrote:
| Haven you tried following the suggestions of SVN? Buried in the below
| output, it suggests running 'svn cleanup'...did that not help? It looks
| like some sort of problem
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Surefire is used to setup and run the JUnit tests (I think it's a
replacement for the JUnit test-runner tools, but I'm not sure). The long
and the short of it is that surefire *should* produce the same results
as the m1 junit stuff...
...with the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You should never need to do that in maven2. Instead, you have an option
of defining a hierarchy of poms, and within that hierarchy defining a
set of managed dependencies. This is an important concept, since it
allows you to declare properties
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
solo turn wrote:
snip/
| 'org.apache.maven.plugins:maven-archtype-plugin': Cannot resolve
This appears to be a typo, probably from your command line or from your POM.
It should be maven-archetype-plugin, so if you're invoking directly from
the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
If you didn't find an issue in JIRA related to this, then it's probably
not on our radar for -beta-1. If you'd like, please file a JIRA for
this, and I'll work on it. :)
- -john
John Fallows wrote:
| I seem to remember some brief discussion that it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
when did you svn up? I checked in some changes related to that stuff
yesterday at around 8:00 PM US Eastern time...if you can svn up again
and the build/bootstrap still breaks, can you let me know?
Thanks,
- -john
Rahul wrote:
| Greetings,
|
| For
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
this should be fixed, I think.
John Casey wrote:
| when did you svn up? I checked in some changes related to that stuff
| yesterday at around 8:00 PM US Eastern time...if you can svn up again
| and the build/bootstrap still breaks, can you let me
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm forwarding this to the users' list, since it should have been copied
there in the first place...
- -j
Hi,
This is a bit of a windy email, so please bear with me. There is some
important information in here that may
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I just forwarded a message which I sent to the dev@ list last night
(should have CC'ed here originally). It was related to this issue.
Basically, you need to run:
m2 -U your-goal
The '-U' switch will help with the plugin version problem. Also, at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Unless I'm misreading something, your poms below look good (except you
don't really inherit/ inside pluginManagement/, but that shouldn't
be getting in the way...).
I'm going to put together a test here to see if I can replicate your
problem. I'll
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alright, I've confirmed the bug. Interestingly enough, it works fine
using the assert keyword and source1.4/source...not sure what to
make of that.
I'll file an issue in JIRA, and reply to this email with it's number for
your tracking purposes.
- -j
step is to get it fixed. :)
- -john
John Casey wrote:
Alright, I've confirmed the bug. Interestingly enough, it works fine
using the assert keyword and source1.4/source...not sure what to
make of that.
I'll file an issue in JIRA, and reply to this email with it's number for
your tracking
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
fixed in SVN.
- -j
John Casey wrote:
Alright, I must not have gotten a clean test when trying out a few
different things between straight plugin inheritance and pluginManagement...
I've verified that this is a bug (JIRA: MNG-522) even against
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
just a guess, but try using file:///dev/repository...
Nathaniel Stoddard wrote:
I'm on day one of having Maven build my project, so I really have no
idea what I'm doing! :)
I've created a remote repository on my local drive to hold some JARs
}/lib...that might work.
NOTE: You might want to double-check the versions on the other wagon
libs in there, and match this one up against it. -alpha-4 may not be
right...
HTH,
john
Nathaniel Stoddard wrote:
Unfortunately, that gives me the same error as before.
On 6/16/05, John Casey [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
just as a test, can you try ${salutation} instead? I'm doing some
research into what expression language is enabled by default, but
currently I'm not sure. also, if you want to use OGNL syntax
specifically regardless of the default, you can specify
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
in this case, I think you want something like:
build
sourceDirectorysrc/sourceDirectory
...
/build
to refer maven to ${basedir}/src for your source code...
Joachim Sautter wrote:
My path: src/com/schneide/labras/framework under this there are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
normally you'd use dependencies for this. Have you read the
documentation on http://maven.apache.org and/or
http://maven.apache.org/maven2 ?
I'm not sure what you're trying to do, exactly, but it sounds like these
class files are coming from some
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
for clarity, it should look more like this:
settings
localRepository/opt/develop/m2-repository/localRepository
/settings
- -j
Emmanuel Venisse wrote:
Yes, localRepository is now under settings.
Emmanuel
Anatol Pomozov wrote:
I try to
own
projects.
Thanks for all the good work.
Peter van de Hoef
John Casey wrote:
I'm looking at:
- org.apache.maven.project.inheritance.DefaultModelInheritanceAssembler
- org.apache.maven.project.injection.DefaultModelDefaultsInjector
and here's what I see:
- Combination of inherited
will work to configure the compiler plugin.
Sorry for the confusion, and I'll try not to yell my comments in from
the other room next time. :)
john
John Casey wrote:
I have a refinement or two to this...
Brett Porter wrote:
John has just made a final fix. So, to summarise the behaviour
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
See http://maven.apache.org/maven2/configuration.html about 2/3 of the
way down, in the proxy example. If you look, you should see:
...
nonProxyHostssomething.somewhere.com|somethingelse.nowhere.com|*.suchandsuch.com/nonProxyHosts
...
HTH,
- -john
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
If you can checkout the sources from svn (under
/repos/asf/maven/components/trunk), you should see sandbox/repoclean.
You'll have to have a *nix box, or maybe cygwin to run it currently
(sorry, it's sort of a stop-gap right now).
cd into that
,
Peter van de Hoef
John Casey wrote:
Sorry, I forgot all about the design decisions surrounding this... :)
Actually, our original decision was to disallow inheritance of any
plugin configuration, since plugin configuration can (and usually will)
modify the build lifecycle for that project
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
/plugin
/plugins
/build
/project
Thanks in advance,
Peter van de Hoef
John Casey wrote:
Sorry
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm not 100% sure when I say this, but you should NEVER need to specify
a plugin as a dependency of a project. It will not be bound into the
build lifecycle, and cannot be configured here...in short, it's not seen
as a plugin, but as a compile-, run-,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
have you tried offline mode? just use the '-o' (no quotes) command-line
switch...
- -john
Sebastien Arbogast wrote:
Hi,
I'm building a project using SNAPSHOT dependencies. Those are
downloaded at every build which is fine because I always want
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
We actually have the repositories for plugin download specified
separately in the pom, using the pluginRepositories/ stanza. It looks
similar to (using your original example):
pluginRepositories
repository
idmy_own_repo/id
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sorry, I forgot all about the design decisions surrounding this... :)
Actually, our original decision was to disallow inheritance of any
plugin configuration, since plugin configuration can (and usually will)
modify the build lifecycle for that
wrote:
As this *VITAL* information flies by on the mailing list, is there anyone
updating the docs.
I'd be happy to work up some of it into confluence or some such if that will
help
Matthew
-Original Message-
From: John Casey [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've started writing a large-project management overview, and I'm queued
up on the managedDependencies doc (I have a blog entry waiting to go out
for when it's done ;)
Beyond that, pleased to have the help!
- -john
Brett Porter wrote:
Being
thoughts?
- -john
J. Matthew Pryor wrote:
Tell me when we should take this off-list, but are:
# plugin management
# plugin configuration
safe areas to work? That is the basic topic we were
discussing.
Also what format should I work in?
Cheers,
jmp
--- John Casey [EMAIL PROTECTED
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
One little thing I find annoying is this: I have restructured the layout
of my sources according to the guidelines : resulting the logo of my
app ending up in the directory : src/main/resources, when I compile my
program using maven that is ok
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Craig S.Cottingham wrote:
On Apr 22, 2005, at 12:19, Mykel Alvis wrote:
If the manner of accessing the repository were abstracted, one might
be able
to write a repository manager that would retrieve dependencies
arbitrarily
from a service
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'll add my $0.02:
http://blogs.codehaus.org/people/jdcasey/archives/001053_dependencies_to_version_or_not_to_version.html
Cheers,
- -john
Jason van Zyl wrote:
On Fri, 2005-04-22 at 09:36 +0200, Kenney Westerhof wrote:
On Thu, 21 Apr 2005, Mykel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sorry, when I said to send a message to the users list, I meant to send
it to users@maven.apache.org :) (I talked to you on IRC, I think?)
I'm going to cross-post this, just to see if it conjurs any more help
for you.
HTH,
john
Agustin Ramos
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Leonid,
You would need to add a stanza that looks like this:
servers
server
idlex-deploy/id
usernamesomeuser/username
passwordsomepass/password
/server
/servers
Although if you're deploying to localhost I'm not actually convinced
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Response inline.
Jamie Bisotti wrote:
OK, JIRA issue was rejected; moving to the list. Sorry for the long
post. First...what I think I need:
I'm looking for something like Spring's, PropertyPlaceholderConfigurer
in pom.xml (or any other Maven
impossible than to write a book that wins every reader's
approval. - Miguel de Cervantes
-
-Original Message-
From: John Casey [mailto:[EMAIL PROTECTED]
Sent: Friday, April 08, 2005 3:35 PM
To: Maven Users List
Subject: Re: Maven 2
Hi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
WRT maven plugins, it's a safe assumption that anything under the
grouping maven is a maven-1 plugin, while anything under the grouping
org/apache/maven (repo) or org.apache.maven (POM, etc.) is a maven-2
plugin.
So, the javadoc plugin for maven2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi!
I tried to reply to your query on IRC, but I guess I was too late. So,
I'll re-reply here. :)
Ilyevsky, Leonid (Equity Trading) wrote:
I got maven2 today, and I am eager to start. Two main problems right in
the beginning:
1. Where do I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Just letting you know that the maven-eclipse-plugin for Maven 2.0 is
deployed to ibiblio.org.
To use it, type:
m2 eclipse:eclipse
in the root of your project directory.
HTH,
john
Ilyevsky, Leonid (Equity Trading) wrote:
I got maven2 today, and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dan,
Maven2 won't be able to directly use maven1 repositories, as it is very
much dependent on the POM for each artifact being in the repository, and
in the new maven2 format (the POM format has changed a bit).
HOWEVER... ;)
We are building a
The stuff missing from axis is activation.jar and the mail jar(s) that
AFAIK noone has successfully produced a open source version of.
You might try Tiger jMail (sp?)...anyway the artifact is called tjmail I
believe...
It doesn't have _all_ of the features of Sun's javamail package (some
Maybe it would be easier if you split your RMIC target classes into a
separate project, to be built separately as needed, and include them in
your tests/application as a separate classpath artifact? This would
definitely fit the traditional maven approach more closely. The only
downside I
sounds like you're wanting a sourceModifications stanza...like this:
sourceModifications
sourceModification
classNamesomeClass (can be fake for always modify)/className
excludes
exclude**/MyPattern*.java/exclude
/excludes
/sourceModification
/sourceModifications
See
On the off chance you're trying to sniff the environment and adjust
accordingly, you can try injecting a new sourceModification
programmatically, but you may have to rebuild the
compile.src.set...dunno about that. I believe there is (there used to
be) a driver.jelly in the maven.jar that
be able to choose their own parser without modifying maven script and classpath.
- Original Message -
From: John Casey [EMAIL PROTECTED]
To: Maven Users List [EMAIL PROTECTED]
Sent: Tuesday, October 26, 2004 11:40 PM
Subject: Re: xerces
Yes, maven has an extdir that includes xerces-2.4.0
Yes, maven has an extdir that includes xerces-2.4.0 and xml-apis-1.0-b2.
You should try specifying 'maven.compile.fork=true' in your
project.properties to see whether this helps. It should cause the javac
execution to take place in a new process which is free of the maven
version of xerces et
to relocate the thread to
[EMAIL PROTECTED] (see the project website for subscription
information).
HTH,
John Casey
Colin Chalmers wrote:
Jelly, Marmalade hhmm what's next Jam I guess :-))
Any info on Mamalade? I can't seem to find any, with google.
Colin
Jason van Zyl wrote:
On Thu, 2004-10-07
about this same problem for a while.
Thanks.
-Original Message-
From: John Casey [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 22, 2004 4:38 PM
To: Maven Users List
Subject: Re: Maven/Junit: printing test failure/error stack trace to
stdout
try this:
maven -Djunit.usefile=false
try this:
maven -Djunit.usefile=false test:test
or put the following line in your project.properties file:
junit.usefile=false
HTH,
john
Omair-Inam Abdul-Matin wrote:
Is it possible to print out the stack trace for tests that fail or raise
an error. I would like more details that a failure/error
Maven does not currently handle multiple source directories gracefully.
I think you can add a preGoal of java:compile to your project's
maven.xml, in which you might add your other source directories to
${maven.compile.src.set} (at least, I'm pretty sure that's what the
property is called -
/home/charvey/.maven/cache/maven-nsis-plugin-1.1/META-INF/MANIFEST.MF
Does the /home/charvey/.maven/cache directory exist? You might be able
to rebuild your plugin cache by deleting this directory, and re-running
maven...also, off the top of my head, you might have a privs problem
with
When I run maven jar:install for one particular jar, it installs
a corrupt jar. The jar in target/ is fine. But the one it installs
in the repository is corrupt. I have NO idea what could cause this.
Sorry to be such a bother. Thanks again.
Charlie
John Casey said the following on 8/24/2004 10:45
You might want to try Ant's java task for this. To use it, you should
try embedding in a custom goal within your project's maven.xml file.
I'll look something like this:
project default=dbLoad xmlns:ant=jelly:ant
goal name=dbLoad
ant:java [...options...] classname=com.myco.DbLoader
Message -
From: John Casey [EMAIL PROTECTED]
To: Maven Users List [EMAIL PROTECTED]
Sent: Friday, August 13, 2004 3:21 PM
Subject: Re: A Goal that can execute a class' main method?
You might want to try Ant's java task for this. To use it, you should
try embedding in a custom goal within your
, but I've never actually used it.
Thanks,
David
- Original Message -
From: John Casey [EMAIL PROTECTED]
To: Maven Users List [EMAIL PROTECTED]
Sent: Friday, August 13, 2004 3:49 PM
Subject: Re: A Goal that can execute a class' main method?
1) within the ant:classpath I need to somehow
.
The build cannot continue because of the following unsatisfied dependencies:
threadpool.jar
And in the project.xml:
dependency
groupIdthreadpool/groupId
artifactIdthreadpool/artifactId
version1.0/version
jarthreadpool.jar/jar
/dependency
--
John Casey
[EMAIL
401 - 500 of 565 matches
Mail list logo
