[jira] Closed: (MAVENUPLOAD-903) Please upload missing jars for findbugs 0.9.4
[ http://jira.codehaus.org/browse/MAVENUPLOAD-903?page=all ] Carlos Sanchez closed MAVENUPLOAD-903: -- Assign To: Carlos Sanchez Resolution: Fixed > Please upload missing jars for findbugs 0.9.4 > - > > Key: MAVENUPLOAD-903 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-903 > Project: maven-upload-requests > Type: Task > Reporter: Lukas Theussl > Assignee: Carlos Sanchez > > > http://people.apache.org/~ltheussl/coreplugin-0.9.4-bundle.jar > http://people.apache.org/~ltheussl/findbugs-ant-0.9.4-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-917) hibernate 3.2.0.cr2
[ http://jira.codehaus.org/browse/MAVENUPLOAD-917?page=all ] Carlos Sanchez closed MAVENUPLOAD-917: -- Assign To: Carlos Sanchez Resolution: Fixed > hibernate 3.2.0.cr2 > --- > > Key: MAVENUPLOAD-917 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-917 > Project: maven-upload-requests > Type: Task > Reporter: fabrizio giustina > 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] Created: (MSUREFIRE-122) Support tests written in Jython
Support tests written in Jython --- Key: MSUREFIRE-122 URL: http://jira.codehaus.org/browse/MSUREFIRE-122 Project: Maven 2.x Surefire Plugin Type: New Feature Reporter: Charlie Groves Attachments: jythonProvider.tar.gz I've written a first pass at a surefire-provider for JUnit and Python unittest TestCases written in Jython. Before I continue any further I'd like to make sure that the provider is wanted and that I'm heading in the right direction. To do the minimum to get it up and running, I've hooked into the maven-surefire-plugin to hook my provider into the system somewhat like the TestNG provider did. maven-surefire-plugin passes a path(defaults to src/test/jython) to the provider. The provider searches the path for files matching include patterns and loads those as Python modules. For every class in the matching modules that extends junit or unittest TestCase, it makes a SurefireTestSuite and exposes them for running. Sound like a decent approach? To give it a spin, apply maven-surefire-plugin.patch, mvn install on the surefire-jython project and run mvn test in jythonProviderTest. It's just contains a single Junit testcase with a failing and passing test. I haven't even checked what happens when the jython tests throw exceptions, and I know there's alot to be done as far as making it a usable plugin, but I felt like getting some feedback before continuing. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly 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-918) hibernate annotations 3.2.0.cr1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-918?page=all ] Carlos Sanchez closed MAVENUPLOAD-918: -- Assign To: Carlos Sanchez Resolution: Fixed > hibernate annotations 3.2.0.cr1 > --- > > Key: MAVENUPLOAD-918 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-918 > Project: maven-upload-requests > Type: Task > Reporter: fabrizio giustina > 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-897) snmp4j 1.7.1 jar
[ http://jira.codehaus.org/browse/MAVENUPLOAD-897?page=all ] Carlos Sanchez closed MAVENUPLOAD-897: -- Resolution: Fixed > snmp4j 1.7.1 jar > > > Key: MAVENUPLOAD-897 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-897 > Project: maven-upload-requests > Type: Task > Reporter: Dan Diephouse > Assignee: Carlos Sanchez > Attachments: snmp4j-bundle.jar > > > http://snmp4j.org/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly 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-909) Upload ajaxtags-1.2-beta2
[ http://jira.codehaus.org/browse/MAVENUPLOAD-909?page=all ] Carlos Sanchez closed MAVENUPLOAD-909: -- Assign To: Carlos Sanchez Resolution: Fixed > Upload ajaxtags-1.2-beta2 > - > > Key: MAVENUPLOAD-909 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-909 > Project: maven-upload-requests > Type: Bug > Reporter: Tomislav Stojcevich > Assignee: Carlos Sanchez > Attachments: ajaxtags-1.2-beta2-bundle.jar > > > Upload ajaxtags-1.2-beta2 with sources. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly 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-910) Please upload ldaptemplate 1.0.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-910?page=all ] Carlos Sanchez closed MAVENUPLOAD-910: -- Assign To: Carlos Sanchez Resolution: Fixed > Please upload ldaptemplate 1.0.1 > > > Key: MAVENUPLOAD-910 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-910 > Project: maven-upload-requests > Type: Task > Reporter: Alexandre Poitras > Assignee: Carlos Sanchez > Attachments: ldaptemplate-1.0.1.jar, ldaptemplate-1.0.1.jar > > > attached > http://ldaptemplate.sourceforge.net/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-906) Add sources to commons-httpclient-3.0.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-906?page=all ] Carlos Sanchez closed MAVENUPLOAD-906: -- Assign To: Carlos Sanchez Resolution: Fixed > Add sources to commons-httpclient-3.0.1 > --- > > Key: MAVENUPLOAD-906 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-906 > Project: maven-upload-requests > Type: Bug > Reporter: Tomislav Stojcevich > Assignee: Carlos Sanchez > Attachments: commons-httpclient-3.0.1-bundle.jar > > > Add sources only from bundle. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly 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-913) Upload request for new version of jcifs 1.2.9
[ http://jira.codehaus.org/browse/MAVENUPLOAD-913?page=all ] Carlos Sanchez closed MAVENUPLOAD-913: -- Assign To: Carlos Sanchez Resolution: Fixed > Upload request for new version of jcifs 1.2.9 > - > > Key: MAVENUPLOAD-913 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-913 > Project: maven-upload-requests > Type: Task > Reporter: Deenar Toraskar > Assignee: Carlos Sanchez > Attachments: jcifs-1.2.9.jar > > > http://jcifs.samba.org/ > JCIFS is an Open Source client library that implements the CIFS/SMB > networking protocol in 100% Java. CIFS is the standard file sharing protocol > on the Microsoft Windows platform (e.g. Map Network Drive ...). This client > is used extensively in production on large Intranets. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly 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: (MSUREFIRE-121) ability to add dependency to jvm's classpath rather in surefirebooter classloader
[ http://jira.codehaus.org/browse/MSUREFIRE-121?page=comments#action_66056 ] Trygve Laugstol commented on MSUREFIRE-121: --- The boot class path is not the same classpath as -classpath, which one are you really after here? I'm pretty sure the boot class path is an optional class path (it might be the same as -classpath). > ability to add dependency to jvm's classpath rather in surefirebooter > classloader > - > > Key: MSUREFIRE-121 > URL: http://jira.codehaus.org/browse/MSUREFIRE-121 > Project: Maven 2.x Surefire Plugin > Type: Bug > Versions: 2.2 > Environment: xp > Reporter: Dan Tran > Fix For: 2.3 > Attachments: MSUREFIRE-121-booter.patch, MSUREFIRE-121.plugin.patch > > > I have a usecase where i have a jar file got loaded by -Xbootclasspath, that > jar file then loads classes from another jar ( my dependency) > expected in the classpath. > The problem is that surefire plugin does not add my dependencies at JVM > commanline thru -classpath option, but after the JVM starts -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSITE-131) Not inheriting the site settings for distributionManagement from a super pom
[ http://jira.codehaus.org/browse/MSITE-131?page=comments#action_66058 ] Wahid Bashirazad commented on MSITE-131: After moving the distributionManagement settings for site into the parent pom nothing deploy despite the follwing log output: [INFO] [site:deploy] file:iis/webs/wwwroot/projects/childProject - Session: Opened file:iis/webs/wwwroot/projects/childProject - Session: Disconnecting file:iis/webs/wwwroot/projects/childProject - Session: Disconnected [INFO] --- [INFO] BUILD SUCCESSFUL > Not inheriting the site settings for distributionManagement from a super pom > > > Key: MSITE-131 > URL: http://jira.codehaus.org/browse/MSITE-131 > Project: Maven 2.x Site Plugin > Type: Bug > Reporter: Malcolm Wong Ho > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly 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: (MECLIPSE-76) Projects containing war's as dependency will not include war-reference
[ http://jira.codehaus.org/browse/MECLIPSE-76?page=comments#action_66060 ]
Tom Spengler commented on MECLIPSE-76:
--
and how you will debug a war-project ??
> Projects containing war's as dependency will not include war-reference
> --
>
> Key: MECLIPSE-76
> URL: http://jira.codehaus.org/browse/MECLIPSE-76
> Project: Maven 2.x Eclipse Plugin
> Type: Bug
> Reporter: Tom Spengler
>
>
> if you have a dependency like
>
> j-core
> j-core-webapp-axx
> 0.0.1
> war
>
> it will not included int .classpath
> Resolution could be
> EclipseClasspathWriter
> --old--
> Artifact artifact = (Artifact) it.next();
> if ( artifact.getArtifactHandler().isAddedToClasspath() )
> --new --
> Artifact artifact = (Artifact) it.next();
> if ( artifact.getArtifactHandler().isAddedToClasspath()
> ||artifact.getArtifactHandler().isIncludesDependencies() )
>
> and
> EclipsePlugin.prepareArtifacts()
> --old--
> Collection artifacts = project.getTestArtifacts();
> --new--
> Collection artifacts = project.getTestArtifacts();
> Set artifact_2 = project.getArtifacts();
> for (Iterator at = artifact_2.iterator(); at.hasNext();){
> Artifact arti = (Artifact) at.next();
> if (! artifacts.contains(arti))
> artifacts.add(arti);
> }
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly 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-123) release plugin does not take commandline parameters into account
release plugin does not take commandline parameters into account Key: MRELEASE-123 URL: http://jira.codehaus.org/browse/MRELEASE-123 Project: Maven 2.x Release Plugin Type: Bug Versions: 2.0-beta-4 Reporter: Jorg Heymans i would like to do a release of a top-level pom only : intuitively i do "mvn -N release:prepare". During release preparation the -N parameter is left out however and maven does a full integration on all child modules and subsequently includes them in the release process. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly 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-127) Reindexing Local is too expensive to do it on every restart
Reindexing Local is too expensive to do it on every restart --- Key: MNGECLIPSE-127 URL: http://jira.codehaus.org/browse/MNGECLIPSE-127 Project: Maven 2.x Extension for Eclipse Type: Bug Versions: 0.0.7 Environment: Laptop with Windows XP, Pentium 4 2.4Ghz, 512Mb Reporter: Abel Muiño Assigned to: Eugene Kuleshov Priority: Minor When starting Eclipse with m2 projects on the workspace, the m2 plugin starts "Indexing Local". This makes my laptop almost unusable for several minutes (it is less noticeable on more modern machines). * index once, keep MD5 (or some other info) about each indexed artifact. * persist the generated index. * on restart, check each file. ** If it is new or its MD5 has changed, reindex that file. ** Otherwise, use the persisted index. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly 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-123) release plugin does not take commandline parameters into account
[ http://jira.codehaus.org/browse/MRELEASE-123?page=comments#action_66063 ] Feniks Nator commented on MRELEASE-123: --- I'm having the same kind of problem here. I want to do a release using the special settings.xml (because we let continuum build the artifact) file so I ran: mvn release:perform -e -s %MAVEN_HOME%\conf\settings_continuum.xml -DconnectionUrl=... As part of the release perform maven launches also the following: [INFO] Executing: mvn deploy site-deploy --no-plugin-updates -P continuum,defaultprofile,continuum -DperformRelease=true WITHOUT taking the original command-line arguments into account (which is a rather unexpected behavior, I find) > release plugin does not take commandline parameters into account > > > Key: MRELEASE-123 > URL: http://jira.codehaus.org/browse/MRELEASE-123 > Project: Maven 2.x Release Plugin > Type: Bug > Versions: 2.0-beta-4 > Reporter: Jorg Heymans > > > i would like to do a release of a top-level pom only : intuitively i do "mvn > -N release:prepare". During release preparation the -N parameter is left out > however and maven does a full integration on all child modules and > subsequently includes them in the release process. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly 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-123) release plugin does not take commandline parameters into account
[ http://jira.codehaus.org/browse/MRELEASE-123?page=comments#action_66064 ] Olivier Lamy commented on MRELEASE-123: --- try with -Darguments="-N" -- Olivier > release plugin does not take commandline parameters into account > > > Key: MRELEASE-123 > URL: http://jira.codehaus.org/browse/MRELEASE-123 > Project: Maven 2.x Release Plugin > Type: Bug > Versions: 2.0-beta-4 > Reporter: Jorg Heymans > > > i would like to do a release of a top-level pom only : intuitively i do "mvn > -N release:prepare". During release preparation the -N parameter is left out > however and maven does a full integration on all child modules and > subsequently includes them in the release process. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly 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-123) release plugin does not take commandline parameters into account
[ http://jira.codehaus.org/browse/MRELEASE-123?page=comments#action_66066 ] Grzegorz Slowikowski commented on MRELEASE-123: --- Hi I had the same problem. -Darguments helps, but I think it's for non-standard parameters, eg. -Darguments="-Dmaven.test.skip=true", which are not on mvn release:prepare command line. I don't know which ones, but -N should definitely be copied to invoked command line because it means that I don't want subprojects to be released so nothing should be done to them. Greg > release plugin does not take commandline parameters into account > > > Key: MRELEASE-123 > URL: http://jira.codehaus.org/browse/MRELEASE-123 > Project: Maven 2.x Release Plugin > Type: Bug > Versions: 2.0-beta-4 > Reporter: Jorg Heymans > > > i would like to do a release of a top-level pom only : intuitively i do "mvn > -N release:prepare". During release preparation the -N parameter is left out > however and maven does a full integration on all child modules and > subsequently includes them in the release process. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly 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-111) Additional webResources are not added to the component list when using WTP projects generation
Additional webResources are not added to the component list when using WTP
projects generation
--
Key: MECLIPSE-111
URL: http://jira.codehaus.org/browse/MECLIPSE-111
Project: Maven 2.x Eclipse Plugin
Type: Bug
Versions: 2.2
Reporter: Renaud Julienne
I have a war project, with the standard layout :
+ project
+ src
+ main
+ java
+ resources
+ webapp
But my project is also relying on a common web application framework,
containing web resources I must add to my project.
So in the pom.xml, for the maven-war-plugin configuration, I have additional
webResources declared :
maven-war-plugin
${project.build.directory}/fwk
When I generate the eclipse project, with WTP activated, the .component
generated does not include the wb-resource element corresponding to my
webResource. It should contain :
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly 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-923) Incoherences / duplication between javax.xml and com.sun.xml
Incoherences / duplication between javax.xml and com.sun.xml Key: MAVENUPLOAD-923 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-923 Project: maven-upload-requests Type: Bug Reporter: Guillaume Nodet See http://repo.mergere.com/maven2/javax/xml/jaxb-impl/2.0EA3/jaxb-impl-2.0EA3.pom and http://repo.mergere.com/maven2/com/sun/xml/jaxb-impl/2.0EA3/jaxb-impl-2.0EA3.pom See http://repo.mergere.com/maven2/com/sun/xml/jaxb-xjc/2.0EA3/jaxb-xjc-2.0EA3.pom and http://repo.mergere.com/maven2/javax/xml/jaxb-xjc/2.0EA3/jaxb-xjc-2.0EA3.pom If the javax.xml is to be preferred for the implementation RI, i guess that the com/sun/xml should redirect to javax.xml artifacts. Note that the poms in com.sun.xml have dependencies whereas javax.xml poms have none. So they need to be updated according to the con.sun.xml ones. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (CONTINUUM-714) SCM Connection for PVCS / Serena Version Manager
SCM Connection for PVCS / Serena Version Manager Key: CONTINUUM-714 URL: http://jira.codehaus.org/browse/CONTINUUM-714 Project: Continuum Type: New Feature Components: Core system Versions: 1.0.3 Environment: All Reporter: Thorsten Düvelmeyer A scm connection to Serena Version Manger (PVCS) would be very useful. As far as i know, PVCS has the largest number of commercial scm tool installations. Therefor it would be a great feature to have a direct scm connection and not only file as scm provider. Regards, Thorsten -- This message is automatically generated by JIRA. - If you think it was sent incorrectly 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-924) vafer.org dependency bundle
vafer.org dependency bundle --- Key: MAVENUPLOAD-924 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-924 Project: maven-upload-requests Type: Task Reporter: Torsten Curdt I need it for maven and mojo! Please upload! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-922) JavaNCSS 25.45
[ http://jira.codehaus.org/browse/MAVENUPLOAD-922?page=comments#action_66068 ] Mike Perham commented on MAVENUPLOAD-922: - The javancss POM does not contain the dependencies required. I'm preparing revision 2 of this zip right now. > JavaNCSS 25.45 > -- > > Key: MAVENUPLOAD-922 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-922 > Project: maven-upload-requests > Type: Task > Reporter: Mike Perham > Attachments: javancss.zip > > > JavaNCSS is not a Maven 2 project so I cannot create an upload bundle for it. > I have deployed its jars and the attached zip contains the repository > contents after the deploy process is complete. > This version is required for the upcoming javancss-maven-plugin release. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly 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: (MSUREFIRE-121) ability to add dependency to jvm's classpath rather in surefirebooter classloader
[ http://jira.codehaus.org/browse/MSUREFIRE-121?page=comments#action_66070
]
Dan Tran commented on MSUREFIRE-121:
I am after placing the project dedendencies on the -classpath list of the fork
command
My surefire plugin would look like this
maven-surefire-plugin
once
${project.build.directory}
-Xrunpri:${basedir}/src/test/resources/optimizeit.xml
-Xbootclasspath/p:myboot.jar
true
myboot.jar after booting up needs to reference some other class in my project
dependencies expected on -classpath
> ability to add dependency to jvm's classpath rather in surefirebooter
> classloader
> -
>
> Key: MSUREFIRE-121
> URL: http://jira.codehaus.org/browse/MSUREFIRE-121
> Project: Maven 2.x Surefire Plugin
> Type: Bug
> Versions: 2.2
> Environment: xp
> Reporter: Dan Tran
> Fix For: 2.3
> Attachments: MSUREFIRE-121-booter.patch, MSUREFIRE-121.plugin.patch
>
>
> I have a usecase where i have a jar file got loaded by -Xbootclasspath, that
> jar file then loads classes from another jar ( my dependency)
> expected in the classpath.
> The problem is that surefire plugin does not add my dependencies at JVM
> commanline thru -classpath option, but after the JVM starts
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly 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: (MAVENUPLOAD-922) JavaNCSS 25.45
[ http://jira.codehaus.org/browse/MAVENUPLOAD-922?page=all ] Mike Perham updated MAVENUPLOAD-922: Attachment: javancss.zip > JavaNCSS 25.45 > -- > > Key: MAVENUPLOAD-922 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-922 > Project: maven-upload-requests > Type: Task > Reporter: Mike Perham > Attachments: javancss.zip > > > JavaNCSS is not a Maven 2 project so I cannot create an upload bundle for it. > I have deployed its jars and the attached zip contains the repository > contents after the deploy process is complete. > This version is required for the upcoming javancss-maven-plugin release. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly 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: (MAVENUPLOAD-922) JavaNCSS 25.45
[ http://jira.codehaus.org/browse/MAVENUPLOAD-922?page=all ] Mike Perham updated MAVENUPLOAD-922: Attachment: (was: javancss.zip) > JavaNCSS 25.45 > -- > > Key: MAVENUPLOAD-922 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-922 > Project: maven-upload-requests > Type: Task > Reporter: Mike Perham > Attachments: javancss.zip > > > JavaNCSS is not a Maven 2 project so I cannot create an upload bundle for it. > I have deployed its jars and the attached zip contains the repository > contents after the deploy process is complete. > This version is required for the upcoming javancss-maven-plugin release. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly 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-2326) exclusion of transitive dependency is too dominant
exclusion of transitive dependency is too dominant -- Key: MNG-2326 URL: http://jira.codehaus.org/browse/MNG-2326 Project: Maven 2 Type: Bug Components: Dependencies Versions: 2.0.4 Reporter: Andreas Schildbach Please consider the following structure: I've got a module M that has got the dependencies D1 and D2. Both D1 and D2 depend on a transitive dependency T. I have excluded T from D1 per on the M POM in the dependency to D1. Now, one would expect that T is still pulled into M, because there is no exclusion on the D2 path. But this is not the case, "mvn site" on M is missing T (in the dependency report), and it is missing from the classpath, too. However "mvn eclipse:eclipse" on M does the job right: T is listed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly 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: (MNGECLIPSE-127) Reindexing Local is too expensive to do it on every restart
[ http://jira.codehaus.org/browse/MNGECLIPSE-127?page=all ] Eugene Kuleshov closed MNGECLIPSE-127: -- Resolution: Fixed Fix Version: 0.0.8 Index is already persistent. In version 0.8 indexer skip files that already present in the index, which gives about 10x performance improvement (1s vs 10s to reindex 120Mb local repository). Once we'll have repositories view, on startup indexing will be disasbled, so you would be able re force reindexing. See MNGECLIPSE-33 > Reindexing Local is too expensive to do it on every restart > --- > > Key: MNGECLIPSE-127 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-127 > Project: Maven 2.x Extension for Eclipse > Type: Bug > Versions: 0.0.7 > Environment: Laptop with Windows XP, Pentium 4 2.4Ghz, 512Mb > Reporter: Abel Muiño > Assignee: Eugene Kuleshov > Priority: Minor > Fix For: 0.0.8 > > > When starting Eclipse with m2 projects on the workspace, the m2 plugin starts > "Indexing Local". This makes my laptop almost unusable for several minutes > (it is less noticeable on more modern machines). > * index once, keep MD5 (or some other info) about each indexed artifact. > * persist the generated index. > * on restart, check each file. > ** If it is new or its MD5 has changed, reindex that file. > ** Otherwise, use the persisted index. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly 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-123) Goals in dialog are getting mixed by new selection
[ http://jira.codehaus.org/browse/MNGECLIPSE-123?page=all ] Eugene Kuleshov updated MNGECLIPSE-123: --- Fix Version: (was: 0.0.8) 0.0.9 > Goals in dialog are getting mixed by new selection > -- > > Key: MNGECLIPSE-123 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-123 > Project: Maven 2.x Extension for Eclipse > Type: Bug > Components: Maven Launcher > Versions: 0.0.7 > Reporter: jeremie granat > Assignee: Eugene Kuleshov > Priority: Minor > Fix For: 0.0.9 > Attachments: Maven2LaunchMainTab.java > > > If you change he goal of a maven2 external tool configuration, the editor > will add it to the list creating a undefined goal: > before ==> compile:compile > want to change to jar:jar > after ==> jar:jarcompile:compile > I think that when you change the goals using the chooser, the field should be > overwritten by the selection. > actually, there is only one line to change :) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly 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: (MCHANGELOG-3) Links in File Activity Report can be wrong when using subversion, after a copy command has been issued
[ http://jira.codehaus.org/browse/MCHANGELOG-3?page=comments#action_66076 ] Julian Wood commented on MCHANGELOG-3: -- Still there AFAIK. Check out: http://commons.ucalgary.ca/projects/lc-webapp-archetype/changelog.html and look at some of the links like: /trunk/pom.xml (from /pom.xml:8) Let me check if the patch still works. J > Links in File Activity Report can be wrong when using subversion, after a > copy command has been issued > -- > > Key: MCHANGELOG-3 > URL: http://jira.codehaus.org/browse/MCHANGELOG-3 > Project: Maven 2.x Changelog Plugin > Type: Bug > Environment: OSX 10.4.3, java 1.4.2_09 > Reporter: Julian Wood > Assignee: Edwin Punzalan > Priority: Minor > Fix For: 2.0 > Attachments: MOJO-216-changelog-maven-plugin-1a.patch, > MOJO-216-changelog-maven-plugin.patch, changelog.xml, svnlog2.txt > > > When you do a subversion copy command, the list of files produced by svn log > often have additional information that is part of the filename: > R /tags/prt-1.3/prt-admin/pom.xml (from /trunk/prt-admin/pom.xml:128) > In SvnChangeLogParser.java, the file name is parsed as > /tags/prt-1.3/prt-admin/pom.xml (from /trunk/prt-admin/pom.xml:128) when of > course it should be /tags/prt-1.3/prt-admin/pom.xml. This is most > significantly manifested when a link is generated, such as in the File > Activity Report. > http://...?repname=prt&sc=0&path=/tags/prt-1.3/pom.xml%20(from%20/trunk/pom.xml:128) > I can see two approaches to the problem. The simplest is to add a regular > expression which deletes the extraneous data, but then you lose that > potentially valuable information. Maybe ChangeLogFile should keep track of a > file (path) and a name, rather than just a name, so that the link can be made > 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: (MCHANGELOG-36) Tests fail on build
[ http://jira.codehaus.org/browse/MCHANGELOG-36?page=comments#action_66081 ] Julian Wood commented on MCHANGELOG-36: --- I think the real problem is that we don't get the timezone information into the changelog.xml. Thus I made the assumption that all change entries were in the timezone of the person creating the site, and just used that timezone to correct the date entry. I don't think that assumption is going to hold up. Let me see if I can correct the real problem. > Tests fail on build > --- > > Key: MCHANGELOG-36 > URL: http://jira.codehaus.org/browse/MCHANGELOG-36 > Project: Maven 2.x Changelog Plugin > Type: Bug > Versions: 2.0 > Environment: osx 10.4.6, java 1.4.2_06 > Reporter: Julian Wood > Assignee: Edwin Punzalan > Fix For: 2.0 > Attachments: MCHANGELOG-36.patch > > > The date test assertions all fail: > junit.framework.AssertionFailedError: Test changelog 1 set 1 date/time > expected:<23963580> but was:< 23971500 > > at > org.apache.maven.changelog.ChangeLogTest.testReadFile(ChangeLogTest.java:50) > assertEquals( "Test changelog 1 set 1 date/time", 23963580L, > changeSet.getDate().getTime() ); > They just have the wrong date, and they are offset by the timezone ( 7 hours, > in my case - I'm MST -0700) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly 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: (MEV-401) Incoherences / duplication between javax.xml and com.sun.xml
[ http://jira.codehaus.org/browse/MEV-401?page=all ] Carlos Sanchez moved MAVENUPLOAD-923 to MEV-401: Bundle URL: (was: none) Workflow: jira (was: Maven New) Key: MEV-401 (was: MAVENUPLOAD-923) Project: Maven Evangelism (was: maven-upload-requests) > Incoherences / duplication between javax.xml and com.sun.xml > > > Key: MEV-401 > URL: http://jira.codehaus.org/browse/MEV-401 > Project: Maven Evangelism > Type: Bug > Reporter: Guillaume Nodet > > > See > > http://repo.mergere.com/maven2/javax/xml/jaxb-impl/2.0EA3/jaxb-impl-2.0EA3.pom > and > > http://repo.mergere.com/maven2/com/sun/xml/jaxb-impl/2.0EA3/jaxb-impl-2.0EA3.pom > See > > http://repo.mergere.com/maven2/com/sun/xml/jaxb-xjc/2.0EA3/jaxb-xjc-2.0EA3.pom > and > > http://repo.mergere.com/maven2/javax/xml/jaxb-xjc/2.0EA3/jaxb-xjc-2.0EA3.pom > If the javax.xml is to be preferred for the implementation RI, i guess that > the com/sun/xml should redirect to javax.xml artifacts. > Note that the poms in com.sun.xml have dependencies whereas javax.xml poms > have none. > So they need to be updated according to the con.sun.xml ones. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSUREFIRE-121) ability to add dependency to jvm's classpath rather in surefirebooter classloader
[ http://jira.codehaus.org/browse/MSUREFIRE-121?page=comments#action_66085 ] Carlos Sanchez commented on MSUREFIRE-121: -- The problem is that if the classpath makes the command line too long it will fail > ability to add dependency to jvm's classpath rather in surefirebooter > classloader > - > > Key: MSUREFIRE-121 > URL: http://jira.codehaus.org/browse/MSUREFIRE-121 > Project: Maven 2.x Surefire Plugin > Type: Bug > Versions: 2.2 > Environment: xp > Reporter: Dan Tran > Fix For: 2.3 > Attachments: MSUREFIRE-121-booter.patch, MSUREFIRE-121.plugin.patch > > > I have a usecase where i have a jar file got loaded by -Xbootclasspath, that > jar file then loads classes from another jar ( my dependency) > expected in the classpath. > The problem is that surefire plugin does not add my dependencies at JVM > commanline thru -classpath option, but after the JVM starts -- This message is automatically generated by JIRA. - If you think it was sent incorrectly 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-922) JavaNCSS 25.45
[ http://jira.codehaus.org/browse/MAVENUPLOAD-922?page=comments#action_66087 ] Carlos Sanchez commented on MAVENUPLOAD-922: You have to create an upload bundle so the script we have will install it. > JavaNCSS 25.45 > -- > > Key: MAVENUPLOAD-922 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-922 > Project: maven-upload-requests > Type: Task > Reporter: Mike Perham > Attachments: javancss.zip > > > JavaNCSS is not a Maven 2 project so I cannot create an upload bundle for it. > I have deployed its jars and the attached zip contains the repository > contents after the deploy process is complete. > This version is required for the upcoming javancss-maven-plugin release. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly 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: (MEV-401) Incoherences / duplication between javax.xml and com.sun.xml
[ http://jira.codehaus.org/browse/MEV-401?page=comments#action_66086 ] Carlos Sanchez commented on MEV-401: I think it's ok to have them duplicated. i'll check the dependencies > Incoherences / duplication between javax.xml and com.sun.xml > > > Key: MEV-401 > URL: http://jira.codehaus.org/browse/MEV-401 > Project: Maven Evangelism > Type: Bug > Reporter: Guillaume Nodet > > > See > > http://repo.mergere.com/maven2/javax/xml/jaxb-impl/2.0EA3/jaxb-impl-2.0EA3.pom > and > > http://repo.mergere.com/maven2/com/sun/xml/jaxb-impl/2.0EA3/jaxb-impl-2.0EA3.pom > See > > http://repo.mergere.com/maven2/com/sun/xml/jaxb-xjc/2.0EA3/jaxb-xjc-2.0EA3.pom > and > > http://repo.mergere.com/maven2/javax/xml/jaxb-xjc/2.0EA3/jaxb-xjc-2.0EA3.pom > If the javax.xml is to be preferred for the implementation RI, i guess that > the com/sun/xml should redirect to javax.xml artifacts. > Note that the poms in com.sun.xml have dependencies whereas javax.xml poms > have none. > So they need to be updated according to the con.sun.xml ones. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-922) JavaNCSS 25.45
[ http://jira.codehaus.org/browse/MAVENUPLOAD-922?page=comments#action_66088 ] Mike Perham commented on MAVENUPLOAD-922: - Carlos, how am I supposed to create an upload bundle for a project which is not built with Maven? Are we expected to create a pom for each of the project's artifacts by hand and then run the bundle mojo? The guide to uploading to ibiblio does not mention anything about how to deal with these legacy projects. > JavaNCSS 25.45 > -- > > Key: MAVENUPLOAD-922 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-922 > Project: maven-upload-requests > Type: Task > Reporter: Mike Perham > Attachments: javancss.zip > > > JavaNCSS is not a Maven 2 project so I cannot create an upload bundle for it. > I have deployed its jars and the attached zip contains the repository > contents after the deploy process is complete. > This version is required for the upcoming javancss-maven-plugin release. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly 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-922) JavaNCSS 25.45
[ http://jira.codehaus.org/browse/MAVENUPLOAD-922?page=comments#action_66089 ] Carlos Sanchez commented on MAVENUPLOAD-922: http://maven.apache.org/guides/mini/guide-ibiblio-upload.html "If you are not using maven as your build system but want something uploaded to Ibiblio then you just need to make a JAR (using the jar executable, not zip, pkzip or equivalent) with the following format:" ... > JavaNCSS 25.45 > -- > > Key: MAVENUPLOAD-922 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-922 > Project: maven-upload-requests > Type: Task > Reporter: Mike Perham > Attachments: javancss.zip > > > JavaNCSS is not a Maven 2 project so I cannot create an upload bundle for it. > I have deployed its jars and the attached zip contains the repository > contents after the deploy process is complete. > This version is required for the upcoming javancss-maven-plugin release. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly 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: (MAVENUPLOAD-922) JavaNCSS 25.45
[ http://jira.codehaus.org/browse/MAVENUPLOAD-922?page=all ] Mike Perham updated MAVENUPLOAD-922: Attachment: ccl-25.45-bundle.jar > JavaNCSS 25.45 > -- > > Key: MAVENUPLOAD-922 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-922 > Project: maven-upload-requests > Type: Task > Reporter: Mike Perham > Attachments: ccl-25.45-bundle.jar, javancss.zip > > > JavaNCSS is not a Maven 2 project so I cannot create an upload bundle for it. > I have deployed its jars and the attached zip contains the repository > contents after the deploy process is complete. > This version is required for the upcoming javancss-maven-plugin release. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly 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: (MAVENUPLOAD-922) JavaNCSS 25.45
[ http://jira.codehaus.org/browse/MAVENUPLOAD-922?page=all ] Mike Perham updated MAVENUPLOAD-922: Attachment: javancss-25.45-bundle.jar > JavaNCSS 25.45 > -- > > Key: MAVENUPLOAD-922 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-922 > Project: maven-upload-requests > Type: Task > Reporter: Mike Perham > Attachments: ccl-25.45-bundle.jar, javancss-25.45-bundle.jar, > jhbasic-25.45-bundle.jar > > > JavaNCSS is not a Maven 2 project so I cannot create an upload bundle for it. > I have deployed its jars and the attached zip contains the repository > contents after the deploy process is complete. > This version is required for the upcoming javancss-maven-plugin release. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly 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: (MAVENUPLOAD-922) JavaNCSS 25.45
[ http://jira.codehaus.org/browse/MAVENUPLOAD-922?page=all ] Mike Perham updated MAVENUPLOAD-922: Attachment: (was: javancss.zip) > JavaNCSS 25.45 > -- > > Key: MAVENUPLOAD-922 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-922 > Project: maven-upload-requests > Type: Task > Reporter: Mike Perham > Attachments: ccl-25.45-bundle.jar, javancss-25.45-bundle.jar, > jhbasic-25.45-bundle.jar > > > JavaNCSS is not a Maven 2 project so I cannot create an upload bundle for it. > I have deployed its jars and the attached zip contains the repository > contents after the deploy process is complete. > This version is required for the upcoming javancss-maven-plugin release. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly 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: (MAVENUPLOAD-922) JavaNCSS 25.45
[ http://jira.codehaus.org/browse/MAVENUPLOAD-922?page=all ] Mike Perham updated MAVENUPLOAD-922: Attachment: jhbasic-25.45-bundle.jar > JavaNCSS 25.45 > -- > > Key: MAVENUPLOAD-922 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-922 > Project: maven-upload-requests > Type: Task > Reporter: Mike Perham > Attachments: ccl-25.45-bundle.jar, javancss-25.45-bundle.jar, > jhbasic-25.45-bundle.jar > > > JavaNCSS is not a Maven 2 project so I cannot create an upload bundle for it. > I have deployed its jars and the attached zip contains the repository > contents after the deploy process is complete. > This version is required for the upcoming javancss-maven-plugin release. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly 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-922) JavaNCSS 25.45
[ http://jira.codehaus.org/browse/MAVENUPLOAD-922?page=comments#action_66092 ] Mike Perham commented on MAVENUPLOAD-922: - Thanks for your patience. :-) Bundles created. JavaNCSS source is not available via URL so I could not include an element. > JavaNCSS 25.45 > -- > > Key: MAVENUPLOAD-922 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-922 > Project: maven-upload-requests > Type: Task > Reporter: Mike Perham > Attachments: ccl-25.45-bundle.jar, javancss-25.45-bundle.jar, > jhbasic-25.45-bundle.jar > > > JavaNCSS is not a Maven 2 project so I cannot create an upload bundle for it. > I have deployed its jars and the attached zip contains the repository > contents after the deploy process is complete. > This version is required for the upcoming javancss-maven-plugin release. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly 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-116) Embedder can't find local repository
[ http://jira.codehaus.org/browse/MNGECLIPSE-116?page=all ] Ovidio Mallo updated MNGECLIPSE-116: Attachment: 20060529_MNGECLIPSE-116_trunk.patch > Embedder can't find local repository > > > Key: MNGECLIPSE-116 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-116 > Project: Maven 2.x Extension for Eclipse > Type: Bug > Versions: 0.0.7 > Environment: WinXP, Eclipse 3.1.2, Maven2.0.4 > Reporter: Cliff Resnick > Assignee: Jason van Zyl > Attachments: 20060526_MNGECLIPSE-116_trunk.patch, > 20060529_MNGECLIPSE-116_trunk.patch, maven-embedder-2.0.4_fixed-dep.jar > > > I upgraded from 0.0.5 to 0.0.7 and the plugin fails to load. > Below is output from the workspace log file: > java.lang.IllegalArgumentException: When not aligning with a user install you > must specify a local repository location using the > setLocalRepositoryDirectory( File ) method. > at > org.apache.maven.embedder.MavenEmbedder.createMavenSettings(MavenEmbedder.java:699) > at org.apache.maven.embedder.MavenEmbedder.start(MavenEmbedder.java:628) > at > org.maven.ide.eclipse.Maven2Plugin.createEmbedder(Maven2Plugin.java:267) > at > org.maven.ide.eclipse.Maven2Plugin.getMavenEmbedder(Maven2Plugin.java:155) > at > org.maven.ide.eclipse.Maven2Plugin.executeInEmbedder(Maven2Plugin.java:165) > at org.maven.ide.eclipse.Maven2Plugin.start(Maven2Plugin.java:112) > at > org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run(BundleContextImpl.java:994) > at java.security.AccessController.doPrivileged(Native Method) > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly 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-2327) [maven-maven1-plugin] Don't add plugins twice
[maven-maven1-plugin] Don't add plugins twice - Key: MNG-2327 URL: http://jira.codehaus.org/browse/MNG-2327 Project: Maven 2 Type: Bug Components: Sandbox Reporter: Dennis Lundberg Attachments: dontAddPluginsTwice.patch When using a PluginConfigurationConverter it can sometimes add a plugin that already exists in the v4 pom. The attached patch makes sure that the pom is searched for the plugin first, and adds a new one only if the plugin doesn't already exist. If the plugin already exist, the configuration is added to the existing plugin. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly 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-123) Goals in dialog are getting mixed by new selection
[ http://jira.codehaus.org/browse/MNGECLIPSE-123?page=all ] Eugene Kuleshov updated MNGECLIPSE-123: --- Version: (was: 0.0.7) > Goals in dialog are getting mixed by new selection > -- > > Key: MNGECLIPSE-123 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-123 > Project: Maven 2.x Extension for Eclipse > Type: Bug > Components: Maven Launcher > Reporter: jeremie granat > Assignee: Eugene Kuleshov > Priority: Minor > Fix For: 0.0.9 > Attachments: Maven2LaunchMainTab.java > > > If you change he goal of a maven2 external tool configuration, the editor > will add it to the list creating a undefined goal: > before ==> compile:compile > want to change to jar:jar > after ==> jar:jarcompile:compile > I think that when you change the goals using the chooser, the field should be > overwritten by the selection. > actually, there is only one line to change :) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly 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-123) Goals in dialog are getting mixed by new selection
[ http://jira.codehaus.org/browse/MNGECLIPSE-123?page=all ] Eugene Kuleshov updated MNGECLIPSE-123: --- Version: 0.0.7 Fix Version: (was: 0.0.9) > Goals in dialog are getting mixed by new selection > -- > > Key: MNGECLIPSE-123 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-123 > Project: Maven 2.x Extension for Eclipse > Type: Bug > Components: Maven Launcher > Versions: 0.0.7 > Reporter: jeremie granat > Assignee: Eugene Kuleshov > Priority: Minor > Attachments: Maven2LaunchMainTab.java > > > If you change he goal of a maven2 external tool configuration, the editor > will add it to the list creating a undefined goal: > before ==> compile:compile > want to change to jar:jar > after ==> jar:jarcompile:compile > I think that when you change the goals using the chooser, the field should be > overwritten by the selection. > actually, there is only one line to change :) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly 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-2328) include / exclude not working
include / exclude not working - Key: MNG-2328 URL: http://jira.codehaus.org/browse/MNG-2328 Project: Maven 2 Type: Bug Components: POM, General, Bootstrap & Build Versions: 2.0.4 Environment: windows 2000 Reporter: Mike Gabelmann If I provide any text within the or tags of the sequence I get an error: org.apache.maven.reactor.MavenExecutionException: Parse error reading POM. Reason: expected START_TAG or END_TAG not TEXT (position: TEXT seen ...\r\n\t\t**/*.xmlhttp://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNGECLIPSE-128) An internal error occurred during: "Indexing local".
An internal error occurred during: "Indexing local".
Key: MNGECLIPSE-128
URL: http://jira.codehaus.org/browse/MNGECLIPSE-128
Project: Maven 2.x Extension for Eclipse
Type: Bug
Components: Repository Management
Versions: 0.0.8
Environment: Eclipse 3.1.1, Windows XP
Reporter: Kees de Kooter
Assigned to: Eugene Kuleshov
Here's the Eclipse log:
{noformat}
!ENTRY org.eclipse.core.runtime 4 2 2006-05-29 23:37:08.343
!MESSAGE An internal error occurred during: "Indexing local".
!STACK 0
java.lang.StringIndexOutOfBoundsException: String index out of range: -1
at java.lang.String.substring(Unknown Source)
at org.maven.ide.eclipse.index.Indexer$FileInfo.(Indexer.java:421)
at
org.maven.ide.eclipse.index.Indexer$IndexerModifierAdapter.(Indexer.java:470)
at
org.maven.ide.eclipse.index.Indexer.createIndexerAdapter(Indexer.java:205)
at org.maven.ide.eclipse.index.Indexer.reindex(Indexer.java:212)
at
org.maven.ide.eclipse.Maven2Plugin$IndexerJob.run(Maven2Plugin.java:622)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76)
{noformat}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly 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-128) An internal error occurred during: "Indexing local".
[ http://jira.codehaus.org/browse/MNGECLIPSE-128?page=comments#action_66113
]
Eugene Kuleshov commented on MNGECLIPSE-128:
Pleaze archive local index from
{eclipse_workspace}/.metadata/.plugins/org.maven.ide.eclipse/index/local and
attach to this report
> An internal error occurred during: "Indexing local".
>
>
> Key: MNGECLIPSE-128
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-128
> Project: Maven 2.x Extension for Eclipse
> Type: Bug
> Components: Repository Management
> Versions: 0.0.8
> Environment: Eclipse 3.1.1, Windows XP
> Reporter: Kees de Kooter
> Assignee: Eugene Kuleshov
>
>
> Here's the Eclipse log:
> {noformat}
> !ENTRY org.eclipse.core.runtime 4 2 2006-05-29 23:37:08.343
> !MESSAGE An internal error occurred during: "Indexing local".
> !STACK 0
> java.lang.StringIndexOutOfBoundsException: String index out of range: -1
> at java.lang.String.substring(Unknown Source)
> at org.maven.ide.eclipse.index.Indexer$FileInfo.(Indexer.java:421)
> at
> org.maven.ide.eclipse.index.Indexer$IndexerModifierAdapter.(Indexer.java:470)
> at
> org.maven.ide.eclipse.index.Indexer.createIndexerAdapter(Indexer.java:205)
> at org.maven.ide.eclipse.index.Indexer.reindex(Indexer.java:212)
> at
> org.maven.ide.eclipse.Maven2Plugin$IndexerJob.run(Maven2Plugin.java:622)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76)
> {noformat}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly 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-2328) include / exclude not working
[ http://jira.codehaus.org/browse/MNG-2328?page=all ] Brett Porter closed MNG-2328: - Assign To: Brett Porter Resolution: Won't Fix **/*.xml is the correct format. > include / exclude not working > - > > Key: MNG-2328 > URL: http://jira.codehaus.org/browse/MNG-2328 > Project: Maven 2 > Type: Bug > Components: POM, General, Bootstrap & Build > Versions: 2.0.4 > Environment: windows 2000 > Reporter: Mike Gabelmann > Assignee: Brett Porter > > > If I provide any text within the or tags of the > sequence I get an error: > org.apache.maven.reactor.MavenExecutionException: Parse error reading POM. > Reason: expected START_TAG or END_TAG not TEXT (position: TEXT seen > ...\r\n\t\t**/*.xmlhttp://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNGECLIPSE-128) An internal error occurred during: "Indexing local".
[ http://jira.codehaus.org/browse/MNGECLIPSE-128?page=all ]
Kees de Kooter updated MNGECLIPSE-128:
--
Attachment: local.zip
> An internal error occurred during: "Indexing local".
>
>
> Key: MNGECLIPSE-128
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-128
> Project: Maven 2.x Extension for Eclipse
> Type: Bug
> Components: Repository Management
> Versions: 0.0.8
> Environment: Eclipse 3.1.1, Windows XP
> Reporter: Kees de Kooter
> Assignee: Eugene Kuleshov
> Attachments: local.zip
>
>
> Here's the Eclipse log:
> {noformat}
> !ENTRY org.eclipse.core.runtime 4 2 2006-05-29 23:37:08.343
> !MESSAGE An internal error occurred during: "Indexing local".
> !STACK 0
> java.lang.StringIndexOutOfBoundsException: String index out of range: -1
> at java.lang.String.substring(Unknown Source)
> at org.maven.ide.eclipse.index.Indexer$FileInfo.(Indexer.java:421)
> at
> org.maven.ide.eclipse.index.Indexer$IndexerModifierAdapter.(Indexer.java:470)
> at
> org.maven.ide.eclipse.index.Indexer.createIndexerAdapter(Indexer.java:205)
> at org.maven.ide.eclipse.index.Indexer.reindex(Indexer.java:212)
> at
> org.maven.ide.eclipse.Maven2Plugin$IndexerJob.run(Maven2Plugin.java:622)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76)
> {noformat}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly 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-128) An internal error occurred during: "Indexing local".
[ http://jira.codehaus.org/browse/MNGECLIPSE-128?page=comments#action_66116
]
Eugene Kuleshov commented on MNGECLIPSE-128:
It looks like you have maven1 repository there. It is not supported.
> An internal error occurred during: "Indexing local".
>
>
> Key: MNGECLIPSE-128
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-128
> Project: Maven 2.x Extension for Eclipse
> Type: Bug
> Components: Repository Management
> Versions: 0.0.8
> Environment: Eclipse 3.1.1, Windows XP
> Reporter: Kees de Kooter
> Assignee: Eugene Kuleshov
> Attachments: local.zip
>
>
> Here's the Eclipse log:
> {noformat}
> !ENTRY org.eclipse.core.runtime 4 2 2006-05-29 23:37:08.343
> !MESSAGE An internal error occurred during: "Indexing local".
> !STACK 0
> java.lang.StringIndexOutOfBoundsException: String index out of range: -1
> at java.lang.String.substring(Unknown Source)
> at org.maven.ide.eclipse.index.Indexer$FileInfo.(Indexer.java:421)
> at
> org.maven.ide.eclipse.index.Indexer$IndexerModifierAdapter.(Indexer.java:470)
> at
> org.maven.ide.eclipse.index.Indexer.createIndexerAdapter(Indexer.java:205)
> at org.maven.ide.eclipse.index.Indexer.reindex(Indexer.java:212)
> at
> org.maven.ide.eclipse.Maven2Plugin$IndexerJob.run(Maven2Plugin.java:622)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76)
> {noformat}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly 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-128) An internal error occurred during: "Indexing local".
[ http://jira.codehaus.org/browse/MNGECLIPSE-128?page=comments#action_66117
]
Kees de Kooter commented on MNGECLIPSE-128:
---
I have never used maven1.
How can I identify a maven1 repository?
> An internal error occurred during: "Indexing local".
>
>
> Key: MNGECLIPSE-128
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-128
> Project: Maven 2.x Extension for Eclipse
> Type: Bug
> Components: Repository Management
> Versions: 0.0.8
> Environment: Eclipse 3.1.1, Windows XP
> Reporter: Kees de Kooter
> Assignee: Eugene Kuleshov
> Attachments: local.zip
>
>
> Here's the Eclipse log:
> {noformat}
> !ENTRY org.eclipse.core.runtime 4 2 2006-05-29 23:37:08.343
> !MESSAGE An internal error occurred during: "Indexing local".
> !STACK 0
> java.lang.StringIndexOutOfBoundsException: String index out of range: -1
> at java.lang.String.substring(Unknown Source)
> at org.maven.ide.eclipse.index.Indexer$FileInfo.(Indexer.java:421)
> at
> org.maven.ide.eclipse.index.Indexer$IndexerModifierAdapter.(Indexer.java:470)
> at
> org.maven.ide.eclipse.index.Indexer.createIndexerAdapter(Indexer.java:205)
> at org.maven.ide.eclipse.index.Indexer.reindex(Indexer.java:212)
> at
> org.maven.ide.eclipse.Maven2Plugin$IndexerJob.run(Maven2Plugin.java:622)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76)
> {noformat}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly 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-2329) PluginDependencyTask
[ http://jira.codehaus.org/browse/MNG-2329?page=all ] Lukas Theussl moved MPARTIFACT-69 to MNG-2329: -- Complexity: Intermediate Workflow: Maven New (was: jira) Key: MNG-2329 (was: MPARTIFACT-69) Project: Maven 2 (was: maven-artifact-plugin) > PluginDependencyTask > > > Key: MNG-2329 > URL: http://jira.codehaus.org/browse/MNG-2329 > Project: Maven 2 > Type: New Feature > Components: Artifacts > Reporter: Erik Romson > Attachments: maven-artifact-ant.zip > > > I need to run ant tasks outside of maven2, because we use ant to populate > databases, generate reports etc from the database. Without going into any > discussions on the appropriate usage of ant, I needed to be able to get hold > of the classpath for plugins. I made a task for it. > Copy - paste of DependencyTask basically. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly 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-2329) PluginDependencyTask
[ http://jira.codehaus.org/browse/MNG-2329?page=all ] Lukas Theussl updated MNG-2329: --- Component: Artifacts > PluginDependencyTask > > > Key: MNG-2329 > URL: http://jira.codehaus.org/browse/MNG-2329 > Project: Maven 2 > Type: New Feature > Components: Artifacts > Reporter: Erik Romson > Attachments: maven-artifact-ant.zip > > > I need to run ant tasks outside of maven2, because we use ant to populate > databases, generate reports etc from the database. Without going into any > discussions on the appropriate usage of ant, I needed to be able to get hold > of the classpath for plugins. I made a task for it. > Copy - paste of DependencyTask basically. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly 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-128) An internal error occurred during: "Indexing local".
[ http://jira.codehaus.org/browse/MNGECLIPSE-128?page=comments#action_66118
]
Eugene Kuleshov commented on MNGECLIPSE-128:
Actually I take that back. I've got confused by jar name like
"xerces/xdoclet-xdoclet-module-1.2.3.pom" which does not make any sense to me.
Maybe you just have some garbage there... Anyways, I'll see if I can work
around this.
> An internal error occurred during: "Indexing local".
>
>
> Key: MNGECLIPSE-128
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-128
> Project: Maven 2.x Extension for Eclipse
> Type: Bug
> Components: Repository Management
> Versions: 0.0.8
> Environment: Eclipse 3.1.1, Windows XP
> Reporter: Kees de Kooter
> Assignee: Eugene Kuleshov
> Attachments: local.zip
>
>
> Here's the Eclipse log:
> {noformat}
> !ENTRY org.eclipse.core.runtime 4 2 2006-05-29 23:37:08.343
> !MESSAGE An internal error occurred during: "Indexing local".
> !STACK 0
> java.lang.StringIndexOutOfBoundsException: String index out of range: -1
> at java.lang.String.substring(Unknown Source)
> at org.maven.ide.eclipse.index.Indexer$FileInfo.(Indexer.java:421)
> at
> org.maven.ide.eclipse.index.Indexer$IndexerModifierAdapter.(Indexer.java:470)
> at
> org.maven.ide.eclipse.index.Indexer.createIndexerAdapter(Indexer.java:205)
> at org.maven.ide.eclipse.index.Indexer.reindex(Indexer.java:212)
> at
> org.maven.ide.eclipse.Maven2Plugin$IndexerJob.run(Maven2Plugin.java:622)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76)
> {noformat}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly 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-128) An internal error occurred during: "Indexing local".
[ http://jira.codehaus.org/browse/MNGECLIPSE-128?page=comments#action_66121
]
Kees de Kooter commented on MNGECLIPSE-128:
---
Eugene, I think this is a related issue:
{noformat}
!ENTRY org.eclipse.core.runtime 4 2 2006-05-30 00:17:48.484
!MESSAGE An internal error occurred during: "Read Project".
!STACK 0
java.lang.StringIndexOutOfBoundsException: String index out of range: -1
at java.lang.String.substring(Unknown Source)
at org.maven.ide.eclipse.index.Indexer$FileInfo.(Indexer.java:421)
at
org.maven.ide.eclipse.index.Indexer$IndexerModifierAdapter.(Indexer.java:470)
at
org.maven.ide.eclipse.index.Indexer.createIndexerAdapter(Indexer.java:205)
at org.maven.ide.eclipse.index.Indexer.addDocument(Indexer.java:301)
at
org.maven.ide.eclipse.TransferListenerAdapter.transferCompleted(TransferListenerAdapter.java:72)
at
org.apache.maven.wagon.events.TransferEventSupport.fireTransferCompleted(TransferEventSupport.java:135)
at
org.apache.maven.wagon.AbstractWagon.fireGetCompleted(AbstractWagon.java:325)
at
org.apache.maven.wagon.AbstractWagon.getTransfer(AbstractWagon.java:230)
at
org.apache.maven.wagon.AbstractWagon.getTransfer(AbstractWagon.java:182)
at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:80)
at
org.apache.maven.artifact.manager.DefaultWagonManager.getRemoteFile(DefaultWagonManager.java:369)
at
org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:282)
at
org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:244)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:124)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:63)
at
org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:467)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:225)
at
org.apache.maven.project.artifact.MavenMetadataSource.retrieve(MavenMetadataSource.java:102)
at
org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:275)
at
org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:67)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:223)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:211)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:192)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildWithDependencies(DefaultMavenProjectBuilder.java:342)
at
org.apache.maven.embedder.MavenEmbedder.readProjectWithDependencies(MavenEmbedder.java:271)
at
org.maven.ide.eclipse.Maven2Plugin$ReadProjectTask.run(Maven2Plugin.java:536)
at
org.maven.ide.eclipse.Maven2Plugin$EmbedderJob.run(Maven2Plugin.java:590)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76)
{noformat}
> An internal error occurred during: "Indexing local".
>
>
> Key: MNGECLIPSE-128
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-128
> Project: Maven 2.x Extension for Eclipse
> Type: Bug
> Components: Repository Management
> Versions: 0.0.8
> Environment: Eclipse 3.1.1, Windows XP
> Reporter: Kees de Kooter
> Assignee: Eugene Kuleshov
> Fix For: 0.0.9
> Attachments: local.zip
>
>
> Here's the Eclipse log:
> {noformat}
> !ENTRY org.eclipse.core.runtime 4 2 2006-05-29 23:37:08.343
> !MESSAGE An internal error occurred during: "Indexing local".
> !STACK 0
> java.lang.StringIndexOutOfBoundsException: String index out of range: -1
> at java.lang.String.substring(Unknown Source)
> at org.maven.ide.eclipse.index.Indexer$FileInfo.(Indexer.java:421)
> at
> org.maven.ide.eclipse.index.Indexer$IndexerModifierAdapter.(Indexer.java:470)
> at
> org.maven.ide.eclipse.index.Indexer.createIndexerAdapter(Indexer.java:205)
> at org.maven.ide.eclipse.index.Indexer.reindex(Indexer.java:212)
> at
> org.maven.ide.eclipse.Maven2Plugin$IndexerJob.run(Maven2Plugin.java:622)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76)
> {noformat}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly 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: (MNGECLIPSE-128) An internal error occurred during: "Indexing local".
[ http://jira.codehaus.org/browse/MNGECLIPSE-128?page=all ]
Eugene Kuleshov closed MNGECLIPSE-128:
--
Resolution: Fixed
Fix Version: 0.0.9
> An internal error occurred during: "Indexing local".
>
>
> Key: MNGECLIPSE-128
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-128
> Project: Maven 2.x Extension for Eclipse
> Type: Bug
> Components: Repository Management
> Versions: 0.0.8
> Environment: Eclipse 3.1.1, Windows XP
> Reporter: Kees de Kooter
> Assignee: Eugene Kuleshov
> Fix For: 0.0.9
> Attachments: local.zip
>
>
> Here's the Eclipse log:
> {noformat}
> !ENTRY org.eclipse.core.runtime 4 2 2006-05-29 23:37:08.343
> !MESSAGE An internal error occurred during: "Indexing local".
> !STACK 0
> java.lang.StringIndexOutOfBoundsException: String index out of range: -1
> at java.lang.String.substring(Unknown Source)
> at org.maven.ide.eclipse.index.Indexer$FileInfo.(Indexer.java:421)
> at
> org.maven.ide.eclipse.index.Indexer$IndexerModifierAdapter.(Indexer.java:470)
> at
> org.maven.ide.eclipse.index.Indexer.createIndexerAdapter(Indexer.java:205)
> at org.maven.ide.eclipse.index.Indexer.reindex(Indexer.java:212)
> at
> org.maven.ide.eclipse.Maven2Plugin$IndexerJob.run(Maven2Plugin.java:622)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76)
> {noformat}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly 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-128) An internal error occurred during: "Indexing local".
[ http://jira.codehaus.org/browse/MNGECLIPSE-128?page=comments#action_66122
]
Eugene Kuleshov commented on MNGECLIPSE-128:
That is exactly the same. I am about to release new build that will ignore
those entries. Though 0.0.8 should work if you remove
"xerces/xdoclet-xdoclet-module-1.2.3.pom" file.
> An internal error occurred during: "Indexing local".
>
>
> Key: MNGECLIPSE-128
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-128
> Project: Maven 2.x Extension for Eclipse
> Type: Bug
> Components: Repository Management
> Versions: 0.0.8
> Environment: Eclipse 3.1.1, Windows XP
> Reporter: Kees de Kooter
> Assignee: Eugene Kuleshov
> Fix For: 0.0.9
> Attachments: local.zip
>
>
> Here's the Eclipse log:
> {noformat}
> !ENTRY org.eclipse.core.runtime 4 2 2006-05-29 23:37:08.343
> !MESSAGE An internal error occurred during: "Indexing local".
> !STACK 0
> java.lang.StringIndexOutOfBoundsException: String index out of range: -1
> at java.lang.String.substring(Unknown Source)
> at org.maven.ide.eclipse.index.Indexer$FileInfo.(Indexer.java:421)
> at
> org.maven.ide.eclipse.index.Indexer$IndexerModifierAdapter.(Indexer.java:470)
> at
> org.maven.ide.eclipse.index.Indexer.createIndexerAdapter(Indexer.java:205)
> at org.maven.ide.eclipse.index.Indexer.reindex(Indexer.java:212)
> at
> org.maven.ide.eclipse.Maven2Plugin$IndexerJob.run(Maven2Plugin.java:622)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76)
> {noformat}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly 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-128) An internal error occurred during: "Indexing local".
[ http://jira.codehaus.org/browse/MNGECLIPSE-128?page=comments#action_66123
]
Kees de Kooter commented on MNGECLIPSE-128:
---
Will do. Thanks for the fast action Eugene!
> An internal error occurred during: "Indexing local".
>
>
> Key: MNGECLIPSE-128
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-128
> Project: Maven 2.x Extension for Eclipse
> Type: Bug
> Components: Repository Management
> Versions: 0.0.8
> Environment: Eclipse 3.1.1, Windows XP
> Reporter: Kees de Kooter
> Assignee: Eugene Kuleshov
> Fix For: 0.0.9
> Attachments: local.zip
>
>
> Here's the Eclipse log:
> {noformat}
> !ENTRY org.eclipse.core.runtime 4 2 2006-05-29 23:37:08.343
> !MESSAGE An internal error occurred during: "Indexing local".
> !STACK 0
> java.lang.StringIndexOutOfBoundsException: String index out of range: -1
> at java.lang.String.substring(Unknown Source)
> at org.maven.ide.eclipse.index.Indexer$FileInfo.(Indexer.java:421)
> at
> org.maven.ide.eclipse.index.Indexer$IndexerModifierAdapter.(Indexer.java:470)
> at
> org.maven.ide.eclipse.index.Indexer.createIndexerAdapter(Indexer.java:205)
> at org.maven.ide.eclipse.index.Indexer.reindex(Indexer.java:212)
> at
> org.maven.ide.eclipse.Maven2Plugin$IndexerJob.run(Maven2Plugin.java:622)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76)
> {noformat}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly 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: (MCHANGELOG-36) Tests fail on build
[ http://jira.codehaus.org/browse/MCHANGELOG-36?page=all ] Julian Wood updated MCHANGELOG-36: -- Attachment: MCHANGELOG-36a.patch > Tests fail on build > --- > > Key: MCHANGELOG-36 > URL: http://jira.codehaus.org/browse/MCHANGELOG-36 > Project: Maven 2.x Changelog Plugin > Type: Bug > Versions: 2.0 > Environment: osx 10.4.6, java 1.4.2_06 > Reporter: Julian Wood > Assignee: Edwin Punzalan > Fix For: 2.0 > Attachments: MCHANGELOG-36.patch, MCHANGELOG-36a.patch > > > The date test assertions all fail: > junit.framework.AssertionFailedError: Test changelog 1 set 1 date/time > expected:<23963580> but was:< 23971500 > > at > org.apache.maven.changelog.ChangeLogTest.testReadFile(ChangeLogTest.java:50) > assertEquals( "Test changelog 1 set 1 date/time", 23963580L, > changeSet.getDate().getTime() ); > They just have the wrong date, and they are offset by the timezone ( 7 hours, > in my case - I'm MST -0700) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly 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: (MCHANGELOG-36) Tests fail on build
[ http://jira.codehaus.org/browse/MCHANGELOG-36?page=comments#action_66125 ] Julian Wood commented on MCHANGELOG-36: --- MCHANGELOG-36a.patch supercedes MCHANGELOG-36.patch (ie ignore or delete MCHANGELOG-36.patch) > Tests fail on build > --- > > Key: MCHANGELOG-36 > URL: http://jira.codehaus.org/browse/MCHANGELOG-36 > Project: Maven 2.x Changelog Plugin > Type: Bug > Versions: 2.0 > Environment: osx 10.4.6, java 1.4.2_06 > Reporter: Julian Wood > Assignee: Edwin Punzalan > Fix For: 2.0 > Attachments: MCHANGELOG-36.patch, MCHANGELOG-36a.patch > > > The date test assertions all fail: > junit.framework.AssertionFailedError: Test changelog 1 set 1 date/time > expected:<23963580> but was:< 23971500 > > at > org.apache.maven.changelog.ChangeLogTest.testReadFile(ChangeLogTest.java:50) > assertEquals( "Test changelog 1 set 1 date/time", 23963580L, > changeSet.getDate().getTime() ); > They just have the wrong date, and they are offset by the timezone ( 7 hours, > in my case - I'm MST -0700) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly 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: (MSUREFIRE-123) unable to establish my own http protocol handler for unit tests
unable to establish my own http protocol handler for unit tests --- Key: MSUREFIRE-123 URL: http://jira.codehaus.org/browse/MSUREFIRE-123 Project: Maven 2.x Surefire Plugin Type: Bug Versions: 2.2 Environment: jse 5.0 (osx) Reporter: Andy Fyfe Attachments: protocol.zip In order to establish my own http protocol handler, I set the system property java.protocol.handler.pkgs and ensure that the tests require a fork. The test runs fine under maven 1.0.2, but fails under maven 2.0.4. I have tried both surefire 2.1.3 and 2.2, and both with the childDelegation option. The test sees the system property properly set, but the test's protocol handler is not actually used. The attached zip file demonstrates this problem (run "maven test" and "mvn test"). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly 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: (MCHANGELOG-3) Links in File Activity Report can be wrong when using subversion, after a copy command has been issued
[ http://jira.codehaus.org/browse/MCHANGELOG-3?page=all ] Julian Wood updated MCHANGELOG-3: - Attachment: MCHANGELOG-3.patch > Links in File Activity Report can be wrong when using subversion, after a > copy command has been issued > -- > > Key: MCHANGELOG-3 > URL: http://jira.codehaus.org/browse/MCHANGELOG-3 > Project: Maven 2.x Changelog Plugin > Type: Bug > Environment: OSX 10.4.3, java 1.4.2_09 > Reporter: Julian Wood > Assignee: Edwin Punzalan > Priority: Minor > Fix For: 2.0 > Attachments: MCHANGELOG-3.patch, MOJO-216-changelog-maven-plugin-1a.patch, > MOJO-216-changelog-maven-plugin.patch, changelog.xml, svnlog2.txt > > > When you do a subversion copy command, the list of files produced by svn log > often have additional information that is part of the filename: > R /tags/prt-1.3/prt-admin/pom.xml (from /trunk/prt-admin/pom.xml:128) > In SvnChangeLogParser.java, the file name is parsed as > /tags/prt-1.3/prt-admin/pom.xml (from /trunk/prt-admin/pom.xml:128) when of > course it should be /tags/prt-1.3/prt-admin/pom.xml. This is most > significantly manifested when a link is generated, such as in the File > Activity Report. > http://...?repname=prt&sc=0&path=/tags/prt-1.3/pom.xml%20(from%20/trunk/pom.xml:128) > I can see two approaches to the problem. The simplest is to add a regular > expression which deletes the extraneous data, but then you lose that > potentially valuable information. Maybe ChangeLogFile should keep track of a > file (path) and a name, rather than just a name, so that the link can be made > 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: (MCHANGELOG-36) Tests fail on build
[ http://jira.codehaus.org/browse/MCHANGELOG-36?page=comments#action_66127 ] Julian Wood commented on MCHANGELOG-36: --- While this patch is fine on it's own, if one then tries to apply the MCHANGELOG-3.patch, it won't work. Do it in the opposite order: MCHANGELOG-3.patch MCHANGELOG-36a.patch > Tests fail on build > --- > > Key: MCHANGELOG-36 > URL: http://jira.codehaus.org/browse/MCHANGELOG-36 > Project: Maven 2.x Changelog Plugin > Type: Bug > Versions: 2.0 > Environment: osx 10.4.6, java 1.4.2_06 > Reporter: Julian Wood > Assignee: Edwin Punzalan > Fix For: 2.0 > Attachments: MCHANGELOG-36.patch, MCHANGELOG-36a.patch > > > The date test assertions all fail: > junit.framework.AssertionFailedError: Test changelog 1 set 1 date/time > expected:<23963580> but was:< 23971500 > > at > org.apache.maven.changelog.ChangeLogTest.testReadFile(ChangeLogTest.java:50) > assertEquals( "Test changelog 1 set 1 date/time", 23963580L, > changeSet.getDate().getTime() ); > They just have the wrong date, and they are offset by the timezone ( 7 hours, > in my case - I'm MST -0700) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly 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: (MSUREFIRE-121) ability to add dependency to jvm's classpath rather in surefirebooter classloader
[ http://jira.codehaus.org/browse/MSUREFIRE-121?page=comments#action_66130 ] Dan Tran commented on MSUREFIRE-121: most of the time, the normal processing of classpath after JVM is loaded shoudl work, however in my use case, due the relationship between the jvm's bootclasspath and -classpath, my patch solve the immedidate need. I would urge to get my patch accepted unless it is radically changing the architechure of the plugin > ability to add dependency to jvm's classpath rather in surefirebooter > classloader > - > > Key: MSUREFIRE-121 > URL: http://jira.codehaus.org/browse/MSUREFIRE-121 > Project: Maven 2.x Surefire Plugin > Type: Bug > Versions: 2.2 > Environment: xp > Reporter: Dan Tran > Fix For: 2.3 > Attachments: MSUREFIRE-121-booter.patch, MSUREFIRE-121.plugin.patch > > > I have a usecase where i have a jar file got loaded by -Xbootclasspath, that > jar file then loads classes from another jar ( my dependency) > expected in the classpath. > The problem is that surefire plugin does not add my dependencies at JVM > commanline thru -classpath option, but after the JVM starts -- This message is automatically generated by JIRA. - If you think it was sent incorrectly 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: (MCHANGELOG-36) Tests fail on build
[ http://jira.codehaus.org/browse/MCHANGELOG-36?page=all ] Edwin Punzalan closed MCHANGELOG-36: Resolution: Fixed Patch applied. Thanks. > Tests fail on build > --- > > Key: MCHANGELOG-36 > URL: http://jira.codehaus.org/browse/MCHANGELOG-36 > Project: Maven 2.x Changelog Plugin > Type: Bug > Versions: 2.0 > Environment: osx 10.4.6, java 1.4.2_06 > Reporter: Julian Wood > Assignee: Edwin Punzalan > Fix For: 2.0 > Attachments: MCHANGELOG-36.patch, MCHANGELOG-36a.patch > > > The date test assertions all fail: > junit.framework.AssertionFailedError: Test changelog 1 set 1 date/time > expected:<23963580> but was:< 23971500 > > at > org.apache.maven.changelog.ChangeLogTest.testReadFile(ChangeLogTest.java:50) > assertEquals( "Test changelog 1 set 1 date/time", 23963580L, > changeSet.getDate().getTime() ); > They just have the wrong date, and they are offset by the timezone ( 7 hours, > in my case - I'm MST -0700) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly 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-922) JavaNCSS 25.45
[ http://jira.codehaus.org/browse/MAVENUPLOAD-922?page=all ] Carlos Sanchez closed MAVENUPLOAD-922: -- Assign To: Carlos Sanchez Resolution: Fixed > JavaNCSS 25.45 > -- > > Key: MAVENUPLOAD-922 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-922 > Project: maven-upload-requests > Type: Task > Reporter: Mike Perham > Assignee: Carlos Sanchez > Attachments: ccl-25.45-bundle.jar, javancss-25.45-bundle.jar, > jhbasic-25.45-bundle.jar > > > JavaNCSS is not a Maven 2 project so I cannot create an upload bundle for it. > I have deployed its jars and the attached zip contains the repository > contents after the deploy process is complete. > This version is required for the upcoming javancss-maven-plugin release. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly 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-924) vafer.org dependency bundle
[ http://jira.codehaus.org/browse/MAVENUPLOAD-924?page=all ] Carlos Sanchez closed MAVENUPLOAD-924: -- Assign To: Carlos Sanchez Resolution: Fixed I hope you already read about jar analyzer http://www.jroller.com/page/carlossg?entry=analyzing_jar_dependencies > vafer.org dependency bundle > --- > > Key: MAVENUPLOAD-924 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-924 > Project: maven-upload-requests > Type: Task > Reporter: Torsten Curdt > Assignee: Carlos Sanchez > > > I need it for maven and mojo! Please upload! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-920) Upload wicket-1.2-bundle.jar, wicket-extensions-1.2-bundle.jar, wicket-auth-roles-1.2-bundle.jar, wicket-spring-1.2-bundle.jar, wicket-spring-annot-1.2-bundle.jar
[ http://jira.codehaus.org/browse/MAVENUPLOAD-920?page=all ] Carlos Sanchez closed MAVENUPLOAD-920: -- Assign To: Carlos Sanchez Resolution: Fixed > Upload wicket-1.2-bundle.jar, wicket-extensions-1.2-bundle.jar, > wicket-auth-roles-1.2-bundle.jar, wicket-spring-1.2-bundle.jar, > wicket-spring-annot-1.2-bundle.jar > -- > > Key: MAVENUPLOAD-920 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-920 > Project: maven-upload-requests > Type: Task > Reporter: Martijn Dashorst > Assignee: Carlos Sanchez > > > http://wicketframework.org/downloads/wicket-1.2-bundle.jar > http://wicketframework.org/downloads/wicket-extensions-1.2-bundle.jar > http://wicketframework.org/downloads/wicket-spring-1.2-bundle.jar > http://wicketframework.org/downloads/wicket-spring-annot-1.2-bundle.jar > http://wicketframework.org/downloads/wicket-auth-roles-1.2-bundle.jar > http://wicketframework.org > http://wicketframework.org/team-list.html > Wicket is an open source, component based web application framework licensed > under the Apache 2 license. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly 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-907) State Machine Compiler v 4.3
[ http://jira.codehaus.org/browse/MAVENUPLOAD-907?page=all ] Carlos Sanchez closed MAVENUPLOAD-907: -- Assign To: Carlos Sanchez Resolution: Fixed > State Machine Compiler v 4.3 > > > Key: MAVENUPLOAD-907 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-907 > Project: maven-upload-requests > Type: Task > Reporter: Jerome Lacoste > Assignee: Carlos Sanchez > Attachments: smc-4.3-bundle.jar > > > The Smc project helps write state diagram in a simple to understand language > and will generate State pattern classes for you (as well as documentation). > Smc has a maven plugin currently stored in mojo sandbox. > Notes: > * The project is self-contained and has no dependencies. > * I asked the main smc developer to add a comment to this issue to > officialize the upload request on the net.sf.smc groupId. > * if you really need a public URL, I have made the bundle and am ready to > upload it in > https://svn.codehaus.org/mojo/trunk/mojo/mojo-sandbox/smc-maven-plugin/temp > (where today the jar and an old version of the pom reside), but I cannot > upload it until codehaus is up again. Otherwise I can ask the smc author to > place it on sourceforge. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly 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-915) Upload struts-menu 2.4
[ http://jira.codehaus.org/browse/MAVENUPLOAD-915?page=all ] Carlos Sanchez closed MAVENUPLOAD-915: -- Assign To: Carlos Sanchez Resolution: Fixed > Upload struts-menu 2.4 > -- > > Key: MAVENUPLOAD-915 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-915 > Project: maven-upload-requests > Type: Bug > Reporter: Tomislav Stojcevich > Assignee: Carlos Sanchez > Attachments: struts-menu-2.4-bundle.jar > > > Please upload with sources. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly 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-899) dunamis 0.9.4
[ http://jira.codehaus.org/browse/MAVENUPLOAD-899?page=comments#action_66137 ] Carlos Sanchez commented on MAVENUPLOAD-899: group has to be net.java.dev.dunamis > dunamis 0.9.4 > - > > Key: MAVENUPLOAD-899 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-899 > Project: maven-upload-requests > Type: Task > Reporter: Anders Hermansen > Attachments: dunamis-0.9.4-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-905) Upload 1.2B3 "cayenne", "cayenne-nodeps" and "cayenne-client-nodeps
[ http://jira.codehaus.org/browse/MAVENUPLOAD-905?page=all ] Carlos Sanchez closed MAVENUPLOAD-905: -- Assign To: Carlos Sanchez Resolution: Fixed > Upload 1.2B3 "cayenne", "cayenne-nodeps" and "cayenne-client-nodeps > --- > > Key: MAVENUPLOAD-905 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-905 > Project: maven-upload-requests > Type: Task > Reporter: Andrus Adamchik > Assignee: Carlos Sanchez > > > Cayenne is already on ibiblio. Please upload these three new bundles: > http://objectstyle.org/downloads/cayenne/maven-bundles/cayenne-1.2B3-bundle.jar > http://objectstyle.org/downloads/cayenne/maven-bundles/cayenne-client-nodeps-1.2B3-bundle.jar > http://objectstyle.org/downloads/cayenne/maven-bundles/cayenne-nodeps-1.2B3-bundle.jar > Thanks! > Andrus -- This message is automatically generated by JIRA. - If you think it was sent incorrectly 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-901) add sources for commons-logging 1.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-901?page=all ] Carlos Sanchez closed MAVENUPLOAD-901: -- Assign To: Carlos Sanchez Resolution: Fixed > add sources for commons-logging 1.1 > --- > > Key: MAVENUPLOAD-901 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-901 > Project: maven-upload-requests > Type: Bug > Reporter: Tomislav Stojcevich > Assignee: Carlos Sanchez > Attachments: commons-logging-1.1-bundle.jar > > > Please add sources only. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly 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-896) imageinfo 1.7
[ http://jira.codehaus.org/browse/MAVENUPLOAD-896?page=comments#action_66138 ] Carlos Sanchez commented on MAVENUPLOAD-896: please remove url from license, as that's the link for the text of the license, in this case does not apply name is empty > imageinfo 1.7 > - > > Key: MAVENUPLOAD-896 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-896 > Project: maven-upload-requests > Type: Task > Reporter: fabrizio giustina > > > ImageInfo, a free Java class to retrieve properties from image files. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly 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: (MEV-402) janino 2.4.1 and 2.4.3 are missing pom.xml
[ http://jira.codehaus.org/browse/MEV-402?page=all ] Carlos Sanchez moved MAVENUPLOAD-898 to MEV-402: Bundle URL: (was: http://janino.net/) Workflow: jira (was: Maven New) Key: MEV-402 (was: MAVENUPLOAD-898) Project: Maven Evangelism (was: maven-upload-requests) > janino 2.4.1 and 2.4.3 are missing pom.xml > -- > > Key: MEV-402 > URL: http://jira.codehaus.org/browse/MEV-402 > Project: Maven Evangelism > Type: Task > Reporter: Mark Proctor > Attachments: janino-2.4.1.pom, janino-2.4.3.pom, pom.xml, pom.xml > > > janino 2.4.1 and 2.4.3 is missing pom.xml - which is breaking builds. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly 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-894) Updating jmdns to 1.0
[ http://jira.codehaus.org/browse/MAVENUPLOAD-894?page=comments#action_66139 ] Carlos Sanchez commented on MAVENUPLOAD-894: See upload instructions about required elements in pom > Updating jmdns to 1.0 > - > > Key: MAVENUPLOAD-894 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-894 > Project: maven-upload-requests > Type: Task > Reporter: Keith R. Bennett > Attachments: jmdns-for-maven-repo.jar > > > The repository's latest existing version is 0.2; this is version 1.0. > I am new to Maven 2.0, and am using version 1.0 of this jar file in a > project, so I'd like it to be in the repository. I hope I've done everything > right, I'm sorry in advance if not. > The URL above is on a private site of mine that has nothing to do with the > jmdns project -- it's just a site I was able to use for the purpose of making > it accessible to you. If the URL is intended to be used by users, then it > will not work, as I will delete the file sometime soon. I am attaching the > same file as well, in case you have any problem getting it via the URL. > The URL at sourceforge for downloading this product is > http://sourceforge.net/project/showfiles.php?group_id=93852&package_id=99663&release_id=365488. > I have included only the jar file from the distribution, not the source, > docs, or sample files. > - Keith Bennett -- This message is automatically generated by JIRA. - If you think it was sent incorrectly 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-893) Java Bean Library
[ http://jira.codehaus.org/browse/MAVENUPLOAD-893?page=all ] Carlos Sanchez closed MAVENUPLOAD-893: -- Assign To: Carlos Sanchez Resolution: Fixed > Java Bean Library > - > > Key: MAVENUPLOAD-893 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-893 > Project: maven-upload-requests > Type: Task > Reporter: Joe D. Velopar > Assignee: Carlos Sanchez > Attachments: beanlib-3.2.0.jar, beanlib-hibernate-3.2.0.jar > > > Java Bean Library (beanlib) is a utilities library for use with JavaBean's. > Java Bean Library for Hibernate (beanlib-hibernate) is particularly handy > when used with Hibernate. > It allows developers to easily reuse the same pojo classes for both > persistence instances and data transfer objects. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly 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-402) janino 2.4.1 and 2.4.3 are missing pom.xml
[ http://jira.codehaus.org/browse/MEV-402?page=all ] Carlos Sanchez closed MEV-402: -- Assign To: Carlos Sanchez Resolution: Fixed Next time please check, license url is the one tha actually contains the license, http://janino.net/javadoc/org/codehaus/janino/doc-files/new_bsd_license.txt > janino 2.4.1 and 2.4.3 are missing pom.xml > -- > > Key: MEV-402 > URL: http://jira.codehaus.org/browse/MEV-402 > Project: Maven Evangelism > Type: Task > Reporter: Mark Proctor > Assignee: Carlos Sanchez > Attachments: janino-2.4.1.pom, janino-2.4.3.pom, pom.xml, pom.xml > > > janino 2.4.1 and 2.4.3 is missing pom.xml - which is breaking builds. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly 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-874) CoWarp 0.5 Release
[ http://jira.codehaus.org/browse/MAVENUPLOAD-874?page=all ] Carlos Sanchez closed MAVENUPLOAD-874: -- Assign To: Carlos Sanchez Resolution: Won't Fix > CoWarp 0.5 Release > -- > > Key: MAVENUPLOAD-874 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-874 > Project: maven-upload-requests > Type: Task > Reporter: Carsten Ziegeler > Assignee: Carlos Sanchez > > > 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: (MCHANGELOG-3) Links in File Activity Report can be wrong when using subversion, after a copy command has been issued
[ http://jira.codehaus.org/browse/MCHANGELOG-3?page=all ] Edwin Punzalan closed MCHANGELOG-3: --- Resolution: Fixed Patch applied, thanks. > Links in File Activity Report can be wrong when using subversion, after a > copy command has been issued > -- > > Key: MCHANGELOG-3 > URL: http://jira.codehaus.org/browse/MCHANGELOG-3 > Project: Maven 2.x Changelog Plugin > Type: Bug > Environment: OSX 10.4.3, java 1.4.2_09 > Reporter: Julian Wood > Assignee: Edwin Punzalan > Priority: Minor > Fix For: 2.0 > Attachments: MCHANGELOG-3.patch, MOJO-216-changelog-maven-plugin-1a.patch, > MOJO-216-changelog-maven-plugin.patch, changelog.xml, svnlog2.txt > > > When you do a subversion copy command, the list of files produced by svn log > often have additional information that is part of the filename: > R /tags/prt-1.3/prt-admin/pom.xml (from /trunk/prt-admin/pom.xml:128) > In SvnChangeLogParser.java, the file name is parsed as > /tags/prt-1.3/prt-admin/pom.xml (from /trunk/prt-admin/pom.xml:128) when of > course it should be /tags/prt-1.3/prt-admin/pom.xml. This is most > significantly manifested when a link is generated, such as in the File > Activity Report. > http://...?repname=prt&sc=0&path=/tags/prt-1.3/pom.xml%20(from%20/trunk/pom.xml:128) > I can see two approaches to the problem. The simplest is to add a regular > expression which deletes the extraneous data, but then you lose that > potentially valuable information. Maybe ChangeLogFile should keep track of a > file (path) and a name, rather than just a name, so that the link can be made > 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
