geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Jencks <david_jen...@yahoo.com>
Subject Re: Weird HEAD build problem, maven 1.0.2
Date Sun, 02 Oct 2005 01:11:40 GMT
so you are saying this works in 1.0.2 in one multiproject build, and 
the reactor will figure out the correct order?

build modules 1-5
build plugin, call plugin:install-now in this module
build modules 6-10 that use plugin: include dependency on plugin module 
in project.xml

or did I misunderstand?  I've spent several days trying to get this to 
work in the past so I'm not too keen to spend a lot of time 
experimenting.

thanks
david jencks

On Oct 1, 2005, at 4:08 PM, Brett Porter wrote:

> I think this was more the case that it works on the second run because
> the plugin is installed?
>
> Plugin dependencies should do what you want and work in maven 1.0.2+.
> When using a dependency, you only need to call
> plugin:repository-install (install to repo, not Maven) instead of
> plugin:install (which doesn't work in the same instance). Another
> alternative is plugin:install-now (installs permanently, and into the
> running instace).
>
> And yes, all plugins are plugin dependencies in m2 and this works out
> of the box.
>
> HTH,
> Brett
>
> On 10/2/05, Aaron Mulder <ammulder@alumni.princeton.edu> wrote:
>> It looks like it's fixed in Maven 1.1 beta 2.  I guess we ought to
>> push everyone in that direction.
>>
>> Thanks,
>>     Aaron
>>
>> On 10/1/05, David Jencks <david_jencks@yahoo.com> wrote:
>>> This is a symptom of a different problem, that you can't build a 
>>> plugin
>>> and use it in the same build (at least not reliably, as far as I can
>>> tell)  magicGball now uses the deployment plugin which has 
>>> deploy-jsr88
>>> as a dependency.  If the plugin isn't built you will get a related
>>> error when you get to assembly.
>>>
>>> It might help to include a dependency on the deploy plugin in
>>> project.xml.  However, I have faint memories that this might cause
>>> other problems.  In general I've found maven 1 to have problems
>>> building a plugin and using it in the same multiproject build.  I 
>>> don't
>>> know if this is fixed in maven 1.1, I believe it is fixed in maven 2.
>>>
>>> Wish I had better news,
>>> david jencks
>>>
>>> On Oct 1, 2005, at 8:09 AM, Aaron Mulder wrote:
>>>
>>>> When I do a rebuild-all on HEAD, I get (eventually):
>>>>
>>>> +----------------------------------------
>>>> | Executing default The Magic G Ball
>>>> | Memory: 67M/83M
>>>> +----------------------------------------
>>>> You are working offline so the build will continue, but
>>>> geronimo-common-1.0-SNAPSHOT.jar may be out of date!
>>>> You are working offline so the build will continue, but
>>>> geronimo-kernel-1.0-SNAPSHOT.jar may be out of date!
>>>> You are working offline so the build will continue, but
>>>> geronimo-deployment-1.0-SNAPSHOT.jar may be out of date!
>>>> You are working offline so the build will continue, but
>>>> geronimo-system-1.0-SNAPSHOT.jar may be out of date!
>>>>
>>>> BUILD FAILED
>>>> File......
>>>> /Users/ammulder/.maven/cache/maven-multiproject-plugin-1.3.1/
>>>> plugin.jelly
>>>> Element... maven:reactor
>>>> Line...... 217
>>>> Column.... 9
>>>> The build cannot continue because of the following unsatisfied
>>>> dependency:
>>>>
>>>> geronimo-deploy-jsr88-1.0-SNAPSHOT.jar
>>>>
>>>> Total time: 4 minutes 44 seconds
>>>> Finished at: Sat Oct 01 10:53:15 EDT 2005
>>>>
>>>>
>>>> I don't understand why it wants geronimo-deploy-jsr88 even though
>>>> that's not listed as a dependency in project.xml for the magic G 
>>>> ball.
>>>>  In any case, if that's a prerequisite, shouldn't something force 
>>>> the
>>>> deploy-jsr88 module to be built before the magic G ball module?
>>>>
>>>> Thanks,
>>>>     Aaron
>>>>
>>>
>>>
>>
>


Mime
View raw message