[jira] Created: (MAVENUPLOAD-645) Jini Service Archetype version 2.0
Jini Service Archetype version 2.0 -- Key: MAVENUPLOAD-645 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-645 Project: maven-upload-requests Type: Task Reporter: Chris Sterling Archetype for Jini service project creation -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVENUPLOAD-644) Maven Jini Plug-in version 2.0
Maven Jini Plug-in version 2.0 -- Key: MAVENUPLOAD-644 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-644 Project: maven-upload-requests Type: Task Reporter: Chris Sterling This is a Maven plug-in for Jini service based projects. It's initial capabilities are: * Archetype for Jini service project creation * Starting/Stopping of Jini starter kit services: Reggie, Mahalo, Phoenix, Fiddler, Norm, Mercury, Outrigger, Browser, and HTTP daemon * Configurable RMI runtime: JRMP, JERI, or JERI/JSSE * Configurable activation and persistence modes: transient, activatable, nonactivatable -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MECLIPSE-50) Add getter/setter methods to the Eclipse Plugin Mojos to allow reuse via composition
[ http://jira.codehaus.org/browse/MECLIPSE-50?page=all ] Rahul Thakur updated MECLIPSE-50: - Attachment: MECLIPSE-50.diff > Add getter/setter methods to the Eclipse Plugin Mojos to allow reuse via > composition > > > Key: MECLIPSE-50 > URL: http://jira.codehaus.org/browse/MECLIPSE-50 > Project: Maven 2.x Eclipse Plugin > Type: New Feature > Reporter: Rahul Thakur > Assignee: Jason van Zyl > Attachments: MECLIPSE-50.diff > > > Add getter/setter methods to Mojos under Eclipse Plugin to allow extension > and reuse via composition. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MECLIPSE-50) Add getter/setter methods to the Eclipse Plugin Mojos to allow reuse via composition
Add getter/setter methods to the Eclipse Plugin Mojos to allow reuse via composition Key: MECLIPSE-50 URL: http://jira.codehaus.org/browse/MECLIPSE-50 Project: Maven 2.x Eclipse Plugin Type: New Feature Reporter: Rahul Thakur Assigned to: Jason van Zyl Add getter/setter methods to Mojos under Eclipse Plugin to allow extension and reuse via composition. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-33) add based on existing indexer for jar classes, packages and filenames
[ http://jira.codehaus.org/browse/MRM-33?page=all ] Edwin Punzalan updated MRM-33: -- Remaining Estimate: 18 hours Original Estimate: 18 hours > add based on existing indexer for jar classes, packages and filenames > - > > Key: MRM-33 > URL: http://jira.codehaus.org/browse/MRM-33 > Project: Maven Repository Manager > Type: Sub-task > Components: indexing > Reporter: Brett Porter > Assignee: Edwin Punzalan > Fix For: 1.0-alpha-1 > > Original Estimate: 18 hours > Remaining: 18 hours > -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-1851) "Duplicate project ID found" message with maven-artifact-ant-2.0.1
[ http://jira.codehaus.org/browse/MNG-1851?page=comments#action_53903 ]
Brett Porter commented on MNG-1851:
---
r357237
Are you sure you aren't looking at trunk?
> "Duplicate project ID found" message with maven-artifact-ant-2.0.1
> --
>
> Key: MNG-1851
> URL: http://jira.codehaus.org/browse/MNG-1851
> Project: Maven 2
> Type: Bug
> Components: Ant tasks
> Versions: 2.0.1
> Reporter: John Casey
> Assignee: John Casey
> Priority: Blocker
> Fix For: 2.0.2
>
>
> from the original email:
> I tried upgrading my Maven 2 Ant Tasks' JAR tonight, and after doing
> so, I'm getting the following error:
> foxxy:~/dev/equinox mraible$ ant war
> Buildfile: build.xml
> init:
> [artifact:dependencies] An error has occurred while processing the
> Maven artifact tasks.
> [artifact:dependencies] Diagnosis:
> [artifact:dependencies]
> [artifact:dependencies] Unable to build project:
> /Users/mraible/Work/equinox/pom.xml
> [artifact:dependencies] Duplicate project ID found in
> /Users/mraible/Work/equinox/pom.xml
> BUILD FAILED
> /Users/mraible/Work/equinox/build.xml:27: Unable to build project:
> /Users/mraible/Work/equinox/pom.xml
> Total time: 2 seconds
> foxxy:~/dev/equinox mraible$
> I haven't been able to find the "duplicate project id" the error is
> referring to. The strange thing is if I run "mvn package" on my
> project, everything works fine with Maven 2.0.1. If I revert my
> maven-artifact-ant-2.0.1-dep.jar to maven-artifact-ant-2.0-dep.jar,
> everything works as expected.
> Here's how I declare the Maven Ant tasks in my build.xml:
>
> uri="urn:maven-artifact-ant">
>
> location="${basedir}/lib/maven-artifact-ant-2.0-dep.jar" />
>
>
>
> Here's line 27 of build.xml:
> filesetId="compile.fileset" useScope="compile">
>
>
> Thanks,
> Matt
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
--
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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: m2 plugin classpath
I had this same issue with a Kodo plugin I wrote. It seems the only way is to extend the class loader. I can send some code if you want to persue this option. -Original Message- From: Miguel Griffa [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 20, 2005 7:17 PM To: Maven Developers List Subject: m2 plugin classpath Hi all I have an m2 plugin that neets to run using classes compiled from the project. I have added for this @execute phase=compile so the project gets compiled first, but I can't find a way to add the project classpath to the running plugin classpath, I have considered creating an new jvm or creating a classloader, but I think this 2 options are horrible, there must be a better way. I'd really appreciate any feedback on this, thanks -- Miguel Griffa Skype: miguel.griffa Y!: m_griffa MSN: [EMAIL PROTECTED] Cell: 54-911-62519355 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-1851) "Duplicate project ID found" message with maven-artifact-ant-2.0.1
[ http://jira.codehaus.org/browse/MNG-1851?page=comments#action_53902 ]
Tomislav Bodor commented on MNG-1851:
-
I have looked at the current 2.0.2 snapshot (and svn trunk) and there doesn't
seem to be any difference in behaviour (or code). Is this fix committed?
> "Duplicate project ID found" message with maven-artifact-ant-2.0.1
> --
>
> Key: MNG-1851
> URL: http://jira.codehaus.org/browse/MNG-1851
> Project: Maven 2
> Type: Bug
> Components: Ant tasks
> Versions: 2.0.1
> Reporter: John Casey
> Assignee: John Casey
> Priority: Blocker
> Fix For: 2.0.2
>
>
> from the original email:
> I tried upgrading my Maven 2 Ant Tasks' JAR tonight, and after doing
> so, I'm getting the following error:
> foxxy:~/dev/equinox mraible$ ant war
> Buildfile: build.xml
> init:
> [artifact:dependencies] An error has occurred while processing the
> Maven artifact tasks.
> [artifact:dependencies] Diagnosis:
> [artifact:dependencies]
> [artifact:dependencies] Unable to build project:
> /Users/mraible/Work/equinox/pom.xml
> [artifact:dependencies] Duplicate project ID found in
> /Users/mraible/Work/equinox/pom.xml
> BUILD FAILED
> /Users/mraible/Work/equinox/build.xml:27: Unable to build project:
> /Users/mraible/Work/equinox/pom.xml
> Total time: 2 seconds
> foxxy:~/dev/equinox mraible$
> I haven't been able to find the "duplicate project id" the error is
> referring to. The strange thing is if I run "mvn package" on my
> project, everything works fine with Maven 2.0.1. If I revert my
> maven-artifact-ant-2.0.1-dep.jar to maven-artifact-ant-2.0-dep.jar,
> everything works as expected.
> Here's how I declare the Maven Ant tasks in my build.xml:
>
> uri="urn:maven-artifact-ant">
>
> location="${basedir}/lib/maven-artifact-ant-2.0-dep.jar" />
>
>
>
> Here's line 27 of build.xml:
> filesetId="compile.fileset" useScope="compile">
>
>
> Thanks,
> Matt
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
--
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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build branches/maven-2.0.x - SUCCESS - update] Wed Dec 21 04:34:56 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20051221.043456.tar.gz Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051221.043456.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build branches/maven-2.0.x - FAILED - update] Wed Dec 21 04:24:42 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051221.042442.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build branches/maven-2.0.x - FAILED - checkout] Wed Dec 21 04:15:09 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20051221.041509.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build trunk - SUCCESS - update] Wed Dec 21 04:03:46 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/trunk/m2-20051221.040346.tar.gz Log: http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20051221.040346.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build trunk - FAILED - checkout] Wed Dec 21 03:47:25 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20051221.034725.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MSUREFIRE-34) surefire-report-plugin 2.1 is having Failure to parse Surefire 1.5 xml file
surefire-report-plugin 2.1 is having Failure to parse Surefire 1.5 xml file Key: MSUREFIRE-34 URL: http://jira.codehaus.org/browse/MSUREFIRE-34 Project: Maven 2.x Surefire Plugin Type: Bug Environment: surefire 1.5 default plugin that bundled with maven 2 release. surefire-report verson 2.0-beta-2-SNAPSHOT that I checkout from mojo svn Reporter: Leung Man-Chi Assigned to: Jason van Zyl I used surefire-report plugin to parse surefire generated xml file but encountered the following exception. I checked out surefire-report jira, and got a reply that it is due to the invalid xml format in surefire generated TEST- com.mycompany.app.AppTest.xml file. I tried the following attempt: - since surefire-plugin that bundles with m2 release is version 1.5, in fact, I tried to checkout the latest 2.1 from http://svn.apache.org/repos/asf/maven/components/tags/maven-surefire-plugin-2.1. I did a mvn compile and install to my local .m2 repository, trying to run it again. However, M2 , by default only depends surefire 1.5 version, NOT running ver 2.1 . may I know how to make m2 to run surefire 2.1 instead? pls help --- ERROR MSG: --- [INFO] Generate "Maven Surefire Report" report. java.lang.Exception: Failure to parse file at: ~/myproject/my-app/target/surefire-reports/TEST-com.mycompany.app.AppTest.xml at org.codehaus.mojo.surefire.ReportTestSuite.(ReportTestSuite.java:68) at org.codehaus.mojo.surefire.SurefireReportParser.parseXMLReportFiles(SurefireReportParser.java:49) at org.codehaus.mojo.surefire.SurefireReportGenerator.doGenerateReport(SurefireReportGenerator.java:44) at org.codehaus.mojo.surefire.SurefireReportMojo.executeReport(SurefireReportMojo.java:77) at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:98) at org.apache.maven.plugins.site.SiteMojo.generateReportsPages(SiteMojo.java:802) at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:301) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:432) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:530) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:472) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:451) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:303) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:270) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:139) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.xml.sax.SAXParseException: Whitespace required before attributes. at org.apache.crimson.parser.Parser2.fatal(Parser2.java:3376) at org.apache.crimson.parser.Parser2.fatal(Parser2.java:3364) at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1556) at org.apache.crimson.parser.Parser2.content(Parser2.java:1963) at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1691) at org.apache.crimson.parser.Parser2.content(Parser2.java:1963) at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1691) at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:667) at org.apache.crimson.parser.Parser2.parse(Parser2.java:337) at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:448) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at javax.xml.parsers.SAXParser.parse(SAXParser.java:281) at org.codehaus.mojo.surefire.ReportTestSuite.(ReportTestSuite.java:64) ... 24 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly co
[jira] Created: (MECLIPSE-49) Existing settings in org.eclipse.jdt.core.prefs are overwritten
Existing settings in org.eclipse.jdt.core.prefs are overwritten --- Key: MECLIPSE-49 URL: http://jira.codehaus.org/browse/MECLIPSE-49 Project: Maven 2.x Eclipse Plugin Type: Bug Reporter: Dirk Olmes Assigned to: Jason van Zyl Attachments: EclipseSettingsWriter.patch If the file org.eclipse.jdt.core.prefs exists and does not match the properties that are to be generated, the file is silently overwritten. When project specific compiler settings are enabled for a project, these settings will also be stored in the file org.eclipse.jdt.core.prefs. When re-generating the eclipse project all the settings will be overwritten. I've attached a patch that merges the existing settings with the generated ones. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MSITE-29) Imposible to generated UTF-8 site with APT
[ http://jira.codehaus.org/browse/MSITE-29?page=all ] Brett Porter updated MSITE-29: -- Fix Version: 2.0 > Imposible to generated UTF-8 site with APT > -- > > Key: MSITE-29 > URL: http://jira.codehaus.org/browse/MSITE-29 > Project: Maven 2.x Site Plugin > Type: Bug > Environment: Linux 2.6.10, JDK 1.5, Maven 2.0-alpha-3 > Reporter: Jean-Charles Giardina > Priority: Minor > Fix For: 2.0 > > > Maven plugin's site cannot generated HTML files from APT files using charset > UTF-8 rather than ISO-8859-1. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MSITE-23) problems with site:stage
[ http://jira.codehaus.org/browse/MSITE-23?page=all ] Brett Porter updated MSITE-23: -- Fix Version: 2.0 > problems with site:stage > > > Key: MSITE-23 > URL: http://jira.codehaus.org/browse/MSITE-23 > Project: Maven 2.x Site Plugin > Type: Bug > Reporter: John Allen > Fix For: 2.0 > > > The patches contributed by myself and Vincent are faulty due to the > assumption that project.getParent() returns an interpolated project which is > not the case. > Additionally the only way I know to get 'cooked' (interpolated) projects is > via reactor environment but this breaks the perfectly valid requirement of > being able to generate a site and its links to parent and child projects on > its own (i.e. not in a reactor build) > There's also a bug in patches that causes invalid paths to be generated in > site:stage mojo under win32 where a ':' is left hanging in the middle fo the > newly generated project URLs. i.e. D:\Foo ends up in the middle of patch. > I have a few made comments on confluence regarding the wider problems re > addressing related projects and the need for a cooked project model when not > in a reactor environment: > http://docs.codehaus.org/display/MAVEN/Sites+and+Inheritence -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MSITE-51) add breadcrumbs
[ http://jira.codehaus.org/browse/MSITE-51?page=all ] Brett Porter updated MSITE-51: -- Fix Version: 2.0 > add breadcrumbs > --- > > Key: MSITE-51 > URL: http://jira.codehaus.org/browse/MSITE-51 > Project: Maven 2.x Site Plugin > Type: Bug > Reporter: Brett Porter > Fix For: 2.0 > > > not sure if this was a popular feature, so not for 2.0 > would be best integrated with aggregation, descriptor inheritence and the > reactor -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MSITE-19) Various encoding problems with InputStream and XML
[ http://jira.codehaus.org/browse/MSITE-19?page=all ] Brett Porter updated MSITE-19: -- Fix Version: 2.0 > Various encoding problems with InputStream and XML > -- > > Key: MSITE-19 > URL: http://jira.codehaus.org/browse/MSITE-19 > Project: Maven 2.x Site Plugin > Type: Bug > Reporter: Naoki Nose > Fix For: 2.0 > Attachments: plexus-i18n.diff, plexus-site-renderer.diff, plexus-utils.diff, > plexus-utils_2.diff > > > There is various encoding problems with InputStream and XML in different > components. > - Property resource file is encoded with UTF-8 , but Java reads bundle with > UTF-8. > - In different components Reader is constructed with default system encoding. > - MXParser ignores encoding attribute in xml declaration. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MSITE-41) Add a list of available language in site plugin
[ http://jira.codehaus.org/browse/MSITE-41?page=all ] Brett Porter updated MSITE-41: -- Fix Version: 2.0 > Add a list of available language in site plugin > --- > > Key: MSITE-41 > URL: http://jira.codehaus.org/browse/MSITE-41 > Project: Maven 2.x Site Plugin > Type: Bug > Reporter: Vincent Siveton > Fix For: 2.0 > Attachments: language_menu.jpg, language_menu.jpg, language_menu.jpg, > language_menu_as_select.jpg > > > Please see the attached screenshots > This preference menu could be a list of links or a tag. > The site descriptor needs to be updated: > * for , by adding asSelect attribute in the menu element. > * for links list, by adding nostrong attribute in the menu element (to not > display as strong the current language and the current page) -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MSITE-48) add other themes
[ http://jira.codehaus.org/browse/MSITE-48?page=all ] Brett Porter updated MSITE-48: -- Fix Version: 2.0 > add other themes > > > Key: MSITE-48 > URL: http://jira.codehaus.org/browse/MSITE-48 > Project: Maven 2.x Site Plugin > Type: Bug > Reporter: Brett Porter > Fix For: 2.0 > > > add the classic theme from m1, and perhaps a derivative of the new theme for > other sites -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MSITE-3) site adds relative paths to css, etc, but doesn't work for error documents
[ http://jira.codehaus.org/browse/MSITE-3?page=all ] Brett Porter updated MSITE-3: - Fix Version: 2.0 > site adds relative paths to css, etc, but doesn't work for error documents > -- > > Key: MSITE-3 > URL: http://jira.codehaus.org/browse/MSITE-3 > Project: Maven 2.x Site Plugin > Type: Bug > Reporter: Brett Porter > Fix For: 2.0 > > > we should possibly use the absolute urls for these anyway. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MSITE-30) site:deploy incompatibilities with m1.02
[ http://jira.codehaus.org/browse/MSITE-30?page=all ] Brett Porter updated MSITE-30: -- Fix Version: 2.0 > site:deploy incompatibilities with m1.02 > > > Key: MSITE-30 > URL: http://jira.codehaus.org/browse/MSITE-30 > Project: Maven 2.x Site Plugin > Type: Bug > Environment: All > Reporter: Paul Spencer > Fix For: 2.0 > > > Deploying a site in m2 has changed since m1. > 1) m1 used the "tar" and "gunzip" command on the remote site, where m2 uses > the "unzip" command. This poses a problem for be since my remote site does > not support the "unzip" command, thus making the "priority" of this issue > major > 1.1) Their may be desire to deploy without the use of tools like tar and zip > on some site. The deploy would esentailly be a recersive copy > 2) No equivelent to m1 property maven.site.chmod.mode. I use this to allow > other member is the group update and delete permission > 3) No equivelent to m1 property maven.site.publish.clean > Their are other properties for the m1.02 not mentioned above, but I suspect > the they can be calculated from m2 files, i.e. pom.xml and settings.xml. > Paul Spencer -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MSITE-25) mvn site:site ignores server configuration in settings.xml
[ http://jira.codehaus.org/browse/MSITE-25?page=all ] Brett Porter updated MSITE-25: -- Fix Version: 2.0 > mvn site:site ignores server configuration in settings.xml > -- > > Key: MSITE-25 > URL: http://jira.codehaus.org/browse/MSITE-25 > Project: Maven 2.x Site Plugin > Type: Bug > Reporter: Alan Cabrera > Priority: Critical > Fix For: 2.0 > > > mvn site:site ignores parts of my settings.xml: > > livetribe-website > 664 > 775 > > plink > pscp > > livetribe > > It uses the username when ssh but does not invoke plink. > [INFO] [site:deploy] > Using private key: C:\Documents and Settings\adc\.ssh\id_dsa > scpexe://repo.livetribe.org/home/projects/livetribe/public_html/maven/ - > Session: Opened > Executing command: ssh -i "C:\Documents and Settings\adc\.ssh\id_dsa" -o > "BatchMode yes" [EMAIL PROTECTED] "mkdir -p > /home/projects/livetribe/public_html/maven/." > scpexe://repo.livetribe.org/home/projects/livetribe/public_html/maven/ - > Session: Disconnecting > scpexe://repo.livetribe.org/home/projects/livetribe/public_html/maven/ - > Session: Disconnected -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MSITE-58) Ability to assign a report to choosen navigation menu
[ http://jira.codehaus.org/browse/MSITE-58?page=all ] Brett Porter updated MSITE-58: -- Fix Version: 2.0 > Ability to assign a report to choosen navigation menu > -- > > Key: MSITE-58 > URL: http://jira.codehaus.org/browse/MSITE-58 > Project: Maven 2.x Site Plugin > Type: Bug > Reporter: Michal Maczka > Priority: Minor > Fix For: 2.0 > > > It will be nice to have a possibiliy of deciding per report basis where (in > which menu) given report will appear in the left side navigation instead of > putting all reports into one bag (reports menu). -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MSITE-40) don't generate doc file if it is unchanged
[ http://jira.codehaus.org/browse/MSITE-40?page=all ] Brett Porter updated MSITE-40: -- Fix Version: 2.0 > don't generate doc file if it is unchanged > -- > > Key: MSITE-40 > URL: http://jira.codehaus.org/browse/MSITE-40 > Project: Maven 2.x Site Plugin > Type: Bug > Reporter: Brett Porter > Fix For: 2.0 > > > this would help make rsync more effecient not to mention faster site gen -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MSITE-24) Site deployment doesn't allow users in the group to write files
[ http://jira.codehaus.org/browse/MSITE-24?page=all ] Brett Porter updated MSITE-24: -- Fix Version: 2.0 > Site deployment doesn't allow users in the group to write files > --- > > Key: MSITE-24 > URL: http://jira.codehaus.org/browse/MSITE-24 > Project: Maven 2.x Site Plugin > Type: Bug > Reporter: Arnaud Heritier > Priority: Minor > Fix For: 2.0 > > > When Brett deployed maven 2.0 site, some files (new files I think) had the > mode rwxr-xr-x -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MSITE-44) make site reactor aware
[ http://jira.codehaus.org/browse/MSITE-44?page=all ] Brett Porter updated MSITE-44: -- Fix Version: 2.0 Remaining Estimate: 8 hours Original Estimate: 8 hours http://docs.codehaus.org/display/MAVEN/Sites+and+Inheritence > make site reactor aware > --- > > Key: MSITE-44 > URL: http://jira.codehaus.org/browse/MSITE-44 > Project: Maven 2.x Site Plugin > Type: Bug > Reporter: Brett Porter > Assignee: Brett Porter > Priority: Blocker > Fix For: 2.0 > > Original Estimate: 8 hours > Remaining: 8 hours > > there are a few things I'd like to do to make the sites more workable: > - it's good they can still build independantly > - however, if built from the parent, it would be good to go into aggregation > mode and pull in those separately built sites, do any dashboards and deploy > together > - some reports would aggregate themselves, as well as participate in the > dashboards (eg javadoc) > - I'd like the navigation to behave hierachically (sections of the parent > navigation marked as inherited remain on the child sites) > - this means that when building from independant projects they'd need to be > able to locate the parent site descriptor. This could be tricky without a USD > - should it fail if it is not a USD, or should the site descriptor be > published/referenced externally somehow? -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MSITE-32) Confluence sink Support
[ http://jira.codehaus.org/browse/MSITE-32?page=all ] Brett Porter updated MSITE-32: -- Summary: Confluence sink Support (was: Confluence Support) we already have a parser - this is for a sink > Confluence sink Support > --- > > Key: MSITE-32 > URL: http://jira.codehaus.org/browse/MSITE-32 > Project: Maven 2.x Site Plugin > Type: Bug > Reporter: Thomas Van de Velde > > > I'd like to suggest to add support for generating Confluence-compatible wiki > markup from Maven xdocs. A specific deployment plugin could then call a > Confluence Web Service to add the generated pages to a section in the wiki. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
m2 plugin classpath
Hi all I have an m2 plugin that neets to run using classes compiled from the project. I have added for this @execute phase=compile so the project gets compiled first, but I can't find a way to add the project classpath to the running plugin classpath, I have considered creating an new jvm or creating a classloader, but I think this 2 options are horrible, there must be a better way. I'd really appreciate any feedback on this, thanks -- Miguel Griffa Skype: miguel.griffa Y!: m_griffa MSN: [EMAIL PROTECTED] Cell: 54-911-62519355
[continuum build - FAILED - update] Wed Dec 21 00:00:00 GMT 2005
Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051221.00.txt
[jira] Commented: (MNG-1505) Create an abstract source generation mojo
[ http://jira.codehaus.org/browse/MNG-1505?page=comments#action_53887 ] Chad Brandon commented on MNG-1505: --- The only problem is that parameter is readOnly, so it can't be set from a plugin configuration. > Create an abstract source generation mojo > - > > Key: MNG-1505 > URL: http://jira.codehaus.org/browse/MNG-1505 > Project: Maven 2 > Type: New Feature > Components: Plugin Requests > Reporter: Jason van Zyl > > > There are many source generation mojos and a common base can't hurt. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-1505) Create an abstract source generation mojo
[ http://jira.codehaus.org/browse/MNG-1505?page=comments#action_53885 ] Cédric Vidal commented on MNG-1505: --- I might be wrong but isn't maven-compile-plugin's compileSourceRoots parameter what you're looking for Chad ? http://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html > Create an abstract source generation mojo > - > > Key: MNG-1505 > URL: http://jira.codehaus.org/browse/MNG-1505 > Project: Maven 2 > Type: New Feature > Components: Plugin Requests > Reporter: Jason van Zyl > > > There are many source generation mojos and a common base can't hurt. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MEV-266) Maven2 ActiveMQ Poms do not work
[ http://jira.codehaus.org/browse/MEV-266?page=all ] Carlos Sanchez closed MEV-266: -- Assign To: Carlos Sanchez Resolution: Incomplete Some versions have been fixed, see MEV-193 Patches are welcome > Maven2 ActiveMQ Poms do not work > > > Key: MEV-266 > URL: http://jira.codehaus.org/browse/MEV-266 > Project: Maven Evangelism > Type: Bug > Reporter: Tim Dysinger > Assignee: Carlos Sanchez > > > Active MQ POMS have variables in them instead of concrete version numbers. > If your project depends on ActiveMQ, forget about using maven2. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MPASPECTJ-21) Support AspectJ 5
[ http://jira.codehaus.org/browse/MPASPECTJ-21?page=all ] Carlos Sanchez closed MPASPECTJ-21: --- Assign To: Carlos Sanchez Resolution: Fixed > Support AspectJ 5 > - > > Key: MPASPECTJ-21 > URL: http://jira.codehaus.org/browse/MPASPECTJ-21 > Project: maven-aspectj-plugin > Type: Improvement > Reporter: Carlos Sanchez > Assignee: Carlos Sanchez > Fix For: 4.0 > > -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MAVEN-1345) Upgrade to dom4j 1.4
[ http://jira.codehaus.org/browse/MAVEN-1345?page=comments#action_53878 ] Brett Porter commented on MAVEN-1345: - If its the Aelfred2 parser, we don't use it. We can surgically remove it from the JAR. The dom4j project should also ask us to retract or update the releases from ibiblio. > Upgrade to dom4j 1.4 > > > Key: MAVEN-1345 > URL: http://jira.codehaus.org/browse/MAVEN-1345 > Project: Maven > Type: Bug > Components: core > Versions: 1.0-rc3 > Reporter: Paul Libbrecht > Assignee: Brett Porter > Priority: Critical > Fix For: 1.1-beta-3 > > > Currently, Maven relies on dom4j beta 8. > This is bad in many respects, the worst being that the XML output, for > example provided by Jelly XML plugin, has wrong xmlns attributes. > At least the 1.5 betas of dom4j all fix this, they also fix the html output > which was, otherwise, inserting random (kind-of) spaces in the text. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MAVEN-1345) Upgrade to dom4j 1.4
[ http://jira.codehaus.org/browse/MAVEN-1345?page=comments#action_53877 ] Lukas Theussl commented on MAVEN-1345: -- I suppose it is the use of the Aelfred2 parser that was removed in the 1.5.2 release (http://www.dom4j.org/changes-report.html#1_5_2). But I have to agree with Brett, this is a complete blocker for us if CDATA sections are being swallowed. If we can't use it for licensing issues, what alternatives would we have? > Upgrade to dom4j 1.4 > > > Key: MAVEN-1345 > URL: http://jira.codehaus.org/browse/MAVEN-1345 > Project: Maven > Type: Bug > Components: core > Versions: 1.0-rc3 > Reporter: Paul Libbrecht > Assignee: Brett Porter > Priority: Critical > Fix For: 1.1-beta-3 > > > Currently, Maven relies on dom4j beta 8. > This is bad in many respects, the worst being that the XML output, for > example provided by Jelly XML plugin, has wrong xmlns attributes. > At least the 1.5 betas of dom4j all fix this, they also fix the html output > which was, otherwise, inserting random (kind-of) spaces in the text. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problems with JIRA Plug-in Projects
1) the versions would be irrelevant anyway. I'm happy for old issues to have no version, and create the upcoming version in each project to use properly from now on 2) we rarely use this. Let's just change it on a needs basis - Brett Jason van Zyl wrote: > Hi, > > There are a few issues with the movement of the issues. So I'll list > them and then we need to decide what to do: > > 1) I selected the retain option which I assumed would create the > versions in new projects, but the affects/fix version information > appears to have been lost. > > 2) I thought I selected the option I thought would map > Bug/Improvement/etc into their equivalents in the new projects but it > appears that all the types went in as Bugs. > > These are the bigs ones. > > So versions need to be recreated and the workflow needs to be set as > Vincent made a special workflow for us. These I can automate. > > I think if we identify the leads then each of the plugin projects can > be cleaned up quickly and if users take a peek at issues they raised > it probably won't take long. But we can always restore a backup too. I > would prefer not to do that. I think we can clean up the issues in the > plug-in projects relatively quickly. > > Any thoughts? > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Maven Wiki] Update of "JavadocPlugin" by AlexanderHars
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Maven Wiki" for change notification. The following page has been changed by AlexanderHars: http://wiki.apache.org/maven/JavadocPlugin New page: == Tips and Suprises == * tag: Use plain text. Html-mark up or links are not possible. They lead to an error. * tag: currently does not work (2006-Dec-20). See: http://jira.codehaus.org/browse/MJAVADOC-21 * tag: Can usually be left at the default setting. If you are unsure about which doclet is used, you can use this tag to specify the path to the jre/lib/tools.jar file of your preferred JDK. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MAVEN-1345) Upgrade to dom4j 1.4
[ http://jira.codehaus.org/browse/MAVEN-1345?page=all ] Brett Porter updated MAVEN-1345: Fix Version: (was: 1.1-beta-1) 1.1-beta-3 > Upgrade to dom4j 1.4 > > > Key: MAVEN-1345 > URL: http://jira.codehaus.org/browse/MAVEN-1345 > Project: Maven > Type: Bug > Components: core > Versions: 1.0-rc3 > Reporter: Paul Libbrecht > Assignee: Brett Porter > Priority: Critical > Fix For: 1.1-beta-3 > > > Currently, Maven relies on dom4j beta 8. > This is bad in many respects, the worst being that the XML output, for > example provided by Jelly XML plugin, has wrong xmlns attributes. > At least the 1.5 betas of dom4j all fix this, they also fix the html output > which was, otherwise, inserting random (kind-of) spaces in the text. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Reopened: (MAVEN-1345) Upgrade to dom4j 1.4
[ http://jira.codehaus.org/browse/MAVEN-1345?page=all ] Brett Porter reopened MAVEN-1345: - Elliotte - can you please elaborate on what the issues are. We can't use dom4j 1.5.2 because it is not backwards compatible and I was unable to get it to work with Jelly. > Upgrade to dom4j 1.4 > > > Key: MAVEN-1345 > URL: http://jira.codehaus.org/browse/MAVEN-1345 > Project: Maven > Type: Bug > Components: core > Versions: 1.0-rc3 > Reporter: Paul Libbrecht > Assignee: Brett Porter > Priority: Critical > Fix For: 1.1-beta-3 > > > Currently, Maven relies on dom4j beta 8. > This is bad in many respects, the worst being that the XML output, for > example provided by Jelly XML plugin, has wrong xmlns attributes. > At least the 1.5 betas of dom4j all fix this, they also fix the html output > which was, otherwise, inserting random (kind-of) spaces in the text. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MPA-34) Process Mike Perham
[ http://jira.codehaus.org/browse/MPA-34?page=all ] Jason van Zyl closed MPA-34: Resolution: Fixed Karma has been granted. Mike should be all setup. > Process Mike Perham > --- > > Key: MPA-34 > URL: http://jira.codehaus.org/browse/MPA-34 > Project: Maven Project Administration > Type: Task > Components: new-commiters > Reporter: Emmanuel Venisse > Assignee: Jason van Zyl > > > Preferred userid: mperham > Full name: Mike Perham > Forwarding email address: [EMAIL PROTECTED] > Requested UNIX groups: maven > Vote thread: > http://mail-archives.apache.org/mod_mbox/maven-scm-dev/200512.mbox/[EMAIL > PROTECTED] -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MCOMPILER-22) Compilation fails: "The command line is too long."
Compilation fails: "The command line is too long." -- Key: MCOMPILER-22 URL: http://jira.codehaus.org/browse/MCOMPILER-22 Project: Maven 2.x Compiler Plugin Type: Bug Reporter: Matthew Beermann Assigned to: Jason van Zyl Priority: Critical For one of my project, compilation fails with the message "The command line is too long". As far as I can tell, it's listing each and every source file, one at a time, in the -sourcepath attribute. (?!?) Here's the log: [DEBUG] Source roots: [DEBUG] C:\continuum-1.0.2\apps\continuum\working-directory\26\src [DEBUG] Command line options: [DEBUG] -d C:\continuum-1.0.2\apps\continuum\working-directory\26\target\classes -classpath -sourcepath -g -nowarn -target 1.4 -source 1.4 Compiling 167 source files to C:\continuum-1.0.2\apps\continuum\working-directory\26\target\classes [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Compilation failure Failure executing javac, but could not parse the error: The command line is too long. [INFO] [DEBUG] Trace org.apache.maven.BuildFailureException: Compilation failure at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:551) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:472) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:451) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:303) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:270) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:139) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation failure at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:429) at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:110) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:432) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:530) ... 16 more -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPA-34) Process Mike Perham
[ http://jira.codehaus.org/browse/MPA-34?page=comments#action_53867 ] Emmanuel Venisse commented on MPA-34: - account is created. Need to grant karma to maven-scm and maven plugins > Process Mike Perham > --- > > Key: MPA-34 > URL: http://jira.codehaus.org/browse/MPA-34 > Project: Maven Project Administration > Type: Task > Components: new-commiters > Reporter: Emmanuel Venisse > Assignee: Jason van Zyl > > > Preferred userid: mperham > Full name: Mike Perham > Forwarding email address: [EMAIL PROTECTED] > Requested UNIX groups: maven > Vote thread: > http://mail-archives.apache.org/mod_mbox/maven-scm-dev/200512.mbox/[EMAIL > PROTECTED] -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-1882) activeByDefault is ignored in pom.xml
activeByDefault is ignored in pom.xml - Key: MNG-1882 URL: http://jira.codehaus.org/browse/MNG-1882 Project: Maven 2 Type: Bug Components: POM Versions: 2.0.1 Reporter: Cédric Vidal The activation of a profile by the activeByDefault element in pom.xml is ignored. The profile does not get active automatically. As workaround it can be activated with: 1 -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-1881) maven-clean-plugin doesn't remove the reporting output directory ${project.reporting.outputDirectory}
[ http://jira.codehaus.org/browse/MNG-1881?page=all ]
mark struberg updated MNG-1881:
---
Attachment: MNG-1881-maven-clean-plugin.diff
> maven-clean-plugin doesn't remove the reporting output directory
> ${project.reporting.outputDirectory}
> -
>
> Key: MNG-1881
> URL: http://jira.codehaus.org/browse/MNG-1881
> Project: Maven 2
> Type: Improvement
> Components: Plugins and Lifecycle
> Versions: 2.0.1
> Environment: Linux FC4, sun jdk1.5
> Reporter: mark struberg
> Priority: Minor
> Attachments: MNG-1881-maven-clean-plugin.diff
>
>
> DESCRIPTION:
> The maven-clean-plugin does only remove the directories given in the
> section of the POM.
> Directories created by the other standard lifecycle sections like the
> section of the POM will not be removed by the clean mojo.
> I see 2 ways to fix this issue:
> 1.) (which 1 prefere) Provide all clean actions for the other standard
> lifecyles too inside the maven-clean-plugin
> 2.) Add new mojos with the @goal clean to the corresponding maven-plugins,
> like ie the maven-site-plugin
> TESTCASE (pom.xml):
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
> 4.0.0
> at.struct.mvntest
> mvntest
> jar
> 1.0-SNAPSHOT
> MSX Maven Test App
>
> msxtarget
> msxtarget/classes
>
>
> msxreports
>
>
> PATCH:
> Added
> removeDirectory( reportingOutputDirectory );
> to CleanMojo.java
> Maybe there are also other directories to be removed in the same way
--
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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-1881) maven-clean-plugin doesn't remove the reporting output directory ${project.reporting.outputDirectory}
maven-clean-plugin doesn't remove the reporting output directory
${project.reporting.outputDirectory}
-
Key: MNG-1881
URL: http://jira.codehaus.org/browse/MNG-1881
Project: Maven 2
Type: Improvement
Components: Plugins and Lifecycle
Versions: 2.0.1
Environment: Linux FC4, sun jdk1.5
Reporter: mark struberg
Priority: Minor
DESCRIPTION:
The maven-clean-plugin does only remove the directories given in the
section of the POM.
Directories created by the other standard lifecycle sections like the
section of the POM will not be removed by the clean mojo.
I see 2 ways to fix this issue:
1.) (which 1 prefere) Provide all clean actions for the other standard
lifecyles too inside the maven-clean-plugin
2.) Add new mojos with the @goal clean to the corresponding maven-plugins, like
ie the maven-site-plugin
TESTCASE (pom.xml):
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
4.0.0
at.struct.mvntest
mvntest
jar
1.0-SNAPSHOT
MSX Maven Test App
msxtarget
msxtarget/classes
msxreports
PATCH:
Added
removeDirectory( reportingOutputDirectory );
to CleanMojo.java
Maybe there are also other directories to be removed in the same way
--
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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MASSEMBLY-17) Unable to map a file in FileSet to another file name
[ http://jira.codehaus.org/browse/MASSEMBLY-17?page=all ]
Dan Tran closed MASSEMBLY-17:
-
Resolution: Fixed
new source checked in to svn
> Unable to map a file in FileSet to another file name
>
>
> Key: MASSEMBLY-17
> URL: http://jira.codehaus.org/browse/MASSEMBLY-17
> Project: Maven 2.x Assembly Plugin
> Type: Bug
> Environment: xp
> Reporter: Dan Tran
> Assignee: Dan Tran
>
>
> Currently it is not possible to copy ${frompath}/file1 to ${toPath}/file2
> using Assembly FileSet
> However the dependencySet does support this feature
--
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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problems with JIRA Plug-in Projects
Stephane Nicoll wrote: EAR plugin is done, sorry for the noise. No problem, thanks for the help. I'll tackle the ones with more issues as I created the problem :-) Thanks again. On 12/20/05, Jason van Zyl <[EMAIL PROTECTED]> wrote: Vincent Massol wrote: I'm working on restoring the clover plugin as I write. I think we can fix things by hands rather than do a dangerous restore (we won't know how many new issues were added after the last backup point). Cool, thanks. Stephane is fixing the EAR and RAR plugins. Shall I make versions within the plugin projects or do the leads want to do this on a plugin project basis? Thanks -Vincent In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society - 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] -- jvz. Jason van Zyl jason at maven.org http://maven.apache.org you are never dedicated to something you have complete confidence in. No one is fanatically shouting that the sun is going to rise tomorrow. They know it is going to rise tomorrow. When people are fanatically dedicated to political or religious faiths or any other kind of dogmas or goals, it's always because these dogmas or goals are in doubt. -- Robert Pirzig, Zen and the Art of Motorcycle Maintenance - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- .::You're welcome ::. -- jvz. Jason van Zyl jason at maven.org http://maven.apache.org Our achievements speak for themselves. What we have to keep track of are our failures, discouragements and doubts. We tend to forget the past difficulties, the many false starts, and the painful groping. We see our past achievements as the end result of a clean forward thrust, and our present difficulties as signs of decline and decay. -- Eric Hoffer, Reflections on the Human Condition - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problems with JIRA Plug-in Projects
RAR as well, same remark ;-) On 12/20/05, Stephane Nicoll <[EMAIL PROTECTED]> wrote: > > EAR plugin is done, sorry for the noise. > > On 12/20/05, Jason van Zyl <[EMAIL PROTECTED]> wrote: > > > > Vincent Massol wrote: > > > > > I'm working on restoring the clover plugin as I write. > > > > > > I think we can fix things by hands rather than do a dangerous restore > > (we > > > won't know how many new issues were added after the last backup > > point). > > > > Cool, thanks. Stephane is fixing the EAR and RAR plugins. > > > > Shall I make versions within the plugin projects or do the leads want to > > do this on a plugin project basis? > > > > > Thanks > > > -Vincent > > > > > > > > >>In short, man creates for himself a new religion of a rational > > >>and technical order to justify his work and to be justified in it. > > >> > > >> -- Jacques Ellul, The Technological Society > > >> > > >>- > > >>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] > > > > > > > > > > > > > > > -- > > > > jvz. > > > > Jason van Zyl > > jason at maven.org > > http://maven.apache.org > > > > you are never dedicated to something you have complete confidence in. > > No one is fanatically shouting that the sun is going to rise tomorrow. > > They know it is going to rise tomorrow. When people are fanatically > > dedicated to political or religious faiths or any other kind of > > dogmas or goals, it's always because these dogmas or > > goals are in doubt. > > > >-- Robert Pirzig, Zen and the Art of Motorcycle Maintenance > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > .::You're welcome ::. -- .::You're welcome ::.
[jira] Closed: (MRAR-1) Plugin can not install the generated rar file to the local repository
[ http://jira.codehaus.org/browse/MRAR-1?page=all ] Stephane Nicoll closed MRAR-1: -- Resolution: Fixed > Plugin can not install the generated rar file to the local repository > - > > Key: MRAR-1 > URL: http://jira.codehaus.org/browse/MRAR-1 > Project: Maven 2.x Rar Plugin > Type: Bug > Environment: Win XP SP2, JDK 5, M2 2.0.1-SNAPSHOT > Reporter: Henry S. Isidro > Assignee: Edwin Punzalan > Fix For: 2.1 > Attachments: maven-rar-plugin.diff > > > The build stops and generates an Access Denied error because it cannot > install the correct file to the local repository. Looking at the console > output, these lines are present: > [INFO] [install:install] > [INFO] Installing C:\myrar-project\target\classes to C:\Documents and > Settings\user1\.m2\repository\myrar-project\myrar-project\1.0-SNAPSHOT\myrar-project-1.0-SNAPSHOT.rar > So it seems that the plugin is trying to copy the target\classes to the local > repository and renaming it as the rar file. I've attached a DIFF file with > some changes that I think will make the plugin work. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRAR-1) Plugin can not install the generated rar file to the local repository
[ http://jira.codehaus.org/browse/MRAR-1?page=all ] Stephane Nicoll updated MRAR-1: --- Fix Version: 2.1 Summary: Plugin can not install the generated rar file to the local repository (was: maven-rar-plugin can not install the generated rar file to the local repository) > Plugin can not install the generated rar file to the local repository > - > > Key: MRAR-1 > URL: http://jira.codehaus.org/browse/MRAR-1 > Project: Maven 2.x Rar Plugin > Type: Bug > Environment: Win XP SP2, JDK 5, M2 2.0.1-SNAPSHOT > Reporter: Henry S. Isidro > Assignee: Edwin Punzalan > Fix For: 2.1 > Attachments: maven-rar-plugin.diff > > > The build stops and generates an Access Denied error because it cannot > install the correct file to the local repository. Looking at the console > output, these lines are present: > [INFO] [install:install] > [INFO] Installing C:\myrar-project\target\classes to C:\Documents and > Settings\user1\.m2\repository\myrar-project\myrar-project\1.0-SNAPSHOT\myrar-project-1.0-SNAPSHOT.rar > So it seems that the plugin is trying to copy the target\classes to the local > repository and renaming it as the rar file. I've attached a DIFF file with > some changes that I think will make the plugin work. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Reopened: (MRAR-1) maven-rar-plugin can not install the generated rar file to the local repository
[ http://jira.codehaus.org/browse/MRAR-1?page=all ] Stephane Nicoll reopened MRAR-1: > maven-rar-plugin can not install the generated rar file to the local > repository > --- > > Key: MRAR-1 > URL: http://jira.codehaus.org/browse/MRAR-1 > Project: Maven 2.x Rar Plugin > Type: Bug > Environment: Win XP SP2, JDK 5, M2 2.0.1-SNAPSHOT > Reporter: Henry S. Isidro > Assignee: Edwin Punzalan > Attachments: maven-rar-plugin.diff > > > The build stops and generates an Access Denied error because it cannot > install the correct file to the local repository. Looking at the console > output, these lines are present: > [INFO] [install:install] > [INFO] Installing C:\myrar-project\target\classes to C:\Documents and > Settings\user1\.m2\repository\myrar-project\myrar-project\1.0-SNAPSHOT\myrar-project-1.0-SNAPSHOT.rar > So it seems that the plugin is trying to copy the target\classes to the local > repository and renaming it as the rar file. I've attached a DIFF file with > some changes that I think will make the plugin work. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MRAR-2) Packaging does not check artifacts if they are tagged as optional
[ http://jira.codehaus.org/browse/MRAR-2?page=all ] Stephane Nicoll closed MRAR-2: -- Resolution: Fixed > Packaging does not check artifacts if they are tagged as optional > -- > > Key: MRAR-2 > URL: http://jira.codehaus.org/browse/MRAR-2 > Project: Maven 2.x Rar Plugin > Type: Bug > Reporter: Stephane Nicoll > Assignee: Edwin Punzalan > Fix For: 2.1 > > > This fixes war, ear, and rar. Are there other artifacts that should also > check for the optional tag? -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MRAR-2) Packaging does not check artifacts if they are tagged as optional
[ http://jira.codehaus.org/browse/MRAR-2?page=all ] Stephane Nicoll moved MEAR-16 to MRAR-2: Fix Version: (was: 2.1) 2.1 Key: MRAR-2 (was: MEAR-16) Project: Maven 2.x Rar Plugin (was: Maven 2.x Ear Plugin) > Packaging does not check artifacts if they are tagged as optional > -- > > Key: MRAR-2 > URL: http://jira.codehaus.org/browse/MRAR-2 > Project: Maven 2.x Rar Plugin > Type: Bug > Reporter: Stephane Nicoll > Assignee: Edwin Punzalan > Fix For: 2.1 > > > This fixes war, ear, and rar. Are there other artifacts that should also > check for the optional tag? -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MEAR-16) Packaging does not check artifacts if they are tagged as optional
Packaging does not check artifacts if they are tagged as optional -- Key: MEAR-16 URL: http://jira.codehaus.org/browse/MEAR-16 Project: Maven 2.x Ear Plugin Type: Bug Reporter: Stephane Nicoll Assigned to: Edwin Punzalan Fix For: 2.1 This fixes war, ear, and rar. Are there other artifacts that should also check for the optional tag? -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[continuum build - FAILED - update] Tue Dec 20 18:00:00 GMT 2005
Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051220.18.txt
Re: Problems with JIRA Plug-in Projects
EAR plugin is done, sorry for the noise. On 12/20/05, Jason van Zyl <[EMAIL PROTECTED]> wrote: > > Vincent Massol wrote: > > > I'm working on restoring the clover plugin as I write. > > > > I think we can fix things by hands rather than do a dangerous restore > (we > > won't know how many new issues were added after the last backup point). > > Cool, thanks. Stephane is fixing the EAR and RAR plugins. > > Shall I make versions within the plugin projects or do the leads want to > do this on a plugin project basis? > > > Thanks > > -Vincent > > > > > >>In short, man creates for himself a new religion of a rational > >>and technical order to justify his work and to be justified in it. > >> > >> -- Jacques Ellul, The Technological Society > >> > >>- > >>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] > > > > > > > > > -- > > jvz. > > Jason van Zyl > jason at maven.org > http://maven.apache.org > > you are never dedicated to something you have complete confidence in. > No one is fanatically shouting that the sun is going to rise tomorrow. > They know it is going to rise tomorrow. When people are fanatically > dedicated to political or religious faiths or any other kind of > dogmas or goals, it's always because these dogmas or > goals are in doubt. > >-- Robert Pirzig, Zen and the Art of Motorcycle Maintenance > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- .::You're welcome ::.
Re: Problems with JIRA Plug-in Projects
Vincent Massol wrote: I'm working on restoring the clover plugin as I write. I think we can fix things by hands rather than do a dangerous restore (we won't know how many new issues were added after the last backup point). Cool, thanks. Stephane is fixing the EAR and RAR plugins. Shall I make versions within the plugin projects or do the leads want to do this on a plugin project basis? Thanks -Vincent In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society - 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] -- jvz. Jason van Zyl jason at maven.org http://maven.apache.org you are never dedicated to something you have complete confidence in. No one is fanatically shouting that the sun is going to rise tomorrow. They know it is going to rise tomorrow. When people are fanatically dedicated to political or religious faiths or any other kind of dogmas or goals, it's always because these dogmas or goals are in doubt. -- Robert Pirzig, Zen and the Art of Motorcycle Maintenance - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MASSEMBLY-17) Unable to map a file in FileSet to another file name
[ http://jira.codehaus.org/browse/MASSEMBLY-17?page=comments#action_53858 ]
Dan Tran commented on MASSEMBLY-17:
---
OK, I am going to use Edwin's suggestion since most of code already there in
FileSet handling.
> Unable to map a file in FileSet to another file name
>
>
> Key: MASSEMBLY-17
> URL: http://jira.codehaus.org/browse/MASSEMBLY-17
> Project: Maven 2.x Assembly Plugin
> Type: Bug
> Environment: xp
> Reporter: Dan Tran
> Assignee: Dan Tran
>
>
> Currently it is not possible to copy ${frompath}/file1 to ${toPath}/file2
> using Assembly FileSet
> However the dependencySet does support this feature
--
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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MEAR-3) ear includes and excludes don't handle comma separated tokens
[ http://jira.codehaus.org/browse/MEAR-3?page=all ] Stephane Nicoll updated MEAR-3: --- Version: 2.1 2.0 Fix Version: 2.2 Summary: ear includes and excludes don't handle comma separated tokens (was: war includes and excludes don't handle comma separated tokens (patch included)) > ear includes and excludes don't handle comma separated tokens > - > > Key: MEAR-3 > URL: http://jira.codehaus.org/browse/MEAR-3 > Project: Maven 2.x Ear Plugin > Type: Bug > Versions: 2.1, 2.0 > Reporter: David Hawkins > Assignee: Stephane Nicoll > Fix For: 2.2 > Attachments: MNG-1696-maven-war-plugin.patch > > > The documentation for warSourceIncludes, warSourceExcludes, > dependantWarIncludes, and dependantWarExcludes all state something that they > support comma delimited tokens but it simply doesn't work when a comma is > specified. This patch makes all four parameters properly process comma > delimited values. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Deleted: (MEAR-7) bundleDir
[ http://jira.codehaus.org/browse/MEAR-7?page=all ] Stephane Nicoll deleted MEAR-7: --- > bundleDir > -- > > Key: MEAR-7 > URL: http://jira.codehaus.org/browse/MEAR-7 > Project: Maven 2.x Ear Plugin > Type: Bug > Reporter: Michal Stochmialek > > -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MEAR-1) Plugin configuration doesn't support .ejb3 and .par EJB modules
[ http://jira.codehaus.org/browse/MEAR-1?page=all ] Stephane Nicoll closed MEAR-1: -- Resolution: Fixed Fix Version: 2.1 > Plugin configuration doesn't support .ejb3 and .par EJB modules > --- > > Key: MEAR-1 > URL: http://jira.codehaus.org/browse/MEAR-1 > Project: Maven 2.x Ear Plugin > Type: Bug > Reporter: Tim Kettler > Assignee: Stephane Nicoll > Priority: Minor > Fix For: 2.1 > Attachments: MNG-1723.patch, test-prj.zip > > > When specifying a module configuration for an EJB-Module which is of the type > .ejb3 or .par maven fails with ther following error: > [EMAIL PROTECTED]:~/Develop/test-prj$ mvn -e package > + Error stacktraces are turned on. > [INFO] Scanning for projects... > [INFO] Reactor build order: > [INFO] Unnamed - test:test-project:pom:1.0-SNAPSHOT > [INFO] Unnamed - test:test-ejb:ejb3:1.0-SNAPSHOT > [INFO] Unnamed - test:test-ear:ear:1.0-SNAPSHOT > [INFO] > > [INFO] Building Unnamed - test:test-project:pom:1.0-SNAPSHOT > [INFO]task-segment: [package] > [INFO] > > [INFO] No goals needed for project - skipping > [INFO] > > [INFO] Building Unnamed - test:test-ejb:ejb3:1.0-SNAPSHOT > [INFO]task-segment: [package] > [INFO] > > [INFO] [resources:resources] > [INFO] Using default encoding to copy filtered resources. > [INFO] [compiler:compile] > Compiling 1 source file to /home/tik/Develop/test-prj/test-ejb/target/classes > [INFO] [resources:testResources] > [INFO] Using default encoding to copy filtered resources. > [INFO] [compiler:testCompile] > [INFO] No sources to compile > [INFO] [surefire:test] > [INFO] No tests to run. > [INFO] [ejb3:ejb3] > [INFO] Building jar: > /home/tik/Develop/test-prj/test-ejb/target/test-ejb-1.0-SNAPSHOT.ejb3 > [INFO] > > [INFO] Building Unnamed - test:test-ear:ear:1.0-SNAPSHOT > [INFO]task-segment: [package] > [INFO] > > [INFO] [ear:generate-application-xml] > [INFO] > > [ERROR] BUILD FAILURE > [INFO] > > [INFO] Artifact[test:test-ejb:ejb] is not a dependency of the project. > [INFO] > > [INFO] Trace > org.apache.maven.BuildFailureException: Artifact[test:test-ejb:ejb] is not a > dependency of the project. > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:540) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:469) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:448) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:301) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:268) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:137) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > Caused by: org.apache.maven.plugin.MojoFailureException: > Artifact[test:test-ejb:ejb] is not a dependency of the project. > at > org.apache.maven.plugin.ear.AbstractEarModule.resolveArtifact(AbstractEarModule.java:98) > at > org.apache.maven.plugin.ear.AbstractEarMojo.execute(AbstractEarMojo.java:98) > at > org.apache.maven.plugin.ear.GenerateApplicationXmlMojo.execute(GenerateApplicationXmlMojo.java:96) >
[jira] Reopened: (MEAR-1) Plugin configuration doesn't support .ejb3 and .par EJB modules
[ http://jira.codehaus.org/browse/MEAR-1?page=all ] Stephane Nicoll reopened MEAR-1: > Plugin configuration doesn't support .ejb3 and .par EJB modules > --- > > Key: MEAR-1 > URL: http://jira.codehaus.org/browse/MEAR-1 > Project: Maven 2.x Ear Plugin > Type: Bug > Reporter: Tim Kettler > Assignee: Stephane Nicoll > Priority: Minor > Fix For: 2.1 > Attachments: MNG-1723.patch, test-prj.zip > > > When specifying a module configuration for an EJB-Module which is of the type > .ejb3 or .par maven fails with ther following error: > [EMAIL PROTECTED]:~/Develop/test-prj$ mvn -e package > + Error stacktraces are turned on. > [INFO] Scanning for projects... > [INFO] Reactor build order: > [INFO] Unnamed - test:test-project:pom:1.0-SNAPSHOT > [INFO] Unnamed - test:test-ejb:ejb3:1.0-SNAPSHOT > [INFO] Unnamed - test:test-ear:ear:1.0-SNAPSHOT > [INFO] > > [INFO] Building Unnamed - test:test-project:pom:1.0-SNAPSHOT > [INFO]task-segment: [package] > [INFO] > > [INFO] No goals needed for project - skipping > [INFO] > > [INFO] Building Unnamed - test:test-ejb:ejb3:1.0-SNAPSHOT > [INFO]task-segment: [package] > [INFO] > > [INFO] [resources:resources] > [INFO] Using default encoding to copy filtered resources. > [INFO] [compiler:compile] > Compiling 1 source file to /home/tik/Develop/test-prj/test-ejb/target/classes > [INFO] [resources:testResources] > [INFO] Using default encoding to copy filtered resources. > [INFO] [compiler:testCompile] > [INFO] No sources to compile > [INFO] [surefire:test] > [INFO] No tests to run. > [INFO] [ejb3:ejb3] > [INFO] Building jar: > /home/tik/Develop/test-prj/test-ejb/target/test-ejb-1.0-SNAPSHOT.ejb3 > [INFO] > > [INFO] Building Unnamed - test:test-ear:ear:1.0-SNAPSHOT > [INFO]task-segment: [package] > [INFO] > > [INFO] [ear:generate-application-xml] > [INFO] > > [ERROR] BUILD FAILURE > [INFO] > > [INFO] Artifact[test:test-ejb:ejb] is not a dependency of the project. > [INFO] > > [INFO] Trace > org.apache.maven.BuildFailureException: Artifact[test:test-ejb:ejb] is not a > dependency of the project. > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:540) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:469) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:448) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:301) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:268) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:137) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > Caused by: org.apache.maven.plugin.MojoFailureException: > Artifact[test:test-ejb:ejb] is not a dependency of the project. > at > org.apache.maven.plugin.ear.AbstractEarModule.resolveArtifact(AbstractEarModule.java:98) > at > org.apache.maven.plugin.ear.AbstractEarMojo.execute(AbstractEarMojo.java:98) > at > org.apache.maven.plugin.ear.GenerateApplicationXmlMojo.execute(GenerateApplicationXmlMojo.java:96) > at > org.apache.maven.plugin.Defaul
[jira] Updated: (MEAR-8) Add security role definitions to maven-ear-plugin
[ http://jira.codehaus.org/browse/MEAR-8?page=all ]
Stephane Nicoll updated MEAR-8:
---
Fix Version: 2.2
type: Improvement (was: Bug)
> Add security role definitions to maven-ear-plugin
> -
>
> Key: MEAR-8
> URL: http://jira.codehaus.org/browse/MEAR-8
> Project: Maven 2.x Ear Plugin
> Type: Improvement
> Reporter: Martijn de Bruijn
> Assignee: Stephane Nicoll
> Priority: Minor
> Fix For: 2.2
>
>
> The maven-ear-plugin is not capable of defining security-roles. This should
> be added.
> An example of the pom.xml:
>
> org.apache.maven.plugins
> maven-ear-plugin
>
> ${basedir}/META-INF
>
>
>
> manager
>
>
>
> teller
>
>
>
>
> It should be possible to add the id field to the security-role element to be
> able to link the roles to other generated artifacts.
--
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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Reopened: (MEAR-10) need to set default bundleDir for all ear modules
[ http://jira.codehaus.org/browse/MEAR-10?page=all ] Stephane Nicoll reopened MEAR-10: - > need to set default bundleDir for all ear modules > - > > Key: MEAR-10 > URL: http://jira.codehaus.org/browse/MEAR-10 > Project: Maven 2.x Ear Plugin > Type: Bug > Reporter: Michal Stochmialek > Assignee: Stephane Nicoll > Fix For: 2.1 > > > I need an improvement of bundleDir feature. I would like to specify common > bundleDir for all modules in ear. For example: > > maven-ear-plugin > > src/resources > APP-INF/lib > > > ... > > > ... > > > > > I have ear with single ejb and a bunch of jar archives. I would like them all > placed in APP-INF/lib directory. Using bundleDir tag I must duplicate whole > dependency list (and also transitive dependencies) in ear-plugin > configuration and change bundle dir of each archive. It's very frustrating. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MEAR-2) EAR plugin ignores application XML setting
[ http://jira.codehaus.org/browse/MEAR-2?page=all ]
Stephane Nicoll closed MEAR-2:
--
Resolution: Fixed
Fix Version: 2.1
> EAR plugin ignores application XML setting
> --
>
> Key: MEAR-2
> URL: http://jira.codehaus.org/browse/MEAR-2
> Project: Maven 2.x Ear Plugin
> Type: Bug
> Reporter: mike perham
> Assignee: Stephane Nicoll
> Fix For: 2.1
>
>
> In EarMojo.java:
> /**
> * The location of the application.xml file to be used within the ear
> file.
> *
> * @parameter
> expression="${basedir}/src/main/application/META-INF/application.xml"
> */
> private File applicationXmlFile;
> I set this and Maven still generates an application.xml file anyways.
> Checking the code, this variable is never actually referenced anywhere so it
> appears impossible to use the EAR plugin with a pre-written application.xml.
--
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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MEAR-10) need to set default bundleDir for all ear modules
[ http://jira.codehaus.org/browse/MEAR-10?page=all ] Stephane Nicoll closed MEAR-10: --- Resolution: Fixed Fix Version: 2.1 > need to set default bundleDir for all ear modules > - > > Key: MEAR-10 > URL: http://jira.codehaus.org/browse/MEAR-10 > Project: Maven 2.x Ear Plugin > Type: Bug > Reporter: Michal Stochmialek > Assignee: Stephane Nicoll > Fix For: 2.1 > > > I need an improvement of bundleDir feature. I would like to specify common > bundleDir for all modules in ear. For example: > > maven-ear-plugin > > src/resources > APP-INF/lib > > > ... > > > ... > > > > > I have ear with single ejb and a bunch of jar archives. I would like them all > placed in APP-INF/lib directory. Using bundleDir tag I must duplicate whole > dependency list (and also transitive dependencies) in ear-plugin > configuration and change bundle dir of each archive. It's very frustrating. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPJAVADOC-68) Combined use of online and offline links
[ http://jira.codehaus.org/browse/MPJAVADOC-68?page=comments#action_53857 ] Lukas Theussl commented on MPJAVADOC-68: The source repository is here: http://svn.apache.org/viewcvs.cgi/maven/maven-1/plugins/trunk/javadoc/ please check the main maven site for instructions on how to create a patch: http://maven.apache.org/maven-1.x/contributing/patches.html Anyway, I'll have a look at your patch ASAP, thanks! > Combined use of online and offline links > > > Key: MPJAVADOC-68 > URL: http://jira.codehaus.org/browse/MPJAVADOC-68 > Project: maven-javadoc-plugin > Type: Improvement > Versions: 1.7 > Reporter: Wouter Hermeling > Priority: Minor > Attachments: plugin.jelly, plugin.jelly.patch > > > i want to be able to use both offline and online links. For offline links i > mean 'online links in offline mode'. > The reason is trivial: > 1. I have links to online available apidocs like the javaapi, j2ee api, > jasperrepots api, etc > 2. I also have links to apidocs which are not availble yet. These apidocs > become availble when the whole maven site is being published to a secure site. > For situation 1, i'd like to use online links > For situation 2, i'd like to use online links in offline mode. > I've read the plugin jelly. It seems there's a build in feature to use > offline links even in online mode, but that does not seem to work. > According to the javadoc api itself, it supports both online and offline > links simultaneously. It does not even have a online/offline mode. This is > what the maven-javadoc-plugin should support as well. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Reopened: (MEAR-13) excluding resources in ear archive
[ http://jira.codehaus.org/browse/MEAR-13?page=all ] Stephane Nicoll reopened MEAR-13: - > excluding resources in ear archive > -- > > Key: MEAR-13 > URL: http://jira.codehaus.org/browse/MEAR-13 > Project: Maven 2.x Ear Plugin > Type: Bug > Reporter: Michal Stochmialek > Assignee: Stephane Nicoll > Fix For: 2.1 > > > I'm using resourceDir for including additional resources in ear archive. > Since the project is stored in CVS, directories within resourcesDir contain > 'CVS' directories. I would like to exclude those directories from ear archive. > I believe that the same issue is with earSourceDirectory. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Reopened: (MEAR-2) EAR plugin ignores application XML setting
[ http://jira.codehaus.org/browse/MEAR-2?page=all ]
Stephane Nicoll reopened MEAR-2:
> EAR plugin ignores application XML setting
> --
>
> Key: MEAR-2
> URL: http://jira.codehaus.org/browse/MEAR-2
> Project: Maven 2.x Ear Plugin
> Type: Bug
> Reporter: mike perham
> Assignee: Stephane Nicoll
>
>
> In EarMojo.java:
> /**
> * The location of the application.xml file to be used within the ear
> file.
> *
> * @parameter
> expression="${basedir}/src/main/application/META-INF/application.xml"
> */
> private File applicationXmlFile;
> I set this and Maven still generates an application.xml file anyways.
> Checking the code, this variable is never actually referenced anywhere so it
> appears impossible to use the EAR plugin with a pre-written application.xml.
--
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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MEAR-13) excluding resources in ear archive
[ http://jira.codehaus.org/browse/MEAR-13?page=all ] Stephane Nicoll closed MEAR-13: --- Resolution: Fixed Fix Version: 2.1 > excluding resources in ear archive > -- > > Key: MEAR-13 > URL: http://jira.codehaus.org/browse/MEAR-13 > Project: Maven 2.x Ear Plugin > Type: Bug > Reporter: Michal Stochmialek > Assignee: Stephane Nicoll > Fix For: 2.1 > > > I'm using resourceDir for including additional resources in ear archive. > Since the project is stored in CVS, directories within resourcesDir contain > 'CVS' directories. I would like to exclude those directories from ear archive. > I believe that the same issue is with earSourceDirectory. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MEAR-5) application.xml generated incorrectly
[ http://jira.codehaus.org/browse/MEAR-5?page=all ] Stephane Nicoll closed MEAR-5: -- Resolution: Fixed Fix Version: 2.1 > application.xml generated incorrectly > - > > Key: MEAR-5 > URL: http://jira.codehaus.org/browse/MEAR-5 > Project: Maven 2.x Ear Plugin > Type: Bug > Reporter: Tomislav Stojcevich > Assignee: Stephane Nicoll > Priority: Minor > Fix For: 2.1 > Attachments: MNG-1402-maven-ear-plugin.patch, > MNG-1402-maven-ear-pluginB.patch > > > When generating an application.xml the description is written out before the > display-name. > According to the DTD, display-name needs to be first. See: > http://java.sun.com/dtd/application_1_3.dtd > A work around is to not use a description element in the pom. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Reopened: (MEAR-6) Packaging plugins like war, ear does not check artifacts if they are tagged as optional
[ http://jira.codehaus.org/browse/MEAR-6?page=all ] Stephane Nicoll reopened MEAR-6: > Packaging plugins like war, ear does not check artifacts if they are tagged > as optional > --- > > Key: MEAR-6 > URL: http://jira.codehaus.org/browse/MEAR-6 > Project: Maven 2.x Ear Plugin > Type: Bug > Reporter: Edwin Punzalan > Assignee: Edwin Punzalan > Fix For: 2.1 > Attachments: MNG-1280-maven-ear-plugin.patch, > MNG-1280-maven-rar-plugin.patch, MNG-1280-maven-war-plugin.patch > > > This fixes war, ear, and rar. Are there other artifacts that should also > check for the optional tag? -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Reopened: (MEAR-5) application.xml generated incorrectly
[ http://jira.codehaus.org/browse/MEAR-5?page=all ] Stephane Nicoll reopened MEAR-5: > application.xml generated incorrectly > - > > Key: MEAR-5 > URL: http://jira.codehaus.org/browse/MEAR-5 > Project: Maven 2.x Ear Plugin > Type: Bug > Reporter: Tomislav Stojcevich > Assignee: Stephane Nicoll > Priority: Minor > Fix For: 2.1 > Attachments: MNG-1402-maven-ear-plugin.patch, > MNG-1402-maven-ear-pluginB.patch > > > When generating an application.xml the description is written out before the > display-name. > According to the DTD, display-name needs to be first. See: > http://java.sun.com/dtd/application_1_3.dtd > A work around is to not use a description element in the pom. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MEAR-6) Packaging plugins like war, ear does not check artifacts if they are tagged as optional
[ http://jira.codehaus.org/browse/MEAR-6?page=all ] Stephane Nicoll closed MEAR-6: -- Resolution: Fixed Fix Version: 2.1 > Packaging plugins like war, ear does not check artifacts if they are tagged > as optional > --- > > Key: MEAR-6 > URL: http://jira.codehaus.org/browse/MEAR-6 > Project: Maven 2.x Ear Plugin > Type: Bug > Reporter: Edwin Punzalan > Assignee: Edwin Punzalan > Fix For: 2.1 > Attachments: MNG-1280-maven-ear-plugin.patch, > MNG-1280-maven-rar-plugin.patch, MNG-1280-maven-war-plugin.patch > > > This fixes war, ear, and rar. Are there other artifacts that should also > check for the optional tag? -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MEAR-9) Add support for packaging .par and .ejb3 files in an .ear file
[ http://jira.codehaus.org/browse/MEAR-9?page=all ]
Stephane Nicoll closed MEAR-9:
--
Resolution: Fixed
Fix Version: 2.1
> Add support for packaging .par and .ejb3 files in an .ear file
> --
>
> Key: MEAR-9
> URL: http://jira.codehaus.org/browse/MEAR-9
> Project: Maven 2.x Ear Plugin
> Type: Bug
> Reporter: Adrian
> Assignee: Stephane Nicoll
> Priority: Minor
> Fix For: 2.1
> Attachments: MNG-1264.diff
>
>
> The ear plugin does not support packaging of .ejb3 and .par files into an
> .ear file.
> To fix this a few lines of code need to be added to the
> org.apache.maven.plugin.ear.EarModuleFactory class in the newEarModule method.
> else if ( "ejb3".equals( artifact.getType() ) )
> {
> return new EjbModule( artifact );
> }
> else if ( "par".equals( artifact.getType() ) )
> {
> return new EjbModule( artifact );
> }
> This will allow an application.xml file to be created with .ejb3 and .par
> files, for example
>
>
> entities.par
>
>
>
> business.ejb3
>
>
--
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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Reopened: (MEAR-9) Add support for packaging .par and .ejb3 files in an .ear file
[ http://jira.codehaus.org/browse/MEAR-9?page=all ]
Stephane Nicoll reopened MEAR-9:
> Add support for packaging .par and .ejb3 files in an .ear file
> --
>
> Key: MEAR-9
> URL: http://jira.codehaus.org/browse/MEAR-9
> Project: Maven 2.x Ear Plugin
> Type: Bug
> Reporter: Adrian
> Assignee: Stephane Nicoll
> Priority: Minor
> Fix For: 2.1
> Attachments: MNG-1264.diff
>
>
> The ear plugin does not support packaging of .ejb3 and .par files into an
> .ear file.
> To fix this a few lines of code need to be added to the
> org.apache.maven.plugin.ear.EarModuleFactory class in the newEarModule method.
> else if ( "ejb3".equals( artifact.getType() ) )
> {
> return new EjbModule( artifact );
> }
> else if ( "par".equals( artifact.getType() ) )
> {
> return new EjbModule( artifact );
> }
> This will allow an application.xml file to be created with .ejb3 and .par
> files, for example
>
>
> entities.par
>
>
>
> business.ejb3
>
>
--
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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Reopened: (MEAR-4) Some src/main/resources contents are not included in the package
[ http://jira.codehaus.org/browse/MEAR-4?page=all ] Stephane Nicoll reopened MEAR-4: > Some src/main/resources contents are not included in the package > > > Key: MEAR-4 > URL: http://jira.codehaus.org/browse/MEAR-4 > Project: Maven 2.x Ear Plugin > Type: Bug > Environment: Maven 2, Java 1.4.2_08 > Reporter: John Tolentino > Assignee: Brett Porter > Fix For: 2.0 > > > Some src/main/resources files and folders were excluded in the package (e.g. > other META-INF xmls). Even defining the resource directory in the pom does > not work. Use the standard resources goals instead of > copyDirectoryStructure(). -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MEAR-4) Some src/main/resources contents are not included in the package
[ http://jira.codehaus.org/browse/MEAR-4?page=all ] Stephane Nicoll closed MEAR-4: -- Resolution: Fixed Fix Version: 2.0 > Some src/main/resources contents are not included in the package > > > Key: MEAR-4 > URL: http://jira.codehaus.org/browse/MEAR-4 > Project: Maven 2.x Ear Plugin > Type: Bug > Environment: Maven 2, Java 1.4.2_08 > Reporter: John Tolentino > Assignee: Brett Porter > Fix For: 2.0 > > > Some src/main/resources files and folders were excluded in the package (e.g. > other META-INF xmls). Even defining the resource directory in the pom does > not work. Use the standard resources goals instead of > copyDirectoryStructure(). -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MPXDOC-186) Mailing list links break if the address starts with http
[ http://jira.codehaus.org/browse/MPXDOC-186?page=all ]
Lukas Theussl closed MPXDOC-186:
Resolution: Fixed
Fix Version: 1.10
> Mailing list links break if the address starts with http
>
>
> Key: MPXDOC-186
> URL: http://jira.codehaus.org/browse/MPXDOC-186
> Project: maven-xdoc-plugin
> Type: Bug
> Versions: 1.9.2
> Reporter: Ortwin Glück
> Fix For: 1.10
>
>
> Our mailing lists have email addresses that start with http: e.g. [EMAIL
> PROTECTED]
> Our POM:
> http://svn.apache.org/repos/asf/jakarta/commons/proper/httpclient/trunk/project.xml
> The generated HTML:
> http://jakarta.apache.org/commons/httpclient/mail-lists.html
> As you can see the mailing list links are missing the mailto: prefix.
> The problem is on line 24 in the file
> plugin-resources/templates/mail-lists.xml:
> #if ($link.trim().startsWith("http"))
> which should be
> #if ($link.trim().startsWith("http://";))
> or equivalent.
--
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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MEAR-12) Make maven-ear-plugin feature complete against m1 version
[ http://jira.codehaus.org/browse/MEAR-12?page=all ] Stephane Nicoll closed MEAR-12: --- Resolution: Fixed Fix Version: 2.0 > Make maven-ear-plugin feature complete against m1 version > - > > Key: MEAR-12 > URL: http://jira.codehaus.org/browse/MEAR-12 > Project: Maven 2.x Ear Plugin > Type: Bug > Reporter: Edwin Punzalan > Assignee: Edwin Punzalan > Fix For: 2.0 > Attachments: MNG-822-maven-ear-plugin.patch > > Original Estimate: 8 hours >Time Spent: 2 hours > Remaining: 0 minutes > -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Reopened: (MEAR-12) Make maven-ear-plugin feature complete against m1 version
[ http://jira.codehaus.org/browse/MEAR-12?page=all ] Stephane Nicoll reopened MEAR-12: - > Make maven-ear-plugin feature complete against m1 version > - > > Key: MEAR-12 > URL: http://jira.codehaus.org/browse/MEAR-12 > Project: Maven 2.x Ear Plugin > Type: Bug > Reporter: Edwin Punzalan > Assignee: Edwin Punzalan > Fix For: 2.0 > Attachments: MNG-822-maven-ear-plugin.patch > > Original Estimate: 8 hours >Time Spent: 2 hours > Remaining: 0 minutes > -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MEAR-15) Support of sar files
[ http://jira.codehaus.org/browse/MEAR-15?page=all ] Stephane Nicoll closed MEAR-15: --- Resolution: Fixed Fix Version: 2.1 > Support of sar files > > > Key: MEAR-15 > URL: http://jira.codehaus.org/browse/MEAR-15 > Project: Maven 2.x Ear Plugin > Type: Bug > Environment: Maven 2.0.1, maven-ear-plugin 2.0, Windows XP. > Reporter: Jay Stramel > Assignee: Stephane Nicoll > Fix For: 2.1 > > > Building an ear file will fail if the ear file requires a SAR file as one of > it's components. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Reopened: (MEAR-15) Support of sar files
[ http://jira.codehaus.org/browse/MEAR-15?page=all ] Stephane Nicoll reopened MEAR-15: - Building the roadmap for 2.1 > Support of sar files > > > Key: MEAR-15 > URL: http://jira.codehaus.org/browse/MEAR-15 > Project: Maven 2.x Ear Plugin > Type: Bug > Environment: Maven 2.0.1, maven-ear-plugin 2.0, Windows XP. > Reporter: Jay Stramel > Assignee: Stephane Nicoll > Fix For: 2.1 > > > Building an ear file will fail if the ear file requires a SAR file as one of > it's components. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MNG-1691) [maven-par-plugin] NPE in ParMojo.java
[ http://jira.codehaus.org/browse/MNG-1691?page=all ] Stephane Nicoll closed MNG-1691: Resolution: Duplicate See MNG-1690. > [maven-par-plugin] NPE in ParMojo.java > -- > > Key: MNG-1691 > URL: http://jira.codehaus.org/browse/MNG-1691 > Project: Maven 2 > Type: Bug > Components: Sandbox > Reporter: Tim Kettler > Assignee: Stephane Nicoll > Attachments: maven-par-plugin.patch > > > Same problem as described in MNG-1690. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MNG-1690) [maven-ejb3-plugin] NPE in EJB3Mojo.java
[ http://jira.codehaus.org/browse/MNG-1690?page=all ] Stephane Nicoll closed MNG-1690: Resolution: Fixed Applied to ejb3 and par plugins ; Thanks. > [maven-ejb3-plugin] NPE in EJB3Mojo.java > > > Key: MNG-1690 > URL: http://jira.codehaus.org/browse/MNG-1690 > Project: Maven 2 > Type: Bug > Components: Sandbox > Reporter: Tim Kettler > Assignee: Stephane Nicoll > Attachments: maven-ejb3-plugin.patch > > > running mvn package fails with: > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Error assembling EJB3 > [INFO] > > [INFO] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: Error assembling EJB3 > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:544) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:469) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:448) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:301) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:268) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:137) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > Caused by: org.apache.maven.plugin.MojoExecutionException: Error assembling > EJB3 > at org.apache.maven.plugin.ejb3.Ejb3Mojo.execute(Ejb3Mojo.java:146) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:519) > ... 16 more > Caused by: java.lang.NullPointerException > at org.apache.maven.plugin.ejb3.Ejb3Mojo.execute(Ejb3Mojo.java:136) > ... 18 more > A look at the source shows that the archiver is never initialized. The > attached patch initializes the archiver with a JarArchiver. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MCLEAN-2) Delete additional directories and files including testOutputDirectory, outputDirectory, and directory
[ http://jira.codehaus.org/browse/MCLEAN-2?page=comments#action_53853 ] Dan Tran commented on MCLEAN-2: --- mavne-assembly-plugin uses its own generated FileSet maven-scm-plugin ( in maven-scm ) uses it s own ScmFileSet > Delete additional directories and files including testOutputDirectory, > outputDirectory, and directory > - > > Key: MCLEAN-2 > URL: http://jira.codehaus.org/browse/MCLEAN-2 > Project: Maven 2.x Clean Plugin > Type: Bug > Reporter: Ash Lux > Priority: Minor > Attachments: MCLEAN-2.txt, MNG-1801-maven-clean-lugin.patch > > -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (CONTINUUM-354) Need a way to poll for new projects
[ http://jira.codehaus.org/browse/CONTINUUM-354?page=comments#action_53852 ] Matthew Beermann commented on CONTINUUM-354: No, CONTINUUM-330 didn't solve this. Here's why: 1. Add a new to the parent project and check in. 2. Rebuild the parent project. 3. I would expect the new module to be added to the Continuum project list, if it doesn't exist already. However, no such thing occurs. It seems that Continuum will check/add modules when the parent project is first added, but not when the parent project changes. It should, IMO. > Need a way to poll for new projects > --- > > Key: CONTINUUM-354 > URL: http://jira.codehaus.org/browse/CONTINUUM-354 > Project: Continuum > Type: Improvement > Versions: 1.0-beta-1 > Reporter: Matthew Beermann > Fix For: 1.1 > > > The feature where Continuum can populate its build list from a URL is > wonderful; it'd be even more wonderful if it could remember that URL and poll > it periodically. We have a "master build list" of all projects that we'll use > to initially populate the build database; but ideally we could simply add a > new project to that in CVS and have Continuum just pick it up. > This is a feature that we've (somewhat painfully) managed to implement in > CruiseControl, and it's a must-have if we're going to switch over... this > might or might not depend on CONTINUUM-330. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCLEAN-2) Delete additional directories and files including testOutputDirectory, outputDirectory, and directory
[ http://jira.codehaus.org/browse/MCLEAN-2?page=comments#action_53851 ] ruel loehr commented on MCLEAN-2: - Is there an example in any existing plugins where filesets are used? > Delete additional directories and files including testOutputDirectory, > outputDirectory, and directory > - > > Key: MCLEAN-2 > URL: http://jira.codehaus.org/browse/MCLEAN-2 > Project: Maven 2.x Clean Plugin > Type: Bug > Reporter: Ash Lux > Priority: Minor > Attachments: MCLEAN-2.txt, MNG-1801-maven-clean-lugin.patch > > -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MJAVADOC-30) javadoc plugin does not work on war projects
[ http://jira.codehaus.org/browse/MJAVADOC-30?page=comments#action_53850 ] Matt Hicks commented on MJAVADOC-30: I downloaded Maven 2.0.1 and new repository plugins and I still see this behavior. Are there additional steps required or can we re-open this issue? > javadoc plugin does not work on war projects > - > > Key: MJAVADOC-30 > URL: http://jira.codehaus.org/browse/MJAVADOC-30 > Project: Maven 2.x Javadoc Plugin > Type: Bug > Environment: Linux/sun jdk 1.4.1_04 > Reporter: Joe Shomphe > Assignee: Brett Porter > > > when mvn javadoc:javadoc is run, the following error occurs: > "[INFO] Not executing Javadoc as the project is not a Java classpath-capable > package" > this only happens when my pom,xml has > war > declared > When this is set to jar, javadoc works fine. The war project has java > sources in it! -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MCLEAN-2) Delete additional directories and files including testOutputDirectory, outputDirectory, and directory
[ http://jira.codehaus.org/browse/MCLEAN-2?page=comments#action_53849 ] Dan Tran commented on MCLEAN-2: --- rather than removing directories, It is best to remove using FileSet(s) where we can exclude/includes files within a directory. > Delete additional directories and files including testOutputDirectory, > outputDirectory, and directory > - > > Key: MCLEAN-2 > URL: http://jira.codehaus.org/browse/MCLEAN-2 > Project: Maven 2.x Clean Plugin > Type: Bug > Reporter: Ash Lux > Priority: Minor > Attachments: MCLEAN-2.txt, MNG-1801-maven-clean-lugin.patch > > -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MCLEAN-2) Delete additional directories and files including testOutputDirectory, outputDirectory, and directory
[ http://jira.codehaus.org/browse/MCLEAN-2?page=comments#action_53847 ] ruel loehr commented on MCLEAN-2: - I ran into the same situation and have attached a patch MCLEAN-2.txt as well. > Delete additional directories and files including testOutputDirectory, > outputDirectory, and directory > - > > Key: MCLEAN-2 > URL: http://jira.codehaus.org/browse/MCLEAN-2 > Project: Maven 2.x Clean Plugin > Type: Bug > Reporter: Ash Lux > Priority: Minor > Attachments: MCLEAN-2.txt, MNG-1801-maven-clean-lugin.patch > > -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MCLEAN-2) Delete additional directories and files including testOutputDirectory, outputDirectory, and directory
[ http://jira.codehaus.org/browse/MCLEAN-2?page=all ] ruel loehr updated MCLEAN-2: Attachment: MCLEAN-2.txt > Delete additional directories and files including testOutputDirectory, > outputDirectory, and directory > - > > Key: MCLEAN-2 > URL: http://jira.codehaus.org/browse/MCLEAN-2 > Project: Maven 2.x Clean Plugin > Type: Bug > Reporter: Ash Lux > Priority: Minor > Attachments: MCLEAN-2.txt, MNG-1801-maven-clean-lugin.patch > > -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Reopened: (MCLOVER-10) Upgrade to Clover 1.3.10_01
[ http://jira.codehaus.org/browse/MCLOVER-10?page=all ] Vincent Massol reopened MCLOVER-10: --- Reopen to set again versions after the jira move from "Maven 2" to "Maven 2.x Clover Plugin" > Upgrade to Clover 1.3.10_01 > --- > > Key: MCLOVER-10 > URL: http://jira.codehaus.org/browse/MCLOVER-10 > Project: Maven 2.x Clover Plugin > Type: Bug > Versions: 2.0-alpha-1 > Reporter: Vincent Massol > Assignee: Vincent Massol > Fix For: 2.0 > > -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MCLOVER-10) Upgrade to Clover 1.3.10_01
[ http://jira.codehaus.org/browse/MCLOVER-10?page=all ] Vincent Massol closed MCLOVER-10: - Resolution: Fixed Fixed again versions after the jira move from "Maven 2" to "Maven 2.x Clover Plugin" > Upgrade to Clover 1.3.10_01 > --- > > Key: MCLOVER-10 > URL: http://jira.codehaus.org/browse/MCLOVER-10 > Project: Maven 2.x Clover Plugin > Type: Improvement > Versions: 2.0-alpha-1 > Reporter: Vincent Massol > Assignee: Vincent Massol > Fix For: 2.0 > > -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MCLOVER-10) Upgrade to Clover 1.3.10_01
[ http://jira.codehaus.org/browse/MCLOVER-10?page=all ] Vincent Massol updated MCLOVER-10: -- Version: 2.0-alpha-1 Fix Version: 2.0 type: Improvement (was: Bug) set again versions after the jira move from "Maven 2" to "Maven 2.x Clover Plugin" > Upgrade to Clover 1.3.10_01 > --- > > Key: MCLOVER-10 > URL: http://jira.codehaus.org/browse/MCLOVER-10 > Project: Maven 2.x Clover Plugin > Type: Improvement > Versions: 2.0-alpha-1 > Reporter: Vincent Massol > Assignee: Vincent Massol > Fix For: 2.0 > > -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MCLOVER-11) Add support for passing flush policy/flush interval to Clover
[ http://jira.codehaus.org/browse/MCLOVER-11?page=all ] Vincent Massol closed MCLOVER-11: - Resolution: Fixed Fixed again versions after the jira move from "Maven 2" to "Maven 2.x Clover Plugin" > Add support for passing flush policy/flush interval to Clover > - > > Key: MCLOVER-11 > URL: http://jira.codehaus.org/browse/MCLOVER-11 > Project: Maven 2.x Clover Plugin > Type: New Feature > Versions: 2.0-alpha-1 > Reporter: Vincent Massol > Assignee: Vincent Massol > Fix For: 2.0 > > > See http://cenqua.com/clover/doc/adv/flushpolicies.html. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MCLOVER-11) Add support for passing flush policy/flush interval to Clover
[ http://jira.codehaus.org/browse/MCLOVER-11?page=all ] Vincent Massol updated MCLOVER-11: -- Version: 2.0-alpha-1 Fix Version: 2.0 type: New Feature (was: Bug) set again versions after the jira move from "Maven 2" to "Maven 2.x Clover Plugin" > Add support for passing flush policy/flush interval to Clover > - > > Key: MCLOVER-11 > URL: http://jira.codehaus.org/browse/MCLOVER-11 > Project: Maven 2.x Clover Plugin > Type: New Feature > Versions: 2.0-alpha-1 > Reporter: Vincent Massol > Assignee: Vincent Massol > Fix For: 2.0 > > > See http://cenqua.com/clover/doc/adv/flushpolicies.html. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MCLOVER-9) Locale problem in Clover plugin
[ http://jira.codehaus.org/browse/MCLOVER-9?page=all ] Vincent Massol updated MCLOVER-9: - Version: 2.0-alpha-1 Fix Version: 2.0 set again versions after the jira move from "Maven 2" to "Maven 2.x Clover Plugin" > Locale problem in Clover plugin > --- > > Key: MCLOVER-9 > URL: http://jira.codehaus.org/browse/MCLOVER-9 > Project: Maven 2.x Clover Plugin > Type: Bug > Versions: 2.0-alpha-1 > Reporter: Wim Deblauwe > Assignee: Vincent Siveton > Fix For: 2.0 > > > I get the following error with the clover plugin > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] Can't find bundle for base name clover-report, locale nl_NL > [INFO] > > [INFO] Trace > java.util.MissingResourceException: Can't find bundle for base name > clover-report, locale nl_NL > at > java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:837) > at java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:806) > at java.util.ResourceBundle.getBundle(ResourceBundle.java:700) > at > org.apache.maven.plugin.clover.CloverReportMojo.getBundle(CloverReportMojo.java:104) > at > org.apache.maven.plugin.clover.CloverReportMojo.getName(CloverReportMojo.java:136) > at > org.apache.maven.plugins.site.ReportComparator.compare(ReportComparator.java:40) > at java.util.Arrays.mergeSort(Arrays.java:1284) > at java.util.Arrays.sort(Arrays.java:1223) > at java.util.Collections.sort(Collections.java:159) > at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:240) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:399) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:519) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:469) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:448) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:301) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:268) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:137) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:113) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > regards, > Wim -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
