Default categories for shortcut

Hi All.

When I install my application in linux MenuGroup is created and all  
shortcut's also. But
All of them also appear under Development MenuGroup.
Quick look in .desktop file revealed Categories=Application;Development.
Why Development is in there ?

I found :
data.Categories = shortcutSpec.getAttribute(
                    SPEC_CATEGORIES, "Application;Development");
in ShortCutPanel.java:978

So default categories are Application and Development. I am just  
interested why it is so ? I think development should be taken away  
from the default value and if it is possible to configure categories  
from shortcutSpec.xml it would be nice to have it in Documentation.

-Alex

-Alex

This list is now closed, last message

Hello,

As our migration to Codehaus nears completion, I would like to inform
you that this mailing-list is no longer active.

The new mailing-lists details are now available from
http://xircles.codehaus.org/projects/izpack/lists

Cheers

Future best practices

I have written a first version that you can consult at:
http://docs.codehaus.org/display/IZPACK/Best+practices

IzPack developers can make modifications.

Cheers

Next release and migration

Hi everyone;

We are on the way to the migration to Codehaus. Here are a few news.

1. Mailing-lists migration

I can now get the list of the registered people in a convenient
manner. My plan is to make the migration next monday by AUTOMATICALLY
SUBSCRIBING YOU to the new lists.

If you don't want your address to be automatically subscribed, then
please let me know.

2. IzPack 3.11.0 and beyond

I will release it next week, at Codehaus, from the current SVN trunk
that we have at BerliOS. This will be the last 3.x release series as
I plan to upgrade to 4.x afterwards.

This is probably going to be an interim release. Starting from this
one, people will be able to report issues on our JIRA instance. The
website will stay the same for this release, but with updated
information regarding the lists and issues reporting. It will be
changed for version 4.0.0.

3. SVN migration

Once 3.11.0 has been released, I will freeze the SVN repository, then
have it migrated to Codehaus. We won't loose any single change in the
history (including the old revisions when we were using CVS!). BTW the

Planning the move to Codehaus

Hi everyone,

Here are few news regarding the (smooth) move to Codehaus.

First of all you can find the project summary at
https://xircles.codehaus.org/projects/izpack

Everything is ready there for us to jump in 

We have a JIRA issues manager at
http://jira.codehaus.org/browse/IZPACK where I have put a list of
tasks to complete the move. You are invited to have a look and
comment. I will also progressively post explanations as some of the
tasks are completed.

A few interesting tasks:
* http://jira.codehaus.org/browse/IZPACK-3 provide a streamline
izpack.org website. I have posted a few links to good-looking
candidate Wordpress templates, your point of view would be appreciated

* http://jira.codehaus.org/browse/IZPACK-9 major enhancement proposals
will be documented as IZEP (IzPack Enhancement Proposals), like many
other projects do.

I would like the current IzPack developers to help me close this one:
http://jira.codehaus.org/browse/IZPACK-6. All you need is to go to
https://xircles.codehaus.org/, create yourself an account and notify
me so that I add you to the project.

I have not yet set a date for the move to be completed, any suggestion

Italian translation does not work

Hi

I noticed that the italian translation does not work for our installer, 
all other seem to work. I get the error below. Using lates IzPack from SVN.

Thanks for any help

Regards

Sylvain

java -jar aTunes_installer.jar
net.n3.nanoxml.XMLParseException: Closing tag does not match opening 
tag: `langpack' != `str', SystemID='file:.', Line=214
        at net.n3.nanoxml.XMLUtil.errorWrongClosingTag(XMLUtil.java:468)
        at net.n3.nanoxml.StdXMLParser.processElement(StdXMLParser.java:493)
        at net.n3.nanoxml.StdXMLParser.scanSomeTag(StdXMLParser.java:261)
        at net.n3.nanoxml.StdXMLParser.processElement(StdXMLParser.java:512)
        at net.n3.nanoxml.StdXMLParser.scanSomeTag(StdXMLParser.java:261)
        at net.n3.nanoxml.StdXMLParser.scanData(StdXMLParser.java:221)
        at net.n3.nanoxml.StdXMLParser.parse(StdXMLParser.java:194)
        at com.izforge.izpack.LocaleDatabase.add(LocaleDatabase.java:72)
        at com.izforge.izpack.LocaleDatabase.<init>(LocaleDatabase.java:53)
        at 
com.izforge.izpack.installer.GUIInstaller.loadLangPack(GUIInstaller.java:278)
        at 
com.izforge.izpack.installer.GUIInstaller.access$000(GUIInstaller.java:81)
        at 
com.izforge.izpack.installer.GUIInstaller$1.run(GUIInstaller.java:131)
        at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:199)

Re: xinclude - can't use include from within userInputSpec.xml (in installation time)

This is what I was talking about yesterday.

The SystemID is being set incorrectly to "file:/tmp/izpp45530.tmp" when 
it should be set to the location of the actual include.xml file I'm not 
sure when this change occurred (but I know it used to work).

I'm a bit to busy to fix it at the moment. You might want to look at it 
(I don't think its a big fix)

Cheers

Matt

----- Original Message ----
From: Piotr Skowronek <piotr <at> skowro.net>
To: izpack-devel <at> lists.berlios.de
Sent: Tuesday, 5 February, 2008 2:17:35 PM
Subject: Re: [izpack-devel] xinclude - can't use include from within userInputSpec.xml (in
installation time)

Matthew 
Fudge 
wrote:
> 
Hi 
Piotr,
> 
> 
Try 
using 

IzPack is a CodeHaus proiect!

Hi everyone,

I'm pleased to announce that we are now a CodeHaus project!

I would like a painless and smooth transition, so we will perform a
progressive move in the next few weeks. BTW the BerliOS project will
not disappear, but will become dormant (and marked as dormant).

I will get back to the IzPack community with a transition roadmap and
detailed instructions.

Cheers

Fwd: Investigating a move of IzPack to CodeHaus

We are in 

---------- Forwarded message ----------
From: Ben Walding <bwalding@...>
Date: Feb 4, 2008 8:25 AM
Subject: Re: Investigating a move of IzPack to CodeHaus
To: Julien Ponge <julien.ponge@...>
Cc: bob@..., Guillaume Laforge <glaforge@...>

Julien,

Sounds like a good fit. Throw it into Xircles and I'll create it for you.

Cheers,

Ben

On Feb 2, 2008 11:21 PM, Julien Ponge <julien.ponge@...> wrote:

> Hello Ben, Bob,
>
> I am the original creator and project leader of the IzPack project
> (http://izpack.org/), a cross-platform Java installer released under
> the Apache License 2.0.
>
> The project is quite mature and was started in 2001. It is still
> growing with an active community. The tool is used by a good number
> of companies around the world. "Famous" examples of IzPack-based
> installers include the ones of JBoss (they use a custom version but
> send patches upstream). There is also some interest in the GlassFish

VariableSubstitutor - parameters should be able to support a dash (-)

Hi All,

Recently I have added additional parameter for VariableSubstitutor,
that allows ANT-like (@param@) parameters parsing.

Currently, variable names can contain following characters (if
not using braces): letters, digits, underscore (_), dot.
I would like to add a dash to the list of allowed parameters,
as people seem to like use dashes especially in ANT scripts.
Example: @my-parameter-to-be-substituted@.

Do you have any objections?
Patch in the attachment.

Regards,
Piotr

Index: src/lib/com/izforge/izpack/util/VariableSubstitutor.java
===================================================================
--- src/lib/com/izforge/izpack/util/VariableSubstitutor.java	(revision 2031)
+++ src/lib/com/izforge/izpack/util/VariableSubstitutor.java	(working copy)
@@ -341,7 +341,7 @@
             StringBuffer nameBuffer = new StringBuffer();
             while (c != -1 && (braces && c != '}') || (c >= 'a' && c <= 'z')
                     || (c >= 'A' && c <= 'Z') || (braces && (c == '[') || (c == ']'))
-                    || (((c >= '0' && c <= '9') || c == '_' || c == '.') && nameBuffer.length() > 0))
+                    || (((c >= '0' && c <= '9') || c == '_' || c == '.' || c == "-") && nameBuffer.length() > 0))
             {
                 nameBuffer.append((char) c);

xinclude - can't use include from within userInputSpec.xml (in installation time)

Hi All,

There is a problem with using xinclude feature when used
in userInputSpec.xml. The problem appears in installation-time,
when XIncludeXMLBuilder is unable to find fragments. They would
have to be placed outside of install.jar, to be accessible
in installation-time.

However, xinclude feature works fine for install.xml as fragments
are included/resolved during compilation time. UserInputSpec.xml
is not parsed in compile-time, but simply embedded into resources.

I have worked out a quick solution for it. It can be found
in the attachment. Tell me what do you think about it.
The solution is to modify XIncludeXMLBuilder, to be able
to check resources whether they contain referenced fragment.
Fragments have to be put in resources, and referenced using
/res/ prefix, as I didn't want to hard code this prefix into
XIncludeXMLBuilder.

One more time, tell me what do you think about this patch.

Regards,
Piotr Skowronek

Index: src/lib/net/n3/nanoxml/XIncludeXMLBuilder.java
===================================================================
--- src/lib/net/n3/nanoxml/XIncludeXMLBuilder.java	(revision 2031)
+++ src/lib/net/n3/nanoxml/XIncludeXMLBuilder.java	(working copy)