Hi all,
I have a hard time figuring out how provided-scoped dependencies
interact with transitivity; either the documentation or the
maven-dependency-plugin seem to get it wrong.
According to the matrix in
Hi Andreas,
Andreas Sewe wrote:
Hi all,
I have a hard time figuring out how provided-scoped dependencies
interact with transitivity; either the documentation or the
maven-dependency-plugin seem to get it wrong.
According to the matrix in
Hi Jörg,
thanks for the quick reply.
According to the matrix in
http://maven.apache.org/guides/introduction/introduction-to-dependency-
mechanism.html#Dependency_Scope
a provided-scoped dependencies of a provided-scoped project dependency
are themselves of scope provided (w.r.t. the project
Hi Andreas,
Andreas Sewe wrote:
Hi Jörg,
thanks for the quick reply.
According to the matrix in
http://maven.apache.org/guides/introduction/introduction-to-dependency-
mechanism.html#Dependency_Scope
a provided-scoped dependencies of a provided-scoped project dependency
are themselves
I'm considering moving my solution to using the concept of WAR overlays;
a WAR project that requires certain javascripts specifies those as project
dependencies, which themselves are simple WAR projects with only js files in
their correct paths
they get slapped onto the using WARs, and presto, no
On Tue, Jun 15, 2010 at 12:04 PM, Daniele Dellafiore ilde...@gmail.com wrote:
I have patched maven-eclipse-plugin to create an eclipse project also for
projects with pom packaging type.
I was wondering if this was a bug or a feature and if someone is interested
in the plugin behaving this way
Mixed feeling for me.
MultiModule pom project aren't to be imported as a project, I do agree.
But parent kind of pom project, I would like to see them imported. Problem
is that there is no way in maven to make a distinction.
Actually, m-e-p does not create any .project while M2Eclipse import
I'm having some problems making unpack-dependencies work right. It
seems that no matter what I put for includeGroupId and includeArtifactId
it always unpacks all dependencies instead of only those that I want.
I was looking through jira to see if anyone else had this problem and
found something
Actually, m-e-p does not create any .project while M2Eclipse import both of
them... and the multi-module is useless and I will just delete it.
IMO you are better off just switching over to m2eclipse full time
instead of continuing to fight with m-e-p.
Wayne
I'm experiencing a strange issue and discrepancy with Maven 2.2.1 and
the m2eclipse plugin.
This artifact:
org.hsqldb:hsqldb-j5:2.0.0:jar
has a pom in repo1.maven.org which does not have a defined artifactId.
The m2eclipse plugin successfully resolves the artifact and downloaded
it
Oh no... It seems to be a new artifact as well. I thought there were rules
in place that would prevent this from happening.
Could you please file a jira about this at
http://jira.codehaus.org/browse/MEV
/Anders
On Wed, Jun 16, 2010 at 21:54, Stopp, Bryan bryan.st...@argushealth.comwrote:
I'm
This artifact:
org.hsqldb:hsqldb-j5:2.0.0:jar
has a pom in repo1.maven.org which does not have a defined artifactId.
In all likelihood, this artifact did not come through a forge that
would have vetted the data but instead was merely rsync'ed with the
hsqdldb repo, or something. For reasons
On Wed, Jun 16, 2010 at 3:54 PM, Stopp, Bryan
bryan.st...@argushealth.com wrote:
I'm experiencing a strange issue and discrepancy with Maven 2.2.1 and
the m2eclipse plugin.
This artifact:
org.hsqldb:hsqldb-j5:2.0.0:jar
has a pom in repo1.maven.org which does not have a defined artifactId.
I removed them so they can put the right things in place. To Maven, POMs that
don't validate are equivalent to no POMs anyway. I kept the JARs in place
despite them being removed in the source repository.
Yes, they should be using a system that checks for them instead of copying them
blind.
-
Eric,
The properties you should use are includeGroupIds [1] and
includeArtifactIds [2]. The POM file you provided does not pluralize
those properties.
[1]
http://maven.apache.org/plugins/maven-dependency-plugin/unpack-dependenc
ies-mojo.html#excludeGroupIds
[2]
From: Haszlakiewicz, Eric [mailto:ehas...@transunion.com]
Sent: Thursday, June 03, 2010 12:26 PM
I'm trying to turn on useStrictFiltering in a fileSet in an assembly
descriptor, but maven doesn't fail when the file does not exist. Here
I just created a bug for this problem:
On 15/06/2010 9:04 AM, Eric Rotick wrote:
All good advice but my feeling is that is all comes down to one basic rule;
if it can go wrong, it will.
Yes but it your systems should reduce the chance of it getting worse. A
lot of cached releases in local Maven repos that are incorrect will
On 15/06/2010 9:04 AM, Eric Rotick wrote:
All good advice but my feeling is that is all comes down to one basic rule;
if it can go wrong, it will.
We've all been there; the code's written, the documentation's done and it's
just about to go out the door when someone spots something. The project
18 matches
Mail list logo
