Gilles Scokart wrote on 10/08/2008 09:40 AM:
I would like to start with the easiest : the compile path. (Next I
would try to do the same for test classpath, and maybe for runtime
classpath)
I would like to push my build to an extreme solution. I want to make
a build fail if some jars of the com
ds or forwards compatible. A real flag day!
---
Kirby Files
Software Architect
Masergy Communications
kfi...@masergy.com
CalvinJ wrote on 01/21/2009 08:13 PM:
I'm guessing I've configured something wrong but when using Ivy
2.0.0rc2 and IvyDE 2.0.0beta1 in Eclipse 3.3, it works the first
time you set it up on a project. But when you change any
dependencies in ivy.xml outside of Eclipse, it never picks up the
change.
http://repository.springsource.com/ivy/bundles/external/[organisation]/[module]/[revision]/[artifact]-[revision].[ext]";
/>
ref="jcom.springsource.repository.bundles.external"/>
Thanks,
---
Kirby Files
Software
Tyler Kocheran wrote on 02/04/2009 01:57 PM:
The error actually turned out to be in this line:
If I change that line to something else that's a real package, like
"org.springframework.orm", it works. How do I download the entire Spring
Framework, though? If I can't figure that out, whatever, I
nding good resolvers on the web? It
seems the main problem with Ivy is not having all of the correct resolvers.
Well, I use these two all of the time:
On Wed, Feb 4, 2009 at 11:21 AM, Kirby Files wrote:
Tyler Kocheran wrote on 02/04/2009 01:57 PM:
The error actually turned out to be in this li
esolver is the maven2 repo.
Also, the Ivy Roundup package resolver provides lots of modules for
projects which do not have a repository:
http://code.google.com/p/ivyroundup/
Thanks,
---
Kirby Files
Software Architect
Masergy Communications
kfi...@masergy.com
atching on
the module name; (3) the top-level of the jar packages; (4) if all
else fails. just ask the user.
Note the script requires all jars to follow the naming convention
module-ver.jar. Too few jars have relevant and consistent metadata
within their MANIFEST to do otherwise.
Thanks,
---
K
Nicolas Lalevée wrote on 03/25/2009 11:29 AM:
The worksapce resolver implemented in the beta1 is a sort of workaround. The
process implemented is to launch a normal resolve. Then if some of the
resolved dependency is mathing the organization name and module name of some
project in your Eclipse wo
with branch_A specified will show up in the list.
As always, Shawn, I am in awe of your descriptions of your dev/build
environment. You clearly get a lot more out of ant/ivy than most.
---
Kirby Files
Software Architect
Masergy Communications
kfi...@masergy.com
I had similar issues when using retrieved libs in my compile and test stages.
The solution is instead to use ivy:cacheclasspath to populate the build and
test classpath, and only use retrieve for deployment.
Thanks,
Kirby Files
-Original Message-
From: Imner, Andreas
Sent: Friday
11 matches
Mail list logo