[jira] Work started: (MENFORCER-8) Ability to disallow groups of deps
[
http://jira.codehaus.org/browse/MENFORCER-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on MENFORCER-8 started by Brian Fox.
> Ability to disallow groups of deps
> --
>
> Key: MENFORCER-8
> URL: http://jira.codehaus.org/browse/MENFORCER-8
> Project: Maven 2.x Enforcer Plugin
> Issue Type: New Feature
> Components: Standard Rules
>Reporter: David Blevins
>Assignee: Brian Fox
> Fix For: 1.0-alpha-3
>
>
> There's a related issue MNG-2796 (http://jira.codehaus.org/browse/MNG-2796)
> involving some issue with using one pom ("server" parent pom) to depend on
> another pom ("container" parent pom). The desired effect is that any
> children modules of the container parent pom cannot depend on any children
> modules of the server parent pom. Having the server parent pom depend on the
> container parent pom is one way to ensure this cannot happen, but maybe
> considered a hack -- and I suppose it is when you consider that this only
> works if you control the poms of the deps that are "off limits".
> Brett has suggested adding explicit support for this so that groups of deps
> or individual deps could be marked as disallowed. That feature would
> definitely work as an alternate ensuring that nothing in the container group
> depends on anything in the server group.
--
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] Work logged: (MENFORCER-8) Ability to disallow groups of deps
[
http://jira.codehaus.org/browse/MENFORCER-8?page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#action_100107
]
Brian Fox logged work on MENFORCER-8:
-
Time Logged: 1 hour
Time Spent: 1 hour
Remaining Estimate: 1 hour
> Ability to disallow groups of deps
> --
>
> Key: MENFORCER-8
> URL: http://jira.codehaus.org/browse/MENFORCER-8
> Project: Maven 2.x Enforcer Plugin
> Issue Type: New Feature
> Components: Standard Rules
>Reporter: David Blevins
>Assignee: Brian Fox
> Fix For: 1.0-alpha-3
>
> Time Spent: 1 hour
> Remaining Estimate: 1 hour
>
> There's a related issue MNG-2796 (http://jira.codehaus.org/browse/MNG-2796)
> involving some issue with using one pom ("server" parent pom) to depend on
> another pom ("container" parent pom). The desired effect is that any
> children modules of the container parent pom cannot depend on any children
> modules of the server parent pom. Having the server parent pom depend on the
> container parent pom is one way to ensure this cannot happen, but maybe
> considered a hack -- and I suppose it is when you consider that this only
> works if you control the poms of the deps that are "off limits".
> Brett has suggested adding explicit support for this so that groups of deps
> or individual deps could be marked as disallowed. That feature would
> definitely work as an alternate ensuring that nothing in the container group
> depends on anything in the server group.
--
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] Closed: (NMAVEN-81) The FileInstallerMojo does not work if a pom file is specified
[ http://jira.codehaus.org/browse/NMAVEN-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed NMAVEN-81. -- Resolution: Fixed Fixed in trunk. > The FileInstallerMojo does not work if a pom file is specified > -- > > Key: NMAVEN-81 > URL: http://jira.codehaus.org/browse/NMAVEN-81 > Project: NMaven > Issue Type: Bug >Reporter: Shane Isbell >Priority: Minor > > The FileInstallerMojo does not install the artifact if the -DpomFile= option > is specified. -- 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] Updated: (MNG-2516) Central isn't checked if pluginRepo specified in pom isn't reachable
[ http://jira.codehaus.org/browse/MNG-2516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox updated MNG-2516: --- Fix Version/s: (was: Reviewed Pending Version Assignment) 2.0.5 > Central isn't checked if pluginRepo specified in pom isn't reachable > > > Key: MNG-2516 > URL: http://jira.codehaus.org/browse/MNG-2516 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.0.4 >Reporter: Brian Fox >Assignee: Brian Fox > Fix For: 2.0.5 > > Attachments: pom.xml, settings.xml > > > I ran into a case where we have a repo defined in our pom. In some > installations, this repo isn't reachable. To work around this, we synched our > repo locally and setup file based remote repos and pluginrepos. However when > checking for plugins, central wasn't being checked because it was stopping at > the repo it couldn't reach. I was able to replicate this with a simple pom > and settings.xml that are attached. Put them in a folder and run mvn -s > ./settings.xml install. > It seems like failures accessing one repo will cause the whole build to fail. > Shouldn't it at least check other repos like central before giving up > completely? -- 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] Closed: (MNG-2516) Central isn't checked if pluginRepo specified in pom isn't reachable
[ http://jira.codehaus.org/browse/MNG-2516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox closed MNG-2516. -- Resolution: Cannot Reproduce This seems to have been fixed back in 2.0.5 when the repository blacklisting was added. The attached pom builds fine. > Central isn't checked if pluginRepo specified in pom isn't reachable > > > Key: MNG-2516 > URL: http://jira.codehaus.org/browse/MNG-2516 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.0.4 >Reporter: Brian Fox >Assignee: Brian Fox > Fix For: Reviewed Pending Version Assignment > > Attachments: pom.xml, settings.xml > > > I ran into a case where we have a repo defined in our pom. In some > installations, this repo isn't reachable. To work around this, we synched our > repo locally and setup file based remote repos and pluginrepos. However when > checking for plugins, central wasn't being checked because it was stopping at > the repo it couldn't reach. I was able to replicate this with a simple pom > and settings.xml that are attached. Put them in a folder and run mvn -s > ./settings.xml install. > It seems like failures accessing one repo will cause the whole build to fail. > Shouldn't it at least check other repos like central before giving up > completely? -- 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: (MNG-2858) Maven isn't looking in all repositories
[ http://jira.codehaus.org/browse/MNG-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100104 ] Brian Fox commented on MNG-2858: I think I've seen this too. Will try to reproduce it. > Maven isn't looking in all repositories > --- > > Key: MNG-2858 > URL: http://jira.codehaus.org/browse/MNG-2858 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.0.5 >Reporter: David Jackman > > I've created a settings.xml that lists all of our internal repositories (some > Maven 1, some Maven 2). One of these repositories contains the parent POM > for the project I'm trying to build. However, Maven reports that it can't > "locate resource in repository" and lists all of the repositories in > settings.xml. > > Looking at the debug output, it seems like Maven is only looking for the > parent pom in the first of the repositories in this list (the one just after > central). The correct repository is the second one in the list. > > To test this theory, I removed the repository it was having problems with > from settings.xml. Sure enough, Maven found the parent pom just fine. I > also changed the ID of the repository in settings.xml (which changes its > position in the list--must be a HashMap or something) and it found the parent > pom just fine in this situation, too. -- 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] Updated: (MNG-2961) DefaultArtifact getBaseVersion is changed to "xxxx-SNAPSHOT" only if you first call isSnapshot()
[
http://jira.codehaus.org/browse/MNG-2961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Fox updated MNG-2961:
---
Assignee: Brian Fox
Fix Version/s: (was: Reviewed Pending Version Assignment)
2.0.x
> DefaultArtifact getBaseVersion is changed to "-SNAPSHOT" only if you
> first call isSnapshot()
>
>
> Key: MNG-2961
> URL: http://jira.codehaus.org/browse/MNG-2961
> Project: Maven 2
> Issue Type: Bug
> Components: Artifacts and Repositories
>Affects Versions: 2.0, 2.0.1, 2.0.2, 2.0.3, 2.0.4, 2.0.5, 2.0.6
>Reporter: Brian Fox
>Assignee: Brian Fox
>Priority: Minor
> Fix For: 2.0.x
>
>
> calling isSnapshot() actually modifies the baseVersion:
> public boolean isSnapshot()
> {
> if ( version != null || baseVersion != null )
> {
> Matcher m = VERSION_FILE_PATTERN.matcher( getBaseVersion() );
> if ( m.matches() )
> {
> setBaseVersion( m.group( 1 ) + "-" + SNAPSHOT_VERSION );
> return true;
> }
> else
> {
> return getBaseVersion().endsWith( SNAPSHOT_VERSION ) ||
> getBaseVersion().equals( LATEST_VERSION );
> }
> }
> else
> {
> return false;
> }
> }
--
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] Closed: (MNG-2696) maven-cli assembly exceptions when using maven to build
[ http://jira.codehaus.org/browse/MNG-2696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox closed MNG-2696. -- Assignee: Brian Fox Resolution: Cannot Reproduce Fix Version/s: (was: Reviewed Pending Version Assignment) 2.0.7 Rechecked with 2.0.7 building trunk and I have no issues. > maven-cli assembly exceptions when using maven to build > --- > > Key: MNG-2696 > URL: http://jira.codehaus.org/browse/MNG-2696 > Project: Maven 2 > Issue Type: Bug > Components: Bootstrap & Build >Affects Versions: 2.0-alpha-1 >Reporter: Brian Fox >Assignee: Brian Fox > Fix For: 2.0.7 > > > Using 2.0.4 to build 2.1: > E:\svn\maven-trunk\maven-cli>mvn assembly:assembly [INFO] Scanning for > projects... > [INFO] Searching repository for plugin with prefix: 'assembly'. > [INFO] -- > --- > [INFO] Building Maven Core - CLI > [INFO]task-segment: [assembly:assembly] (aggregator-style) > [INFO] -- > > . > > --- > T E S T S > --- > Running org.apache.maven.cli.BatchModeDownloadMonitorTest > Downloading: null://nullnull/null > 97K downloaded > java.lang.RuntimeException > at > org.apache.maven.cli.AbstractConsoleDownloadMonitorTest.testTransferE > rror(AbstractConsoleDownloadMonitorTest.java:83) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. > java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces > sorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at junit.framework.TestCase.runTest(TestCase.java:154) > at junit.framework.TestCase.runBare(TestCase.java:127) > at junit.framework.TestResult$1.protect(TestResult.java:106) > at junit.framework.TestResult.runProtected(TestResult.java:124) > at junit.framework.TestResult.run(TestResult.java:109) > at junit.framework.TestCase.run(TestCase.java:118) > at junit.framework.TestSuite.runTest(TestSuite.java:208) > at junit.framework.TestSuite.run(TestSuite.java:203) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. > java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces > sorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at > org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.jav > a:210) > at > org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTes > tSet(AbstractDirectoryTestSuite.java:135) > Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.062 sec > Running org.apache.maven.cli.ConsoleDownloadMonitorTest > Downloading: null://nullnull/null > 0/97K > 97K downloaded > at > org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(Ab > stractDirectoryTestSuite.java:122) > at org.apache.maven.surefire.Surefire.run(Surefire.java:129) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. > java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces > sorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at > org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(Su > refireBooter.java:269) > at > org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.j > ava:788) > java.lang.RuntimeException > at > org.apache.maven.cli.AbstractConsoleDownloadMonitorTest.testTransferE > rror(AbstractConsoleDownloadMonitorTest.java:83) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. > java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces > sorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at junit.framework.TestCase.runTest(TestCase.java:154) > at junit.framework.TestCase.runBare(TestCase.java:127) > at junit.framework.TestResult$1.protect(TestResult.java:106) > at junit.framework.TestResult.runProtected(TestResult.java:124) > at junit.framework.TestResult.run(TestResult.java:109) > at junit.framework.TestCase.run(TestCase.java:118) > at junit.framework.TestSuite.runTest(Test
[jira] Closed: (MENFORCER-9) Exception in java rule when using Apple JDK 6 Developer Preview
[ http://jira.codehaus.org/browse/MENFORCER-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox closed MENFORCER-9. - Resolution: Fixed Fix Version/s: 1.0-alpha-3 all set now > Exception in java rule when using Apple JDK 6 Developer Preview > --- > > Key: MENFORCER-9 > URL: http://jira.codehaus.org/browse/MENFORCER-9 > Project: Maven 2.x Enforcer Plugin > Issue Type: Bug > Components: Standard Rules >Affects Versions: 1.0-alpha-2 > Environment: java version "1.6.0-dp" > Java(TM) SE Runtime Environment (build 1.6.0-dp-b88-34) > Java HotSpot(TM) Client VM (build 1.6.0-b88-17-release, mixed mode, sharing) >Reporter: Brett Porter >Assignee: Brian Fox >Priority: Blocker > Fix For: 1.0-alpha-3 > > > [ERROR] FATAL ERROR > [INFO] > > [INFO] For input string: "" > [INFO] > > [INFO] Trace > java.lang.NumberFormatException: For input string: "" > at > java.lang.NumberFormatException.forInputString(NumberFormatException.java:48) > at java.lang.Integer.parseInt(Integer.java:468) > at java.lang.Integer.parseInt(Integer.java:497) > at > org.apache.maven.plugin.enforcer.RequireJavaVersion.normalizeJDKVersion(RequireJavaVersion.java:87) > at > org.apache.maven.plugin.enforcer.RequireJavaVersion.execute(RequireJavaVersion.java:53) > at > org.apache.maven.plugin.enforcer.EnforceMojo.execute(EnforceMojo.java:143) > at > org.apache.maven.plugin.enforcer.EnforceOnceMojo.execute(EnforceOnceMojo.java:39) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:272) > 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:589) > 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) -- 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] Closed: (NMAVEN-77) Maven Visual Studio 2005 Installer Plugin Should Generate Sample Project on Install
[ http://jira.codehaus.org/browse/NMAVEN-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed NMAVEN-77. -- Resolution: Won't Fix Currently have support for generating a project through a VS wizard, so it is not necessary to autogenerate a generic project with the vsinstaller. > Maven Visual Studio 2005 Installer Plugin Should Generate Sample Project on > Install > --- > > Key: NMAVEN-77 > URL: http://jira.codehaus.org/browse/NMAVEN-77 > Project: NMaven > Issue Type: Improvement >Reporter: Shane Isbell >Priority: Minor > > Maven Visual Studio 2005 installer plugin should generate sample project and > solution on install. This will make it easier for first-time users. -- 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] Created: (NMAVEN-82) Support for IoC Container
Support for IoC Container - Key: NMAVEN-82 URL: http://jira.codehaus.org/browse/NMAVEN-82 Project: NMaven Issue Type: New Feature Reporter: Shane Isbell Need to add support for IoC container for use within the NMaven projects. Currently investigating the use of the MicroKernel from http://www.castleproject.org/. They use ASL 2.0 license so it is compatible. -- 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: (NMAVEN-18) Archetype Plugins
[ http://jira.codehaus.org/browse/NMAVEN-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100095 ] Shane Isbell commented on NMAVEN-18: Completed an archetype for a library project using a VisualStudio wizard. > Archetype Plugins > - > > Key: NMAVEN-18 > URL: http://jira.codehaus.org/browse/NMAVEN-18 > Project: NMaven > Issue Type: New Feature >Reporter: Shane Isbell >Priority: Minor > > Archetype plugins that generate the directory structure and the pom.xml based > on target build environment: Visual Studio, SharpDevelop, CLI and on project > type: library, ASP.NET, etc. VS, SD and CLI may each have different directory > structures, but all projects, regardless of structure, will be buildable from > the command line. This extends the NMaven concept of making the build system > platform aware (in terms of compilers, vendors, OS) to also being build > structure aware (in terms of the dev environment). -- 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] Created: (NMAVEN-81) The FileInstallerMojo does not work if a pom file is specified
The FileInstallerMojo does not work if a pom file is specified -- Key: NMAVEN-81 URL: http://jira.codehaus.org/browse/NMAVEN-81 Project: NMaven Issue Type: Bug Reporter: Shane Isbell Priority: Minor The FileInstallerMojo does not install the artifact if the -DpomFile= option is specified. -- 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] Updated: (CONTINUUM-1321) Improve error message when perform release fails due to missing distributionManagement
[
http://jira.codehaus.org/browse/CONTINUUM-1321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wendy Smoak updated CONTINUUM-1321:
---
Description:
When 'perform release' fails because there is no distributionManagment section
in the pom, all you get in 'View Output' is the following:
{noformat}
[ERROR] org.apache.maven.shared.release.ReleaseExecutionException: Maven
execution failed, exit code: '1'
at
org.apache.maven.shared.release.phase.AbstractRunGoalsPhase.execute(AbstractRunGoalsPhase.java:66)
at
org.apache.maven.shared.release.phase.RunPerformGoalsPhase.execute(RunPerformGoalsPhase.java:57)
at
org.apache.maven.shared.release.DefaultReleaseManager.perform(DefaultReleaseManager.java:319)
at
org.apache.maven.shared.release.DefaultReleaseManager.performWithResult(DefaultReleaseManager.java:279)
at
org.apache.maven.continuum.release.executors.PerformReleaseTaskExecutor.execute(PerformReleaseTaskExecutor.java:82)
at
org.apache.maven.continuum.release.executors.AbstractReleaseTaskExecutor.executeTask(AbstractReleaseTaskExecutor.java:67)
at
org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ThreadedTaskQueueExecutor.java:116)
at
edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442)
at
edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
at java.lang.Thread.run(Thread.java:595)
Caused by: org.apache.maven.shared.release.exec.MavenExecutorException: Maven
execution failed, exit code: '1'
at
org.apache.maven.shared.release.exec.ForkedMavenExecutor.executeGoals(ForkedMavenExecutor.java:103)
at
org.apache.maven.shared.release.exec.ForkedMavenExecutor.executeGoals(ForkedMavenExecutor.java:121)
at
org.apache.maven.shared.release.phase.AbstractRunGoalsPhase.execute(AbstractRunGoalsPhase.java:59)
... 11 more
{noformat}
The log file shows the actual error:
{noformat}
INFO | jvm 1| 2007/06/19 17:19:37 | [INFO]
INFO | jvm 1| 2007/06/19 17:19:37 | [ERROR] BUILD ERROR
INFO | jvm 1| 2007/06/19 17:19:37 | [INFO]
INFO | jvm 1| 2007/06/19 17:19:37 | [INFO] Failed to configure plugin
parameters for: org.apache.maven.plugins:maven-deploy-plugin:2.3
INFO | jvm 1| 2007/06/19 17:19:37 |
INFO | jvm 1| 2007/06/19 17:19:37 | check that the following section
of the pom.xml is present and correct:
INFO | jvm 1| 2007/06/19 17:19:37 |
INFO | jvm 1| 2007/06/19 17:19:37 |
INFO | jvm 1| 2007/06/19 17:19:37 |
INFO | jvm 1| 2007/06/19 17:19:37 |
INFO | jvm 1| 2007/06/19 17:19:37 | repo
INFO | jvm 1| 2007/06/19 17:19:37 | Repository Name
INFO | jvm 1| 2007/06/19 17:19:37 |
scp://host/path/to/repo
INFO | jvm 1| 2007/06/19 17:19:37 |
INFO | jvm 1| 2007/06/19 17:19:37 |
INFO | jvm 1| 2007/06/19 17:19:37 |
INFO | jvm 1| 2007/06/19 17:19:37 | repo
INFO | jvm 1| 2007/06/19 17:19:37 | Repository Name
INFO | jvm 1| 2007/06/19 17:19:37 |
scp://host/path/to/repo
INFO | jvm 1| 2007/06/19 17:19:37 |
INFO | jvm 1| 2007/06/19 17:19:37 |
INFO | jvm 1| 2007/06/19 17:19:37 |
INFO | jvm 1| 2007/06/19 17:19:37 | Cause: Class
'org.apache.maven.artifact.repository.ArtifactRepository' cannot be instantiated
INFO | jvm 1| 2007/06/19 17:19:37 | [INFO]
INFO | jvm 1| 2007/06/19 17:19:37 | [INFO] For more information, run
Maven with the -e switch
INFO | jvm 1| 2007/06/19 17:19:37 | [INFO]
INFO | jvm 1| 2007/06/19 17:19:37 | [INFO] Total time: 5 seconds
INFO | jvm 1| 2007/06/19 17:19:37 | [INFO] Finished at: Tue Jun 19
17:19:37 PDT 2007
INFO | jvm 1| 2007/06/19 17:19:37 | [INFO] Final Memory: 9M/17M
INFO | jvm 1| 2007/06/19 17:19:37 | [INFO]
{noformat}
was:
When a build fails because there is no distributionManagment section in the
pom, all you get in 'View Output' is the following:
{noformat}
[ERROR] org.apache.maven.shared.release.ReleaseExecutionException: Maven
execution failed, exit code: '1'
at
org.apache.maven.s
[jira] Closed: (MRM-221) Webdav upload is not working
[ http://jira.codehaus.org/browse/MRM-221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wendy Smoak closed MRM-221. --- Resolution: Fixed Fix Version/s: (was: 1.0-alpha-2) webdav deployment is working fine for me in 1.0-alpha-1 please ask on the user list or re-open if it's still an issue > Webdav upload is not working > > > Key: MRM-221 > URL: http://jira.codehaus.org/browse/MRM-221 > Project: Archiva > Issue Type: Bug > Components: WebDAV interface >Affects Versions: 1.0 > Environment: Mac OS X using the default jetty container. Jetty > started with mvn jetty:run >Reporter: Greg Luck > > MRM-172 added webdav support. This is not working. > I have everything working scping to the repository. webdav via Archiva does > not work. > When I use > > > > > > url="dav://localhost:9091/repository/maven_repository"> > password="###"/> > > > > I get > upload-to-repository: > [artifact:install-provider] Installing provider: > org.apache.maven.wagon:wagon-webdav:jar:1.0-beta-1 > [artifact:install-provider] Installing provider: > org.apache.maven.wagon:wagon-ssh:jar:1.0-beta-1 > [artifact:install] [INFO] Installing > /Users/gluck/work/ehcache/trunk/target/dist/ehcache-1.2.4.jar to > /m2repository/net/sf/ehcache/ehcache/1.2.4/ehcache-1.2.4.jar > [artifact:deploy] Deploying to > dav://localhost:9091/repository/maven_repository > [artifact:deploy] WAGON_VERSION: 1.0-beta-1 > BUILD FAILED > /Users/gluck/work/ehcache/trunk/build.xml:364: > java.lang.IllegalArgumentException: id is null > If I click on the webdav link from archiva I get: > Error 404 Not Found > Resource in error: http://localhost:9091/repository/LOCAL/maven_repository > Exception details: > it.could.webdav.DAVException: Not found > at it.could.webdav.methods.HEAD.process(HEAD.java:52) > at it.could.webdav.methods.GET.process(GET.java:58) > at it.could.webdav.DAVProcessor.process(DAVProcessor.java:79) > at > org.apache.maven.archiva.web.servlet.repository.RepositoryAccess.servletRequest(RepositoryAccess.java:223) > at > org.apache.maven.archiva.web.servlet.PlexusComponentServlet.service(PlexusComponentServlet.java:126) > at > org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:445) > at > org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1049) > at > com.opensymphony.webwork.dispatcher.FilterDispatcher.doFilter(FilterDispatcher.java:189) > at > org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1040) > at > com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:118) > at > com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:52) > at > org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1040) > at > com.opensymphony.webwork.dispatcher.ActionContextCleanUp.doFilter(ActionContextCleanUp.java:88) > at > org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1040) > at > org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:352) > at > org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:230) > at > org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:627) > at > org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:149) > at > org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:123) > at > org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:141) > at org.mortbay.jetty.Server.handle(Server.java:286) > at > org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:444) > at > org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:701) > at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:500) > at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:203) > at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:340) > at > org.mortbay.jetty.nio.HttpChannelEndPoint.run(HttpChannelEndPoint.java:270) > at > org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:475) -- 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] Created: (CONTINUUM-1321) Improve error message when perform release fails due to missing distributionManagement
Improve error message when perform release fails due to missing
distributionManagement
--
Key: CONTINUUM-1321
URL: http://jira.codehaus.org/browse/CONTINUUM-1321
Project: Continuum
Issue Type: Improvement
Components: Release
Affects Versions: 1.1-alpha-2
Reporter: Wendy Smoak
Priority: Minor
When a build fails because there is no distributionManagment section in the
pom, all you get in 'View Output' is the following:
{noformat}
[ERROR] org.apache.maven.shared.release.ReleaseExecutionException: Maven
execution failed, exit code: '1'
at
org.apache.maven.shared.release.phase.AbstractRunGoalsPhase.execute(AbstractRunGoalsPhase.java:66)
at
org.apache.maven.shared.release.phase.RunPerformGoalsPhase.execute(RunPerformGoalsPhase.java:57)
at
org.apache.maven.shared.release.DefaultReleaseManager.perform(DefaultReleaseManager.java:319)
at
org.apache.maven.shared.release.DefaultReleaseManager.performWithResult(DefaultReleaseManager.java:279)
at
org.apache.maven.continuum.release.executors.PerformReleaseTaskExecutor.execute(PerformReleaseTaskExecutor.java:82)
at
org.apache.maven.continuum.release.executors.AbstractReleaseTaskExecutor.executeTask(AbstractReleaseTaskExecutor.java:67)
at
org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ThreadedTaskQueueExecutor.java:116)
at
edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442)
at
edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
at java.lang.Thread.run(Thread.java:595)
Caused by: org.apache.maven.shared.release.exec.MavenExecutorException: Maven
execution failed, exit code: '1'
at
org.apache.maven.shared.release.exec.ForkedMavenExecutor.executeGoals(ForkedMavenExecutor.java:103)
at
org.apache.maven.shared.release.exec.ForkedMavenExecutor.executeGoals(ForkedMavenExecutor.java:121)
at
org.apache.maven.shared.release.phase.AbstractRunGoalsPhase.execute(AbstractRunGoalsPhase.java:59)
... 11 more
{noformat}
The log file shows the actual error:
{noformat}
INFO | jvm 1| 2007/06/19 17:19:37 | [INFO]
INFO | jvm 1| 2007/06/19 17:19:37 | [ERROR] BUILD ERROR
INFO | jvm 1| 2007/06/19 17:19:37 | [INFO]
INFO | jvm 1| 2007/06/19 17:19:37 | [INFO] Failed to configure plugin
parameters for: org.apache.maven.plugins:maven-deploy-plugin:2.3
INFO | jvm 1| 2007/06/19 17:19:37 |
INFO | jvm 1| 2007/06/19 17:19:37 | check that the following section
of the pom.xml is present and correct:
INFO | jvm 1| 2007/06/19 17:19:37 |
INFO | jvm 1| 2007/06/19 17:19:37 |
INFO | jvm 1| 2007/06/19 17:19:37 |
INFO | jvm 1| 2007/06/19 17:19:37 |
INFO | jvm 1| 2007/06/19 17:19:37 | repo
INFO | jvm 1| 2007/06/19 17:19:37 | Repository Name
INFO | jvm 1| 2007/06/19 17:19:37 |
scp://host/path/to/repo
INFO | jvm 1| 2007/06/19 17:19:37 |
INFO | jvm 1| 2007/06/19 17:19:37 |
INFO | jvm 1| 2007/06/19 17:19:37 |
INFO | jvm 1| 2007/06/19 17:19:37 | repo
INFO | jvm 1| 2007/06/19 17:19:37 | Repository Name
INFO | jvm 1| 2007/06/19 17:19:37 |
scp://host/path/to/repo
INFO | jvm 1| 2007/06/19 17:19:37 |
INFO | jvm 1| 2007/06/19 17:19:37 |
INFO | jvm 1| 2007/06/19 17:19:37 |
INFO | jvm 1| 2007/06/19 17:19:37 | Cause: Class
'org.apache.maven.artifact.repository.ArtifactRepository' cannot be instantiated
INFO | jvm 1| 2007/06/19 17:19:37 | [INFO]
INFO | jvm 1| 2007/06/19 17:19:37 | [INFO] For more information, run
Maven with the -e switch
INFO | jvm 1| 2007/06/19 17:19:37 | [INFO]
INFO | jvm 1| 2007/06/19 17:19:37 | [INFO] Total time: 5 seconds
INFO | jvm 1| 2007/06/19 17:19:37 | [INFO] Finished at: Tue Jun 19
17:19:37 PDT 2007
INFO | jvm 1| 2007/06/19 17:19:37 | [INFO] Final Memory: 9M/17M
INFO | jvm 1| 2007/06/19 17:19:37 | [INFO]
{noformat}
--
This message is automatically ge
[jira] Commented: (MSITE-238) multi project default URL is wrong
[
http://jira.codehaus.org/browse/MSITE-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100084
]
Paul Sundling commented on MSITE-238:
-
workaround is to use the following for all childProjects (modules):
../../${project.artifactId}/target/site
It would be nice if the child projects/modules had a link back to the parent
project/module in multi module builds
> multi project default URL is wrong
> --
>
> Key: MSITE-238
> URL: http://jira.codehaus.org/browse/MSITE-238
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
>Reporter: Paul Sundling
>Priority: Trivial
>
> In multi module projects the default URL if non is included is
> //target/site//index.html , but it
> should be ///target/site/index.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
[jira] Updated: (CONTINUUM-44) multiple profiles
[ http://jira.codehaus.org/browse/CONTINUUM-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated CONTINUUM-44: -- Attachment: CONTINUUM-44-GOODIES This patch provide the following : * validation of the user entry when saving installation (jdk path, M2_HOME value etc..) * adding information on the builder use (like mvn -v) in the mail * change edit profile screen to not display installation (Add button) in case of profile creation * create a class ExecutorConfigurator to store configuration regarding executable informations. > multiple profiles > - > > Key: CONTINUUM-44 > URL: http://jira.codehaus.org/browse/CONTINUUM-44 > Project: Continuum > Issue Type: New Feature > Components: Core - Profiles >Reporter: Brett Porter >Assignee: Emmanuel Venisse > Fix For: 1.1-alpha-3 > > Attachments: CONTINUUM-44, CONTINUUM-44, > CONTINUUM-44-continuum-data-management, > CONTINUUM-44-continuum-data-management, CONTINUUM-44-GOODIES, > CONTINUUM-44-LICENSE-REFORMATED > > > would like to be able to define a profile (which can include certain > environmental things such as the version of m2 to use, the JDK version, etc). > Profiles should be able to be used globally, per group or per project. In > this way, you could build certain projects under a variety of different JDKs > for example. -- 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] Closed: (MAVEN-1267) create source distribution for Maven 1.0 as part of installer process
[ http://jira.codehaus.org/browse/MAVEN-1267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier closed MAVEN-1267. -- Resolution: Fixed Done. Goal : maven:build-src First sources available here : http://people.apache.org/repo/m1-snapshot-repository/maven/distributions/20070619/ > create source distribution for Maven 1.0 as part of installer process > - > > Key: MAVEN-1267 > URL: http://jira.codehaus.org/browse/MAVEN-1267 > Project: Maven 1 > Issue Type: Task > Components: installer >Affects Versions: 1.1-rc1 >Reporter: Brett Porter >Assignee: Arnaud Heritier > Fix For: 1.1 > > > currently build several binaries, but no source distribution -- 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] Closed: (MAVEN-1851) Upgrade maven-artifact-plugin to v 1.9.1
[ http://jira.codehaus.org/browse/MAVEN-1851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier closed MAVEN-1851. -- Resolution: Fixed Released by Lukas. Bundled in 1.1 > Upgrade maven-artifact-plugin to v 1.9.1 > > > Key: MAVEN-1851 > URL: http://jira.codehaus.org/browse/MAVEN-1851 > Project: Maven 1 > Issue Type: Improvement > Components: planning >Affects Versions: 1.1-rc1 >Reporter: Arnaud Heritier >Assignee: Arnaud Heritier > Fix For: 1.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
[jira] Created: (MAVEN-1851) Upgrade maven-artifact-plugin to v 1.9.1
Upgrade maven-artifact-plugin to v 1.9.1 Key: MAVEN-1851 URL: http://jira.codehaus.org/browse/MAVEN-1851 Project: Maven 1 Issue Type: Improvement Components: planning Affects Versions: 1.1-rc1 Reporter: Arnaud Heritier Assignee: Arnaud Heritier Fix For: 1.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
[jira] Closed: (MAVEN-1850) Upgrade maven-test-plugin to v 1.8.2
[ http://jira.codehaus.org/browse/MAVEN-1850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier closed MAVEN-1850. -- Resolution: Fixed Release done by Lukas. Integrated in 1.1 > Upgrade maven-test-plugin to v 1.8.2 > > > Key: MAVEN-1850 > URL: http://jira.codehaus.org/browse/MAVEN-1850 > Project: Maven 1 > Issue Type: Improvement > Components: planning >Affects Versions: 1.1-rc1 >Reporter: Arnaud Heritier >Assignee: Arnaud Heritier > Fix For: 1.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
[jira] Created: (MAVEN-1850) Upgrade maven-test-plugin to v 1.8.2
Upgrade maven-test-plugin to v 1.8.2 Key: MAVEN-1850 URL: http://jira.codehaus.org/browse/MAVEN-1850 Project: Maven 1 Issue Type: Improvement Components: planning Affects Versions: 1.1-rc1 Reporter: Arnaud Heritier Assignee: Arnaud Heritier Fix For: 1.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
[jira] Commented: (WAGON-54) Scm Wagon not expanding ${user.home}
[
http://jira.codehaus.org/browse/WAGON-54?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100075
]
Ian Springer commented on WAGON-54:
---
I'm seeing the same issue. Why has nobody responded to this case yet? It seems
like a pretty major problem to me...
> Scm Wagon not expanding ${user.home}
>
>
> Key: WAGON-54
> URL: http://jira.codehaus.org/browse/WAGON-54
> Project: wagon
> Issue Type: Bug
> Components: wagon-scm
>Affects Versions: 1.0-alpha-5
> Environment: windows xp, maven 2.0.4
>Reporter: Jean Deruelle
>
> when trying to deploy a jar to a svn repository , wagon-scm doesn't translate
> ${user.home} (because of space in the user home's windows path?) and create
> this directory in the current directory
> ...
>
>
> svn-repository
> scm:svn:https://[EMAIL
> PROTECTED]/svn/maven2-repository/trunk/repository
>
>
>
>
> org.apache.maven.wagon
> wagon-scm
> 1.0-alpha-5
>
>
> Here is the log :
> [INFO] [deploy:deploy]
> Uploading:
> scm:svn:https://maven2-repository.dev.java.net/svn/maven2-repository/trunk/repository/org/apache/maven/plugins/maven-slee-du-plugin/1.0/maven-slee-du-plugin-1.0.jar
> [INFO] Working directory:
> C:\java\java.net\slee-sip-ra\maven-slee-du-plugin\${user.home}\.m2\repository
> [INFO] Command line: svn add --non-recursive ${user.home}/.m2/repository/org
> [INFO] Working directory:
> C:\java\java.net\slee-sip-ra\maven-slee-du-plugin\${user.home}\.m2\repository\org
> [INFO] Command line: svn add --non-recursive
> ${user.home}/.m2/repository/org/apache
> [INFO] Working directory:
> C:\java\java.net\slee-sip-ra\maven-slee-du-plugin\${user.home}\.m2\repository\org\apache
> [INFO] Command line: svn add --non-recursive
> ${user.home}/.m2/repository/org/apache/maven
> [INFO] Working directory:
> C:\java\java.net\slee-sip-ra\maven-slee-du-plugin\${user.home}\.m2\repository\org\apache\maven
> [INFO] Command line: svn add --non-recursive
> ${user.home}/.m2/repository/org/apache/maven/plugins
> [INFO] Working directory:
> C:\java\java.net\slee-sip-ra\maven-slee-du-plugin\${user.home}\.m2\repository\org\apache\maven\plugins
> [INFO] Command line: svn add --non-recursive
> ${user.home}/.m2/repository/org/apache/maven/plugins/maven-slee-du-plugin
> [INFO] Working directory:
> C:\java\java.net\slee-sip-ra\maven-slee-du-plugin\${user.home}\.m2\repository\org\apache\maven\plugins\maven-slee-du-plugin
> [INFO] Command line: svn add --non-recursive
> ${user.home}/.m2/repository/org/apache/maven/plugins/maven-slee-du-plugin/1.0
> [INFO] Working directory:
> C:\java\java.net\slee-sip-ra\maven-slee-du-plugin\${user.home}\.m2\repository\org\apache\maven\plugins\maven-slee-du-plugin\1.0
> [INFO] Command line: svn --username deruelle_jean --password L0veSt1nks
> --non-interactive checkout
> https://maven2-repository.dev.java.net/svn/maven2-repository/
> trunk/repository/org/apache/maven/plugins/maven-slee-du-plugin/1.0 1.0
> [INFO] Working directory:
> C:\java\java.net\slee-sip-ra\maven-slee-du-plugin\${user.home}\.m2\repository\org\apache\maven\plugins\maven-slee-du-plugin
> [INFO] Command line: svn --username deruelle_jean --password L0veSt1nks
> --non-interactive commit --file
> C:\DOCUME~1\T405732\LOCALS~1\Temp\maven-scm-465347372.commit
> ${user.home}/.m2/repository/org/apache/maven/plugins/maven-slee-du-plugin/1.0
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Error deploying artifact: Unable to commit file svn:
> 'C:\java\java.net\slee-sip-ra\maven-slee-du-plugin\${user.home}\.m2\repository\org\apache\maven\plugins\maven-slee-du-plugin\${user.home}\.m2\repository\org\apache\maven\plugins\ma
> ven-slee-du-plugin' is not a working copy
--
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: (MPIR-69) add anchors for developers
[ http://jira.codehaus.org/browse/MPIR-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100070 ] Paul Sundling commented on MPIR-69: --- To be more clear, what I'm asking for is that anchors be added, so the changes report links will work correctly. > add anchors for developers > -- > > Key: MPIR-69 > URL: http://jira.codehaus.org/browse/MPIR-69 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Improvement >Reporter: Paul Sundling >Priority: Minor > > Currently the changes plugin links to the team list page with an anchor > corresponding to their id. For small teams that fit on one page this is > trivial, but it would be an issue for teams larger than a page of developers. -- 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] Created: (MPIR-69) add anchors for developers
add anchors for developers -- Key: MPIR-69 URL: http://jira.codehaus.org/browse/MPIR-69 Project: Maven 2.x Project Info Reports Plugin Issue Type: Improvement Reporter: Paul Sundling Priority: Minor Currently the changes plugin links to the team list page with an anchor corresponding to their id. For small teams that fit on one page this is trivial, but it would be an issue for teams larger than a page of developers. -- 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] Created: (MSITE-238) multi project default URL is wrong
multi project default URL is wrong -- Key: MSITE-238 URL: http://jira.codehaus.org/browse/MSITE-238 Project: Maven 2.x Site Plugin Issue Type: Bug Reporter: Paul Sundling Priority: Trivial In multi module projects the default URL if non is included is //target/site//index.html , but it should be ///target/site/index.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
[jira] Commented: (CONTINUUM-1007) pb getting a project being added after a first error
[ http://jira.codehaus.org/browse/CONTINUUM-1007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100067 ] Tom Guyette commented on CONTINUUM-1007: Reproduced. Priority needn't be "major," though, since there's a workaround. > pb getting a project being added after a first error > > > Key: CONTINUUM-1007 > URL: http://jira.codehaus.org/browse/CONTINUUM-1007 > Project: Continuum > Issue Type: Bug >Reporter: Emmanuel Lécharny > Fix For: 1.1-alpha-# > > > If you make a mistake when adding a project, there is no way to add another > project without stopping and starting the server. > Here is a scenario : > I try to add a wrong url : > http://svn.apache.org/repos/asf/directory/trunks/daemon > which is a directory, not a pom.xml > I get this error : > "Cannot build maven project from > /Applications/continuum-1.0.3/temp/continuum/repos/asf/directory/trunks/daemon > (Not a v4.0.0 POM.)." > which is correct so far (except that the error message is not really clear : > the error is not that the pom.xml is not a 4.0.0 version, but that it's > simply not a pom !!!) > So I try with : > http://svn.apache.org/repos/asf/directory/trunks/daemon/pom.xml > and now I get the error : > "Could not download > http://svn.apache.org/repos/asf/directory/trunks/daemon/pom.xml: > /Applications/continuum-1.0.3/temp/continuum/repos/asf/directory/trunks/daemon/pom.xml > (Not a directory)" > If I stop and restart continuum, and correctly add the .../pom.xml file, it > works fine > I guess some kind of state is kept somwhere after the first error. -- 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] Created: (WAGON-89) When you use a call that doesn not use authentication the call should not throw an authentication exception
When you use a call that doesn not use authentication the call should not throw an authentication exception Key: WAGON-89 URL: http://jira.codehaus.org/browse/WAGON-89 Project: wagon Issue Type: Improvement Components: wagon-provider-api Affects Versions: 1.0-beta-2 Reporter: Jason van Zyl A general problem with the way we make requests. We should differentiate between authenticated and non-authenticated requests. To make a call that requires no authentication like a simple file or http retrieval and have to trap an authentication error makes no sense and is confusing to consumers of the API. -- 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] Closed: (CONTINUUM-656) Child Project / Module added twice
[ http://jira.codehaus.org/browse/CONTINUUM-656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse closed CONTINUUM-656. -- Assignee: Emmanuel Venisse Resolution: Fixed Fix Version/s: (was: 1.1-alpha-3) 1.1-alpha-1 I can't reproduce it with 1.1-alpha-* > Child Project / Module added twice > -- > > Key: CONTINUUM-656 > URL: http://jira.codehaus.org/browse/CONTINUUM-656 > Project: Continuum > Issue Type: Bug > Components: Web interface >Affects Versions: 1.0.3 > Environment: Red Hat Enterprise Linux; Java 1.5 >Reporter: David H. DeWolf >Assignee: Emmanuel Venisse >Priority: Minor > Fix For: 1.1-alpha-1 > > > Added parent project with 10 subprojects. Parent and all children were added > successfully. One of the modules was duplicated. Working to put together a > smaller test case. -- 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] Closed: (CONTINUUM-643) NPE in addPathInfo
[ http://jira.codehaus.org/browse/CONTINUUM-643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse closed CONTINUUM-643. -- Assignee: Emmanuel Venisse Resolution: Won't Fix Fix Version/s: (was: 1.1-alpha-3) 1.0.3 velocity issues won't be fixed > NPE in addPathInfo > -- > > Key: CONTINUUM-643 > URL: http://jira.codehaus.org/browse/CONTINUUM-643 > Project: Continuum > Issue Type: Bug > Components: Web interface >Affects Versions: 1.0.3 >Reporter: Brett Porter >Assignee: Emmanuel Venisse >Priority: Minor > > I get this exception in the logs, coming from a velocity template: > java.lang.NullPointerException > at > org.codehaus.plexus.summit.util.UriBuilder.addPathInfo(UriBuilder.java:263) > It seems to be when the database might already have problems, so I'm > deferring this until WW is in place to see if it goes way. It doesn't seem to > have any major side effects. -- 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] Closed: (CONTINUUM-1002) build email cleanup
[ http://jira.codehaus.org/browse/CONTINUUM-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse closed CONTINUUM-1002. --- Assignee: Emmanuel Venisse Resolution: Fixed > build email cleanup > --- > > Key: CONTINUUM-1002 > URL: http://jira.codehaus.org/browse/CONTINUUM-1002 > Project: Continuum > Issue Type: Improvement > Components: Notifier - Mail >Reporter: Jon >Assignee: Emmanuel Venisse >Priority: Minor > Fix For: 1.1-alpha-3 > > Attachments: Picture 1.png > > > In the build emails, at the top it comes out something like this: > Online report : > http://build.365:8080/continuum/buildResult.action?buildId=68&projectId=17&projectName=Integration > Tests > It would be really cool if someone put a newline between the end of the url > and the "Tests" > jon -- 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] Created: (MNG-3062) Allow access to mojoExecution from within plugin.
Allow access to mojoExecution from within plugin. - Key: MNG-3062 URL: http://jira.codehaus.org/browse/MNG-3062 Project: Maven 2 Issue Type: Improvement Affects Versions: 2.0.6 Reporter: Paul Gier Attachments: PluginParameterExpressionEvaluator.patch I would like to be able to access the execution ID from within a plugin. This could be useful for example to run only certain executions. This could be done with a small change to the plugin expression evaluator. I created a patch that would give the plugin access to the current MojoExecution. -- 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: (MDEP-98) The source must not be a directory
[ http://jira.codehaus.org/browse/MDEP-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100057 ] Brian Fox commented on MDEP-98: --- can you please attach a sample project to reproduce this? > The source must not be a directory > -- > > Key: MDEP-98 > URL: http://jira.codehaus.org/browse/MDEP-98 > Project: Maven 2.x Dependency Plugin > Issue Type: Bug > Components: unpack-dependencies >Affects Versions: 2.0-alpha-4 > Environment: Windows XP Professional SP2 > Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03) > Java HotSpot(TM) Client VM (build 1.5.0_11-b03, mixed mode, sharing) >Reporter: Pablo Muñiz >Assignee: Brian Fox > > Using maven-dependency-plugin in a multimodule project inside a module wich > has a dependency with another module in the same project the next error > ocurrs : > org.codehaus.plexus.archiver.ArchiverException: The source must not be a > directory. > at > org.codehaus.plexus.archiver.AbstractUnArchiver.validate(AbstractUnArchiver.java:98) > at > org.codehaus.plexus.archiver.AbstractUnArchiver.extract(AbstractUnArchiver.java:84) > at > org.apache.maven.plugin.dependency.AbstractDependencyMojo.unpack(AbstractDependencyMojo.java:232) > at > org.apache.maven.plugin.dependency.UnpackDependenciesMojo.execute(UnpackDependenciesMojo.java:72) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:272) > 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) > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Error unpacking file: > c:\D\desarrollo\proyectos\plataforma\platform-core\target\classes to: > c:\D\desarrollo\proyectos\plataforma\platform-bundle\platform-bundle-jar\target\classes > org.codehaus.plexus.archiver.ArchiverException: The source must not be a > directory. > Project structure is as follows: > plataforma > - platform-core > - platform-bundle > - platform-bundle-jar > - platform-bundle-src > and the error happens on executing any goal from parent pom. > maven-dependency-plugin seems to receive a reference to target/classes > directory for platform-core dependency instead of the URL to my local > repository where platform-core is located. -- 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: (MNG-2565) plugin version aren't taken from pluginManagement in a sub-sub-modules
[ http://jira.codehaus.org/browse/MNG-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100058 ] Emmanuel Venisse commented on MNG-2565: --- I think we can close it, I can't reproduce it with 2.0.6. I don't have tested the issue described by kenney > plugin version aren't taken from pluginManagement in a sub-sub-modules > -- > > Key: MNG-2565 > URL: http://jira.codehaus.org/browse/MNG-2565 > Project: Maven 2 > Issue Type: Bug > Components: Inheritance and Interpolation >Affects Versions: 2.0.5 >Reporter: Emmanuel Venisse >Priority: Critical > Fix For: Reviewed Pending Version Assignment > > > It works only for the first inheritence level -- 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] Updated: (MIDEA-96) generated projects do not load in Selena #7020
[ http://jira.codehaus.org/browse/MIDEA-96?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Perepelytsya updated MIDEA-96: - Attachment: MIDEA-96.patch The attached MIDEA-96 patch cleans up offending commented out sections in module and project templates. Well, the code is in SVN, so those sections could generally be removed safely anyway. It got me moving on in an >80 module project. > generated projects do not load in Selena #7020 > -- > > Key: MIDEA-96 > URL: http://jira.codehaus.org/browse/MIDEA-96 > Project: Maven 2.x IDEA Plugin > Issue Type: Bug >Affects Versions: 2.0 > Environment: maven 2.0.4 > windows > IntelliJ build #7020 >Reporter: zak jacobson > Attachments: MIDEA-96.patch > > > Idea trows an error: > Error during dispatching of > java.awt.event.MouseEvent[MOUSE_RELEASED,(47,53),button=1,modifiers=Button1,clickCount=1] > on ###overrideRedirect###: Wrong node: [Comment: ] > java.lang.IllegalArgumentException: Wrong node: [Comment: ] > at com.intellij.openapi.util.JDOMUtil.internElement(JDOMUtil.java:181) > Manually editing the .iml & .ipr files to remove all comments, such as: > > is a work around. -- 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: (MIDEA-96) generated projects do not load in Selena #7020
[ http://jira.codehaus.org/browse/MIDEA-96?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100053 ] Andrew Perepelytsya commented on MIDEA-96: -- Moreover, Jetbrains rejected this as Won't Fix, so plugin has to handle it. > generated projects do not load in Selena #7020 > -- > > Key: MIDEA-96 > URL: http://jira.codehaus.org/browse/MIDEA-96 > Project: Maven 2.x IDEA Plugin > Issue Type: Bug >Affects Versions: 2.0 > Environment: maven 2.0.4 > windows > IntelliJ build #7020 >Reporter: zak jacobson > > Idea trows an error: > Error during dispatching of > java.awt.event.MouseEvent[MOUSE_RELEASED,(47,53),button=1,modifiers=Button1,clickCount=1] > on ###overrideRedirect###: Wrong node: [Comment: ] > java.lang.IllegalArgumentException: Wrong node: [Comment: ] > at com.intellij.openapi.util.JDOMUtil.internElement(JDOMUtil.java:181) > Manually editing the .iml & .ipr files to remove all comments, such as: > > is a work around. -- 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: (MAVENUPLOAD-1604) release ognl 2.7
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100052 ] Carlos Sanchez commented on MAVENUPLOAD-1604: - can you deploy to opensymphony server maven2.opensymphony.com:/opt/repository/maven2 ? and we'll sync from there http://svn.apache.org/viewvc/maven/archiva/trunk/maven-meeper/src/bin/synchronize/m2-sync/conf/com.opensymphony.sh?view=markup > release ognl 2.7 > > > Key: MAVENUPLOAD-1604 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1604 > Project: maven-upload-requests > Issue Type: Task >Reporter: Jesse Kuhnert > > The 2.7 release has been made to a remote repository which can be found here: > http://opencomponentry.com/repository/m2-ibiblio-sync-repo/ognl/ognl/2.7/ . > The main project web site is http://www.ognl.org, but also > http://opensymphony.com/ognl/ since the project was taken over by > opensymphony. > I haven't yet made any new changes to the actual web site (still syncing with > Patrick) so I'm not listed officially on a team list but am visible as the > project lead here: http://jira.opensymphony.com/browse/OGNL. -- 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] Closed: (MRM-358) Update Consumers button in Database - Artifact Scanning doesn't work
[ http://jira.codehaus.org/browse/MRM-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joakim Erdfelt closed MRM-358. -- Resolution: Fixed Patch applied in trunk. > Update Consumers button in Database - Artifact Scanning doesn't work > > > Key: MRM-358 > URL: http://jira.codehaus.org/browse/MRM-358 > Project: Archiva > Issue Type: Bug >Affects Versions: 1.0-alpha-1 >Reporter: Dawn Angelito >Assignee: Joakim Erdfelt >Priority: Critical > Fix For: 1.0-alpha-2 > > Attachments: MRM-358-archiva-webapp.patch > > > 1) Log in as admin. > 2) Click the Database button in the left menu under Administration. > 3) In Database - Unprocessed Artifacts Scanning, uncheck > "validate-repository-metadata" to disable it. > 4) Click the Update Consumers button. > Once the page is refreshed, notice that "validate-repository-metadata" is > still enabled. > Note: Try the same procedure in Database - Artifact Cleanup Scanning. The > changes made will not be saved. -- 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] Closed: (MAVENUPLOAD-1594) Upload request for tatooine-gtx-0.1.0 to ibiblio
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1594. --- Assignee: Carlos Sanchez Resolution: Incomplete > Upload request for tatooine-gtx-0.1.0 to ibiblio > > > Key: MAVENUPLOAD-1594 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1594 > Project: maven-upload-requests > Issue Type: Task >Reporter: tooru noda >Assignee: Carlos Sanchez > > http://tatooine.sourceforge.jp/gtx/bundle/tatooine-gtx-0.1.0-bundle.jar > http://tatooine.sourceforge.jp/gtx/ > http://sourceforge.jp/project/memberlist.php?group_id=2520 > Please upload! -- 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: (MAVENUPLOAD-1601) Cooee 1.0 Upload
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100048 ] Carlos Sanchez commented on MAVENUPLOAD-1601: - you have to - remove the reposiotries section - provide the parent pom in a separate bundle (or even better create a repository that can be synced from, see http://maven.apache.org/guides/mini/guide-central-repository-upload.html ) > Cooee 1.0 Upload > > > Key: MAVENUPLOAD-1601 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1601 > Project: maven-upload-requests > Issue Type: Task >Reporter: Daniel Murley > > http://www.karora.org/maven-repository/bundles/cooee-1.0-bundle.jar > http://www.karora.org > http://www.karora.org/projects/cooee/team-list.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
[jira] Closed: (MAVENUPLOAD-1602) Upload ZK 2.4.0 to the central repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1602. --- Assignee: Carlos Sanchez Resolution: Fixed Start thinking on creating a synced repo http://maven.apache.org/guides/mini/guide-central-repository-upload.html > Upload ZK 2.4.0 to the central repository > - > > Key: MAVENUPLOAD-1602 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1602 > Project: maven-upload-requests > Issue Type: Task >Reporter: Tom M. Yeh >Assignee: Carlos Sanchez > > http://www.zkoss.org/maven/bundles/2.4.0/zcommon-2.4.0-bundle.jar > http://www.zkoss.org/maven/bundles/2.4.0/zweb-2.4.0-bundle.jar > http://www.zkoss.org/maven/bundles/2.4.0/zk-2.4.0-bundle.jar > http://www.zkoss.org/maven/bundles/2.4.0/zul-2.4.0-bundle.jar > http://www.zkoss.org/maven/bundles/2.4.0/zhtml-2.4.0-bundle.jar > http://www.zkoss.org/maven/bundles/2.4.0/zkplus-2.4.0-bundle.jar > http://www.zkoss.org/maven/bundles/2.4.0/timelinez-1.1_3-bundle.jar > http://www.zkoss.org > http://sourceforge.net/users/tomyeh/ > ZK is an open-source Ajax Web framework that enables rich user interface for > Web applications with no JavaScript and little programming. -- 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] Closed: (MAVENUPLOAD-1603) Upload JIDE Common Layer to maven repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1603. --- Assignee: Carlos Sanchez Resolution: Fixed > Upload JIDE Common Layer to maven repository > > > Key: MAVENUPLOAD-1603 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1603 > Project: maven-upload-requests > Issue Type: Task >Reporter: David Qiao >Assignee: Carlos Sanchez > > JIDE Common Layer is Swing component library built on top of Java/Swing. It > is also the foundation of other component products from JIDE. This project > has over 30 Swing components and over 100k lines of code. It greatly enhanced > the default component set provided by Swing and allow developers to focus on > business logic layer instead of making components. > JIDE Common Layer was originally developed by JIDE Software developers as a > foundation in order to build other more advanced components. In April of > 2007, JIDE Software decided to open source this common layer so that more and > more developers can leverage them instead of wasting time building them > again. > For more information, please visit project home page on JIDE Software website > at http://www.jidesoft.com/products/oss.htm or on java.net at > https://jide-oss.dev.java.net. -- 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] Closed: (MAVENUPLOAD-1605) H2 Database Engine 1.0.20070617
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1605. --- Assignee: Carlos Sanchez Resolution: Fixed > H2 Database Engine 1.0.20070617 > --- > > Key: MAVENUPLOAD-1605 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1605 > Project: maven-upload-requests > Issue Type: Task >Reporter: Toshihiro Nakamura >Assignee: Carlos Sanchez > > H2 Database Engine 1.0.20070617 -- 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] Created: (SUREFIRE-342) Tests fail if JAVA_HOME path contains spaces
Tests fail if JAVA_HOME path contains spaces Key: SUREFIRE-342 URL: http://jira.codehaus.org/browse/SUREFIRE-342 Project: Maven Surefire Issue Type: Bug Affects Versions: 2.4 Environment: Windows XP Reporter: Scott Stephenson Did default install of jdk1.5.0_12 Set JAVA_HOME environment variable to C:\Program Files\Java\jdk1.5.0_12 Did 'mvn clean test' Maven fails with this message: [DEBUG] Using JVM: C:\Program Files\Java\jdk1.5.0_12\jre\bin\java [INFO] Surefire report directory: C:\EclipseProjects\TNManage\target\surefire-reports Forking command line: "C:\Program Files\Java\jdk1.5.0_12\jre\bin\java" -classpath "C:\Documents and Settings\ssteph\.m2\repository\org\codehaus\plexus\plexus-archiver\1.0-alpha-7\plexus-archiver-1.0-alpha-7.jar;C:\Documents and Settings\ssteph\.m2\repository\junit\junit\3.8.1\junit-3.8.1.jar;C:\Documents and Settings\ssteph\.m2\repository\org\codehaus\plexus\plexus-container-default\1.0-alpha-8\plexus-container-default-1.0-alpha-8.jar;C:\Documents and Settings\ssteph\.m2\repository\org\apache\maven\surefire\surefire-booter\2.4-SNAPSHOT\surefire-booter-2.4-SNAPSHOT.jar;C:\Documents and Settings\ssteph\.m2\repository\classworlds\classworlds\1.1-alpha-2\classworlds-1.1-alpha-2.jar;C:\Documents and Settings\ssteph\.m2\repository\org\apache\maven\surefire\surefire-api\2.4-SNAPSHOT\surefire-api-2.4-SNAPSHOT.jar;C:\Documents and Settings\ssteph\.m2\repository\commons-lang\commons-lang\2.1\commons-lang-2.1.jar;C:\Documents and Settings\ssteph\.m2\repository\org\codehaus\plexus\plexus-utils\1.4.1-SNAPSHOT\plexus-utils-1.4.1-SNAPSHOT.jar;C:\Documents and Settings\ssteph\.m2\repository\org\testng\testng\5.5\testng-5.5-jdk15.jar" org.apache.maven.surefire.booter.SurefireBooter C:\DOCUME~1\ssteph\LOCALS~1\Temp\surefire60476tmp C:\DOCUME~1\ssteph\LOCALS~1\Temp\surefire60477tmp 'C:\Program' is not recognized as an internal or external command, operable program or batch file. [ERROR] mojo-execute : surefire:test Diagnosis: There are test failures. FATAL ERROR: Error executing Maven for a project [ERROR] project-execute : edu.washington.cac.rome.tnmanage:TNManage:war:1.0 ( task-segment: [clean, test] ) Diagnosis: There are test failures. FATAL ERROR: Error executing Maven for a project org.apache.maven.BuildFailureException: There are test failures. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:555) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140) at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:441) at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:382) at org.maven.ide.eclipse.Maven2Executor.main(Maven2Executor.java:68) Caused by: org.apache.maven.plugin.MojoFailureException: There are test failures. at org.apache.maven.plugin.surefire.SurefirePlugin.execute(SurefirePlugin.java:424) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534) ... 8 more It fails because of the whitespace in C:\Program Files. I can make it work by copying the JDK to a folder whose name does not contain spaces and point JAVA_HOME to it. When I do this, everything works fine. This isn't a long-term solution though, as it requires a special-case install of the JDK. This seems to be a new bug in the 2.4-SNAPSHOT. We had to move to this because we're using the latest TestNG, which requires it. Before this, we used jUnit with version 2.3 of SUREFIRE and things worked fine. -- 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: (NMAVEN-79) With MICROSOFT still failing with "NMAVEN-9011-007: Mono installation could not be found."
[
http://jira.codehaus.org/browse/NMAVEN-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100040
]
Shane Isbell commented on NMAVEN-79:
I committed that change of
string outputFile = Environment.GetEnvironmentVariable("USERPROFILE") +
"/.m2/nmaven-settings.xml";
within the SettingsGeneratorMojo. There is no need to deal with the alternate
"SYSTEMDRIVE" + "HOMEPATH" because 1) this file is only auto-generated on
Windows (where the userprofile is given) and 2) the registry-config.xml is
specified to look in the ${user.home} which maps to the USERPROFILE.
> With MICROSOFT still failing with "NMAVEN-9011-007: Mono
> installation could not be found."
> ---
>
> Key: NMAVEN-79
> URL: http://jira.codehaus.org/browse/NMAVEN-79
> Project: NMaven
> Issue Type: Bug
> Environment: ALLUSERSPROFILE=C:\Documents and Settings\All Users
> APPDATA=C:\Documents and Settings\bdeacon\Application Data
> ASMROOT=C:\TNGSD\SD
> CLASSPATH=.;C:\Program Files\Java\jre1.5.0_11\lib\ext\QTJava.zip
> CLIENTNAME=Console
> CommonProgramFiles=C:\Program Files\Common Files
> COMPUTERNAME=SDGD04202608
> ComSpec=C:\WINDOWS\system32\cmd.exe
> CVSROOT=:pserver:[EMAIL PROTECTED]:/v/releng/cvsroot
> ERROR_CODE=1
> FP_NO_HOST_CHECK=NO
> HOMEDRIVE=H:
> HOMEPATH=\
> HOMESHARE=\\sdgfs01\users\bdeacon
> Intuit=1
> JAVA_HOME=C:\Program Files\Java\jdk1.5.0_12
> LOGONSERVER=\\SDGDCCORP04
> M2_HOME=C:\Program Files\Apache Software Foundation\maven-2.0.6
> MAVEN_HOME=C:\Program Files\Apache Software Foundation\Maven 1.0.2
> MSILIB=\\SDPSDO05\MSILIB
> NUMBER_OF_PROCESSORS=2
> OS=Windows_NT
> Path=C:\Program
> Files\Java\jdk1.5.0_12\bin;C:\Perl\bin\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\Downloaded
> Program Files;C:\Program Files\Common Files\Roxio
> Shared\DLLShared;C:\TNGSD\BIN;c:\Program Files\Microsoft SQL
> Server\90\Tools\binn\;C:\utils\bin;C:\Program Files\Apache Software
> Foundation\Maven 1.0.2\bin;C:\Program Files\Apache Software
> Foundation\maven-2.0.6\bin;C:\Program Files\cvsnt;C:\Program
> Files\Perforce;C:\Program Files\IDM Computer
> Solutions\UltraEdit-32;C:\mysql5\bin;C:\ruby\bin;C:\Program
> Files\QuickTime\QTSystem\
> PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH
> PROCESSOR_ARCHITECTURE=x86
> PROCESSOR_IDENTIFIER=x86 Family 15 Model 4 Stepping 1, GenuineIntel
> PROCESSOR_LEVEL=15
> PROCESSOR_REVISION=0401
> ProgramFiles=C:\Program Files
> PROMPT=$P$G
> QTJAVA=C:\Program Files\Java\jre1.5.0_11\lib\ext\QTJava.zip
> RUBYOPT=rubygems
> RUBY_HOME=C:\ruby
> SESSIONNAME=Console
> SystemDrive=C:
> SystemRoot=C:\WINDOWS
> TEMP=C:\TEMP
> TMP=C:\TEMP
> USERDNSDOMAIN=CORP.INTUIT.NET
> USERDOMAIN=CORP
> USERNAME=bdeacon
> USERPROFILE=C:\Documents and Settings\bdeacon
> VS80COMNTOOLS=C:\Program Files\Microsoft Visual Studio 8\Common7\Tools\
> windir=C:\WINDOWS
>Reporter: Brian Deacon
> Attachments: build.log, pom.xml, SettingsGeneratorMojo.diff,
> SettingsGeneratorMojo.diff
>
>
> Pom and log output attached.
--
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: (NMAVEN-79) With MICROSOFT still failing with "NMAVEN-9011-007: Mono installation could not be found."
[ http://jira.codehaus.org/browse/NMAVEN-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100039 ] Brian Deacon commented on NMAVEN-79: It occurs to me that since that hunt now involves actually looking at the file system, and so involves some minimal IO, that we might want to have that GetSettingsFilePath done only once as a static class initializer and then just returned from a static variable... but I don't imagine the hit is much of a big deal. Or even just change it to a public static property "SettingsFilePath" that returns the full path to nmaven-settings.xml, and that could become the authoritative source for getting the file name, and we could stop having ".m2" and "nmaven-settings.xml" sprinkled around as literals throughout the code. > With MICROSOFT still failing with "NMAVEN-9011-007: Mono > installation could not be found." > --- > > Key: NMAVEN-79 > URL: http://jira.codehaus.org/browse/NMAVEN-79 > Project: NMaven > Issue Type: Bug > Environment: ALLUSERSPROFILE=C:\Documents and Settings\All Users > APPDATA=C:\Documents and Settings\bdeacon\Application Data > ASMROOT=C:\TNGSD\SD > CLASSPATH=.;C:\Program Files\Java\jre1.5.0_11\lib\ext\QTJava.zip > CLIENTNAME=Console > CommonProgramFiles=C:\Program Files\Common Files > COMPUTERNAME=SDGD04202608 > ComSpec=C:\WINDOWS\system32\cmd.exe > CVSROOT=:pserver:[EMAIL PROTECTED]:/v/releng/cvsroot > ERROR_CODE=1 > FP_NO_HOST_CHECK=NO > HOMEDRIVE=H: > HOMEPATH=\ > HOMESHARE=\\sdgfs01\users\bdeacon > Intuit=1 > JAVA_HOME=C:\Program Files\Java\jdk1.5.0_12 > LOGONSERVER=\\SDGDCCORP04 > M2_HOME=C:\Program Files\Apache Software Foundation\maven-2.0.6 > MAVEN_HOME=C:\Program Files\Apache Software Foundation\Maven 1.0.2 > MSILIB=\\SDPSDO05\MSILIB > NUMBER_OF_PROCESSORS=2 > OS=Windows_NT > Path=C:\Program > Files\Java\jdk1.5.0_12\bin;C:\Perl\bin\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\Downloaded > Program Files;C:\Program Files\Common Files\Roxio > Shared\DLLShared;C:\TNGSD\BIN;c:\Program Files\Microsoft SQL > Server\90\Tools\binn\;C:\utils\bin;C:\Program Files\Apache Software > Foundation\Maven 1.0.2\bin;C:\Program Files\Apache Software > Foundation\maven-2.0.6\bin;C:\Program Files\cvsnt;C:\Program > Files\Perforce;C:\Program Files\IDM Computer > Solutions\UltraEdit-32;C:\mysql5\bin;C:\ruby\bin;C:\Program > Files\QuickTime\QTSystem\ > PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH > PROCESSOR_ARCHITECTURE=x86 > PROCESSOR_IDENTIFIER=x86 Family 15 Model 4 Stepping 1, GenuineIntel > PROCESSOR_LEVEL=15 > PROCESSOR_REVISION=0401 > ProgramFiles=C:\Program Files > PROMPT=$P$G > QTJAVA=C:\Program Files\Java\jre1.5.0_11\lib\ext\QTJava.zip > RUBYOPT=rubygems > RUBY_HOME=C:\ruby > SESSIONNAME=Console > SystemDrive=C: > SystemRoot=C:\WINDOWS > TEMP=C:\TEMP > TMP=C:\TEMP > USERDNSDOMAIN=CORP.INTUIT.NET > USERDOMAIN=CORP > USERNAME=bdeacon > USERPROFILE=C:\Documents and Settings\bdeacon > VS80COMNTOOLS=C:\Program Files\Microsoft Visual Studio 8\Common7\Tools\ > windir=C:\WINDOWS >Reporter: Brian Deacon > Attachments: build.log, pom.xml, SettingsGeneratorMojo.diff, > SettingsGeneratorMojo.diff > > > Pom and log output attached. -- 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: (MSITE-146) Version not printing in strapline
[ http://jira.codehaus.org/browse/MSITE-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100034 ] Tim Pizey commented on MSITE-146: - Patch in DOXIA-121 includes this change, though sets version to "" not "unset version" > Version not printing in strapline > - > > Key: MSITE-146 > URL: http://jira.codehaus.org/browse/MSITE-146 > Project: Maven 2.x Site Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-4 > Environment: linux and XP >Reporter: Tim Pizey > > The maven-site.vm has a missing #else, such that the publishDate macro fails > to print the version. > #if ( $version ) > #if ( $version.position ) > #set ( $versionPosition = $version.position ) > #else > #set ( $versionPosition = "left" ) > #end > #end > could become: > #if ( $version ) > #if ( $version.position ) > #set ( $versionPosition = $version.position ) > #else > #set ( $versionPosition = "left" ) > #end > #else > #set ( $version = "unset version" ) > #set ( $versionPosition = "left" ) > #end > which fixes for me. -- 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] Created: (DOXIA-121) Add titles to hrefs, tweaks to powered by
Add titles to hrefs, tweaks to powered by -- Key: DOXIA-121 URL: http://jira.codehaus.org/browse/DOXIA-121 Project: doxia Issue Type: Improvement Components: Site Renderer Affects Versions: 1.0-alpha-8 Environment: Firefox/WinXP Reporter: Tim Pizey Priority: Trivial Attachments: default-site.patch Add title to banner images, use div not span tags, add else conditions to macros, to fix missing version bug, add size and class to poweredby -- 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] Created: (DOXIA-120) Firefox barfs on text-shadow css
Firefox barfs on text-shadow css Key: DOXIA-120 URL: http://jira.codehaus.org/browse/DOXIA-120 Project: doxia Issue Type: Improvement Components: Site Renderer Affects Versions: 1.0-alpha-8 Environment: Firefox Reporter: Tim Pizey Priority: Trivial Attachments: maven-base.patch Firefox does not like the missing arguments to text-shadow, added three 1px arguments. This has no effect in firefox, other than to stop the error in the error console. -- 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: (MNG-2621) Add stricter pattern filters to maven-common-artifact-filters
[ http://jira.codehaus.org/browse/MNG-2621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100031 ] John Casey commented on MNG-2621: - my apologies, didn't read the patch closely enough. :) > Add stricter pattern filters to maven-common-artifact-filters > - > > Key: MNG-2621 > URL: http://jira.codehaus.org/browse/MNG-2621 > Project: Maven 2 > Issue Type: Improvement > Components: Shared >Reporter: Brian Topping >Assignee: Mark Hobson > Fix For: Shared Components > > Attachments: IncludesArtifactFilter.patch, MNG-2621.patch > > > There is a todo in > http://svn.apache.org/viewvc/maven/components/trunk/maven-artifact/src/main/java/org/apache/maven/artifact/resolver/filter/IncludesArtifactFilter.java?view=markup > to add regex. I checked all the sources and could only find usages of this > code by maven-assembly-plugin, webstart-maven-plugin and exec-maven-plugin. > The latter two are in mojo. > If you look at > http://svn.palle.net/projects/hauskeeper/hauskeeper-server/src/assemblies/debian.xml, > Trygvis is assuming that wildcards work, when in fact they do not. Arguably, > this is a documentation bug that it does not work. > The attached patch fixes this problem. -- 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: (MRM-371) Unable to add a remote repository
[
http://jira.codehaus.org/browse/MRM-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100030
]
Kerstin Klein commented on MRM-371:
---
Hi, I configured an archiva.xml file in ${archiva.home}/conf, it doesn't work
at all.
i put this configuration on it , but there was no possibility to select the
named repository in the archiva gui.
{code:xml}
1
codehaus.org
codehaus.org
http://snapshots.maven.codehaus.org/maven2
default
true
true
false
{code}
where is my mistake?
Thanks,
Kerstin Klein
> Unable to add a remote repository
> -
>
> Key: MRM-371
> URL: http://jira.codehaus.org/browse/MRM-371
> Project: Archiva
> Issue Type: Bug
>Affects Versions: 1.0-alpha-1
>Reporter: Wendy Smoak
>Assignee: Fabrice BELLINGARD
> Fix For: 1.0-alpha-2
>
>
> There is no "Add Repository" link to the right of "Remote Repositories".
> Assuming that the 'Add Repository' link at the top (to the right of "Local
> Repositories") is intended to also add remote repositories, if I supply a URL
> rather than a directory, the new repo does not appear in the list. There is
> no error in the log, it just doesn't happen.
--
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: (DOXIA-86) The results of Site Renderer does not validate (CSS)
[
http://jira.codehaus.org/browse/DOXIA-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100029
]
Tim Pizey commented on DOXIA-86:
Createing an empty one with the test 'put your style overrides here' seesm good.
> The results of Site Renderer does not validate (CSS)
>
>
> Key: DOXIA-86
> URL: http://jira.codehaus.org/browse/DOXIA-86
> Project: doxia
> Issue Type: Bug
> Components: Site Renderer
>Reporter: Dennis Lundberg
>
> When I try to validate the css of a document produced by doxia site renderer
> I get a validation error: "File not found ...". Here is the page that I try
> to validate:
> http://people.apache.org/~dennisl/commons-lang5/userguide.html
> Here are the validation results, having set the css level to 3, which is as
> high as it can be set:
>
> http://jigsaw.w3.org/css-validator/validator?profile=css3&warning=2&uri=http%3A%2F%2Fpeople.apache.org%2F~dennisl%2Fcommons-lang5%2Fuserguide.html
> The default-site.vm has this on line 286:
> @import url("$relativePath/css/site.css");
> However the file css/site.css is never created by either site renderer or the
> 3 skins that are available.
> I see two possible solutions for this. Either remove the line mentioned
> above, but that might have backward-compatibility issues, or add an empty
> "css/site.css" file to the site build.
--
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: (NMAVEN-79) With MICROSOFT still failing with "NMAVEN-9011-007: Mono installation could not be found."
[ http://jira.codehaus.org/browse/NMAVEN-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100026 ] Shane Isbell commented on NMAVEN-79: Thanks Brian! Looking over the patch today. This is becoming more of a high priority since a number of people (including myself) are hitting this issue. > With MICROSOFT still failing with "NMAVEN-9011-007: Mono > installation could not be found." > --- > > Key: NMAVEN-79 > URL: http://jira.codehaus.org/browse/NMAVEN-79 > Project: NMaven > Issue Type: Bug > Environment: ALLUSERSPROFILE=C:\Documents and Settings\All Users > APPDATA=C:\Documents and Settings\bdeacon\Application Data > ASMROOT=C:\TNGSD\SD > CLASSPATH=.;C:\Program Files\Java\jre1.5.0_11\lib\ext\QTJava.zip > CLIENTNAME=Console > CommonProgramFiles=C:\Program Files\Common Files > COMPUTERNAME=SDGD04202608 > ComSpec=C:\WINDOWS\system32\cmd.exe > CVSROOT=:pserver:[EMAIL PROTECTED]:/v/releng/cvsroot > ERROR_CODE=1 > FP_NO_HOST_CHECK=NO > HOMEDRIVE=H: > HOMEPATH=\ > HOMESHARE=\\sdgfs01\users\bdeacon > Intuit=1 > JAVA_HOME=C:\Program Files\Java\jdk1.5.0_12 > LOGONSERVER=\\SDGDCCORP04 > M2_HOME=C:\Program Files\Apache Software Foundation\maven-2.0.6 > MAVEN_HOME=C:\Program Files\Apache Software Foundation\Maven 1.0.2 > MSILIB=\\SDPSDO05\MSILIB > NUMBER_OF_PROCESSORS=2 > OS=Windows_NT > Path=C:\Program > Files\Java\jdk1.5.0_12\bin;C:\Perl\bin\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\Downloaded > Program Files;C:\Program Files\Common Files\Roxio > Shared\DLLShared;C:\TNGSD\BIN;c:\Program Files\Microsoft SQL > Server\90\Tools\binn\;C:\utils\bin;C:\Program Files\Apache Software > Foundation\Maven 1.0.2\bin;C:\Program Files\Apache Software > Foundation\maven-2.0.6\bin;C:\Program Files\cvsnt;C:\Program > Files\Perforce;C:\Program Files\IDM Computer > Solutions\UltraEdit-32;C:\mysql5\bin;C:\ruby\bin;C:\Program > Files\QuickTime\QTSystem\ > PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH > PROCESSOR_ARCHITECTURE=x86 > PROCESSOR_IDENTIFIER=x86 Family 15 Model 4 Stepping 1, GenuineIntel > PROCESSOR_LEVEL=15 > PROCESSOR_REVISION=0401 > ProgramFiles=C:\Program Files > PROMPT=$P$G > QTJAVA=C:\Program Files\Java\jre1.5.0_11\lib\ext\QTJava.zip > RUBYOPT=rubygems > RUBY_HOME=C:\ruby > SESSIONNAME=Console > SystemDrive=C: > SystemRoot=C:\WINDOWS > TEMP=C:\TEMP > TMP=C:\TEMP > USERDNSDOMAIN=CORP.INTUIT.NET > USERDOMAIN=CORP > USERNAME=bdeacon > USERPROFILE=C:\Documents and Settings\bdeacon > VS80COMNTOOLS=C:\Program Files\Microsoft Visual Studio 8\Common7\Tools\ > windir=C:\WINDOWS >Reporter: Brian Deacon > Attachments: build.log, pom.xml, SettingsGeneratorMojo.diff, > SettingsGeneratorMojo.diff > > > Pom and log output attached. -- 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: (MNG-2795) Classloader problem loading a resource from a build extension Jar : difference between 2.0.4 and (future) 2.0.5
[ http://jira.codehaus.org/browse/MNG-2795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100025 ] Julien S commented on MNG-2795: --- I believe I has the same issue as reported by Fabrice, in a very similar setting (own conventions.xml and custom checker). However, the funny part is: mvn checkstyle:checkstyle works mvn site fails with the above error mvn checkstyle:checkstyle site works I should also say and moved my custom jar from an extension to a plugin dependency too. Hope this helps. > Classloader problem loading a resource from a build extension Jar : > difference between 2.0.4 and (future) 2.0.5 > --- > > Key: MNG-2795 > URL: http://jira.codehaus.org/browse/MNG-2795 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.0.5 >Reporter: Fabrice BELLINGARD >Assignee: Jason van Zyl > Fix For: 2.0.5 > > Attachments: Checkstyle-2.0.4.txt, Checkstyle-2.0.5.txt, > Test-BuildExtension.zip > > > I had a problem when executing the Checkstyle plugin (version 2.1) with the > pre-release of Maven 2.0.5. So I dug a bit to see if this could be related to > maven core or not, and here is what I found. > I isolated the code that breaks the build in the checkstyle plugin: it > happens when the plugin tries to load my Checkstyle configuration file, which > is actually located in a JAR that is specified in the build extensions. The > code lies in the Locator#resolveLocation() method: > // Attempt a Resource. > URL url = this.getClass().getClassLoader().getResource( > location ); > This code returns null for the "url" variable, which in turns breaks the > plugin because it doesn't find any configuration file. > I haven't had the time to dig more into it, but I found the following issue > that might be related to this problem: "MNG-2228 : Classloader problem > loading jars from build extensions". Brett and Carlos worked on it and fixed > it, so maybe they could tell more about it. > I attached the logs of the execution with Maven 2.0.4 (which works fine) and > Maven 2.0.5 (which breaks). I haven't had the time yet to dig further into > that problem. -- 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] Created: (NMAVEN-80) Support for batch builds of multiple projects in VIsual Studio 2005
Support for batch builds of multiple projects in VIsual Studio 2005 Key: NMAVEN-80 URL: http://jira.codehaus.org/browse/NMAVEN-80 Project: NMaven Issue Type: Improvement Environment: Windows Reporter: Shane Isbell Priority: Minor The user should be able to select multiple projects within VIsual Studio 2005 and have NMaven build them as a batch. NMaven should be able to resolve the dependency order dynamically. -- 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] Updated: (MAVEN-1267) create source distribution for Maven 1.0 as part of installer process
[ http://jira.codehaus.org/browse/MAVEN-1267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl updated MAVEN-1267: - Assignee: Arnaud Heritier Affects Version/s: 1.1-rc1 Fix Version/s: 1.1 > create source distribution for Maven 1.0 as part of installer process > - > > Key: MAVEN-1267 > URL: http://jira.codehaus.org/browse/MAVEN-1267 > Project: Maven 1 > Issue Type: Task > Components: installer >Affects Versions: 1.1-rc1 >Reporter: Brett Porter >Assignee: Arnaud Heritier > Fix For: 1.1 > > > currently build several binaries, but no source distribution -- 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: (MSITE-211) Can't deploy site using site:deploy due to a ProxyHTTP error
[ http://jira.codehaus.org/browse/MSITE-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100024 ] Yves Van Steen commented on MSITE-211: -- I also have some problems with the beta-5. I'm getting an error "Server string invalid" When removing my proxy declaration all is fine. This error seems only to occur when using the beta-5. beta-4 is fine. The specific error comes from the jsch package which provides ssh support. The trouble is propably the proxy information that is injected in this Session class of the jsch package but the non proxy information is never checked in the wagon scpwagon class which initializes it. > Can't deploy site using site:deploy due to a ProxyHTTP error > > > Key: MSITE-211 > URL: http://jira.codehaus.org/browse/MSITE-211 > Project: Maven 2.x Site Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-5 > Environment: linux ubuntu dapper drake >Reporter: Elid OR >Priority: Blocker > > When I execute the site deployment (with version that comes with maven 2.0.5) > "mvn site:deploy " I got an error see log en debug mode below. This used to > work correctly with maven version 2.04 (so maybe site plugin version > 2.0-beta-4 : > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Error uploading site > Embedded error: Cannot connect. Reason: ProxyHTTP: java.io.IOException: proxy > error: Forbidden > [INFO] > > [DEBUG] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: Error uploading site > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:330) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:123) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:272) > 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.apache.maven.plugin.MojoExecutionException: Error uploading > site > at > org.apache.maven.plugins.site.SiteDeployMojo.execute(SiteDeployMojo.java:184) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:420) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) > ... 16 more > Caused by: org.apache.maven.wagon.authentication.AuthenticationException: > Cannot connect. Reason: ProxyHTTP: java.io.IOException: proxy error: > Forbidden > at > org.apache.maven.wagon.providers.ssh.jsch.AbstractJschWagon.openConnection(AbstractJschWagon.java:186) > at > org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:143) > at > org.apache.maven.plugins.site.SiteDeployMojo.execute(SiteDeployMojo.java:149) > ... 18 more > Caused by: com.jcraft.jsch.JSchException: ProxyHTTP: java.io.IOException: > proxy error: Forbidden > at com.jcraft.jsch.ProxyHTTP.connect(Unknown Source) > at com.jcraft.jsch.Session.connect(Unknown Source) > at com.jcraft.jsch.Session.connect(Unknown Source) > at > org.apache.maven.wagon.providers.ssh.jsch.AbstractJschWagon.openConnection(AbstractJschWagon.java:158) > ... 20 more > [INFO] > > [INFO] Total time: 3 seconds > [INFO] Finished at: Wed Feb 21 12:00:41 CET 2007 > [INFO] Final Me
[jira] Updated: (CONTINUUM-44) multiple profiles
[ http://jira.codehaus.org/browse/CONTINUUM-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-44: -- Assignee: Emmanuel Venisse Fix Version/s: (was: 1.1-alpha-#) 1.1-alpha-3 Great work, thanks Olivier > multiple profiles > - > > Key: CONTINUUM-44 > URL: http://jira.codehaus.org/browse/CONTINUUM-44 > Project: Continuum > Issue Type: New Feature > Components: Core - Profiles >Reporter: Brett Porter >Assignee: Emmanuel Venisse > Fix For: 1.1-alpha-3 > > Attachments: CONTINUUM-44, CONTINUUM-44, > CONTINUUM-44-continuum-data-management, > CONTINUUM-44-continuum-data-management, CONTINUUM-44-LICENSE-REFORMATED > > > would like to be able to define a profile (which can include certain > environmental things such as the version of m2 to use, the JDK version, etc). > Profiles should be able to be used globally, per group or per project. In > this way, you could build certain projects under a variety of different JDKs > for example. -- 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] Closed: (CONTINUUM-1291) In a special configuration the report mail can contains false java version used for the build
[ http://jira.codehaus.org/browse/CONTINUUM-1291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse closed CONTINUUM-1291. --- Assignee: Emmanuel Venisse Resolution: Fixed Fix Version/s: 1.1-alpha-3 Patch provided in CONTINUUM-44 is applied. > In a special configuration the report mail can contains false java version > used for the build > - > > Key: CONTINUUM-1291 > URL: http://jira.codehaus.org/browse/CONTINUUM-1291 > Project: Continuum > Issue Type: New Feature >Affects Versions: 1.1-alpha-1 > Environment: using continuum with tomcat on a solaris machine >Reporter: Olivier Lamy >Assignee: Emmanuel Venisse > Fix For: 1.1-alpha-3 > > > I have installed the webapp on a tomcat. > The catalina.sh contains a forced JAVA_HOME (1.6). > Whereas the user JAVA_HOME (setted in .profile) contains a different one > (1.4). > The mail report says : > Operating system : SunOS(unknown) > Java version : 1.6.0(Sun Microsystems Inc.) > Whereas the real JAVA_HOME (because the maven build is launched with a cli) > is the one defined in the .profile. > This can cause an other trouble if I set the target in the > maven-compiler-plugin with 1.5. > I see the in the mail : > Java version : 1.6.0(Sun Microsystems Inc.) > And at the end of the report I can see : > javac: invalid target release: 1.5 > More generally It could to be nice to have something which can define > different JAVA_HOME per projectGroup and/or project. > I will try to provide a patch for the mail report (not today because I have > some jobs). > Do not hesitate to ping me if I don't do this :D -- 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: (CONTINUUM-44) multiple profiles
[ http://jira.codehaus.org/browse/CONTINUUM-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100020 ] Emmanuel Venisse commented on CONTINUUM-44: --- Patch committed. We'll close this issue when all other patches will be provided/applied too > multiple profiles > - > > Key: CONTINUUM-44 > URL: http://jira.codehaus.org/browse/CONTINUUM-44 > Project: Continuum > Issue Type: New Feature > Components: Core - Profiles >Reporter: Brett Porter > Fix For: 1.1-alpha-# > > Attachments: CONTINUUM-44, CONTINUUM-44, > CONTINUUM-44-continuum-data-management, > CONTINUUM-44-continuum-data-management, CONTINUUM-44-LICENSE-REFORMATED > > > would like to be able to define a profile (which can include certain > environmental things such as the version of m2 to use, the JDK version, etc). > Profiles should be able to be used globally, per group or per project. In > this way, you could build certain projects under a variety of different JDKs > for example. -- 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: (MRM-371) Unable to add a remote repository
[ http://jira.codehaus.org/browse/MRM-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100019 ] Wendy Smoak commented on MRM-371: - Kerstin, you can pre-configure the repositories in the archiva.xml file. > Unable to add a remote repository > - > > Key: MRM-371 > URL: http://jira.codehaus.org/browse/MRM-371 > Project: Archiva > Issue Type: Bug >Affects Versions: 1.0-alpha-1 >Reporter: Wendy Smoak >Assignee: Fabrice BELLINGARD > Fix For: 1.0-alpha-2 > > > There is no "Add Repository" link to the right of "Remote Repositories". > Assuming that the 'Add Repository' link at the top (to the right of "Local > Repositories") is intended to also add remote repositories, if I supply a URL > rather than a directory, the new repo does not appear in the list. There is > no error in the log, it just doesn't happen. -- 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] Created: (MRELEASE-253) AIOOB exception on release:prepare
AIOOB exception on release:prepare -- Key: MRELEASE-253 URL: http://jira.codehaus.org/browse/MRELEASE-253 Project: Maven 2.x Release Plugin Issue Type: Bug Reporter: Milos Kleint I've tried to do a nbm-maven-plugin 2.5 release (project at mojo.codehaus.org) with the release:prepare goal. got this rather "symbolic" error message. :) [INFO] [ERROR] FATAL ERROR [INFO] [INFO] 42 [INFO] full output along with stacktrace. [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'release'. WAGON_VERSION: 1.0-beta-2 [INFO] [INFO] Building NBM Maven Plugin [INFO]task-segment: [release:prepare] (aggregator-style) [INFO] [INFO] [release:prepare] [INFO] Resuming release from phase 'rewrite-poms-for-release' [INFO] Transforming 'NBM Maven Plugin'... [INFO] [ERROR] FATAL ERROR [INFO] [INFO] 42 [INFO] [INFO] Trace java.lang.ArrayIndexOutOfBoundsException: 42 at org.apache.maven.shared.release.phase.RewritePomsForReleasePhase.translateUrlPath(RewritePomsForReleasePhase.java:249) at org.apache.maven.shared.release.phase.RewritePomsForReleasePhase.translateScm(RewritePomsForReleasePhase.java:124) at org.apache.maven.shared.release.phase.RewritePomsForReleasePhase.transformScm(RewritePomsForReleasePhase.java:79) at org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.transformDocument(AbstractRewritePomsPhase.java:271) at org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.transformProject(AbstractRewritePomsPhase.java:180) at org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.transform(AbstractRewritePomsPhase.java:116) at org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.execute(AbstractRewritePomsPhase.java:99) at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:194) at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:131) at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:94) at org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:127) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:420) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:224) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:330) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:123) at org.apache.maven.cli.MavenCli.main(MavenCli.java:272) 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:597) 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) [INFO] [INFO] Total time: 3 seconds [INFO] Finished at: Tue Jun 19 15:37:58 CEST 2007 [INFO] Final Memory: 6M/11M [INFO] -- -- 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: (MEAR-69) Both ejb-client and ejb JARs of the same artifact are included
[ http://jira.codehaus.org/browse/MEAR-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100015 ] Stefan Seidel commented on MEAR-69: --- Of course it is somewhere in the dependencies - transitively. It is just common practice: typically, an EAR consists of EJBs and WARs. The WARs have dependencies on the EJB as ejb-client (because they only need to access the interfaces), and thus there are transitive dependencies of type ejb-client in the EAR project. Can you give me one example where ejb and ejb-client need to be included in the same EAR? In fact, this will most likely violate class loading constraints, because the same class files are present twice. I know that I can exclude them with module tags, but this seems much more of a workaround. > Both ejb-client and ejb JARs of the same artifact are included > -- > > Key: MEAR-69 > URL: http://jira.codehaus.org/browse/MEAR-69 > Project: Maven 2.x Ear Plugin > Issue Type: Bug >Affects Versions: 2.3, 2.3.1 >Reporter: Stefan Seidel >Assignee: Stephane Nicoll >Priority: Minor > > When the dependencies of the EAR include both the ejb and > ejb-client dependencies of the same artifact, both JAR files are > included in the EAR - which really doesn't make much sense to me, as all > files of the client-jar should be included in the ejb-jar 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
[jira] Updated: (MEAR-35) Generate id for modules in application.xml
[ http://jira.codehaus.org/browse/MEAR-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeroen Leenarts updated MEAR-35: Attachment: MEAR-35-maven-ear-plugin-2.patch The current work-around I am using right now. (we're running an inhouse repository by overriding central) It's a bit different compared to the earlier patch. With this patch I can use a "moduleId" element within my ejbModule items. I've done this for the ejbModule only because this is just a proof of concept. > Generate id for modules in application.xml > -- > > Key: MEAR-35 > URL: http://jira.codehaus.org/browse/MEAR-35 > Project: Maven 2.x Ear Plugin > Issue Type: Improvement >Reporter: Manikandan Balasubramanian >Priority: Minor > Fix For: 2.4 > > Attachments: MEAR-35-maven-ear-plugin-2.patch, > MEAR-35-maven-ear-plugin.patch > > > When the ear plugin generates application.xml, it should generate an "id" > with each module. This "id" is according to application.xml schema. > This would help eclipse plugin to generate correct eclipse metedata. -- 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] Created: (MSITE-237) Empty modules list generated when using '--non-recursive' flag for single module projects
Empty modules list generated when using '--non-recursive' flag for single
module projects
-
Key: MSITE-237
URL: http://jira.codehaus.org/browse/MSITE-237
Project: Maven 2.x Site Plugin
Issue Type: Bug
Affects Versions: 2.0-beta-5
Reporter: Fernando Lindner
Priority: Critical
Attachments: sample-project.zip
Using '--non-recursive' flag for a single module project causes site's modules
list to be empty.
When starting a new project it's usual to have just one module for a while.
It seems to be a problem in *org.apache.maven.plugins.site.AbstractSiteMojo"
class, inside {{populateModulesMenuItemsFromModels}} method, when
{{models.size()}} is checked.
{code:title=AbstractSiteMojo.java|borderStyle=solid}
...
private void populateModulesMenuItemsFromModels( List models, Menu menu )
{
if ( models != null && models.size() > 1 )
{
Iterator reactorItr = models.iterator();
while ( reactorItr.hasNext() )
{
Model model = (Model) reactorItr.next();
String reactorUrl = model.getUrl();
String name = model.getName();
appendMenuItem( menu, name, reactorUrl, model.getArtifactId() );
}
}
}
...
{code}
A single project is attached, for testing purposes.
No errors when omitting '--non-recursive' flag:
{{mvn clean site}}
--
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: (MEAR-35) Generate id for modules in application.xml
[ http://jira.codehaus.org/browse/MEAR-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100011 ] Jeroen Leenarts commented on MEAR-35: - I've ran into this problem as well. Here is the use-case I am dealing with. The module ID's are used by IBM application server 5.1 (and 6.1 for that matter) to wire up all security roles and EJBs. While I won't be doing any security administration myself. I do have to provide unique id's to modules. > Generate id for modules in application.xml > -- > > Key: MEAR-35 > URL: http://jira.codehaus.org/browse/MEAR-35 > Project: Maven 2.x Ear Plugin > Issue Type: Improvement >Reporter: Manikandan Balasubramanian >Priority: Minor > Fix For: 2.4 > > Attachments: MEAR-35-maven-ear-plugin.patch > > > When the ear plugin generates application.xml, it should generate an "id" > with each module. This "id" is according to application.xml schema. > This would help eclipse plugin to generate correct eclipse metedata. -- 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] Updated: (CONTINUUM-44) multiple profiles
[ http://jira.codehaus.org/browse/CONTINUUM-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated CONTINUUM-44: -- Attachment: CONTINUUM-44-LICENSE-REFORMATED New patch (note the file name :-) ). I have made some test on solaris and work fine as expected (fix my use case CONTINUUM-1291). I will provide other patchs for other points (gui validation) > multiple profiles > - > > Key: CONTINUUM-44 > URL: http://jira.codehaus.org/browse/CONTINUUM-44 > Project: Continuum > Issue Type: New Feature > Components: Core - Profiles >Reporter: Brett Porter > Fix For: 1.1-alpha-# > > Attachments: CONTINUUM-44, CONTINUUM-44, > CONTINUUM-44-continuum-data-management, > CONTINUUM-44-continuum-data-management, CONTINUUM-44-LICENSE-REFORMATED > > > would like to be able to define a profile (which can include certain > environmental things such as the version of m2 to use, the JDK version, etc). > Profiles should be able to be used globally, per group or per project. In > this way, you could build certain projects under a variety of different JDKs > for example. -- 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: (MEAR-69) Both ejb-client and ejb JARs of the same artifact are included
[ http://jira.codehaus.org/browse/MEAR-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_18 ] Stephane Nicoll commented on MEAR-69: - you say so by including both in your project's dependencies. It's bad to handle that kind of use cases because it might make sense for somebody else. If you don't want it, don't set it as a dependency, period. > Both ejb-client and ejb JARs of the same artifact are included > -- > > Key: MEAR-69 > URL: http://jira.codehaus.org/browse/MEAR-69 > Project: Maven 2.x Ear Plugin > Issue Type: Bug >Affects Versions: 2.3, 2.3.1 >Reporter: Stefan Seidel >Assignee: Stephane Nicoll >Priority: Minor > > When the dependencies of the EAR include both the ejb and > ejb-client dependencies of the same artifact, both JAR files are > included in the EAR - which really doesn't make much sense to me, as all > files of the client-jar should be included in the ejb-jar 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
[jira] Commented: (MEAR-69) Both ejb-client and ejb JARs of the same artifact are included
[ http://jira.codehaus.org/browse/MEAR-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_17 ] Stefan Seidel commented on MEAR-69: --- I think this is very well an issue. Can you in any way justify having the same artifact included twice in the EAR? > Both ejb-client and ejb JARs of the same artifact are included > -- > > Key: MEAR-69 > URL: http://jira.codehaus.org/browse/MEAR-69 > Project: Maven 2.x Ear Plugin > Issue Type: Bug >Affects Versions: 2.3, 2.3.1 >Reporter: Stefan Seidel >Assignee: Stephane Nicoll >Priority: Minor > > When the dependencies of the EAR include both the ejb and > ejb-client dependencies of the same artifact, both JAR files are > included in the EAR - which really doesn't make much sense to me, as all > files of the client-jar should be included in the ejb-jar 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
[jira] Closed: (MEAR-69) Both ejb-client and ejb JARs of the same artifact are included
[ http://jira.codehaus.org/browse/MEAR-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephane Nicoll closed MEAR-69. --- Resolution: Won't Fix Not an issue. Please control your dependencies. http://maven.apache.org/plugins/maven-ear-plugin/modules.html Use the excluded flag to exclude it if you don't want to change your dependencies. > Both ejb-client and ejb JARs of the same artifact are included > -- > > Key: MEAR-69 > URL: http://jira.codehaus.org/browse/MEAR-69 > Project: Maven 2.x Ear Plugin > Issue Type: Bug >Affects Versions: 2.3, 2.3.1 >Reporter: Stefan Seidel >Priority: Minor > > When the dependencies of the EAR include both the ejb and > ejb-client dependencies of the same artifact, both JAR files are > included in the EAR - which really doesn't make much sense to me, as all > files of the client-jar should be included in the ejb-jar 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
[jira] Commented: (MRM-371) Unable to add a remote repository
[ http://jira.codehaus.org/browse/MRM-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_15 ] Fabrice BELLINGARD commented on MRM-371: Kerstin, which alpha are you using? This bug was fixed on trunk, and will be available only in next release (1.0-alpha-2). If you're using alpha-1, then I suggest you build Archiva from trunk so that you can test this. > Unable to add a remote repository > - > > Key: MRM-371 > URL: http://jira.codehaus.org/browse/MRM-371 > Project: Archiva > Issue Type: Bug >Affects Versions: 1.0-alpha-1 >Reporter: Wendy Smoak >Assignee: Fabrice BELLINGARD > Fix For: 1.0-alpha-2 > > > There is no "Add Repository" link to the right of "Remote Repositories". > Assuming that the 'Add Repository' link at the top (to the right of "Local > Repositories") is intended to also add remote repositories, if I supply a URL > rather than a directory, the new repo does not appear in the list. There is > no error in the log, it just doesn't happen. -- 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: (MRM-371) Unable to add a remote repository
[ http://jira.codehaus.org/browse/MRM-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12 ] Kerstin Klein commented on MRM-371: --- hi guys, in result of MRM-239 I've decided to migrate to the 1.0-alpha, now I get this problem, too. is there any hint how to edit manually or an useful workarround for this issue? > Unable to add a remote repository > - > > Key: MRM-371 > URL: http://jira.codehaus.org/browse/MRM-371 > Project: Archiva > Issue Type: Bug >Affects Versions: 1.0-alpha-1 >Reporter: Wendy Smoak >Assignee: Fabrice BELLINGARD > Fix For: 1.0-alpha-2 > > > There is no "Add Repository" link to the right of "Remote Repositories". > Assuming that the 'Add Repository' link at the top (to the right of "Local > Repositories") is intended to also add remote repositories, if I supply a URL > rather than a directory, the new repo does not appear in the list. There is > no error in the log, it just doesn't happen. -- 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] Created: (CONTINUUM-1320) DefaultBuildController.makeAndStoreBuildResult cannot save build result due to maximum size of COMMAND_LINE
DefaultBuildController.makeAndStoreBuildResult cannot save build result due to maximum size of COMMAND_LINE --- Key: CONTINUUM-1320 URL: http://jira.codehaus.org/browse/CONTINUUM-1320 Project: Continuum Issue Type: Bug Affects Versions: 1.1-alpha-2 Environment: Continuum with Perforce SCM Reporter: Matthias Wurm Since the maven perforce scm provider creates temporary client specs with a long name (see below), the checkout command gets quite long, too, and hence cannot be save in the COMMAND_LINE column due to the maximum size of 256. Here is the stack trace: 2007-06-19 13:06:40,122 [Thread-6] ERROR TaskQueueExecutor:build-project - Error executing task edu.emory.mathcs.backport.java.util.concurrent.ExecutionException: javax.jdo.JDOFatalUserException: Attempt to store value "p4 -d /home/continuum/local/continuum-1.1-alpha-2/apps/continuum/webapp/WEB-INF/working-directory/1 -p perforce.mycompany.com:1666 -cperforce-host.mycompany.com-MavenSCM-\home\continuum\local\continuum-1.1-alpha-2\apps\continuum\webapp\WEB-INF\working-directory\1 sync" in column "COMMAND_LINE" that has maximum length of 256. Please correct your data! at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.getResult(FutureTask.java:299) at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.get(FutureTask.java:128) at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable.waitForTask(ThreadedTaskQueueExecutor.java:165) at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable.run(ThreadedTaskQueueExecutor.java:127) Caused by: javax.jdo.JDOFatalUserException: Attempt to store value "p4 -d /home/continuum/local/continuum-1.1-alpha-2/apps/continuum/webapp/WEB-INF/working-directory/1 -p perforce.mycompany.com:1666 -cperforce-host.mycompany.com-MavenSCM-\home\continuum\local\continuum-1.1-alpha-2\apps\continuum\webapp\WEB-INF\working-directory\1 sync" in column "COMMAND_LINE" that has maximum length of 256. Please correct your data! at org.jpox.store.rdbms.mapping.CharRDBMSMapping.setString(CharRDBMSMapping.java:214) at org.jpox.store.mapping.SingleFieldMapping.setString(SingleFieldMapping.java:203) at org.jpox.store.rdbms.fieldmanager.ParameterSetter.storeStringField(ParameterSetter.java:122) at org.jpox.state.StateManagerImpl.providedStringField(StateManagerImpl.java:2757) at org.apache.maven.continuum.model.scm.ScmResult.jdoProvideField(ScmResult.java) at org.apache.maven.continuum.model.scm.ScmResult.jdoProvideFields(ScmResult.java) at org.jpox.state.StateManagerImpl.provideFields(StateManagerImpl.java:3115) at org.jpox.store.rdbms.request.InsertRequest.execute(InsertRequest.java:252) at org.jpox.store.rdbms.table.ClassTable.insert(ClassTable.java:2519) at org.jpox.store.StoreManager.insert(StoreManager.java:920) at org.jpox.state.StateManagerImpl.internalMakePersistent(StateManagerImpl.java:3667) at org.jpox.state.StateManagerImpl.makePersistent(StateManagerImpl.java:3646) at org.jpox.AbstractPersistenceManager.internalMakePersistent(AbstractPersistenceManager.java:1198) at org.jpox.AbstractPersistenceManager.makePersistentInternal(AbstractPersistenceManager.java:1243) at org.jpox.store.mapping.PersistenceCapableMapping.setObject(PersistenceCapableMapping.java:450) at org.jpox.store.rdbms.fieldmanager.ParameterSetter.storeObjectField(ParameterSetter.java:144) at org.jpox.state.StateManagerImpl.providedObjectField(StateManagerImpl.java:2771) at org.apache.maven.continuum.model.project.BuildResult.jdoProvideField(BuildResult.java) at org.apache.maven.continuum.model.project.BuildResult.jdoProvideFields(BuildResult.java) at org.jpox.state.StateManagerImpl.provideFields(StateManagerImpl.java:3115) at org.jpox.store.rdbms.request.InsertRequest.execute(InsertRequest.java:252) at org.jpox.store.rdbms.table.ClassTable.insert(ClassTable.java:2519) at org.jpox.store.StoreManager.insert(StoreManager.java:920) at org.jpox.state.StateManagerImpl.internalMakePersistent(StateManagerImpl.java:3667) at org.jpox.state.StateManagerImpl.makePersistent(StateManagerImpl.java:3646) at org.jpox.AbstractPersistenceManager.internalMakePersistent(AbstractPersistenceManager.java:1198) at org.jpox.AbstractPersistenceManager.makePersistent(AbstractPersistenceManager.java:1261) at org.codehaus.plexus.jdo.PlexusJdoUtils.makePersistent(PlexusJdoUtils.java:175) at org.apache.maven.continuum.store.JdoContinuumStore.makePersistent(JdoContinuumStore.java:714) at org.apache.maven.continuum.store.JdoContinuumStor
[jira] Closed: (MNG-2621) Add stricter pattern filters to maven-common-artifact-filters
[ http://jira.codehaus.org/browse/MNG-2621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hobson closed MNG-2621. Resolution: Fixed Fix Version/s: (was: 2.0.x) Shared Components Applied patch to maven-common-artifact-filters with John's suggestions: new filters are called StrictPatternIncludesArtifactFilter and StrictPatternExcludesArtifactFilter. > Add stricter pattern filters to maven-common-artifact-filters > - > > Key: MNG-2621 > URL: http://jira.codehaus.org/browse/MNG-2621 > Project: Maven 2 > Issue Type: Improvement > Components: Shared >Reporter: Brian Topping >Assignee: Mark Hobson > Fix For: Shared Components > > Attachments: IncludesArtifactFilter.patch, MNG-2621.patch > > > There is a todo in > http://svn.apache.org/viewvc/maven/components/trunk/maven-artifact/src/main/java/org/apache/maven/artifact/resolver/filter/IncludesArtifactFilter.java?view=markup > to add regex. I checked all the sources and could only find usages of this > code by maven-assembly-plugin, webstart-maven-plugin and exec-maven-plugin. > The latter two are in mojo. > If you look at > http://svn.palle.net/projects/hauskeeper/hauskeeper-server/src/assemblies/debian.xml, > Trygvis is assuming that wildcards work, when in fact they do not. Arguably, > this is a documentation bug that it does not work. > The attached patch fixes this problem. -- 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] Updated: (MNG-2621) Add stricter pattern filters to maven-common-artifact-filters
[ http://jira.codehaus.org/browse/MNG-2621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hobson updated MNG-2621: - Assignee: Mark Hobson (was: John Casey) Summary: Add stricter pattern filters to maven-common-artifact-filters (was: IncludesArtifactFilter in maven-artifact should accept wildcards) Updated issue title to reflect current direction. > Add stricter pattern filters to maven-common-artifact-filters > - > > Key: MNG-2621 > URL: http://jira.codehaus.org/browse/MNG-2621 > Project: Maven 2 > Issue Type: Improvement > Components: Shared >Reporter: Brian Topping >Assignee: Mark Hobson > Fix For: 2.0.x > > Attachments: IncludesArtifactFilter.patch, MNG-2621.patch > > > There is a todo in > http://svn.apache.org/viewvc/maven/components/trunk/maven-artifact/src/main/java/org/apache/maven/artifact/resolver/filter/IncludesArtifactFilter.java?view=markup > to add regex. I checked all the sources and could only find usages of this > code by maven-assembly-plugin, webstart-maven-plugin and exec-maven-plugin. > The latter two are in mojo. > If you look at > http://svn.palle.net/projects/hauskeeper/hauskeeper-server/src/assemblies/debian.xml, > Trygvis is assuming that wildcards work, when in fact they do not. Arguably, > this is a documentation bug that it does not work. > The attached patch fixes this problem. -- 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: (CONTINUUM-44) multiple profiles
[ http://jira.codehaus.org/browse/CONTINUUM-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_2 ] Olivier Lamy commented on CONTINUUM-44: --- Ok for license format. I'm using eclipse file format found here http://maven.apache.org/developers/committer-environment.html. What can I do better ? I will provide an other patch with the non reformated license. But I don't really understand the trouble with import ? (again I use eclipse provided format file). > multiple profiles > - > > Key: CONTINUUM-44 > URL: http://jira.codehaus.org/browse/CONTINUUM-44 > Project: Continuum > Issue Type: New Feature > Components: Core - Profiles >Reporter: Brett Porter > Fix For: 1.1-alpha-# > > Attachments: CONTINUUM-44, CONTINUUM-44, > CONTINUUM-44-continuum-data-management, CONTINUUM-44-continuum-data-management > > > would like to be able to define a profile (which can include certain > environmental things such as the version of m2 to use, the JDK version, etc). > Profiles should be able to be used globally, per group or per project. In > this way, you could build certain projects under a variety of different JDKs > for example. -- 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] Updated: (MNG-3036) NullPointerException when eclipse jars are marked as "provided"
[ http://jira.codehaus.org/browse/MNG-3036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Leggett updated MNG-3036: Attachment: npe-fix.patch The attached patch fixes the NullPointerException. > NullPointerException when eclipse jars are marked as "provided" > --- > > Key: MNG-3036 > URL: http://jira.codehaus.org/browse/MNG-3036 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies >Affects Versions: 2.0.6 >Reporter: Graham Leggett > Fix For: Reviewed Pending Version Assignment > > Attachments: npe-fix.patch, pom.xml > > > When a pde artifact is built that transitively depends on some eclipse jars, > and an attempt is made to filter out those eclipse jars by marking the scope > as provided, maven NPEs during eclipse:eclipse as follows: > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] null > [INFO] > > [INFO] Trace > java.lang.NullPointerException > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:164) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:334) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:334) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:334) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:334) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:334) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:75) > at > org.apache.maven.plugin.ide.AbstractIdeSupportMojo.doDependencyResolution(AbstractIdeSupportMojo.java:447) > at > org.apache.maven.plugin.ide.AbstractIdeSupportMojo.execute(AbstractIdeSupportMojo.java:398) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:272) > 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) > [INFO] > > [INFO] Total time: 6 seconds > [INFO] Finished at: Tue Jun 05 19:00:22 BST 2007 > [INFO] Final Memory: 7M/13M > [INFO] > -- 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: (MNG-1957) clause in the activation section has to provide more complex expressions.
[ http://jira.codehaus.org/browse/MNG-1957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99983 ] Tim Hedger commented on MNG-1957: - VersionRange syntax doesn't support the ! negation syntax that the current tag allows. Maximum reusability/simplicity here will be to use the existing VersionRange syntax (as you mention Eric used for dependency versions), but for backwards compatibility on that would mean allowing ! to be used in dependency versions. Is this OK? > clause in the activation section has to provide more complex > expressions. > - > > Key: MNG-1957 > URL: http://jira.codehaus.org/browse/MNG-1957 > Project: Maven 2 > Issue Type: Improvement > Components: POM >Affects Versions: 2.0, 2.0.1 >Reporter: Trustin Lee > Fix For: 2.0.x > > > For now, provides only one operator '!' which means negation, but > it would be great if i can use '+' and ~ operator: > 1.5+ > 1.1 ~ 1.4 > ~ 1.3 > 1.4 ~ -- 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: (CONTINUUM-44) multiple profiles
[ http://jira.codehaus.org/browse/CONTINUUM-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99982 ] Emmanuel Venisse commented on CONTINUUM-44: --- Your patch isn't correct, I can't apply it. Please don't reformat the license in files and don't change the import order. > multiple profiles > - > > Key: CONTINUUM-44 > URL: http://jira.codehaus.org/browse/CONTINUUM-44 > Project: Continuum > Issue Type: New Feature > Components: Core - Profiles >Reporter: Brett Porter > Fix For: 1.1-alpha-# > > Attachments: CONTINUUM-44, CONTINUUM-44, > CONTINUUM-44-continuum-data-management, CONTINUUM-44-continuum-data-management > > > would like to be able to define a profile (which can include certain > environmental things such as the version of m2 to use, the JDK version, etc). > Profiles should be able to be used globally, per group or per project. In > this way, you could build certain projects under a variety of different JDKs > for example. -- 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: (MNG-2621) IncludesArtifactFilter in maven-artifact should accept wildcards
[ http://jira.codehaus.org/browse/MNG-2621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99979 ] Mark Hobson commented on MNG-2621: -- Hi John, sure I can add this to maven-common-artifact-filters directly. I'll assign this to myself, refactor the code as mentioned above and commit, if that's okay? I'm not sure I understand you regarding point (1), the for-loop will be short-circuited since matched will be false. > IncludesArtifactFilter in maven-artifact should accept wildcards > > > Key: MNG-2621 > URL: http://jira.codehaus.org/browse/MNG-2621 > Project: Maven 2 > Issue Type: Improvement > Components: Shared >Reporter: Brian Topping >Assignee: John Casey > Fix For: 2.0.x > > Attachments: IncludesArtifactFilter.patch, MNG-2621.patch > > > There is a todo in > http://svn.apache.org/viewvc/maven/components/trunk/maven-artifact/src/main/java/org/apache/maven/artifact/resolver/filter/IncludesArtifactFilter.java?view=markup > to add regex. I checked all the sources and could only find usages of this > code by maven-assembly-plugin, webstart-maven-plugin and exec-maven-plugin. > The latter two are in mojo. > If you look at > http://svn.palle.net/projects/hauskeeper/hauskeeper-server/src/assemblies/debian.xml, > Trygvis is assuming that wildcards work, when in fact they do not. Arguably, > this is a documentation bug that it does not work. > The attached patch fixes this problem. -- 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] Created: (CONTINUUM-1319) Add a link to the project web page when available.
Add a link to the project web page when available. -- Key: CONTINUUM-1319 URL: http://jira.codehaus.org/browse/CONTINUUM-1319 Project: Continuum Issue Type: Improvement Components: Web interface Reporter: Julien S Priority: Minor On the group summary page, a icon link to the project WEB page would be a worthwhile addition, when the project URL is known (e.g. for Maven1 / 2). -- 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] Created: (CONTINUUM-1318) Add the ability to use different colors for SNAPSHOT and stable projects
Add the ability to use different colors for SNAPSHOT and stable projects Key: CONTINUUM-1318 URL: http://jira.codehaus.org/browse/CONTINUUM-1318 Project: Continuum Issue Type: Improvement Components: Web - UI Affects Versions: 1.1-alpha-2 Reporter: Julien S Priority: Minor When you want to release a large project, it really helps to be able to figure in a glimpse which projects are in development, so it would be nice if the lines corresponding to "SNAPSHOT" projects were in a different color. -- 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: (MNG-2979) Cross module dependencies for multi-module site
[ http://jira.codehaus.org/browse/MNG-2979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99975 ] Stepan Roh commented on MNG-2979: - I believe this is not a missing feature, but a bug. If in the chain of called goals is some with "@requiresDependencyResolution compile" then it works (e.g. compilation during compile phase in default lifecycle) otherwise it does not - can be tested by calling "mvn compile site". > Cross module dependencies for multi-module site > --- > > Key: MNG-2979 > URL: http://jira.codehaus.org/browse/MNG-2979 > Project: Maven 2 > Issue Type: Improvement > Components: Artifacts and Repositories >Affects Versions: 2.0.5 > Environment: Linux 2.6.18-gentoo-r6 #2 SMP PREEMPT Wed Feb 28 > 10:25:50 CET 2007 i686 Pentium III (Coppermine) GenuineIntel GNU/Linux >Reporter: Wally Wallou >Priority: Minor > Fix For: Reviewed Pending Version Assignment > > Attachments: gwttk-m2.zip, package.txt, site.txt > > > Considering a multi-module project A which declares two sub-projects > (modules) B and C. Having module C indicating in its POM a dependency against > module B. Compilation and packaging work great without having to install > module B in maven local repository, it locate module B for module C using > declared aggregation at top level project A. > But for site goals it does not work, that is to say when maven try to > generate site for module C it tells that module B artifact cannot be found. > So we have to install module B to be able to generate module C site, whereas > it is not necessary for compile or package goals. > I think it would be great if site goals behaves like compile and package with > aggregation. It would be more coherent, and avoid to have to run install just > for site goals. -- 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] Created: (MEAR-69) Both ejb-client and ejb JARs of the same artifact are included
Both ejb-client and ejb JARs of the same artifact are included -- Key: MEAR-69 URL: http://jira.codehaus.org/browse/MEAR-69 Project: Maven 2.x Ear Plugin Issue Type: Bug Affects Versions: 2.3, 2.3.1 Reporter: Stefan Seidel Priority: Minor When the dependencies of the EAR include both the ejb and ejb-client dependencies of the same artifact, both JAR files are included in the EAR - which really doesn't make much sense to me, as all files of the client-jar should be included in the ejb-jar 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
[jira] Created: (WAGONSSH-58) SFTP deploy creates wrong target dir
SFTP deploy creates wrong target dir Key: WAGONSSH-58 URL: http://jira.codehaus.org/browse/WAGONSSH-58 Project: wagon-ssh Issue Type: Bug Environment: Maven-1.1-RC1, wagon-ssh-1.0-beta-2 Reporter: Lukas Theussl Using the m11 artifact plugin to deploy via sftp, I have the following setting: maven.repo.R2.directory=/home/qopt/theussl/maven/sftp If initially the maven/sftp/ dir does not exist in my home dir, the deploy fails with a TransferFailedException and no useful error message. However, the above directory tree is created in my home dir, ie /home/qopt/theussl/home/qopt/theussl/maven/ If I create the target directory by hand, the deploy succeeds, the files are put in the correct locations, but the empty dummy directory in my home dir is still created. -- 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] Closed: (CONTINUUM-1316) Hitting 'Add' button repetitively in adding an Ant, Shell and Schedule using empty string only accumulates validation prompts in IE browser
[ http://jira.codehaus.org/browse/CONTINUUM-1316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse closed CONTINUUM-1316. --- Assignee: Emmanuel Venisse Resolution: Fixed Fix Version/s: 1.1-alpha-3 Applied. Thanks. > Hitting 'Add' button repetitively in adding an Ant, Shell and Schedule using > empty string only accumulates validation prompts in IE browser > --- > > Key: CONTINUUM-1316 > URL: http://jira.codehaus.org/browse/CONTINUUM-1316 > Project: Continuum > Issue Type: Bug > Components: Web - UI >Affects Versions: 1.1-alpha-3 > Environment: windows XP, IE >Reporter: jan ancajas >Assignee: Emmanuel Venisse >Priority: Minor > Fix For: 1.1-alpha-3 > > Attachments: CONTINUUM-1316-continuum-webapp.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
