You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Stefan Bodewig <bo...@apache.org> on 2005/01/12 10:59:31 UTC

[Jelly] Re: [GUMP@brutus]: Project commons-jelly (in module commons-jelly) failed

On Tue, 11 Jan 2005, commons-jelly development
<co...@jakarta.apache.org> wrote:
>  __ __
> |  \/  |__ _Apache__ ___
> | |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
> |_|  |_\__,_|\_/\___|_||_|  v. 1.0
> 
> The build cannot continue because of the following unsatisfied
> dependency:
> 
> forehead-1.0-beta-5.jar (try downloading from
> http://forehead.werken.com/)
> 
> Total time: 5 seconds
> Finished at: Tue Jan 11 23:42:04 PST 2005
> 

When built with Ant, Jelly compiled fine without forehead.  Has
anything changed or does project.xml simply claim a dependency that
doesn't exist?

Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Re: [Jelly] Re: [GUMP@brutus]: Project commons-jelly (in module commons-jelly) failed

Posted by Dion Gillard <di...@gmail.com>.
On Wed, 12 Jan 2005 21:12:10 +1100, Brett Porter <br...@apache.org> wrote:

> dion, forehead is essentially dead. I was going to repackage it and
> commons-grant (approved on commons-dev last year) into maven, but I've
> discovered that jelly uses both.
> 
> What do you think is the best alternative here? I'm of the impression that:
> - forehead's 2 or 3 classes (bob will relicense them ASL) get folded
> into both Jelly and Maven as part of their own source tree. They're
> unlikely to change, so I don't think there is any need to sync between them.

Sounds good.

> - commons-grant be folded into jelly-tags-ant (only place it is used),
> and Maven depends on that to obtain the class. Every chance it will go
> away when I get to testing it out with ant 1.6 too.
Also sounds good.

-- 
http://www.multitask.com.au/people/dion/

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Re: [Jelly] Re: [GUMP@brutus]: Project commons-jelly (in module commons-jelly) failed

Posted by Brett Porter <br...@apache.org>.
As promised, I'm actually looking at this now (sorry for the delay). 
Packaging this is probably necessary.

forehead was omitted from the Ant build because it is a runtime dependency.

dion, forehead is essentially dead. I was going to repackage it and 
commons-grant (approved on commons-dev last year) into maven, but I've 
discovered that jelly uses both.

What do you think is the best alternative here? I'm of the impression that:
- forehead's 2 or 3 classes (bob will relicense them ASL) get folded 
into both Jelly and Maven as part of their own source tree. They're 
unlikely to change, so I don't think there is any need to sync between them.
- commons-grant be folded into jelly-tags-ant (only place it is used), 
and Maven depends on that to obtain the class. Every chance it will go 
away when I get to testing it out with ant 1.6 too.

WDYT?

- Brett

Dion Gillard wrote:

>Forehead is a runtime dependency.
>
>
>On Wed, 12 Jan 2005 10:59:31 +0100, Stefan Bodewig <bo...@apache.org> wrote:
>  
>
>>On Tue, 11 Jan 2005, commons-jelly development
>><co...@jakarta.apache.org> wrote:
>>    
>>
>>> __ __
>>>|  \/  |__ _Apache__ ___
>>>| |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
>>>|_|  |_\__,_|\_/\___|_||_|  v. 1.0
>>>
>>>The build cannot continue because of the following unsatisfied
>>>dependency:
>>>
>>>forehead-1.0-beta-5.jar (try downloading from
>>>http://forehead.werken.com/)
>>>
>>>Total time: 5 seconds
>>>Finished at: Tue Jan 11 23:42:04 PST 2005
>>>
>>>      
>>>
>>When built with Ant, Jelly compiled fine without forehead.  Has
>>anything changed or does project.xml simply claim a dependency that
>>doesn't exist?
>>
>>Stefan
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
>>For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>>
>>
>>    
>>
>
>
>  
>


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Re: [Jelly] Re: [GUMP@brutus]: Project commons-jelly (in module commons-jelly) failed

Posted by Brett Porter <br...@apache.org>.
Stefan Bodewig wrote:

>On Wed, 12 Jan 2005, Dion Gillard <di...@gmail.com> wrote:
>
>  
>
>>Forehead is a runtime dependency.
>>    
>>
>
>Hmm, it didn't need them when running unit tests either ...
>
>Anyway.  Does that mean we need to add forehead to Gump in order to
>*build* Jelly?
>
>Stefan
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
>  
>
unfortunate problem in the current state of Maven is that it doesn't 
distinguish between compile time and runtime dependencies, so yes. Apart 
from my other email, this would resolve one of Maven's current 
compiletime dependencies, so adding forehead isn't a bad thing.

- Brett

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Re: [Jelly] Re: [GUMP@brutus]: Project commons-jelly (in module commons-jelly) failed

Posted by Stefan Bodewig <bo...@apache.org>.
On Wed, 12 Jan 2005, Dion Gillard <di...@gmail.com> wrote:

> Forehead is a runtime dependency.

Hmm, it didn't need them when running unit tests either ...

Anyway.  Does that mean we need to add forehead to Gump in order to
*build* Jelly?

Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Re: [Jelly] Re: [GUMP@brutus]: Project commons-jelly (in module commons-jelly) failed

Posted by Paul Libbrecht <pa...@activemath.org>.

Le 12 janv. 05, à 11:02, Dion Gillard a écrit :
> Forehead is a runtime dependency.

... for some special deployment.
Hence maven does wish to download it.

I doubt it'd be easy to avoid these dependencies if one wishes to jar 
only.
I know that dependency annotation for a role has been discussed with 
maven users and developers but this is not, yet, matured, I fear.

Is forehead really a problem for gump ?
Should we then try to isolate this dependency (quite some restructuring 
I fear) ?

Maybe an easy to trick would be to change the project.xml before 
running gump to remove some of the dependencies (there's really not 
only this one) using some XPath processing (... chicken and egg but... 
I'd do this with jelly!).

I think there are many other dependencies in jelly's project.xml(s) 
which are only at runtime.

paul

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Re: [Jelly] Re: [GUMP@brutus]: Project commons-jelly (in module commons-jelly) failed

Posted by Dion Gillard <di...@gmail.com>.
Forehead is a runtime dependency.


On Wed, 12 Jan 2005 10:59:31 +0100, Stefan Bodewig <bo...@apache.org> wrote:
> On Tue, 11 Jan 2005, commons-jelly development
> <co...@jakarta.apache.org> wrote:
> >  __ __
> > |  \/  |__ _Apache__ ___
> > | |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
> > |_|  |_\__,_|\_/\___|_||_|  v. 1.0
> >
> > The build cannot continue because of the following unsatisfied
> > dependency:
> >
> > forehead-1.0-beta-5.jar (try downloading from
> > http://forehead.werken.com/)
> >
> > Total time: 5 seconds
> > Finished at: Tue Jan 11 23:42:04 PST 2005
> >
> 
> When built with Ant, Jelly compiled fine without forehead.  Has
> anything changed or does project.xml simply claim a dependency that
> doesn't exist?
> 
> Stefan
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> 
> 


-- 
http://www.multitask.com.au/people/dion/

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org