Yea.. i think that's the only way,
what i did is to add a script to /etc/profile.d/set_ld_path.sh
with the line: export LD_LIBRARY_PATH=/path/with/the/so/file
so it will work for all users.
Eyal.
On Tue, Apr 13, 2010 at 2:14 PM, Jochen Stiepel j.stie...@gmail.com wrote:
Hi Eydal,
as far
Hi All,
I tried again on Ubuntu Linix and found that it is case-sensitive while on
Windows it is not. I am sorry that I had made a not all-inclusive
conclusion.
Regards,
On Tue, Apr 13, 2010 at 9:23 PM, Garin Yan yangu...@gmail.com wrote:
Hi All,
I tried it on just Windows. Later I will try
Hi,
I'm building a simple archetype that won't have any included Java source code,
but an empty src/main/java folder so that the user has the base structure there
if he has the need to add some java classes later.
But when I tried to create a maven project from the archetype it asked me for a
I am a win32 shell scripting fun!
If anyone know the mailing-list for that technology,
please tell me!
thanks a lot!
_
想知道明天天气如何？必应告诉你！
Hi
I use maven for the creation of my jars and it works very well.
Now I want to create a zip file containing for example 2 jar (these jars are
maven projects having many dependencies ).
To do that, I use maven assembly plugin (i use jar-with-dependencies as
descriptorRef, but in my zip, the
I was trying to use the Assembly plugin to create a zip consisting of
javadoc, source and class jar files. The Maven project consist of multi
module projects.While writing the assembler descriptor I observed that type
for source jar was getting changed depedending on the phases included in
What I see when I deploy a business model to be used by other components, is
that install is run before deploy. This is quite logical and the deploy then
uploads the artifact to Nexus.
When I then build the other component, the artifact is downloaded from
Nexus. This seems strange to me, since
On Wed, Apr 14, 2010 at 05:11:28AM -0400, Garin Yan wrote:
I tried again on Ubuntu Linix and found that it is case-sensitive while on
Windows it is not. I am sorry that I had made a not all-inclusive
conclusion.
Correct. Most filesystem types on Unix or Linux will be
case-sensitive. NTFS (on
When I then build the other component, the artifact is downloaded from
Nexus. This seems strange to me, since the version in my local repository is
the same as the one in Nexus. If I run an explicit install after the deploy
What version(s) are you working with -- I am guess they're snapshots?
Hello,
I have the issue, that maven does not add the time information of
snapshot artifacts to the class path.
For example
[INFO] [dependency:build-classpath {execution: default-cli}]
[INFO] Dependencies classpath:
/home/xxx/.m2/repository/com/foo/1.0.0-SNAPSHOT/bar-1.0.0-SNAPSHOT.jar
Wayne Fay wrote:
What version(s) are you working with -- I am guess they're snapshots?
Maven 3 alpha 5 I believe. Yes, they are snapshots.
--
View this message in context:
http://old.nabble.com/install-after-deploy--tp28243701p28244155.html
Sent from the Maven - Users mailing list
I am attempting to copy the Jar files and source Jar files into a
non-maven project using the copy-dependencies control.
I have tried several different approaches, and none of them seem to
work.
I have a configuration section that looks like this.
configuration
Maven 3 alpha 5 I believe. Yes, they are snapshots.
What does your repo declaration look like in settings.xml? I'm
guessing you've got an always in the updatePolicy field.
http://maven.apache.org/settings.html
Wayne
-
To
On Wed, Apr 14, 2010 at 11:24 AM, tbee t...@tbee.org wrote:
Maven 3 alpha 5 I believe. Yes, they are snapshots.
Sounds like http://jira.codehaus.org/browse/MNG-4281 (supposed to be
fixed though).
JIRA is down but Google has it cached:
Wayne Fay wrote:
What does your repo declaration look like in settings.xml? I'm
guessing you've got an always in the updatePolicy field.
Nope, just id, user and password.
I do use -U (if the repository can be pinged) so snapshots are always
checked, but that does not change that once
On 2010-04-13 20:53, Shahzad Bhatti wrote:
I have a project that builds a war file using Maven 2.2. I would like to
serve jnlp file that can be used to start an application remotely using Java
Web Start. I need to do following things:
1. Sign the project jar file as well as all dependent
Thanks Dennis, I will give it a try.
On 4/14/10 10:42 AM, Dennis Lundberg denn...@apache.org wrote:
On 2010-04-13 20:53, Shahzad Bhatti wrote:
I have a project that builds a war file using Maven 2.2. I would like to
serve jnlp file that can be used to start an application remotely using Java
You do know that you can use -f and name it whatever you want? (though
I don't know about module for that)
On Wed, Apr 14, 2010 at 10:57 AM, Mark H. Wood mw...@iupui.edu wrote:
On Wed, Apr 14, 2010 at 05:11:28AM -0400, Garin Yan wrote:
I tried again on Ubuntu Linix and found that it is
I'm working on making the grizzly deployments actually work with maven
(currently we have an involved set of instructions due, in part, to java.net's
wonderous performance but that's a rant for another time). Given this pom:
On Wed, Apr 14, 2010 at 2:06 PM, Justin Lee evancho...@gmail.com wrote:
I'm working on making the grizzly deployments actually work with maven
[INFO] The version could not be updated: ${grizzly-version}
The problem, it seems, is that we use the property grizzly-version defined
in the root pom
I thought about that (and I plan on moving all our deps to that -- the
current set up is a mess) but it seems a bit of an antipattern to have to
specify intra-project dependencies like that. Seems overly redundant.
On Wed, Apr 14, 2010 at 5:30 PM, Kalle Korhonen
kalle.o.korho...@gmail.comwrote:
I keep forgetting those links need passwords. you can
https://guest:@grizzly.dev.java.net/svn/grizzly/trunk/code/modules/utils/pom.xmland
https://guest:@grizzly.dev.java.net/svn/grizzly/trunk/code/pom.xml instead.
On Wed, Apr 14, 2010 at 5:06 PM, Justin Lee evancho...@gmail.com wrote:
I'm
That's the best practice. Read about it if you don't believe me.
Kalle
On Wed, Apr 14, 2010 at 2:32 PM, Justin Lee evancho...@gmail.com wrote:
I thought about that (and I plan on moving all our deps to that -- the
current set up is a mess) but it seems a bit of an antipattern to have to
I don't doubt it. and for external deps, i'm all for it. but for
intra-project dependencies, it's a huge deficiency regardless of best
practice status or not. But if that's the best that maven can do right now
then that's what i'll have to deal with. I'd rather hard code those version
numbers
Well, usually, all the related-by-aggregation submodules have the same
version, so ${project.version} works in the dependencies.
On Wed, Apr 14, 2010 at 5:42 PM, Justin Lee evancho...@gmail.com wrote:
I don't doubt it. and for external deps, i'm all for it. but for
intra-project dependencies,
On Apr 14, 2010, at 2:32 PM, Justin Lee wrote:
I thought about that (and I plan on moving all our deps to that -- the
current set up is a mess) but it seems a bit of an antipattern to have to
specify intra-project dependencies like that. Seems overly redundant.
You don't want us magically
That's a good suggestion. I'll try that and see how that works.
On Wed, Apr 14, 2010 at 5:44 PM, Benson Margulies bimargul...@gmail.comwrote:
Well, usually, all the related-by-aggregation submodules have the same
version, so ${project.version} works in the dependencies.
On Wed, Apr 14, 2010
Just look at Maven's POM:
http://svn.apache.org/repos/asf/maven/maven-3/trunk/pom.xml
On Apr 14, 2010, at 2:51 PM, Justin Lee wrote:
That's a good suggestion. I'll try that and see how that works.
On Wed, Apr 14, 2010 at 5:44 PM, Benson Margulies
bimargul...@gmail.comwrote:
Well,
Looks like we have a winner. ${grizzly-version} is redundant anyway.
Replacing it with ${project.version} achieves the same goal and works with
the release plugin. I'll run with that for now. Thanks, everyone.
On Wed, Apr 14, 2010 at 5:51 PM, Justin Lee evancho...@gmail.com wrote:
That's a
Hi folks,
In a clean maven 2.2.1 installation (on Fedora/Linux in this case),
I'm having problems with some dependencies from maven central that
depend on the maven repo at
https://maven-repository.dev.java.net/nonav/repository/.
Steps to reproduce:
1) Rename your ~/.m2 folder to something else
The jar files have a null classifier, so probably what happens is the
field gets set from one execution and not unset in the other. You
could try flipping the order around to see if that helps, or in the
jars config, try setting it to and see if that helps. We need to
trick plexus into injecting
31 matches
Mail list logo
