[jira] Commented: (ARCHETYPE-31) Create a tool that will generate an archetype from an existing project
[ http://jira.codehaus.org/browse/ARCHETYPE-31?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_120651 ] Dave Syer commented on ARCHETYPE-31: I can see that something has happened because there are a couple of pages of docos and I can do mvn clean archetypeng:create-from-project and see code appear in target/generated-sources/archetypeng. It might even almost be a valid archetype, but when I install it and then use it I get Embedded error: The META-INF/maven/archetype.xml descriptor cannot be found. (Despite the fact that the file exists in the jar. I guess it is somehow invalid and the error message is unclear?) The archetype groupId and artifacfId are the same as the project it was created from (not very useful). I also see target/archetype.properties appearing. Maybe that's being used to set the archetype pom properties up? Not so you'd notice. Is this supposed to work? How would I modify the archetype? Is there going to be some more documentation? > Create a tool that will generate an archetype from an existing project > -- > > Key: ARCHETYPE-31 > URL: http://jira.codehaus.org/browse/ARCHETYPE-31 > Project: Maven Archetype > Issue Type: New Feature >Reporter: Jason van Zyl >Assignee: Jason van Zyl > > An archetype author shold be able to work/debug an existing project and when > satisfied just flip it into an archetype. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MPLUGIN-66) Add unit test
Add unit test - Key: MPLUGIN-66 URL: http://jira.codehaus.org/browse/MPLUGIN-66 Project: Maven 2.x Plugin Tools Issue Type: Sub-task Reporter: Benjamin Bentmann Priority: Trivial Is there a particular reason why my previously attached patch was not applied? Is there another test to guard against a regression of this bug underway? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (SUREFIRE-121) System properties set on the command line get clobbered
[ http://jira.codehaus.org/browse/SUREFIRE-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_120661 ] Milos Kleint commented on SUREFIRE-121: --- fixed the embedded use problem. http://svn.apache.org/viewvc?rev=613539&view=rev > System properties set on the command line get clobbered > --- > > Key: SUREFIRE-121 > URL: http://jira.codehaus.org/browse/SUREFIRE-121 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.0 (2.2 plugin) > Environment: Linux, Maven 2.0.4, Sun JDK 1.5U5, bash 3.0 >Reporter: Brenton Leanhardt >Priority: Critical > Fix For: 2.x > > > Some system properties get clobbered if you set them on the command line. For > example, > mvn clean test -Dtest=LoginTest -Dselenium.user=test32 > The 'test' system property will work, but the 'selenium.user' property will > be null at runtime. I have tried: > * hard coding the system property in the unit test, this worked fine. > * setting the system properties in the pom file, this worked fine also. > * tried an older version of the surefire plugin, this worked fine. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-1887) Upload HtmlUnit-1.14
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_120668 ] Julien HENRY commented on MAVENUPLOAD-1887: --- You're right. Sorry for the bad example. Only stay the last point: clover2 plugin. Should HtmlUnit project doesn't use it because it is not on ibiblio? Thanks > Upload HtmlUnit-1.14 > > > Key: MAVENUPLOAD-1887 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1887 > Project: maven-upload-requests > Issue Type: Task >Reporter: Marc Guillemot > > http://htmlunit.sourceforge.net/tmp/htmlunit-1.14-bundle.jar > http://htmlunit.sourceforge.net/ > http://htmlunit.sourceforge.net/team-list.html > I'm a developer of HtmlUnit, 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] Created: (MRESOURCES-53) maven replaces @@ with [EMAIL PROTECTED] in resources
maven replaces @@ with [EMAIL PROTECTED] in resources -- Key: MRESOURCES-53 URL: http://jira.codehaus.org/browse/MRESOURCES-53 Project: Maven 2.x Resources Plugin Issue Type: Bug Environment: Linux 2.6 Reporter: Jan Torben Heuer Priority: Critical maven replaces the String @@ in resources with [EMAIL PROTECTED] I enabled filtering for the resources and my variables are correctly replaced. Jan -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MJAVADOC-138) javadoc:test-javadoc failed if target/classes not already created
[
http://jira.codehaus.org/browse/MJAVADOC-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_120685
]
Benjamin Bentmann commented on MJAVADOC-138:
Vincent, if there is urgent need to get this done, I can't help. If it can wait
a couple of weeks, well, I will try.
As a hotfix, annotating the mojo with [EMAIL PROTECTED] phase=test-compile}} to
create the test classes by a forked Maven invocation should do.
> javadoc:test-javadoc failed if target/classes not already created
> -
>
> Key: MJAVADOC-138
> URL: http://jira.codehaus.org/browse/MJAVADOC-138
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.3
>Reporter: Vincent Siveton
>
> Using
> {noformat}
> mvn clean javadoc:test-javadoc
> {noformat}
> it could produce unsuccessful build or warning (depending the javadoc version
> used, i.e 1.4 vs 1.5)
> The options file contains:
> {noformat}
> -classpath '[SNIP]/target/classes;[SNIP]/target/tests-classes;...'
> {noformat}
> The explanation is that no target\classes was created before executing
> test-javadoc
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact 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: (SUREFIRE-121) System properties set on the command line get clobbered
[ http://jira.codehaus.org/browse/SUREFIRE-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_120689 ] Dan Fabulich commented on SUREFIRE-121: --- This hotfix switches from using System.getProperties to using MavenSession.getExecutionProperties. MavenSession has no JavaDoc (or documentation of any kind?) so it's hard for me to tell how this hotfix works. What sort of properties get into executionProperties? What properties don't get into executionProperties? http://maven.apache.org/ref/2.0.8/maven-core/apidocs/org/apache/maven/execution/MavenSession.html > System properties set on the command line get clobbered > --- > > Key: SUREFIRE-121 > URL: http://jira.codehaus.org/browse/SUREFIRE-121 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.0 (2.2 plugin) > Environment: Linux, Maven 2.0.4, Sun JDK 1.5U5, bash 3.0 >Reporter: Brenton Leanhardt >Priority: Critical > Fix For: 2.x > > > Some system properties get clobbered if you set them on the command line. For > example, > mvn clean test -Dtest=LoginTest -Dselenium.user=test32 > The 'test' system property will work, but the 'selenium.user' property will > be null at runtime. I have tried: > * hard coding the system property in the unit test, this worked fine. > * setting the system properties in the pom file, this worked fine also. > * tried an older version of the surefire plugin, this worked fine. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MEV-569) jstl-1.2.jar is not correctly buils
jstl-1.2.jar is not correctly buils --- Key: MEV-569 URL: http://jira.codehaus.org/browse/MEV-569 Project: Maven Evangelism Issue Type: Bug Reporter: j p The the jar file on repo2.maven.org has this structure: -classes |--org |--javax -META-INF it should be (to work in my project): -org -javax -META-INF I think we have to supply a new jar file. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-1899) Oracle JDBC driver for JDK 1.4/1.5, v10.2.0.3.0
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_120701 ] Ian Springer commented on MAVENUPLOAD-1899: --- Ah, I didn't notice that http://repo1.maven.org/maven2/com/oracle/ojdbc14/10.2.0.2.0/ didn't contain the actual jars... Ok, I'll upload another zipfile w/ just the poms and checksums. > Oracle JDBC driver for JDK 1.4/1.5, v10.2.0.3.0 > --- > > Key: MAVENUPLOAD-1899 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1899 > Project: maven-upload-requests > Issue Type: Wish >Reporter: Ian Springer >Assignee: Carlos Sanchez > > Latest version of Oracle JDBC jar. > Previous version is already on the central repo: > http://repo1.maven.org/maven2/com/oracle/ojdbc14/10.2.0.2.0/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-1899) Oracle JDBC driver for JDK 1.4/1.5, v10.2.0.3.0
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_120704 ] Carlos Sanchez commented on MAVENUPLOAD-1899: - I already put them > Oracle JDBC driver for JDK 1.4/1.5, v10.2.0.3.0 > --- > > Key: MAVENUPLOAD-1899 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1899 > Project: maven-upload-requests > Issue Type: Wish >Reporter: Ian Springer >Assignee: Carlos Sanchez > > Latest version of Oracle JDBC jar. > Previous version is already on the central repo: > http://repo1.maven.org/maven2/com/oracle/ojdbc14/10.2.0.2.0/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MANTTASKS-103) Can't deploy to a file: repository
[ http://jira.codehaus.org/browse/MANTTASKS-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MANTTASKS-103. --- Assignee: Herve Boutemy Resolution: Fixed Fix Version/s: 2.0.9 fixed in r613696 > Can't deploy to a file: repository > -- > > Key: MANTTASKS-103 > URL: http://jira.codehaus.org/browse/MANTTASKS-103 > Project: Maven 2.x Ant Tasks > Issue Type: Bug >Affects Versions: 2.0.8 > Environment: ant 1.7.0+maven-ant-tasks-2.0.8 > OS: Windows XP >Reporter: Olov Andersson >Assignee: Herve Boutemy > Fix For: 2.0.9 > > Attachments: maven-ant-tasks-jiratestcase.zip > > > The artifact:deploy target doesn't work, at least not when deploying to > repositories with a file:-based url. > Seem to be some issue with updating the metadata file, the path to the remote > repository becomes corrupt during the metadata update. > Provided a simple testcase pointing to a repository at C:\. > The deployment fails with the following message: > [artifact:deploy] Deploying to file:C:\ > [artifact:deploy] Uploading: org/dummy/dummy/1.0/dummy-1.0.jar to file:C:\ > [artifact:deploy] [INFO] Retrieving previous metadata from file:C:\ > [artifact:deploy] [INFO] Uploading project information for dummy 1.0 > [artifact:deploy] [INFO] Retrieving previous metadata from file:C:\ > [artifact:deploy] An error has occurred while processing the Maven artifact > task > s. > [artifact:deploy] Diagnosis: > [artifact:deploy] > [artifact:deploy] Error deploying artifact 'org.dummy:dummy:jar': Error > installi > ng artifact's metadata: Error installing metadata: Error updating group > reposito > ry metadata > [artifact:deploy] C:\Documents and > Settings\oland\.m2\repository\org\dummy\dummy > \maven-metadata-file:C:\.xml (The filename, directory name, or volume label > synt > ax is incorrect) > [artifact:deploy] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-1901) please add redirect from ant:ant:1.7.0 to org.apache.ant:ant:1.7.0
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1901. --- Assignee: Carlos Sanchez Resolution: Fixed > please add redirect from ant:ant:1.7.0 to org.apache.ant:ant:1.7.0 > -- > > Key: MAVENUPLOAD-1901 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1901 > Project: maven-upload-requests > Issue Type: Bug >Reporter: Milos Kleint >Assignee: Carlos Sanchez > > all the previous versions (< 1.7.0) of ant have the the "ant" groupId, while > the 1.7.0 is already in the org.apache.ant groupid. Please add a redirect. > fom ant->org.apache.ant > thanks. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MEV-565) commons-lang is missing versions greater then 2.1 in the metadata.
[ http://jira.codehaus.org/browse/MEV-565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MEV-565. -- Resolution: Fixed > commons-lang is missing versions greater then 2.1 in the metadata. > -- > > Key: MEV-565 > URL: http://jira.codehaus.org/browse/MEV-565 > Project: Maven Evangelism > Issue Type: Bug > Components: Invalid Metadata >Reporter: Paul Spencer >Assignee: Carlos Sanchez > > Versions > 2.1 are missing from the metadata. This is preventing version > range like [2.2,) from working, -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-567) WS Common POM v1.0.1 has a compile time dependency on JUnit
[ http://jira.codehaus.org/browse/MEV-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MEV-567. -- Assignee: Carlos Sanchez Resolution: Won't Fix they should fix it on their side for next versions, old versions can't be modified now > WS Common POM v1.0.1 has a compile time dependency on JUnit > --- > > Key: MEV-567 > URL: http://jira.codehaus.org/browse/MEV-567 > Project: Maven Evangelism > Issue Type: Bug > Components: Invalid POM >Reporter: Vincent Massol >Assignee: Carlos Sanchez > > WS Common POM v1.0.1 has a compile time dependency on JUnit. It should be > declared using a test scope instead. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-569) jstl-1.2.jar is not correctly buils
[ http://jira.codehaus.org/browse/MEV-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_120722 ] Carlos Sanchez commented on MEV-569: it was taken from http://download.java.net/maven/1/javax.servlet.jsp.jstl/jars/ Removed until somebody provides it, license needs to allow redistribution > jstl-1.2.jar is not correctly buils > --- > > Key: MEV-569 > URL: http://jira.codehaus.org/browse/MEV-569 > Project: Maven Evangelism > Issue Type: Bug >Reporter: j p > > The the jar file on repo2.maven.org has this structure: > -classes > |--org > |--javax > -META-INF > it should be (to work in my project): > -org > -javax > -META-INF > I think we have to supply a new jar file. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-569) jstl-1.2.jar is not correctly buils
[ http://jira.codehaus.org/browse/MEV-569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MEV-569. -- Assignee: Carlos Sanchez Resolution: Fixed > jstl-1.2.jar is not correctly buils > --- > > Key: MEV-569 > URL: http://jira.codehaus.org/browse/MEV-569 > Project: Maven Evangelism > Issue Type: Bug >Reporter: j p >Assignee: Carlos Sanchez > > The the jar file on repo2.maven.org has this structure: > -classes > |--org > |--javax > -META-INF > it should be (to work in my project): > -org > -javax > -META-INF > I think we have to supply a new jar file. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-1902) sync central repo with mmm releases repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_120721 ] Carlos Sanchez commented on MAVENUPLOAD-1902: - if the project at eclipse is m-m-m the group id should be net.sf.m-m-m > sync central repo with mmm releases repository > -- > > Key: MAVENUPLOAD-1902 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1902 > Project: maven-upload-requests > Issue Type: Task >Reporter: Jörg Hohwiller > Attachments: net.sf.mmm.sh > > > I am the admin and maintainer of the mmm project: > http://m-m-m.sourceforge.net/maven/index.html > We provide cool open-source software licensed under ASL. > Maven2 is our project-management-tool. > We would like to have our releases available in the central maven repository. > Therefore we read and followed the instructions we found here: > http://maven.apache.org/guides/mini/guide-central-repository-upload.html > You will find a sync-script 'net.sf.mmm.sh' attached. > I hope everything is perfect. Please let us know, if we did something wrong. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-568) Missing versions in maven-metadata.xml for Joda Time
[ http://jira.codehaus.org/browse/MEV-568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MEV-568. -- Assignee: Carlos Sanchez Resolution: Fixed > Missing versions in maven-metadata.xml for Joda Time > > > Key: MEV-568 > URL: http://jira.codehaus.org/browse/MEV-568 > Project: Maven Evangelism > Issue Type: Bug > Components: Invalid Metadata >Reporter: Stefan Hübner >Assignee: Carlos Sanchez > Attachments: joda-tima-maven-metadata.tar.gz > > > Could you please fix the maven-metadata for joda-time:joda-time? all releases > after 1.2.1 (1.3, 1.4, 1.5, 1.5.1) are missing. > I'll provide an updated maven-metadata.xml plus checksums. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-566) Please deploy jpox 1.1.9 to central repo
[ http://jira.codehaus.org/browse/MEV-566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MEV-566. -- Assignee: Carlos Sanchez Resolution: Fixed > Please deploy jpox 1.1.9 to central repo > > > Key: MEV-566 > URL: http://jira.codehaus.org/browse/MEV-566 > Project: Maven Evangelism > Issue Type: Task >Reporter: Maria Odea Ching >Assignee: Carlos Sanchez > > This artifact is needed by Archiva for this issue > http://jira.codehaus.org/browse/MRM-630. > It is here in the jpox repo: > http://www.jpox.org/downloads/maven/ > Thanks -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-1887) Upload HtmlUnit-1.14
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_120720 ] Carlos Sanchez commented on MAVENUPLOAD-1887: - you should convince atlassian to push it to ibiblio ;) or you can remove it from rhe pom > Upload HtmlUnit-1.14 > > > Key: MAVENUPLOAD-1887 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1887 > Project: maven-upload-requests > Issue Type: Task >Reporter: Marc Guillemot > > http://htmlunit.sourceforge.net/tmp/htmlunit-1.14-bundle.jar > http://htmlunit.sourceforge.net/ > http://htmlunit.sourceforge.net/team-list.html > I'm a developer of HtmlUnit, 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-1899) Oracle JDBC driver for JDK 1.4/1.5, v10.2.0.3.0
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_120725 ] Ian Springer commented on MAVENUPLOAD-1899: --- Thanks. Fyi, the md5/sha1 files are in the wrong format (they contain "filename checksum" rather than just "checksum"). > Oracle JDBC driver for JDK 1.4/1.5, v10.2.0.3.0 > --- > > Key: MAVENUPLOAD-1899 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1899 > Project: maven-upload-requests > Issue Type: Wish >Reporter: Ian Springer >Assignee: Carlos Sanchez > > Latest version of Oracle JDBC jar. > Previous version is already on the central repo: > http://repo1.maven.org/maven2/com/oracle/ojdbc14/10.2.0.2.0/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-1899) Oracle JDBC driver for JDK 1.4/1.5, v10.2.0.3.0
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_120726 ] Carlos Sanchez commented on MAVENUPLOAD-1899: - there's nothing wrong with that, there are several formats > Oracle JDBC driver for JDK 1.4/1.5, v10.2.0.3.0 > --- > > Key: MAVENUPLOAD-1899 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1899 > Project: maven-upload-requests > Issue Type: Wish >Reporter: Ian Springer >Assignee: Carlos Sanchez > > Latest version of Oracle JDBC jar. > Previous version is already on the central repo: > http://repo1.maven.org/maven2/com/oracle/ojdbc14/10.2.0.2.0/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
