[ http://jira.codehaus.org/browse/MASSEMBLY-54?page=comments#action_56929 ]
Corridor Software Developer commented on MASSEMBLY-54:
--
agreed, this is an issue when creating distributions for various environments.
We're currently working ar
[ http://jira.codehaus.org/browse/CONTINUUM-483?page=comments#action_52897
]
Corridor Software Developer commented on CONTINUUM-483:
---
I'd like to add for the sake of completeness that I ended with the following
command:
su - $RUN_AS_U
[ http://jira.codehaus.org/browse/CONTINUUM-410?page=comments#action_52333
]
Corridor Software Developer commented on CONTINUUM-410:
---
Yep, it's the best approach. It uses the existing run.sh script with continuum,
which operates as an
[ http://jira.codehaus.org/browse/MEV-6?page=comments#action_51143 ]
Corridor Software Developer commented on MEV-6:
---
This dependency doesn't appear to be in the maven 2 repository. The
xmlbeans-maven-plugin depends on it because of the stax de
[ http://jira.codehaus.org/browse/MNG-32?page=comments#action_51141 ]
Corridor Software Developer commented on MNG-32:
I am Dave. Kenney Westerhof pointed me to the apache maven sandbox for an
example test project runner maven-it-plugin used
503 Error downloading geronimo:geronimo-j2ee 1.0-M5 pom
---
Key: MNG-1485
URL: http://jira.codehaus.org/browse/MNG-1485
Project: Maven 2
Type: Bug
Environment: ibiblio
Reporter: Corridor Software Developer
Se
Exception error messages and i18n
-
Key: MNG-1453
URL: http://jira.codehaus.org/browse/MNG-1453
Project: Maven 2
Type: Improvement
Components: maven-core
Versions: 2.0
Environment: all
Reporter: Corridor Software Devel
Assigning a runAs user in the rc script yields "directory does not exist" error.
Key: CONTINUUM-410
URL: http://jira.codehaus.org/browse/CONTINUUM-410
Project: Continuum
Type: Bug
Comp
[ http://jira.codehaus.org/browse/MNG-1178?page=all ]
Corridor Software Developer updated MNG-1178:
-
Attachment: mng-1178-1.tar.gz
I am receiving the same exception under the following conditions:
- Revision: 326303
- Consistently caused wi
[ http://jira.codehaus.org/browse/MNG-1178?page=comments#action_48814 ]
Corridor Software Developer commented on MNG-1178:
--
The problem seems to stem from having a dependency on junit 3.7 in a
subproject. Fabrizio, I'm assuming the junit de
NPE In DiagnosisUtils while using tomcat plugin
---
Key: MNG-1235
URL: http://jira.codehaus.org/browse/MNG-1235
Project: Maven 2
Type: Bug
Components: maven-core
Versions: 2.0 (RC)
Environment: gentoo linux, jd
[ http://jira.codehaus.org/browse/MNG-1130?page=comments#action_48549 ]
Corridor Software Developer commented on MNG-1130:
--
https://svn.codehaus.org/mojo/trunk/mojo/mojo-sandbox/netbeans-freeform-maven-plugin/
is a better example. Demonstra
[ http://jira.codehaus.org/browse/MNG-1130?page=comments#action_48547 ]
Corridor Software Developer commented on MNG-1130:
--
The jpox plugin on the mojo site has an example of an automated unit test.
Check it out of svn:
https://svn.codeha
[ http://jira.codehaus.org/browse/MNG-1130?page=comments#action_48541 ]
Corridor Software Developer commented on MNG-1130:
--
Suggested Answers:
1) JarSignMojo is a good name.
2) Putting the signed jar at
${project.build.directory}/signed/${
[ http://jira.codehaus.org/browse/MNG-1130?page=comments#action_48513 ]
Corridor Software Developer commented on MNG-1130:
--
Brought them over from the keystore settings properties of the maven 1 jnlp
plugin. I thought it was a little stran
[ http://jira.codehaus.org/browse/MNG-1130?page=all ]
Corridor Software Developer updated MNG-1130:
-
Attachment: mng-1130.tar.gz
rough ideas of how plugin configurations would appear.
> Support jar signing.
>
>
>
Support jar signing.
Key: MNG-1130
URL: http://jira.codehaus.org/browse/MNG-1130
Project: Maven 2
Type: New Feature
Components: maven-jar-plugin
Versions: 2.0-beta-3
Environment: gentoo linux, jdk 1.4.2_06
Reporter: Corridor Softwar
Reformat the autogenerated goal parameters page to improve readibility.
---
Key: MNG-1091
URL: http://jira.codehaus.org/browse/MNG-1091
Project: Maven 2
Type: Improvement
Components: maven-plugin-p
[ http://jira.codehaus.org/browse/MNG-1044?page=comments#action_47431 ]
Corridor Software Developer commented on MNG-1044:
--
Test project and code fix are in svn now. Running src/test/projects/mojo-54
ought to yield the warnings described no
@requiresDependencyResolution compile doesn't set plugin artifact file.
---
Key: MNG-1044
URL: http://jira.codehaus.org/browse/MNG-1044
Project: Maven 2
Type: Bug
Components: maven-artifact
V
[ http://jira.codehaus.org/browse/MNG-1009?page=comments#action_47024 ]
Corridor Software Developer commented on MNG-1009:
--
m2 plugin:xdoc site:site generates an xdoc which is then rolled into the site.
> Is it possible for all plugins to
[ http://jira.codehaus.org/browse/MNG-910?page=comments#action_46619 ]
Corridor Software Developer commented on MNG-910:
-
outdated 1.0 snapshot, I believe it was
maven-xdoclet-plugin-1.0-20050615.091250-3.jar or
maven-xdoclet-plugin-1.0-2005
[ http://jira.codehaus.org/browse/MNG-910?page=all ]
Corridor Software Developer closed MNG-910:
---
Resolution: Won't Fix
environment issue. please disregard.
> Plugin descriptor in pom.xml causes NPE when DefaultPluginManager populates
>
Plugin descriptor in pom.xml causes NPE when DefaultPluginManager populates the
plugin's fields.
Key: MNG-910
URL: http://jira.codehaus.org/browse/MNG-910
Project: Maven 2
[ http://jira.codehaus.org/browse/MNG-643?page=all ]
Corridor Software Developer updated MNG-643:
Attachment: FilterCriteriaForCompilerPlugin.patch
The last conversation put the configuration of this functionality as such:
or
[ http://jira.codehaus.org/browse/MNG-643?page=comments#action_44765 ]
Corridor Software Developer commented on MNG-643:
-
Dan Tran:
Assuming the generated-source directory is added to the source path for the
compile goal, then yes, the filte
[ http://jira.codehaus.org/browse/MNG-744?page=comments#action_44593 ]
Corridor Software Developer commented on MNG-744:
-
Adding my name to the Confluence Maven Plugin Matrix to indicate that the
plugin is being developed.
> Create and main
Create and maintain an M2 implementation of a maven webstart (JNLP) plugin.
---
Key: MNG-744
URL: http://jira.codehaus.org/browse/MNG-744
Project: Maven 2
Type: New Feature
Components: maven-pl
[ http://jira.codehaus.org/browse/MNG-631?page=all ]
Corridor Software Developer resolved MNG-631:
-
Resolution: Fixed
Fix Version: (was: 2.0-beta-1)
Code changes committed to the mojo repository. Maven Plugin Matrix updated as
[ http://jira.codehaus.org/browse/MNG-700?page=all ]
Corridor Software Developer resolved MNG-700:
-
Resolution: Fixed
Updated the plugin matrix to reflect the code update.
> Update Maven Plugin Matrix to reflect availability of maven XM
Update Maven Plugin Matrix to reflect availability of maven XML Beans Plugin.
-
Key: MNG-700
URL: http://jira.codehaus.org/browse/MNG-700
Project: Maven 2
Type: Improvement
Components: docu
[ http://jira.codehaus.org/browse/MNG-631?page=comments#action_43952 ]
Corridor Software Developer commented on MNG-631:
-
Rather than resubmitting as a tarball, the code has been committed to the
codehaus mojo svn repo.
> Update the Apache
[ http://jira.codehaus.org/browse/MNG-631?page=comments#action_43482 ]
Corridor Software Developer commented on MNG-631:
-
Answers:
1) CodedException is an extension of MojoExecutionException which consolidates
all of the error messages of t
[ http://jira.codehaus.org/browse/MNG-643?page=all ]
Corridor Software Developer updated MNG-643:
Attachment: FilterCriteriaForCompilerPlugin.patch
Testing revealed that assuming empty filters meant compile everything was
wrong. Updated to
[ http://jira.codehaus.org/browse/MNG-643?page=all ]
Corridor Software Developer updated MNG-643:
Attachment: FilterCriteriaForCompilerPlugin.patch
That's very reasonable. This patch is an implementation of that idea. The
compiler plugin fil
Support and for the source and testSource directories.
Key: MNG-643
URL: http://jira.codehaus.org/browse/MNG-643
Project: Maven 2
Type: Improvement
Components: maven-model
Versions
Update the Apache XML Beans plugin based on latest changes to plugin API & 1.x
releases.
Key: MNG-631
URL: http://jira.codehaus.org/browse/MNG-631
Project: Maven 2
Type: Improve
[ http://jira.codehaus.org/browse/MNG-581?page=all ]
Corridor Software Developer updated MNG-581:
Attachment: IncludeOutputInCompilerClasspath.maven-project.patch
This patch adds the output directory to the compile classpath in the same
man
[ http://jira.codehaus.org/browse/MNG-581?page=comments#action_42732 ]
Corridor Software Developer commented on MNG-581:
-
Someone please check me, but I believe this won't do any good now that I have
another look at it. MavenProject.getCompil
Add target/classes director to compiler:compile classpath
-
Key: MNG-581
URL: http://jira.codehaus.org/browse/MNG-581
Project: Maven 2
Type: Improvement
Components: maven-plugins
Versions: 2.0-alpha-3
Maven Plugin Matrix: XML Beans 2.0 support for m2
-
Key: MNG-566
URL: http://jira.codehaus.org/browse/MNG-566
Project: Maven 2
Type: Improvement
Components: maven-plugins, documentation
Environment: n/a
Reporter:
JavadocReport is missing @requiresDependencyResolution compile tag
---
Key: MNG-565
URL: http://jira.codehaus.org/browse/MNG-565
Project: Maven 2
Type: Bug
Components: maven-reports
Versions: 2.
AbstractMavenReport.execut() exception handling
---
Key: MNG-564
URL: http://jira.codehaus.org/browse/MNG-564
Project: Maven 2
Type: Bug
Components: maven-reports
Versions: 2.0-alpha-3
Environment: gentoo linux
[ http://jira.codehaus.org/browse/MNG-556?page=comments#action_42570 ]
Corridor Software Developer commented on MNG-556:
-
Ran into this as well while developing a plugin, only it was caused by not
having @requiresDependencyResolution in the
M2: pom for javax:j2ee:1.4
--
Key: MAVENUPLOAD-417
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-417
Project: maven-upload-requests
Type: Improvement
Reporter: Corridor Software Developer
Attachments: j2ee-1.4.pom
Here is a basic pom.
45 matches
Mail list logo