RE: 3.0 Arftifact changes

2010-10-11 Thread Jason Chaffee
Jason -Original Message- From: Brett Porter [mailto:br...@porterclan.net] On Behalf Of Brett Porter Sent: Monday, October 11, 2010 4:17 AM To: Maven Users List Subject: Re: 3.0 Arftifact changes Ok sorry, I wasn't looking closely enough at the error message. ArtifactTransformation has been

Re: 3.0 Arftifact changes

2010-10-11 Thread Brett Porter
gt; [DEBUG] Excluded: org.apache.maven:maven-repository-metadata:jar:2.2.1 > [DEBUG] Excluded: org.apache.maven:maven-artifact:jar:2.2.1 > > > > -Original Message- > From: Brett Porter on behalf of Brett Porter > Sent: Mon 10/11/2010 12:44 AM > To: Maven Users Li

RE: 3.0 Arftifact changes

2010-10-11 Thread Jason Chaffee
:maven-repository-metadata:jar:2.2.1 [DEBUG] Excluded: org.apache.maven:maven-artifact:jar:2.2.1 -Original Message- From: Brett Porter on behalf of Brett Porter Sent: Mon 10/11/2010 12:44 AM To: Maven Users List Subject: Re: 3.0 Arftifact changes On 11/10/2010, at 5:42 PM, Jason Chaffee

Re: 3.0 Arftifact changes

2010-10-11 Thread Brett Porter
On 11/10/2010, at 5:42 PM, Jason Chaffee wrote: > Yes. > > The 2.2.1 is configured in the parent pom dependencyMangement. > > I remember Jason saying talking about the Artifact refactoring about a year > ago and saying it would not be backwards compatible with 2.0 and that if you > had pl

RE: 3.0 Arftifact changes

2010-10-10 Thread Jason Chaffee
. -Original Message- From: Brett Porter on behalf of Brett Porter Sent: Sun 10/10/2010 11:28 PM To: Maven Users List Subject: Re: 3.0 Arftifact changes They should be fine. Just to be clear, they are in the maven-version-plugin-1.0.0.pom, in the local repository? On 11/10/2010, at 4:07 PM

Re: 3.0 Arftifact changes

2010-10-10 Thread Brett Porter
e [mailto:jchaf...@ebates.com] > Sent: Sun 10/10/2010 9:54 PM > To: Maven Users List; Maven Users List > Subject: RE: 3.0 Arftifact changes > > I have these dependencies in my pom: > > > org.apache.maven > maven-model > >

RE: 3.0 Arftifact changes

2010-10-10 Thread Jason Chaffee
I should add that the version on all of these is 2.2.1 -Original Message- From: Jason Chaffee [mailto:jchaf...@ebates.com] Sent: Sun 10/10/2010 9:54 PM To: Maven Users List; Maven Users List Subject: RE: 3.0 Arftifact changes I have these dependencies in my pom

RE: 3.0 Arftifact changes

2010-10-10 Thread Jason Chaffee
maven-artifact -Original Message- From: Brett Porter on behalf of Brett Porter Sent: Sun 10/10/2010 7:36 PM To: Maven Users List Subject: Re: 3.0 Arftifact changes It looks like you were missing a dependency before - there's no dep on maven-artifact or maven-model. Do you have th

Re: 3.0 Arftifact changes

2010-10-10 Thread Brett Porter
lm > ClassRealm[plexus.core, parent: null]] > [ERROR] import: Entry[import org.codehaus.classworlds from realm > ClassRealm[plexus.core, parent: null]] > [ERROR] import: Entry[import org.apache.maven from realm > ClassRealm[plexus.core, parent: null]] > [ERROR] > [ERROR] ----

RE: 3.0 Arftifact changes

2010-10-10 Thread Jason Chaffee
lf of Brett Porter Sent: Sun 10/10/2010 6:40 PM To: Maven Users List Subject: Re: 3.0 Arftifact changes I assume you mean "does not work". These APIs should continue to work without modification, as it's commonly used in other plugins. What's the problem you're see

Re: 3.0 Arftifact changes

2010-10-10 Thread Brett Porter
I assume you mean "does not work". These APIs should continue to work without modification, as it's commonly used in other plugins. What's the problem you're seeing? - Brett On 11/10/2010, at 11:35 AM, Jason Chaffee wrote: > I have a custom plugin that is using the following classes from maven

3.0 Arftifact changes

2010-10-10 Thread Jason Chaffee
I have a custom plugin that is using the following classes from maven 2.x. import org.apache.maven.artifact.Artifact; import org.apache.maven.artifact.repository.ArtifactRepository; import org.apache.maven.artifact.repository.DefaultArtifactRepository; import org.apache.maven.artifact.repository