version info in the POM. But then arise next problem, Ivy can't read
version ranges, so plugin resolution fails. dependOn with fixed versions
> On Thu, Jul 14, 2011 at 10:04 AM, Mos<
[hidden email]> wrote:
>> Hi Graeme,
>>
>>> Sorry what is the problem with the information from dependsOn going in the
>>> POM?
>> As described in other threads and some JIRAs the version specifications
>> like
>> def dependsOn = ['myNewsletter':'0.1> *']
>> goes straight into the POM definition (including a ] when I remember right).
>> "0.1>*]" seems not to be valid for POMs and breaks the Grails dependency
>> resolution.
>>
>> For me it works to remove the lines 276 to 307 in
>>
https://github.com/grails-plugins/grails-release/blob/master/scripts/_GrailsMaven.groovy#L276> Maybe you're using an older version of the release plugin?
>
> Because the current code contains handling to transform invalid
> version syntax (like "0.1> *") to valid version syntax (like "[0.1,)"
>
> Cheers
>
>> Because the BuildConfig files are holding my dependency definitions the
>> dependsOn section
>> doesn't need to be parsed.
>>
>> Cheers,
>> Mos
>> ---
>>
http://www.mosbase.com/>>
>>
>> On Wed, Jul 13, 2011 at 11:23 PM, Graeme Rocher<
[hidden email]> wrote:
>>> Sorry what is the problem with the information from dependsOn going in the
>>> POM?
>>>
>>> Can you elaborate on what issue that caused?
>>>
>>> Thanks
>>>
>>> On Wed, Jul 13, 2011 at 10:43 PM, Mos<
[hidden email]> wrote:
>>>> Thanks for pointing me to the release-plugin.
>>>>
>>>> It's better, but for our project we still had two issues:
>>>>
>>>> 1.) The POM file includes definitions from the dependsOn section
>>>> (inluding
>>>> invalid version specification)
>>>> Solution: I patches the Plugin just reading the information from
>>>> the
>>>> BuildConfig and ignoring the dependsOn for the POM generation
>>>>
>>>> 2.) A custom groupId make the dependency resolution of Grails 1.3.7
>>>> still
>>>> unstable.
>>>> Solution: I gave up and work now with the standard groupId:
>>>> org.grails.plugins
>>>>
>>>> I hope so much that with Grails 2.0 Plugin management will be much more
>>>> stable and straight forward!
>>>>
>>>>
>>>> Cheers,
>>>> Mos
>>>> ---
>>>>
http://www.mosbase.com/>>>>
>>>>
>>>> On Mon, Jul 11, 2011 at 6:15 PM, Peter Ledbrook<
[hidden email]>
>>>> wrote:
>>>>>> The 'com.myGroup:' specifies the groupId of the related plugin.
>>>>>> This seems to be required by the maven-Publisher-Plugin to generate a
>>>>>> valid
>>>>>> POM like:
>>>>>> ....
>>>>>> <dependency>
>>>>>> <groupId>com.myGroup</groupId>
>>>>>> <artifactId>my-other-plugin</artifactId>
>>>>>> <version>0.9.5</version>
>>>>>> <type>zip</type>
>>>>>> </dependency>
>>>>>> ....
>>>>>>
>>>>>> But when running Grails maven-install (or any other Grails command)
>>>>>> it
>>>>>> failed with:
>>>>>> Environment set to production
>>>>>> Error: The following plugins failed to load due to missing
>>>>>> dependencies:
>>>>>> [geniosCms]
>>>>>> - Plugin: cms
>>>>>> - Dependencies:
>>>>>> ! com.myGroup:myOtherPlugin (Required: 0.9.5, Found: Not
>>>>>> Installed)
>>>>>> [INVALID]
>>>>> I recommend replacing 'dependsOn' with a dependency declared in
>>>>> BuildConfig.groovy and published with the Release plugin (which is the
>>>>> new name for Maven Publisher). You might also be interested in my
>>>>> replies to Goran's recent emails about the Release plugin.
>>>>>
>>>>> Peter
>>>>>
>>>>> --
>>>>> Peter Ledbrook
>>>>> Grails Advocate
>>>>> SpringSource - A Division of VMware
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe from this list, please visit:
>>>>>
>>>>>
http://xircles.codehaus.org/manage_email>>>>>
>>>>>
>>>>
>>>
>>>
>>> --
>>> Graeme Rocher
>>> Grails Project Lead
>>> SpringSource - A Division of VMware
>>>
http://www.springsource.com>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe from this list, please visit:
>>>
>>>
http://xircles.codehaus.org/manage_email>>>
>>>
>>
>
>
Locked
