RE: How to resolve right dependency which enabled and built/install with profile?

[Liu, Raymond]

Actually, I think it is possible, though probably could not be done by current 
Maven implementation. As long as B can know which libjar the shim A is built 
upon. I am saying that it is possible is because that I can achieve the goal 
with SBT, when sbt do publish local, it will fill the profile info ( actually 
not profile in sbt, but some compile time config ) into A's final pom, then 
when assemble B, the installed A actually do not have any profile info in A's 
pom. B then assemble with the right libjar which A is built upon.

Best Regards,
Raymond Liu


-Original Message-
From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] 
Sent: Wednesday, December 11, 2013 6:47 PM
To: Maven Users List
Subject: Re: How to resolve right dependency which enabled and built/install 
with profile?

You are looking for the impossible.

You want A to work with any version of libjar

You want B to use A but not know which version of libjar the A it is using 
depends on... actually to be independent of the version of libjar that A 
depends on... but also to bundle the specific one...

Rethink what you are asking and you will see that you are asking an impossible 
request... you are asking somebody to hop on one leg and mandating that the one 
leg be both their left and right leg.

When you are asking an impossibility, that is usually a sign that you are going 
at things the wrong way.

If A is going to become part of a fatjar at some point, you need to make a 
decision *at the point of creating the fatjar* as to which libjar will be 
included within A.

Or else perhaps, you include all versions of libjar and provide a means for A 
to decide which version it wants... there are many ways to achieve this...

* use the service provider pattern to introduce another shim layer and then use 
the shade plugin to put all the shim impl libjar deps into independent package 
namespaces
* use a custom classloader and package libjar as resources, so that A's entry 
point loads the correct libjar at runtime
* etc.

With the above you would be including *all* versions of libjar within A and the 
whole thing becomes moot anyway...

-Stephen


On 11 December 2013 00:52, Liu, Raymond  wrote:

> Thanks Stephen
>
> I see your solution is let B manage the libjar version. While 
> this is against my wish, I wish B to know nothing about A's internal 
> implementation. In the future, A might depends on a v3.0 libjar, I do 
> wish to just repackage B to make it work not revise B's code or assembly 
> rules.
> And sometime A might be buried deep in the dependent tree, Those 
> project might not even aware it depends on A, they just wish it works 
> on whatever current A's binary jar, which then need the right libjar 
> dependency when assembly.
>
> And I know it seems hard to use profiles to manipulate 
> dependencies. While by theory, I think this is a reasonable 
> requirement that a project do not need to take care of its 
> dependencies' internal implementation of what it depends on, It just 
> wish it works. E.g. if the POM file is installed in a way that when it 
> build with profile, the corresponding dependencies and any other 
> modifying is fill in the final POM file. ( since the profile is not 
> used anyway when resolve dependencies, why keep it there? For source 
> jar? ) Then those project depend on it won't worry about A's profile, 
> it's already the correct one which been used on building A with this 
> installed or downloaded binary jar.
>
> So , using profile might not be the right solution, While if 
> there isn't an automatic way to meet this requirement, can I take it 
> as a feature missing?
>
> Best Regards,
> Raymond Liu
>
> -Original Message-
> From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
> Sent: Tuesday, December 10, 2013 6:57 PM
> To: Maven Users List
> Subject: Re: How to resolve right dependency which enabled and 
> built/install with profile?
>
> Using profiles to manipulate dependencies is a route to madness.
>
> An modules dependencies should be a constant... It was a mistake to 
> allow  within .
>
> The correct solution is to create additional modules that aggregate in 
> the corresponding lib versions (this is also a bad plan, but less 
> worse than your current plan by quite some margin). The additional 
> modules would depend on A and the respective version of libjar and 
> bundle the two together.
>
> Then B can depend if the corresponding internmediate... Now at this 
> point you will start to see the madness returning... That is if you 
> need two versions of B.
>
> The better solution is to just let B depend in A and then do the 
> fatjar as the final later after B and *override* the transitive dep on 
> libjar in the two fatjar building modules
>
> On Tuesday, 10 December 2013, Liu, Raymond wrote:
>
> > Hi
> >
> > I have a project with module A that will be built with or without 
> > profile say -Pnewlib , thus I can have it build with dif

Re: how to run compile and packaging before test?

[Barrie Treloar]

Please have a look at the freely available books at
http://maven.apache.org/articles.html

These will help you understand the Maven lifecycle and what you should
be doing in each phase.

As Roy points out, you are doing integration tests.
You can also pull these out into their own module so they can be run
independently of the artifact being built.
This is useful if you are just writing more integration tests, as you
dont need to rebuilt the artifact being tested.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Maven does not download the jar but it download the pom

[javi.lse]

I have been reading some question similar issue with downloading the jars but
none seem to be really related to my problem.

I am migrating a project from using Eclipse indigo SR2 runtime to use
eclipse Kepler SR1.

I had created one maven repository with the eclipse bundles that i needed
from indigo SR2 and everything was working fine.

Now, for the migration, i have created a new branch of my project for kepler
SR1. I have created a new repository for eclipse kepler SR1. The pom in the
branch for kepler SR1 is now pointing to the new repository and the
dependencies has been updated accordingly.

Using eclipse IDE indigo SR2 i work on the branch for indigo SR2 for
maintenance Using eclipse IDE kepler SR1 i work on the branch for kepler SR1
on new fetures for the future release.

At least that was the plan.

The issue is that when running mvn clean package -U (both from the command
line and within eclipse) on the kepler SR1 only the poms were downloaded but
not the jars. No matter what i try the jars would not get downloaded.

For trouble shooting i cleared the local maven repository. Then I run maven
on the kepler branch first, the jar were downloaded. However when after i
tried to run maven on the indigo sr2 project only the poms were downloaded.

So on a clean local repository, only the project on which maven is run first
will download both the jar and the poms and the other will only download the
poms

I have really run out of ideas, so i would apreaciate if somebody could
point me towards where the problem may be.

I tried with maven 3.0.4 and 3.0.5

Version range are not use in any of the poms, below is an extract of the
dependency definition.


  org.eclipse.emf.ecore
  xmi
  [2.9.1]


  org.eclipse.emf
  edit
  [2.9.0]


cheers, 



--
View this message in context: 
http://maven.40175.n5.nabble.com/Maven-does-not-download-the-jar-but-it-download-the-pom-tp5778273.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: how to run compile and packaging before test?

[Andrew E. Davidson]

Hi Roy

we use


org.apache.maven.plugins
maven-surefire-plugin


is this a problem?

Andy

On Dec 11, 2013, at 3:19 PM, "Lyons, Roy"  wrote:

> I have a feeling that you aren't running unit tests, but instead
> integration tests...
> 
> http://maven.apache.org/surefire/maven-failsafe-plugin/ is what you want!
> that happens after the package phase.
> 
> On 12/11/13 4:57 PM, "Andrew E. Davidson"  wrote:
> 
>> 
>> Hi 
>> 
>> my unit test require I a *.tar.gz. The *.tar.gz needs to include the 3rd
>> party dependencies and the projects jar file artifact.
>> 
>> I tried using an assembly and setting the phase, so it will run before
>> the unit tests run, how ever my project artifact has not been packaged yet
>> 
>> Any comments or suggestions would be greatly appreciated
>> 
>> Andy
>> 
>> $ mvn -version
>> Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19
>> 05:51:28-0800)
>> 
>> from my pom.xml
>> 
>>  
>>  
>>  org.apache.maven.plugins
>>  maven-assembly-plugin
>>  2.4
>>  
>>  
>>  createTarball-assembly
>>  
>>  
>> process-test-classes
>>  
>>  single
>>  
>>  false
>>  
>>  
>>  
>>  
>>   
>> src/createTarballAssembly.xml
>>  
>>  
>> ${project.build.finalName}
>>  
>> false
>>  
>>  
>> 
>> 
>> 
>> here is my assembly file
>> 
>> >  
>> xmlns="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1
>> .0"
>>  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>>  
>> xsi:schemaLocation="http://maven.apache.org/plugins/maven-assembly-plugin
>> /assembly/1.1.0 http://maven.apache.org/xsd/assembly-1.1.0.xsd";>
>> 
>>  
>> 
>>  createTarball-assembly
>>  
>>  tar.gz
>>  
>>  false
>>  
>>  
>>  
>>  
>> ${project.build.directory}/${project.build.finalName}> e>
>>  aid-athena-common
>>  
>>  true
>>  false
>>  runtime
>>  lib
>>  
>>  
>>  
>>  
>>  
>>  
>> 
>> 
> 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
> 

Re: how to run compile and packaging before test?

[Lyons, Roy]

I have a feeling that you aren't running unit tests, but instead
integration tests...

http://maven.apache.org/surefire/maven-failsafe-plugin/ is what you want!
that happens after the package phase.

On 12/11/13 4:57 PM, "Andrew E. Davidson"  wrote:

>
>Hi 
>
>my unit test require I a *.tar.gz. The *.tar.gz needs to include the 3rd
>party dependencies and the projects jar file artifact.
>
>I tried using an assembly and setting the phase, so it will run before
>the unit tests run, how ever my project artifact has not been packaged yet
>
>Any comments or suggestions would be greatly appreciated
>
>Andy
>
>$ mvn -version
>Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19
>05:51:28-0800)
>
>from my pom.xml
>
>   
>   
>   org.apache.maven.plugins
>   maven-assembly-plugin
>   2.4
>   
>   
>   createTarball-assembly
>   
>   
> process-test-classes
>   
>   single
>   
>   false
>   
>   
>   
>   
>
> src/createTarballAssembly.xml
>   
>   
> ${project.build.finalName}
>   
> false
>   
>   
>
>
>
>here is my assembly file
>
>   
> xmlns="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1
>.0"
>   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>   
> xsi:schemaLocation="http://maven.apache.org/plugins/maven-assembly-plugin
>/assembly/1.1.0 http://maven.apache.org/xsd/assembly-1.1.0.xsd";>
>
>   
>
>   createTarball-assembly
>   
>   tar.gz
>   
>   false
>   
>   
>   
>   
> ${project.build.directory}/${project.build.finalName}e>
>   aid-athena-common
>   
>   true
>   false
>   runtime
>   lib
>   
>   
>   
>   
>   
>   
>
>


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

how to run compile and packaging before test?

[Andrew E. Davidson]

Hi 

my unit test require I a *.tar.gz. The *.tar.gz needs to include the 3rd party 
dependencies and the projects jar file artifact. 

I tried using an assembly and setting the phase, so it will run before the unit 
tests run, how ever my project artifact has not been packaged yet

Any comments or suggestions would be greatly appreciated

Andy

$ mvn -version
Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 
05:51:28-0800)

from my pom.xml



org.apache.maven.plugins
maven-assembly-plugin
2.4


createTarball-assembly


process-test-classes

single

false




 
src/createTarballAssembly.xml


${project.build.finalName}

false





here is my assembly file

http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";

xsi:schemaLocation="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0
 http://maven.apache.org/xsd/assembly-1.1.0.xsd";>



createTarball-assembly

tar.gz

false




${project.build.directory}/${project.build.finalName}
aid-athena-common

true
false
runtime
lib

Re: Rsync Plugin?

[Phil Lello]

Several years late, but I've written a prototype rsync wagon, called
rsync-maven-wagon. It's available through maven central, and the homepage is 
http://www.pcl-solutions.com/maven/rsync-maven-wagon/1.0/
  
Please use the linked mailing lists from that page for feedback, help and
support

Phil Lello



--
View this message in context: 
http://maven.40175.n5.nabble.com/Rsync-Plugin-tp88184p5778268.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: Overriding artifact to be installed/deployed

[Ron Wheeler]

I think that your suggestion has a lot of merit.
It is easier to optimize something that works than to try to make 
something new without a set of working components.


Ron

On 11/12/2013 11:50 AM, Bruce Albrecht wrote:

One of my teams is trying to build a bundled application that first
builds a jar file using the jar plugin and then uses maven-exec plugin
to run something that bundles the jar file into a specialized osgi
bundle.  When we run the mvn install or deploy, it will deploy the jar
file created by the jar plugin. Is there some way to override the
artifact location so that it will upload the bundled jar?  Currently
this is all done in a single project, and I'm beginning to wonder if the
way to go is to change it to a multi-module project, with one module to
create the jar file, and a second module to create the bundled jar, and
use build-helper:attach-artifact to attach the bundled jar. They don't
need the unbundled jar to be uploaded to the repository.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org





--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Overriding artifact to be installed/deployed

[Bruce Albrecht]

One of my teams is trying to build a bundled application that first
builds a jar file using the jar plugin and then uses maven-exec plugin
to run something that bundles the jar file into a specialized osgi
bundle.  When we run the mvn install or deploy, it will deploy the jar
file created by the jar plugin. Is there some way to override the
artifact location so that it will upload the bundled jar?  Currently
this is all done in a single project, and I'm beginning to wonder if the
way to go is to change it to a multi-module project, with one module to
create the jar file, and a second module to create the bundled jar, and
use build-helper:attach-artifact to attach the bundled jar. They don't
need the unbundled jar to be uploaded to the repository.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: How to resolve right dependency which enabled and built/install with profile?

[Stephen Connolly]

You are looking for the impossible.

You want A to work with any version of libjar

You want B to use A but not know which version of libjar the A it is using
depends on... actually to be independent of the version of libjar that A
depends on... but also to bundle the specific one...

Rethink what you are asking and you will see that you are asking an
impossible request... you are asking somebody to hop on one leg and
mandating that the one leg be both their left and right leg.

When you are asking an impossibility, that is usually a sign that you are
going at things the wrong way.

If A is going to become part of a fatjar at some point, you need to make a
decision *at the point of creating the fatjar* as to which libjar will be
included within A.

Or else perhaps, you include all versions of libjar and provide a means for
A to decide which version it wants... there are many ways to achieve this...

* use the service provider pattern to introduce another shim layer and then
use the shade plugin to put all the shim impl libjar deps into independent
package namespaces
* use a custom classloader and package libjar as resources, so that A's
entry point loads the correct libjar at runtime
* etc.

With the above you would be including *all* versions of libjar within A and
the whole thing becomes moot anyway...

-Stephen


On 11 December 2013 00:52, Liu, Raymond  wrote:

> Thanks Stephen
>
> I see your solution is let B manage the libjar version. While this
> is against my wish, I wish B to know nothing about A's internal
> implementation. In the future, A might depends on a v3.0 libjar, I do wish
> to just repackage B to make it work not revise B's code or assembly rules.
> And sometime A might be buried deep in the dependent tree, Those project
> might not even aware it depends on A, they just wish it works on whatever
> current A's binary jar, which then need the right libjar dependency when
> assembly.
>
> And I know it seems hard to use profiles to manipulate
> dependencies. While by theory, I think this is a reasonable requirement
> that a project do not need to take care of its dependencies' internal
> implementation of what it depends on, It just wish it works. E.g. if the
> POM file is installed in a way that when it build with profile, the
> corresponding dependencies and any other modifying is fill in the final POM
> file. ( since the profile is not used anyway when resolve dependencies, why
> keep it there? For source jar? ) Then those project depend on it won't
> worry about A's profile, it's already the correct one which been used on
> building A with this installed or downloaded binary jar.
>
> So , using profile might not be the right solution, While if there
> isn't an automatic way to meet this requirement, can I take it as a feature
> missing?
>
> Best Regards,
> Raymond Liu
>
> -Original Message-
> From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
> Sent: Tuesday, December 10, 2013 6:57 PM
> To: Maven Users List
> Subject: Re: How to resolve right dependency which enabled and
> built/install with profile?
>
> Using profiles to manipulate dependencies is a route to madness.
>
> An modules dependencies should be a constant... It was a mistake to allow
>  within .
>
> The correct solution is to create additional modules that aggregate in the
> corresponding lib versions (this is also a bad plan, but less worse than
> your current plan by quite some margin). The additional modules would
> depend on A and the respective version of libjar and bundle the two
> together.
>
> Then B can depend if the corresponding internmediate... Now at this point
> you will start to see the madness returning... That is if you need two
> versions of B.
>
> The better solution is to just let B depend in A and then do the fatjar as
> the final later after B and *override* the transitive dep on libjar in the
> two fatjar building modules
>
> On Tuesday, 10 December 2013, Liu, Raymond wrote:
>
> > Hi
> >
> > I have a project with module A that will be built with or without
> > profile say -Pnewlib , thus I can have it build with different version
> > of library dependency let's say by default use libjar-1.0 and when
> > -Pnewlib will use libjar-2.0.
> >
> > Then, I have a module B to depends on module A. The issue is that how
> > can I get the right dependency in module B for libjar? I want to
> > assemble a fat jar so I need to figure out which version of libjar to
> include.
> >
> > In my test, it seems to me that when mvn -Pnewlib install module A,
> > though it will build with libjar-2.0. but the installed pom do not
> reflect this.
> > Thus when module B resolve the dependency, it will resolve the
> > dependency as libjar-1.0 ( though when building module B, -Pnewlib is
> > also passed in, But I think this will not pass to the dependent
> > package when resolve the dependency).
> >
> > I don't want to have module B know anything about the libjar-1.0 and
> > libjar-2.0. it

Painless way to update a frameworks group id?

[Christofer Dutz]

Hi,



I am the current maintainer of the Flexmojos Maven Plugin and contributor to 
the Apache Flex Project.

Currently I am working on a new Version of Flexmojos which is able to work with 
Flex SDKs that have a groupId of org.apache.flex instead of the old 
com.adobe.flex. While building applications with the new groupId was no big 
Problem, we are now facing a Problem, that I don't quite know how to elegantly 
solve it.



Assuming I am building a Project and I switched the groupId of the Flex 
Framework to "org.apache.flex". As Long as I am building all artifacts in the 
Project this is fine. But as soon as I am using a Flex library that was built 
for com.apache.flex Maven correctly adds that artifacts dependencies to the 
build. Unfortunately this way I have several artifacts in my build twice ... 
once with com.adobe.flex and once with org.apache.flex groupId.



Now I was suggesting to manually exclude Framework artifacts when using an 
external lib, but I would like to automate this. Therefore I suggested to add 
all the org.apache.flex artifacts as com.adobe.flex artifacts, but to set the 
scope on These to "provided". But it still sort of doesn't feel right.



Any suggestions? Would be really happy to sort this out and make it less 
painfull for my users.



Chris

Re: Sonar with Maven: Fail to connect to database: Cannot loa d JDBC driver class 'oracle.jdbc.OracleDriver'

[Omar@Gmail]

Thanks Richard,

Sounds like you know your stuff. I will check and confirm. Many Thanks

Omar


On 11 December 2013 03:05, Richard Vowles wrote:

> Sonar downloads everything it needs (jar file wise) inside the plugin and
> adds them to its Maven plugin classpath. If Sonar isn't doing this
> properly, its Sonar's fault (I have spent *way* too much time in the
> internals of Sonar).
>
>
> On Tue, Dec 10, 2013 at 11:34 AM, Omar@Gmail  >wrote:
>
> > OK I see, so we are throwing it over the fence :)
> >
> > Sonar has very nice solution for it's side which is a folder under lib to
> > hold jdbc drivers, shame Maven doesn't. Seems I have to stick with
>  hacking
> > the mvn script file. Thanks guys this is done with.
> >
> >
> >
> >
> > On 9 December 2013 22:06, Robert Scholte  wrote:
> >
> > > I agree with David. The Sonar team should be able to help you.
> > > I had a small look at the code of the *plugin*[1], and it doesn't
> contain
> > > any references to JDBC drivers.
> > > Sonar probably has a trick, which reuses the Maven classpath.
> > > Anyhow, they know the trick, so they should know the solution for you.
> > >
> > > Robert
> > >
> > > [1] http://mojo.codehaus.org/sonar-maven-plugin/xref/index.html
> > >
> > > Op Mon, 09 Dec 2013 22:46:51 +0100 schreef Omar@Gmail <
> > > omarnet...@googlemail.com>:
> > >
> > >
> > >  Thanks David,
> > >>
> > >> The problem is Maven side as  I have clearly explained so not not sure
> > why
> > >> I should pursue this on Sonar user list.
> > >>
> > >> Explain to me why you still think it is a Sonar issue.
> > >>
> > >>
> > >>
> > >> On 9 December 2013 00:44, David Karr 
> > wrote:
> > >>
> > >>  I suggest you pursue this on the Sonar user list, then.
> > >>>
> > >>> On Sun, Dec 8, 2013 at 11:55 AM, Omar@Gmail <
> omarnet...@googlemail.com
> > >>> >wrote:
> > >>>
> > >>> > Thanks David,
> > >>> >
> > >>> > Yes Sonar on separate server.
> > >>> >
> > >>> > Also please see
> > >>> > http://www.mail-archive.com/users@maven.apache.org/msg132123.html
> > >>> >
> > >>> >
> > >>> > On 8 December 2013 18:31, David Karr 
> > >>> wrote:
> > >>> >
> > >>> > > I assume that your Sonar server is not the box you're running
> Maven
> > >>> on?
> > >>> > >
> > >>> > > What Sonar properties are you setting in your settings.xml?  Feel
> > >>> free
> > >>> to
> > >>> > > omit the value for each if you need to.
> > >>> > >
> > >>> > > In the Sonar installation instructions there is a section titled
> > >>> "Adding
> > >>> > > the JDBC Driver" which talks about adding the Oracle JDBC driver
> to
> > >>> the
> > >>> > > SONAR installation.  Have you done this?
> > >>> > >
> > >>> > >
> > >>> > >
> > >>> > >
> > >>> > > On Sat, Dec 7, 2013 at 4:33 AM, Omar@Gmail <
> > >>> omarnet...@googlemail.com
> > >>> > > >wrote:
> > >>> > >
> > >>> > > > Objective: Get Maven to publish sonar results to running Sonar
> > >>> server
> > >>> > > >
> > >>> > > > Steps:
> > >>> > > >
> > >>> > > >- Installed and ran Sonar, accessible from browser
> > >>> > > >   - The back-end database is Oracle
> > >>> > > >-
> > >>> > > >
> > >>> > > >Installed and configured Maven in settings.xml file to
> connect
> > >>> to
> > >>> > the
> > >>> > > >Oracle db
> > >>> > > >-
> > >>> > > >
> > >>> > > >Invoked: mvn clean install -DSkipTests=true
> > >>> > > >- Invoke: mvn sonar:sonar
> > >>> > > >
> > >>> > > > But getting following mvn sonar:sonar Fail to connect to
> > database:
> > >>> > Cannot
> > >>> > > > load JDBC driver class 'oracle.jdbc.OracleDriver'
> > >>> > > >
> > >>> > > > So I need somehow to put the ojdbc6.jar on Maven classpath.
> Tried
> > >>> > placing
> > >>> > > > the ojdbc6.jar in /lib and lib/ext but did not help.
> > >>> > > >
> > >>> > > > Am I missing something here? please help.
> > >>> > > >
> > >>> > > > To fix this I modified *maven113home/bin/mvn*.bat at line 161
> and
> > >>> added
> > >>> > > >
> > >>> > > > %MAVEN_JAVA_EXE% %MAVEN_OPTS% -classpath path/to/ojdbc6.jar;...
> > >>> > > >
> > >>> > > > *Which is nasty!*
> > >>> > > >
> > >>> > > > Please suggest a better approach.
> > >>> > > >
> > >>> > >
> > >>> >
> > >>>
> > >>
> > > -
> > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > > For additional commands, e-mail: users-h...@maven.apache.org
> > >
> > >
> >
>
>
>
> --
> ---
> Richard Vowles,
> Groovy, Java, Javascript, AngularJS
>
> ph: +64275467747, google+:plus.to/Richard.Vowles 
>