[jira] Created: (MRELEASE-103) No SCM URL was provided to perform the release from
No SCM URL was provided to perform the release from --- Key: MRELEASE-103 URL: http://jira.codehaus.org/browse/MRELEASE-103 Project: Maven 2.x Release Plugin Type: Bug Environment: solaris Reporter: Olivier Lamy Priority: Blocker Attachments: olamy.tar.gz The stack trace says : DEBUG] Trace org.apache.maven.BuildFailureException: No SCM URL was provided to perform the release from at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor .java:555) I included a test case with multi modules project (you need to change scm url in all poms to complete the test). Strange because all scm parts are filled in all modules. To test it, I launch ./buildis.sh $svnuser $svnpwd Olivier -- 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: (MRELEASE-103) No SCM URL was provided to perform the release from
[ http://jira.codehaus.org/browse/MRELEASE-103?page=comments#action_65002 ] Olivier Lamy commented on MRELEASE-103: --- I fixed it by adding : -DconnectionUrl=scm:svn:http://57.200.0.197:7770/Accommons/olamy/trunk \ in the script buildis.sh. Strange this should be setted with developerConnection from the root pom ? Olivier > No SCM URL was provided to perform the release from > --- > > Key: MRELEASE-103 > URL: http://jira.codehaus.org/browse/MRELEASE-103 > Project: Maven 2.x Release Plugin > Type: Bug > Environment: solaris > Reporter: Olivier Lamy > Priority: Blocker > Attachments: olamy.tar.gz > > > The stack trace says : > DEBUG] Trace > org.apache.maven.BuildFailureException: No SCM URL was provided to perform > the release from > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor > .java:555) > I included a test case with multi modules project (you need to change scm url > in all poms to complete the test). > Strange because all scm parts are filled in all modules. > To test it, I launch ./buildis.sh $svnuser $svnpwd > Olivier -- 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: (MRELEASE-103) No SCM URL was provided to perform the release from
[ http://jira.codehaus.org/browse/MRELEASE-103?page=comments#action_65003 ] Olivier Lamy commented on MRELEASE-103: --- If it's required it should be set @required in the mojo ? > No SCM URL was provided to perform the release from > --- > > Key: MRELEASE-103 > URL: http://jira.codehaus.org/browse/MRELEASE-103 > Project: Maven 2.x Release Plugin > Type: Bug > Environment: solaris > Reporter: Olivier Lamy > Priority: Blocker > Attachments: olamy.tar.gz > > > The stack trace says : > DEBUG] Trace > org.apache.maven.BuildFailureException: No SCM URL was provided to perform > the release from > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor > .java:555) > I included a test case with multi modules project (you need to change scm url > in all poms to complete the test). > Strange because all scm parts are filled in all modules. > To test it, I launch ./buildis.sh $svnuser $svnpwd > Olivier -- 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: (MECLIPSE-105) deploy gives NPE in wagon-ftp
deploy gives NPE in wagon-ftp - Key: MECLIPSE-105 URL: http://jira.codehaus.org/browse/MECLIPSE-105 Project: Maven 2.x Eclipse Plugin Type: Bug Environment: Win 2000 Pro, Sun JDK 1.5.0_06, Maven 2.0.4, Eclipse 3.2 RC2, org.maven.ide.eclipse_0.0.7 Reporter: Mauritz Lovgren Attachments: command.log, eclipse.log When running deploy goal for pom containing ftp deployment, the following NPE is thrown just as files are starting to push to ftp server: [INFO] deploy:deploy [DEBUG] not adding permissions to wagon connection java.lang.NullPointerException at org.apache.maven.wagon.providers.ftp.FtpWagon.openConnection(FtpWagon.java:127) at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:143) at org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:178) at org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:109) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:77) at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:131) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534) 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) This problem does not occur when running mvn deploy in command prompt. I notice a small difference in debug output from Eclipse / command prompt that might be something? Eclipse: [DEBUG] Found 0 components to load on start [DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and Settings\t539537\.m2\plugin-registry.xml' [DEBUG] Building Maven global-level settings from: 'C:\dev\ws\ic-sntdispatcher\conf\settings.xml' [DEBUG] Building Maven user-level settings from: 'C:\Documents and Settings\t539537\.m2\settings.xml' [DEBUG] Profile with id: 'default-profile' has been explicitly activated. [DEBUG] Profile with id: 'default-profile' has been explicitly activated. Command prompt: [DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and Settings\t539537\.m2\plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: 'C:\Program Files\maven-2.0.2\conf\plugin-registry.xml' [INFO] Scanning for projects... I have defined ftp server credentials in user home ./m2/settings.xml. Could it be that these credentials are not found when running in Eclipse Maven2 plugin? This is not a critical error for me, as I can just deploy using command prompt, but nice to have it all inside Eclipse you know :-)... Attached debug logs for command and Eclipse run of same pom. Hope you find something in the logs that is helpful. Regards, Mauritz -- 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: (MRELEASE-103) No SCM URL was provided to perform the release from
[ http://jira.codehaus.org/browse/MRELEASE-103?page=comments#action_65006 ] Brett Porter commented on MRELEASE-103: --- it reads it from the release.properties like the previous version did, but I can add it. > No SCM URL was provided to perform the release from > --- > > Key: MRELEASE-103 > URL: http://jira.codehaus.org/browse/MRELEASE-103 > Project: Maven 2.x Release Plugin > Type: Bug > Environment: solaris > Reporter: Olivier Lamy > Priority: Blocker > Attachments: olamy.tar.gz > > > The stack trace says : > DEBUG] Trace > org.apache.maven.BuildFailureException: No SCM URL was provided to perform > the release from > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor > .java:555) > I included a test case with multi modules project (you need to change scm url > in all poms to complete the test). > Strange because all scm parts are filled in all modules. > To test it, I launch ./buildis.sh $svnuser $svnpwd > Olivier -- 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: (MIDEA-53) copyright line endings are written incorrectly since changing to dom4j
[ http://jira.codehaus.org/browse/MIDEA-53?page=all ] Brett Porter closed MIDEA-53: - Assign To: Brett Porter Resolution: Cannot Reproduce Fix Version: (was: 2.0) I must have been using the old version > copyright line endings are written incorrectly since changing to dom4j > -- > > Key: MIDEA-53 > URL: http://jira.codehaus.org/browse/MIDEA-53 > Project: Maven 2.x Idea Plugin > Type: Bug > Versions: 2.0 > Reporter: Brett Porter > Assignee: Brett Porter > > > it all ends up on one line when rewriting. -- 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: (MRELEASE-103) No SCM URL was provided to perform the release from
[ http://jira.codehaus.org/browse/MRELEASE-103?page=all ] Brett Porter updated MRELEASE-103: -- Fix Version: 2.0-beta-4 > No SCM URL was provided to perform the release from > --- > > Key: MRELEASE-103 > URL: http://jira.codehaus.org/browse/MRELEASE-103 > Project: Maven 2.x Release Plugin > Type: Bug > Environment: solaris > Reporter: Olivier Lamy > Priority: Blocker > Fix For: 2.0-beta-4 > Attachments: olamy.tar.gz > > > The stack trace says : > DEBUG] Trace > org.apache.maven.BuildFailureException: No SCM URL was provided to perform > the release from > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor > .java:555) > I included a test case with multi modules project (you need to change scm url > in all poms to complete the test). > Strange because all scm parts are filled in all modules. > To test it, I launch ./buildis.sh $svnuser $svnpwd > Olivier -- 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: (MRELEASE-103) No SCM URL was provided to perform the release from
[ http://jira.codehaus.org/browse/MRELEASE-103?page=comments#action_65009 ] Olivier Lamy commented on MRELEASE-103: --- Ok for fix version. But just to know what will we do : - add it in release.properties during release:prepare - set @required in the mojo Note it's not really a bug but just a user convenience ;-). The plugin works like a charm. Olivier > No SCM URL was provided to perform the release from > --- > > Key: MRELEASE-103 > URL: http://jira.codehaus.org/browse/MRELEASE-103 > Project: Maven 2.x Release Plugin > Type: Bug > Environment: solaris > Reporter: Olivier Lamy > Priority: Blocker > Fix For: 2.0-beta-4 > Attachments: olamy.tar.gz > > > The stack trace says : > DEBUG] Trace > org.apache.maven.BuildFailureException: No SCM URL was provided to perform > the release from > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor > .java:555) > I included a test case with multi modules project (you need to change scm url > in all poms to complete the test). > Strange because all scm parts are filled in all modules. > To test it, I launch ./buildis.sh $svnuser $svnpwd > Olivier -- 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: (MIDEA-30) Bad/missing settings for generated web app module
[ http://jira.codehaus.org/browse/MIDEA-30?page=all ] Brett Porter closed MIDEA-30: - Assign To: Brett Porter Resolution: Fixed > Bad/missing settings for generated web app module > - > > Key: MIDEA-30 > URL: http://jira.codehaus.org/browse/MIDEA-30 > Project: Maven 2.x Idea Plugin > Type: Bug > Reporter: Aaron Mulder > Assignee: Brett Porter > Fix For: 2.0 > Attachments: MIDEA-30.patch > > > I generated an Idea project for an EAR with several modules including an EJB > JAR and WAR. > The generated web app module has a web.xml location of > modules/web/src/main/webapp/WEB-INF/web.xml and a web resource directory of > modules/web/src/main/webapp as / > However, I have my webapp in src/webapp (not src/main/webapp) using: > > > org.apache.maven.plugins > maven-war-plugin > > src/webapp > > > > Also, the app server was not populated for the web app module. > Finally, the web app module has a dependency on the EJB module. In the > generated project, that was reflected as the web app module having a library > reference to the EJB output JAR. It would be much better to reflect that as > a dependency of the web app module on the EJB module, so that way any changes > to the source of the EJB module would immediately be visible to the web app > module, instead of waiting for a build/synchronize project cycle. > Thanks! -- 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: (MRELEASE-103) No SCM URL was provided to perform the release from
[ http://jira.codehaus.org/browse/MRELEASE-103?page=comments#action_65010 ] Brett Porter commented on MRELEASE-103: --- 1) is already done 2) would negate the use of 1) What I will do: - if it is null and not in the release properties, read it from the project configuration > No SCM URL was provided to perform the release from > --- > > Key: MRELEASE-103 > URL: http://jira.codehaus.org/browse/MRELEASE-103 > Project: Maven 2.x Release Plugin > Type: Bug > Environment: solaris > Reporter: Olivier Lamy > Priority: Blocker > Fix For: 2.0-beta-4 > Attachments: olamy.tar.gz > > > The stack trace says : > DEBUG] Trace > org.apache.maven.BuildFailureException: No SCM URL was provided to perform > the release from > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor > .java:555) > I included a test case with multi modules project (you need to change scm url > in all poms to complete the test). > Strange because all scm parts are filled in all modules. > To test it, I launch ./buildis.sh $svnuser $svnpwd > Olivier -- 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: (MIDEA-50) StringIndexOutOfBoundsException when adding a resource to the pom
[ http://jira.codehaus.org/browse/MIDEA-50?page=all ] Brett Porter closed MIDEA-50: - Assign To: Brett Porter Resolution: Fixed already fixed > StringIndexOutOfBoundsException when adding a resource to the pom > - > > Key: MIDEA-50 > URL: http://jira.codehaus.org/browse/MIDEA-50 > Project: Maven 2.x Idea Plugin > Type: Bug > Reporter: Tim Kettler > Assignee: Brett Porter > Fix For: 2.0 > Attachments: testprj.zip > > > When running 'mvn idea:idea' on the attached test project the plugin fails > with the following exception: > [ERROR] FATAL ERROR > [INFO] > > [INFO] String index out of range: -1 > [INFO] > > [INFO] Trace > java.lang.StringIndexOutOfBoundsException: String index out of range: -1 > at java.lang.String.substring(String.java:1768) > at java.lang.String.substring(String.java:1735) > at org.apache.maven.plugin.idea.IdeaMojo.toRelative(IdeaMojo.java:395) > at > org.apache.maven.plugin.idea.IdeaMojo.getModuleFileUrl(IdeaMojo.java:409) > at > org.apache.maven.plugin.idea.IdeaMojo.addSourceFolder(IdeaMojo.java:382) > at > org.apache.maven.plugin.idea.IdeaMojo.rewriteModule(IdeaMojo.java:255) > at org.apache.maven.plugin.idea.IdeaMojo.execute(IdeaMojo.java:79) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:415) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:531) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:485) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:455) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:303) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:270) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:139) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > [INFO] > > [INFO] Total time: 1 second > [INFO] Finished at: Fri Apr 14 10:46:22 CEST 2006 > [INFO] Final Memory: 1M/4M > [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] Closed: (MIDEA-49) WebModuleProperties reactor modules: adding with method 5 not compatible with /WEB-INF/classes
[ http://jira.codehaus.org/browse/MIDEA-49?page=all ]
Brett Porter closed MIDEA-49:
-
Assign To: Brett Porter
Resolution: Fixed
committed, thanks!
> WebModuleProperties reactor modules: adding with method 5 not compatible with
> /WEB-INF/classes
> --
>
> Key: MIDEA-49
> URL: http://jira.codehaus.org/browse/MIDEA-49
> Project: Maven 2.x Idea Plugin
> Type: Bug
> Versions: 2.0
> Reporter: Manfred Geiler
> Assignee: Brett Porter
> Fix For: 2.0
> Attachments: MIDEA-49-1.patch, MIDEA-49-2.patch
>
>
> Currently reactor project modules are added with method "5":
> if ( linkModules && isReactorProject( artifact.getGroupId(),
> artifact.getArtifactId() ) )
> {
> containerElement.addAttribute( "type", "module" );
> containerElement.addAttribute( "name",
> artifact.getArtifactId() );
> Element methodAttribute = createElement( containerElement,
> "attribute" );
> methodAttribute.addAttribute( "name", "method" );
> methodAttribute.addAttribute( "value", "5" );
> <
> Element uriAttribute = createElement( containerElement,
> "attribute" );
> uriAttribute.addAttribute( "name", "URI" );
> uriAttribute.addAttribute( "value", "/WEB-INF/classes" );
> }
> Well, method "5" seems to be "JAR module output and copy file to" in IDEA.
> This method is not compatible with the given URI attribute, which should
> rather be something like "/WEB-INF/lib/foobar.jar".
> So, one way to fix this is to use method "1" ("Copy module output to")
> instead, then the used URI is correct. -->See patch 1.
> Another (more maven-style way) is to fix the URI to be "/WEB-INF/lib/" +
> artifact.getArtifactId() + "-" + artifact.getVersion() + ".jar". -->See patch
> 2.
> Regards,
> Manfred
--
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-33) Use path variables instead of absolute path to the Maven repository
[ http://jira.codehaus.org/browse/MIDEA-33?page=all ] Brett Porter updated MIDEA-33: -- Fix Version: (was: 2.0) dropping from 2.0 since there is still an open question on the patch, and because it looks like it might be better suited to sharing the ide classes with eclipse which is the next phase of development > Use path variables instead of absolute path to the Maven repository > --- > > Key: MIDEA-33 > URL: http://jira.codehaus.org/browse/MIDEA-33 > Project: Maven 2.x Idea Plugin > Type: New Feature > Reporter: Aleksandr Tarutin > Attachments: MIDEA-33.patch, maven-idea-plugin-1.patch, > maven-idea-plugin.patch > > > IDEA can use variables just as well as Eclipse. They can be configured from > the Path Variables screen in the configuration and used in the .ipr or .iml > files as $M2_REPO$. -- 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: (MAVENUPLOAD-884) dnsjava 2.0.1 bundle import
dnsjava 2.0.1 bundle import --- Key: MAVENUPLOAD-884 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-884 Project: maven-upload-requests Type: Task Reporter: Stefano Bagnara I added few informations (license, url) to the pom.xml that is already in maven2 repository for old releases. I left the dnsjava groupid to be consistent with previous releases. If you prefer I can resubmit this in the "org.xbill" groupid (same of the package) or "org.dnsjava" groupid (as the sitename). -- 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: (MASSEMBLY-70) assembly:directory does not honor
[ http://jira.codehaus.org/browse/MASSEMBLY-70?page=all ]
Trygve Laugstol closed MASSEMBLY-70:
Resolution: Fixed
Fix Version: 2.1
This was fixed a while back.
> assembly:directory does not honor
>
>
> Key: MASSEMBLY-70
> URL: http://jira.codehaus.org/browse/MASSEMBLY-70
> Project: Maven 2.x Assembly Plugin
> Type: Bug
> Versions: 2.0.1
> Environment: Linux 2.6.10-gentoo-r4 #1 SMP Mon Jan 10 14:53:56 EST 2005 i686
> AMD Athlon(tm) MP 2400+ AuthenticAMD GNU/Linux
> java version "1.4.2_10"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_10-b03)
> Java HotSpot(TM) Client VM (build 1.4.2_10-b03, mixed mode)
> Reporter: Andrew Moore
> Assignee: Trygve Laugstol
> Fix For: 2.1
>
>
> When running {{assembly:assembly}}, the {{}} specified in the
> assembly descriptor [[#1]] is honored in the resulting archive [[#2]].
> When running {{assembly:directory}}, the {{}} is not honored in the
> resulting directory structure [[#3]].
> {anchor:1}
> {code:xml|title=Listing 1: package.xml}
>
> package
>
> tar.gz
>
> false
>
>
> target
> /lib
>
> *.jar
>
> 0640
>
>
> src/main/shell/bin
> /bin
>
> **/*
>
> 0750
>
>
> src/main/shell/environments
> /environments
>
> **/*
>
> 0640
>
>
> src/main/shell/etc
> /etc
>
> **/*
>
> 0640
>
>
>
>
> /lib
> runtime
> 0640
>
>
>
> {code}
> {anchor:2}
> {code:title=Listing 2: target/nabpoc-b1_0_0001-package.tar.gz}
> $ tar -tvzf target/nabpoc-b1_0_0001-package.tar.gz
> drwxr-xr-x / 0 2006-02-16 10:23:40 environments/databases/
> -rw-r- /257398 2006-02-16 10:56:41 lib/nabpoc-b1_0_0001.jar
> ...
> -rwxr-x--- / 1152 2006-02-16 10:23:40 bin/sting
> -rwxr-x--- / 392 2006-02-16 10:23:40 bin/distra
> -rwxr-x--- / 578 2006-02-16 10:23:40 bin/get_classpath
> -rwxr-x--- / 1545 2006-02-16 10:23:40 bin/set_rate
> -rwxr-x--- / 1817 2006-02-16 10:23:40 bin/sting.bat
> -rw-r- / 1570 2006-02-16 10:23:40
> environments/databases/lab-installation.xml
> -rw-r- / 729 2006-02-16 10:23:40 environments/nabpoc.xml
> -rw-r- / 990 2006-02-16 10:23:40 environments/systest.xml
> -rw-r- / 3084 2006-02-16 10:23:41 etc/switch.conf
> -rw-r- / 2820 2006-02-16 10:23:41 etc/sim.conf
> -rw-r- / 1523 2006-02-16 10:23:41 etc/distra.conf
> -rw-r- / 1322 2006-02-16 10:23:41 etc/harouter.conf
> {code}
> {anchor:3}
> {code:title=Listing 3: target/nabpoc-b1_0_0001-package/}
> files under bin/ should be rwxr-x--- as in tar.gz, above
> $ find target/nabpoc-b1_0_0001-package -ls
> 25964120 drwxr-sr-x 6 amm coders152 Feb 16 11:02
> target/nabpoc-b1_0_0001-package
> 25964620 drwxr-sr-x 2 amm coders184 Feb 16 11:02
> target/nabpoc-b1_0_0001-package/bin
> 25964634 -rw-r--r-- 1 amm coders 1152 Feb 16 11:02
> target/nabpoc-b1_0_0001-package/bin/sting
> 25964644 -rw-r--r-- 1 amm coders392 Feb 16 11:02
> target/nabpoc-b1_0_0001-package/bin/distra
> 25964654 -rw-r--r-- 1 amm coders578 Feb 16 11:02
> target/nabpoc-b1_0_0001-package/bin/get_classpath
> 25964664 -rw-r--r-- 1 amm coders 1545 Feb 16 11:02
> target/nabpoc-b1_0_0001-package/bin/set_rate
> 25964674 -rw-r--r-- 1 amm coders 1817 Feb 16 11:02
> target/nabpoc-b1_0_0001-package/bin/sting.bat
> 25964720 drwxr-sr-x 2 amm coders168 Feb 16 11:02
> target/nabpoc-b1_0_0001-package/etc
> 25964734 -rw-r--r-- 1 amm coders 3084 Feb 16 11:02
> target/nabpoc-b1_0_0001-package/etc/switch.conf
> 25964744 -rw-r--r-- 1 amm coders 2820 Feb 16 11:02
> target/nabpoc-b1_0_0001-package/etc/sim.conf
> 25964754 -rw-r--r-- 1 amm coders 1523 Feb 16 11:02
> target/nabpoc-b1_0_0001-package/etc/distra.conf
> 25964794 -rw-r--r-- 1 amm coders 1322 Feb 16 11:02
> target/nabpoc-b1_0_0001-package/etc/harouter.conf
> 25964201 drwxr-sr-x 2 amm coders 1616 Feb 16 11:02
> target/nabpoc-b1_0_0001-package/lib
> 2596459 252 -rw-r--r-- 1 amm coders 257398 Feb 16 11:02
> target/nabpoc-b1_0_0001-package/lib/nabpoc-b1_0_0001.jar
> ...
> 25964140 drwxr-sr-x 3 amm coders144 Feb 16 11:02
> target/nabpoc-b1_0_0001-package/environments
> 25964190 drwxr-sr-x 2 amm coders 88 Feb 16 11:02
> target/nabpoc-b1_0_0001-package/environments/databases
> 25964684 -rw-r--r-- 1 amm coders 1570 Feb 16 11:02
[jira] Created: (SCM-196) scm:update doesn't reuse developerConnection when connection not defined.
scm:update doesn't reuse developerConnection when connection not defined. - Key: SCM-196 URL: http://jira.codehaus.org/browse/SCM-196 Project: Maven SCM Type: Improvement Components: maven-scm-provider-svn, maven-plugin Environment: mvn 2.0.4 scm: 1.0-20060505.091301-5 svn 1.3.1 Reporter: Jerome Lacoste I am using mvn scm:update in a project without a connection (but with a developerConnectino) and scm:update fails: [INFO] -- [ERROR] BUILD ERROR [INFO] -- [INFO] Cannot run checkout command : Embedded error: Can't load the scm provider. You need to define a connectionUrl parameter [INFO] -- The plugin should use the developerConnection when no connection has been defined. Otherwise that forces one to copy the developerConnection into the connection one which defeats DRY and the fact that the connection represents a read-only element. Not sure if that problem is subversion dependent or not, so I selected both the plugin and the svn specific component. -- 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: (MJAR-41) Cannot specify additional classpath entries in jar manifest when using addClasspath
Cannot specify additional classpath entries in jar manifest when using addClasspath --- Key: MJAR-41 URL: http://jira.codehaus.org/browse/MJAR-41 Project: Maven 2.x Jar Plugin Type: Bug Versions: 2.1, 2.0 Environment: Maven 2.0.4, maven-jar-plugin 2.0 and 2.1-SNAPSHOT, JDK 1.5.0_06, Windows XP Reporter: Fredrik Vraalsen The plugin configuration snippet below leads to the generation of an illegal jar manifest file, as it contains two Class-Path entries. This works in Maven 1.1b2 by adding the following to project.properties: maven.jar.manifest.classpath.add=true maven.jar.classpath=help/ resources/ For more information, please see http://www.nabble.com/classpath-in-jar-manifest-t1582724.html org.apache.maven.plugins maven-jar-plugin true help/ resources/ -- 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-2284) Cannot specify additional classpath entries in manifest when using addClasspath
Cannot specify additional classpath entries in manifest when using addClasspath --- Key: MNG-2284 URL: http://jira.codehaus.org/browse/MNG-2284 Project: Maven 2 Type: Bug Components: maven-archiver Versions: 2.0, 2.0.1, 2.0.2, 2.0.3, 2.0.4 Environment: Maven 2.0.4, maven-jar-plugin 2.0 and 2.1-SNAPSHOT, JDK 1.5.0_06, Windows XP Reporter: Fredrik Vraalsen Attachments: MNG-archiver-classpath.patch When using addClasspath, e.g. in the maven-jar-plugin, it is not possible to add additional classpath entries using manifestEntries, as this generates an illegal manifest file (contains two Class-Path entries). Please see http://jira.codehaus.org/browse/MJAR-41 I have been looking through the code, and it seems this might need to be resolved in MavenArchiver? I've attached a simple fix that solves the problem for me, but a more thorough solution might be needed of course. ;-) -- 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: (MJAR-41) Cannot specify additional classpath entries in jar manifest when using addClasspath
[ http://jira.codehaus.org/browse/MJAR-41?page=comments#action_65018 ] Fredrik Vraalsen commented on MJAR-41: -- See http://jira.codehaus.org/browse/MNG-2284 for a simple patch that solved the issue for me. > Cannot specify additional classpath entries in jar manifest when using > addClasspath > --- > > Key: MJAR-41 > URL: http://jira.codehaus.org/browse/MJAR-41 > Project: Maven 2.x Jar Plugin > Type: Bug > Versions: 2.1, 2.0 > Environment: Maven 2.0.4, maven-jar-plugin 2.0 and 2.1-SNAPSHOT, JDK > 1.5.0_06, Windows XP > Reporter: Fredrik Vraalsen > > > The plugin configuration snippet below leads to the generation of an illegal > jar manifest file, as it contains two Class-Path entries. This works in > Maven 1.1b2 by adding the following to project.properties: > maven.jar.manifest.classpath.add=true > maven.jar.classpath=help/ resources/ > For more information, please see > http://www.nabble.com/classpath-in-jar-manifest-t1582724.html > > org.apache.maven.plugins > maven-jar-plugin > > > > true > > > help/ resources/ > > > > -- 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-2258) Wrong execution order of plugins in same phase
[ http://jira.codehaus.org/browse/MNG-2258?page=comments#action_65019 ] Fredrik Vraalsen commented on MNG-2258: --- I'm having the same problem. I need to run two plugins in the generate-sources phase, where one depends on the output of the other. For more information, please see http://www.nabble.com/Plugin-execution-order-within-lifecycle-phase-t1541372.html#a4187121 > Wrong execution order of plugins in same phase > -- > > Key: MNG-2258 > URL: http://jira.codehaus.org/browse/MNG-2258 > Project: Maven 2 > Type: Bug > Versions: 2.0.4 > Environment: N/A > Reporter: David J. M. Karlsen > > > AFAIK plugins should be execute in the same order as they are listed in the > POM, when bound to the same phase. This does not happen, the execution order > is arbitrary. -- 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-129) modules list empty if modules don't use this project as parent in reactor build
modules list empty if modules don't use this project as parent in reactor build
---
Key: MSITE-129
URL: http://jira.codehaus.org/browse/MSITE-129
Project: Maven 2.x Site Plugin
Type: Bug
Versions: 2.0-beta-5
Reporter: Kenney Westerhof
Assigned to: Kenney Westerhof
Priority: Minor
The code in the AbstractSiteRenderingMojo does the following:
- if it's running in a reactor build (i.e. more than 1 project in the reactor
projects) it scans all
projects to see if it's parent project equals the current project. If so, it's
marked as a module.
- if it's running on a single project, the project.build.modules is consulted
and those modules
are marked as modules.
I've got a 'fake' root pom, for utility purposes: it lists all projects as
modules so that I can easily
built everything and generate a site. However, this fake root pom is never used
as a parent - there's
a /pom/pom.xml project for that.
The result of this is that the modules list is empty.
A workaround is to first run 'mvn site' and then 'mvn site -N'.
I'm not sure what the correct solution should be - basically now 2 site layouts
are implemented:
- a physical layout where the modules match the section of the pom,
reflecting filesystem layout,
- a project hierarchy layout based on
and one or the other is used depending on wheter the build contains more than 1
project or not.
My first feeling is that since the tag is called ${modules} (or ) that
the site should use the , not the .
It should also take into consideration, that IF a reactor build is running, it
should only use the modules that are also
in the reactor (so you can use -r -Dmaven.reactor.excludes=.. to generate a
site with not all projects in it).
Thoughts?
--
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-41) Source attachments are maintained when running idea:idea
[ http://jira.codehaus.org/browse/MIDEA-41?page=comments#action_65029 ]
Brett Porter commented on MIDEA-41:
---
the patch unfortunately didn't work:
1) on windows, urls didn't match due to case changes
2) -DdownloadSources=true no longer added sources that weren't there (it
wouldn't change an existing element).
I did this, and simplified it at the same time. Algorithm is now:
1) map out all the urls in the IML
2) loop through artifacts. Never replace an entire element, but
modify it
2a) if artifact is in IML, replace classes
2b) if downloading sources, replace existing SOURCES (but only if sources are
found remotely)
2c) if downloading javadocs, replace existing JAVADOC (but only if javadocs
are found remotely)
3) remove any dependencies in IML that were not processed in the list above.
> Source attachments are maintained when running idea:idea
>
>
> Key: MIDEA-41
> URL: http://jira.codehaus.org/browse/MIDEA-41
> Project: Maven 2.x Idea Plugin
> Type: New Feature
> Reporter: Mark Chaimungkalanont
> Fix For: 2.0
> Attachments: MIDEA-41.patch, patches.diff
>
>
> This patch will allow source attachments to not be nuked when running
> {{idea:idea}}. You'll have to run {{idea:idea}} again first (this will put a
> "name" attribute on your IDEA deps) and _then_ after that, any source you
> attach to your JAR should be maintained. Note that If you specify the source
> lib as per MIDEA-26 or {{downloadSources}} tag, your existing source will not
> be kept.
> This patch *does* add a dependency on {{jaxen}} (for xPath) which seems to in
> turn depend on whole bunch of crap. Not sure if there is a push to keep deps
> down for the idea plugin or not. MIght be worth keeping in mind when you're
> evaluating the 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
[jira] Closed: (MIDEA-41) Source attachments are maintained when running idea:idea
[ http://jira.codehaus.org/browse/MIDEA-41?page=all ]
Brett Porter closed MIDEA-41:
-
Assign To: Brett Porter
Resolution: Fixed
> Source attachments are maintained when running idea:idea
>
>
> Key: MIDEA-41
> URL: http://jira.codehaus.org/browse/MIDEA-41
> Project: Maven 2.x Idea Plugin
> Type: New Feature
> Reporter: Mark Chaimungkalanont
> Assignee: Brett Porter
> Fix For: 2.0
> Attachments: MIDEA-41.patch, patches.diff
>
>
> This patch will allow source attachments to not be nuked when running
> {{idea:idea}}. You'll have to run {{idea:idea}} again first (this will put a
> "name" attribute on your IDEA deps) and _then_ after that, any source you
> attach to your JAR should be maintained. Note that If you specify the source
> lib as per MIDEA-26 or {{downloadSources}} tag, your existing source will not
> be kept.
> This patch *does* add a dependency on {{jaxen}} (for xPath) which seems to in
> turn depend on whole bunch of crap. Not sure if there is a push to keep deps
> down for the idea plugin or not. MIght be worth keeping in mind when you're
> evaluating the 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
[jira] Updated: (MIDEA-51) source code is not linked to dependencies with a classifier
[ http://jira.codehaus.org/browse/MIDEA-51?page=all ] Brett Porter updated MIDEA-51: -- Fix Version: (was: 2.0) I want to spend more time investigating this to see whether the classifier is consistenly appended to the existing one on release. The problem would be because it is being replaced. If there's no way to consistently designate this, then it may need to be a configuration mapping. How are your test sources generated? > source code is not linked to dependencies with a classifier > --- > > Key: MIDEA-51 > URL: http://jira.codehaus.org/browse/MIDEA-51 > Project: Maven 2.x Idea Plugin > Type: Bug > Environment: Sun-JDK 1.5.0_06, Fedora Core 5 > Reporter: Arik Kfir > > > Using the latest copy of the plugin from SVN, it correctly downloads and > links source code (and javadocs) to dependencies defined in the POM. This > does not happen, however, to dependencies with a classifier. > To reproduce, add a dependency with a classifier, like this: > > ... > ... > ... > tests > -- 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: (MAVENUPLOAD-885) OpenWFE 1.7.0 upload request
OpenWFE 1.7.0 upload request Key: MAVENUPLOAD-885 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-885 Project: maven-upload-requests Type: Task Reporter: John Mettraux http://openwfe.org/upload/openwfe-1.7.0-bundle.jar http://openwfe.org/upload/openwfe-applic-1.7.0-bundle.jar http://openwfe.org/upload/openwfe-embed-1.7.0-bundle.jar http://openwfe.org/upload/openwfe-embed-wom-1.7.0-bundle.jar http://openwfe.org/upload/openwfe-engine-1.7.0-bundle.jar http://openwfe.org/upload/openwfe-engine-actions-1.7.0-bundle.jar http://openwfe.org/upload/openwfe-worklist-1.7.0-bundle.jar http://openwfe.org/upload/openwfe-worklist-actions-1.7.0-bundle.jar OpenWFE is an open source workflow engine under a BSD license. Thanks in advance, John -- 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-2236) DefaultMavenProjectBuilder.buildStandaloneSuperProject() should include a ProfileManager that includes active profiles from settings.xml
[ http://jira.codehaus.org/browse/MNG-2236?page=comments#action_65036 ] Aaron Anderson commented on MNG-2236: - This is a gating issue for my plugin and archetype project http://bobber.javaforge.com/ > DefaultMavenProjectBuilder.buildStandaloneSuperProject() should include a > ProfileManager that includes active profiles from settings.xml > > > Key: MNG-2236 > URL: http://jira.codehaus.org/browse/MNG-2236 > Project: Maven 2 > Type: Bug > Components: Inheritence and Interpolation > Versions: 2.0.4 > Reporter: Aaron Anderson > Attachments: patch.txt > > > I have a custom plugin that performs JMX operations using properties defined > in a profile. I have defined an active profile in the settings.xml that > specifies properties that the plugin uses and everything works fine when a > POM is present. Now I would like the plugin to work from any directory and > have added the plugin annotation "requiresProject=false" to it. > If I run the plugin in a directory without a POM the profile properties from > settings.xml are never loaded. After performing some debugging I have > determined that the default super-pom's model that is used when no POM xml > file is available does not contain the profile properties defined in > settings.xml while if a POM.xml is available the settings.xml profiles are > loaded into the POM. > This all appears to boil down to the lack of a ProfileManager parameter to > thebuildStandaloneSuperProject method defined in the MavenProjectBuilder > interface. While DefaultMaven's invocation of the component has a > globalProfileManager available (with the active settings profiles set) it > cannot be passed into the MavenProjectBuilder component. Alternatively, If > the DefaultMavenProjectBuilder had the Settings component injected into it > could pass it into the constructor of the DefaultProfileManager instance it > creates and then the DefaultProfileManager would load the active profiles > into the POM. > By enabling this fix it would make plugins useful for management tasks, for > example starting or stoping an application server. -- 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: (SCM-117) Add parameters to scm configuration element
[ http://jira.codehaus.org/browse/SCM-117?page=comments#action_65038 ] Dan Tran commented on SCM-117: -- maven-scm-provider-starteam has a hidden system property that allow you to issue "-cr path" during checking 1. Create a CR using your starteam 2. pass -Dmaven.scm.issue=path to your CR Would this work? > Add parameters to scm configuration element > --- > > Key: SCM-117 > URL: http://jira.codehaus.org/browse/SCM-117 > Project: Maven SCM > Type: Wish > Components: maven-scm-provider-starteam > Versions: 1.0-beta-2 > Reporter: Aviran Mordo > Assignee: Dan Tran > > > It would be very nice to have the ability to add parameters to the scm > element. For instance to add parameter to always force checkout. for instance > in Starteam I would like to add -o so every time stcmd is called the > parameters will be concatenated to the command line -- 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: (MNGECLIPSE-122) wrong download url for javadoc ?
wrong download url for javadoc ? Key: MNGECLIPSE-122 URL: http://jira.codehaus.org/browse/MNGECLIPSE-122 Project: Maven 2.x Extension for Eclipse Type: Bug Components: Dependency Resolver Versions: 0.0.7 Environment: Eclipse 3.1.2 / Windows 2003 / Java 1.4.2 Reporter: Dirk Datzert Assigned to: Eugene Kuleshov Hi, after upgrading to latested release 0.0.7 I tried the download if javadoc artefacts. I saw in the log of the maven-proxy that m2 tried to download javadoc named name-version-java-doc.javadoc instead of name-version-javadoc.jar As I looked into Maven2Plugin.java I would expect the downloads of java-doc to be named name-version-javadoc.jar. Some examples of the maven-proxy.log: 2006-05-05 21:46:44,308 [INFO ] proxy.config.HttpRepoConfiguration - Repo[www-ibib lio-org]: Checking last modified time for http://www.ibiblio.org/maven2/com/sap/ip/ bi/sdk/aii_proxy_rt/3.50.16.0/aii_proxy_rt-3.50.16.0-javadoc.java-doc 2006-05-05 21:46:45,228 [INFO ] components.impl.DefaultSnapshotCache - Adding /com /sap/ip/bi/sdk/aii_proxy_rt/3.50.16.0/aii_proxy_rt-3.50.16.0-javadoc.java-doc to sn apshot cache 2006-05-05 21:46:45,228 [DEBUG] components.impl.DefaultSnapshotCache - Unable to f ind /com/sap/ip/bi/sdk/aii_proxy_rt/3.50.16.0/aii_proxy_rt-3.50.16.0-javadoc.java-d oc in snapshot cache 2006-05-05 21:46:45,228 [INFO ] proxy.config.HttpRepoConfiguration - Repo[cargo-co dehaus-org]: Checking last modified time for http://cargo.codehaus.org/dist2/com/sa p/ip/bi/sdk/aii_proxy_rt/3.50.16.0/aii_proxy_rt-3.50.16.0-javadoc.java-doc 2006-05-05 21:46:45,495 [INFO ] components.impl.DefaultSnapshotCache - Adding /com /sap/ip/bi/sdk/aii_proxy_rt/3.50.16.0/aii_proxy_rt-3.50.16.0-javadoc.java-doc to sn apshot cache Regards, Dirk -- 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: (MNGECLIPSE-122) wrong download url for javadoc ?
[ http://jira.codehaus.org/browse/MNGECLIPSE-122?page=all ] Eugene Kuleshov updated MNGECLIPSE-122: --- Priority: Minor (was: Major) Description: after upgrading to latested release 0.0.7 I tried the download if javadoc artefacts. I saw in the log of the maven-proxy that m2 tried to download javadoc named name-version-java-doc.javadoc instead of name-version-javadoc.jar As I looked into Maven2Plugin.java I would expect the downloads of java-doc to be named name-version-javadoc.jar. Some examples of the maven-proxy.log: 2006-05-05 21:46:44,308 [INFO ] proxy.config.HttpRepoConfiguration - Repo[www-ibiblio-org]: Checking last modified time for http://www.ibiblio.org/maven2/com/sap/ip/bi/sdk/aii_proxy_rt/3.50.16.0/aii_proxy_rt-3.50.16.0-javadoc.java-doc 2006-05-05 21:46:45,228 [INFO ] components.impl.DefaultSnapshotCache - Adding /com/sap/ip/bi/sdk/aii_proxy_rt/3.50.16.0/aii_proxy_rt-3.50.16.0-javadoc.java-doc to snapshot cache 2006-05-05 21:46:45,228 [DEBUG] components.impl.DefaultSnapshotCache - Unable to find /com/sap/ip/bi/sdk/aii_proxy_rt/3.50.16.0/aii_proxy_rt-3.50.16.0-javadoc.java-doc in snapshot cache 2006-05-05 21:46:45,228 [INFO ] proxy.config.HttpRepoConfiguration - Repo[cargo-codehaus-org]: Checking last modified time for http://cargo.codehaus.org/dist2/com/sap/ip/bi/sdk/aii_proxy_rt/3.50.16.0/aii_proxy_rt-3.50.16.0-javadoc.java-doc 2006-05-05 21:46:45,495 [INFO ] components.impl.DefaultSnapshotCache - Adding /com/sap/ip/bi/sdk/aii_proxy_rt/3.50.16.0/aii_proxy_rt-3.50.16.0-javadoc.java-doc to snapshot cache was: Hi, after upgrading to latested release 0.0.7 I tried the download if javadoc artefacts. I saw in the log of the maven-proxy that m2 tried to download javadoc named name-version-java-doc.javadoc instead of name-version-javadoc.jar As I looked into Maven2Plugin.java I would expect the downloads of java-doc to be named name-version-javadoc.jar. Some examples of the maven-proxy.log: 2006-05-05 21:46:44,308 [INFO ] proxy.config.HttpRepoConfiguration - Repo[www-ibib lio-org]: Checking last modified time for http://www.ibiblio.org/maven2/com/sap/ip/ bi/sdk/aii_proxy_rt/3.50.16.0/aii_proxy_rt-3.50.16.0-javadoc.java-doc 2006-05-05 21:46:45,228 [INFO ] components.impl.DefaultSnapshotCache - Adding /com /sap/ip/bi/sdk/aii_proxy_rt/3.50.16.0/aii_proxy_rt-3.50.16.0-javadoc.java-doc to sn apshot cache 2006-05-05 21:46:45,228 [DEBUG] components.impl.DefaultSnapshotCache - Unable to f ind /com/sap/ip/bi/sdk/aii_proxy_rt/3.50.16.0/aii_proxy_rt-3.50.16.0-javadoc.java-d oc in snapshot cache 2006-05-05 21:46:45,228 [INFO ] proxy.config.HttpRepoConfiguration - Repo[cargo-co dehaus-org]: Checking last modified time for http://cargo.codehaus.org/dist2/com/sa p/ip/bi/sdk/aii_proxy_rt/3.50.16.0/aii_proxy_rt-3.50.16.0-javadoc.java-doc 2006-05-05 21:46:45,495 [INFO ] components.impl.DefaultSnapshotCache - Adding /com /sap/ip/bi/sdk/aii_proxy_rt/3.50.16.0/aii_proxy_rt-3.50.16.0-javadoc.java-doc to sn apshot cache Regards, Dirk Please provide an example project to reproduce this issue. > wrong download url for javadoc ? > > > Key: MNGECLIPSE-122 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-122 > Project: Maven 2.x Extension for Eclipse > Type: Bug > Components: Dependency Resolver > Versions: 0.0.7 > Environment: Eclipse 3.1.2 / Windows 2003 / Java 1.4.2 > Reporter: Dirk Datzert > Assignee: Eugene Kuleshov > Priority: Minor > > > after upgrading to latested release 0.0.7 I tried the download if javadoc > artefacts. I saw in the log of the maven-proxy that m2 tried to download > javadoc named name-version-java-doc.javadoc instead of > name-version-javadoc.jar > As I looked into Maven2Plugin.java I would expect the downloads of java-doc > to be named name-version-javadoc.jar. > Some examples of the maven-proxy.log: > 2006-05-05 21:46:44,308 [INFO ] proxy.config.HttpRepoConfiguration - > Repo[www-ibiblio-org]: Checking last modified time for > http://www.ibiblio.org/maven2/com/sap/ip/bi/sdk/aii_proxy_rt/3.50.16.0/aii_proxy_rt-3.50.16.0-javadoc.java-doc > 2006-05-05 21:46:45,228 [INFO ] components.impl.DefaultSnapshotCache - > Adding > /com/sap/ip/bi/sdk/aii_proxy_rt/3.50.16.0/aii_proxy_rt-3.50.16.0-javadoc.java-doc > to snapshot cache > 2006-05-05 21:46:45,228 [DEBUG] components.impl.DefaultSnapshotCache - > Unable to find > /com/sap/ip/bi/sdk/aii_proxy_rt/3.50.16.0/aii_proxy_rt-3.50.16.0-javadoc.java-doc > in snapshot cache > 2006-05-05 21:46:45,228 [INFO ] proxy.config.HttpRepoConfiguration - > Repo[cargo-codehaus-org]: Checking last modified time for > http://cargo.codehaus.org/dist2/com/sap/ip/bi/sdk/aii_proxy_rt/3.50.16.0/aii_proxy_rt-3.50.16.0-javadoc.java-doc > 2006-05-05 21:46:45,495 [INFO ] components.impl.DefaultSnapshotCache - > Adding > /com/sap/ip/bi/sdk/aii_proxy_rt/3.50.1
[jira] Created: (MNG-2285) local repository path cannot have special characters
local repository path cannot have special characters Key: MNG-2285 URL: http://jira.codehaus.org/browse/MNG-2285 Project: Maven 2 Type: Bug Components: Repositories, General, Errors Versions: 2.0.2 Environment: Windows XP Reporter: Ravi Varanasi Priority: Minor Attachments: settings.xml When there are special characters in the path and running the command *mvn clean*.causes the exception --- java.lang.NullPointerException at org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginM anager.java:295) at org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(De faultPluginManager.java:200) at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPlug inManager.java:165) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(Defa ultLifecycleExecutor.java:1218) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor (DefaultLifecycleExecutor.java:1430) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListBy AggregationNeeds(DefaultLifecycleExecutor.java:378) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi fecycleExecutor.java:134) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.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) --- Attached is the settiings.xml. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MRESOURCES-11) Module doesn't depend on commons-io - remove dependency from pom
[ http://jira.codehaus.org/browse/MRESOURCES-11?page=all ] Jesse McConnell closed MRESOURCES-11: - Resolution: Fixed removed > Module doesn't depend on commons-io - remove dependency from pom > > > Key: MRESOURCES-11 > URL: http://jira.codehaus.org/browse/MRESOURCES-11 > Project: Maven 2.x Resources Plugin > Type: Improvement > Reporter: Grzegorz Slowikowski > Priority: Trivial > Fix For: 2.2 > > > commons-io dependency should be removed -- 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: (SCM-183) Added listFiles to ScmProvider
[ http://jira.codehaus.org/browse/SCM-183?page=all ] Carlos Sanchez updated SCM-183: --- Assign To: (was: Carlos Sanchez) Fix Version: 1.0 Added to API and SVN implementation to 1.0-SNAPSHOT > Added listFiles to ScmProvider > -- > > Key: SCM-183 > URL: http://jira.codehaus.org/browse/SCM-183 > Project: Maven SCM > Type: New Feature > Components: maven-scm-api > Reporter: Zsolt Koppany > Fix For: 1.0 > Attachments: scm-maven.patch, scm-maven.patch > > > This patch adds "listFiles" method to "ScmProvider" and contains the > implementation for subversion. -- 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: (SCM-183) Added listFiles to ScmProvider
[ http://jira.codehaus.org/browse/SCM-183?page=comments#action_65049 ] Carlos Sanchez commented on SCM-183: This patch is not complete so CVS implementation was not added > Added listFiles to ScmProvider > -- > > Key: SCM-183 > URL: http://jira.codehaus.org/browse/SCM-183 > Project: Maven SCM > Type: New Feature > Components: maven-scm-api > Reporter: Zsolt Koppany > Fix For: 1.0 > Attachments: scm-maven.patch, scm-maven.patch > > > This patch adds "listFiles" method to "ScmProvider" and contains the > implementation for subversion. -- 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-2286) Uploading missing jar files
Uploading missing jar files --- Key: MNG-2286 URL: http://jira.codehaus.org/browse/MNG-2286 Project: Maven 2 Type: Improvement Versions: 2.0.5 Reporter: Sanket Desai Attachments: missing-jar-files.zip maven2 repos @ ibiblio is missing some important jar files: 1) activation-1.0.2.jar (group Id: javax.activation, artifactId : activation, Version: 1.0.2) can be obtained from http://java.sun.com/products/javabeans/jaf/index.jsp 2) connector-1.0.jar (group Id: javax.resource, artifactId : connector, Version: 1.0) can be obtained from http://java.sun.com/j2ee/connector/index.jsp 3) jacc-1.0.jar (group Id: javax.security, artifactId : jacc, Version: 1.0) can be obtained from http://java.sun.com/products/javabeans/jaf/index.jsp 4) jta-1.0.1B.jar (group Id: javax.transaction, artifactId : jta, Version: 1.0.1B) can be obtained from http://java.sun.com/products/jta In some of the websites where the jar can be downloaded, there is a ZIP file available with class files in them. One will need to jar them up with specified name. Note: I've also attached the zip file containing all the jar files. 5) mail-1.3.2.jar (group Id: javax.activation, artifactId : activation, Version: 1.0.2) can be obtained from : http://java.sun.com/products/javamail/index.jsp -- 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: (MRESOURCES-10) Filtering should handle java.io.File values
[ http://jira.codehaus.org/browse/MRESOURCES-10?page=comments#action_65050
]
Jesse McConnell commented on MRESOURCES-10:
---
svn diff -r3065:3066 .
run that at the top of plexus checkout and it will tell you the changes that
took it from 3065 to version 3066
> Filtering should handle java.io.File values
> ---
>
> Key: MRESOURCES-10
> URL: http://jira.codehaus.org/browse/MRESOURCES-10
> Project: Maven 2.x Resources Plugin
> Type: Improvement
> Reporter: Mike Perham
> Fix For: 2.2
>
>
> I'm trying to use filters along with ${basedir} to setup my unit test Derby
> database. Derby must have a unique directory to build its database in and
> this becomes a problem in multi-module builds.
> Currently I'm doing this:
> {code:xml}
> class="org.apache.commons.dbcp.BasicDataSource">
>name="driverClassName">org.apache.derby.jdbc.EmbeddedDriver
>name="url">jdbc:derby:target/test/testdb/${pom.artifactId};create=true
>
> {code}
> But I'd like to do this:
> {code:xml}
> class="org.apache.commons.dbcp.BasicDataSource">
>name="driverClassName">org.apache.derby.jdbc.EmbeddedDriver
>name="url">jdbc:derby:${basedir}/target/test/testdb;create=true
>
> {code}
> When I try to do the latter, I get this:
> java.lang.ClassCastException: java.io.File
> at
> org.codehaus.plexus.util.InterpolationFilterReader.read(InterpolationFilterReader.java:269)
> at
> org.codehaus.plexus.util.InterpolationFilterReader.read(InterpolationFilterReader.java:162)
> at java.io.Reader.read(Reader.java:100)
> at org.codehaus.plexus.util.IOUtil.copy(IOUtil.java:212)
> at org.codehaus.plexus.util.IOUtil.copy(IOUtil.java:200)
> at
> org.apache.maven.plugin.resources.ResourcesMojo.copyFile(ResourcesMojo.java:249)
> at
> org.apache.maven.plugin.resources.ResourcesMojo.copyResources(ResourcesMojo.java:172)
> at
> org.apache.maven.plugin.resources.TestResourcesMojo.execute(TestResourcesMojo.java:53)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:415)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:531)
--
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-2286) Uploading missing jar files
[ http://jira.codehaus.org/browse/MNG-2286?page=comments#action_65051 ] Wayne Fay commented on MNG-2286: To understand why these jars are not currently available in the Maven repository, please refer to: http://maven.apache.org/guides/mini/guide-coping-with-sun-jars.html > Uploading missing jar files > --- > > Key: MNG-2286 > URL: http://jira.codehaus.org/browse/MNG-2286 > Project: Maven 2 > Type: Improvement > Versions: 2.0.5 > Reporter: Sanket Desai > Attachments: missing-jar-files.zip > > > maven2 repos @ ibiblio is missing some important jar files: > 1) activation-1.0.2.jar (group Id: javax.activation, artifactId : activation, > Version: 1.0.2) > can be obtained from http://java.sun.com/products/javabeans/jaf/index.jsp > 2) connector-1.0.jar (group Id: javax.resource, artifactId : connector, > Version: 1.0) > can be obtained from http://java.sun.com/j2ee/connector/index.jsp > 3) jacc-1.0.jar (group Id: javax.security, artifactId : jacc, Version: 1.0) > can be obtained from http://java.sun.com/products/javabeans/jaf/index.jsp > 4) jta-1.0.1B.jar (group Id: javax.transaction, artifactId : jta, Version: > 1.0.1B) > can be obtained from http://java.sun.com/products/jta > In some of the websites where the jar can be downloaded, there is a ZIP file > available with class files in them. > One will need to jar them up with specified name. > Note: I've also attached the zip file containing all the jar files. > 5) mail-1.3.2.jar (group Id: javax.activation, artifactId : activation, > Version: 1.0.2) > can be obtained from : http://java.sun.com/products/javamail/index.jsp -- 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: (MNGECLIPSE-122) wrong download url for javadoc ?
[ http://jira.codehaus.org/browse/MNGECLIPSE-122?page=all ] Dirk Datzert updated MNGECLIPSE-122: Attachment: pom.xml > wrong download url for javadoc ? > > > Key: MNGECLIPSE-122 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-122 > Project: Maven 2.x Extension for Eclipse > Type: Bug > Components: Dependency Resolver > Versions: 0.0.7 > Environment: Eclipse 3.1.2 / Windows 2003 / Java 1.4.2 > Reporter: Dirk Datzert > Assignee: Eugene Kuleshov > Priority: Minor > Attachments: pom.xml > > > after upgrading to latested release 0.0.7 I tried the download if javadoc > artefacts. I saw in the log of the maven-proxy that m2 tried to download > javadoc named name-version-java-doc.javadoc instead of > name-version-javadoc.jar > As I looked into Maven2Plugin.java I would expect the downloads of java-doc > to be named name-version-javadoc.jar. > Some examples of the maven-proxy.log: > 2006-05-05 21:46:44,308 [INFO ] proxy.config.HttpRepoConfiguration - > Repo[www-ibiblio-org]: Checking last modified time for > http://www.ibiblio.org/maven2/com/sap/ip/bi/sdk/aii_proxy_rt/3.50.16.0/aii_proxy_rt-3.50.16.0-javadoc.java-doc > 2006-05-05 21:46:45,228 [INFO ] components.impl.DefaultSnapshotCache - > Adding > /com/sap/ip/bi/sdk/aii_proxy_rt/3.50.16.0/aii_proxy_rt-3.50.16.0-javadoc.java-doc > to snapshot cache > 2006-05-05 21:46:45,228 [DEBUG] components.impl.DefaultSnapshotCache - > Unable to find > /com/sap/ip/bi/sdk/aii_proxy_rt/3.50.16.0/aii_proxy_rt-3.50.16.0-javadoc.java-doc > in snapshot cache > 2006-05-05 21:46:45,228 [INFO ] proxy.config.HttpRepoConfiguration - > Repo[cargo-codehaus-org]: Checking last modified time for > http://cargo.codehaus.org/dist2/com/sap/ip/bi/sdk/aii_proxy_rt/3.50.16.0/aii_proxy_rt-3.50.16.0-javadoc.java-doc > 2006-05-05 21:46:45,495 [INFO ] components.impl.DefaultSnapshotCache - > Adding > /com/sap/ip/bi/sdk/aii_proxy_rt/3.50.16.0/aii_proxy_rt-3.50.16.0-javadoc.java-doc > to snapshot cache -- 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: (MJAR-38) Maven Puts Arbitrary Extension Definition in JAR Manifest by Default.
[ http://jira.codehaus.org/browse/MJAR-38?page=all ] Jochen Wiedmann updated MJAR-38: Attachment: MavenArchiver.patch.3 MavenArchiver.patch.2 MavenArchiver.patch.1 > Maven Puts Arbitrary Extension Definition in JAR Manifest by Default. > - > > Key: MJAR-38 > URL: http://jira.codehaus.org/browse/MJAR-38 > Project: Maven 2.x Jar Plugin > Type: Bug > Versions: 2.0 > Environment: Maven version: 2.0.4 > Microsoft Windows XP [Version 5.1.2600] > Reporter: Steven Coco > Attachments: Jar Extension-Name Tester.zip, MavenArchiver.patch.1, > MavenArchiver.patch.2, MavenArchiver.patch.3 > > > I'm using the latest Maven release. When I build my project, the > resulting Jar file's manifest contains an Extension-Name attribute along with > Specification and Implementation attributes. The POM contains no mention > that this project is a Java optional package -- an "extension" (or an > extension of any other kind). > I don't know why Maven is doing that. > If Maven is doing this by default for some reason, it absolutely > shouldn't. Maven should not identify my Jar as an optional package unless I > explicitly say so. Jars are only extensions if explicitly created as such. > The name it uses for the extension name is the POM's . > That's not even a UID! -- 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-2286) Uploading missing jar files
[ http://jira.codehaus.org/browse/MNG-2286?page=all ] Carlos Sanchez closed MNG-2286: --- Assign To: Carlos Sanchez Resolution: Won't Fix > Uploading missing jar files > --- > > Key: MNG-2286 > URL: http://jira.codehaus.org/browse/MNG-2286 > Project: Maven 2 > Type: Improvement > Versions: 2.0.5 > Reporter: Sanket Desai > Assignee: Carlos Sanchez > Attachments: missing-jar-files.zip > > > maven2 repos @ ibiblio is missing some important jar files: > 1) activation-1.0.2.jar (group Id: javax.activation, artifactId : activation, > Version: 1.0.2) > can be obtained from http://java.sun.com/products/javabeans/jaf/index.jsp > 2) connector-1.0.jar (group Id: javax.resource, artifactId : connector, > Version: 1.0) > can be obtained from http://java.sun.com/j2ee/connector/index.jsp > 3) jacc-1.0.jar (group Id: javax.security, artifactId : jacc, Version: 1.0) > can be obtained from http://java.sun.com/products/javabeans/jaf/index.jsp > 4) jta-1.0.1B.jar (group Id: javax.transaction, artifactId : jta, Version: > 1.0.1B) > can be obtained from http://java.sun.com/products/jta > In some of the websites where the jar can be downloaded, there is a ZIP file > available with class files in them. > One will need to jar them up with specified name. > Note: I've also attached the zip file containing all the jar files. > 5) mail-1.3.2.jar (group Id: javax.activation, artifactId : activation, > Version: 1.0.2) > can be obtained from : http://java.sun.com/products/javamail/index.jsp -- 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: (MNGECLIPSE-122) wrong download url for javadoc ?
[ http://jira.codehaus.org/browse/MNGECLIPSE-122?page=comments#action_65054 ] Dirk Datzert commented on MNGECLIPSE-122: - Log from Eclipse on clean/rebuild sample project: 09.05.06 21:21:09 CEST: Reading /m2test/pom.xml 09.05.06 21:21:10 CEST: [WARN] Unable to get resource from repository local-mirror (http://your.local.mirror.com:9992/repository) 09.05.06 21:21:29 CEST: Error transferring file junit:junit-4.0.java-doc Log from Maven2-Proxy: 2006-05-09 21:21:31,492 [INFO ] proxy.servlets.RepositoryServlet - Received reques t: /junit/junit/4.0/junit-4.0-javadoc.java-doc 2006-05-09 21:21:31,492 [DEBUG] proxy.engine.DownloadEngine - Request: source=10.9 .100.17, path=/junit/junit/4.0/junit-4.0-javadoc.java-doc, lastModified=-1, headOnl y=false, ifModifiedSince=-1 2006-05-09 21:21:31,492 [DEBUG] proxy.config.FileRepoConfiguration - Repo[global]: Checking last modified time for ./target/repo2/junit/junit/4.0/junit-4.0-javadoc.j ava-doc 2006-05-09 21:21:31,492 [DEBUG] proxy.config.FileRepoConfiguration - Repo[local-re po]: Checking last modified time for ./target/repo2-local/junit/junit/4.0/junit-4.0 -javadoc.java-doc 2006-05-09 21:21:31,492 [DEBUG] proxy.config.FileRepoConfiguration - Repo[rasselst ein-repo]: Checking last modified time for ./target/repo2-rasselstein/junit/junit/4 .0/junit-4.0-javadoc.java-doc 2006-05-09 21:21:31,492 [INFO ] components.impl.DefaultSnapshotCache - Updating /j unit/junit/4.0/junit-4.0-javadoc.java-doc in snapshot cache 2006-05-09 21:21:31,492 [INFO ] components.impl.DefaultSnapshotCache - Updating /j unit/junit/4.0/junit-4.0-javadoc.java-doc in snapshot cache > wrong download url for javadoc ? > > > Key: MNGECLIPSE-122 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-122 > Project: Maven 2.x Extension for Eclipse > Type: Bug > Components: Dependency Resolver > Versions: 0.0.7 > Environment: Eclipse 3.1.2 / Windows 2003 / Java 1.4.2 > Reporter: Dirk Datzert > Assignee: Eugene Kuleshov > Priority: Minor > Attachments: pom.xml > > > after upgrading to latested release 0.0.7 I tried the download if javadoc > artefacts. I saw in the log of the maven-proxy that m2 tried to download > javadoc named name-version-java-doc.javadoc instead of > name-version-javadoc.jar > As I looked into Maven2Plugin.java I would expect the downloads of java-doc > to be named name-version-javadoc.jar. > Some examples of the maven-proxy.log: > 2006-05-05 21:46:44,308 [INFO ] proxy.config.HttpRepoConfiguration - > Repo[www-ibiblio-org]: Checking last modified time for > http://www.ibiblio.org/maven2/com/sap/ip/bi/sdk/aii_proxy_rt/3.50.16.0/aii_proxy_rt-3.50.16.0-javadoc.java-doc > 2006-05-05 21:46:45,228 [INFO ] components.impl.DefaultSnapshotCache - > Adding > /com/sap/ip/bi/sdk/aii_proxy_rt/3.50.16.0/aii_proxy_rt-3.50.16.0-javadoc.java-doc > to snapshot cache > 2006-05-05 21:46:45,228 [DEBUG] components.impl.DefaultSnapshotCache - > Unable to find > /com/sap/ip/bi/sdk/aii_proxy_rt/3.50.16.0/aii_proxy_rt-3.50.16.0-javadoc.java-doc > in snapshot cache > 2006-05-05 21:46:45,228 [INFO ] proxy.config.HttpRepoConfiguration - > Repo[cargo-codehaus-org]: Checking last modified time for > http://cargo.codehaus.org/dist2/com/sap/ip/bi/sdk/aii_proxy_rt/3.50.16.0/aii_proxy_rt-3.50.16.0-javadoc.java-doc > 2006-05-05 21:46:45,495 [INFO ] components.impl.DefaultSnapshotCache - > Adding > /com/sap/ip/bi/sdk/aii_proxy_rt/3.50.16.0/aii_proxy_rt-3.50.16.0-javadoc.java-doc > to snapshot cache -- 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-2226) The links in the top link row of the main documentation page are doubled.
[ http://jira.codehaus.org/browse/MNG-2226?page=all ] Alex Mayorga Adame updated MNG-2226: Attachment: Fixed link bar.jpg > The links in the top link row of the main documentation page are doubled. > - > > Key: MNG-2226 > URL: http://jira.codehaus.org/browse/MNG-2226 > Project: Maven 2 > Type: Bug > Components: Documentation: General > Versions: 2.0.4 > Environment: not important (Firefox 1.5.1 on WinXPSP2) > Reporter: Thomas Minor > Priority: Trivial > Attachments: Fixed link bar.jpg > > > The links in the top link row of the main documentation page are doubled. -- 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: (MRESOURCES-10) Filtering should handle java.io.File values
[ http://jira.codehaus.org/browse/MRESOURCES-10?page=comments#action_65057
]
Mike Perham commented on MRESOURCES-10:
---
Thanks Jesse. Looks like it got fixed by adding a toString() to ensure if the
variable is not a string, it is converted into one.
> Filtering should handle java.io.File values
> ---
>
> Key: MRESOURCES-10
> URL: http://jira.codehaus.org/browse/MRESOURCES-10
> Project: Maven 2.x Resources Plugin
> Type: Improvement
> Reporter: Mike Perham
> Fix For: 2.2
>
>
> I'm trying to use filters along with ${basedir} to setup my unit test Derby
> database. Derby must have a unique directory to build its database in and
> this becomes a problem in multi-module builds.
> Currently I'm doing this:
> {code:xml}
> class="org.apache.commons.dbcp.BasicDataSource">
>name="driverClassName">org.apache.derby.jdbc.EmbeddedDriver
>name="url">jdbc:derby:target/test/testdb/${pom.artifactId};create=true
>
> {code}
> But I'd like to do this:
> {code:xml}
> class="org.apache.commons.dbcp.BasicDataSource">
>name="driverClassName">org.apache.derby.jdbc.EmbeddedDriver
>name="url">jdbc:derby:${basedir}/target/test/testdb;create=true
>
> {code}
> When I try to do the latter, I get this:
> java.lang.ClassCastException: java.io.File
> at
> org.codehaus.plexus.util.InterpolationFilterReader.read(InterpolationFilterReader.java:269)
> at
> org.codehaus.plexus.util.InterpolationFilterReader.read(InterpolationFilterReader.java:162)
> at java.io.Reader.read(Reader.java:100)
> at org.codehaus.plexus.util.IOUtil.copy(IOUtil.java:212)
> at org.codehaus.plexus.util.IOUtil.copy(IOUtil.java:200)
> at
> org.apache.maven.plugin.resources.ResourcesMojo.copyFile(ResourcesMojo.java:249)
> at
> org.apache.maven.plugin.resources.ResourcesMojo.copyResources(ResourcesMojo.java:172)
> at
> org.apache.maven.plugin.resources.TestResourcesMojo.execute(TestResourcesMojo.java:53)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:415)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:531)
--
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-2226) The links in the top link row of the main documentation page are doubled.
[ http://jira.codehaus.org/browse/MNG-2226?page=comments#action_65058 ] Alex Mayorga Adame commented on MNG-2226: - This has been fixed already. > The links in the top link row of the main documentation page are doubled. > - > > Key: MNG-2226 > URL: http://jira.codehaus.org/browse/MNG-2226 > Project: Maven 2 > Type: Bug > Components: Documentation: General > Versions: 2.0.4 > Environment: not important (Firefox 1.5.1 on WinXPSP2) > Reporter: Thomas Minor > Priority: Trivial > Attachments: Fixed link bar.jpg > > > The links in the top link row of the main documentation page are doubled. -- 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-2226) The links in the top link row of the main documentation page are doubled.
[ http://jira.codehaus.org/browse/MNG-2226?page=all ] Alex Mayorga Adame closed MNG-2226: --- Resolution: Fixed > The links in the top link row of the main documentation page are doubled. > - > > Key: MNG-2226 > URL: http://jira.codehaus.org/browse/MNG-2226 > Project: Maven 2 > Type: Bug > Components: Documentation: General > Versions: 2.0.4 > Environment: not important (Firefox 1.5.1 on WinXPSP2) > Reporter: Thomas Minor > Priority: Trivial > Attachments: Fixed link bar.jpg > > > The links in the top link row of the main documentation page are doubled. -- 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-104) Probable Invalid Default SVN Tag Information
Probable Invalid Default SVN Tag Information
Key: MRELEASE-104
URL: http://jira.codehaus.org/browse/MRELEASE-104
Project: Maven 2.x Release Plugin
Type: Improvement
Versions: 2.0-beta-4
Environment: Release plugin snapshot 20060509.101136-3, Subversion
Reporter: Bob Allison
Priority: Minor
Fix For: 2.0
When experimenting with a small POM, I neglected to place any configuration for
the release plugin in the POM. When trying to tag the release, the plugin
tried to commit the release into the SVN repository as ${basedir}/tags
--
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: (MRELEASE-104) Probable Invalid Default SVN Tag Information
[ http://jira.codehaus.org/browse/MRELEASE-104?page=all ]
Bob Allison updated MRELEASE-104:
-
Attachment: MRELEASE-104.pom
> Probable Invalid Default SVN Tag Information
>
>
> Key: MRELEASE-104
> URL: http://jira.codehaus.org/browse/MRELEASE-104
> Project: Maven 2.x Release Plugin
> Type: Improvement
> Versions: 2.0-beta-4
> Environment: Release plugin snapshot 20060509.101136-3, Subversion
> Reporter: Bob Allison
> Priority: Minor
> Fix For: 2.0
> Attachments: MRELEASE-104.pom
>
>
> When experimenting with a small POM, I neglected to place any configuration
> for the release plugin in the POM. When trying to tag the release, the
> plugin tried to commit the release into the SVN repository as ${basedir}/tags
--
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-2071) Typo: guide-coping-with-sun-jars.html
[ http://jira.codehaus.org/browse/MNG-2071?page=all ] Alex Mayorga Adame updated MNG-2071: Attachment: MNG-2071.diff > Typo: guide-coping-with-sun-jars.html > - > > Key: MNG-2071 > URL: http://jira.codehaus.org/browse/MNG-2071 > Project: Maven 2 > Type: Bug > Components: Documentation: General > Versions: documentation > Reporter: Rainer Wasserfuhr > Priority: Trivial > Attachments: MNG-2071.diff > > > "if you use the our suggestions" -> "if you use our suggestions" > http://maven.apache.org/guides/mini/guide-coping-with-sun-jars.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: (MNG-2071) Typo: guide-coping-with-sun-jars.html
[ http://jira.codehaus.org/browse/MNG-2071?page=all ] John Casey closed MNG-2071: --- Assign To: John Casey Resolution: Fixed Fix Version: documentation fixed the flow of the whole sentence, not just that phrase... > Typo: guide-coping-with-sun-jars.html > - > > Key: MNG-2071 > URL: http://jira.codehaus.org/browse/MNG-2071 > Project: Maven 2 > Type: Bug > Components: Documentation: General > Versions: documentation > Reporter: Rainer Wasserfuhr > Assignee: John Casey > Priority: Trivial > Fix For: documentation > Attachments: MNG-2071.diff > > > "if you use the our suggestions" -> "if you use our suggestions" > http://maven.apache.org/guides/mini/guide-coping-with-sun-jars.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: (MRESOURCES-10) Filtering should handle java.io.File values
[ http://jira.codehaus.org/browse/MRESOURCES-10?page=comments#action_65064
]
Jesse McConnell commented on MRESOURCES-10:
---
and actually this was two commits so to see the full change (and the original
class cast issue)
svn diff -r3064:3066 .
I'll dig up if this is in a plexus-utils release and change accordingly
> Filtering should handle java.io.File values
> ---
>
> Key: MRESOURCES-10
> URL: http://jira.codehaus.org/browse/MRESOURCES-10
> Project: Maven 2.x Resources Plugin
> Type: Improvement
> Reporter: Mike Perham
> Fix For: 2.2
>
>
> I'm trying to use filters along with ${basedir} to setup my unit test Derby
> database. Derby must have a unique directory to build its database in and
> this becomes a problem in multi-module builds.
> Currently I'm doing this:
> {code:xml}
> class="org.apache.commons.dbcp.BasicDataSource">
>name="driverClassName">org.apache.derby.jdbc.EmbeddedDriver
>name="url">jdbc:derby:target/test/testdb/${pom.artifactId};create=true
>
> {code}
> But I'd like to do this:
> {code:xml}
> class="org.apache.commons.dbcp.BasicDataSource">
>name="driverClassName">org.apache.derby.jdbc.EmbeddedDriver
>name="url">jdbc:derby:${basedir}/target/test/testdb;create=true
>
> {code}
> When I try to do the latter, I get this:
> java.lang.ClassCastException: java.io.File
> at
> org.codehaus.plexus.util.InterpolationFilterReader.read(InterpolationFilterReader.java:269)
> at
> org.codehaus.plexus.util.InterpolationFilterReader.read(InterpolationFilterReader.java:162)
> at java.io.Reader.read(Reader.java:100)
> at org.codehaus.plexus.util.IOUtil.copy(IOUtil.java:212)
> at org.codehaus.plexus.util.IOUtil.copy(IOUtil.java:200)
> at
> org.apache.maven.plugin.resources.ResourcesMojo.copyFile(ResourcesMojo.java:249)
> at
> org.apache.maven.plugin.resources.ResourcesMojo.copyResources(ResourcesMojo.java:172)
> at
> org.apache.maven.plugin.resources.TestResourcesMojo.execute(TestResourcesMojo.java:53)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:415)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:531)
--
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-2020) Broken links on website docu
[ http://jira.codehaus.org/browse/MNG-2020?page=all ] Alex Mayorga Adame closed MNG-2020: --- Resolution: Fixed All links on referred page lead somewhere. > Broken links on website docu > > > Key: MNG-2020 > URL: http://jira.codehaus.org/browse/MNG-2020 > Project: Maven 2 > Type: Bug > Components: Documentation: Introductions > Versions: documentation > Reporter: Rainer Wasserfuhr > Priority: Trivial > > > some hrefs are broken ion > http://maven.apache.org/guides/introduction/introduction-to-repositories.html > see also MNG-1996 ?. -- 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: (MAVENUPLOAD-886) Please upload qalab 0.9.0
Please upload qalab 0.9.0 - Key: MAVENUPLOAD-886 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-886 Project: maven-upload-requests Type: Task Reporter: Benoit Xhenseval Attachments: qalab-0.9.0-bundle.jar Thanks. -- 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: (MAVENUPLOAD-887) please upload QALab plugin 0.9.0 for maven 1.x
please upload QALab plugin 0.9.0 for maven 1.x -- Key: MAVENUPLOAD-887 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-887 Project: maven-upload-requests Type: Task Reporter: Benoit Xhenseval Attachments: maven-qalab-plugin-0.9.0-bundle.jar This is a maven 1.x plugin. thanks! -- 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: (MRESOURCES-12) Wrog filtering after at symbol using profiles
[ http://jira.codehaus.org/browse/MRESOURCES-12?page=all ] Jesse McConnell closed MRESOURCES-12: - Assign To: Jesse McConnell Resolution: Cannot Reproduce I tweaked a unit test to cause this behavior and it worked normally with the @ inserted into the file, so unless we get more feedback I amd going to just go ahead and mark this as cannot reproduce > Wrog filtering after at symbol using profiles > - > > Key: MRESOURCES-12 > URL: http://jira.codehaus.org/browse/MRESOURCES-12 > Project: Maven 2.x Resources Plugin > Type: Bug > Environment: All platforms > Reporter: Motxilo > Assignee: Jesse McConnell > Priority: Minor > > > Using profiles, when a resource -for instance, a Spring XML context file- > needs to be filtered before being deployed, it seems that after an at > character (@) included in a comment in the middle of the file, properties > aren't filtered at all, while others before the aforementioned comment are. -- 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: (MRESOURCES-10) Filtering should handle java.io.File values
[ http://jira.codehaus.org/browse/MRESOURCES-10?page=all ]
Jesse McConnell closed MRESOURCES-10:
-
Assign To: Jesse McConnell
Resolution: Fixed
fix was released in plexus-utils version 1.2 so I added a dependency to that
version of the lib and this will be fixed in the next release of the plugin
which will be rsn (real soon now)
> Filtering should handle java.io.File values
> ---
>
> Key: MRESOURCES-10
> URL: http://jira.codehaus.org/browse/MRESOURCES-10
> Project: Maven 2.x Resources Plugin
> Type: Improvement
> Reporter: Mike Perham
> Assignee: Jesse McConnell
> Fix For: 2.2
>
>
> I'm trying to use filters along with ${basedir} to setup my unit test Derby
> database. Derby must have a unique directory to build its database in and
> this becomes a problem in multi-module builds.
> Currently I'm doing this:
> {code:xml}
> class="org.apache.commons.dbcp.BasicDataSource">
>name="driverClassName">org.apache.derby.jdbc.EmbeddedDriver
>name="url">jdbc:derby:target/test/testdb/${pom.artifactId};create=true
>
> {code}
> But I'd like to do this:
> {code:xml}
> class="org.apache.commons.dbcp.BasicDataSource">
>name="driverClassName">org.apache.derby.jdbc.EmbeddedDriver
>name="url">jdbc:derby:${basedir}/target/test/testdb;create=true
>
> {code}
> When I try to do the latter, I get this:
> java.lang.ClassCastException: java.io.File
> at
> org.codehaus.plexus.util.InterpolationFilterReader.read(InterpolationFilterReader.java:269)
> at
> org.codehaus.plexus.util.InterpolationFilterReader.read(InterpolationFilterReader.java:162)
> at java.io.Reader.read(Reader.java:100)
> at org.codehaus.plexus.util.IOUtil.copy(IOUtil.java:212)
> at org.codehaus.plexus.util.IOUtil.copy(IOUtil.java:200)
> at
> org.apache.maven.plugin.resources.ResourcesMojo.copyFile(ResourcesMojo.java:249)
> at
> org.apache.maven.plugin.resources.ResourcesMojo.copyResources(ResourcesMojo.java:172)
> at
> org.apache.maven.plugin.resources.TestResourcesMojo.execute(TestResourcesMojo.java:53)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:415)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:531)
--
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-939) specify maven settings from command line
[ http://jira.codehaus.org/browse/MNG-939?page=comments#action_65071 ] John Casey commented on MNG-939: personally, I think it would be clearer if we added support for something like: -Dpassword.serverId=passwd and -Dpassphrase.serverId=phrase Wouldn't this be easier to understand? > specify maven settings from command line > > > Key: MNG-939 > URL: http://jira.codehaus.org/browse/MNG-939 > Project: Maven 2 > Type: Improvement > Components: Design, Patterns & Best Practices > Versions: 2.0-beta-1 > Environment: All > Reporter: Guest > Priority: Trivial > Attachments: MNG-939-maven-core.patch > > > Would like to be able to specify my server password at the command line, for > the server configured in the settings.xml file as I'm not happy embedding it > there or permanently giving my computer access via a certificate. -- 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-688) The application.xml file should only specify one component to start up
The application.xml file should only specify one component to start up -- Key: CONTINUUM-688 URL: http://jira.codehaus.org/browse/CONTINUUM-688 Project: Continuum Type: Improvement Components: Core system Versions: 1.1-alpha-1 Reporter: Jason van Zyl Assigned to: Jason van Zyl Fix For: 1.1-alpha-1 A Plexus application should encapsulate all other components it uses. Right now the load-on-start specifies the continuum application and the task queues. It should only be the continuum application. -- 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-939) specify maven settings from command line
[ http://jira.codehaus.org/browse/MNG-939?page=all ] John Casey updated MNG-939: --- Fix Version: 2.0.5 > specify maven settings from command line > > > Key: MNG-939 > URL: http://jira.codehaus.org/browse/MNG-939 > Project: Maven 2 > Type: Improvement > Components: Design, Patterns & Best Practices > Versions: 2.0-beta-1 > Environment: All > Reporter: Guest > Priority: Trivial > Fix For: 2.0.5 > Attachments: MNG-939-maven-core.patch > > > Would like to be able to specify my server password at the command line, for > the server configured in the settings.xml file as I'm not happy embedding it > there or permanently giving my computer access via a certificate. -- 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-2255) Use a external XML Pull parser instead of plexus one
[ http://jira.codehaus.org/browse/MNG-2255?page=comments#action_65075 ] Stefan Hübner commented on MNG-2255: Hm, just a thought, but: To me it seems that the parser used to read in maven's model isn't the problem really. It's more likely the way the POM is handed to the parser. Have a look to class org.apache.maven.model.io.xpp3.MavenXpp3Reader which is generated by maven-model. This MavenXpp3Reader is invoked via read-method with one parameter. This parameter is a Reader and that, to me, is problematic. Problematic because there's no way once you have a Reader on some inputsource (i.e. a stream) to change that reader's handling of character encodings on it's underlying stream. So, as long as reading the model is invoked by handing a Reader to some parser the parser won't be able to adapt to the actual POM's encoding. As a conclusion I would recommend model parser should be handed a stream rather than a Reader-instance working on the underlying POM. I don't know if other parsers can cope with that situation, but XMLPullParser doesn't. It would though, if it is given a stream on the POM, but I don't know which wider implications this would cause. What do you think? > Use a external XML Pull parser instead of plexus one > > > Key: MNG-2255 > URL: http://jira.codehaus.org/browse/MNG-2255 > Project: Maven 2 > Type: Improvement > Components: POM > Versions: 2.0.4 > Reporter: Carlos Sanchez > Priority: Critical > Fix For: 2.0.5 > > > To avoid maintaining the plexus XMLPullParser we should move to a standard > implementation like StaX > As mentioned in DOXIA-60: > There's a performance white paper > http://java.sun.com/performance/reference/whitepapers/StAX-1_0.pdf > The best implementation seems to be http://woodstox.codehaus.org/ > Another nice set of utilities at > http://wiki.java.net/bin/view/Javawsxml/StaxUtilsProject > The indentator could be used instead of the PrettyPrintXMLWriter -- 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-2254) the encoding parameter in xml declaration of POM is ignored
[ http://jira.codehaus.org/browse/MNG-2254?page=comments#action_65078 ] Stefan Hübner commented on MNG-2254: As I just stated in MNG-2255 I think, that ??"...the parser used to read in maven's model isn't the problem really. It's more likely the way the POM is handed to the parser."?? See MNG-2255 for full discussion of the issue. > the encoding parameter in xml declaration of POM is ignored > > > Key: MNG-2254 > URL: http://jira.codehaus.org/browse/MNG-2254 > Project: Maven 2 > Type: Bug > Reporter: Naoki Nose > Attachments: DefaultMavenProjectBuilder.diff, modello-plugin-xpp3.diff > > > DefaultMavenProjectBuilder reads POM in system default character encoding, > and the encoding parameter in xml declartion is ignored. > to fix this problem, We should > - fix modello-plugin-xpp3 to use the xml parser which is able to handle the > encoding parameter properly > - regenerate maven-model using fixed modello-plugin-xpp3 > - fix DefaultMavenProjectBuilder to use regenerated maven-model properly. -- 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-2255) Use a external XML Pull parser instead of plexus one
[ http://jira.codehaus.org/browse/MNG-2255?page=comments#action_65080 ] Carlos Sanchez commented on MNG-2255: - Yes, that's part of the solution too > Use a external XML Pull parser instead of plexus one > > > Key: MNG-2255 > URL: http://jira.codehaus.org/browse/MNG-2255 > Project: Maven 2 > Type: Improvement > Components: POM > Versions: 2.0.4 > Reporter: Carlos Sanchez > Priority: Critical > Fix For: 2.0.5 > > > To avoid maintaining the plexus XMLPullParser we should move to a standard > implementation like StaX > As mentioned in DOXIA-60: > There's a performance white paper > http://java.sun.com/performance/reference/whitepapers/StAX-1_0.pdf > The best implementation seems to be http://woodstox.codehaus.org/ > Another nice set of utilities at > http://wiki.java.net/bin/view/Javawsxml/StaxUtilsProject > The indentator could be used instead of the PrettyPrintXMLWriter -- 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-47) add zip provider (source attahced)
add zip provider (source attahced) -- Key: WAGON-47 URL: http://jira.codehaus.org/browse/WAGON-47 Project: wagon Type: New Feature Components: wagon-provider-api Reporter: John Didion As part of our build process, we generate repository snapshots contained within a jar file. We have written an installer that is able to install certain types of artifacts from any repository including a repository snapshot jar. We needed to add a zip file provider to wagon so we could use maven's repository api. It'd be nice to have that provider as part of wagon proper. -- 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: (WAGON-47) add zip provider (source attahced)
[ http://jira.codehaus.org/browse/WAGON-47?page=all ] John Didion updated WAGON-47: - Attachment: wagon-provider-zip.diff wagon-provider-api.diff > add zip provider (source attahced) > -- > > Key: WAGON-47 > URL: http://jira.codehaus.org/browse/WAGON-47 > Project: wagon > Type: New Feature > Components: wagon-provider-api > Reporter: John Didion > Attachments: wagon-provider-api.diff, wagon-provider-zip.diff > > > As part of our build process, we generate repository snapshots contained > within a jar file. We have written an installer that is able to install > certain types of artifacts from any repository including a repository > snapshot jar. We needed to add a zip file provider to wagon so we could use > maven's repository api. It'd be nice to have that provider as part of wagon > proper. -- 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: (MWAR-5) warSourceExcludes not working properly
[ http://jira.codehaus.org/browse/MWAR-5?page=comments#action_65081 ]
Dimitry Voytenko commented on MWAR-5:
-
Has this been released yet? Which version?
> warSourceExcludes not working properly
> --
>
> Key: MWAR-5
> URL: http://jira.codehaus.org/browse/MWAR-5
> Project: Maven 2.x War Plugin
> Type: Bug
> Environment: Win2k, Java 1.4.2_04, m2 beta1
> Reporter: Fabrice BELLINGARD
> Assignee: Edwin Punzalan
> Fix For: 2.0
> Attachments: MNG-1038-maven-war-plugin.patch, MNG-1038-maven-war-plugin.patch
>
>
> Note: I posted a message on Maven users list
> (http://www.mail-archive.com/users%40maven.apache.org/msg24088.html), but I
> got no answer so I post this issue, which in turn may or not be a bug...
> (sorry if it's not)
> I experienced a strange behaviour with the 'warSourceExcludes' property. When
> I grab some Web projects from the CVS of my company, I usually get all the
> WEB-INF/lib Jars that the developers put in the CVS:
> - With Maven 1, I use the 'maven.war.src.excludes' property to exclude those
> Jars ('maven.war.src.excludes=**/lib/*.*'), and it works well: the Jars
> packaged in the War are only the ones defined in the pom.
> - With m2, I tried to use the 'warSourceExcludes' property, which seemed to
> me to be the equivalent property. However, when the War is generated, there
> is no jar in the WEB-INF/lib folder. This works as if the plugin is excluding
> files after having copied the needed dependencies in the WEB-INF/lib folder
> (whereas in the Maven 1 version, it was excluding them before).
> Looking at the code of the m2 plugin, the value of 'warSourceExcludes' is
> used in method #getExcludes which is actually called in #performPackaging
> method. If this property is to work the same way as in m1, its value should
> be used in #copyResources method, before copying the Jar dependencies in
> WEB-INF/lib.
> What do you guys think of that? Am I right or am I missing something?
--
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-47) add zip provider (source attahced)
[ http://jira.codehaus.org/browse/WAGON-47?page=comments#action_65082 ] Carlos Sanchez commented on WAGON-47: - This can go into Maven, provided copyright ownership is assigned to the Apache Software Foundation (see other maven files) Also note that code formatting should be consistent with the current codebase. > add zip provider (source attahced) > -- > > Key: WAGON-47 > URL: http://jira.codehaus.org/browse/WAGON-47 > Project: wagon > Type: New Feature > Components: wagon-provider-api > Reporter: John Didion > Attachments: wagon-provider-api.diff, wagon-provider-zip.diff > > > As part of our build process, we generate repository snapshots contained > within a jar file. We have written an installer that is able to install > certain types of artifacts from any repository including a repository > snapshot jar. We needed to add a zip file provider to wagon so we could use > maven's repository api. It'd be nice to have that provider as part of wagon > proper. -- 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: (MPIR-43) Use the plugin testing harness and add tests for the project-info-report mojos
[ http://jira.codehaus.org/browse/MPIR-43?page=all ] Brett Porter updated MPIR-43: - Fix Version: (was: 2.0) > Use the plugin testing harness and add tests for the project-info-report mojos > -- > > Key: MPIR-43 > URL: http://jira.codehaus.org/browse/MPIR-43 > Project: Maven 2.x Project Info Reports Plugin > Type: Test > Reporter: Edwin Punzalan > Assignee: Edwin Punzalan > > -- 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: (DOXIA-59) Doxia creates files with inconsistent new lines
[ http://jira.codehaus.org/browse/DOXIA-59?page=all ] Brett Porter updated DOXIA-59: -- Fix Version: (was: 1.0-alpha-8) 1.0 > Doxia creates files with inconsistent new lines > --- > > Key: DOXIA-59 > URL: http://jira.codehaus.org/browse/DOXIA-59 > Project: doxia > Type: Bug > Versions: 1.0-alpha-8 > Reporter: Carlos Sanchez > Fix For: 1.0 > Attachments: DOXIA-59-nramirez.patch > > > It uses \n instead of System.getProperty( line.separator ); -- 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: (MRELEASE-103) No SCM URL was provided to perform the release from
[ http://jira.codehaus.org/browse/MRELEASE-103?page=all ] Brett Porter updated MRELEASE-103: -- Fix Version: (was: 2.0-beta-4) 2.0 > No SCM URL was provided to perform the release from > --- > > Key: MRELEASE-103 > URL: http://jira.codehaus.org/browse/MRELEASE-103 > Project: Maven 2.x Release Plugin > Type: Bug > Environment: solaris > Reporter: Olivier Lamy > Priority: Blocker > Fix For: 2.0 > Attachments: olamy.tar.gz > > > The stack trace says : > DEBUG] Trace > org.apache.maven.BuildFailureException: No SCM URL was provided to perform > the release from > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor > .java:555) > I included a test case with multi modules project (you need to change scm url > in all poms to complete the test). > Strange because all scm parts are filled in all modules. > To test it, I launch ./buildis.sh $svnuser $svnpwd > Olivier -- 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: (MRELEASE-16) release-pom is changed too much
[ http://jira.codehaus.org/browse/MRELEASE-16?page=all ] Brett Porter updated MRELEASE-16: - Fix Version: (was: 2.0-beta-4) 2.0 > release-pom is changed too much > --- > > Key: MRELEASE-16 > URL: http://jira.codehaus.org/browse/MRELEASE-16 > Project: Maven 2.x Release Plugin > Type: Bug > Reporter: Brett Porter > Fix For: 2.0 > > > this needs a full review. > Expressions are populated that shouldn't be (only external settings should be > filled in, but not those like basedir or are otherwise path dependant like > project.file...) > basically need to use the pre-interpolation, post inheritence pom... or can > we live with the original one without inheritence and just fill in resolved > versions? -- 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: (MAVENUPLOAD-888) Upload Stripes 1.3.1 to IBiblio Repository
Upload Stripes 1.3.1 to IBiblio Repository -- Key: MAVENUPLOAD-888 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-888 Project: maven-upload-requests Type: Task Reporter: Tim Fennell -- 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] Moved: (MNG-2287) No reports are generated when executing the plugins on CLI instead of "mvn site"
[ http://jira.codehaus.org/browse/MNG-2287?page=all ] Brett Porter moved MPIR-44 to MNG-2287: --- Fix Version: (was: 2.0) 2.0.5 Complexity: Intermediate Key: MNG-2287 (was: MPIR-44) Project: Maven 2 (was: Maven 2.x Project Info Reports Plugin) > No reports are generated when executing the plugins on CLI instead of "mvn > site" > > > Key: MNG-2287 > URL: http://jira.codehaus.org/browse/MNG-2287 > Project: Maven 2 > Type: Bug > Reporter: Edwin Punzalan > Assignee: Brett Porter > Priority: Critical > Fix For: 2.0.5 > > > Currently, doing project-info-reports: does not generate a report. -- 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-2287) No reports are generated when executing the plugins on CLI instead of "mvn site"
[ http://jira.codehaus.org/browse/MNG-2287?page=comments#action_65083 ] Brett Porter commented on MNG-2287: --- my changes to the abstract maven report mean it gets rendered to a string, not a file. Any plugin that uses 2.0.4 of the reporting impl will need to override generate and work around it > No reports are generated when executing the plugins on CLI instead of "mvn > site" > > > Key: MNG-2287 > URL: http://jira.codehaus.org/browse/MNG-2287 > Project: Maven 2 > Type: Bug > Reporter: Edwin Punzalan > Assignee: Brett Porter > Priority: Critical > Fix For: 2.0.5 > > > Currently, doing project-info-reports: does not generate a report. -- 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: (MEJB-14) Make the ejb-jar.xml deployment descriptor optional (non-trivial clone)
Make the ejb-jar.xml deployment descriptor optional (non-trivial clone) --- Key: MEJB-14 URL: http://jira.codehaus.org/browse/MEJB-14 Project: Maven 2.x Ejb Plugin Type: Improvement Reporter: Dan Greening Priority: Trivial In the now near final EJB3 specification the use of deployment descripors is optional. It would be nice if the maven-ejb-plugin wouldn't bump out with an error if no descriptor is present. The attached patch introduces a new boolean configuration option 'enforceDeploymentDescriptor' which defaults to true so that the default behavior is not changed. Feel free to change the name of the property if appropriate. -- 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: (SCM-197) scm.url gets translated incorrectly during release
scm.url gets translated incorrectly during release -- Key: SCM-197 URL: http://jira.codehaus.org/browse/SCM-197 Project: Maven SCM Type: Bug Versions: 1.0-alpha-4 Reporter: Brian Fox Testing release 2.0-beta4. My original scm urls are like this: scm:svn:http://sv1.tus.stchome.com/svn/training/products/dsms/release-branches/dsms-2.1 scm:svn:http://sv1.tus.stchome.com/svn/training/products/dsms/release-branches/dsms-2.1 http://sv1.tus.stchome.com/viewvc/stc/products/dsms/release-branches/dsms-2.1 after the prepare, they end up like this: scm:svn:http://sv1.tus.stchome.com/svn/training/products/dsms/build-tags/t5 scm:svn:http://sv1.tus.stchome.com/svn/training/products/dsms/build-tags/t5 http://sv1.tus.stchome.com/svn/training/products/dsms/build-tags/t5 Notice the url lost the viewvc reference and ended up with a direct svn url. After a release:perform, the url ends up back to viewvc so only the tag is modified. -- 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: (MEJB-15) ejb-jar.xml file destroys annotation functionality in EJB3
ejb-jar.xml file destroys annotation functionality in EJB3 -- Key: MEJB-15 URL: http://jira.codehaus.org/browse/MEJB-15 Project: Maven 2.x Ejb Plugin Type: Bug Versions: 2.1 Environment: EJB3 Reporter: Dan Greening Priority: Critical Attachments: MEJB-6-maven-ejb-plugin.patch The EJB3 plugin requires an ejb-jar.xml file. But EJB3 does not require this file, and WORSE when that file is present, some appealing new annotation features get turned off. The current EJB plugin is a non-starter for serious EJB3 development. A couple of us jointly wrote a patch to look for 3.0 as a parameter to the EJB plugin. That patch is in issue MEJB-6. When ejbVersion is set to 3.*, the patched EJB maven plugin does not require META-INF/ejb-jar.xml, and we can use all the features of EJB3. Unfortunately, the JIRA issue where this is discussed is marked "trivial": MEJB-6 (http://jira.codehaus.org/browse/MEJB-6). The priority cannot be edited by mortals. The issue and our well-constructed (attached) patch has been ignored for 3 months. Who knows why Tim originally marked it "trivial", possibly because he wasn't using any of the new EJB3 features, but that poor choice of priority has probably doomed our patch to obscurity. (Of course, anyone seriously using EJB3 wouldn't think it was trivial.) Several people have asked for this patch to be applied, including Tim and Todd above, as well as myself and Wayne Fay. Who is responsible for this plugin? No one is assigned to fix it. There are 10 votes and 7 watchers waiting for the patch to be applied. Therefore I believe it justifies marking this problem "critical". It certainly is not trivial. MEJB-6 documents a full, well-structured patch supporting EJB 3.0, as well as retaining default behavior appropriate for EJB 2.x. The patch should be applied and a new EJB plugin released. -- 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-888) Upload Stripes 1.3.1 to IBiblio Repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-888?page=all ] Carlos Sanchez closed MAVENUPLOAD-888: -- Assign To: Carlos Sanchez Resolution: Fixed > Upload Stripes 1.3.1 to IBiblio Repository > -- > > Key: MAVENUPLOAD-888 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-888 > Project: maven-upload-requests > Type: Task > Reporter: Tim Fennell > Assignee: Carlos Sanchez > > -- 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-885) OpenWFE 1.7.0 upload request
[ http://jira.codehaus.org/browse/MAVENUPLOAD-885?page=all ] Carlos Sanchez closed MAVENUPLOAD-885: -- Assign To: Carlos Sanchez Resolution: Fixed > OpenWFE 1.7.0 upload request > > > Key: MAVENUPLOAD-885 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-885 > Project: maven-upload-requests > Type: Task > Reporter: John Mettraux > Assignee: Carlos Sanchez > > > http://openwfe.org/upload/openwfe-1.7.0-bundle.jar > http://openwfe.org/upload/openwfe-applic-1.7.0-bundle.jar > http://openwfe.org/upload/openwfe-embed-1.7.0-bundle.jar > http://openwfe.org/upload/openwfe-embed-wom-1.7.0-bundle.jar > http://openwfe.org/upload/openwfe-engine-1.7.0-bundle.jar > http://openwfe.org/upload/openwfe-engine-actions-1.7.0-bundle.jar > http://openwfe.org/upload/openwfe-worklist-1.7.0-bundle.jar > http://openwfe.org/upload/openwfe-worklist-actions-1.7.0-bundle.jar > OpenWFE is an open source workflow engine under a BSD license. > Thanks in advance, > John -- 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-884) dnsjava 2.0.1 bundle import
[ http://jira.codehaus.org/browse/MAVENUPLOAD-884?page=all ] Carlos Sanchez closed MAVENUPLOAD-884: -- Assign To: Carlos Sanchez Resolution: Fixed > dnsjava 2.0.1 bundle import > --- > > Key: MAVENUPLOAD-884 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-884 > Project: maven-upload-requests > Type: Task > Reporter: Stefano Bagnara > Assignee: Carlos Sanchez > > > I added few informations (license, url) to the pom.xml that is already in > maven2 repository for old releases. > I left the dnsjava groupid to be consistent with previous releases. If you > prefer I can resubmit this in the "org.xbill" groupid (same of the package) > or "org.dnsjava" groupid (as the sitename). -- 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-882) Please upload jgrapht version 0.6.0
[ http://jira.codehaus.org/browse/MAVENUPLOAD-882?page=comments#action_65086 ] Carlos Sanchez commented on MAVENUPLOAD-882: You need to add the minimal information stated in the instructions: license, url,... > Please upload jgrapht version 0.6.0 > --- > > Key: MAVENUPLOAD-882 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-882 > Project: maven-upload-requests > Type: Task > Reporter: jan hrabowski > > > I have been authorized by John V Sichi (perfecthash) > to create this upload request on behalf of the jgrapht project. Since I am > not part of that project, I have not created a new POM but simply copied the > version 0.5.3 POM and edited the version number information. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-880) org:acegisecurity:acegi-security-tiger-1.0.0-RC2 pom file missisng
[ http://jira.codehaus.org/browse/MAVENUPLOAD-880?page=all ] Carlos Sanchez closed MAVENUPLOAD-880: -- Assign To: Carlos Sanchez Resolution: Duplicate See MEV-387 > org:acegisecurity:acegi-security-tiger-1.0.0-RC2 pom file missisng > -- > > Key: MAVENUPLOAD-880 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-880 > Project: maven-upload-requests > Type: Task > Reporter: Ray Tsang > Assignee: Carlos Sanchez > > > http://www.ibiblio.org/maven2/org/acegisecurity/acegi-security-tiger/1.0.0-RC2/ > pom file is missing -- 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-887) please upload QALab plugin 0.9.0 for maven 1.x
[ http://jira.codehaus.org/browse/MAVENUPLOAD-887?page=all ] Carlos Sanchez closed MAVENUPLOAD-887: -- Assign To: Carlos Sanchez Resolution: Fixed > please upload QALab plugin 0.9.0 for maven 1.x > -- > > Key: MAVENUPLOAD-887 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-887 > Project: maven-upload-requests > Type: Task > Reporter: Benoit Xhenseval > Assignee: Carlos Sanchez > Attachments: maven-qalab-plugin-0.9.0-bundle.jar > > > This is a maven 1.x plugin. > thanks! -- 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-886) Please upload qalab 0.9.0
[ http://jira.codehaus.org/browse/MAVENUPLOAD-886?page=all ] Carlos Sanchez closed MAVENUPLOAD-886: -- Assign To: Carlos Sanchez Resolution: Fixed > Please upload qalab 0.9.0 > - > > Key: MAVENUPLOAD-886 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-886 > Project: maven-upload-requests > Type: Task > Reporter: Benoit Xhenseval > Assignee: Carlos Sanchez > Attachments: qalab-0.9.0-bundle.jar > > > Thanks. -- 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: (MJAVADOC-70) {inceptionYear} is not evaluated when inceptionYear is not specified in pom.
{inceptionYear} is not evaluated when inceptionYear is not specified in pom.
Key: MJAVADOC-70
URL: http://jira.codehaus.org/browse/MJAVADOC-70
Project: Maven 2.x Javadoc Plugin
Type: Bug
Versions: 2.0-beta-3
Reporter: Henry S. Isidro
Priority: Minor
Fix For: 2.0-beta-3
Attachments: maven-javadoc-plugin.patch
The javadoc site shows {inceptionYear} if the inceptionYear parameter is not
set in pom.xml. The attached patch remedies this.
--
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-874) CoWarp 0.5 Release
[ http://jira.codehaus.org/browse/MAVENUPLOAD-874?page=comments#action_65089 ] Carlos Sanchez commented on MAVENUPLOAD-874: it will be a mess if you depend on snapshots that continously change. You can upload whatever you want under your group. You can't depend on something that is not in ibiblio or nobody would be able to use it. The best option of course is convincing other people to make releases of their projects. > CoWarp 0.5 Release > -- > > Key: MAVENUPLOAD-874 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-874 > Project: maven-upload-requests > Type: Task > Reporter: Carsten Ziegeler > > > This is the latest release of CoWarp - an extension to the Apache Cocoon > project. -- 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-871) Upload request for SLF4J version 1.0.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-871?page=all ] Carlos Sanchez closed MAVENUPLOAD-871: -- Assign To: Carlos Sanchez Resolution: Fixed > Upload request for SLF4J version 1.0.1 > -- > > Key: MAVENUPLOAD-871 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-871 > Project: maven-upload-requests > Type: Task > Reporter: Ceki Gulcu > Assignee: Carlos Sanchez > Attachments: jcl104-over-slf4j-1.0.1-bundle.jar, slf4j-jcl-1.0.1-bundle.jar, > slf4j-jcl-1.0.1-bundle.jar, slf4j-jdk14-1.0.1-bundle.jar, > slf4j-jdk14-1.0.1-bundle.jar, slf4j-log4j12-1.0.1-bundle.jar, > slf4j-log4j12-1.0.1-bundle.jar, slf4j-log4j13-1.0.1-bundle.jar, > slf4j-log4j13-1.0.1-bundle.jar, slf4j-nop-1.0.1-bundle.jar, > slf4j-nop-1.0.1-bundle.jar, slf4j-simple-1.0.1-bundle.jar, > slf4j-simple-1.0.1-bundle.jar > > -- 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-873) Upload JAI POMs
[ http://jira.codehaus.org/browse/MAVENUPLOAD-873?page=all ] Carlos Sanchez closed MAVENUPLOAD-873: -- Assign To: Carlos Sanchez Resolution: Fixed > Upload JAI POMs > --- > > Key: MAVENUPLOAD-873 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-873 > Project: maven-upload-requests > Type: Task > Reporter: Joerg Schaible > Assignee: Carlos Sanchez > > > POMs for JAI are missing on ibiblio. > Additional bundles: > http://people.apache.org/~joehni/jai_codec-1.1.2.1-bundle.jar > http://people.apache.org/~joehni/jai_imageio-1.0.1-bundle.jar -- 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-867) slf4j 1.0 sources
[ http://jira.codehaus.org/browse/MAVENUPLOAD-867?page=all ] Carlos Sanchez closed MAVENUPLOAD-867: -- Assign To: Carlos Sanchez Resolution: Fixed > slf4j 1.0 sources > - > > Key: MAVENUPLOAD-867 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-867 > Project: maven-upload-requests > Type: Task > Reporter: fabrizio giustina > Assignee: Carlos Sanchez > > > The following bundles contain source jars for the slf4j 1.0 release. > Binary jars are the same actually stored in the ibiblio repo, poms are the > same + the addition of project url and license name/url that were missing in > the original ones > http://magnolia.sourceforge.net/bundles/slf4j-jcl-1.0-bundle.jar > http://magnolia.sourceforge.net/bundles/slf4j-jdk14-1.0-bundle.jar > http://magnolia.sourceforge.net/bundles/slf4j-log4j12-1.0-bundle.jar > http://magnolia.sourceforge.net/bundles/slf4j-log4j13-1.0-bundle.jar > http://magnolia.sourceforge.net/bundles/slf4j-nop-1.0-bundle.jar > http://magnolia.sourceforge.net/bundles/slf4j-simple-1.0-bundle.jar -- 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-866) UISpec4J is an Open Source functional and/or unit testing library for Swing-based Java applications, built on top of the JUnit test harness.
[ http://jira.codehaus.org/browse/MAVENUPLOAD-866?page=all ] Carlos Sanchez closed MAVENUPLOAD-866: -- Assign To: Carlos Sanchez Resolution: Fixed > UISpec4J is an Open Source functional and/or unit testing library for > Swing-based Java applications, built on top of the JUnit test harness. > > > Key: MAVENUPLOAD-866 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-866 > Project: maven-upload-requests > Type: Task > Reporter: Sylvain Rousseau > Assignee: Carlos Sanchez > > > UISpec4J: Java GUI testing made simple! > If you are writing a Swing application, you will appreciate UISpec4J above > all for its simplicity: UISpec4J's APIs are designed to hide as much as > possible the complexity of Swing, resulting in easy to write and easy to read > test scripts. This is especially true when comparing UISpec4J tests with > those produced using Swing or low-level, event-based testing libraries. -- 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-858) Upload Click 0.19 bundles
[ http://jira.codehaus.org/browse/MAVENUPLOAD-858?page=all ] Carlos Sanchez closed MAVENUPLOAD-858: -- Assign To: Carlos Sanchez (was: John Casey) Resolution: Fixed > Upload Click 0.19 bundles > - > > Key: MAVENUPLOAD-858 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-858 > Project: maven-upload-requests > Type: Task > Reporter: Malcolm Edgar > Assignee: Carlos Sanchez > > > Please upload the following Click 0.19 maven bundles: > http://click.sourceforge.net/click-maven-bundle/click-0.19-bundle.jar > http://click.sourceforge.net/click-maven-bundle/click-nodeps-0.19-bundle.jar > http://click.sourceforge.net/click-maven-bundle/click-extras-0.19-bundle.jar > Thanks for your help > regards Malcolm Edgar -- 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-801) Add JBoss-4.0.3SP1 scheduler
[ http://jira.codehaus.org/browse/MAVENUPLOAD-801?page=all ] Carlos Sanchez closed MAVENUPLOAD-801: -- Assign To: Carlos Sanchez Resolution: Incomplete > Add JBoss-4.0.3SP1 scheduler > > > Key: MAVENUPLOAD-801 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-801 > Project: maven-upload-requests > Type: Task > Reporter: yan > Assignee: Carlos Sanchez > > > his is JBoss Application Server Client > JBoss Application Server is a J2EE certified platform for developing and > deploying enterprise Java applications, Web applications, and Portals. It > provides the full range of J2EE 1.4 features as well as extended enterprise > services including clustering, caching, and persistence. -- 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-827) SVG Salamander - tools and utilities for parsing and rendering SVG
[ http://jira.codehaus.org/browse/MAVENUPLOAD-827?page=all ] Carlos Sanchez closed MAVENUPLOAD-827: -- Assign To: Carlos Sanchez (was: John Casey) Resolution: Incomplete > SVG Salamander - tools and utilities for parsing and rendering SVG > -- > > Key: MAVENUPLOAD-827 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-827 > Project: maven-upload-requests > Type: Task > Reporter: Mark McKay > Assignee: Carlos Sanchez > > > https://svgsalamander.dev.java.net > Owner email is on same page, linked to from the owner 'kitfox': [EMAIL > PROTECTED] > This is a libaray that allows inclusion of SVG content in Java programs. > Includes a parser, modifiable scene graph, a 'universe' to organize several > SVG documents and allow them to reference one another, swing components to > render SVG documents, SMIL animation, and a player application for stand > alone viewing and animation of SVG documents. Also allows rendering of SVG > content to any Graphics2D. -- 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-798) Add JBoss-client4.0.3SP1.jar
[ http://jira.codehaus.org/browse/MAVENUPLOAD-798?page=all ] Carlos Sanchez closed MAVENUPLOAD-798: -- Assign To: Carlos Sanchez Resolution: Incomplete > Add JBoss-client4.0.3SP1.jar > > > Key: MAVENUPLOAD-798 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-798 > Project: maven-upload-requests > Type: Task > Reporter: yan > Assignee: Carlos Sanchez > > > This is JBoss Application Server Client > JBoss Application Server is a J2EE certified platform for developing and > deploying enterprise Java applications, Web applications, and Portals. It > provides the full range of J2EE 1.4 features as well as extended enterprise > services including clustering, caching, and persistence. -- 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: (MWAR-5) warSourceExcludes not working properly
[ http://jira.codehaus.org/browse/MWAR-5?page=comments#action_65090 ]
Edwin Punzalan commented on MWAR-5:
---
Unfortunately, not yet. There are efforts in testing the war plugin prior to
release. And I think the release will be soon.
> warSourceExcludes not working properly
> --
>
> Key: MWAR-5
> URL: http://jira.codehaus.org/browse/MWAR-5
> Project: Maven 2.x War Plugin
> Type: Bug
> Environment: Win2k, Java 1.4.2_04, m2 beta1
> Reporter: Fabrice BELLINGARD
> Assignee: Edwin Punzalan
> Fix For: 2.0
> Attachments: MNG-1038-maven-war-plugin.patch, MNG-1038-maven-war-plugin.patch
>
>
> Note: I posted a message on Maven users list
> (http://www.mail-archive.com/users%40maven.apache.org/msg24088.html), but I
> got no answer so I post this issue, which in turn may or not be a bug...
> (sorry if it's not)
> I experienced a strange behaviour with the 'warSourceExcludes' property. When
> I grab some Web projects from the CVS of my company, I usually get all the
> WEB-INF/lib Jars that the developers put in the CVS:
> - With Maven 1, I use the 'maven.war.src.excludes' property to exclude those
> Jars ('maven.war.src.excludes=**/lib/*.*'), and it works well: the Jars
> packaged in the War are only the ones defined in the pom.
> - With m2, I tried to use the 'warSourceExcludes' property, which seemed to
> me to be the equivalent property. However, when the War is generated, there
> is no jar in the WEB-INF/lib folder. This works as if the plugin is excluding
> files after having copied the needed dependencies in the WEB-INF/lib folder
> (whereas in the Maven 1 version, it was excluding them before).
> Looking at the code of the m2 plugin, the value of 'warSourceExcludes' is
> used in method #getExcludes which is actually called in #performPackaging
> method. If this property is to work the same way as in m1, its value should
> be used in #copyResources method, before copying the Jar dependencies in
> WEB-INF/lib.
> What do you guys think of that? Am I right or am I missing something?
--
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-800) Add JBoss-4.0.3 jars
[ http://jira.codehaus.org/browse/MAVENUPLOAD-800?page=all ] Carlos Sanchez closed MAVENUPLOAD-800: -- Assign To: Carlos Sanchez Resolution: Incomplete > Add JBoss-4.0.3 jars > > > Key: MAVENUPLOAD-800 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-800 > Project: maven-upload-requests > Type: Task > Reporter: yan > Assignee: Carlos Sanchez > > > This is JBoss Application Server Client > JBoss Application Server is a J2EE certified platform for developing and > deploying enterprise Java applications, Web applications, and Portals. It > provides the full range of J2EE 1.4 features as well as extended enterprise > services including clustering, caching, and persistence. -- 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: (MEV-387) Acegi 1.0.0-RC2 POM missing
[ http://jira.codehaus.org/browse/MEV-387?page=all ] Carlos Sanchez closed MEV-387: -- Assign To: Carlos Sanchez Resolution: Duplicate See MEV-381 > Acegi 1.0.0-RC2 POM missing > --- > > Key: MEV-387 > URL: http://jira.codehaus.org/browse/MEV-387 > Project: Maven Evangelism > Type: Bug > Components: Missing POM > Reporter: Ralph Poellath > Assignee: Carlos Sanchez > > > There's no POM in > http://www.ibiblio.org/maven2/org/acegisecurity/acegi-security/1.0.0-RC2/ > It might be sufficient to copy > http://www.ibiblio.org/maven2/org/acegisecurity/acegi-security/1.0.0-RC1/acegi-security-1.0.0-RC1.pom > and update the version number. -- 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-2286) Uploading missing jar files
[ http://jira.codehaus.org/browse/MNG-2286?page=comments#action_65092 ] Wayne Fay commented on MNG-2286: Just FYI to Sanket (and Carlos)... Project Glassfish is going to be releasing these jar files (though probably not these exact versions) under the CDDL license in the java.net repository at some point in the coming weeks/months. You can see that activation, connector-api, jacc-api, transaction-api, and mail have all been recently released under CDDL license on this Glassfish page: http://wiki.java.net/bin/view/Projects/GlassFishCodeDependencies So eventually all of these artifacts *will* be released in binary form under the CDDL, and then we can talk about providing them on ibiblio etc. > Uploading missing jar files > --- > > Key: MNG-2286 > URL: http://jira.codehaus.org/browse/MNG-2286 > Project: Maven 2 > Type: Improvement > Versions: 2.0.5 > Reporter: Sanket Desai > Assignee: Carlos Sanchez > Attachments: missing-jar-files.zip > > > maven2 repos @ ibiblio is missing some important jar files: > 1) activation-1.0.2.jar (group Id: javax.activation, artifactId : activation, > Version: 1.0.2) > can be obtained from http://java.sun.com/products/javabeans/jaf/index.jsp > 2) connector-1.0.jar (group Id: javax.resource, artifactId : connector, > Version: 1.0) > can be obtained from http://java.sun.com/j2ee/connector/index.jsp > 3) jacc-1.0.jar (group Id: javax.security, artifactId : jacc, Version: 1.0) > can be obtained from http://java.sun.com/products/javabeans/jaf/index.jsp > 4) jta-1.0.1B.jar (group Id: javax.transaction, artifactId : jta, Version: > 1.0.1B) > can be obtained from http://java.sun.com/products/jta > In some of the websites where the jar can be downloaded, there is a ZIP file > available with class files in them. > One will need to jar them up with specified name. > Note: I've also attached the zip file containing all the jar files. > 5) mail-1.3.2.jar (group Id: javax.activation, artifactId : activation, > Version: 1.0.2) > can be obtained from : http://java.sun.com/products/javamail/index.jsp -- 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: (MEV-386) FOP 0.20.5 dependencies
[ http://jira.codehaus.org/browse/MEV-386?page=all ] Carlos Sanchez closed MEV-386: -- Assign To: Carlos Sanchez Resolution: Fixed > FOP 0.20.5 dependencies > --- > > Key: MEV-386 > URL: http://jira.codehaus.org/browse/MEV-386 > Project: Maven Evangelism > Type: Improvement > Components: Missing POM > Reporter: Joerg Schaible > Assignee: Carlos Sanchez > Attachments: fop-0.20.5.patch, fop-0.20.5.patch, fop-0.20.5.patch > > > The POM of fop:fop:0.20.5 was generated from M1 repo and misses all > dependencies. -- 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: (MEV-385) velocity-dep 1.4 should be relocated to velocity 1.4
[ http://jira.codehaus.org/browse/MEV-385?page=all ] Carlos Sanchez closed MEV-385: -- Assign To: Carlos Sanchez Resolution: Won't Fix As I said if they want to bundle everything it's ok. Users shouldn't use it though. > velocity-dep 1.4 should be relocated to velocity 1.4 > > > Key: MEV-385 > URL: http://jira.codehaus.org/browse/MEV-385 > Project: Maven Evangelism > Type: Bug > Reporter: fabrizio giustina > Assignee: Carlos Sanchez > > > After fixing MEV-384 (velocity 1.4 dependencies) velocity-dep 1.4 should be > relocated to velocity 1.4. > Velocity-dep-1.4.jar is the same as velocity-1.4.jar PLUS logkit, oro and > commons-collections packaged together. Since maven already manages transitive > dependencies it makes no sense providing a single jar with everything > packaged together for easier deploy. > Now projects always end up having two copies of the velocity jars in the > classpath (velocity and velocity-dep are usually both included in > dependencies). > Even worse, your project may depend on a specific version of oro or logkit, > newer than the one in the velocity-dep jar: in that case you will end up > having two different versions of those libraries in the classpath, one of > them hidden in the velocity-dep jar (and so very difficult to detect). That > could cause nasty problems, and maven can't help in selecting only the > version you really need in your project... -- 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: (MEV-363) Spring 1.2.7 POMs Missing
[ http://jira.codehaus.org/browse/MEV-363?page=all ] Carlos Sanchez closed MEV-363: -- Assign To: Carlos Sanchez Resolution: Fixed > Spring 1.2.7 POMs Missing > - > > Key: MEV-363 > URL: http://jira.codehaus.org/browse/MEV-363 > Project: Maven Evangelism > Type: Bug > Components: Missing POM > Reporter: Stephen Duncan Jr > Assignee: Carlos Sanchez > Attachments: spring-poms-1.2.7.zip, spring-poms-1.2.7.zip > > > All Spring 1.2.7 jars need POMs added. POMs should be duplicates of Spring > 1.2.6 but with the following other MEV issues taken into account: > http://jira.codehaus.org/browse/MEV-316 and > http://jira.codehaus.org/browse/MEV-277 -- 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: (MEV-381) Missing pom.xml for acegi-security-1.0.0-RC2
[ http://jira.codehaus.org/browse/MEV-381?page=all ] Carlos Sanchez closed MEV-381: -- Assign To: Carlos Sanchez Resolution: Fixed Added and changed snapshot versions and removed custom repos > Missing pom.xml for acegi-security-1.0.0-RC2 > > > Key: MEV-381 > URL: http://jira.codehaus.org/browse/MEV-381 > Project: Maven Evangelism > Type: Bug > Reporter: Julien Dubois > Assignee: Carlos Sanchez > Attachments: acegi-security-1.0.0-RC2.zip > > > pom.xml files are missing for acegi-security-1.0.0-RC2 > I created my own files from Acegi security's subversion repository, I'll > upload them ASAP. -- 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: (MEV-353) I need to have these 4 pom's posted to reference some bea 3rd party artifacts to support the weblogic plugin
[ http://jira.codehaus.org/browse/MEV-353?page=all ] Carlos Sanchez closed MEV-353: -- Assign To: Carlos Sanchez Resolution: Incomplete > I need to have these 4 pom's posted to reference some bea 3rd party artifacts > to support the weblogic plugin > > > Key: MEV-353 > URL: http://jira.codehaus.org/browse/MEV-353 > Project: Maven Evangelism > Type: Task > Components: Missing POM > Reporter: Scott Ryan > Assignee: Carlos Sanchez > Attachments: weblogic-8.1.pom, weblogic-8.1.pom.txt, weblogic-9.0.pom, > weblogic-9.0.pom.txt, webservices-8.1.pom, webservices-8.1.pom.txt, > webservices-9.0.pom, webservices-9.0.pom.txt > > > I am attaching 4 pom files to support the weblogic plugin. These will allow > local installation of the 3rd party jars and still support clean builds with > the weblogic plugin. Please feel free to correct me or ask any additional > questions needed to get this done. > thanks -- 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
