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'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 almo
I was able to access the jandex jar using this repository entry:
JBoss Repo
https://repository.jboss.org/nexus/content/repositories/releases
JBoss Repo
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
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 th
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" wrote:
> Hi Wayne,
>
> Sorry I missed the post update..
>
> So, to answer your question, what am I trying to a
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
