directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ole Ersoy <ole_er...@yahoo.com>
Subject Re: Maven POM Structuring Automation
Date Fri, 01 Dec 2006 18:23:39 GMT
Oh - OK - So just list all the projects and their
corresponding packaging in a report, and based on this
list we know whether we should be expecting repository
issues?


--- "John E. Conlon" <jconlon@verticon.com> wrote:

> Ole, 
> 
> > So I'm taking "Wish Requests" if anyone has
> burning
> > issues, besides the ones we have already thought
> of.
> 
> Scene One Mr.X nervously enters the room. It's his
> first encounter
> with ... the Maven Anonymous Dependency (MAD)
> group...
> 
> X: Hi my name is X and I am dependent on Maven. 
> 
> Maven Anonymous: Hello X.
> 
> X: My burning issue with Maven is this bug -
> http://jira.codehaus.org/browse/MNG-1682
> 
> Maven Anonymous: That's a weird bug why does it
> effect us?
> 
> X: Because in big multi project maven builds (like
> ApacheDS) it does
> some pretty nasty things like building your projects
> and then deploying
> the artifacts in the repository with the wrong name!
> This presents a
> problem when the multi project needs to build
> artifacts of mixed
> packagings like jar, war, and bundle.
> Some projects like apache Felix have been forced to
> use ant (gasp) to
> weave their maven subprojects together. 
> 
> Maven Anonymous: How can we help?
> 
> X: Please vote for this issue and/or strong arm the
> maven guys to fix
> it....
> 
> 
> In the mean time Ole, if you can also search for
> subprojects using
> different packaging and flag them in your report
> that would help cool
> down this problem.
> 
> I am sure Mr. X would appreciate it.
> 
> thanks
> John
> 
> 
> 
> On Fri, 2006-12-01 at 09:17 -0800, Ole Ersoy wrote:
> > Emmanuel,
> > 
> > I may have to make your wildest dream come true.
> > 
> > Initially while coding the JPackage plugin
> > I was thinking in Single POM thoughts,
> > when I realized that I have to create a
> consolidated
> > model instance using all the parent POM's as well,
> so
> > that I have a completely exhaustive picture of the
> > project's POM elements.
> > 
> > So since I have to do this, I might as well code
> it so
> > that it analyzes the pom structure, and writes a
> > report on things that it thinks could be better.
> > 
> > For instance we might have the same artifact
> > dependency in both the parent and child pom, but
> with
> > different version numbers.
> > 
> > Or we may have repeated elements, which means
> extra
> > maintenance to keep things clean.
> > 
> > OK - I'm rolling up my sleeves and jotting down
> all
> > the rules I can think of.  Then I'll implement a
> > service to the mojo that creates the "Exhaustive
> Mojo"
> > and at the same time analyzes the structure and
> writes
> > a report with restructuring recommendations.
> > 
> > So I'm taking "Wish Requests" if anyone has
> burning
> > issues, besides the ones we have already thought
> of.
> > 
> > Cheers,
> > - Ole
> > 
> > 
> > 
> > 
> >  
> >
>
____________________________________________________________________________________
> > Cheap talk?
> > Check out Yahoo! Messenger's low PC-to-Phone call
> rates.
> > http://voice.yahoo.com
> > 
> 
> 



 
____________________________________________________________________________________
Do you Yahoo!?
Everyone is raving about the all-new Yahoo! Mail beta.
http://new.mail.yahoo.com

Mime
View raw message