really can run my jar file out of repository.
Any thoughts?
-Original Message-
From: Ilyevsky, Leonid (Equity Trading)
Sent: Friday, April 22, 2005 7:12 PM
To: 'Brett Porter'
Subject: RE: Maven2 jar classpath
Thanks Brett. I will try it Monday (it is time now to go home).
One more related
On 5/5/05, Ilyevsky, Leonid (Equity Trading) [EMAIL PROTECTED] wrote:
I assume I have to wait for the next alpha release to get your fix. For
the time being I am using manifestFile feature.
Correct.
The classpath generated by maven will have
commons-collections-3.1.jar, but it should have
05, 2005 9:06 AM
To: Ilyevsky, Leonid (Equity Trading)
Cc: users@maven.apache.org
Subject: Re: FW: Maven2 jar classpath
On 5/5/05, Ilyevsky, Leonid (Equity Trading) [EMAIL PROTECTED]
wrote:
I assume I have to wait for the next alpha release to get your fix.
For
the time being I am using
to look for the specific version of any package.
-Original Message-
From: Ilyevsky, Leonid (Equity Trading)
Sent: Thursday, May 05, 2005 9:25 AM
To: Brett Porter
Cc: users@maven.apache.org
Subject: RE: FW: Maven2 jar classpath
I think the following workaround is acceptable.
Take
PROTECTED]
Sent: Tuesday, April 19, 2005 10:29 AM
To: Maven Users List
Subject: Re: Maven2 jar classpath
On Tue, 19 Apr 2005, Ilyevsky, Leonid (Equity Trading) wrote:
use this:
build
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-jar-plugin/artifactId
Users List
Subject: Re: Maven2 jar classpath
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
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
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
As my dependency list grows, I would like maven 2 to automatically
generage class path in the manifest from dependency information.
How should I specify it in pom.xml?
If you are not an intended recipient of this e-mail, please notify the
On Tue, 19 Apr 2005, Ilyevsky, Leonid (Equity Trading) wrote:
use this:
build
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-jar-plugin/artifactId
configuration
archive
manifest
addClasspathtrue/addClasspath
environment.
Is there a task in maven2 to automate this?
-Original Message-
From: Kenney Westerhof [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 19, 2005 10:29 AM
To: Maven Users List
Subject: Re: Maven2 jar classpath
On Tue, 19 Apr 2005, Ilyevsky, Leonid (Equity Trading) wrote:
use
you are missing plugins/ to wrap the plugin/ element.
On 4/20/05, Pieter Laeremans [EMAIL PROTECTED] wrote:
When I want to do this I get this:
- Brett
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands,
Brett Porter wrote:
you are missing plugins/ to wrap the plugin/ element.
On 4/20/05, Pieter Laeremans [EMAIL PROTECTED] wrote:
When I want to do this I get this:
- Brett
Inded. The problem is fixed Thanks!
kind regards,
Pieter
-
13 matches
Mail list logo
