headers
Martin Grotzke | 1 Dec 2006 09:46
Picon
Favicon
Gravatar

Missing Dependency: modello = 0:1.0-0.a8.2jpp is needed by package modello-maven-plugin

Dear JPackagers,

when I run a yum update I get this error message:
Missing Dependency: modello = 0:1.0-0.a8.2jpp is needed by package modello-maven-plugin

The full dependency resolution:
Resolving Dependencies
--> Populating transaction set with selected packages. Please wait.
---> Downloading header for maven2-plugin-plugin to pack into transaction set.
maven2-plugin-plugin-2.0. 100% |=========================| 3.7 kB    00:00
---> Package maven2-plugin-plugin.noarch 0:2.0.4-10jpp set to be updated
---> Downloading header for maven2-plugin-install to pack into transaction set.
maven2-plugin-install-2.0 100% |=========================| 3.7 kB    00:00
---> Package maven2-plugin-install.noarch 0:2.0.4-10jpp set to be updated
---> Downloading header for maven2-plugin-jar to pack into transaction set.
maven2-plugin-jar-2.0.4-1 100% |=========================| 3.7 kB    00:00
---> Package maven2-plugin-jar.noarch 0:2.0.4-10jpp set to be updated
---> Downloading header for maven2-plugin-eclipse to pack into transaction set.
maven2-plugin-eclipse-2.0 100% |=========================| 3.7 kB    00:00
---> Package maven2-plugin-eclipse.noarch 0:2.0.4-10jpp set to be updated
---> Downloading header for maven2-plugin-site to pack into transaction set.
maven2-plugin-site-2.0.4- 100% |=========================| 3.7 kB    00:00
---> Package maven2-plugin-site.noarch 0:2.0.4-10jpp set to be updated
---> Downloading header for maven2-plugin-resources to pack into transaction set.
maven2-plugin-resources-2 100% |=========================| 3.7 kB    00:00
---> Package maven2-plugin-resources.noarch 0:2.0.4-10jpp set to be updated
---> Downloading header for maven2 to pack into transaction set.
maven2-2.0.4-10jpp.noarch 100% |=========================|  31 kB    00:00
---> Package maven2.noarch 0:2.0.4-10jpp set to be updated
---> Package modello.noarch 0:1.0-0.a8.3jpp set to be updated
(Continue reading)

Permalink | Reply | 2 comments |
headers
Deepak Bhole | 1 Dec 2006 17:11
Picon
Favicon

Re: Missing Dependency: modello = 0:1.0-0.a8.2jpp is needed by package modello-maven-plugin

On Fri, 2006-12-01 at 09:46 +0100, Martin Grotzke wrote:
> Dear JPackagers,
> 
> when I run a yum update I get this error message:
> Missing Dependency: modello = 0:1.0-0.a8.2jpp is needed by package modello-maven-plugin
> 
> The full dependency resolution:
> Resolving Dependencies
> --> Populating transaction set with selected packages. Please wait.
> ---> Downloading header for maven2-plugin-plugin to pack into transaction set.
> maven2-plugin-plugin-2.0. 100% |=========================| 3.7 kB    00:00
> ---> Package maven2-plugin-plugin.noarch 0:2.0.4-10jpp set to be updated
> ---> Downloading header for maven2-plugin-install to pack into transaction set.
> maven2-plugin-install-2.0 100% |=========================| 3.7 kB    00:00
> ---> Package maven2-plugin-install.noarch 0:2.0.4-10jpp set to be updated
> ---> Downloading header for maven2-plugin-jar to pack into transaction set.
> maven2-plugin-jar-2.0.4-1 100% |=========================| 3.7 kB    00:00
> ---> Package maven2-plugin-jar.noarch 0:2.0.4-10jpp set to be updated
> ---> Downloading header for maven2-plugin-eclipse to pack into transaction set.
> maven2-plugin-eclipse-2.0 100% |=========================| 3.7 kB    00:00
> ---> Package maven2-plugin-eclipse.noarch 0:2.0.4-10jpp set to be updated
> ---> Downloading header for maven2-plugin-site to pack into transaction set.
> maven2-plugin-site-2.0.4- 100% |=========================| 3.7 kB    00:00
> ---> Package maven2-plugin-site.noarch 0:2.0.4-10jpp set to be updated
> ---> Downloading header for maven2-plugin-resources to pack into transaction set.
> maven2-plugin-resources-2 100% |=========================| 3.7 kB    00:00
> ---> Package maven2-plugin-resources.noarch 0:2.0.4-10jpp set to be updated
> ---> Downloading header for maven2 to pack into transaction set.
> maven2-2.0.4-10jpp.noarch 100% |=========================|  31 kB    00:00
> ---> Package maven2.noarch 0:2.0.4-10jpp set to be updated
(Continue reading)

Permalink | Reply | 1 comment |
headers
Ole Ersoy | 1 Dec 2006 18:22
Picon
Favicon

Maven POM Structuring Automation

Hi Guys,

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
projects 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.  In this case both would be
written to the spec file, unless the poms were cleaned
up.

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.  These
would have to be taken care of in order to generate a
clean spec.

So I'm going to start writing down all the rules I can
think of.  Meanwhile if anyone has any special "Wish
Request" with respect to this, feel free to send them
(Continue reading)

Permalink | Reply | 0 comments |
headers
Black Hand | 1 Dec 2006 18:58
Gravatar

Re: javamail and other glassfish proyects

On Thursday 30 November 2006 16:09, David Walluck wrote:

> Right now, their are GPL- and ASL-licensed alternatives for both
> javamail and jaf already packaged.

i know about classpathx-mail and classpathx-jaf that are GNU, i imagine that u 
mention the geronimo packages (i think that are only api packages) i dont 
test geronimo, but i test classpathx-mail with two packages and some things 
are not supported yet.

> All of glassfish is supposed to become GPL in the future, so I suspect
> that at some point we will have a complete package for this but for now
> we don't have anything.

exist any problem with the CDDL actual license in glassfish that avoid the 
works in a rpm package ?

--
Black Hand
Permalink | Reply | 2 comments |
headers
David Walluck | 1 Dec 2006 19:28
Favicon

Re: javamail and other glassfish proyects


Black Hand wrote:
> exist any problem with the CDDL actual license in glassfish that avoid the 
> works in a rpm package ?

Other than the fact that nobody seems to like the CDDL, I think that
it's just due to nobody getting around to it yet.

As far as I know, the API's should be complete (for either classpathx or
geronimo), but without a provider the API's are really only good for
building (but not running) things.

--
Sincerely,

David Walluck
<david@...>
Permalink | Reply | 1 comment |
headers
jpackage | 2 Dec 2006 00:09
Favicon

Your Bugzilla buglist needs attention.

[This e-mail has been automatically generated.]

You have one or more bugs assigned to you in the Bugzilla 
bugsystem (https://www.jpackage.org/bugzilla/) that require
attention.

All of these bugs are in the NEW or REOPENED state, and have not
been touched in 7 days or more.  You need to take a look
at them, and decide on an initial action.

Generally, this means one of three things:

(1) You decide this bug is really quick to deal with (like, it's INVALID),
    and so you get rid of it immediately.
(2) You decide the bug doesn't belong to you, and you reassign it to someone
    else.  (Hint: if you don't know who to reassign it to, make sure that
    the Component field seems reasonable, and then use the "Reassign bug to
    owner of selected component" option.)
(3) You decide the bug belongs to you, but you can't solve it this moment.
    Just use the "Accept bug" command.

To get a list of all NEW/REOPENED bugs, you can use this URL (bookmark
it if you like!):

 https://www.jpackage.org/bugzilla/buglist.cgi?bug_status=NEW&bug_status=REOPENED&assigned_to=jpackage-discuss-/hcidOUDYf1g9hUCZPvPmw <at> public.gmane.org

Or, you can use the general query page, at
https://www.jpackage.org/bugzilla/query.cgi.

Appended below are the individual URLs to get to all of your NEW bugs that
(Continue reading)

Permalink | Reply | 0 comments |
headers
Ole Ersoy | 2 Dec 2006 00:11
Picon
Favicon

Re: Version numbers on Dependencies

Hi Julius,

(JPackage team - could you please comment on this if
you think any of my rationale is kooko...Just remember
my mailbox limit is 1 Gig)

I have not investigated it personally, but 
someone from JPackage said that it does.

Yes - It does support non-versioned dependencies :-)

Which I think is the cause of a lot of 

$%# <at> $%^$# 

showing up in some of the maven support mailing lists.

Personally I'm concerned about using any dependency
other than one set by =.

One could make the assumption that someone checked all
the dependencies outside of =.  But if they missed
one, and someone uses it...

On the other hand = is the only thing used and the
application builds and runs, users can be fairly
certain that it's good to go.  They can also be
certain that the developers took care in specifying
versioned dependencies.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Ole Ersoy | 2 Dec 2006 03:24
Picon
Favicon

Re: Version numbers on Dependencies

Hey Julius,

I think the automatic upgrades should be fine (I like
them too, so they better).

Let me explore with a little example.

Suppose ApacheDS sets all it's dependencies using 

=

Then these are generated into the spec file using

=

If ApacheDS is to be installed, all the versions of
the dependencies in the repository have to be
available first, so that the Package manager can pull
them.

I believe the JPackage project is committed to doing
this.

So now ApacheDS is installed on your machine using
fixed dependencies.

Then we go ahead and upgrade one of the dependencies
and 
the ApacheDS version number correspondingly.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Julius Davies | 2 Dec 2006 16:55
Picon
Gravatar

Fwd: Version numbers on Dependencies

Thought I'd cross-post.  Hope no one minds!  I'm pretty tired so some
of my terminology is off.  For example, this was wonky:

"RPM was a tool.  So was DPKG.  But no-one expected these tools
to also try and manage all the packages."

I think what I meant to say was:

"RPM was a tool.  So was DPKG.  But no-one expected these tools to
magically create their own linux distributions."

yours,

Julius

ps.  can we stop the cross posting now and just let the discussion
diverge however it likes on the two mailing lists?

---------- Forwarded message ----------
From: Julius Davies <juliusdavies@...>
Date: Dec 2, 2006 10:36 AM
Subject: Re: Version numbers on Dependencies
To: Apache Directory Developers List <dev@...>

Hi,

First some background.

All my computers at home and my workstations at my job have been
Debian since 2002.  But the actual QA and Production servers my code
(Continue reading)

Permalink | Reply | 0 comments |
headers
jpackage | 3 Dec 2006 00:09
Favicon

Your Bugzilla buglist needs attention.

[This e-mail has been automatically generated.]

You have one or more bugs assigned to you in the Bugzilla 
bugsystem (https://www.jpackage.org/bugzilla/) that require
attention.

All of these bugs are in the NEW or REOPENED state, and have not
been touched in 7 days or more.  You need to take a look
at them, and decide on an initial action.

Generally, this means one of three things:

(1) You decide this bug is really quick to deal with (like, it's INVALID),
    and so you get rid of it immediately.
(2) You decide the bug doesn't belong to you, and you reassign it to someone
    else.  (Hint: if you don't know who to reassign it to, make sure that
    the Component field seems reasonable, and then use the "Reassign bug to
    owner of selected component" option.)
(3) You decide the bug belongs to you, but you can't solve it this moment.
    Just use the "Accept bug" command.

To get a list of all NEW/REOPENED bugs, you can use this URL (bookmark
it if you like!):

 https://www.jpackage.org/bugzilla/buglist.cgi?bug_status=NEW&bug_status=REOPENED&assigned_to=jpackage-discuss-/hcidOUDYf1g9hUCZPvPmw <at> public.gmane.org

Or, you can use the general query page, at
https://www.jpackage.org/bugzilla/query.cgi.

Appended below are the individual URLs to get to all of your NEW bugs that
(Continue reading)

Permalink | Reply | 0 comments |

Gmane