On Fri, 22 Apr 2005, Brett Porter wrote:
About the resource problem: just add your src/main/resources/ directory
to the runtime classpath in the Run-Run.. - Classpath-tab, then
you should be able to load it using the ClassLoader.getResource();
Though this shouldn't be necessary, since resources
On Thu, 21 Apr 2005, Mykel Alvis wrote:
Total now $0.04:
I totally agree, but since Maven 2 already uses directories with the
version in it's name, it should be possible to store the jar itself
without a version in it's name. The path to the jar already has it's
version in it, so you can still
On 4/22/05, Kenney Westerhof [EMAIL PROTECTED] wrote:
On Thu, 21 Apr 2005, Mykel Alvis wrote:
Total now $0.04:
I totally agree, but since Maven 2 already uses directories with the
version in it's name, it should be possible to store the jar itself
without a version in it's name. The path
Jörg Schaible [EMAIL PROTECTED]
21-04-2005 08:52
Please respond to
Maven Users List users@maven.apache.org
To
Maven Users List users@maven.apache.org
cc
Subject
RE: How would I read a non-standard property file?
Hello,
thanks for the feedback. Will try some proposals and given feedback
Just chiming in for the first time since I started using Maven 1 (Other than
asking new user questions).
I have had a love/hate relationship with Maven ever since I started using it
on a large project integrating the output of 4 different development groups.
One of the things that has
-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
I have a bit of a problem understanding why these 2 (scp and scpexe)
behave so differently. I know the scpexe actually calls the command
while the other runs from java, but with my setup (Fedora Core 3, jdk
1.5, maven 1.0.2), the scpexe takes a very long time to complete, but
works every single
I am glad I started this discussion. I believe it is very useful for
many developers.
I totally agree with arguments for using versions; I like the structure
and discipline, and I agree that
it will reduce the number of errors.
Software vendors like Tibco and Oracle may reconsider their artifact
I am in a quandary.
My junit tests require a database to run.
My hibernate:schema-export task needs to have compiled
java class files to run
My junit tests kick off when I try to compile the java
source files
So there isn't a database for my junit test (or rather
there is an out-of-sync one)
Kenney,
You said But beware, only dependencies with scoperuntime/scope get
included in the classpath..
It really behaves like that, but
1. It creates a problem. If I specify runtime then it does not
compile. I managed to see runtime for the manifest when I compiled
without runtime, then put it in
The problem is that artifacts with the compile scope don't get into
the runtime classpath, so when I use addClasspathtrue/addClasspath,
they do not show up in the manifest.
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Friday, April 22, 2005 5:41 PM
To: Maven
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
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 rather than from the filesystem. For
Wow, the change in sshd_config had no effect (I think Protocol 2,1 is
actually default), but turning on nscd seems to have solved my
problem...
Thanks!
Steve
On Fri, 2005-22-04 at 11:10 -0400, eblack wrote:
It probably has more to do with the authentication method on the server.
Our
On 4/23/05, Ilyevsky, Leonid (Equity Trading) [EMAIL PROTECTED] wrote:
The problem is that artifacts with the compile scope don't get into
the runtime classpath,
I'm pretty sure they do.
so when I use addClasspathtrue/addClasspath,
they do not show up in the manifest.
Ok, there was a bug
phillip rhodes wrote:
I am in a quandary.
My junit tests require a database to run.
My hibernate:schema-export task needs to have compiled
java class files to run
My junit tests kick off when I try to compile the java
source files
So there isn't a database for my junit test (or rather
there is
Steve,
I think the SSH_MSG_DISCONNECT problem can be solved by upgrading the
dependency on jsch.
Cheers,
Brett
On 4/23/05, Steve Molloy [EMAIL PROTECTED] wrote:
Wow, the change in sshd_config had no effect (I think Protocol 2,1 is
actually default), but turning on nscd seems to have solved my
2. It was not meant to be this way, because on
http://maven.apache.org/maven2/dependencies.html it says that with
default compile scope the artifact will be in all classpaths.
correct
So, I suspect it is a bug.
I don't see anywhere in the thread that you describe a bug. What's the
-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
Is there anything in changelog.xml under your target directory?
I got this same issue when I wasn't correct authentication with subversion.
Successful build but no changelog.xml.
On 4/22/05, Paul Roberts [EMAIL PROTECTED] wrote:
The maven-changelog-plugin report is not generating a report for
-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
20 matches
Mail list logo
