Hi Carlos!
> that topic was already brought before and didn't succeed
Do you remember what the problem was?
Ciao,
Mario
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi!
> If project A says it depends on B 1.0 and C says it depends on B 1.1,
> there's a conflict in Maven, Ant and anything you want to use, the
> difference is that Maven tries to do it for you, but you still can
> override that behaviour.
We also ended up putting our jars in svn again and using o
Hi!
No one interested?
> Hi!
>
> Given I might find some time I would like to implement the possibility
> to
>
> a) add arguments to the buildcommands.
> b) to define dependencies should be exported
>
> a)
> I would like to archive this by allowing to add a CDATA section to every
> buildcommand i
Hi!
Given I might find some time I would like to implement the possibility
to
a) add arguments to the buildcommands.
b) to define dependencies should be exported
a)
I would like to archive this by allowing to add a CDATA section to every
buildcommand in pom.xml.
So in the end it should look like
jsch 0.1.23
---
Key: MAVENUPLOAD-579
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-579
Project: maven-upload-requests
Type: Wish
Reporter: Mario Ivankovits
Please upload this new version used by commons-vfs.
Thanks!
Mario
--
This message is
