I definitely agree the current maven build is a problem. Is it not
possible to fix that build to get around some of these problems, though?
The worst aspect of the maven build is the many-times-repeated checks
and multiple downloads of jars. If this behavior is truly unavoidable
when using maven for a multiproject build then we should enter a bug
against maven, because the repeated checks and downloads create the
potential for a broken distribution. maven should treat each particular
dependency as atomic for a build, and only check each dependency once.
- Dennis
Davanum Srinivas wrote:
Maven2 is not there yet. Geronimo dev team is struggling to get things
working. FYI, All our custom maven.xml stuff will have to be thrown
out completely.
-- dims
On 4/27/06, Eran Chinthaka <[EMAIL PROTECTED]> wrote:
While Deepal is reverting this, I'd like to suggest one short term
solution and one long term solution for this.
Short term solution : I wrote a script that will create a zip of a maven
repository that can be downloaded by anyone. This zip will be updated
once per day. Anyone setting up Axis2, can first checkout Axis2. Then
download that zip. Unzip that to maven local repository and he is gtg.
This was initially suggested by Sanjiva.[1]
Long term solution : Move in to maven2, which we think have fixes for
some of the problems we are facing now.
Comments ?
-- Chinthaka
[1] http://marc.theaimsgroup.com/?l=axis-dev&m=114570024014379&w=2
Davanum Srinivas wrote:
ok. please revert this change.
thanks,
dims
On 4/27/06, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:
So is that OK if I revert the changes till 1.0 release ? :)
I am always +1 on listening to people's problems , but at this point I
have to selfish otherwise it will make problems for the release testing .
Sanjiva Weerawarana wrote:
We've had these problems for months .. can we please defer this change
for until after this week when we expect to have 1.0 ready? Surely we
can wait for a week; whatever problems people have been having we've
lived with them for so long!
Sanjiva.
On Thu, 2006-04-27 at 18:07 +0530, Deepal Jayasinghe wrote:
We always listen to ppl , but at this point I am not happy with that
change :((
Davanum Srinivas wrote:
drop the jar in lib or fix the override path to your maven local repo.
Guys,
You are *NOT* listening to people's problems :(
thanks,
dims
On 4/27/06, Eran Chinthaka <[EMAIL PROTECTED]> wrote:
I think the next move is to remove maven also as we do not need it
anymore with these changes. Nice !! ;)
Imagine I just did a change to Axiom and now I'm gonna build Axis2. What
are the steps I should follow, with these new changes.
BTW, I'm 0- on this change.
-- Chinthaka
Srinath Perera wrote:
Hi Dims;
Does that mean dependancy jars are with the source and I am going to
get them when I do a checkout?
If yes, :( One main avantage with maven to me is I can keep source
and jars seperate. I am sure we can handle this with maven ..can't we?
Thanks
Srinath
On 4/27/06, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
Team,
All dependency jars are now in SVN. So if you need to update them, you
will need to check them in explicitly.
Also FYI, here are the snapshots we need to replace with final
releases for 1.0. Hope all the areas are covered (i.e. someone is
working on it especially wss4j and jibx). Did anyone get around to
making the name/package changes for neeti??? Are we going to?
axiom-api-SNAPSHOT.jar
axiom-dom-SNAPSHOT.jar
axiom-impl-SNAPSHOT.jar
jibx-bind-SNAPSHOT.jar
jibx-run-SNAPSHOT.jar
policy-SNAPSHOT.jar
wss4j-SNAPSHOT.jar
XmlSchema-SNAPSHOT.jar
Thanks,
dims
--
Davanum Srinivas : http://wso2.com/blogs/
--
============================
Srinath Perera:
http://www.cs.indiana.edu/~hperera/
http://www.bloglines.com/blog/hemapani
--
Davanum Srinivas : http://wso2.com/blogs/
--
Thanks,
Deepal
................................................................
~Future is Open~
--
Davanum Srinivas : http://wso2.com/blogs/
--
Davanum Srinivas : http://wso2.com/blogs/
