Could not find artifact com.sun.codemodel:codemodel:jar:2.5-FROZEN-AA

[GoogleCodeExporter]

I am unable to get a maven configuration working due to the problem mentioned 
above.

Even if I create an exclusion for this artifact in POM (AFAIU this code is 
embedded in androidannotations.jar anyway) I only get past compilation phase.

android-maven-plugin still chokes on aapt.exe

Original issue reported on code.google.com by lgaw...@gmail.com on 6 Nov 2011 at 2:56

[GoogleCodeExporter]

Thanks for reporting issues!

In the coming release, we switched from a custom snapshot build of CodeModel to 
the latest official release. They were slow on making releases and we needed a 
new feature so that's why we used a custom build for some time, but now we 
don't need it anymore.

It seems that we removed this custom build from our repository, and that was a 
mistake. Sorry about that.

You can override 2.5-FROZEN-AA with this version : 2.4.1 (when we froze, they 
were going to make a 2.5 release, and they finally chose 2.4.X)

Anyway, you are right that this code is embedded in the jar (repackaged with 
jarjar), so this shouldn't really be a problem.

Now you have problems with android-maven-plugin. Could you please copy&paste 
the error ? There have been lots of trouble recently with the 
android-maven-plugin, but that's not related to annotation processing, rather 
to the new ADT releases (14 & 15).

Thanks

Original comment by py.ricau on 7 Nov 2011 at 7:45

[GoogleCodeExporter]

By the way, on your first issue : I think we should either create two different 
artifacts (one with the jars repackaged and no dependency, and the other with 
dependencies and no repackaging), or let the CodeModel dep be optional. The 
second option is easier to implement.

Original comment by py.ricau on 7 Nov 2011 at 7:50

[GoogleCodeExporter]

I saw that you commented the 
http://code.google.com/p/androidannotations/wiki/MavenEclipse page, but the 
comments are "deleted". Did you delete them, or is it some automatic antispam 
robot doing too well of a job ? Do you want me to bring them back ?

Original comment by py.ricau on 7 Nov 2011 at 8:02

[GoogleCodeExporter]

I deleted the comments because I thought making an <exclusion> for codegen in 
pom.xml is all that is needed for the project to work. And it actually does not 
generate any errors in Eclipse. Still mvn clean install at aapt.exe phase 
chokes on missing codegen (even though <exclusion> is defined). This is 
probably android-maven-plugin fault.

Original comment by lgaw...@gmail.com on 7 Nov 2011 at 9:08

[GoogleCodeExporter]

We added the frozen snapshot back in our thirdparty repo : 
http://repository.excilys.com/content/repositories/thirdparty/com/sun/codemodel/
codemodel/2.5-FROZEN-AA/

Does it work now ?

Original comment by py.ricau on 7 Nov 2011 at 1:16

[GoogleCodeExporter]

No it doesn't 
The repository contains this file:
codemodel-2.5-FROZEN-AA-AA.jar

instead of 

codemodel-2.5-FROZEN-AA.jar

Original comment by lgaw...@gmail.com on 7 Nov 2011 at 3:24

[GoogleCodeExporter]

Sorry about that, I should have checked. Right now, I don't have the rights to 
push to this repository, so I'm delegating this to someone else. Hopefully, 
we'll fix this asap.

Original comment by py.ricau on 7 Nov 2011 at 3:46

[GoogleCodeExporter]

Is that OK now ?

Original comment by py.ricau on 7 Nov 2011 at 4:17

[GoogleCodeExporter]

I'll take that for a "yes" ;-) . If you think it's not solved, please tell me 
and I'll reopen the bug.

Original comment by py.ricau on 8 Nov 2011 at 3:36

• Changed state: Fixed