You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by Mark Combellack <mc...@apache.org> on 2008/07/07 11:11:27 UTC
Unable to resolve com.google.gdata:gdata-core:jar:1.0 because of spelling mistake in upload script.
Hi,
I've just done an update to the latest revision of the Tuscany root and I am
getting a failure to resolve com.google.gdata:gdata-core:jar:1.0 when
building the binding-gdata-runtime module.
After a bit of investigation, this artefact should be available because:
* I can see that this module has been added over the weekend to the
top level build (SVN commit 674257).
* The poms have been updated to download the Google Maven artifacts
from http://people.apache.org/~lresende/google-gdata/maven/com/google/gdata/
* A new deployGdataToMaven.sh script has been added to upload the
artefacts to the above web site. (SVN commit 674252)
However, this does not work because there is a spelling mistake in the
upload script. The script says:
mvn gpg:sign-and-deploy-file -DgroupId=com.google.gdata
-DartifactId=gdata-core -Dversion=1.0 -Dpackaging=jar
-Dfile=gdata-core-1.0.jar -DrepositoryId=apache.people
-Durl=scp://people.apache.org/home/lresende/public_html/googoe-gdata/maven
-Dkeyname=lresende
The above command misspells google-gdata since it has googoe-gdata. I've
corrected the script in SVN revision 674425.
Is anyone able to run this script as I don't have write access to lresende's
people area on apache.people.org. Guess this means we will need to wait for
Luciano to run this script.
As a work around, all you need to do is download the google-data core jar
manually and install it in your own local Maven repository.
Thanks,
Mark
Re: Depends on 3rd party jars that are not published to maven repos, was: Re: Unable to resolve com.google.gdata:gdata-core:jar:1.0 because of spelling mistake in upload script.
Posted by haleh mahbod <hm...@gmail.com>.
It makes sense to go with 3 since it seems like other projects experienced
the same thing and settled on this approach.
I recall the same kind of problem with SDO project and I don't think it was
ever resolved.
On 7/7/08, Luciano Resende <lu...@gmail.com> wrote:
> +1 for options 1 and 3.
>
> How would option 3 work, you checkout Tuscany maven repo, deploy to
> your local copy and then commit it back with your updates ?
>
> On Mon, Jul 7, 2008 at 1:18 PM, Raymond Feng <en...@gmail.com> wrote:
> > Hi,
> >
> > We have experienced a few cases that some of the 3rd party jars we use
> are
> > not published to the maven repo. There are a few options we have tried
> out:
> >
> > 1) Work with the owner of the 3rd party jars to get them published to
> maven
> > repo
> >
> > It would be the best if it can be worked out. But sometimes the owners
> are
> > reluctant to take the responsibility due to resource, skill and other
> > issues. But usually they are willing to grant us the permission to get
> the
> > artifacts published.
> >
> > 2) Develop an ANT script to download the 3rd party archive and install
> them
> > to the local maven repo
> >
> > We need to run the ANT script in a prerequisite module to get the jars
> > installed to the local maven. It won't support the transitive download
> for
> > other modules that transitively depend on the artifacts.
> >
> > 3) Host the 3rd party jars into a tuscany-owned mave repo inside our SVN
> > repo and declare it as a alternate maven repo in the pom.xml.
> >
> > This is similar to 1) but we have the full control to make the artifacts
> > available to our own build. Some other projects such as Geronimo, Axis2
> and
> > ServiceMix are taking this approach.
> >
> > Should we take option 3) if 1) cannot be easily worked out?
> >
> > Thanks,
> > Raymond
> > From: Mark Combellack
> > Sent: Monday, July 07, 2008 2:11 AM
> > To: dev@tuscany.apache.org ; lresende@apache.org
> > Subject: Unable to resolve com.google.gdata:gdata-core:jar:1.0 because of
> > spelling mistake in upload script.
> >
> > Hi,
> >
> >
> >
> > I've just done an update to the latest revision of the Tuscany root and I
> am
> > getting a failure to resolve com.google.gdata:gdata-core:jar:1.0 when
> > building the binding-gdata-runtime module.
> >
> >
> >
> > After a bit of investigation, this artefact should be available because:
> >
> >
> >
> > I can see that this module has been added over the weekend to the top
> level
> > build (SVN commit 674257).
> > The poms have been updated to download the Google Maven artifacts from
> > http://people.apache.org/~lresende/google-gdata/maven/com/google/gdata/
> > A new deployGdataToMaven.sh script has been added to upload the artefacts
> to
> > the above web site. (SVN commit 674252)
> >
> >
> >
> > However, this does not work because there is a spelling mistake in the
> > upload script. The script says:
> >
> >
> >
> > mvn gpg:sign-and-deploy-file -DgroupId=com.google.gdata
> > -DartifactId=gdata-core -Dversion=1.0 -Dpackaging=jar
> > -Dfile=gdata-core-1.0.jar -DrepositoryId=apache.people
> > -Durl=scp://
> people.apache.org/home/lresende/public_html/googoe-gdata/maven
> > -Dkeyname=lresende
> >
> >
> >
> >
> >
> > The above command misspells google-gdata since it has googoe-gdata. I've
> > corrected the script in SVN revision 674425.
> >
> >
> >
> > Is anyone able to run this script as I don't have write access to
> lresende's
> > people area on apache.people.org. Guess this means we will need to wait
> for
> > Luciano to run this script.
> >
> >
> >
> > As a work around, all you need to do is download the google-data core jar
> > manually and install it in your own local Maven repository.
> >
> >
> >
> > Thanks,
> >
> >
> >
> > Mark
> >
> >
> >
> >
> >
> >
>
>
>
> --
> Luciano Resende
> Apache Tuscany Committer
> http://people.apache.org/~lresende
> http://lresende.blogspot.com/
>
Re: Depends on 3rd party jars that are not published to maven repos, was: Re: Unable to resolve com.google.gdata:gdata-core:jar:1.0 because of spelling mistake in upload script.
Posted by Luciano Resende <lu...@gmail.com>.
+1 for options 1 and 3.
How would option 3 work, you checkout Tuscany maven repo, deploy to
your local copy and then commit it back with your updates ?
On Mon, Jul 7, 2008 at 1:18 PM, Raymond Feng <en...@gmail.com> wrote:
> Hi,
>
> We have experienced a few cases that some of the 3rd party jars we use are
> not published to the maven repo. There are a few options we have tried out:
>
> 1) Work with the owner of the 3rd party jars to get them published to maven
> repo
>
> It would be the best if it can be worked out. But sometimes the owners are
> reluctant to take the responsibility due to resource, skill and other
> issues. But usually they are willing to grant us the permission to get the
> artifacts published.
>
> 2) Develop an ANT script to download the 3rd party archive and install them
> to the local maven repo
>
> We need to run the ANT script in a prerequisite module to get the jars
> installed to the local maven. It won't support the transitive download for
> other modules that transitively depend on the artifacts.
>
> 3) Host the 3rd party jars into a tuscany-owned mave repo inside our SVN
> repo and declare it as a alternate maven repo in the pom.xml.
>
> This is similar to 1) but we have the full control to make the artifacts
> available to our own build. Some other projects such as Geronimo, Axis2 and
> ServiceMix are taking this approach.
>
> Should we take option 3) if 1) cannot be easily worked out?
>
> Thanks,
> Raymond
> From: Mark Combellack
> Sent: Monday, July 07, 2008 2:11 AM
> To: dev@tuscany.apache.org ; lresende@apache.org
> Subject: Unable to resolve com.google.gdata:gdata-core:jar:1.0 because of
> spelling mistake in upload script.
>
> Hi,
>
>
>
> I've just done an update to the latest revision of the Tuscany root and I am
> getting a failure to resolve com.google.gdata:gdata-core:jar:1.0 when
> building the binding-gdata-runtime module.
>
>
>
> After a bit of investigation, this artefact should be available because:
>
>
>
> I can see that this module has been added over the weekend to the top level
> build (SVN commit 674257).
> The poms have been updated to download the Google Maven artifacts from
> http://people.apache.org/~lresende/google-gdata/maven/com/google/gdata/
> A new deployGdataToMaven.sh script has been added to upload the artefacts to
> the above web site. (SVN commit 674252)
>
>
>
> However, this does not work because there is a spelling mistake in the
> upload script. The script says:
>
>
>
> mvn gpg:sign-and-deploy-file -DgroupId=com.google.gdata
> -DartifactId=gdata-core -Dversion=1.0 -Dpackaging=jar
> -Dfile=gdata-core-1.0.jar -DrepositoryId=apache.people
> -Durl=scp://people.apache.org/home/lresende/public_html/googoe-gdata/maven
> -Dkeyname=lresende
>
>
>
>
>
> The above command misspells google-gdata since it has googoe-gdata. I've
> corrected the script in SVN revision 674425.
>
>
>
> Is anyone able to run this script as I don't have write access to lresende's
> people area on apache.people.org. Guess this means we will need to wait for
> Luciano to run this script.
>
>
>
> As a work around, all you need to do is download the google-data core jar
> manually and install it in your own local Maven repository.
>
>
>
> Thanks,
>
>
>
> Mark
>
>
>
>
>
>
--
Luciano Resende
Apache Tuscany Committer
http://people.apache.org/~lresende
http://lresende.blogspot.com/
Depends on 3rd party jars that are not published to maven repos, was: Re: Unable to resolve com.google.gdata:gdata-core:jar:1.0 because of spelling mistake in upload script.
Posted by Raymond Feng <en...@gmail.com>.
Hi,
We have experienced a few cases that some of the 3rd party jars we use are not published to the maven repo. There are a few options we have tried out:
1) Work with the owner of the 3rd party jars to get them published to maven repo
It would be the best if it can be worked out. But sometimes the owners are reluctant to take the responsibility due to resource, skill and other issues. But usually they are willing to grant us the permission to get the artifacts published.
2) Develop an ANT script to download the 3rd party archive and install them to the local maven repo
We need to run the ANT script in a prerequisite module to get the jars installed to the local maven. It won't support the transitive download for other modules that transitively depend on the artifacts.
3) Host the 3rd party jars into a tuscany-owned mave repo inside our SVN repo and declare it as a alternate maven repo in the pom.xml.
This is similar to 1) but we have the full control to make the artifacts available to our own build. Some other projects such as Geronimo, Axis2 and ServiceMix are taking this approach.
Should we take option 3) if 1) cannot be easily worked out?
Thanks,
Raymond
From: Mark Combellack
Sent: Monday, July 07, 2008 2:11 AM
To: dev@tuscany.apache.org ; lresende@apache.org
Subject: Unable to resolve com.google.gdata:gdata-core:jar:1.0 because of spelling mistake in upload script.
Hi,
I've just done an update to the latest revision of the Tuscany root and I am getting a failure to resolve com.google.gdata:gdata-core:jar:1.0 when building the binding-gdata-runtime module.
After a bit of investigation, this artefact should be available because:
a.. I can see that this module has been added over the weekend to the top level build (SVN commit 674257).
b.. The poms have been updated to download the Google Maven artifacts from http://people.apache.org/~lresende/google-gdata/maven/com/google/gdata/
c.. A new deployGdataToMaven.sh script has been added to upload the artefacts to the above web site. (SVN commit 674252)
However, this does not work because there is a spelling mistake in the upload script. The script says:
mvn gpg:sign-and-deploy-file -DgroupId=com.google.gdata -DartifactId=gdata-core -Dversion=1.0 -Dpackaging=jar -Dfile=gdata-core-1.0.jar -DrepositoryId=apache.people -Durl=scp://people.apache.org/home/lresende/public_html/googoe-gdata/maven -Dkeyname=lresende
The above command misspells google-gdata since it has googoe-gdata. I've corrected the script in SVN revision 674425.
Is anyone able to run this script as I don't have write access to lresende's people area on apache.people.org. Guess this means we will need to wait for Luciano to run this script.
As a work around, all you need to do is download the google-data core jar manually and install it in your own local Maven repository.
Thanks,
Mark
RE: Unable to resolve com.google.gdata:gdata-core:jar:1.0 because of spelling mistake in upload script.
Posted by Mark Combellack <mc...@apache.org>.
Hi Luciano,
Thanks for running the script. I can confirm that I can now build the
binding-gdata-runtime project without issue. The gdata-core jar file is
downloading fine.
Thanks,
Mark
> -----Original Message-----
> From: luckbr1975@gmail.com [mailto:luckbr1975@gmail.com] On Behalf Of
> Luciano Resende
> Sent: 08 July 2008 01:38
> To: dev@tuscany.apache.org; mcombellack@apache.org
> Subject: Re: Unable to resolve com.google.gdata:gdata-core:jar:1.0 because
> of spelling mistake in upload script.
>
> Sorry for the misspelling. and thanks for correcting it.
> I have run the scripts and the artifacts should be correct available now.
>
> On Mon, Jul 7, 2008 at 2:11 AM, Mark Combellack <mc...@apache.org>
> wrote:
> > Hi,
> >
> >
> >
> > I've just done an update to the latest revision of the Tuscany root and
> I am
> > getting a failure to resolve com.google.gdata:gdata-core:jar:1.0 when
> > building the binding-gdata-runtime module.
> >
> >
> >
> > After a bit of investigation, this artefact should be available because:
> >
> >
> >
> > I can see that this module has been added over the weekend to the top
> level
> > build (SVN commit 674257).
> > The poms have been updated to download the Google Maven artifacts from
> > http://people.apache.org/~lresende/google-gdata/maven/com/google/gdata/
> > A new deployGdataToMaven.sh script has been added to upload the
> artefacts to
> > the above web site. (SVN commit 674252)
> >
> >
> >
> > However, this does not work because there is a spelling mistake in the
> > upload script. The script says:
> >
> >
> >
> > mvn gpg:sign-and-deploy-file -DgroupId=com.google.gdata
> > -DartifactId=gdata-core -Dversion=1.0 -Dpackaging=jar
> > -Dfile=gdata-core-1.0.jar -DrepositoryId=apache.people
> > -Durl=scp://people.apache.org/home/lresende/public_html/googoe-
> gdata/maven
> > -Dkeyname=lresende
> >
> >
> >
> >
> >
> > The above command misspells google-gdata since it has googoe-gdata. I've
> > corrected the script in SVN revision 674425.
> >
> >
> >
> > Is anyone able to run this script as I don't have write access to
> lresende's
> > people area on apache.people.org. Guess this means we will need to wait
> for
> > Luciano to run this script.
> >
> >
> >
> > As a work around, all you need to do is download the google-data core
> jar
> > manually and install it in your own local Maven repository.
> >
> >
> >
> > Thanks,
> >
> >
> >
> > Mark
> >
> >
> >
> >
> >
> >
>
>
>
> --
> Luciano Resende
> Apache Tuscany Committer
> http://people.apache.org/~lresende
> http://lresende.blogspot.com/
Re: Unable to resolve com.google.gdata:gdata-core:jar:1.0 because of spelling mistake in upload script.
Posted by Luciano Resende <lr...@apache.org>.
Sorry for the misspelling. and thanks for correcting it.
I have run the scripts and the artifacts should be correct available now.
On Mon, Jul 7, 2008 at 2:11 AM, Mark Combellack <mc...@apache.org> wrote:
> Hi,
>
>
>
> I've just done an update to the latest revision of the Tuscany root and I am
> getting a failure to resolve com.google.gdata:gdata-core:jar:1.0 when
> building the binding-gdata-runtime module.
>
>
>
> After a bit of investigation, this artefact should be available because:
>
>
>
> I can see that this module has been added over the weekend to the top level
> build (SVN commit 674257).
> The poms have been updated to download the Google Maven artifacts from
> http://people.apache.org/~lresende/google-gdata/maven/com/google/gdata/
> A new deployGdataToMaven.sh script has been added to upload the artefacts to
> the above web site. (SVN commit 674252)
>
>
>
> However, this does not work because there is a spelling mistake in the
> upload script. The script says:
>
>
>
> mvn gpg:sign-and-deploy-file -DgroupId=com.google.gdata
> -DartifactId=gdata-core -Dversion=1.0 -Dpackaging=jar
> -Dfile=gdata-core-1.0.jar -DrepositoryId=apache.people
> -Durl=scp://people.apache.org/home/lresende/public_html/googoe-gdata/maven
> -Dkeyname=lresende
>
>
>
>
>
> The above command misspells google-gdata since it has googoe-gdata. I've
> corrected the script in SVN revision 674425.
>
>
>
> Is anyone able to run this script as I don't have write access to lresende's
> people area on apache.people.org. Guess this means we will need to wait for
> Luciano to run this script.
>
>
>
> As a work around, all you need to do is download the google-data core jar
> manually and install it in your own local Maven repository.
>
>
>
> Thanks,
>
>
>
> Mark
>
>
>
>
>
>
--
Luciano Resende
Apache Tuscany Committer
http://people.apache.org/~lresende
http://lresende.blogspot.com/