with the manifestaddClasspath. Or is there
another way of accomplishing the same thing?
-Original Message-
From: Brian Fox [mailto:bri...@infinity.nu]
Sent: Wednesday, August 12, 2009 1:58 PM
To: Maven Users List
Subject: Re: How to add SYSTEM scope dependency to manifest?
System scope
Greetings all,
I'm looking for how to configure the
artifactIdmaven-jar-plugin/artifactId so that dependencies with
scopesystem/scope are included in the class-path of the manifest. I
already am using the addClasspath tag of manifest and that works but
if a dependency is defined as
if a dependency is defined as scopesystem/scope then addClasspath
does not include it in the manifest. I need to include it in the
manifest. Any ideas?
Is there a reason the obvious answer -- change it to a different scope
eg compile -- is not acceptable?
Wayne
an error if
systemPath is set and the scope is not system.
-Original Message-
From: Wayne Fay [mailto:wayne...@gmail.com]
Sent: Wednesday, August 12, 2009 9:46 AM
To: Maven Users List
Subject: Re: How to add SYSTEM scope dependency to manifest?
if a dependency is defined as scopesystem
to pull it from a repository. The m2 plugin for eclipse gives an
error if systemPath is set and the scope is not system.
-Original Message-
From: Wayne Fay [mailto:wayne...@gmail.com]
Sent: Wednesday, August 12, 2009 9:46 AM
To: Maven Users List
Subject: Re: How to add SYSTEM scope
The jar is not in any repository so I read it off of the file
system by setting the dependency to scopesystem
/scope This is the only scope which can read jars
off the file system.
You really must install this jar into a corporate repo (nexus etc) and
then depend on it with proper scopes.
configuration with the manifestaddClasspath. Or is there another way of
accomplishing the same thing?
-Original Message-
From: Brian Fox [mailto:bri...@infinity.nu]
Sent: Wednesday, August 12, 2009 1:58 PM
To: Maven Users List
Subject: Re: How to add SYSTEM scope dependency to manifest
Well, this is a common bad practice to import packages like sun.* or
com.sun.*. PMD has even a standard rule to check this pattern.
This can particularly be a problem when deploying on other JVM than sun's.
But if you really really must have a dependency against this jar, then I
would proceed
I need to reference WSBindingProvider, a class in the standard rt.jar:
package edu.upenn.library.itadd.dla.fedora;
...
import com.sun.xml.internal.ws.developer.WSBindingProvider;
...
WSBindingProvider bp = (WSBindingProvider)port;
...
This builds fine in Eclipse (without maven),
Long shot - I know that newest in /usr/lib/jvm/newest/jdk/jre/lib/rt.jar
suggests it is a JDK6 JDK, but might be worth double-checking on the build
machine, in case a JDK5 slipped in unnoticed (which won't have this class).
I see you've extracted the classes from the JAR, but maybe you did this
-
From: jiangshachina [mailto:[EMAIL PROTECTED]
Sent: Monday, February 26, 2007 6:11 PM
To: users@maven.apache.org
Subject: Re: [m2] system scope dependency
Hello,
All of artifacts would be in repository(local or remote).
That's the standard way on manipulating jars(or other artifacts
: Monday, February 26, 2007 6:11 PM
To: users@maven.apache.org
Subject: Re: [m2] system scope dependency
Hello,
All of artifacts would be in repository(local or remote).
That's the standard way on manipulating jars(or other artifacts) by
Maven.
Deploying artifacts to remote
I read somewhere, system scoped dependencies are not recommended.
Do you have any point or details on that.
Thanks
- Insight Solutions, Inc. at Cisco)
wrote:
I read somewhere, system scoped dependencies are not recommended.
Do you have any point or details on that.
Thanks
--
View this message in context:
http://www.nabble.com/system-scope-dependency-tf3297614s177.html#a9173816
Sent from
26, 2007 6:11 PM
To: users@maven.apache.org
Subject: Re: [m2] system scope dependency
Hello,
All of artifacts would be in repository(local or remote).
That's the standard way on manipulating jars(or other artifacts) by
Maven.
Deploying artifacts to remote repository, then they could be shared
]
Sent: Monday, February 26, 2007 6:11 PM
To: users@maven.apache.org
Subject: Re: [m2] system scope dependency
Hello,
All of artifacts would be in repository(local or remote).
That's the standard way on manipulating jars(or other artifacts) by
Maven.
Deploying artifacts to remote repository
(jpadmana - Insight Solutions, Inc. at Cisco)
wrote:
I read somewhere, system scoped dependencies are not recommended.
Do you have any point or details on that.
Thanks
--
View this message in context:
http://www.nabble.com/system-scope-dependency-tf3297614s177.html#a917381
6
Sent
I have just resolved all my problems using jspc plugin. I report it
here if it can help.
1) about error
file:/myproject/WebContent/WEB-INF/tags/html/attributes.tag(13,7)
lt;%@ tag directive can only be used in a tag file.
I have on my web.xml project lines
jsp-config
...
jsp-property-group
18 matches
Mail list logo