db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4267) Investigate why Derby 10.5.1.1 is not available in the maven2 repositories
Date Fri, 11 Sep 2009 12:48:57 GMT

    [ https://issues.apache.org/jira/browse/DERBY-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12754114#action_12754114
] 

Rick Hillegas commented on DERBY-4267:
--------------------------------------

The following conversation happened on irc after I hand-deployed the artifacts:

<oxi> hi
<oxi> where's the largest derby chan?
<oxi> I think I've seen a larger one once
<oxi> there's an error in the lastest pom
* ahfeel (n=ahfeel@84.207.19.58) has left #derby
<oxi> [ERROR] FATAL ERROR
<oxi> [INFO] Invalid uri 'http://repo1.maven.org/maven2/org/apache/derby/derby-project/${derby.version}/derby-project-${derby.version}.pom':
escaped absolute path not valid
<oxi> http://repo1.maven.org/maven2/org/apache/derby/derby/10.5.3.0/derby-10.5.3.0.pom
contains <version>${derby.version}</version>
<oxi> it would be cool if anyone could fix this
<kahatlen> oxi: You may want to add that comment here: https://issues.apache.org/jira/browse/DERBY-4267
<oxi> kahatlen: thanks
<oxi> is there a maven repository with a fixed pom?
<kahatlen> oxi: I don't think so. from the latest comment on the jira issue, it seems
like there were problems getting 10.5.3.0 deployed.
<kahatlen> I haven't followed the discussion closely, but I think someone is getting
really close to making it work now  :) 
<oxi> kahatlen: I see.

I have looked inside the poms and they all have this error. That is, instances of derby.version
were not replaced with 10.5.3.0. It seems that if you set derby.version on the java command
line when you run mvn, the version is picked up when the file names of the artifacts are created
but the version number is not substituted into the contents of the poms.

I don't think that I should fix these poms by hand. I think we should improve the patch to
handle this and then redeploy. I don't know if there is any harm in leaving the broken poms
in the repository until we can post fixed poms.

> Investigate why Derby 10.5.1.1 is not available in the maven2 repositories
> --------------------------------------------------------------------------
>
>                 Key: DERBY-4267
>                 URL: https://issues.apache.org/jira/browse/DERBY-4267
>             Project: Derby
>          Issue Type: Task
>          Components: Build tools
>    Affects Versions: 10.5.1.1, 10.6.0.0
>            Reporter: H.-Dirk Schmitt
>         Attachments: derby-4267-1a-maven2.diff, derby-4267-1a-maven2.stat, derby-4267-2a-using_ant_task.diff,
derby-4267-2a-using_ant_task.stat, derby-4267-2b-using_ant_task.diff, derby-4267-2b-using_ant_task.stat,
maven2.zip
>
>
> Only 10.4.2.0 and older are available in the maven 2 repositories.
> May you please also provide the new version.
> Please see also https://issues.apache.org/jira/browse/DERBY-4220

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message