Stephen McConnell wrote:

Mark R. Diggory wrote:



Stephen McConnell wrote:

Mark R. Diggory wrote:

I guess what I need is a list of all the avalon maven project-id's that your already processing into ibiblio.org/maven/ on your own. Is this all of avalon, or just parts?




Certainly not all. Here is the list:

  avalon-util
  avalon-meta
  avalon-repository
  avalon-activation
  avalon-composition
  avalon-http
  avalon-jmx
  merlin
  merlin/tutorial



So, what I will do is eliminate these from /dist/java-repository because they are already being processed into ibibilo.org/maven by you guys. If you decide you want to have them end up at ibiblio by placing them into /dist/java-repository, then I'll leave that up to you.



Works for me.


Keep in mind that can redirect interim content to another location without too much trouble.

Stephen.


Can I ask: Who in Avalon is not using maven (this includes ant build scripts generated by maven) as their build tool?


Maven is kind of a prereq (but its a love hate relationship). I don't think ant build scripts are being used for anything by gump related stuff. There is still content in Avalon that is mavenized but its growing smaller.

s/that is mavenized/that is *not* mavenized


SJM

The real missing link is a solid reliable maven
release. Currently we have to use beta-10 for site builds - and RC1 seems to be generating more problems than it is solving. A RC2 that builds Avalon artifacts and site is way up high on the wish list.

Stephen.


-Mark





--

|------------------------------------------------|
| Magic by Merlin                                |
| Production by Avalon                           |
|                                                |
| http://avalon.apache.org/merlin                |
| http://dpml.net/merlin/distributions/latest    |
|------------------------------------------------|

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to