Resolving Plugin -SNAPSHOT dependencies from M2 remote repository
|
View:
New views
11 Messages
—
Rating Filter:
Alert me
|
 |
Resolving Plugin -SNAPSHOT dependencies from M2 remote repository
by nick pellow
::
Rate this Message:
Hi,
I'm trying out the nifty new Grails Dependency DSL, as introduced here: http://graemerocher.blogspot.com/2009/09/grails-dependency-resolution-done-right.html . Ivy seems to be having a problem resolving dependencies from our remote maven repository, for -SNAPSHOT versions. Essentially - it looks like Ivy is looking for the -SNAPSHOT.pom, rather than looking up the latestVersion in the maven-metadata.xml . e.g. ==== https://maven.repo.com/private-snapshot: tried https://maven.repo.com/private-snapshot/groupdId/artifactId/1.1.1-SNAPSHOT/artifactId-1.1.1-SNAPSHOT.pom Is there an option available to tell ivy to useMavenMetadata, as there is in the ibiblio resolver? http://ant.apache.org/ivy/history/trunk/resolver/ibiblio.html Cheers, Nick Pellow. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: Resolving Plugin -SNAPSHOT dependencies from M2 remote repository
by nick pellow
::
Rate this Message:
UPDATE: after turning the log level to verbose, I notice this is due
to an authentication error with our maven repository. Ideally - ivy could get these from the ~/.m2/settings.xml file. Has anyone had experience using the Dependency DSL to access artifacts in remote, password protected repositories? Cheers, Nick On 02/11/2009, at 4:23 PM, Nick Pellow wrote: > Hi, > > I'm trying out the nifty new Grails Dependency DSL, as introduced > here: http://graemerocher.blogspot.com/2009/09/grails-dependency-resolution-done-right.html > . > > Ivy seems to be having a problem resolving dependencies from our > remote maven repository, for -SNAPSHOT versions. > > Essentially - it looks like Ivy is looking for the -SNAPSHOT.pom, > rather than looking up the latestVersion in the maven-metadata.xml . > > e.g. > ==== https://maven.repo.com/private-snapshot: tried > > https://maven.repo.com/private-snapshot/groupdId/artifactId/1.1.1-SNAPSHOT/artifactId-1.1.1-SNAPSHOT.pom > > Is there an option available to tell ivy to useMavenMetadata, as > there is in the ibiblio resolver? http://ant.apache.org/ivy/history/trunk/resolver/ibiblio.html > > Cheers, > Nick Pellow. > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: Resolving Plugin -SNAPSHOT dependencies from M2 remote repository
by Graeme Rocher-3
::
Rate this Message:
You could try pass these system properties to Grails:
http://www.mularien.com/blog/2008/01/18/quick-tip-using-an-authenticated-proxy-server-with-ivy/ Since Ivy uses ant for authentication Cheers On Mon, Nov 2, 2009 at 6:39 AM, Nick Pellow <npellow@...> wrote: > UPDATE: after turning the log level to verbose, I notice this is due to an > authentication error with our maven repository. > Ideally - ivy could get these from the ~/.m2/settings.xml file. > Has anyone had experience using the Dependency DSL to access artifacts in > remote, password protected repositories? > > Cheers, > Nick > > > On 02/11/2009, at 4:23 PM, Nick Pellow wrote: > >> Hi, >> >> I'm trying out the nifty new Grails Dependency DSL, as introduced here: >> http://graemerocher.blogspot.com/2009/09/grails-dependency-resolution-done-right.html . >> >> Ivy seems to be having a problem resolving dependencies from our remote >> maven repository, for -SNAPSHOT versions. >> >> Essentially - it looks like Ivy is looking for the -SNAPSHOT.pom, rather >> than looking up the latestVersion in the maven-metadata.xml . >> >> e.g. >> ==== https://maven.repo.com/private-snapshot: tried >> >> >> https://maven.repo.com/private-snapshot/groupdId/artifactId/1.1.1-SNAPSHOT/artifactId-1.1.1-SNAPSHOT.pom >> >> Is there an option available to tell ivy to useMavenMetadata, as there is >> in the ibiblio resolver? >> http://ant.apache.org/ivy/history/trunk/resolver/ibiblio.html >> >> Cheers, >> Nick Pellow. >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > -- Graeme Rocher Head of Grails Development SpringSource - Weapons for the War on Java Complexity http://www.springsource.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: Resolving Plugin -SNAPSHOT dependencies from M2 remote repository
by nick pellow
::
Rate this Message:
Thanks, Graham.
The server needing authentication is our Maven2 repository itself. Essentially - I need to be able to set a credentials element in ivysettings.xml: http://ant.apache.org/ivy/history/latest-milestone/settings/credentials.html Is there a way to do that via the dependency DSL? Or is it possible to specify a ivysettings.xml to use? Cheers, Nick On 02/11/2009, at 7:07 PM, Graeme Rocher wrote: > You could try pass these system properties to Grails: > > http://www.mularien.com/blog/2008/01/18/quick-tip-using-an-authenticated-proxy-server-with-ivy/ > > Since Ivy uses ant for authentication > > Cheers > > On Mon, Nov 2, 2009 at 6:39 AM, Nick Pellow <npellow@...> > wrote: >> UPDATE: after turning the log level to verbose, I notice this is >> due to an >> authentication error with our maven repository. >> Ideally - ivy could get these from the ~/.m2/settings.xml file. >> Has anyone had experience using the Dependency DSL to access >> artifacts in >> remote, password protected repositories? >> >> Cheers, >> Nick >> >> >> On 02/11/2009, at 4:23 PM, Nick Pellow wrote: >> >>> Hi, >>> >>> I'm trying out the nifty new Grails Dependency DSL, as introduced >>> here: >>> http://graemerocher.blogspot.com/2009/09/grails-dependency-resolution-done-right.html >>> . >>> >>> Ivy seems to be having a problem resolving dependencies from our >>> remote >>> maven repository, for -SNAPSHOT versions. >>> >>> Essentially - it looks like Ivy is looking for the -SNAPSHOT.pom, >>> rather >>> than looking up the latestVersion in the maven-metadata.xml . >>> >>> e.g. >>> ==== https://maven.repo.com/private-snapshot: tried >>> >>> >>> https://maven.repo.com/private-snapshot/groupdId/artifactId/1.1.1-SNAPSHOT/artifactId-1.1.1-SNAPSHOT.pom >>> >>> Is there an option available to tell ivy to useMavenMetadata, as >>> there is >>> in the ibiblio resolver? >>> http://ant.apache.org/ivy/history/trunk/resolver/ibiblio.html >>> >>> Cheers, >>> Nick Pellow. >>> >>> --------------------------------------------------------------------- >>> To unsubscribe from this list, please visit: >>> >>> http://xircles.codehaus.org/manage_email >>> >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> >> > > > > -- > Graeme Rocher > Head of Grails Development > SpringSource - Weapons for the War on Java Complexity > http://www.springsource.com > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: Resolving Plugin -SNAPSHOT dependencies from M2 remote repository
by Graeme Rocher-3
::
Rate this Message:
Not at the moment. Please JIRA a fix for 1.2 RC1 and I will get it
done. Think this is pretty important for the release. Cheers On Mon, Nov 2, 2009 at 9:20 AM, Nick Pellow <npellow@...> wrote: > Thanks, Graham. > > The server needing authentication is our Maven2 repository itself. > > Essentially - I need to be able to set a credentials element in > ivysettings.xml: > http://ant.apache.org/ivy/history/latest-milestone/settings/credentials.html > Is there a way to do that via the dependency DSL? Or is it possible to > specify a ivysettings.xml to use? > > Cheers, > Nick > > > On 02/11/2009, at 7:07 PM, Graeme Rocher wrote: > >> You could try pass these system properties to Grails: >> >> >> http://www.mularien.com/blog/2008/01/18/quick-tip-using-an-authenticated-proxy-server-with-ivy/ >> >> Since Ivy uses ant for authentication >> >> Cheers >> >> On Mon, Nov 2, 2009 at 6:39 AM, Nick Pellow <npellow@...> wrote: >>> >>> UPDATE: after turning the log level to verbose, I notice this is due to >>> an >>> authentication error with our maven repository. >>> Ideally - ivy could get these from the ~/.m2/settings.xml file. >>> Has anyone had experience using the Dependency DSL to access artifacts in >>> remote, password protected repositories? >>> >>> Cheers, >>> Nick >>> >>> >>> On 02/11/2009, at 4:23 PM, Nick Pellow wrote: >>> >>>> Hi, >>>> >>>> I'm trying out the nifty new Grails Dependency DSL, as introduced here: >>>> >>>> http://graemerocher.blogspot.com/2009/09/grails-dependency-resolution-done-right.html . >>>> >>>> Ivy seems to be having a problem resolving dependencies from our remote >>>> maven repository, for -SNAPSHOT versions. >>>> >>>> Essentially - it looks like Ivy is looking for the -SNAPSHOT.pom, rather >>>> than looking up the latestVersion in the maven-metadata.xml . >>>> >>>> e.g. >>>> ==== https://maven.repo.com/private-snapshot: tried >>>> >>>> >>>> >>>> https://maven.repo.com/private-snapshot/groupdId/artifactId/1.1.1-SNAPSHOT/artifactId-1.1.1-SNAPSHOT.pom >>>> >>>> Is there an option available to tell ivy to useMavenMetadata, as there >>>> is >>>> in the ibiblio resolver? >>>> http://ant.apache.org/ivy/history/trunk/resolver/ibiblio.html >>>> >>>> Cheers, >>>> Nick Pellow. >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe from this list, please visit: >>>> >>>> http://xircles.codehaus.org/manage_email >>>> >>>> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe from this list, please visit: >>> >>> http://xircles.codehaus.org/manage_email >>> >>> >>> >> >> >> >> -- >> Graeme Rocher >> Head of Grails Development >> SpringSource - Weapons for the War on Java Complexity >> http://www.springsource.com >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > -- Graeme Rocher Head of Grails Development SpringSource - Weapons for the War on Java Complexity http://www.springsource.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: Resolving Plugin -SNAPSHOT dependencies from M2 remote repository
by Graeme Rocher-3
::
Rate this Message:
You might be able to work around it at this point by adding:
org.apache.ivy.util.url.CredentialsStore.INSTANCE.addCredentials(realm, host, userName, passwd); To your BuildConfig.groovy Cheers On Mon, Nov 2, 2009 at 9:39 AM, Graeme Rocher <graeme.rocher@...> wrote: > Not at the moment. Please JIRA a fix for 1.2 RC1 and I will get it > done. Think this is pretty important for the release. > > Cheers > > On Mon, Nov 2, 2009 at 9:20 AM, Nick Pellow <npellow@...> wrote: >> Thanks, Graham. >> >> The server needing authentication is our Maven2 repository itself. >> >> Essentially - I need to be able to set a credentials element in >> ivysettings.xml: >> http://ant.apache.org/ivy/history/latest-milestone/settings/credentials.html >> Is there a way to do that via the dependency DSL? Or is it possible to >> specify a ivysettings.xml to use? >> >> Cheers, >> Nick >> >> >> On 02/11/2009, at 7:07 PM, Graeme Rocher wrote: >> >>> You could try pass these system properties to Grails: >>> >>> >>> http://www.mularien.com/blog/2008/01/18/quick-tip-using-an-authenticated-proxy-server-with-ivy/ >>> >>> Since Ivy uses ant for authentication >>> >>> Cheers >>> >>> On Mon, Nov 2, 2009 at 6:39 AM, Nick Pellow <npellow@...> wrote: >>>> >>>> UPDATE: after turning the log level to verbose, I notice this is due to >>>> an >>>> authentication error with our maven repository. >>>> Ideally - ivy could get these from the ~/.m2/settings.xml file. >>>> Has anyone had experience using the Dependency DSL to access artifacts in >>>> remote, password protected repositories? >>>> >>>> Cheers, >>>> Nick >>>> >>>> >>>> On 02/11/2009, at 4:23 PM, Nick Pellow wrote: >>>> >>>>> Hi, >>>>> >>>>> I'm trying out the nifty new Grails Dependency DSL, as introduced here: >>>>> >>>>> http://graemerocher.blogspot.com/2009/09/grails-dependency-resolution-done-right.html . >>>>> >>>>> Ivy seems to be having a problem resolving dependencies from our remote >>>>> maven repository, for -SNAPSHOT versions. >>>>> >>>>> Essentially - it looks like Ivy is looking for the -SNAPSHOT.pom, rather >>>>> than looking up the latestVersion in the maven-metadata.xml . >>>>> >>>>> e.g. >>>>> ==== https://maven.repo.com/private-snapshot: tried >>>>> >>>>> >>>>> >>>>> https://maven.repo.com/private-snapshot/groupdId/artifactId/1.1.1-SNAPSHOT/artifactId-1.1.1-SNAPSHOT.pom >>>>> >>>>> Is there an option available to tell ivy to useMavenMetadata, as there >>>>> is >>>>> in the ibiblio resolver? >>>>> http://ant.apache.org/ivy/history/trunk/resolver/ibiblio.html >>>>> >>>>> Cheers, >>>>> Nick Pellow. >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe from this list, please visit: >>>>> >>>>> http://xircles.codehaus.org/manage_email >>>>> >>>>> >>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe from this list, please visit: >>>> >>>> http://xircles.codehaus.org/manage_email >>>> >>>> >>>> >>> >>> >>> >>> -- >>> Graeme Rocher >>> Head of Grails Development >>> SpringSource - Weapons for the War on Java Complexity >>> http://www.springsource.com >>> >>> --------------------------------------------------------------------- >>> To unsubscribe from this list, please visit: >>> >>> http://xircles.codehaus.org/manage_email >>> >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> >> > > > > -- > Graeme Rocher > Head of Grails Development > SpringSource - Weapons for the War on Java Complexity > http://www.springsource.com > -- Graeme Rocher Head of Grails Development SpringSource - Weapons for the War on Java Complexity http://www.springsource.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: Resolving Plugin -SNAPSHOT dependencies from M2 remote repository
by nick pellow
::
Rate this Message:
Great - I will give that a go!
Is it possible to define the dependencies outside of the grails-app directory? Since I am writing a plugin - I don't wish the dependency to be resolved again from the grails project. I just want it resolved and packaged into the plugin's lib dir - and then at runtime, have the plugin load it onto the applications classpath. Cheers, Nick On 02/11/2009, at 8:02 PM, Graeme Rocher wrote: > You might be able to work around it at this point by adding: > > org > .apache.ivy.util.url.CredentialsStore.INSTANCE.addCredentials(realm, > host, userName, passwd); > > To your BuildConfig.groovy > > Cheers > > On Mon, Nov 2, 2009 at 9:39 AM, Graeme Rocher > <graeme.rocher@...> wrote: >> Not at the moment. Please JIRA a fix for 1.2 RC1 and I will get it >> done. Think this is pretty important for the release. >> >> Cheers >> >> On Mon, Nov 2, 2009 at 9:20 AM, Nick Pellow <npellow@...> >> wrote: >>> Thanks, Graham. >>> >>> The server needing authentication is our Maven2 repository itself. >>> >>> Essentially - I need to be able to set a credentials element in >>> ivysettings.xml: >>> http://ant.apache.org/ivy/history/latest-milestone/settings/credentials.html >>> Is there a way to do that via the dependency DSL? Or is it >>> possible to >>> specify a ivysettings.xml to use? >>> >>> Cheers, >>> Nick >>> >>> >>> On 02/11/2009, at 7:07 PM, Graeme Rocher wrote: >>> >>>> You could try pass these system properties to Grails: >>>> >>>> >>>> http://www.mularien.com/blog/2008/01/18/quick-tip-using-an-authenticated-proxy-server-with-ivy/ >>>> >>>> Since Ivy uses ant for authentication >>>> >>>> Cheers >>>> >>>> On Mon, Nov 2, 2009 at 6:39 AM, Nick Pellow >>>> <npellow@...> wrote: >>>>> >>>>> UPDATE: after turning the log level to verbose, I notice this is >>>>> due to >>>>> an >>>>> authentication error with our maven repository. >>>>> Ideally - ivy could get these from the ~/.m2/settings.xml file. >>>>> Has anyone had experience using the Dependency DSL to access >>>>> artifacts in >>>>> remote, password protected repositories? >>>>> >>>>> Cheers, >>>>> Nick >>>>> >>>>> >>>>> On 02/11/2009, at 4:23 PM, Nick Pellow wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> I'm trying out the nifty new Grails Dependency DSL, as >>>>>> introduced here: >>>>>> >>>>>> http://graemerocher.blogspot.com/2009/09/grails-dependency-resolution-done-right.html >>>>>> . >>>>>> >>>>>> Ivy seems to be having a problem resolving dependencies from >>>>>> our remote >>>>>> maven repository, for -SNAPSHOT versions. >>>>>> >>>>>> Essentially - it looks like Ivy is looking for the - >>>>>> SNAPSHOT.pom, rather >>>>>> than looking up the latestVersion in the maven-metadata.xml . >>>>>> >>>>>> e.g. >>>>>> ==== https://maven.repo.com/private-snapshot: tried >>>>>> >>>>>> >>>>>> >>>>>> https://maven.repo.com/private-snapshot/groupdId/artifactId/1.1.1-SNAPSHOT/artifactId-1.1.1-SNAPSHOT.pom >>>>>> >>>>>> Is there an option available to tell ivy to useMavenMetadata, >>>>>> as there >>>>>> is >>>>>> in the ibiblio resolver? >>>>>> http://ant.apache.org/ivy/history/trunk/resolver/ibiblio.html >>>>>> >>>>>> Cheers, >>>>>> Nick Pellow. >>>>>> >>>>>> --------------------------------------------------------------------- >>>>>> To unsubscribe from this list, please visit: >>>>>> >>>>>> http://xircles.codehaus.org/manage_email >>>>>> >>>>>> >>>>> >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe from this list, please visit: >>>>> >>>>> http://xircles.codehaus.org/manage_email >>>>> >>>>> >>>>> >>>> >>>> >>>> >>>> -- >>>> Graeme Rocher >>>> Head of Grails Development >>>> SpringSource - Weapons for the War on Java Complexity >>>> http://www.springsource.com >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe from this list, please visit: >>>> >>>> http://xircles.codehaus.org/manage_email >>>> >>>> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe from this list, please visit: >>> >>> http://xircles.codehaus.org/manage_email >>> >>> >>> >> >> >> >> -- >> Graeme Rocher >> Head of Grails Development >> SpringSource - Weapons for the War on Java Complexity >> http://www.springsource.com >> > > > > -- > Graeme Rocher > Head of Grails Development > SpringSource - Weapons for the War on Java Complexity > http://www.springsource.com > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: Resolving Plugin -SNAPSHOT dependencies from M2 remote repository
by Graeme Rocher-3
::
Rate this Message:
On Mon, Nov 2, 2009 at 11:02 AM, Nick Pellow <npellow@...> wrote:
> Great - I will give that a go! > > Is it possible to define the dependencies outside of the grails-app > directory? > Since I am writing a plugin - I don't wish the dependency to be resolved > again from the grails project. > I just want it resolved and packaged into the plugin's lib dir - and then at > runtime, have the plugin load it onto the applications classpath. The plugins BuildConfig.groovy will be packaged with the plugin and then the application will resolve dependencies when the plugin is installed. The only way I know of right now to force packaging of resolved JAR files inside the plugin is to set your target version to 1.1 inside the plugin descriptor: def grailsVersion = "1.1 > *" Cheers > > Cheers, > Nick > > > On 02/11/2009, at 8:02 PM, Graeme Rocher wrote: > >> You might be able to work around it at this point by adding: >> >> org.apache.ivy.util.url.CredentialsStore.INSTANCE.addCredentials(realm, >> host, userName, passwd); >> >> To your BuildConfig.groovy >> >> Cheers >> >> On Mon, Nov 2, 2009 at 9:39 AM, Graeme Rocher >> <graeme.rocher@...> wrote: >>> >>> Not at the moment. Please JIRA a fix for 1.2 RC1 and I will get it >>> done. Think this is pretty important for the release. >>> >>> Cheers >>> >>> On Mon, Nov 2, 2009 at 9:20 AM, Nick Pellow <npellow@...> >>> wrote: >>>> >>>> Thanks, Graham. >>>> >>>> The server needing authentication is our Maven2 repository itself. >>>> >>>> Essentially - I need to be able to set a credentials element in >>>> ivysettings.xml: >>>> >>>> http://ant.apache.org/ivy/history/latest-milestone/settings/credentials.html >>>> Is there a way to do that via the dependency DSL? Or is it possible to >>>> specify a ivysettings.xml to use? >>>> >>>> Cheers, >>>> Nick >>>> >>>> >>>> On 02/11/2009, at 7:07 PM, Graeme Rocher wrote: >>>> >>>>> You could try pass these system properties to Grails: >>>>> >>>>> >>>>> >>>>> http://www.mularien.com/blog/2008/01/18/quick-tip-using-an-authenticated-proxy-server-with-ivy/ >>>>> >>>>> Since Ivy uses ant for authentication >>>>> >>>>> Cheers >>>>> >>>>> On Mon, Nov 2, 2009 at 6:39 AM, Nick Pellow <npellow@...> >>>>> wrote: >>>>>> >>>>>> UPDATE: after turning the log level to verbose, I notice this is due >>>>>> to >>>>>> an >>>>>> authentication error with our maven repository. >>>>>> Ideally - ivy could get these from the ~/.m2/settings.xml file. >>>>>> Has anyone had experience using the Dependency DSL to access artifacts >>>>>> in >>>>>> remote, password protected repositories? >>>>>> >>>>>> Cheers, >>>>>> Nick >>>>>> >>>>>> >>>>>> On 02/11/2009, at 4:23 PM, Nick Pellow wrote: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> I'm trying out the nifty new Grails Dependency DSL, as introduced >>>>>>> here: >>>>>>> >>>>>>> >>>>>>> http://graemerocher.blogspot.com/2009/09/grails-dependency-resolution-done-right.html . >>>>>>> >>>>>>> Ivy seems to be having a problem resolving dependencies from our >>>>>>> remote >>>>>>> maven repository, for -SNAPSHOT versions. >>>>>>> >>>>>>> Essentially - it looks like Ivy is looking for the -SNAPSHOT.pom, >>>>>>> rather >>>>>>> than looking up the latestVersion in the maven-metadata.xml . >>>>>>> >>>>>>> e.g. >>>>>>> ==== https://maven.repo.com/private-snapshot: tried >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> https://maven.repo.com/private-snapshot/groupdId/artifactId/1.1.1-SNAPSHOT/artifactId-1.1.1-SNAPSHOT.pom >>>>>>> >>>>>>> Is there an option available to tell ivy to useMavenMetadata, as >>>>>>> there >>>>>>> is >>>>>>> in the ibiblio resolver? >>>>>>> http://ant.apache.org/ivy/history/trunk/resolver/ibiblio.html >>>>>>> >>>>>>> Cheers, >>>>>>> Nick Pellow. >>>>>>> >>>>>>> --------------------------------------------------------------------- >>>>>>> To unsubscribe from this list, please visit: >>>>>>> >>>>>>> http://xircles.codehaus.org/manage_email >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> --------------------------------------------------------------------- >>>>>> To unsubscribe from this list, please visit: >>>>>> >>>>>> http://xircles.codehaus.org/manage_email >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Graeme Rocher >>>>> Head of Grails Development >>>>> SpringSource - Weapons for the War on Java Complexity >>>>> http://www.springsource.com >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe from this list, please visit: >>>>> >>>>> http://xircles.codehaus.org/manage_email >>>>> >>>>> >>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe from this list, please visit: >>>> >>>> http://xircles.codehaus.org/manage_email >>>> >>>> >>>> >>> >>> >>> >>> -- >>> Graeme Rocher >>> Head of Grails Development >>> SpringSource - Weapons for the War on Java Complexity >>> http://www.springsource.com >>> >> >> >> >> -- >> Graeme Rocher >> Head of Grails Development >> SpringSource - Weapons for the War on Java Complexity >> http://www.springsource.com >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > -- Graeme Rocher Head of Grails Development SpringSource - Weapons for the War on Java Complexity http://www.springsource.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: Resolving Plugin -SNAPSHOT dependencies from M2 remote repository
by nick pellow
::
Rate this Message:
Hi Graeme,
That has done the trick. Cheers, Nick. On 02/11/2009, at 8:02 PM, Graeme Rocher wrote: > You might be able to work around it at this point by adding: > > org > .apache.ivy.util.url.CredentialsStore.INSTANCE.addCredentials(realm, > host, userName, passwd); > > To your BuildConfig.groovy > > Cheers > > On Mon, Nov 2, 2009 at 9:39 AM, Graeme Rocher > <graeme.rocher@...> wrote: >> Not at the moment. Please JIRA a fix for 1.2 RC1 and I will get it >> done. Think this is pretty important for the release. >> >> Cheers >> >> On Mon, Nov 2, 2009 at 9:20 AM, Nick Pellow <npellow@...> >> wrote: >>> Thanks, Graham. >>> >>> The server needing authentication is our Maven2 repository itself. >>> >>> Essentially - I need to be able to set a credentials element in >>> ivysettings.xml: >>> http://ant.apache.org/ivy/history/latest-milestone/settings/credentials.html >>> Is there a way to do that via the dependency DSL? Or is it >>> possible to >>> specify a ivysettings.xml to use? >>> >>> Cheers, >>> Nick >>> >>> >>> On 02/11/2009, at 7:07 PM, Graeme Rocher wrote: >>> >>>> You could try pass these system properties to Grails: >>>> >>>> >>>> http://www.mularien.com/blog/2008/01/18/quick-tip-using-an-authenticated-proxy-server-with-ivy/ >>>> >>>> Since Ivy uses ant for authentication >>>> >>>> Cheers >>>> >>>> On Mon, Nov 2, 2009 at 6:39 AM, Nick Pellow >>>> <npellow@...> wrote: >>>>> >>>>> UPDATE: after turning the log level to verbose, I notice this is >>>>> due to >>>>> an >>>>> authentication error with our maven repository. >>>>> Ideally - ivy could get these from the ~/.m2/settings.xml file. >>>>> Has anyone had experience using the Dependency DSL to access >>>>> artifacts in >>>>> remote, password protected repositories? >>>>> >>>>> Cheers, >>>>> Nick >>>>> >>>>> >>>>> On 02/11/2009, at 4:23 PM, Nick Pellow wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> I'm trying out the nifty new Grails Dependency DSL, as >>>>>> introduced here: >>>>>> >>>>>> http://graemerocher.blogspot.com/2009/09/grails-dependency-resolution-done-right.html >>>>>> . >>>>>> >>>>>> Ivy seems to be having a problem resolving dependencies from >>>>>> our remote >>>>>> maven repository, for -SNAPSHOT versions. >>>>>> >>>>>> Essentially - it looks like Ivy is looking for the - >>>>>> SNAPSHOT.pom, rather >>>>>> than looking up the latestVersion in the maven-metadata.xml . >>>>>> >>>>>> e.g. >>>>>> ==== https://maven.repo.com/private-snapshot: tried >>>>>> >>>>>> >>>>>> >>>>>> https://maven.repo.com/private-snapshot/groupdId/artifactId/1.1.1-SNAPSHOT/artifactId-1.1.1-SNAPSHOT.pom >>>>>> >>>>>> Is there an option available to tell ivy to useMavenMetadata, >>>>>> as there >>>>>> is >>>>>> in the ibiblio resolver? >>>>>> http://ant.apache.org/ivy/history/trunk/resolver/ibiblio.html >>>>>> >>>>>> Cheers, >>>>>> Nick Pellow. >>>>>> >>>>>> --------------------------------------------------------------------- >>>>>> To unsubscribe from this list, please visit: >>>>>> >>>>>> http://xircles.codehaus.org/manage_email >>>>>> >>>>>> >>>>> >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe from this list, please visit: >>>>> >>>>> http://xircles.codehaus.org/manage_email >>>>> >>>>> >>>>> >>>> >>>> >>>> >>>> -- >>>> Graeme Rocher >>>> Head of Grails Development >>>> SpringSource - Weapons for the War on Java Complexity >>>> http://www.springsource.com >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe from this list, please visit: >>>> >>>> http://xircles.codehaus.org/manage_email >>>> >>>> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe from this list, please visit: >>> >>> http://xircles.codehaus.org/manage_email >>> >>> >>> >> >> >> >> -- >> Graeme Rocher >> Head of Grails Development >> SpringSource - Weapons for the War on Java Complexity >> http://www.springsource.com >> > > > > -- > Graeme Rocher > Head of Grails Development > SpringSource - Weapons for the War on Java Complexity > http://www.springsource.com > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: Resolving Plugin -SNAPSHOT dependencies from M2 remote repository
by nick pellow
::
Rate this Message:
Thanks for clarifying this. As I currently understand it, when defining dependencies in the BuildConfig.groovy of a plugin, the following occurs: 1) grails package-plugin the dependencies are resolved, and packaged into the lib directory of the plugin 2) grails install-plugin the dependencies are resolved again, even though they already exist in the lib directory of the plugin. This means that if I create and package a plugin - there will most likely be a large warning from ivy when a user tries to install the plugin. ie. :::::::::::::::::::::::::::::::::::::::::::::: :: UNRESOLVED DEPENDENCIES :: :::::::::::::::::::::::::::::::::::::::::::::: :: group#artifact;0.0.1-SNAPSHOT: not found :::::::::::::::::::::::::::::::::::::::::::::: because the artifact will probably not be available for the user installing the plugin. Could the dependency resolver first look in the plugins lib directory for dependencies, before trying to resolve them? Or is there some other way to stop dependencies being resolved when the plugin is installed? Cheers, Nick On 02/11/2009, at 9:31 PM, Graeme Rocher wrote:
|
|
|
Re: Resolving Plugin -SNAPSHOT dependencies from M2 remote repository
by Graeme Rocher-3
::
Rate this Message:
This is fixed in github head where we now also resolve dependencies
from the plugin lib directories Cheers On Wed, Nov 4, 2009 at 1:04 AM, Nick Pellow <npellow@...> wrote: > > Thanks for clarifying this. > As I currently understand it, when defining dependencies in the > BuildConfig.groovy of a plugin, the following occurs: > 1) grails package-plugin the dependencies are resolved, and packaged into > the lib directory of the plugin > 2) grails install-plugin the dependencies are resolved again, even > though they already exist in the lib directory of the plugin. > This means that if I create and package a plugin - there will most likely be > a large warning from ivy when a user tries to install the plugin. > ie. > :::::::::::::::::::::::::::::::::::::::::::::: > :: UNRESOLVED DEPENDENCIES :: > :::::::::::::::::::::::::::::::::::::::::::::: > :: group#artifact;0.0.1-SNAPSHOT: not found > :::::::::::::::::::::::::::::::::::::::::::::: > because the artifact will probably not be available for the user installing > the plugin. > Could the dependency resolver first look in the plugins lib directory for > dependencies, before trying to resolve them? > Or is there some other way to stop dependencies being resolved when the > plugin is installed? > Cheers, > Nick > > > On 02/11/2009, at 9:31 PM, Graeme Rocher wrote: > > On Mon, Nov 2, 2009 at 11:02 AM, Nick Pellow <npellow@...> wrote: > > Great - I will give that a go! > > Is it possible to define the dependencies outside of the grails-app > > directory? > > Since I am writing a plugin - I don't wish the dependency to be resolved > > again from the grails project. > > I just want it resolved and packaged into the plugin's lib dir - and then at > > runtime, have the plugin load it onto the applications classpath. > > The plugins BuildConfig.groovy will be packaged with the plugin and > then the application will resolve dependencies when the plugin is > installed. The only way I know of right now to force packaging of > resolved JAR files inside the plugin is to set your target version to > 1.1 inside the plugin descriptor: > > def grailsVersion = "1.1 > *" > > Cheers > > Cheers, > > Nick > > > On 02/11/2009, at 8:02 PM, Graeme Rocher wrote: > > You might be able to work around it at this point by adding: > > org.apache.ivy.util.url.CredentialsStore.INSTANCE.addCredentials(realm, > > host, userName, passwd); > > To your BuildConfig.groovy > > Cheers > > On Mon, Nov 2, 2009 at 9:39 AM, Graeme Rocher > > <graeme.rocher@...> wrote: > > Not at the moment. Please JIRA a fix for 1.2 RC1 and I will get it > > done. Think this is pretty important for the release. > > Cheers > > On Mon, Nov 2, 2009 at 9:20 AM, Nick Pellow <npellow@...> > > wrote: > > Thanks, Graham. > > The server needing authentication is our Maven2 repository itself. > > Essentially - I need to be able to set a credentials element in > > ivysettings.xml: > > http://ant.apache.org/ivy/history/latest-milestone/settings/credentials.html > > Is there a way to do that via the dependency DSL? Or is it possible to > > specify a ivysettings.xml to use? > > Cheers, > > Nick > > > On 02/11/2009, at 7:07 PM, Graeme Rocher wrote: > > You could try pass these system properties to Grails: > > > > http://www.mularien.com/blog/2008/01/18/quick-tip-using-an-authenticated-proxy-server-with-ivy/ > > Since Ivy uses ant for authentication > > Cheers > > On Mon, Nov 2, 2009 at 6:39 AM, Nick Pellow <npellow@...> > > wrote: > > UPDATE: after turning the log level to verbose, I notice this is due > > to > > an > > authentication error with our maven repository. > > Ideally - ivy could get these from the ~/.m2/settings.xml file. > > Has anyone had experience using the Dependency DSL to access artifacts > > in > > remote, password protected repositories? > > Cheers, > > Nick > > > On 02/11/2009, at 4:23 PM, Nick Pellow wrote: > > Hi, > > I'm trying out the nifty new Grails Dependency DSL, as introduced > > here: > > > http://graemerocher.blogspot.com/2009/09/grails-dependency-resolution-done-right.html . > > Ivy seems to be having a problem resolving dependencies from our > > remote > > maven repository, for -SNAPSHOT versions. > > Essentially - it looks like Ivy is looking for the -SNAPSHOT.pom, > > rather > > than looking up the latestVersion in the maven-metadata.xml . > > e.g. > > ==== https://maven.repo.com/private-snapshot: tried > > > > > https://maven.repo.com/private-snapshot/groupdId/artifactId/1.1.1-SNAPSHOT/artifactId-1.1.1-SNAPSHOT.pom > > Is there an option available to tell ivy to useMavenMetadata, as > > there > > is > > in the ibiblio resolver? > > http://ant.apache.org/ivy/history/trunk/resolver/ibiblio.html > > Cheers, > > Nick Pellow. > > --------------------------------------------------------------------- > > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > > > --------------------------------------------------------------------- > > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > > > > > -- > > Graeme Rocher > > Head of Grails Development > > SpringSource - Weapons for the War on Java Complexity > > http://www.springsource.com > > --------------------------------------------------------------------- > > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > > > --------------------------------------------------------------------- > > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > > > > > -- > > Graeme Rocher > > Head of Grails Development > > SpringSource - Weapons for the War on Java Complexity > > http://www.springsource.com > > > > > -- > > Graeme Rocher > > Head of Grails Development > > SpringSource - Weapons for the War on Java Complexity > > http://www.springsource.com > > --------------------------------------------------------------------- > > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > > > --------------------------------------------------------------------- > > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > > > > > -- > Graeme Rocher > Head of Grails Development > SpringSource - Weapons for the War on Java Complexity > http://www.springsource.com > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > > -- Graeme Rocher Head of Grails Development SpringSource - Weapons for the War on Java Complexity http://www.springsource.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
| Free embeddable forum powered by Nabble | Forum Help |
