Awesome! :(
I am not a Groovy developer. In fact Gradle is really the first time I
have played with Groovy. So terms like "duck typing" have zero meaning
to me.
Regardless, this is very disappointing. Especially considering I know I
am just going to have to turn around and change this again for m4 due to
this new "publishing api" (assuming it actually makes it in this time).
On 05/05/2011 11:47 AM, Peter Niederwieser wrote:
Steve Ebersole wrote:
This is holding up a release
(http://lists.jboss.org/pipermail/hibernate-dev/2011-May/006411.html),
so please if anyone has ideas...
To cut a long story short, the only solution I can think of right now is to
port the code that references Maven types to Groovy and then get rid of
those type references (i.e. use duck typing). Or stick to Java and use
reflection.
--
Peter Niederwieser
Developer, Gradle
http://www.gradle.org
Trainer& Consultant, Gradleware
http://www.gradleware.com
Creator, Spock Framework
http://spockframework.org
--
View this message in context:
http://gradle.1045684.n5.nabble.com/MavenDeployer-MavenRepository-tp4371835p4373316.html
Sent from the gradle-user mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
--
Steve Ebersole <[email protected]>
http://hibernate.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
