New Maven Dependencies for latest 0.93 SNAPSHOT?
Mike
getting a compile error in my maven project...
could not parse error message: com/google/code/morphia/mapping/lazy/
CGLibLazyProxyFactory.java(com/google/code/morphia/mapping/
lazy:CGLibLazyProxyFactory.java):17: package
com.thoughtworks.proxy.factory does not exist
import com.thoughtworks.proxy.factory.CglibProxyFactory;
Thanks.
Scott Hernandez
This seems like a compiler error, but not in your project.
The latest pom is here:
http://code.google.com/p/morphia/source/browse/mavenrepo/com/google/code/morphia/morphia/0.93-SNAPSHOT/morphia-0.93-20100609.210914-27.pom
The snapshot is pointing to it:
http://code.google.com/p/morphia/source/browse/mavenrepo/com/google/code/morphia/morphia/0.93-SNAPSHOT/maven-metadata.xml
It is clear from the pom that the deps are there.
<dependency>
<groupId>cglib</groupId>
<artifactId>cglib-nodep</artifactId>
<version>[2.1_3,)</version>
<type>jar</type>
<optional>true</optional>
</dependency>
<dependency>
<groupId>com.thoughtworks.proxytoys</groupId>
<artifactId>proxytoys</artifactId>
<version>1.0</version>
<type>jar</type>
<optional>true</optional>
</dependency>
You will note that these are optional, but that will only affect your
project if you want to use those features; in which case you need to
add them to your project (so the libraries are added to your run-time
class path). See
http://maven.apache.org/guides/introduction/introduction-to-optional-and-excludes-dependencies.html
I will push up another snapshot to the repo. just in case, but there
were no errors on that last one, and the commit logs looked good.
Mike
So, I'm using the jars and have maven set up as follows:
MyProject -> Morphia (0.93-SNAPSHOT) -> Optional Jars
It cannot build my project because it cannot find those optional jars.
I'm not too familiar with maven optional jars, as I continue studying
the link you sent me, I'd appreciate any advice.
-Mike
On Jun 9, 6:02 pm, Scott Hernandez <scotthernan...@gmail.com> wrote:
> I'm confused. Are you building from source or using the jars?
>
> This seems like a compiler error, but not in your project.
>
>
> The snapshot is pointing to it:http://code.google.com/p/morphia/source/browse/mavenrepo/com/google/c...
> It is clear from the pom that the deps are there.
> <dependency>
> <groupId>cglib</groupId>
> <artifactId>cglib-nodep</artifactId>
> <version>[2.1_3,)</version>
> <type>jar</type>
> <optional>true</optional>
> </dependency>
> <dependency>
> <groupId>com.thoughtworks.proxytoys</groupId>
> <artifactId>proxytoys</artifactId>
> <version>1.0</version>
> <type>jar</type>
> <optional>true</optional>
> </dependency>
>
> You will note that these are optional, but that will only affect your
> project if you want to use those features; in which case you need to
> add them to your project (so the libraries are added to your run-time
Mike
<groupId>cglib</groupId>
<artifactId>cglib-nodep</artifactId>
<version>[2.1_3,)</version>
<type>jar</type>
<optional>true</optional>
</dependency>
<dependency>
<groupId>com.thoughtworks.proxytoys</groupId>
<artifactId>proxytoys</artifactId>
<version>1.0</version>
<type>jar</type>
<optional>true</optional>
</dependency>
my understanding, this defeats the purpose of the optional jars in the
first place. Hmmm...Perhaps if "MyProject" is referencing optional
jars via some import in morphia, it triggers this non-optional
dependency and requires it during compile time?
Oh well, I'm building again.
Scott Hernandez
Your project will then include them. I think it is that simple.
I don't use maven (for project I start, and can keep away from maven);
I would suggest not using it. It is broken by design.
Scott Hernandez
> It's probably worth adding that when I add:
> <dependency>
> <groupId>cglib</groupId>
> <artifactId>cglib-nodep</artifactId>
> <version>[2.1_3,)</version>
> <type>jar</type>
> <optional>true</optional>
> </dependency>
> <dependency>
> <groupId>com.thoughtworks.proxytoys</groupId>
> <artifactId>proxytoys</artifactId>
> <version>1.0</version>
> <type>jar</type>
> <optional>true</optional>
> </dependency>
>
> to "MyProject" which references morphia, it builds fine, but based on
> my understanding, this defeats the purpose of the optional jars in the
> first place. Hmmm...Perhaps if "MyProject" is referencing optional
> jars via some import in morphia, it triggers this non-optional
> dependency and requires it during compile time?
No, the optional part only applied to projects that include you as a
dep. The docs talk about this rather explicitly. That section above,
with or without optional means the same thing for your project
dependencies and classpath.
Uwe Schäfer
> I don't use maven (for project I start, and can keep away from maven);
> I would suggest not using it. It is broken by design.
i reaaaaally dont want to enter this discussion, but i cannot stay away
from - just for the record - objecting here ;)
it might be not fit for absolutely everthing but it saves time like hell
even in smaller teams.
cu uwe
:)
