You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shindig.apache.org by Martin Hoeller <ma...@xss.co.at> on 2014/09/10 10:47:40 UTC
broken caja dependeny
Hi!
The current Shindig version has a dependency to caja defined in
java/gadgets/pom.xml (and in <dependencyManagement of the main pom.xml):
<dependency>
<groupId>caja</groupId>
<artifactId>caja</artifactId>
<version>r5054</version>
</dependency>
However, this artifact does not exist! (I'm aware of the repository
http://google-caja.googlecode.com/svn/maven/.) According to caja's POM,
the specified version has a groupId of com.google.caja.
This should be fixed in Shindigs POMs. Do you agree?
Should I create a JIRA for this?
thx,
- martin
Re: broken caja dependeny
Posted by Raj Janorkar <ra...@gmail.com>.
My question may be out of topic.
I started creating my first project using Shindig, and i install .WAR file.
We can download .WAR file and it is easy to install in TOMCAT.
Just trying to understand (i am not java programmer), until and unless i
dont make any changes to java source code (some customization). i really
dont need to build it?? Or do i need to build shindig even i dont change
source code to pickup system configuration (java version, memory etc...) on
which i will be running shindig??
Shindig is good application.
For PHP application we need to install APACHE and TOMCAT (its setup is bit
complex.) otherwise everything is perfect.
Regards,
Raj
On Thu, Sep 11, 2014 at 11:19 AM, Paul Lindner <li...@inuus.com> wrote:
> Can you attach the output from mvn? Things work for me as well, even after
> clearing ~/.m2/
>
> On Wed Sep 10 2014 at 11:25:56 AM Ryan Baxter <rb...@apache.org>
> wrote:
>
> > Martin are you having issues building shindig because the dependency
> > cannot be found? I just built shindig and maven was able to download
> > the dependency into my local repo and build.
> >
> > On Wed, Sep 10, 2014 at 4:47 AM, Martin Hoeller <ma...@xss.co.at>
> wrote:
> > > Hi!
> > >
> > > The current Shindig version has a dependency to caja defined in
> > > java/gadgets/pom.xml (and in <dependencyManagement of the main
> pom.xml):
> > >
> > > <dependency>
> > > <groupId>caja</groupId>
> > > <artifactId>caja</artifactId>
> > > <version>r5054</version>
> > > </dependency>
> > >
> > > However, this artifact does not exist! (I'm aware of the repository
> > > http://google-caja.googlecode.com/svn/maven/.) According to caja's
> POM,
> > > the specified version has a groupId of com.google.caja.
> > >
> > > This should be fixed in Shindigs POMs. Do you agree?
> > >
> > > Should I create a JIRA for this?
> > >
> > > thx,
> > > - martin
> >
>
Re: broken caja dependeny
Posted by Paul Lindner <li...@inuus.com>.
Can you attach the output from mvn? Things work for me as well, even after
clearing ~/.m2/
On Wed Sep 10 2014 at 11:25:56 AM Ryan Baxter <rb...@apache.org> wrote:
> Martin are you having issues building shindig because the dependency
> cannot be found? I just built shindig and maven was able to download
> the dependency into my local repo and build.
>
> On Wed, Sep 10, 2014 at 4:47 AM, Martin Hoeller <ma...@xss.co.at> wrote:
> > Hi!
> >
> > The current Shindig version has a dependency to caja defined in
> > java/gadgets/pom.xml (and in <dependencyManagement of the main pom.xml):
> >
> > <dependency>
> > <groupId>caja</groupId>
> > <artifactId>caja</artifactId>
> > <version>r5054</version>
> > </dependency>
> >
> > However, this artifact does not exist! (I'm aware of the repository
> > http://google-caja.googlecode.com/svn/maven/.) According to caja's POM,
> > the specified version has a groupId of com.google.caja.
> >
> > This should be fixed in Shindigs POMs. Do you agree?
> >
> > Should I create a JIRA for this?
> >
> > thx,
> > - martin
>
Re: broken caja dependeny
Posted by felix <fe...@gmail.com>.
btw, I have a todo item to remove Caja from Shindig, since nobody uses it
and it isn't kept up to date, but I don't know when I'll get to it
On Fri, Sep 12, 2014 at 4:51 AM, Martin Hoeller <ma...@xss.co.at> wrote:
> On 12 Sep 2014, Stanton Sievers wrote:
>
> > I understand what you're saying but I don't think that will resolve.
> I've
> > tested updating the groupId in Shindig and the caja resources will not
> > resolve from the google-caja.googlecode repository. As you stated
> earlier,
> > the path to the resource in that repository is at caja/caja and not
> > com/google/caja/caja.
> >
> > When Maven tries to download a resource with groupId com.google.caja, it
> > fails against all repositories that are defined.
> >
> > Downloading:
> >
> http://google-caja.googlecode.com/svn/maven/com/google/caja/htmlparser/r4209/htmlparser-r4209.jar
> > Downloading:
> >
> http://google-caja.googlecode.com/svn/maven/com/google/caja/caja/r5054/caja-r5054.jar
> >
> > It doesn't matter what the groupId of the actual resource pom says;
> rather,
> > the path is what matters.
>
> Oh, this is bad. I thought maven would request an artifact with given
> coordinates from the repo and not a specific file :(
>
> So the caja reposiroty/POM coordinates do not match (as stated earlier)
> and no artifact with the new coordinates from the POM is served by any
> repository.
>
> To solve this issue (as suggested in my orginal mail), we would first
> need some repository that serves caja with the correct groupId. But this
> is currently not available and caja seems not to use or support maven
> very well.
>
> Should I still file an issue (that won't be fixed now) to track this?
> I could also file an issue against caja to fix this maven-issues.
>
> Any thoughts?
>
> - martin
>
Re: broken caja dependeny
Posted by Stanton Sievers <ss...@apache.org>.
Thanks for walking through these issues with us and writing up these issues.
On Sep 12, 2014 8:40 AM, "Martin Hoeller" <ma...@xss.co.at> wrote:
> Done. I've filed
> http://code.google.com/p/google-caja/issues/detail?id=1938
> for Caja and
> https://issues.apache.org/jira/browse/SHINDIG-1982
> for Shindig.
>
> hth,
> - martin
>
>
> On 12 Sep 2014, Stanton Sievers wrote:
>
> > Filing two tickets would be fine. We can point the Shindig ticket to the
> > Caja ticket and fix the former when the latter is resolved.
> >
> > Thanks!
> > On Sep 12, 2014 7:52 AM, "Martin Hoeller" <ma...@xss.co.at> wrote:
> >
> > > On 12 Sep 2014, Stanton Sievers wrote:
> > >
> > > > I understand what you're saying but I don't think that will resolve.
> > > I've
> > > > tested updating the groupId in Shindig and the caja resources will
> not
> > > > resolve from the google-caja.googlecode repository. As you stated
> > > earlier,
> > > > the path to the resource in that repository is at caja/caja and not
> > > > com/google/caja/caja.
> > > >
> > > > When Maven tries to download a resource with groupId
> com.google.caja, it
> > > > fails against all repositories that are defined.
> > > >
> > > > Downloading:
> > > >
> > >
> http://google-caja.googlecode.com/svn/maven/com/google/caja/htmlparser/r4209/htmlparser-r4209.jar
> > > > Downloading:
> > > >
> > >
> http://google-caja.googlecode.com/svn/maven/com/google/caja/caja/r5054/caja-r5054.jar
> > > >
> > > > It doesn't matter what the groupId of the actual resource pom says;
> > > rather,
> > > > the path is what matters.
> > >
> > > Oh, this is bad. I thought maven would request an artifact with given
> > > coordinates from the repo and not a specific file :(
> > >
> > > So the caja reposiroty/POM coordinates do not match (as stated earlier)
> > > and no artifact with the new coordinates from the POM is served by any
> > > repository.
> > >
> > > To solve this issue (as suggested in my orginal mail), we would first
> > > need some repository that serves caja with the correct groupId. But
> this
> > > is currently not available and caja seems not to use or support maven
> > > very well.
> > >
> > > Should I still file an issue (that won't be fixed now) to track this?
> > > I could also file an issue against caja to fix this maven-issues.
> > >
> > > Any thoughts?
> > >
> > > - martin
>
Re: broken caja dependeny
Posted by Martin Hoeller <ma...@xss.co.at>.
Done. I've filed
http://code.google.com/p/google-caja/issues/detail?id=1938
for Caja and
https://issues.apache.org/jira/browse/SHINDIG-1982
for Shindig.
hth,
- martin
On 12 Sep 2014, Stanton Sievers wrote:
> Filing two tickets would be fine. We can point the Shindig ticket to the
> Caja ticket and fix the former when the latter is resolved.
>
> Thanks!
> On Sep 12, 2014 7:52 AM, "Martin Hoeller" <ma...@xss.co.at> wrote:
>
> > On 12 Sep 2014, Stanton Sievers wrote:
> >
> > > I understand what you're saying but I don't think that will resolve.
> > I've
> > > tested updating the groupId in Shindig and the caja resources will not
> > > resolve from the google-caja.googlecode repository. As you stated
> > earlier,
> > > the path to the resource in that repository is at caja/caja and not
> > > com/google/caja/caja.
> > >
> > > When Maven tries to download a resource with groupId com.google.caja, it
> > > fails against all repositories that are defined.
> > >
> > > Downloading:
> > >
> > http://google-caja.googlecode.com/svn/maven/com/google/caja/htmlparser/r4209/htmlparser-r4209.jar
> > > Downloading:
> > >
> > http://google-caja.googlecode.com/svn/maven/com/google/caja/caja/r5054/caja-r5054.jar
> > >
> > > It doesn't matter what the groupId of the actual resource pom says;
> > rather,
> > > the path is what matters.
> >
> > Oh, this is bad. I thought maven would request an artifact with given
> > coordinates from the repo and not a specific file :(
> >
> > So the caja reposiroty/POM coordinates do not match (as stated earlier)
> > and no artifact with the new coordinates from the POM is served by any
> > repository.
> >
> > To solve this issue (as suggested in my orginal mail), we would first
> > need some repository that serves caja with the correct groupId. But this
> > is currently not available and caja seems not to use or support maven
> > very well.
> >
> > Should I still file an issue (that won't be fixed now) to track this?
> > I could also file an issue against caja to fix this maven-issues.
> >
> > Any thoughts?
> >
> > - martin
Re: broken caja dependeny
Posted by Martin Hoeller <ma...@xss.co.at>.
On 12 Sep 2014, Stanton Sievers wrote:
> I understand what you're saying but I don't think that will resolve. I've
> tested updating the groupId in Shindig and the caja resources will not
> resolve from the google-caja.googlecode repository. As you stated earlier,
> the path to the resource in that repository is at caja/caja and not
> com/google/caja/caja.
>
> When Maven tries to download a resource with groupId com.google.caja, it
> fails against all repositories that are defined.
>
> Downloading:
> http://google-caja.googlecode.com/svn/maven/com/google/caja/htmlparser/r4209/htmlparser-r4209.jar
> Downloading:
> http://google-caja.googlecode.com/svn/maven/com/google/caja/caja/r5054/caja-r5054.jar
>
> It doesn't matter what the groupId of the actual resource pom says; rather,
> the path is what matters.
Oh, this is bad. I thought maven would request an artifact with given
coordinates from the repo and not a specific file :(
So the caja reposiroty/POM coordinates do not match (as stated earlier)
and no artifact with the new coordinates from the POM is served by any
repository.
To solve this issue (as suggested in my orginal mail), we would first
need some repository that serves caja with the correct groupId. But this
is currently not available and caja seems not to use or support maven
very well.
Should I still file an issue (that won't be fixed now) to track this?
I could also file an issue against caja to fix this maven-issues.
Any thoughts?
- martin
Re: broken caja dependeny
Posted by Martin Hoeller <ma...@xss.co.at>.
Hi Stanton!
On 11 Sep 2014, Stanton Sievers wrote:
> Hi Martin,
>
> I don't see Caja in the maven central repository.
Correct, it isn't there.
> My concern is that it
> won't resolve if we update the groupId. We're explicitly adding the
> google-caja repository to find this artifact.
Yes, I know. And I'm talking exactly about the artifact in this
google-caja repository:
http://google-caja.googlecode.com/svn/maven/caja/caja/r5054/caja-r5054.pom
This pom.xml has
<groupId>com.google.caja</groupId>
<artifactId>caja</artifactId>
<packaging>jar</packaging>
So the groupId the should be used is (according to this pom)
com.google.caja and not caja. And that's exactly what I'm asking for.
Got me now?
- martin
Re: broken caja dependeny
Posted by Stanton Sievers <ss...@apache.org>.
Hi Martin,
I don't see Caja in the maven central repository. My concern is that it
won't resolve if we update the groupId. We're explicitly adding the
google-caja repository to find this artifact.
Until the artifact is properly stored in maven central I don't think we can
do anything. There was a recommendation of adding caja to the maven
central repository [1] but it didn't go anywhere. I haven't found any
other responses regarding why caja is not in maven central.
Sorry I couldn't be of more help.
-Stanton
[1] https://code.google.com/p/google-caja/issues/detail?id=1306
On Thu, Sep 11, 2014 at 2:11 AM, Martin Hoeller <ma...@xss.co.at> wrote:
> On 10 Sep 2014, Ryan Baxter wrote:
>
> > Martin are you having issues building shindig because the dependency
> > cannot be found?
>
> We had issues after an upgrade of our local repository manager (nexus 1.x
> to 2.9) which I solved by deploying a relocation POM for caja in our
> local repository manager. So no, I do not (no longer) have any problems
> building shindig or our project that uses shinding.
>
> Still, shinding depends on an artifact that (according to POM coordinates)
> does not exist, which feels just broken.
>
> > I just built shindig and maven was able to download
> > the dependency into my local repo and build.
>
> Background information: when building WITHOUT our local repository
> manager everthing worked and works fine. But when I use our local
> repository-manager maven said it cannot find the artifact caja:
>
> [...]
> [ERROR] Failed to execute goal on project emcs-shindig-integration: Could
> not resolve dependencies for project at.co.xss.myProject:jar:5.1-SNAPSHOT:
> The following
> artifacts could not be resolved: caja:caja:jar:r5054: Could not find
> artifact caja:caja:jar:r5054 in nexus-repo
>
> The thing is, the artifact caja:caja:jar:r5054 really does NOT exist! So
> the error message is correct. As I wrote earlier, according to caja's
> POM, it has a groupId of com.google.caja.
>
> However, in the repository http://google-caja.googlecode.com/svn/maven/
> it's in the directory caja/caja which should correspond to the groupId
> (but does not). So the actual problem seems to be, that caja's maven repo
> is kind of broken.
>
> I already fixed the problem with a relocation POM for caja in our local
> repository manager. So there is no problem for me building our project.
>
> But I still think shinding's dependency to caja is incorrect. IMHO the
> whole thing only works because caja's repository serves an artifact that
> actually is not available according to POM coordinates.
>
> Did I make myself clear?
>
> hth,
> - martin
>
Re: broken caja dependeny
Posted by Martin Hoeller <ma...@xss.co.at>.
On 10 Sep 2014, Ryan Baxter wrote:
> Martin are you having issues building shindig because the dependency
> cannot be found?
We had issues after an upgrade of our local repository manager (nexus 1.x
to 2.9) which I solved by deploying a relocation POM for caja in our
local repository manager. So no, I do not (no longer) have any problems
building shindig or our project that uses shinding.
Still, shinding depends on an artifact that (according to POM coordinates)
does not exist, which feels just broken.
> I just built shindig and maven was able to download
> the dependency into my local repo and build.
Background information: when building WITHOUT our local repository
manager everthing worked and works fine. But when I use our local
repository-manager maven said it cannot find the artifact caja:
[...]
[ERROR] Failed to execute goal on project emcs-shindig-integration: Could not resolve dependencies for project at.co.xss.myProject:jar:5.1-SNAPSHOT: The following
artifacts could not be resolved: caja:caja:jar:r5054: Could not find artifact caja:caja:jar:r5054 in nexus-repo
The thing is, the artifact caja:caja:jar:r5054 really does NOT exist! So
the error message is correct. As I wrote earlier, according to caja's
POM, it has a groupId of com.google.caja.
However, in the repository http://google-caja.googlecode.com/svn/maven/
it's in the directory caja/caja which should correspond to the groupId
(but does not). So the actual problem seems to be, that caja's maven repo
is kind of broken.
I already fixed the problem with a relocation POM for caja in our local
repository manager. So there is no problem for me building our project.
But I still think shinding's dependency to caja is incorrect. IMHO the
whole thing only works because caja's repository serves an artifact that
actually is not available according to POM coordinates.
Did I make myself clear?
hth,
- martin
Re: broken caja dependeny
Posted by Ryan Baxter <rb...@apache.org>.
Martin are you having issues building shindig because the dependency
cannot be found? I just built shindig and maven was able to download
the dependency into my local repo and build.
On Wed, Sep 10, 2014 at 4:47 AM, Martin Hoeller <ma...@xss.co.at> wrote:
> Hi!
>
> The current Shindig version has a dependency to caja defined in
> java/gadgets/pom.xml (and in <dependencyManagement of the main pom.xml):
>
> <dependency>
> <groupId>caja</groupId>
> <artifactId>caja</artifactId>
> <version>r5054</version>
> </dependency>
>
> However, this artifact does not exist! (I'm aware of the repository
> http://google-caja.googlecode.com/svn/maven/.) According to caja's POM,
> the specified version has a groupId of com.google.caja.
>
> This should be fixed in Shindigs POMs. Do you agree?
>
> Should I create a JIRA for this?
>
> thx,
> - martin