'Re: [JPackage-discuss] James & Apache-DS, was Tomcat Jpackage'

[prev in list] [next in list] [prev in thread] [next in thread] 

List:       jpackage-discuss
Subject:    Re: [JPackage-discuss] James & Apache-DS, was Tomcat Jpackage
From:       Deepak Bhole <dbhole () redhat ! com>
Date:       2006-10-26 17:52:12
Message-ID: 1161885132.9565.47.camel () tocatta ! toronto ! redhat ! com
[Download RAW message or body]

On Thu, 2006-10-26 at 09:45 -0700, Ole Ersoy wrote:
> Hey Deepak,
> 
> Let me make sure I understand.
> 
> When creating the RPM we specify 
> BuildRequires: blahblahpackage >= 1.7
> 
> And in Maven we specify:
> 
> <dependency>
> 		<groupId>blahblahgroupId</groupId>
> 		<artifactId>blahblahpackage</artifactId>
> 		<version>1.7</version>
> </dependency>
> 
> So with RPM, any package satisfying the >= 1.7
> constraint can be used, but with Maven 
> it better be 1.7.
> 
> So if all the dependencies are built by Maven as well,
> we just generate the corresponding RPM per their build
> processes, but if there are dependencies built using
> something other than Maven, then we would have to
> create the exact corresponding RPM?
> 

Actually, the jpp maven version is going to be a slightly modified one.
It will introduce a "mvn-jpp" command that will facilitate using system
installed jars. Since JPackage builds must be offline and reproducible
by users, they will have to stick to using whatever rpm does (i.e. 1
version per package)

> I'd have to check whether Maven supports version
> ranges...seems like a fairly simple thing to
> implement...
> 

Maven does support this, but changing all packages will be necessary in
that case. 

> Although - Package build constraints that allow
> ranges...It does provide flexibility, but is that a
> good thing?
> 
> Personally I like to know precisely what versions are
> being used.
> 
> It's a lot tighter.
> 

True. But until a resolution is reached on how to allow rpm to install
and track multiple versions of the same package, it will not be possible
for us to build against specific versions :/

> wdyt?
> 

Anyways, I don't think it will be that much of a hassle. As Ralph
pointed out, some dev effort will be needed to make this work with
jpackage, but shouldn't be too bad (atleast not this particular aspect).
I just brought up the concern because it is one of the things we need to
be aware of.

Cheers,
Deepak

> 
> 
> --- Deepak Bhole <dbhole@redhat.com> wrote:
> 
> > 
> > One concern though. How will this work with
> > different versions? maven
> > relies on having specific versions of packages.
> > JPackage rpms on the
> > other hand, installs a single version of each
> > package (in most cases)
> > and uses that. I guess it is not much of a concern
> > this early, but it
> > needs to be addressed eventually.
> > 
> > Deepak
> > 
> > On Thu, 2006-10-26 at 11:47 -0400, Fernando Nasser
> > wrote:
> > > Wow!  This is a great idea.  I can setup a CVS
> > module for that (I will 
> > > check if we have SVN already).
> > > 
> > > Deepak, Ralph, what do you think?
> > > 
> > > This is way better than having a template
> > (although it would only work 
> > > for the projects that have been mavenized).
> > > 
> > > The way maven2 and JPackage interoperate in JPP
> > 1.7 (with dbhole's new 
> > > maven2 RPM revision -- soon to be uploaded) and
> > with something like this 
> > > Java packaging would be making a huge progress. 
> > We can also have this 
> > > plugin produce Debian packages, a long dream we
> > have.
> > > 
> > > Regards to all,
> > > Fernando
> > > 
> > > Ole Ersoy wrote:
> > > > Ralph, Fernando
> > > > 
> > > > This is terrific (Directory Team - I need to
> > forward
> > > > another mail from Ralph just so you get the full
> > > > context)
> > > > 
> > > > ...- I'm sure the whole directory team would
> > love to
> > > > hear more about this effort.  I'm copying us on
> > this
> > > > reply, and feel free to copy us in for the
> > future as
> > > > well:
> > > > 
> > > > Apache Directory Developers List
> > > > <dev@directory.apache.org>,
> > > > 
> > > > Incidentally - we have this Maven plugin for
> > > > automatically generating the RPM:
> > > > 
> > > > 
> > 
> http://svn.apache.org/repos/asf/directory/trunks/daemon/plugin/src/main/java/org/apache/directory/daemon/installers/rpm/
> 
> > > > 
> > > > There's also this one:
> > > > 
> > > > 
> > http://mojo.codehaus.org/rpm-maven-plugin/pom.html
> > > > 
> > > > An idea would be to have JPackage host a maven
> > RPM
> > > > plugin.  I'm hoping this would centralize
> > development
> > > > around the plugin.
> > > > 
> > > > Once this plugin is complete, all apache builds
> > > > running maven could incorporate it and JPackage
> > would
> > > > get their packages done automagically.  
> > > > 
> > > > As the standards evolve, we just change the
> > plugin,
> > > > and voila, all packages built by Maven are up to
> > date.
> > > > 
> > > > Thoughts?
> > > > 
> > > > Cheers,
> > > > - Ole
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > --- Fernando Nasser <fnasser@redhat.com> wrote:
> > > > 
> > > > > Hi Ralph,
> > > > > 
> > > > > Ralph Apel wrote:
> > > > > (...)
> > > > > > For JPP-1.7 there is a problem though:
> > > > > > mina (and with it all the rest) rely on
> > > > > javax.net.ssl.SSLEngine,
> > > > > > which is not available in java-1.4.2.
> > > > > > 
> > > > > > I am trying to patch everything such as to
> > build a
> > > > > DS without SSL
> > > > > > support for JPP-1.7, and a full build for
> > JPP-5.0.
> > > > > > 
> > > > > > And will need a few days more, of course.
> > > > > > 
> > > > > That could be useful for the ApacheDS folks as
> > well,
> > > > > as it would allow 
> > > > > it to be built/used on Java 1.4.2.  Perhaps
> > someone
> > > > > from that community 
> > > > > already has it (unpublished)?  Or perhaps they
> > can
> > > > > do it themselves?  Or 
> > > > > help?
> > > > > 
> > > > > Cheers,
> > > > > Fernando
> > > > > 
> > > > 
> > > > 
> > > > 
> > __________________________________________________
> > > > Do You Yahoo!?
> > > > Tired of spam?  Yahoo! Mail has the best spam
> > protection around 
> > > > http://mail.yahoo.com 
> > > > 
> > 
> > 
> 
> 
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around 
> http://mail.yahoo.com 

_______________________________________________
JPackage-discuss mailing list
JPackage-discuss@zarb.org
https://www.zarb.org/mailman/listinfo/jpackage-discuss

[prev in list] [next in list] [prev in thread] [next in thread] 