[jira] Created: (MPNSIS-6) Add ${pom.url} to constants in project.jelly
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPNSIS-6
Here is an overview of the issue:
-
Key: MPNSIS-6
Summary: Add ${pom.url} to constants in project.jelly
Type: Task
Status: Open
Priority: Trivial
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-nsis-plugin
Assignee: dion gillard
Reporter: Geoffrey
Created: Mon, 5 Jul 2004 2:57 AM
Updated: Mon, 5 Jul 2004 2:57 AM
Description:
With ${pom.url} the homepage shortcut can be dynamicaly set.
In time it would be nice to be able to get any pom variable in the custom scripts,
although this might not be possible because of the nature of NSIS scripts.
It is arguable that since the docs are by default included in the binary distribution,
this might not be that necessary.
-
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/nsis/xdocs index.xml
dion2004/07/04 22:40:00 Modified:nsis/xdocs index.xml Log: Add other docs to index Revision ChangesPath 1.4 +16 -1 maven-plugins/nsis/xdocs/index.xml Index: index.xml === RCS file: /home/cvs/maven-plugins/nsis/xdocs/index.xml,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- index.xml 2 Jul 2004 08:13:07 - 1.3 +++ index.xml 5 Jul 2004 05:39:59 - 1.4 @@ -27,9 +27,18 @@ - This plugin is used to generate Win32 installer programs using NSIS + +This plugin is used to generate Win32 installer programs using +http://nsis.sourceforge.net";>NSIS. + DocumentDescription + How it works + + This describes the process of using this plugin to create an + installation program. + + Properties The behavior of this plugin can be altered via @@ -41,6 +50,12 @@ This plugin provides goals to help in building the installer. This document describes each goal available. + + + Customizing the installer + + This describes the ways you can customize the generated installer, + e.g. creating shortcuts, add environment variables etc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/nsis/xdocs customizing.xml
dion2004/07/04 22:33:15 Modified:nsis/xdocs customizing.xml Log: Section on custom templates Revision ChangesPath 1.5 +19 -0 maven-plugins/nsis/xdocs/customizing.xml Index: customizing.xml === RCS file: /home/cvs/maven-plugins/nsis/xdocs/customizing.xml,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- customizing.xml 5 Jul 2004 05:29:02 - 1.4 +++ customizing.xml 5 Jul 2004 05:33:15 - 1.5 @@ -255,6 +255,25 @@ + +You can of course provide your own versions of the project.jelly +and setup.jelly templates. This requires you to understand NSIS +and a little bit of http://jakarta.apache.org/commons/jelly/";>jelly +as well. + + +To use your own templates, override the maven.nsis.project.template +and maven.nsis.setup.template variables. + + +The templates are expected to be well formed Jelly scripts, i.e. valid +XML documents. + + +If you do provide your own templates, you have complete control over +the way the installation process will work. You will also be able to +completely ruin it as well :-). + - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/nsis/xdocs customizing.xml
dion2004/07/04 22:29:02
Modified:nsis/xdocs customizing.xml
Log:
Details on the scripts available for customising the default templates
Revision ChangesPath
1.4 +81 -0 maven-plugins/nsis/xdocs/customizing.xml
Index: customizing.xml
===
RCS file: /home/cvs/maven-plugins/nsis/xdocs/customizing.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- customizing.xml 5 Jul 2004 04:45:42 - 1.3
+++ customizing.xml 5 Jul 2004 05:29:02 - 1.4
@@ -171,6 +171,87 @@
+
+There are several .nsh files that you can place in
${maven.nsis.src}
+directory to add functionality to the installer. In this section, we'll
look
+at an example for each of the scripts included by the default template that
+will be overridden.
+
+
+
+
+ This file is used to do any pre-installation checks. It can hold any
+ http://nsis.sourceforge.net/Docs/";>valid NSIS code.
+
+
+ One example is to check the environment has been correctly set up, e.g.
+
+Call AssertJavaHome
+
+ This will check, using the function provided in JDK.nsh,
+ that an environment variable for JAVA_HOME is available,
+ and abort the installation if it's not.
+
+
+
+
+
+ If you provide this file, the installer will allow the user to choose
+ whether or not to create shortcuts on the desktop. The shortcuts specified
+ in this file will be created.
+
+
+ As always, see the http://nsis.sourceforge.net/Docs/";>NSIS
docs
+ for details on the code to use. The example below creates a shortcut
+ on the desktop to maven.bat from the installation directory
+ the user has chosen.
+
+CreateShortCut "$DESKTOP\Maven.lnk" "$INSTDIR\bin\maven.bat" ""
"$INSTDIR\bin\maven.bat" 0
+
+
+
+
+ During installation, you may want to add entries to the user's registry
+ or environment for use either in your application, the installation
process, or uninstall.
+ Here's a small example that adds an environment variable called
MYAPP_HOME
+ with the value of the installation directory.
+
+
+Push "MYAPP_HOME"
+Push "$INSTDIR"
+Call WriteEnvStr
+
+
+ Note: this relies on the included functions from
Environment.nsh.
+
+
+
+
+
+ During uninstallation, you must remove any entries to the user's registry
+ or environment. Here's a small example that removes an environment
variable
+ called MYAPP_HOME.
+
+
+Push "MYAPP_HOME"
+Call un.DeleteEnvStr
+
+
+
+
+
+ If you provide this file, the installer will allow the user to choose
+ whether or not to create shortcuts in the Start Menu.
+ The shortcuts specified in this file will be created.
+
+
+CreateShortCut "${PROJECT_STARTMENU_FOLDER}\Myapp.lnk" "$INSTDIR\bin\myapp.bat" ""
"$INSTDIR\bin\myapp.bat" 0
+CreateShortCut "${PROJECT_STARTMENU_FOLDER}\Uninstall.lnk" "$INSTDIR\Uninst.exe" ""
"$INSTDIR\Uninst.exe" 0
+CreateShortCut "${PROJECT_STARTMENU_FOLDER}\Homepage.lnk" "http://www.myapp.nfi/";
+CreateShortCut "${PROJECT_STARTMENU_FOLDER}\User Guide.lnk"
"http://www.myapp.nfi/user-guide.html";
+
+
+
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: 1.0 branch and dist plugin
Bizarre... I'll take a look tonight. Quoting Dion Gillard <[EMAIL PROTECTED]>: > On Mon, 5 Jul 2004 14:54:38 +1000, Dion Gillard <[EMAIL PROTECTED]> > wrote: > > I'll try adding a prereq of dist:build-setup > > Same sort of failure: > > Tag library requested that is not present: 'dist' in plugin: > 'maven-nsis-plugin-1.1-SNAPSHOT' > INTERNAL ERROR > Reference made to goal 'dist:build-setup' which has no definition. > -- > http://www.multitask.com.au/people/dion/ > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: 1.0 branch and dist plugin
On Mon, 5 Jul 2004 14:54:38 +1000, Dion Gillard <[EMAIL PROTECTED]> wrote: > I'll try adding a prereq of dist:build-setup Same sort of failure: Tag library requested that is not present: 'dist' in plugin: 'maven-nsis-plugin-1.1-SNAPSHOT' INTERNAL ERROR Reference made to goal 'dist:build-setup' which has no definition. -- http://www.multitask.com.au/people/dion/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: 1.0 branch and dist plugin
On Mon, 5 Jul 2004 11:18:26 +1000, Brett Porter <[EMAIL PROTECTED]> wrote: > Quoting Dion Gillard <[EMAIL PROTECTED]>: > > > I'm having problems with maven:get in the latest builds of the 1.0 branch. > > > > In the NSIS plugin I have this: > > > > > plugin="maven-dist-plugin" property="maven.dist.bin.assembly.dir"/> > > > > And it comes back blank. > > This stuff has always been flaky. It depends on the plugin already being loaded. > The "documented" fashion of doing so is a taglib dependency handle (see > eclipse's use of test/cactus). Using a pregoal will also work. As far as I can tell from maven -X, using xmlns:dist="dist" doesn't load the dist plugin. > Clear your plugin cache and try again... try depending on dist:dist... that's > all I can think of off the top of my head. I cleared the cache (~/.maven/plugins and ~/.maven/cache) and it's still blank. Can you try this on your installation? Just checkout and install the latest nsis plugin, and then do 'maven nsis' from the maven source directory. On my machine it barfs because maven:get returns a blank value, with: 'maven.dist.bin.assembly.dir' must be specified. It is the directory containing files to be placed in the installer I'll try adding a prereq of dist:build-setup -- http://www.multitask.com.au/people/dion/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/nsis/xdocs customizing.xml
dion2004/07/04 21:45:42
Modified:nsis/xdocs customizing.xml
Log:
Add section on the provided templates and customization points
Revision ChangesPath
1.3 +70 -1 maven-plugins/nsis/xdocs/customizing.xml
Index: customizing.xml
===
RCS file: /home/cvs/maven-plugins/nsis/xdocs/customizing.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- customizing.xml 5 Jul 2004 03:41:35 - 1.2
+++ customizing.xml 5 Jul 2004 04:45:42 - 1.3
@@ -35,7 +35,7 @@
- You can customize the resultant executable installer either
+ You can customize the installer either
by providing your own scripts that the existing templates
includes, or you can provide your own templates.
@@ -98,6 +98,75 @@
+
+ This template produces a file (${maven.build.dir}/setup.nsi)
+ which is used by the NSIS 'compiler', makensis.exe to
+ produce the installer.
+
+
+ The file, when processed, includes other files which you can optionally
+ provide, to add functionality to the installer. The property,
+ ${maven.nsis.src}, which
defaults to
+ ${basedir}/src/nsis, is where you can place any NSIS source
+ files which you want included.
+
+
+ The setup.nsh file that is generated uses following list
+ of directories to search for files to include:
+
+${maven.nsis.src} if it exists,
+${maven.build.dir}
+${plugin.resources}
+
+ So anything in your NSIS source will override the defaults.
+
+
+ The generated setup.nsh file includes the following files:
+
+
+ FilePurpose
+
+before-install.nsh
+Allow customization of code to be run before the install, e.g.
check JAVA_HOME etc
+
+
+BrandingImage.nsh
+Adds a macro to display the project logo on the installer
+
+
+desktop-shortcuts.nsh
+Allow customization of desktop shortcuts to be added
+
+
+Environment.nsh
+Adds functionality to set environment variables
+
+
+JDK.nsh
+Adds a function to check for JAVA_HOME being set
+
+
+project.nsh
+The generated file with project details as constants
+
+
+registry.nsh
+Allow customization of environment variables and registry entries
to be written
+
+
+registry-uninstall.nsh
+Allow customization of environment variables and registry entries
to be removed on uninstall
+
+
+startmenu-shortcuts.nsh
+Allow start menu shortcuts to be added
+
+
+
+ Typically you wont provide overrides for BrandingImage.nsh,
+ Environment.nsh and JDK.nsh, as these are utilities used in the setup.nsh
+ script.
+
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/nsis/xdocs properties.xml
dion2004/07/04 21:45:19 Modified:nsis/xdocs properties.xml Log: Make blank default easier Revision ChangesPath 1.3 +1 -3 maven-plugins/nsis/xdocs/properties.xml Index: properties.xml === RCS file: /home/cvs/maven-plugins/nsis/xdocs/properties.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- properties.xml4 Mar 2004 18:37:54 - 1.2 +++ properties.xml5 Jul 2004 04:45:19 - 1.3 @@ -75,9 +75,7 @@ maven.nsis.logo.widthHeight Yes -Default value is - - . +Default value is blank - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/nsis/src/plugin-resources/templates setup.jelly
dion2004/07/04 21:31:53
Modified:nsis/src/plugin-resources/templates setup.jelly
Log:
Remove old FIXME
Revision ChangesPath
1.13 +0 -1 maven-plugins/nsis/src/plugin-resources/templates/setup.jelly
Index: setup.jelly
===
RCS file: /home/cvs/maven-plugins/nsis/src/plugin-resources/templates/setup.jelly,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- setup.jelly 4 Jul 2004 14:27:30 - 1.12
+++ setup.jelly 5 Jul 2004 04:31:53 - 1.13
@@ -60,7 +60,6 @@
XPStyle on
; branding with logo
-; FIXME: position and size need to be properties
!ifdef PROJECT_LOGO
AddBrandingImage ${maven.nsis.logo.position} ${maven.nsis.logo.widthHeight}
!endif
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/nsis/xdocs customizing.xml
dion2004/07/04 20:41:35
Modified:nsis/xdocs customizing.xml
Log:
More detail on the project.jelly template
Revision ChangesPath
1.2 +25 -0 maven-plugins/nsis/xdocs/customizing.xml
Index: customizing.xml
===
RCS file: /home/cvs/maven-plugins/nsis/xdocs/customizing.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- customizing.xml 4 Jul 2004 14:47:25 - 1.1
+++ customizing.xml 5 Jul 2004 03:41:35 - 1.2
@@ -71,6 +71,31 @@
+
+ This template produces a file
(${maven.build.dir}/project.nsi)
+ which is included in the generated setup file.
+
+
+ The template makes available select values from the
project.xml
+ for use in the installation process as constants, i.e. using the NSIS
+ !define statement.
+
+
+ Constant Value
+ ORGANIZATION ${pom.organization}
+ PROJECT_BUILD_DIR ${maven.build.dir}
+ PROJECT_FINAL_NAME${maven.final.name}
+ PROJECT_LICENSE_FILE
${maven.license.licenseFile}
+ PROJECT_LICENSE_TEXT
${maven.nsis.license.text}
+ PROJECT_NAME ${pom.name}
+ PROJECT_REG_KEY
SOFTWARE\${pom.organization}\${pom.name}\${pom.currentVersion}
+ PROJECT_REG_UNINSTALL_KEY
Software\Microsoft\Windows\CurrentVersion\Uninstall\${pom.name}
${pom.currentVersion}
+ PROJECT_STARTMENU_FOLDER
$$SMPROGRAMS\${pom.organization}\${pom.name} ${pom.currentVersion}
+ PROJECT_VERSION ${pom.currentVersion}
+ PROJECT_DIST_BIN_DIR
${maven.dist.bin.assembly.dir}
+ PROJECT_DIST_DIR ${maven.dist.dir}
+ PROJECT_LOGO ${maven.nsis.logo}
+
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/nsis/xdocs changes.xml
dion2004/07/04 20:38:33 Modified:nsis/xdocs changes.xml Log: Fix typo in registry uninstall key Revision ChangesPath 1.5 +1 -0 maven-plugins/nsis/xdocs/changes.xml Index: changes.xml === RCS file: /home/cvs/maven-plugins/nsis/xdocs/changes.xml,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- changes.xml 4 Jul 2004 14:29:20 - 1.4 +++ changes.xml 5 Jul 2004 03:38:33 - 1.5 @@ -25,6 +25,7 @@ + Fix typo in registry uninstall key. Generate exe in distributions directory. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/nsis/src/plugin-resources/templates project.jelly
dion2004/07/04 20:38:10
Modified:nsis/src/plugin-resources/templates project.jelly
Log:
Fix typo in registry uninstall key
Revision ChangesPath
1.7 +1 -1 maven-plugins/nsis/src/plugin-resources/templates/project.jelly
Index: project.jelly
===
RCS file: /home/cvs/maven-plugins/nsis/src/plugin-resources/templates/project.jelly,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- project.jelly 4 Jul 2004 12:25:15 - 1.6
+++ project.jelly 5 Jul 2004 03:38:10 - 1.7
@@ -40,7 +40,7 @@
!define PROJECT_NAME "${pom.name}"
!define PROJECT_REG_KEY
"SOFTWARE\${pom.organization}\${pom.name}\${pom.currentVersion}"
-!define PROJECT_REG_UNINSTALL_KEY
"Software\Microsoft\Windows\CurrentVersion\Uninstall\${pom.name} ${pom.version}"
+!define PROJECT_REG_UNINSTALL_KEY
"Software\Microsoft\Windows\CurrentVersion\Uninstall\${pom.name} ${pom.currentVersion}"
!define PROJECT_STARTMENU_FOLDER "$$SMPROGRAMS\${pom.organization}\${pom.name}
${pom.currentVersion}"
!define PROJECT_VERSION "${pom.currentVersion}"
!define PROJECT_DIST_BIN_DIR "${maven.dist.bin.assembly.dir}"
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: 1.0 branch and dist plugin
Quoting Dion Gillard <[EMAIL PROTECTED]>: > Given Jason's comments last week, I'm trying not to put preGoals in plugins. Yep, that's a good thing. I probably meant prereq though - if there is a goal (like the :init stuff) you can prereq on that'll work (eg war:load was used for this), but the taglib stuff is definitely preferable as it is slightly less gross. > > Incidentially, I saw the bug you filed against dist + touchstone. Maven > doesn't > > use dist to build releases at the moment, so I'm not sure fix for 1.0 is > > appropriate. > > I'm more worried that dist is exposing an issue in Maven. Touchstone is fairly sensitive to the context it is run from, so it may break run under certain circumstances. Hooking it onto test:test wasn't a great idea but at least it gets run :) Given that we haven't had any other reports of that type of issue recently, I'm not particularly worried about it being a big problem, so can be pushed behind 1.0 IMO. Cheers, Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: cvs commit: maven maven.xml
On Mon, 5 Jul 2004 12:16:58 +1000, Dion Gillard <[EMAIL PROTECTED]> wrote: > Sorry, I meant the test plugin Which, duh, is called by site -- http://www.multitask.com.au/people/dion/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: cvs commit: maven maven.xml
Sorry, I meant the test plugin
On Mon, 5 Jul 2004 11:10:52 +1000, Brett Porter <[EMAIL PROTECTED]> wrote:
> How do you propose to test this?
>
> - Brett
>
>
>
> Quoting Dion Gillard <[EMAIL PROTECTED]>:
>
> > How about including test as well?
> >
> > On 3 Jul 2004 01:50:37 -, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > > brett 2004/07/02 18:50:37
> > >
> > > Modified:.Tag: MAVEN-1_0-BRANCH maven.xml
> > > Log:
> > > generate a seed repo. just encompasses site (and default reports),
> > java:compile
> > >
> > > Revision ChangesPath
> > > No revision
> > > No revision
> > > 1.97.2.29 +22 -0 maven/maven.xml
> > >
> > > Index: maven.xml
> > > ===
> > > RCS file: /home/cvs/maven/maven.xml,v
> > > retrieving revision 1.97.2.28
> > > retrieving revision 1.97.2.29
> > > diff -u -r1.97.2.28 -r1.97.2.29
> > > --- maven.xml 12 Jun 2004 04:38:50 - 1.97.2.28
> > > +++ maven.xml 3 Jul 2004 01:50:37 - 1.97.2.29
> > > @@ -379,5 +379,27 @@
> > >
> > >
> > >
> > > +
> > > +
> > > +
> > > +
> > > +
> > > + > />
> > > +
> > > + > descriptor="src/test/touchstone-build/src/reactor-build/default/project.xml"
> > goals="java:compile,site" />
> > > +
> > > + > compression="gzip" longfile="gnu">
> > > +
> > > +
> > > +
> > > +
> > > + > name="${dep.groupId}/jars/${dep.artifactId}-${dep.version}.jar" />
> > > + > name="${dep.groupId}/jars/${dep.artifactId}-${dep.version}.jar.md5" />
> > > +
> > > +
> > > +
> > > +
> > > +
> > > +
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
--
http://www.multitask.com.au/people/dion/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: 1.0 branch and dist plugin
On Mon, 5 Jul 2004 11:18:26 +1000, Brett Porter <[EMAIL PROTECTED]> wrote: > Quoting Dion Gillard <[EMAIL PROTECTED]>: > > This stuff has always been flaky. It depends on the plugin already being loaded. > The "documented" fashion of doing so is a taglib dependency handle (see > eclipse's use of test/cactus). Using a pregoal will also work. Given Jason's comments last week, I'm trying not to put preGoals in plugins. > > Also, running maven dist by itself works ok, but putting it as a > > pre-req for a plugin goal fails miserably with > > > > INTERNAL ERROR > > Reference made to goal 'dist' which has no definition. > > Clear your plugin cache and try again... try depending on dist:dist... that's > all I can think of off the top of my head. Will do. > Incidentially, I saw the bug you filed against dist + touchstone. Maven doesn't > use dist to build releases at the moment, so I'm not sure fix for 1.0 is > appropriate. I'm more worried that dist is exposing an issue in Maven. -- http://www.multitask.com.au/people/dion/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: 1.0 branch and dist plugin
Quoting Dion Gillard <[EMAIL PROTECTED]>: > I'm having problems with maven:get in the latest builds of the 1.0 branch. > > In the NSIS plugin I have this: > > plugin="maven-dist-plugin" property="maven.dist.bin.assembly.dir"/> > > And it comes back blank. This stuff has always been flaky. It depends on the plugin already being loaded. The "documented" fashion of doing so is a taglib dependency handle (see eclipse's use of test/cactus). Using a pregoal will also work. > Also, running maven dist by itself works ok, but putting it as a > pre-req for a plugin goal fails miserably with > > INTERNAL ERROR > Reference made to goal 'dist' which has no definition. Clear your plugin cache and try again... try depending on dist:dist... that's all I can think of off the top of my head. Incidentially, I saw the bug you filed against dist + touchstone. Maven doesn't use dist to build releases at the moment, so I'm not sure fix for 1.0 is appropriate. - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: cvs commit: maven maven.xml
How do you propose to test this?
- Brett
Quoting Dion Gillard <[EMAIL PROTECTED]>:
> How about including test as well?
>
> On 3 Jul 2004 01:50:37 -, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > brett 2004/07/02 18:50:37
> >
> > Modified:.Tag: MAVEN-1_0-BRANCH maven.xml
> > Log:
> > generate a seed repo. just encompasses site (and default reports),
> java:compile
> >
> > Revision ChangesPath
> > No revision
> > No revision
> > 1.97.2.29 +22 -0 maven/maven.xml
> >
> > Index: maven.xml
> > ===
> > RCS file: /home/cvs/maven/maven.xml,v
> > retrieving revision 1.97.2.28
> > retrieving revision 1.97.2.29
> > diff -u -r1.97.2.28 -r1.97.2.29
> > --- maven.xml 12 Jun 2004 04:38:50 - 1.97.2.28
> > +++ maven.xml 3 Jul 2004 01:50:37 - 1.97.2.29
> > @@ -379,5 +379,27 @@
> >
> >
> >
> > +
> > +
> > +
> > +
> > +
> > + />
> > +
> > + descriptor="src/test/touchstone-build/src/reactor-build/default/project.xml"
> goals="java:compile,site" />
> > +
> > + compression="gzip" longfile="gnu">
> > +
> > +
> > +
> > +
> > + name="${dep.groupId}/jars/${dep.artifactId}-${dep.version}.jar" />
> > + name="${dep.groupId}/jars/${dep.artifactId}-${dep.version}.jar.md5" />
> > +
> > +
> > +
> > +
> > +
> > +
> >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVENUPLOAD-157) add commons-convert-0.1-bundle.jar to ibiblio
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MAVENUPLOAD-157 Here is an overview of the issue: - Key: MAVENUPLOAD-157 Summary: add commons-convert-0.1-bundle.jar to ibiblio Type: Task Status: Open Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-upload-requests Assignee: Jason van Zyl Reporter: Mark Proctor Created: Sun, 4 Jul 2004 4:48 PM Updated: Sun, 4 Jul 2004 4:48 PM Description: http://www.markproctor.com/commons-convert-0.1-bundle.jar Needed for simple-jndi - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVENUPLOAD-156) add simple-jndi-0.9 to ibiblio
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MAVENUPLOAD-156 Here is an overview of the issue: - Key: MAVENUPLOAD-156 Summary: add simple-jndi-0.9 to ibiblio Type: Task Status: Open Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-upload-requests Assignee: Jason van Zyl Reporter: Mark Proctor Created: Sun, 4 Jul 2004 4:46 PM Updated: Sun, 4 Jul 2004 4:46 PM Description: simple-jndi-0.9 - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPANNOUNCEMENT-4) Cannot use plugin in project.xml's report element.
The following comment has been added to this issue:
Author: Gary Gregory
Created: Sun, 4 Jul 2004 4:31 PM
Body:
Sure, as long as I can still do:
maven.announcement.file=${maven.build.dir}/RELEASE-NOTES.txt
-
View this comment:
http://jira.codehaus.org/browse/MPANNOUNCEMENT-4?page=comments#action_21365
-
View the issue:
http://jira.codehaus.org/browse/MPANNOUNCEMENT-4
Here is an overview of the issue:
-
Key: MPANNOUNCEMENT-4
Summary: Cannot use plugin in project.xml's report element.
Type: New Feature
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-announcement-plugin
Versions:
1.1
Assignee:
Reporter: Gary Gregory
Created: Tue, 22 Jun 2004 5:44 PM
Updated: Sun, 4 Jul 2004 4:31 PM
Environment: >maven -i
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0-rc3
# BEGIN: Which report
Which.version=Which.java:($Revision: 1.2 $) WhichJar.java:($Revision: 1.2 $)
java.version=1.4.2_04
file.encoding=Cp1252
java.ext.dirs=C:\java\sun\1.4.2_04\jre\lib\ext
java.class.path=C:\Program Files\Apache Software Foundation\Maven
1.0-rc3\lib\forehead-1.0-beta-5.jar
os.name=Windows XP
java.vendor=Sun Microsystems Inc.
sun.boot.class.path=C:\Program Files\Apache Software Foundation\Maven
1.0-rc3\lib\endorsed\xerces-2.4.0.jar;C:\Program Files\Apache Software
Foundation\Maven 1.
0-rc3\lib\endorsed\xml-apis-1.0.b2.jar;C:\java\sun\1.4.2_04\jre\lib\rt.jar;C:\java\sun\1.4.2_04\jre\lib\i18n.jar;C:\java\sun\1.4.2_04\jre\lib\sunrsasign.jar;C:\
java\sun\1.4.2_04\jre\lib\jsse.jar;C:\java\sun\1.4.2_04\jre\lib\jce.jar;C:\java\sun\1.4.2_04\jre\lib\charsets.jar;C:\java\sun\1.4.2_04\jre\classes
java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition
# END: Which report
Installed plugins:
maven-castor-plugin-1.2
maven-site-plugin-1.5
maven-multiproject-plugin-1.3
maven-jdepend-plugin-1.5
maven-clover-plugin-1.5
maven-genapp-plugin-2.2
maven-jbuilder-plugin-1.5
maven-jboss-plugin-1.5
maven-dashboard-plugin-1.3
maven-artifact-plugin-1.2
maven-developer-activity-plugin-1.5
maven-war-plugin-1.6
maven-native-plugin-1.1
maven-cruisecontrol-plugin-1.2
maven-webserver-plugin-2.0
maven-docbook-plugin-1.2
maven-deploy-plugin-1.3
maven-ear-plugin-1.5
maven-repository-plugin-1.2
maven-j2ee-plugin-1.5
maven-jnlp-plugin-1.3
maven-linkcheck-plugin-1.2
maven-javadoc-plugin-1.5
maven-vdoclet-plugin-1.2
maven-hibernate-plugin-1.1
maven-appserver-plugin-2.0
maven-antlr-plugin-1.2
maven-jira-plugin-1.1
maven-ant-plugin-1.7
maven-gump-plugin-1.3
maven-tasklist-plugin-2.3
maven-xdoc-plugin-1.7.1
maven-ashkelon-plugin-1.2
maven-tjdo-plugin-1.0.0
maven-html2xdoc-plugin-1.3
maven-announcement-plugin-1.1
maven-pmd-plugin-1.4
maven-jxr-plugin-1.4
maven-struts-plugin-1.3
maven-latka-plugin-1.4
maven-junit-doclet-plugin-1.2
maven-pom-plugin-1.4
maven-changelog-plugin-1.5
maven-clean-plugin-1.2
maven-license-plugin-1.2
maven-jetty-plugin-1.1
maven-jdee-plugin-1.1
maven-file-activity-plugin-1.5
maven-jcoverage-plugin-1.0.4
maven-jdiff-plugin-1.4
maven-jar-plugin-1.5
maven-scm-plugin-1.3
maven-aspectwerkz-plugin-1.2
maven-faq-plugin-1.3
maven-plugin-plugin-1.3
maven-dist-plugin-1.5
maven-jellydoc-plugin-1.3
maven-javacc-plugin-1.1
maven-shell-plugin-1.1
maven-simian-plugin-1.4
maven-ejb-plugin-1.4
maven-java-plugin-1.4
maven-console-plugin-1.1
maven-pdf-plugin-2.1
maven-release-plugin-1.3
maven-changes-plugin-1.4
maven-nsis-plugin-1.0
maven-checkstyle-plugin-2.4.1
maven-wizard-plugin-1.1
maven-uberjar-plugin-1.2
maven-caller-plugin-1.1
maven-junit-report-plugin-1.5
maven-eclipse-plugin-1.7
maven-latex-plugin-1.2
maven-jdeveloper-plugin-1.4
maven-aspectj-plugin-3.0
maven-idea-plugin-1.4
maven-jalopy-plugin-1.2
maven-test-plugin-1.6.1
maven-multichanges-plugin-1.1
Home Build properties: {jaxp.xslt.jar=C:/java/apache/xalan-2_5_D1//bin/xalan.jar,
servlet.jar=C:/java/sun/jwsdp-1.1/common/lib/servlet.jar, jaxp.jaxp.jar=C:/jav
a/apache/xalan-2_5_D1//bin/xml-apis.jar, junit.jar=C:/java/junit3.8.1/junit.jar}
Description:
Cannot use plugin in project.xml's report element.
I want to be able to say:
[snip]
maven-announcement-plugin
[snip]
Thanks.
-
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug
[jira] Closed: (MPANNOUNCEMENT-8) Plugin fails if destination directory doesn't exist
Message: The following issue has been closed. Resolver: Carlos Sanchez Date: Sun, 4 Jul 2004 4:21 PM You're right, it happens with version 1.1 but not with CVS version I'm almost sure I'd installed the CVS version but who knows... Sorry - View the issue: http://jira.codehaus.org/browse/MPANNOUNCEMENT-8 Here is an overview of the issue: - Key: MPANNOUNCEMENT-8 Summary: Plugin fails if destination directory doesn't exist Type: Bug Status: Closed Priority: Minor Resolution: CANNOT REPRODUCE Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-announcement-plugin Assignee: Vincent Massol Reporter: Carlos Sanchez Created: Sat, 3 Jul 2004 8:19 PM Updated: Sun, 4 Jul 2004 4:21 PM Description: - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVENUPLOAD-155) upload dom4j 1.5 RC1 to ibiblio
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MAVENUPLOAD-155 Here is an overview of the issue: - Key: MAVENUPLOAD-155 Summary: upload dom4j 1.5 RC1 to ibiblio Type: Task Status: Open Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-upload-requests Assignee: Jason van Zyl Reporter: Maarten Coene Created: Sun, 4 Jul 2004 4:19 PM Updated: Sun, 4 Jul 2004 4:19 PM Description: thanks Maarten - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MPNSIS-5) Bundle with JVM for computers without Java
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MPNSIS-5 Here is an overview of the issue: - Key: MPNSIS-5 Summary: Bundle with JVM for computers without Java Type: New Feature Status: Open Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-nsis-plugin Assignee: dion gillard Reporter: Geoffrey Created: Sun, 4 Jul 2004 4:11 PM Updated: Sun, 4 Jul 2004 4:11 PM Description: Many end users don't have Java, or don't have the correct version of Java to run the project. For J2SE desktop applications, bundling a JVM in the installer's exe would be really helpfull. It's possible that such an open source script has already been written for NSIS. Extra features that could be included for this task (but don't need to be in the first release): - a nsis property defining the version of the JVM bundled, defaulting to the java version needed by the pom. - public (for all programs on the desktop) or private (just for the project) JVM install - optionally install the JVM - picking the JVM to use when not installing the bundled one - different goals for generating an exe with or without JVM Reference: InstallAnywhere provides a commercial installer alternative. It has a free version that does most of the JVM functionality, but has many limitations such as no build from command line, support for i18n, etc - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPANNOUNCEMENT-8) Plugin fails if destination directory doesn't exist
The following comment has been added to this issue: Author: Vincent Massol Created: Sun, 4 Jul 2004 3:51 PM Body: Hi Carlos, It's working fine for me (see below). Do you have a use case that I could use to try to reproduce the problem? C:\dev\maven-plugins\announcement>maven clean __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0-final-SNAPSHOT build:start: clean:clean: [delete] Deleting directory C:\dev\maven-plugins\announcement\target [delete] Deleting: C:\dev\maven-plugins\announcement\velocity.log BUILD SUCCESSFUL Total time: 5 seconds Finished at: Sun Jul 04 21:49:43 CEST 2004 C:\dev\maven-plugins\announcement>maven announcement __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0-final-SNAPSHOT build:start: announcement:init: [mkdir] Created dir: C:\dev\maven-plugins\announcement\target\generated-xdocs\announcements announcement:check-version: announcement:generate: [echo] Generating announcement for release 1.2-SNAPSHOT in C:\dev\maven-plugins\announcement/target/generated-xdocs/announceme nts/announcement-1.2-SNAPSHOT.txt... BUILD SUCCESSFUL Total time: 2 seconds Finished at: Sun Jul 04 21:49:47 CEST 2004 C:\dev\maven-plugins\announcement> - View this comment: http://jira.codehaus.org/browse/MPANNOUNCEMENT-8?page=comments#action_21363 - View the issue: http://jira.codehaus.org/browse/MPANNOUNCEMENT-8 Here is an overview of the issue: - Key: MPANNOUNCEMENT-8 Summary: Plugin fails if destination directory doesn't exist Type: Bug Status: Open Priority: Minor Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-announcement-plugin Assignee: Vincent Massol Reporter: Carlos Sanchez Created: Sat, 3 Jul 2004 8:19 PM Updated: Sun, 4 Jul 2004 3:51 PM Description: - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/eclipse/xdocs faq.fml
epugh 2004/07/04 10:02:24 Added: eclipse/xdocs faq.fml Log: starting adding FAQ entries. Revision ChangesPath 1.1 maven-plugins/eclipse/xdocs/faq.fml Index: faq.fml === General I can't seem to get JUnit to show up in the classpath. What gives? You must have some unit tests for your project, otherwise JUnit is ignored. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/eclipse/xdocs properties.xml
epugh 2004/07/04 09:20:28
Modified:eclipse plugin.properties
eclipse/src/plugin-resources/templates classpath.jelly
eclipse/src/plugin-test maven.xml
eclipse/xdocs properties.xml
Log:
Add better support for generated sources
Revision ChangesPath
1.5 +1 -0 maven-plugins/eclipse/plugin.properties
Index: plugin.properties
===
RCS file: /home/cvs/maven-plugins/eclipse/plugin.properties,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- plugin.properties 4 Mar 2004 18:04:37 - 1.4
+++ plugin.properties 4 Jul 2004 16:20:28 - 1.5
@@ -24,3 +24,4 @@
# This accepts two values: 'all' for all the goals,
# and 'plugins' to generate only the plugins' default goals.
maven.eclipse.goals = plugins
+maven.gen.src=${maven.build.dir}/generated-sources
1.17 +9 -0
maven-plugins/eclipse/src/plugin-resources/templates/classpath.jelly
Index: classpath.jelly
===
RCS file:
/home/cvs/maven-plugins/eclipse/src/plugin-resources/templates/classpath.jelly,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- classpath.jelly 28 Jun 2004 22:07:32 - 1.16
+++ classpath.jelly 4 Jul 2004 16:20:28 - 1.17
@@ -27,6 +27,15 @@
trim="true">
+
+
+
+
+
+
+
+
+
1.5 +82 -53maven-plugins/eclipse/src/plugin-test/maven.xml
Index: maven.xml
===
RCS file: /home/cvs/maven-plugins/eclipse/src/plugin-test/maven.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- maven.xml 6 May 2004 05:43:12 - 1.4
+++ maven.xml 4 Jul 2004 16:20:28 - 1.5
@@ -20,7 +20,7 @@
xmlns:u="jelly:util"
xmlns:x="jelly:xml">
-
+
@@ -38,57 +38,86 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Dude ${dude}
+Dude Parent ${dude.parent}
+Dude Parent ${dude.files}
+
+file ${file}
+
+
+
1.11 +43 -2 maven-plugins/eclipse/xdocs/properties.xml
Index: properties.xml
===
RCS file: /home/cvs/maven-plugins/eclipse/xdocs/properties.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- properties.xml28 Jun 2004 22:07:31 - 1.10
+++ properties.xml4 Jul 2004 16:20:28 - 1.11
@@ -81,7 +81,7 @@
the classpath, like src/conf.
-
+
maven.eclipse.buildcommands
Yes
@@ -89,7 +89,7 @@
to include in the project description file.
-
+
maven.eclipse.projectnatures
Yes
@@ -98,6 +98,16 @@
will be added after the java nature.
+
+ maven.gen.src
+ Yes (default=${maven.build.dir}/generated-sources)
+
+The directory that generated source code is placed. Maven will select
+any directories under this as source code. This prevents the generated
+source from being removed whenever Eclipse does a clean build, and
allows
+the generated code to be clearly in the build directory.
+
+
Note that you will need to defined a MAVEN_REPO Java
@@ -131,6 +141,37 @@
The inverse also works. If you have included extra jars that shouldn't be
in the eclipse classpath then you can set
eclipse.dependency=false
+
+
+
+ When Eclipse is not generating source code for you there is a conflict
between
cvs commit: maven-plugins/eclipse/src/plugin-test .cvsignore
epugh 2004/07/04 09:20:04 Modified:eclipse/src/plugin-test .cvsignore Log: Ignore target directory Revision ChangesPath 1.2 +2 -1 maven-plugins/eclipse/src/plugin-test/.cvsignore Index: .cvsignore === RCS file: /home/cvs/maven-plugins/eclipse/src/plugin-test/.cvsignore,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- .cvsignore3 Feb 2004 19:14:55 - 1.1 +++ .cvsignore4 Jul 2004 16:20:04 - 1.2 @@ -1,3 +1,4 @@ *.log .project -.classpath \ No newline at end of file +.classpath +target - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: cvs commit: maven-plugins/ant/xdocs changes.xml
Sorry about my english, what you mean is that I had to write a test to
verify that the bug won't arise again, isn't it?
If I'm right I've just committed a test for that.
BTW the assert jelly tab library throws an exception when it's declared in
maven.xml
That's the case of the plugin-test in the ant plugin
> -Original Message-
> From: Dion Gillard [mailto:[EMAIL PROTECTED]
> Sent: Sunday, July 04, 2004 2:41 PM
> To: Maven Developers List
> Subject: Re: cvs commit: maven-plugins/ant/xdocs changes.xml
>
> No, i meant that you'd 'fixed' something, but we didn't have
> a test case to check it against.
> There are test cases for the ant plugin, and as someone once
> said, "Fix a bug without a test case and you're asking
> someone to break it again".
>
> On Sun, 4 Jul 2004 13:41:53 +0200, Carlos Sanchez
> <[EMAIL PROTECTED]> wrote:
> > Sorry, do you mean if I've wrotten a test for the changes I'd made?
> >
> > If that's the question I'm afraid the answer is no. I've
> only tested
> > it with one of my projects Tell me if test is needed and
> I'll do after
> > seeing Fernando Alonso win the Magny Cours Formula1 Grand Prix ;)
> >
> > Carlos Sanchez
> > A Coruña, Spain
> >
> > Oness Project
> > http://oness.sourceforge.net
> >
> >
> >
> >
> > > -Original Message-
> > > From: Dion Gillard [mailto:[EMAIL PROTECTED]
> > > Sent: Sunday, July 04, 2004 11:42 AM
> > > To: Maven Developers List
> > > Subject: Re: cvs commit: maven-plugins/ant/xdocs changes.xml
> > >
> > > Was there a failing plugin test for this?
> > >
> > > On 3 Jul 2004 17:49:14 -, [EMAIL PROTECTED]
> <[EMAIL PROTECTED]>
> > > wrote:
> > > > carlos 2004/07/03 10:49:14
> > > >
> > > > Modified:ant/src/plugin-resources/templates build.jelly
> > > >ant/xdocs changes.xml
> > > > Log:
> > > > Use relative paths in directory properties. Issue MPANT-16
> > > >
> > > > Revision ChangesPath
> > > > 1.16 +12 -6
> > > maven-plugins/ant/src/plugin-resources/templates/build.jelly
> > > >
> > > > Index: build.jelly
> > > >
> > >
> ===
> > > > RCS file:
> > > /home/cvs/maven-plugins/ant/src/plugin-resources/templates/bui
> > > ld.jelly,v
> > > > retrieving revision 1.15
> > > > retrieving revision 1.16
> > > > diff -u -r1.15 -r1.16
> > > > --- build.jelly 18 May 2004 21:16:04 - 1.15
> > > > +++ build.jelly 3 Jul 2004 17:49:14 - 1.16
> > > > @@ -42,15 +42,21 @@
> > > >
> > > >
> > > >
> > > > - value="${maven.build.dir}"/>
> > > > -
> > > > -
> > > > - value="${maven.test.dest}" />
> > > > + > > value="${pom.file.canonicalFile.parentFile}"/>
> > > > + > > path="${maven.build.dir}" separator="/" var="defaulttargetdir"/>
> > > > + value="${defaulttargetdir}"/>
> > > > +
> > > > +
> > > > + > > path="${maven.build.dest}" separator="/" var="classesdir"/>
> > > > +
> > > >
> > > >
> > > > - > > property="maven.test.dest" var="testclassesdir" />
> > > > + > > property="maven.test.dest" var="abstestclassesdir" />
> > > > + > > path="${abstestclassesdir}" separator="/" var="testclassesdir"/>
> > > > value="${testclassesdir}" />
> > > > - > > property="maven.test.reportsDirectory" var="testreportdir" />
> > > > +
> > > > + > > property="maven.test.reportsDirectory" var="abstestreportdir" />
> > > > + > > path="${abstestreportdir}" separator="/" var="testreportdir"/>
> > > > value="${testreportdir}" />
> > > >
> > > >
> > > > 1.23 +1 -0 maven-plugins/ant/xdocs/changes.xml
> > > >
> > > > Index: changes.xml
> > > >
> > >
> ===
> > > > RCS file: /home/cvs/maven-plugins/ant/xdocs/changes.xml,v
> > > > retrieving revision 1.22
> > > > retrieving revision 1.23
> > > > diff -u -r1.22 -r1.23
> > > > --- changes.xml 18 May 2004 21:29:51 - 1.22
> > > > +++ changes.xml 3 Jul 2004 17:49:14 - 1.23
> > > > @@ -25,6 +25,7 @@
> > > >
> > > >
> > > >
> > > > + > > due-to="Brent Worden" due-to-email="[EMAIL PROTECTED]">Use
> > > relative paths in directory properties.
> > > > Run Junit
> > > only if present in ANT (display a warning otherwise).
> > > >
> > > >
> > > >
> > > >
> > >
>
> > > -
> > > > To unsubscribe, e-mail: [EMAIL PROTECTED] For
> > > > additional commands, e-mail: [EMAIL PROTECTED]
> > > >
> > > >
> > >
> > >
>
> > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For
> > > additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> > >
> >
> >
> -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/ant/src/plugin-test maven.xml
carlos 2004/07/04 08:31:22 Modified:ant/src/plugin-test maven.xml Log: Use relative paths in directory properties. Issue MPANT-16 Revision ChangesPath 1.6 +12 -5 maven-plugins/ant/src/plugin-test/maven.xml Index: maven.xml === RCS file: /home/cvs/maven-plugins/ant/src/plugin-test/maven.xml,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- maven.xml 22 May 2004 03:00:20 - 1.5 +++ maven.xml 4 Jul 2004 15:31:22 - 1.6 @@ -18,6 +18,7 @@ @@ -31,12 +32,18 @@ - - - - - + + + + + + + + + + + - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/nsis/xdocs customizing.xml navigation.xml
dion2004/07/04 07:47:25 Modified:nsis/xdocs navigation.xml Added: nsis/xdocs customizing.xml Log: Start on customizing docs Revision ChangesPath 1.5 +1 -0 maven-plugins/nsis/xdocs/navigation.xml Index: navigation.xml === RCS file: /home/cvs/maven-plugins/nsis/xdocs/navigation.xml,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- navigation.xml4 Jul 2004 12:26:09 - 1.4 +++ navigation.xml4 Jul 2004 14:47:25 - 1.5 @@ -29,6 +29,7 @@ + 1.1 maven-plugins/nsis/xdocs/customizing.xml Index: customizing.xml === Maven NSIS Plug-in dIon Gillard Customizing Default Templates Default Template Scripts Custom Templates You can customize the resultant executable installer either by providing your own scripts that the existing templates includes, or you can provide your own templates. Of these, the easiest is to provide your own scripts to supplement the default templates. The most complex is to provide your own custom templates. No matter which way you decide to customize the installation process, you will need to be familiar with http://nsis.sourceforge.net/";>NSIS and have easy access to the http://nsis.sourceforge.net/Docs/";>NSIS Docs. We've also found the http://hmne.sourceforge.net/";>HM NIS EDIT tool, which is a free NSIS Editor/IDE, very useful. The plugin provides two templates by default: project.jelly to get access to information in project.xml from within NSIS scripts. setup.jelly which generates the final script for NSIS compilation. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MPNSIS-2) Generate exe in distributions directory.
Message: The following issue has been closed. Resolver: dion gillard Date: Sun, 4 Jul 2004 10:40 AM Done. There are issues with retrieving variables from the dist plugin still - View the issue: http://jira.codehaus.org/browse/MPNSIS-2 Here is an overview of the issue: - Key: MPNSIS-2 Summary: Generate exe in distributions directory. Type: Improvement Status: Closed Priority: Minor Resolution: FIXED Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-nsis-plugin Assignee: dion gillard Reporter: Geoffrey Created: Thu, 1 Jul 2004 2:50 PM Updated: Sun, 4 Jul 2004 10:40 AM Description: The normal distributions: .zip, .tar.gz, -src.zip, .tar.gz are generated in a directory defined by a property, defaulting to /target/distributions. The exe seems like a distribution to me :) - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/nsis/xdocs changes.xml
dion2004/07/04 07:29:20 Modified:nsis/xdocs changes.xml Log: Document change of exe location Revision ChangesPath 1.4 +3 -0 maven-plugins/nsis/xdocs/changes.xml Index: changes.xml === RCS file: /home/cvs/maven-plugins/nsis/xdocs/changes.xml,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- changes.xml 4 Jul 2004 12:27:09 - 1.3 +++ changes.xml 4 Jul 2004 14:29:20 - 1.4 @@ -25,6 +25,9 @@ + +Generate exe in distributions directory. + Rename PROJECT_DIST_DIR constant to PROJECT_DIST_BIN_DIR, and define - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/nsis/src/plugin-resources/templates setup.jelly
dion2004/07/04 07:27:30
Modified:nsis plugin.jelly
nsis/src/plugin-resources/templates setup.jelly
Log:
Fix for MPNSIS-2. Create .exe in distributions directory.
Revision ChangesPath
1.7 +3 -1 maven-plugins/nsis/plugin.jelly
Index: plugin.jelly
===
RCS file: /home/cvs/maven-plugins/nsis/plugin.jelly,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- plugin.jelly 4 Jul 2004 12:26:39 - 1.6
+++ plugin.jelly 4 Jul 2004 14:27:30 - 1.7
@@ -38,7 +38,7 @@
-
+
@@ -77,6 +77,8 @@
+
+
1.12 +1 -1 maven-plugins/nsis/src/plugin-resources/templates/setup.jelly
Index: setup.jelly
===
RCS file: /home/cvs/maven-plugins/nsis/src/plugin-resources/templates/setup.jelly,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- setup.jelly 4 Jul 2004 12:25:15 - 1.11
+++ setup.jelly 4 Jul 2004 14:27:30 - 1.12
@@ -54,7 +54,7 @@
Name "$${PROJECT_NAME}"
; Maven Setup executable
-OutFile "$${PROJECT_BUILD_DIR}\$${PROJECT_FINAL_NAME}.exe"
+OutFile "$${PROJECT_DIST_DIR}\$${PROJECT_FINAL_NAME}.exe"
; Adds an XP manifest to the installer
XPStyle on
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
1.0 branch and dist plugin
I'm having problems with maven:get in the latest builds of the 1.0 branch. In the NSIS plugin I have this: And it comes back blank. Thinking it was the variable, I tried: Still no luck. Also, running maven dist by itself works ok, but putting it as a pre-req for a plugin goal fails miserably with INTERNAL ERROR Reference made to goal 'dist' which has no definition. Any ideas? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVEN-1358) touchstone tests fail during 'maven dist' on maven itself
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MAVEN-1358 Here is an overview of the issue: - Key: MAVEN-1358 Summary: touchstone tests fail during 'maven dist' on maven itself Type: Bug Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Components: core Fix Fors: 1.0 Versions: 1.0 Assignee: Reporter: dion gillard Created: Sun, 4 Jul 2004 9:35 AM Updated: Sun, 4 Jul 2004 9:35 AM Description: Our processing order: subproject + | Cleaning subproject | Memory: 25M/32M + Starting the reactor... Our processing order: subproject + | Cleaning subproject | Memory: 27M/32M + build:end: test-reactor-run-twice: build:start: run_twice: run: build:start: clean:clean: clean: build:end: run: build:start: clean:clean: clean: build:end: build:end: test-context-switch: touchstone-partner:test-context-switch: build:start: touchstone:test-context-switch-dummy: [echo] testing differing plugin contexts BUILD FAILED File.. C:\source\maven\maven.xml Element... maven:maven Line.. 66 Column 7 Unable to obtain goal [touchstone-tests] -- C:\source\maven\src\test\touchstone-build\maven.xml:784:17: Default goal in s ubproject is not overriding parent project Total time: 2 minutes 32 seconds Finished at: Sun Jul 04 23:34:10 EST 2004 C:\source\maven> - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPPLUGIN-21) Autogenerate plugin.properties and properties documentation
The following comment has been added to this issue:
Author: dion gillard
Created: Sun, 4 Jul 2004 8:49 AM
Body:
1) Do we want to remove plugin:generate-properties yet? I'd be happier to see it
deprecated, and a message displayed to the user about it's replacement.
2) Do we really want a 'report' on the plugin properties, rather than just a
documented link to properties.html? Or is this to make sure the xdoc gets generated
automatically?
Other than that it's looking good.
-
View this comment:
http://jira.codehaus.org/browse/MPPLUGIN-21?page=comments#action_21357
-
View the issue:
http://jira.codehaus.org/browse/MPPLUGIN-21
Here is an overview of the issue:
-
Key: MPPLUGIN-21
Summary: Autogenerate plugin.properties and properties documentation
Type: New Feature
Status: Open
Priority: Minor
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-plugin-plugin
Assignee: Carlos Sanchez
Reporter: Carlos Sanchez
Created: Thu, 1 Jul 2004 5:43 AM
Updated: Sun, 4 Jul 2004 8:49 AM
Description:
As sent to the developer list this is a suggestion of how to create and document
plugin properties easier.
- Create an xml file called plugin-properties.xml
In the plugin project:
- Process it to generate the properties.xml xdoc using
maven-plugin-plugin
- Process it to generate the plugin.properties file (goal plugin:generate-properties),
maybe in the future there will be support for reading properties directly from it.
Just one issue, I wasn't able to add a newline character in a jsl file:
${name}=${default}
Examples:
The base file
http://maven.apache.org/reference/plugins/aspectj/plugin-properties.xml
The generated documentation
http://maven.apache.org/reference/plugins/aspectj/properties.html
The DTD
http://maven.apache.org/reference/plugins/aspectj/plugin_properties_1_0.dtd
-
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: cvs commit: maven-plugins/ant/xdocs changes.xml
No, i meant that you'd 'fixed' something, but we didn't have a test
case to check it against.
There are test cases for the ant plugin, and as someone once said,
"Fix a bug without a test case and you're asking someone to break it
again".
On Sun, 4 Jul 2004 13:41:53 +0200, Carlos Sanchez
<[EMAIL PROTECTED]> wrote:
> Sorry, do you mean if I've wrotten a test for the changes I'd made?
>
> If that's the question I'm afraid the answer is no. I've only tested it with
> one of my projects
> Tell me if test is needed and I'll do after seeing Fernando Alonso win the
> Magny Cours Formula1 Grand Prix ;)
>
> Carlos Sanchez
> A Coruña, Spain
>
> Oness Project
> http://oness.sourceforge.net
>
>
>
>
> > -Original Message-
> > From: Dion Gillard [mailto:[EMAIL PROTECTED]
> > Sent: Sunday, July 04, 2004 11:42 AM
> > To: Maven Developers List
> > Subject: Re: cvs commit: maven-plugins/ant/xdocs changes.xml
> >
> > Was there a failing plugin test for this?
> >
> > On 3 Jul 2004 17:49:14 -, [EMAIL PROTECTED]
> > <[EMAIL PROTECTED]> wrote:
> > > carlos 2004/07/03 10:49:14
> > >
> > > Modified:ant/src/plugin-resources/templates build.jelly
> > >ant/xdocs changes.xml
> > > Log:
> > > Use relative paths in directory properties. Issue MPANT-16
> > >
> > > Revision ChangesPath
> > > 1.16 +12 -6
> > maven-plugins/ant/src/plugin-resources/templates/build.jelly
> > >
> > > Index: build.jelly
> > >
> > ===
> > > RCS file:
> > /home/cvs/maven-plugins/ant/src/plugin-resources/templates/bui
> > ld.jelly,v
> > > retrieving revision 1.15
> > > retrieving revision 1.16
> > > diff -u -r1.15 -r1.16
> > > --- build.jelly 18 May 2004 21:16:04 - 1.15
> > > +++ build.jelly 3 Jul 2004 17:49:14 - 1.16
> > > @@ -42,15 +42,21 @@
> > >
> > >
> > >
> > > -
> > > -
> > > -
> > > -
> > > + > value="${pom.file.canonicalFile.parentFile}"/>
> > > + > path="${maven.build.dir}" separator="/" var="defaulttargetdir"/>
> > > +
> > > +
> > > +
> > > + > path="${maven.build.dest}" separator="/" var="classesdir"/>
> > > +
> > >
> > >
> > > - > property="maven.test.dest" var="testclassesdir" />
> > > + > property="maven.test.dest" var="abstestclassesdir" />
> > > + > path="${abstestclassesdir}" separator="/" var="testclassesdir"/>
> > >
> > > - > property="maven.test.reportsDirectory" var="testreportdir" />
> > > +
> > > + > property="maven.test.reportsDirectory" var="abstestreportdir" />
> > > + > path="${abstestreportdir}" separator="/" var="testreportdir"/>
> > >
> > >
> > >
> > > 1.23 +1 -0 maven-plugins/ant/xdocs/changes.xml
> > >
> > > Index: changes.xml
> > >
> > ===
> > > RCS file: /home/cvs/maven-plugins/ant/xdocs/changes.xml,v
> > > retrieving revision 1.22
> > > retrieving revision 1.23
> > > diff -u -r1.22 -r1.23
> > > --- changes.xml 18 May 2004 21:29:51 - 1.22
> > > +++ changes.xml 3 Jul 2004 17:49:14 - 1.23
> > > @@ -25,6 +25,7 @@
> > >
> > >
> > >
> > > + > due-to="Brent Worden" due-to-email="[EMAIL PROTECTED]">Use
> > relative paths in directory properties.
> > > Run Junit
> > only if present in ANT (display a warning otherwise).
> > >
> > >
> > >
> > >
> > -
> > > To unsubscribe, e-mail: [EMAIL PROTECTED] For
> > > additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED] For
> > additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/nsis/xdocs changes.xml
dion2004/07/04 05:27:09
Modified:nsis/xdocs changes.xml
Log:
Doc changes
Revision ChangesPath
1.3 +6 -0 maven-plugins/nsis/xdocs/changes.xml
Index: changes.xml
===
RCS file: /home/cvs/maven-plugins/nsis/xdocs/changes.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- changes.xml 2 Jul 2004 08:13:50 - 1.2
+++ changes.xml 4 Jul 2004 12:27:09 - 1.3
@@ -25,6 +25,12 @@
+
+Rename PROJECT_DIST_DIR constant to
+PROJECT_DIST_BIN_DIR, and define
+PROJECT_DIST_DIR to be ${maven.dist.dir>
+
+ Add docs on how the plugin process
works
Add some basic documentation
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/nsis plugin.jelly
dion2004/07/04 05:26:39 Modified:nsis plugin.jelly Log: Fix typo in comment Revision ChangesPath 1.6 +1 -1 maven-plugins/nsis/plugin.jelly Index: plugin.jelly === RCS file: /home/cvs/maven-plugins/nsis/plugin.jelly,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- plugin.jelly 4 Mar 2004 18:37:54 - 1.5 +++ plugin.jelly 4 Jul 2004 12:26:39 - 1.6 @@ -77,7 +77,7 @@ - + - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/nsis/xdocs process.xml navigation.xml
dion2004/07/04 05:26:09
Modified:nsis/xdocs navigation.xml
Added: nsis/xdocs process.xml
Log:
Add details on the typical process
Revision ChangesPath
1.4 +1 -0 maven-plugins/nsis/xdocs/navigation.xml
Index: navigation.xml
===
RCS file: /home/cvs/maven-plugins/nsis/xdocs/navigation.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- navigation.xml1 Jul 2004 19:27:43 - 1.3
+++ navigation.xml4 Jul 2004 12:26:09 - 1.4
@@ -28,6 +28,7 @@
+
1.1 maven-plugins/nsis/xdocs/process.xml
Index: process.xml
===
Maven NSIS Plug-in
dIon Gillard
The process of creating an installer from your
${maven.dist.bin.dir}
using the plugin is as follows:
You, the user invoke the nsis, or
nsis:installer
goal.
This calls the nsis:generate-project goal, which creates
a file, ${maven.build.dir}/project.nsh. This file contains
details from your project.xml file as constants so they are available
for during the NSIS compilation step. The file is generated from a jelly
template specified by the ${maven.nsis.project.template}
variable. See the properties documentation
for more information on the defaults for this variable.
Next the nsis:generate-setup goal is called, which creates
a file, ${maven.build.dir}/setup.nsi. This file is later
the file passed to the NSIS executable compiler,
makensis.exe.
This file is generated from a jelly template specified by the
${maven.nsis.setup.template} variable. See the
properties documentation
for more information on the defaults for this variable.
Lastly, makensis.exe is called to compile to generated
setup.nsi file.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/nsis/src/plugin-resources/templates project.jelly setup.jelly
dion2004/07/04 05:25:15
Modified:nsis/src/plugin-resources/templates project.jelly
setup.jelly
Log:
Rename PROJECT_DIST_DIR to PROJECT_DIST_BIN_DIR
Revision ChangesPath
1.6 +2 -1 maven-plugins/nsis/src/plugin-resources/templates/project.jelly
Index: project.jelly
===
RCS file: /home/cvs/maven-plugins/nsis/src/plugin-resources/templates/project.jelly,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- project.jelly 4 Mar 2004 18:37:54 - 1.5
+++ project.jelly 4 Jul 2004 12:25:15 - 1.6
@@ -43,7 +43,8 @@
!define PROJECT_REG_UNINSTALL_KEY
"Software\Microsoft\Windows\CurrentVersion\Uninstall\${pom.name} ${pom.version}"
!define PROJECT_STARTMENU_FOLDER "$$SMPROGRAMS\${pom.organization}\${pom.name}
${pom.currentVersion}"
!define PROJECT_VERSION "${pom.currentVersion}"
-!define PROJECT_DIST_DIR "${maven.dist.bin.assembly.dir}"
+!define PROJECT_DIST_BIN_DIR "${maven.dist.bin.assembly.dir}"
+!define PROJECT_DIST_DIR "${maven.dist.dir}"
1.11 +1 -1 maven-plugins/nsis/src/plugin-resources/templates/setup.jelly
Index: setup.jelly
===
RCS file: /home/cvs/maven-plugins/nsis/src/plugin-resources/templates/setup.jelly,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- setup.jelly 4 Mar 2004 18:37:54 - 1.10
+++ setup.jelly 4 Jul 2004 12:25:15 - 1.11
@@ -91,7 +91,7 @@
SetOutPath $$INSTDIR
; Put files and directories there
; the script will be run from a directory below Maven
- File /r "$${PROJECT_DIST_DIR}\*.*"
+ File /r "$${PROJECT_DIST_BIN_DIR}\*.*"
; Write the installation path into the registry
WriteRegStr HKLM "$${PROJECT_REG_KEY}" "Install_Dir" "$$INSTDIR"
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/ant/src/plugin-resources/templates build.jelly
carlos 2004/07/04 04:58:21 Modified:ant/src/plugin-resources/templates build.jelly Log: Added testclassesdir property although there's no test source directory as it was incorrectly removed Revision ChangesPath 1.17 +3 -0 maven-plugins/ant/src/plugin-resources/templates/build.jelly Index: build.jelly === RCS file: /home/cvs/maven-plugins/ant/src/plugin-resources/templates/build.jelly,v retrieving revision 1.16 retrieving revision 1.17 diff -u -r1.16 -r1.17 --- build.jelly 3 Jul 2004 17:49:14 - 1.16 +++ build.jelly 4 Jul 2004 11:58:21 - 1.17 @@ -50,6 +50,9 @@ + + + - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPPLUGIN-21) Autogenerate plugin.properties and properties documentation
The following comment has been added to this issue:
Author: Carlos Sanchez
Created: Sun, 4 Jul 2004 7:43 AM
Body:
Forgot to add test-generate-properties to testPlugin goal
-
View this comment:
http://jira.codehaus.org/browse/MPPLUGIN-21?page=comments#action_21356
-
View the issue:
http://jira.codehaus.org/browse/MPPLUGIN-21
Here is an overview of the issue:
-
Key: MPPLUGIN-21
Summary: Autogenerate plugin.properties and properties documentation
Type: New Feature
Status: Open
Priority: Minor
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-plugin-plugin
Assignee: Carlos Sanchez
Reporter: Carlos Sanchez
Created: Thu, 1 Jul 2004 5:43 AM
Updated: Sun, 4 Jul 2004 7:43 AM
Description:
As sent to the developer list this is a suggestion of how to create and document
plugin properties easier.
- Create an xml file called plugin-properties.xml
In the plugin project:
- Process it to generate the properties.xml xdoc using
maven-plugin-plugin
- Process it to generate the plugin.properties file (goal plugin:generate-properties),
maybe in the future there will be support for reading properties directly from it.
Just one issue, I wasn't able to add a newline character in a jsl file:
${name}=${default}
Examples:
The base file
http://maven.apache.org/reference/plugins/aspectj/plugin-properties.xml
The generated documentation
http://maven.apache.org/reference/plugins/aspectj/properties.html
The DTD
http://maven.apache.org/reference/plugins/aspectj/plugin_properties_1_0.dtd
-
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: cvs commit: maven-plugins/ant/xdocs changes.xml
Sorry, do you mean if I've wrotten a test for the changes I'd made?
If that's the question I'm afraid the answer is no. I've only tested it with
one of my projects
Tell me if test is needed and I'll do after seeing Fernando Alonso win the
Magny Cours Formula1 Grand Prix ;)
Carlos Sanchez
A Coruña, Spain
Oness Project
http://oness.sourceforge.net
> -Original Message-
> From: Dion Gillard [mailto:[EMAIL PROTECTED]
> Sent: Sunday, July 04, 2004 11:42 AM
> To: Maven Developers List
> Subject: Re: cvs commit: maven-plugins/ant/xdocs changes.xml
>
> Was there a failing plugin test for this?
>
> On 3 Jul 2004 17:49:14 -, [EMAIL PROTECTED]
> <[EMAIL PROTECTED]> wrote:
> > carlos 2004/07/03 10:49:14
> >
> > Modified:ant/src/plugin-resources/templates build.jelly
> >ant/xdocs changes.xml
> > Log:
> > Use relative paths in directory properties. Issue MPANT-16
> >
> > Revision ChangesPath
> > 1.16 +12 -6
> maven-plugins/ant/src/plugin-resources/templates/build.jelly
> >
> > Index: build.jelly
> >
> ===
> > RCS file:
> /home/cvs/maven-plugins/ant/src/plugin-resources/templates/bui
> ld.jelly,v
> > retrieving revision 1.15
> > retrieving revision 1.16
> > diff -u -r1.15 -r1.16
> > --- build.jelly 18 May 2004 21:16:04 - 1.15
> > +++ build.jelly 3 Jul 2004 17:49:14 - 1.16
> > @@ -42,15 +42,21 @@
> >
> >
> >
> > -
> > -
> > -
> > -
> > + value="${pom.file.canonicalFile.parentFile}"/>
> > + path="${maven.build.dir}" separator="/" var="defaulttargetdir"/>
> > +
> > +
> > +
> > + path="${maven.build.dest}" separator="/" var="classesdir"/>
> > +
> >
> >
> > - property="maven.test.dest" var="testclassesdir" />
> > + property="maven.test.dest" var="abstestclassesdir" />
> > + path="${abstestclassesdir}" separator="/" var="testclassesdir"/>
> >
> > - property="maven.test.reportsDirectory" var="testreportdir" />
> > +
> > + property="maven.test.reportsDirectory" var="abstestreportdir" />
> > + path="${abstestreportdir}" separator="/" var="testreportdir"/>
> >
> >
> >
> > 1.23 +1 -0 maven-plugins/ant/xdocs/changes.xml
> >
> > Index: changes.xml
> >
> ===
> > RCS file: /home/cvs/maven-plugins/ant/xdocs/changes.xml,v
> > retrieving revision 1.22
> > retrieving revision 1.23
> > diff -u -r1.22 -r1.23
> > --- changes.xml 18 May 2004 21:29:51 - 1.22
> > +++ changes.xml 3 Jul 2004 17:49:14 - 1.23
> > @@ -25,6 +25,7 @@
> >
> >
> >
> > + due-to="Brent Worden" due-to-email="[EMAIL PROTECTED]">Use
> relative paths in directory properties.
> > Run Junit
> only if present in ANT (display a warning otherwise).
> >
> >
> >
> >
> -
> > To unsubscribe, e-mail: [EMAIL PROTECTED] For
> > additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED] For
> additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: cvs commit: maven maven.xml
How about including test as well?
On 3 Jul 2004 01:50:37 -, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> brett 2004/07/02 18:50:37
>
> Modified:.Tag: MAVEN-1_0-BRANCH maven.xml
> Log:
> generate a seed repo. just encompasses site (and default reports), java:compile
>
> Revision ChangesPath
> No revision
> No revision
> 1.97.2.29 +22 -0 maven/maven.xml
>
> Index: maven.xml
> ===
> RCS file: /home/cvs/maven/maven.xml,v
> retrieving revision 1.97.2.28
> retrieving revision 1.97.2.29
> diff -u -r1.97.2.28 -r1.97.2.29
> --- maven.xml 12 Jun 2004 04:38:50 - 1.97.2.28
> +++ maven.xml 3 Jul 2004 01:50:37 - 1.97.2.29
> @@ -379,5 +379,27 @@
>
>
>
> +
> +
> +
> +
> +
> +
> +
> + descriptor="src/test/touchstone-build/src/reactor-build/default/project.xml"
> goals="java:compile,site" />
> +
> + compression="gzip" longfile="gnu">
> +
> +
> +
> +
> + name="${dep.groupId}/jars/${dep.artifactId}-${dep.version}.jar" />
> + name="${dep.groupId}/jars/${dep.artifactId}-${dep.version}.jar.md5" />
> +
> +
> +
> +
> +
> +
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: cvs commit: maven-plugins/xdoc/xdocs changes.xml
Are any of the 'new' xdoc features going to get documented somewhere?
On 3 Jul 2004 02:02:30 -, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> brett 2004/07/02 19:02:30
>
> Modified:xdoc plugin.jelly
>xdoc/src/plugin-resources navigation.jelly
>xdoc/src/plugin-resources/templates maven-reports.xml
>xdoc/xdocs changes.xml
> Log:
> allow external link to be used for a report
>
> Revision ChangesPath
> 1.61 +1 -0 maven-plugins/xdoc/plugin.jelly
>
> Index: plugin.jelly
> ===
> RCS file: /home/cvs/maven-plugins/xdoc/plugin.jelly,v
> retrieving revision 1.60
> retrieving revision 1.61
> diff -u -r1.60 -r1.61
> --- plugin.jelly 10 May 2004 22:25:05 - 1.60
> +++ plugin.jelly 3 Jul 2004 02:02:30 - 1.61
> @@ -74,6 +74,7 @@
> ${report.put('pluginName', pluginName)}
> ${report.put('description', description)}
> ${report.put('link', link)}
> + ${report.put('externalLink', externalLink)}
> ${report.put('target', target)}
> ${reports.add(report)}
>
>
> 1.10 +5 -1 maven-plugins/xdoc/src/plugin-resources/navigation.jelly
>
> Index: navigation.jelly
> ===
> RCS file: /home/cvs/maven-plugins/xdoc/src/plugin-resources/navigation.jelly,v
> retrieving revision 1.9
> retrieving revision 1.10
> diff -u -r1.9 -r1.10
> --- navigation.jelly 10 May 2004 22:25:05 - 1.9
> +++ navigation.jelly 3 Jul 2004 02:02:30 - 1.10
> @@ -53,9 +53,13 @@
> collapse="true">
>
>
> +
>
> target="${report.target}"/>
>
> +
> + target="${report.target}"/>
> +
>
>
>
> @@ -76,4 +80,4 @@
>
>
>
> -
> \ No newline at end of file
> +
>
> 1.13 +10 -0
> maven-plugins/xdoc/src/plugin-resources/templates/maven-reports.xml
>
> Index: maven-reports.xml
> ===
> RCS file:
> /home/cvs/maven-plugins/xdoc/src/plugin-resources/templates/maven-reports.xml,v
> retrieving revision 1.12
> retrieving revision 1.13
> diff -u -r1.12 -r1.13
> --- maven-reports.xml 18 May 2004 22:39:12 - 1.12
> +++ maven-reports.xml 3 Jul 2004 02:02:30 - 1.13
> @@ -47,6 +47,16 @@
> $report.description
>
>#end
> +#if ($report.externalLink && $report.externalLink.length() != 0)
> +
> + #if($report.target && $report.target.length() != 0)
> + target="${report.target}">$report.name
> + #else
> + class="externalLink">$report.name
> + #end
> + $report.description
> +
> +#end
> #end
>
>
>
> 1.59 +1 -0 maven-plugins/xdoc/xdocs/changes.xml
>
> Index: changes.xml
> ===
> RCS file: /home/cvs/maven-plugins/xdoc/xdocs/changes.xml,v
> retrieving revision 1.58
> retrieving revision 1.59
> diff -u -r1.58 -r1.59
> --- changes.xml 2 Jul 2004 21:27:56 - 1.58
> +++ changes.xml 3 Jul 2004 02:02:30 - 1.59
> @@ -26,6 +26,7 @@
>
>
>
> + Add an externalLink attribute to a report to
> use if link is not present
>
>Added a link to the release notes in the download report. Note that this
>link is only created if the project has a xdocs/changes.xml
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: cvs commit: maven-plugins/ant/xdocs changes.xml
Was there a failing plugin test for this? On 3 Jul 2004 17:49:14 -, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > carlos 2004/07/03 10:49:14 > > Modified:ant/src/plugin-resources/templates build.jelly >ant/xdocs changes.xml > Log: > Use relative paths in directory properties. Issue MPANT-16 > > Revision ChangesPath > 1.16 +12 -6 maven-plugins/ant/src/plugin-resources/templates/build.jelly > > Index: build.jelly > === > RCS file: /home/cvs/maven-plugins/ant/src/plugin-resources/templates/build.jelly,v > retrieving revision 1.15 > retrieving revision 1.16 > diff -u -r1.15 -r1.16 > --- build.jelly 18 May 2004 21:16:04 - 1.15 > +++ build.jelly 3 Jul 2004 17:49:14 - 1.16 > @@ -42,15 +42,21 @@ > > > > - > - > - > - > + > + separator="/" var="defaulttargetdir"/> > + > + > + > + separator="/" var="classesdir"/> > + > > > - var="testclassesdir" /> > + var="abstestclassesdir" /> > + separator="/" var="testclassesdir"/> > > - property="maven.test.reportsDirectory" var="testreportdir" /> > + > + property="maven.test.reportsDirectory" var="abstestreportdir" /> > + separator="/" var="testreportdir"/> > > > > 1.23 +1 -0 maven-plugins/ant/xdocs/changes.xml > > Index: changes.xml > === > RCS file: /home/cvs/maven-plugins/ant/xdocs/changes.xml,v > retrieving revision 1.22 > retrieving revision 1.23 > diff -u -r1.22 -r1.23 > --- changes.xml 18 May 2004 21:29:51 - 1.22 > +++ changes.xml 3 Jul 2004 17:49:14 - 1.23 > @@ -25,6 +25,7 @@ > > > > + due-to-email="[EMAIL PROTECTED]">Use relative paths in directory properties. > Run Junit only if present in ANT > (display a warning otherwise). > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
