Re: Multi modules and profiles
Hi Wayne, Sorry I missed the post update.. So, to answer your question, what am I trying to achieve here ? I have this project which originally has one child module, called the core module. This core module takes care of the Dao layer. And the setup for the dependencies are inherited from the parent module. That means I have Dao related dependencies listed in the parent module. Now, I need to have another view module, for the client side of the application. This view module should not be bothered by any Dao related dependencies. So my idea was to move all these Dao related dependencies from the parent module into the core child module, so that the view child module would not have to bother with them. By maybe there is a better way to go about this issue of separating dependencies concerns by modules.. -- View this message in context: http://maven.40175.n5.nabble.com/Multi-modules-and-profiles-tp4732786p4882403.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Multi modules and profiles
Regards Mirko -- Sent from my phone http://illegalstateexception.blogspot.com http://github.com/mfriedenhagen/ https://bitbucket.org/mfriedenhagen/ On Oct 8, 2011 10:43 AM, Stephane-3 mittiprove...@yahoo.se wrote: Hi Wayne, Sorry I missed the post update.. So, to answer your question, what am I trying to achieve here ? I have this project which originally has one child module, called the core module. This core module takes care of the Dao layer. And the setup for the dependencies are inherited from the parent module. That means I have Dao related dependencies listed in the parent module. Now, I need to have another view module, for the client side of the application. This view module should not be bothered by any Dao related dependencies. So my idea was to move all these Dao related dependencies from the parent module into the core child module, so that the view child module would not have to bother with them. By maybe there is a better way to go about this issue of separating dependencies concerns by modules.. -- View this message in context: http://maven.40175.n5.nabble.com/Multi-modules-and-profiles-tp4732786p4882403.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Multi modules and profiles
Stephane I mostly never define dependencies directly in the parent pom but have a dependencyManagement section so versions will not differ between modules. Same goes for plugins and pluginManagement. Maybe you could add something like junit in test scope directly to the parent's dependencies. I think seperation of declaring the version in the parent and including a dependency in the modules is the way to go. Regards Mirko -- Sent from my phone http://illegalstateexception.blogspot.com http://github.com/mfriedenhagen/ https://bitbucket.org/mfriedenhagen/ On Oct 8, 2011 10:43 AM, Stephane-3 mittiprove...@yahoo.se wrote:
Re: hibernate4: referential integrity of maven central violated
I was able to access the jandex jar using this repository entry: repository idJBoss Repo/id urlhttps://repository.jboss.org/nexus/content/repositories/releases/url nameJBoss Repo/name /repository Hope that this helps. I'm sorry to say that I'm not familiar enough with the nexus staging process be able to reply concerning your question one way or another. Andy On 10/7/11 2:44 PM, Jörg Hohwiller wrote: Hi there, hibernate-core 4.0.0CR4 is in central and has a dependency on jandex that is not present in maven central: http://search.maven.org/remotecontent?filepath=org/hibernate/hibernate-core/4.0.0.CR4/hibernate-core-4.0.0.CR4.pom I thought that via the nexus staging process this is prevented by validation rules. Is there some gap? Even more strange is that it is listed in jboss repo, but the links end in 404: https://repository.jboss.org/nexus/content/repositories/public/org/jboss/jandex/1.0.3.Final/ Does somebody have a clue where to get the artifact? Has someone an idea how this can happen - IMHO central should not end up with missing dependencies? Regards Jörg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Managing Different Java Versions
I've been using Maven for about 6 months now so I am still a big green. Recently I discovered that my project needs to be compatible with client code that requires Java 5, because it needs to run on OS 10.5 32-bit Intel. Unfortunately I have been doing all my development with Java 6. I am almost complete reworking things to run on a Java 5 run-time, and while everything compiles, things are dying in hibernate somewhere because there are Java 6 class files in some of the artifacts. Unfortunately from the diaganosics I cannot tell which artifact I am importing that has the Java 6 class files. Is there some common wisdom or best practices on how to determine which Java versions were used to build an artifact. I know you can specify a java version in the classifier, but is there a way to search for specific coordinates based on the classifier, or some way to tell Maven to only use artifacts with a specific version of Java class files? Cheers, Eric - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Managing Different Java Versions
On 09/10/2011, at 11:25 AM, Eric Kolotyluk wrote: I've been using Maven for about 6 months now so I am still a big green. Recently I discovered that my project needs to be compatible with client code that requires Java 5, because it needs to run on OS 10.5 32-bit Intel. Unfortunately I have been doing all my development with Java 6. I am almost complete reworking things to run on a Java 5 run-time, and while everything compiles, things are dying in hibernate somewhere because there are Java 6 class files in some of the artifacts. Unfortunately from the diaganosics I cannot tell which artifact I am importing that has the Java 6 class files. It should give you the name of the class itself, which you can search for in your repository manager or on one of the public instances of repository search to find out which JAR it is coming from. You might also try the animal sniffer plugin: http://mojo.codehaus.org/animal-sniffer-maven-plugin/examples/generating-other-api-signatures.html Is there some common wisdom or best practices on how to determine which Java versions were used to build an artifact. I know you can specify a java version in the classifier, but is there a way to search for specific coordinates based on the classifier, or some way to tell Maven to only use artifacts with a specific version of Java class files? Maven can't do dependency resolution based on this, because there is no global flag for a JAR that's applicable (each class in it can be different). - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
