Open GoogleCodeExporter opened 8 years ago
Hi thanks to interest to this project
1. Personnally I do not like very much how libraries are handled in ant default
project. And I think it will be very confusing to mix the 2, ivy resolved
results and
libraries. That's why I have chosen at the beginning to separate those part.
As for maven projects, I choose to handle libraries very differently from the
ant
default. But differently from maven based projects, you can still with ivy
enabled
projects deal with the old libraries management.
2. You mean rename the "ivy Configuration" node to "Project Files" ? AFAIK, the
"project Files" node does'not exist in ant based project. FYI, In Netbans module
project this kind of node is called : "Important files".
Original comment by laurent....@gmail.com
on 1 May 2009 at 7:17
I think the lib dependency management(add dependency to project or create new
libraries in "Libraries" manager) can be united.
For example , in project properties panel , the "Libraries" can accept
jar/folder,
maven dependency, ivy denpendency, regardless this project is based on ant or
maven.
The dependency item list can display like :
file:///zzz/xxx/yyy.jar
classpath:xxx.jar
ivy:[org][module][artifact][version][jar]
maven:[group]:[artifact]:[version][jar]
The netbeans should parse these items to real system path at runtime.
Original comment by hantsy
on 2 May 2009 at 1:51
If I well understand you, you tell that nevermind the structure of the project
(ant
based or maven) we should have the ability to choose one or another dependency
Manager. It is interesting thought but I think very difficult to apply.
Indeed, when you write "maven:" you are only interested in the dependency
management
offered by maven. But when you talk about project based on maven you mean all
the
maven stuff, and Netbeans delegate (maven is embedded) all the project
management to
maven. And AFAIK there is no way to tell maven to use ivy instead.
Furthermore I think not simple and easy to use maven dependency manager outside
maven
itself.
Maybe OSGi could help here. Too big stuff for instance.
Regards.
Laurent.
Original comment by laurent....@gmail.com
on 2 May 2009 at 9:26
I think such features should be provided by the platform. For more common use, I
think NetBeans should provide more effective and simple approaches to resolve
resource including static resource , resourcebundle, java classes, etc. Add a
maven
dependency and delegate project management to maven sounds unreasonable.
Obviously, I
only want reuse the maven repository to resolve dependency, add a maven
dependency
like "maven:[group]:[artifact]:[version][jar]" can result in adding a classpath
item
like
"/home/<user>/.m2/respository/<group>/<artifact>/<artifact>-<version>.jar".
I think this is the responsibility of NetBeans team.
Netbeans 6.7 provides a way to create "Libraries" from maven dependencies. But
it
does not support create a hybrid "Libraries" as I described before.
I think this project should improve ant project support currently, and provide
more
features about ivy later.
1. global and project specific ivy setting
2. generate project scope ivy repository (add it own namespace to all
libraries).
3. convert ant project libraries to ivy management.
Thanks.
Original comment by hantsy
on 2 May 2009 at 10:16
There is no a downloadable file for 1.1-M2?
Original comment by hantsy
on 2 May 2009 at 10:21
I deprecate this download due to
http://code.google.com/p/ivybeans/issues/detail?id=28
BTW, I plan to make a stable version with the current deatures for the 6.7
release.
Sorry for that.
Original comment by laurent....@gmail.com
on 3 May 2009 at 9:50
Original issue reported on code.google.com by
hantsy
on 1 May 2009 at 2:57