Your Bugzilla bug list needs attention.

[This e-mail has been automatically generated.]

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

All of these bugs are in the NEW orREOPENED 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 default assignee 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 haven't been touched for 7 days or more.

Your Bugzilla bug list needs attention.

[This e-mail has been automatically generated.]

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

All of these bugs are in the NEW orREOPENED 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 default assignee 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 haven't been touched for 7 days or more.

Re: [JPackage-announce] [RPM (6.0)] [DIST generic] bcel-5.1-17.jpp6

What are we keeping 5.1 for (in 6.0!) ?
Will we need to create bcel52 and bcel53 and bcel54.....?

On Mon, 2009-11-02 at 20:44 +0100, David Walluck wrote:
> Name        : bcel                         Relocations: (not relocatable)
> Version     : 5.1                               Vendor: JPackage Project
> Release     : 17.jpp6                       Build Date: Mon 02 Nov 2009 08:38:16 PM CET
> Install Date: (not installed)               Build Host: flat
> Group       : Development/Libraries/Java    Source RPM: (none)
> Size        : 3524371                          License: ASL 2.0
> Signature   : (none)
> Packager    : David Walluck <david@...>
> URL         : http://jakarta.apache.org/bcel/
> Summary     : Byte Code Engineering Library
> Description :
> The Byte Code Engineering Library (formerly known as JavaClass) is

Mavenizing the installation layout for JPP6

Hi all,

With JPP 5.0 finaly released, and work on JPP 6 goinng full speed, it is 
time to define the new layout we've talked about monnths ago, as well as 
some script inprovements for jpackage-utils 6.0.

Ralph Apel has created a scheme that is backwards compatible, which 
facilitates migration, requires less modifications to maven, and he did 
a proof-of-concept application of it in a package (which worked fine).  
We just need to polish it to make it easier to use, perhaps with the 
addition of some macros and/or scripts to jpackage-utils.

I have attached Ralph's original e-mail, so we all have a starting point 
for discussions.

Regards to all,
Fernando

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

Some questions about the maven setup in JPP 6

Hi Ralph,

I have a few questions/suggestions that I would like to run through you 
(and everyone else).

1) The location of the versioned and unversioned repos

Background: there is a versioned repository which is thhe current maven2 
layout.  If the exact version is found there, maven will take it, 
otherwise it falls back to a symlink-based unversioned repository and 
takes whatever was installed there.  All packages will install the 
versioned repo, only the main packages, the ones without a version in 
their names, install the unversioned symlinks.  This allows one to have 
a xxx, xxx2 (legacy) and xxx4 (progressive) packages installed, request 
the specific one or just take the default.  NOTE: It will still fall 
back even further to the pre-mavenization layout installation, and in 
that case depmaps and depmap fragments are still used.  That will vanish 
as the conversion is done.

Location of the versioned repo:

%{javadir}/repo/maven2

Location of the unversioned repo:

%{javadir}/repo/unver2

QUESTION:  Ralph, I'd like to change this to just %{javadir}.  The 
contents will be a bit messy while the conversion is done but will clear 
up as the old layout goes away.  Is there any reason we cannot do that?

Re: Some questions about the maven setup in JPP 6

Le Mar 3 novembre 2009 17:10, Fernando Nasser a écrit :

> Here is the possible contents of such script based on your prototype:

Wouldn't it be cleaner and more extensible to process this xml via with an
xslt filter using xsltproc (in a single pass) ? sed was not really designed to
frob xml files, as soon as you'll stop doing very basic changes sed will limit
you.

xsltproc is not a huge dep and will be installed for other reasons on most
systems.

--

-- 
Nicolas Mailhot

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

Re: Some questions about the maven setup in JPP 6

Nicolas Mailhot wrote:
> Le Mar 3 novembre 2009 17:10, Fernando Nasser a écrit :
>
>   
>> Here is the possible contents of such script based on your prototype:
>>     
>
> Wouldn't it be cleaner and more extensible to process this xml via with an
> xslt filter using xsltproc (in a single pass) ? sed was not really designed to
> frob xml files, as soon as you'll stop doing very basic changes sed will limit
> you.
>
>   
I don't think we may even need sed at all.  This settings.xml file 
should not become larger, but smaller.  And if we make this a script, or 
macro, we may be able to just replace that token with an (optional) 
argument (which defaults to %{name}.

This said, I have no preference in case we need to make more evolved 
modifications.  Ralph used sed because it was just a quick prototype 
created as a proof-of-concept.

> xsltproc is not a huge dep and will be installed for other reasons on most
> systems.
>
>   
Got it.  We can use it instead of sed if we have to do a more complex 
replacement.  maven already BuildRequires lots of things, so adding 
xsltproc and dependencies to the list will not make it much worse.

Your Bugzilla bug list needs attention.

[This e-mail has been automatically generated.]

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

All of these bugs are in the NEW orREOPENED 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 default assignee 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 haven't been touched for 7 days or more.

Your Bugzilla bug list needs attention.

[This e-mail has been automatically generated.]

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

All of these bugs are in the NEW orREOPENED 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 default assignee 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 haven't been touched for 7 days or more.

Your Bugzilla bug list needs attention.

[This e-mail has been automatically generated.]

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

All of these bugs are in the NEW orREOPENED 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 default assignee 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 haven't been touched for 7 days or more.