Working on grails-data-mapping

[Lancaster, Nolan]

Hi,

 

I’ve found a few quirks with the simple map datastore not functioning in a unit test environment like the hibernate datastore does in a full environment.  I checked out the grails-data-mapping project to work on these issues, and I believe I’ve fixed one where embedded entities with custom types do not persist properly.  I modified the test in the grails-datastore-gorm-test sub-project to account for this issue and it is passing. 

 

However, I’d like to run this against my grails project to make sure it works in the real world before submitting a pull request.  I’ve done a gradle install and see the jars in my local maven repo, but haven’t been able to figure out a good way to get grails-core to use my build of the simple datastore instead of the one it comes with.  Could someone give me some advice on what to do from this point?

 

Thanks,

Nolan Lancaster

These messages are subject to a disclaimer. To view the disclaimer, please go to http://www.tritoncontainer.com/tritoncontainer/disclaimer.do

[johnrengelman]

Hey Nolan,

I haven't tried this before, so I would of course defer to those more knowledgeable, but I think, you'll need to modify the build.gradle script in a checked out version of grails-core and do the following:

add mavenLocal to the buildscript.repositories section

change the datastoreVersion number in the 'ext' section to the modified version that you created and published to your maven local

Then you can run mvn install for grails-core which will produce a copy of grails using your modified datastore, then use that custom version of Grails to run your project.

Hope this helps and I didn't lead you astray. 

--

John

On Wednesday, June 27, 2012 at 12:43 PM, Lancaster, Nolan wrote:

Hi,

 

I’ve found a few quirks with the simple map datastore not functioning in a unit test environment like the hibernate datastore does in a full environment.  I checked out the grails-data-mapping project to work on these issues, and I believe I’ve fixed one where embedded entities with custom types do not persist properly.  I modified the test in the grails-datastore-gorm-test sub-project to account for this issue and it is passing. 

 

However, I’d like to run this against my grails project to make sure it works in the real world before submitting a pull request.  I’ve done a gradle install and see the jars in my local maven repo, but haven’t been able to figure out a good way to get grails-core to use my build of the simple datastore instead of the one it comes with.  Could someone give me some advice on what to do from this point?

 

Thanks,

Nolan Lancaster

These messages are subject to a disclaimer. To view the disclaimer, please go to http://www.tritoncontainer.com/tritoncontainer/disclaimer.do

[Lancaster, Nolan]

Hi John,

 

I’ve been trying to make this work, but even after adding mavenLocal() to the top of the repositories block it still pulls the jars out of the grails remote repo.  It seems like your solution should be correct though, so I’m not sure what the issue is.

 

Nolan

 

From: John Engelman [mailto:[hidden email]]
Sent: Wednesday, June 27, 2012 3:39 PM
To: [hidden email]
Subject: Re: [grails-dev] Working on grails-data-mapping

 

Hey Nolan,

I haven't tried this before, so I would of course defer to those more knowledgeable, but I think, you'll need to modify the build.gradle script in a checked out version of grails-core and do the following:

add mavenLocal to the buildscript.repositories section

change the datastoreVersion number in the 'ext' section to the modified version that you created and published to your maven local

 

Then you can run mvn install for grails-core which will produce a copy of grails using your modified datastore, then use that custom version of Grails to run your project.

 

Hope this helps and I didn't lead you astray. 

 

--

John

 

On Wednesday, June 27, 2012 at 12:43 PM, Lancaster, Nolan wrote:

Hi,

 

I’ve found a few quirks with the simple map datastore not functioning in a unit test environment like the hibernate datastore does in a full environment.  I checked out the grails-data-mapping project to work on these issues, and I believe I’ve fixed one where embedded entities with custom types do not persist properly.  I modified the test in the grails-datastore-gorm-test sub-project to account for this issue and it is passing. 

 

However, I’d like to run this against my grails project to make sure it works in the real world before submitting a pull request.  I’ve done a gradle install and see the jars in my local maven repo, but haven’t been able to figure out a good way to get grails-core to use my build of the simple datastore instead of the one it comes with.  Could someone give me some advice on what to do from this point?

 

Thanks,

Nolan Lancaster

These messages are subject to a disclaimer. To view the disclaimer, please go to http://www.tritoncontainer.com/tritoncontainer/disclaimer.do